GSPR Mapping: How to Do It Properly and Avoid Notified Body Rejections
The General Safety and Performance Requirements (GSPRs) form the backbone of MDR technical documentation. They define the essential criteria every medical device must meet before achieving CE marking. Notified Bodies report that weak, vague, or incomplete GSPR mapping is one of the leading causes of MDR nonconformities and prolonged review cycles. A compliant, defensible GSPR table must demonstrate clear evidence, precise justification, and complete traceability. This article outlines the architecture, expectations, and common failures associated with GSPR mapping—and how to avoid Notified Body rejections.
1. Understanding the Purpose of the GSPR Table
The GSPR table is not an administrative checklist. It is a structured demonstration that the device meets every applicable MDR requirement through:
- Objective evidence
- Risk-based justification
- Traceability to design, verification, and clinical data
- Alignment with harmonised standards and state of the art
Efficiency and compliance depend on the clarity of this mapping and the robustness of referenced documentation.
2. Core Principles of a Compliant GSPR Mapping Strategy
2.1 Provide Clause-Level Evidence References
Notified Bodies reject GSPR tables that list document names without pointing to specific sections or test results. A mature table includes:
- Exact document title
- Version or revision reference
- Clause or page number
- Specific verification test or analysis
Ambiguous evidence links are interpreted as inadequate conformity.
2.2 Use Harmonised Standards Correctly
Harmonised standards simplify conformity demonstration only when used accurately. Each standard should include:
- Correct designation and revision year
- Applicable clauses
- Clear link to the GSPR requirement it addresses
Referencing entire standards without clause alignment is a common nonconformity.
2.3 Apply Risk-Based Justification for Non-Applicable Requirements
Some GSPRs legitimately do not apply, but justification must be:
- Risk-based
- Specific to the device type and configuration
- Traceable to the risk management file
Examples of weak justifications include: “Not applicable for this device”—without explanation.
2.4 Ensure Consistency Across All Technical Documentation
GSPR mapping must reflect the same information found in:
- Risk management file
- Clinical evaluation
- Design verification and validation reports
- Usability documentation
- Biocompatibility and sterilisation evidence
- IFU content
Any inconsistency is flagged by Notified Bodies as a system weakness.
3. Building a Strong, Audit-Ready GSPR Table
3.1 Begin With a Structured Template
An efficient GSPR table includes columns for:
- Requirement text
- Applicability
- Justification (if not applicable)
- Evidence reference
- Standards applied
- Traceability notes
3.2 Align GSPR Evidence With Device Configuration
If the technical file covers multiple variants or accessories, evidence must match each configuration. Notified Bodies frequently reject submissions where:
- Testing was performed on unrepresentative models
- Evidence belongs to an earlier or different configuration
- Variants are not clearly differentiated
3.3 Integrate GSPR Mapping Early in the Development Process
GSPR mapping should begin at design input stage—not at submission. When performed early, it:
- Guides design control
- Ensures required verification tests are planned
- Prevents documentation gaps
- Reduces need for retesting or late engineering changes
3.4 Validate Mapping Through Cross-Functional Review
A mature review panel includes experts in:
- Regulatory affairs
- Risk management
- Design engineering
- Clinical affairs
- Quality assurance
Cross-functional review ensures accuracy, completeness, and coherent evidence flow.
4. Common Failure Points Leading to Notified Body Rejection
- Generic references instead of specific evidence links
- Incorrect or outdated standards listed without applicability analysis
- GSPR 1–9 inadequately supported, especially regarding risk reduction and benefit–risk justification
- Biological safety evidence incomplete or not aligned with ISO 10993 strategy
- IFU inconsistencies relative to risk controls and clinical claims
- PMS and PMCF misalignment with identified risks
- Weak rationales for non-applicability
- Missing traceability between GSPR items and design outputs
5. Strengthening GSPR Mapping for Faster NB Approval
5.1 Build a Traceability Engine
Efficient manufacturers create a single source of truth linking:
- GSPR requirements
- Risk controls
- Verification evidence
- Clinical data
- Labelling content
5.2 Update GSPR Mapping Throughout the Lifecycle
Changes in design, manufacturing, suppliers, risk assessments, or clinical evidence require immediate updates to the GSPR table. Notified Bodies expect dynamic maintenance.
5.3 Demonstrate Compliance Using State-of-the-Art Evidence
MDR requires manufacturers to show alignment with current knowledge and benchmark devices, especially when novel technologies or materials are used.
Conclusion
GSPR mapping under MDR is both a compliance requirement and an opportunity to demonstrate technical competence. Properly executed, it strengthens the entire technical documentation package, accelerates Notified Body review, and reinforces lifecycle safety and performance claims. Manufacturers that invest in structured, precise, risk-aligned GSPR mapping consistently achieve smoother CE certification and long-term regulatory confidence.
