Updated:
Is your AI tool a medical device? FDA’s CDS guidance
FDA’s January 2026 guidance explains which decision support software falls outside the device definition, and what a hospital buyer should ask a vendor.
A vendor says the product is “just decision support,” so it does not need FDA review. For a hospital administrator, that sentence decides how much checking you need to do yourself. Whether it is true depends on what the software actually does, and FDA has published guidance on exactly this question.
What the guidance covers
FDA’s page for Clinical Decision Support Software shows a final guidance for industry and FDA staff dated January 2026. It explains how FDA reads the non-device clinical decision support criteria in section 520(o)(1)(E) of the Federal Food, Drug, and Cosmetic Act. That section was added to the statute by section 3060(a) of the 21st Century Cures Act, which excluded certain medical software functions from the device definition.
The guidance also says that FDA’s existing digital health policies continue to apply to software functions that meet the device definition, including functions meant for patients or caregivers. It includes many examples of both non-device decision support functions and device software functions.
Why the label is not enough
The exclusion is not a category a vendor can claim by name. A software function is outside the device definition only if it meets the statutory criteria, and FDA’s guidance is its explanation of how it applies them. So “decision support” on a brochure does not settle anything. What the software does with its inputs, and who uses its output, does.
For a hospital, this means the regulatory status of a clinical AI tool is the vendor’s position, not a fact you can read off the box. Ask for that position in writing, with the basis.
Questions to put to the vendor
- Do you treat this product as a medical device, or as non-device clinical decision support? On what basis?
- If it is a device, what is the FDA authorization and the intended use as authorized, and does our planned use match it?
- If you say it is not a device, which of the statutory criteria do you rely on, and what in the product design supports that?
- Does the product have versions or features meant for patients or caregivers, and are they treated differently?
Keep the written answer with the contract file. If it changes later, you will want to know.
Key takeaways
- FDA’s clinical decision support guidance is shown as final and dated January 2026 on FDA’s page.
- It explains how FDA reads the non-device criteria in section 520(o)(1)(E) of the FD&C Act.
- FDA says its digital health policies still apply to software functions that meet the device definition, including those for patients or caregivers.
- A vendor’s “decision support” label does not decide the question; ask for the position and its basis in writing.
Sources: FDA, Clinical Decision Support Software, guidance for industry and FDA staff