Why your PMCF plan keeps getting rejected

Written by HATEM RABEH, MD, MSc Ing

Your Clinical Evaluation Expert And Partner

in
S

Under MDR Article 61 and Annex XIV Part B, manufacturers must establish a Post-Market Clinical Follow-up plan as part of their ongoing clinical evaluation. This is not optional. It applies to all device classes unless you can justify an exception. Most manufacturers understand the requirement. What they struggle with is building a PMCF plan that demonstrates regulatory maturity.

A PMCF plan that works is not a research protocol. It is a strategic document that shows how you will continuously verify the safety and performance of your device once it is on the market. Reviewers and Notified Bodies assess whether your plan addresses the actual gaps in your clinical data, whether your methods are appropriate for your device type, and whether you have the systems in place to execute what you promise.

When a PMCF plan gets rejected, it is usually because the structure does not support the logic. The manufacturer lists activities but does not explain why those activities are necessary. The plan describes methods but does not connect them to specific residual risks or performance questions. The document exists to satisfy a checklist, not to demonstrate control.

What MDR and MDCG Guidance Require

The regulatory foundation for PMCF is clear. MDR Article 61 requires manufacturers to proactively collect and evaluate clinical data from the use of their devices. Annex XIV Part B specifies that the PMCF plan must be part of the clinical evaluation plan and updated throughout the device lifecycle.

MDCG 2020-7 and MDCG 2020-8 provide practical guidance on PMCF methods and planning. These documents explain that PMCF serves two purposes: to confirm the safety and performance of the device in routine use, and to identify emerging risks or side effects. The plan must show how you will achieve both.

The expectation is that your PMCF plan reflects your clinical evaluation conclusions. If your CER identified data gaps or uncertainties, your PMCF plan must explain how you will address them. If your device has residual risks, your PMCF plan must include surveillance methods that detect related adverse events. If you claimed equivalence, your PMCF plan must monitor whether performance in your population matches the equivalent device data.

The Core Structure That Works

A PMCF plan that passes review has a clear structure. It starts with the clinical context, defines specific objectives, describes methods that match those objectives, and outlines how data will be analyzed and fed back into the clinical evaluation and risk management.

Here is the structure I use and recommend:

1. Device Description and Intended Use

This section anchors the plan. Include the device name, classification, intended purpose, target population, and any relevant design or material characteristics. The description should match what is in your CER and technical documentation. Consistency across documents signals control.

Do not write a marketing summary. Write a technical description that allows a reviewer to understand what the device does and who will use it.

2. Clinical Evaluation Summary and Identified Gaps

This is where most plans fail. Manufacturers write a generic summary of their clinical evaluation without identifying specific gaps or uncertainties. The reviewer is left guessing why PMCF is needed.

Instead, state explicitly what is not yet fully known. Are there questions about long-term performance? Are there subpopulations with limited data? Are there residual risks that require monitoring? Are there claims that need real-world confirmation?

Each gap you identify here should connect directly to an objective in the next section.