What is SaMD (Software as a Medical Device)?

Software as a Medical Device (SaMD) is software intended for one or more medical purposes that performs those purposes without being part of a hardware medical device. FDA uses this definition from the International Medical Device Regulators Forum (IMDRF).

The test is intended use. If software is meant to diagnose, treat, mitigate, or prevent disease, or otherwise meets the device definition in section 201(h) of the FD&C Act, and it runs on its own rather than inside a piece of medical hardware, it is SaMD. FDA chaired the IMDRF working group, formed in 2013, that produced the shared definitions, a risk categorization framework, a quality management approach, and principles for clinical evaluation of SaMD.

What is and is not SaMD

FDA's examples of SaMD include software that lets a smartphone view images from an MRI device, computer-aided detection software that post-processes images to help detect breast cancer, radiation treatment planning software that supplies information used in a linear accelerator, and software that uses a consumer device's accelerometer to help diagnose a condition.

FDA's examples of software that is not SaMD include software that drives the motors of an infusion pump, closed-loop control in a pacemaker, software that encrypts data for transmission from a device, software that enables clinical communication and workflow such as scheduling, registration, and voice or video calling, and a database with search functions and no medical purpose. Software embedded in a device is still regulated, as part of that device, but it is not SaMD.

Why it matters

Once a function is SaMD, it needs a regulatory pathway such as a 510(k), De Novo, or PMA, and the submission needs software documentation. FDA's 2023 guidance on device software functions scales that documentation by risk. Enhanced Documentation applies when a failure or flaw in the software could present a hazardous situation with a probable risk of death or serious injury, assessed before risk controls. Basic Documentation applies otherwise. Either way, FDA expects a risk management file, a software requirements specification, architecture documentation, and evidence of testing. Design records should be kept in step with development, because records written after the fact can raise concerns about control of the design process.

Example

A company sells a scheduling and messaging app for cardiology clinics, which is workflow software. It then plans a feature that analyzes a wearable's signal to flag possible arrhythmia for clinician review. That feature has a medical purpose and runs on general-purpose hardware, so it is likely SaMD, while the scheduling functions stay outside device regulation. The company scopes the regulated function tightly and builds it under a documented life cycle. Onix Health builds medical device software under an IEC 62304 process and produces the software documentation an FDA submission needs. The manufacturer owns the submission and the clearance decision.