本文へ移動
cccskills
無料GitHub で公開

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').

インストール方法を見る

含まれるファイル(5)

  • SKILL.md10.2 KB
  • references/clinical-evidence-requirements.md9.2 KB
  • references/mdr-classification-guide.md8.7 KB
  • references/technical-documentation-templates.md10.1 KB
  • scripts/mdr_gap_analyzer.py17.7 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Accessibility audit skill for scanning, fixing, and verifying WCAG 2.2 Level A and AA compliance across React, Next.js, Vue, Angular, Svelte, and plain HTML codebases. Use when auditing accessibility, fixing a11y violations, checking color contrast, generating compliance reports, or integrating accessibility checks into CI/CD pipelines.

日本語の概要は準備中です。原文の説明を表示しています。

alirezarezvani/claude-skills2.8万2026年8月30日 更新

When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.

日本語の概要は準備中です。原文の説明を表示しています。

alirezarezvani/claude-skills2.8万2026年8月30日 更新

When the user needs to generate, iterate, or scale ad creative for paid advertising. Use when they say 'write ad copy,' 'generate headlines,' 'create ad variations,' 'bulk creative,' 'iterate on ads,' 'ad copy validation,' 'RSA headlines,' 'Meta ad copy,' 'LinkedIn ad,' or 'creative testing.' This is pure creative production — distinct from paid-ads (campaign strategy). Use ad-creative when you need the copy, not the campaign plan.

日本語の概要は準備中です。原文の説明を表示しています。

alirezarezvani/claude-skills2.8万2026年8月30日 更新

Adversarial code review that breaks the self-review monoculture. Use when you want a genuinely critical review of recent changes, before merging a PR, or when you suspect Claude is being too agreeable about code quality. Forces perspective shifts through hostile reviewer personas that catch blind spots the author's mental model shares with the reviewer.

日本語の概要は準備中です。原文の説明を表示しています。

alirezarezvani/claude-skills2.8万2026年8月30日 更新

aeo

無料

Answer Engine Optimization (AEO) skill — optimize content to be cited by AI language models (ChatGPT, Perplexity, Claude, Gemini, Mistral) as authoritative sources. Distinct from SEO — AEO optimizes for citation in LLM-generated responses, not search rankings. Use when planning content for AI-first search audiences, auditing existing content for E-E-A-T signals, tracking which pages get cited by which LLMs, or building a citation-friendly content strategy. Triggers — 'AEO audit', 'optimize for ChatGPT', 'get cited by Perplexity', 'LLM citation strategy', 'answer engine optimization', 'content for AI search', 'E-E-A-T audit'. Output is a markdown audit report (default) or JSON for pipeline integration. Stdlib-only Python tools.

日本語の概要は準備中です。原文の説明を表示しています。

alirezarezvani/claude-skills2.8万2026年8月30日 更新

Mint a tamper-evident, post-quantum-signed receipt for a consequential agent action (deploy, delete, pay, grant-access, model decision) so it can be verified later from the certificate alone. Use when an autonomous agent takes a side-effecting action that may need to be proven later, or when satisfying EU AI Act Article 12 record-keeping. Three decisions: whether an action needs a receipt, minting it, verifying it. Signing is delegated to the open-source OpenAgentOntology package. Not after-the-fact log analysis; not a hosted notary; not a legal opinion.

日本語の概要は準備中です。原文の説明を表示しています。

alirezarezvani/claude-skills2.8万2026年8月30日 更新

alirezarezvani のスキルをすべて見る

このスキルの問題を報告する