In short
- IEC 62304:2006 with Amendment 1:2015 defines the life cycle processes for medical device software and scales what you must do and document by software safety class A, B or C.
- The class follows from the risk analysis, only risk controls outside the software can lower it, and unclassified software is treated as Class C.
- FDA's Basic and Enhanced documentation levels are a separate scheme, but a declaration of conformity to the FDA-recognized version of IEC 62304 can cover the development, maintenance and configuration management part of a premarket submission.
IEC 62304 is the international standard for the software life cycle of medical devices. It does not tell you which tools, languages or methodology to use. It requires a defined set of processes (planning, requirements, architecture, verification, maintenance, configuration management, risk management and problem resolution) and scales how much of that you must do and document by the software's safety class: A, B or C. The version in force is IEC 62304:2006 with Amendment 1 from 2015, published together as edition 1.1. FDA accepts a declaration of conformity to it in premarket submissions for some parts of the software documentation.
What is IEC 62304, and what does it cover?
The IEC catalogue describes IEC 62304:2006+AMD1:2015 as defining the life cycle requirements for medical device software: a common framework of processes, activities and tasks. It applies to the development and maintenance of medical device software, both when the software is itself a medical device and when it is embedded in or an integral part of a device. The consolidated edition 1.1 was published on 26 June 2015 by IEC subcommittee 62A, and the IEC lists its stability date as 2028.
One boundary trips up software-only companies. The standard says it does not cover validation and final release of the medical device, even when the device consists entirely of software. IEC 62304 covers how you build and maintain the software. Showing that the finished product meets user needs in its intended use is handled by your quality management system and design controls.
IEC 62304 works alongside other standards. It relies on ISO 14971 for risk management. In the US, FDA's Quality Management System Regulation, which took effect on February 2, 2026, incorporates ISO 13485:2016 by reference. Cybersecurity is a separate topic: FDA's premarket cybersecurity guidance names IEC 81001-5-1 among the secure development frameworks a manufacturer can use.
What are the IEC 62304 software safety classes?
The safety class decides how much process and documentation the standard requires. As summarized by the Johner Institute for the 2015 edition:
- Class A: the software system cannot contribute to a hazardous situation, or it can but the resulting risk is acceptable after risk control measures that sit outside the software system.
- Class B: the software can still contribute to a hazardous situation after risk controls, and the possible harm is not severe (non-serious injury).
- Class C: the software can still contribute to a hazardous situation after risk controls, and the possible harm is severe, up to death.
Three rules follow from the class definitions and are where teams most often go wrong.
- If you do not classify, everything is Class C. The standard treats an unclassified software system and all its components as the highest class.
- Risk controls that lower the class must be outside the software system, typically in hardware or in the clinical workflow, and you must verify they are implemented and effective. Controls that depend on people usually need usability testing as evidence. A software component that monitors another component inside the same system can be a risk control, but it does not reduce the safety class.
- Software items can carry different classes only if their independence is justified by the architecture, for example through weak or no coupling. The highest class among the items sets the class of the system.
The class changes the required activities. For Class A, the standard requires software requirements and a software release process, and since Amendment 1 also system testing. Class B adds software architecture and further verification. Class C adds detailed design. The Johner Institute recommends developing to Class C practice regardless, since skipping detailed design or unit testing does not match professional development practice. The class then mainly decides how much of that work the standard obliges you to document.
Do IEC 62304 classes match FDA documentation levels?
No. FDA's June 2023 guidance, Content of Premarket Submissions for Device Software Functions, replaced its 2005 software guidance and uses two documentation levels instead of safety classes. Enhanced Documentation applies when a failure or flaw of a device software function could present a hazardous situation with a probable risk of death or serious injury, assessed before risk controls are applied. Basic Documentation applies to everything else. FDA also generally recommends Enhanced Documentation for Class III devices and for device constituents of combination products.
The two systems answer different questions. A 62304 safety class is assigned to a software system or item after external risk controls are considered. The FDA documentation level is assigned to the device as a whole, based on the risks of its software functions before risk controls. You need both, and they will not always line up.
How does FDA use IEC 62304 in a 510(k) or De Novo?
The FDA software guidance lists the documentation elements it expects in a premarket submission, and IEC 62304 conformity can stand in for one of them. For software development, configuration management and maintenance practices, a sponsor can either describe them or provide a declaration of conformity to the FDA-recognized version of IEC 62304. For Basic Documentation the declaration should cover subclauses 5.1.1 to 5.1.3 and 5.1.6 to 5.1.9 of development planning, clause 6 (the software maintenance process) and clause 8 (the software configuration management process). For Enhanced Documentation it should cover subclause 5.1 in full plus clauses 6 and 8.
The declaration does not replace the rest of the file. The guidance still expects:
- A documentation level evaluation with its rationale.
- A software description covering features, functions, inputs, outputs and hardware platforms.
- A risk management file: plan, risk assessment and report.
- A software requirements specification with enough detail to trace it to the risk file, design and tests.
- A system and software architecture design with diagrams of modules, layers, interfaces and data flow.
- A software design specification for Enhanced Documentation. For Basic, it stays in the design history file and FDA may request it.
- Software testing as part of verification and validation: a summary of unit, integration and system testing, a system-level test protocol and report, and for Enhanced Documentation the unit and integration protocols and reports.
- A software version history of every tested version, with dates and the changes from the previous one.
- A list of unresolved software anomalies, each with an evaluation of its impact on safety and effectiveness.
FDA's summary of what this package should demonstrate is close to the spirit of 62304: planning, requirements, risk assessment, design reviews, traceability, change management, testing plans and results. If your 62304 process produces those records as you work, the submission package is mostly assembly.
What does IEC 62304 require for SOUP and third-party libraries?
SOUP, software of unknown provenance, is a software item that is already developed and generally available and was not developed for the device, or a previously developed item without adequate records of its development process. Open-source libraries, operating systems and commercial SDKs usually fall here. A medical device software system as a whole cannot be claimed to be SOUP.
- Specify the requirements the SOUP must meet for your use, like any other component, and test that they are met.
- Specify what the SOUP itself depends on, such as available memory, operating system, runtime and library versions, and check those prerequisites are satisfied.
- Identify each SOUP item precisely: name, version and manufacturer, plus where its bug reports and release notes are published.
- Feed the SOUP's published anomalies into your risk analysis, and keep tracking them after release as part of post-market surveillance.
- Treat each SOUP item at the safety class of the software system or item that contains it.
This overlaps with FDA's cybersecurity expectations. FDA's premarket cybersecurity guidance asks manufacturers to document all software components and to provide a software bill of materials. For cyber devices, an SBOM is required by section 524B of the FD&C Act. A well-kept SOUP list is most of the way to an SBOM.
What do teams get wrong about IEC 62304?
- Treating it as a coverage target. The standard asks for verification that traces to requirements, not a percentage of lines executed.
- Classifying low to save paperwork. Classification follows the risk analysis, and the risk controls that justify a lower class must live outside the software and be verified.
- Writing the documents at the end. Plans, requirements and architecture decisions written after the code describe what was built, not what was intended, and the gaps show in the traceability.
- Forgetting maintenance. Clause 6, maintenance, and clause 8, configuration management, are both named in FDA's declaration-of-conformity recommendations. A released device still needs controlled change, and the version history FDA asks for is the trail of that control.
- Assuming 62304 covers cybersecurity. It does not. FDA expects a separate security risk management process, and points to frameworks such as IEC 81001-5-1.
Is a new edition of IEC 62304 coming?
Yes, but not soon. An earlier second-edition draft was marked withdrawn around the turn of 2021 and 2022. A new committee draft circulated in 2025 and drew just under 1,500 comments. As of July 2026, the Johner Institute reported that the working group planned a second committee draft and did not expect a final draft before 2028, with publication possibly slipping to 2029. The draft widens the scope from medical device software to health software in general and adds security risk management as a separate requirement. Until a new edition is published and recognized, IEC 62304:2006 with Amendment 1:2015 is what you build to.
How to start an IEC 62304 process on a new product
- Write down the intended use first. Both the 62304 safety class and the FDA documentation level depend on it.
- Run the ISO 14971 hazard analysis before you classify, and record which external risk controls you rely on.
- Write a software development plan that names your processes, tools, configuration management and maintenance approach. Those are the subclauses FDA asks you to declare conformity to.
- Set up traceability from day one: requirement to architecture item to test to result, in the same tools the team already uses.
- Start the SOUP list with the first dependency you add, and record version, supplier and where anomalies are published.
- Keep a running list of unresolved anomalies with an impact evaluation. FDA asks for it at submission time, and it is much easier to keep than to reconstruct.
We build medical device software under an IEC 62304 process and produce the software documentation an FDA submission needs: plans, requirements, architecture, traceability, test records, SOUP lists and anomaly evaluations. Onix Systems has built software since 2000 and has 370+ engineers.
If you are planning a SaMD product, or inheriting a codebase that now needs a 62304 trail, talk to one of our engineers. Our 5-day free technical audit ends with a written report on where your process and documentation stand.
Sources
- IEC 62304:2006+AMD1:2015 CSV, Medical device software: Software life cycle processes (IEC webstore)
- FDA: Content of Premarket Submissions for Device Software Functions (June 2023)
- Johner Institute: Safety class according to IEC 62304
- Johner Institute: Off-the-shelf software (OTS) versus SOUP
- Johner Institute: IEC 62304 2nd edition, areas of application and changes
- FDA: Cybersecurity in Medical Devices: Quality Management System Considerations and Content of Premarket Submissions (February 2026)
- Wikipedia: IEC 62304 (structure, SOUP and safety classes overview)