
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, 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').
- Installs
- 738
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/alirezarezvani/claude-skills --skill mdr-745-specialist- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads mdr-745-specialist automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
MDR 2017/745 Specialist
EU MDR compliance patterns for medical device classification, technical documentation, and clinical evidence.
Table of Contents
- Device Classification Workflow
- Technical Documentation
- Clinical Evidence
- Post-Market Surveillance
- EUDAMED and UDI
- Reference Documentation
- Tools
Device Classification Workflow
Classify device under MDR Annex VIII:
- Identify device duration (transient, short-term, long-term)
- Determine invasiveness level (non-invasive, body orifice, surgical)
- Assess body system contact (CNS, cardiac, other)
- Check if active device (energy dependent)
- Apply classification rules 1-22
- For software, apply MDCG 2019-11 algorithm
- Document classification rationale
- 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:
- Create device description (variants, accessories, intended purpose)
- Develop labeling (Article 13 requirements, IFU)
- Document design and manufacturing process
- Complete GSPR compliance matrix
- Prepare benefit-risk analysis
- Compile verification and validation evidence
- Integrate risk management file (ISO 14971)
- 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, 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 |
Clinical Evidence
Develop clinical evidence strategy per Annex XIV:
- Define clinical claims and endpoints
- Conduct systematic literature search
- Appraise clinical data quality
- Assess equivalence (technical, biological, clinical)
- Identify evidence gaps
- Determine if clinical investigation required
- Prepare Clinical Evaluation Report (CER)
- 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:
- Develop PMS plan (Article 84)
- Define data collection methods
- Establish complaint handling procedures
- Create vigilance reporting process
- Plan Periodic Safety Update Reports (PSUR)
- Integrate with PMCF activities
- Define trend analysis and signal detection
- Validation: PMS system audited annually
PMS System Components
| 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 |
PSUR Schedule
| 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) |
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:
- Obtain issuing entity code (GS1, HIBCC, ICCBBA)
- Assign UDI-DI to each device variant
- Assign UDI-PI (production identifier)
- Apply UDI carrier to labels (AIDC + HRI)
- Register actor in EUDAMED
- Register devices in EUDAMED
- Upload certificates when available
- 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
# 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
FAQ
What does the mdr-745-specialist 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, 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').
How do I install mdr-745-specialist?
Run npx skills add https://github.com/alirezarezvani/claude-skills --skill mdr-745-specialist in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/mdr-745-specialist/ (personal) or .claude/skills/mdr-745-specialist/ (project).
Which AI agents can use mdr-745-specialist?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is mdr-745-specialist safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains mdr-745-specialist?
It is published by alirezarezvani in alirezarezvani/claude-skills. It has 738 recorded installs.
More from alirezarezvani/claude-skills
engineering-skills
alirezarezvani/claude-skills
Index of the engineering-team skills bundle for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw, and 6 more tools. Architecture, frontend, backend, QA, DevOps, security, AI/ML, data engineering, Playwright, Stripe, AWS, MS365 (stdlib-only Python tools). Use when browsing or choosing among engineering-team role skills — load only the one specialist SKILL.md you need, never bulk-load the bundle.
finance-skills
alirezarezvani/claude-skills
Router/index for the finance skills bundled in this plugin: financial-analyst (ratio analysis, DCF valuation, budget variance, rolling forecasts), saas-metrics-coach (ARR/MRR, churn, CAC/LTV, NRR, quick ratio) and month-end-close (close calendar, reconciliations, flux review). Use when a finance request doesn't obviously match one skill and you need to pick the right one (e.g., 'analyze these financials', 'how healthy are my SaaS metrics').
marketing-skills
alirezarezvani/claude-skills
Directory and router for the marketing skills library. Use when you need to find the right marketing skill for a task, see what marketing capabilities exist, or get oriented in this plugin. 44 specialist skills across 8 pods (content, SEO + AEO, CRO, channels, growth, intelligence, sales enablement, ops), 59 stdlib Python tools. Routes to one skill — it does not execute marketing work itself.
business-growth-skills
alirezarezvani/claude-skills
Router/index for the 4 business & growth skills bundled in this plugin: customer-success-manager (health scoring, churn risk, expansion), sales-engineer (RFP analysis, competitive matrices, PoC planning), revenue-operations (pipeline, forecast accuracy, GTM efficiency), and contract-and-proposal-writer. Use when a growth/revenue request doesn't obviously match one skill and you need to pick the right one (e.g., 'which accounts are at risk', 'should we bid on this RFP').
engineering-advanced-skills
alirezarezvani/claude-skills
Index of 37 advanced engineering agent skills for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. Use when browsing or choosing among the POWERFUL-tier engineering skills: agent design, RAG, MCP servers, CI/CD, database design, observability, security auditing, changelog/release automation, reliability (SLO/chaos/flags/operators), platform ops.
product-skills
alirezarezvani/claude-skills
Use when coordinating product work across the 12 bundled product sub-skills (RICE, OKRs, UX research, design tokens, competitive teardown, analytics, experiments, discovery, roadmaps, spec-to-repo, landing pages, SaaS scaffolding) or the 4 standalone product-team plugins (user stories, Apple HIG, code-to-PRD, research summarizer). Triggers on 'help me prioritize', 'plan a product experiment', 'we ship features nobody uses', 'run the discovery loop', 'is our OST sound'. Forks context to route to one sub-skill via a deterministic signal router and returns a digest; can also drive a continuous-discovery loop (Torres cadence tracker + OST linter as machine gates) or a full goal→plan→execute→verify→close run through the repo-wide agent-harness. Distinct from project-management (how to deliver vs what to build), marketing/landing (from-scratch pages), and engineering/agent-harness (the generic loop engine this orchestrator plugs into).
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.