Welcome to our new website! If this is the first time you are logging in on the new site, you will need to reset your password. Please contact us at firstname.lastname@example.org if you need assistance.
Your membership opens the door to free learning resources on demand. Check out the Member Knowledge Center for free webcasts, publications and online courses.
Hear from leaders around the globe as they share insights about their experiences and lessons learned throughout their certification journey.
Posted 08 April 2015 | By Michael Mezher
In recent years, general-purpose devices such as personal computers, smartphones and wearables have enabled the proliferation of “software as a medical device” (SaMD) products.
The International Medical Device Regulators Forum (IMDRF) is considering a new document that explores how quality management system (QMS) principles can apply to software as a medical device (SaMD) development.
IMDRF was formed in 2011 to “accelerate international medical device regulatory harmonization” after the dissolution of the Global Harmonization Task Force on Medical Devices (GHTF).
IMDRF has identified software as an increasingly critical area of healthcare product development, and has recognized two distinct types of medical purpose software:
The main distinction between the two is whether the software is used “to drive a hardware medical device.” The proposed document, Software as a Medical Device (SaMD): Application of Quality Management System, considers the latter of these two.
In order to promote a harmonized approach to the development and regulation of SaMD products, IMDRF has developed a series of documents concerning their definition and categorization. In 2013, IMDRF’s SaMD Working Group released its Software as a Medical Device (SaMD): Key Definitions, to create a standard terminology for SaMD. The following year, IMDRF adopted its Software as a Medical Device: Possible Framework for Risk Categorization and Corresponding Considerations, which proposes a method for categorizing SaMD based on the seriousness of the condition the SaMD is intended to diagnose or treat.
For traditional medical devices with a software component, manufacturers should follow QMS principles for medical devices as well as any good software engineering practices that may apply. While many QMS principles that apply to traditional medical devices, such as those found in ISO 13485:2003, translate to SaMD, companies developing SaMD products will also need to make some additional considerations.
Some of the factors SaMD developers should consider are:
Developers should also consider the risk posed by the platform or operating system (Windows, Mac OS, iOS, Android, etc.) a SaMD product is installed to. This includes designing SaMD products that take into account “unanticipated upgrades to the underlying platform.”
Software as a Medical Device (SaMD): Application of Quality Management System
Tags: Software as a Medical Device, SaMD, ISO 13845:2003, QMS
Regulatory Focus newsletters
All the biggest regulatory news and happenings.