SaMD vs SiMD: How to Tell Which One Your Software Is

Software as a medical device performs a medical purpose on its own. Software in a medical device is part of the hardware and needed for it to work. FDA's examples, the gray zone between the two, the software that is not a device at all, and what changes for your team either way.

In short

  • SaMD is software intended for one or more medical purposes that performs them without being part of a hardware medical device, while SiMD is software integral to a hardware device, such as the code that drives an infusion pump's motors.
  • Software that a hardware device needs to achieve its intended use is not SaMD even when sold separately, and software that connects to a device but is not needed by it is SaMD rather than an accessory.
  • Both are device software functions under FDA's premarket software guidance and IEC 62304, so the documentation is similar; what differs is whose submission the software belongs to, which platforms it depends on and how updates reach users.

SaMD, software as a medical device, is software intended for one or more medical purposes that performs those purposes without being part of a hardware medical device. SiMD, software in a medical device, is software that is integral to a hardware medical device, such as the code that drives an infusion pump's motors or the closed-loop control in a pacemaker. To separate them, ask whether a hardware device needs this software to achieve its own intended use. If yes, it is part of that device. If the software achieves a medical purpose on its own, it is SaMD.

There is also a third answer. Some software that touches medical data is not a device at all, and the law says so explicitly. Getting the classification right early decides whose submission the software belongs to and how you will ship updates.

Where do the SaMD and SiMD definitions come from?

FDA's SaMD page uses the definition from the International Medical Device Regulators Forum: software intended to be used for one or more medical purposes that performs these purposes without being part of a hardware medical device. The same page describes three kinds of medical device software: SaMD, software that is integral to a medical device, and software used in the manufacture or maintenance of a medical device.

The SiMD abbreviation appears in FDA's guidance on predetermined change control plans, which says device software functions may include both SaMD and SiMD. That guidance defines a device software function as a software function that meets the device definition in section 201(h) of the Federal Food, Drug, and Cosmetic Act. Whether software is SaMD or SiMD, the starting question is the same: does it meet the device definition?

SaMD and SiMD compared
QuestionSaMDSiMD
What it isPerforms a medical purpose on its ownIntegral to a hardware medical device
FDA examplesMRI image viewer on a phone, breast cancer detection softwareInfusion pump motor control, pacemaker closed-loop control
Runs onGeneral purpose platformsThe hardware device
Whose submissionIts ownThe hardware device's
How updates shipApp stores, installers or the cloudUsually a firmware update
IEC 62304AppliesApplies

What software is not a device at all?

Section 520(o) of the FD&C Act, codified at 21 U.S.C. 360j(o), removes five kinds of software functions from the device definition:

  • Administrative support of a health care facility, such as billing, appointment scheduling, inventory and population health management.
  • Software for maintaining or encouraging a healthy lifestyle that is unrelated to diagnosing, curing, mitigating, preventing or treating a disease or condition.
  • Electronic patient records, under conditions: the records are created or reviewed by health professionals, the software is part of certified health IT, and it does not interpret or analyze the records to diagnose or treat.
  • Software that transfers, stores, converts or displays laboratory or other device data and results, unless it interprets or analyzes that data.
  • Certain clinical decision support that displays or analyzes medical information and supports a clinician's recommendation, when the clinician can review the basis and is not meant to rely primarily on it. Software that processes medical images or signals does not qualify for this exclusion.

If a function fits one of these and stays inside its conditions, it is neither SaMD nor SiMD. Add one feature that interprets data for a diagnosis, and the answer can change.

What does FDA count as SaMD?

FDA's examples page lists several:

  • Software that allows a smartphone to view images obtained from an MRI medical device.
  • Computer-aided detection software that performs image post-processing to help detect breast cancer.
  • Treatment planning software that supplies information used in a linear accelerator.
  • Software intended to diagnose a condition using the tri-axial accelerometer of a consumer device.

The page adds three clarifications. SaMD is capable of running on general purpose, nonmedical computing platforms. It may be interfaced with other medical devices, including hardware devices, and with general purpose software. And software that connects to a hardware medical device but is not needed by that device to achieve its intended medical purpose is SaMD, not an accessory to the hardware.

What does FDA say is not SaMD?

  • Software used to drive or control the motors and the pumping of medication in an infusion pump.
  • Software used in closed-loop control in an implantable pacemaker or other hardware medical devices.
  • Embedded software, firmware and micro-code.
  • Software required by a hardware medical device to perform the hardware's intended use, even if sold separately from the hardware.
  • Software that relies on data from a medical device but has no medical purpose, such as software that encrypts data for transmission from a medical device.
  • Software that enables clinical communication and workflow, including patient registration, scheduling visits, voice calling and video calling.
  • Software that monitors a device's performance for servicing, such as monitoring x-ray tube performance to anticipate replacement.

The first four are the SiMD side: the software is part of a hardware device, so it is regulated as part of that device. The rest are not SaMD because they lack a medical purpose of their own.

How do you work out which one your software is?

Write down the intended use first, then ask these questions in order.

  • Does the software have a medical purpose: diagnosis, cure, mitigation, treatment or prevention of disease? If not, it is likely not a device.
  • Does the function fit one of the 520(o) exclusions, and does it stay inside the conditions?
  • Does a hardware medical device need this software to achieve the hardware's intended use? If yes, it is part of that device, even if you sell or download it separately.
  • Does the software achieve its medical purpose on its own, on a phone, a PC or in the cloud, possibly using data from other devices? Then it is SaMD.
  • Does the product do several things? FDA's software guidance treats each distinct purpose as a function. A product that stores, transfers and analyzes data has three functions, and each one is assessed.

The multiple-function point matters most for platforms. A patient app might schedule visits, which is excluded, display device readings, which may be excluded, and compute a risk score that drives treatment, which likely is not. Separate the functions in your architecture and your documentation so the regulated part has clear boundaries.

Does the classification change the paperwork?

Less than teams expect. FDA's June 2023 guidance, Content of Premarket Submissions for Device Software Functions, covers firmware and other means for software-based control of medical devices, software accessories, and software-only functions that meet the device definition. The same documentation elements apply, and the level of detail, Basic or Enhanced, depends on the risk of the device's software functions in the context of its intended use, for the device as a whole.

IEC 62304 is the same for both. The IEC describes it as applying to the development and maintenance of medical device software when the software is itself a medical device or when it is an embedded or integral part of the final medical device.

What does change between SaMD and SiMD?

  • Whose submission it is. SiMD is part of the hardware device's marketing submission, and a change to it is a change to that device. SaMD has its own intended use and its own submission.
  • What it depends on. SaMD runs on general purpose platforms, so operating systems, browsers and cloud services become off-the-shelf software in your documentation. FDA's software guidance defines off-the-shelf software as a generally available component for which the manufacturer cannot claim complete life cycle control.
  • How updates ship. SiMD usually reaches users as a firmware update to the device. SaMD ships through app stores, installers or the cloud. Either way, FDA's October 2017 guidance on deciding when to submit a 510(k) for a software change to an existing device applies to the change, and for AI-enabled functions a predetermined change control plan can authorize planned changes in advance.
  • Security scope. Both need cybersecurity content in a submission, and FDA's software guidance points to its separate cybersecurity guidance for it. Networked SaMD and connected SiMD reach that content from different directions: the app and its cloud on one side, the device and its interfaces on the other.

What do teams get wrong?

  • Calling a companion app SaMD because it is sold separately. If the hardware needs it to achieve its intended use, FDA says it is not SaMD.
  • Assuming SaMD means lighter scrutiny. The documentation level follows the risk of the software functions, not whether the software runs on a phone.
  • Letting excluded features drift. A scheduling or records feature that starts interpreting data for a diagnosis can leave the 520(o) exclusion.
  • Classifying the product as one thing when it has several functions. Assess each function, and keep the boundaries in the architecture.
  • Deciding the classification after the build. The intended use, the safety class under IEC 62304 and the FDA documentation level all follow from it.

Need help with the engineering side?

We build medical device software, standalone or embedded in a larger system, under an IEC 62304 process, and we produce the software documentation an FDA submission needs. The manufacturer defines the intended use and makes the submission. Onix Systems has built software since 2000 and has 370+ engineers. If you are not sure which side of the line your product sits on, talk to one of our engineers. Our free five-day technical audit ends with a written report on your software, its functions and the documentation they will need.