FDA's Final Guidance on Prescription Drug Software: When a Companion App Becomes Drug Labeling

On 20 October 2026, the United States Food and Drug Administration finalized its guidance on prescription drug use-related software. The message is short and consequential: the output a companion app or connected device shows a patient can be prescription drug labeling, and FDA regulates it as such. For any drug sponsor shipping software alongside a medicine, that reframes a software release as a labeling decision.

This matters well beyond the United States. Canadian pharmaceutical and combination-product companies that market, or plan to market, a drug with a companion app in the U.S. now have a clear framework for when that app is labeling, when it belongs in the Prescribing Information, and what to send FDA. This article walks through the guidance and what it means for Canadian sponsors.

Executive Summary

The final guidance, Regulatory Considerations for Prescription Drug Use-Related Software, finalizes the draft FDA issued in September 2023. It answers three questions and adds a decision tree and example Prescribing Information language. The key points for sponsors:

End-user output can be labeling. FDA considers the output a software function presents to the end user to be a type of prescription drug labeling when it is disseminated by or on behalf of the drug sponsor.
Two buckets: required labeling or promotional labeling. Whether the output is FDA-required labeling or promotional labeling drives how it is reviewed and what you submit.
The Prescribing Information may need to describe the software. Device-connected software is generally described in the Prescribing Information; standalone software is described when it is essential for safe and effective use or shows a meaningful clinical benefit.
Canada frames the same software differently. Health Canada often regulates companion software as a medical device under the Medical Devices Regulations, so a U.S. labeling analysis does not map one-to-one onto Canada.

What FDA Finalized

What is it? The guidance is titled Regulatory Considerations for Prescription Drug Use-Related Software. It finalizes the draft published on 19 September 2023 and appeared in the Federal Register on 21 October 2026 as document 2026-21516, under docket FDA-2023-D-2482. Prescription drug use-related software, often shortened to PDURS, is software disseminated by or on behalf of a drug sponsor for use with one or more of the sponsor's prescription drugs, including drug-led combination products.

Why does it matter? Companion apps, connected injectors, dosing calculators and adherence tools are now common. The guidance confirms that the content these tools show patients is not a free zone outside FDA's reach. When the sponsor disseminates it, FDA considers the end-user output to be a type of prescription drug labeling, with the compliance obligations that follow.

What should companies do? Treat every piece of software output your drug program disseminates as a labeling artifact. Decide early whether it is FDA-required labeling or promotional labeling, whether the software needs to appear in the Prescribing Information, and what you will submit to FDA. Build that analysis into your software development lifecycle, not into a scramble before launch.

How does it affect compliance? Labeling that is false or misleading, or that is not submitted when required, is a compliance problem regardless of whether it sits on a carton or a phone screen. Software that changes after launch can drift out of step with the approved labeling, so change control over app content becomes a labeling control.

End-User Output Is Drug Labeling

The anchor of the guidance is a single idea: FDA considers end-user output to be a type of prescription drug labeling. End-user output is what the software shows the patient or caregiver, such as a dosing reminder, an injection instruction, a tracked symptom trend or an educational screen. If the drug sponsor disseminates that output, FDA treats it as labeling for the drug.

That has two practical consequences. First, the content must be truthful, balanced and consistent with the approved labeling, just like a package insert. Second, the content may need to be submitted to FDA, and in some cases described in the Prescribing Information. The medium is new, but the labeling rules are the ones sponsors already know.

Required Labeling or Promotional Labeling? The First Question

What is it? The first question the guidance answers is whether a given piece of end-user output is FDA-required labeling or promotional labeling. The answer shapes the review pathway and the submission obligations.

In broad terms, output that is tied to the safe and effective use of the drug tends toward FDA-required labeling, while output that promotes the drug tends to be promotional labeling. FDA has indicated that the content of many standalone apps will, in most cases, be treated as promotional material, consistent with how the agency handles other drug advertising and promotion. The guidance adds a decision tree to help sponsors work through the classification.

Type of output	How FDA generally treats it	What that means for you
Output essential to safe and effective use (for example, device-connected dosing or injection guidance)	More likely FDA-required labeling	Describe in the Prescribing Information and submit for review as labeling
Standalone app content that promotes the drug	In most cases promotional labeling	Submit under the promotional labeling pathway; keep it truthful and non-misleading
Standalone app essential for safe and effective use, or with a meaningful clinical benefit	May warrant a description in the Prescribing Information	Document the basis and reflect it in labeling

When Software Goes in the Prescribing Information: The Second Question

What is it? The second question is when a software function should be described in the Prescribing Information, the FDA-approved labeling that guides the prescriber. The guidance treats device-connected and standalone software differently.

Software connected to a medical device, such as an app paired with a connected injector or sensor, generally should be described in the Prescribing Information, because the software plays a central role in how the medicine is used. Standalone software, which runs without a connected device, should be described when the sponsor can show it is essential for the safe and effective use of the drug or that it provides a meaningful clinical benefit.

The final guidance adds illustrative Prescribing Information language for both device-connected and standalone software, and it recommends a statement in the Prescribing Information for device-connected functions that do not show a meaningful improvement in a clinical outcome. In other words, if the software is part of the delivery system but the data does not prove it improves outcomes, the label should say so rather than imply a benefit.

What You Must Submit: The Third Question

What is it? The third question is what sponsors should submit to FDA when they distribute software output to end users. FDA-required labeling and promotional labeling follow different submission routes, and the guidance clarifies how each applies to software output.

The practical takeaway is that app content is not exempt from the submission discipline that applies to other labeling and promotional materials. Sponsors who already manage promotional review and labeling submissions should extend those processes to software output. Companies that have seen how FDA enforces against false or unsupported labeling claims will recognize the risk of leaving app screens outside that system.

The Canadian Angle: SaMD, the Product Monograph and Combination Products

What is it? Canada and the United States start from different places. The U.S. PDURS guidance works through the FDA's drug labeling authority. Health Canada often approaches companion software through its medical device framework, classifying software that meets the definition of a medical device as Software as a Medical Device under the Medical Devices Regulations.

That difference is not academic. A companion app that FDA analyses as drug labeling might, in Canada, require its own medical device licence and classification if it meets the Software as a Medical Device definition, while the drug side is handled through the product monograph. A Canadian sponsor planning a cross-border launch has to run both analyses and reconcile them, rather than assume one jurisdiction's answer travels.

Question	United States (FDA PDURS)	Canada (Health Canada)
Primary lens for companion software	Drug labeling authority over end-user output	Medical device framework (Software as a Medical Device), plus the product monograph for the drug
Where the software is described	Prescribing Information, where required	Product monograph for the drug; device licensing for qualifying software
Governing rules	FD&C Act labeling provisions and FDA guidance	Food and Drug Regulations and the Medical Devices Regulations (SOR/98-282)

For drug-led combination products, the two systems add another layer. Decide early which components are drug, which are device, and which are software, because that classification drives your submission pathway in each country. The same discipline that governs a Canadian drug approval pathway should extend to the software that ships with the product.

Prescription Drug Software Compliance Checklist

Use this checklist for each companion app, connected device or software function tied to your drug:

List every software output your drug program disseminates to patients or caregivers.
Classify each output as FDA-required labeling or promotional labeling, using the guidance decision tree.
Decide whether the software is device-connected or standalone.
Determine whether the software must be described in the Prescribing Information, and draft that language.
For device-connected functions without a proven clinical outcome benefit, add the recommended clarifying statement to the Prescribing Information.
Confirm every output is truthful, balanced and consistent with the approved labeling.
Route each output through the correct FDA submission pathway for required or promotional labeling.
Put change control over app content so updates stay consistent with approved labeling.
For Canada, assess whether the software meets the Software as a Medical Device definition and whether a device licence is needed, and align the product monograph.

Common Mistakes

Treating the app as outside FDA's reach. If the sponsor disseminates the output, it can be prescription drug labeling. A phone screen is not a loophole.
Implying a benefit the data does not support. A connected feature that does not improve a clinical outcome should be labeled honestly, not marketed as a benefit.
Skipping the submission step. App content follows the same submission discipline as other labeling and promotional materials. Leaving it out of that system is a gap FDA can act on.
Ignoring post-launch changes. Software updates can push content out of step with the approved labeling. Without change control, your labeling drifts.
Assuming one country's analysis fits the other. The U.S. treats companion software through drug labeling; Canada often treats it as a medical device. Run both analyses.

Frequently Asked Questions

What is prescription drug use-related software?

Prescription drug use-related software, or PDURS, is software disseminated by or on behalf of a drug sponsor for use with one or more of the sponsor's prescription drugs, including drug-led combination products. Examples include companion apps, connected injectors, dosing calculators and adherence tools.

Is a companion app's content considered drug labeling?

FDA considers the end-user output of software to be a type of prescription drug labeling when the drug sponsor disseminates it. That output must be truthful and consistent with the approved labeling, and it may need to be submitted to FDA and, in some cases, described in the Prescribing Information.

When does software have to appear in the Prescribing Information?

Device-connected software is generally described in the Prescribing Information because it is central to how the drug is used. Standalone software should be described when the sponsor can show it is essential for the safe and effective use of the drug or that it provides a meaningful clinical benefit.

Is the guidance binding?

FDA guidance documents describe the agency's current thinking and are recommendations, not binding rules. The underlying labeling requirements in the law, however, are binding. Following the guidance is the clearest way to meet those requirements for software output.

How does Canada regulate companion software?

Health Canada often regulates companion software through its medical device framework, classifying software that meets the definition of a medical device as Software as a Medical Device under the Medical Devices Regulations. The drug itself is handled through the product monograph. A Canadian sponsor should run both the drug and device analyses.

What changed from the 2023 draft?

The final guidance adds a decision tree for labeling determinations, illustrative Prescribing Information language for device-connected and standalone software, clearer treatment of standalone software, and a recommended Prescribing Information statement for device-connected functions that do not show a meaningful improvement in a clinical outcome.

How MFLRC Can Help

MF License & Regulatory Consultants helps pharmaceutical and combination-product companies bring companion software to market without a labeling surprise. We classify each software output as required or promotional labeling, draft the Prescribing Information and product monograph language, and build the submission and change-control processes that keep app content in step with the approved labeling. Our work spans FDA drug submissions and the labeling controls that keep both countries satisfied.

With more than 20 years of regulatory affairs and quality assurance experience across pharmaceuticals and medical devices, our team also advises on the Canadian Software as a Medical Device analysis, drug-led combination product strategy, gap assessments, SOP development and audits, so a cross-border launch is planned once, not twice.

Launching a drug with a companion app? Contact MFLRC for a prescription drug software labeling assessment tailored to your product and your target markets.

Book a Software Labeling Assessment

Conclusion

The PDURS guidance does not invent a new rulebook. It applies the familiar logic of drug labeling to the software patients now carry in their pockets. The output a companion app shows can be labeling, it may belong in the Prescribing Information, and it must be truthful and submitted like any other labeling. For Canadian sponsors, the added task is reconciling the U.S. labeling view with Canada's device-centred approach. The companies that classify their software early, label it honestly and control it after launch will turn a compliance obligation into a smoother path to both markets.