Clinical Decision Support Software (CDS) – Medical Device or Not, and How the FDA Draws the Line

Many products, particularly in the software sector, target workflows in hospitals and clinical decision-making. This quickly raises the question: Is this a medical device or not? Although the boundaries can blur depending on the case, the classification carries significant implications in terms of regulatory burden and liability. As a guide for making this distinction, the U.S. Food & Drug Administration (FDA) has published an updated guidance document on Clinical Decision Support Software (CDS). Specifically, the Agency describes the characteristics that define a medical device – and therefore when the FDA itself has regulatory jurisdiction:

According to the guidance, CDS software is exempt from the device definition when all four of the following criteria are met:

• No acquisition, processing, or analysis of medical images or signals
  The software is not intended to acquire, process, or analyze medical images or signals from in vitro diagnostics or patterns/signals from patient monitoring systems.
  
• Display, analysis, or printing of medical information
  The functionality is limited to displaying, analyzing, or printing medical information about a patient or other clinical information (e.g., clinical publications/papers and clinical practice guidelines).
• Support of healthcare professionals in prevention, diagnosis, or treatment
  The software is intended to support healthcare professionals in the prevention, diagnosis, or treatment of a disease or condition, or to provide recommendations in this regard.
  
• CDS software recommendations must be independently reviewable
  The software must enable healthcare professionals to independently review the basis of its recommendations, such that the clinical diagnosis or treatment decision is not based primarily on the CDS software's recommendation itself.
  

If all four criteria are met, the CDS software does not fall under FDA regulation as a medical device. As soon as one of the criteria is not met – for example, analysis of raw data, direct control of therapeutic decisions, or lack of transparency – the CDS software falls under the definition of a medical device pursuant to Section 201(h) of the Federal Food, Drug, and Cosmetic Act (FD&C Act). The guidance document thus provides greater clarity for developers and manufacturers of CDS software and identifies legally relevant boundaries.

What does this mean in practice?

For many vendors, a clearer regulatory framework is now emerging. At the same time, drawing the line in specific cases remains challenging – particularly for AI-based systems. Those interested in the details can find the guidance document on the FDA website.

Please feel free to reach out to us, and we will assess together whether your CDS software qualifies as a medical device subject to FDA oversight.