HTI-1 compliance doesn't end with certification. Learn how EHRs can maintain FHIR APIs, EHI Export, Decision Support Interventions, Real World Testing, and other ONC-certified capabilities to reduce compliance risk and support reliable interoperability.

HTI-1 compliance involves much more than implementing a FHIR API. This practical checklist helps EHRs and health IT teams evaluate certification, operations, SMART on FHIR, USCDI, EHI Export, Real World Testing, and whether to build internally or integrate with a certified partner.

A closer look at the MIPS 2026 updates that can affect measure selection, reporting workflows, support priorities, and MIPS readiness for EHRs and Provider Organizations alike.

Learn why annual MIPS measure updates, maintaining ONC certification, and supporting submission workflows create more internal work than many EHR teams expect.

January 1, 2023, is not just the beginning of a new year, it is also the beginning of the enforcement period for the Information Blocking portion of the Cures Act. The EHRs must provide FHIR APIs for all their users, and Providers must ensure that their FHIR API endpoints are publicly available.

The ONC has announced its punitive action plan to deal with non-compliant Health IT developers. EHRs failing compliance will undergo Direct Review, have to submit a Corrective Action Plan (CAP) and will be placed under a Certification Ban till they become compliant. Integrating with (g)(10) pre-certified BlueButtonPRO is an easy solution.

Tune in to the message the ONC is broadcasting through their recent blogs/media to reinforce the need for (g)(10) FHIR® API and Information Blocking compliance, whom these apply to, and how the mandates will be enforced. Let’s turn up the volume on the latest hits from ONC.

The misinformation floating around combined with an incomplete understanding of the (g)(10) FHIR API and other Cures Act requirements can be detrimental to the EHR developers and the providers. In this blog, we bust these myths, shatter misconceptions, and guide you to ask the right questions.

With the Cures Act deadlines around the corner, the focus has been on “how” to meet the requirements, and not “why”. Let’s not forget that each one of us will be a patient at some point in our lives. When we are the patient, we want Health IT to work for us. We need access to our health data for that and Cures Act makes it possible. This personal experience will make that evident.

EHRs are feeling the heat of Cures Act requirements as the deadlines draw closer. Read on to find answers to burning questions that EHR developers and providers are faced with as they are trying to understand the implementation details of the (g)(10) FHIR API and its implications.

Over the last decade, billions of American taxpayer dollars have been spent to achieve “interoperability” in healthcare. Has it worked? The answer depends on who you ask. However, everyone agrees that we have a long way to go. Is FHIR® the answer to the interoperability conundrum?

Over the last decade, billions of American tax payer dollars have been spent to achieve “interoperability” in healthcare. Has it worked? The answer depends on who you ask. However, everyone agrees that we have a long way to go. Can FHIR® might be the answer to the interoperability conundrum?