Token导航 LogoToken导航TokenDH.com
研究检索只读clawhub未标认证来源可访问clear审计通过

mdr-745-specialistMDR 745 专家

Agent Skill

mdr-745-specialist 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

56,720

周安装

2,317

GitHub Stars

1

下载量

18,165
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:mdr-745-specialist(MDR 745 专家)
来源仓库:https://github.com/alirezarezvani/mdr-745-specialist
安装命令:
openclaw skills install mdr-745-specialist
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install mdr-745-specialist

简介

mdr-745-specialist 专注欧盟 MDR 2017/745 法规合规,支持医疗器械分类决策。

  • 处理技术文档编写、临床证据收集和上市后监督要求。
  • 提供公告机构预审模拟和标签语言本地化建议。
  • 安装命令:openclaw skills install mdr-745-specialist,需医学背景知识验证。
  • 所有输出必须标注适用范围,不可声称具备法律效力。

SKILL.md

name
mdr-745-specialist
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.
triggers

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 + X or X + XIType exam + production
IIIAnnex IX + XFull QMS + type exam

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
PSURClass IIa and higherPer class schedule
PMCF PlanAnnex XIV Part BUpdate with CER
PMCF ReportAnnex XIV Part BAnnual (Class III)
VigilanceArticles 87-92As events occur

PSUR Schedule

ClassFrequency
Class IIIAnnual
Class IIb implantableAnnual
Class IIbEvery 2 years
Class IIaWhen necessary

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

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

74.67%
按下载量换算13,564

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills