SSCP Notified Body Deficiency Response Pack: How to Respond to NB Comments on Your Summary of Safety and Clinical Performance
Practical playbook for responding to Notified Body deficiencies on SSCP documents under EU MDR — response table format, clinical benefit wording fixes, residual risk language, patient readability, CER/IFU alignment, translation consistency, and EUDAMED publication readiness.
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:
| Device Class | Validation Timing | Typical Deficiency Volume |
|---|---|---|
| Class III | Every certification, re-certification, and certificate update | High (8–15 comments per validation cycle) |
| Class IIb implantable | Every certification, re-certification, and certificate update | Moderate (5–10 comments) |
| Class IIa implantable / Art. 52(4) devices | Sample assessed during initial certification; remainder over certification period | Variable (3–8 comments when selected) |
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
| NB Ref # | SSCP Section | NB Comment (verbatim) | Manufacturer Response | Revised SSCP Section/Location | Supporting Evidence Attached | Status |
|---|---|---|---|---|---|---|
| NB-001 | Section 4.1 | "Clinical benefit claims are not supported by quantitative data from the CER. Please provide specific performance metrics." | Added quantitative success rates from CER Table 12: 94.2% technical success (n=312, 95% CI: 91.1–96.5%) and 89.7% clinical success at 12 months. Removed promotional language ("excellent outcomes"). | SSCP Section 4.1, paragraph 2, Table 4 | CER v8.2 Table 12; Clinical investigation final report p. 47 | Closed |
| NB-002 | Section 4.2 | "Residual risk descriptions are generic. Provide device-specific probability and severity data." | Replaced generic statements with device-specific residual risk data from ISO 14971 risk management file: infection rate 2.1% (severity: serious, probability: rare), device migration 0.8% (severity: critical, probability: remote). | SSCP Section 4.2, Table 5 | Risk Management File v6.1, FMEA-023 | Closed |
| NB-003 | Section 5 (Patient) | "Patient section uses technical jargon ('biocompatible titanium alloy Grade 5'). Rewrite in plain language tested with layperson panel." | Replaced with "The device is made of a type of metal called titanium. Titanium is commonly used in implants because the body usually accepts it well." Added readability test results: Flesch-Kincaid Grade 6.2, confirmed by 5-patient readability panel. | SSCP Section 5, subsection on device description | Readability test report REV-001; Patient panel feedback forms | Closed |
Response Package Composition
The complete response package should include:
- Cover letter identifying the SSCP, device, Basic UDI-DI, NB reference, and certification scope
- Deficiency response table (Table 1 format above)
- Revised SSCP (clean version, with version number incremented)
- Revised SSCP (tracked-changes version showing all modifications)
- Supporting evidence (relevant excerpts from CER, risk management file, IFU, PSUR — not entire documents)
- Readability test report (if patient section was revised)
- 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
| SSCP Section | Cross-Check Against | What to Verify | Common Mismatch |
|---|---|---|---|
| Device description | Technical documentation Section 1.1 | Materials, dimensions, model variants | SSCP lists discontinued variants |
| Clinical benefits | CER Section 8 (clinical conclusions) | Success rates, confidence intervals, population | SSCP cites outdated pooled analysis |
| Residual risks | Risk management file, ISO 14971 Table | Probability, severity, clinical impact | SSCP describes risks not in RM file |
| PMCF summary | PMCF evaluation report, PMCF plan | Status of PMCF activities, interim results | SSCP describes completed study that was terminated |
| Warnings/precautions | IFU Section 2.3, 2.4 | Contraindications, warnings, precautions | SSCP omits recently added warning |
| Undesirable effects | CER Section 7, PSUR | Adverse event rates, complaint data | SSCP rates differ from PSUR trending data |
| Expected lifetime | Technical documentation | Duration of safety/performance data | SSCP claims longer lifetime than data supports |
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
| Remove (Promotional) | Replace With (Objective) |
|---|---|
| "Superior clinical outcomes" | "94.2% technical success rate at 12 months (95% CI: 91.1–96.5%)" |
| "Gold standard treatment" | "Widely used surgical approach; see therapeutic alternatives in Section 6" |
| "Excellent safety profile" | "Serious adverse event rate of 1.2% (n=312); see Section 4.2 for all reported undesirable effects" |
| "Innovative design" | [Delete — device description in Section 1 covers design features objectively] |
| "Minimal complications" | "Complication rate of 3.8%; most common complications were infection (1.4%) and device migration (0.8%)" |
| "Proven reliability" | "Five-year PMCF data show consistent performance: see Table 4 and PMCF evaluation report REF-PMCF-004" |
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:
| Technical Text | Plain-Language Rewrite |
|---|---|
| "Biocompatible titanium alloy Grade 5 (Ti-6Al-4V) per ISO 5832-3" | "The device is made of titanium, a metal that the body usually accepts well" |
| "Incidence of periprocedural myocardial infarction was 0.3%" | "In about 3 out of 1,000 procedures, a heart attack happened around the time of the procedure" |
| "Contraindicated in patients with known hypersensitivity to nickel" | "Do not use this device if you are allergic to nickel" |
| "PMCF activities include a post-market registry and systematic literature review" | "After the device is sold, the manufacturer continues to check that it works safely by collecting information from doctors and patients and reviewing medical studies" |
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
| Residual Risk | Probability | Severity | Rate (from CER/RM) | Clinical Context | Risk Mitigation |
|---|---|---|---|---|---|
| Infection at implant site | Rare | Serious | 1.4% (n=312) | Typically occurs within 30 days; managed with antibiotics | Sterile packaging, surgical technique guide, IFU warning |
| Device migration | Remote | Critical | 0.8% (n=312) | May require re-operation to reposition | Implant fixation protocol, post-operative imaging per IFU |
| Allergic reaction to material | Very rare | Moderate | 0.3% (n=312) | Localized skin reaction; self-limiting in most cases | Material biocompatibility tested per ISO 10993; IFU lists materials |
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
| Data Element | IFU Section | CER Section | SSCP Section | Aligned? | Action |
|---|---|---|---|---|---|
| Contraindication: active infection | IFU 2.3.2 | CER 7.4 | SSCP 2.3 | No — missing from SSCP | Add to SSCP 2.3 |
| Success rate: 94.2% | N/A | CER 8.2, Table 12 | SSCP 4.1, Table 4 | Yes | None |
| Adverse event: device migration | IFU 4.4 | CER 7.2, Table 9 | SSCP 4.2, Table 5 | Yes | None |
| Expected device lifetime: 10 years | IFU 1.1 | CER 8.5 | SSCP 1.2 | No — SSCP says "lifetime" without specifying | Update SSCP to "10 years" |
| PMCF: registry active | N/A | PMCF eval report v3.1 | SSCP 4.3 | No — SSCP says "planned" | Update to "active, data collection ongoing" |
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
| Step | Owner | Description |
|---|---|---|
| 1. English master approved | Regulatory Affairs | English SSCP validated by NB |
| 2. Translation brief prepared | Regulatory Affairs + Medical Writing | Style guide, glossary, list of terms not to translate (e.g., Basic UDI-DI) |
| 3. Forward translation | Qualified medical translator (native speaker of target language) | Full translation with regulatory context |
| 4. Back-translation review | Independent translator | Back-translate to English; compare against original |
| 5. Reconciliation | Regulatory Affairs | Resolve discrepancies; ensure no promotional language introduced |
| 6. Final review | Local regulatory specialist | Confirm compliance with local regulatory terminology |
| 7. Upload to EUDAMED | Regulatory Affairs | All language versions uploaded with matching version numbers |
Common Failure Modes and How to Avoid Them
Table 7: SSCP Deficiency Response Failure Modes
| Failure Mode | Description | How to Avoid |
|---|---|---|
| Arguing with the NB | Responding defensively instead of addressing the deficiency | Accept the comment, make the change, explain what was changed |
| Partial remediation | Addressing only part of a multi-part deficiency | Break each comment into sub-items; close each one individually |
| Submitting full documents | Attaching the entire 200-page CER instead of the relevant excerpt | Extract only the pages/tables referenced in the response |
| Version confusion | Citing CER v8.2 but the current version is v9.1 | Confirm document versions before submitting; update SSCP to current versions |
| Missing the patient section | Fixing only the HCP section and ignoring patient-section comments | Treat patient-section comments with the same rigor; run readability testing |
| Uncoordinated translations | Updating English SSCP but not refreshing translations | Include translation timeline in the remediation project plan |
| No traceability | Making changes without showing the NB where each change was made | Use tracked-changes version and cross-reference in the response table |
| Patient section is a copy of HCP section | Manufacturer pastes the HCP section into the patient section without adapting language or reading level | Rewrite patient section from scratch using plain language; do not copy-paste from HCP section; run Flesch-Kincaid test (per Team-NB BPG V4, April 2026) |
Remediation Project RACI
Table 8: SSCP Deficiency Response RACI
| Activity | Responsible | Accountable | Consulted | Informed |
|---|---|---|---|---|
| Decode NB deficiency letter | Regulatory Affairs Lead | Regulatory Affairs Manager | Clinical, Quality | NB Coordinator |
| CER/IFU/RM alignment check | Clinical Evaluation Writer | Regulatory Affairs Manager | Risk Management, Labeling | Quality, NB Coordinator |
| Revise SSCP HCP sections | Medical Writer | Regulatory Affairs Manager | Clinical, Regulatory | NB Coordinator |
| Revise SSCP patient section | Medical Writer + Patient Advocate | Regulatory Affairs Manager | Clinical, Readability Panel | NB Coordinator |
| Readability testing | Clinical Research / CRO | Regulatory Affairs Manager | Patient panel | Quality |
| Translation coordination | Localization Project Manager | Regulatory Affairs Manager | Local regulatory specialists | NB Coordinator, Quality |
| Compile response package | Regulatory Affairs Lead | Regulatory Affairs Manager | All contributors | Quality, NB Coordinator |
| Submit to NB | NB Coordinator | Regulatory Affairs Manager | Regulatory Affairs Lead | Clinical, Quality, Management |
EUDAMED Publication Readiness Checklist
Before the NB validates and uploads the SSCP to EUDAMED, confirm:
Table 9: EUDAMED Publication Readiness Checklist
| # | Item | Verified? |
|---|---|---|
| 1 | SSCP version number matches across all language versions | ☐ |
| 2 | Basic UDI-DI is correctly referenced in the SSCP | ☐ |
| 3 | Manufacturer reference number is included | ☐ |
| 4 | All quantitative data matches current CER version | ☐ |
| 5 | No promotional language in any language version | ☐ |
| 6 | Patient section readability ≤ Grade 8 Flesch-Kincaid | ☐ |
| 7 | All residual risks include probability, severity, and rate data | ☐ |
| 8 | Contraindications match current IFU | ☐ |
| 9 | PMCF section references current PMCF plan and evaluation report | ☐ |
| 10 | Revision history is complete and accurate | ☐ |
| 11 | Date of SSCP is within 12 months (for Class III / IIb implantable) | ☐ |
| 12 | Translations cover all Member States where device is sold | ☐ |
| 13 | NB validation comments from prior cycle are addressed | ☐ |
| 14 | SSCP file format is PDF (as required by EUDAMED) | ☐ |
| 15 | File size is within EUDAMED upload limits | ☐ |
Response Timeline
| Milestone | Target Timeline |
|---|---|
| Receive NB deficiency letter | Day 0 |
| Internal kick-off; assign RACI | Day 1–3 |
| Decode all deficiencies; create remediation plan | Day 3–7 |
| CER/IFU/RM alignment verification | Day 7–14 |
| Revise SSCP HCP sections | Day 14–28 |
| Revise patient section; run readability testing | Day 28–42 |
| Coordinate translations | Day 42–60 |
| Compile response package; internal review | Day 60–70 |
| Submit to NB | Day 70–75 |
| NB validation of revised SSCP | Day 75–105 (typical NB turnaround: 30 days) |
| EUDAMED upload (by NB) | Upon successful validation |
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