技能 硬件工程 医疗器械软件合规

医疗器械软件合规

v20261116
medical-device-software
面向医疗器械软件与 SaMD 的合规检查工具:按 IEC 62304 判定 A/B/C 安全等级,核查生命周期活动缺口、SOUP 与 SBOM 清单、追踪矩阵,并评估 FDA 文档等级与 524B 网络设备义务。
获取技能
280 次下载
概览

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:

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

Workflow

# 1 - Classify: system and item classes, FDA level, cyber device?
python scripts/software_safety_classifier.py --inventory assets/software_inventory.example.csv
# 2 - Gap check: is every activity the class requires done, with evidence?
python scripts/lifecycle_gap_check.py --class B --security --assessment assets/lifecycle_assessment.example.csv
# 3 - SOUP: identified, specified, anomaly lists reviewed, in the SBOM?
python scripts/soup_register_check.py --register assets/soup_register.example.csv --sbom assets/sbom.example.cdx.json --cyber-device
# 4 - Release: every requirement tested, every risk control verified?
python scripts/trace_matrix_check.py --matrix assets/trace_matrix.example.csv --class C --release

Class first: steps 2 to 4 take the class from step 1. --template prints an
empty input; lifecycle_gap_check.py --list --class X prints the required ids.

The gates block on (exit 4)

  1. A claimed class below what the harm allows, or an item below its system without a segregation rationale — 62304 4.3.
  2. An external risk control used to lower the class that is not itself verified — 62304 4.3 (A1).
  3. A required activity NOT MET, or NA where the clause is not conditional — the class table (A1 Table A.1).
  4. A SOUP item with no exact version (8.1.2), no stated requirements (5.3.3/5.3.4) or no anomaly-list review (7.1.3) for class B/C, or past end of support with no plan.
  5. A class B/C risk control with no hazard or no passing test (7.3.1, 7.3.3); with --release, any untested requirement or open failed result without an anomaly record (5.7, 5.8).
  6. A cyber device with no vulnerability monitoring on a SOUP item — 524B(b)(1).

Hard rules

  • Unassessed is not MET. The gap check refuses a file that skips a required id.
  • Unclassified is class C. Unknown inputs never round down.
  • Severity decides the class, not probability. Only verified external controls lower it.
  • Class A still tests. Software system testing (5.7) applies to every class since A1.
  • Mark the confidence. 🟢 primary text checked · 🟡 secondary sources agree · 🔴 not verified. EN 62304 and EN IEC 81001-5-1 are not confirmed as cited in the OJ under the MDR; never claim presumption of conformity without checking the current list.
  • Never sign or submit. The scripts prepare evidence; the manufacturer's named people approve the class, the release and the submission.

Scripts

ScriptRoleExit codes
scripts/software_safety_classifier.py62304 4.3 class per system and item, segregation, FDA documentation level, 524B cyber device0 classified · 2 findings · 3 bad input · 4 blocked
scripts/lifecycle_gap_check.py62304 activities by class (+4.4 legacy), 81001-5-1 activities with --security0 ready · 2 gaps · 3 · 4 blocked
scripts/soup_register_check.py8.1.2, 5.3.3/5.3.4, 7.1.3, end of support, 81001-5-1 risk-transfer category, SBOM cross-check (CycloneDX/SPDX)0 pass · 2 · 3 · 4 blocked
scripts/trace_matrix_check.pysystem → software requirement → test → result, risk control → hazard, release state0 pass · 2 · 3 · 4 blocked

All support --help, --sample, --template and --output json.

References and assets

信息
分类 硬件工程
名称 medical-device-software
版本 v20261116
大小 40.21KB
更新时间 2026-11-17
语言