The clinical decision support exemption: when AI software isn’t an FDA device
Many AI tools sold to clinicians, from chart summarizers to risk scores, are marketed as "not a medical device". Often that rests on the clinical decision support (CDS) exemption in the 21st Century Cures Act.
This explainer covers what the exemption requires and what to ask when a vendor relies on it. It is general information, not legal or regulatory advice about any specific tool.
Last reviewed November 2026 · Independent and vendor-neutral
The four criteria
Software is excluded from the device definition only if it meets all four (FD&C Act section 520(o)(1)(E)).
The software must
- 1. Not acquire, process or analyze a medical image, a signal from an in vitro diagnostic, or a pattern or signal from a signal acquisition system (such as an ECG or EEG). Tools that read images or waveforms are devices.
- 2. Display, analyze or print medical information, such as patient data, clinical studies or practice guidelines.
- 3. Support or provide recommendations to a health care professional about prevention, diagnosis or treatment. Tools aimed at patients don’t qualify.
- 4. Let the professional independently review the basis for the recommendation, so they don’t rely mainly on the software.
What FDA’s January 2026 guidance changed
Key points
- FDA revised its CDS guidance in January 2026, replacing the 2022 version.
- Software that gives a single recommendation is no longer automatically treated as a device: FDA says it will use enforcement discretion when that one output is clinically appropriate and the other criteria are met.
- Time-critical use still counts against the exemption. When a clinician has no time to review the basis, FDA sees a higher risk of automation bias.
- The guidance puts more weight on presenting decision-relevant information clearly, without overload, so the clinician can actually check the reasoning.
Questions to ask a vendor who says "not a device"
Ask
- Which of the four criteria do you rely on, and do you have a written regulatory assessment you can share?
- Does any part of the product analyze images, waveforms or device signals? If so, which parts are FDA-cleared and which are not?
- What exactly does the clinician see to check the basis of a recommendation: inputs used, logic, sources, known limits?
- Is it used in time-critical settings (emergency, ICU, stroke) where review time is short?
- If FDA’s view changes, what is your plan, and what happens to our contract?
Remember
- "Not a device" means no FDA premarket review. Your own validation, monitoring and governance matter even more.
- Your hospital still owns how the tool is used. Liability questions don’t go away because software is outside FDA rules.