ISO 14155:2026 What’s Changed and What It Means for Your Clinical Investigation

The fourth edition of the international GCP standard for medical device clinical investigations is now in effect, with no transition period. Here is what sponsors, investigators, and CROs need to know.

A Standard That Has Been a Long Time Coming

ISO 14155 has been the GCP reference for medical device clinical investigations since its first edition in 2003. The third edition, published in July 2020, made significant strides in aligning the standard with the EU Medical Devices Regulation (MDR 2017/745) and the ICH E6(R2) framework. But five years of practical implementation exposed gaps, particularly around risk management, study oversight structures, and statistical planning.

The fourth edition directly addresses those gaps. It introduces more prescriptive requirements, clearer distinctions between types of risk, new formal oversight structures, and a statistical annex that brings medical device investigations much closer to the rigour expected in pharmaceutical trials.

⚠ No transition period, requirements apply immediately

One timing point worth noting: ISO 14155:2020 had only just achieved formal harmonisation with the EU MDR when the fourth edition arrived, an unusual situation that has created legitimate questions for sponsors about the harmonisation status of the new standard. As of publication, EN ISO 14155:2020 remains the harmonised standard for MDR conformity purposes. The harmonisation process for ISO 14155:2026 is ongoing. Sponsors should monitor the EU Official Journal for updates.

The Key Changes: What’s New in ISO 14155:2026

1. Risk Management: A Clearer, More Structured Framework

If applying ISO 14971 risk management principles to clinical investigations has been a grey area in your organisation, the fourth edition addresses this directly.

The key distinction introduced is the separation of two categories of risk:

Device-related risks: including residual risks relevant to the specific study population, sample size, and indication, must be evaluated using full ISO 14971 methodology. The standard recognises that adverse device effect rates during an investigation can differ from post-market use. A small trial population amplifies ethical impact; risks must be contextualised accordingly.

Procedure-related risks: arising from non-routine clinical procedures required by the Clinical Investigation Plan (CIP) but outside standard clinical practice, require a descriptive risk assessment.

A risk based monitoring approach should be defined to manage the oversight of risks associated with the clinical investigation.

The standard clarifies how general device risk management principles translate into study-specific considerations, with focus on investigational device risks, especially residual risks relevant to the study population, sample size, and indication. These updates will require greater rigour when conducting and documenting risk assessments, but the result will be sponsors having more robust, better-documented risk management files tailored to each investigation.

Kirsty Macleod, Head of Clinical Research, MDx CRO

2. Data Monitoring Committees and Clinical Events Committees: Formal Requirements for Both

Study oversight structures receive significant attention in the fourth edition.

For DMCs, ISO 14155:2026 provides further clarification on this requirement. Where a DMC is determined to be in place, sponsors must now pre-define, and document in the CIP, the specific conditions under which a study would be suspended or stopped.

CECs are introduced for the first time in ISO 14155:2026. A Clinical Events Committee is an independent group of clinical experts established by the sponsor to ensure consistent classification and assessment of clinical events across sites. In multi-centre studies, different investigators may characterise the same event type differently, a CEC reduces that variability and strengthens data reliability. Where a CEC is used, its independence, role, and conflict-of-interest management must be formally defined at the outset of the study.

3.Informed Consent: Strengthened Expectations and Ethics Committee Implications

The fourth edition introduces more operational requirements around ethics, subject rights, and consent.

Specific updates include a prohibition on deviations from eligibility criteria without a formal CIP amendment; clearer requirements for explaining future use of health data to subjects; and expanded protection requirements for vulnerable populations and cross-border studies.

Ethics committees will scrutinise these more closely. Sponsors referencing ISO 14155:2026 compliance in submissions should expect greater attention to consent documentation, the consent process itself, and how protocol deviations are governed.

Ethics committees will have altered expectations when sponsors state compliance with the revised standard. Any mismatches between the risk management file and the informed consent form, downplaying known residual risks, using generic language, are routinely flagged during ethics review. The risk file and the consent must tell the same story, in plain language.

Kirsty Macleod, Head of Clinical Research, MDx CRO

4. Design Considerations: The Estimand Framework Arrives

The introduction of Annex K, a new informative annex on clinical investigation design considerations, brings the device world significantly closer to the statistical expectations long standard in pharmaceutical development.

In practice, this means study protocols are expected to more precisely define the clinical question being answered, including how intercurrent events (patient dropouts, treatment switches, protocol deviations) are handled in the primary analysis. Missing data strategies must be planned prospectively, not fixed post-hoc.

For organisations working across both medical devices and pharmaceuticals, this alignment reduces friction. For teams accustomed to simpler device trial designs, it will require additional investment in biostatistics at the planning stage.

5. Clinical Performance: A Sharper Definition With Real Consequences

The definition of “clinical performance” has been updated to more explicitly link device performance to measurable clinical benefit resulting from technical or functional characteristics. This is not a minor editorial change. It has direct implications for how endpoints are selected and justified in the CIP, and how clinical evidence is structured in Clinical Evaluation Reports (CERs).

Sponsors designing new studies need to ensure their primary endpoints map directly to the updated definition. For CER authors, it adds another layer of alignment to consider when assessing clinical data generated under different versions of the standard.

The Most Common Mistakes Sponsors Make regarding ISO 14155, and How to Avoid Them

When running and overseeing clinical investigations, the same errors appear repeatedly when sponsors try to apply risk management requirements to active studies. The fourth edition makes some of these errors significantly harder to ignore during regulatory or ethics review.

The mistakeWhat is expected instead
Reusing the post-market risk file unchanged

Clinical investigations have different risk profiles, smaller populations, learning-curve users, investigational configurations. The ISO 14971 product risk file created for design verification does not translate directly.
A study-specific risk assessment clearly linked to the CIP, subject population, site capabilities, and operator experience. Justified differences between clinical investigation risk and intended-use risk.
Applying full ISO 14971 to procedure risks

Sponsors apply the full methodology to blood draws, biopsies, imaging, and extra clinic visits, logging these as device risks. Regulators increasingly challenge over-engineered risk files because they obscure actual device risk.
Clear separation in documentation: device-related risks, ISO 14971 process; procedure-related risks, descriptive assessment. Explicit statement in the CIP explaining this distinction.
Freezing the risk file once the study starts

Risk management is treated as a design artefact with no named responsibility during execution. Adverse events, near-misses, and protocol deviations that reveal new hazards are not fed back into risk assessment.
Defined triggers for risk review (SADEs, DMC recommendations, deviation trends). Documented updates showing how clinical findings feed back into hazard identification, risk estimation, and benefit-risk evaluation.
Weak linkage between risk file and consent form

The informed consent form downplays known residual risks, uses generic language, or is inconsistent with what appears in the risk management file. Ethics committees view this as a red flag.
Clear mapping between residual risks and subject-facing explanations. Justification where technical risks are simplified or grouped. Immediate consent updates if risk understanding changes.
Risk controls that exist on paper but not in the study

Controls are listed in the risk file but not implemented, training listed but not documented, IFU warnings not reflected in consent, monitoring controls not built into the protocol.
Traceability from risk, control, CIP section, training, monitoring. Cross-checks during monitoring that controls are actively applied. This is one of the most common audit findings.

What Happens to Studies Already Underway?

This is a frequently asked question by sponsors where the answer requires some nuance.

Studies initiated and approved under ISO 14155:2020 remain valid. The publication of the fourth edition does not retroactively invalidate work done in compliance with the previous version. A study designed, approved, and conducted in line with ISO 14155:2020 remains compliant with that version, and that data remains usable to support CE marking, clinical evaluation updates, and post-market evidence, provided it was compliant at the time of initiation.

Where things become more complex is with substantial amendments. If an ongoing study undergoes a significant change after March 2026, a protocol amendment, addition of new sites, introduction of a DMC or CEC, changes to the subject population, regulators and notified bodies may expect the affected areas to be brought into alignment with ISO 14155:2026. This is not a hard rule, but it is a risk-based expectation that should be assessed and documented.

In practice, authorities accept a clear, documented rationale: the clinical investigation was designed and initiated in compliance with ISO 14155:2020, which represented the state of the art at the time of study initiation. The publication of ISO 14155:2026 has been reviewed, and no changes were required that would materially impact subject safety, data integrity, or scientific validity. This approach is widely accepted, provided it is documented, risk-based, and justified.

Kirsty Macleod, Head of Clinical Research, MDx CRO

What Sponsors and Investigators Must Do Now

Given that there is no transition period, the question is not whether to act but how to prioritise. Here is a practical framework:

1. Run a formal gap analysis

Assess your current SOPs, CIP templates, risk management processes, and oversight structures against ISO 14155:2026. Focus first on risk management (device vs. procedure risk distinction), DMC/CEC governance, and statistical planning documentation.

2. Update your QMS and SOPs

Procedures, templates, and SOPs that reference ISO 14155:2020 need revision, particularly around CEC governance (new), DMC governance (strengthened), risk management integration, and informed consent processes.

3. Assess ongoing studies

Review active protocols or protocols in development. For studies with upcoming substantial amendments, prepare a documented assessment of whether and how ISO 14155:2026 requirements apply. Always document the rationale for decisions made, or not made.

4. Deliver structured training

Sharing the updated standard document is not sufficient. The risk management changes in particular require dedicated training for clinical affairs, regulatory affairs, and quality teams, not just a circulated PDF.

5. Monitor the harmonisation process

Keep an eye on the EU Official Journal for updates on the formal harmonisation of ISO 14155:2026 under the MDR. Until harmonised, EN ISO 14155:2020 remains the reference for MDR conformity presumption.

Frequently Asked Questions about ISO 14155:2026

When did ISO 14155:2026 come into effect?

ISO 14155:2026 (Edition 4) was published in March 2026 and replaced ISO 14155:2020 immediately, with no defined transition period. Any new clinical investigation initiated after publication is expected to reference ISO 14155:2026 or provide a clear justification for non-alignment.

Do studies already underway under ISO 14155:2020 need to be updated?

Studies initiated and approved under ISO 14155:2020 remain valid. However, any substantial amendment to an ongoing study after March 2026 may trigger an expectation to align affected parts with ISO 14155:2026, or provide a documented justification explaining why partial or full transition is not appropriate. Always document the rationale.

Is ISO 14155:2026 harmonised with the EU MDR?

Not yet. As of April 2026, EN ISO 14155:2020 remains the harmonised standard providing presumption of conformity with the EU MDR. The formal harmonisation process for ISO 14155:2026 is underway. Sponsors should monitor the EU Official Journal regularly for updates.

What is the difference between a DMC and a CEC under ISO 14155:2026?

A Data Monitoring Committee (DMC) oversees overall trial safety and has the authority to recommend stopping or modifying a study. ISO 14155:2026 requires sponsors to pre-define stopping conditions and justify the absence of a DMC. A Clinical Events Committee (CEC) newly introduced in the 2026 edition, is an independent panel of clinical experts that ensures consistent classification of events across sites in multi-centre studies, improving data reliability.

Does ISO 14155:2026 apply to PMCF studies?

Yes. ISO 14155 applies to post-market clinical investigations, including PMCF studies. Annex I of the standard defines the applicability of requirements to different types of post-market investigations. Some requirements may be modified or exempt for observational studies, but the core GCP principles, including risk management, monitoring, and data governance, apply.

What is the estimand framework introduced in Annex K?

The estimand framework (from ICH E9(R1)) provides a structured approach to defining exactly what clinical question the investigation is designed to answer, and how events that disrupt the intended treatment (dropouts, protocol deviations, treatment switches) should be handled in the primary analysis. It requires these decisions to be made and documented at the design stage, not resolved post hoc in statistical analysis.

Does ISO 14155:2026 apply to IVD clinical performance studies?

ISO 14155 applies to medical devices, not in vitro diagnostics (IVDs). IVD clinical performance studies are governed by ISO 20916:2019. However, where a medical device and an IVD are used in an integrated system, elements of both standards may apply. Sponsors of combination investigations should assess both standards.

    

Related Articles

ISO 14971 Applied to Clinical Investigations: A Practical Guide

PMCF Under MDR: What ISO 14155 Requires

Clinical Investigation Plan: What You Must Include (2026 Update)

EN ISO 14155:2020/A11:2024 and MDR Harmonisation

Written by:
Kirsty Macleod

Kirsty Macleod

Head of Clinical Research

Clinical Operations leader with IVD and CDx device expertise, delivering global clinical studies while establishing best practices and high performing teams.
Industry Insights & Regulatory Updates

EU AI Act and Medical Devices: What SaMD Developers Need to Know (2026)

The EU AI Act (Regulation (EU) 2024/1689) entered into force on 1 August 2024 and is being phased in progressively through 2026 and beyond. For companies developing AI-powered Software as a Medical Device (SaMD), it introduces a second, overlapping regulatory obligation that runs alongside, and interacts with, the existing requirements of EU MDR and IVDR.

This is not a distant compliance horizon. The provisions most relevant to medical device AI became applicable from August 2026. Companies that have not yet assessed their AI systems against the AI Act risk gaps in their technical documentation and conformity processes at exactly the moment Notified Bodies are beginning to incorporate AI Act considerations into their assessments.

This guide explains what the AI Act requires from SaMD developers, how it interacts with MDR and IVDR, and what practical steps manufacturers should be taking now.

For general SaMD MDR compliance, see our SaMD EU MDR Compliance Guide

1. Does the AI Act Apply to Your Software?

The AI Act applies to AI systems placed on the market or put into service in the EU. An AI system is defined as a machine-based system that, given explicit or implicit objectives, infers from inputs how to generate outputs such as predictions, content, recommendations, or decisions that can influence real or virtual environments.

This definition is intentionally broad. It covers:

  • Machine learning models (supervised, unsupervised, reinforcement learning)
  • Deep learning systems including convolutional neural networks used in medical imaging
  • Natural language processing tools used in clinical documentation or decision support
  • Bayesian classifiers and other probabilistic inference systems

It does not cover:

  • Traditional rule-based software with no learning or inference component
  • Software that executes fixed logic without adaptive behaviour

If your SaMD uses any form of machine learning or statistical inference to generate clinical outputs, the AI Act almost certainly applies.

2. High-Risk AI Classification for Medical Devices

The AI Act categorises AI systems by risk level. For medical device manufacturers, the critical category is high-risk AI.

Under Annex III of the AI Act, AI systems intended to be used as safety components of medical devices, or which are themselves medical devices regulated under MDR or IVDR, are automatically classified as high-risk AI.

This means: if your SaMD is a CE-marked medical device or IVD, or is a software component that performs a safety function within one, it is high-risk AI under the AI Act. There is no further classification analysis required, the medical device status determines it.

High-risk AI systems are subject to the full obligations of the AI Act, including:

  • Risk management system: an AI-specific risk management process, documented and integrated with the ISO 14971 risk management already required under MDR
  • Data and data governance: training, validation, and testing datasets must be relevant, representative, free of errors, and sufficiently complete; demographic and geographic representativeness must be documented
  • Technical documentation: a detailed record of the AI system’s design, development process, training methodology, validation approach, and performance characteristics
  • Transparency and instructions for use: users must be provided with clear information about the AI system’s capabilities, limitations, accuracy metrics, and circumstances under which human oversight is required
  • Human oversight: the system must be designed to allow human oversight and intervention; it must not undermine the ability of the operator or user to override, disregard, or reverse outputs
  • Accuracy, robustness, and cybersecurity: performance must be declared and validated; the system must be resilient to errors, faults, and adversarial manipulation
  • Conformity assessment: high-risk AI systems must undergo a conformity assessment before being placed on the market

3. How the AI Act Interacts with MDR and IVDR

This is where the compliance picture becomes complex, and where early planning pays off.

The AI Act does not replace MDR or IVDR. Both regulatory frameworks apply simultaneously to AI-powered SaMD. However, the EU has designed a streamlined pathway for medical devices that are already subject to Notified Body review under MDR or IVDR.

Under Article 11 and Annex II of the AI Act, AI systems that are regulated as medical devices benefit from a single technical documentation approach meaning the AI Act technical documentation requirements can be integrated into the existing MDR/IVDR technical file rather than creating a separate document set.

Similarly, for Class IIb and III medical devices (MDR) and Class C and D IVDs (IVDR) which are the most likely to contain high-risk AI the Notified Body involvement already required under MDR/IVDR can cover the AI Act conformity assessment. The Notified Body acts as the relevant conformity assessment body for both frameworks.

In practice this means:

What changes for AI-powered SaMD under the AI Act:

  • Technical documentation must now explicitly address AI-specific elements: training data governance, model validation across subgroups, bias assessment, explainability approach, and human oversight mechanisms
  • Post-market monitoring must include AI performance monitoring tracking model drift, accuracy degradation over time, and distribution shift in real-world data
  • Transparency obligations require new IFU content describing AI limitations and human oversight requirements
  • A fundamental rights impact assessment may be required for certain high-risk AI applications in healthcare

What does not change:

  • The MDR/IVDR conformity assessment route remains the primary pathway
  • The Notified Body relationship established for MDR/IVDR CE marking remains the relevant body
  • ISO 14971 risk management, IEC 62304 lifecycle management, and clinical evaluation requirements are unchanged AI Act risk management is additive, not a replacement

4. General Purpose AI (GPAI) Models in Medical Devices

A separate and increasingly relevant category is General Purpose AI (GPAI) large foundation models or multimodal AI systems that can be adapted or fine-tuned for specific applications.

If a SaMD developer is building on top of a GPAI model: for example, fine-tuning a large language model for clinical documentation, or adapting a vision foundation model for medical image analysis both the GPAI model provider and the SaMD developer have obligations under the AI Act.

GPAI model providers must publish technical documentation and comply with copyright and transparency requirements. SaMD developers who deploy or fine-tune GPAI models are responsible for ensuring the resulting system meets all high-risk AI obligations, including data governance, validation, and clinical performance claims. The validation methodology for fine-tuned GPAI models in medical contexts is an area where regulatory guidance is still developing, early engagement with your Notified Body is strongly recommended.

5. Key Timelines

August 2024: AI Act enters into force.

February 2025: Prohibitions on unacceptable-risk AI systems apply. Not directly relevant for medical SaMD, but important for any AI used in patient-facing administrative processes.

August 2025: GPAI model obligations apply. SaMD developers building on foundation models must assess their exposure now.

August 2026: High-risk AI obligations fully apply. This is the key deadline for medical device AI. From this date, new AI-powered SaMD placed on the EU market must comply with all high-risk AI requirements.

Post-2026: Notified Bodies designated under the AI Act will begin conducting AI Act-specific conformity assessments. The intersection with MDR/IVDR NB assessments will become a standard part of the conformity process.

6. What to Do Now: A Practical Checklist

Classify your AI systems. Identify every AI component in your SaMD portfolio and confirm whether it meets the EU’s definition of an AI system. For each, document the risk classification and the rationale.

Assess your technical documentation gaps. Review your existing MDR/IVDR technical files against the AI Act Annex IV requirements. Identify where AI-specific content, training data documentation, bias assessment, explainability approach, is missing or insufficient.

Review your data governance. The AI Act’s requirements for training data representativeness and bias documentation are more explicit than anything in MDR. If your training data governance is not documented at the level the AI Act requires, this is a gap that needs addressing before your next Notified Body audit.

Update your IFU and labelling. Transparency obligations mean users must be explicitly informed about AI limitations, performance metrics across relevant subgroups, and circumstances requiring human override. Most current SaMD IFUs are not written to this standard.

Engage your Notified Body. Ask your NB directly how they are approaching AI Act integration into MDR/IVDR assessments. Different NBs are at different stages of readiness, and early clarity on what they will expect prevents last-minute documentation gaps.

Build AI performance monitoring into your PMS. Post-market surveillance for AI-powered SaMD must now track model performance over time. If your PMS plan does not include AI-specific monitoring metrics, update it before August 2026.

Read more about Software, Digital Health and AI services.

Frequently Asked Questions: EU AI Act and Medical Devices

What is the difference between the EU AI Act and the MDR for medical device AI?

The MDR (Medical Device Regulation) governs the safety, efficacy, and quality of medical devices, including those powered by AI. The EU AI Act is a separate regulatory framework that addresses the risks and accountability of AI systems themselves. The AI Act focuses on how the AI system was built, trained, validated, and deployed, while MDR focuses on the clinical performance of the device. Both apply simultaneously to AI-powered SaMD from August 2026 onwards.

Does the AI Act apply to all machine learning models in medical devices?

Yes, if you use any form of machine learning, deep learning, or statistical inference to generate clinical outputs, the AI Act applies. This includes supervised learning, convolutional neural networks for medical imaging, natural language processing for clinical documentation, and Bayesian classifiers. It does NOT apply to traditional rule-based software with fixed logic and no learning or inference capability

What does ‘high-risk AI’ mean under the EU AI Act?

High-risk AI includes AI systems that are themselves medical devices or safety components of medical devices regulated under MDR, or AI systems regulated under IVDR. If your SaMD is CE-marked or classified as a medical device, it is automatically classified as high-risk AI. High-risk AI must comply with all AI Act obligations: risk management, data governance, technical documentation, transparency, human oversight, and conformity assessment.

What are the data governance requirements under the AI Act?

The AI Act requires explicit documentation that training, validation, and testing datasets are relevant, representative, free of errors and bias, and sufficiently complete. Demographic and geographic representativeness must be documented, particularly important for medical AI to ensure performance across age, sex, ethnicity, and geography. This is more explicit than MDR alone.

What are the human oversight requirements under the AI Act?

High-risk AI systems must be designed to enable human oversight and intervention. Users must be able to override, disregard, or reverse the AI’s decision, and the system must not undermine this ability. For clinical SaMD, this typically means the AI operates in decision-support mode and clinicians retain authority to override recommendations.

When do I need to comply with the AI Act?

August 2026 is the key deadline for medical device AI. From this date, all new AI-powered SaMD placed on the EU market must comply with high-risk AI requirements, Notified Bodies will incorporate AI Act assessments into MDR/IVDR reviews, and technical documentation must include AI-specific content.

Medical professionals at a webinar discussing AI in medical devices, focusing on clinical evaluation, evidence, and regulatory compliance for SaMD development.
Written by:
Diego Rodríguez Muñoz, PhD

Diego Rodríguez Muñoz, PhD

RA Specialist

Regulatory affairs specialist & CRA with expertise in EU MDR/IVDR, CE marking, Biological Evaluations (dental), and clinical investigations & technical documentation for MDs & IVDs.
Industry Insights & Regulatory Updates

FDA Laboratory Developed Tests (LDTs) Regulation

The FDA Laboratory Developed Tests regulation marks one of the most significant shifts in U.S. diagnostic oversight in decades. The FDA’s new rule phases in full regulation of LDTs over four years, with no grandfathering. This change elevates the importance of IVD CROs, whose regulatory and clinical expertise will be critical as laboratories adapt to stringent new requirements. The rule represents a major transformation in the U.S. IVD landscape and will reshape how laboratories develop, validate, and maintain LDTs.

Introduction

On September 29, 2023, the FDA released a groundbreaking proposed rule that fundamentally redefines how the agency regulates Laboratory‑Developed Tests (LDTs). This proposal shifts LDTs out of decades of enforcement discretion and brings them fully under the FDA’s medical device framework.

Because LDTs are a subset of in vitro diagnostic products (IVDs), the new rule has sweeping implications for clinical laboratories, manufacturers, and the broader diagnostics industry. Under the FDA Laboratory Developed Tests regulation, LDTs will now be treated like other medical devices—requiring quality systems, medical device reporting, registration, listing, and in many cases, premarket review.

For stakeholders across the IVD sector, this change is significant.

Key Points to Consider as the FDA regulates LDTs

  1. Expanded Definition of IVDs
    The FDA proposes to explicitly classify LDTs as IVDs under 21 CFR 809.3.
    This means LDTs will now fall under the same requirements as traditional IVD medical devices.
  2. Phased, Four‑Year Implementation
    The FDA will remove enforcement discretion in five stages over a four‑year timeline.
    Each stage introduces new regulatory obligations for laboratories.
  3. No Grandfather Clause
    The proposal does not exempt existing LDTs. All LDTs (old and new) must eventually comply.
  4. Test Categories Exempt from Enhanced Oversight
    Certain test types, including forensic tests and HLA assays, are proposed for exemption.
  5. Public Comment Period
    Stakeholders were invited to submit comments through December 4, 2023.

Background on FDA Regulation for LDTs and IVDs

IVDs have traditionally been subject to rigorous regulatory scrutiny under various heads:

  • 510(k) premarket notification or premarket approval (PMA)
  • Quality system regulation
  • Medical device reporting
  • Registration and listing
  • Labeling

LDTs, however, historically operated under enforcement discretion, receiving minimal oversight. This approach was based on the assumption that LDTs were low risk and used primarily within single laboratories.

That landscape has changed.

The Evolving Landscape of LDTs

Over the last 50 years, LDTs have become increasingly complex, widely used, and technically sophisticated. This evolution has driven demand for stronger oversight in areas such as:

  • Clinical validity
  • Analytical performance
  • Manufacturing consistency
  • Patient safety

The new FDA Laboratory Developed Tests regulation directly responds to these gaps. By redefining LDTs and removing enforcement discretion, the FDA aims to strengthen public health protections.

The Road Ahead: Key Regulatory Impacts

The phased implementation timeline will introduce major compliance requirements:

Medical Device Reporting

The first enforcement area to take effect.

Quality Systems Regulation

Expected three years after publication of the final rule.

Premarket Review

Introduced 3.5 to four years after the final rule, starting with high‑risk LDTs and expanding to moderate-and-low risk tests.

Labs performing LDTs must begin planning now. Clinical and analytical validation, documentation systems, and regulatory processes will all require upgrades.

Alignment With Europe’s IVDR Rollout

The FDA’s new approach mirrors developments in Europe under the In Vitro Diagnostic Regulation (IVDR). The IVDR already applies strict rules to in‑house tests and LDTs, requiring:

  • Complete Technical Documentation
  • A compliant Quality Management System
  • Performance evaluation and validation
  • Adherence to Article 5.5 requirements for in‑house devices

çUnder IVDR, an LDT cannot be used if an equivalent CE‑marked test exists. This forces laboratories to justify in‑house development and meet near‑manufacturer‑level standards.

Conclusion: An Industry in Transition

As experts in IVD quality, regulatory, and clinical operations, MDx CRO encourages laboratories and manufacturers to prepare now for the FDA Laboratory Developed Tests regulation. Although legal challenges may influence the timeline, increased oversight is inevitable, and already fully established within Europe under the IVDR.

Stakeholders should submit comments to the FDA by December 4, 2023, and begin strengthening their regulatory systems immediately.

Written by:
Carlos Galamba

Carlos Galamba

CEO

Senior regulatory leader and former BSI IVDR reviewer with deep experience in CE marking high-risk IVDs, companion diagnostics, and IVDR implementation.
Industry Insights & Regulatory Updates

IVDR Transition: Insights from the Dutch Authority

State of play of IVDR Transition:

In the realm of in vitro diagnostics (IVD), a seismic shift is underway as manufacturers grapple with the complexities of transitioning to the new European In Vitro Diagnostic Regulation (IVDR). This transition, necessitated by advancements in technology and evolving patient safety concerns, brings both challenges and opportunities for IVD manufacturers. A recent report by the Dutch Competent Authority (IGJ) delves into the progress, setbacks, and strategies of IVD manufacturers in their journey toward IVDR compliance. Over 40% of respondents raised doubts about whether they will be able to obtain the CE marking for their IVDs before the transition periods expire.

The IGJ Report Findings:

The IGJ report sheds light on the multifaceted landscape of the IVDR transition. Manufacturers are confronted with stringent requirements that demand a paradigm shift in their approach to product development, documentation, quality assurance, and post-market surveillance. The report identifies several key challenges:

  1. Technical Documentation Overhaul: The IVDR mandates comprehensive and meticulously documented technical files and dossiers. This demand presents a considerable challenge as manufacturers strive to align existing documentation with the new regulations. Additionally, the dynamic nature of diagnostic technologies requires continuous updates, further complicating the documentation process. Gathering of IVDR Clinical Evidence is particularly challenging for manufacturers due to lack of guidelines and international coordination. For example, application for clinical performance studies across Member States is not fully harmonised.
  2. Certification Complexities: Acquiring the necessary certification from Notified Bodies is a crucial step in the IVDR transition. However, the IGJ report underscores the intricate nature of the certification process, involving rigorous assessments and evaluations. This complexity can lead to delays in bringing products to market. Notified Bodies have reported delays in the certification process due to lack of information in the IVDR technical documentation and also lack of structure and clarity in the file.
  3. Post-Market Surveillance Emphasis: The IVDR places increased importance on post-market surveillance (PMS) and vigilance. Manufacturers are expected to establish robust systems for monitoring the performance and safety of their products throughout their lifecycle. This shift necessitates a proactive approach to identifying and addressing potential issues. 80% of respondents have adapted their vigilance procedures to IVDR requirements, however compliance to PMS System, PMS plan and PMPF requirements is lower, at 70% of respondents. The IGJ has declared they will promote or enforce compliance through random inspection visits.
  4. Educational Imperative: The IGJ report emphasizes the significance of educating all stakeholders, from manufacturers to regulatory bodies, about the intricacies of IVDR compliance. Adequate training is crucial to ensure that everyone understands their roles, responsibilities, and the broader implications of the new regulation.

The Role of MDx CRO in your IVDR Transition:

Amid these challenges, MDx CRO emerges as a guiding light for IVD manufacturers. As the industry grapples with the transformative implications of the IVDR, MDx CRO stands as a stalwart partner, offering expert guidance and tailored solutions to navigate the evolving regulatory landscape.

Strategic Guidance: MDx CRO’s team of seasoned experts provides strategic advice that empowers manufacturers to make informed decisions. Transitioning to the IVDR isn’t just about compliance; it requires a forward-looking approach that considers the long-term impact on products and business strategies.

Technical Documentation Excellence: The IGJ report highlights the criticality of accurate and comprehensive technical documentation. MDx CRO’s expertise shines in this arena, aiding manufacturers in compiling technical files and dossiers that meet IVDR standards while showcasing the safety and innovation of their products.

Certification Support: With the certification process’s complexities highlighted in the report, MDx CRO’s collaborative approach becomes invaluable. By assisting manufacturers in preparing for interactions with Notified Bodies, MDx CRO streamlines the certification journey, ensuring quicker time-to-market for products. Read about our pre-submission service.

Continuous Partnership: The IGJ report’s emphasis on post-market surveillance aligns with MDx CRO’s commitment to the entire product lifecycle. Beyond the transition, MDx CRO supports manufacturers in establishing robust PMS systems, enabling them to meet ongoing compliance and safety monitoring requirements.

Knowledge Dissemination: As underscored by the report, education is pivotal in a successful IVDR transition. MDx CRO’s training and workshops empower manufacturers with the insights and understanding needed to navigate the new landscape with confidence.

Conclusions:

The IGJ report provides a comprehensive view of the challenges and advancements in the IVD sector’s transition to IVDR compliance. One message is clear, the IGJ unequivocally mandates manufacturers to expedite IVDR certification without delay. This is key to prevent peak in applications when the transition period come to an end. Within this landscape, MDx CRO emerges as a crucial enabler, equipping manufacturers with the tools, expertise, and support needed to thrive in the new regulatory era. By offering strategic guidance, technical excellence, certification support, ongoing collaboration, and knowledge dissemination, MDx CRO paves the way for compliant, innovative, and patient-centered IVD products. As the industry continues to navigate the evolving regulatory seas, MDx CRO stands as a steadfast partner in this transformative journey.

Contact our team today to discuss your IVDR transition needs!

Written by:
Carlos Galamba

Carlos Galamba

CEO

Senior regulatory leader and former BSI IVDR reviewer with deep experience in CE marking high-risk IVDs, companion diagnostics, and IVDR implementation.
Industry Insights & Regulatory Updates