{"id":2266,"date":"2026-10-21T19:09:12","date_gmt":"2026-10-21T19:09:12","guid":{"rendered":"https:\/\/chatscopeai.com\/news\/fda-finalizes-labeling-guidance-for-prescription-drug-apps-and\/"},"modified":"2026-10-21T19:09:13","modified_gmt":"2026-10-21T19:09:13","slug":"fda-finalizes-labeling-guidance-for-prescription-drug-apps-and","status":"publish","type":"post","link":"https:\/\/chatscopeai.com\/news\/fda-finalizes-labeling-guidance-for-prescription-drug-apps-and\/","title":{"rendered":"FDA Finalizes Labeling Guidance for Prescription Drug Apps and Software"},"content":{"rendered":"\n<p class=\"wp-block-paragraph hsn-lede\">The FDA finalized guidance treating content from drug companies&#8217; apps as drug labeling, replacing its 2023 draft on Oct. 21, 2026.<\/p>\n<p class=\"wp-block-paragraph\"><strong>The US Food and Drug Administration (FDA) has finalized guidance on apps and software that drug companies give out with prescription medicines. It treats what the software shows patients and doctors as drug labeling, and comments stay open at any time.<\/strong><\/p>\n<p class=\"wp-block-paragraph\">The FDA announced the final guidance in the Federal Register on <strong>Oct. 21, 2026<\/strong>, ending a process that began with a draft on Sept. 19, 2023<sup class=\"hsn-cite\"><a href=\"#hsn-ref-1\" id=\"hsn-cite-1\">1<\/a><\/sup>. It covers drug companies, called sponsors, that distribute software for use with prescription drugs or drug-led drug-device combination products<sup class=\"hsn-cite\"><a href=\"#hsn-ref-1\">1<\/a><\/sup>. The guidance is nonbinding, and the public may comment on it at any time under docket FDA-2023-D-2482<sup class=\"hsn-cite\"><a href=\"#hsn-ref-2\" id=\"hsn-cite-2\">2<\/a><\/sup>.<\/p>\n<div class=\"hsn-table\">\n<div class=\"pcrstb-wrap\"><table>\n<thead><tr><th>At a glance<\/th><th>Details<\/th><\/tr><\/thead>\n<tbody>\n<tr><td>What was published<\/td><td>Final guidance for industry, &quot;Regulatory Considerations for Prescription Drug Use-Related Software&quot;<\/td><\/tr>\n<tr><td>Published on<\/td><td>21 October 2026 (posted by FDA on 20 October 2026)<\/td><\/tr>\n<tr><td>Who must comply<\/td><td>Drug sponsors that distribute software for use with their prescription drugs<\/td><\/tr>\n<tr><td>Feedback deadline \/ Effective date<\/td><td>Comments accepted at any time. No fixed compliance date is set<\/td><\/tr>\n<tr><td>Final rules \/ Next milestone<\/td><td>Guidance is final. It replaces the September 2023 draft<\/td><\/tr>\n<\/tbody>\n<\/table><\/div>\n<\/div>\n<h2 class=\"wp-block-heading\">What is drug use-related software, and why does it matter?<\/h2>\n<p class=\"wp-block-paragraph\">The guidance covers software that a drug sponsor, or a developer working for it, distributes<sup class=\"hsn-cite\"><a href=\"#hsn-ref-3\" id=\"hsn-cite-3\">3<\/a><\/sup>. The software must produce output that <strong>supplements, explains, or relates<\/strong> to one of the sponsor&#8217;s drugs<sup class=\"hsn-cite\"><a href=\"#hsn-ref-3\">3<\/a><\/sup>. This applies whether or not the software is also regulated as a medical device<sup class=\"hsn-cite\"><a href=\"#hsn-ref-1\">1<\/a><\/sup>.<\/p>\n<figure class=\"hsn-fig hsn-fig--solid hsn-fig--v1\" data-at=\"what-is-drug-use-related-software-and-why-does-it-matter\">\n  <div class=\"hsn-fig__table\">\n    <h4>What the guidance covers<\/h4>\n    <div class=\"pcrstb-wrap\"><table>\n      <thead>\n        <tr><th>Dimension<\/th><th>Provision<\/th><\/tr>\n      <\/thead>\n      <tbody>\n        <tr><th>Who it covers<\/th><td>Software distributed by or for a drug sponsor<\/td><\/tr>\n        <tr><th>What it covers<\/th><td>Output that supplements, explains or relates to the sponsor&#8217;s drugs<\/td><\/tr>\n        <tr><th>How output is treated<\/th><td>As a type of prescription drug labeling<\/td><\/tr>\n        <tr><th>Outside scope<\/th><td>Software not distributed by or for a sponsor<\/td><\/tr>\n      <\/tbody>\n    <\/table><\/div>\n  <\/div>\n<\/figure>\n<p class=\"wp-block-paragraph\">Output means any content the software shows an end user, such as a patient, caregiver or health care practitioner<sup class=\"hsn-cite\"><a href=\"#hsn-ref-1\">1<\/a><\/sup>. The FDA considers that output a <strong>type of prescription drug labeling<\/strong><sup class=\"hsn-cite\"><a href=\"#hsn-ref-1\">1<\/a><\/sup>. That brings app screens and messages under the same truthfulness rules that apply to printed drug information.<\/p>\n<p class=\"wp-block-paragraph\">The FDA lists possible uses such as tracking doses, giving individual dosing advice, predicting treatment response and managing side effects<sup class=\"hsn-cite\"><a href=\"#hsn-ref-3\">3<\/a><\/sup>. Software made by an outside developer, not distributed by or for a sponsor, falls outside the guidance<sup class=\"hsn-cite\"><a href=\"#hsn-ref-3\">3<\/a><\/sup>. Software whose content is purely about a disease, not a specific drug, is generally also outside it<sup class=\"hsn-cite\"><a href=\"#hsn-ref-3\">3<\/a><\/sup>.<\/p>\n<h2 class=\"wp-block-heading\">How the FDA sorts software output<\/h2>\n<p class=\"wp-block-paragraph\">The agency splits drug labeling into two groups<sup class=\"hsn-cite\"><a href=\"#hsn-ref-3\">3<\/a><\/sup>. <strong>FDA-required labeling<\/strong> is reviewed and approved as part of a drug&#8217;s marketing application<sup class=\"hsn-cite\"><a href=\"#hsn-ref-3\">3<\/a><\/sup>. Promotional labeling is generally everything else<sup class=\"hsn-cite\"><a href=\"#hsn-ref-3\">3<\/a><\/sup>.<\/p>\n<p class=\"wp-block-paragraph\">To decide which group an app&#8217;s output belongs in, the FDA will weigh three questions<sup class=\"hsn-cite\"><a href=\"#hsn-ref-3\">3<\/a><\/sup>.<\/p>\n<div class=\"hsn-table\">\n<div class=\"pcrstb-wrap\"><table>\n<thead><tr><th>Question the FDA asks<\/th><th>Why it matters<\/th><\/tr><\/thead>\n<tbody>\n<tr><td>Is the software essential to safe and effective drug use?<\/td><td>It may need describing in the prescribing information<sup class=\"hsn-cite\"><a href=\"#hsn-ref-3\">3<\/a><\/sup><\/td><\/tr>\n<tr><td>Does evidence show a meaningful improvement in a clinical outcome?<\/td><td>FDA decides this based on evidence the sponsor provides<sup class=\"hsn-cite\"><a href=\"#hsn-ref-3\">3<\/a><\/sup><\/td><\/tr>\n<tr><td>Does the software rely on data from a device?<\/td><td>This marks it as device-connected rather than standalone<sup class=\"hsn-cite\"><a href=\"#hsn-ref-3\">3<\/a><\/sup><\/td><\/tr>\n<\/tbody>\n<\/table><\/div>\n<\/div>\n<p class=\"wp-block-paragraph\">Device-connected functions use data sent from the device part of a combination product<sup class=\"hsn-cite\"><a href=\"#hsn-ref-3\">3<\/a><\/sup>. Standalone functions are all the rest, such as features that rely on data typed in by users<sup class=\"hsn-cite\"><a href=\"#hsn-ref-3\">3<\/a><\/sup>.<\/p>\n<h2 class=\"wp-block-heading\">What changed from the 2023 draft<\/h2>\n<p class=\"wp-block-paragraph\">The FDA says it considered public comments on the draft before finalizing<sup class=\"hsn-cite\"><a href=\"#hsn-ref-1\">1<\/a><\/sup>. The final version makes four main changes<sup class=\"hsn-cite\"><a href=\"#hsn-ref-1\">1<\/a><\/sup>.<\/p>\n<ul>\n<li>It clarifies how the rules apply to <strong>standalone software functions<\/strong><sup class=\"hsn-cite\"><a href=\"#hsn-ref-1\">1<\/a><\/sup>.<\/li>\n<li>It adds a decision tree to guide sponsors through labeling choices<sup class=\"hsn-cite\"><a href=\"#hsn-ref-1\">1<\/a><\/sup>.<\/li>\n<li>It gives example wording for the prescribing information for both device-connected and standalone software<sup class=\"hsn-cite\"><a href=\"#hsn-ref-1\">1<\/a><\/sup>.<\/li>\n<li>It recommends a statement in the prescribing information when device-connected software shows <strong>no meaningful clinical improvement<\/strong><sup class=\"hsn-cite\"><a href=\"#hsn-ref-1\">1<\/a><\/sup>.<\/li>\n<\/ul>\n<p class=\"wp-block-paragraph\">The prescribing information is the official drug summary for doctors. It must hold the essential scientific facts needed for safe and effective use<sup class=\"hsn-cite\"><a href=\"#hsn-ref-3\">3<\/a><\/sup>. It must also be accurate, up to date, and not promotional or misleading<sup class=\"hsn-cite\"><a href=\"#hsn-ref-3\">3<\/a><\/sup>.<\/p>\n<h2 class=\"wp-block-heading\">What changes for drug sponsors<\/h2>\n<p class=\"wp-block-paragraph\">The guidance explains how the prescribing information should describe software functions<sup class=\"hsn-cite\"><a href=\"#hsn-ref-3\">3<\/a><\/sup>. It also explains when and how sponsors should submit software output to the FDA for review<sup class=\"hsn-cite\"><a href=\"#hsn-ref-1\">1<\/a><\/sup>. Sponsors are encouraged to discuss planned software functions with the relevant FDA review division<sup class=\"hsn-cite\"><a href=\"#hsn-ref-3\">3<\/a><\/sup>.<\/p>\n<p class=\"wp-block-paragraph\">Promotional output carries its own duties. Promotional labeling must be truthful, balanced on benefits and risks, and reveal material facts<sup class=\"hsn-cite\"><a href=\"#hsn-ref-3\">3<\/a><\/sup>. Firms that send out promotional materials must also submit them to the FDA on <strong>Form FDA 2253<\/strong><sup class=\"hsn-cite\"><a href=\"#hsn-ref-3\">3<\/a><\/sup>.<\/p>\n<p class=\"wp-block-paragraph\">The guidance does not change device rules<sup class=\"hsn-cite\"><a href=\"#hsn-ref-3\">3<\/a><\/sup>. Some software functions may still meet the legal definition of a medical device and face device requirements<sup class=\"hsn-cite\"><a href=\"#hsn-ref-3\">3<\/a><\/sup>.<\/p>\n<h2 class=\"wp-block-heading\">Legal status and enforcement<\/h2>\n<p class=\"wp-block-paragraph\">FDA guidance documents do not create legally enforceable duties on their own<sup class=\"hsn-cite\"><a href=\"#hsn-ref-3\">3<\/a><\/sup>. Firms may use another approach if it meets the applicable laws and regulations<sup class=\"hsn-cite\"><a href=\"#hsn-ref-1\">1<\/a><\/sup>. The FDA found the action is neither a regulatory nor a deregulatory action under Executive Order 14192<sup class=\"hsn-cite\"><a href=\"#hsn-ref-1\">1<\/a><\/sup>.<\/p>\n<figure class=\"hsn-fig hsn-fig--solid hsn-fig--v1\" data-at=\"legal-status-and-enforcement\">\n  <div class=\"hsn-fig__axis\">\n    <h4>From draft to final<\/h4>\n    <div class=\"hsn-fig__ev\">\n      <span class=\"hsn-fig__evdate\">19 Sep 2023<\/span>\n      <span class=\"hsn-fig__evlab\">Draft guidance issued<\/span>\n    <\/div>\n    <div class=\"hsn-fig__ev\">\n      <span class=\"hsn-fig__evdate\">20 Oct 2026<\/span>\n      <span class=\"hsn-fig__evlab\">Final guidance posted<\/span>\n    <\/div>\n    <div class=\"hsn-fig__ev\">\n      <span class=\"hsn-fig__evdate\">21 Oct 2026<\/span>\n      <span class=\"hsn-fig__evlab\">Federal Register notice<\/span>\n    <\/div>\n  <\/div>\n<\/figure>\n<p class=\"wp-block-paragraph\">The underlying law still bites. A drug shipped across state lines with false or misleading labeling is <strong>misbranded<\/strong> under the Federal Food, Drug, and Cosmetic Act<sup class=\"hsn-cite\"><a href=\"#hsn-ref-3\">3<\/a><\/sup>. Because app output counts as labeling, that standard now clearly reaches software content.<\/p>\n<div class=\"hsn-table\">\n<div class=\"pcrstb-wrap\"><table>\n<thead><tr><th>Key date<\/th><th>What happens<\/th><\/tr><\/thead>\n<tbody>\n<tr><td>19 September 2023<\/td><td>FDA issues the draft guidance<sup class=\"hsn-cite\"><a href=\"#hsn-ref-1\">1<\/a><\/sup><\/td><\/tr>\n<tr><td>20 October 2026<\/td><td>FDA posts the final guidance<sup class=\"hsn-cite\"><a href=\"#hsn-ref-2\">2<\/a><\/sup><\/td><\/tr>\n<tr><td>21 October 2026<\/td><td>Federal Register notice published<sup class=\"hsn-cite\"><a href=\"#hsn-ref-1\">1<\/a><\/sup><\/td><\/tr>\n<\/tbody>\n<\/table><\/div>\n<\/div>\n<h2 class=\"wp-block-heading\">Key terms in plain words<\/h2>\n<div class=\"hsn-table\">\n<div class=\"pcrstb-wrap\"><table>\n<thead><tr><th>Term<\/th><th>Meaning<\/th><\/tr><\/thead>\n<tbody>\n<tr><td>Sponsor<\/td><td>A company that seeks or holds FDA approval for a drug<\/td><\/tr>\n<tr><td>End-user output<\/td><td>Any content an app shows a patient, caregiver or doctor<\/td><\/tr>\n<tr><td>Prescribing information<\/td><td>The official FDA-approved drug summary for health professionals<\/td><\/tr>\n<tr><td>Combination product<\/td><td>A product that contains both a drug and a device part<\/td><\/tr>\n<tr><td>Standalone software<\/td><td>Software features not fed by data from a device<\/td><\/tr>\n<tr><td>Misbranded<\/td><td>Sold with false or misleading labeling, which breaks federal law<\/td><\/tr>\n<\/tbody>\n<\/table><\/div>\n<\/div>\n<p class=\"wp-block-paragraph\">The guidance was announced on Oct. 21, 2026, and comments remain open at any time under docket FDA-2023-D-2482<sup class=\"hsn-cite\"><a href=\"#hsn-ref-2\">2<\/a><\/sup>.<\/p>\n<h2 class=\"wp-block-heading hsn-refs-title\">Sources<\/h2>\n<ol class=\"hsn-refs\">\n<li id=\"hsn-ref-1\"><a class=\"hsn-refs__back\" href=\"#hsn-cite-1\" aria-label=\"Back to reference 1 in the text\">\u21a9<\/a> <a href=\"https:\/\/www.federalregister.gov\/documents\/2026\/10\/21\/2026-21516\/regulatory-considerations-for-prescription-drug-use-related-software-guidance-for-industry\" rel=\"noopener\" target=\"_blank\">Federal Register\n       :: \n      Regulatory Considerations for Prescription Drug Use-Related Software; Guidance for Industry; Availability<\/a> <span class=\"hsn-refs__url\">https:\/\/www.federalregister.gov\/documents\/2026\/10\/21\/2026-21516\/regulatory-considerations-for-prescription-drug-use-related-software-guidance-for-industry<\/span><\/li>\n<li id=\"hsn-ref-2\"><a class=\"hsn-refs__back\" href=\"#hsn-cite-2\" aria-label=\"Back to reference 2 in the text\">\u21a9<\/a> <a href=\"https:\/\/www.fda.gov\/regulatory-information\/search-fda-guidance-documents\/regulatory-considerations-prescription-drug-use-related-software\" rel=\"noopener\" target=\"_blank\">Regulatory Considerations for Prescription Drug Use-Related Software | FDA<\/a> <span class=\"hsn-refs__url\">https:\/\/www.fda.gov\/regulatory-information\/search-fda-guidance-documents\/regulatory-considerations-prescription-drug-use-related-software<\/span><\/li>\n<li id=\"hsn-ref-3\"><a class=\"hsn-refs__back\" href=\"#hsn-cite-3\" aria-label=\"Back to reference 3 in the text\">\u21a9<\/a> <a href=\"https:\/\/www.fda.gov\/media\/172165\/download\" rel=\"noopener\" target=\"_blank\">Regulatory Considerations for Prescription Drug Use- Related Software<\/a> <span class=\"hsn-refs__url\">https:\/\/www.fda.gov\/media\/172165\/download<\/span><\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"<p>The FDA finalized guidance treating content from drug companies&#8217; apps as drug labeling, replacing its 2023 draft on Oct. 21, 2026.<\/p>\n","protected":false},"author":1,"featured_media":2264,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_lmt_disableupdate":"","_lmt_disable":"","_regnews_id":"35880","_hsn_citations":"[{\"n\":1,\"url\":\"https:\/\/www.federalregister.gov\/documents\/2026\/10\/21\/2026-21516\/regulatory-considerations-for-prescription-drug-use-related-software-guidance-for-industry\",\"label\":\"Federal Register\\n       :: \\n      Regulatory Considerations for Prescription Drug Use-Related Software; Guidance for Industry; Availability\"},{\"n\":2,\"url\":\"https:\/\/www.fda.gov\/regulatory-information\/search-fda-guidance-documents\/regulatory-considerations-prescription-drug-use-related-software\",\"label\":\"Regulatory Considerations for Prescription Drug Use-Related Software | FDA\"},{\"n\":3,\"url\":\"https:\/\/www.fda.gov\/media\/172165\/download\",\"label\":\"Regulatory Considerations for Prescription Drug Use- Related Software\"}]","_hsn_no_sources":"","_hsn_content_hash":"f8bdf8bc98c52dff605ed683fd8d86883caa329a:b9febab7499ffef4041378aab93ed3067451f1da","_yoast_wpseo_focuskw":"prescription drug software","footnotes":""},"categories":[58,40],"tags":[50],"class_list":["post-2266","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-americas","category-pharma-medical","tag-united-states-of-america"],"_links":{"self":[{"href":"https:\/\/chatscopeai.com\/news\/wp-json\/wp\/v2\/posts\/2266","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/chatscopeai.com\/news\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/chatscopeai.com\/news\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/chatscopeai.com\/news\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/chatscopeai.com\/news\/wp-json\/wp\/v2\/comments?post=2266"}],"version-history":[{"count":1,"href":"https:\/\/chatscopeai.com\/news\/wp-json\/wp\/v2\/posts\/2266\/revisions"}],"predecessor-version":[{"id":2267,"href":"https:\/\/chatscopeai.com\/news\/wp-json\/wp\/v2\/posts\/2266\/revisions\/2267"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/chatscopeai.com\/news\/wp-json\/wp\/v2\/media\/2264"}],"wp:attachment":[{"href":"https:\/\/chatscopeai.com\/news\/wp-json\/wp\/v2\/media?parent=2266"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/chatscopeai.com\/news\/wp-json\/wp\/v2\/categories?post=2266"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/chatscopeai.com\/news\/wp-json\/wp\/v2\/tags?post=2266"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}