mdr-745-specialist
EU MDR 2017/745 compliance specialist for medical device classification, technical documentation, clinical evidence, and post-market surveillance. Covers Annex VIII classification rules, Annex II/III technical files, Annex XIV clinical evaluation, and EUDAMED integration.
Best use case
mdr-745-specialist is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
EU MDR 2017/745 compliance specialist for medical device classification, technical documentation, clinical evidence, and post-market surveillance. Covers Annex VIII classification rules, Annex II/III technical files, Annex XIV clinical evaluation, and EUDAMED integration.
Teams using mdr-745-specialist should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/mdr-745-specialist/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How mdr-745-specialist Compares
| Feature / Agent | mdr-745-specialist | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
EU MDR 2017/745 compliance specialist for medical device classification, technical documentation, clinical evidence, and post-market surveillance. Covers Annex VIII classification rules, Annex II/III technical files, Annex XIV clinical evaluation, and EUDAMED integration.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
AI Agent for SaaS Idea Validation
Use AI agent skills for SaaS idea validation, market research, customer discovery, competitor analysis, and documenting startup hypotheses.
AI Agents for Startups
Explore AI agent skills for startup validation, product research, growth experiments, documentation, and fast execution with small teams.
SKILL.md Source
# MDR 2017/745 Specialist EU MDR compliance patterns for medical device classification, technical documentation, and clinical evidence. --- ## Table of Contents - [Device Classification Workflow](#device-classification-workflow) - [Technical Documentation](#technical-documentation) - [Clinical Evidence](#clinical-evidence) - [Post-Market Surveillance](#post-market-surveillance) - [EUDAMED and UDI](#eudamed-and-udi) - [Reference Documentation](#reference-documentation) - [Tools](#tools) --- ## 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 | Factor | Class I | Class IIa | Class IIb | Class III | |--------|---------|-----------|-----------|-----------| | Duration | Any | Short-term | Long-term | Long-term | | Invasiveness | Non-invasive | Body orifice | Surgical | Implantable | | System | Any | Non-critical | Critical organs | CNS/cardiac | | Risk | Lowest | Low-medium | Medium-high | Highest | ### Software Classification (MDCG 2019-11) | Information Use | Condition Severity | Class | |-----------------|-------------------|-------| | Informs decision | Non-serious | IIa | | Informs decision | Serious | IIb | | Drives/treats | Critical | III | ### 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 | Requirement | Evidence | Status | |-------------|----------|--------| | 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 | Class | Route | NB Involvement | |-------|-------|----------------| | I | Annex II self-declaration | None | | Is/Im | Annex II + IX/XI | Sterile/measuring aspects | | IIa | Annex II + IX or XI | Product or QMS | | IIb | Annex IX + X or X + XI | Type exam + production | | III | Annex IX + X | Full 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 | Class | Minimum Evidence | Investigation | |-------|------------------|---------------| | I | Risk-benefit analysis | Not typically required | | IIa | Literature + post-market | May be required | | IIb | Systematic literature review | Often required | | III | Comprehensive clinical data | Required (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 | Component | Requirement | Frequency | |-----------|-------------|-----------| | PMS Plan | Article 84 | Maintain current | | PSUR | Class IIa and higher | Per class schedule | | PMCF Plan | Annex XIV Part B | Update with CER | | PMCF Report | Annex XIV Part B | Annual (Class III) | | Vigilance | Articles 87-92 | As events occur | ### PSUR Schedule | Class | Frequency | |-------|-----------| | Class III | Annual | | Class IIb implantable | Annual | | Class IIb | Every 2 years | | Class IIa | When necessary | ### Serious Incident Reporting | Timeline | Requirement | |----------|-------------| | 2 days | Serious public health threat | | 10 days | Death or serious deterioration | | 15 days | Other 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 | Module | Content | Actor | |--------|---------|-------| | Actor | Company registration | Manufacturer, AR | | UDI/Device | Device and variant data | Manufacturer | | Certificates | NB certificates | Notified Body | | Clinical Investigation | Study registration | Sponsor | | Vigilance | Incident reports | Manufacturer | | Market Surveillance | Authority actions | Competent 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 ```bash # 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 | Factor | Considerations | |--------|----------------| | Designation scope | Covers your device type | | Capacity | Timeline for initial audit | | Geographic reach | Markets you need to access | | Technical expertise | Experience with your technology | | Fee structure | Transparency, 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
Related Skills
risk-management-specialist
Medical device risk management specialist implementing ISO 14971 throughout product lifecycle. Provides risk analysis, risk evaluation, risk control, and post-production information analysis. Use when user mentions risk management, ISO 14971, risk analysis, FMEA, fault tree analysis, hazard identification, risk control, risk matrix, benefit-risk analysis, residual risk, risk acceptability, or post-market risk.
fda-consultant-specialist
FDA regulatory consultant for medical device companies. Provides 510(k)/PMA/De Novo pathway guidance, QSR (21 CFR 820) compliance, HIPAA assessments, and device cybersecurity. Use when user mentions FDA submission, 510(k), PMA, De Novo, QSR, premarket, predicate device, substantial equivalence, HIPAA medical device, or FDA cybersecurity.
agency-agents-ai-specialists
A collection of specialized AI agent personalities for Claude Code, Cursor, Aider, Windsurf, and other AI coding tools — covering engineering, design, marketing, sales, and more.
---
name: article-factory-wechat
humanizer
Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
tavily-search
Use Tavily API for real-time web search and content extraction. Use when: user needs real-time web search results, research, or current information from the web. Requires Tavily API key.
baidu-search
Search the web using Baidu AI Search Engine (BDSE). Use for live information, documentation, or research topics.
agent-autonomy-kit
Stop waiting for prompts. Keep working.
Meeting Prep
Never walk into a meeting unprepared again. Your agent researches all attendees before calendar events—pulling LinkedIn profiles, recent company news, mutual connections, and conversation starters. Generates a briefing doc with talking points, icebreakers, and context so you show up informed and confident. Triggered automatically before meetings or on-demand. Configure research depth, advance timing, and output format. Walking into meetings blind is amateur hour—missed connections, generic small talk, zero leverage. Use when setting up meeting intelligence, researching specific attendees, generating pre-meeting briefs, or automating your prep workflow.
self-improvement
Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Claude ('No, that's wrong...', 'Actually...'), (3) User requests a capability that doesn't exist, (4) An external API or tool fails, (5) Claude realizes its knowledge is outdated or incorrect, (6) A better approach is discovered for a recurring task. Also review learnings before major tasks.
botlearn-healthcheck
botlearn-healthcheck — BotLearn autonomous health inspector for OpenClaw instances across 5 domains (hardware, config, security, skills, autonomy); triggers on system check, health report, diagnostics, or scheduled heartbeat inspection.