Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
alirezarezvani avatar

Mdr 745 Specialist

  • 746 installs
  • 23.5k repo stars
  • Updated July 17, 2026
  • alirezarezvani/claude-skills

MDR 745 Specialist is a regulatory compliance skill that generates clinical evidence frameworks and literature-based justifications aligned with EU MDR Annex XIV for developers building AI-powered medical or regulated he

About

MDR 745 Specialist is an installable skill from alirezarezvani/claude-skills focused on EU Medical Device Regulation clinical evidence requirements. It documents clinical evaluation processes, literature-based evidence, clinical investigation requirements, and post-market clinical follow-up under MDR Annex XIV guidance. An evidence hierarchy table ranks randomized controlled trials through lower-strength sources with usage guidance for Class III and high-risk claims. Developers reach for MDR 745 Specialist when drafting compliant clinical evaluation documentation for regulated health or medical AI tools. Output targets formal evidence frameworks rather than general HIPAA checklists.

  • Evidence hierarchy with 5 strength tiers from RCTs to expert opinion
  • Clinical evidence requirements by device class (I, IIa, IIb, III)
  • Step-by-step clinical evidence pathway starting with device classification
  • Literature-based evidence protocols and post-market clinical follow-up guidance
  • MDR Annex XIV clinical evaluation and PMCF templates

Mdr 745 Specialist by the numbers

  • 746 all-time installs (skills.sh)
  • Ranked #318 of 1,881 Documentation skills by installs in the Skillselion catalog
  • Security screen: MEDIUM risk (skills.sh audit)
  • Data as of Jul 31, 2026 (Skillselion catalog sync)
npx skills add https://github.com/alirezarezvani/claude-skills --skill mdr-745-specialist

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs746
repo stars23.5k
Security audit2 / 3 scanners passed
Last updatedJuly 17, 2026
Repositoryalirezarezvani/claude-skills

How do you document EU MDR clinical evidence?

Generate compliant clinical evidence frameworks and literature-based justifications when building AI-powered medical or regulated health tools.

Who is it for?

Developers building regulated medical or health AI products who must produce MDR Annex XIV clinical evaluation and PMCF documentation.

Skip if: Teams shipping non-medical consumer apps or projects that only need generic application security scans without EU device regulation scope.

When should I use this skill?

A developer asks about EU MDR clinical evaluation, Annex XIV evidence, literature-based justification, or post-market clinical follow-up for health software.

What you get

Clinical evidence framework, literature review justification, clinical evaluation plan sections, and post-market clinical follow-up guidance aligned with MDR Annex XIV.

  • clinical evidence framework
  • literature-based justification document

Files

SKILL.mdMarkdownGitHub ↗

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, or Annex X + XIQMS + tech doc assessment, or type exam + production
IIIAnnex IX, or Annex X + XIFull QMS + product dossier, or type exam + production

---

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
PSURArticle 86 — Class IIa and higherPer Art. 86(1) schedule below
PMCF PlanAnnex XIV Part BUpdate with CER
PMCF ReportAnnex XIV Part BAnnual (Class III)
VigilanceArticles 87-92As events occur

PSUR Schedule

ClassFrequency (MDR Art. 86(1))
Class IIIUpdated at least annually
Class IIb (all, incl. implantable)Updated at least annually
Class IIaWhen necessary, at least every 2 years
Class INo PSUR — PMS report instead (Art. 85)

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

Related skills

How it compares

Choose MDR 745 Specialist for EU device clinical evidence documentation; use general security audit skills for application vulnerability scanning without regulatory clinical evaluation scope.

FAQ

What regulation does MDR 745 Specialist cover?

MDR 745 Specialist addresses EU Medical Device Regulation requirements, including Annex XIV clinical evaluation, literature-based evidence, clinical investigations, and post-market clinical follow-up.

Who should use MDR 745 Specialist?

MDR 745 Specialist fits developers building AI-powered medical or regulated health tools who need compliant clinical evidence frameworks rather than informal risk notes.

Is Mdr 745 Specialist safe to install?

skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

Documentationagentsresearchautomation

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.