MDR PMCF: The Objectives Have to Trace to a Named Gap — Not Restate the Regulation

Post-market clinical follow-up has been governed by MDR Annex XIV, Part B since the Medical Device Regulation began applying, and the European Commission's MDCG 2020-7 template has walked manufacturers through the plan's sections since September 2020. Neither shortage of guidance is the reason PMCF plans keep coming back with findings on EU MDR technical documentation. The reason is simpler: most objectives describe what PMCF is for in general, when a Notified Body is checking whether each objective closes a specific gap this device's own clinical evaluation already admitted to having.

What Annex XIV, Part B actually asks for

Section 6.1 gives PMCF five objectives: confirm the device's safety and performance, including clinical benefit where applicable, throughout its expected lifetime; identify previously unknown side effects and monitor known ones and contraindications; identify and analyze emergent risks on the basis of factual evidence; confirm the benefit-risk ratio referred to in Annex I remains acceptable; and detect possible systematic misuse or off-label use. Those five purposes are categories, not content. A PMCF plan that lists them as its objectives has described the regulation, not the device. The plan a Notified Body is actually reviewing has to answer a narrower question for each objective: which specific residual risk, open question, or evidence gap from this device's own clinical evaluation report does this activity close, and how.

Where generic objectives come from

The pattern is not carelessness. It is sequencing. A PMCF plan drafted from the MDCG 2020-7 template's section headings, before the clinical evaluation report's gap analysis is finished, has nothing device-specific to reference yet — so its objectives default to paraphrasing Annex XIV, Part B itself. By the time the CER identifies its actual residual risks and open questions, the PMCF plan has already been written, and updating it becomes a copy-edit instead of a rebuild. The plan and the report describe the same device without describing the same gaps.

• Generic objective, no finding basis. "Confirm continued safety and performance" restates Section 6.1 without saying which residual risk or open question makes that confirmation necessary for this device.
• Traceable objective. "Confirm the long-term wear-related failure rate does not exceed the residual risk accepted in RMF Section X, identified as a data gap in CER Section Y" names the source, the risk, and the activity in one line.
• Study design divorced from the risk. A registry or survey sized by convention rather than by the statistical power needed to detect the specific residual risk the objective claims to be watching for.
• A blanket "not applicable." A one-line waiver that does not address why existing clinical evidence and ongoing post-market surveillance already cover the device's residual risks — the justification Annex III actually requires in place of a PMCF plan.

A PMCF objective that could be pasted into any device's plan unchanged has told a reviewer nothing about this device. The ones that survive review are the ones that could only belong to the file they're in. Why traceability, not template completion, is the standard

Where PMCF meets the equivalence route and PMS

PMCF is not a standalone document; it is the clinical arm of the broader post-market surveillance system Annex III requires, and its inputs come directly from the clinical evaluation. That connection matters most for devices relying on the equivalence route: a CER built on another manufacturer's clinical data, rather than the device's own, generally carries more open questions about how that equivalence holds up in real-world use — which is exactly the kind of gap a PMCF objective should be built to close, and exactly the kind of gap a generic objective quietly ignores. A manufacturer that treats equivalence as closing the clinical-evidence question, rather than as one input a PMCF plan still has to account for, is building the same disconnect the Notified Body is trained to find.

None of this asks for more PMCF activity — it asks for a plan that can be read backward to the clinical evaluation it came from. A five-line objectives section that names its gaps is a stronger file than a twelve-line section that paraphrases the regulation. Manufacturers that finish the CER's gap analysis before drafting PMCF objectives get a plan a reviewer can trace in one pass. Manufacturers that draft the plan from the template's headings get a plan that reads correctly and still draws a finding, because correct and traceable are not the same thing.