ComparisonEU

MDR vs IVDR medical devices and IVDs compared

MDR covers medical devices and their accessories. IVDR covers in vitro diagnostic medical devices, including products and software whose intended purpose is tied to in vitro examination of specimens.

This comparison helps separate scope, classification, conformity assessment, documentation, evidence, UDI/EUDAMED, PMS, and vigilance workstreams without assuming one device file can serve both laws.

Author
Sorena AI
Published
May 9, 2026
Updated
Jul 25, 2026
Sections
3

Structured answer sets in this page tree.

Primary sources
10

Cited legal and guidance references.

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

MDR and IVDR are parallel EU regulations with different scope and classification rules. A product is an when its intended purpose is to provide specified medical information through in vitro examination of specimens derived from the human body, including blood and tissue donations. Use MDR for other medical devices and accessories. A product's format or use in a laboratory does not decide the route.

Side-by-side comparison

MDR vs IVDR: medical device and IVD routing

A focused comparison for deciding whether a product, software module, kit, assay workflow, or connected instrument belongs under MDR, IVDR, or neither, and for identifying separately qualified MDR and IVDR products or modules in a combined release.

Review all sources
First framework
MDR

Use MDR for medical devices, accessories, and covered non-medical-purpose products where the intended purpose and risk profile fit Regulation (EU) 2017/745.

Second framework
IVDR

Use IVDR for in vitro diagnostic medical devices and IVD-related software or accessories where the intended purpose is tied to in vitro examination of specimens.

Comparison row 1

Scope boundary

MDR

MDR applies to medical devices and accessories, and the MDR text expressly separates its scope from in vitro diagnostic medical devices.

IVDR

IVDR applies to in vitro diagnostic medical devices and accessories, including IVD software when the intended purpose fits the IVDR definition.

Operational implication

Start with intended purpose and data source, then determine which regulation applies to each product or module, or record that it is outside both regimes. For a combined release, identify separately qualified MDR and IVDR products or modules.

Comparison row 2

Classification rules

MDR

MDR uses medical-device classification rules that route devices into MDR risk classes such as class I, IIa, IIb, and III.

IVDR

IVDR classifies IVDs as A, B, C, or D under seven Annex VIII rules. Classification considers the device's intended purpose and the risk to the individual and public health; class D carries the highest risk.

Operational implication

Do not translate an MDR class into an IVDR class. Re-run the classification rule set under the regulation that applies to the intended purpose.

Comparison row 3

Trigger

MDR

For MDR, class I devices are generally under manufacturer responsibility, while class IIa, IIb, and III devices require an appropriate level of notified-body involvement.

IVDR

IVDR class A devices generally use manufacturer self-declaration unless supplied sterile. Class A sterile, B, C, and D devices require notified-body involvement under Article 48, with the assessment scope increasing by class and device type.

Operational implication

Confirm the notified body's IVDR designation and relevant device codes. An MDR designation does not establish IVDR authority.

Comparison row 4

Core obligations

MDR

MDR technical documentation should support the device description, intended purpose, classification, general safety and performance requirements, risk management, clinical evaluation, PMS, UDI, and conformity route.

IVDR

IVDR technical documentation should support the IVD intended purpose, classification, performance evidence, UDI, EUDAMED, PMS, vigilance, and conformity route for the IVD product.

Operational implication

Use a shared document only when it is mapped to both MDR and IVDR requirements; otherwise maintain separate files and cross-references.

Comparison row 5

Evidence record

MDR

MDR evidence centers on clinical evaluation and clinical evidence, including PMCF where applicable, to support safety and performance throughout the device lifecycle.

IVDR

IVDR performance evaluation must establish scientific validity, analytical performance, and, where applicable, clinical performance. The performance evaluation and its report are updated across the lifecycle with post-market performance follow-up and PMS data.

Operational implication

Identify which evidence supports the analyte or marker relationship, measurement performance, and correlation with the clinical condition or process. Do not label an MDR clinical evaluation as an IVDR performance evaluation.

Comparison row 6

UDI and EUDAMED

MDR

MDR devices need UDI handling and Basic UDI-DI linkage. Since 28 May 2026, the Actor, UDI/Device, and Notified Bodies and Certificates modules have been mandatory where applicable. The Vigilance and Post-Market Surveillance module remains in development, and the Market Surveillance module is for competent authorities and the Commission.

IVDR

IVDR devices also use UDI and the applicable mandatory EUDAMED modules, including IVD-specific device or kit handling. The Vigilance and Post-Market Surveillance module remains in development.

Operational implication

Use each mandatory EUDAMED module only for the actors and records in its scope, and continue the applicable national vigilance and PMS processes until that module becomes mandatory. Do not reuse an MDR UDI or Basic UDI-DI for an IVDR device unless the UDI rule and product identity actually allow it.

Comparison row 7

Enforcement

MDR

MDR manufacturers need PMS and vigilance records for the MDR device, including serious incidents and field safety corrective actions where reportable.

IVDR

IVDR manufacturers need PMS and vigilance records for the IVD device, and UDI can be part of reporting serious incidents and field safety corrective actions.

Operational implication

One complaint intake system can feed both regimes, but triage must identify the device, UDI, applicable regulation, report type, and authority or EUDAMED route.

Comparison row 8

Overlap and reuse

MDR

MDR artifacts can be reused only where the same product boundary, intended purpose, risk control, evidence method, and device version support the MDR requirement.

IVDR

IVDR artifacts can be reused only where the same facts support the IVD intended purpose, performance claim, classification, UDI, and PMS or vigilance obligation.

Operational implication

Create a bridge note for every shared artifact; otherwise a reviewer cannot tell whether evidence proves MDR conformity, IVDR conformity, or only a general quality-system control.

Comparison row 9

Practical decision rule

MDR

MDR applies to medical devices and accessories, and the MDR text expressly separates its scope from in vitro diagnostic medical devices.

IVDR

IVDR applies to in vitro diagnostic medical devices and accessories, including IVD software when the intended purpose fits the IVDR definition.

Operational implication

Start with intended purpose and data source, then determine which regulation applies to each product or module, or record that it is outside both regimes. For a combined release, identify separately qualified MDR and IVDR products or modules.

Practical decision rule

How should teams decide between MDR and IVDR?

  • Write the intended-purpose statement first, then identify whether MDR, IVDR, or neither applies to each product or module. For mixed MDR and IVD data sources, determine which source substantially drives the intended purpose.
  • Classify the product under the applicable regulation instead of translating a class from the other regime.
  • Pick the conformity route and notified body based on the applicable legislation and device class.
  • Build separate clinical or performance evidence conclusions, then map any shared technical, UDI, EUDAMED, PMS, or vigilance artifact to both regimes.
  • Reopen the decision after a claim change, software change, specimen or data-source change, supplier change, market-role change, incident, or new notified-body finding.
Section 1

Where the MDR and IVDR split

The first boundary check is the intended purpose stated in labels, instructions, promotional materials, sales materials, and the evaluation file. MDR qualification is tied to the medical-device definition and MDR accessories. IVDR qualification requires an in vitro examination of specimens derived from the human body and an intended purpose within the IVDR definition, such as information on a physiological or pathological process, congenital impairment, predisposition to a condition or disease, suitability for a potential recipient, likely treatment response, or therapeutic monitoring.

Representative IVDR products include reagents, calibrators, control materials, test kits, specimen receptacles, instruments, and software when their intended purpose meets that specimen-examination test. General laboratory equipment and research-use products are not pulled into IVDR only because an IVD laboratory uses them; the manufacturer's stated purpose and the product's actual characteristics still need review.

Software is not an IVD merely because it receives laboratory data. It falls under IVDR when the manufacturer intends the software, alone or in combination, to provide information that meets the IVD definition. Software that only stores, transfers, searches, or displays data without an IVD purpose needs a separate qualification analysis.

Do not merge the routes just because the same platform, sensor, software module, or customer workflow is involved. A release may need an MDR file, an IVDR file, or a documented conclusion that one route does not apply.

  • Check whether the product acts on, monitors, diagnoses, treats, compensates for, or supports a medical purpose as a medical device.
  • Check whether the product or software uses in vitro examination of specimens, IVD instrument output, or IVD-derived data as the basis for the claimed result.
  • For software, record whether it is a device in its own right, an accessory, or software that drives or influences another device.
  • Separate Annex XVI non-medical-purpose MDR products from IVDR products; do not treat aesthetic-purpose MDR coverage as an IVD route.
Section 2

Evidence files are similar in shape, different in substance

Both regimes require manufacturers to maintain technical documentation and post-market records, but the evidence question changes. MDR evidence is built around general safety and performance requirements, classification, conformity assessment, clinical evaluation, PMCF where applicable, PMS, vigilance, UDI, and EUDAMED records.

For IVDR, do not copy the MDR clinical-evaluation file into the IVD file. IVDR performance evaluation is a continuous lifecycle process covering scientific validity, analytical performance, and, where applicable, clinical performance. The performance evaluation report must bring those reports together and assess whether the clinical evidence supports the intended purpose and applicable general safety and performance requirements.

  • Maintain one comparison memo that names the product, intended purpose, data inputs, user, specimen or patient context, market role, and applicable regulation.
  • Keep separate evidence indexes for MDR clinical evaluation and IVDR performance evaluation, even when the same quality system or risk process supports both. For IVDR, identify the analyte or marker relationship, specimen types, analytical performance parameters, clinical-performance claims, data gaps, and post-market performance follow-up.
  • Tag shared documents, such as risk management, software validation, standards mapping, UDI assignments, and EUDAMED registrations, to the regulation and device version they support.
  • Use the comparison as a release gate: unresolved scope, classification, evidence, UDI, or EUDAMED gaps should block reuse of the other regime's file.
Recommended next step

Route MDR and IVDR work before reusing evidence

Separate medical-device and IVD scope, evidence, UDI, EUDAMED, PMS, and vigilance decisions before combining release files or customer assurances.

Section 3

MDR vs IVDR checklist

Use this checklist when a product, software module, assay workflow, connected instrument, or kit could fall under MDR or IVDR, or when a combined release contains separately qualified MDR and IVDR products or modules. Record the result in a controlled routing memo with the facts, rules, evidence owners, and review triggers.

  • Intended purpose: compare claims in labels, instructions, promotional material, sales material, clinical evaluation, and performance evaluation drafts.
  • Data source: identify whether the result depends on patient/device observations, in vitro specimen examination, IVD instrument output, or mixed inputs.
  • Classification: map MDR devices to classes I, IIa, IIb, or III under MDR Annex VIII. Map IVDs to classes A, B, C, or D under IVDR Annex VIII, with class D as the highest risk class. Do not translate class labels across regimes.
  • Conformity route: identify whether a notified body is needed and which certificate, technical documentation assessment, or manufacturer declaration path is relevant. Under IVDR, class A devices generally use manufacturer self-declaration unless supplied sterile; class A sterile, B, C, and D devices require the IVDR conformity route and notified-body involvement specified in Article 48.
  • Documentation: prepare MDR technical documentation and clinical evidence separately from IVDR technical documentation and performance evidence unless a shared artifact is explicitly mapped.
  • UDI and EUDAMED: assign Basic UDI-DI and UDI records to the actual device, kit, system, procedure pack, or configurable product and register data in the relevant EUDAMED workflow.
  • PMS and vigilance: route complaints, serious incidents, field safety corrective actions, PSUR or PMS reports, and EUDAMED vigilance data to the regulation that controls the device.
  • Boundary decision: document MDR, IVDR, or neither for each product or module; for a combined release, identify any separately qualified MDR and IVDR products or modules. Record the facts that would reopen the decision after a claim, software, supplier, assay, data-source, or market-role change.
Primary sources

References and citations

webgate.ec.europa.eu
Referenced sections
  • Supports keeping EUDAMED routing visible in the decision record.
"lifecycle of medical devices"
health.ec.europa.eu
Referenced sections
  • Confirms which modules are mandatory, which actors use the Market Surveillance module, and that the Vigilance and Post-Market Surveillance module remains in development.
"Vigilance and post-market surveillance (in development)"
single-market-economy.ec.europa.eu
Referenced sections
  • Commission source for harmonised standards and voluntary use of standards to demonstrate compliance with EU legislation.
"Harmonised standards are European standards"
health.ec.europa.eu
Referenced sections
  • Supports connecting reused UDI and device-identity records to the correct documentation and device family.
"connect devices with same intended purpose"
health.ec.europa.eu
Referenced sections
  • Non-binding MDCG guidance confirming continued national vigilance processes until the Vigilance and Post-Market Surveillance module becomes mandatory.
"economic operators need to continue using the national processes"
health.ec.europa.eu
Referenced sections
  • Supports checking notified-body designation for MDR or IVDR conformity assessment.
"filtered by legislation"
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.
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 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.