Drugmakers' software output counts as drug labeling, FDA says in final guidance
The guidance, announced in the Federal Register Oct. 21, finalizes a 2023 draft. It covers software that drug sponsors distribute with prescription products and says when they should send FDA what that software displays.

When a drugmaker distributes an app or other software for use with one of its prescription products, what that software shows its users is a type of prescription drug labeling, in the Food and Drug Administration's view. The agency made that position final on Oct. 21.
FDA announced the final guidance, "Regulatory Considerations for Prescription Drug Use-Related Software," in a Federal Register notice that day. It finalizes a draft the agency issued on Sept. 19, 2023.
Why it matters: Treating software output as labeling puts it under FDA's drug labeling authorities, which shapes how sponsors describe their software in prescribing information and when they should submit its content to the agency. The policy applies whether or not the software is also regulated as a medical device, so some products sit at the intersection of drug and device review.
As the notice describes it, prescription drug use-related software generally has two features. It is distributed by a drug sponsor or on the sponsor's behalf, and it produces output tied to that sponsor's own drugs, by supplementing or explaining them or by otherwise relating to them in text.
The guidance applies to prescription drugs and to drug-led drug-device combination products for which FDA's drug center or biologics center is the lead. FDA defines end-user output as any content the software presents to the person using it, with patients, caregivers and health care practitioners given as examples. A software function is one distinct purpose the software serves.
The final document addresses three questions: how FDA plans to use its drug labeling powers on that output, how a product's prescribing information should describe software functions, and the timing and method for sending end-user output to FDA for review.
What changed from the draft
FDA listed four main changes since 2023. It clarified what it considers for standalone software functions, added a decision tree to walk sponsors through labeling determinations, and supplied sample prescribing-information language covering device-connected and standalone software alike.
The fourth change is a new recommendation. For device-connected software functions that do not meaningfully improve a clinical outcome, FDA now recommends adding a statement to the prescribing information. The agency also said it considered public comments on the draft and made editorial changes for clarity.
The notice does not reproduce the decision tree or the sample language. Sponsors will need the guidance document itself to see how those tools sort specific products.
How it fits and what comes next
FDA said the recommendations are meant to fit with work under way across its product centers, among them the digital health efforts of its Center for Devices and Radiological Health. It said it weighed existing agency policies so that device software is regulated consistently and so that review is coordinated when a sponsor's software is also reviewed as a device. The notice lists contacts at the drug, device and biologics centers.
The device center has its own software policy in motion. It plans a draft revision of its "Policy for Device Software Functions" guidance during fiscal 2027, as resources permit, according to the guidance agenda CDRH posted Oct. 1.
Like other guidance, the document is nonbinding and represents FDA's current thinking, the notice says, and a company may take a different approach that meets the relevant laws and regulations. FDA takes comments on its guidance documents at any time; this one sits under docket FDA-2023-D-2482.
The notice was signed by Grace R. Graham, FDA's deputy commissioner for policy, legislation and international affairs.



