Every reminder, chart and nudge in a drug company’s app is now, in the FDA’s eyes, drug labeling. That is the same category as the leaflet in the box and the brochure in the doctor’s office.
That was the core idea of a draft the FDA published in September 2023. Three years later it is final [1]. For drug makers it settles how their apps are regulated. For the digital health companies that build those apps, and for anyone designing a drug programme around wearable data, it decides what every screen can say and who has to sign it off.
The short version is in the title: unless an app is essential to using the drug or a trial proves it improves a clinical outcome, what it shows counts as promotion.
What did the FDA finalise in October 2026?
A guidance for industry titled Regulatory Considerations for Prescription Drug Use-Related Software, published in the Federal Register on 21 October 2026 under docket FDA-2023-D-2482 [1]. It covers software that:
- is disseminated by or on behalf of a drug company, and
- produces output that “supplements, explains, or is otherwise textually related to” one of that company’s drugs, “regardless of whether the software is regulated as a device” [1].
“Output” means anything the software presents to a patient, caregiver or clinician, from screens to messages and sounds [1][2]. “On behalf of” reaches further than the drug company’s own app: it can include a developer working under an agreement with the company, or an app the company points patients towards [2][3].
Is a drug company’s app part of the drug’s label?
Once output counts as labeling, the guidance sorts it two ways [1][2][3]:
- Into the Prescribing Information, the official label, only if the software is essential to safe and effective use of the drug, or if adequate and well-controlled studies show a meaningful improvement in a clinical outcome compared with the drug without the software.
- Otherwise, promotional labeling. The output must be submitted to FDA on Form FDA 2253 when it is first released, and resubmitted when it changes. Software updates that leave the output unchanged, such as security patches, generally do not need resubmitting [2][3].
Device status does not change the answer. Being a low-risk device, or one under FDA’s enforcement discretion, does not exempt the output from drug labeling review, and a Form 2253 filing does not replace a device submission where one is needed [2][3].
What does it take to get an app into the drug’s label?
Evidence that the drug works better with it. The guidance’s own new example is a standalone diabetes app with dose reminders, health tracking and behavioural coaching, studied in a randomised trial against using the drug without the app [2]. Real-world data can contribute where appropriate [2][3].
Even then, the label has limits. Software is described in sections such as Clinical Studies, not in Indications and Usage or Dosage and Administration, which matters for tools that help choose patients or doses [2]. And where a connected function is not needed to use the drug safely, the label is expected to say so [1][3].
For most companion apps, that is a high bar. A reminder app that helps people stay on treatment is useful, but showing it produces a meaningful improvement in a clinical outcome in a controlled trial is a drug-development project, not a product sprint. Expect most apps to live as promotional labeling.
What changed from the 2023 draft?
| 2023 draft | 2026 final | |
|---|---|---|
| Decision process | No decision tree | A decision tree for labeling determinations [1] |
| Standalone software | Less detailed considerations | Clarified when it belongs in the label, with a randomised diabetes app example [1][2] |
| Device-connected functions | No such statement recommended | A recommended statement in the label when they show no meaningful clinical improvement [1] |
| Device review and Form 2253 | Device review could stand in for a separate 2253 filing | Form 2253 filing applies whether or not the device side was reviewed [2] |
| Example label language | None | Illustrative Prescribing Information wording for both kinds of software [1] |
The direction is clear: fewer shortcuts, more paperwork, and a clearer reward for companies willing to run the trial.
Does it cover apps that use wearable data?
Not by name. The guidance’s device-connected examples are inhalers and autoinjectors that send dose data to an app [3]. Consumer wearables are not mentioned [3].
That does not put wearable-based features outside it. The test is about the output, not the data source. Take a weight-loss drug programme that reads heart rate from a watch. In our analysis of GLP-1 drugs and wearable data, 26% of adults on Wegovy had a resting heart rate rise of 20 bpm or more at some visit, against 16% on placebo. A screen in a drug company’s app that tells a user their rising heart rate is expected on that drug is output about the drug, so under this guidance it is drug labeling, whatever sensor produced the number. The same chart in an independent fitness app, not distributed for the drug company and not about its drug, is not.
What should teams building these apps do?
- Settle who is distributing the app. If a drug company pays for it, co-brands it or directs patients to it, assume “on behalf of” applies and plan for labeling review [2][3].
- Separate disease content from drug content. Output only about a condition generally falls outside the guidance [1][3]. Keep those parts of the product distinct, and know which screens mention the drug.
- Inventory every output. Screens, notifications, coaching scripts and sounds. Promotional output is filed when first released and again when it changes, so build change control that separates content changes from code changes [2][3].
- Decide early whether to chase the label. A place in the Prescribing Information needs a controlled trial against the drug alone, and FDA encourages early engagement on design and endpoints [2][3].
- Do not rely on device status. Wellness positioning or enforcement discretion does not exempt drug-specific output [2]. FDA’s separate wellness rules, which we covered in the 2026 general wellness guidance, answer a different question.
- Watch for a challenge. Some lawyers argue FDA’s First Amendment reasoning for treating software output as labeling is weak [2]. Plan for the guidance as written, but expect it to be tested.
The FDA has finally answered how to treat the app that ships with a drug: as part of the drug’s labeling. Most of those apps will be promotional material, filed and tracked like any other. The ones that make it into the label will be the ones whose makers ran a trial and showed patients did better. That raises the bar, and it also gives a clear target to any team that thinks its app genuinely changes outcomes.
References
- Food and Drug Administration (21 October 2026). Regulatory Considerations for Prescription Drug Use-Related Software; Guidance for Industry; Availability. Federal Register, docket FDA-2023-D-2482. https://www.federalregister.gov/documents/2026/10/21/2026-21516/regulatory-considerations-for-prescription-drug-use-related-software-guidance-for-industry
- Arnold & Porter (October 2026). FDA issues prescription drug use-related software guidance after a several-year delay. https://www.arnoldporter.com/en/perspectives/advisories/2026/10/fda-issues-prescription-drug-use-related-software-guidance-after-a-several-year-delay
- Crowell & Moring (4 November 2026). FDA issues final guidance on prescription drug use-related software (PDURS): what sponsors must do now. https://www.crowell.com/en/insights/client-alerts/fda-issues-guidance-on-prescription-drug-use-related-software
- Sahha. Biomarkers. Sahha Docs. https://sahha.ai/docs/products/biomarkers/