V5 Ultimate
Compliance · The complete guide

IVDREU In Vitro Diagnostic Regulation (2017/746)

TL;DR

The EU In Vitro Diagnostic Regulation (IVDR, Regulation (EU) 2017/746) replaced the IVDD in May 2022, redefining risk classification, widening Notified Body oversight, formalizing performance evidence, and embedding UDI and EUDAMED transparency with staged legacy transitions through 2029.

Reviewed · By V5 Ultimate compliance team· 2,811 words · ~13 min read
AI · Explain it for MY operation

How does IVDR apply to your shop floor?

Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.

Your scale

01What the IVDR is and why it matters

Regulation (EU) 2017/746, the In Vitro Diagnostic Regulation (IVDR), is the EU’s end‑to‑end legal framework governing design, manufacture, performance evaluation, market access, and post‑market responsibilities for in vitro diagnostic medical devices. It became applicable on 26 May 2022, replacing Directive 98/79/EC (IVDD) and aligning IVD oversight with the EU’s broader, lifecycle model for medical devices.

IVDR inverts the legacy risk pyramid. Under IVDD, only a minority of IVDs required Notified Body involvement; under IVDR’s Annex VIII classification rules (A, B, C, D), the majority do. The regulation codifies a unified performance evaluation framework spanning scientific validity, analytical performance, and clinical performance, and it requires proactive post‑market performance follow‑up. It also mandates Unique Device Identification (UDI) and staged deployment of EUDAMED modules to increase transparency and traceability.

For high‑risk Class D devices, IVDR establishes EU Reference Laboratories to verify performance and, where applicable, batch release testing. Companion diagnostics, near‑patient testing, and software used for diagnostic purposes fall squarely within scope, and laboratory‑developed tests (LDTs) operated by health institutions are tightly controlled through specific derogations.

Practically, IVDR reshapes development and compliance rhythms. Manufacturers must operate a robust quality management system, produce auditable technical documentation aligned with Annexes I–III, and engage with a Notified Body for most classifications. Early classification decisions and evidence‑gap assessments are consequently critical for portfolio planning and resource allocation.

See also complementary topics: how the rules map to medical device classifications and the practical role of a Notified Body in conformity assessment, certification, and surveillance.

02Scope and applicability of IVDR

IVDR applies to devices and accessories intended by the manufacturer for the in vitro examination of specimens derived from the human body. This includes reagents, calibrators, controls, kits, instruments, software, and specimen receptacles when they drive a medical diagnostic purpose such as prediction, prognosis, monitoring, or predisposition assessment. Placement on the market, making available, and putting into service are all regulated events with distinct obligations for manufacturers, authorized representatives, importers, and distributors.

Companion diagnostics are explicitly covered and linked to medicinal product use, creating an interdependency with medicines authorities and, downstream, HTA processes in Member States. Software intended to provide information for diagnostic or therapeutic decisions is an IVD when its core function is to determine or support a diagnostic output, in contrast to purely administrative or general‑wellness tools.

Health institutions can use laboratory‑developed tests (LDTs) under strict conditions: they must have an appropriate quality management system, produce the tests on a non‑industrial scale, and use them to address specific patient needs when no equivalent CE‑marked device can meet the performance required. These derogations do not eliminate core safety and performance obligations, nor do they excuse inadequate documentation or oversight.

Borderlines with the EU Medical Device Regulation (MDR) hinge on intended purpose. Devices that act on the human body, or non‑diagnostic software, typically fall under MDR. Combination products and integrated systems require careful scoping to avoid fragmented responsibilities across multiple legal frameworks.

  • In scope: diagnostic reagents, control materials, calibrators, kits, instruments, and software intended to derive diagnostic information from human specimens.
  • Accessories specifically intended to enable an IVD to be used in accordance with its intended purpose.
  • Companion diagnostics linked to specific medicinal products and clinical decisions.
  • Near‑patient and self‑testing devices supplied to lay persons, with strengthened usability and labeling controls.
  • LDTs under health‑institution derogations, subject to strict conditions and Member‑State oversight.
  • Exclusions include research‑use‑only materials with no diagnostic intended purpose and general laboratory equipment without a medical claim.
  • Economic operators (manufacturers, authorized representatives, importers, distributors) each carry defined, auditable obligations.

Where functions straddle diagnostic and therapeutic decision support, alignment with MDR (Regulation (EU) 2017/745) becomes pivotal. Cross‑functional teams should document intended purpose rationales and comparison matrices to demonstrate why the IVD regime, or the EU MDR, is appropriate for each component.

03Risk classification under Annex VIII

Annex VIII of IVDR implements rule‑based classification across Classes A, B, C, and D. Classification reflects the risk of an incorrect result and its downstream impact on public health and individual patients, not merely device invasiveness. This construct markedly expands third‑party scrutiny compared to the IVDD era.

Class D covers assays with the highest public‑health risk, such as tests for transmissible agents in blood and organs or major life‑threatening diseases. Class C captures many diagnostic areas including oncology markers, companion diagnostics, and certain infectious disease assays. Class B includes a wide range of general IVDs, while Class A encompasses low‑risk devices like some laboratory instruments and specimen receptacles. Sterile Class A devices still require Notified Body assessment for sterility aspects.

Borderline examples illustrate how intended purpose and claims language drive risk. A software algorithm that stratifies cancer therapy may land in Class C as a companion diagnostic, while an instrument with no diagnostic claim may be Class A. Misclassification is costly; it triggers redesign of evidence packages, rework of technical files, and delays in Notified Body engagement.

Risk management is continuous. Hazard identification covers erroneous results, sample handling failures, interfering substances, cybersecurity of networked analyzers, and usability by lay users for self‑tests. The risk framework should inform verification and validation plans, clinical performance studies, and post‑market controls, and it must tie transparently to benefit‑risk conclusions in the technical documentation.

Manufacturers should anchor classification rationales in the exact wording of Annex VIII rules and rule‑implementing guidance. Traceability from intended purpose to rule application, to residual‑risk rationales and mitigations, demonstrates systematic application of state‑of‑the‑art risk control aligned with ISO 14971.

04Core requirements: GSPR, QMS, and technical documentation

Annex I enumerates the General Safety and Performance Requirements (GSPR). These include chemical, biological, and physical safety; performance characteristics; analytical and clinical claims; protection against environmental and cybersecurity risks; and robust information for users. Evidence must be risk‑based, testable, and consistent with the intended purpose, including for self‑testing and near‑patient use.

Technical documentation under Annex II must show conformity to the GSPR. It is a living dossier that explains design choices, specifications, verification and validation, performance evaluation, labeling and IFU content, manufacturing controls, and benefit‑risk justifications. Annex III extends this to post‑market surveillance planning, periodic reporting, and post‑market performance follow‑up.

A quality management system is mandatory and should align with state‑of‑the‑art practices. ISO 13485 provides the recognized baseline for device QMS design under IVDR, including design controls, supplier management, production process validation, and corrective and preventive action. The Person Responsible for Regulatory Compliance (PRRC) oversees release and surveillance obligations, ensuring technical documentation is continuously maintained.

Documentation must be structured for easy Notified Body review and for internal control. Maintain explicit trace matrices from GSPR to tests, from risk controls to verification evidence, and from performance claims to study results. Labeling and the instructions for use must be consistent, readable, and localized where required.

  • Define intended purpose and link each GSPR to specific, objective evidence.
  • Embed risk management outputs into verification, validation, and usability testing plans.
  • Consolidate performance evaluation across scientific validity, analytical performance, and clinical performance with justified claim limits.
  • Keep manufacturing and batch‑release controls auditable, including change control and supplier files.
  • Maintain PMS and PMPF plans with triggers for updates and escalation pathways.
  • Ensure IFU and labeling content reflect verified claims, warnings, and lay‑user needs where applicable.

Map your QMS to standards updates such as the ISO 13485 amendment, and use a structured system like QMS with robust instructions for use (IFU) controls to keep evidence coherent and inspection‑ready.

05Performance evaluation, studies, and ongoing evidence

Performance evaluation under IVDR is a unified, lifecycle process that integrates scientific validity, analytical performance, and clinical performance. Scientific validity establishes the association between an analyte and a clinical condition. Analytical performance addresses sensitivity, specificity, precision, interference, limits of detection and quantitation, and robustness. Clinical performance evaluates how the device’s output correlates with clinical status or outcomes in the target population and use environment.

Annex XIII requires a performance evaluation plan, a performance evaluation report, and a post‑market performance follow‑up (PMPF) plan with a living PMPF Evaluation Report. Literature, state‑of‑the‑art comparators, traceability to reference methods or materials, and well‑designed studies are expected. For companion diagnostics, alignment with medicinal product indications and benefit‑risk is essential.

Clinical performance studies must follow ethical approval processes, informed consent, robust data integrity practices, and appropriate statistical designs. Multi‑site studies should address lot variability, operator effects, and specimen handling. Where applicable, EU Reference Laboratories may verify performance claims for Class D devices, and they can require access to study data and reference panels.

Analytical method validation draws on established international norms for accuracy, precision, and detection limits. Where harmonized standards or common specifications exist, they should be used or justified. The evaluation must be revisited post‑market as real‑world data accrue, with claims adjusted if evidence shifts.

Operationally, a laboratory‑grade evidence engine helps. Standardize data capture, statistical plans, and file naming. Use role‑based controls for raw data and device history records, and integrate quality control trending so that outliers trigger PMPF updates. A dedicated Lab QC capability helps maintain traceability from study plans to results and final claims.

06Conformity assessment routes and Notified Body oversight

Conformity assessment varies by class. Class A, non‑sterile devices may follow internal control with self‑declaration. Sterile Class A, and Classes B, C, and D require Notified Body involvement. Routes include a full quality management system assessment with technical documentation review, EU type examination with production conformity, or production quality assurance approaches. The chosen path must be appropriate to the device’s risk and manufacturing model.

Notified Bodies will examine the QMS, sample technical documentation, performance evaluation, and post‑market plans. For high‑risk devices they will expand sampling and may require expert panels or EU Reference Laboratory interactions. Certificates specify scopes and conditions, and they trigger ongoing surveillance audits. Manufacturers must maintain readiness for unannounced audits and for evidence refreshes when changes occur.

Class D devices face additional scrutiny, including potential batch verification and confirmatory testing by EU Reference Laboratories. Traceability of critical materials, lot‑release criteria, stability studies, and contamination controls are routine focal points. For companion diagnostics, coordination with medicinal product regulatory timelines is often on the critical path.

Timely engagement reduces scheduling risks. Capacity constraints persist across several Notified Bodies, so a clean, well‑indexed file and a transparent change‑control narrative can materially reduce review iterations. Internal mock audits and document freezes prior to submission help avoid avoidable nonconformities.

  • Clean GSPR traceability matrix linking requirements, standards, and test reports.
  • Complete performance evaluation set: plan, reports, data, and PMPF linkages.
  • Validated manufacturing processes and lot‑release specifications with stability data.
  • Risk management file with usability, cybersecurity, and software lifecycle evidence where applicable.
  • Labeling and IFU consistent with claims, languages, and lay‑user controls.
  • Change‑control register with rationales and re‑verification strategy.

Practice continuous inspection readiness rather than episodic preparation. A structured audit readiness program aligned to the selected conformity route helps sustain certification and smooth surveillance cycles.

07UDI, EUDAMED, and market transparency

IVDR mandates Unique Device Identification to enhance traceability and safety. A Basic UDI‑DI groups devices with the same intended purpose, risk class, and essential design and manufacturing characteristics. Each market unit also carries a UDI‑DI and a UDI‑PI to identify production information such as lot or serial number and, when relevant, expiry date. Issuing agency rules and data formatting requirements must be followed.

EUDAMED is the EU database that interlinks actor registration, UDI device data, certificates, clinical and performance studies, vigilance, and market surveillance. As modules become mandatory, manufacturers will submit and maintain device and certificate data, and Competent Authorities and the public will gain greater visibility into safety communications and field actions.

Labeling, the instructions for use, and electronic records must consistently present identifiers. Master data governance is essential to keep device, packaging, and distribution systems aligned. Distributors and importers should confirm that UDI data match labeling and that obligations for language and readability are met in each Member State.

Global supply networks should anticipate scans at goods receipt, warehouse movements, and field servicing. Harmonization with GS1 standards supports interoperability with hospitals and laboratories. When devices transition from legacy identifiers, plan dual‑label periods and communication with users to avoid mix‑ups and stock obsolescence.

For terminology and data design, see UDI basics and how to distinguish UDI‑DI versus UDI‑PI. Robust master data, labeling controls, and distribution traceability close the loop from production records to market surveillance.

08Post‑market surveillance, vigilance, and trend reporting

Under IVDR, post‑market surveillance (PMS) is proactive and evidence‑driven. Manufacturers must operate a PMS plan that defines data sources, statistical methods, thresholds for action, and linkages to CAPA and design changes. Real‑world performance feeds into the Post‑Market Performance Follow‑Up (PMPF) program, which refines claims and risk controls over time.

Serious incidents, field safety corrective actions (FSCAs), and field safety notices (FSNs) must be managed within strict reporting timelines and documented communications. Trend reports are required where a statistically significant increase in non‑serious incidents or expected adverse effects could affect the benefit‑risk profile. Class C and D devices require a Periodic Safety Update Report (PSUR) with defined cadence and submission obligations.

Effective PMS integrates complaint handling, stability studies, usability feedback, quality control data, and literature surveillance. For self‑tests and near‑patient devices, user comprehension and false‑result consequences should be continually assessed. For software, new operating systems, cybersecurity threats, and algorithm drift become post‑market risk factors that may trigger updates and re‑verification.

Competent Authorities will expect clear rationales for signal detection thresholds, transparent decision logs, and documented benefit‑risk reassessments when performance shifts. Suppliers and distributors have roles in feedback loops and must be included in recall simulations and communication templates.

  • PMS Plan and PMS Report or PSUR, linked to CAPA and change control.
  • PMPF Plan and PMPF Evaluation Report reflecting real‑world evidence.
  • Signal detection and trend analysis methods with documented thresholds.
  • FSCA procedures, decision trees, and communication packages.
  • Post‑market labeling and IFU update controls with translation governance.

Discipline in deviations and containment accelerates recovery from market events. Configure Structured Deviations with tight owner and due‑date controls, and ensure that traceability from batches to customers enables rapid, targeted actions when a safety signal emerges.

09Transition timelines, legacy devices, and common pitfalls

Article 110 of IVDR sets transitional provisions for legacy IVDD devices, and the EU has further extended these via Regulation (EU) 2024/1860. The intent is to mitigate Notified Body capacity constraints while preserving safety. Legacy devices may remain on the market under staggered, class‑dependent timelines that now run through 2029, provided strict conditions are met.

Conditions typically include maintaining a compliant quality management system, having no significant design or intended‑purpose changes, operating a PMS system under IVDR expectations, meeting vigilance obligations, and actively pursuing IVDR certification. Economic operators must retain documentation demonstrating eligibility and be prepared to show contract status and planning with a Notified Body.

Manufacturers should treat transitional breathing room as a structured program, not a deferment. Establish a portfolio‑wide classification map, a gap assessment to Annex I–III, and a critical‑path plan for performance studies. Freeze marketing claims where evidence is marginal, and ensure that labeling does not drift beyond validated limits during transition.

Special attention is warranted for software and algorithms that may receive updates during the transition. Even minor feature changes can be interpreted as intended‑purpose shifts or significant design changes. Closely manage change control and document justifications for any updates to avoid losing transitional status unexpectedly.

Plan supplier readiness as well. Contracts for critical reagents and materials should include change‑notification clauses and second‑source strategies, because upstream changes can force re‑verification or precipitate shortages that jeopardize performance claims and certification milestones.

10How IVDR relates to neighboring frameworks

IVDR is part of a broader regulatory ecosystem. Its sibling, the EU MDR, governs non‑IVD medical devices and shares concepts like the General Safety and Performance Requirements, UDI, EUDAMED, and lifecycle post‑market controls. Borderline determinations often hinge on intended purpose, algorithm function, and whether a device acts on the human body or analyzes specimens.

For companion diagnostics, IVDR requirements must align with medicinal product labeling. Coordination with medicines regulators and, downstream, health technology assessment processes in Member States is essential for synchronized availability. Clinical evidence packages should anticipate payer and HTA expectations for analytical and clinical validity beyond the minimum regulatory bar.

Internationally, the IVDR approach to performance evaluation resonates with global norms. ISO 14971‑based risk management, ISO 13485‑based QMS, and statistical principles for analytical validation are recognized worldwide. While terminology and timelines vary, manufacturers benefit from a single, harmonized evidence backbone that maps to different jurisdictions’ submission formats.

In the United Kingdom, national rules and the MHRA’s evolving roadmap shape IVD requirements post‑Brexit, with transitional recognition periods for CE‑marked devices in certain categories. In the United States, FDA’s policy direction on laboratory‑developed tests and software provides a parallel view of risk and evidence expectations. Convergence trends continue, but procedural details and data formats remain jurisdiction‑specific.

11How V5 supports IVDR implementation and sustained compliance

IVDR execution is a document‑ and data‑intensive team sport. You must maintain a clean GSPR trace, performance evidence with raw‑data provenance, auditable manufacturing and lot‑release records, and continuously refreshed PMS and PMPF outputs. V5 Ultimate provides a unified operational backbone that binds these obligations into repeatable, inspection‑ready workflows without fragmenting source‑of‑truth.

Our platform structures technical documentation to Annex II, maintains live risk and verification traceability, and enforces role‑based controls for evidence updates. It links device master data to labeling and shop‑floor execution, ensuring that what you build, label, and ship lines up with certified claims. At the same time, deviations, complaints, and stability trends flow straight into CAPA, PSUR, and PMPF pipelines.

For conformity assessment, V5 helps teams stage clean submissions, run mock audits, and keep surveillance‑ready files. On the shop floor and in the lab, electronic records capture operator actions, measurements, and batch context to create durable traceability from raw materials to market actions. Master data stay aligned across SKUs, packaging hierarchies, and distribution events to support UDI and recall scenarios.

Organizations standardize on V5 to reduce review cycles, prevent evidence drift, and shorten the path from prototype to certification and scale. The result is resilient compliance and faster, safer market access as IVDR continues its staged, capacity‑aware rollout.

Frequently asked questions

Q.What did IVDR change compared to IVDD?+

IVDR expanded Notified Body involvement via Annex VIII classification, formalized performance evaluation across scientific validity, analytical, and clinical performance, mandated UDI and EUDAMED transparency, and strengthened PMS, PMPF, and vigilance obligations.

Q.Which devices need a Notified Body under IVDR?+

All Classes B, C, and D require Notified Body assessment, as do sterile Class A devices. Only non‑sterile Class A devices can self‑declare conformity without Notified Body involvement.

Q.How are companion diagnostics treated under IVDR?+

They are Class C IVDs linked to specific medicines and require alignment with the medicinal product’s labeling. Evidence and timelines must be coordinated with medicines regulators and clinical practice.

Q.What are EU Reference Laboratories and when are they involved?+

EU Reference Laboratories support verification of performance for certain Class D devices and may conduct confirmatory tests or batch verification. They add independent technical assurance for the highest‑risk assays.

Q.What are the key components of performance evaluation?+

A plan and report covering scientific validity, analytical performance, and clinical performance, plus a PMPF plan and evaluation report. Evidence must support each claimed indication and user population.

Q.How do IVDR transition extensions work?+

Regulation (EU) 2024/1860 extends class‑dependent deadlines through 2029 for eligible legacy IVDD devices. Eligibility is conditional on QMS, PMS, and vigilance under IVDR, no significant changes, and active pursuit of IVDR certification.

Q.What UDI elements are required for IVDs?+

A Basic UDI‑DI for device family, a UDI‑DI for the marketed unit, and a UDI‑PI with production information. Data must be accurate, synchronized with labeling, and submitted to EUDAMED as modules mandate.

Primary sources

Further reading

Explore this topic

IVDR sits inside this topic cluster in our glossary. Every neighbour is one click away.

See IVDR working on a real shop floor

V5 Ultimate ships with the IVDR controls already wired in — audit trail, e-signatures, validation evidence. Free trial, no credit card, onboard in days, not months.