Component Changes: When Your Clinical Evidence Suddenly Vanishes
A supplier notifies you that a critical component is discontinued. Your team sources an alternative, validates it technically, updates the risk file, and ships within weeks. Then the Notified Body asks: where is the clinical justification for this change? The technical file says compliant. The clinical evaluation file says nothing.
In This Article
This gap appears more often than most manufacturers expect. Supply chain disruption forces component substitutions. Teams move fast to maintain production. Technical documentation gets updated. But the clinical evaluation? It often remains untouched until an audit reveals the disconnect.
The assumption is simple: if the component meets the same specifications and passes verification testing, the clinical evidence remains valid. But MDR does not work on assumptions. It works on documented justification.
The Clinical Evaluation Obligation Under Component Change
Article 61(1) of MDR 2017/745 requires manufacturers to establish, document, implement, maintain, and update a clinical evaluation throughout the lifecycle of the device. This is not limited to design changes classified as significant by your change control procedure.
The clinical evaluation must demonstrate that the device meets the general safety and performance requirements (GSPRs) set out in Annex I. When a component changes, the question becomes: does the existing clinical evidence still support compliance with those requirements?
If the change affects device performance, biocompatibility, safety profile, intended use, or any element cited in the clinical evaluation, then the clinical evaluation must be updated. This is not optional. It is not triggered only by major design overhauls.
Even when a component substitution is classified as minor in your change control procedure, it may still require clinical evaluation update if it affects any element referenced in the clinical data supporting your GSPRs.
What Triggers the Need for Clinical Re-Evaluation?
Not every component change demands a full clinical re-evaluation. But the decision cannot be made by engineering alone. It requires input from clinical affairs and regulatory to assess whether the change impacts the clinical evidence basis.
Here are the critical questions:
Does the change affect biocompatibility?
Material changes, coatings, adhesives, or components in contact with tissue or blood require biocompatibility reassessment per ISO 10993-1. If new tests are performed, the clinical evaluation must reference them and justify continued compliance with Annex I requirements related to material safety.
Does the change affect device performance or functionality?
If the component plays any role in the intended clinical outcome—sensor accuracy, delivery mechanism, structural integrity under use—then the clinical data supporting performance claims must be reviewed. Equivalence arguments may no longer hold if the new component differs in material, geometry, or mechanism.
Does the change affect the risk profile?
If new risks are introduced or existing risks change likelihood or severity, the clinical evaluation must address whether the benefit-risk balance remains acceptable. This includes referencing the updated risk management file and justifying that residual risks remain acceptable in light of clinical benefits.
Does the change affect claims made in the clinical evaluation?
If your CER cites device characteristics—material properties, dimensional tolerances, mechanical performance—and the component change alters any of those, the justification for your clinical claims may be undermined. Reviewers will notice if the technical file describes version B but the CER still references version A.
Manufacturers update the risk file and technical documentation but leave the clinical evaluation report unchanged. During audit, the Notified Body identifies a mismatch: the device described in the CER no longer matches the device in production. This creates doubt about whether the clinical evidence still applies.
The Equivalence Problem
Component changes become especially complex when the clinical evaluation relies on equivalence to another device. Equivalence is built on demonstrating that your device and the equivalent device are similar enough—clinically, technically, and biologically—that the clinical data from the equivalent device can support your device’s safety and performance.
MDCG 2020-5 lays out strict criteria for claiming equivalence. Technical equivalence requires that devices are of similar design, use similar materials and technologies, and have similar specifications. Clinical equivalence requires similar clinical performance, similar intended use, and similar risk profiles.
When you change a component, you may break equivalence. If the new component uses a different material, a different manufacturing process, or different mechanical properties, the technical equivalence argument may no longer hold. And if technical equivalence is lost, clinical equivalence is lost.
This does not mean you must abandon the equivalence claim entirely. But you must reassess it. You must document whether the change affects the parameters that supported equivalence. If it does, you must either justify why equivalence still holds or generate additional clinical data to fill the gap.
Many manufacturers discover this too late. They assume that because the change was validated internally, equivalence remains intact. But the Notified Body applies MDCG 2020-5 criteria independently. If your updated technical file shows a device that diverges from the equivalent device in a way that affects clinical similarity, the equivalence claim collapses.
Documentation and Traceability
The clinical evaluation file must trace the evolution of the device. When a component changes, the clinical evaluation update should reference the change, explain its impact on clinical evidence, and justify the decision to either update evidence or maintain the existing basis.
This is not bureaucracy. It is how you demonstrate control over your clinical evaluation process. Reviewers assess whether you have a systematic approach to maintaining the validity of your clinical evidence throughout the device lifecycle.
Here is what effective documentation includes:
A summary of the component change:
What was changed, why, and what technical validation was performed.
An assessment of clinical impact:
Which GSPRs and clinical claims might be affected. Which sections of the CER reference device characteristics that changed.
A justification of clinical evidence validity:
Why the existing clinical data remains applicable, or what new data is needed. This must be explicit, not implied.
Updated risk-benefit analysis if needed:
If the risk profile changed, the clinical evaluation must reflect the updated risk analysis and justify that the benefit-risk ratio remains favorable.
Traceability to other technical documentation:
The CER should reference the latest device version, the latest risk file version, and the latest biocompatibility assessment if applicable.
The clinical evaluation is not a static document. It is a living file that must evolve with the device. Every change that affects clinical claims, risk profile, or equivalence basis should trigger a review, even if that review concludes no update is needed. The review itself must be documented.
The Notified Body Perspective
Notified Bodies see component changes regularly. They know that supply chain pressure forces substitutions. They also know that many manufacturers treat clinical evaluation as a pre-market formality rather than a lifecycle obligation.
When reviewing a component change, the Notified Body looks for alignment. Does the clinical evaluation file reflect the current device? Does it justify that the clinical evidence still applies? Does it address any new risks or changes in equivalence?
If the answers are unclear, the reviewer raises findings. These findings are not minor. They signal a fundamental gap in how clinical evaluation is maintained. And they delay approvals, batch releases, and certificate renewals.
The most common deficiency is silence. The technical file describes the change. The risk file addresses it. But the clinical evaluation file says nothing. The Notified Body then has no basis to assess whether clinical evidence remains valid. They must assume it does not, and they must request justification.
The second most common deficiency is vague justification. The manufacturer adds a sentence to the CER: “Component X was replaced with Component Y, which has equivalent performance.” But no evidence supports this claim. No testing data. No comparison of materials. No reassessment of equivalence criteria.
Reviewers do not accept assertions. They assess evidence. If the component change affects clinical relevance, the justification must be detailed and traceable.
What Should You Do When a Component Changes?
The process starts with cross-functional review. Do not let engineering decide alone whether a change is clinically relevant. Involve clinical affairs and regulatory from the start.
Ask these questions together:
Does this change affect biocompatibility?
Does it affect performance cited in clinical claims?
Does it affect risk profile?
Does it affect equivalence basis?
Does it affect any GSPR justification in Annex I?
If the answer to any question is yes, update the clinical evaluation. If the answer is no, document the assessment and file it. The justification for not updating is as important as the update itself.
When updating the clinical evaluation, be explicit. Describe the change. Reference the validation data. Explain why the clinical evidence remains applicable or what additional data was generated. Update the risk-benefit analysis if needed.
And update all related documents in parallel. If the CER changes, ensure the clinical evaluation plan, the PMCF plan, and the summary of safety and clinical performance (SSCP) reflect the change if relevant.
Manufacturers update the CER but forget to update the clinical evaluation plan or the PMCF plan. The Notified Body finds inconsistencies during the next audit. The result is additional findings and follow-up reviews that could have been avoided with better document control.
Why This Matters Beyond Compliance
Maintaining the clinical evaluation through component changes is not just about satisfying Notified Body requirements. It is about maintaining confidence in your device’s safety and performance.
If you do not assess clinical impact when components change, you risk shipping a device whose clinical evidence no longer applies. You risk missing safety signals. You risk undermining post-market surveillance because your PMCF plan targets the wrong device version.
The clinical evaluation is your documented argument that the device is safe and performs as intended. When the device changes, that argument must be reassessed. If you skip this step, you lose control over the foundation of your regulatory compliance.
This is why Notified Bodies pay attention. They are not checking boxes. They are assessing whether you have a systematic process to ensure that clinical evidence remains valid as the device evolves.
If that process is missing, the entire clinical evaluation framework is at risk.
Final Reflection
Component changes will happen. Supply chains will fail. Suppliers will discontinue materials. You will need to adapt quickly.
The question is whether your clinical evaluation process can keep up. If it cannot, you will face delays, findings, and doubt about the validity of your clinical evidence.
The solution is not complex. It is discipline. Assess every change for clinical relevance. Document the assessment. Update the clinical evaluation when needed. Maintain traceability across all files.
Do this consistently, and component changes become manageable. Skip it, and each change becomes a regulatory risk that compounds over time.
Peace,
Hatem
Clinical Evaluation Expert for Medical Devices
Follow me for more insights and practical advice.
Frequently Asked Questions
What is a Clinical Evaluation Report (CER)?
A CER is a mandatory document under MDR 2017/745 that demonstrates the safety and performance of a medical device through systematic analysis of clinical data. It must be updated throughout the device lifecycle based on PMCF findings.
How often should the CER be updated?
The CER should be updated whenever significant new clinical data becomes available, after PMCF activities, when there are changes to the device or intended purpose, and at minimum during annual reviews as part of post-market surveillance.
What causes CER rejection by Notified Bodies?
Common reasons include inadequate equivalence demonstration, insufficient clinical data for claims, poorly structured SOTA analysis, missing gap analysis, and lack of clear benefit-risk determination. Structure and logical flow are as important as the data itself.
Which MDCG guidance documents are most relevant for clinical evaluation?
Key documents include MDCG 2020-5 (Equivalence), MDCG 2020-6 (Sufficient Clinical Evidence), MDCG 2020-13 (CEAR Template), MDCG 2020-7 (PMCF Plan), and MDCG 2020-8 (PMCF Evaluation Report).
Need Expert Help with Your Clinical Evaluation?
Get personalized guidance on MDR compliance, CER writing, and Notified Body preparation.
✌
Peace, Hatem
Your Clinical Evaluation Partner
Follow me for more insights and practical advice.
– MDR 2017/745 Article 61
– MDR 2017/745 Annex I (General Safety and Performance Requirements)
– MDCG 2020-5 (Clinical Evaluation – Equivalence)
– MDCG 2020-13 (Clinical Evaluation Assessment Report Template)
Deepen Your Knowledge
Read Complete Guide to Clinical Evaluation under EU MDR for a comprehensive overview of clinical evaluation under EU MDR 2017/745.
