Periodic Safety Update Report (PSUR) is a regulatory document that manufacturers of Class IIa, IIb, and III medical devices prepare under EU MDR 2017/745, summarizing post-market surveillance data, safety and performance findings, and benefit-risk conclusions over a defined period. Class IIa devices are updated every two years; Class IIb and III devices are updated annually.
What is a Periodic Safety Update Report (PSUR)?
A Periodic Safety Update Report (PSUR) sits inside the post-market phase of the device lifecycle, after CE marking and commercial release. It pulls together what a manufacturer has learned about a device’s real-world safety and performance since the last report: complaint trends, field safety corrective actions (FSCA), post-market clinical follow-up (PMCF) results, and vigilance data, then draws conclusions about whether the benefit-risk profile still holds.
The PSUR is not a standalone activity. It depends on a functioning post-market surveillance (PMS) system that feeds it data continuously. Article 86 of EU MDR 2017/745 sets the legal basis, and Annex III describes what a PMS plan and PSUR must contain. For lower-risk Class I devices, the equivalent document is a Post-Market Surveillance Report (PMSR), which is simpler and not routinely reviewed by a Notified Body.
Why the Periodic Safety Update Report (PSUR) matters in medical device development
A late or thin PSUR creates real exposure. Notified Bodies review the PSUR for Class III and implantable devices as part of ongoing conformity assessment, and a report that contradicts complaint data the Notified Body already holds can trigger corrective action requests, additional audits, or a hold on certificate renewal.
There is also a patient safety dimension underneath the paperwork. The PSUR forces a manufacturer to ask, at fixed intervals, whether the device still performs the way its risk file assumed. If complaint rates are climbing or an unpredicted failure mode keeps showing up, the PSUR is often where that pattern first gets documented, ahead of any recall decision.
Cost and timeline exposure follow from both. A manufacturer that treats the PSUR as a scramble each cycle ends up pulling data from complaints, service records, and PMCF studies never structured for this purpose, which slows the report and raises the odds of reviewer gaps.
How the Periodic Safety Update Report (PSUR) works
A PSUR draws on several ongoing inputs rather than a single data pull:
- Volume of devices placed on the market and, where estimable, population and frequency of use
- A summary of complaints, serious incidents, and any trend reports filed with competent authorities.
- Results and conclusions from PMCF activities, or a documented justification if PMCF was not required
- Any preventive or corrective actions taken, including FSCAs, and their outcomes
- An updated benefit-risk determination, cross-referenced to the risk management file under ISO 14971
Class IIb and III devices update the PSUR at least annually as part of their technical documentation; Class IIa devices update it when necessary and at least every two years. Only Class III and implantable devices go further: their PSUR is submitted through EUDAMED for Notified Body review, with the evaluation recorded there. Class IIa and IIb PSURs stay within the technical documentation, available to the Notified Body or authorities on request.
The underlying quality system matters too. A PSUR produced under a mature ISO 13485 quality system, with complaint handling and CAPA processes that already generate structured, dated records, is easier to compile than one assembled from scattered spreadsheets.
Common challenges and best practices
The most common mistake is treating the PSUR as a document exercise rather than an output of ongoing surveillance. Teams that only think about PMS data once a year end up reconstructing timelines from memory and email threads, leaving gaps a Notified Body will notice.
Another frequent issue is confusing the PSUR with the PMCF report or the PMSR. They are related but distinct: PMCF results feed into the PSUR as one input among several, and the PMSR is the Class I equivalent, with lighter requirements and no routine Notified Body review.
Good practice starts with a PMS plan that defines which data sources feed the PSUR and who owns each one. Building the PSUR incrementally, with a running draft updated as data comes in, keeps the report accurate and cuts the scramble before a deadline. Cross-referencing PSUR conclusions back to the ISO 14971 risk file, rather than treating them as separate documents, also holds up better under Notified Body scrutiny.
How SJML helps with the Periodic Safety Update Report (PSUR)
SJML’s QARA team supports post-market surveillance planning and PSUR and PMSR preparation as part of its managed compliance services, alongside PMCF planning, vigilance and adverse-event handling, and complaint intake tied to root-cause analysis and CAPA. This work sits within SJML’s broader regulatory sustenance offering, which also covers technical documentation, ISO 13485 quality system support, and EUDAMED submissions. Because these services scale from startups building their first PMS process to larger OEMs managing an established device portfolio, SJML can take on as much or as little of the PSUR workflow as a team needs.
Frequently asked questions
Class IIa devices need an updated PSUR at least every two years. Class IIb and III devices, along with all implantable devices, need to be inspected at least annually. The frequency is tied to device classification under EU MDR 2017/745, not to a manufacturer’s internal reporting calendar.
Both summarize post-market surveillance data, but a PSUR applies to Class IIa, IIb, and III devices and, for higher-risk classes, goes through Notified Body review via EUDAMED. A Post-Market Surveillance Report (PMSR) applies to Class I devices, carries lighter content requirements, and is not routinely submitted for review.
For Class III and implantable devices, yes: the PSUR goes through EUDAMED and receives a Notified Body evaluation as part of conformity assessment. For Class IIa and IIb devices, it is generally kept within the technical documentation and made available on request.
Yes. EU IVDR 2017/746 includes an equivalent requirement under Article 81 for Class B, C, and D in vitro diagnostic devices, following a similar structure and update frequency to the MDR PSUR, administered through the same EUDAMED framework.
A PSUR draws on complaint and vigilance data, PMCF results, sales and usage volume where it can be estimated, and any corrective or preventive actions taken during the reporting period, all rolled into an updated benefit-risk conclusion for the device.
Related terms
- Post-Market Surveillance (PMS)
- Post-Market Clinical Follow-up (PMCF)
- Post-Market Surveillance Report (PMSR)
- Clinical Evaluation Report (CER)
- EUDAMED
