PMCF Plan and Evaluation Report: What MDR Requires and How to Deliver It

Post-Market Clinical Follow-up is one of the areas where MDR genuinely raised the stakes compared to MDD. Under MDD, PMCF existed on paper for most devices but was rarely implemented with any rigour. Under MDR, Notified Bodies are checking whether PMCF plans describe real activities — not just a commitment to "monitor literature and complaints." If your PMCF plan reads like a placeholder, it will be flagged.

What PMCF actually is

PMCF is a sub-part of your post-market surveillance system specifically focused on gathering clinical data after your device is on the market. The purpose is to proactively confirm that your device continues to perform as claimed under real-world conditions, detect emerging risks or trends early, and provide the clinical data needed to keep your Clinical Evaluation Report current.

The key word is proactive. PMCF is not the same as reactive surveillance (waiting for complaints or adverse events and then investigating). PMCF means actively going out to collect clinical data — through surveys, registries, follow-up studies, or analysis of real-world data. Annex XIV Part B of MDR defines the framework; MDCG 2020-7 and MDCG 2020-8 provide the implementation guidance.

What the PMCF Plan needs to contain

Annex XIV Part B lists the required elements. In practice, your PMCF plan should address:

Objectives — What specific clinical questions is your PMCF trying to answer? "Monitor device performance" is not an objective. "Confirm the long-term implant stability rate in the primary patient population over 5 years" is an objective. Be specific about what you're measuring and why.

Methods — What activities will you run? Options include: patient registries, user surveys (post-implant questionnaires, for example), follow-up studies (observational or interventional), published literature surveillance specifically on your device (not just the technology class), and real-world data analysis from hospital systems or claims data where accessible.

Rationale for the methods chosen — This is where a lot of PMCF plans fall short. You have to justify why the chosen methods are adequate to meet the objectives. If you're only planning a literature review, you need to explain why that's sufficient for your device and risk class. For Class III and implantables, literature surveillance alone is rarely considered adequate.

Timelines — When will each activity be initiated, what are the interim milestones, and when will data be available for the evaluation report?

Reference to the CER — The PMCF Plan should cross-reference the open questions or data gaps identified in the CER. PMCF activities should be designed to address those gaps.

The PMCF Evaluation Report

The PMCF Evaluation Report is not the same as the CER. It is a separate document that records what your PMCF activities produced — what data was collected, what conclusions were drawn, and whether those conclusions require the CER to be updated.

Annex XIV Part B is explicit: the PMCF Evaluation Report must be part of the technical documentation, and it must feed into the CER update process. If your PMCF Evaluation Report concludes that new data confirms existing conclusions, you document that and note no CER update is triggered. If the new data changes the benefit-risk picture, you update the CER.

The PMCF Evaluation Report also feeds into your Periodic Safety Update Report (PSUR) — this is the document linkage chain that many teams only discover during their first surveillance audit.

Update frequency and timing

The update frequency for PMCF activities depends on your device risk class:

• Class IIa and IIb: PMCF Evaluation Report at least every two years (with the PSUR)
• Class III and implantable devices: PMCF Evaluation Report annually

These timelines align with the PSUR cadence because the two documents are connected. If your PSUR is due and your PMCF Evaluation Report hasn't been updated, your PSUR will be incomplete.

Where teams get into trouble

The most common PMCF failure modes at Notified Body audit are:

• A PMCF Plan that lists only literature surveillance as the method, without justification of adequacy
• PMCF activities described vaguely with no timelines or ownership
• PMCF Evaluation Reports produced on schedule but disconnected from the CER — no feedback loop
• PMCF data that reveals a trend (increased complaint rate, emerging failure mode) that was not fed back into the CER

The second one often comes down to internal process, not regulatory knowledge: PMCF is owned by regulatory, PMS is owned by quality, and nobody has assigned someone to make sure the two talk to each other. Getting that coordination in place before your first surveillance audit saves significant pain.

PMCF for devices with limited market data

For newly introduced devices, the challenge is that PMCF can't produce meaningful data until the device is actually in use at scale. In this situation, the PMCF Plan should acknowledge the current data limitations, describe how data collection will be ramped up as the device reaches more sites, and be specific about what early indicators will be monitored in the interim. Notified Bodies understand this situation — they just want to see a credible plan, not a blank page.