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 Classification Changes

Under the EU MDR, device class depends on the manufacturer-assigned intended purpose, the Annex VIII classification rules, and the device's inherent risks.

This answer applies when a claim, design, software function, clinical use, or legal transition assumption may move a device into a different MDR conformity route.

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

Structured answer sets in this page tree.

Primary sources
5

Cited legal and guidance references.

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

When an EU MDR device class may have changed, stop treating the old classification as reusable evidence. Reassess the and Annex VIII rule mapping, check whether software or a design/use change changes the route, involve the notified body where the route or certificate can be affected, and update the technical documentation before relying on the old certificate or declaration.

Search this module

Find a question or answer quickly

2 of 2 questions
Question 1

How should manufacturers assess an MDR class change?

Start with the as stated in labels, instructions for use, advertising, clinical documentation, and software release material. MDR classification is based on intended purpose and inherent risk, and Annex VIII applies the strictest applicable rule when more than one rule fits the device.

Treat the reassessment as a conformity-route question. A label update alone is insufficient. Moving from class I self-declaration into class Is, Im, Ir, IIa, IIb, or III can add notified-body involvement; moving between higher classes can change the depth of technical documentation, clinical evaluation, certificate scope, and surveillance expectations.

Keep classification and legacy-device significant-change decisions separate. A corrected or newly interpreted class does not by itself answer whether a design or intended-purpose change is significant under Article 120, and a non-significant legacy change does not validate the existing class. Record both analyses when both issues arise.

For software, reassess the medical purpose, the information the software provides, the clinical decision it supports, the user population and setting, and whether the software drives or influences another device. A change in algorithm, output, indication, user group, integration, or risk-control logic can change the Annex VIII analysis.

  • Re-map the product against Annex VIII using the current , device characteristics, duration, invasiveness, active-device status, substance or medicinal components, and software functions.
  • For software, document the decision or physiological process supported, the worst reasonably foreseeable harm from a wrong output, whether deterioration could be serious or irreversible, whether intervention could be surgical, and whether a monitored vital-parameter variation could create immediate danger.
  • Compare the new class with the existing declaration, notified-body certificate, Basic UDI-DI/device registration data, technical documentation, clinical evaluation, PMS/PMCF plans, labels, and instructions for use.
  • If the device is a legacy device relying on MDR transitional provisions, assess whether the change is a significant change in design or ; significant changes can prevent continued reliance on the legacy route.
  • Ask the notified body before implementation when the existing certificate, approved type, technical-documentation assessment, or surveillance arrangement may be affected.
  • Do not publish new claims, indications, target populations, software outputs, or system/procedure-pack combinations until the classification rationale and conformity route have been updated.

What should manufacturers do when an EU MDR device may be in the wrong class?

Re-run classification from the current and Annex VIII rules before relying on old evidence. Check whether the corrected class affects software qualification, the conformity assessment route, notified-body involvement, certificate scope, technical documentation, clinical evidence, PMS/PMCF plans, UDI/device registration data, labels, and instructions for use. If a legacy device also changed in design or intended purpose, run the separate Article 120 significant-change assessment.

What evidence should support an EU MDR class-change decision?

Keep a dated classification rationale showing the reviewed, Annex VIII rules considered, the strictest applicable rule, software or accessory analysis, old and new conformity route, notified-body correspondence, certificate or declaration impact, updated technical-documentation references, clinical/PMS changes, label or IFU changes, approver, and trigger for the next review.

Citations
Question 2

What evidence should be retained for an MDR class-change review?

The evidence file should let a reviewer see why the old class is still valid or why the device needs a new conformity route. Keep the classification rationale with the technical documentation rather than as a separate project note.

Where a notified body is involved, retain the submission, questions, decisions, certificate supplement or new-certificate path, and any surveillance-transfer or transitional-provision correspondence. Where the conclusion is that no class change occurred, retain the classification analysis and the device facts that kept the same Annex VIII rule and class. If a separate Article 120 review concludes that a legacy-device change is not significant, retain that assessment separately.

  • Intended-purpose evidence: current IFU, label, website and sales claims, clinical claims, target population, user setting, contraindications, and any planned claim changes.
  • Rule evidence: Annex VIII rule mapping, rule conflicts resolved by the highest applicable class, software analysis, accessory or system/procedure-pack analysis, and rationale for exclusions.
  • Route evidence: old and new conformity route, notified-body role, certificate/declaration status, Basic UDI-DI or device-registration impact, and affected technical-documentation sections.
  • Change evidence: design, material, sterilisation, software, algorithm, data model, cybersecurity, integration, manufacturing, supplier, or intended-use changes reviewed for significance.
  • Approval evidence: regulatory owner, quality approval, notified-body correspondence, open conditions, implementation hold/release decision, and post-market monitoring trigger.
Citations
Recommended next step

Document the class before changing the conformity route

Keep the intended purpose, Annex VIII mapping, old and new route, notified-body decision, technical-documentation updates, and release approval in one controlled record.

Research workflow
Open Research Copilot

Answer EU MDR scope, timing, and interpretation questions with cited outputs.

Explore next step
Talk to Sorena
Talk through implementation

Review your scope, evidence model, controls, and next actions.

Explore next step
Primary sources

References and citations

Regulation (EU) 2017/745 on medical devices
eur-lex.europa.eu
Referenced sections
  • MDR source for keeping technical documentation up to date and retaining certificates, declarations, and technical documentation for competent authorities.
"draw up and keep up to date technical documentation"
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.
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 do software or products make medical purpose claims under the EU MDR? | EU MDR FAQ
EU MDR FAQ on medical purpose claims, intended purpose evidence, software qualification, Annex XVI contrasts, and records to keep.
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.