United States: End Of Year Attention To Health IT And Digital Health Tools In 21st Century Cures

Summary



The 21st Century Cures Act encourages biomedical research investment and facilitates innovation review and approval processes, but also serves as a vehicle for a wide variety of other health-related measures, including provisions relating to health information technology (HIT) and related digital health initiatives. President Barack Obama has expressed support for the Cures legislation and is expected to sign the bill this month. This On the Subject summarizes the HIT and digital health tool provisions in title IV of the new legislation. Our continuing coverage of the 21st Century Cares Act addresses additional titles and provisions.

In Depth

On December 7, 2016, the US Congress approved the 21st Century Cures Act (Cures legislation), which is intended to accelerate the "discovery, development and delivery" of medical therapies by encouraging public and private biomedical research investment, facilitating innovation review and approval processes, and continuing to invest and modernize the delivery of health care. The massive bill, however, also served as a vehicle for a variety of other health-related measures, including provisions relating to health information technology (HIT) and related digital health initiatives. President Barack Obama has expressed support for the Cures legislation and is expected to sign the bill this month.

This On the Subject summarizes the HIT provisions in title IV of the new legislation. Other titles and provisions will be examined through other On the Subject articles.

Overview of the Health Information Technology Provisions in the Cures Legislation

The HIT provisions of the Cures legislation in general seek to

  • Reduce administrative and regulatory burdens associated with providers' use of electronic health records (EHRs)
  • Advance interoperability
  • Promote standards for HIT
  • Curb information blocking
  • Improve patient care and access to health information in EHRs

Why These Provisions Matter

As public and private payers increasingly move from fee-for-service payments to value-based payment models, with a focus on maximizing health outcomes, population health improvement, and patient engagement, HIT—including EHRs and digital health tools—will be increasingly relied upon to collect clinical data, measure quality and cost effectiveness; assure continuity of care between patients and providers in different locations; and develop evidence-based clinical care guidelines. Further, newly implemented government programs like the Quality Payment Program will increasingly require clinicians and hospitals to use certified EHR technology (CEHRT) that meets certification guidelines specified by the Office of the National Coordinator for Health Information Technology (ONC) of the US Department of Health and Human Services (HHS). The continued evolution of these certification guidelines will also influence the development of digital health tools that are designed to interface or otherwise interact with CEHRT and assist providers to succeed under value-based payment models.

Congressman Tom Price (R-GA), a physician and a strong advocate for reducing burdens associated with the use of EHRs by providers, has been nominated to serve as HHS secretary in the administration of President-elect Donald Trump. Should Congressman Price be confirmed by the Senate, industry can likely expect HHS to use the new authority provided to it under the Cures legislation to reduce requirements of the Meaningful Use and Advancing Care Information programs, electronic clinical quality measure reporting requirements and other federal requirements relating to HIT that are perceived to make providers less efficient without improving quality or reducing costs. The new HHS secretary, however, will face competing pressures to leverage the expansion of HIT adoption and quality measure reporting to incentivize high-quality care at lower Medicare program costs.

What Is Required by These Cures Legislation Provisions

Reduction of Burdens ‒ In response to clinician and hospital concerns about the regulatory and administrative burdens associated with EHR technology

  • The HHS secretary is required within one year of enactment to develop with public comment from providers, suppliers, payers, technology developers and others a strategy and recommendations to reduce regulatory or administrative burdens related to the use of EHRs; this strategy must prioritize the Medicare and Medicaid EHR Incentive Programs, HIT certification, the Merit-based Incentive Payment System, the Hospital Value-Based Purchasing Program, Alternative Payment Models, and other value-based payment programs that the HHS secretary determines are appropriate;
  • Physicians may delegate EHR documentation requirements to unlicensed assistants, or "scribes" (to the extent permitted by state law), provided the physician signs and verifies the documentation;
  • The HHS secretary must encourage, keep or recognize voluntary certification of HIT for use in sites of services and medical specialties for which no certified technology is currently available, with the goal of making EHR certification more relevant and useful for those who use such EHRs.
  • The HHS secretary must report to the new HIT Advisory Committee statistics on attestation of Meaningful Use under the Medicare and Medicaid EHR Incentive Programs to assist in informing standards adoption and related practices. The statistics must include, to the extent practicable, the number of providers who did not meet the minimum criteria necessary to attest, and must be made publically available on the HHS website;
  • Authorizes $15 million to award grants, contracts or agreements to independent entities on a competitive basis to develop a required CEHRT reporting system to address provider concerns that CEHRT technology does not always work as intended. As a condition of certification and attestation, CEHRT would be required to report measures developed by the independent entity on attributes that include
    • Security
    • User-centered design
    • Interoperability
    • Testing in real-world conditions
    • This provision aims to create an unbiased reporting system on EHR product usability, interoperability and security to assist providers in choosing product. This reporting system replaces a proposed "Star Rating" plan for EHR technology found in an earlier version of the legislation.

    Advancement of Interoperability ‒ In response to lawmakers' and stakeholders' concerns that while the Health Information Technology for Economic and Clinical Health Act (HITECH) increased the adoption by clinicians and hospitals of electronic health records, it did not sufficiently move the national needle on interoperability, the Cures legislation seeks to advance interoperability through

    • Creating a definition for "interoperability" as HIT that
      • Enables the secure exchange of electronic health information with, and use of electronic health information from, other HIT without special effort on the part of the user
      • Allows for complete access, exchange and use of all electronically accessible health information for authorized use under applicable state or federal law
      • Does not constitute information blocking as defined in the Cures legislation
    • Replacing the HIT Policy and Standards Committees with a new HIT Advisory Committee. This new committee will consist of at least 25 members, eight of whom shall be appointed by Congress, three appointed by the HHS secretary and the remainder appointed by the comptroller general of the US Government Accountability Office (GAO). Specific health sectors must be represented on the committee. This new federal advisory committee will address, in general, issues related to interoperability and privacy and security of health information and will also engage stakeholders to identify priorities for standards adoption. The Cures legislation provides additional direction on priority target areas on which the committee shall make recommendations. These directives are highly similar to those provided to the predecessor HIT Policy and Standards Committee in HITECH. This reiteration of areas for consideration likely signals that lawmakers believe that many of the objectives set forth in HITECH have not yet been fully achieved.

      One new priority area is patient matching, which relates to the unfulfilled directive to further interoperability between EHR systems. Specifically, the Cures legislation requires the new HIT Advisory Committee to make recommendations for "technology that provides accurate patient information for the correct patient, including exchanging such information, and avoids the duplication of patient records." This directive and the call for a GAO study on patient matching indicates that policy makers recognize the importance of accurately identifying patients for electronic exchange of health information among providers in different organization and locations as well as for patient safety.

    • Tasking ONC to create a process by which the public could submit complaints that HIT products or developers are not interoperable or engage in information blocking.
    • Directing ONC to, within six months of enactment, convene stakeholders to develop or support (within 12 months of convening) a trusted exchange framework for trust policies and practices and for a common agreement for exchange between health information networks. ONC and the National Institute of Standards and Technology are to provide technical assistance on developing this trusted exchange framework and common agreement. A process will be established through rulemaking by which health information networks may voluntarily adopt the framework and common agreement. Federal agencies may by contracting or entering into agreements with health information exchange networks that require such networks to adopt the trusted exchange framework and common agreement.

    Promotion of Standards – Lawmakers have increasingly recognized that stronger leadership is needed to ensure the consistent implementation and use of common standards. Accordingly, the Cures legislation requires the ONC to, not later than six months after the date on which the HIT Advisory Committee first meets, convene the HIT Advisory Committee to

    • Enhance the use of common standards with deference given to standards published by private standards development organizations and voluntary consensus-based standards bodies.
    • Identify priority use cases for HIT, focusing on use cases relating to
      • The implementation of Medicare's EHR Incentive Program, the Merit-based Incentive Payment System, Alternative Payment Models, the Hospital Value-Based Purchasing Program and any other value-based payment program determined appropriate by the HHS secretary
      • Quality of patient care
      • Public health
      • Clinical research
      • Privacy and security of electronic health information
      • Innovation in the field of HIT
      • Patient safety
      • Usability of health information technology
      • Individuals' access to electronic health information
    • Identify existing standards and implementation specifications that support such use cases.
    • Publish a report summarizing the findings of the analysis and make appropriate recommendations.
    • Evaluate the need for a core set of common data elements and associate value sets to enhance the ability of CEHRT to capture, use and exchange structured electronic health information.

    Starting five years after the enactment of the Cures legislation, and every three years thereafter, the ONC must convene stakeholders to review the existing set of adopted standards and implementation specifications and make recommendations for maintaining or phasing out such standards and implementation specifications.

    Combatting Information Blocking The Cures legislation builds on the April 2015 ONC Report to Congress on Health Information Blocking and the voluntary ONC interoperability pledges signed earlier this year by companies that provide at least 90 percent of EHRs used by hospitals, and takes even stronger steps to combat information blocking by

    • Defining "information blocking" as a practice, except as required by law or allowed by the HHS secretary pursuant to rulemaking, that
      • Is likely to interfere with, prevent or materially discourage access, exchange or use of electronic health information
      • If conducted by an HIT developer, exchange or network, such entity knows or should know that such practice is likely to interfere with, prevent or materially discourage the access, exchange or use of electronic health information
      • If conducted by a health care provider, such provider knows that such practice is unreasonable and is likely to interfere with, prevent or materially discourage access, exchange or use of electronic health information
    • Establishing that information blocking practices may include
      • Practices that restrict authorized access, exchange or use of such information for treatment and other permitted purposes under such applicable law, including transitions between certified HIT systems
      • Implementing HIT in nonstandard ways that are likely to substantially increase the complexity or burden of accessing, exchanging or using electronic health information
      • Implementing HIT in ways that are likely to
        • Restrict access, exchange or use of electronic health information with respect to exporting complete information sets or in transitioning between HIT systems
        • Lead to fraud, waste or abuse, or impede innovations and advancements in health information access, exchange and use, including care delivery enabled by HIT
    • Establishing new civil monetary penalties of up to $1 million per information blocking violation, including false attestations, that would be applicable to HIT developers, health information exchanges and networks. In contrast, provider penalties will be determined through notice and comment rulemaking. Importantly, for enforcement purposes, information blocking does not include any practice or conduct occurring prior to the date that is 30 days after enactment

    Improving Patient Care and Improving Patient Access to Their Health Information in EHRs

    • Requires the GAO to conduct two studies
      • A study on patient matching within two years of enactment. In calling for this study, lawmakers recognize that, with the increasing use of EHRs and the push toward interoperability, identifying accurately a single individual represented in multiple databases of different provider, payer and clearinghouse organizations is increasingly important for facilitating health information exchange and ensuring patient safety
      • A study on patient access to their own health information, including barriers to patient access
    • Enables developers of HIT to participate in discussions with patient safety organizations without fear of liability risk in order to help improve the safety of HIT products for patients. Within four years after the date of enactment, the HHS secretary must submit to Congress a report concerning the best practices and current trends voluntarily provided, without identifying individual providers or developers
    • Requires CEHRT to be capable of transmitting data to, and receiving data from clinician-led clinical data registries

    Action Steps for Providers and Developers of HIT and Digital Tools

    Providers and Developers of HIT and Digital Tools Should

    • Review the definition of information blocking and take measures necessary to avoid engaging in practices that may constitute information blocking as defined in the new statute.
    • Review applicable state laws that permit physician delegation to scribes to determine if the new federal flexibility applies.
    • Assess potential interest in seeking representation on the new HIT Advisory Committee, either directly or through an association or other group (note that it is unclear how quickly after enactment ONC will form the HIT Advisory Committee, as a timeline for the transition from the HIT Policy Committee and the HIT Standards Committee to the new HIT Advisory Committee is not specified).
    • Assess their implementation of HIT standards to determine the extent to which different standards and inconsistent implementation of the same standards may be prevalent.
    • Be aware that changes to existing government requirements relating to EHRs are likely forthcoming.

    Providers Should

    • Assess their unique regulatory environment to provide input on the forthcoming HHS efforts to reduce regulatory burdens.
    • Determine whether their sites of service or specialties would benefit from CEHRT certified to meet their sites' or specialties' unique needs.

    Developers of HIT and Digital Tools Should

    • Consider participating in stakeholder outreach efforts to advise ONC on
      • The establishment of a trusted exchange framework and common agreement
      • Criteria and measures for the new CEHRT reporting system
      • The HIT Advisory Committee's review of the existing set of adopted standards and implementation specifications every three years
    • Adapt HIT development and testing strategies based on the criteria and measures established by the independent entity selected by ONC.
    • Consider opportunities to partner with clinician-led organizations or professional societies to develop clinician-led clinical data registries.
    • Keep abreast of new HIT requirements to inform the development of digital tools.
    • Evaluate how best to work with patient safety organizations to promote shared learning to improve HIT safety now that privilege and confidentiality protection has been extended to HIT developers.

21st Century Cures: Health Information Technology and Digital Health Tool Provisions in Title IV

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
 
In association with
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
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement

Mondaq.com (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of www.mondaq.com

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). 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 & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about Mondaq.com’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.

Disclaimer

Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd 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 or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.

Registration

Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to unsubscribe@mondaq.com with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.

Cookies

A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.

Links

This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.

Mail-A-Friend

If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.

Security

This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to webmaster@mondaq.com.

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to EditorialAdvisor@mondaq.com.

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at enquiries@mondaq.com.

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at problems@mondaq.com and we will use commercially reasonable efforts to determine and correct the problem promptly.