medical-device-software

Installation
SKILL.md

Medical Device Software

Portability: 4 stdlib scripts, no network. Fill CSVs, run, keep the output with the software file. Not a conformity assessment. IEC 62304 is paywalled: clause markers here come from two agreeing secondary sources (🟡) and your licensed copy prevails. A notified body or FDA reviewer can read a borderline call differently.

Software files fail review in the same places: a class claimed lower than the harm allows, an "external" risk control that lives in the same software system, a SOUP list with "latest" as the version and no anomaly review, a trace matrix with risk controls nobody tested, and security treated as an afterthought. Three classifications get confused, and they use different inputs:

Question Decided by Assessed
IEC 62304 class A/B/C (which activities) worst-case harm, clause 4.3 + A1 Fig. 3 after risk controls external to the software system
FDA Basic / Enhanced (what you submit) probable risk of death or serious injury before any risk controls
FD&C Act 524B cyber device software + any internet-capable path (USB counts) not risk-based

Workflow

Installs
4
GitHub Stars
30.2K
First Seen
11 days ago