> ## Content Index
> Fetch the complete content index at: https://www.fdaweb.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Agency Clarifies Clinical Decision Support Software
- URL: https://www.fdaweb.com/agency-clarifies-clinical-decision-support-software/
- Published: 2026-01-29T12:00:00.000Z
- Updated: 2026-09-14T15:32:00.000Z
- Author: David McFarland
- Tags: Devices, #legacy-id-D5160567

FDA has issued an [updated guidance](https://www.fda.gov/media/109618/download?ref=fdaweb.com) clarifying when clinical decision support (CDS) software functions fall outside the definition of a regulated medical device, offering developers greater insight into how the agency interprets its statutory authority over digital health tools. The document, Clinical Decision Support Software, which supersedes an identically titled guidance issued on 1/6, includes recommendation that focus on how software uses medical data, the nature of its outputs, and the role of health care professionals (HCPs) in reviewing and acting on those outputs.

A central distinction in the guidance is between software that acquires, processes, or analyzes signals or patterns from medical devices — which FDA considers regulated device software — and software that merely displays, analyzes, or prints medical information. FDA defines “signals” and “patterns” broadly to include continuous or repeated measurements such as ECG waveforms, next-generation sequencing data sets, or continuous glucose monitoring trends. Software that interprets the clinical significance of such signals or images, including image analysis, ECG interpretation, or genetic variant analysis, generally remains subject to FDA oversight.

By contrast, discrete, point-in-time results, such as a single lab value or a blood pressure reading, from legally marketed devices are considered “medical information” and may be used by non-device CDS software if other statutory criteria are met.

The agency also reiterates that specimen collection systems and signal acquisition systems intended for medical purposes are typically medical devices, even when used in conjunction with laboratory-developed tests. However, FDA noted that some systems, such as general wellness or biometric identification tools not marketed for medical purposes, may fall outside its device authority.

In addressing software intended to support clinical decision-making, FDA emphasizes that non-device CDS must support — not replace — clinical judgment. Software may provide recommendations, risk estimates, treatment options, or differential diagnoses for HCPs to consider, but it cannot issue definitive diagnoses or direct treatment decisions, particularly when based on real-time physiologic signals, medical images, or other complex data inputs.

The guidance includes extensive examples illustrating when FDA intends to exercise enforcement discretion, such as software that recommends treatment plans to be reviewed and finalized by an HCP, or tools that estimate longer-term risks using well-established clinical data. Conversely, software that provides time-critical directives, relies on poorly validated data sources, or analyzes signals or images directly remains a regulated device.

A key requirement for non-device CDS is transparency. FDA said software must be designed to allow HCPs to independently review the basis for its recommendations, including clear descriptions of intended use, data inputs, algorithm development and validation, and known limitations. The agency also highlights concerns about automation bias, particularly in urgent clinical settings, noting that high levels of automation or time-sensitive decision-making may undermine an HCP’s ability to independently assess recommendations.