Regulatory guide

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

By Kieran Redington, Founder of MedFortis Updated 23 October 2026 ~9 min read

Under Regulation (EU) 2017/745, getting a device CE-marked is only the beginning. Articles 83 to 92 of the EU MDR set out what manufacturers must do after a device reaches the market, and Notified Bodies look at them closely in audits. This guide goes through each obligation in plain terms.

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:

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:

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 classOutputMinimum update frequency
Class IPMS report (Art. 85)When necessary; available to authorities on request
Class IIaPSURWhen necessary, and at least every 2 years; made available to the Notified Body and, on request, to competent authorities
Class IIbPSURAt least annually; made available to the Notified Body and, on request, to competent authorities
Class III & implantablePSURClass III: at least annually. Class III and implantable devices: submitted to the Notified Body through the electronic system
Note: for Class III and implantable devices the PSUR is submitted through the electronic system and reviewed by the Notified Body. For other devices it is made available to the Notified Body and, on request, to competent authorities. An implantable device in a lower class keeps its own update frequency but follows the Class III submission route. Devices sharing a Basic UDI-DI can, under MDCG guidance, be grouped into a single PSUR where certain conditions are met.
Proposed change: the European Commission's December 2025 proposal to amend the MDR (COM(2025) 1023) would move Class IIb and III PSURs to once in the first year after certification and then every two years. It is still going through the EU legislative process, so the current frequencies apply for now.

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:

SituationDeadline
Serious public health threatImmediately, and no later than 2 days
Death or unanticipated serious deterioration in healthNo later than 10 days
Any other serious incidentNo 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.

What this means for you: the deadline runs from the day you become aware, not from when you finish investigating. Finding out late is no defence, so how quickly your organisation spots a signal decides whether you can meet a 2-, 10- or 15-day clock.

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:

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.
This article is provided for general information only and is not legal or regulatory advice. Requirements are summarised and paraphrased; always refer to the official text of Regulation (EU) 2017/745 and relevant MDCG guidance, and consult a qualified regulatory professional for your specific devices.