United States: 21st Century Cures Act Clarifies (And Somewhat Reduces) Regulation Of Stand Alone Software Products Used In Healthcare

Our firm has previously posted some summaries of the 21st Century Cures Act (Cures Act), which the President signed into law on December 13, 2016 (Public Law No. 114-255). (Those summaries are available here, here, and here.)

This post focuses on only one section of the new law: Section 3060, "Clarifying Medical Software Regulation." We covered the basics of Section 3060 in our prior summary, but thought it would be worthwhile to delve a little further in a separate post.

Section 3060 amends the Food, Drug, and Cosmetic Act (FDCA) to exclude from the definition of a "device" software intended:

(A) "for administrative support of a health care facility, including the processing and maintenance of financial records, claims or billing information, appointment schedules, business analytics, information about patient populations, admissions, practice and inventory management, analysis of historical claims data to predict future utilization or cost-effectiveness, determination of health benefit eligibility, population health management, and laboratory workflow;"

(B) "for maintaining or encouraging a healthy lifestyle and is unrelated to the diagnosis, cure, mitigation, prevention, or treatment of a disease or condition;" and

(C) "to serve as electronic patient records, including patient-provided information, to the extent that such records are intended to transfer, store, convert formats, or display the equivalent of a paper medical chart, so long as" such records "were created, stored, transferred, or reviewed by health care professionals, or by individuals working under supervision of such professionals" and the software "is not intended to interpret or analyze patient records, including medical image data, for the purpose of the diagnosis, cure, mitigation, prevention, or treatment of a disease or condition."

The exclusion of the above classes of software from the FDC Act should not be controversial. Category A are obviously not medical devices. Categories B and C are arguable, but FDA has said already that, even if these types of software fall within the definition of a medical device, as a matter of agency enforcement discretion, FDA does not intend to regulate them. Now Congress has taken them off the table altogether.

The fourth exclusion provided in the Cures Act is software intended:

(D) "for transferring, storing, converting formats, or displaying clinical laboratory test or other device data and results, findings by a health care professional with respect to such data and results, general information about such findings, and general background information about such laboratory test or other device," unless the software "is intended to interpret or analyze clinical laboratory test or other device data, results, and findings."

Category D above appears to include products meeting the definition of either a medical device data system (MDDS) or a laboratory information system (LIS). FDA has previously announced it is exercising enforcement discretion not to regulate MMDS; this provision codifies that position. FDA currently regulates LIS as 510(k) exempt Class I devices under 21 C.F.R. § 862.2100, product code NVV. An LIS is "intended to store, retrieve, and process laboratory data." FDA has continued to apply the quality system regulation (QSR) to these devices. Under the exclusion above, LIS products will now not be subject to the QSR or any other regulatory requirements at all.

The last type of software excluded from the definition of a device is software intended:

(E) unless the function is 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, for the purpose of –

(i) displaying, analyzing, or printing medical information about a patient or other medical information (such as peer-reviewed clinical studies and clinical practice guidelines);

(ii) supporting or providing recommendations to a health care professional about prevention, diagnosis, or treatment of a disease or condition; and

(iii) enabling such health care professional to independently review the basis for such recommendations that such software presents so that it is not the intent that such health care professional rely primarily on any of such recommendations to make a clinical diagnosis or treatment decision regarding an individual patient.

The software described in the above provision is commonly known as "clinical decision support software" (CDSS). It is well known that FDA has been mulling CDSS guidance for the past few years. However, it has never issued draft guidance. The closest FDA has come is the Mobile Medical Apps guidance (Feb. 2015), which classifies mobile apps as medical devices if they perform "patient specific analysis and provid[e] patient-specific diagnosis, or treatment recommendations." This statement suggests that FDA intended to regulate CDSS. However, it is possible that the CDSS guidance, had it been issued, would have walked that position back to some extent. In any event, Section 3060 resolves the status of CDSS more definitively than FDA guidance could have, by excluding CDSS from the definition of a medical device altogether.

The application of the definition in Category E will not always be self evident. There are questions about what it means for a health care professional to "independently review" the basis for software recommendations. Surely it does not require that the health care professional understand how the software reached a recommendation at the level of software coding and algorithms. It would be more reasonable to infer that the software must provide a sufficient level of transparency to allow a health care professional to discern the clinical basis of a recommendation. How exactly that must be accomplished will have to be worked out by FDA in guidance and administration and implementation of the statute.

In many cases, it may be sufficient for the software to provide links to the underlying clinical literature or guidelines. But what if the software uses "big data" from hospital records to derive recommendations for a patient? What information must the health care professional be given? And may the recommendations have confidence levels attached, if they are worked out with complicated probabilistic analysis? If so, what must be said about how the confidence levels are derived or should be used?

Another question is how the intended use environment factors in. For example, healthcare professionals have different levels of training and expertise. One of the benefits of CDSS is to encode the expertise of the best trained and most experienced doctors and make it available to other doctors. Yet, the latter are likely to rely more heavily on the software recommendations than would the best trained and most experienced doctors. Does that bring the CDSS under FDA regulation? FDA has long been prohibited under the statute from restricting devices to particular classes of health care practitioners based upon training or experience (see FDCA § 520(e)). However, the question here is whether the software is or is not to be regulated as a medical device. Therefore, it is not so clear that FDA may not make distinctions among the health care practitioners for whom the CDSS is intended when determining if it is regulated.

There is one more aspect of Category E we have not discussed. The clause that begins "unless the function is 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" designates software products that are excluded from Category E and will continue to be fully FDA regulated as medical devices.

Had this clause not been included, one could argue that computer assisted detection or diagnostic (CAD) devices that analyze image data (e.g., identifying suspicious lesions in a CT scan) and in vitro diagnostic devices are a type of CDSS. Nonetheless, FDA has a long history of regulating these types of devices. This language ensures that FDA will continue to do so.

Section 3060 also gives FDA authority to bring some excluded CDSS software back under its jurisdiction. FDA may bring software described in Categories C, D, or E, above, back under its jurisdiction if it makes certain findings regarding: (1) the likelihood and severity of patient harm if the software does not perform as intended, (2) the extent to which the software is intended to support the clinical judgment of a health care professional, (3) whether there is a reasonable opportunity for a health care professional to review the basis of the information or treatment recommendation, and (4) the intended user and use environment.

For FDA to determine that software excluded from the device definition should in fact be regulated, FDA must publish a notification and proposed order in the Federal Register, and must include its rationale and evidence on which it is relying for the conclusion that such software should be regulated. The notice must allow for at least 30 days of public comment before issuing a final order or withdrawing the proposed order.  

Section 3060 requires the Secretary of Health and Human Services to publish a report, within two years of enactment of the Cures Act and every two years thereafter, that includes input from industry, consumers, patients, health plans, and other "stakeholders with relevant expertise." The report must include information about any risks and benefits associated with the software functions provided in the Cures Act, and "summarizes findings regarding the impact of such software functions on patient safety, including best practices to promote safety, education, and competency related to such function." Time will tell how this information may be used to further modify FDA's authority over software.

For now, the software exclusions in Section 3060 of the Cures Act are welcome news to an industry that has been struggling with the question of whether its products are subject to FDA regulation, particularly in the area of CDSS. The new clarity will allow innovative software developers to move forward with greater confidence as to whether a product will or will not be regulated by FDA as a medical device.

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.

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
Font Size:
Mondaq on Twitter
Mondaq Free Registration
Gain access to Mondaq global archive of over 375,000 articles covering 200 countries with a personalised News Alert and automatic login on this device.
Mondaq News Alert (some suggested topics and region)
Select Topics
Registration (please 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.


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.


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