Short answer

Under the EU MDR, post-market surveillance for SaMD is built on named documents: a PMS plan (Annex III) that includes a PMCF plan or a justification why PMCF is not applicable, and a PSUR for class IIa and above or a PMS report for class I. Class IIa SaMD updates the PSUR when necessary and at least every two years; class IIb and III at least annually (Article 86). For software, frequent releases and usage data make PMS a continuous process that feeds the clinical evaluation and the risk file. In surveillance audits, Notified Bodies check that the plan is actually executed, complaints are classified, vigilance is handled and findings lead to updates.

Why post-market surveillance matters more under EU MDR

Under the MDD, post-market surveillance was required as a systematic procedure, but the Directive said little about how it should be documented. In practice, many companies maintained minimal PMS systems — a complaint log, an annual literature search, and a brief summary. EU MDR changed this. Articles 83–86 and Annexes III and XIV introduce specific, named post-market documents with defined content requirements, minimum update frequencies, and a direct link to the clinical evaluation, which must be kept up to date throughout the device's lifetime.

For SaMD specifically, post-market surveillance has a dimension that hardware devices do not: the product is continuously updated, and each update creates a data point relevant to real-world performance. A SaMD company with an active user base can have a large amount of post-market performance data available — but only if the PMS system is designed to capture it.

A frequent post-certification audit finding: In our experience, NBs regularly cite PMS systems that exist on paper but have not generated actual data. A PMS plan that describes data collection methods but shows no collected data, no complaint trend analysis, and no PSUR prepared on schedule tends to be treated as evidence that the PMS system is not functioning — regardless of whether the device has performed safely in the market.

The four documents: what they are and how they connect

For Class IIa, IIb and III devices, EU MDR creates four distinct but interconnected post-market documents. They are not interchangeable, and the failure to understand the difference between them is itself a common audit finding. For Class I software (no Notified Body involvement), a post-market surveillance report under Article 85 takes the place of the PSUR: it summarises the results and conclusions of the PMS data analysis, with a rationale and description of any preventive and corrective actions, is updated when necessary, and is made available to the competent authority on request.

EU MDR Article 84 · Annex III
PMS Plan
The master plan for all post-market data collection. Defines data sources, collection methods, analysis approach, and indicators and threshold values that would trigger action. Part of the technical documentation, so it must be in place before market entry.
Kept up to date throughout the lifetime
EU MDR Article 86 · Annex III
PSUR
Periodic Safety Update Report. Synthesises the PMS findings into a benefit-risk conclusion. Class IIb and III: at least annually. Class IIa: when necessary and at least every two years. Integrates complaint trends, vigilance events, PMCF findings, and sales and usage data.
IIb/III annually · IIa every 2 years
EU MDR Annex XIV Part B
PMCF Plan
Post-Market Clinical Follow-up Plan. Defines systematic clinical data collection activities — literature surveillance, studies, registries, surveys, real-world data analysis. Part of the PMS plan for every device, unless the PMS plan justifies why PMCF is not applicable.
Updated per PMCF cycle
EU MDR Annex XIV Part B
PMCF Report
The PMCF evaluation report documents findings from PMCF activities conducted per the PMCF Plan. It is part of the CER and the technical documentation. If findings reveal new risks or performance variation, CER and risk file must be updated.
Per PMCF Plan · at least annually for Class III
The hierarchy: The PMS Plan is the umbrella. The PMCF Plan sits inside it as the clinical data collection component. The PSUR integrates outputs from both, plus complaint data and vigilance information, into a periodic benefit-risk conclusion. The PMCF Report documents what PMCF activities actually found. The CER is updated using PMCF Report findings. Each document feeds the next in a continuous loop.

What each document must contain for SaMD

PMS Plan

The PMS Plan must specify proactive and reactive data collection methods. For SaMD, this typically includes: complaint handling and trend analysis (classification, severity, frequency thresholds triggering escalation); serious incident and field safety corrective action reporting (Article 87) and trend reporting (Article 88); post-market literature surveillance covering the clinical domain and comparable devices; PMCF activities as specified in the PMCF Plan; and data from user feedback channels. Critically, Annex III requires the plan to define suitable indicators and threshold values — specific criteria that, when met, trigger a defined response (design change, field safety notice, NB notification, CER update). A PMS Plan without thresholds is a data collection plan, not a surveillance plan.

PSUR (Class IIa, IIb and III)

Article 86 sets the cadence: Class IIb and III devices update the PSUR at least annually; Class IIa devices update it when necessary and at least every two years. MDCG 2022-21 recommends that the data collection period starts on the MDR certification date, so for a Class IIa SaMD the first PSUR covers the first two years after certification (one year for Class IIb or III).

The PSUR summarises the results and conclusions of the analysis of PMS data, with a rationale and description of any preventive and corrective actions taken. Article 86 requires it to include the conclusions of the benefit-risk determination (the actual analysis, not just a statement that the benefit-risk is acceptable), the main findings of the PMCF, and the volume of sales together with an estimate of the size and characteristics of the user population and, where practicable, the usage frequency. In practice it also covers complaint trends, vigilance events and literature findings. For Class IIa and IIb devices, the PSUR is not submitted through EUDAMED: you make it available to your Notified Body and, on request, to competent authorities. For Class III devices, it is submitted to the NB through EUDAMED, and the NB adds its evaluation; until that EUDAMED functionality is mandatory, MDCG 2022-21 asks manufacturers to deliver it to the NB by appropriate means. If the PSUR identifies a new risk or a change in the benefit-risk profile, update the risk management file and the CER, and assess any resulting device change under your change control — including whether the NB must be informed before it is implemented.

PMCF Plan

The PMCF Plan for SaMD should specify: the specific clinical questions or evidence gaps it is designed to address (taken directly from the conclusions of your clinical evaluation report); the data collection methods to be used and why they are appropriate; timelines and responsible parties for each activity; acceptance criteria that would confirm or refute the clinical hypotheses; and what will happen when the PMCF Report is completed (how findings feed back into the CER). For software, PMCF activities often include systematic literature surveillance (most efficient for SaMD teams with limited field study capacity), analysis of usage logs linked to clinical outcomes, and structured user feedback with clinical performance dimensions.

PMCF Report

The PMCF Report — called the PMCF evaluation report in Annex XIV Part B — documents what was actually done per the PMCF Plan and what was found. It is part of the clinical evaluation report; for Class III devices, Article 61(11) requires it to be updated at least annually. It must conclude whether the PMCF findings confirm the clinical evaluation's benefit-risk analysis or whether a CER update is required. If findings reveal unexpected adverse effects, performance variation across patient subgroups, or new evidence about the clinical domain, the PMCF Report triggers a CER revision — and any resulting change to the device or its intended purpose has to be assessed under your change control, including whether the NB must be informed.

The post-market lifecycle timeline for Class IIa SaMD

Certification (Month 0)
PMS Plan and PMCF Plan (or a justification why PMCF is not applicable) already in place as part of technical file. Complaint handling system live. Literature surveillance scheduled. The PSUR data collection period starts on the certification date.
Months 1–12
PMS data collection ongoing: complaints logged and classified, literature surveillance executed, PMCF activities underway. Each software release reviewed for change control significance.
Within 12 months
NB surveillance audit. Under Annex IX, the NB audits and assesses at least once every 12 months that you apply the approved QMS and the PMS plan. It checks complaint records, PMCF activities against the Plan, vigilance reporting, and whether PMS findings triggered any required QMS or design changes.
Month 24
First PSUR due (Class IIa). Synthesise all PMS data collected over the two years. Update benefit-risk analysis. Prepare the PMCF evaluation report as scheduled in the PMCF Plan. Update CER if findings require it. Make the PSUR available to your NB. (Class IIb or III software: first PSUR at month 12, then annually.)
Year 3 onward
PSUR updated at least every two years (and whenever necessary). NB surveillance audits continue at least every 12 months. PMCF Plan reviewed and updated. CER updated with PMCF and PMS data as defined in your plans. PMS Plan updated if device, indication, or user base changes materially.

Connecting PMS to real-world SaMD operations

For SaMD teams, the practical challenge is that post-market regulatory obligations run in parallel with normal product development. The same engineering team managing sprint cycles and software releases is also the source of post-market performance data. Designing the PMS system to capture this data without creating separate manual processes is both possible and important.

Specifically for SaMD, operational data that can serve PMS purposes includes: support ticket classification by symptom type and clinical impact severity; error rate telemetry on algorithm outputs where clinical impact can be assessed; user-reported discrepancies between algorithm output and clinical judgement; and usage patterns that indicate the device is being used outside its validated intended use. None of this requires building a separate regulatory data collection process — it requires designing the existing operational systems to retain and classify data in a way that feeds PMS analysis.

The PMS–QMS loop: EU MDR Article 83 makes the PMS system part of the QMS and requires PMS data to be used to update the benefit-risk determination and the risk management process, the design and manufacturing information, the instructions for use and labelling, and the clinical evaluation, and to identify preventive and corrective actions. If complaint analysis identifies a new use-related hazard, the risk file must be updated. If PMCF findings reveal a performance issue in a patient subgroup, the CER and potentially the technical file must be updated. The PMS system is not a documentation exercise — it is the mechanism by which real-world data maintains the accuracy of your certified technical file over time.

What NBs look for in PMS surveillance audits

Based on NB audit experience, the most frequently cited PMS deficiencies for SaMD under EU MDR are:

  • PSUR not produced on schedule: In our experience one of the most frequent findings. The PSUR cadence is a legal requirement (Class IIb and III at least annually, Class IIa at least every two years), and missing or late PSURs can be graded as major non-conformities.
  • PMS Plan not being executed: Literature surveillance described in the Plan but not performed; PMCF activities listed but no evidence of execution; complaint thresholds defined but no evidence of threshold monitoring.
  • Complaint data not classified by clinical severity: Logging all complaints as equivalent regardless of whether they relate to minor UI issues or potential clinical impact misses the purpose of complaint trend analysis.
  • PMCF Plan and CER not connected: PMCF activities that do not address the specific evidence gaps identified in the CER do not satisfy the PMCF requirement, regardless of how much data they collect.
  • PMS findings not feeding back into the QMS or risk file: A complaint analysis that concludes "no action required" every cycle — without documented analysis of whether risk controls remain adequate — is treated as evidence of a non-functioning PMS system.

If you do not have a quality and regulatory lead in-house to run this cycle after launch, part-time QA/RA support can keep PSURs, PMCF activities and audit preparation on schedule.

Official sources & references