SSCP Notified Body Deficiency Response Pack for EU MDR

What This Article Covers

This article is a focused response playbook for manufacturers who have received Notified Body (NB) deficiency comments on their Summary of Safety and Clinical Performance (SSCP) under EU MDR Article 32. It explains how to decode NB comments, structure a deficiency response, fix the most common SSCP deficiencies, and prepare the revised SSCP for NB validation and EUDAMED upload.

This article covers:

• Decoding NB deficiency comments into actionable remediation items

• The deficiency response table format and supporting evidence structure

• The seven most common SSCP deficiency categories and how to fix each one

• Clinical benefit wording: how to write objective, quantified, non-promotional statements

• Residual risk language that satisfies NB reviewers

• Patient-section readability standards and testing

• CER, IFU, and risk management file alignment verification

• Translation consistency for multi-language SSCPs

• EUDAMED publication readiness checklist

• RACI for SSCP remediation projects

• Timeline and resubmission logistics

This article does NOT cover:

• How to draft an SSCP from scratch (see the SSCP guide)

• General EU MDR conformity assessment processes

• PSUR preparation or PMS plan design

• IFU drafting or translation workflows

• EUDAMED device registration basics

SSCP NB Validation Context

Regulatory Basis

Under MDR Article 32 and MDCG 2019-9 Rev.1, the SSCP must be validated by the NB before publication on EUDAMED. Validation means the NB has assessed the SSCP against the technical documentation and concluded it is a true and accurate representation of the relevant information. NB validation costs typically range from €1,200 to €4,000 per document (per MedTech Europe 2025 administrative burden data).

From May 28, 2026, EUDAMED becomes mandatory for device registration. All validated SSCPs for CE-marked Class III and implantable devices must be uploaded and publicly accessible.

The December 2025 EU reform proposal may eliminate separate NB SSCP validation in the future (SSCP would instead be reviewed as part of technical documentation during certification or surveillance). However, until that proposal is adopted and enters into force, the current validation requirement remains in effect.

Who Receives SSCP Deficiencies

Not all SSCPs go through the same validation path:

When Deficiencies Arrive

SSCP deficiencies are typically issued as part of the NB's technical documentation assessment report. They may arrive:

• During initial conformity assessment

• During re-certification (SSCP must be updated within the previous 12 months for Class III and IIb implantable devices per MDCG 2019-9 Rev.1)

• After a significant change to the device, CER, or risk management file

• When the PSUR identifies new safety data that affects the benefit-risk profile

Deficiency Response Table Format

Recommended Response Structure

Every SSCP deficiency response should use a structured table format. The NB needs to trace each comment to a specific remediation action and verify it in the revised SSCP.

Table 1: SSCP Deficiency Response Table

Response Package Composition

The complete response package should include:

1. Cover letter identifying the SSCP, device, Basic UDI-DI, NB reference, and certification scope

2. Deficiency response table (Table 1 format above)

3. Revised SSCP (clean version, with version number incremented)

4. Revised SSCP (tracked-changes version showing all modifications)

5. Supporting evidence (relevant excerpts from CER, risk management file, IFU, PSUR — not entire documents)

6. Readability test report (if patient section was revised)

7. Translation status update (if applicable — see Section 7)

The Seven Most Common SSCP Deficiency Categories

Based on NB audit data, Team-NB position papers, and industry reports (2024–2026), these are the most frequent SSCP deficiencies.

Deficiency Category 1: Inconsistency with CER

NB objection: "Data presented in SSCP Section 4.1 does not match the clinical evaluation report. The success rate cited in the SSCP (97%) differs from the CER pooled estimate (94.2%)."

Root cause: The SSCP was drafted from an earlier version of the CER, and subsequent CER updates were not reflected.

How to remediate:

• Extract all quantitative claims from the current CER and cross-reference against the SSCP

• Use the CER evidence traceability matrix as the source of truth

• Ensure the SSCP cites the same data sets, confidence intervals, and follow-up periods as the CER

• Document the CER version and date that the SSCP data is drawn from

Table 2: SSCP-CER Alignment Verification Checklist

Deficiency Category 2: Promotional Language

NB objection: "The SSCP contains promotional language including 'superior outcomes,' 'gold standard,' and 'best-in-class performance.' MDR Article 32(2) requires the SSCP to be objective and non-promotional."

How to remediate:

• Replace all comparative marketing claims with objective performance data from the CER

• Remove terms: superior, best-in-class, gold standard, leading, innovative, cutting-edge, state-of-the-art (unless defined by CER state-of-the-art analysis), revolutionary

• Replace with: specific success rates, complication rates, performance metrics with confidence intervals

Table 3: Promotional Language Replacement Guide

Deficiency Category 3: Inadequate Patient-Section Readability

NB objection: "The patient section is not written in plain language. Technical terms are not explained. Readability has not been tested with laypersons."

How to remediate:

• Target Flesch-Kincaid Grade Level 6–8 (maximum Grade 8)

• Replace every technical term with a plain-language explanation

• Test with a readability panel of 5+ laypersons (not employees)

• Include a readability test report in the response package

Plain-language rewrite examples:

Deficiency Category 4: Residual Risk Wording

NB objection: "Residual risks are described generically as 'low' without device-specific probability or severity data. The SSCP must present both favourable and unfavourable data per MDR Article 32(2)."

How to remediate:

• For each residual risk, provide: specific adverse event, probability category (with numerical rate if available), severity category, clinical context, and how the risk is managed

• Source all data from the risk management file and CER

• Present unfavourable data objectively — do not minimize

Table 4: Residual Risk Description Template

Deficiency Category 5: IFU/CER/SSCP Misalignment

NB objection: "The contraindications listed in SSCP Section 2.3 do not include 'active systemic infection' which appears in the IFU (Section 2.3.2)."

How to remediate:

• Perform a three-way alignment check: IFU ↔ CER ↔ SSCP

• Create a traceability matrix linking each SSCP claim to its source document and section

• Update the SSCP to include all contraindications, warnings, and precautions from the current IFU version

• Confirm the CER conclusions are consistent with both the IFU and SSCP

Table 5: Three-Way Alignment Matrix

Deficiency Category 6: Generic PMCF Content

NB objection: "The PMCF section (SSCP Section 4.3) describes PMCF activities in generic terms without providing status, interim findings, or timeline."

How to remediate:

• Reference the specific PMCF plan and PMCF evaluation report by document number and version

• State the current status of each PMCF activity (planned, active, completed)

• Include interim findings if available

• Provide a timeline with milestones

• Explain how PMCF data feeds back into the CER and risk management file

Deficiency Category 7: Translation Consistency

NB objection: "The French translation of SSCP Section 4.1 uses 'taux de réussite exceptionnel' which introduces promotional language not present in the English original."

How to remediate:

• Ensure translations are performed by qualified medical translators (not machine translation alone)

• Implement a translation review process: English SSCP → translation → back-translation review → reconciliation

• Confirm the NB validates only the English master SSCP; translations are the manufacturer's responsibility

• Store all language versions with clear version control

Table 6: Translation QA Checklist

Common Failure Modes and How to Avoid Them

Table 7: SSCP Deficiency Response Failure Modes

Remediation Project RACI

Table 8: SSCP Deficiency Response RACI

EUDAMED Publication Readiness Checklist

Before the notified body validates the SSCP — and before whoever currently uploads it deposits the file in EUDAMED — confirm the items below. MDCG 2019-9 still describes notified-body upload. After 28 May 2026, MDCG 2026-4 splits interim notified-body master-only upload from the later manufacturer handover; use that page for the actor and clock, and this checklist for file readiness.

Table 9: EUDAMED Publication Readiness Checklist

Response Timeline

Key Regulatory References

• MDR Article 32 — Summary of safety and clinical performance

• MDCG 2019-9 Rev.1 (March 2022) — SSCP guide and template for manufacturers and notified bodies

• Team-NB BPG V4 (April 2026) — Best Practice Guide on Technical Documentation under EU MDR 2017/745, including updated SSCP common pitfalls (e.g., patient section copying HCP section verbatim, lack of 1:1 alignment across SSCP/IFU/patient information)

• Team-NB Position Paper Rev.2 (April 2023) — Technical documentation requirements, including SSCP-specific guidance

• MDR Article 86 — Periodic safety update reports (PSUR), which feed SSCP updates

• MDR Annex XIV Part B — PMCF requirements referenced in SSCP Section 4.3

• ISO 14971:2019 — Risk management, source of residual risk data for SSCP Section 4.2

• EUDAMED Actor and Device Registration — Mandatory from May 28, 2026

Related Articles

• SSCP Safety and Clinical Performance Summary Guide

• Clinical Evaluation Report Template

• PMCF Post-Market Clinical Follow-Up Guide

• PSUR Periodic Safety Update Report Guide