The standard, first published by IEC in 2006 and amended in 2015 (available as the consolidated IEC 62304:2006+AMD1:2015), sets a common framework of life cycle processes for building and maintaining medical device software, including software development planning, the maintenance process, and the configuration management process. It does not cover validation and final release of the finished medical device, which sit with the manufacturer's quality system.
How FDA uses it
FDA's 2023 guidance on premarket submissions for device software functions lists IEC 62304 among the standards it harmonized with. For the documentation element on development, configuration management, and maintenance practices, a sponsor can submit summaries of its plans or a declaration of conformity. At the Basic Documentation level the declaration covers subclauses 5.1.1 to 5.1.3 and 5.1.6 to 5.1.9, clause 6 (maintenance), and clause 8 (configuration management). At the Enhanced level it covers subclause 5.1, clause 6, and clause 8, among others as applicable. The alternative at the Enhanced level is the Basic-level summaries plus the complete configuration management and maintenance plan documents, so a 62304 process that already produces those plans gives the sponsor a choice.
The same guidance warns that design history documentation created long after development can raise questions about whether the developer controlled its design process. In practice, that means producing the 62304 records as you build, instead of assembling them just before the submission. Onix Health builds medical device software under an IEC 62304 process and produces the software documentation an FDA submission needs. Our full write-up on safety classes, common misreadings, and how the clauses map to everyday engineering work is in IEC 62304 in practice.