DocpingBlog
Get featured Subscribe

Product

Prescription Drug Use-Related Software: FDA Finalizes Guidance

The FDA outlines clear regulatory boundaries between required drug labeling and promotional user outputs for pharma companion apps.

Prescription Drug Use-Related Software: FDA Finalizes Guidance

The Food and Drug Administration (FDA) has finalized its regulatory framework for prescription drug use-related software, ending years of ambiguity for digital health companies that develop companion software alongside pharmaceutical treatments 13. For digital health engineering and product teams building tools that touch prescription therapeutics, the guidance establishes explicit boundaries between core product labeling that requires premarket agency clearance and day-to-day user outputs governed under standard promotional rules 13.

Key takeaways

  • The FDA finalized long-awaited guidance governing software outputs disseminated by or on behalf of drug and biologic sponsors 13.
  • Software paired directly with a medical device generally belongs in a drug’s official prescribing information, while standalone apps face strict clinical benefit thresholds to appear on drug labels 1.
  • Content displayed by standalone companion apps to end users will primarily be regulated as promotional labeling, subject to standard submission workflows 13.

Prescription drug use-related software encompasses any software that is disseminated by or on behalf of a drug sponsor and generates end-user outputs that supplement, explain, or otherwise textually relate to one or more of the sponsor’s prescription products 3. Under the Federal Food, Drug, and Cosmetic Act (FD&C Act), this framework applies regardless of whether the underlying software itself meets the statutory definition of a medical device 3.

The guidance, published in the Federal Register under Docket No. FDA-2023-D-2482, covers drug products as well as prescription drug-led, drug-device combination products assigned to the Center for Drug Evaluation and Research (CDER) or the Center for Biologics Evaluation and Research (CBER) 3. As defined by the agency, a “software function” represents a distinct purpose of the software, whereas “end-user output” refers to any content presented to a patient, caregiver, or healthcare practitioner 3. The agency treats these end-user outputs as a form of prescription drug labeling 3.

This release finalizes draft guidance that the agency originally issued on September 19, 2023 3. In the final release, the FDA addressed public feedback across industry and trade groups, clarifying how regulatory obligations shift depending on whether a tool is device-connected or standalone 123.

How does the FDA divide companion apps into categories?

The framework establishes two distinct categories for companion software, each carrying different evidentiary expectations and labeling implications 1:

  1. Apps connected to a medical device: Software paired directly with a physical device—such as a mobile application connected to an asthma inhaler—is generally expected to be described in the drug’s official Prescribing Information (PI) 1. Because the software plays a central operational role in how the patient administers or manages the medication, the FDA views its description on the drug’s primary label as critical 1.

  2. Standalone software: Tools such as medication dose reminders, symptom trackers, or automated health coaching platforms do not automatically belong in the prescribing label 1. Instead, standalone software should only be referenced in the official prescribing information if the sponsor demonstrates that the software is essential for safe and effective drug use, or presents clinical evidence showing a meaningful clinical benefit 1.

In most operating scenarios, content presented to users by standalone companion software will be regulated as promotional labeling rather than required prescribing information 1. This treats the user-facing screens, alerts, and instructions similarly to traditional direct-to-consumer and provider-directed drug advertising 1.

What changed between the draft and final guidance?

The FDA incorporated four major structural updates into the final text following review of industry comments submitted under Docket No. FDA-2023-D-2482 3.

First, the agency clarified specific regulatory considerations for standalone software functions, addressing ambiguity around products that assist patients without communicating with physical hardware 3. Second, the agency added an explicit decision tree designed to walk drug sponsors and technology vendors through labeling determinations step by step 3. Third, the guidance provides illustrative text examples showing how Prescribing Information language should be drafted for both device-connected software and standalone tools 3.

Fourth, the agency introduced a specific recommendation for device-connected software functions: if a connected software tool does not demonstrate a meaningful improvement in clinical outcomes, the sponsor should add a statement stating this directly in the Prescribing Information 3.

FDA leadership emphasized that the unified structure connects policy across its pharmaceutical and device centers. Captain Chris Wheeler, Pharm.D., Director of the Division of Medical Policy Programs in CDER, noted that the guidance aims to ensure information provided by apps is “accurate, evidence-based, and clearly communicated to both patients and their providers” 1. Michael Davis, M.D., Ph.D., Director of CDER, stated that the policy aligns CDER, CBER, and the Center for Devices and Radiological Health (CDRH) to establish a consistent pathway for digital health technologies 13. Jared Seehafer, M.S., FDA Deputy Commissioner for Technology, added that companion tools are evolving beyond static dose alerts into adaptive software, making a predictable foundation necessary 1.

What does this mean in practice for product and clinical teams?

For digital health engineering teams and pharmaceutical software partners, the final guidance establishes clear operational rules for product architecture, submission schedules, and label claims 13.

  • Audit product roadmaps against the decision tree: Digital health teams operating companion software must determine whether their software functions qualify as device-connected or standalone under CDER and CDRH standards 13. If a product does not connect to a device and lacks validated trial data showing clinical benefit, teams must avoid architecture and language that presume inclusion in official prescribing documentation 1.

  • Prepare standard promotional submission workflows: Because the FDA will treat most standalone end-user outputs as promotional labeling, sponsors and software partners must ensure their content pipelines support post-marketing promotional review rules, including submissions under Form FDA 2253 and compliance with 21 CFR 202.1 advertising standards 13.

  • Evaluate clinical claims for connected hardware: Teams developing software for connected delivery systems, like smart inhalers or injectors, must evaluate whether their clinical datasets support outcome claims 13. If no statistically meaningful clinical benefit is documented, technical writers and regulatory teams must prepare to include the FDA’s recommended negative disclosure statement directly in the product’s Prescribing Information 3.

  • Coordinate across drug and device centers: Software developers operating in partnerships with life sciences manufacturers should review the agency’s cross-center alignment 13. While the guidance does not create legally binding requirements on the public or agency per 21 CFR 10.115, it represents the FDA’s current thinking on prescription drug use-related software 3.

Our read: Digital health developers often hoped that pairing a companion app with a medication would automatically elevate the app into the official drug label, providing a strong clinical moat. By drawing a sharp regulatory line between required labeling and promotional materials, the FDA has clarified that software alone does not earn a spot on the drug label without rigorous proof of clinical benefit 13. Technology vendors should design their release pipelines around standard promotional submission workflows unless they have invested in formal clinical trials 13.

Sources

  1. FDA Issues Final Guidance on Prescription Drug Apps and Software — FDA, 2026-10-20
  2. STAT+: FDA finalizes its guidance on apps related to drugs, pharma rejoices — STAT, 2026-10-22
  3. https://www.federalregister.gov/d/2026-21516 — federalregister.gov

Researched and drafted with AI from the sources above, and checked claim by claim against them before publishing.

DT

Written by

Docping Team

The people building Docping Bridge — one API for every EHR.

Get featured

Your team could be the next story.

Building on Docping? Tell us what you shipped — we'll help you tell it.

Pitch your story

The Docping Briefing

One sharp read on healthcare interoperability. Every morning.

Written for founders, CTOs and clinical-ops leaders who build with EHR data. Free.