Get the FREE Ultimate OpenClaw Setup Guide →
a

Mdr 745 Specialist

Verified

@alirezarezvani

npx machina-cli add skill @alirezarezvani/mdr-745-specialist --openclaw
Files (1)
SKILL.md
9.7 KB

MDR 2017/745 Specialist

EU MDR compliance patterns for medical device classification, technical documentation, and clinical evidence.


Table of Contents


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

FactorClass IClass IIaClass IIbClass III
DurationAnyShort-termLong-termLong-term
InvasivenessNon-invasiveBody orificeSurgicalImplantable
SystemAnyNon-criticalCritical organsCNS/cardiac
RiskLowestLow-mediumMedium-highHighest

Software Classification (MDCG 2019-11)

Information UseCondition SeverityClass
Informs decisionNon-seriousIIa
Informs decisionSeriousIIb
Drives/treatsCriticalIII

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

RequirementEvidenceStatus
Safe design (GSPR 1-3)Risk management file
Chemical properties (GSPR 10.1)Biocompatibility report
Infection risk (GSPR 10.2)Sterilization validation
Software requirements (GSPR 17)IEC 62304 documentation
Labeling (GSPR 23)Label artwork, IFU

Conformity Assessment Routes

ClassRouteNB Involvement
IAnnex II self-declarationNone
Is/ImAnnex II + IX/XISterile/measuring aspects
IIaAnnex II + IX or XIProduct or QMS
IIbAnnex IX + X or X + XIType exam + production
IIIAnnex IX + XFull QMS + type exam

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

ClassMinimum EvidenceInvestigation
IRisk-benefit analysisNot typically required
IIaLiterature + post-marketMay be required
IIbSystematic literature reviewOften required
IIIComprehensive clinical dataRequired (Article 61)

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

ComponentRequirementFrequency
PMS PlanArticle 84Maintain current
PSURClass IIa and higherPer class schedule
PMCF PlanAnnex XIV Part BUpdate with CER
PMCF ReportAnnex XIV Part BAnnual (Class III)
VigilanceArticles 87-92As events occur

PSUR Schedule

ClassFrequency
Class IIIAnnual
Class IIb implantableAnnual
Class IIbEvery 2 years
Class IIaWhen necessary

Serious Incident Reporting

TimelineRequirement
2 daysSerious public health threat
10 daysDeath or serious deterioration
15 daysOther serious incidents

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

ModuleContentActor
ActorCompany registrationManufacturer, AR
UDI/DeviceDevice and variant dataManufacturer
CertificatesNB certificatesNotified Body
Clinical InvestigationStudy registrationSponsor
VigilanceIncident reportsManufacturer
Market SurveillanceAuthority actionsCompetent Authority

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

FactorConsiderations
Designation scopeCovers your device type
CapacityTimeline for initial audit
Geographic reachMarkets you need to access
Technical expertiseExperience with your technology
Fee structureTransparency, predictability

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

Source

git clone https://clawhub.ai/alirezarezvani/mdr-745-specialistView on GitHub

Overview

This skill guides you through EU MDR 2017/745 compliance for device classification, technical documentation, and clinical evidence. It covers Annex VIII classification rules, Annex II/III technical files, Annex XIV clinical evaluation, and EUDAMED integration, including UDI and PMCF considerations. It helps teams align classification decisions with Notified Body expectations to achieve regulatory readiness.

How This Skill Works

Start by identifying device duration, invasiveness, body contact, and whether the device is active. Apply MDR Annex VIII rules (and MDCG 2019-11 for software) and document the classification rationale, validated with a Notified Body. Then assemble Annex II/III technical documentation, complete GSPR mappings, conduct a benefit-risk analysis, compile clinical evidence per Annex XIV, plan PMCF, and set up EUDAMED/UDI data integration.

When to Use It

  • Planning MDR remediation or a new product to determine regulatory class before design freeze
  • Creating or updating Annex II/III technical documentation and labeling for conformity
  • Gathering and organizing clinical evidence to support Annex XIV clinical evaluation
  • Developing or refreshing post-market surveillance plans including PMCF
  • Setting up EUDAMED data, UDI tagging, and ensuring device data feeds are compliant

Quick Start

  1. Step 1: Determine duration, invasiveness, contact, and energy use to select the MDR class
  2. Step 2: Apply Annex VIII rules (and MDCG 2019-11 for software) and document rationale
  3. Step 3: Assemble Annex II/III docs, map GSPR, plan clinical evaluation (Annex XIV) and PMCF, set up EUDAMED/UDI

Best Practices

  • Define device scope early: duration, invasiveness, and contact to anchor the correct MDR class
  • Use MDCG 2019-11 guidance for software classification and keep rationale traceable
  • Map GSPR requirements to risk management (ISO 14971) and link to Annex II/III artifacts
  • Structure Annex II/III docs consistently and maintain a living technical file
  • Plan PMCF and EUDAMED/UDI data integration from the start to avoid gaps

Example Use Cases

  • Example 1: Absorbable surgical suture classified as Class IIb under Rule 8 with long-term contact
  • Example 2: AI Diagnostic Software classified using MDCG 2019-11 and Rule 11 logic
  • Example 3: Cardiac Pacemaker classified as Class III based on implantable contact and system risk
  • Example 4: Software-only medical device with Annex II/III documentation and software lifecycle evidence
  • Example 5: Device with PMCF plan and full EUDAMED/UDI data integration for post-market oversight

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers