United States: FDA Seeks Comments On The Regulatory Framework For Prescription Drug-Use-Related Software

Virtually all pharmaceutical companies have been exploring the use of various software tools in both drug development and in conjunction with marketed products. In the future, such software will be a routine part of drug treatment, providing a better physician and patient understanding of the course of treatment, supporting adherence and proper dosing, and many other applications. While the Food and Drug Administration (FDA or Agency) must ensure that such software is reliable, does not misbrand or adulterate the drug product, and is otherwise consistent with statutory requirements, all stakeholders have an interest in ensuring that the potentially enormous benefits of these tools are achieved.

To that end, on November 20, 2018, FDA published a Federal Register notice requesting comments on a proposed framework for the regulation of prescription drug-use-related software, which the FDA defines broadly to include any software disseminated by drug sponsors to be used with one or more of the sponsor's prescription drugs.1 The proposed framework was issued for discussion purposes only—it is not intended as draft guidance or a proposed rule. Rather, the goal is to seek early input from stakeholders prior to development of a draft guidance. Comments on the framework are due by January 22, 2019.

The range of prescription drug-use-related software varies widely, including both simple and complex tools designed for use by patients, providers, and in conjunction with medical devices, including software designed to, among other applications:

  • record and track dosages, provide reminders to take a drug, and measure a patient's physical activity or other attributes while using a specific drug;
  • enable a healthcare provider to enter dosing instructions for a specific drug that a patient may review and retrieve; and
  • interface with a device that is embedded in an oral tablet of a specific drug to automatically record when the tablet has been ingested by the patient.

Notably, the framework is not intended to focus on the software itself, but rather "on the output of such software that is presented to the end user."

Highlights of the framework include:

  • FDA would regulate drug-use-related software "output" as drug labeling. Under the proposed framework, software "output" would be regulated as drug labeling. As such, the framework distinguishes output that would be classified as "FDA-required labeling," which requires approval prior to dissemination, from output that is characterized as "promotional labeling." Promotional labeling must be submitted to FDA at the time of initial dissemination of the promotional materials (with the exception of accelerated approval drugs subject to special provisions on submission prior to use). Under some circumstances, however, the framework recommends that promotional software output be submitted for pre-dissemination review under the Agency's existing voluntary process for requesting advisory comments where it may increase the potential for harm to patients compared to the use of the drug without such output.
  • The framework does not address precisely when prescription drug-use-related software is considered a device but—not surprisingly—contemplates overlap between software outputs and medical device regulatory requirements. The focus of the proposed framework is not on when prescription drug-use-related software is considered a device, and it does not propose to alter the regulatory framework for such devices. However, FDA anticipates overlap between this proposed framework regulating software output and device regulation, for instance, in the case of combination products.
  • The framework distinguishes between software disseminated by drug sponsors versus independent third-parties. The proposed framework is only intended to apply to software disseminated by, or on behalf of, a drug sponsor for the use with one or more of the sponsor's prescription drugs. Other software disseminated by third parties unaffiliated with a drug sponsor would not fall under the purview of this framework, even if the intention of the software is for it to be used in conjunction with a particular prescription drug and the third-party software meets the definition of a device. Such software would be regulated under existing device authorities, to the extent applicable. However, where a drug sponsor licenses software originally developed or disseminated by a third party and then disseminates the software for use in conjunction with the sponsor's prescription drug, the software would then fall under the purview of the proposed framework.

A more detailed review is found below.

I. Prescription Drug-Use-Related Software Output as "Drug Labeling"

A major goal of the framework is to ensure that sponsors' digital communications about their prescription drugs are consistent with applicable prescription drug labeling requirements, while preserving flexibility in the development and use of software that will help patients. The framework advances a risk-based approach designed to regulate the "output" of prescription drug-use-related software. "Output" includes all material presented to the end user (i.e., a patient, caregiver, or healthcare professional), such as screen displays created by the software, whether static or dynamic, as well as sounds or audio messages. For instance, output might include a screen display that:

  • permits patients to enter a record of their ingestion of a drug and view records of ingestion over time, as well as track physical activities or symptoms;
  • reminds patients to take medication at appropriate times;
  • shows dosing instructions that a patient may retrieve through an app; or
  • provides a risk calculator to assist healthcare providers in deciding when to prescribe medication and how to calculate the appropriate dose.

Under the proposed framework, prescription drug-use-related software "output" would be regulated as drug labeling. Because this software output accompanies a specific prescription drug—often by explaining how to use the drug or by supplementing the use of the drug—the FDA framework recognizes it as "drug labeling" within the definition found in the Federal Food, Drug, and Cosmetic Act.2

Under current authorities, the FDA recognizes two broad categories of labeling for drugs:

  • FDA-required labeling: Information essential for a provider to make an informed decision about the risks and benefits of prescribing the drug for a patient as well as information needed to safely and effectively use the drug. This type of labeling must be reviewed and approved by FDA prior to dissemination as a part of a new drug application.
  • Promotional labeling: Any other information devised for promotion or advertisement of the product or that is otherwise descriptive of a drug. Promotional labeling is usually not approved by FDA in advance of dissemination but is submitted to the FDA at the time of initial dissemination or publication of the promotional labeling.

Under the proposed framework, whether software output will be considered FDA-required labeling or instead constitutes promotional labeling depends on how the output is used with the prescription drug. FDA anticipates that most forms of prescription drug-use-related software output would be considered promotional labeling and thus would only be required to be submitted at the time of initial dissemination pursuant to existing regulations.

A. FDA-Required Labeling

The FDA describes two situations where it anticipates prescription drug-use-related software output may be included in FDA-required labeling:

  • A drug sponsor demonstrates to FDA that there is substantial evidence of an effect on a clinically meaningful outcome as a result of the use of prescription drug-use-related software and chooses to include this information in the drug application. If the use of the software with the drug demonstrably indicates improved clinical outcomes compared to the use of the drug alone without the software, such evidence would be sufficient to support a labeling claim.
  • A drug-led, drug-device combination product where prescription drug-use-related software is either (1) a device constituent part or (2) an element of a device constituent part, and such software provides a function or information that is essential to one or more intended uses of the combination product.3

In these instances, the output of prescription-drug-use-related software would be regulated as FDA-required labeling and would be reviewed and approved by FDA as a part of the new drug application.

B. Promotional Labeling

Under the proposed framework, output not included in the FDA-required labeling would be considered promotional labeling. As such, it would be submitted to FDA by drug sponsors in the same way that drug sponsors currently submit promotional materials.4 Submissions would include screenshots or other appropriate representations of how the user will experience software output. Examples of promotional labeling output include content that:

  • reminds providers of interventions or tests, consistent with FDA-required labeling, needed before prescribing a drug product;
  • provides patients with information about the prescribed drug also found on the FDA-required labeling, like instructions for use;
  • offers patients simple tools to track their health information related to a condition or drug, enter a dosing regimen, and remind the patient of when the next dose is appropriate; and
  • permits prescribers to provide dosing instructions to patients that are consistent with FDA-required labeling

However, the proposed framework also addresses situations in which prescription drug-use-related software output has the potential to be inconsistent with FDA-required labeling and potentially increases the risk of harm to patient health compared to the use of the drug alone without such output. Specifically, FDA cites as higher risk software that provides recommendations directing patients to make decisions about their drug or disease that would normally be made in consultation with healthcare providers. FDA notes that in certain cases, such software might be considered a device if it provides recommendations to patients to prevent, diagnose, or treat a disease or condition. In these circumstances, the proposed framework recommends that sponsors avail themselves of the opportunity for pre-dissemination review of such prescription drug-use-related software output through the existing voluntary advisory comment process for promotional materials.5 Examples of these instances include software output that instructs patients on when to adjust their dose without first consulting a healthcare provider, or and processes symptom-related information and provides recommendations on when the patient should or should not contact a healthcare provider.

Software and medical technology developers should take note of this proposal, as there is no analog to the routine FDA post-marketing prescription drug labeling submission requirement in medical device regulations. Companies should also consider the extent to which the contours of FDA's recent enforcement discretion policy for general wellness technologies and the availability of statutory exemptions for clinical decision support tools are affected by the approach set forth in the proposed framework, particularly when they "marry" those technologies with prescription drug marketing or disease awareness education programs. For example, software outputs which historically have not been subjected to FDA post-marketing labeling review requirements (either due to exemptions from FDA's premarket notification or approval process, or due to FDA's enforcement discretion policy for wellness products) could now potentially be reviewed under FDA's standards for claim substantiation, fair balance, and consistency with approved indication. Further, while the proposed framework is not intended to disrupt current FDA regulatory approaches to the underlying software, a question about the substantiation for a software output "claim" with the labeling of the referenced prescription drug product could have the effect of calling into question the validation of the software for its intended uses.

II. Prescription Drug-Use-Related Software as a Medical Device

FDA does not intend for the proposed framework to alter the current regulatory landscape for medical devices. For example, if adopted, the framework would not impact the regulation of stand-alone software functions that do not accompany a prescription drug. However, FDA recognizes points of overlap between the framework and existing device regulations. For example, prescription drug-use-related software that meets the definition of a device based on its function would be subject to regulation of its device functionality, as well as regulation of its output under the framework for drug labeling. According to FDA, however, the proposed framework takes into account existing Agency policy to ensure an efficient and coordinated review. For instance, if a prescription drug-use-related software is cleared or approved as a device, and is not a constituent of an approved drug-device combination product, sponsors would only need to submit software output for FDA review once at the time of dissemination through the promotional labeling review process. Because such software was reviewed as a device by Center for Devices and Radiological Health, FDA would not expect that the use of that software would result in an increased potential for harm to patients.

If the prescription drug-use-related software meets the device definition and, according to its labeling, is intended for use with an approved individually-specified drug, where both the software and drug are required to achieve the intended use, indication, or effect, then the software and drug together may constitute a "cross-labeled" combination product. 21 C.F.R. § 3.2(e)(3) and (4)). For regulated companies that do not normally develop or commercialize drug-device combination products, this potential distinction is critical, as the investment in modified drug-device combination product quality and adverse event management systems—particularly post-marketing internal company systems intended to identify device failures which could result in significant patient harm—can be significant and require different systems and expertise than "conventional" pharmacovigilance requires.

* * * * *

FDA's new docket on the regulatory framework for prescription drug-use-related software presents an important opportunity to shape the future regulation of software that is increasingly an essential part of drug development, approval, and labeling. Companies planning to develop and/or utilize such software should carefully consider FDA's notice in their software and drug development activities, and consider commenting on the non-binding framework. As noted, comments are currently due on January 22, 2019. After considering comments submitted to the docket, FDA expects to issue a draft guidance that will convey FDA's proposed approach and recommendations.

*Ira Stup contributed to this Advisory. He is a University of Michigan Law School graduate employed at Arnold & Porter Kaye Scholer LLP and is not admitted to the District of Columbia Bar.

Footnotes

1. 83 Fed. Reg. 58574 (Nov. 20, 2018).

2. See 21 U.S.C. § 321(m).

3. As an example, FDA cites the approval of an ingestible event marker (IEM) designed to communicate a time- stamped confirmation of IEM device ingestion via volume conduction communication, also known as intrabody communication, with an external patch. See Evaluation of Automatice Class III Designation (De Novo) for Proteus Personal Monitor Including Ingestion Event Marker. Software can be used to interact with the external patch to organize and display the information about ingestion for a patient, provider, or both. The software program that communicates with the patch, which gathers the information from the IEM, is essential to allow review of the data collected by the IEM about ingestion. The information about that function of the software was included in the FDA-required drug labeling because that function is essential for the combination product to achieve one of its intended use—tracking ingestion of the drug.

4. Under FDA's postmarket reporting regulations, drug sponsors must submit FDA "labeling or advertising devised for promotion" of a drug using Form FDA 2253 ("Transmittal of Advertisements and Promotional Labeling for Drugs for Human Use") and a copy of the drugs professional labeling. See 21 C.F.R. § 314.81(b)(3)(i); § 601.12(f)(4). Special pre-submission rules apply to certain accelerated approval products. 21 C.F.R. § 314.550; § 601.45.

5. See 21 CFR 202.1(j)(4).

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on Mondaq.com.

Click to Login as an existing user or Register so you can print this article.

Authors
Similar Articles
Relevancy Powered by MondaqAI
 
In association with
Related Topics
 
Similar Articles
Relevancy Powered by MondaqAI
Related Articles
 
Related Video
Up-coming Events Search
Tools
Print
Font Size:
Translation
Channels
Mondaq on Twitter
 
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
 
Email Address
Company Name
Password
Confirm Password
Position
Mondaq Topics -- Select your Interests
 Accounting
 Anti-trust
 Commercial
 Compliance
 Consumer
 Criminal
 Employment
 Energy
 Environment
 Family
 Finance
 Government
 Healthcare
 Immigration
 Insolvency
 Insurance
 International
 IP
 Law Performance
 Law Practice
 Litigation
 Media & IT
 Privacy
 Real Estate
 Strategy
 Tax
 Technology
 Transport
 Wealth Mgt
Regions
Africa
Asia
Asia Pacific
Australasia
Canada
Caribbean
Europe
European Union
Latin America
Middle East
U.K.
United States
Worldwide Updates
Registration (you must scroll down to set your data preferences)

Mondaq Ltd requires you to register and provide information that personally identifies you, including your content preferences, for three primary purposes (full details of Mondaq’s use of your personal data can be found in our Privacy and Cookies Notice):

  • To allow you to personalize the Mondaq websites you are visiting to show content ("Content") relevant to your interests.
  • To enable features such as password reminder, news alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our content providers ("Contributors") who contribute Content for free for your use.

Mondaq hopes that our registered users will support us in maintaining our free to view business model by consenting to our use of your personal data as described below.

Mondaq has a "free to view" business model. Our services are paid for by Contributors in exchange for Mondaq providing them with access to information about who accesses their content. Once personal data is transferred to our Contributors they become a data controller of this personal data. They use it to measure the response that their articles are receiving, as a form of market research. They may also use it to provide Mondaq users with information about their products and services.

Details of each Contributor to which your personal data will be transferred is clearly stated within the Content that you access. For full details of how this Contributor will use your personal data, you should review the Contributor’s own Privacy Notice.

Please indicate your preference below:

Yes, I am happy to support Mondaq in maintaining its free to view business model by agreeing to allow Mondaq to share my personal data with Contributors whose Content I access
No, I do not want Mondaq to share my personal data with Contributors

Also please let us know whether you are happy to receive communications promoting products and services offered by Mondaq:

Yes, I am happy to received promotional communications from Mondaq
No, please do not send me promotional communications from Mondaq
Terms & Conditions

Mondaq.com (the Website) is owned and managed by Mondaq Ltd (Mondaq). Mondaq grants you a non-exclusive, revocable licence to access the Website and associated services, such as the Mondaq News Alerts (Services), subject to and in consideration of your compliance with the following terms and conditions of use (Terms). Your use of the Website and/or Services constitutes your agreement to the Terms. Mondaq may terminate your use of the Website and Services if you are in breach of these Terms or if Mondaq decides to terminate the licence granted hereunder for any reason whatsoever.

Use of www.mondaq.com

To Use Mondaq.com you must be: eighteen (18) years old or over; legally capable of entering into binding contracts; and not in any way prohibited by the applicable law to enter into these Terms in the jurisdiction which you are currently located.

You may use the Website as an unregistered user, however, you are required to register as a user if you wish to read the full text of the Content or to receive the Services.

You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these Terms or with the prior written consent of Mondaq. You may not use electronic or other means to extract details or information from the Content. Nor shall you extract information about users or Contributors in order to offer them any services or products.

In your use of the Website and/or Services you shall: comply with all applicable laws, regulations, directives and legislations which apply to your Use of the Website and/or Services in whatever country you are physically located including without limitation any and all consumer law, export control laws and regulations; provide to us true, correct and accurate information and promptly inform us in the event that any information that you have provided to us changes or becomes inaccurate; notify Mondaq immediately of any circumstances where you have reason to believe that any Intellectual Property Rights or any other rights of any third party may have been infringed; co-operate with reasonable security or other checks or requests for information made by Mondaq from time to time; and at all times be fully liable for the breach of any of these Terms by a third party using your login details to access the Website and/or Services

however, you shall not: do anything likely to impair, interfere with or damage or cause harm or distress to any persons, or the network; do anything that will infringe any Intellectual Property Rights or other rights of Mondaq or any third party; or use the Website, Services and/or Content otherwise than in accordance with these Terms; use any trade marks or service marks of Mondaq or the Contributors, or do anything which may be seen to take unfair advantage of the reputation and goodwill of Mondaq or the Contributors, or the Website, Services and/or Content.

Mondaq reserves the right, in its sole discretion, to take any action that it deems necessary and appropriate in the event it considers that there is a breach or threatened breach of the Terms.

Mondaq’s Rights and Obligations

Unless otherwise expressly set out to the contrary, nothing in these Terms shall serve to transfer from Mondaq to you, any Intellectual Property Rights owned by and/or licensed to Mondaq and all rights, title and interest in and to such Intellectual Property Rights will remain exclusively with Mondaq and/or its licensors.

Mondaq shall use its reasonable endeavours to make the Website and Services available to you at all times, but we cannot guarantee an uninterrupted and fault free service.

Mondaq reserves the right to make changes to the services and/or the Website or part thereof, from time to time, and we may add, remove, modify and/or vary any elements of features and functionalities of the Website or the services.

Mondaq also reserves the right from time to time to monitor your Use of the Website and/or services.

Disclaimer

The Content is general information only. It is not intended to constitute legal advice or seek to be the complete and comprehensive statement of the law, nor is it intended to address your specific requirements or provide advice on which reliance should be placed. Mondaq and/or its Contributors and other suppliers make no representations about the suitability of the information contained in the Content for any purpose. All Content provided "as is" without warranty of any kind. Mondaq and/or its Contributors and other suppliers hereby exclude and disclaim all representations, warranties or guarantees with regard to the Content, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. To the maximum extent permitted by law, Mondaq expressly excludes all representations, warranties, obligations, and liabilities arising out of or in connection with all Content. In no event shall Mondaq and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use of the Content or performance of Mondaq’s Services.

General

Mondaq may alter or amend these Terms by amending them on the Website. By continuing to Use the Services and/or the Website after such amendment, you will be deemed to have accepted any amendment to these Terms.

These Terms shall be governed by and construed in accordance with the laws of England and Wales and you irrevocably submit to the exclusive jurisdiction of the courts of England and Wales to settle any dispute which may arise out of or in connection with these Terms. If you live outside the United Kingdom, English law shall apply only to the extent that English law shall not deprive you of any legal protection accorded in accordance with the law of the place where you are habitually resident ("Local Law"). In the event English law deprives you of any legal protection which is accorded to you under Local Law, then these terms shall be governed by Local Law and any dispute or claim arising out of or in connection with these Terms shall be subject to the non-exclusive jurisdiction of the courts where you are habitually resident.

You may print and keep a copy of these Terms, which form the entire agreement between you and Mondaq and supersede any other communications or advertising in respect of the Service and/or the Website.

No delay in exercising or non-exercise by you and/or Mondaq of any of its rights under or in connection with these Terms shall operate as a waiver or release of each of your or Mondaq’s right. Rather, any such waiver or release must be specifically granted in writing signed by the party granting it.

If any part of these Terms is held unenforceable, that part shall be enforced to the maximum extent permissible so as to give effect to the intent of the parties, and the Terms shall continue in full force and effect.

Mondaq shall not incur any liability to you on account of any loss or damage resulting from any delay or failure to perform all or any part of these Terms if such delay or failure is caused, in whole or in part, by events, occurrences, or causes beyond the control of Mondaq. Such events, occurrences or causes will include, without limitation, acts of God, strikes, lockouts, server and network failure, riots, acts of war, earthquakes, fire and explosions.

By clicking Register you state you have read and agree to our Terms and Conditions