Notified Body Readiness: Does Your MDR Evidence Tell One Story?
A technical file can be complete and still generate difficult Notified Body questions.
The issue is not always a missing document. Sometimes the vulnerability appears when the evidence package is read as a whole.
Your product claims may appear reasonable on their own. Your clinical evaluation report may be complete. PMCF and PMS activities may each have their own plans and reports. Risk management documentation and the SSCP may also be present.
But when those materials are placed side by side, do they support the same evidence story?
That is where Notified Body readiness goes beyond document completeness.
Completeness and readiness are not the same question
A completeness check asks whether the expected documentation exists.
A readiness review asks a different question: what happens when a reviewer begins moving across those documents and testing whether the assumptions, claims, evidence and conclusions remain aligned?
A file can therefore look complete section by section while still creating questions at the points where one document depends on another.
Those interfaces deserve attention before formal scrutiny begins.
Stress-test the evidence interfaces
One useful way to examine an MDR evidence package is to stop reviewing each document only within its own lane.
Instead, follow the evidence story across:
- Product claims
- Clinical Evaluation Report (CER)
- Post-Market Clinical Follow-up (PMCF)
- Post-Market Surveillance (PMS)
- Risk management documentation
- Summary of Safety and Clinical Performance (SSCP)
The objective is not simply to confirm that each document exists. It is to identify whether the connections between them are defensible.
For example, consider the claims being made for the device. Then ask whether the clinical evidence supports those claims consistently. Look at the uncertainties or evidence needs reflected in the CER. Compare those with the questions PMCF and PMS are designed to address. Then examine whether the risk documentation and SSCP communicate a position that remains consistent with the same evidence base.
The useful question is straightforward:
If your Notified Body placed your CER, PMCF, PMS, risk management documentation, SSCP and product claims side by side today, would they tell the same story?
Contradictions often appear between documents
Teams naturally work within functional responsibilities. Regulatory, clinical and quality groups may each maintain different parts of the technical documentation.
That makes cross-document review especially important.
The weakness may not sit neatly inside a single document. It may appear in the relationship between documents.
A claim may be broader than the evidence position reflected elsewhere. A conclusion may rely on an assumption that another document does not carry forward. A post-market activity may not clearly connect to an uncertainty identified in the clinical evidence. The risk position may not read the same way as the clinical or public-facing evidence story.
These are the kinds of interfaces worth finding before a reviewer finds them.
Repeated questions may point to something larger
When the same issue continues to reappear through review cycles, it can be useful to ask whether the problem is larger than the wording of an individual response.
Repeated questions may indicate that the underlying evidence position is not fully aligned across the system.
In that situation, producing another isolated answer may not resolve the reason the question keeps returning.
Leadership may need a clearer view of where the evidence story separates, which assumption needs to be revisited and which decision should happen before more document work continues.
A practical readiness review
Before a submission, renewal or response cycle, bring the core evidence documents together and review them through the questions they may generate rather than only through the sections they contain.
Look for where the story changes.
Identify where a claim depends on evidence that is weaker, narrower or differently framed elsewhere. Trace open questions through CER, PMCF and PMS. Compare those findings with the risk position and SSCP. Separate straightforward documentation gaps from contradictions that may require a broader regulatory, clinical or management decision.
The goal is not to create more documentation.
The goal is to understand which parts of the existing evidence package are aligned, where tension exists and where action is needed before formal scrutiny makes the decision for you.
Put the evidence package under review before the reviewer does
On October 14, SHOTUNE Medical Consulting Group is hosting the live executive webinar Notified Body Ready? What Your MDR Documentation Needs to Withstand Before the Questions Begin.
The session will show MedTech regulatory, clinical and quality leaders how to distinguish a technically complete file from a review-ready evidence package and how to stress-test alignment across Claims → CER → PMCF → PMS → Risk → SSCP.