Under the EU MDR, clinical evaluation is considered a continuous process. This means that the Clinical Evaluation Report (CER) should be reviewed and updated throughout the lifetime of the device, taking into account new clinical data and relevant changes. The key considerations are when an update is needed, how frequently the CER should be reviewed, and which developments or findings may trigger an update.
What the MDR Annex XIV Says
MDR Annex XIV, Part A states that the clinical evaluation and its documentation must be updated with data obtained from post-market surveillance. It also links directly to the obligation to conduct PMCF, the results of which feed back into the CER on an ongoing basis.
In plain language: your PMCF findings are not just data to be collected. They are mandatory inputs to your CER. A CER that has not been updated with current PMCF data is a non-compliant CER.
Event-Based Triggers for CER Updates
Beyond the periodic update cycle, specific events should trigger an immediate CER review:
Device Changes
- Any modification to the device design, materials, or software that could impact safety or performance
- Changes to the intended purpose or target patient population
- Expansion to new clinical indications
New Clinical Evidence
- Publication of new clinical data on your device or equivalent devices
- Completion of clinical investigations or registries involving your device
- New systematic reviews or meta-analyses relevant to your technology
Post-Market Signals
- Adverse events, field safety corrective actions (FSCAs), or recalls
- Trends identified in your Post-Market Surveillance report (PMSR)
- Vigilance reports from comparable devices on the market
Regulatory and Guidance Changes
- New MDCG guidance relevant to your device’s risk class or technology
- Updated harmonized standards affecting your device’s safety or performance claims
- Notified Body feedback from surveillance audits
Recommended Update Frequencies by Risk Class
Some manufacturers wait for their Notified Body’s surveillance audit or renewal cycle to update their CER. This is a high-risk strategy. If a post-market signal emerged between updates and you did not act on it, the absence of an updated CER becomes evidence of a systemic failure.
The MDR’s continuous evaluation requirement exists for patient safety reasons. Manufacturers who internalize this — rather than treating it as a documentation burden — are better positioned both regulatorily and commercially. While MDR does not prescribe fixed update intervals, industry best practice and Notified Body expectations broadly align as follows:
| Risk Classification | Recommended Update Frequencies |
|
Class III and Implantable devices |
Annual CER review as a baseline, with event-triggered updates in between |
|
Class IIb devices |
Review at least every two years, or sooner if triggered by PMCF findings or post-market signals |
|
Class IIa devices |
Review every two to three years, with continuous PMS monitoring to identify triggers |
|
Class I devices (with measuring function or sterility) |
At a minimum upon any significant change; continuous PMS monitoring required |
These are starting points. Your specific device’s risk profile, complexity, novelty, and available evidence base may require a more frequent update cycle.
Building a CER Lifecycle Management Process
The most effective approach to CER maintenance is to embed it within your Quality Management System (QMS) as a scheduled, documented activity, not a reactive response to regulatory pressure.
A robust CER lifecycle management process includes:
- A defined update schedule tied to your PMCF evaluation report cadence
- A literature monitoring programme that flags new publications in real time
- A designated clinical evaluation owner with clear accountability
- A documented trigger log that records when and why each CER update was initiated
- Version control and audit trail for all CER revisions
- Integration with your PMS plan so post-market signals automatically route to the CER owner
Regulatory bodies don’t just look at the content of your CER, they look at the version history. A CER that hasn’t been touched in three years raises immediate questions about whether your PMCF programme is functioning.
Summary: Your CER Update Checklist
Use this as a starting point for your CER lifecycle review:
- Has your PMCF evaluation report been completed? → Update required
- Has your device or its intended purpose changed? → Update required
- Have new relevant publications been identified in literature monitoring? → Review and likely update
- Have any adverse events or vigilance signals been reported? → Immediate review required
- Is it more than 12-24 months since your last CER update (depending on device class)? → Schedule update
- Has your Notified Body issued feedback on your CER or technical file? → Update required
How Qserve can Support Your Organization
If your organization is navigating CER development, remediation, or ongoing lifecycle management under MDR, our regulatory team is ready to help. Reach out to discuss how we can support your clinical evaluation strategy.
This was the last blog of our CEP/CER Support series. Read the previous blogs in the series:
Blog 2: CEP vs. CER: What’s the Real Difference?
Blog 3: Top 5 Notified Body Findings in CER Reviews