The EN 62304:2006 standard defines the life cycle requirements for medical device software. It applies whenever the software is itself a medical device, is an element, part or accessory of one, or is involved in the production of a medical device.
EN 62304:2006 covers neither the validation nor the final release of the medical device. On its own, it is therefore not enough to demonstrate compliance with the essential requirements of directives 90/385/EEC and 93/42/EEC, which require the software to be validated according to the state of the art.
The manufacturer assigns a class to the software according to the potential hazard of injury.
| Class | Potential hazard |
|---|---|
| Class A | No injury or damage to health is possible |
| Class B | Non-serious injury is possible |
| Class C | Death or serious injury is possible |
The development effort depends directly on this class: it is much higher — and more costly — in class C than in class A or B.
EN 62304 gives no specific guidance on verification techniques and methods. Yet the importance of static analysis and test coverage keeps growing.
Using professional tools — requirements management, code analysis, software testing — is highly recommended: it reduces costs while increasing the quality and productivity of development.
For Testwell CTC++ 10.x, we provide a certificate from TÜV SÜD Rail GmbH, covering all SIL and ASIL levels of the standards concerned — including IEC 62304 for all software safety classes.
As an alternative — and for DO-178C —, a qualification kit (currently available for versions 9.x and earlier) provides the documentation, test cases and procedures to qualify the coverage analyzer for projects based on DO-178C, EN 50128, IEC 61508, IEC 60880 and ISO 26262.
IEC 62304 does not prescribe a coverage rate, but code that the tests do not reach must be explainable: defensive code, handling of hardware faults. The animation shows how Testwell CTC++ records these justifications and shows them in the report.
The 13 Testwell CTC++ animations →For classes B and C, IEC 62304 requires you to set software unit acceptance criteria before integration (5.5.3) — for example compliance with programming procedures or coding standards — and then to verify that each unit meets them. The standard leaves the choice of means open: static analysis has become the established way to do it.
TiCS turns this criterion into a continuous measurement: checking of your coding rules by your analyzers (MISRA C/C++ or in-house rules), compiler warnings, complexity — in a single dashboard, from the unit up to the product.
TIOBE's software composition analysis also helps to inventory third-party components and their known vulnerabilities — useful for keeping the SOUP list required by the standard up to date.
TiCS does not replace unit verification: it makes it measurable and traceable. Validating the tool for its intended use is a matter for your quality system.
IEC 62304 classifies software according to the risk it poses to the patient. The animation shows how to spot the riskiest modules, open their code in three clicks and know which fixes to make first.
The 14 TiCS animations →
References, testimonials and uses of Testwell CTC++ in medical devices.
DO-178C, EN 50716, IEC 60880, IEC 61508, ISO 26262, ISO 25119: each standard sets its own requirements.