Understanding the FDA's 2026 Clinical Decision Support Software Guidance: What Medical Device Companies NTK

Yashaswini Maregowda

April 7, 2026

In February 2026, the FDA quietly redrew the map for Clinical Decision Support (CDS) software. The core framework didn't change. The four criteria from the 21st Century Cures Act still stand. But the agency's updated guidance introduced enforcement discretion for single clinically appropriate recommendations, explicit automation bias language, and prescriptive transparency requirements that didn't exist before.

For teams that built CDS products under the 2022 guidance, this necessitates evaluating if the classification rationale still holds.

Many organizations built CDS tools assuming they fell outside FDA oversight. Some were right. Others are about to discover that the 2026 guidance's expanded examples and sharper definitions have moved their product from "probably non-device" into regulated territory. The cost of getting this wrong isn't theoretical: it's a redesign, a delayed launch, or an unplanned conversation with the FDA.

As software becomes deeply embedded in clinical workflows, CDS systems are rapidly shaping how healthcare decisions are made. From risk calculators and diagnostic algorithms to AI-powered recommendations, CDS tools are now central to modern healthcare delivery.

However, with increased influence comes increased regulatory scrutiny. Many organizations build CDS tools assuming they are not regulated medical devices, only to later discover they fall under FDA oversight. Understanding the FDA's CDS guidance is now essential for developers, quality teams, regulatory professionals, and digital health leaders.

This blog provides a complete introduction to CDS for beginners, explains the key differences between the FDA's 2022 and 2026 CDS guidance, and breaks down how to build a classification strategy that holds up under the new guidance.

What Is Clinical Decision Support (CDS)?

Clinical Decision Support (CDS) refers to software that provides information, recommendations, or insights to support clinical decision-making.

CDS systems are designed to assist healthcare professionals in making informed decisions about diagnosis, treatment, disease prevention, care management, and patient monitoring.

Examples of CDS tools include:

Drug-drug interaction alerts
Algorithms that analyze radiology images
Software that suggests treatment options based on patient history
Risk stratification dashboards for chronic disease management

Not all CDS is regulated. The regulatory status depends on how the software functions and how users rely on it.

Why FDA Regulates CDS?

CDS software can directly influence clinical decisions. When software meaningfully impacts diagnosis or treatment, patient safety risks increase.

To address this, the U.S. Congress included provisions for CDS in the 21st Century Cures Act (2016). This law created a category of CDS that could be excluded from regulation as a medical device, but only if specific criteria are met.

FDA's CDS guidance documents explain:

Which CDS functions may be exempt from regulation
Which CDS functions are considered medical devices
How manufacturers should interpret and apply the law

As technology evolved, particularly with the rise of AI/ML, the FDA updated its interpretation, resulting in important clarifications between the 2022 and 2026 guidance.

The Four Legal Criteria for Non-Device CDS

Four Criteria for Non-Device CDS

21st Century Cures Act, Section 520(o)(1)(E)

Software must meet all four criteria to qualify as non-device CDS. Failing any one makes it a regulated medical device (SaMD).

Data source restriction: Does not acquire, process, or analyze medical images, signals from IVD devices, or patterns from signal acquisition systems.
Medical information display: Displays, analyzes, or prints medical information about a patient or other medical information such as clinical guidelines or peer-reviewed studies.
Support, not replace, clinical judgment: Intended to support or provide recommendations to healthcare professionals about prevention, diagnosis, or treatment. Not to replace or direct clinical judgment.
Independent reviewability: Enables the healthcare professional to independently review the basis for the recommendations so they do not rely primarily on those recommendations.

Pass all four = Non-device CDS

Fail any one = Regulated SaMD (medical device)

CDS vs SaMD

CDS and SaMD often overlap but are not identical.

Non-device CDS: Software that meets all four criteria and is not regulated as a medical device.

Device CDS (regulated SaMD): CDS that fails one or more criteria and therefore qualifies as Software as a Medical Device (SaMD), subject to FDA regulation.

In Feb 2026, a rule-based checklist that references clinical guidelines and clearly shows its logic may qualify as non-device CDS, while an AI model that outputs a diagnosis without enabling clinicians to understand the reasoning likely qualifies as regulated SaMD.

Overview of the 2022 FDA CDS Guidance

The 2022 guidance represented the FDA's comprehensive interpretation of how CDS should be regulated under the Cures Act framework. It established:

Clear examples of regulated vs non-regulated CDS
The requirement for meaningful transparency and independent reviewability
Recognition that CDS risk depends on how it is used in clinical practice
Acknowledgement of emerging technologies such as AI/ML
The principle that proprietary algorithms still need to provide adequate background information

The 2022 guidance provided a solid foundation, but as the FDA gained more experience reviewing digital health and AI-enabled submissions, it identified opportunities for enhanced clarity.

Why was the FDA issue updated CDS Guidance in 2026?

Between 2022 and 2026, the FDA observed:

Growing complexity in AI/ML implementations
Need for more specific examples to guide the industry
Questions about single clinically appropriate recommendations
Need for clearer distinction between patterns and discrete measurements
Importance of addressing time-critical decision-making explicitly
Evolving landscape of genomic and precision medicine applications

The 2026 guidance builds on the 2022 framework with enhanced clarity, expanded examples, and important new policies.

Key Differences Between the 2022 and 2026 CDS Guidance

1. Introduction of Enforcement Discretion for Single Clinically Appropriate Recommendations

2022 Guidance: Criterion 3 required software to provide recommendations that support rather than replace clinical judgment.

2026 Guidance: Introduces a significant new policy: "If only one option is clinically appropriate and the software function otherwise meets all criteria under section 520(o)(1)(E), FDA intends to exercise enforcement discretion for such functions."

2. Expanded Examples

2022 Guidance: Provided approximately 12-15 examples across different categories.

2026 Guidance: Includes 32 detailed device software function examples in Section V.C alone, plus numerous additional examples throughout the document illustrating non-device CDS.

3. More Explicit Guidance on "Patterns" vs. Discrete Measurements

2022 Guidance: Mentioned patterns under Criterion 1, but without extensive detail about the distinction from discrete measurements.

2026 Guidance: Provides a clear definition: "Discrete, episodic, or intermittent point-in-time physiological measurements generally do not, by themselves, constitute a pattern."

4. Enhanced and More Prescriptive Criterion 4 Requirements

2026 Guidance: Provides substantially more prescriptive recommendations for what "independently review the basis" actually means.

5. Significantly Enhanced Genomic and Precision Medicine Guidance

6. Consistent Treatment of Patient-Facing CDS

Both guidance versions state clearly that software providing recommendations to patients or caregivers meets the definition of a device. This has not changed.

7. More Granular Risk-Based Examples and Contextual Analysis

What Hasn't Changed

The four-criteria framework is unchanged
The requirement for transparency, regardless of algorithm complexity was present in both versions
Patient-facing CDS as devices was already clear in 2022
Focus on actual functionality over labeling alone has been the FDA's approach throughout
Risk-based evaluation principles remain consistent

The 2026 guidance builds upon and clarifies the 2022 framework rather than replacing it with a fundamentally different approach.

Challenges in CDS Development and Compliance

Explainability and Transparency

Regulatory Classification Uncertainty

Human Factors and Usability

Lifecycle Management

Time-Critical vs. Non-Time-Critical Design

The CDS Development Lifecycle for regulated products

Requirements Definition
Risk Management
Design and Development
Verification and Validation
Human Factors Engineering
Post-Market Activities

How Ketryx Can Help Companies Building CDS Software

For teams building CDS that qualifies as SaMD, the 2026 guidance clarifies the rules and raises the standard for what is sufficient as "compliant".

Practical Guidance for CDS Developers

Step 1: Determine Your Classification

Step 2: Document Your Rationale

Step 3: Engage with FDA Early (If Uncertain)

Step 4: Build Appropriate Quality Systems

Common Misconceptions About CDS Regulation

Misconception 1: "AI/ML CDS can't be non-device CDS." Reality: AI/ML CDS can qualify as non-device CDS if it meets all four criteria, including providing sufficient transparency for independent review.

Misconception 2: "The 2026 guidance fundamentally changed the rules." Reality: The 2026 guidance clarified, expanded, and enhanced the 2022 framework. The core principles remained consistent.

Misconception 3: "If our labeling says it's for HCP support only, we're exempt." Reality: FDA evaluates actual functionality and likely use, not just labeling claims.

Misconception 4: "Non-device CDS doesn't need quality systems." Reality: While not subject to medical device regulations, good software development practices are still essential for safety and effectiveness.

Final Thoughts

If you're new to CDS regulation, the most important takeaway is this:

The 2022 guidance established a comprehensive framework. The 2026 guidance enhanced it with greater clarity, expanded examples, and important new policies.

The FDA evaluates CDS based on what data it uses, how it's intended to be used, whether clinicians can meaningfully review its recommendations, whether the use is time-critical, and actual functionality, not just labeling.

The regulatory landscape will keep evolving, but the principles hold: transparency, safety, and keeping clinical judgment central to patient care.