Maps to
ISO 13485: §7.3
IEC 81001-5-1: §4.1.9
Requirement text
The manufacturer shall establish activities for identifying, characterizing, and tracking to closure security-related errors and omissions in accompanying documentation, including the security guidelines.
What changed
IEC 81001-5-1:2021 is the first standalone cybersecurity standard purpose-built for health software and medical device software. Published in December 2021, it was adapted from IEC 62443-4-1 (industrial control systems security) to address the unique safety and regulatory context of medical devices — adding 64 health-specific requirements that account for patient safety, clinical workflows, and the manufacturer-HDO relationship.
The standard mirrors IEC 62304's lifecycle structure but adds security-specific activities at every phase — planning, development, testing, release, and maintenance. It requires security risk management to be integrated with ISO 14971 safety risk management, not treated as a separate IT concern. FDA formally recognized it as Consensus Standard #13-112 in December 2022 and references it as providing a framework for the Secure Product Development Framework (SPDF) required by Section 524B.
EU MDR harmonization was originally targeted for May 2024 but postponed to May 2028. Despite this delay, Notified Bodies and Competent Authorities universally recognize it as "state of the art" for health software cybersecurity under MDR GSPR Annex I, Section 17.2. Missing or inadequate cybersecurity documentation is already a top cause of Notified Body major non-conformities for SaMD. A December 2025 Interpretation Sheet (ISH1:2025) clarified software item classification into maintained, supported, and required software categories, affecting risk transfer and post-market obligations.
Atomic constraints
- •An activity (or activities) for identifying security-related errors and omissions in accompanying documentation SHALL be established.
- •Security-related documentation errors and omissions SHALL be characterized (described and assessed).
- •Security-related documentation errors and omissions SHALL be tracked to closure.
- •Security guidelines documentation SHALL be included in the scope of this review activity.
Common gaps
Accompanying documentation lacks security guidance for operators
moderateProduct documentation (IFU, installation guides, admin manuals) does not include security-relevant information that operators need: hardening guidance, network configuration requirements, default credential changes, and security maintenance responsibilities.
Evidence signals
- •
FILE_EXISTS
(Documentation.*Review|IFU.*Review|Security.*Guide|Accompanying.*Doc|Release.*Notes.*Security)
- •
CONTENT_MATCH
Does this document describe a process for identifying, tracking, or correcting errors and omissions in security-related product documentation or user guides?
Audit defense
Our accompanying documentation review process (Doc ID: [your document ID]) identifies, characterizes, and tracks to closure all security-related errors and omissions in [your product] documentation, including security guidelines, per clause 4.1.9.