---
title: "When do software or products make medical purpose claims under the EU MDR?"
canonical_url: "https://www.sorena.io/artifacts/eu/medical-device-regulation/faq/medical-purpose-claims"
source_url: "https://www.sorena.io/artifacts/eu/medical-device-regulation/faq/medical-purpose-claims"
author: "Sorena AI"
description: "EU MDR FAQ on medical purpose claims, intended purpose evidence, software qualification, Annex XVI contrasts, and records to keep."
published_at: "2026-05-09"
updated_at: "2026-05-09"
keywords:
  - "EU MDR medical purpose claims"
  - "medical device software"
  - "intended purpose"
  - "Annex XVI"
  - "MDR Article 2"
  - "EU Medical Device Regulation"
  - "EU MDR"
  - "Medical Purpose Claims"
  - "EU MDR FAQ"
---
**[SORENA](https://www.sorena.io/)** - AI-Powered GRC Platform

[Home](https://www.sorena.io/) | [Solutions](https://www.sorena.io/solutions) | [Artifacts](https://www.sorena.io/artifacts) | [About Us](https://www.sorena.io/about-us) | [Contact](https://www.sorena.io/contact) | [Portal](https://app.sorena.io)

---

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

EU MDR FAQ on medical purpose claims, intended purpose evidence, software qualification, Annex XVI contrasts, and records to keep.

*FAQ* *EU*

## 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.

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

## 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.

The MDR does not limit intended purpose 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.

Sources for this answer:

- [Regulation (EU) 2017/745 on medical devices](https://eur-lex.europa.eu/eli/reg/2017/745/oj?ref=sorena.io) - Defines medical devices, intended purpose, labels, instructions for use, and prohibited misleading claims.

## 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 Annex XVI 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 intended purpose. 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.

Sources for this answer:

- [MDCG 2019-11 - Qualification and classification of software](https://health.ec.europa.eu/document/download/b45335c5-1679-4c71-a91c-fc7a4d37f12b_en?filename=mdcg_2019_11_en.pdf&ref=sorena.io) - MDCG guidance for software qualification, including medical purpose, data actions, individual-patient benefit, accessories, and software driving or influencing devices.

## How does Annex XVI differ from a medical purpose claim?

Annex XVI 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 Annex XVI 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 Annex XVI 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.

Sources for this answer:

- [Regulation (EU) 2017/745 on medical devices](https://eur-lex.europa.eu/eli/reg/2017/745/oj?ref=sorena.io) - MDR source for Annex XVI and products with both medical and non-medical intended purposes.
- [Commission Implementing Regulation (EU) 2022/2346](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32022R2346&ref=sorena.io) - Sets common specifications for Annex XVI product groups without an intended medical purpose.

## 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 intended purpose 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.

Sources for this answer:

- [Regulation (EU) 2017/745 on medical devices](https://eur-lex.europa.eu/eli/reg/2017/745/oj?ref=sorena.io) - Annex II source for technical-documentation evidence, including intended purpose, qualification rationale, classification rationale, labels, and instructions.
- [MDCG 2019-11 - Qualification and classification of software](https://health.ec.europa.eu/document/download/b45335c5-1679-4c71-a91c-fc7a4d37f12b_en?filename=mdcg_2019_11_en.pdf&ref=sorena.io) - Supports keeping software-specific evidence around function, intended purpose, patient-specific benefit, and device-driving or device-influencing behavior.

## Primary sources

- [Regulation (EU) 2017/745 on medical devices](https://eur-lex.europa.eu/eli/reg/2017/745/oj?ref=sorena.io) - Primary MDR source for medical-device definition, intended purpose evidence, Article 7 claims, Annex XVI mixed-purpose handling, and Annex II records.
  - Quote: "intended by the manufacturer to be used"
- [MDCG 2019-11 - Qualification and classification of software](https://health.ec.europa.eu/document/download/b45335c5-1679-4c71-a91c-fc7a4d37f12b_en?filename=mdcg_2019_11_en.pdf&ref=sorena.io) - MDCG software guidance for medical device software qualification, software location, non-medical functions, and software driving or influencing a device.
  - Quote: "regardless of its location"
- [Commission Implementing Regulation (EU) 2022/2346](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32022R2346&ref=sorena.io) - Annex XVI common-specifications source for listed product groups without an intended medical purpose.
  - Quote: "common specifications for the groups of products"

## Topic Guides

- [Custom-made medical devices under the EU MDR | EU MDR FAQ](/artifacts/eu/medical-device-regulation/faq/custom-made-devices.md): 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](/artifacts/eu/medical-device-regulation/annex-ii-and-iii-technical-documents.md): 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](/artifacts/eu/medical-device-regulation/annex-viii-classification.md): 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](/artifacts/eu/medical-device-regulation/annex-xvi-products.md): source-linked EU MDR guide for Annex XVI products: listed product groups, common specifications, clinical evidence, notified-body route, UDI, EUDAMED, PMS, and vigilance evidence before launch.
- [EU MDR Applicability Test](/artifacts/eu/medical-device-regulation/applicability-test.md): 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](/artifacts/eu/medical-device-regulation/change-assessment-workflow.md): 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](/artifacts/eu/medical-device-regulation/checklist.md): 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](/artifacts/eu/medical-device-regulation/classification-workflow.md): 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](/artifacts/eu/medical-device-regulation/clinical-evaluation-overview.md): 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](/artifacts/eu/medical-device-regulation/clinical-evaluation-report-template.md): A source-linked 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](/artifacts/eu/medical-device-regulation/clinical-evidence.md): source-linked EU MDR guide to clinical evaluation, clinical investigations, equivalence, PMCF, GSPR support, technical documentation, and notified-body review.
- [EU MDR compliance obligations](/artifacts/eu/medical-device-regulation/compliance.md): 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](/artifacts/eu/medical-device-regulation/conformity-route-workflow.md): source-linked 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](/artifacts/eu/medical-device-regulation/deadlines-and-compliance-calendar.md): Grounded EU MDR calendar for application, legacy-device transition, UDI, EUDAMED, and recurring QMS, technical documentation, clinical, PMS, vigilance, certificate, and change reviews.
- [EU MDR Device Classification Guide](/artifacts/eu/medical-device-regulation/device-classification-guide.md): 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](/artifacts/eu/medical-device-regulation/eudamed-and-udi.md): source-linked 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](/artifacts/eu/medical-device-regulation/faq.md): 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](/artifacts/eu/medical-device-regulation/legacy-device-transition.md): source-linked EU MDR legacy device transition guide covering Regulation (EU) 2023/607 conditions, certificate validity, significant-change limits, surveillance, PMS, vigilance, QMS, and evidence records.
- [EU MDR notified body route selection](/artifacts/eu/medical-device-regulation/notified-body-route-selection.md): 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](/artifacts/eu/medical-device-regulation/penalties-and-fines.md): source-linked EU MDR penalties and enforcement-risk guide covering Article 113, Member State penalty rules, market restrictions, recalls, certificate consequences, and evidence.
- [EU MDR PMS and Vigilance Guide](/artifacts/eu/medical-device-regulation/pms-and-vigilance.md): 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](/artifacts/eu/medical-device-regulation/post-market-surveillance-and-vigilance.md): source-linked 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](/artifacts/eu/medical-device-regulation/post-market-surveillance-plan-template.md): A source-linked 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](/artifacts/eu/medical-device-regulation/qms-and-technical-file.md): 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](/artifacts/eu/medical-device-regulation/qms.md): 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](/artifacts/eu/medical-device-regulation/qualification-and-borderline-products.md): 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](/artifacts/eu/medical-device-regulation/qualification-workflow.md): 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](/artifacts/eu/medical-device-regulation/requirements.md): 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](/artifacts/eu/medical-device-regulation/rule-11-software.md): 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](/artifacts/eu/medical-device-regulation/faq/significant-changes.md): FAQ on MDR significant changes for legacy devices, including intended-purpose, design, software, material, sterilisation, clinical, QMS, notified-body, and evidence impacts.
- [EU MDR Transition Timelines: practical guide](/artifacts/eu/medical-device-regulation/transition-timelines.md): EU Medical Device Regulation guide to Transition Timelines with scope decisions, owner actions, evidence records, source-linked citations, and practical next steps.
- [EU MDR UDI and EUDAMED registration guide](/artifacts/eu/medical-device-regulation/udi-and-eudamed.md): 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](/artifacts/eu/medical-device-regulation/vigilance-reporting-workflow.md): 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](/artifacts/eu/medical-device-regulation/faq/udi-di-and-basic-udi-di.md): EU MDR FAQ explaining what Basic UDI-DI and UDI-DI identify, how they connect to UDI carriers, EUDAMED records, change triggers, and retained evidence.
- [MDR vs AI Act for medical-device software](/artifacts/eu/medical-device-regulation/mdr-vs-ai-act.md): Compare MDR software qualification, classification, clinical evidence, QMS, PMS, UDI, EUDAMED, and notified-body evidence boundaries against cautiously scoped AI Act overlap.
- [MDR vs GPSR: medical-device boundary checks](/artifacts/eu/medical-device-regulation/mdr-vs-gpsr.md): 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](/artifacts/eu/medical-device-regulation/mdr-vs-ivdr.md): Compare EU MDR and IVDR scope, classification, conformity routes, technical documentation, clinical or performance evidence, UDI, EUDAMED, PMS, and vigilance.
- [MDR vs Product Liability Directive evidence comparison](/artifacts/eu/medical-device-regulation/mdr-vs-product-liability-directive.md): Compare EU MDR market-access evidence with Product Liability Directive exposure without treating compliance records as a liability outcome.
- [What should an EU MDR PMCF plan and report cover? | EU MDR FAQ](/artifacts/eu/medical-device-regulation/faq/pmcf.md): 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](/artifacts/eu/medical-device-regulation/faq/class-changes.md): 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?](/artifacts/eu/medical-device-regulation/faq/equivalence.md): 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](/artifacts/eu/medical-device-regulation/faq/psur.md): 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](/artifacts/eu/medical-device-regulation/faq/accessories.md): 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 regulated as SaMD under the EU MDR? | EU MDR FAQ](/artifacts/eu/medical-device-regulation/faq/software-and-samd.md): Concise EU MDR FAQ on software qualification, intended medical purpose, Rule 11 classification, modules, clinical evidence, change assessment, UDI, and EUDAMED.
- [Which devices need an SSCP under the EU MDR and what should it include? | EU MDR FAQ](/artifacts/eu/medical-device-regulation/faq/sscp.md): EU MDR FAQ on when an SSCP is required, who prepares, validates, uploads, and updates it, and what evidence should support the summary.
- [Which EUDAMED modules matter under the EU MDR? | EU MDR FAQ](/artifacts/eu/medical-device-regulation/faq/eudamed-modules.md): EU MDR FAQ mapping EUDAMED modules to actor registration, UDI/device data, certificates, clinical investigations, vigilance/PMS, market surveillance, and practical records.

*Recommended next step*

*Placement: after evidence section*

## 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.

- [Open Research Copilot](/solutions/research-copilot.md): Answer MDR scope and qualification questions with cited outputs.
- [Talk through implementation](/contact.md): Review your claim set, software functions, evidence record, and next actions.


---

[Privacy Policy](https://www.sorena.io/privacy) | [Terms of Use](https://www.sorena.io/terms-of-use) | [DMCA](https://www.sorena.io/dmca) | [About Us](https://www.sorena.io/about-us)

(c) 2026 Sorena AB (559573-7338). All rights reserved.

Source: https://www.sorena.io/artifacts/eu/medical-device-regulation/faq/medical-purpose-claims