EU MDR Article 83–92: Post-Market Surveillance Requirements Explained

How Articles 83–92 fit together

The MDR treats post-market surveillance (PMS) as a continuous, closed-loop system, not a one-off document. Broadly, the chapter splits into two connected streams:

• The PMS system (Articles 83–86) — a proactive, ongoing process of gathering and analysing real-world data on your device, and producing periodic outputs such as the PMS report or PSUR.
• Vigilance (Articles 87–92) — a reactive process of reporting specific serious incidents and field safety corrective actions to competent authorities within strict deadlines, plus trend reporting and the underlying electronic systems.

Both feed the same goal: continuously confirming that your device's benefit-risk profile still holds, and acting quickly when it doesn't.

Article 83 — The post-market surveillance system

Article 83 is the foundation. 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.

Its purpose is to actively collect and review experience from devices on the market and use that data to update the benefit-risk determination, the clinical evaluation, the risk management file, the design and manufacturing information, the instructions for use, and — where needed — to 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. In practice, 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. Beyond 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:

Article 87 — Reporting serious incidents and FSCAs

This is the vigilance obligation most teams worry about, because the clock is unforgiving. Manufacturers must report serious incidents and field safety corrective actions to the relevant competent authority. Reporting begins 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:

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 — which the authority can challenge.

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 materially affect the benefit-risk analysis. The methodology and thresholds for detecting such trends should be defined in your technical documentation.

Articles 89–92 — Authority analysis and Eudamed

The final articles shift to the regulator side and the infrastructure that supports reporting. Articles 89 and 90 govern how competent authorities analyse serious incidents, FSCAs and aggregated vigilance data and coordinate any resulting action. Article 92 establishes the Eudamed electronic system for vigilance and post-market surveillance — the central database through which reports and PSURs are increasingly submitted and shared between authorities as its modules become mandatory.

PMS vs vigilance: the common confusion

A frequent audit finding is treating PMS and vigilance as the same thing. They are linked but distinct:

• PMS is proactive and continuous — it operates at the system level and produces periodic outputs (PMS report, PSUR).
• Vigilance is reactive and event-driven — it operates at the incident level with fixed reporting deadlines.

Crucially, the thresholds you set for PMS trend analysis are not automatically the same as the triggers for vigilance trend reporting under Article 88, even though they overlap. Documenting the relationship between the two is what auditors look for.

Keeping surveillance current in practice

The recurring theme across Articles 83–92 is that surveillance must be continuous, documented and evidence-backed — and that speed of detection determines whether you meet your reporting clocks. Yet much of the underlying work is still done manually: analysts periodically checking adverse-event databases, recall notices, literature and the open market across disconnected sources, then reconstructing an evidence trail after the fact.

That manual approach is exactly where gaps and missed deadlines creep in. Automating the external-signal side of PMS — continuously monitoring sources like the FDA MAUDE adverse-event database, recall notices, clinical-trial registries and unauthorised marketplace listings, and capturing a timestamped record of every finding — feeds your PMS plan and PSUR with current data and gives you the defensible audit trail these articles demand. It does not replace your QMS, complaint handling or clinical evaluation; it strengthens the data-collection and evidence layer beneath them.