When Your PSUR Can’t Wait Until Next Year
I reviewed a PSUR last week that was six months old and already obsolete. The manufacturer had just received three serious adverse event reports, but they were waiting for the annual deadline to update the document. Their Notified Body disagreed. Strongly.
In This Article
The annual PSUR deadline creates a comfortable rhythm for regulatory teams. Submit in Q1, relax until next year, maybe update if time allows before the audit. But that rhythm breaks the moment something significant happens. And under MDR, the threshold for “significant” is lower than many teams assume.
This is the fourth post in the SSCP & PSUR series. We’ve covered structure, methodology, and integration with the CER. Now we address timing. Because submitting on schedule means nothing if the content is already outdated when it reaches the reviewer.
What the Annual Deadline Actually Means
MDR Article 86 requires manufacturers to prepare a PSUR at least annually. That establishes the outer limit, not the standard. The regulation also states that PSURs must be updated whenever necessary based on new information from post-market surveillance activities.
The word “whenever” matters. It removes the safety net of waiting until the calendar tells you to act. Instead, you must evaluate continuously whether new data triggers an update obligation.
MDCG 2022-21 reinforces this by clarifying that the PSUR is a living document, reflecting the current state of post-market data. If that state changes materially, the document must change too.
The annual deadline is a regulatory minimum, not a safe harbor. Significant post-market events create their own deadlines, regardless of your submission schedule.
What Triggers an Interim Update
The regulation does not provide an exhaustive list. That is intentional. The trigger depends on the nature of the device, the risk profile, and the significance of the new information. But certain categories recur in audit findings and Notified Body requests.
Serious Adverse Events and Field Safety Corrective Actions
Any serious adverse event that affects the benefit-risk profile triggers immediate evaluation. Not every serious event requires a PSUR update, but you must document the decision either way.
If the event leads to a Field Safety Corrective Action, the PSUR must reflect that action. The timing here is critical. The FSCA itself must be reported within defined timelines. The PSUR should be updated shortly after, before the next surveillance audit.
I have seen manufacturers report an FSCA in June and leave the PSUR unchanged until the following March. The auditor asks why the serious event is not reflected in the summary. The answer is usually, “We were waiting for the annual update.” That answer does not satisfy anyone.
Trend Data from Complaint Analysis
A single complaint rarely triggers an update. A pattern does. If your complaint trending shows an increase in a specific failure mode, or a new type of complaint emerges across multiple batches, that trend must be evaluated.
The challenge here is recognizing when isolated events become a trend. Many teams wait too long. They treat each complaint as independent until the pattern becomes undeniable. By then, the PSUR is already behind.
The practical test: if the trend would change your risk assessment or clinical evaluation, it belongs in the PSUR now, not next year.
Manufacturers often track complaint trends in separate systems without linking them to the PSUR. This creates a documentation gap where significant patterns are known internally but not reflected in the regulatory summary.
New Clinical Data or Literature Findings
If new clinical evidence contradicts your existing benefit-risk conclusions, the PSUR must be updated. This includes data from your own PMCF studies and relevant publications identified through literature surveillance.
The timing here depends on the nature of the finding. A large systematic review challenging the safety of your device class requires immediate action. A single case report with unclear relevance can wait for the annual update, provided you document the evaluation.
The key question: does this new information change what you would tell a clinician about the device? If yes, update the PSUR. If no, document why not.
Regulatory Actions or Market Withdrawals in Your Device Category
When a competitor withdraws a similar device or a regulatory authority issues a safety communication about your device category, you must evaluate the relevance to your own product.
Even if the action does not directly concern your device, the PSUR should reflect your analysis. Notified Bodies and competent authorities will ask. They want to see that you are aware of the market context and have assessed the implications.
I reviewed a PSUR for an implantable device where a major competitor had recalled a similar product six months earlier. The manufacturer’s PSUR made no mention of it. During the review, the question came immediately: “Are you aware of the recall? What is your position?” The manufacturer was aware. They had analyzed it internally. But the PSUR was silent. That silence creates doubt.
How to Structure Interim Updates
An interim PSUR does not mean starting from scratch. You are updating specific sections to reflect new data, not rewriting the entire document.
The structure should follow your original PSUR format. The difference is in the scope and the level of detail. Focus on what has changed and why it matters.
Executive Summary and Conclusion Updates
Always update the executive summary and conclusion, even if the changes are localized to one section. These are the first places reviewers look to understand what has changed and whether the benefit-risk balance remains favorable.
State clearly what triggered the update. Be direct. Do not bury the reason in the appendices or assume the reviewer will infer it from the data.
Updated Data Sections
Include the new data in the relevant sections: complaints, adverse events, PMCF findings, literature. Provide context. Show how the new data relates to previously reported information.
If the new data changes a trend, say so. If it confirms existing conclusions, state that too. The reviewer needs to see your reasoning, not just the numbers.
Risk-Benefit Re-evaluation
If the new data affects the benefit-risk profile, include an updated risk-benefit analysis. This does not need to be exhaustive, but it must address the specific change.
If the benefit-risk balance remains positive, explain why. If it shifts, describe the implications and any corrective actions taken or planned.
An interim PSUR is not a burden. It is a tool. It demonstrates that you are actively managing your device’s post-market performance and responding to new information in real time. Reviewers respect that.
The Link to the Clinical Evaluation Report
An updated PSUR often triggers a CER update. The two documents are interdependent. If post-market data changes your benefit-risk conclusions, those conclusions must be reflected in the CER as well.
This creates a timing challenge. Updating both documents takes time. But the regulatory expectation is clear: the CER must reflect current data. If the PSUR shows new safety concerns, the CER cannot remain silent.
The practical approach: plan CER updates alongside significant PSUR updates. Treat them as linked events, not isolated tasks. This keeps both documents aligned and reduces the risk of contradictory statements.
Documentation and Version Control
Every PSUR update must be versioned and documented. The version history should show when the update was made, what triggered it, and what changed.
This is not bureaucracy. It is evidence of your vigilance system. During audits, reviewers often ask to see the version history of key documents. They want to know if you update reactively or proactively.
A well-maintained version history shows that you respond to triggers promptly. A single annual version suggests you wait for the calendar, not the data.
Many manufacturers maintain detailed internal tracking of post-market events but fail to link those tracking records to PSUR updates. This creates an appearance of reactive updating, even when the internal process is proactive.
The Practical Reality
Interim updates add work. No one enjoys revising a document that was finalized months ago. But the alternative is worse. Outdated PSURs create regulatory risk, audit findings, and questions about your vigilance system.
The best approach is to build interim update triggers into your standard procedures. Define clear criteria for when an update is required. Assign responsibility. Make it routine.
When updating becomes part of the process, it stops feeling like a burden. It becomes evidence that your post-market surveillance system works.
The next post in this series will address how to handle conflicting data sources within the PSUR and what to do when your internal data contradicts published literature. Because that conflict is more common than most teams admit, and how you handle it defines the credibility of your entire summary.
Peace,
Hatem
Clinical Evaluation Expert for Medical Devices
Follow me for more insights and practical advice.
Frequently Asked Questions
What is a Clinical Evaluation Report (CER)?
A CER is a mandatory document under MDR 2017/745 that demonstrates the safety and performance of a medical device through systematic analysis of clinical data. It must be updated throughout the device lifecycle based on PMCF findings.
How often should the CER be updated?
The CER should be updated whenever significant new clinical data becomes available, after PMCF activities, when there are changes to the device or intended purpose, and at minimum during annual reviews as part of post-market surveillance.
What causes CER rejection by Notified Bodies?
Common reasons include inadequate equivalence demonstration, insufficient clinical data for claims, poorly structured SOTA analysis, missing gap analysis, and lack of clear benefit-risk determination. Structure and logical flow are as important as the data itself.
Which MDCG guidance documents are most relevant for clinical evaluation?
Key documents include MDCG 2020-5 (Equivalence), MDCG 2020-6 (Sufficient Clinical Evidence), MDCG 2020-13 (CEAR Template), MDCG 2020-7 (PMCF Plan), and MDCG 2020-8 (PMCF Evaluation Report). MDR Article 86, MDCG 2022-21
Need Expert Help with Your Clinical Evaluation?
Get personalized guidance on MDR compliance, CER writing, and Notified Body preparation.
✌
Peace, Hatem
Your Clinical Evaluation Partner
Follow me for more insights and practical advice.
– MDR 2017/745 Article 86
– MDCG 2022-21 Guidance on Periodic Safety Update Reports (PSUR)
Deepen Your Knowledge
Read Complete Guide to Clinical Evaluation under EU MDR for a comprehensive overview of clinical evaluation under EU MDR 2017/745.
