Mdr 745 Specialist

Device Classification Workflow

Classify device under MDR Annex VIII:

1. Identify device duration (transient, short-term, long-term)
2. Determine invasiveness level (non-invasive, body orifice, surgical)
3. Assess body system contact (CNS, cardiac, other)
4. Check if active device (energy dependent)
5. Apply classification rules 1-22
6. For software, apply MDCG 2019-11 algorithm
7. Document classification rationale
8. Validation: Classification confirmed with Notified Body

Classification Matrix

Software Classification (MDCG 2019-11)

Classification Examples

Example 1: Absorbable Surgical Suture

• Rule 8 (implantable, long-term)
• Duration: > 30 days (absorbed)
• Contact: General tissue
• Classification: Class IIb

Example 2: AI Diagnostic Software

• Rule 11 + MDCG 2019-11
• Function: Diagnoses serious condition
• Classification: Class IIb

Example 3: Cardiac Pacemaker

• Rule 8 (implantable)
• Contact: Central circulatory system
• Classification: Class III

Technical Documentation

Prepare technical file per Annex II and III:

1. Create device description (variants, accessories, intended purpose)
2. Develop labeling (Article 13 requirements, IFU)
3. Document design and manufacturing process
4. Complete GSPR compliance matrix
5. Prepare benefit-risk analysis
6. Compile verification and validation evidence
7. Integrate risk management file (ISO 14971)
8. Validation: Technical file reviewed for completeness

Technical File Structure

ANNEX II TECHNICAL DOCUMENTATION
├── Device description and UDI-DI
├── Label and instructions for use
├── Design and manufacturing info
├── GSPR compliance matrix
├── Benefit-risk analysis
├── Verification and validation
└── Clinical evaluation report

GSPR Compliance Checklist

Conformity Assessment Routes

Clinical Evidence

Develop clinical evidence strategy per Annex XIV:

1. Define clinical claims and endpoints
2. Conduct systematic literature search
3. Appraise clinical data quality
4. Assess equivalence (technical, biological, clinical)
5. Identify evidence gaps
6. Determine if clinical investigation required
7. Prepare Clinical Evaluation Report (CER)
8. Validation: CER reviewed by qualified evaluator

Evidence Requirements by Class

Clinical Evaluation Report Structure

CER CONTENTS
├── Executive summary
├── Device scope and intended purpose
├── Clinical background (state of the art)
├── Literature search methodology
├── Data appraisal and analysis
├── Safety and performance conclusions
├── Benefit-risk determination
└── PMCF plan summary

Qualified Evaluator Requirements

• Medical degree or equivalent healthcare qualification
• 4+ years clinical experience in relevant field
• Training in clinical evaluation methodology
• Understanding of MDR requirements

Post-Market Surveillance

Establish PMS system per Chapter VII:

1. Develop PMS plan (Article 84)
2. Define data collection methods
3. Establish complaint handling procedures
4. Create vigilance reporting process
5. Plan Periodic Safety Update Reports (PSUR)
6. Integrate with PMCF activities
7. Define trend analysis and signal detection
8. Validation: PMS system audited annually

PMS System Components

PSUR Schedule

Serious Incident Reporting

EUDAMED and UDI

Implement UDI system per Article 27:

1. Obtain issuing entity code (GS1, HIBCC, ICCBBA)
2. Assign UDI-DI to each device variant
3. Assign UDI-PI (production identifier)
4. Apply UDI carrier to labels (AIDC + HRI)
5. Register actor in EUDAMED
6. Register devices in EUDAMED
7. Upload certificates when available
8. Validation: UDI verified on sample labels

EUDAMED Modules

UDI Label Requirements

Required elements per Article 13:

• UDI-DI (device identifier)
• UDI-PI (production identifier) for Class II+
• AIDC format (barcode/RFID)
• HRI format (human-readable)
• Manufacturer name and address
• Lot/serial number
• Expiration date (if applicable)

Reference Documentation

MDR Classification Guide

references/mdr-classification-guide.md contains:

• Complete Annex VIII classification rules (Rules 1-22)
• Software classification per MDCG 2019-11
• Worked classification examples
• Conformity assessment route selection

Clinical Evidence Requirements

references/clinical-evidence-requirements.md contains:

• Clinical evidence framework and hierarchy
• Literature search methodology
• Clinical Evaluation Report structure
• PMCF plan and evaluation report guidance

Technical Documentation Templates

references/technical-documentation-templates.md contains:

• Annex II and III content requirements
• Design History File structure
• GSPR compliance matrix template
• Declaration of Conformity template
• Notified Body submission checklist

Tools

MDR Gap Analyzer

# Quick gap analysis
python scripts/mdr_gap_analyzer.py --device "Device Name" --class IIa

# JSON output for integration
python scripts/mdr_gap_analyzer.py --device "Device Name" --class III --output json

# Interactive assessment
python scripts/mdr_gap_analyzer.py --interactive

Analyzes device against MDR requirements, identifies compliance gaps, generates prioritized recommendations.

Output includes:

• Requirements checklist by category
• Gap identification with priorities
• Critical gap highlighting
• Compliance roadmap recommendations

Notified Body Interface

Selection Criteria

Pre-Submission Checklist

• Technical documentation complete
• GSPR matrix fully addressed
• Risk management file current
• Clinical evaluation report complete
• QMS (ISO 13485) certified
• Labeling and IFU finalized
• Validation: Internal gap assessment complete

MDCG Guidance Documents Update (2024-2025)

Key MDCG Guidance Documents

MDR Transition Timeline (Post-Amendment Regulation 2023/607)

Conditions for extended deadlines:

• Device continues to comply with MDD/AIMDD
• No significant changes in design or intended purpose
• No unacceptable safety or performance risk
• Manufacturer has applied to Notified Body for MDR conformity assessment before applicable deadline

Software as Medical Device Under MDR (MDCG 2019-11 Rev.1)

Software Qualification Decision

Is the software a medical device?
        │
        ▼
Does the software perform an action on data?
        │
    Yes─┴─No → NOT a medical device (data storage/communication only)
     │
     ▼
Is the action for the benefit of individual patients?
        │
    Yes─┴─No → NOT a medical device (population health/admin)
     │
     ▼
Is the action one of: treatment, diagnosis, monitoring, prediction?
        │
    Yes─┴─No → NOT a medical device (lifestyle/wellness)
     │
     ▼
QUALIFIES AS MEDICAL DEVICE SOFTWARE → Apply classification rules

Software Classification Under MDR

Software Lifecycle Requirements Under MDR

AI/ML Medical Devices Under MDR

AI/ML Classification Considerations

AI/ML-Specific Technical Documentation

In addition to standard Annex II requirements, AI/ML devices must document:

EU AI Act Interaction with MDR

See also: ../risk-management-specialist/SKILL.md for AI-specific risk management under ISO 14971, and ../fda-consultant-specialist/SKILL.md for FDA's AI/ML SaMD framework and PCCP.

Eudamed Implementation Status and Requirements

Eudamed Module Deployment Status (as of 2025)

Key consideration: Until Eudamed is declared fully functional by the European Commission, manufacturers must use existing national systems (e.g., BfArM in Germany, ANSM in France) for vigilance reporting.

Eudamed Registration Requirements for Manufacturers

UDI-DI and UDI-PI Detailed Requirements

UDI-DI (Device Identifier) — Static Information

UDI-PI (Production Identifier) — Variable Information

UDI Carrier Requirements

Labeling placement rules:

• UDI on each level of packaging (unit, intermediate, case)
• For reusable devices requiring sterilization: UDI on device itself (direct marking)
• Class III implantable: UDI on device or packaging that remains with patient record
• UDI must survive device lifecycle (including reprocessing cycles for reusable devices)

UDI Database Submission Timeline

Note: All timelines are contingent on Eudamed being declared fully functional. Until then, manufacturers should pre-register in Eudamed (available modules) and maintain data readiness.

Cross-Reference: NIS2 for Critical Infrastructure (Healthcare)

Healthcare organizations manufacturing or deploying medical devices may be classified as essential entities under NIS2:

See also: ../information-security-manager-iso27001/SKILL.md for ISO 27001 alignment with NIS2 requirements.

MDR Updates & Cross-Framework Integration

Latest MDCG Guidance Documents

• MDCG 2019-11 Rev.1: Qualification and classification of software — updated algorithm for SaMD
• MDCG 2020-1 Rev.1: Clinical evaluation (Annex XIV) — updated methodologies
• MDCG 2024-8: EU AI Act interaction with MDR for AI-enabled medical devices
• MDCG 2023-4: Legacy devices and Article 120 transition provisions

AI/ML Medical Devices Under MDR

• Classification: AI/ML-based SaMD typically Class IIa or higher (Rule 11)
• Clinical Evidence: Must demonstrate AI algorithm clinical performance (sensitivity, specificity, AUC)
• Continuous Learning: PCCP-equivalent under MDR for adaptive AI devices
• Post-Market: Enhanced PMCF for AI devices monitoring real-world algorithm performance
• EU AI Act Interaction: High-risk AI medical devices subject to BOTH MDR and EU AI Act
• Cross-reference: See eu-ai-act-specialist for AI Act obligations

NIS2 Impact on Healthcare

• Healthcare entities are "Essential Entities" under NIS2 Directive
• Medical device manufacturers may be "Important Entities"
• NIS2 cybersecurity requirements supplement MDR cybersecurity expectations
• Cross-reference: See nis2-directive-specialist for NIS2 compliance

EUDAMED Implementation Status

• Actor Registration Module: Operational — all economic operators must register
• UDI/Device Registration Module: Operational — mandatory device registration
• Notified Body Module: Operational — certificate information
• Clinical Investigation Module: Available
• Vigilance Module: Under development
• Market Surveillance Module: Under development

UDI Detailed Requirements

• UDI-DI (Device Identifier): Unique to device model — used for EUDAMED registration
• UDI-PI (Production Identifier): Identifies production unit — lot, serial, expiry, manufacturing date
• Issuing Entities: GS1, HIBCC, ICCBBA, IFA
• Carrier Types: AIDC (barcode/2D) + HRI (human readable)
• Implant Card: Required for Class III implantable devices (UDI + patient information)

Troubleshooting

Success Criteria

• Device correctly classified with documented rationale -- classification per Annex VIII with all applicable rules evaluated, highest class selected, and rationale documented for NB review
• Complete technical file per Annex II structure -- device description, labeling/IFU, design and manufacturing info, GSPR compliance matrix, benefit-risk analysis, verification and validation, and clinical evaluation report all present and current
• GSPR compliance matrix fully addressed -- all applicable General Safety and Performance Requirements mapped to evidence with cross-references to risk management file, biocompatibility reports, sterilization validation, software documentation, and labeling
• Clinical evaluation report meets Annex XIV requirements -- literature search methodology documented, data appraised and analyzed, safety and performance conclusions stated, benefit-risk determined, and PMCF plan included
• PMS system operational -- PMS plan per Article 84, complaint handling procedures, vigilance reporting process, PSUR schedule defined by class, and PMCF activities integrated with CER
• UDI system fully implemented -- UDI-DI assigned per device variant, UDI-PI applied (lot/serial/dates), AIDC and HRI carriers on all packaging levels, EUDAMED registration complete (when applicable)
• MDR gap analysis shows zero critical gaps -- as measured by mdr_gap_analyzer.py, with all requirements addressed or in-progress with documented timeline

Scope & Limitations

In Scope:

• Device classification per MDR Annex VIII (Rules 1-22) including software classification per MDCG 2019-11 Rev.1
• Technical documentation structure and requirements per Annex II and Annex III
• GSPR compliance matrix with evidence mapping
• Clinical evidence strategy including equivalence assessment, CER structure, and PMCF planning
• Post-market surveillance system design including PMS plan, PSUR schedule, and vigilance reporting timelines
• EUDAMED and UDI system implementation guidance
• Conformity assessment route selection by device class
• MDR transition timeline tracking (post-Amendment Regulation 2023/607)
• AI/ML medical device considerations including EU AI Act interaction

Out of Scope:

• Clinical investigation protocol design, execution, or statistical analysis
• Biocompatibility testing per ISO 10993 (beyond evidence mapping in GSPR)
• Sterilization validation per ISO 11135/11137 (beyond evidence mapping)
• Notified Body selection, engagement, or commercial negotiation
• Quality Management System implementation -- use quality-manager-qms-iso13485 for ISO 13485 QMS
• Risk management process implementation -- use risk-management-specialist for ISO 14971

Important Notes:

• EUDAMED's first four modules became mandatory from May 28, 2026; manufacturers must have SRN and device registrations ready
• Only approximately 40 Notified Bodies are designated EU-wide as of 2025, creating capacity constraints; early NB engagement is critical
• The European Commission published updated transition timelines in December 2025 extending deadlines for certain device categories
• Manufacturers must adopt recently harmonized standards with no formal transition period (Decision EU 2025/2078)

Integration Points

Tool Reference

mdr_gap_analyzer.py

Analyzes device against MDR requirements, identifies compliance gaps, and generates prioritized recommendations.

Analysis Categories: Technical documentation (Annex II), GSPR compliance, clinical evidence (Annex XIV), post-market surveillance (Chapter VII), UDI/EUDAMED, labeling (Article 13), quality management system, risk management, and conformity assessment route.

Output: Requirements checklist with per-item status (Not Started/In Progress/Complete/N/A), gap identification with priority (Critical/High/Medium/Low), critical gap highlighting, completion percentage, and compliance roadmap recommendations.