PSUR vs PMSR: Class-Based Reporting Requirements Under EU MDR

Two reports, two different obligations

One of the most common points of confusion in EU MDR post-market surveillance is treating the PSUR and the PMSR as interchangeable. They are not. They serve related but distinct purposes, apply to different device classes, and have different update requirements. Getting this wrong is one of the more reliable ways to pick up an audit finding.

The short version: Class I devices produce a Post-Market Surveillance Report (PMSR). Class IIa, IIb, and III devices produce a Periodic Safety Update Report (PSUR). The PSUR is the more demanding document — it requires synthesis of all post-market data against a structured benefit-risk framework. The PMSR is simpler, but it still needs to be substantive.

PMSR — Class I devices

The Post-Market Surveillance Report is required under Article 85 for Class I devices. It must summarise the results of the PMS plan and present conclusions about the continued acceptability of the device's benefit-risk profile.

There is no fixed update interval in MDR for the PMSR — the regulation says it must be updated "when necessary." In practice, this means you should update it when:

• Your PMS data reveals a significant new finding or trend
• You make a design change that affects safety or performance
• New literature emerges that changes the benefit-risk picture
• A competent authority or Notified Body requests it

"When necessary" is not a licence to never update it. If your last PMSR is three years old and no one has reviewed it, that's a gap an inspector will notice.

The PMSR must be part of your technical documentation and available to competent authorities on request. Class I manufacturers are not subject to Notified Body oversight in the same way as higher-class devices, but competent authorities can and do audit them.

PSUR — Class IIa, IIb, and III devices

The Periodic Safety Update Report is governed by Article 86. It applies to all devices in Classes IIa, IIb, and III, including devices that gained CE marking under MDD and are operating under transitional provisions.

The update intervals are:

• Class IIb and III: at minimum annually
• Class IIa: at minimum every two years

"At minimum" means more frequently if your PMS data warrants it. If you detect a significant signal mid-cycle, you do not wait for the annual update — you produce an unplanned PSUR update and document why.

For Class IIb and III devices, the PSUR must be submitted to your Notified Body for review. For Class IIa devices, the PSUR must be available to the Notified Body on request — it is not submitted proactively unless the NB specifies otherwise.

The PSUR must be lodged in EUDAMED. The EUDAMED vigilance and PMS module has been phased in, and manufacturers of IIb and III devices in particular should verify their EUDAMED registration and reporting obligations are current.

What the PSUR must contain

The PSUR synthesises all post-market data for the device into a structured benefit-risk assessment. Article 86 sets out the required content:

• Conclusions from the PMS plan analysis, including volume of devices sold and user population characteristics
• A summary of significant findings from PMCF activities (PMCF evaluation report — a key input, discussed below)
• Literature review results for the device and similar/equivalent devices
• Complaint and incident data analysis, including trends
• Information from the vigilance system
• Information on field safety corrective actions
• An updated benefit-risk determination
• Assessment of whether the instructions for use and product labelling remain appropriate
• Conclusions on whether the device continues to meet the GSPR

This is a synthesis document, not a collection of raw data. The PSUR must reach conclusions — not just present information — and those conclusions must be traceable back to the evidence.

The PMCF evaluation report is not the PSUR

This is worth stating clearly because the two are often conflated, particularly by teams new to MDR. The PMCF evaluation report is an output of your PMCF activities — it evaluates the data gathered through PMCF (registries, surveys, literature, clinical follow-up studies) and presents conclusions about the device's clinical performance and safety. It is one input into the PSUR.

The PSUR draws on the PMCF evaluation report alongside all other PMS data sources to reach an overall benefit-risk conclusion. If you write the PMCF evaluation report and then copy most of it into a document called "PSUR," you do not have a compliant PSUR — you have a mislabelled PMCF evaluation report.

Common mistakes to avoid

Using the wrong document type for the device class. A Class IIa manufacturer producing a PMSR instead of a PSUR is a direct non-conformity.

Missing update intervals. A PSUR for a Class III device that hasn't been updated in 18 months — without documented justification — is a gap.

Treating the PSUR as a collection of data rather than a synthesis. The PSUR must reach conclusions. Auditors distinguish between a document that presents data and one that analyses it.

Not connecting PSUR conclusions back to the technical file. If the PSUR identifies a new risk or a change in the benefit-risk profile, that conclusion must trigger a review of the risk management file and, if warranted, the clinical evaluation report. Document that connection explicitly.

Forgetting EUDAMED submission obligations. For Class IIb and III devices, the PSUR must be submitted through EUDAMED — this is not optional.

Where to go from here

If you are building your PMS system from scratch, the PMS plan resource in this category covers what the plan itself must contain. The PSUR document structure resource goes into detail on how to organise and write the PSUR sections.