A practical comparison for mixed device portfolios.
Use this to decide which regulation applies, how classification differs, and what that means for evidence and operations.
Structured answer sets in this page tree.
Cited legal and guidance references.
MDR and IVDR share concepts (economic operators, conformity assessment, technical documentation, UDI/EUDAMED), but they diverge in scope and evidence expectations. If you build software and diagnostics workflows, the intended-purpose question becomes the single most important decision.
MDR covers medical devices used on or in the human body (including many software functions) for prevention/diagnosis/monitoring/treatment-related intended purposes.
IVDR covers in vitro diagnostic medical devices: products intended to examine specimens derived from the human body to provide information about physiological/pathological states, congenital abnormalities, safety/compatibility with recipients, or to predict treatment responses.
Research Copilot can take EU MDR vs IVDR What Changes from how this topic compares with adjacent regulations or standards to a reusable workflow inside Sorena. Teams working on EU MDR vs IVDR can keep owners, evidence, and next steps aligned without copying this guide into separate documents.
Start from EU MDR vs IVDR What Changes and answer scope, timing, and interpretation questions with cited outputs.
Review your current process, evidence gaps, and next steps for EU MDR vs IVDR What Changes.
MDR classification uses Annex VIII rules (Classes I, IIa, IIb, III). IVDR uses a separate classification approach (Classes A, B, C, D) driven by diagnostic impact and public health risk.
Operational impact: classification determines the conformity assessment route and the depth of evidence expected.
The evidence story differs: MDR focuses on clinical evaluation for safety and performance in patients/users; IVDR focuses on performance evaluation (scientific validity, analytical performance, clinical performance) tied to intended diagnostic use.
Practical rule: write your claims as testable endpoints and build traceability from claims, evidence, and conclusions.