On December 8, 2017, the Food and Drug Administration (FDA) published a notice of availability for the Clinical and Patient Decision Support Software – Clinical and Patient Decision Support Software – Draft Guidance for Industry and Food and Drug Administration Staff (“Draft Guidance”). The Draft Guidance, available here, provides clarity on the scope of FDA’s regulatory oversight of (1) clinical decision support software intended for health care professionals, and (2) patient decision support software intended for patients and caregivers who are not health care professionals.

The purpose the Draft Guidance is to identify the types of decision support software functionalities that: (1) do not meet the definition of a “device” as amended by the 21st Century Cures Act (“Cures”); (2) may meet the definition of a “device” under Cures but for which FDA does not intend to enforce compliance with applicable regulatory requirements, including, but not limited to, premarket clearance and premarket approval; and (3) “devices” that will be the focus of FDA’s regulatory and enforcement oversight.

Medical device and software manufacturers with products that may influence medical decision-making should study the Draft Guidance since it reflects FDA’s current regulatory thinking.

Section 3060(a) of Cures amended section 520 of the Food, Drug, and Cosmetic Act to exclude certain software functions from the definition of a “device,” thereby reducing the regulatory obligations applicable to such software. Specifically, under Cures, “clinical decision support software” (CDS) that meets all four of the following criteria excluded from the definition of a medical device:

  1. Software that is not intended to acquire, process, or analyze a medical image or a signal from an in vitro diagnostic device or a pattern or signal from a signal acquisition system;
  2. Software that is intended for the purpose of displaying, analyzing, or printing medical information about a patient, or other types of information (such as a peer-reviewed clinical studies and clinical practice guidelines);
  3. Software that is intended for the purpose of supporting or providing recommendations to a health care professional about prevention, diagnosis, or treatment of a disease or condition; and
  4. Software that is intended to enable a health care professional (HCP) to independently review the basis for the recommendations that the software presents so that it is not the intent that such HCP rely primarily on any of such recommendations to make a clinical diagnosis or treatment decision regarding an individual patient.

Cures does not apply to patient decision support software (PDS), which refers to software that a patient or non-HCP caregiver may use to help make a medical decision. PDS implicates a much different balance of risks and benefits because the software must make up the difference between a lay patient and a physician’s education and training. With respect to PDS, the fourth criteria should allow patients or their non-HCP caregivers to independently review the software’s recommendation. FDA states that it does not intend to take enforcement action against manufacturers with PDS for violating the applicable regulatory requirements if the PDS meets all of the above criteria.

FDA does not single-out any one of the four criteria as being more important, but it does identify the fourth criteria as the lynchpin of its analysis. Therefore, manufacturers seeking apply the Draft Guidance must ensure that an HCP or a patient (or their non-HCP caregiver) can reach the same recommendation as the software, without relying primarily on the software to come to that decision. In practice, this means that the software functions clearly explain (1) the purpose or intended use of the software function; (2) the intended user (e.g., patient, non-HCP); (3) the inputs used to generate the recommendations (e.g., patient age and gender); and (4) the rationale or support for the recommendation.

The Draft Guidance provides many examples that manufactures can review to help understand how these criteria will be evaluated in practice. For example, software that simply identifies drug-allergy contraindications based on FDA-approved labeling, or identifies patients that meet the clinical definition of a disease based on test results, are no longer medical devices. On the other hand, software that conducts its own analyses on a patient and, for example, uses those analyses to create treatment or surgical plans, will continue to be medical devices under FDA’s oversight.

Either electronic or written comments on the Draft Guidance may be submitted to FDA by February 6, 2018 to ensure that the FDA considers all comments on the Draft Guidance before it begins work on the final version. Submit electronic comments to https://www.regulations.gov or submit written comments to the Dockets Management Staff (HFA-305), Food and Drug Administration, 5630 17 Fishers Lane, Rm. 1061, Rockville, MD 20852. Identify all comments with Docket No. FDA–2017–D–6569.

If you have any questions regarding the Draft Guidance, please contact the authors or your regular Squire Patton Boggs attorney.