We use privacy-by-default, cookieless analytics.

Optional analytics cookies are used only if you accept them.

Read our Terms of Use and Privacy Policy.

FAQEU

EU MDR FAQ Medical Purpose Claims

A product or software can fall within the EU MDR when the manufacturer intends it for a medical purpose such as diagnosis, prevention, monitoring, prediction, prognosis, treatment, or alleviation.

Assess the claim against the manufacturer's labels, instructions, promotional and sales statements, clinical evaluation, software functions, and any Annex XVI no-medical-purpose positioning.

Back to main artifactReview sources
Author
Sorena AI
Published
May 9, 2026
Updated
Jul 24, 2026
Questions
4

Structured answer sets in this page tree.

Primary sources
4

Cited legal and guidance references.

Publication metadata
Sorena AI
Published May 9, 2026
Updated Jul 24, 2026
Overview

Under the EU MDR, medical purpose claims are assessed through the device definition and the manufacturer's . Look at what the product or software says it does for human beings, and preserve the evidence showing how that intended purpose was derived.

Search this module

Find a question or answer quickly

4 of 4 questions
Question 1

When does a claim create MDR medical-device scope?

A product, including software, is within the MDR device definition when the manufacturer intends it to be used for one or more MDR medical purposes for human beings. Core medical-purpose language includes diagnosis, prevention, monitoring, prediction, prognosis, treatment, or alleviation of disease, injury, or disability; investigation, replacement, or modification of anatomy or a physiological or pathological process or state; and certain in vitro information uses.

Do not use the MDR reference to in vitro examination as a shortcut for an IVD decision. Regulation (EU) 2017/746 is the principal framework for in vitro diagnostic medical devices, while this page addresses qualification under the MDR. A product that examines human specimens needs a separate MDR/IVDR scope analysis based on its and the applicable definitions.

The MDR does not limit to a single formal statement. It is read from data supplied by the manufacturer on the label, instructions for use, promotional or sales materials or statements, and as specified in the clinical evaluation. Advertising and product claims also matter because Article 7 prohibits claims that mislead users or patients about intended purpose, safety, or performance.

  • Treat phrases such as diagnose, predict, monitor, treat, triage, detect, screen, clinical decision support, therapy recommendation, or patient-specific risk score as MDR qualification triggers to assess, not as copy-only choices.
  • Review the live claim set across packaging, app-store text, website pages, sales decks, manuals, onboarding screens, demo scripts, support articles, and clinical evaluation material.
  • If the intended use changes from wellness, administration, or information transfer into patient-specific medical information or device control, reopen the qualification and classification rationale.

When do software or products make medical purpose claims under the EU MDR?

They make MDR-relevant medical purpose claims when the manufacturer presents the product or software as being intended for an MDR medical purpose for human beings, such as diagnosis, prevention, monitoring, prediction, prognosis, treatment, or alleviation. Check the evidence in labels, instructions for use, promotional and sales materials, statements, and clinical evaluation, not only the product team's internal label.

Can marketing copy affect the analysis?

Yes. The MDR definition of includes promotional and sales materials or statements, and Article 7 addresses misleading claims in labelling, instructions, making available, putting into service, and advertising. Keep screenshots or controlled copies of public claims and sales materials with the qualification rationale.

Citations
Question 2

How should software and borderline functions be handled?

MDCG software guidance says software must have a medical purpose on its own to qualify as medical device software, unless it is an accessory, an product, or software that drives or influences a medical device. The location of the software, such as cloud, mobile, computer, or a hardware device, does not determine qualification.

The practical split is the function and . General administration, invoicing, staff planning, storage, archival, communication, simple search, or population-only analytics are not enough by themselves. Software that processes, analyses, creates, or modifies medical information for an individual patient and for a medical intended purpose can qualify as medical device software.

  • Keep a module-level map for mixed products: separate administrative, communication, display, control, and patient-specific analysis functions.
  • For software that drives or influences a hardware device, document whether it operates, controls, modifies, or supplies output related to the device's functioning.
  • For patient-specific outputs, record the input data, algorithmic action, output, intended user, medical purpose, and whether the output treats, diagnoses, drives, or informs clinical management.

Is software automatically outside the MDR if it only runs in the cloud or on a phone?

No. MDCG guidance says software may qualify regardless of location, including cloud, computer, mobile phone, or additional functionality on hardware. Qualification depends on and function, especially whether it creates or modifies patient-specific medical information or drives or influences a device.

Are hospital workflow or analytics tools medical device software?

Not merely because they are used in healthcare. MDCG guidance distinguishes non-medical administration, storage, communication, simple search, population analytics, and generic pathways from software that performs patient-specific medical analysis or supports diagnosis, therapy, monitoring, or other MDR medical purposes.

Citations
Question 3

How does Annex XVI differ from a medical purpose claim?

is the MDR route for listed groups of products without an intended medical purpose, such as certain contact lenses, invasive anatomy-modification products, dermal fillers, adipose-tissue reduction equipment, high-intensity electromagnetic radiation equipment for skin treatment, and brain-stimulation equipment. That is different from saying a product has no MDR relevance.

The contrast matters: a product with both medical and non-medical intended purposes must satisfy both sets of applicable requirements. Do not use language to neutralize medical claims if the same product materials also claim diagnosis, treatment, monitoring, or another MDR medical purpose.

  • Identify whether the product is listed in and whether the claim set is limited to a non-medical purpose.
  • Check for mixed positioning, such as aesthetic promotion alongside therapeutic, diagnostic, or clinical-performance claims.
  • If both medical and non-medical purposes are claimed, preserve both analyses instead of forcing the product into a single bucket.

Does no medical purpose mean no MDR analysis?

No. brings specific listed products without an intended medical purpose into the MDR framework through common specifications. The key questions are whether the product is in an Annex XVI group, whether any medical purpose is also claimed, and whether the claim evidence supports a medical, non-medical, or mixed .

Citations
Question 4

What evidence should be retained?

Keep the qualification record with the technical documentation or equivalent product-compliance file. MDR Annex II expects a product description including and users, medical conditions to be diagnosed, treated or monitored where relevant, qualification rationale, classification rationale, labels, instructions for use, and user-facing specifications such as brochures or catalogues.

The evidence should let a reviewer reconstruct the decision without interviews. Keep the source rule, the claim inventory, the software or product function map, the intended-user and patient-population analysis, screenshots or controlled copies of claims, clinical-evaluation linkage where applicable, approvals, unresolved assumptions, and triggers for review after claim, feature, indication, user, output, or market changes.

  • Preserve the dated claim inventory and identify which claim text maps to each medical-purpose criterion.
  • Attach the labels, instructions for use, website and app-store copy, sales materials, release notes, and clinical evaluation excerpts reviewed.
  • For software, keep version, module, input, processing action, output, intended user, patient-specific benefit, and device-control or device-influence evidence.
  • Record the final qualification conclusion, classification follow-up if in scope, reviewer approvals, and the change triggers that reopen the analysis.
Citations
Recommended next step

Review the claim record before release

Use the MDR claim inventory, intended-purpose evidence, software function map, and Annex XVI contrast to decide whether the product needs MDR qualification and classification follow-up.

Research workflow
Open Research Copilot

Answer MDR scope and qualification questions with cited outputs.

Explore next step
Talk to Sorena
Talk through implementation

Review your claim set, software functions, evidence record, and next actions.

Explore next step
Primary sources

References and citations

MDCG 2019-11 - Qualification and classification of software
health.ec.europa.eu
Referenced sections
  • Supports keeping software-specific evidence around function, intended purpose, patient-specific benefit, and device-driving or device-influencing behavior.
"process, analyse, create or modify medical information"
Regulation (EU) 2017/745 on medical devices
eur-lex.europa.eu
Referenced sections
  • Annex II source for technical-documentation evidence, including intended purpose, qualification rationale, classification rationale, labels, and instructions.
"the rationale for the qualification of the product as a device"
Related guides

Explore more topics

Custom-made medical devices under the EU MDR | EU MDR FAQ
Concise EU MDR FAQ on custom-made device definition, mass-produced exclusions, Annex XIII statements, documentation, conformity assessment, PMS, vigilance, and records to retain.
EU MDR Annex II and III Technical Documentation
Build an MDR technical documentation index for Annex II device files and Annex III post-market surveillance evidence, including GSPR, risk, clinical, PMS, UDI, and EUDAMED records.
EU MDR Annex VIII Classification Guide
Classify EU MDR medical devices under Annex VIII using intended purpose, duration, invasiveness, active device and software rules, and conformity assessment impact.
EU MDR Annex XVI products without a medical purpose
EU MDR guide for Annex XVI products: listed groups, common specifications, binding reclassification rules, clinical evidence, notified-body route, transition conditions, UDI, EUDAMED, PMS, and vigilance.
EU MDR Applicability Test
Test whether a product, accessory, software function, or Annex XVI product falls under the EU Medical Device Regulation, and record the evidence for the next classification step.
EU MDR change assessment workflow
Assess EU MDR device, design, software, intended purpose, QMS, clinical, PMS, UDI, classification, and notified-body impacts before releasing a medical device change.
EU MDR Checklist for Medical Device Compliance
Practical EU MDR checklist covering qualification, classification, conformity assessment, technical documentation, GSPR, clinical evidence, UDI, EUDAMED, PMS, vigilance, QMS, and legacy transition evidence.
EU MDR classification workflow
A concrete EU MDR classification workflow for intended purpose, device or accessory qualification, Annex VIII rule selection, Rule 11 software review, class outcome, and notified body impact.
EU MDR Clinical Evaluation Overview
EU MDR clinical evaluation overview covering Article 61, Annex XIV, clinical data sources, equivalence, PMCF, CER evidence, notified body review, GSPR, and benefit-risk support.
EU MDR Clinical Evaluation Report Template
A cited EU MDR clinical evaluation report template covering intended purpose, GSPR linkage, clinical data appraisal, equivalence limits, PMCF, conclusions, and reviewer signoff.
EU MDR clinical evidence guide
EU MDR guide to clinical evaluation, clinical investigations, equivalence, PMCF, GSPR support, technical documentation, and notified-body review.
EU MDR compliance obligations
EU MDR compliance guide for device qualification, classification, conformity assessment, QMS, technical documentation, UDI, EUDAMED, PMS, vigilance, and legacy transition controls.
EU MDR conformity route workflow
EU MDR workflow for classifying a device, choosing the conformity assessment route, preparing technical and QMS evidence, and reaching certificate, DoC, UDI, EUDAMED, and CE outputs.
EU MDR deadlines and compliance calendar
EU MDR calendar for application, conditional legacy-device transition, UDI carrier dates, mandatory EUDAMED modules, and recurring compliance reviews.
EU MDR Device Classification Guide
Classify an EU MDR medical device by intended purpose, Annex VIII duration, invasiveness, active-device and software rules, then document the conformity route impact.
EU MDR EUDAMED and UDI registration
cited MDR guide to Basic UDI-DI, UDI-DI, EUDAMED device registration, actor roles, labels, technical documentation, and UDI data governance.
EU MDR FAQ: qualification, evidence, UDI, and transition
Concise EU MDR FAQ covering device qualification, software classification, accessories, custom-made devices, clinical evidence, UDI, EUDAMED, notified bodies, significant changes, and legacy transition.
EU MDR Legacy Device Transition
EU MDR legacy-device guide to Article 120 eligibility, class-based end dates, certificate validity, significant changes, surveillance, and evidence.
EU MDR notified body route selection
Choose an EU MDR conformity assessment route by device class, Article 52 option, notified body designation scope, QMS readiness, technical documentation, clinical evidence, and certificate evidence.
EU MDR penalties and enforcement risk
EU MDR guide to Article 113 national penalties, authority measures, recalls, certificate action, and the evidence needed for a country-specific assessment.
EU MDR PMS and Vigilance Guide
EU MDR guide to post-market surveillance, PMCF updates, PMS reports, PSURs, serious incident reporting, FSCA/FSN handling, trend reporting, and evidence records.
EU MDR PMS and vigilance records
Cited EU MDR guide to PMS plans, PMS reports, PSURs, PMCF updates, serious incident and FSCA reporting, trend reporting, and EUDAMED evidence handling.
EU MDR PMS Plan Template for Medical Devices
A cited EU MDR post-market surveillance plan template covering device scope, PMS data sources, PMCF linkage, vigilance, trend reporting, PMSR or PSUR outputs, roles, cadence, and evidence records.
EU MDR QMS and technical file evidence map
Map EU MDR Article 10 QMS duties to Annex II and Annex III technical documentation, PMS, vigilance, UDI records, and notified-body review evidence.
EU MDR QMS requirements under Article 10
EU MDR QMS guide for Article 10 manufacturer controls covering regulatory strategy, design, risk, clinical evaluation, PMS, vigilance, UDI, suppliers, CAPA, and conformity records.
EU MDR qualification and borderline products
EU MDR qualification guide for medical purpose claims, accessories, software, Annex XVI products, and borderline routes to classification and conformity assessment.
EU MDR qualification workflow
A concrete EU MDR workflow for deciding whether a product is a medical device, accessory, Annex XVI product, IVD interface, medicinal-product interface, or non-MDR product before classification and conformity assessment.
EU MDR requirements checklist
Concrete EU MDR requirements for medical-device scope, classification, GSPR, conformity assessment, technical documentation, QMS, clinical evidence, UDI, EUDAMED, PMS, vigilance, and economic-operator records.
EU MDR Rule 11 software classification
Classify MDR medical device software under Rule 11 using intended purpose, diagnosis or therapy decision impact, physiological monitoring, conformity route, clinical evidence, and software-change records.
EU MDR significant changes FAQ: legacy-device transition and notified-body review
FAQ on MDR significant changes for legacy devices, including intended-purpose, design, software, material, sterilisation, clinical, QMS, notified-body, and evidence impacts.
EU MDR SSCP: Devices and Requirements
Decide whether an EU medical device needs an SSCP, see worked class IIa, IIb, and III examples, and check the required content, evidence, publication, and update controls.
EU MDR transition timeline and end dates
EU MDR chronology for 2021 application, 2023 amendments, 2024 eligibility milestones, and conditional 2026, 2027, and 2028 transition endpoints.
EU MDR UDI and EUDAMED registration guide
EU MDR guide to Basic UDI-DI, UDI-DI, UDI carriers, EUDAMED actor and device registration, change impacts, and evidence governance.
EU MDR vigilance reporting workflow
Concrete EU MDR vigilance workflow for incident intake, serious incident assessment, FSCA and FSN handling, trend reporting, EUDAMED caveats, CAPA, PMS, clinical evaluation updates, and records.
How should Basic UDI-DI and UDI-DI be assigned under the EU MDR? | EU MDR FAQ
EU MDR FAQ on Basic UDI-DI grouping, device and package UDI-DIs, UDI carriers, EUDAMED registration, change triggers, and required records.
MDR vs AI Act for medical-device software
Compare MDR and AI Act scope, high-risk classification, conformity assessment, evidence, monitoring, and timing for AI-enabled medical devices.
MDR vs EU Product Liability Directive
Compare MDR compliance evidence with EU product-liability claims, responsible parties, disclosure, presumptions, damage, and the December 2026 transition.
MDR vs GPSR: medical-device boundary checks
Compare MDR medical-device scope with general product-safety fallback questions for borderline, non-medical, and Annex XVI products.
MDR vs IVDR: medical devices and IVDs compared
Compare EU MDR and IVDR scope, classification, conformity routes, technical documentation, clinical or performance evidence, UDI, EUDAMED, PMS, and vigilance.
What should an EU MDR PMCF plan and report cover? | EU MDR FAQ
Under the EU MDR, PMCF is part of PMS and clinical evaluation. See what the plan, activities, report, updates, and retained evidence should cover.
What should manufacturers do when an EU MDR classification changes? | EU MDR FAQ
Concise EU MDR FAQ on classification changes, intended purpose, software, notified-body route impact, certificates, technical documentation, and retained evidence.
When can clinical equivalence be used under the EU MDR?
EU MDR FAQ on clinical equivalence, including technical, biological, and clinical characteristics, access to equivalent-device data, class III and implantable-device limits, clinical evaluation, PMCF, and retained evidence.
When is a PSUR required under the EU MDR and what should it contain? | EU MDR FAQ
EU MDR FAQ on PSUR scope, content, update cadence, PMS and PMCF links, notified-body handling, EUDAMED submission, and evidence to retain.
When is an accessory regulated under the EU MDR? | EU MDR FAQ
EU MDR FAQ on when an article is a medical device accessory, how intended purpose affects classification, and what evidence to keep.
When is software a medical device under the EU MDR?
EU MDR FAQ on medical device software qualification, Rule 11 and other classification rules, modules, evidence, software changes, UDI, and EUDAMED.
Which EUDAMED modules matter under the EU MDR? | EU MDR FAQ
EU MDR FAQ mapping EUDAMED modules to actor registration, UDI/device data, certificates, clinical investigations, vigilance/PMS, market surveillance, and practical records.