United States: The Latest FDA Move To Limit Digital Health Software Regs

On Dec. 8, 2017, the U.S. Food and Drug Administration issued two draft guidance documents that describe types of software functions that the FDA will not regulate, including the FDA's long-awaited policy on clinical decision support software. The FDA published these documents in response to the 21st Century Cures Act, in which Congress removed certain low-risk digital health software from the FDA's jurisdiction. In addition, as part of its broader Digital Health Innovation Action Plan, the FDA announced that it was adopting as final guidance a document developed by the International Medical Device Regulators Forum (IMDRF) on clinical evaluation of software as a medical device. The FDA also announced a Jan. 30, 2018, public workshop on the progress of the Software Precertification (Pre-Cert) Pilot Program.

These developments continue to build on the policies the FDA has been developing in recent years to clarify the applicability of FDA regulatory requirements to digital health technologies. While the FDA's policy structure in this area remains a work in progress, these documents continue the general trend toward relatively limited, risk-based FDA regulation of digital health software.

Draft Guidance on Clinical and Patient Decision Support Software

As discussed in several previous Ropes & Gray articles (summarizing the 21st Century Cures Act, the general wellness guidance, and the Digital Health Innovation Action Plan), device manufacturers have long anticipated FDA guidance on clinical decision support (CDS) software. The FDA's new draft guidance, "Clinical and Patient Decision Support Software," describes the FDA's proposed views on the regulation of CDS as well as a related category of software that the FDA defines as patient decision support (PDS) software.

Section 3060 of the 21st Century Cures Act (Section 520(o) of the Federal Food, Drug, and Cosmetic Act) removes certain software functions from the definition of "device." One category under this provision is a software function that:

  1. Is not intended to acquire, process or analyze a medical image or a signal from an in vitro diagnostic device or a pattern or signal from a signal acquisition system;
  2. Is intended to display, analyze, or print medical information about a patient or other medical information, like clinical practice guidelines;
  3. Is intended to support or provide recommendations to a health care professional about prevention, diagnosis, or treatment of a disease or condition; and
  4. Is intended to enable health care professionals to independently review the basis for the software's recommendations so professionals do not primarily rely on the recommendations when making a clinical diagnosis or treatment decision.

In the draft guidance, the FDA proposes to define CDS as software functions that meet the first, second and third criteria listed above. The FDA states that such a CDS function, in order not to be considered a "device," would also have to meet the fourth criterion. The FDA also states that it would continue to regulate as devices software that is Class III (i.e., software that is intended for a use in supporting or sustaining human life or for a use which is of substantial importance in preventing impairment of human health, or that presents a potential unreasonable risk of illness or injury).

The FDA provides examples of CDS that meet, and do not meet, all four of the agency's proposed criteria. Software functions that the FDA would consider to be excluded from FDA regulation are:

  1. Software that makes recommendations by matching patient information with reference information that is commonly used in clinical practice. Within this category, the FDA includes (1) software that identifies drug-drug interaction alerts based on FDA-approved drug labeling and patient-specific information, and (2) software that uses a patient's diagnosis to provide a health care provider with current practice treatment guidelines for common diseases and provides the source of those guidelines;
  2. Software that suggests an intervention or test using clinical guidelines in response to a physician's order, such as suggesting that a health care professional order liver function tests before prescribing a statin; and
  3. Software that uses rule-based tools that compare patient-specific signs, symptoms or results with available practice guidelines to recommend condition-specific diagnostic tests, investigations or therapy.

In contrast, the FDA intends to focus its regulatory oversight on two types of CDS-related software.

First, the FDA will regulate software intended to generate treatment and diagnostic recommendations on which the health care professional will rely primarily in making clinical decisions or determining therapy plans. To be excluded from the definition of "device," the CDS function must be intended to enable the health care professional to independently review the basis for the recommendations presented by the software. In the draft guidance, the FDA states that, to meet this criterion, such software must clearly explain (1) the purpose or intended use of the software function; (2) the intended user; (3) the inputs used to generate the recommendation; and (4) the rationale or support for the recommendation. The FDA believes that a health care professional would be unable to evaluate the basis of a software recommendation independently if it were based on nonpublic or proprietary information. Thus, under the draft guidance, a software function would fail to qualify as nondevice CDS if it operates via a nontransparent algorithm. This aspect of the draft guidance is likely to generate public comment, because it does not take into account the degree of risk posed by the product. However, it is possible that the FDA might choose to exercise enforcement discretion with respect to such software if it falls within another low-risk category set forth in the second draft guidance, described below.

Second, the FDA intends to regulate software designed to acquire, process or analyze a medical image, a signal from an in vitro diagnostic (IVD) device that can detect diseases, or a pattern or signal from a signal acquisition system (a machine that receives, as inputs, signals from sensors on the body). The FDA has historically regulated technologies that analyze the information from signal acquisition systems, such as IVD tests and technologies that measure and assess electrical activity in the body (e.g., electrocardiograph and electroencephalograph machines) as well as medical imaging technologies. Also included within this category are algorithms that process physiological data to generate new data points or that analyze and interpret genomic data to determine a patient's risk for a particular disease.

The following are examples of software functions that the FDA intends to regulate:

  1. Software that customizes the patient-specific surgical plan and instrumentation based on analysis of imaging and device characteristics for orthopedic implant procedures;
  2. Software that analyzes multiple physiological signals (e.g., sweat, heart rate, breathing) to monitor whether a person is having a heart attack;
  3. Software that analyzes near-infrared camera signals of a patient intended for use in determining and/or diagnosing brain hematoma; and
  4. Software that analyzes multiple physiological signals, such as heart rate and eye movement, to monitor whether an individual is having a heart attack or narcolepsy episode, and software that analyzes images of body fluid preparations or digital slides to perform cell counts and morphology reviews.

Moreover, the draft guidance addresses the agency's enforcement discretion policy for low-risk PDS software that is intended for patients or caregivers who are not health care professionals. Specifically, the FDA will exercise enforcement discretion and not enforce compliance with applicable regulatory requirements if the PDS meets the same four criteria that CDS must meet as outlined in Section 520(o)(1)(E) of the FDCA, thus generally mirroring the policy the FDA is adopting for CDS, except that the fourth criterion would be modified in the PDS context to require transparency of the basis for the software recommendations to laypersons (patients) rather than health care professionals.

Other Changes to FDA's Existing Software Policies

The 21st Century Cures Act also excludes from the definition of "device" four other categories of low-risk software functions. These statutory changes affect several existing FDA policies and guidance documents. As a consequence, the draft guidance on "Changes to Existing Medical Software Policies Resulting from Section 3060 of the 21st Century Cures Act," describes the changes the FDA intends to make to several previously published guidance documents, including the FDA's guidances on "Mobile Medical Applications," "General Wellness: Policy for Low Risk Devices," and "Medical Device Data Systems, Medical Image Storage Devices, and Medical Image Communications Devices." As an overarching concept, the FDA notes that Section 3060 of the 21st Century Cures Act creates a function-specific standard of software functions that do not meet the definition of "device," independent of the platform on which the software runs.

The draft guidance describes the four types of software functions that the FDA is excluding from the scope of its regulation:

  1. Software functions intended for administrative support of a health care facility: The FDA has historically not regulated most of these software functions as devices. The draft guidance clarifies, however, that laboratory information management systems, which is software intended for administrative support of laboratories and/or for transferring, storing, converting formats or displaying clinical laboratory test data and results, no longer falls under the definition of "device."
  2. Software functions intended for maintaining or encouraging a healthy lifestyle: We have previously described the FDA's policy of exercising enforcement discretion with respect to software devices intended for certain "wellness" purposes. In the draft guidance, the FDA identifies the following examples from the General Wellness Guidance of mobile applications that no longer meet the definition of "device" due to the 21st Century Cures Act amendments: (1) an application that plays music to soothe and relax an individual to manage stress; and (2) an application that solely monitors and records daily energy expenditure and cardiovascular workout activities to allow awareness to improve or maintain good cardiovascular health. In addition, although the statutory amendment does not apply to wellness claims that relate to the role of a healthy lifestyle in helping reduce the risk or impact of particular chronic diseases or conditions, the FDA states that it will continue to exercise enforcement discretion over this category of products as long as they present a low risk to the safety of users and other persons.
  3. Software functions intended to serve as electronic patient records: Under the 21st Century Cures Act, a software function intended to transfer, store, convert formats or display electronic patient records that are the equivalent of a paper medical chart would not be a "device" if: (1) the records were created, stored, transferred or reviewed by health care professionals; (2) the records are part of information technology certified by the Office of the National Coordinator for Health Information Technology (ONC); and (3) the software function is not intended for interpretation or analysis of patient records. In the draft guidance, the FDA states that as long as criteria (1) and (3) are met, it does not intend to enforce the statutory requirement that the software function be certified by ONC. Additionally, the draft guidance clarifies that personal health records, which include software functions that enable a patient or non-health care provider to create, store or transfer health records for their own record-keeping, are not devices.
  4. Software functions that are intended for transferring, storing, converting formats and displaying data and results. In the draft guidance, the agency explains that software functions that solely transfer, store, covert formats and display medical device data would no longer fall within the definition of a "device," but that this exclusion does not apply to software that analyzes or interprets medical device data. Accordingly, software functions that generate alarms or alerts or prioritize patients based on their clinical status are not excluded from the definition of "device." The FDA explains, however, that it intends to exercise enforcement discretion not to regulate "low-risk" software functions of this type, such as analysis of data to provide a notification for which immediate clinical action is not needed.

However, the FDA notes that a software function described above will not be excluded from the definition of "device" if the FDA makes a finding that the software function would be reasonably likely to have serious adverse health consequences and certain substantive and procedural criteria are met, or if the device is Class III.

Software Precertification Program Workshop

The FDA also announced an upcoming public workshop that will be held on Jan. 30 and 31, 2018, which aims to discuss the current development of its Software Pre-Cert Pilot Program, which we summarized here. This voluntary pilot program — which began in September 2017 and currently includes nine participants — will assess a new approach for regulating digital health software that focuses on evaluating the software developer or digital health technology developer, rather than focusing primarily on the product. The public workshop will discuss various topics relating to precertification, such as the criteria and measures to evaluate whether a company is conducting high-quality software design, testing and ongoing maintenance of its software products and the types of digital health products that should be marketed without FDA review based on precertification.

IMDRF Guidance on Clinical Evaluation of Software as a Medical Device

The IMDRF is a voluntary group of medical device regulators from around the world that focuses on international medical device regulatory harmonization and convergence. This group has published several documents relating to regulation of software as a medical device (SaMD), defined as software intended to be used for one or more medical purposes that performs these purposes without being part of a hardware medical device. The guidance document the FDA has recently adopted and published in final form addresses the "clinical evaluation" of SaMD, which includes the activities needed to assess the clinical safety, performance and effectiveness of SaMD for its intended use. When the FDA initially proposed adopting this guidance document in October 2016, the draft was criticized by the medical device industry for its heavy use of terminology and concepts from foreign regulatory systems (particularly European), and its unclear relevance to the FDA regulatory framework. The final document eliminates some of the most concerning uses of such terminology and concepts that commenters identified, but may continue to be of uncertain application for entities that design and develop SaMD for the U.S. market.

Implications for the Digital Health Software Industry

The FDA's release of the two draft guidance documents, and continuing efforts to facilitate the Software Pre-Cert program, represent the agency's efforts to oversee digital health products under a risk-based framework and to prioritize innovation in this field. Whether the IMDRF guidance on clinical evaluation of SaMD will have any real-world impact for U.S. software developers remains to be seen, but the document represents yet another step in the FDA's efforts to build out a more complete and internationally consistent regulatory framework for digital health software. The FDA also has indicated that it will publish separate guidance on the regulation of a product with multiple functions, including at least one device function and at least one software function that is not a device.

Interested persons have until Feb. 6, 2018, to submit comments on the two draft guidance documents.

Originally published by Law360 on December 21, 2017.

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
McDermott Will & Emery
 
In association with
Related Topics
 
Similar Articles
Relevancy Powered by MondaqAI
McDermott Will & Emery
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