HHS finalized a rule removing 14 health software certification criteria and revising seven. Most changes take effect 60 days after publication.
The US health department has finalized a rule that removes 14 certification requirements for health software and revises seven more. Most changes take effect 60 days after publication, with some starting on Jan. 1, 2027.
The final rule comes from the Office of the National Coordinator for Health Information Technology (ONC), part of the Department of Health and Human Services (HHS)1. It affects software makers that certify their electronic health record products under ONC’s voluntary program, and the bodies that test and certify them1. The rule was filed for public inspection on 26 October 2026 and is scheduled for publication in the Federal Register on 28 October 20262.
| At a glance | Details |
|---|---|
| What was published | Final rule, "ONC Deregulatory Actions to Unleash Prosperity" (RIN 0955-AA09) |
| Published on | Filed 26 October 2026; Federal Register publication scheduled 28 October 2026 |
| Who must comply | Developers of certified health IT, certification bodies and testing labs |
| Effective date | 60 days after publication; three instructions take effect 1 January 2027 |
| Next milestone | Other proposals from the draft rule remain under review |
What does the rule change, and why?
ONC runs the Certification Program, a voluntary scheme that checks whether health software meets federal standards1. The rule removes or revises certification criteria, meaning the specific features software must have to be certified1. HHS says many of these features no longer drive adoption in the market1.
The agency ties the rule to two executive orders on deregulation and competition1. It also wants to steer the program toward FHIR-based APIs, a modern standard that lets health systems exchange data through software links1. HHS says this shift will allow newer tools, including ones that work with large language models, to emerge1.
How many requirements are going?
The draft rule proposed far deeper cuts than the final version1. Out of 60 criteria now in effect, HHS had proposed removing 34 and revising seven1.
| Certification criteria by the numbers | Details |
|---|---|
| Criteria currently in effect | 60 |
| Proposed for removal | 34 |
| Removed in final rule | 14 |
| Revised in final rule | 7 |
| Kept without change | 39 |
The 39 criteria kept unchanged include new electronic prior authorization criteria adopted in an earlier rule known as HTI-41. Proposals not addressed in this rule remain under review and may return in later rules1.
What changes for health software developers
One major revision narrows the "decision support interventions" criterion, which covers tools that help clinicians make decisions1. The rule fully removes its "model card" requirements, which covered source information that users could see and edit1.
The rule also scales back other duties for developers:
- Real world testing: plans and results requirements are cut back, in line with an enforcement notice issued on June 30, 20251.
- Insights reporting: most proposed removals of these measures were finalized, but not all1.
- Standards: outdated standards no longer used in the program are removed1.
- Definitions: "Common Clinical Data Set" is deleted and "Base EHR" is updated1.
Some standards will be removed only after a transition period until Jan. 1, 20271. The rule also deletes references to the Assistant Secretary for Technology Policy from the program’s rules1.
Costs and savings for the industry
HHS estimates the changes impose $0 in compliance costs on developers of certified health IT1. It put the cost of reading the rule at $1,293,508 for an estimated 616 reviewers1.
| Cost estimate | Amount |
|---|---|
| Compliance cost for developers | $0 |
| Cost for rule reviewers | $1,293,508 |
| Present value of savings | $1.55 billion |
| Annual net savings | $108.1 million |
The agency estimates savings with a present value of $1.55 billion1. Annual net savings are put at $108.1 million in 2024 dollars, discounted at 7%, starting in 20271. HHS says lower barriers should bring new developers into the market and give providers more choice1.
Transition timeline and key deadlines
The rule takes effect 60 days after its Federal Register publication1. Publication is scheduled for 28 October 20262.
| Key date | What happens |
|---|---|
| 26 October 2026 | Rule filed for public inspection |
| 28 October 2026 | Scheduled Federal Register publication |
| 60 days after publication | Most of the rule takes effect |
| 1 January 2027 | Three amendatory instructions take effect, and some standards end |
The rule says each provision is meant to stand alone1. If a court strikes down one part, HHS intends the rest to stay in force1.
Key terms in plain words
| Term | Meaning |
|---|---|
| ONC | The HHS office that sets standards for health software |
| Certification criteria | Features software must have to win federal certification |
| FHIR | A modern standard for sharing health data between systems |
| API | A software link that lets one system request data from another |
| Real world testing | Checks that certified software works in actual clinical use |
| Model card | A summary of source details behind a decision support tool |
Most of the rule takes effect 60 days after its scheduled 28 October 2026 publication, with the rest following on Jan. 1, 20271.
Sources
- ↩ 2026-21943.pdf https://public-inspection.federalregister.gov/2026-21943.pdf
- ↩ Federal Register :: Public Inspection: Health Data, Technology, and Interoperability: Office of the National Coordinator for Health Information Technology Deregulatory Actions to Unleash Prosperity https://www.federalregister.gov/public-inspection/2026-21943/health-data-technology-and-interoperability-office-of-the-national-coordinator-for-health