Why your PSUR is not just a compliance formality

Written by HATEM RABEH, MD, MSc Ing

Your Clinical Evaluation Expert And Partner

in
S

I see this pattern in almost every PSUR review. The report exists. The data is presented. But the document fails to fulfill its actual regulatory purpose under MDR Article 86.

The reason is simple. Many teams treat the PSUR as a reporting obligation rather than as a continuous safety and performance evaluation tool. They compile data. They list incidents. They describe complaint trends. But they stop short of the analytical work that turns a PSUR into evidence of responsible post-market oversight.

Let me walk through what Article 86 actually requires, why it matters beyond compliance theater, and what makes a PSUR defensible when a Notified Body or authority reviews it.

What Article 86 actually mandates

Article 86 of the MDR establishes the requirement for manufacturers to prepare a PSUR for certain device classes. The regulation specifies that the PSUR must include:

• A summary of the results and conclusions of the analyses of post-market surveillance data
• A rationale and description of any preventive and corrective actions taken
• Conclusions on the benefit-risk determination
• The main findings of the PMCF

This is where the misunderstanding starts. Many teams read this list and think it means presenting data summaries. But the regulation asks for something different. It asks for conclusions drawn from analysis.

That shift from reporting to reasoning is what most PSURs miss.

Who must submit a PSUR and when

Not all devices require a PSUR. The obligation applies to Class IIa, IIb, and III devices. Class I devices are generally exempt unless they have a measuring function or are reusable surgical instruments.

The frequency depends on device class. For Class IIa devices, a PSUR must be updated at least every two years. For Class IIb and III devices, at least annually. For implantable devices, the expectation is annual and sometimes more frequent depending on risk profile and post-market findings.

These timelines are not arbitrary. They reflect the regulatory expectation that higher-risk devices require more frequent reassessment of their safety and performance in real-world use.

But here is where things go sideways. Some manufacturers interpret the timeline as a deadline for document submission. They wait until the last moment. They rush to compile whatever data is available. The result is a reactive document instead of a continuous evaluation process.

The PSUR timeline should drive your post-market surveillance activities, not just your reporting schedule.

The structure that actually works

A compliant PSUR follows a logical progression. It starts with device identification and the scope of the report. It moves through post-market surveillance data. It analyzes trends, incidents, complaints, and vigilance reports. It integrates PMCF findings. It revisits the benefit-risk determination. It documents corrective and preventive actions.

But structure alone does not make a PSUR defensible. What matters is whether each section answers a critical question.

For the post-market surveillance data section: Have you captured all relevant sources? Are you analyzing trends or just listing events? Are you comparing current data with previous periods?

For the incident and complaint analysis: Are you identifying patterns? Are you linking complaints to potential safety issues? Are you explaining why certain trends do not require action?

For the PMCF findings: Are you integrating clinical data into your safety assessment? Are you showing how real-world evidence supports or challenges your claims?

For the benefit-risk conclusion: Are you explicitly stating whether the balance remains favorable? Are you justifying that statement with data? Are you transparent about uncertainties?

These are the questions a reviewer asks. If your PSUR does not answer them clearly, it will fail.

The benefit-risk reassessment trap

This is where most PSURs collapse under scrutiny. The benefit-risk section often reads like a formality. A single sentence stating that the balance remains favorable. No supporting argument. No reference to data. No acknowledgment of new risks or performance concerns.

The MDR requires manufacturers to continuously evaluate the benefit-risk profile. That means revisiting it with new data. If incidents have increased, explain why the risk remains acceptable. If performance complaints have emerged, show how they fit within expected variability or describe what you are doing about them.

If you are just repeating the same benefit-risk statement from the previous PSUR, you are not complying. You are documenting the absence of evaluation.

I have seen manufacturers face findings for this exact issue. The Notified Body pointed to unchanged benefit-risk language despite a documented increase in complaints. The manufacturer had no response because they had not actually reassessed anything. They had copied text from the last submission.

The lesson is clear. The benefit-risk section must reflect current evidence. If the conclusion is unchanged, explain why based on the latest data. If the conclusion has shifted, document the reasoning and any actions taken.

How PMCF findings integrate into the PSUR

The PSUR must include the main findings of your PMCF activities. This is not optional. It is a direct requirement under Article 86.

Many manufacturers struggle with this because their PMCF plan and PSUR are managed separately. The PMCF is handled by clinical affairs. The PSUR is handled by post-market surveillance or regulatory. The result is a disconnection. PMCF findings exist but are not meaningfully integrated into the PSUR analysis.

This is a structural mistake. The PSUR is the place where post-market surveillance data and clinical follow-up converge. It is where you demonstrate that real-world evidence supports your claims and that you are actively monitoring performance beyond initial clearance.

If your PMCF plan generated new data, that data must appear in your PSUR. If your PMCF is ongoing, the PSUR must explain what has been observed so far. If your PMCF has been delayed, the PSUR must acknowledge that and explain the impact on your benefit-risk assessment.

There is no acceptable scenario where the PSUR ignores PMCF.

Preventive and corrective actions: when absence is a problem

A PSUR without documented corrective or preventive actions often raises a red flag. Not because every period requires action, but because the absence of action must be justified.

If your post-market data shows no concerning trends, state that explicitly. Explain what you monitored and why no action was required. Show that you evaluated the data and concluded that current controls are sufficient.

If issues were identified but not acted upon, explain why. Perhaps the issue is within acceptable limits. Perhaps the root cause is being investigated. Perhaps a risk-benefit analysis determined that the current profile is still favorable.

What you cannot do is remain silent. Silence implies either that you did not analyze the data or that you chose not to act without justification.

I have reviewed PSURs where incidents were listed, trends were visible, and the corrective action section was blank. When asked, the manufacturer said they did not think the issue warranted action. That may be true. But without documenting the reasoning, the PSUR fails to demonstrate responsible oversight.

What happens when the PSUR is submitted

The PSUR is submitted to the Notified Body as part of ongoing surveillance. For high-risk devices, it may also be submitted to competent authorities upon request. The expectation is that the document will be reviewed and assessed.

Reviewers look for coherence. Does the data support the conclusions? Are trends explained? Are actions proportional to findings? Is the benefit-risk assessment current?

If the PSUR is weak, findings follow. The Notified Body may request clarification. They may ask for additional analysis. They may question whether your post-market surveillance system is functioning as required.

In severe cases, a deficient PSUR can trigger a broader audit. If the report suggests that you are not monitoring safety and performance adequately, the Notified Body may examine your entire post-market surveillance process.

This is why the PSUR cannot be an afterthought. It is a window into your post-market oversight. If that window reveals gaps, you will face scrutiny.

The PSUR as a living document

The best PSURs are not written in a rush. They are built continuously. Post-market data is collected throughout the period. Trends are analyzed as they emerge. PMCF findings are integrated in real time. The PSUR becomes a summary of work already done, not a scramble to compile data at the deadline.

This approach requires coordination. Your post-market surveillance team, clinical affairs, regulatory, and quality must align. They must agree on what data matters, how trends are interpreted, and when action is required.

When that alignment exists, the PSUR reflects a functioning system. When it does not, the PSUR reveals dysfunction.

I see this clearly when reviewing technical documentation. Some manufacturers have PSURs that read like coherent narratives. The data flows logically. The conclusions are justified. The actions make sense. These are teams that have integrated post-market surveillance into their operations.

Other manufacturers have PSURs that feel bolted together. Data from different sources does not align. Conclusions are vague. Actions are mentioned without context. These are teams that are reacting to a deadline, not managing a continuous process.

The difference is not about resources. It is about mindset. The PSUR is either treated as a compliance document or as a tool for ongoing oversight. The former leads to findings. The latter leads to defensible evidence.

Where this connects to the broader MDR framework

The PSUR does not exist in isolation. It is part of the MDR’s integrated approach to lifecycle oversight. It connects to your post-market surveillance plan, your PMCF plan, your Clinical Evaluation Report, and your risk management file.

The CER establishes initial clinical evidence. The PMCF plan describes how you will monitor performance after market entry. The PSUR demonstrates that you are executing that plan and using the data to reassess benefit-risk. The post-market surveillance plan defines your data sources and monitoring processes. The PSUR is the output of those processes.

If any of these documents are weak, the PSUR will expose it. A PSUR cannot compensate for inadequate PMCF. It cannot justify claims that were never validated in the CER. It cannot manufacture conclusions from missing data.

This is why the PSUR often becomes the moment when regulatory weaknesses surface. It is the first time a Notified Body or authority sees your post-market evidence compiled and analyzed. If that evidence is insufficient, you will face questions that go beyond the PSUR itself.

The PSUR is not just a report. It is a test of whether your post-market surveillance system is working as the MDR requires.

What this means for your next PSUR

If your next PSUR is approaching, start by asking whether your post-market surveillance data is truly being analyzed. Are you tracking trends or just logging events? Are you integrating PMCF findings or treating them as separate? Are you reassessing benefit-risk or repeating old conclusions?

If the answer to any of these questions is unclear, your PSUR is at risk of being deficient.

The solution is not to write a better report. The solution is to strengthen the processes that feed the report. Fix the data collection. Improve the trend analysis. Align PMCF and post-market surveillance. Document your reasoning as you go.

When you do that, the PSUR becomes straightforward. It is a summary of work that has already been done, not a last-minute effort to manufacture compliance.

That is the difference between a PSUR that passes review and one that triggers findings. Not the writing. Not the formatting. The substance. The evidence that you are actually monitoring your device and acting on what you find.

This is what Article 86 requires. This is what reviewers expect. And this is what separates responsible manufacturers from those who treat post-market surveillance as a regulatory formality.

Peace,
Hatem
Clinical Evaluation Expert for Medical Devices
Follow me for more insights and practical advice.