IEC 62304¶
IEC 62304 (Medical device software: software life cycle processes) is the standard a medical device manufacturer follows for the software in its device. It applies to the manufacturer's process, not to a library on its own. This page explains how a Kokeb component fits into that process, so that a manufacturer can use one in software of any safety class, including class C.
This page is general guidance, not regulatory advice. The manufacturer decides how a component is treated and remains responsible for the device.
Two ways a manufacturer can use a Kokeb component¶
- As SOUP (software of unknown provenance): the component is used as released. The manufacturer identifies it, states the requirements it relies on, evaluates its published anomalies, and verifies it within their system. The evidence package gives them everything that needs.
- As their own software item: the manufacturer brings the component under their own process, for example by forking it at a release. The rules, tests, coverage, traceability and deviation records then become starting evidence for their own verification.
How handbook mechanisms map onto the standard¶
| IEC 62304 clause | What it asks of the manufacturer | What a Kokeb component provides |
|---|---|---|
| 5.1 Development planning | Plans, standards, methods and tools | This handbook: the rules, the coding standards, the named tools and their versions |
| 5.2 Requirements analysis | Software requirements | docs/requirements.yml at the safety level |
| 5.3 Architectural design | Architecture, interfaces, SOUP requirements | Standards pages and decision records; the Contract page of each driver; the SBOM |
| 5.4 Detailed design | Design of each unit (class C) | Doxygen API reference generated from documented headers |
| 5.5 Unit implementation and verification | Unit verification process and acceptance criteria; additional criteria for class C | Static analysis, host tests, sanitizers, coverage and the coding-standard matrix, all in CI (KB-CPP-008, KB-TST-001) |
| 5.6 Integration and integration testing | Integration testing | Builds for every supported target; ESP-IDF and board examples |
| 5.8 Release | Known residual anomalies, archived, repeatable build | Immutable tags, provenance, the anomaly list, reproducible CI builds |
| 7.1 Risk analysis, SOUP | Evaluate SOUP and its published anomalies | The anomaly list in the evidence package |
| 8 Configuration management | Identify items and SOUP, control change | Releases and tags (KB-GIT-003), pull-request-only changes (KB-GIT-002), the SBOM |
| 9 Problem resolution | Record, investigate and resolve problems | GitHub issues and the security policy; fixes linked to releases in the changelog |
What stays with the manufacturer¶
Safety classification, risk management (ISO 14971), system requirements, hazard analysis, system testing, clinical evaluation and the device's technical documentation. A Kokeb component supplies evidence for its own part; it cannot supply the device's.