MDR reform proposals (Dec 2025) — what the breakthrough pathways actually mean for manufacturers

The December 2025 reform proposals feel like the EU finally admitting the MDR needed practical fixes. To be fair, the original intent — stronger clinical evidence, better post-market surveillance, and a harmonised single market — was correct. In practice the implementation created bottlenecks: notified-body capacity, inconsistent equivalence interpretations, and an avalanche of PMCF/PSUR demands that small teams cannot realistically resource.

I read the proposals as a set of pragmatic trade-offs: faster access for well‑characterised innovation, tighter post‑market requirements where risk is uncertain, and more centralised support for clinical data reuse. Below I translate the headline ideas into what they mean for a Regulatory Affairs team three quarters away from your next audit.

What the proposals aim to fix (practical view)

• Reduce time-to-market for high‑need or genuinely novel devices while keeping patient safety central.
• Clarify equivalence and clinical evidence expectations so notified bodies stop inventing different versions of the same test.
• Create defined "breakthrough" or "innovation" pathways with explicit post‑market obligations rather than indefinite, vague promises.
• Improve EUDAMED data usability and UDI enforcement so the signals from PMS actually help not hurt small manufacturers.

If those aims sound familiar, it’s because they’re the places MDR players have been stumbling on since 2021.

Breakthrough pathways — how they’ll work in practice

The proposals outline accelerated review tracks. In plain terms, expect something like:

• Eligibility criteria: clear definitions for "high unmet need" or "step‑change innovation" — not merely marginal upgrades.
• Rolling review with staged deliverables: initial technical/clinical package to get to market; committed PMCF, registry linkage, and adaptive CE updates submitted post‑market.
• Conditional CE certificates with explicit milestones and automatic re‑review triggers if milestones are missed.
• A central resource (or hub) for complex clinical evidence questions and for pooling registry data — intended to reduce repeated equivalence fights.

In practice this means: you may be able to get to market faster, but only if your PMCF and PSUR behaviour is impeccable and demonstrably resourced. Per Article 10 obligations, the manufacturer remains fully responsible for post‑market obligations; accelerated access does not reduce that burden, it time‑shifts and concentrates it.

What notified bodies will actually ask for

From multiple NB interactions over the last four years, a few predictable patterns will continue:

• Concrete, auditable PMCF plans with timelines and resourcing — vague "we will do post‑market studies" no longer passes.
• Clear risk management linking to real‑world performance data — Annex II/ISO 14971 traceability must be tight.
• Evidence of data flows: how EUDAMED/UDI feeds into your signal detection, who owns the data pipeline, and how CAPAs will be triggered.

So prepare for "conditional" reviews that read like a project‑plan audit: milestones, deliverables, owners, and escalation paths.

Practical actions for RA/QMS teams (what I’d do this quarter)

• Update your Technical File template to accommodate staged submissions: an "initial pack" and an "evolving pack" section.
• Run a change impact mapping exercise (use the Change Impact Mapping tab in your eQMS if you have one) to show how new PMCF/PSUR commitments affect suppliers, manufacturing, and clinical affairs.
• Add capacity to PMCF and vigilance ownership in your QMS: allocate named owners, timelines, and budget lines — auditors ask "who will do it" as much as "what will you do".
• Document your conditional‑access risk acceptances in CAPAs and link them to requirements in your QMS (automated CAPAs and traceability help here — they make the post‑market story reviewable).
• Rehearse data flows: how will UDI and EUDAMED entries update your complaint handling? Map that into your incident and signal detection workflows.

If your QMS doesn’t already produce an auditable "connected workflow" view of change → risk → CAPA → PMS data, now is the time to build it.

Clinical evidence and equivalence — progress, but not a magic bullet

The proposals try to make equivalence more usable by encouraging centralised reuse of registry/clinical data and by clarifying when literature is adequate. In reality:

• Notified bodies will still push for direct clinical data for medium‑to‑high risk devices.
• Expect inspectable justification for any reliance on equivalence — traceability from claim to dataset to statistical reasoning.
• PMCF will often be used to close "evidence gaps" left by accelerated access; make sure your post‑market plans can earn the missing evidence.

Per Article 52, clinical evaluation remains evidence‑driven. The reform reduces ambiguity, but does not lower the bar for proof.

A note on AI SaMD and continuously learning systems

The proposals explicitly signal special pathways for adaptive AI: conditional approvals with enforced governance, transparent model‑change controls, and real‑world performance obligations. In practice that requires:

• Versioned model governance embedded in your QMS.
• Clear procedures for model updates, revalidation, and user notification.
• Linkage between your MLOps pipeline and the device Technical File so changes are traceable and auditable.

If your software team treats model updates like dev ops and not like regulated device changes, you’ll be audited.

Final practical checklist (quick)

• Revise Technical File templates for staged submissions.
• Assign named PMCF/PSUR owners and budget.
• Map UDI → EUDAMED → vigilance dataflows and test them.
• Strengthen CAPA traceability (AI‑assisted CAPA assistance can help keep volume manageable).
• Ensure ISO 14971 risk traceability across pre/post‑market lifecycle.

These proposals, if adopted as drafted, shift some of the compliance workload later — but they also make it more concentrated and audit‑intense.

If you’re in a two‑person RA/QA team: don’t assume "conditional" equals "easier". It means sharper deadlines and more visible deliverables. Use your eQMS to keep that work reviewable and traceable.

What part of your Technical File or QMS would you prioritise for an accelerated‑access route: the initial clinical pack, the PMCF plan, or the data‑infrastructure that feeds signal detection?