PMS vs PMCF: Why Confusing Them Costs You Months in Review

Written by HATEM RABEH, MD, MSc Ing

Your Clinical Evaluation Expert And Partner

in
S

The distinction between Post-Market Surveillance and Post-Market Clinical Follow-up is not semantic. It defines two separate systems with different purposes, different requirements, and different oversight structures. Yet manufacturers routinely conflate them, submitting PMS plans that mention clinical data without actual PMCF protocols, or PMCF reports that simply summarize complaint data.

Notified Bodies reject these submissions. Auditors flag them as major non-conformities. And the cost is not just delay. It is a fundamental gap in your clinical evidence strategy.

The Core Distinction

Post-Market Surveillance is a quality management obligation. It is defined in MDR Article 83 and applies to all medical devices. PMS is the system you establish to collect, record, and analyze data about your devices once they are on the market. It includes complaints, vigilance reports, trend analysis, field safety corrective actions, and general safety information.

PMCF is a clinical evaluation obligation. It is defined in MDR Article 61 and Annex XIV Part B. PMCF is the continuous process of updating clinical evaluation through the systematic gathering and analysis of clinical data from devices already placed on the market. It is not a passive surveillance system. It is an active, methodologically structured clinical investigation without an investigational purpose.

The confusion arises because both systems involve post-market data. But the nature of the data, the rigor of collection, and the regulatory purpose are completely different.

What PMS Actually Covers

Your PMS system is broader than clinical data. It includes:

Complaints and non-conformities. Field performance issues. Usability problems reported by users. Returns and exchanges. Market feedback from distributors and sales channels. Competitor intelligence. Regulatory intelligence from other markets.

This information feeds into your risk management file, your periodic safety update reports, and your trend analysis. It informs whether corrective actions are needed. It tells you if something is going wrong.

But most of this data is not clinical evidence. A complaint about packaging is PMS data. A return due to unclear instructions is PMS data. These do not belong in a clinical evaluation report.

Even when PMS captures clinical information, such as a serious adverse event, the way it is documented and analyzed is different from PMCF. A vigilance report describes an event and investigates root cause. A PMCF data point is part of a structured clinical dataset designed to answer a predefined clinical question.

What PMCF Actually Requires

PMCF is not surveillance. It is clinical investigation. The key word is methodological structure.

MDCG 2020-7 and MDCG 2020-8 make this clear. Your PMCF plan must define specific clinical objectives. These objectives come from gaps or uncertainties identified in your clinical evaluation. Your plan must describe methods for systematic data collection, acceptance criteria, statistical considerations, and timelines.

PMCF methods include:

PMCF studies. These are prospective, protocol-driven studies with defined endpoints, patient populations, and data collection procedures. They are not clinical investigations under MDR Article 62 because they involve CE-marked devices, but they require the same methodological rigor.

Registry data. When appropriately structured, registries can provide longitudinal clinical data on defined cohorts. But access to a registry is not a PMCF plan. You must define what data you will extract, how you will analyze it, and what clinical questions it will answer.

Systematic literature review updates. Your clinical evaluation is based on literature. PMCF includes updating that literature search systematically to identify new clinical evidence about your device or equivalent devices.

Surveys and questionnaires. When used correctly, these can generate clinical data on patient-reported outcomes, functional performance, or quality of life. But they must be methodologically sound, not informal feedback forms.

Where the Confusion Creates Risk

The overlap between PMS and PMCF exists in one specific area: clinical data that enters through PMS channels can inform PMCF analysis. But the reverse is not true. PMCF does not replace PMS.

For example, if a surgeon reports an adverse event through your complaint system, that event is recorded in PMS. If that event is clinically relevant to a safety question defined in your PMCF plan, the data may also be included in PMCF analysis. But the PMS system did not generate the data for PMCF purposes. It captured it as part of post-market monitoring.

The confusion becomes a deficiency when manufacturers assume that having a PMS system exempts them from PMCF activities. It does not. MDR Annex XIV Part B requires PMCF for all devices unless specifically justified otherwise.

If your clinical evaluation identifies residual uncertainties, you need PMCF. If your device relies on equivalence, you need PMCF to confirm continued equivalence. If your clinical data at the time of conformity assessment was limited, you need PMCF to address those limitations.

The Documentation Gap

Another place this confusion surfaces is in documentation. Manufacturers submit a combined PMS-PMCF plan. This almost never works.

A PMS plan is a quality document. It describes processes, responsibilities, data sources, and workflows. It belongs in your quality management system.

A PMCF plan is a clinical document. It describes clinical objectives, patient populations, endpoints, data collection methods, and statistical analysis. It belongs in your clinical evaluation documentation and technical file.

These are not the same document. Trying to combine them results in a PMS plan that lacks operational detail and a PMCF plan that lacks clinical rigor.

Similarly, the PMS report and PMCF evaluation report serve different regulatory purposes. The PMS report feeds into your PSUR and informs risk management. The PMCF evaluation report updates your clinical evaluation and informs benefit-risk reassessment.

Notified Bodies expect to see both. Auditors check both. If your PMCF evaluation report is just a summary of complaints and returns, you do not have PMCF. You have a subset of PMS data misclassified as clinical evidence.

How This Plays Out in Real Submissions

I have reviewed files where the PMCF plan consisted of a single sentence: “Clinical data will be collected as part of our PMS activities.” No objectives. No methods. No timelines. The manufacturer believed that because their PMS system included a checkbox for “clinical data,” they had fulfilled PMCF requirements.

The Notified Body issued a major non-conformity. The review cycle extended by four months while the manufacturer developed an actual PMCF plan with defined studies, registry participation, and literature review protocols.

In another case, a manufacturer submitted a PMCF evaluation report that was a repackaged complaint log. It listed adverse events, device returns, and user feedback. But there was no analysis against predefined clinical objectives. No comparison to clinical data from the pre-market phase. No reassessment of benefit-risk conclusions.

The auditor asked: “What clinical question does this data answer?” The manufacturer could not provide an answer. The data existed, but it was not being used for clinical evaluation. It was being used for quality monitoring.

The Strategic Implication

Understanding the difference between PMS and PMCF changes how you design your post-market strategy. You cannot treat PMCF as an afterthought or a compliance checkbox. It is a core part of maintaining conformity.

When you write your clinical evaluation, the gaps and uncertainties you identify directly inform your PMCF plan. If your clinical data shows short-term safety but lacks long-term performance data, your PMCF plan must address that gap. If your equivalence claim relies on similarity to a predicate device, your PMCF plan must monitor whether that equivalence holds over time.

This linkage is what reviewers check. They read your clinical evaluation, identify the limitations, and then look at your PMCF plan to see if those limitations are being addressed. If the plan is generic or disconnected from the evaluation, it signals that PMCF is not being used as intended.

PMS, on the other hand, is your operational backbone. It captures everything happening in the field. It alerts you to problems. It feeds risk management. But it does not replace the need for structured clinical evidence generation.

What Notified Bodies Expect to See

During technical documentation review, the Notified Body will assess both your PMS system and your PMCF plan. They expect to see:

A PMS plan that describes how you systematically collect, analyze, and act on post-market data. Clear roles and responsibilities. Defined data sources. Processes for trend analysis and corrective action.

A PMCF plan that defines clinical objectives based on your clinical evaluation. Specific methods for data collection. Timelines and milestones. Acceptance criteria for evaluating whether clinical performance remains acceptable.

A PMCF evaluation report that analyzes post-market clinical data against the objectives in your plan. Conclusions about benefit-risk. Updates to your clinical evaluation.

If these documents overlap in content, the Notified Body will question whether you understand the distinction. If your PMCF plan references your PMS plan without additional clinical methodology, you will receive a request for clarification or a non-conformity.

How to Structure Both Systems

Start by defining your PMS system according to MDR Article 83 and MDCG 2019-9. This system should capture all post-market data, not just clinical information. It should integrate with your risk management, vigilance, and quality management processes.

Then, based on your clinical evaluation, develop a PMCF plan according to MDR Annex XIV Part B and MDCG 2020-8. Identify the clinical questions that remain unanswered or uncertain. Define how you will generate post-market clinical evidence to address those questions.

Your PMCF plan may reference PMS data sources. For example, if you plan to analyze adverse events as part of PMCF, you will draw that data from your PMS system. But the PMCF plan must specify how that data will be analyzed clinically, not just recorded operationally.

The two systems feed each other but remain distinct. PMS alerts you to signals. PMCF investigates whether those signals have clinical significance. PMS tells you what is happening. PMCF tells you what it means for benefit-risk.

Final Thought

The distinction between PMS and PMCF is not bureaucratic. It reflects two different types of oversight: quality oversight and clinical oversight. Both are required under MDR. Both are assessed by Notified Bodies. And both must be maintained throughout the lifecycle of your device.

When manufacturers confuse them, it reveals a deeper issue: they are treating PMCF as a passive data collection activity rather than an active clinical evaluation process. That misunderstanding delays submissions, triggers non-conformities, and weakens the clinical evidence base that supports continued market access.

If your PMCF plan is a copy of your PMS plan with the word “clinical” added, you do not have PMCF. And that is a problem you will face in your next review.

Peace,
Hatem
Clinical Evaluation Expert for Medical Devices
Follow me for more insights and practical advice.