FDA Finalizes October 2026 Guidance on Prescription Drug Use-Related Software: App Output Treated as Drug Labeling, Device Authorization Remains Separate

Published: October 25, 2026, 09:32 | Category: Registration and Market Access

News Summary

On October 20, 2026, the U.S. Food and Drug Administration (FDA) issued the final guidance Regulatory Considerations for Prescription Drug Use-Related Software. The Federal Register published the notice of availability on October 21, 2026, at 91 FR 66561, Docket No. FDA-2023-D-2482. The guidance is dated October 2026 and replaces the draft guidance of the same title issued on September 19, 2023 (88 FR 64443).

The document was led by the CDER Office of Medical Policy, with participation from CBER, CDRH, the Oncology Center of Excellence, and the Office of Combination Products. This point is noteworthy: in the past, questions about whether software is a device were usually directed to CDRH; this document also applies the drug-labeling framework to software output.

What Counts as Prescription Drug Use-Related Software

The guidance sets a two-part threshold that must be met at the same time. First, the software is distributed by the drug sponsor or on the sponsor's behalf. Second, the end-user output generated by the software supplements, explains, or is textually related to a specific prescription drug of the sponsor.

End users may be patients, caregivers, or prescribers. As long as both conditions are met, the software falls within the scope of the guidance regardless of whether the software itself is regulated as a device.

Scope is limited to prescription drugs and drug-led combination products for which CDER or CBER is the lead review center. Device-led combination products led by CDRH are not covered by this document.

The boundary is also stated. Output that is not specific to the sponsor's drug, for example output addressing only a disease state, generally does not constitute prescription drug use-related software. The guidance also reminds sponsors that they must still assess whether device regulations apply.

Core Conclusion: What the Software Shows Users Is Labeling

The most substantive point is here. FDA treats the end-user output of this type of software directly as a form of prescription drug labeling.

Prescription drug labeling falls into two categories. One is statutory labeling approved by FDA in NDA, ANDA, BLA, and supplement applications. The other is promotional labeling, meaning labeling other than statutory labeling.

The category determines the next action. Output that is statutory labeling requires a change review before modification, following a process similar to changing the prescribing information. Promotional labeling is lighter: it is submitted on Form FDA 2253 at first distribution.

Device-Connected and Standalone Software: Whether to Include in Prescribing Information

The guidance sets two sets of rules for prescribing information based on software form.

Device-connected software generally should be described in the prescribing information, commonly in storage and handling sections. Examples include an inhaler or autoinjector that syncs use records to a mobile app. The guidance gives two examples: an inhaler records each use and the app displays the remaining dose; an autoinjector records the time of use and transmits it to the app. These descriptions address only the device component and software function; the end-user output itself is treated as promotional labeling.

There is an exception. If the sponsor provides adequate and well-controlled studies demonstrating a substantial improvement in clinical outcomes when the software is used, the information may be included in the Clinical Studies section. In that case, the output becomes statutory labeling, and postmarketing changes must be handled under 21 CFR 314.70 or 601.12; some changes may be included in the annual report.

Standalone software works the other way: it generally should not be included in the prescribing information unless the software is necessary for safe and effective use or there is evidence of a substantial improvement in clinical outcomes. If it is not necessary and such evidence is not available, the output is treated as promotional labeling and is not included in the prescribing information.

The guidance adds a new recommendation. When software is not necessary for safe and effective use, the prescribing information should note, where the function is described, that use of the software is not necessary for safe and effective use.

Submission Actions and Timing

Promotional output is submitted on Form FDA 2253 at first distribution, and the form includes PDURS as a selectable material type. Updates that do not change the content of previously submitted output, such as security patches or operating system upgrades, do not need to be resubmitted.

If the software itself constitutes a device and requires device marketing authorization, it is reviewed separately through the device pathway, and CDRH consults CDER or CBER as appropriate during review. The guidance states clearly that Form FDA 2253 cannot replace a device submission. For changes to an approved device, if the change involves a new clinical claim or is inconsistent with approved drug labeling and affects safety or effectiveness, a new device submission is generally required under 21 CFR 814.39(a) and 807.81(a)(3).

Changes Compared with the Draft

According to the Federal Register notice, there are four changes: further explanation of the assessment of standalone software functions; addition of a decision tree (Appendix A) to guide labeling determinations; examples of prescribing information wording for device-connected and standalone software (Appendix B); and a recommendation to add a note in the prescribing information for device-connected functions that do not have a substantial improvement in clinical outcomes.

Who Is Affected

Companies developing drug-device combination products for global markets, device manufacturers developing companion apps for pharmaceutical companies, and software companies working on digital therapeutics are all on this line. A suggested reverse order for assessment is: first determine the lead review center; then determine whether the software is distributed by the sponsor and whether the output points to a specific drug; only then address how the labeling should be written.

AIMEILI Regulatory Interpretation

The final guidance confirms a two-track model. The content shown to users by sponsor-distributed prescription drug software is assessed under the drug labeling framework, while the software itself may still require device authorization if it meets the device definition. This is not a new device classification rule; it is a labeling and submission rule that sits alongside device regulation.

For regulatory teams, the practical consequence is that software output must be mapped to labeling early. Device-connected functions are more likely to require prescribing information text and may need clinical evidence to enter the Clinical Studies section. Standalone functions are generally kept out of the prescribing information unless they are necessary for safe and effective use or supported by substantial clinical outcome evidence, but they may still be promotional labeling subject to Form FDA 2253.

The guidance also creates a documentation burden. Sponsors should keep a rationale for whether each software function is device-connected or standalone, whether it is necessary for safe and effective use, and whether the output is statutory or promotional labeling. The decision tree in Appendix A and wording examples in Appendix B are useful for internal labeling reviews, but the final responsibility remains with the sponsor.

Business Impact

• Drug sponsors and combination product companies: software output should be included in labeling strategy at the development stage. Promotional output requires Form FDA 2253 at first distribution, and device-connected features may require prescribing information updates and, in some cases, clinical outcome evidence.
• Device manufacturers supporting pharmaceutical apps: a 2253 submission by the drug sponsor does not replace device authorization. Where the software is a device, a separate device submission and change-control plan are needed.
• Digital therapeutics and software companies: standalone products may avoid prescribing information inclusion, but sponsor-distributed output can still be promotional labeling. Commercial teams should align claims and user-facing content with the labeling category.
• Global regulatory affairs teams and CROs: U.S. labeling and device pathways should be coordinated with other markets. The same app function may be drug labeling in the United States and a device or software item in another jurisdiction, so a single global content map is useful.

Sources and Scope Note

Sources: U.S. Food and Drug Administration, Regulatory Considerations for Prescription Drug Use-Related Software (final guidance, October 2026). Federal Register notice: Regulatory Considerations for Prescription Drug Use-Related Software; Guidance for Industry; Availability, October 21, 2026, 91 FR 66561. FDA press release: FDA Issues Final Guidance on Prescription Drug Apps and Software, October 20, 2026.

Federal Register notice: https://www.federalregister.gov/documents/2026/10/21/2026-21516/regulatory-considerations-for-prescription-drug-use-related-software-guidance-for-industry

Final guidance: https://www.fda.gov/media/172165/download

FDA press release: https://www.fda.gov/news-events/press-announcements/fda-issues-final-guidance-prescription-drug-apps-and-software

Verification scope and access date: on October 25, 2026, AIMEILI verified the main text of the guidance, including the explanation of Section IV labeling determinations, Appendix A decision tree, and Appendix B wording examples; the full Federal Register notice of availability; the full FDA press release; and the content date shown on the guidance page. Not every example wording in the appendices was verified line by line.

Scope note: this article is an interpretation of public regulatory information and does not constitute a conclusion or commitment for any specific product, company, or registration application. The official original text controls, and information may change with subsequent official updates.