Regulatory guide

PSUR vs PMS Report: What's the Difference?

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

Under the EU MDR, every manufacturer has to report on its post-market surveillance, but the document you produce depends on your device's risk class. Lower-risk devices need a PMS Report (PMSR). Higher-risk devices need a Periodic Safety Update Report (PSUR). They look similar and are often confused. This guide sets out how they differ and how to tell which one applies to you.

The difference in one sentence

A PMS Report (PMSR) is the post-market surveillance summary required for Class I devices under Article 85, while a PSUR is the more detailed report required for Class IIa, IIb and III devices under Article 86. The PSUR adds a benefit-risk conclusion, PMCF findings and sales and usage data, and for the highest-risk devices it is actively reviewed by a Notified Body.

Same system, two outputs

Start with this: the PMSR and the PSUR come from the same process. They are two possible outputs of the same post-market surveillance system that every manufacturer must run under Article 83, driven by the PMS plan under Article 84. Both summarise the results and conclusions of the PMS data you collect, and both describe any preventive or corrective actions (CAPA) you took. The difference is how much more the PSUR asks for on top of that shared core, and who gets to see it. (For the full picture of the obligations these reports sit within, see our guide to EU MDR Articles 83–92.)

What is a PMS Report (PMSR)?

The PMS Report is defined in Article 85 and applies to Class I devices. It summarises the results and conclusions of the analysis of your post-market surveillance data, together with a rationale and description of any preventive and corrective actions taken.

Two things make it lighter-touch than a PSUR:

What is a PSUR?

The Periodic Safety Update Report is defined in Article 86 and applies to Class IIa, IIb and III devices. It contains everything a PMSR does, and then adds the elements that let a reviewer judge whether the device's benefit-risk balance still holds:

Unlike the PMSR, the PSUR runs on a fixed update cycle and, for higher-risk devices, is actively reviewed rather than merely held on file.

Side-by-side comparison

 PMS Report (PMSR)PSUR
RegulationArticle 85Article 86
Applies toClass IClass IIa, IIb, III
Shared corePMS data results & conclusions + rationale and description of any CAPA
Extra content—Benefit-risk conclusions, PMCF findings, sales volume, user-population estimate
Update frequencyWhen necessaryClass IIa: when necessary and at least every 2 years · Class IIb & III: at least annually
Who sees itCompetent authorities, on requestClass III & implantable: submitted through the electronic system (Eudamed) to the Notified Body, which reviews and evaluates it · Class IIa & IIb: made available to the Notified Body and, on request, to competent authorities
Part of technical documentationYesYes
Note on implantables: implantable devices follow the Class III submission route (through the electronic system to the Notified Body), whatever their class. Update frequency still follows the class: an implantable Class IIa device is updated at least every two years, and IIb and III at least annually.
Proposed change: in December 2025 the European Commission proposed amending the MDR (COM(2025) 1023). Under the proposal, PSURs for Class IIb and III devices would be due once in the first year after certification and then every two years. This is a proposal, not law yet, so the frequencies above still apply until an amended regulation is adopted and in force.

Which one does your device need?

It comes down to classification:

You prepare the report per device, though the MDR allows you to prepare it for a category or group of devices, and MDCG guidance lets you group devices that share a Basic UDI-DI into a single PSUR where defined conditions are met. If part of your portfolio is Class I and part is higher-risk, you will be producing both types of report in parallel.

Common mistakes

Keeping either report current

Whichever report you owe, it draws on the same raw material: real-world signals about your device from adverse-event databases, recall notices, literature, clinical-trial data and the open market. Writing the document is rarely what takes the time. Keeping that data current, and being able to show where each conclusion came from, usually does.

You can automate the external side of surveillance: monitor sources such as FDA MAUDE, recall notices, clinical-trial registries and unauthorised marketplace listings continuously, and log every finding with a timestamp. Your PMSR or PSUR is then built from current data instead of being pieced together from scratch each cycle, and every statement has a record behind it. It complements your QMS and clinical evaluation rather than replacing them.

See what your surveillance data looks like

Book a demo and we'll run MedFortis against your device lines to show you, live, what's coming up in FDA data, recalls, trials and the open market: the raw material behind your PMSR or PSUR.

Book a Demo →

Key takeaways

  • PMSR (Article 85) is for Class I; PSUR (Article 86) is for Class IIa, IIb and III.
  • Both share a core (PMS data conclusions + CAPA); the PSUR adds benefit-risk, PMCF findings and sales/usage data.
  • PMSR: updated when necessary, held for authorities on request. PSUR: fixed cycle (2 years for IIa; annual for IIb/III).
  • Class III and implantable PSURs are submitted through the electronic system and reviewed by the Notified Body; for other classes the PSUR is made available to the Notified Body and, on request, to competent authorities.
  • Both are only as strong as the PMS data behind them, which is where continuous monitoring pays off.
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.