EU MDR treats clinical evaluation as a lifecycle activity, not a one-time document. Article 61 and Annex XIV Part A require that post-market clinical follow-up data continuously informs the clinical evaluation — and that the CER is updated accordingly. In practice, many technical files contain up-to-date PMS and PMCF documents that are not reflected in the CER. This disconnect is one of the most commonly flagged inconsistencies in Notified Body reviews.
The regulatory basis for the feedback loop
Annex XIV Part A of EU MDR requires that PMCF is used to confirm the continuing acceptability of the benefit-risk ratio identified in the clinical evaluation. The PMCF Evaluation Report — the output of each PMCF cycle — must feed back into the CER. A CER that acknowledges the existence of a PMCF programme but does not reflect its findings in the benefit-risk analysis or clinical data section is not fulfilling this requirement.
Similarly, the Post-Market Surveillance Report (or PSUR for Class IIa and above) summarises complaint data, vigilance reports, post-market literature, and PMCF outputs. This summary should be visible in the CER's state-of-the-art and clinical data sections.
What data to pull from PMS and PMCF
The specific data that belongs in the CER depends on what your PMS and PMCF activities have generated. Common inputs include:
- Complaint and adverse event rates — comparison of observed rates against the residual risks identified in the risk management file
- PMCF survey or registry findings — device performance data from real-world use
- Post-market literature updates — new publications affecting the state of the art or device-specific evidence base
- Vigilance data — serious incidents and field safety corrective actions, if any
- Competitor or equivalent device updates — changes in the market that affect SOTA conclusions
Where post-market data belongs in the CER
Post-market data typically feeds into three sections of the CER:
- State-of-the-art section — updated literature and knowledge about the device category
- Clinical data section — PMCF findings, real-world performance data, post-market clinical study results where applicable
- Benefit-risk section — updated analysis of whether the benefit-risk balance still holds in light of the post-market evidence
The benefit-risk section is where the connection is most often missing. A common pattern is a benefit-risk analysis that was written at initial MDR submission and has not been updated to reflect subsequent PMCF or PMS findings. Even if the conclusions have not changed, the analysis should explicitly reference the post-market evidence that supports the continuing conclusion.
Timing the update cycle
The PSUR and PMCF Evaluation Report should trigger a CER review. In most cases, this means an annual cycle for Class IIb and III devices, and a cycle aligned with the PSUR frequency for Class IIa. The review should assess whether the new post-market data materially affects any of the CER's conclusions — if it does, the CER should be updated before the next annual review or Notified Body audit.
Building this into a documentation schedule — rather than treating CER updates as reactive — is the most efficient way to maintain compliance across the technical file. Teams that update the CER only in response to Notified Body comments are usually doing more work than teams that maintain a structured update cycle.
Making the connection explicit
When integrating post-market data into a CER update, the clearest approach is to reference the source document explicitly — "as documented in the PMCF Evaluation Report dated [date]" — rather than restating findings without attribution. This gives reviewers a clear trail between the CER conclusions and the post-market evidence that supports them, and it makes the document easier to maintain in subsequent update cycles.