Which devices need an SSCP?
The EU MDR trigger is specific: implantable devices and class III devices need an SSCP unless they are custom-made or investigational devices. Do not create the answer from a broad risk label alone; confirm classification, implantable status, intended purpose, and whether an exclusion applies.
The SSCP is not a marketing brochure, instructions for use replacement, implant-card replacement, or general treatment guide. Its purpose is public access to an updated summary of clinical data and other safety and clinical performance information for the device.
- Manufacturer role: draw up the SSCP, source it from technical documentation, keep it updated, manage translations, and verify the needed EUDAMED uploads before placing the device on the relevant market.
- Notified body role: validate the draft against required content and current technical documentation, upload validated SSCPs to EUDAMED, and consider PMS, PSUR, PMCF plan, PMCF evaluation report, and other relevant information during surveillance.
- EUDAMED role: make the SSCP publicly available and link it to the Basic UDI-DI; the public availability caveat is that some implantable class IIa and some class IIb implantable SSCP revisions may be uploaded before notified-body validation, so the revision history should state validation status.
Article 32 is the binding source for the SSCP trigger, manufacturer duty, notified-body validation, EUDAMED upload, public availability, and label or IFU reference.
MDCG guidance for SSCP presentation, content, validation, translations, revision history, and EUDAMED upload mechanics.
Commission EUDAMED source for the database role in transparency and device lifecycle information.