FDA Finalizes Guidance Treating Drug Apps as Labeling

FDA finalized guidance on 20 October 2026 that pulls a wide range of patient-facing software — dose reminders, symptom trackers, inhaler-connected companion apps — under the agency's drug-labeling authority. The Federal Register notice announcing the final guidance, "Regulatory Considerations for Prescription Drug Use-Related Software," published 21 October 2026. The core move: software a sponsor distributes alongside a prescription drug can itself become part of that drug's labeling, whether or not the software is separately regulated as a device.

Why FDA is reaching for its labeling authority, not device authority

Software distributed alongside a prescription drug has historically been evaluated through two separate lenses: is it a regulated medical device (software as a medical device, or SaMD), and separately, does it affect the drug's labeling. This guidance addresses the second question directly and broadly. FDA's position is that when a sponsor — or an agent acting on the sponsor's behalf — distributes software that produces an end-user output textually related to the sponsor's drug, that output counts as prescription drug labeling under FDA's existing authorities, independent of whatever device classification the software itself might separately carry. A symptom tracker that is not a regulated device at all can still generate labeling obligations if its output is distributed by or for the sponsor and relates to the drug.

What counts as “sponsor-distributed,” and why that phrase does the real work

The guidance's practical reach depends heavily on how broadly “by or on behalf of a drug sponsor” gets applied. Trade coverage of the final text indicates this covers software built by a technology partner under contract or collaboration with the sponsor, not only software the sponsor's own engineering team ships — closing an obvious workaround where a company could outsource a companion app's development specifically to keep the output outside labeling scrutiny. Examples circulating in early coverage include inhaler-connected apps that track usage and adherence, standalone dose-reminder tools distributed under a sponsor's branding or in coordination with a sponsor's patient program, and symptom trackers that surface drug-specific guidance to the user. The common thread is not the software's technical classification but its functional relationship to the sponsor's drug and its distribution channel.

What sponsors and their technology partners need to do differently

• Audit existing software relationships: sponsors with any patient-facing app, reminder tool, or tracker tied to a branded drug — whether built in-house or through a vendor — should map which of those outputs are “textually related” to the drug product under this guidance's scope, not just which are regulated devices.
• Review vendor and technology-partner agreements: contracts with app developers and digital-health vendors built before this guidance finalized may not anticipate that the resulting software output is drug labeling, with the compliance and review obligations that status carries.
• Align with FDA on submission and review expectations: the guidance addresses when and how sponsors should submit end-user software output to FDA as part of required labeling — regulatory teams should confirm current submission practice against the final text rather than the September 2023 draft, since final guidance can and does shift from draft language after comment.
• Watch for downstream device-guidance interplay: this labeling-focused guidance sits alongside, not in place of, FDA's separate device-software framework; software that is both a regulated device and sponsor-distributed drug-related software may now face obligations under both regimes.

Background: a three-year path from draft to final

FDA issued the draft version of this guidance in September 2023 under docket FDA-2023-D-2482, describing the same core framework: applying drug-labeling authorities to end-user software output distributed by or for a sponsor. The draft drew comment from industry and professional groups, including a December 2023 letter from AMCP and later input from ATA Action addressing the guidance's PDURS (prescription drug use-related software) framework specifically, which trade coverage describes industry group members as broadly receptive to — particularly its treatment of the FDA-required-labeling category. The gap between the September 2023 draft and the October 2026 final guidance reflects the ordinary pace of FDA guidance finalization on a technically complex, cross-cutting topic rather than any reported controversy stalling the process; regulatory teams relying on the draft's specific language in the interim should now confirm current practice against the final text.

What remains open

The secondary coverage available at this writing describes the guidance's scope and labeling framework but does not fully detail every submission mechanic — exact timing requirements, the specific FDA review pathway for software-generated labeling updates, and how the guidance treats software updates issued after initial drug approval. Sponsors and their regulatory affairs teams should read the final guidance text itself, available on FDA's guidance documents page under the same docket, before changing internal processes, since the Federal Register notice announcing availability is not a substitute for the guidance document's full technical content.

Frequently asked questions

What did FDA finalize, and when?

On 20 October 2026, FDA finalized "Regulatory Considerations for Prescription Drug Use-Related Software." The Federal Register notice published 21 October 2026 under docket FDA-2023-D-2482, document number 2026-21516.

What software does the guidance cover?

Software disseminated by or on behalf of a drug sponsor producing an end-user output textually related to the sponsor's drug product, regardless of device-regulatory status — examples include inhaler-connected apps, dose reminders and symptom trackers.

What does "treated as labeling" actually mean?

FDA considers the covered software's end-user output a type of prescription drug labeling, subject to the same accuracy and consistency expectations as a package insert, regardless of whether a technology partner built the software.

How long has this been in the works?

FDA issued the draft in September 2023 under the same docket, FDA-2023-D-2482, taking public comment — including from AMCP and ATA Action — before finalizing just over three years later.