본문으로 건너뛰기
cccskills
무료GitHub에 공개

mdr-745-specialist

Supports preparation for EU medical device regulation reviews by organizing device classification, technical documentation, clinical evidence, and post-market monitoring. Includes a tool to identify documentation and compliance gaps and prioritize the next steps.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

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

설치 방법 보기

이럴 때 유용합니다

  • Documenting a device classification rationale under MDR
  • Checking technical documentation before a review
  • Planning clinical evaluation and identifying evidence gaps
  • Reviewing post-market monitoring and safety report schedules

포함된 파일(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

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Audit web applications for accessibility issues against WCAG 2.2 Level A and AA, the web accessibility standards. Get framework-specific code fixes, contrast checks, verification steps, and reports, with options for automated checks in development pipelines.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Audit a web application before release
  • Fix contrast and keyboard navigation issues
  • Prepare accessibility reports for stakeholders
alirezarezvani/claude-skills2.9만2026년 10월 22일 업데이트

Plan A/B tests that compare page variations, from headlines to pricing layouts. Define a hypothesis, choose success metrics, calculate sample size and duration, and prepare launch checks and results reports to support decisions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Comparing landing page headlines
  • Testing signup button changes
  • Planning pricing page experiments
alirezarezvani/claude-skills2.9만2026년 10월 22일 업데이트

Create paid ad headlines and body copy tailored to each platform's character limits. Use existing performance data to develop variations, explore new messaging angles, and check copy for length, quality, and potential rejection risks.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Creating Google RSA headlines
  • Writing Meta and LinkedIn ad copy
  • Developing variations of successful ads
alirezarezvani/claude-skills2.9만2026년 10월 22일 업데이트

Review code changes from three critical perspectives: production failures, maintainability, and security. Get a consolidated report that ranks findings by severity and provides merge guidance, helping examine assumptions that an ordinary self-review may overlook.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Reviewing a pull request before merging
  • Getting a second opinion on AI-written code
  • Checking authentication or data access code
alirezarezvani/claude-skills2.9만2026년 10월 22일 업데이트

aeo

무료

Audit and improve content intended for citation in AI answers. Review evidence, author information, and structure, generate revised content and structured metadata, and keep a local record of observed citations across AI services.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Audit existing articles for evidence and credibility gaps
  • Revise article structure and references for AI answers
  • Record citations observed across AI services
alirezarezvani/claude-skills2.9만2026년 10월 22일 업데이트

Create signed records for consequential agent actions such as deployments, deletions, and payments. Decide which actions need evidence, record the agent, action, target, and policy, then verify the resulting certificate offline to detect later changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Creating signed records for production deployments
  • Preserving evidence of deletions and payments
  • Recording access grants for later review
alirezarezvani/claude-skills2.9만2026년 10월 22일 업데이트

alirezarezvani의 스킬 모두 보기

이 스킬의 문제 신고