ONC’s HTI-5 final rule: what leaves the Health IT Certification Program
ONC’s rule of October 28, 2026 removes 14 certification criteria, narrows the decision support criterion and descopes real world testing and Insights reporting. Most changes take effect December 28, 2026; seven removals wait until January 1, 2027.
The rule and its dates
The Office of the National Coordinator for Health Information Technology (ONC) published “Health Data, Technology, and Interoperability: ONC Deregulatory Actions To Unleash Prosperity”, known as HTI-5, on October 28, 2026 (91 FR 67916). It takes effect on December 28, 2026, except for three amendatory instructions that take effect on January 1, 2027 [1] [2]. It finalizes part of a proposed rule published December 29, 2025 (90 FR 60970), whose comment period closed February 27, 2026 [3].
The rule changes the ONC Health IT Certification Program, the voluntary program that certifies electronic health record products and other health IT to criteria in 45 CFR 170.315. ONC describes the rule as resetting the program’s scope to build on requirements for FHIR-based application programming interfaces [4]. Its stated reasoning is that certification is likely no longer a primary factor driving improvement in several areas, and that some functions are widely adopted: it cites its 2024 survey data, in which 99 percent of hospitals and 91 percent of physicians reported having a certified EHR [1].
The numbers
Of the 60 certification criteria in effect, ONC had proposed removing 34 and revising seven. The final rule removes 14 and revises seven, and leaves 39 unchanged, including the electronic prior authorization and real-time prescription benefit criteria added in 2025 by the HTI-4 rule [1]. ONC says comments on the proposals it did not finalize remain under review, and those proposals may return in later rules [1].
Criteria removed on December 28, 2026
- Clinical decision support, 170.315(a)(9): already expired on January 1, 2025; the rule removes it from the regulation [1].
- Security tags, summary of care, send and receive, 170.315(b)(7) and (b)(8) [1].
- Care plan, 170.315(b)(9) [1].
- Consolidated CDA creation performance, 170.315(g)(6) [1].
- Transport methods, 170.315(h)(1) direct project and (h)(2) direct project, edge protocol and XDR/XDM [1].
Criteria removed on January 1, 2027
- Family health history, 170.315(a)(12) [1].
- Clinical quality measures, filter, 170.315(c)(4) [1].
- Patient health information capture, 170.315(e)(3) [1].
- Automated numerator recording, 170.315(g)(1), and automated measure calculation, 170.315(g)(2) [1].
- Application access, patient selection, 170.315(g)(7), and all data request, 170.315(g)(9) [1].
For patient health information capture, ONC chose January 1, 2027 because the criterion is part of CMS’s definitions of certified EHR technology; ONC notes that CMS removed the criterion from its hospital definition of certified EHR technology in the FY 2027 hospital inpatient payment rule of August 4, 2026, and proposed a similar change for clinicians [1]. For the two application access criteria, ONC’s reasoning is that the standardized FHIR API criterion, 170.315(g)(10), already requires the same patient selection function through the SMART App Launch guide [1].
Criteria revised
Decision support interventions
The largest revision narrows the decision support interventions criterion, 170.315(b)(11). The rule removes the source attribute requirements for evidence-based and predictive interventions, the requirements for users to access and modify source attributes, and the intervention risk management requirements for predictive interventions. It also drops the reference to drug-drug and drug-allergy contraindication checking and limits the criterion’s scope [1]. A matching assurance in 170.402(b)(4), which had required developers to review and update source attribute and risk management information, is removed [1].
Transitions of care
ONC had proposed removing Direct messaging and C-CDA document exchange requirements from the transitions of care criterion, 170.315(b)(1). After comments, it finalized the removal with a later date: the “send and receive via edge protocol”, “create”, “display” and “display section views” requirements are removed effective January 1, 2030 [1].
What ONC kept
Several proposals were not finalized. The privacy and security certification criteria, 170.315(d)(1) through (13), stay [1]. The implantable device list criterion stays; ONC notes that CMS has adopted a Medicare Promoting Interoperability measure on unique device identifiers for implantable devices, beginning with the CY 2027 reporting period [1]. The transmission to cancer registries criterion stays; ONC says it will continue to monitor FHIR-based standards for cancer reporting [1].
Conditions of certification for developers
Two ongoing obligations on certified health IT developers shrink. The real world testing condition is descoped, with changes to testing plans, results reporting and use of the standards version advancement process, consistent with an enforcement discretion notice ONC issued on June 30, 2025 [1]. Most measures under the Insights condition are removed; ONC kept the measures on use of FHIR in apps and use of FHIR bulk data access [1].
The rule also removes standards no longer referenced, including two API standards in 170.215(b)(1)(i) and (c)(1) that expired on January 1, 2026, and removes references to the Assistant Secretary for Technology Policy from the certification program and the Trusted Exchange Framework and Common Agreement rules [1].
What changes for health systems and practices
The rule regulates certification, not providers. A removed criterion means a product no longer has to be certified to that function, and the certification program no longer tests it; it does not stop a developer from offering the function. Commenters told ONC they would keep supporting Direct messaging after the transport criteria go [1], and the Direct requirements inside the transitions of care criterion stay until 2030 [1].
For buyers, the effect is that a certification listing says less than it did. Where a health system relies on a removed function, such as care plan exchange, security tags on summaries of care, or source attribute information for decision support, it can ask its vendor whether the function will be kept and write that into the contract. That is good practice for procurement, not something the rule requires.
ONC’s fact sheets and a recording of its October 29, 2026 information session are on its HTI-5 page [4]. Moraph’s teams help organizations with work like this; see our solutions.
Spotted an error? Tell us and we will check it and correct the explainer where needed.