EU MDR Compliance: Where Medical Device Manufacturers Commonly Get Stuck

Getting a medical device ready for the European market under Regulation (EU) 2017/745 (MDR) is not simply a matter of updating an MDD technical file and sending it to a Notified Body.

The MDR requires manufacturers to demonstrate a much tighter connection between the device, its clinical evidence, risk management, technical documentation, quality system, and post-market activities.

That is where many manufacturers run into trouble.

A clinical evaluation may not fully support the device's claims. The risk-management file may not reflect the clinical findings. The PMS system may not address the risks identified during the pre-market assessment. The QMS may be ISO 13485 certified but not adequately aligned with the manufacturer's MDR obligations.

These disconnects are exactly the types of issues that lead to Notified Body deficiency questions, repeated review cycles, additional testing, remediation work, and delayed market entry.

The 12 Areas Where Manufacturers Commonly Get Stuck

1. Getting the Device Classification Wrong

Classification is one of the first decisions in an MDR project—and one of the easiest places to create downstream problems. The applicable classification under Annex VIII must be supported by the device's intended purpose and the relevant classification rules. It is not enough to rely on how the device was classified under the MDD or how a similar product is classified by another manufacturer.

Particular attention is often needed for:

• Medical device software (MDSW) and SaMD (Rule 11)
• Implantable and invasive devices
• Reusable surgical instruments (Class Ir)
• Active therapeutic and diagnostic devices
• Devices incorporating medicinal substances or nanomaterials
• Combination and borderline products
• Devices with measuring functions (Class Im)

A classification decision should be documented with a clear regulatory rationale. If the classification is weak, the conformity-assessment strategy, clinical requirements, QMS scope, and Notified Body involvement can all be affected.

2. Assuming Existing Clinical Data Will Be Enough

This is one of the most common issues seen during MDR remediation. Manufacturers often have years of clinical experience, published literature, legacy MDD data, or data from a comparable device. The problem is not necessarily the absence of data—it is whether the data actually supports the device being placed on the EU market today.

The clinical evaluation needs to rigorously address intended purpose, clinical claims, state of the art (SOTA), benefit-risk profile, clinical risks, and the relevant patient population. Equivalence also requires careful consideration: a generic statement that another device is “similar” is not enough to establish regulatory equivalence under the MDR.

3. Treating PMS as a Compliance File Instead of a Feedback System

Post-market surveillance should not be a static document that sits on a shelf after CE marking. A well-designed PMS system provides ongoing information that feeds back into clinical evaluation, PMCF, risk management, CAPA, vigilance, trend reporting, labelling, and technical documentation.

A common weakness is a PMS procedure that looks complete on paper but does not define meaningful data sources, responsibilities, analysis methods, statistical thresholds, or proactive actions.

4. Technical Documentation That Does Not Tell One Consistent Story

A strong MDR technical file should read as one connected body of evidence. Unfortunately, inconsistencies between documents are common:

• The intended purpose in the technical documentation differs from the wording in the clinical evaluation.
• Clinical claims are not supported by the available clinical evidence.
• The risk-management file identifies risks that are not addressed in the IFU.
• The PMS plan does not monitor the specific uncertainties flagged in the CER.

These inconsistencies create immediate questions during Notified Body review. A technical file should be reviewed not only for completeness, but also for consistency and end-to-end traceability.

5. Risk Management That Stops at the Risk File

Risk management under ISO 14971 should not operate independently from the rest of the regulatory system. There should be a continuous relationship:

If these elements do not connect, the manufacturer will struggle to demonstrate that risks have been adequately controlled throughout the device lifecycle.

6. A PMCF Plan That Exists Only Because the MDR Requires One

Post-Market Clinical Follow-up should answer a specific question: What additional clinical information do we need after market entry, and how will we obtain it?

A generic PMCF plan rarely satisfies a Notified Body. The PMCF strategy should be directly connected to the clinical evaluation and address identified evidence gaps or residual clinical uncertainties through registries, PMCF clinical investigations, or structured user follow-up.

7. Labelling and IFU Are Not an Afterthought

Labelling and Instructions for Use (IFU) are often left until late in the project. That is risky. User information must strictly align with technical documentation, risk management, clinical evaluation and claims. A last-minute label review can expose inconsistencies that unravel several other parts of the submission dossier.

8. Assuming ISO 13485 Certification Equals MDR Compliance

ISO 13485 is an essential foundation, but it is not a substitute for MDR compliance. A manufacturer can hold ISO 13485 certification and still have severe gaps in MDR-specific requirements such as clinical evaluation procedures, PMS/PMCF systems, vigilance reporting, economic-operator controls, and General Safety and Performance Requirements (GSPR) documentation.

9. Waiting Too Long to Engage the Notified Body

Notified Body capacity remains constrained across Europe. Early engagement is essential, but it does not mean approaching a Notified Body with an unfinished regulatory strategy and half-prepared documentation. Clear classification, conformity route, QMS readiness, and dossier maturity must be established first.

10. Underestimating Economic Operator Responsibilities

Manufacturers outside the EU must pay close attention to European Authorised Representatives (EC REP / EAR), importers, and distributors. The MDR assigns strict statutory responsibilities regarding verification, registration, traceability, complaints, and vigilance communication, which must be formalized in robust agreements.

11. UDI and EUDAMED Should Be Built Into the Regulatory Process

Basic UDI-DI allocation, device registration, and EUDAMED data governance should be treated as core operational requirements rather than administrative afterthoughts. Inconsistencies between UDI attributes and technical documentation cause significant bottlenecks.

12. MDR Compliance Does Not End With the CE Certificate

CE marking is not the finish line. The MDR establishes continuing obligations throughout the product lifecycle. Manufacturers must continuously monitor PMS data, vigilance signals, emerging clinical literature, MDCG guidance updates, standard revisions, and design changes.

What a Strong MDR Readiness Assessment Looks At

Before entering formal Notified Body review, manufacturers should step back and audit the entire regulatory system:

How NKB Regovanta Supports EU MDR Compliance

At NKB Regovanta, we approach MDR compliance as an integrated regulatory, clinical and quality-system exercise. Our role is not limited to preparing documents for submission—we work alongside manufacturers to establish defensible strategies that withstand intense Notified Body scrutiny:

• MDR Regulatory Strategy & Gap Assessment
• Medical Device Classification (Annex VIII)
• Technical Documentation Preparation and Review (Annex II/III)
• Clinical Evaluation & Clinical Evidence Strategy (MEDDEV / MDCG)
• PMCF Planning and Documentation
• Risk Management Integration (ISO 14971:2019)
• ISO 13485 QMS Development and MDR Alignment
• PMS, Periodic Safety Update Reports (PSUR) and Vigilance
• UDI, Labelling and IFU Compliance Audits
• Notified Body Review Deficiency Support

The Bottom Line

The MDR has raised the standard for demonstrating medical device safety, performance and clinical benefit in Europe. Manufacturers that approach MDR as a documentation exercise often discover gaps late—during Notified Body review or after market entry.

A stronger approach is to build the regulatory system around the device from the beginning. Classification, clinical evidence, risk management, technical documentation, QMS, PMS and post-market clinical follow-up should all tell the same story.