FDA Finalizes Regulatory Framework for Prescription Drug Software
The U.S. Food and Drug Administration (FDA) has finalized its guidance for “Prescription Drug Use-Related Software” (PDURS), establishing a definitive policy on when digital tools distributed by pharmaceutical sponsors must comply with drug-labeling requirements. As reported by Crowell & Moring, the agency aims to resolve years of uncertainty regarding how software that supplements or explains a medication should be categorized and regulated.
The guidance, published in the Federal Register on October 21, 2026, centers on a core definitional shift: if software disseminated by or on behalf of a drug sponsor produces output that is textually related to that sponsor’s product, the FDA will generally treat that output as drug labeling. This classification forces sponsors to determine whether the software constitutes “FDA-required” labeling or “promotional” labeling, a distinction that carries significant operational and legal consequences. End-user output is defined as any content presented to a patient, caregiver, or healthcare practitioner, including static or dynamic screen displays, sounds, and audio messages.
FDA Splits Software Guidance into Two Buckets Based on Impact
The FDA’s approach splits PDURS into two distinct buckets based on clinical impact. Promotional materials must be submitted to the agency at the time of initial dissemination using Form FDA 2253. To determine whether software belongs in the Prescribing Information (PI), the FDA evaluates whether the software is essential to safe and effective use, leads to a meaningful improvement in a clinical outcome, or relies on device data. If the software is essential or provides a demonstrated meaningful clinical improvement, the output is generally considered FDA-required labeling, necessitating more rigorous review procedures for post-approval changes.
Software Integration in Prescribing Information
The guidance distinguishes “device-connected” software functions—which rely on data from a device or constituent part, such as an app paired with an inhaler—from “standalone” functions, which often rely on user-entered data. For device-connected software, the FDA recommends a case-by-case evaluation. In these instances, the PI may include a brief description of the connectivity, even if the end-user output itself is categorized as promotional labeling.
Operational Challenges for Pharmaceutical Sponsors
The FDA’s final framework moves PDURS management from a purely digital concern to a core labeling governance issue. As noted by Crowell & Moring, sponsors should be aware that software disseminated on their behalf may be subject to FDA drug-labeling requirements, including the submission of promotional output on Form FDA 2253. The agency also emphasizes that PDURS may still be subject to medical device regulations regardless of its labeling status. This dual-track reality means that even if an app’s output is classified as promotional labeling, the underlying software must still meet the agency’s expectations for device reliability and the prevention of medication errors, such as inaccurate dosing data.
Today, the @FDA issued its Regulatory Considerations for Prescription Drug Use-Related Software (PDURS) Final Guidance, providing a clearer framework for prescription drug companion apps. https://t.co/qobRaEzpLw The guidance increases transparency for patients and gives industry… pic.twitter.com/YWaxB8fElU
Unresolved Questions in Digital Health Compliance
The FDA has clarified that this guidance represents its current thinking and does not establish new laws, meaning sponsors may still utilize other approaches if they meet existing regulatory requirements.
FDA Addresses Third-Party App Compliance and Device Rules
Does this guidance apply to apps developed by third parties?
The guidance applies if the software is disseminated “by or on behalf of” a drug sponsor.
What happens if my software is classified as a medical device? The FDA notes that this guidance does not replace device marketing requirements. Sponsors must still adhere to device-style documentation and change-control expectations where applicable, and the agency notes that sponsors whose software meets the device definition should expect to address device requirements in parallel with drug-labeling considerations, as reported by Crowell & Moring.
Are all software updates subject to FDA review?
Not necessarily. The FDA acknowledges that certain updates, such as security patches or operating system changes that do not alter the end-user output, do not require resubmission via Form FDA 2253, according to Crowell & Moring.
Related reading