Standards, Guidance & Notices
Showing 41–50 of 71
MHLW
Notice
Notice
Admin-Notice-2023-12-22-IDATEN-KISAIJIREI
Examples of Application Forms and Supporting Documents for Change Control Plan Confirmation Applications for Software as a Medical Device
Practical worked examples of application forms and supporting documentation for IDATEN change control plan confirmation applications specific to SaMD. Illustrates how to describe proposed changes, set acceptance criteria, and prepare draft revised approval documents. Issued concurrently with the consolidated Q&A revision.
Published: 2023-12-22
MHLW
Notice
Notice
Admin-Notice-2023-12-22-IDATEN-QA
Q&A on Change Control Plan Confirmation Applications for Medical Devices, AI-Enabled Medical Devices, and Software as a Medical Device (Consolidated Revision)
Consolidated revision of Q&A guidance on the IDATEN change control plan confirmation system, integrating three previously separate documents. Adds provisions specific to AI/ML-enabled medical devices and SaMD, requiring submission of procedures for developing and implementing the change control plan and materials for appropriate AI technology management. Reflects startup company needs and accumulated regulatory experience since the system's 2020 launch.
Published: 2023-12-22
EU
MDCG
MDCG
MDCG 2023-4
Medical Device Software (MDSW) – Hardware combinations Guidance on MDSW intended to work in combination with hardware or hardware components
MDCG 2023-4 addresses MDSW that cannot achieve its intended medical purpose without hardware or a hardware component, setting out three regulatory scenarios (desktop PCs and cloud platforms are out of scope): (1) the hardware qualifies as an accessory to the MDSW under MDR Annex VIII classification rules; (2) the hardware is placed on the market as a standalone medical device -- as part of a system (Art. 22), a combination (Art. 2(1)), or an integral component -- in which case the manufacturer may rely on the hardware's MDR conformity for general safety and performance requirements, though clinical evaluation must still cover the combined intended purpose; (3) the hardware is part of a general consumer or wearable product with no medical device/accessory status, in which case the MDSW manufacturer bears sole responsibility for the safety, performance and reproducibility of the combination across all supported configurations, with correspondingly broader post-market surveillance. Illustrative examples include dermal sensor patches and smartwatches (temperature, SpO2, heart rate) paired with a companion app.
Published: 2023-10-01
FDA
CDRH
CDRH
FDA-OTS-Software-2023
Off-The-Shelf (OTS) Software Use in Medical Devices
FDA guidance setting out the recommended documentation in premarket submissions for off-the-shelf (OTS) software incorporated into medical devices, such as operating systems, database management systems, and libraries. A practical basis for managing SOUP (Software of Unknown Provenance). It presents requirements for evaluating and documenting vendor information, known anomalies, and the support life cycle. Referenced in relation to the SOUP management requirements of IEC 62304.
Published: 2023-09-28
MHLW
Notice
Notice
Admin-Notice-2023-07-20
Q&A on Application of Essential Principles Article 12(3) for Medical Devices
Q&A addressing application and conformance assessment of Essential Principles Article 12(3). Covers transition period marketing approval application handling, submission documentation methods, third-party agency utilization for JIS T 81001-5-1 conformance, and reliability document review scope. References related MHLW regulatory notices issued in March and May 2023.
Published: 2023-07-20
FDA
CDRH
CDRH
FDA-Device-Software-Functions-2023
Content of Premarket Submissions for Device Software Functions
FDA final guidance (2023) on the content of software documentation required in premarket submissions (510(k), PMA, De Novo) for SaMD and SiMD. It organizes documentation requirements by documentation level (Basic or Enhanced) and specifies what to include for software design specifications, architecture, verification and validation, and unresolved anomalies. It replaces the 2005 Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices.
Published: 2023-06-14
MHLW
Notice
Notice
Admin-Notice-2023-05-29
Publication of Guidance on Appropriate and Expedited Approval and Development of Software as Medical Devices (SaMD)
Practical guidance on expedited regulatory approval for SaMD including two-stage approval processes. Clarifies early marketing approval application handling across different development stages while maintaining consistent pre- and post-market safety/effectiveness assurance. Developed through public-private-academic collaboration as part of DASH for SaMD strategy, applicable to AI/ML-enabled SaMD.
Published: 2023-05-29
MHLW
Notice
Notice
MHLW-PSEHB-MDED-0523-No.1
Conformance Assessment Procedures for Essential Principles Article 12(3) of Medical Devices
Notice specifying concrete compliance assessment considerations for Essential Principles Article 12(3). Details additional verification items against JIS T 81001-5-1 provisions (general requirements, maintenance processes, configuration management). Requires demonstration of intended use environment through system/network architecture diagrams and integration of vulnerability notification activities into quality management systems.
Published: 2023-05-23
IMDRF
IMDRF/CYBER WG/N73 FINAL:2023
Principles and Practices for Software Bill of Materials for Medical Device Cybersecurity
Final document of the IMDRF Medical Device Cybersecurity Working Group on the Software Bill of Materials (SBOM), complementing the medical device cybersecurity principles set out in IMDRF N60. It provides recommendations for medical device manufacturers on creating, maintaining, and distributing SBOMs, and for healthcare providers on receiving and managing them. It also describes how both manufacturers and healthcare providers can use SBOMs in risk management, vulnerability management, and incident response across the total product life cycle.
Published: 2023-04-13
IMDRF
IMDRF/CYBER WG/N70 FINAL:2023
Principles and Practices for the Cybersecurity of Legacy Medical Devices
Final document of the IMDRF Medical Device Cybersecurity Working Group on the cybersecurity of legacy medical devices, complementing IMDRF N60. It divides the total product life cycle for cybersecurity into four stages (Development, Support, Limited Support, and End of Support (EOS)) and sets out the responsibilities and expectations of medical device manufacturers and healthcare providers at each stage in three areas: communication, risk management, and transfer of responsibility. Responsibility shifts from the manufacturer to the healthcare provider as the life cycle progresses, and cybersecurity responsibility for devices used beyond the EOS communicated by the manufacturer rests entirely with the healthcare provider. The document also notes that the end of life or end of support of a software or firmware component can prematurely move the device itself into a later stage, which manufacturers should address in advance.
Published: 2023-04-11
