The PMCF Evaluation Report Is Supposed to Rewrite the CER, Not Sit Beside It

MDR Annex XIV, Part B does not end at the PMCF plan. Once post-market clinical follow-up data exists, the regulation requires a separate document — the PMCF evaluation report — that analyzes those findings against the clinical evaluation report's existing conclusions, not against a data-collection checklist. Manufacturers that have the plan under control often still produce an evaluation report that reads like a dataset description rather than a judgment on whether the device's benefit-risk conclusion still holds.

One provision, two different documents

The PMCF plan and the PMCF evaluation report both live under Annex XIV, Part B, and the two get treated as a single workstream more often than the regulation intends. The plan is prospective: it sets objectives, methods, and a data-collection design before any PMCF data exists. The evaluation report is retrospective and analytical: once that data has been collected, Part B expects a document that tests it against what the clinical evaluation report already concludes about the device's safety, performance, and benefit-risk balance — not a narrative of what the registry or survey turned up.

Where the connection to the CER gets lost

The failure mode is rarely a missing report. It is a report that exists, is technically complete, and never changes anything. Clinical affairs teams under deadline pressure for the annual update write toward the PSUR renewal date rather than toward the CER's open questions, and the result is a document that restates what PMCF activity occurred without stating what it proves or disproves about the CER's standing conclusions.

• Data recap, no comparison. The report lists registry enrollment and survey results without stating whether each finding confirms, weakens, or contradicts a specific CER conclusion.
• Residual risks never revisited. The CER's risk file names specific open questions, and the evaluation report does not say whether PMCF data answered any of them.
• No link forward to the PSUR or SSCP. The evaluation report's conclusions should carry directly into the PSUR's safety and performance assessment, not require a separate summarization pass.
• The annual deadline drives the content. Written to close out the PSUR cycle on schedule rather than because the CER's conclusions needed re-testing against new data.

A PMCF evaluation report that does not change a sentence in the CER has not done its job, whatever its page count says. Why the evaluation report has to feed back, not just file

Building the report backward from the CER

The fix mirrors the discipline the PMCF plan already needs: start from the CER's stated conclusions, not from the PMCF template's section headings. Pull the specific residual risks and open questions the clinical evaluation already names, and structure the evaluation report's analysis around whether each one is now confirmed, newly uncertain, or contradicted by what PMCF collected. That structure also makes the post-market surveillance system's feedback loop visible to a notified body reviewer in one pass, instead of asking them to cross-reference a data appendix against a CER written on a different timeline.

None of this adds PMCF activity — it asks for the analysis the regulation already expects from the data a manufacturer is already collecting. A short evaluation report that names which CER conclusions moved is a stronger file than a long one that never says. Manufacturers who treat the evaluation report as the CER's update mechanism, rather than as an annual PSUR attachment, are the ones whose clinical evidence file stays current instead of drifting from what their post-market data actually shows.