This guide covers what a compliant PMS system looks like, what documents you need to produce for each device class, what data sources MDR expects you to use, and how to build a program that functions as a real quality system — not just paperwork.

What EU MDR requires for post-market surveillance

EU MDR Articles 83 through 86 form the legal framework for post-market surveillance. Each article covers a distinct element:

• Article 83 defines the manufacturer’s obligation to plan, establish, document, implement, maintain, and update a post-market surveillance system for each device
• Article 84 specifies what a Post-Market Surveillance Plan (PMSP) must contain
• Article 85 requires a Post-Market Surveillance Report (PMSR) for Class I devices
• Article 86 requires a Periodic Safety Update Report (PSUR) for Class IIa, IIb, and III devices

The European Commission’s Medical Device Coordination Group published MDCG 2025-10 guidance providing updated interpretation of these PMS requirements, reflecting findings from notified body audits across the EU. The guidance confirms that PMS must be a living, data-driven process — not a static document produced at certification time.

PMS plan vs PMS report vs PSUR: what each document is

Many quality teams conflate these documents. They serve different purposes and have different update frequencies.

Post-Market Surveillance Plan (PMSP)

The PMSP, required under Article 84, describes how you will collect and analyze post-market data for a specific device. It must cover:

• The proactive and reactive data collection methods you will use
• Performance indicators and thresholds that would trigger action
• Reference to applicable standards and guidance documents
• Specific timelines for data collection and review activities
• How findings will feed back into your risk register, clinical evaluation, and technical documentation

The PMSP is part of your technical documentation and must be device-specific. A single generic PMSP for all products does not satisfy MDR.

Post-Market Surveillance Report (PMSR) — Class I devices

For Class I devices, Article 85 requires a PMSR that summarizes the results of your PMS activities, states whether corrective or preventive measures are needed, and confirms the benefit-risk determination remains favorable. There is no mandatory update frequency stated in Article 85 — the PMSR is updated when significant changes occur or when new information from PMS activities warrants it. Notified bodies have generally interpreted “when needed” to mean at least every two to three years.

Periodic Safety Update Report (PSUR) — Class IIa, IIb, and III

The PSUR under Article 86 has defined update requirements. Class IIa devices: PSUR updated at minimum every two years. Class IIb and III devices: PSUR updated annually. For Class III and implantable Class IIb devices, the PSUR is submitted to the notified body and assessed as part of the conformity assessment process.

The PSUR must include: a summary of PMS data, conclusions of benefit-risk analysis, a summary of any FSCA/field safety corrective actions taken, results of post-market clinical follow-up (PMCF) if applicable, and proposed corrective and preventive actions.

Data sources your PMS system must use

Article 83 MDR specifies that the PMS system must gather, record, and analyze relevant data from the post-production phase. Article 84(a) provides a list of data sources. Your PMSP should address each of these explicitly:

Complaints and feedback

Your complaint handling process feeds directly into PMS. Every complaint, whether from users, patients, healthcare professionals, or distributors, is post-market data. The PMS system should analyze complaint trends — not just individual incidents — to identify signals that may not be visible at the single-event level.

Vigilance and serious incident reporting

Serious incidents and field safety corrective actions (FSCAs) reported under MDR Article 87 are both inputs to your PMS system and outputs from it. If your PMS data analysis identifies a pattern that meets the serious incident threshold, that triggers the vigilance reporting obligation. The two systems are connected.

Literature surveillance

Article 84(d) requires manufacturers to monitor scientific and technical publications relevant to their device, including equivalent devices. This means a structured, documented literature search — not an informal awareness of publications. The MDCG 2020-6 guidance on clinical evaluation describes the search methodology in detail, and the same methodology applies to ongoing PMS literature review.

Registries and real-world data

For implantable devices and Class III devices, MDR expects manufacturers to draw on device registries where they exist. In practice, this means monitoring national registries in EU member states where your device is marketed, and documenting what that monitoring showed.

Social media and user feedback

MDCG 2022-21 confirms that social media monitoring can be a PMS data source — specifically for identifying safety concerns that do not reach you through formal complaint channels. This is not a major burden for most manufacturers, but it should be addressed in your PMSP.

Distributor and importer reports

If you have authorized representatives, importers, or distributors in the EU, they have obligations under Articles 13 and 14 MDR to pass information relevant to PMS back to you. Your quality agreement with these parties should specify what they are required to report and how frequently.

Post-Market Clinical Follow-Up (PMCF)

PMCF is a specific subset of PMS. It covers the ongoing collection of clinical data on a device already on the market, to confirm continued safety and performance, identify emerging risks, and monitor long-term outcomes.

PMCF is required for all Class III devices and implantable devices by default. For other classes, PMCF is required unless the manufacturer can justify why it is not necessary — and that justification must be documented in the PMCF evaluation report.

PMCF activities include device registries, post-market clinical studies, surveys of users and patients, and systematic literature review. The plan for PMCF goes into Annex XIV Part B of your technical documentation. Results feed into the PSUR and the clinical evaluation report.

How PMS connects to your broader QMS

PMS does not operate as a standalone activity. The outputs of your PMS system are inputs to multiple parts of your quality management system:

• Risk management — PMS data may reveal new hazards or change probability/severity estimates for known risks. Your risk register should be updated when PMS findings warrant it.
• Clinical evaluation — the PSUR feeds back into the clinical evaluation report. Changes in the benefit-risk assessment must be reflected in both documents.
• CAPA — when PMS identifies a trend or signal requiring action, that action is processed through your CAPA system.
• Design control — significant PMS findings may indicate that design outputs need to be revisited. This can trigger a design change review under your change management process.
• Labeling and IFU — if PMS reveals that users are misusing the device in ways that could cause harm, labeling changes may be required.

This interconnection is exactly why MDR requires the PMS system to be fully integrated with the quality management system — not managed by regulatory affairs as a separate workstream with no links to quality events or risk files.

Common gaps notified bodies find during technical documentation review

Generic PMS plans not tailored to the device

A PMS plan that applies identical data sources, indicators, and review timelines to a Class I bandage and a Class IIb active implant will not satisfy MDR. Notified bodies flag this repeatedly. The PMSP must reflect the specific risk profile, intended use, user population, and regulatory history of the device it covers.

No defined action thresholds

Article 84 requires the PMSP to specify performance indicators and threshold values. Many manufacturers describe data collection activities but never state what result would trigger a response. If you collect complaint data but never defined the rate at which complaints become a signal, your PMS system cannot generate actionable output.

Literature searches that are too narrow

MDCG guidance confirms that literature surveillance must cover equivalent devices, not just your own device. A search limited to your own product name will miss clinical evidence on comparable devices that may be relevant to your benefit-risk assessment.

PMSR and PSUR not updated after significant events

If a serious incident occurred, an FSCA was issued, or a complaint trend was identified and resolved, the PMSR/PSUR should reflect it. Documents that look unchanged from the original submission despite real-world events in the interim draw immediate scrutiny from notified bodies and national competent authorities.

No documented connection between PMS and risk management

Notified bodies look for evidence that PMS outputs actually influenced risk management decisions. If your PMS reports are produced and filed but never change anything in your risk file or CAPA system, auditors will question whether the system is active or purely procedural.

Building the PMS system in your QMS

The practical challenge for most manufacturers is that PMS data flows in from multiple sources — the complaint system, vigilance reports, literature searches, registry monitoring, distributor reports — and needs to be consolidated, trended, analyzed, and documented in a format that produces the PMSR or PSUR on a defined schedule.

Paper-based PMS systems fail at this. Data sits in separate folders for each source, trending requires manual compilation, and producing the PSUR involves weeks of document assembly. By the time the document is ready, the analysis is already outdated.

Cloudtheapp’s quality management platform connects complaint handling, CAPA, adverse event tracking, and risk management in a single system. PMS data collected through complaints, deviations, and adverse event records feeds automatically into dashboards that support PMSR and PSUR preparation. When a CAPA is opened in response to a PMS finding, it is linked to the originating PMS record — giving you the audit trail MDR requires showing that findings drove action.

Want to see how Cloudtheapp handles post-market surveillance documentation for Class IIa, IIb, and III devices? Book a demo to walk through the system with a specialist.

Notified body and competent authority access to PMS data

Under MDR Article 83(4), national competent authorities have the right to request access to post-market surveillance data. For Class IIb and III devices, the PSUR is submitted to your notified body and subject to formal assessment. This means your PMS records need to be retrievable, coherent, and complete — not reconstructed when a request arrives.

The EUDAMED database, as it reaches full functionality, will include modules for vigilance and post-market surveillance data. Manufacturers are expected to upload incident reports and summaries of safety and clinical performance (SSCPs) for implantable and Class III devices directly to EUDAMED. The timeline for full EUDAMED go-live has shifted several times; confirm current requirements with your notified body.

Summary

A compliant EU MDR post-market surveillance program has five elements that all need to work together: a device-specific PMSP with defined data sources and action thresholds, active data collection from complaints, vigilance, literature, registries, and distributor networks, a systematic analysis process that produces trend data and signals, PMSR or PSUR documentation produced on the correct schedule, and documented connections between PMS outputs and risk management, CAPA, and design changes.

The companies that struggle with MDR PMS compliance are generally those that treat it as a documentation obligation rather than a quality function. The regulation is designed for manufacturers that actually use post-market data to improve their devices. Build the system around that intent, and the documentation follows naturally.

Cloudtheapp’s 60+ quality and compliance applications cover complaint management, CAPA, adverse events, and risk management — all of the functions that feed your PMS system. Schedule a demo to see how it all connects.

This post created by and appeared first on Cloudtheapp

EU MDR Regulation (EU) 2017/745 transformed post-market surveillance from a passive reporting activity into an active, data-driven lifecycle obligation. Articles 83 through 86 define a mandatory system structure: a documented PMS system, a device-specific PMS plan, periodic PMS reports for Class I devices, and Periodic Safety Update Reports (PSURs) for Class IIa through III devices. The December 2025 MDCG 2025-10 guidance provides the most detailed official interpretation of these obligations to date, clarifying how to build, operate, and integrate a compliant PMS system within your QMS. This guide covers everything manufacturers need to know.

What Is Post-Market Surveillance Under EU MDR?

Post-market surveillance is the ongoing, proactive process of collecting and analyzing real-world performance data from medical devices once they are placed on the EU market. Under EU MDR (Regulation 2017/745/EU), PMS is not a reactive complaint-handling function. It is a systematic, proactive process integrated into the manufacturer's Quality Management System to continuously verify that devices remain safe, perform as intended, and meet general safety and performance requirements throughout their entire market lifetime.

Article 10(10) of the MDR mandates that every manufacturer establish, document, implement, maintain, update, and improve a PMS system appropriate to the risk class and type of device. This obligation applies regardless of device class, from Class I to Class III.

The critical shift from the predecessor Medical Device Directive (MDD) is one of intent. Under the MDD, PMS was often treated as a periodic reporting exercise. Under MDR, it is a living system that feeds back into clinical evaluation, risk management, design control, and technical documentation updates continuously.

Why EU MDR Raised the PMS Bar

The increased PMS rigor under MDR was a direct response to real-world device safety failures. The PIP breast implant scandal, metal-on-metal hip replacement complications, and surgical mesh problems all revealed a systemic failure: devices with deteriorating real-world performance stayed on the market too long because post-market data was not systematically collected, analyzed, or escalated to corrective action.

MDR's response was structural. Under the regulation:

• PMS plans are device-specific, not general system documents
• Notified Bodies have expanded oversight access to PMS reports and PSURs during surveillance audits
• PSUR update frequencies are defined by risk class with firm deadlines
• Post-Market Clinical Follow-Up (PMCF) is required for most devices unless explicitly justified otherwise
• Proactive data gathering from multiple defined sources is mandatory

Manufacturers who build rigorous PMS systems gain a measurable advantage in Notified Body interactions and demonstrate the kind of proactive safety governance that regulators now explicitly expect.

The 4 Core PMS Articles: 83 Through 86

Article 83: The PMS System

Article 83 defines the foundational requirement: every manufacturer must establish, document, implement, maintain, and continuously improve a PMS system. This system must actively gather post-market data from defined sources, analyze it for safety signals and performance trends, and feed findings back into risk management, clinical evaluation, and QMS processes.

The PMS system is not a document. It is a connected operational process that links complaint handling, vigilance reporting, PMCF, field safety corrective actions, and CAPA into a coherent feedback loop.

Article 84: The PMS Plan

Article 84 requires a documented PMS plan for each device, specifying:

• What data will be gathered and from which specific sources
• The methods and processes for data collection, storage, and analysis
• Defined threshold criteria that trigger CAPA or field safety corrective action
• Explicit reference to the clinical evaluation and risk management processes that PMS data feeds into

The PMS plan is a living document. When PMS data generates new risk insights, the plan updates accordingly. Notified Bodies review PMS plans during initial certification audits and at every surveillance audit, making plan quality a direct factor in certification outcomes.

Article 85: The PMS Report (PMSR)

Article 85 applies to Class I devices. Manufacturers must document PMS findings in a Post-Market Surveillance Report that summarizes results, analyzes conformity with general safety and performance requirements, presents a benefit-risk determination, and records any CAPA taken. The PMSR must be updated when PMS activities generate new relevant findings and must be available to competent authorities upon request.

Article 86: The Periodic Safety Update Report (PSUR)

Article 86 applies to Class IIa, IIb, and III devices and represents the most rigorous PMS reporting obligation under MDR.

PSURs must be updated at the following minimum frequencies:

• Class IIa: At least every 2 years
• Class IIb and III: At least annually

Each PSUR must include: the conclusions of the benefit-risk determination, main findings from PMCF, volume of sales and estimated population using the device, and a complete summary of PMS data analyzed with rationale for any corrective or preventive actions taken.

Class IIb and III PSURs must be submitted to the Notified Body. Class IIa PSURs must be available to the Notified Body on request. Both are reviewed during Notified Body surveillance activities.

What Data Sources Feed a PMS System?

A compliant PMS system draws from a defined, broad set of data sources. MDCG 2025-10 provides detailed guidance on the minimum expected inputs:

Reactive data sources:

• Customer complaints and device user feedback
• Vigilance reports from competent authorities
• Post-market adverse events reported by users, patients, or healthcare institutions
• Field safety corrective action (FSCA) data from similar devices on the market

Proactive data sources:

• Systematic literature searches covering the device type, equivalent devices, and relevant clinical areas
• PMCF studies, device registries, and structured patient or user surveys
• Market surveillance data from competent authorities and Notified Bodies
• Analysis of returned, repaired, or scrapped devices
• Feedback networks from distributors and healthcare providers

Every data source must be described in the PMS plan, including search methodology, frequency, responsible person, and the process by which findings are assessed against defined threshold criteria.

Post-Market Clinical Follow-Up (PMCF)

PMCF is a subset of PMS activities focused specifically on post-market clinical data collection. Under EU MDR Annex XIV Part B, PMCF is required unless the manufacturer explicitly justifies why it is not applicable to a specific device.

PMCF activities include:

• Prospective clinical investigations using the device in its intended patient population
• Clinically relevant data from literature reviews, device registries, or structured user surveys
• Structured feedback programs with healthcare institutions using the device

PMCF findings must feed directly into the clinical evaluation and Clinical Evaluation Report (CER), the technical documentation, and the risk management file. MDCG 2025-10 reinforces this closed-loop requirement: PMCF is not a standalone project but a continuous input into the full technical documentation ecosystem that sustains the device's CE marking.

Vigilance: Serious Incidents and FSCAs

Vigilance reporting under EU MDR (Articles 87-90) operates in parallel with PMS but responds to specific triggering events. Manufacturers must report to the competent authority of the relevant Member State:

• Serious incidents (events that led or could lead to patient death, serious deterioration in health, or serious public health threat): within 15 days of becoming aware
• Field Safety Corrective Actions (FSCAs): reported through a Field Safety Notice (FSN) before implementation wherever possible

An adverse event investigation that identifies a device-related root cause must trigger both a vigilance report and a CAPA. MDCG 2025-10 makes clear that the PMS system must define explicit processes for identifying potential serious incidents within complaint and feedback data streams, with documented escalation criteria and named responsible persons.

Vigilance data is also a required input into the PSUR. Unreported or delayed incidents create gaps not only in vigilance compliance but in the accuracy of the periodic safety update analysis itself.

MDCG 2025-10: What the December 2025 Guidance Adds

The Medical Device Coordination Group published MDCG 2025-10 in December 2025, providing the most comprehensive official interpretation of EU MDR PMS requirements to date. Key guidance elements that manufacturers must address:

• QMS integration: MDCG 2025-10 reinforces that PMS must be embedded within and connected to the full QMS, with defined interfaces to risk register processes, clinical evaluation, CAPA, and technical documentation. Standalone PMS binders do not meet MDR intent.
• Active, not reactive, surveillance: Guidance emphasizes that waiting for complaints to arrive does not satisfy the MDR's proactivity requirement. Manufacturers must design systems that actively seek real-world performance data.
• Quantified thresholds and triggers: MDCG 2025-10 expects manufacturers to define quantitative or qualitative threshold criteria that trigger CAPA or FSCA initiation when breached. Vague assessment language is not sufficient.
• IVD applicability: The guidance covers both MDR (2017/745) and IVDR (2017/746), applying the same PMS framework to in vitro diagnostic devices.
• Proportionality: PMS plans, reports, and PMCF scope should be proportionate to the device's risk class, intended population, and complexity of clinical use.

Manufacturers who have not yet reviewed and updated their PMS plans in light of MDCG 2025-10 face potential major findings at their next Notified Body surveillance audit.

Integrating PMS Into Your QMS

A PMS system that operates in isolation produces compliance artifacts but not compliance outcomes. True MDR conformity requires PMS to function as a connected element within the full QMS.

PMS findings must have documented pathways to:

• Risk management: New safety signals and threshold breaches update the risk file and the benefit-risk determination in the CER
• Clinical evaluation: PMCF data and real-world evidence feed into the CER on the cadence defined in the PMS plan
• CAPA: Identified trends or threshold breaches initiate formal root cause investigations and deviation CAPAs with defined timelines
• Technical documentation: Updated risk files and clinical evaluations require corresponding updates to the technical documentation supporting CE marking
• Management review: PMS trend data and PSUR conclusions should appear as standing agenda items

Managing these connections across disconnected spreadsheets, email threads, and shared drives creates version control failures, traceability gaps, and missed escalation windows. An integrated QMS platform that connects PMS data to CAPA, clinical evaluation, risk management, and document control removes these gaps structurally.

How Cloudtheapp Supports EU MDR PMS Compliance

Building a compliant EU MDR PMS system on manual tools is both time-consuming and structurally fragile. Cloudtheapp's AI-powered QMS platform provides medical device manufacturers with an integrated environment for every PMS obligation:

• Complaint and adverse event capture linked directly to PMS analysis workflows and threshold monitoring
• PMCF data collection modules connected to clinical evaluation and CER management records
• CAPA initiation triggered automatically from PMS threshold breaches with full traceability
• PSUR and PMSR report generation with audit-ready traceability back to underlying PMS data
• Risk management integration: PMS findings update risk assessments in real time
• Management review dashboards surfacing PMS trends alongside CAPA performance and audit results

Because Cloudtheapp is validated per FDA QMSR, ISO 13485:2016, and ISO 9001, every PMS record generated in the platform meets both EU MDR and global QMS standards. Manufacturers operating in EU and US markets maintain a single compliant record set rather than parallel systems.

Ready to build a PMS system that holds up under MDCG 2025-10 and Notified Body scrutiny? Request a demo to see how Cloudtheapp connects every EU MDR PMS obligation end to end.

Conclusion

EU MDR post-market surveillance is a mandatory, proactive, and deeply interconnected compliance obligation. Articles 83 through 86 define the structural requirements. MDCG 2025-10 clarifies what "good" looks like in practice. And an integrated QMS is the only architecture that sustains these requirements without creating unsustainable manual overhead.

Manufacturers who treat PMS as a living system rather than a periodic reporting task produce better safety outcomes, pass Notified Body scrutiny more consistently, and build the real-world evidence base that the next generation of clinical evaluation demands.

This post created by and appeared first on Cloudtheapp