Standards, Guidance & Notices
Showing 71–80 of 81
IMDRF
IMDRF/CYBER WG/N60 FINAL:2020
Principles and Practices for Medical Device Cybersecurity
This core document establishes international principles and practices for medical device cybersecurity, covering the complete device lifecycle. It specifies requirements for security by design, vulnerability management, and incident response frameworks. Manufacturers should integrate cybersecurity considerations throughout product development, maintenance, and end-of-life phases. The document serves as the common foundation referenced in Japan's Basic Principles for Conformity Assessment of Medical Devices (Article 12, Paragraph 3), FDA 2023 final cybersecurity guidance, and EU MDCG cybersecurity guidance. Japanese regulatory authorities directly reference this document in official notifications, making it essential for regulatory compliance in multiple jurisdictions.
Published: 2020-04-20
EU
MDCG
MDCG
MDCG 2020-1
Guidance on clinical evaluation (MDR) / Performance evaluation (IVDR) of medical device software
MDCG 2020-1 — Guidance on clinical evaluation (MDR) / Performance evaluation (IVDR) of medical device software — (March 2020)
Published: 2020-03-01
EU
MDCG
MDCG
MDCG 2018-5
UDI assignment to medical device software
MDCG 2018-5 — UDI assignment to medical device software — (October 2018)
Published: 2018-10-01
IMDRF
IMDRF/SaMD WG/N41 FINAL:2017
Software as a Medical Device (SaMD): Clinical Evaluation
This document specifies the clinical evaluation framework for SaMD, defining a three-layer structure for evidence of effectiveness: analytical validation, technical verification, and clinical validation. Manufacturers should determine the depth of clinical evidence required based on the SaMD risk category established in the N12 framework. The document provides guidance on what constitutes appropriate clinical evidence for each risk level and serves as the baseline for clinical evaluation requirements in regulatory submissions. This framework is referenced in FDA, PMDA, and EU MDCG approval processes, establishing harmonized expectations for clinical documentation and evidence standards in SaMD regulatory submissions globally.
Published: 2017-09-21
FDA
CDRH
CDRH
FDA-Interoperability-2017
Design Considerations and Pre-market Submission Recommendations for Interoperable Medical Devices
This FDA final guidance addresses design and regulatory considerations for medical devices that communicate electronically with other devices, health information systems, or electronic health records (EHR). The document emphasizes that interoperable devices must maintain safety and effectiveness across diverse clinical environments and integration scenarios. Manufacturers should incorporate risk management per ISO 14971 to identify and mitigate hazards associated with data exchange, system interoperability, and information integrity. Key design considerations include error detection and correction mechanisms, data validation and reconciliation procedures, interface standardization (HL7, DICOM, or equivalent standards), and cybersecurity protections ensuring confidential and accurate information exchange. Premarket submissions for interoperable devices must include technical documentation describing data exchange protocols, interface specifications, validation testing demonstrating accurate data transmission and receipt, and labeling clearly defining compatible systems and valid use cases. The guidance establishes that interoperability requirements should be addressed through systematic design controls incorporating software development processes per IEC 62304 where applicable. Manufacturers should validate interoperability across representative healthcare information technology environments. The guidance recognizes that interoperable devices create complex system-level risks requiring comprehensive validation approaches extending beyond individual device testing.
Published: 2017-09-06
IMDRF
IMDRF/SaMD WG/N23 FINAL:2015
Software as a Medical Device (SaMD): Application of Quality Management System
Describes how quality management system principles apply to Software as a Medical Device. Addresses requirements definition, the software development process, verification and validation, change management and risk management, setting out the quality assurance structure and process requirements needed to develop and deliver SaMD.
Published: 2015-10-02
IMDRF
IMDRF/MC/N35 FINAL:2015
Statement regarding Use of IEC 62304:2006 "Medical device software - Software life cycle processes"
An official statement by IMDRF regulators on the use of IEC 62304:2006. Sets out a common international position on the scope, interpretation and anticipated revision of the standard for medical device software development, in order to promote consistency among regulatory authorities.
Published: 2015-10-02
IMDRF
IMDRF/SaMD WG/N12 FINAL:2014
Software as a Medical Device: Possible Framework for Risk Categorization and Corresponding Considerations
This core document defines the risk classification framework for SaMD using a two-axis matrix approach. The framework combines clinical context (serious condition, significant condition, or minor condition) with the significance of information provided by the SaMD (treatment, diagnosis, or notification), resulting in four risk categories. This classification scheme provides the basis for regulatory decision-making regarding appropriate oversight levels. The framework is referenced internationally in Japan's Program Medical Device classification system, FDA Digital Health Policy, and EU MDR risk assessment requirements, establishing a harmonized foundation for SaMD regulatory evaluation across multiple jurisdictions.
Published: 2014-09-18
IMDRF
IMDRF/SaMD WG/N10 FINAL:2013
Software as a Medical Device (SaMD): Key Definitions
This foundational document establishes international definitions and terminology for Software as a Medical Device (SaMD), distinguishing it from hardware-based medical devices. SaMD is defined as software intended for use in achieving a medical purpose without being part of a hardware medical device. This definition serves as the baseline reference for all subsequent IMDRF SaMD guidance documents and national regulatory frameworks. The FDA, PMDA, and EU MDR all reference this definition in their respective SaMD regulatory frameworks, making it essential to understanding harmonized international SaMD regulation and classification schemes adopted globally.
Published: 2013-12-18
FDA
CDRH
CDRH
FDA-Cybersecurity-OTS-2005
Cybersecurity for Networked Medical Devices Containing Off-the-Shelf (OTS) Software
This FDA guidance document (2005) addresses cybersecurity management for network-connected medical devices incorporating off-the-shelf (OTS) software components. The guidance delineates responsibility allocation between manufacturers and healthcare facility information technology personnel, acknowledging shared accountability for device cybersecurity posture. Key technical topics include operating system patch management, antivirus software deployment, network access controls, and authentication mechanisms. The document establishes that manufacturers bear primary responsibility for device design incorporating security controls, while healthcare facilities assume responsibility for network infrastructure, patch management, and periodic security assessments appropriate to their operational environments. While superseded by more contemporary 2023 guidance addressing current cybersecurity threats and FDA regulatory expectations, this 2005 document provides valuable historical context for understanding the evolution of FDA cybersecurity requirements. Manufacturers and healthcare organizations benefit from understanding these foundational cybersecurity management principles, which remain relevant despite advances in threat landscape and technology. The document emphasizes that cybersecurity is a shared responsibility requiring collaboration between device manufacturers and end-users.
Published: 2005-01-14
