IDS 2027 16–20 March · CologneHall 11.3 · Aisle A · Booth 085Hall 11.3 · Booth A085 Book a meeting at our boothBook a meeting

IEC 62304 Software Safety Classes A, B and C: Requirements per Class

If you develop software for a medical device, you have to assign it to one of the three IEC 62304 software safety classes. Class A, B or C determines which development activities the standard requires and how much of them you have to document. Classify too high and you spend time and budget you did not need to. Classify too low and the notified body will find it, which means rework on architecture, testing and documentation.

This article explains how classification works, what each safety class requires and where projects typically lose time.

IEC 62304 in brief

IEC 62304 is the international standard for the software life cycle of medical devices. It defines which processes must be in place for development, maintenance, risk management, configuration management and problem resolution. In the EU and the US it is the recognized state of the art for medical device software. The current version is IEC 62304:2006 with Amendment 1 from 2015.

The three IEC 62304 software safety classes

Since Amendment 1, the class depends on the harm that is still possible after risk control measures external to the software have been taken into account:

  • Class A: The software system cannot contribute to a hazardous situation, or the remaining risk is acceptable thanks to risk control measures external to the software.
  • Class B: The software system can contribute to a hazardous situation with unacceptable risk, but the possible harm is non-serious injury.
  • Class C: The software system can contribute to a hazardous situation with unacceptable risk that can result in death or serious injury.
Decision path to software safety class A, B or C under IEC 62304
Simplified decision path to the software safety class under IEC 62304:2006 + A1:2015.

How classification into the safety classes works

  1. Identify hazards: Risk management according to ISO 14971 records which hazardous situations the software can contribute to.
  2. Check external measures: Risk control measures only count if they sit outside the software system, for example a hardware interlock or an independent monitoring system.
  3. Assess severity: If an unacceptable risk remains, the severity of the possible harm decides between Class B and Class C.
  4. Document the rationale: The classification and its justification belong in the risk management file, not only in the development plan.

Two rules are often overlooked. Until a software system is classified, it is treated as Class C. And software items inherit the class of the system unless the architecture separates them in a way that demonstrably prevents a lower-class item from being affected by another.

IEC 62304 requirements per safety class

The standard states for every subclause which classes it applies to. The table summarizes the development activities in clause 5.

ActivityClass AClass BClass C
5.1 Software development planningcore development planplus integration planning (5.1.5) and configuration control (5.1.10 to 5.1.12)plus standards, methods and tools (5.1.4)
5.2 Software requirements analysisyesyes, including risk control measures in the requirements (5.2.3)as B
5.3 Software architectural designnot requiredyes, including SOUP requirements (5.3.3, 5.3.4)plus segregation of software items (5.3.5)
5.4 Software detailed designnot requiredonly subdivision into software units (5.4.1)complete (5.4.1 to 5.4.4)
5.5 Software unitsimplementation only (5.5.1)plus verification process, acceptance criteria and verification (5.5.2, 5.5.3, 5.5.5)plus additional acceptance criteria (5.5.4)
5.6 Integration and integration testingnot requiredyesyes
5.7 Software system testingyesyesyes
5.8 Software releasecore scopeplus evaluation of known residual anomalies and documentation of the build processas B
IEC 62304:2006 + A1:2015. Simplified summary; the class markers in the standard text prevail.

For Class A this means: software units are implemented, but the standard only requires unit-level verification from Class B upwards. In Class A, assurance comes from system testing, which Amendment 1 made mandatory for all classes.

Clauses 6 to 9 on maintenance, risk management, configuration management and problem resolution generally apply to all classes, with some subclauses only for B and C. Third-party software (SOUP) must be identified in every class. From Class B, requirements for SOUP and the evaluation of published anomaly lists are added.

Where the step from Class B to Class C hits your project

The biggest step is between Class B and Class C. Class C requires a detailed design of every software unit and its interfaces, plus additional acceptance criteria for unit verification. That applies to every change over the whole product life.

An early architecture decision pays off: if the functions that can contribute to serious injury can be placed in a few, cleanly separated software items, the rest of the system can stay in Class B. The separation has to be justified and demonstrated in the architecture.

Software safety class and MDR risk class are two different things

The IEC 62304 safety class determines the development process. The MDR risk class (I, IIa, IIb, III) determines the conformity assessment route and, for standalone software, usually follows from Rule 11 in Annex VIII. The two are related but not identical. A Class IIa device under the MDR can, for example, contain software of safety class B.

To check whether your software is a medical device in the first place and which MDR class applies, read MDCG 2019-11: when is software a medical device?

Common classification mistakes

  • The class is fixed shortly before submission, and architecture and tests have to be documented after the fact.
  • The classification appears in the development plan but without a rationale in the risk management file.
  • Risk control measures inside the same software system are used to lower the class.
  • Segregation of software items is claimed but not demonstrated in the architecture.
  • SOUP components such as libraries, frameworks or operating systems are missing from the documentation.

How SimQ supports you

SimQ develops regulatory-compliant MedTech software. The company has been ISO 13485 certified since 2018 and develops along IEC 62304 and the EU MDR, from the first classification through architecture and verification to release. With SimQ OSA, SimQ developed a product combining AI and in-silico technologies and brought it through CE marking as a medical device. Three SimQ software products were acquired by the KLS Martin Group in a 2025 asset deal.

Learn more about Software Development for MedTech. If you plan to work with an external partner, read our guide to outsourcing medical device software development. To discuss your project, book a first call.

Frequently asked questions

Which class applies to software that has not been classified yet?

Class C. Only a justified classification in risk management allows a lower class.

Can a hardware interlock lower the software safety class?

Yes, if it sits outside the software system and effectively reduces the risk to an acceptable level.

Does Class A software need unit tests?

IEC 62304 does not require unit-level verification for Class A. System testing, however, is required for all classes. Many teams test units anyway because it finds defects earlier.

Can parts of a system have different classes?

Yes, if the architecture demonstrably separates the items. Without that evidence, the highest class applies to all items.

Note: This article summarizes the standard in simplified form and does not replace regulatory advice. The text of IEC 62304 prevails.

Leave a Reply

Your email address will not be published. Required fields are marked *