ra-qm-team/skills/mdr-745-specialist/SKILL.md
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, Art. 86 PSUR schedules, and EUDAMED integration. Use when classifying a medical device under MDR, building or gap-checking a technical file, planning clinical evaluation or PMS/PSUR cadence, or preparing for notified body review (e.g., 'what class is my device under MDR', 'review my PSUR schedule').
npx skillsauth add alirezarezvani/claude-skills mdr-745-specialistInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
EU MDR compliance patterns for medical device classification, technical documentation, and clinical evidence.
Classify device under MDR Annex VIII:
| 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 |
| Information Use | Condition Severity | Class | |-----------------|-------------------|-------| | Informs decision | Non-serious | IIa | | Informs decision | Serious | IIb | | Drives/treats | Critical | III |
Example 1: Absorbable Surgical Suture
Example 2: AI Diagnostic Software
Example 3: Cardiac Pacemaker
Prepare technical file per Annex II and III:
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
| 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 | ☐ |
| 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, or Annex X + XI | QMS + tech doc assessment, or type exam + production | | III | Annex IX, or Annex X + XI | Full QMS + product dossier, or type exam + production |
Develop clinical evidence strategy per Annex XIV:
| 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) |
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
Establish PMS system per Chapter VII:
| Component | Requirement | Frequency | |-----------|-------------|-----------| | PMS Plan | Article 84 | Maintain current | | PSUR | Article 86 — Class IIa and higher | Per Art. 86(1) schedule below | | 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 |
| Class | Frequency (MDR Art. 86(1)) | |-------|-----------------------------| | Class III | Updated at least annually | | Class IIb (all, incl. implantable) | Updated at least annually | | Class IIa | When necessary, at least every 2 years | | Class I | No PSUR — PMS report instead (Art. 85) |
| Timeline | Requirement | |----------|-------------| | 2 days | Serious public health threat | | 10 days | Death or serious deterioration | | 15 days | Other serious incidents |
Implement UDI system per Article 27:
| 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 |
Required elements per Article 13:
references/mdr-classification-guide.md contains:
references/clinical-evidence-requirements.md contains:
references/technical-documentation-templates.md contains:
# 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:
| 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 |
development
Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says "/cs:weekly-review". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.
development
Use when someone wants to decide whether a meeting is worth calling, price a meeting in dollars, build a timeboxed agenda with desired outcomes, or turn messy meeting notes into owned action items — or says "should this be a meeting", "/cs:meeting-prep", or "/cs:meeting-actions". Runs a cost gate (ASYNC / NOT-READY / MEET), builds a decision-first agenda, and extracts an owner + due-date checklist that flags every orphan.
development
Convert a rambling description of a desired outcome into one polished, autonomous /goal prompt ready to paste into a fresh session. Use when the user says "/fable-goal", "turn this into a goal prompt", "write me a fable prompt", "write the prompt that builds X", or rambles about something they want made and asks for the prompt that makes it happen. The output is a single copy-paste prompt, never the build itself. Do NOT use when the user wants the thing built right now in this session — only when they want the PROMPT that will make it happen in a fresh session.
development
Use when someone wants to plan a deep work day, time-block their calendar or task list, budget or cut shallow work, protect focus hours, track deep-work sessions and streaks, run an end-of-day shutdown ritual, or says "/deep-work" or "/time-block". Classifies tasks deep vs shallow, builds an energy-first time-blocked schedule that refuses deep demand past the 4-hour ceiling, batches shallow work into at most two windows, and logs focus sessions against a weekly target.