Two lab technicians in safety glasses testing medical-device equipment, one at a computer and one adjusting an instrument rack

Medical & regulated devices

IEC 62304: medical device software life cycle processes, explained

Last updated:

IEC 62304, "Medical device software — Software life cycle processes," is the standard that spells out, across nine clauses and three software safety classes (A, B and C), what development, maintenance, risk-management, configuration-management and problem-resolution work has to happen around software that is itself a medical device or embedded in one — with far less documented rigor required for low-risk Class A than for B or C. First published in 2006, amended in 2015, and now available as a consolidated Edition 1.1 (170 pages, 2028 stability date), it is one of the most widely cited software standards in medical device regulatory submissions worldwide — and it is explicitly recognized by FDA for use in US premarket review.

Key takeaways

  • Two things sit outside its scope by design.
  • Clauses 1 to 3 cover scope, the single normative reference (ISO 14971) and definitions.
  • Clause 4.1 requires a quality management system; most manufacturers show this through ISO 13485.
  • A software item inherits its parent's class unless the manufacturer documents a segregation rationale for a lower one.

What does it cover, and what does it deliberately leave out?

Per its own scope, IEC 62304 "defines the life cycle requirements for medical device software" and applies "when software is itself a medical device or when software is an embedded or integral part of the final medical device." The IEC 62304 preview adds that it applies regardless of the storage medium (flash, EEPROM, disk) and the delivery method, and that the delivery method itself is not medical device software. That makes it as relevant to an MCU firmware image in a pump as to a desktop viewer.

Two things sit outside its scope by design. It "does not cover validation and final release of the medical device, even when the medical device consists entirely of software"; for stand-alone software those system activities sit in IEC 82304-1. And it "does not prescribe a specific life cycle model": the manufacturer maps the standard's processes, activities and tasks onto its own model, agile or otherwise. Compliance, per clause 1.4, means "implementing all of the processes, activities, and tasks identified in this standard in accordance with the software safety class."

How is the standard structured?

Clauses 1 to 3 cover scope, the single normative reference (ISO 14971) and definitions. Clause 4 sets general requirements. Clauses 5 to 9 are the processes:

Clause Process Core activities
4 General requirements Quality management system, risk management per ISO 14971, software safety classification, legacy software
5 Software development 5.1 planning, 5.2 requirements, 5.3 architecture, 5.4 detailed design, 5.5 unit implementation and verification, 5.6 integration testing, 5.7 system testing, 5.8 release
6 Software maintenance 6.1 maintenance plan, 6.2 problem and modification analysis, 6.3 modification implementation
7 Software risk management 7.1 software contributing to hazardous situations, 7.2 risk control measures, 7.3 verification of those measures, 7.4 risk management of changes
8 Software configuration management 8.1 configuration identification, 8.2 change control, 8.3 configuration status accounting
9 Software problem resolution 9.1 prepare problem reports through 9.8 test documentation contents, including 9.6 trend analysis

Subclause titles come from the standard's contents page. Annex A (informative) holds the rationale, including Table A.1, which summarises which requirements apply to each safety class.

What does Clause 4 require before the first line of code?

Clause 4.1 requires a quality management system; most manufacturers show this through ISO 13485. Clause 4.2 requires a risk management process conforming to ISO 14971, run across the life cycle. Clause 4.3 requires a documented software safety classification (A, B or C) for each software system, and that decision drives how much of Clauses 5 to 9 applies, so it belongs at the start of the project. Clause 4.4 handles legacy software: instead of a retroactive development record, the manufacturer runs a gap analysis against the current requirements and decides from a risk assessment which gaps to close.

How do the three safety classes work, and what did Amendment 1 change?

Class Definition (summarized from the standard) Practical effect
A Software cannot contribute to a hazardous situation, or its contribution does not result in unacceptable risk after risk control measures external to the software Lightest documented-evidence burden in Table A.1
B Software failure could contribute to a hazardous situation resulting in non-serious injury Intermediate evidence burden
C Software failure could contribute to a hazardous situation resulting in death or serious injury Heaviest evidence burden; most activities apply in full

The standard's "Introduction to Amendment 1" says the 2015 amendment added requirements for legacy software "to assist manufacturers who must show compliance to the standard to meet European Directives," and changed classification to include "clarification of requirements and updating of the software safety classification to include a risk-based approach." In practice, risk control measures outside the software, such as a hardware interlock, can lower a software system's class.

A software item inherits its parent's class unless the manufacturer documents a segregation rationale for a lower one. That makes classification an architecture decision: if the Bluetooth logging task shares memory and a scheduler with the dosing loop, arguing it down to Class A after the fact is hard.

How does IEC 62304 treat third-party and open-source code?

As SOUP, software of unknown provenance, and it expects you to identify it. The scope's Note 2 says the standard applies to embedded software "including the requirements concerning software of unknown provenance (see 8.1.2)." FDA's Off-The-Shelf Software guidance (August 2023) describes the same thing from the regulator's side: a "generally available software component, used by a medical device manufacturer for which the manufacturer cannot claim complete software life cycle control (e.g., operating system, printer/display libraries)."

For a typical firmware image, that means the RTOS, the TCP/IP and TLS stacks, the Bluetooth stack, the vendor HAL and any open-source library. A workable routine:

  1. Identify every SOUP itemby name, supplier and exact version under configuration management (8.1.2). A firmware SBOM is the natural record; see our firmware SBOM guide.
  2. Analyse what each item can contribute to a hazardous situationunder Clause 7, including its published defects.
  3. Monitor it after releaseClause 6.2 problem and modification analysis covers field reports; for a cyber device, the FD&C Act section 524B also requires "a software bill of materials, including commercial, open-source, and off-the-shelf software components."
  4. Route new vulnerabilities through Clause 9, so a CVE in a SOUP item becomes a problem report with an investigation, a decision and a verified fix.

The IMDRF SBOM guide and our FDA postmarket cybersecurity guide cover the monitoring side.

How does IEC 62304 map to FDA's documentation levels?

Not one-to-one. FDA's recognition record 13-79 lists IEC 62304 Edition 1.1:2015-06 and ANSI/AAMI/IEC 62304:2006/A1:2016, recognized 14 January 2019, extent "Complete standard." The record's list of related guidance includes FDA's February 2026 cybersecurity guidance.

FDA's device software functions guidance (June 2023) uses two documentation levels instead of three classes. Enhanced Documentation applies where a software failure "could present a hazardous situation with a probable risk of death or serious injury," and FDA says "these risks should be assessed prior to implementation of risk control measures." That is the key difference: IEC 62304 Amendment 1 lets external risk controls lower the class, while FDA's level is set before them. A Class B system can still need Enhanced Documentation.

For the "Software Development, Configuration Management, and Maintenance Practices" element, the guidance accepts a Declaration of Conformity to the FDA-recognized 62304 instead of summaries:

FDA level Declaration of Conformity covers
Basic Subclauses 5.1.1-5.1.3 and 5.1.6-5.1.9, clause 6 and clause 8, "among others as applicable"
Enhanced All of subclause 5.1 (software development planning), clause 6 and clause 8, "among others as applicable"

Without a declaration, an Enhanced submission adds the complete configuration management and maintenance plan documents to the Basic-level summaries.

FDA adds that a Declaration of Conformity to the complete standard "is not needed due to known differences in categorization of device software functions." The Section 524B cybersecurity duties sit alongside all of this; see FDA premarket cybersecurity for medical devices.

How does it sit next to ISO 13485, ISO 14971, the QMSR and IEC 81001-5-1?

IEC 62304 builds on ISO 13485 and ISO 14971 instead of repeating them. In the US, FDA's Quality Management System Regulation now incorporates ISO 13485:2016 by reference, and FDA began using the matching inspection process on 2 February 2026; see our QMSR guide.

For security, IEC 81001-5-1 extends the same life cycle. Its introduction says clauses 5 to 8 "are arranged in the ordering of IEC 62304," that implementations "can extend existing processes at the manufacturer's organization – notably existing processes conforming to IEC 62304," and that it "can therefore support conformance to IEC 62443-4-1." A connected device team runs one life cycle with both sets of activities, not two parallel ones.

Worked example: how would a connected infusion pump team classify its software?

Synthetic example, for illustration only. A pump has a dosing controller on one MCU and a Wi-Fi/Bluetooth module running a vendor RTOS that sends logs to a hospital server.

  1. System classificationOver-infusion could cause serious injury or death, and no hardware measure fully prevents it, so the software system is Class C.
  2. SegregationThe connectivity module runs on separate silicon and talks to the controller over a one-way, checksummed UART that the controller can ignore. The team documents that rationale and classes the connectivity software as Class B, because a corrupted log could delay a clinician's response.
  3. SOUP listRTOS, Wi-Fi stack, TLS library and bootloader go into configuration management with versions, and the firmware SBOM is generated from the build.
  4. FDA levelAssessed before risk controls, a dosing failure presents a probable risk of serious injury, so the submission uses Enhanced Documentation.
  5. DeclarationThe team declares conformity to 62304 subclause 5.1, clauses 6 and 8 and the applicable others, and adds the 524B cybersecurity material.

Is an Edition 2 on the way?

A revision is under way, with no published text. IEC's own catalogue entry for the consolidated edition shows it as "Under development" at the "Approved for CD" stage, with a 2028 stability date; the 2015 amendment's introduction already said "work is continuing in parallel to develop the second edition." Secondary reporting describes proposals to widen the scope to health software, replace the three classes with two rigor levels closer to FDA's Basic/Enhanced split, and add an informative AI/ML annex. Treat those as proposals until IEC publishes the text.

What are the common pitfalls?

  • Classifying after the architecture is fixed. Segregation is hard to argue once tasks share memory and a scheduler.
  • Treating the FDA level as the 62304 class. One is set before risk controls, the other after.
  • An incomplete SOUP list. Bootloaders, vendor HALs and libraries pulled in by the build system are the usual gaps.
  • No route from CVE to problem report. A vulnerability in a SOUP item belongs in Clause 9 like any other defect.
  • Citing the 2006 base text alone. FDA recognizes the consolidated Edition 1.1 and the AAMI adoption.
  • Planning around Edition 2 proposals. Only Edition 1.1 is published and recognized.

What evidence can tooling produce for Clauses 6, 8 and 9?

SoftWSP extracts an SBOM from a firmware image (CycloneDX 1.6 JSON), which can serve as the SOUP inventory for that image. It matches the components against NVD, CISA KEV, FIRST EPSS and CISA CSAF ICS advisories and drafts a cited report that an engineer reviews; watchlist alerts flag new advisories by CVE id or vendor and product. The classification, risk decisions and problem reports stay with your team. See device & firmware security.

This guide summarises IEC's catalogue and preview text for IEC 62304:2006+AMD1:2015, FDA's Recognized Consensus Standards database and guidance, and secondary reporting on the draft Edition 2; it is not a substitute for the purchased IEC text and does not constitute regulatory or legal advice.

Put this guide to work

Frequently asked questions

What is IEC 62304?

IEC 62304, "Medical device software — Software life cycle processes," is an International Standard from IEC technical committee TC 62/SC 62A (common aspects of electrical equipment used in medical practice). Edition 1.0 was published 9 May 2006 (155 pages); Amendment 1 followed on 26 June 2015 (42 pages); the consolidated version, IEC 62304:2006+AMD1:2015 CSV, Edition 1.1, runs 170 pages and carries a 2028 stability date. Per its own scope, it "defines the life cycle requirements for medical device software" and establishes "a common framework for medical device software life cycle processes," applying whether the software is itself a medical device or is embedded in one. It explicitly excludes validation and final release of the complete medical device, and it does not prescribe any one life cycle model — a manufacturer picks its own, and the standard's processes slot into it.

What are the three software safety classes, and why do they matter?

Clause 4.3 requires every software system to be assigned a safety classification — Class A, B or C — based on the severity of harm the software could contribute to. Per the standard, Class A is software that "could not contribute to a hazardous situation" or whose contribution "will not result in unacceptable risk" after other risk controls; Class B covers software whose failure could contribute to a hazardous situation resulting in non-serious injury; Class C covers software whose failure could contribute to a hazardous situation resulting in death or serious injury. The class is not a label — it sets how much life cycle evidence a manufacturer must produce: Annex A's activity table requires far less documented rigor for Class A than for B or C, and a software item inherits its parent's classification unless the manufacturer can demonstrate adequate segregation.

Is IEC 62304 recognized by the FDA?

Yes. FDA's Recognized Consensus Standards database lists IEC 62304 Edition 1.1:2015-06 (the consolidated version) and the equivalent ANSI/AAMI/IEC 62304:2006/A1:2016 both under recognition number 13-79, recognized 14 January 2019, category Software/Informatics, extent of recognition "Complete." A manufacturer can therefore cite conformance to the consolidated Edition 1.1 directly in a premarket submission's Software/Firmware section without separately re-justifying the standard's applicability — though FDA recognition of a standard never substitutes for FDA's own review of the specific submission.

What does IEC 62304 require for legacy software already on the market?

Clause 4.4 ("Legacy software") sets a gap-analysis path for software a manufacturer is not developing fresh: rather than retroactively producing a full Clause 5 development-process record, the manufacturer documents the legacy software's safety classification, identifies which of the standard's requirements are not already met by existing life cycle documentation and field history, and performs a risk analysis to decide whether the gaps need closing before the software can be used in a new or changed medical device. It is the practical route for software a manufacturer inherited, acquired, or has shipped for years before IEC 62304 compliance became a submission expectation.

Is IEC 62304 changing? What would Edition 2 do differently?

A revision is in development; as of this guide, IEC/TC 62/SC 62A and mirror committees such as BSI have an active project (BSI reference 2024-03021) but no published Edition 2 text or firm publication date, so treat specifics as provisional. Independent secondary reporting on the draft describes a proposed retitling and scope broadening from "medical device software" to "health software" generally (aligning with how IEC 81001-5-1 already defines that broader term), a proposed collapse of the three safety classes (A/B/C) into two rigor levels to better match FDA's Basic/Enhanced documentation framework, and a proposed informative annex addressing AI/ML software as a discussion topic. None of this is confirmed normative text — it is what public secondary sources report about a standard still being drafted; always verify against IEC's or your national body's current project status before planning compliance work around it.

Sources

  1. IEC: IEC 62304:2006+AMD1:2015 CSV — Medical device software — Software life cycle processes (catalogue record, consolidated Edition 1.1, 170 pages, TC 62/SC 62A, ICS 11.040.01, stability date 2028)
  2. IEC: IEC 62304:2006 — Medical device software — Software life cycle processes (catalogue record, Edition 1.0, published 2006-05-09, 155 pages)
  3. IEC: IEC 62304:2006/AMD1:2015 — Amendment 1 (catalogue record, published 2015-06-26, 42 pages, prepared by TC 62/SC 62A)
  4. FDA: Recognized Consensus Standards database — search results for "62304" (recognition number 13-79, recognized 01/14/2019, covering IEC 62304 Ed.1.1:2015-06 CSV and ANSI/AAMI/IEC 62304:2006/A1:2016, category Software/Informatics, extent Complete)
  5. BSI Standards Development: BS EN IEC 62304 Ed2 project page (draft revision project reference 2024-03021; independent secondary reporting — confirm against the live BSI project page)
  6. IntuitionLabs: "IEC 62304 Guide: Medical Device Software Safety Standard" (independent secondary analysis, including reported Edition 2 draft proposals)
  7. Qualitiso: "IEC 62304 Medical device - Software life cycle" (independent secondary analysis of safety classification and ISO 13485/ISO 14971 relationship)
  8. IEC 62304 Edition 1.1 2015-06 consolidated version preview (iTeh): foreword, introduction, Introduction to Amendment 1, scope 1.1-1.4, contents
  9. FDA: Recognized Consensus Standards record 13-79 (IEC 62304 Ed. 1.1 and ANSI/AAMI/IEC 62304:2006/A1:2016; related guidance list)
  10. FDA: Content of Premarket Submissions for Device Software Functions (June 2023) — Basic and Enhanced Documentation Levels, IEC 62304 Declaration of Conformity subclauses
  11. FDA: Off-The-Shelf Software Use in Medical Devices (August 2023)
  12. FDA: Quality Management System Regulation (QMSR) — 21 CFR Part 820 incorporating ISO 13485:2016 by reference
  13. 21 U.S.C. 360n-2 (FD&C Act section 524B): ensuring cybersecurity of devices, including the SBOM requirement
  14. IEC 81001-5-1:2021 preview (iTeh): introduction on clause ordering relative to IEC 62304 and support for IEC 62443-4-1
Was this guide helpful?

In this cluster

IEC 62304: medical device software life cycle processes, explained