The FDA prescription drug software guidance, finalised in the week of 20 October 2026, sets out how the agency treats apps and other software that a drug company provides alongside a prescription medicine. Titled Regulatory Considerations for Prescription Drug Use-Related Software, it confirms that the text and other output such a program shows to patients or clinicians is treated as a form of prescription drug labeling.
Key takeaways from the FDA prescription drug software guidance
- The guidance finalises a draft issued on 19 September 2023, and the Federal Register notice of availability is dated 21 October 2026 (91 FR 66561, docket FDA-2023-D-2482).
- It covers software disseminated by or on behalf of a drug sponsor whose output supplements, explains or is textually related to the sponsor’s drug products, whether or not the software is itself regulated as a device.
- Software that is connected to a device, such as an app paired with an inhaler, should be described in the drug’s Prescribing Information (PI).
- Standalone software, such as a symptom tracker or dose reminder, should be mentioned in the PI if the sponsor shows it is essential for safe and effective use or gives a meaningful clinical benefit.
- The guidance is not binding; it represents the FDA’s current thinking.
What the FDA prescription drug software guidance covers
The FDA defines prescription drug use-related software as software that is disseminated by or on behalf of a drug sponsor and produces end-user output that supplements, explains or is textually related to one or more of the sponsor’s drug products. The definition applies whether or not the software is regulated as a device. The agency treats that output as a type of prescription drug labeling. The guidance applies to products for which the Center for Drug Evaluation and Research (CDER) or the Center for Biologics Evaluation and Research (CBER) is the lead centre.
It addresses three questions: how the FDA applies its drug labeling authorities to the output, how required labeling, especially the Prescribing Information, should describe the software’s functions, and when and how sponsors should submit the output to the agency. The FDA’s guidance documents are listed on its guidance search page, and comments can be made through docket FDA-2023-D-2482.
Device-connected versus standalone software under the FDA prescription drug software guidance
The guidance separates two groups. For device-connected software, such as an app paired with an asthma inhaler, the FDA says the software should be included in the drug’s Prescribing Information because of its significant role in medication use. For standalone software, such as symptom trackers, dose reminders or coaching tools, it should be mentioned in the PI if the sponsor shows it is essential for safe and effective use or demonstrates meaningful clinical benefit.
A trade report on the final guidance adds that content displayed by a companion app is generally treated as promotional material, consistent with how the FDA handles other drug advertising. We have not read the full guidance text for that point, so it is attributed to the report.
What changed in the FDA prescription drug software guidance from the 2023 draft
- Clearer considerations for standalone software functions.
- A new decision tree (Appendix A) to guide labeling determinations.
- Updated Appendix B examples showing how device and software components appear in the PI.
- Illustrative PI language for device-connected and standalone software.
- A recommended PI statement for device-connected functions that do not show meaningful improvement in a clinical outcome.
- A change of terminology from digital health technologies to software used with prescription drugs, plus editorial edits.
Submission and updates under the FDA prescription drug software guidance
According to the trade report, sponsors do not need to resubmit end-user output for a software update that leaves previously submitted content unchanged. The FDA will focus its review on factors that affect safe and effective use, including promotional labeling considerations, and says it may issue more guidance on certain types of output updates as it gains experience. That experience is described in the report as ongoing.
Market context for the FDA prescription drug software guidance
Acumen Research and Consulting’s report Digital Therapeutics Market Size, Share, Analysis, Trends and Forecast 2023 to 2032 puts the global digital therapeutics market at USD 5.2 billion in 2022 and projects USD 66.1 billion by 2032, a compound annual growth rate of 29.3% from 2023 to 2032. It lists apps for asthma, lifestyle management, mental health and diabetes nutrition among the attractive segments.
Digital therapeutics are a related but not identical category: the Acumen report does not describe sponsor-distributed companion apps as a separate market, so its figures give context only. See our Healthcare IT coverage.
General background: why labeling matters for apps
Prescription drug labeling, especially the Prescribing Information, is the main document that tells clinicians how to use a medicine safely. If an app changes how a drug is dosed, monitored or taken, regulators want that reflected in labeling and to review what the app tells patients. The guidance tries to give sponsors a predictable way to decide what belongs in the label.
Our analysis: what sponsors and developers should take from it
In our assessment, the FDA prescription drug software guidance mainly gives sponsors a decision framework and reduces uncertainty about whether and how an app appears in the label. The test for standalone software, essential for safe and effective use or meaningful clinical benefit, is a high bar that will push sponsors to gather evidence for an app’s value.
The practical effect on developers who work for drug companies will depend on how the FDA applies the decision tree. We have not seen the appendices, so we do not describe them in detail. CDER Director Michael Davis described the approach as risk-proportionate oversight of digital health, according to the report.
What is not disclosed about the FDA prescription drug software guidance
- The full content of the decision tree and example PI language, which we did not read.
- Exact submission procedures and timelines for end-user output.
- How many sponsor apps are currently on the market.
- Industry reaction, which was not included in the reports we read.
Risks and caveats of the FDA prescription drug software guidance
The guidance is non-binding, and this summary relies on the Federal Register notice and a trade report. One report expands the abbreviation PDURS differently from the Federal Register title; we use the FDA’s own title. Acumen’s figures are third-party estimates. This article is news reporting and not legal or regulatory advice.
What to watch next on the FDA prescription drug software guidance
- Industry comments on docket FDA-2023-D-2482.
- Further FDA guidance on software output updates.
- Examples of Prescribing Information that cite companion apps.
- Alignment with FDA device guidance from the Digital Health Center of Excellence.
FAQ
What is the FDA prescription drug software guidance?
A final guidance titled Regulatory Considerations for Prescription Drug Use-Related Software, which explains how the FDA treats drug-linked apps and their output as labeling.
Does it make apps mandatory?
No. It explains how output is treated and when software belongs in the Prescribing Information. It is non-binding guidance.
When was it finalised?
It was reported finalised on 20 October 2026, with the Federal Register notice dated 21 October 2026.
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.