AMIA Urges More Work on FDA’s Decision Support Guidance

Tuesday, February 6, 2018

Informatics experts anticipate tremendous innovation in CDS, necessitating a need for transparency and performance standards

In comments submitted to the Food & Drug Administration (FDA) today, the American Medical Informatics Association (AMIA) said new draft guidance is well-timed to initiate a broad discussion over the future of clinical decision support (CDS) and patient decision support (PDS) software. Several trends are converging to transform the delivery of knowledge resources through decision support software for patient care and wellness, including cloud-based computing, machine learning, and improved patient access to their clinical data. However, the nation’s leading biomedical and clinical informaticians also noted that the FDA’s draft guidance was incomplete, given a lack of discussion regarding how FDA would regulate CDS and PDS still considered medical devices.

Section 3060 of the 21st Century Cures Act of 2016 (Cures) compels the FDA to exclude certain software functionalities from the definition of device. This legislative language effectively prohibits the FDA from regulating that software as a device, which then may require pre-market review, clinical trials, and other clearance activities. Some of these excluded functionalities describe what is commonly understood as CDS, and the patient-facing equivalent, PDS.

However, not all CDS/PDS was excluded from the definition of the device by Cures. This draft guidance tries to articulate where the line between regulated device and unregulated functionality lies per the FDA’s interpretation of Cures.

AMIA supported development of the FDA’s guidance, but the group warned of “lingering confusion among developers and clinicians trying to determine whether specific decision support software is, or is not, considered a device.” This is because some of the criteria used to determine if a functionality should be excluded is ambiguous. For instance, one criterion requires independent review of the basis for recommendations presented by the CDS/PDS, and FDA describes such review to be independent if the clinician/patient does not “rely primarily on such recommendations, but rather on their own judgement.” Unfortunately, this caveat is founded in the Cures statute, so while ambiguous, it remains part of the equation to determine if the functionality is a device.

To be useful and practical for its intended audiences, AMIA recommended that the FDA:

  • Articulate why examples of software are categorized as exempt or not, using the criteria established by Cures;
  • Include discussion regarding FDA’s intended regulatory controls for CDS software considered a device, even if the intended regulatory controls are still in development; and
  • Include discussion regarding the anticipated literacy levels, and their variance, across intended users of patient decision support software functions.

AMIA and the informatics community it represents has a long history of development and innovation related to CDS. In 1997, AMIA led a consortium of diverse stakeholders to develop a framework for monitoring and regulating clinical software systems.  This consortium recommended that “the FDA focus its regulatory efforts on those systems posing highest clinical risk that give limited opportunities for competent human intervention,” and it established a decision algorithm for FDA to use in its regulation of standalone clinical software systems as medical devices.  

Since that time, cloud computing and machine learning have changed the way decision support software can impact patient care. CDS and PDS functionalities can be based on a trained neural network, multivariate regressions, or fuzzy logic with perhaps millions of data points, enabling a data-driven approach to decision-making at the bedside. This new paradigm also creates new risks to patient safety, and requires new thinking around regulation, the group noted.

“Twenty years ago, AMIA led a national dialogue over how to regulate software,” said AMIA President and CEO Douglas B. Fridsma, MD, PhD, FACMI. “Now is the time to revisit old assumptions, and the informatics community is eager to help.”

Click here for AMIA’s full response to FDA’s draft guidance.


AMIA, the leading professional association for informatics professionals, is the center of action for 5,500 informatics professionals from more than 65 countries. As the voice of the nation’s top biomedical and health informatics professionals, AMIA and its members play a leading role in assessing the effect of health innovations on health policy, and advancing the field of informatics. AMIA actively supports five domains in informatics: translational bioinformatics, clinical research informatics, clinical informatics, consumer health informatics, and public health informatics.