EU MDR Post-Market Surveillance under Article 83: Building a Compliant PMS System

Updated: 2026-11-12 · GRZAN Regulatory Team · Verification date 2026-10-20

1. Key takeaways

Under Article 83 of Regulation (EU) 2017/745 (MDR), manufacturers must plan, establish, document, implement, maintain and update a post-market surveillance (PMS) system for each device, in a manner that is proportionate to the risk classification of the device and the type of device concerned. Article 84 requires the PMS system to be based on a post-market surveillance plan that meets the requirements set out in Section 1 of Annex III, and that plan must form part of the technical documentation described in Annex II. Article 85 separately requires manufacturers of Class I devices to prepare a post-market surveillance report.

Taken together, these three articles turn PMS into a continuous, documented and auditable activity rather than an optional quality gesture. The PMS system is the data engine of the whole post-market compliance framework: it feeds trend reporting under Article 88, supplies the evidential basis for periodic safety update reports, and provides the upstream signals that trigger vigilance reporting under Article 87. A PMS system that exists only on paper will be exposed during notified body assessments and competent authority inspections, so the system must actually run and produce records, not merely exist in the quality manual.

For compliance teams, the architecture to remember is simple: Article 83 builds the system, Article 84 turns it into a plan that lives inside the technical documentation, and Article 85 gives Class I devices their own reporting instrument. The three articles share one premise: post-market data must be generated on purpose, not discovered by accident. Organisations that assign PMS to a part-time role without resources, defined methods or named reviewers almost always fail the first notified body audit that probes the topic in depth.

2. Legal basis

The obligations summarised below derive directly from Regulation (EU) 2017/745 and its annexes.

Regulation / documentArticle(s)DateSource
Regulation (EU) 2017/745Article 83 (PMS system); Article 84 (PMS plan); Article 85 (PMS report)Adopted 2017-04-05; applicable from 2021-05-26EUR-Lex
Regulation (EU) 2017/745Annex III Section 1 (PMS technical documentation requirements); Annex IISame as aboveEUR-Lex
Regulation (EU) 2017/745Article 10(15) (manufacturer PMS obligations); Article 83(4) (corrective actions and notification)Same as aboveEUR-Lex

3. Expert insights

Insight 1: PMS is a proactive, systematic and continuous activity, not passive complaint handling.

Article 83(1) requires the PMS system to collect, record and analyse, in a proactive and systematic manner, data on the quality, performance and safety of the device throughout its entire lifetime once it has been placed on the market, and to draw the necessary conclusions and take corrective and preventive actions. Section 1 of Annex III further requires the PMS plan to cover information on serious incidents, including PSUR information, and field safety corrective actions; records of non-serious incidents and undesirable side-effects; information from trend reporting; pertinent specialised or scientific literature and publicly available databases and registers; feedback and complaints from users, distributors and importers; and publicly available information on similar devices. A system that merely logs complaints and waits for serious incidents to arrive falls clearly short of this scope.

Insight 2: The PMS plan is a component of the technical documentation, not a standalone file.

Under Article 84, except for custom-made devices, the PMS plan must form part of the technical documentation described in Annex II. The practical consequence is that the notified body reviews the PMS plan together with the rest of the technical documentation during conformity assessment, and a missing or incomplete plan directly affects the outcome of that review. Manufacturers should therefore treat PMS planning as a conformity assessment deliverable with the same rigour as clinical evaluation or risk management documents, keeping the plan synchronised with every update of the technical file rather than drafting it once and leaving it untouched for years.

Insight 3: Article 83(4) connects PMS directly to vigilance.

Under Article 83(4), where the PMS process identifies a need for preventive or corrective measures, the manufacturer must implement appropriate measures and inform the competent authorities concerned, and, where applicable, the notified body. Where a serious incident is identified or a field safety corrective action is taken, the matter must be reported in accordance with Article 87. PMS is therefore the upstream data source of the vigilance system: the quality of incident triage and signal detection inside PMS determines whether vigilance deadlines can be met reliably when an event escalates.

Insight 4: PMS data must support the calculation of rates, not just absolute counts.

Annex III requires the PMS plan to specify the methods for collecting and processing the information it covers. Trend judgements under Article 88 depend on incidence rates rather than raw complaint volumes, so the PMS database must also record sales, installations and volumes of use as denominators (a practical estimate). Without denominators, a rising complaint count cannot be distinguished from rising sales, and the database cannot support the trend reporting obligation at all.

4. Practical recommendations

The measures below convert the three articles into an operating workflow suitable for a mid-size manufacturer and can be scaled to the size of the device portfolio.

  1. Build the PMS plan item by item against Section 1 of Annex III, defining data sources, collection frequency, review owners and thresholds.
  2. Include the PMS plan in the technical documentation and update it in step with the technical file, as required by Article 84.
  3. Establish a complaint triage flow with a defined decision path from complaint to incident to serious incident, including time limits (a practical estimate) that support the Article 87 deadlines.
  4. Record both incident counts and sales or usage volumes in the PMS database so that trend calculations are possible.
  5. For Class I devices, prepare the PMS report under Article 85, update it where necessary, and make it available upon request by a competent authority.

5. Verification checklist

Use the checklist below before a notified body assessment or a competent authority inspection to confirm that the system described above is actually operating.

  • □ PMS system has been established and documented in accordance with Article 83
  • □ PMS plan conforms to Section 1 of Annex III and is included in the technical documentation (Article 84)
  • □ PMS data include sales or usage denominators
  • □ A decision path from complaint to incident to serious incident has been established
  • □ Corrective action and notification processes under Article 83(4) are in place
  • □ PMS report for Class I devices has been prepared (Article 85)

Regulatory information verified as of 29 October 2026.

GRZAN regulatory support. GRZAN assists medical device manufacturers with post-market compliance in the European Union market under Regulation (EU) 2017/745, covering vigilance reporting, field safety corrective action (FSCA) recalls, PMS and PSUR preparation, and responses to competent authority inspections and market surveillance enquiries. If you need support with your EU MDR post-market obligations, contact info@grzanglobal.com.

Disclaimer

Prepared by GRZAN from publicly available regulation. It is provided for general information only and does not constitute legal advice. Legislation and official fees are subject to change by the competent authority.

About GRZAN

GRZAN (Global Regulatory Zone Access Navigator) — the global market-access navigator for medical devices and IVDs.

GRZAN is a specialist consultancy for medical device and IVD market access, providing end-to-end regulatory solutions across the product lifecycle and making international market entry simpler and faster.

Key figures. More than 25 wholly owned subsidiaries worldwide covering 50+ countries and regions; chosen by 100+ listed and leading Chinese device manufacturers, with 4,000+ successful cases; 12+ years in the sector and 200+ regulatory training sessions and seminars delivered.

What we do. Global market access: multi-country registration programmes, technical documentation, regulatory advice. Clinical evidence: clinical evaluation reports (CER), usability studies, overseas clinical investigations. Quality systems: ISO 13485, MDSAP, FDA QMSR and BGMP implementation and audit readiness. Authorised representative and licence-holder services across Southeast Asia, Latin America, the Middle East, Africa, Europe and North America.

Why GRZAN. A real operating entity, with the certificate held by the manufacturer: our direct overseas subsidiaries act as the compliant local holder, so the regulatory relationship stays clear and you keep control rather than being tied to a distributor. Direct access to the team: no time-zone gap, no language barrier, no cultural gap. Review points anticipated: we know what FDA 510(k), EU MDR, Southeast Asian, Latin American and Middle Eastern reviewers look for, which shortens timelines and reduces deficiency letters. Pathway planning: pre-decision analysis and risk assessment before you commit.

Every engagement rests on three commitments: efficiency through pre-submission review, certainty through a clear pathway, and stability through a licence-holder that stays in place.

Take your devices global with GRZAN

We work with manufacturers worldwide to open new markets with a clear regulatory pathway.

Contact us
WhatsApp
QR Code
WhatsApp QR Code
Scan to chat on WhatsApp
Phone
Call
Office Mon-Fri 9:00-18:00
0755-88659477
Mobile 24/7 Service
+86 15816864648
Email
Mail