The FDA prescription drug software guidance answers a question that has hung over drug-company apps for years: when the text on a screen counts as drug labeling. In the final guidance, reported on 20 October 2026, the FDA says output from software that a drug sponsor provides with a prescription medicine is treated as a type of prescription drug labeling, and it explains when such software should be named in the Prescribing Information.
Key takeaways: the FDA prescription drug software guidance and app labelling
- End-user output from sponsor-provided software that relates to a drug product is treated as prescription drug labeling.
- Device-connected software should be described in the Prescribing Information; standalone software should be mentioned if it is essential for safe and effective use or gives a meaningful clinical benefit.
- A new decision tree helps sponsors decide how to classify app content.
- Companion app content is generally treated as promotional material, according to a trade report.
- The guidance is non-binding and finalises a September 2023 draft.
How the FDA prescription drug software guidance treats app output
The agency says prescription drug use-related software is software disseminated by or on behalf of a drug sponsor that produces end-user output supplementing, explaining or textually related to the sponsor’s drug products. It applies whether or not the software is itself regulated as a device. The Federal Register notice says the guidance is intended for products where CDER or CBER is the lead centre, and that it reflects current thinking and not a binding requirement.
The practical consequence is that what an app tells patients about a medicine is not a free-floating digital product: it falls within the system that governs drug labeling and promotion. That is the agency’s position as reported, not our reading. The agency’s guidance listings are on its guidance page.
Labelling examples under the FDA prescription drug software guidance
The guidance includes illustrative Prescribing Information language for device-connected and standalone software, and a recommended statement for device-connected functions that do not show meaningful improvement in a clinical outcome. We did not read the appendices, so we do not reproduce the wording. The trade report says the two groups are treated as follows:
- Device-connected, such as an app paired with an asthma inhaler: include in the PI because of its significant role in medication use.
- Standalone, such as symptom trackers, dose reminders or coaching tools: mention if essential for safe and effective use or if meaningful clinical benefit is shown.
- Unchanged content in a software update: no need to resubmit end-user output.
What changed since the draft FDA prescription drug software guidance
The FDA made five changes according to the Federal Register notice: clearer considerations for standalone software, a decision tree, illustrative PI language, a recommended PI statement for functions without meaningful clinical improvement, and editorial clarifications. It also replaced the draft’s phrase digital health technologies with a reference to software used with prescription drugs, according to the trade report. The draft was published as 88 FR 64443 on 19 September 2023.
The digital health market behind the FDA prescription drug software guidance
Acumen Research and Consulting’s report Digital Health Market Size, Share and Growth Report estimates the global digital health market at USD 217 billion in 2022 and USD 1,592 billion by 2032, a CAGR of 25.3% from 2023 to 2032. It says North America occupied around USD 93.4 billion in 2022, Europe is the second-largest regional market, and Asia Pacific is projected to grow fastest at more than 26% a year.
The figures cover digital health broadly and are not an estimate of the market for sponsor-provided drug apps. They explain why regulators want a consistent framework as the sector grows. More coverage is in our Healthcare IT section.
General background: the Prescribing Information and the FDA prescription drug software guidance
The Prescribing Information, often called the label or package insert, is the FDA-approved document that tells clinicians how to prescribe a medicine. It includes indications, dosing, warnings and instructions for use. Mentioning an app there signals that the app is part of how the drug should be used, which is why the guidance sets conditions for it. The FDA’s device-side work on software is described by its Digital Health Center of Excellence.
Our analysis of the FDA prescription drug software guidance: a framework with an evidence test
In our assessment, the FDA prescription drug software guidance is most important for what it does not do: it does not require sponsors to build apps, and it does not make every app part of the label. It tells them what to expect if they do. The test for standalone software, essential or clinically meaningful, means that a reminder tool without evidence is unlikely to appear in the PI.
The statement that content is generally promotional means that app copy will face the same scrutiny as other drug advertising, as reported. We have not assessed how this compares with the draft in practice and do not predict enforcement.
What is not disclosed about the FDA prescription drug software guidance
- The decision tree and PI examples in full.
- Submission mechanics for end-user output.
- Any estimate of how many apps are affected.
- Stakeholder comments on the final text.
Risks and caveats of the FDA prescription drug software guidance
This article draws on the Federal Register notice and a trade report, not the full guidance. Details may differ in the appendices. The guidance is non-binding. Acumen’s figures are third-party estimates. This is news reporting and not legal advice.
What to watch next on the FDA prescription drug software guidance
- Comments and questions from industry on the docket.
- Additional guidance on output updates.
- First labels that reference a companion app under the new framework.
- Joint work between drug and device centres.
FAQ
Is app output treated as drug labeling?
Yes, according to the FDA, end-user output from sponsor-provided prescription drug use-related software is treated as a type of prescription drug labeling.
Which apps go in the Prescribing Information?
Device-connected software should be described; standalone software if essential for safe and effective use or clinically meaningful.
Is the guidance mandatory?
No. It is non-binding and represents current thinking.
How we reported this: we relied on the Federal Register notice, a trade report and the Acumen Research and Consulting report cited above, and attributed every claim. Last updated 24 October 2026. This is news reporting and not advice.
