What this guide covers
- How Articles 83–92 fit together
- Article 83: the PMS system
- Article 84: the PMS plan
- Article 85: the PMS report (Class I)
- Article 86: the PSUR (Class IIa/IIb/III)
- Article 87: serious incident & FSCA reporting
- Article 88: trend reporting
- Articles 89–92: authority analysis & Eudamed
- PMS and vigilance are not the same thing
- Keeping surveillance up to date
How Articles 83–92 fit together
The MDR treats post-market surveillance (PMS) as an ongoing system that feeds back into your device, rather than a document you write once. The chapter splits into two connected parts:
- The PMS system (Articles 83–86): you gather and analyse real-world data on your device as a matter of routine, and produce regular reports such as the PMS report or PSUR.
- Vigilance (Articles 87–92): you report specific serious incidents and field safety corrective actions to competent authorities within strict deadlines. This part also covers trend reporting and the electronic systems behind it.
Both serve the same purpose: checking that your device's benefit-risk profile still holds, and acting quickly when it doesn't.
Article 83: the post-market surveillance system
Everything else in the chapter builds on Article 83. It requires every manufacturer to plan, establish, document, implement, maintain and update a PMS system as an integral part of its quality management system. The system must be proportionate to the device's risk class and appropriate to its type.
The system exists to collect and review experience from devices on the market. You then use that data to update the benefit-risk determination, the clinical evaluation, the risk management file, the design and manufacturing information and the instructions for use. Where needed, it should also trigger corrective or preventive action (CAPA).
Article 84: the post-market surveillance plan
The PMS system has to run on a documented PMS plan, whose required contents are set out in Annex III. A compliant plan describes:
- The proactive and reactive data you will collect: complaints, incident reports, field data, published literature, and information from public databases and registries.
- The methods and indicators used to assess that data, including thresholds that trigger a benefit-risk reassessment.
- Procedures to manage vigilance obligations (Articles 87–92) and to communicate with authorities, Notified Bodies and economic operators.
- Systematic procedures to identify and initiate CAPA, plus tools to trace and identify affected devices.
- Your PMCF plan (post-market clinical follow-up, Annex XIV Part B), or a documented justification if PMCF is not applicable.
Article 85: the post-market surveillance report (Class I)
For Class I devices, the output is a PMS report. It summarises the results and conclusions of the analysis of the PMS data, together with a rationale and description of any preventive or corrective actions taken. It must be updated when necessary and made available to competent authorities on request.
Article 86: the periodic safety update report (PSUR)
For Class IIa, IIb and III devices, the output is the more demanding PSUR. On top of what a Class I report contains, the PSUR must include the conclusions of the benefit-risk determination, the main findings of PMCF, and the volume of sales together with an estimate of the size and characteristics of the population using the device.
Update frequency and who reviews it depend on the device class:
| Device class | Output | Minimum update frequency |
|---|---|---|
| Class I | PMS report (Art. 85) | When necessary; available to authorities on request |
| Class IIa | PSUR | When necessary, and at least every 2 years; made available to the Notified Body and, on request, to competent authorities |
| Class IIb | PSUR | At least annually; made available to the Notified Body and, on request, to competent authorities |
| Class III & implantable | PSUR | Class III: at least annually. Class III and implantable devices: submitted to the Notified Body through the electronic system |
Article 87: reporting serious incidents and FSCAs
This is the vigilance obligation most teams worry about, because the deadlines are short. Manufacturers must report serious incidents and field safety corrective actions to the relevant competent authority. You report as soon as a causal link between the device and the incident is established or is reasonably possible, and no later than the following deadlines, counted in calendar days from the awareness date:
| Situation | Deadline |
|---|---|
| Serious public health threat | Immediately, and no later than 2 days |
| Death or unanticipated serious deterioration in health | No later than 10 days |
| Any other serious incident | No later than 15 days |
Partial (initial) reports are permitted to meet these deadlines, with follow-up as the investigation progresses. If you judge that an event is not a serious incident, or is an expected side-effect covered by trend reporting, you must provide an explanatory statement, and the authority can challenge it.
The same December 2025 proposal would extend the 15-day deadline to 30 days for serious incidents that don't involve a public health threat, a death or a serious deterioration in health. Until it's adopted, 15 days is the rule.
Article 88: trend reporting
Article 88 covers patterns rather than single events. Manufacturers must report any statistically significant increase in the frequency or severity of incidents that are not serious incidents, or of expected undesirable side-effects, where that increase could have a significant impact on the benefit-risk analysis and has led or may lead to unacceptable risks to the health or safety of patients, users or other persons. The methodology and thresholds for detecting such trends should be defined in your technical documentation.
Articles 89–92: authority analysis and Eudamed
The last articles cover the regulator's side and the systems that support reporting. Articles 89 and 90 govern how competent authorities analyse serious incidents, FSCAs and combined vigilance data, and how they coordinate any action that follows. Article 92 establishes the Eudamed electronic system for vigilance and post-market surveillance. This is the central database through which reports and PSURs are meant to be submitted and shared between authorities. Four modules (actor registration, UDI/device registration, notified bodies and certificates, and market surveillance) have been mandatory since 28 May 2026. The vigilance module is not yet mandatory, so check which route applies to you before relying on Eudamed for incident or PSUR submission.
PMS and vigilance are not the same thing
Auditors often find that a manufacturer has treated PMS and vigilance as one process. They are linked, but they work differently:
- PMS runs all the time. It works at the system level and produces regular reports (the PMS report or PSUR).
- Vigilance responds to events. It works at the incident level, with fixed reporting deadlines.
The thresholds you set for PMS trend analysis are also not automatically the same as the triggers for trend reporting under Article 88, even though the two overlap. Auditors will want to see that you've documented how they relate.
Keeping surveillance up to date
Across Articles 83–92, the message is the same: surveillance must be continuous, documented and backed by evidence, and how fast you detect a problem decides whether you meet your reporting deadlines. Yet much of this work is still done by hand. Analysts check adverse-event databases, recall notices, literature and online marketplaces one site at a time, then piece together an evidence trail afterwards.
That is where gaps and missed deadlines come from. You can automate the external side of PMS: monitoring sources such as the FDA MAUDE adverse-event database, recall notices, clinical-trial registries and unauthorised marketplace listings, and keeping a timestamped record of each finding. Your PMS plan and PSUR then draw on current data, and you have the audit trail these articles ask for. This doesn't replace your QMS, complaint handling or clinical evaluation. It improves the data collection and record-keeping underneath them.
See what your post-market surveillance is missing
Book a demo and we'll run MedFortis against your device lines to show you, live, what's turning up across FDA data, recalls, trials and the open market.
Book a Demo →Key takeaways
- Articles 83–86 define the proactive PMS system and its outputs (PMS report for Class I; PSUR for Class IIa/IIb/III).
- Articles 87–92 define reactive vigilance: serious-incident reporting within 2, 10 or 15 days, plus trend reporting and Eudamed.
- PSUR frequency scales with risk: at least every 2 years (IIa), at least annually (IIb, III). Class III and implantables are submitted to the Notified Body; for other classes the PSUR is made available to it.
- Reporting clocks start at awareness, so how fast you detect a signal is a compliance question, as well as an efficiency one.
- Automated monitoring of external sources makes the system easier to keep up to date and easier to evidence in an audit.