Beckage attorneys have been busy helping clients understand and prepare for the two rules concerning interoperability issued on March 9, 2020 by the Centers for Medicare & Medicaid Services (CMS) and the Office of the National Coordinator for Health Information Technology (ONC) (collectively referred to as the “Final Rules”). The Final Rules implement interoperability and record access requirements intended to help patients obtain health records and payment data so they can make informed decisions about healthcare. To help de-mystify these technical rules, Beckage will be releasing a blog series outlining how the Final Rules will impact different organizations in the health sector.
While future blogs will tackle some of the technical nuances of the Final Rules, this blog will provide some context by answering a few high-level questions:
1. Who should pay attention to these Final Rules? Healthcare providers, health IT developers, health information exchanges, health information networks, electronic health record (EHR) vendors, and insurers participating in CMS programs (for purposes of this blog, these stakeholders are collectively referred to as “health care organizations,” although as discussed in future posts, they often have different interests and obligations under the Final Rules).
2. What is an API? ”API” stands for application programming interface. An API is essentially a software intermediary that allows two applications to talk to each other using standardized language.
3. What does the CMS Final Rule cover? The CMS Final Rule requires states and certain health care organizations to develop APIs that allow patients, medical providers, and insurers to access specific categories of data. The rule is intended to improve patient access to health information and standardize the types of health information that can be shared. For example, patients will be able to request access to their medical records via third-party apps, and payers may deny access only under specific circumstances. The CMS Rule also requires payers to provide information about in-network providers and exchange information with other insurers in the event a patient enrolls with a new insurance company.
4. What does the ONC Final Rule cover? The ONC Final Rule imposes standardized protocols to allow networks and software applications to talk to one another. Basically, the ONC Final Rule requires insurers, medical providers, IT vendors, and health exchanges to speak the same language. This is accomplished through updated and standardized health IT certification requirements, data classifications, and systematic requirements for APIs. The ONC Rule also implements the information blocking provisions of the 21st Century Cures Act.
5. When will the rules take effect? United States Department of Health and Human Services (HHS) recently issued guidance stating that it was extending some enforcement deadlines. Below are just a few of the new compliance deadlines relevant to hospital and payer organizations:
· Spring 2020: Hospitals must be able to demonstrate that they comply with patient admission, discharge, andtransfer (ADT) event notification procedures required by the CMS Rule.
· July 1, 2021: Payers must make a PatientAccess API available so patients’ third-party apps can access medical records via the API.
· July 1, 2021: Payers must make a Provider Directory API available, so patients know which providers are in network.
The Final Rules represent a complete overhaul of well-established standards and an introduction of new and highly technical requirements with compliance deadlines as early as Spring 2021. Now is the ideal time for health care organizations to assess compliance requirements, contract with vendors, and develop a compliance framework. Beckage attorneys are uniquely experienced to help health organizations and tech companies of all sizes to navigate the complicated maze of legal and practical considerations raised by these and other health law regulations.
*Attorney Advertising. Prior results do not guarantee future outcomes.