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, and EUDAMED integration.
- License 许可
- MIT
- 所属仓库
- msm47/Gitskil
- 最近更新
- 2026-06-22
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- mdr-745-specialist
- triggers
- [ "MDR compliance", "EU MDR", "medical device classification", "Annex VIII", "technical documentation", "clinical evaluation", "PMCF", "EUDAMED", "UDI", "notified body" ]
- description
- 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, and EUDAMED integration.
02 资源文件 4
- 参考文档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
03 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
- 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 + X or X + XI | Type exam + production |
| III | Annex IX + X | Full QMS + type exam |
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 | Class IIa and higher | Per class schedule |
| 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 |
|---|---|
| Class III | Annual |
| Class IIb implantable | Annual |
| Class IIb | Every 2 years |
| Class IIa | When necessary |
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
04 同仓库更多 Skills
syllabus
Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Triggers whenever a user uploads a syllabus, course outline, or curriculum document and wants supplementary readings. Also triggers on: 'syllabus reading list', 'find papers for my course', 'create a reading list from this syllabus', 'recent research for my class', 'supplementary readings', 'find journal articles for these topics', 'what recent papers cover this material', 'any new research on these course topics', 'update my syllabus with recent papers'. Even casual mentions when a syllabus is attached should trigger this skill.
research
Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends/sentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Triggers — "research [topic]", "look into [topic]", "what do we know about [topic]", "investigate [topic]", "find me information on [topic]", "do some research on [topic]", "I need to understand [topic]", or any research request that doesn't obviously match a more-specific specialist skill. Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.
pulse
Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X/Twitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend/sentiment/problems/opportunities/comparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Triggers: 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]', or any variation requesting multi-source recency intelligence on a topic. Also use for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.
patent
Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search / freedom-to-operate / competitive landscape / acquisition diligence / litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Triggers: 'prior art search for [invention]', 'patent search on [topic]', 'freedom to operate analysis', 'FTO for [product]', 'patent landscape for [field]', 'is [invention] novel', 'patents on [topic]', 'competitive patent analysis', 'prior art for litigation', 'patent diligence on [company]'. Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.
notebooklm
Browser automation skill for controlling Google's NotebookLM. Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio Overview, infographics, slide decks, study guides, briefing docs, mind maps, timelines, FAQs), and creating new notebooks. Triggers on any phrase involving NotebookLM — 'open NotebookLM', 'check my [name] notebook', 'pull info from NotebookLM', 'ask my notebook about X', 'add [source] to NotebookLM', 'create an infographic in NotebookLM', 'use NotebookLM Studio', 'generate a slide deck from my notebook', or any variation where the goal involves NotebookLM. Requires browser automation environment — fails gracefully when unavailable.
litreview
Academic literature orientation skill that searches papers via Consensus, builds a strategic search plan using PICO (default) or SPIDER / Decomposition / hybrid as fallbacks, and synthesizes findings into a professionally formatted Word document (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5/10/20 queries) controls coverage vs. speed. Output is a 'launching pad' — not a finished review, but an orientation guide that lets a researcher dive in confidently. Triggers: 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'. Do NOT trigger for single one-off paper searches where the user just wants a quick list — that's a plain Consensus search.