Under the EU MDR, medical device post-market surveillance is a continuous, systematic process that manufacturers must run for the full lifecycle of a device. It is not optional, and it is not “nice to have”. The legal foundation is clear: manufacturers must plan, establish, document, implement, maintain, and update a PMS system that actively gathers and analyses real-world data, then uses that evidence to keep the device safe, compliant, and appropriately risk-controlled.
One of the most persistent misconceptions is that PMS is basically complaint handling with a spreadsheet. It is not. Complaint handling is one input. A compliant PMS system is proactive, documented, and explicitly linked to risk and benefit risk evaluation, which means it must feed back into your risk management and your quality system in a way an auditor can follow.
This guide explains PMS plan requirements, EU MDR post-market surveillance obligations, PMCF, PSUR, vigilance reporting requirements, and how to build an audit-ready surveillance system that behaves like a living system, not a dusty folder.
Need to review or build your PMS system?
What is Medical Device Post-Market Surveillance?
In plain English, medical device post-market surveillance is the manufacturer’s organised way of collecting real-world information about the device after it is placed on the market, analysing that information, and acting on what it shows. The goal is not simply to “record issues”. The goal is to confirm ongoing safety and performance, detect signals early, and continuously validate that the benefit risk profile remains acceptable.
EU MDR post-market surveillance applies to all device classes. The depth and intensity must be proportionate to risk class and device type, but the obligation exists for everyone. Even Class I manufacturers still need a documented PMS plan and must produce PMS outputs.
A useful way to answer the common search query “what is a post-market surveillance plan” is this: the PMS plan is the written blueprint that explains what you will collect, how you will analyse it, what thresholds trigger action, and how your outputs will be produced and reviewed.
MDR Annex III and Articles 83 to 86, the legal foundation of PMS
If you want PMS to survive an audit, you need to anchor it properly:
- MDR Article 83 sets the requirements for the PMS system itself, including the purpose and the “feedback loop” expectation.
- MDR Article 84 requires a PMS plan, and points you to Annex III for what that plan must contain.
- MDR Articles 85 and 86 define the PMS reporting outputs, split by class:
- PMS Report for Class I (Article 85)
- PSUR for Class IIa, IIb, and III (Article 86)
Translate this into human terms: Annex III tells you what must be in your PMS plan. Articles 85 and 86 tell you what PMS outputs you must produce, and when.
Essential components of a Post-Market Surveillance plan
This section is your minimum viable compliant structure. If your post-market surveillance plan cannot answer these items clearly, it will read as generic, and generic plans are auditor bait.
These elements are based on MDR Article 84 and Annex III
Data collection strategy
Your PMS plan must describe the data sources and methods you will use to collect and evaluate information.
Include both reactive and proactive sources, such as:
- Complaint handling system data (complaints, returns, service reports)
- Vigilance reports and regulatory feedback
- Feedback from users, distributors, installers, and service partners
- Post-market clinical follow-up (PMCF) outputs where applicable
- Scientific literature monitoring relevant to safety, performance, and state of the art
- Registry data where relevant
- Trending of nonconformities, CAPAs, and manufacturing signals that could affect field performance
- Social media or public sources only if you have a defined process and a sensible signal handling method, otherwise you risk creating noise without governance
Good PMS plans specify not just “what” but “how often” and “who owns it”.
Data analysis methodology
A PMS plan should define how you will analyse and interpret signals. Auditors want to see that you can detect issues before they become incidents.
Define:
- Review frequency and cadence by source
- Trending approach, including what constitutes a signal
- Trigger thresholds and escalation rules
- How you ensure data completeness and quality
- How you differentiate expected issues from emerging risk
This is where trend reporting MDR becomes relevant. Trend reporting is not vibes-based. MDR Article 88 requires you to report statistically significant increases in non-serious incidents or expected undesirable side effects.
Risk management integration
This is the part many companies hand-wave, and it is exactly what auditors look for.
Your PMS system must feed into risk and benefit risk evaluation. Practically, that means your PMS plan should state:
- Which risk management documents are updated when certain signals occur
- How PMS findings affect hazard analysis, risk controls, residual risk, and benefit risk conclusions
- How changes are documented, reviewed, and approved
Use your keyword honestly here: risk management integration ISO 14971 should mean a real loop, not a line in a procedure. PMS outcomes should trigger risk file review events, and those events should leave evidence behind.
Reporting and escalation procedures
Your PMS plan should explain how outputs flow into action:
- CAPA initiation and containment
- Vigilance decision-making and reporting timelines
- Field safety corrective action (FSCA) decision pathway
- Labelling and IFU updates when new risks or mitigations are identified
- Design change considerations, including when change control is required
Escalation must link to the vigilance obligations in MDR Articles 87 to 89.
PMS vs PMCF, what’s the difference?
PMS is the whole system. It includes everything you do to monitor safety and performance post-market.
Post-market clinical follow-up (PMCF) is the clinical subset of PMS. It focuses on ongoing clinical evidence generation or confirmation. PMCF exists to ensure your clinical evaluation remains valid over time, especially when there are uncertainties, evolving clinical practice, new state-of-the-art expectations, or higher-risk devices.
If you want a simple mental model:
- PMS answers: What is happening in the field?
- PMCF answers: Is the clinical performance and benefit risk profile still supported by evidence for the intended purpose, users, and patient population?
This distinction matters because many manufacturers try to “do PMS” without maintaining a credible clinical evidence lifecycle. Auditors and Notified Bodies see that pattern constantly.
PMS reporting obligations, PMS report vs PSUR
Under MDR, your PMS system produces formal outputs.
Class I: PMS report
For Class I devices, manufacturers must produce a PMS report summarising the results and conclusions of the analysis of PMS data, including rationale and description of corrective and preventive actions taken.
Class IIa, IIb, III, PSUR
For Class IIa, IIb, and III devices, manufacturers must prepare a PMS report and PSUR, specifically the PSUR format and update cadence defined in MDR Article 86.
If you are targeting the query “when is a PSUR required”, the answer is: PSUR is required for Class IIa, IIb, and III devices under MDR, with frequency determined by class and regulatory expectations as described in Article 86.
Practical point: your PSUR should not read like an annual blog post. It should show structured evidence: trends, signals, complaints, serious incidents, FSCAs, CAPA impact, benefit risk conclusion, and any preventive improvements.
Vigilance reporting requirements under MDR
Vigilance is not the same as PMS, but it is welded to it.
Under MDR Articles 87 to 89, manufacturers must report serious incidents and FSCAs, and they must manage the investigative and corrective pathway that follows.
Key terms:
- Vigilance reporting requirements cover serious incident reporting and FSCA reporting to competent authorities.
- Field safety corrective action (FSCA) is an action taken to reduce the risk of death or serious deterioration in health associated with a device already placed on the market.
Audit reality: if your vigilance records do not feed back into PMS trending, CAPA, and risk management updates, your system will look fragmented. Fragmented systems create findings.
Trend reporting under MDR
Trend reporting MDR is one of the most misunderstood obligations because it sits in the awkward middle, not a serious incident, but still significant.
MDR Article 88 requires reporting statistically significant increases in:
- non-serious incidents, or
- expected undesirable side effects,
That could have a significant impact on the benefit-risk analysis.
Common audit failure patterns include:
- No defined thresholds, so you cannot justify when a trend becomes reportable
- No statistical method or rationale was documented
- Reviews happen sporadically, so you cannot show consistent surveillance
- Over-reliance on “clinical judgement” without documented criteria
A good system defines thresholds, applies them consistently, and documents when a threshold is not met, not just when it is.
Complaint handling and safety monitoring
A complaint handling system is a core data source for PMS, but it is not the entire surveillance system.
Complaints should drive:
- Trending and signal detection
- CAPA initiation and containment where needed
- Risk file updates when thresholds or new hazards are identified
- Vigilance assessment for serious incidents or FSCAs
This is where medical device safety monitoring becomes real. If complaints are collected but never analysed, you have a monitoring theatre, not monitoring.
Integrating PMS with ISO 13485 and ISO 14971
Auditors do not just check whether you have PMS documents. They check whether PMS is integrated into how you run the business.
Here is what they look for in practice:
- PMS outputs appear as management review inputs
- CAPA is triggered by surveillance signals, not just internal failures
- Risk management updates are documented when PMS changes the benefit risk balance
- IFU and labelling updates are governed, not ad hoc
- Trend reporting methodology is defined and applied
- Responsibilities are clear across Regulatory, Quality, Clinical, and PMS owners
The “feedback loop” concept is explicitly part of MDR Article 83. Your evidence must show the loop exists.
PMS Requirements Under IVDR
IVDR has analogous PMS and vigilance expectations for IVDs, with a stronger emphasis on performance monitoring across real-world use and lifecycle evidence.
If you work with both devices and IVDs, the safe operational approach is to treat PMS as a lifecycle requirement across both regimes, then tailor the evidence expectations to the product type.
Official IVDR text: Regulation (EU) 2017/746 consolidated text.
To keep this section precise: treat this as a high-level alignment note unless you want a follow-up version that maps the exact IVDR PMS and vigilance clauses and annex references line by line.
Common PMS audit findings
This is the greatest hits list, and yes, it is painfully familiar.
- PMS plan is generic, not device-specific, has no defined data sources, no thresholds
- No statistical thresholds, making trend reporting impossible to justify
- Weak link to the risk management file, no evidence PMS changed risk decisions
- Missing PSUR, incomplete PSUR, or PSUR does not reflect actual PMS data
- No documented review of PMS outcomes exists, or reviews exist but contain no analysis
- CAPA not linked to surveillance data
- PMCF is treated as optional when the clinical evaluation needs lifecycle support
- Vigilance decisions not traceable, FSCA logic unclear
All of these tie back to the legal expectations in Articles 83 to 86, trend reporting in Article 88, and PMS plan content in Annex III.
How to write a PMS plan for medical devices
If you need a practical flow that maps cleanly to Annex III and Article 84, use this:
- Define scope and device class, include device variants and intended purpose
- Map all data sources, reactive and proactive, and assign ownership
- Set trend thresholds and method, and document the rationale
- Align with risk management and CAPA, define trigger points and update rules
- Define reporting structure and timelines, PMS report or PSUR, plus vigilance escalation
Practical PMS implementation checklist
Use this as your audit sanity check:
- PMS plan documented, approved, and device-specific (Annex III and Article 84)
- PMCF plan established where applicable
- Complaint handling system integrated into PMS analysis
- Trend reporting criteria defined and applied (Article 88)
- PSUR schedule established (Article 86) or PMS report process for Class I (Article 85)
- Risk management file linked to PMS outcomes (Article 83 feedback loop)
- Management review includes PMS outputs and decisions
How Patient Guard supports Post-Market Surveillance compliance
Patient Guard can support you with:
- PMS gap assessments against Articles 83 to 86 and Annex III
- PMS plan drafting and review
- PSUR preparation support, including structure, evidence mapping, and internal review readiness
- Risk management integration support, including ISO 14971-aligned feedback loops
- Audit readiness support, so your PMS system can survive real scrutiny, not just internal optimism
Wrapping Up
Medical device post-market surveillance is ongoing regulatory accountability. Approval is the beginning of evidence gathering, not the end.
If your PMS system is proactive, threshold-driven, and visibly integrated into CAPA and risk management, it will do more than “pass audits”. It will help you catch issues early, control risk intelligently, and protect market access.
FAQ
A post-market surveillance plan is the documented blueprint describing what post-market data you will collect, how you will analyse it, which thresholds trigger action, and what PMS outputs you will produce, aligned to MDR Article 84 and Annex III.
At minimum: data sources and collection methods, analysis and trending methodology, thresholds and escalation rules, risk management integration, CAPA and vigilance interfaces, and reporting outputs.
PMS covers all post-market safety and performance monitoring. PMCF is the clinical subset of PMS focused on ongoing clinical evidence to support the clinical evaluation over time.
PSUR is required for Class IIa, IIb, and III devices under MDR Article 86.
PMS outputs must feed into risk management updates, benefit risk reassessment, and risk control effectiveness review. Evidence of this loop should be visible in risk files, CAPA records, and management review.
Generic PMS plans, missing thresholds for trend reporting, weak risk integration, missing or low-quality PSURs, poor documentation of PMS reviews, and CAPA not linked to surveillance data.
Patient Guards Recent Posts
Medical Device Regulatory Consulting Services Explained
Explore medical device regulatory consulting services for ISO, FDA, EU, and more. Build compliant systems, pass audits, and scale globally with expert support.
Patient Guard’s QMS Achieves ISO 13485 Certification
A milestone that strengthens our commitment to quality
Regulatory and quality consulting is one thing. Building, implementing, and passing audits on your own Quality Management System is another.
UDI Medical Devices: Types Explained (EU MDR Guide)
UDI medical devices are not just a labelling requirement. They are the backbone of traceability under EU MDR.
