The Office of the National Coordinator’s New Interoperability Rule and its Relationship to EHR Mandates

The Office of the National Coordinator (ONC) recently passed the 21st Century Cures Act and the CMS Interoperability Final Rule, which will give both patients and health care providers secure access to personal health information. Under this new rule, companies in the health care industry are encouraged to install standardized Application Programming Interfaces (APIs) that give patients access to their health information from a mobile application. 

But what do these new rules mean for EHR mandates? How does the health care system as a whole improve from them? In our latest article, Iron Bridge examines the 21st Century Cures Act and Final Rule as well as their impact on EHR mandates. 

The Impact of Current EHR Mandates

Learn Why EHR Mandates Are Important for Patients and Their Communities 

person typing on a laptop with a stethoscope beside them

Many patients and physicians initially feel wary about storing sensitive health data onto a cloud-based system. To ensure the safety and protection of this information, CMS payers are required to follow a set of EHR mandates

These guidelines are designed to:

  • Engage both patients and families in their health care
  • Ensure the privacy of patient health information found in the EHRs
  • Improve public health management and services
  • Reduce health disparities among different members of the community

Due to the rise in use of EMR/EHRs, many health care professionals are on the search for innovative technologies that follow these mandates and improve upon the current technology for managing patient records. 


The Cures Act and Interoperability Final Rule

Everything You Need to Know About the New Act

person signing a legal document

The Interoperability and Patient Access Final Rule can be summed up rather quickly. Essentially, the rule requires CMS-regulated payers to utilize APIs and FHIR technology to give physicians and patients better access to their health information. CMS-regulated payers include Medicare Advantage organizations, Medicaid Fee-for-Service (FFS) programs, CHIP FFS programs, Medicaid managed care plans, CHIP managed care entities, and Qualified Health Plan (QHP) issuers. 

Using HL7 FHIR 4.0.1. these APIs must allow users to access their claims, payments, and health information through third-party apps. Payers should also make their provider director information publicly available to viewers through a FHIR-based Provider Directory API. CMS-regulated providers must implement these requirements in increments between now and April 2022. 

Choosing an IT Solution for Following the New ONC Rules 

So how do these new laws affect a payer’s current ability to follow EHR mandates? They essentially aim to make Electronic Health Records more accessible to both physicians and patients. With easier access to electronic health records, physicians can improve patient outcomes as a result of reducing medical errors, increasing the efficiency of care, simplifying administrative tasks, and encouraging patients to become more involved in their health care decisions. 

When it comes to deciding how to overhaul current systems to make them abide by the new ONC rule, EHR vendors are often stuck between building their own technologies or purchasing ready-to-use FHIR API. Payers who choose to build their own FHIR APIs often end up paying a hefty bill for the creation and long-term management of their custom-build systems. That’s why many payers end up looking into purchasing ready-to-use FHIR APIs instead. One such software — the fhirstation by Iron Bridge — was designed to serve as an instant source of Final Rule compliance for CMS payers. 

Fhirstation: An IT Solution for Health Care Providers Following the Cures Act

How the fhirstation Successfully Handles EHR Mandates and Regulations

fhirstation graphic

Fhirstation by Iron Bridge is a Software as a Service (SaaS) solution for EHR vendors and any other entity that is required to provide patient data via an Application Programming Interface or API. One can think of it as a secure health data storage platform, as patients, health systems, and EHR vendors can safely exchange information through fhirstation. 

The fhirstation’s benefits are plentiful. By storing a patient’s health data in a Native FHIR v4 data model, the software does not have to translate this information into a proprietary API to be accessed. Physicians can also assess their patients’ information and test results using a powerful set of data analytics tools. Because fhirstation was built specifically to fit the Cures Act Final Rule, medical centers will not have to worry about whether or not they properly followed its new compliance requirements. No additional experience is needed to utilize fhirstation in your organization.


Iron Bridge was founded upon a mission to simplify interoperability in today’s health care system. To help bridge the glaring gap between a patient’s ability to manage their personal health care data and their power to coordinate their own care, Iron Bridge created fhirstation. Since then, Iron Bridge continues to function as a leader in providing solutions for improving the day-to-day lives of health care workers. For more information on how fhirstation can benefit your company and assist you in following EHR mandates, contact the team at Iron Bridge today.

Back to blog