FDA finalizes guidance on apps tied to prescription drugs
The agency's October 20 guidance tells drugmakers exactly when a companion app, symptom tracker, or dose reminder has to show up on the official prescribing label — and gives sponsors a decision tree to work it out.
On October 20, 2026, the FDA released final guidance on prescription drug use-related software, closing out what the agency calls "longstanding uncertainty" over when apps distributed alongside a prescription medicine fall under drug labeling rules. The guidance covers everything from inhaler-connected apps to standalone symptom trackers, dose reminders, and health-coaching tools sponsors ship with a drug.
As RAPS reports, the final version adds a decision tree and sample prescribing-information language that weren't in the draft — a direct response to sponsors who said the earlier text left too much open to interpretation. For teams building a patient-facing companion app, that's the difference between guessing and having a checklist.
It's a pattern Epica sees constantly across clinical software work: regulatory clarity always arrives after the engineering decisions it affects have already shipped. Teams that bring in a medical software development partner — or a dedicated mobile app development team like YuSMP Group — before the first sprint tend to bake in the versioning, audit logging, and content-review workflow a labeling determination like this one assumes exists. Retrofitting it after a drug is already on market is a much more expensive conversation.
Two buckets: device-connected vs. standalone
The guidance splits companion software into two categories. Apps connected to a drug-device combination — think an asthma inhaler that logs doses over Bluetooth — should generally be described on the drug's official label, because the software plays a critical role in how the medicine is actually used. Standalone tools that aren't tied to a physical device, like a symptom tracker or a medication reminder app, only need to be in the prescribing information when a sponsor can show the tool is essential to safe use or delivers a meaningful clinical benefit.
Why the decision tree matters
A yes/no decision tree sounds like a small addition, but it changes how product and regulatory teams work together. Instead of a case-by-case argument with FDA reviewers over whether a given feature needs label language, sponsors now have a documented path to the answer before a submission is drafted — which pushes the question earlier into product design, not later into legal review.
Building a companion app that needs to survive a labeling review? Talk to Epica →
More from the blog.
Designing HIPAA-aware software from day one
Compliance bolted on at the end is expensive and fragile. Here's how we design privacy and auditability into the foundation.
Choosing an EHR integration approach
HL7v2, FHIR, or a vendor API — how to pick the integration path that won't need a rewrite in a year.
Shipping a patient-facing app?
From regulatory-ready architecture to a shipped clinical UI, we build software that holds up under FDA review.