When is a PMCF plan required under EU MDR, and what has to go in a PSUR?

Under EU MDR Annex XIV Part B, a PMCF plan belongs to the post-market surveillance system unless omission is justified. Article 86 PSURs update at least every two years for Class IIa, annually for Class IIb and Class III.

Clinical evidence under Regulation (EU) 2017/745 does not stop at CE marking. The clinical evaluation report fixes what is known at conformity assessment; post-market surveillance keeps that position current while the device is on the market. Article 83 builds the system, Article 84 plans it, Annex XIV Part B generates the clinical data, Articles 85 and 86 report it. Reviewers read these as one loop.

The PMS system under Article 83 and the PMS plan under Article 84

Article 83 requires a manufacturer to establish a post-market surveillance system, proportionate to risk class and device type, that continuously checks development-phase results against real-world data on safety and performance. The obligation is system-level: it is not discharged by one report at the end of a period, and the system must be documented as running.

Article 84 requires that system to be based on a PMS plan defining what data is needed, how it is collected and how it is assessed, across several downstream functions: updating the risk management file and design and manufacturing information, feeding the clinical evaluation, and detecting trends. The PMS plan is the parent document; the PMCF plan sits inside it as the clinical data-generation component.

What Annex XIV Part B requires a PMCF plan to do

Annex XIV Part B places PMCF inside the PMS system and specifies what the plan's methods must achieve:

The Annex separates two method families. General procedures cover collection of clinical experience, user feedback, and screening of scientific literature. Specific methods cover activities such as registry evaluation and dedicated PMCF studies. Both require a detailed justification of adequacy and a time schedule.

The load-bearing word is justification. A plan listing a literature screen and a complaint review, without explaining why those mechanisms catch emergent risks and off-label use for this device and population, has stated activities rather than justified a method.

If you intend not to run PMCF activities

Where a manufacturer takes the position that PMCF activities are not needed, that position has to be reasoned in the documentation rather than asserted. The exact wording of the justification requirement should be confirmed against the current Annex XIV Part B text; the framing here follows the structure of that Annex and is otherwise unverified. A defensible justification walks through the same six aims and shows, for each, why existing pre-market evidence, complaint handling, vigilance trending and literature screening already satisfy it.

PMCF plan and PMCF evaluation report: the MDCG templates

MDCG 2020-7 provides a PMCF plan template covering safety confirmation, side-effect identification, emerging risk analysis, benefit-risk verification and misuse detection, with justification requirements for study design and timelines. MDCG 2020-8 provides the PMCF evaluation report template: manufacturer details, device description, results of the activities performed, evaluation of the clinical data obtained, and conclusions including preventive or corrective measures.

The plan is forward-looking; the evaluation report is backward-looking. What matters is what happens after the evaluation report is signed: its conclusions return to the clinical evaluation report. PMCF exists to update the clinical evaluation with real-world confirmation, or contradiction, of what was claimed at CE marking. A report that has not absorbed the latest PMCF findings has detached from post-market experience, and the document dates show it.

PSUR periodicity under Article 86

Article 86 sets the Periodic Safety Update Report and its update frequency by risk class:

Two scope limits. Whether "at least every two years" for Class IIa runs on calendar or rolling years is not settled by the wording relied on here, so treat any reading as unverified. And the itemised PSUR content list is not restated here, because only the periodicity above is confirmed by the sources behind this page; draft content from the Article text itself.

The PMS report under Article 85 for lower-class devices

Article 85 covers the equivalent reporting obligation for Class I and Class II devices, under which manufacturers prepare a Post-Market Surveillance Report. Its update interval is not confirmed by the sources behind this page and is left unstated rather than guessed; verify it against the current Article 85 text before fixing a reporting cycle.

Class III and implantable devices: the SSCP under Article 32

For implantable and Class III devices, Article 32 adds a Summary of Safety and Clinical Performance written for end users: healthcare professionals and, where applicable, patients. It must give a balanced summary of both favourable and unfavourable safety and clinical effectiveness data, including residual risks and mitigation, and it goes to a notified body for validation before publication in EUDAMED. MDCG 2019-9 Rev.1 sets a mandatory eight-section structure, from device identification and intended use through to user training and standards. Because it is published, language overstating performance is exposed there first.

How the documents chain together

  1. Clinical evaluation report establishes the baseline clinical evidence and benefit-risk conclusion at CE marking (Article 61, Annex XIV Part A).
  2. PMCF plan defines how that conclusion is confirmed or challenged with real-world data (Annex XIV Part B; MDCG 2020-7).
  3. PMCF evaluation report documents what the activities found and what measures they trigger (MDCG 2020-8).
  4. PSUR (Article 86) or PMS report (Article 85) consolidates PMCF findings with complaint, vigilance and trend data.
  5. Updated clinical evaluation report absorbs those conclusions and becomes the next baseline; for implantable and Class III devices the SSCP is refreshed in step.

A break anywhere in that chain is what a reviewer looks for: a PMCF evaluation report whose findings never appear in the clinical evaluation report, or a PSUR repeating the previous period's conclusions without engaging new PMCF data.

Device class, document and frequency at a glance

Device classPost-market documentUpdate frequency
Class I and Class II (general)Post-Market Surveillance Report (Article 85)Not confirmed here; verify against current Article 85 text
Class IIaPSUR (Article 86)At least every two years, and when necessary
Class IIbPSUR (Article 86)At least annually
Class IIIPSUR (Article 86), submitted via EUDAMED to the notified bodyAt least annually
Implantable and Class IIISSCP (Article 32), published in EUDAMEDKept in step with the clinical evaluation

Which MDCG guidance applies to which step

GuidanceSubjectWhere it bites
MDCG 2020-1Clinical evaluation of medical device softwareValid clinical association; technical, analytical and clinical performance
MDCG 2020-5EquivalenceThree-pillar demonstration; cumulative effect and gap analysis
MDCG 2020-6Legacy devices under 93/42/EEC or 90/385/EECSufficient clinical evidence; evidence hierarchy
MDCG 2020-7PMCF plan templateMethod justification and time schedule
MDCG 2020-8PMCF evaluation report templateResults and preventive or corrective measures
MDCG 2020-13Clinical Evaluation Assessment ReportHow a notified body records assessment conclusions
MDCG 2019-9 Rev.1SSCPEight-section structure; audience-specific presentation

MDCG 2020-13 is a July 2020 publication; whether it remains the current template is unverified here, and MDCG 2023-7 on Article 61 should be checked alongside it.

Recurring deficiencies that surface at the PMCF stage

Deficiencies on clinical evaluation and PMCF documentation cluster into recurring patterns:

Most originate upstream. An unjustified PMCF position on top of an unquantified benefit-risk conclusion compounds the problem: the reviewer has neither a baseline nor a mechanism for closing it.

Where Clinoble fits

Clinoble Innovations Private Limited is based in Hyderabad, Telangana, India. Founder and director: Dr. Jaideep Rao M., MBBS, MD Community Medicine. Two Indian patent applications are pending in quantitative clinical imaging, IND 202641088451 and IND 202641090786.

Clinoble works on the clinical evidence half of this chain: structuring a clinical evaluation plan against Annex XIV Part A, running a prespecified and reproducible literature search to establish state of the art, and setting out how PMCF findings route back into the clinical evaluation report. Details are on the clinical evaluation services page. Its own products, including CardioPulmo and TB F.I.R.S.T, are built as screening aids and triage support for clinicians, not as instruments that determine a diagnosis.

This page is background reading, not legal or regulatory advice. Confirm every requirement above against the current text of Regulation (EU) 2017/745 and the MDCG guidance applicable to your device class.

Working through a PMCF justification, or routing PMCF findings back into a clinical evaluation report?