The FDA’s final prescription drug use-related software guidance concerns what sponsor-linked software communicates about a medicine. It does not approve a category of apps or replace the separate assessment of whether software is a medical device. The October 2026 document explains how the agency intends to apply its existing drug-labeling authorities. Final FDA guidance
That makes the useful starting point more specific than “Does this app need FDA approval?” Who distributes it, what does it say about the drug, and what role does that information play in using the product?
Which software falls within the guidance?
The framework generally covers software disseminated by or on behalf of a drug sponsor whose output supplements, explains or is textually related to one or more of that sponsor’s prescription medicines. It also covers prescription drug-led combination products for which the FDA’s drug or biologics center leads the review.
Software that is not disseminated by or on behalf of a drug sponsor falls outside this guidance’s stated scope, even if its developer intends it to be used with a medicine. That scope boundary does not settle any separate device obligations.
The relevant output can be a static screen, a changing display or an audio message. The agency treats this material as a form of drug labeling, rather than looking only at the app’s underlying code. Scope and software output, sections I and III
Two labeling categories, with different consequences
The FDA distinguishes labeling it reviews and approves as part of a drug application from promotional labeling. Prescribing information—the professional information explaining a medicine’s use—is part of the first category. Promotional labeling still has to be truthful, balanced and non-misleading; the category does not mean that anything goes.
Three considerations shape the guidance’s approach: whether the software is essential to safe and effective use, whether evidence demonstrates a meaningful improvement in a clinical outcome, and whether the function relies on data from a device or a device part of the combination product.
A software description appearing in prescribing information is therefore not, by itself, evidence that the app improves health outcomes. The content and supporting evidence matter. Labeling considerations, sections II–IV
A connected inhaler and a standalone reminder are different cases
The distinction between device-connected and standalone functions concerns their data source. “Standalone” here means a function that is not device-connected, including one relying on information entered by the user. It does not mean that the function can never be a medical device.
The guidance gives a hypothetical connected inhaler that sends use information to an app displaying doses remaining. Even without evidence of an added clinical benefit, the sponsor should propose a brief description of that connectivity in prescribing information. The FDA also expects supporting information on reliable data handling and the risk of medication errors.
For an optional standalone function without evidence of a meaningful clinical improvement, the guidance generally points away from describing it in prescribing information. Its output would generally be promotional labeling. These examples illustrate the agency’s framework, rather than classify a real product. Device-connected and standalone examples, section IV.B
What an added-benefit claim needs
For either type of function, a sponsor can submit adequate, well-controlled evidence comparing use of the drug with the software against use without it. If the FDA determines that this demonstrates a meaningful clinical improvement, the guidance recommends describing the studies and results in the prescribing information. Associated output would generally be FDA-required labeling; certain later changes would need review and approval.
The document itself contains nonbinding recommendations, alongside references to existing legal requirements. It recommends early discussion with the relevant FDA review division. The decision tree is a way to understand that discussion, not a substitute for it. Clinical evidence and labeling changes, section IV.A and Appendix A
For a product team, the practical distinction is between a feature description and an evidenced clinical claim. For a reader encountering an app beside a medicine, the same distinction helps explain why connectivity, inclusion in a label and demonstrated benefit are different pieces of information.