---
title: MDR Articles 83–86: The Post-Market Surveillance Framework Explained
description: MDR Articles 83 to 86 define the post-market surveillance system, plan, report, and PSUR. Here is what each article requires and how they fit together.
authors: Tibor Zechmeister, Felix Lenhard
category: Post-Market Surveillance & Vigilance
primary_keyword: MDR Articles 83 86 PMS framework
canonical_url: https://zechmeister-solutions.com/en/blog/mdr-articles-83-86-pms-framework
source: zechmeister-solutions.com
license: All rights reserved. Content may be cited with attribution and a link to the canonical URL.
---

# MDR Articles 83–86: The Post-Market Surveillance Framework Explained

*By Tibor Zechmeister (EU MDR Expert, Notified Body Lead Auditor) and Felix Lenhard.*

> **MDR Articles 83 to 86 of Regulation (EU) 2017/745 define the four layers of post-market surveillance that every manufacturer must operate. Article 83 requires a PMS system as part of the quality management system. Article 84 requires a PMS plan as part of the technical documentation, with content specified in Annex III. Article 85 requires a PMS Report for Class I devices. Article 86 requires a Periodic Safety Update Report (PSUR) for Class IIa, IIb, and III devices, with class-specific update frequencies and submission routes. The four articles interlock: the system runs under a plan and outputs a class-specific report, all proportionate to the risk class and type of device.**

**By Tibor Zechmeister and Felix Lenhard. Last updated 10 April 2026.**

---

## TL;DR

- Article 83 of Regulation (EU) 2017/745 establishes the obligation to plan, establish, document, implement, maintain, and update a post-market surveillance system as an integral part of the manufacturer's quality management system under Article 10(9).
- Article 84 requires a PMS plan as a technical documentation element, with the mandatory content specified in Annex III.
- Article 85 defines the PMS Report that Class I manufacturers prepare, updated when necessary and made available to the competent authority upon request.
- Article 86 defines the Periodic Safety Update Report (PSUR) for Class IIa, Class IIb, and Class III devices, with different update frequencies, content requirements, and submission routes by class.
- MDCG 2025-10 (December 2025) is the current operational guidance that notified bodies use to assess whether a PMS system built on Articles 83 to 86 is actually working in practice.

---

## A short opener — why four articles, not one

Regulation (EU) 2017/745 could have written post-market surveillance as a single article. It did not. It wrote four. Understanding why those four exist as separate legal hooks is the first step in understanding how they are audited.

Article 83 sets the obligation. Article 84 sets the planning requirement. Article 85 sets the output for low-risk devices. Article 86 sets the output for higher-risk devices. Each article targets a different failure mode: no system at all, a system with no plan, a Class I device that never reports, a Class IIa-to-III device that reports on the wrong cadence or with the wrong content. A notified body auditor works through these four articles in order. The manufacturer who walks in without a separate answer for each one walks out with findings.

The arm-strap sleep-monitoring device we wrote about in [the pillar post on PMS](/blog/what-is-post-market-surveillance-mdr) is the context story for this framework. Skin irritations from prolonged wear that lab testing under EN ISO 10993-1 had not predicted. The only reason the pattern was caught, traced, and corrected was that the manufacturer had a PMS system built against all four of these articles — not just one. The plan said what to monitor. The system collected complaints. The analysis ran on cadence. The report surfaced the trend. The corrective action updated the specification. Four articles, four layers, one loop that actually closed.

## Article 83 — the PMS system

Article 83 is the top-level obligation. It has a specific structure worth knowing by heart because audit questions track it line by line.

Article 83(1) requires manufacturers to plan, establish, document, implement, maintain, and update a post-market surveillance system. Those six verbs are not decoration. Each one is a distinct audit question. "Planned" means the system was designed, not improvised. "Established" means it exists in the QMS. "Documented" means there is written evidence. "Implemented" means people actually execute it. "Maintained" means it is kept running. "Updated" means it evolves based on findings. A system that is documented but not implemented fails Article 83(1). A system that is implemented but not updated fails Article 83(1). All six verbs or none.

Article 83(1) also ties the PMS system to the quality management system under Article 10(9). The PMS system is not a parallel structure — it is an integral part of the QMS. For startups certifying their QMS against EN ISO 13485:2016 + A11:2021, that means the PMS processes live inside the same QMS the auditor is already looking at. The harmonised standard provides the process architecture; the MDR provides the specific PMS obligations that must sit inside it.

Article 83(2) requires the system to be suited to actively and systematically gathering, recording, and analysing relevant data on the quality, performance, and safety of the device throughout its entire lifetime. "Actively and systematically" is the operative phrase. A complaint mailbox that nobody reads is not active. A spreadsheet that exists only after a complaint comes in is not systematic. The system must be designed to surface signals, not to wait for them to arrive.

Article 83(3) names the purposes for which PMS findings must be used: updating the benefit-risk determination, updating the design and manufacturing information, updating the clinical evaluation, updating the summary of safety and clinical performance where applicable, identifying needs for preventive or corrective action, and identifying options to improve usability, performance, and safety. Six named uses. Each is a separate feedback loop that the plan has to describe and the system has to run.

Article 83 is also the article that makes PMS proportionate. It is proportionate to the risk class and appropriate for the type of device. Proportionality is not an escape hatch — it is a calibration rule. A Class I digital health app does not need the same PMS architecture as a Class III implantable. But both need every layer of the framework.

## Article 84 — the PMS plan

Article 84 is short. It says the post-market surveillance system shall be based on a post-market surveillance plan, the requirements for which are set out in Section 1.1 of Annex III. That single sentence does two pieces of work. It makes the plan mandatory. And it points to Annex III as the content specification.

Annex III, Section 1.1, is where the actual content lives. The plan addresses the processes for collecting and using the available information, in particular complaints and reports from healthcare professionals, patients, and users; information from similar devices on the market; publicly available information and state-of-the-art evaluations; and data on serious incidents including from PSURs and field safety corrective actions. The plan sets out effective and appropriate methods and processes to assess the collected data. It describes the tools to investigate complaints and analyse field experience. It specifies the methods and protocols for trend reporting under Article 88, including identifying any statistically significant increase in frequency or severity of incidents. It describes communication with competent authorities, notified bodies, economic operators, and users. It references the procedures fulfilling Article 83, 84, and 86 obligations. It sets out systematic procedures to identify and initiate corrective actions. It describes tools to trace and identify devices for which corrective actions might be necessary. And it includes a PMCF plan or a justification for why PMCF is not applicable.

That list is the audit checklist. Every element in the list is an element a notified body auditor can ask to see. A PMS plan that addresses nine of the ten items and silently skips the tenth is a PMS plan that generates a finding.

The Regulation does not prescribe a template. It prescribes content. The most lean PMS plans we have seen at startups are three to eight pages long, organised as a table with one row per Annex III element, naming the data source, the method, the cadence, the owner, and the document reference. Elegant structure beats elaborate volume. For the full walkthrough of building a plan against Annex III, see [the PMS plan under MDR Annex III](/blog/pms-plan-mdr-annex-iii).

## Article 85 — the PMS Report for Class I devices

Article 85 is the output specification for Class I manufacturers. It requires manufacturers of Class I devices to prepare a post-market surveillance report summarising the results and conclusions of the analyses of the PMS data gathered as a result of the PMS plan, together with a rationale and description of any preventive and corrective actions taken. The report is updated when necessary and made available to the competent authority upon request.

Three features of Article 85 deserve attention because they are the features Class I founders most often misread.

First, "when necessary" is not "never." The Regulation does not set a fixed calendar for Class I, but the expectation is that the report reflects what the underlying system has actually produced. If the PMS system has analysed a full cycle of data, the report is updated. If the device has been on the market for a year with no complaints and no signals, a dated entry noting that conclusion is still a report. "When necessary" means the report keeps pace with what the system knows.

Second, the report content is explicitly results and conclusions, together with a rationale and description of any preventive and corrective actions. It is an analytical document, not a log. An auditor who sees a report that only lists raw complaint counts without analysis will press on the missing analysis.

Third, "made available upon request" does not mean the report can be produced retroactively. The report exists before the competent authority asks for it. The Regulation requires the report to exist as a document; it only requires delivery on request. Class I manufacturers who intend to write the report the week a request arrives are describing a system that does not meet Article 85.

For the Class I-specific mechanics including template structure and update triggers, see [the PMS Report for Class I devices under Article 85](/blog/pms-report-class-i-devices).

## Article 86 — the PSUR for Class IIa, IIb, and III devices

Article 86 scales the post-market report for higher-risk devices. The PSUR is a more substantive document than the Article 85 report because it covers devices where the post-market scrutiny must be correspondingly richer.

Article 86(1) sets the content. The PSUR summarises the results and conclusions of the analyses of the PMS data gathered as a result of the PMS plan, together with a rationale and description of any preventive and corrective actions taken. The PSUR also sets out the conclusions of the benefit-risk determination, the main findings of the PMCF, and the volume of sales of the device together with an estimate of the size and other characteristics of the population using the device and, where practicable, the usage frequency of the device.

That is five content elements, not one. Every PSUR our notified body reviews must contain all five. A PSUR that summarises complaints and skips benefit-risk is non-compliant. A PSUR that reports benefit-risk and skips PMCF findings is non-compliant. A PSUR that reports PMCF findings and has no sales or population data is non-compliant. The article names the elements, the auditor checks the elements.

Article 86(1) also sets the update frequency. For Class IIb and Class III devices, the PSUR is updated at least annually. For Class IIa devices, the PSUR is updated when necessary and at least every two years. The cadence is set by the Regulation itself. There is no negotiation with the notified body on whether a Class IIb PSUR can be updated every 18 months. It cannot.

Article 86(2) sets the submission route for the highest-risk devices. For Class III devices and implantable devices, the PSUR is submitted by means of the electronic system referred to in Article 92 to the notified body involved in the conformity assessment. The notified body reviews the PSUR and adds its evaluation to the electronic system, together with details of any action taken. The PSUR and the notified body evaluation are made available to competent authorities through the electronic system.

For Class IIa and Class IIb devices, Article 86(2) requires the PSUR to be made available to the notified body and, upon request, to competent authorities. The active electronic submission loop applies specifically to Class III and implantable devices.

For the full PSUR mechanics including Eudamed submission, content structure, and review cycles, see [PSUR for Class IIa, IIb, and III devices under MDR](/blog/psur-class-iia-iib-iii).

## How Articles 83 to 86 interlock

Reading the four articles separately is necessary but not sufficient. The framework only makes sense when the interlock is visible.

Article 83 creates the system. Article 84 says the system must run against a plan. Annex III says what the plan must contain. Article 85 or Article 86 — depending on class — says what the plan must output as a report. The report feeds back into the system under Article 83(3), which names the uses of PMS findings. The uses include updating the benefit-risk determination, which changes the risk management file under EN ISO 14971:2019 + A11:2021. The uses include updating the clinical evaluation, which changes the clinical evaluation report under Article 61 and Annex XIV Part A. The uses include updating the design and manufacturing information, which changes the technical documentation under Annex II.

So the loop is: plan specifies monitoring → system collects data → system analyses data → class-specific report summarises analysis → findings feed into benefit-risk, risk file, clinical evaluation, design, and corrective actions → updates flow back into the plan → next cycle runs against the updated plan. Four articles, one loop. A PMS system where any of the four articles is missing breaks the loop. A PMS system where all four are present but the loop does not actually close is a PMS system that exists on paper and nowhere else.

Auditors are trained to test the loop, not the articles in isolation. The competent question at audit is not "do you have a PMS plan." It is "show me one finding from your last PMS cycle and trace it through the plan, the report, the risk file, and the design change." If the trace breaks, the loop breaks.

## What "proportionate to risk class" means in practice

Article 83 says the PMS system is proportionate to the risk class and appropriate for the type of device. In practice, proportionality scales four things.

**Cadence.** A Class I device with low risk and stable technology can run analysis on a longer cadence than a Class III implantable. The plan sets the cadence; the risk class informs what "reasonable" means. A monthly review for a Class III cardiac implant is reasonable; for a Class I reusable instrument with a 10-year history, it is overkill.

**Data sources.** A Class III active implantable will typically pull from registries, structured follow-up studies, and device-specific literature alongside complaints. A Class I non-invasive device may rely primarily on complaints, user feedback, and general literature monitoring. The PMS plan lists sources appropriate to the device, not a generic template applied without thought.

**Depth of analysis.** A Class IIb or III PSUR must include benefit-risk conclusions, PMCF main findings, and population data. A Class I PMS Report does not have the same content spec. The analytical depth scales with the class.

**Notified body involvement.** For Class III and implantables, the notified body reviews every PSUR electronically. For Class IIa and IIb, the notified body sees the PSUR at surveillance audits and on request. For Class I, the competent authority sees the report on request. The oversight intensity is built into the framework.

Proportionality is not a permission to skip obligations for low-risk devices. It is a calibration rule. Every layer of Articles 83 to 86 applies to every class. What changes is how much depth, what cadence, and who sees it when.

## How MDCG 2025-10 shapes implementation

MDCG 2025-10 (December 2025) is the current operational guidance on post-market surveillance of medical devices and in vitro diagnostic medical devices. It does not override the Regulation, but it is the authoritative interpretation notified bodies apply when assessing PMS systems under Articles 83 to 86.

Three ways MDCG 2025-10 shapes implementation in practice. First, it describes the main PMS activities — data collection, assessment, and conclusions — in enough detail that the auditor knows what "good" looks like at each stage. Startups who read only the MDR text miss the operational texture that MDCG 2025-10 provides. Second, it makes the interaction between PMS and other QMS processes (clinical evaluation, risk management, vigilance) explicit in a way the Regulation only implies. The loop we described above is drawn more directly in the guidance than in the article text. Third, it addresses how PMS applies to smaller manufacturers and lean teams, which is the question every startup eventually asks.

Reading MDCG 2025-10 end to end before an audit is the single highest-leverage move a startup PMS lead can make. It is free, it is official, and it is the document the auditor read last week.

## Common misreadings of Articles 83 to 86

A handful of misreadings come up repeatedly in early-stage PMS work. Each one is worth naming directly.

**Misreading 1: "PMS is reactive."** Article 83 requires a proactive, systematic system. A PMS approach that only responds to incoming complaints is non-compliant on the face of Article 83(2).

**Misreading 2: "Class I devices don't need a PMS plan."** Every class needs a PMS plan under Article 84. Annex III applies to every class. The difference is the class-specific report under Article 85 or Article 86, not the existence of the plan.

**Misreading 3: "The PSUR is a summary of complaints."** The PSUR under Article 86 includes benefit-risk conclusions, PMCF main findings, and population data in addition to complaint analysis. A PSUR that only summarises complaints is missing content elements.

**Misreading 4: "Update cadence is negotiable."** It is not. Class IIb and III PSURs are annual. Class IIa is at least biennial. Class I is "when necessary" but not "never." The cadence is fixed by the Regulation.

**Misreading 5: "The notified body will tell us what to put in the plan."** The notified body will tell you whether your plan meets Annex III. They will not write your plan. Confusing their audit role with their consulting role is a standing misunderstanding that costs startups weeks.

**Misreading 6: "PMS only matters at audit."** PMS matters when a signal comes in from the field. The audit is the day you prove the system runs; the field is the day the system actually earns its keep.

## The Subtract to Ship angle

The [Subtract to Ship framework for MDR](/blog/subtract-to-ship-framework-mdr) applied to Articles 83 to 86 produces a simple test. For every element in your PMS documentation, name the specific article, annex paragraph, or MDCG 2025-10 section that requires it. If the trace exists, the element stays. If the trace does not exist, the element is either waste or miscategorised.

The test sounds obvious. It is also brutal in practice. Startups that run it on their first-draft PMS package typically cut 30 to 50 per cent of the document volume without losing a single regulatory obligation — because first-draft PMS packages tend to borrow templates from consultancies that were built for Class III implantables and never trimmed for the actual device. Every cut paragraph is a paragraph the team does not have to maintain, review, or answer for at audit.

What survives the test is a PMS package where every sentence is load-bearing. Article 83 is covered because the system exists and the six verbs are visible. Article 84 is covered because the plan addresses every Annex III element. Article 85 or 86 is covered because the correct class-specific report exists on the correct cadence with the correct content. Nothing extra. Nothing missing.

## Reality Check

1. Can you name the specific sub-paragraph of Article 83 that obligates each of the six verbs (plan, establish, document, implement, maintain, update), and can you show evidence of all six for your system?
2. Does your PMS plan address every Annex III, Section 1.1 element, or are any elements silently missing?
3. Which report does your device class require — the Article 85 PMS Report or the Article 86 PSUR — and is the current version on the correct cadence?
4. If your device is Class III or implantable, is your PSUR submission route to the notified body via Eudamed actually set up, or is it still on your backlog?
5. Can you trace one finding from your last PMS cycle through the plan, the report, and into a documented update of the risk file or the clinical evaluation?
6. Have you read MDCG 2025-10 end to end, or only the sections someone pointed you to?
7. For every element in your PMS documentation, can you name the specific article or annex that requires it? If not, what are you maintaining and why?

## Frequently Asked Questions

**What is the difference between Article 83 and Article 84?**

Article 83 creates the obligation to have a PMS system as part of the QMS. Article 84 requires that the system run against a documented plan whose content is specified in Annex III, Section 1.1. Article 83 is the "what." Article 84 is the "how it is planned."

**Does Article 85 apply to Class IIa devices?**

No. Article 85 applies to Class I devices only. Class IIa, IIb, and III devices are covered by Article 86 and prepare a PSUR rather than a PMS Report.

**How often must the PSUR under Article 86 be updated?**

For Class IIb and Class III devices, at least annually. For Class IIa devices, when necessary and at least every two years. The Class I PMS Report under Article 85 is updated when necessary; the Regulation does not set a calendar cadence for it.

**Is the PMS plan the same as the PMCF plan?**

No. The PMS plan is the umbrella plan required by Article 84 and Annex III. The PMCF plan is a separate document specified in Annex XIV Part B that sits inside the PMS plan or is referenced by it. Annex III explicitly requires the PMS plan to include a PMCF plan or a justification for why PMCF is not applicable.

**Do Class III PSURs go to the notified body directly?**

Yes. Article 86(2) requires the PSUR for Class III and implantable devices to be submitted via the Article 92 electronic system to the notified body involved in the conformity assessment. The notified body evaluates the PSUR and adds its evaluation to the electronic system.

**Does MDCG 2025-10 replace the MDR text?**

No. MDCG 2025-10 (December 2025) is guidance that interprets how Articles 83 to 86 are applied in practice. The Regulation is the legal obligation. The guidance is the authoritative interpretation that notified bodies follow when assessing whether a PMS system meets the Regulation.

## Related reading

- [What is post-market surveillance under MDR?](/blog/what-is-post-market-surveillance-mdr) — the pillar post this article deep-dives from.
- [The PMS plan under MDR Annex III](/blog/pms-plan-mdr-annex-iii) — the plan content specification walked through element by element.
- [The PMS Report for Class I devices under Article 85](/blog/pms-report-class-i-devices) — the Class I output mechanics and template structure.
- [PSUR for Class IIa, IIb, and III devices under MDR](/blog/psur-class-iia-iib-iii) — the higher-class report mechanics and Eudamed submission.
- [Trend reporting under MDR Article 88](/blog/trend-reporting-mdr-article-88) — the trend-reporting rule the PMS plan must operationalise.
- [PMCF under MDR — a guide for startups](/blog/pmcf-mdr-guide-startups) — the clinical arm of the PMS system.
- [Serious incidents under MDR — definition and reporting](/blog/serious-incidents-mdr) — the vigilance reporting channel PMS feeds into.
- [Risk management file updates driven by PMS](/blog/risk-management-file-pms-updates) — the feedback loop into EN ISO 14971:2019 + A11:2021.
- [Clinical evaluation update cycles under Article 61](/blog/clinical-evaluation-update-cycles) — the feedback loop into the CER.
- [The Subtract to Ship framework for MDR compliance](/blog/subtract-to-ship-framework-mdr) — the methodology behind the lean PMS package test.

## Sources

1. Regulation (EU) 2017/745 of the European Parliament and of the Council of 5 April 2017 on medical devices, Article 10(9) (QMS obligation), Article 83 (post-market surveillance system of the manufacturer), Article 84 (post-market surveillance plan), Article 85 (post-market surveillance report), Article 86 (periodic safety update report), and Annex III (technical documentation on post-market surveillance). Official Journal L 117, 5.5.2017.
2. MDCG 2025-10 — Guidance on post-market surveillance of medical devices and in vitro diagnostic medical devices. Medical Device Coordination Group, December 2025.
3. EN ISO 13485:2016 + A11:2021 — Medical devices — Quality management systems — Requirements for regulatory purposes.
4. EN ISO 14971:2019 + A11:2021 — Medical devices — Application of risk management to medical devices.

---

*This post is a deep dive in the Post-Market Surveillance & Vigilance series of the Subtract to Ship: MDR blog. Authored by Felix Lenhard and Tibor Zechmeister. Articles 83 to 86 are the legal backbone of every PMS system in the MedTech industry — understanding them article by article is what separates a PMS package that survives audit from one that generates findings.*

---

*This post is part of the [Post-Market Surveillance & Vigilance](https://zechmeister-solutions.com/en/blog/category/pms-vigilance) cluster in the [Subtract to Ship: MDR Blog](https://zechmeister-solutions.com/en/blog). For EU MDR certification consulting, see [zechmeister-solutions.com](https://zechmeister-solutions.com).*