The MDR SSCP Isn’t a CE-Marking Deliverable — It Updates With Your PSUR

Article 32 of the EU MDR requires manufacturers of implantable and Class III devices to produce a Summary of Safety and Clinical Performance — a public, plain-language account of what the device is, what it does, and what the clinical evidence shows. Most teams treat it the way they treat the CE mark itself: something built once, validated by the notified body, and filed. Article 32 does not describe a static document. It describes one tied to the same review cycle as your periodic safety update report — and every update needs the notified body's sign-off again before it can replace the version the public can already see.

What the SSCP is for

The SSCP exists to give patients and healthcare professionals direct, understandable access to a device's safety and clinical performance — without requiring them to read the full clinical evaluation report or technical file. It must describe the device and its intended purpose, the intended patient population and indications, the expected clinical benefits, residual risks and side effects, alternative treatment options, and any warnings or precautions — sourced entirely from the technical documentation already built to support CE marking. Per MDCG 2019-9, the template guidance the Medical Device Coordination Group published for the document, an SSCP that contains both a patient-facing and a healthcare-professional-facing section must keep those sections distinct and separately identifiable, not blended into one narrative written for neither audience well.

The obligation that outlasts the CE mark

The MDR does not treat the SSCP as a submission artifact that becomes irrelevant once the certificate issues. It ties the summary's currency to the same clinical vigilance the regulation runs for the rest of the device's life: the SSCP is reviewed and updated as needed alongside the PSUR, which Class III and implantable devices must update at least annually. That means an SSCP is only as current as the last time someone checked it against the newest PSUR and clinical evaluation update — and on a device with several years on the market, the gap between a filed SSCP and the device's actual current risk profile can be wide if nobody owns the review.

• New adverse event trends. A signal that changes the benefit-risk picture in a PSUR or post-market surveillance report belongs in the next SSCP revision, not just the internal safety file.
• Updated clinical evidence. A refreshed clinical evaluation — new literature, new PMCF data, an expanded indication — is a trigger to revisit every claim the SSCP makes about expected benefit.
• Design or labeling changes. Anything that shifts intended purpose, patient population, or use instructions needs to be reflected before the next EUDAMED-published version goes stale relative to the device on the market.
• The notified body gate, every time. None of these updates are self-publishing — each one routes back through notified body validation before it replaces the live document.

A validated SSCP from launch tells a regulator what the device looked like at CE marking. It does not tell anyone what the device looks like now — unless someone kept it current. Why the update cycle is the real obligation

Building the SSCP as a standing process

The manufacturers who handle this well do not staff the SSCP as a one-time authoring project inside their EU MDR & IVDR strategy. They assign it to whoever owns the PSUR, put the SSCP review on the same calendar trigger, and treat notified body re-validation as a routine step in that cycle rather than a special request. That also means the SSCP's dual-audience structure — lay language for patients, technical language for healthcare professionals — gets maintained by people who understand both the clinical file and how to write for a general reader, not left to whoever drafted it once for the original submission. For devices approaching mandatory EUDAMED publication, an SSCP that has not been touched since CE marking is a visible gap the moment it goes live for public view.

None of this is exotic work. It is ownership: naming who reviews the SSCP against each PSUR cycle, and building the notified body re-validation into the timeline rather than discovering it late. Manufacturers who treat the SSCP as done at CE marking are the ones who find, at the next notified body audit or the next EUDAMED review, that their most public document is also their most out of date.