What is the ONC Health IT Certification Program?

ONC Health IT Certification is a voluntary federal program, run by ASTP/ONC with third-party certification bodies, that tests health IT such as EHRs against criteria set by HHS. It matters because CMS programs and other rules require providers to use certified health IT.

ONC describes the program as voluntary and run as a third-party product conformity assessment scheme. HHS adopts the standards and certification criteria, ONC-Authorized Certification Bodies certify products and carry out surveillance in the field, and successfully tested products are listed on the Certified Health IT Product List (CHPL).

It is voluntary for vendors but rarely optional in practice. The program exists to support the use of certified health IT under other federal, state and private programs, and CMS's Promoting Interoperability programs require it. ONC says certification gives EHR purchasers assurance that a system meets the capability, functionality and security requirements adopted by HHS.

What gets certified

Products are certified as modules against individual criteria in § 170.315. One of the most consequential for third-party developers is (g)(10), the standardized API for patient and population services. It requires read access for single patients through FHIR R4 and US Core, multi-patient export through FHIR Bulk Data, SMART App Launch for authorization, TLS 1.2 or higher, patient-revocable app access, and public API documentation reachable with no preconditions.

Criteria change through rules such as HTI-1, which made USCDI v3 the baseline from January 1, 2026. ONC tracks a regulatory update deadline per criterion: several HTI-1 updates were due by December 31, 2025, and the decision support interventions and electronic prescribing criteria have deadlines of December 31, 2027.

Obligations after certification

Certified developers must meet Conditions and Maintenance of Certification. They also become actors under the information blocking rules, which carry civil monetary penalties of up to $1 million per violation and certification action that could include termination or a ban.

Example

A health system choosing an ambulatory EHR checks the CHPL for the exact product version and confirms it is certified to the criteria its CMS reporting depends on, plus (g)(10), so that the apps it plans to add later have a standard API to connect to.