SOURCE READING
Original and translation
The excerpt and translation use the primary source below. Further references inform SHIO’s analysis.
Primary source
- Original title
- FDA Issues Final Guidance on Prescription Drug Apps and Software
- Original author / institution
- U.S. Food and Drug Administration (FDA)
- Source language
- English
- Original publication date
A five-word excerpt from FDA’s October 20, 2026 release concerns drug-labeling categories. Chinese and Japanese translations are by SHIO; independent analysis follows separately.
Basis for use：FDA-authored text; public domain unless otherwise noted
This edition uses the source language, so the original appears once.
FDA-required labeling versus promotional labelingSHIO analysis
SHIO analysis: Keep sources, conditions and update responsibilities together
The following is SHIO’s independent judgment and discussion of methods. It is separate from the source text and its translation.
SHIO reading note
On October 20, 2026, FDA issued final guidance on drug labeling for certain software outputs distributed by or for drug sponsors, and descriptions in prescribing information. It does not cover every health app; its nonbinding recommendations leave applicable legal requirements intact. SHIO considers how a screen’s medication information can remain connected to its basis and an owner.
The central idea
SHIO proposes including sources, conditions of use and update responsibilities in the same content-design process. Clear wording is a starting point. A team also needs to explain when information applies, what a missing record means, and who takes responsibility for the next change.
Start with the person and the task
For a medication information service, SHIO would begin by asking who will read each item and what they need to do. A patient reviewing a record, a caregiver interpreting a notification and a professional explaining a document need different levels of detail. Organize content around those tasks, record its supporting source and conditions, and involve people responsible for medical and regulatory judgments. Design should communicate those judgments accurately.
Then distinguish explanations, messages that change with a situation, and records entered by users. Is a reminder restating an agreed plan, or suggesting a different action based on new information? Those messages need different support and responsibilities. Readers should understand what kind of information they are seeing and where it applies. Brighter colors and shorter sentences cannot resolve a difference in meaning.
Give missing information and delays a clear expression
SHIO suggests examining ordinary situations that are easily overlooked: a device has not sent data, a connection has failed, or an older record is still awaiting synchronization. Rehearse these situations with fictional information. Look for wording that turns “not received” into “did not happen,” or makes an earlier record appear newly updated. Timing, source and missing information should jointly shape the message.
The purpose is to identify misunderstandings created by the presentation. Ask intended readers to explain a screen in their own words, then compare their interpretation with the conditions the team meant to convey. One observation describes how particular people understood and used a service in that setting. A claim about better medication use or health outcomes needs research suited to that claim. Understanding and clinical benefit need separate assessment.
Connect this revision to the next update
When a source changes, SHIO would identify every screen, notification and language edition that relies on it, then assign the necessary decisions and their owners. Keep the relevant dates and supporting material with each version. A handover should explain which statements changed and why. Medical and regulatory review belongs within this process, where it can shape the content.
Chinese, Japanese and English editions should retain the same people, conditions and timing. Removing a qualifying word to make a sentence smoother can create different promises across languages. Compare the editions using the same situations, then find a natural expression in each language. For SHIO, a dependable information service helps today’s reader understand and gives tomorrow’s owner a workable basis for keeping it useful.
A question for practice
Design the source, conditions and responsibility alongside the message. A short piece of screen text needs a process that someone can continue to own.
Research limits: findings depend on the study population and methods and do not establish an individual treatment benefit. This essay examines research and does not provide diagnosis or treatment advice.
REFERENCES & EDITORIAL NOTE
Sources & further reading
Source excerpts, translations, and SHIO’s independent analysis are presented separately. The resources below offer additional context and further reading.
U.S. Food and Drug Administration (FDA) · Primary source
FDA Issues Final Guidance on Prescription Drug Apps and Software
Original source date：Accessed：FDA-authored website text is public domain unless otherwise noted. A five-word fragment and SHIO translations are reproduced with attribution; the surrounding analysis is original. No images or full text are reproduced; no FDA endorsement is implied.
U.S. Food and Drug Administration (FDA)
Regulatory Considerations for Prescription Drug Use-Related Software
Original source date：Accessed：FDA-authored guidance under the website’s default public-domain policy unless otherwise noted. Used for a brief scope and status summary; no figures, appendices or full guidance are reproduced. The final PDF is dated October 2026; FDA’s guidance inventory identifies October 20 as its issue date.
U.S. Food and Drug Administration (FDA)
Newly Added Guidance Documents
Original source date：No publication date providedAccessed：Linked to identify the guidance’s issue date and final status. The table itself is not reproduced. Its current entries are not presented as the inventory page’s first-publication date.