Understanding the Revised Clinical Decision Support Software Guidance and Its Impact

The FDA updated its Clinical Decision Support (CDS) Software guidance in January 2026, reshaping how developers and healthcare providers approach digital health tools. This update clarifies which CDS software functions are excluded from FDA regulation under the 21st Century Cures Act and which still require oversight. Understanding these changes is crucial for anyone involved in developing, deploying, or using clinical decision support tools.

What the Revised Guidance Covers

The FDA’s guidance focuses on Section 3060 of the 21st Century Cures Act, which excludes certain medical software functions from being classified as medical devices. This section specifically addresses software that provides clinical decision support but does not meet the definition of a device under the Federal Food, Drug, and Cosmetic (FD&C) Act.

The updated guidance explains:

• Which CDS software functions are considered Non-Device CDS under section 520(o)(1)(E) of the FD&C Act.

• Which software functions still fall under FDA regulation because they meet the device definition.

• Examples to help developers identify the appropriate regulatory pathway for their software.

  
  

This clarity helps reduce confusion about when FDA oversight applies and when it does not.

Why This Update Matters

Clinical decision support software plays a growing role in healthcare by helping providers make informed decisions. However, the regulatory landscape has been complex, with uncertainty about which tools require FDA approval.

The revised guidance:

• Reduces regulatory burden for software developers by clearly defining non-device CDS functions.

• Protects patient safety by ensuring that software with higher risk remains regulated.

• Supports innovation by allowing certain low-risk tools to enter the market more quickly.

• Provides practical examples to guide developers and healthcare organizations.

  
  

This balance encourages the development of useful CDS tools while maintaining necessary oversight.

Key Criteria for Non-Device CDS

The guidance outlines four main criteria that CDS software must meet to be considered non-device and thus outside FDA regulation:

1. Not intended to acquire, process, or analyze medical images or signals

   Software that processes raw medical data or images typically qualifies as a device.

   
   

2. Intended to display, analyze, or print medical information about a patient

   The software should work with existing clinical data rather than generating new data.

   
   

3. Intended to support or provide recommendations to a healthcare professional

   The software must be designed to assist, not replace, clinical judgment.

   
   

4. Intended to enable the healthcare professional to independently review the basis for the recommendations

   Transparency is essential. The clinician should understand how the software arrived at its advice.

   
   

If a CDS tool meets all these criteria, it is classified as non-device CDS and is not subject to FDA regulation.

Examples of Non-Device CDS Functions

The guidance provides concrete examples to illustrate non-device CDS:

• Software that displays patient lab results and highlights abnormal values without interpreting them.

• Tools that provide clinical guidelines or treatment pathways based on established medical knowledge.

• Software that calculates risk scores using well-known algorithms and allows clinicians to review the calculation method.

  
  

These examples show how CDS tools can support clinical decisions without triggering regulatory requirements.

When CDS Software Is Regulated as a Device

If a CDS tool does not meet the non-device criteria, it is considered a medical device and subject to FDA oversight. Examples include:

• Software that analyzes medical images to detect abnormalities.

• Tools that diagnose conditions or recommend specific treatments without clinician review.

• Software that processes raw signals from medical devices to generate new clinical data.

  
  

Such software carries higher risk and requires premarket review, quality controls, and post-market surveillance.

Impact on Developers and Healthcare Providers

The updated guidance affects multiple stakeholders:

For Developers

• Clearer definitions help determine whether FDA clearance or approval is necessary.

• Reduced regulatory hurdles for non-device CDS can speed up product development and market entry.

• Understanding regulatory pathways helps avoid costly delays and compliance issues.

  
  

For Healthcare Providers

• Awareness of which CDS tools are regulated ensures safer adoption.

• Transparency requirements help clinicians trust and effectively use CDS recommendations.

• Providers can better evaluate the reliability and limitations of CDS software.

  
  

Practical Steps for Compliance

Developers and healthcare organizations should:

• Review the updated guidance carefully to classify their software correctly.

• Document how their CDS software meets or does not meet the non-device criteria.

• Ensure transparency by providing clinicians access to the basis of recommendations.

• Engage with the FDA early if their software may require device classification.

• Stay informed about evolving digital health policies and guidance.

  
  

Looking Ahead

The FDA’s revised CDS guidance reflects a growing recognition of the role software plays in healthcare. By distinguishing between low-risk support tools and higher-risk devices, the FDA aims to foster innovation while protecting patients.

Developers who understand these distinctions can design software that meets regulatory expectations and delivers real value to clinicians and patients. Healthcare providers can adopt CDS tools with confidence, knowing when oversight applies and when it does not.

This update marks a significant step toward clearer, more practical regulation of clinical decision support software.