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

Yashaswini Maregowda

April 7, 2026

Table of Contents

1. What Is Clinical Decision Support (CDS)?
2. Why FDA Regulates CDS?
3. The Four Legal Criteria for Non-Device CDS
4. CDS vs SaMD
5. Overview of the 2022 FDA CDS Guidance
6. Why was the FDA issue updated CDS Guidance in 2026?
7. Key Differences Between the 2022 and 2026 CDS Guidance
8. What Hasn't Changed
9. Challenges in CDS Development and Compliance
10. The CDS Development Lifecycle for regulated products
11. How Ketryx Can Help Companies Building CDS Software
12. Practical Guidance for CDS Developers
13. Common Misconceptions About CDS Regulation
14. Final Thoughts

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.

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

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).

1. Data source restriction
   Does not acquire, process, or analyze medical images, signals from IVD devices, or patterns from signal acquisition systems.

2. Medical information display
   Displays, analyzes, or prints medical information about a patient or other medical information such as clinical guidelines or peer-reviewed studies.

3. 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.

4. 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.

For example, 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

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

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. The guidance suggested that software providing a single specific output or directive would typically fail this criterion.

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

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

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

2026 Guidance: Provides detailed clarification regarding genomic applications.

6. Consistent Treatment of Patient-Facing CDS

Both the 2022 and 2026 guidance clearly state that software providing recommendations to patients or caregivers meets the definition of a device.

7. More Granular Risk-Based Examples and Contextual Analysis

2026 Guidance additions: Discusses data quality and source validation requirements.

What Hasn't Changed

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

Challenges in CDS Development and Compliance

Explainability and Transparency

Designing systems that are both powerful and interpretable remains challenging.

Regulatory Classification Uncertainty

Misclassifying CDS can lead to enforcement risk, delayed approvals, or product redesign.

Human Factors and Usability

The 2026 guidance underscored the importance of designing interfaces that enable, rather than replace, clinical judgment.

Lifecycle Management

As CDS systems evolve, particularly adaptive AI/ML systems, maintaining compliance through updates becomes increasingly complex.

Time-Critical vs. Non-Time-Critical Design

Developers must carefully consider whether their software will be used in time-pressured situations where independent review is impractical.

The CDS Development Lifecycle for regulated products

For CDS that qualifies as SaMD, organizations must implement robust lifecycle controls, including:

1. Requirements Definition

• Defining intended use and regulatory classification

2. Risk Management

• Risk management aligned with ISO 14971

3. Design and Development

• Software lifecycle controls (IEC 62304)

4. Verification and Validation

• Verification that implementation matches specifications

5. Human Factors Engineering

• Usability testing (IEC 62366)

6. Post-Market Activities

• Post-market surveillance

How Ketryx Can Help Companies Building CDS Software

Ketryx helps organizations developing CDS by embedding compliance directly into development workflows. This means algorithm transparency records, data representativeness documentation, and clinical validation summaries linked automatically.

Practical Guidance for CDS Developers

Step 1: Determine Your Classification

CDS Classification Flowchart

1. Does your software avoid acquiring, processing, or analyzing images, IVD signals, or patterns?
   Yes, continues
   No = Device

2. Does it display, analyze, or print medical information?
   Yes, continues
   No = Device

3. Is it intended to support (not replace) HCP judgment?
   Yes, continues
   No = Device

4. Can the HCP independently review the basis for the recommendation?
   All four criteria met = Non-device CDS
   Not subject to FDA medical device regulation

Step 2: Document Your Rationale

Regardless of your conclusion, document how your software maps to each criterion.

Step 3: Engage with FDA Early (If Uncertain)

If your classification is unclear, consider a Pre-Submission (Q-Submission).

Step 4: Build Appropriate Quality Systems

If regulated as a device:

• Implement design controls
• Establish risk management processes

If non-device CDS:

• Still implement appropriate software development practices

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.

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

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

Misconception 4: "Non-device CDS doesn't need quality systems." Reality: Good software development practices are still essential for safety and effectiveness.

Final Thoughts

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

Understanding this guidance is foundational to building safe, scalable, and compliant healthcare technology.