SaMD: Software as a Medical Device

Ke Li Yew
Ke Li Yew

In October 2016, the Food and Drug Administration (FDA), along with The International Medical Device Regulators Forum (IMDRF) issued a draft guidance document entitled “Software as a Medical Device (SaMD): Clinical Evaluation”.

The objective of the draft guidance is to “establish a common converged understanding of clinical evaluation and principles for demonstrating the safety, effectiveness and performance of software intended for medical purposes”.

SaMDs, considered to be a “type of medical device”, have serious implications for patients and the public at large. As such, medical device manufacturers of SaMDs must provide assurances as to the safety, effectiveness and performance capacities of their devices.

Clinical Evaluation

All medical devices must undergo a clinical evaluation. A clinical evaluation is the set of processes and activities “that [are] conducted during a product’s lifecycle as part of the quality management system.” It is the assessment and analysis of clinical data pertaining to a medical device to verify its “safety, effectiveness, and performance” capacity.

The guidance documents state that the criteria and the clinical evaluation processes must be as robust for SaMD as they are for medical devices. In particular, medical device manufacturers should read the clinical guidance as “technology[ically] agnostic.

What Constitutes Clinical Evidence?

Despite the fact that the standards applied to SaMDs are to be the same as those applied to medical devices, SaMD are different in kind. They belong to a complex system of interconnected systems that are interactive and that lend themselves to frequent changes, modifications and upgrades that affect their safety and effectiveness.

Additionally, SaMDs often interact with patients by:

  • Performing computations on data input; and/or
  • Providing data output to users to inform or drive clinical management; and/or
  • Aiding in the diagnosis or treatment of the patient

As such, the guidance document requires medical device manufacturers to demonstrate evidence that their SaMD is safe, performs as intended and carefully weighs and balances the risks and benefits to patients.

How Do Companies Provide Assurances?

Companies can provide assurances as to the efficacy and safety of their devices by crafting:

  • “Systematically planned clinical approaches;
  • “Generat[ing] adequate scientific evidence”;
  • Creating transparency; and by
  • Demonstrating the clinical validity of a given device’s intended purposes and indications for use.

Overall, medical device manufacturers must be able to demonstrate that their SaMD actually does what the manufacturers claim that it does; that it does it safely; and, that they can prove it under self-verified and/or independent reviews depending on the category of their device.

Nexus and Interoperability

Data input received by SaMDs rely, often, on additional data provided by a physical medical device. As such, the evidence produced by medical device manufacturers must address the safety and efficacy of their SaMDs at the nexus of all of the systems and devices with which the SaMD is intended to interact.

Providing evidence at the intersection is particularly important because healthcare decisions increasingly depend on the information and outputs provided by SaMDs and therefore will affect both clinical outcomes and overall patient care.

Public Commentary Requested on Draft Guidance

The draft guidance document, endorsed by the IMDRF’s management committee, has been submitted for public commentary.

Over the next 90 days, members of the medical device community are invited to review the guidance document and provide input.

In particular, the FDA and the IMDRF are requesting commentary on eight key aspects of the draft guidance document, including:

  • To what extent does the guidance document capture the objective of the document?
  • Are current clinical vocabularies applied properly?
  • Are there additional SaMD categories that should be addressed in the document?
  • Does the guidance document provide adequate guidance as to the clinical evaluation methods and processes that must be used to generate clinical evidence as defined by the IMDRF?
  • Are there any additional methods that can generate robust clinical evaluation evidence in addition to those included in the guidance document?
  • Are the recommendations identified in Section 7.2 appropriate for the stated purpose of providing clinical evidence and expectations on a category-by-category basis?
  • Are the recommendations identified in Section 7.3 appropriate for the stated purpose of providing an “independent review” as outlined in each SaMD category?
  • Since SaMD are unique and still emerging, will the proposed framework impact existing regulated devices and software in a negative fashion?

Under These Proposed Guidelines, What Must a Medical Device Manufacturer Do?

Depending on the “impact that a SaMD has on clinical outcomes and patient care, a SaMD manufacturer [must] gather, analyze and evaluate data, and develop evidence to demonstrate the assurance of safety, effectiveness and performance of the SaMD.”

They can accomplish this mandate by providing information that demonstrates a fit between the information that the SaMD provides and the “clinical needs within the intended healthcare situation and condition that includes consideration for the target population, characteristics of the disease or condition, and type of user.”

Orthogonal integrates modern agile product development best practices with patient safety and regulatory compliance to build SaMD and connected medical device systems. If you need help building your next SaMD, or to learn more, contact us or call us at (312) 372-1058.

Related Posts

White Paper

Software as a Medical Device (SaMD): What It Is & Why It Matters


SaMD Cleared by the FDA: The Ultimate Running List


Help Us Build an Authoritative List of SaMD Cleared by the FDA


Predetermined Change Control Plans: Seizing the Opportunity