fda-med-device

Installation
SKILL.md

FDA Device Software Guidance and the QMSR

Source: U.S. FDA (CDRH/CBER). Adapted from the sibling 2026-09-24 prototype build and re-checked against the 2026-10-12 FDA source pin, the seven documents vetted in LICENSE as rows S1-S4 and S6-S8 | Licence: Public Domain (US Government work, 17 U.S.C. 105) | Chapters: 12

When to use

Prerequisites: none: plain Markdown; no MCP server, API key, or licence tier needed at runtime.

Use this skill for US FDA questions about software in or around medical devices: what documentation a premarket submission needs, how software must be validated, what the Quality Management System Regulation requires after the 2026-02-02 transition, what cybersecurity artifacts FDA expects, where a software function stops being a device (clinical decision support, MDDS), when a software change triggers a new 510(k), and how eSTAR structures the submission. The pack answers with FDA's own frameworks, cited by chapter and source row.

How to Use This Skill

  • Without arguments: read the Core Frameworks below, covering documentation levels, validation vs assurance, the QMSR transition, the SBOM and 524B obligations, and the 510(k) change trigger.
  • With a topic: use the Topic Index to find the chapter, then ask directly (e.g. "what documentation level applies for this device", "does this OTS library need enhanced testing").
  • With a chapter: ch01 orientation; ch02-ch04 documentation and assurance; ch05-ch07 QMSR and cybersecurity; ch08-ch09 scope boundaries and the cybersecurity submission package; ch10-ch12 changes, CDS, and eSTAR.

Supporting files: glossary.md, cheatsheet.md.

Core Frameworks & Mental Models

Installs
1
GitHub Stars
56
First Seen
Nov 5, 2026