medical-device-mdr-auditor

Audits medical device technical documentation for EU MDR 2017/745 compliance.

1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/HalseyYang/Skills-HY --skill medical-device-mdr-auditor-halseyyang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: medical-device-mdr-auditor
Source: https://github.com/HalseyYang/Skills-HY/tree/main/medical-device-mdr-auditor
Command: npx skills add https://github.com/HalseyYang/Skills-HY --skill medical-device-mdr-auditor-halseyyang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Preparing medical device technical documentation for EU MDR (Regulation 2017/745) submission requires verifying that all mandatory documents—Clinical Evaluation Reports, PMS plans, PMCF plans, SSCP—are present and complete for the device's risk class. Manual checks are error-prone and can miss critical gaps that delay regulatory approval. ## Core Features & Use Cases - Class-Based Document Checklists: Verifies required documents against device classification (I, IIa, IIb, III), including CER, PMS Plan, PMCF Plan, SSCP, and risk management files. - Content-Level Inspection: Scans CER and PMS documents for required sections such as clinical data, benefit-risk conclusions, trend reporting, and data collection methods. - Structured Compliance Reports: Outputs JSON audit reports with findings categorized as CRITICAL, MAJOR, MINOR, or INFO, plus an overall status of COMPLIANT, PARTIAL, or NON_COMPLIANT. - Use Case: Before submitting a Class IIa device technical file to a notified body, run the auditor on the documentation folder to confirm the PMCF plan and clinical evaluation report are present and complete. ## Quick Start Ask the assistant to audit your technical documentation folder for MDR compliance by specifying the folder path and device class, for example: check whether my Class IIa device technical file meets MDR requirements.

Frequently Asked Questions about medical-device-mdr-auditor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check medical device technical documentation for MDR compliance?

Run the audit script with the input folder path and device class, for example: python scripts/main.py --input /path/to/technical/file --class IIa. The tool scans for required documents and outputs a JSON compliance report with findings and an overall status.

What documents does MDR 2017/745 require for Class IIa devices?

Class IIa devices require a Clinical Evaluation Report, Clinical Evaluation Plan, risk management documentation, technical documentation, a Post-Market Surveillance plan, and a PMCF plan. Class IIb adds the SSCP, and Class III additionally requires a PMCF Evaluation Report.

Can I audit multiple device documentation folders at once?

Yes, use the --config parameter with a JSON configuration file listing multiple input paths and device classes. The script runs batch checks and reports each result separately with its own compliance status.

Does the MDR auditor check PDF and Word document contents?

The script accepts PDF and DOCX files, but content extraction for these formats is a simplified placeholder that only reads the file name. Full text inspection currently works reliably for plain text files only.

What do the exit codes of the MDR audit script mean?

Exit code 0 means fully compliant, 1 means compliant with warnings, 2 means the audit failed with deficiencies, and 3 indicates an execution error such as a missing input path. Use these codes to integrate the check into CI or review pipelines.