medical-device-code-review

Review medical device software code for IEC 62304 and NMPA compliance.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Medical device software must meet strict safety and regulatory standards like IEC 62304, YY/T 0664, and NMPA registration requirements, but manually auditing code against these rules is slow and error-prone. This Skill automates the review of code safety, cybersecurity, and quality against those standards. ## Core Features & Use Cases - Safety Classification & Audit Workflow: Determines the IEC 62304/YY/T 0664 software safety class (A/B/C) first, then applies the matching review rigor for documentation, testing coverage, and traceability. - Security & Quality Defect Detection: Flags hardcoded credentials, unencrypted PHI, injection flaws, race conditions, integer overflows, missing timeouts, and low test coverage against defined thresholds. - China NMPA Compliance Checks: Verifies conformity with GB 9706.1-2020, YY/T 0664-2020, cybersecurity guidance, and data protection laws, producing a structured findings report with severity levels. - Use Case: A team developing infusion pump firmware (Class C) submits their C++ codebase for review and receives a report listing critical issues with file/line references, plus a compliance status summary for IEC 62304 and NMPA requirements. ## Quick Start Review this medical device software code for IEC 62304 and NMPA compliance and list any critical safety or security issues.

Frequently Asked Questions about medical-device-code-review

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

FAQPage Schema
How do I review medical device software code for IEC 62304 compliance?

Start by determining the software safety class (A, B, or C) based on potential harm, then audit documentation, hazard analysis, code quality, and test coverage against class-specific requirements. Class C software requires over 90% MC/DC coverage and full traceability from requirements to tests.

What security issues are most common in medical device code?

The most frequent issues are hardcoded credentials, unencrypted patient data in transit, missing authentication on interfaces, injection flaws, and outdated dependencies with known CVEs. Reviews follow the OWASP Medical Device Top 10 and FDA cybersecurity guidance.

Does this code review support China NMPA registration requirements?

Yes, it checks conformity with YY/T 0664-2020, GB 9706.1-2020, the NMPA software registration guidance (2022), and cybersecurity review principles. It also verifies data protection compliance with China's Data Security Law and Personal Information Protection Law.

What test coverage is required for Class C medical device software?

Class C software requires over 90% statement, branch, and MC/DC (Modified Condition/Decision Coverage) under IEC 62304 and YY/T 0664. Class B requires over 70% branch coverage, while Class A only recommends statement coverage.

What output format does the code review produce?

The review produces a structured report with an audit summary, safety classification, and findings grouped into critical, major, and minor issues with file and line references. It also includes a compliance status section for IEC 62304, GB 9706.1, and cybersecurity requirements.