Heading

For many medical device manufacturers, reaching the notified body review stage under the EU Medical Device Regulation (EU MDR 2017/745) feels like crossing the finish line. Technical documentation is prepared, clinical evidence is compiled, risk files are updated, and expectations are high for a smooth conformity assessment.

Yet, this is often where delays begin.

Notified body reviews are far more rigorous than many manufacturers anticipate. Unlike the legacy MDD framework, MDR has significantly increased expectations around clinical evidence, technical documentation, post-market surveillance, and regulatory justification.

A common reason for delays is not missing documentation—it is being unprepared for the right questions.

Manufacturers often focus on assembling files but fail to prepare strong, evidence-based responses to the questions notified bodies are most likely to ask.

Here are the top 7 notified body questions manufacturers frequently fail to prepare for—and how to address them effectively.

1. How Have You Demonstrated Sufficient Clinical Evidence for This Device?

This is one of the first and most critical questions.

Under MDR, notified bodies expect manufacturers to provide clear evidence that demonstrates safety, performance, and clinical benefit for the intended purpose of the device.

Many manufacturers make the mistake of relying heavily on:

• Legacy MDD data
• Limited literature reviews
• Outdated post-market data
• Generic equivalence claims

The problem is that MDR requires device-specific, robust, and current clinical evidence.

What Notified Bodies Expect:

• A well-structured Clinical Evaluation Report (CER)
• Justified clinical data sources
• Clear linkage between clinical evidence and intended purpose
• Demonstration of benefit-risk acceptability

How to Prepare:

Ensure your CER clearly answers:

• Why is the available evidence sufficient?
• How does it support every intended use claim?
• Are there evidence gaps?
• How are residual uncertainties addressed?

Clinical evidence should tell a clear regulatory story—not simply compile data.

2. Why Is Clinical Investigation Not Required?

Many manufacturers assume they can avoid clinical investigations through literature equivalence or historical market experience.

Notified bodies frequently challenge this assumption.

Under MDR Article 61, skipping a clinical investigation requires strong scientific and regulatory justification.

Common Weaknesses:

• Unsupported equivalence claims
• Incomplete literature rationale
• Lack of access to equivalent device technical documentation
• Insufficient PMCF support

What Notified Bodies Ask:

“Please justify why existing clinical evidence is sufficient without conducting a clinical investigation.”

How to Prepare:

Your justification should clearly explain:

• Why clinical investigation is unnecessary
• What evidence replaces it
• How equivalence has been demonstrated
• How uncertainties are managed through PMCF

If your rationale is weak, expect follow-up rounds.

3. How Does Your Risk Management File Connect to Clinical Evidence?

A major MDR expectation is integration across documentation.

Notified bodies often identify disconnects between:

• Risk management files
• Clinical evaluation reports
• PMS data
• Usability files

For example:

A CER may discuss a clinical risk that is absent from the risk management file.

This inconsistency raises immediate concerns.

What Notified Bodies Expect:

A fully aligned evidence chain showing:

Hazard identification → Risk control → Clinical validation → PMS monitoring

How to Prepare:

Cross-check consistency across:

• ISO 14971 risk file
• CER
• IFU
• PMS documentation
• PMCF plans

Every clinical risk should be traceable and justified.

4. How Have You Justified Your Benefit-Risk Determination?

Many manufacturers state that benefits outweigh risks—but fail to explain how this conclusion was reached.

Under MDR, benefit-risk evaluation requires documented evidence and structured reasoning.

Notified bodies often ask:

“What objective evidence supports your benefit-risk conclusion?”

Weak Responses Include:

• Generic statements
• Unsupported assumptions
• Qualitative conclusions without measurable evidence

Strong Responses Include:

• Clinical performance outcomes
• Risk probability/severity assessments
• Comparative clinical outcomes
• Residual risk acceptability rationale

How to Prepare:

Your benefit-risk analysis should demonstrate:

• Quantified or justified benefits
• Residual risks after controls
• Why benefits remain acceptable

The conclusion must be defensible—not assumed.

5. What Is Your PMS Strategy for Detecting Emerging Risks?

Post-market surveillance is no longer a routine compliance checkbox.

Under MDR, notified bodies expect proactive systems capable of detecting trends, complaints, adverse events, and performance degradation.

Many manufacturers present generic PMS procedures that lack device-specific detail.

Common Issues:

• Broad PMS templates
• No trend analysis methodology
• Undefined review frequency
• Weak complaint escalation criteria

What Notified Bodies Want:

A PMS system that demonstrates:

• Active surveillance
• Defined data collection sources
• Clear escalation pathways
• Trending methodology

How to Prepare:

Clearly define:

• Data sources
• Review intervals
• Statistical trend thresholds
• CAPA trigger criteria

Your PMS plan should reflect real-world vigilance readiness.

6. Why Is Your PMCF Plan Appropriate?

A surprisingly common failure point is weak Post-Market Clinical Follow-up (PMCF) justification.

Manufacturers often either:

• Submit generic PMCF templates
• Claim PMCF is unnecessary without adequate rationale

Notified bodies closely examine whether PMCF appropriately addresses residual uncertainties.

Questions You May Face:

• What residual risks remain?
• How will long-term performance be monitored?
• Why is this PMCF approach sufficient?

How to Prepare:

Your PMCF plan should include:

• Clear objectives
• Specific endpoints
• Defined data collection methods
• Timelines
• Links to CER evidence gaps

PMCF should not be a copied template—it must be device-specific.

7. How Have You Ensured Technical Documentation Completeness Under Annex II and III?

This is where many submissions stall.

Manufacturers often believe documentation is complete because all required sections exist.

But notified bodies assess quality, coherence, traceability, and justification.

A technically complete file with weak rationale can still trigger major non-conformities.

Frequent Gaps:

• Missing rationale for standards applicability
• Inconsistent labeling information
• Incomplete GSPR mapping
• Poor traceability between evidence sources

How to Prepare:

Conduct a structured gap review against:

• Annex II
• Annex III
• Device classification rules
• Applicable MDCG guidance

Ask:

Can every claim in this file be traced to objective evidence?

If not, strengthen it before submission.

Final Thoughts

The biggest mistake manufacturers make is preparing documentation for submission rather than preparing documentation for scrutiny.

Notified body reviews under MDR are no longer administrative exercises. They are detailed technical evaluations designed to challenge assumptions, validate evidence, and confirm regulatory robustness.

The most successful manufacturers prepare by asking these difficult questions before the notified body does.

A strong submission is not just complete.

It is:

• Justified
• Defensible
• Traceable
• Evidence-driven
• Strategically aligned

Preparing for these seven questions can significantly reduce review cycles, prevent avoidable delays, and improve your pathway to CE marking success.

In MDR compliance, preparation is no longer optional—it is your strongest regulatory advantage.