I’ve been through enough MDR audits and remediations to see the same misunderstandings show up across teams. People treat CE marking like a rubber stamp process that changed slightly in 2017 — but MDR is a rework of the whole safety and evidence model. Below are the differences I actually had to live through with my engineering and RA colleagues, plus pragmatic steps that helped us survive tighter review by notified bodies.
The headline differences that matter in practice
These aren’t legal theory — they’re the items that caused audit findings in my work:
- Stronger clinical evidence expectations. Clinical evaluation and post-market clinical follow-up (PMCF) need to be proportional, continuous, and demonstrable. The “literature-only” approach for borderline devices seldom stands up anymore.
- More rigorous post-market surveillance (PMS). It’s not a paper plan: you must feed PMS into risk management, trigger CAPAs, and produce periodic outputs (PSUR-type reporting) for higher-risk devices.
- Person Responsible for Regulatory Compliance (PRRC). This is an explicit role with documented qualifications and defined responsibilities — your org needs someone accountable, not just an external consultant on retainer.
- UDI and traceability. Unique Device Identification is real work: labelling, UDI-DI relationships, and linking to technical documentation and vigilance entries.
- Notified bodies changed scope and scrutiny. They want deeper technical documentation, more robust clinical justifications, and evidence that your QMS enforces MDR-specific processes.
- Economic operators clarified. Authorized representatives, importers, and distributors now have explicit obligations — contracts and agreements must reflect those.
If you’re still treating CE as “same as MDD,” you’ll hit findings where it counts: clinical files, PMS outputs, and the traceability between risk, performance, and post-market data.
Where teams typically get it wrong
From my audits and remediation projects, the recurring missteps are:
- Treating clinical evaluation as a one-off dossier. Wrong rhythm. It’s a lifecycle activity; literature review, clinical data, and PMCF loop back to risk.
- Keeping PMS as a passive archive. PMS must generate signals and action. If it sits in a folder and only gets updated for audits, you’ll fail to demonstrate proactive risk control.
- Underestimating labeling and UDI complexity. Label design, barcode generation, and UDI administration across SKUs and kits were more painful than anyone expected.
- Ambiguous PRRC responsibilities. Listing a title on org chart isn’t enough — the PRRC must have documented tasks and evidence they actually participate in conformity assessment.
- Not mapping supplier obligations. Suppliers are now upstream sources of regulatory data; supplier agreements and incoming controls must reflect MDR expectations.
- Assuming the Notified Body will “fill the gaps.” Notified bodies assess; they won’t remediate your QMS. Expect them to flag problems earlier and more sharply than under MDD.
Practical fixes that worked for us
If you need to triage effort because audit is months away, focus on these high-value items first:
-
Clinical strategy and gap list
- Do a rapid clinical evaluation gap assessment: what sources of data do you actually have vs what the MDR expects?
- Prioritize ongoing PMCF activities that can be initiated quickly (registries, targeted follow-up calls).
-
PMS → CAPA → Risk linkage
- Turn PMS outputs into documented inputs to risk management. If trends are detected, show the CAPA and risk-file link.
- Instrument one traceable example end-to-end (complaint → investigation → CAPA → design change → verification).
-
PRRC evidence pack
- Create a short packet that documents the PRRC’s qualifications, appointment letter, role description, and meeting minutes showing involvement in conformity decisions.
-
UDI pilot
- Pick a pilot SKU and implement UDI on label, packing, and in your internal ERP. Document procedures for generation and assignment of basic UDI-DI.
-
Notified Body readiness
- Update your technical documentation table of contents to mirror MDR Annex structure. Even a mapped index will speed NB review and reduce nonconformities.
-
Supplier contracts and evidence
- Ensure supplier technical files and declarations are accessible. Add incoming inspection checks for regulatory-relevant attributes.
Tools and automation pointers (real-world focus)
- Use your QMS to link records. The audit will want traceability from an adverse event through investigation to technical documentation updates — avoid siloed folders.
- Automate routine PMS data pulls where possible (sales, complaint rates, field performance) so you can show trend analysis instead of manual spreadsheets.
- Template clinical evaluation reports and PMCF protocols saved engineering time; they’re not a substitute for evidence but speed documentation.
I’m intentionally not pitching products here — pick tools that can maintain traceable connections between documents, risk files, clinical evidence, and CAPAs.
Final practical reminder
CE under MDR is still a manufacturer’s declaration of conformity, but the bar for the evidence and the systems that produce it is higher. For teams used to MDD-era checklists, the work isn’t just more documents — it’s redesigning how clinical data, risk management, and post-market intelligence talk to each other day-to-day.
What’s one concrete change your team made to link PMS outputs to design verification or CAPA — and did it survive your next audit?
Top comments (0)