IEC 81001-5-1:2021, "Health software and health IT systems safety, effectiveness and security — Part 5-1: Security — Activities in the product life cycle," is the standard that tells a health software manufacturer what security work has to happen at each stage of development and maintenance — planning, design, implementation, testing, release, and the vulnerability handling that follows. Published in December 2021 as a joint IEC/ISO double-logo standard, it layers security activities onto the same life cycle structure IEC 62304 already uses for safety, and is explicitly written to help a manufacturer support conformance with IEC 62443-4-1, the industrial secure-development-lifecycle standard, adapted for health software's specific needs.
Key takeaways
- software-only products for other health use.
- For health software generally — implement the requirements in Clauses 4 through 9 in full.
- Footnote 44 (security design inputs): IEC 81001-5-1 is listed among the medical-device-specific frameworks.
- Not as of 12 November 2026.
Who wrote it, and for what?
Per its own Foreword, IEC 81001-5-1 "has been prepared by a Joint Working Group of IEC subcommittee 62A: Common aspects of electrical equipment used in medical practice, of IEC technical committee 62: Electrical equipment in medical practice, and ISO technical committee 215: Health informatics. It is published as a double logo standard." Its Clause 1 (Scope) states its purpose directly: "to increase the cybersecurity of health software by establishing certain activities and tasks in the health software life cycle processes and also by increasing the security of software life cycle processes themselves," while maintaining "an appropriate balance of the key properties safety, effectiveness and security as discussed in ISO 81001-1." Notably, Clause 2 (Normative references) is empty — "there are no normative references in this document" — meaning the standard is self-contained even though its own terms clause sources definitions from ISO/IEC 27000, IEC 62443-4-1, IEC 62304, ISO 81001-1 and several other documents. The quotations on this page come from the IEC's free preview of the standard, which carries the foreword, introduction, scope, the first definitions and the full table of contents.
What counts as "health software" here?
Per Clause 0.2 (Field of application), the standard applies to:
- software as part of a medical device;
- software as part of hardware specifically intended for health use;
- software as a medical device (SaMD); and
- software-only products for other health use.
A medical device's own software is therefore only one subset of what this standard calls "health software" — the scope is deliberately wider than "medical device software" alone, and its Introduction notes the standard's field of application also looks ahead to future ISO/IEC 81001-5 parts covering the implementation, operations and use phases at healthcare delivery organizations. A note to 0.2 matters for firmware teams: the software considered for security "is larger and includes more software (drivers, platforms, operating systems) than for SAFETY," because security looks at "any use including foreseeable unauthorized access rather than just the INTENDED USE." An embedded Linux kernel or an RTOS that an IEC 62304 file treats as off-the-shelf software is inside the security work.
What do the six process clauses require?
| Clause | Process | Sub-clauses named in the contents (selection) |
|---|---|---|
| 4 | General requirements | 4.1 quality management, including security expertise (4.1.4), software items from third-party suppliers (4.1.5), disclosing security-related issues (4.1.7), periodic review of security defect management (4.1.8); 4.2 security risk management; 4.3 software item classification relating to risk transfer |
| 5 | Software development process | Development environment security (5.1.2), secure coding standards (5.1.3), security risks for required software (5.2.3), defense-in-depth architecture (5.3.1), secure health software interfaces (5.4.3), security requirements, threat mitigation, vulnerability and penetration testing (5.7.1–5.7.4), managing conflicts of interest between testers and developers (5.7.5), release: resolve findings, file integrity, controls for private keys, secure decommissioning guidelines (5.8) |
| 6 | Software maintenance process | Timely delivery of security updates (6.1.1), monitoring public incident reports (6.2.1), security update verification (6.2.2), update documentation, delivery and integrity for supported and maintained software (6.3) |
| 7 | Security risk management process | Product security context (7.1.2); identification of vulnerabilities, threats and adverse impacts (7.2); estimation and evaluation (7.3); controlling security risks (7.4); monitoring the effectiveness of risk controls (7.5) |
| 8 | Software configuration management process | One clause with no sub-clauses in the contents |
| 9 | Software problem resolution process | Receiving notifications about vulnerabilities (9.2), reviewing (9.3), analysing (9.4) and addressing security-related issues (9.5) |
Per the Introduction, Clauses 5 through 8 "are arranged in the ordering of IEC 62304" specifically so that a manufacturer already running an IEC 62304-conformant life cycle can extend it with these clauses rather than build a second, parallel process. The same Introduction says the process requirements in Clauses 4 to 9 "have been derived from the IEC 62443-4-1 PRODUCT LIFE CYCLE management." Annex A adds Table A.1, "Required level of independence of testers from developers," which backs 5.7.5.
How does it support IEC 62443-4-1 without replacing it?
Clause 0.3 (Conformance) is explicit about the relationship: "This document is designed to assist in the implementation of the processes required by IEC 62443-4-1, however, conformance to this document is not necessarily a sufficient condition for conformance to IEC 62443-4-1." Annex D ("Relation to practices in IEC 62443-4-1:2018") gives an informative mapping in both directions (D.1 from 81001-5-1 to 62443-4-1, D.2 the reverse), and Annex E ("Documents specified in IEC 62443-4-1") lists the release documents 62443-4-1 expects: product documentation, defense-in-depth documentation, measures expected in the environment, security hardening guidelines, security update information and decommissioning documents. The clause-by-clause correspondence inside Annex D is in the paid text. See IEC 62443-4-1: the secure product development lifecycle, explained for that standard's own eight practices.
How do the two conformance routes work?
Per Clause 0.3, a manufacturer can claim conformance in one of two ways:
For health software generally— implement the requirements in Clauses 4 through 9 in full. For Transitional Health Software— implement only the processes, activities and tasks identified in the normative Annex F.
Annex F exists because software already on the market cannot realistically be run back through a from-scratch secure development life cycle; it defines a narrower, documented gap-closure path (development assessment and gap-closure activities, rationale for use, and post-release activities) instead. Annex A also introduces a related concept, risk transfer, distinguishing between maintained, supported and required software — software items an organization still actively develops versus software it only supports or merely requires, each carrying a different practical security obligation. Annex G assigns object identifiers to the document's conformance concepts.
Which threat modelling techniques does it point to?
Annex C (informative, "Threat modelling") lists specific techniques a manufacturer can draw on, without mandating any single one: attack-defense trees, CAPEC/OWASP/SANS-based approaches, CWSS, DREAD, listing known potential vulnerabilities, OCTAVE, STRIDE, Trike, and VAST. This is guidance, not a requirement to use a named methodology — Clause 5's security requirements and threat-mitigation testing activities are the actual normative obligation. For a practical method, see OWASP threat modeling.
What does FDA say about IEC 81001-5-1?
FDA added IEC 81001-5-1 to its Recognized Consensus Standards database on 19 December 2022, under recognition number 13-122, category Software/Informatics, with extent of recognition listed as "Complete standard." The FDA recognition record adds that conformance "may not satisfy all the cybersecurity requirements outlined in Section 524B of FD&C Act."
FDA's premarket cybersecurity guidance, issued on 3 February 2026 under docket FDA-2021-D-1158, names the standard in three places in the guidance PDF:
- Section V (Secure Product Development Framework): "Possible frameworks to consider include, but are not limited to, the medical device-specific framework that can be found in the Medical Device and Health IT Joint Security Plan (JSP2) and IEC 81001-5-1."
- Footnote 44 (security design inputs): IEC 81001-5-1 is listed among the medical-device-specific frameworks.
- Footnote 48 (testing): standards that "may partially meet the security testing recommendations" are ANSI/UL 2900, ANSI/ISA 62443-4-1 and IEC 81001-5-1.
The February 2026 text supersedes the June 2025 final guidance, which replaced the September 2023 edition; FDA's own guidance-history table also lists a March 2024 draft. See FDA premarket cybersecurity for medical devices for the Section 524B duties that framework sits alongside.
The IEC catalogue lists an Interpretation Sheet 1 (IEC 81001-5-1:2021/ISH1:2025), published 4 December 2025: three pages, sold at no charge. The base standard's catalogue page now sells a corrected version dated 2025-12 that includes the sheet, so a team buying the standard today receives both together.
Is IEC 81001-5-1 harmonised under the EU MDR?
Not as of 12 November 2026. The Commission's standardisation request M/575 (consolidated text with amendments 1 and 2) lists IEC 81001-5-1 as item 50 in Annex I, Table 2, the new harmonised standards CEN and CENELEC are asked to draft in support of the MDR, with a deadline for adoption of 27 May 2028. The IVDR annex of the same request does not list it. None of the MDR and IVDR implementing decisions linked from the Commission's harmonised standards page, up to (EU) 2026/2479 and 2026/2481, references it.
Until a reference is published, the standard is state-of-the-art evidence rather than a presumption of conformity. Regulation (EU) 2017/745 Annex I 17.2 requires software to be "developed and manufactured in accordance with the state of the art taking into account the principles of development life cycle, risk management, including information security, verification and validation"; the IVDR repeats this at Annex I 16.2. An IEC 81001-5-1 process is one of the most direct ways to show that, as the MDR Annex I guide explains.
Which evidence does each clause produce for FDA and MDR files?
The mapping below is SoftWSP's reading of the texts quoted above; neither IEC, FDA nor the Commission publishes it.
| IEC 81001-5-1 activity | Evidence it produces | FDA guidance (Feb 2026) | MDR Annex I |
|---|---|---|---|
| 4.1.5, 5.2.3 third-party and required software | Component list, supplier assessment | V.A.4 Third-Party Software Components; SBOM under 524B(b)(3) | 17.2 |
| 7.1–7.5 security risk management | Threat model, risk assessment, control effectiveness | V.A Security Risk Management | 17.2 (risk management, including information security) |
| 5.3–5.4 architecture and design | Defense-in-depth design, interface specifications | V.B Security Architecture | 17.2 |
| 5.7.1–5.7.5 testing | Test reports, tester independence record | V.C Cybersecurity Testing | 17.2 (verification and validation) |
| 5.8 release, Annex E documents | Hardening guide, update information, decommissioning guidance | VI.A Labeling | 17.4 and 23.4(ab) |
| 6.1.1, 6.2.1, 9.2–9.5 maintenance and problem resolution | Monitoring records, vulnerability handling cases, update releases | VI.B Cybersecurity Management Plans; 524B(b)(1) | Post-market surveillance (Article 83) |
Worked example: how would a team close the gaps for a hypothetical connected inhaler app?
Hypothetical product, for illustration only. A maker sells a Bluetooth inhaler sensor with a companion app (SaMD). Version 2 of the app has been on the market for two years; version 3 is starting development under the company's IEC 62304 process.
Split the productsVersion 3 goes through Clauses 4 to 9 in full. Version 2 is declared Transitional Health Software and follows Annex F. Run the Annex F assessment on version 2Compare the existing design records with Clauses 5 and 7; record which activities can still be done after release (threat model, vulnerability testing, SBOM) and which cannot (secure coding standard applied during implementation), with the rationale F.3 asks for. Classify the components (4.3)The sensor firmware is maintained software; the mobile OS is required software the company neither develops nor supports, which drives the 5.2.3 risk analysis. Close the testing gapCommission vulnerability and penetration testing (5.7.3, 5.7.4) from testers outside the app team, and record their independence against Table A.1. Build the maintenance loopGenerate an SBOM for the firmware and the app, monitor public reports for its components (6.2.1), and route findings into the Clause 9 process. A KEV and EPSS check helps rank what to fix first under 6.1.1. Write the release documentsHardening guidance and update information (Annex E) feed the FDA labeling and the MDR instructions for use. State the claim preciselyVersion 3 claims conformance through Clauses 4 to 9; version 2 through Annex F, citing the matching Annex G object identifier where a machine-readable claim is needed.
What are the common pitfalls?
- A parallel security life cycle. Clauses 5 to 8 follow IEC 62304's order so they can extend the existing process; a separate document set drifts.
- Leaving out platform software. The 0.2 note pulls drivers, platforms and operating systems into scope.
- Annex F as a permanent home. Transitional status suits software already released, not new development.
- Citing it as a harmonised standard in an EU file. It is listed in M/575 with a 2028 deadline, but no reference is published.
- Developers testing their own code. 5.7.5 and Table A.1 set independence levels; FDA's testing section also asks about tester independence.
- Buying the 2021 text without the interpretation sheet. The corrected 2025-12 version includes ISH1.
Where should a manufacturer start?
Map your existing IEC 62304 life cycle first— Clauses 5-8 follow 62304's own ordering deliberately, so an existing safety life cycle is the scaffold to extend, not something to replace. Decide early whether a product is "health software" or "Transitional Health Software"— new development goes through Clauses 4-9 in full; software already released may only need the Annex F gap-closure path, and conflating the two creates unnecessary rework. Treat Annexes D and E as your IEC 62443-4-1 bridge, if a connected health device also needs to speak to industrial or hospital-network security buyers who ask for 62443-4-1 evidence. Use Annex C's technique list as options, not a checklist— pick the threat-modelling method that fits your team's existing practice rather than trying to run all of them. Confirm your FDA submission language against the current guidance page, not a cached PDF — the premarket guidance that references this standard has already been reissued three times since 2023.
SoftWSP supports two of these activities for device firmware: the platform extracts an SBOM from the firmware image as CycloneDX 1.6 JSON and matches the components against NVD, CISA KEV, FIRST EPSS and CISA ICS advisories (CSAF), with an AI-drafted, cited report that an engineer reviews; watchlist alerts on a CVE ID or a vendor and product support the 6.2.1 monitoring. It does not write VEX statements, analyse reachability or re-match each new release's SBOM automatically, and it does not perform penetration testing. See firmware SBOM, device & firmware security and PSIRT as a service.
This guide summarises IEC's own published preview text of IEC 81001-5-1:2021, its catalogue record, and FDA and European Commission documents; 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 81001-5-1?
IEC 81001-5-1:2021, "Health software and health IT systems safety, effectiveness and security — Part 5-1: Security — Activities in the product life cycle," is a joint IEC/ISO double-logo International Standard published in December 2021 (Edition 1.0, 114 pages). It was prepared by a Joint Working Group of IEC Subcommittee 62A (common aspects of electrical equipment used in medical practice) and ISO Technical Committee 215 (health informatics). Per its own Clause 1 scope, it "defines the life cycle requirements for development and maintenance of health software needed to support conformance to IEC 62443-4-1 — taking the specific needs for health software into account."
How does IEC 81001-5-1 relate to IEC 62304 and IEC 62443-4-1?
Its own Introduction says it does not prescribe a specific system of processes, "similar to IEC 62304," and that Clauses 5 through 8 are "arranged in the ordering of IEC 62304" — it layers security activities onto the same software life cycle structure IEC 62304 already uses for safety. Separately, its Conformance clause (0.3) states the document "is designed to assist in the implementation of the processes required by IEC 62443-4-1, however, conformance to this document is not necessarily a sufficient condition for conformance to IEC 62443-4-1" — the two are related but not interchangeable.
Does IEC 81001-5-1 apply to all health software, or just medical device software?
Per its Field of application (0.2), it applies to health software as part of a medical device, as part of hardware specifically intended for health use, as software as a medical device (SaMD), and as a software-only product for other health use — a broader category than "medical device software" alone. A medical device's software is one subset of the health software this standard covers.
Is IEC 81001-5-1 recognized by FDA?
Yes. FDA's own Recognized Consensus Standards database lists IEC 81001-5-1 Edition 1.0 2021-12 under recognition number 13-122, category Software/Informatics, recognized 12/19/2022, with extent of recognition "Complete." Secondary analysis describes FDA's premarket cybersecurity guidance as naming IEC 81001-5-1 among example Secure Product Development Frameworks; always check FDA's live guidance page for the current title and date before citing it, since that guidance has already been reissued more than once.
What is "Transitional Health Software" and why does Annex F exist?
Per Clause 0.3 (Conformance), a manufacturer can claim conformance to IEC 81001-5-1 in one of two ways: by implementing the full requirements in Clauses 4 through 9, or, for existing health software that cannot realistically be run back through a full secure life cycle, by implementing only the processes, activities and tasks identified in the normative Annex F for "Transitional Health Software." Annex F is the standard's own acknowledgement that software already on the market needs a narrower, documented path to conformance.
Sources
- IEC: IEC 81001-5-1:2021 — Health software and health IT systems safety, effectiveness and security — Part 5-1: Security — Activities in the product life cycle (catalogue record, Edition 1.0, 114 pages, prepared with ISO/TC 215)
- IEC 81001-5-1:2021 — Document Preview (foreword, introduction, scope, full table of contents including Annexes A-G; iTeh Standards sample PDF)
- IEC: IEC 81001-5-1:2021/ISH1:2025 — Interpretation Sheet 1 (catalogue record, published 2025-12-04)
- FDA: Recognized Consensus Standards database — search result for "81001-5-1" (recognition number 13-122, recognized 12/19/2022, category Software/Informatics)
- FDA: Cybersecurity in Medical Devices — Quality Management System Considerations and Content of Premarket Submissions (guidance document page, current edition February 2026, docket FDA-2021-D-1158)
- Johner Institute: "IEC 81001-5-1: The standard for secure health software" (independent secondary analysis)
- FDA: Recognized Consensus Standard record — IEC 81001-5-1 Edition 1.0 2021-12 (recognition number 13-122, extent: complete standard)
- FDA: Cybersecurity in Medical Devices guidance PDF (3 February 2026), Section V, footnotes 44 and 48, guidance history
- European Commission: consolidated standardisation request M/575 (C(2021)2406 with amendments 1 and 2), Annex I Table 2 item 50
- European Commission: Harmonised standards for medical devices (list of MDR and IVDR implementing decisions)
- Regulation (EU) 2017/745 (MDR), Annex I sections 17.2, 17.4, 23.4(ab) and Article 83, EUR-Lex
About this guide
SoftWSP Regulation Desk
Covers the Medical & regulated devices cluster: 30 guides.

In this cluster
Questions about this page?
