SSCP in EUDAMED: What Patients Will Actually Read About Your Device
Most manufacturers focus on completing their technical documentation, CER, and PMCF. Then EUDAMED registration arrives. Suddenly, you must write for patients. Not regulators. Not clinicians. Patients. And most companies realize too late that this is not a summary exercise. It is a transparency requirement with legal and reputational consequences.
In This Article
The Summary of Safety and Clinical Performance, or SSCP, is not just another regulatory document to check off. It is the first piece of clinical information about your device that patients, healthcare professionals, and the public can access directly through EUDAMED.
Under MDR Article 32, this document must be published for Class III devices and implantable devices. It becomes publicly available. It sits next to your device registration. And it must be written in language that a layperson can understand.
This changes everything.
Why the SSCP Exists
The MDR introduced the SSCP to increase transparency. Before the regulation, clinical information remained locked inside technical files and CERs. Patients had no direct access to performance data, clinical evidence, or residual risks.
Now, they do.
The SSCP is the patient-facing clinical document. It must summarize the device, its intended purpose, its clinical benefits, and its risks. It must reference the clinical evaluation. It must present residual risks clearly. And it must do all of this without hiding behind technical jargon.
MDCG 2019-9 provides the template and the guidance. But many manufacturers treat this document as a compliance formality. They compress the CER into shorter paragraphs and call it done.
That is not what regulators expect. And it is not what patients need.
What Must Be Included
The SSCP follows a fixed structure defined in MDCG 2019-9. Each section has a purpose. Each section will be read by reviewers, patients, and possibly lawyers.
The document must include:
Device identification and general information. This is straightforward. Name, model, UDI-DI, intended purpose, patient population. But even here, clarity matters. If your intended purpose is vague in the technical file, it will be vague here too.
Clinical benefits and performance. This section summarizes what the device does clinically. Not what it claims to do. What it actually does based on evidence. If your CER shows limited clinical data, this section will reflect that limitation.
Residual risks and undesirable side effects. This is where most manufacturers hesitate. You must present risks clearly. Not minimized. Not buried in statistical language. If infection is a known complication, it must be stated. If device failure has occurred in post-market data, it must be mentioned.
Reference to harmonized standards and common specifications. This shows alignment with regulatory expectations. But it is also a signal to patients that your device meets defined safety benchmarks.
Summary of clinical evaluation and follow-up. This is not the full CER. But it must reference the clinical data, the evidence base, and the PMCF activities. If your PMCF is weak, this section will expose it.
The SSCP is not a marketing document. It is a transparency document. If your clinical evidence is thin, the SSCP will show it. If your risk management is incomplete, the SSCP will reflect it. This is intentional.
The Language Challenge
Here is where most submissions fail.
The SSCP must be understandable to a layperson. That means no technical abbreviations without explanation. No assumption of medical knowledge. No complex statistical phrasing.
But it must also remain accurate. You cannot oversimplify to the point of distortion. You cannot omit risks to make the device sound safer. You cannot exaggerate benefits to make the device sound better.
This balance is difficult.
I have reviewed SSCPs where the language was so technical that even a healthcare professional would struggle. I have also seen SSCPs where risks were described so vaguely that they became meaningless.
Both approaches fail.
The reviewers at Notified Bodies and competent authorities check for clarity. But they also check for honesty. If the SSCP does not align with the CER, you will receive deficiencies. If the risks in the SSCP do not match the risks in your risk management file, the inconsistency will be flagged.
Publication and Updates
Once the SSCP is approved, it must be published in EUDAMED. It becomes publicly accessible. It stays there. And it must be updated.
Under MDR Article 32, the SSCP must be updated at least annually. Or whenever there is a significant change in the clinical data, performance, or safety profile.
This is not optional.
If you conduct a PMCF study and identify a new risk, the SSCP must reflect it. If post-market surveillance shows a higher incidence of a complication than initially expected, the SSCP must be revised. If your CER is updated with new literature or clinical data, the SSCP must follow.
This means the SSCP is not a one-time task. It is part of your ongoing clinical and post-market obligations.
Many manufacturers publish the SSCP at certification and then forget about it. Years pass. Post-market data accumulates. The CER is updated. But the SSCP remains unchanged. This is a non-compliance that competent authorities will eventually catch.
What Reviewers Check
When a Notified Body reviews your SSCP, they are checking for alignment. Does this document match your CER? Does it match your risk management file? Does it match your IFU?
They also check for transparency. Are the risks presented honestly? Are the benefits supported by evidence? Is the language accessible?
And they check for completeness. Did you address every section in MDCG 2019-9? Did you reference the clinical data correctly? Did you describe the PMCF plan?
If any of these checks fail, you receive deficiencies. And unlike some other documents, the SSCP cannot be fixed with minor edits. It often requires rethinking how you present your clinical evidence.
Why This Matters Beyond Compliance
The SSCP is more than a regulatory requirement. It is a public statement about your device.
Patients will read it. Healthcare professionals will read it. Competent authorities will monitor it. And if a serious incident occurs, investigators will compare it to your post-market data.
If your SSCP presents a risk as rare, but your vigilance reports show multiple cases, there will be questions. If your SSCP describes a clinical benefit that is not supported by your PMCF data, that inconsistency will surface.
This is why the SSCP must be treated seriously from the start. Not as a summary task at the end of your submission. But as a document that reflects the integrity of your entire clinical evaluation process.
Practical Implications
For regulatory and clinical teams, this means planning ahead.
Start drafting the SSCP early. Use it as a test of your CER clarity. If you cannot explain your clinical evidence in layperson language, your CER may be too vague or too complex.
Involve technical writers who understand medical communication. The SSCP is not a job for engineers alone. It requires someone who can translate clinical data into accessible language without losing accuracy.
Review the SSCP alongside your CER updates. Do not treat them as separate documents. They must be consistent. Any gap between them will be noticed.
And build a process for annual reviews. Set a reminder. Assign responsibility. Make sure that post-market data, PMCF results, and vigilance trends feed into SSCP revisions.
The SSCP is a mirror of your clinical evaluation quality. If your CER is weak, the SSCP will expose it. If your risk management is incomplete, the SSCP will show it. Use this document as a quality check, not just a compliance output.
Final Thoughts
The SSCP is one of the most visible regulatory documents you will produce. It sits in EUDAMED. It is publicly accessible. And it directly reflects your clinical and regulatory rigor.
Most manufacturers underestimate it. They see it as a summary task. But the SSCP is not a summary. It is a commitment. A statement of what your device does, what risks it carries, and what evidence supports it.
When you publish it, you are no longer writing for regulators. You are writing for everyone. And that changes how you must think about transparency, clarity, and accountability.
In the next part of this series, I will address another EUDAMED requirement that catches manufacturers off guard: the technical documentation summary and what it reveals about your submission readiness.
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 32, MDCG 2019-9
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 32
– MDCG 2019-9 Summary of Safety and Clinical Performance
Deepen Your Knowledge
Read Complete Guide to Clinical Evaluation under EU MDR for a comprehensive overview of clinical evaluation under EU MDR 2017/745.
