Acceptability Is Not a Fixed Standard
Under the EU MDR 2017/745, acceptability is not a fixed or predefined threshold.
It is a context-dependent determination based on a risk-based approach, where the adequacy of technical documentation is evaluated in relation to the following:
- Device risk classification
- Clinical complexity
- Novelty of technology
- Strength of justification of supporting evidence
Consequently, documentation that appears complete and structured may still be considered insufficient if it does not provide scientifically valid, clinically relevant, and well-justified evidence appropriate to the device under assessment.
In MDR terms: “Acceptable” = Justified + Contextual + Scientifically defensible
What is acceptable in one context may be unacceptable in another?
1. The Regulatory Lens: How documentation is actually evaluated
Technical documentation is no longer evaluated as a checklist of required sections. Instead, regulators assess it as a connected body of scientific reasoning.
Three core questions typically guide this evaluation:
- Does the documentation demonstrate compliance with Annex I GSPRs?
- Are the conclusions supported by relevant, sufficient, and device-specific clinical, pre-clinical, and post-market data?
- Is there clear linkage across clinical evaluation, risk management, and post-market surveillance?
If the answer to any of these is uncertain, the documentation shifts from acceptable to unacceptable regardless of how complete it appears.
2. The Illusion of Compliance
A common challenge in EU MDR submissions is the illusion of compliance, where:
- Required sections are present
- Standard formats are followed
- References are included
But… the underlying justification is weak, generic, or assumed.
Examples:
- Literature is cited, but relevance to the specific device is not demonstrated
- Risk acceptability is stated, but not clinically justified
- Claims align with general knowledge rather than device-specific evidence
This creates a gap between:
- Formal compliance (what is written)
- Substantive compliance (what is scientifically demonstrated)
This gap is where most regulatory findings originate.
Where Acceptability Breaks Down
1. When relevance is assumed rather than demonstrated
- Using literature on similar devices without demonstrating comparability in design, materials, or intended Purpose.
- Applying population data without justification for applicability to the device’s target users
Without explicit justification, data may be considered supportive at best, not sufficient as evidence.
2. When Justification Is Implicit Instead of Explicit
Many documents rely on statements that imply sufficiency without demonstrating it.
Examples include:
- “The literature supports safety and performance”
- “Risks are acceptable based on current knowledge”
These statements may be technically correct, but without supporting rationale, clear linkage to specific data and explanation of how conclusions were reached.
Problem: The reasoning is hidden. Regulators can’t see how you reached the conclusion.
Under EU MDR, regulators expect to see the logical pathway from data → analysis → conclusion.
If that pathway is not visible, the conclusion is not considered reliable.
3. When Documents Exist but Do Not Communicate
Technical documentation often contains all required elements but lacks clarity in how they connect. For Example:
- Residual risks identified in the risk management file are not addressed in the clinical evaluation
- PMS data is presented but not analysed for trends or clinical impact
- Slight differences in conclusions across CER, RMF, and PMS reports
This creates a situation where each document may appear acceptable individually, but collectively they fail to support a consistent scientific position.
Regulators expect documentation to function as an integrated system, where each element reinforces the others.
4. When State-of-the-Art Is Treated as Background Information
State-of-the-art (SOTA) is sometimes listed descriptively, rather than informing device design, safety, and performance expectations. For Example:
Outdated references, lack of comparison to alternatives, general disease description without relevance to device claims
SOTA directly influences how regulators assess:
- Whether the device offers meaningful clinical benefit
- Whether risks are acceptable compared to alternatives
- Whether claims are realistic in today’s context
If SOTA is weak, all downstream conclusions—especially benefit–risk—become difficult to justify.
5. When Lifecycle Thinking Is Missing
EU MDR requires continuous evaluation across the entire device lifecycle.
Documentation becomes unacceptable when:
- PMS findings are not integrated into clinical evaluation
- PMCF is dismissed without scientific rationale
- Risk assessments are not updated based on real-world data
This reflects a static approach to documentation, where information is treated as fixed rather than evolving.
Regulators expect documentation to show ongoing learning and adaptation based on real-world use.
How These Issues Are Identified in Practice
These gaps are rarely flagged due to missing sections. They are flagged because something cannot be defended.
Typical regulator questions include:
- “How does this apply specifically to your device?”
- “Where is the clinical justification?”
- “How is this claim supported?”
- “How are PMS findings reflected in your conclusions?”
If documentation cannot clearly answer these questions, it is considered insufficient.
From Documentation to Demonstration
Technical documentation is no longer about collecting information, it is about demonstrating evidence.
A strong submission shows:
- Data → Analysis → Justification → Evidence
- Clear reasoning behind every conclusion
- Alignment across all documents
- Continuous updates based on real-world data
Conclusion: Acceptability Is Defined by Defensibility
Under EU MDR, the concept of “acceptability” extends far beyond the mere presence of documented sections or adherence to templates. True compliance is measured by defensibility—whether every claim, conclusion, and risk assessment is convincingly demonstrated, scientifically justified, and traceable across the device lifecycle. What may appear acceptable during internal reviews can still fail under Notified Body scrutiny if the reasoning is implicit, data relevance is assumed, or documents lack integration.
The regulatory focus has shifted: it is no longer enough to ask, “Is this documented?” The question that defines compliance today is, “Is this evidence-based, robust, and defensible?” Achieving this standard requires rigorous justification, clear reasoning, and a holistic approach to documentation that connects clinical evidence, risk management, and post-market insights into a cohesive, scientifically sound narrative.
Reference:
MDCG 2020‑6 Guidance on Sufficient Clinical Evidence for MDR
