Feature guide

PMS Report and PSUR Data, Without the Spreadsheet

By Kieran Redington, Founder of MedFortis Published 29 October 2026 ~6 min read

Ask anyone who has written a PSUR what took the longest, and it's rarely the writing. It's the gathering: rerunning last year's searches, exporting adverse events, chasing down recalls for similar devices, screening the literature and then working out what changed since the last report. Most of that work is the same every cycle, and most of it is done by hand.

What external data the reports need

Under the EU MDR, Class I devices need a PMS report (Article 85) and Class IIa, IIb and III devices need a periodic safety update report, or PSUR (Article 86). The differences are covered in our PSUR vs PMS report guide. Both draw on the same kinds of outside information:

Why gathering it takes so long

Each source has its own website, search syntax and export format. Searches from last cycle have to be found and rerun with new dates. Counts have to be compared by hand with the previous report, which may have used slightly different searches. And when a notified body asks why a particular recall or article wasn't considered, the answer is often in someone's inbox, if it's anywhere.

For a PSUR due every year, this can take weeks. For a portfolio, it's a standing job.

The European Commission has proposed making Class IIb and III PSURs less frequent, every two years after the first. If that's adopted, there will be fewer reports, but each one will cover a longer period. Keeping the data current between reports matters more, not less, because there's more ground to cover when the report is due.

How MedFortis handles it

A data annex, on demand

MedFortis produces a data annex for your PMS report or PSUR that compares one period with the last for your devices, so you can see straight away what changed. You can run it whenever you need it, or schedule it weekly or monthly so the numbers are always current rather than assembled at the deadline.

Literature screening that keeps its reasons

A PubMed screening queue, based on the MEDDEV 2.7/1 rev 4 approach, lets your team include or exclude each article and record why. That record supports your duty under MDR Articles 83 and 84 to review external data, and it means the next report starts from where the last one finished.

Trials and trends in the same place

Terminated and suspended clinical trials in your device categories are shown first. Trend alerts flag when a device's reports rise above a threshold or above its own normal level, so a change shows up during the year, not when you sit down to write.

Drafts for a person to review

MedFortis can draft a compliance summary from the data. It's a starting point. A person reviews it, edits it and decides what goes into the report.

What it doesn't do

MedFortis doesn't write your PSUR, make your benefit-risk conclusion or replace your clinical evaluation. Sales volumes, complaint data and PMCF findings come from inside your business and stay in your QMS. It takes care of the external half of the work, the part that repeats every cycle, and keeps it up to date.

See the data behind your next report

Book a free 30-minute demo. We'll run MedFortis on your device lines and show you what an annex for them would contain.

Book a Demo →

Key takeaways

  • PMS reports (Class I) and PSURs (Class IIa, IIb, III) both need external data: adverse events, recalls, literature, trials and trends.
  • Gathering it by hand each cycle is slow, inconsistent and hard to defend when questioned.
  • MedFortis produces a period-on-period data annex on demand or on a schedule, screens literature with recorded reasons and flags trends during the year.
  • Your team still writes the report and makes the benefit-risk call.
This article is provided for general information only and is not legal or regulatory advice. Regulatory requirements are summarised and paraphrased; always refer to the official texts and guidance, and consult a qualified regulatory professional for your specific devices and markets.