HHS's HTI-5 Rule Cuts $1.5B in Health-IT Certification Costs Starting December

HHS eliminates certification requirements as HTI-5 takes effect in two months

The U.S. Department of Health and Human Services finalized its HTI-5 deregulatory rule on October 26, removing or revising requirements in the ONC Health IT Certification Program. The rule takes effect December 28, 2026, with specified provisions starting January 1, 2027. HHS projects the changes will eliminate more than $1.5 billion in regulatory costs across the industry — but that aggregate figure tells enterprise buyers nothing about their own software bills.

The rule revises certification criteria, health-IT standards, implementation specifications, and program obligations that vendors currently navigate to sell certified products. It does not mandate new interoperability technology, replace FHIR, or name a preferred platform. The competitive effect is economic: EHR vendors, health-information exchanges, integration platforms, and API providers will spend less on compliance paperwork. Whether they pass those savings to customers depends on contract leverage, not regulatory intent.

What changes for enterprise buyers

Organizations selecting or renewing certified health-IT products should require vendors to document which certification criteria are being removed, retained, or revised — and when their products will reflect those changes. The $1.5 billion cost-reduction figure is an HHS estimate spread across thousands of vendors and health systems, not a line item in any single hospital's budget. Buyers should separate vendor compliance savings from their own procurement costs.

Reduced certification obligations lower vendor costs but increase the importance of contractual controls. Enterprises should tighten contract language covering API availability, conformance testing, data portability, audit rights, cybersecurity baselines, and transition support. The rule removes some federal requirements; it does not remove the need for buyers to specify what interoperability capabilities they expect and how they will verify them.

HTI-5 preserves the broader policy direction toward interoperability and API use while leaving detailed future standards decisions open. ONC stated that future actions may address expanded API use, successor technologies, and targeted conditions of certification — but those proposals are not part of the current rule. Buyers should not treat HTI-5 as a reason to abandon FHIR-based integration plans. The rule reduces compliance friction; it does not rewrite the technical architecture of U.S. healthcare interoperability.

Competitive pressure shifts from certification to product differentiation

Vendors competing with large platforms such as Epic and Oracle Health — including interface and interoperability suppliers such as Rhapsody, InterSystems, and Health Gorilla — can now redirect compliance spending toward product development, implementation services, or pricing concessions. Buyers may gain negotiating leverage if vendors pass through lower certification costs, but should demand evidence rather than accept blanket claims of savings.

The rule also creates less certainty around which certification requirements will remain strategically important as ONC considers future API and successor-technology proposals. Buyers procuring interoperability platforms should ask vendors how they plan to respond to future ONC actions and whether their product road maps depend on federal certification requirements or customer demand.

Carenet Health acquires Invene, adding FHIR integration to patient engagement platform

Carenet Health acquired Invene, a healthcare-focused AI and data-engineering consulting firm, in its 12th corporate acquisition. Invene provides healthcare data architecture, FHIR-based EHR interoperability, data pipelines, predictive modeling, and agentic-AI deployment within HIPAA environments. The acquisition followed Carenet's purchase of conversational clinical-AI company Orbita earlier the same week. The announcement does not disclose a purchase price, funding amount, customer count, or quantified performance result.

The deal combines Carenet's clinical execution, navigation, consumer engagement, and operations scale with Invene's integration and data-engineering capabilities. Buyers seeking a single partner for patient engagement, clinical operations, FHIR integration, and AI deployment may face fewer vendor handoffs. The acquisition also increases concentration risk: customers should clarify whether Invene remains operationally independent, how existing contracts will be supported, and whether Carenet will prioritize proprietary delivery over multivendor interoperability.

Because the transaction lacks disclosed price, revenue, customer, or deployment metrics, it should not by itself justify changing an enterprise's interoperability platform strategy.

What to watch

The immediate enterprise task is not to rewrite interoperability architecture, but to reassess vendor certification road maps, contract protections, and expected pricing as HTI-5 requirements are implemented. Buyers should track which vendors update their products before the December 28 effective date and which delay until January 1 or later. That timing reveals prioritization and operational discipline.

ONC's future proposals on API expansion and successor technologies will determine whether HTI-5 represents lasting deregulation or temporary simplification before a new compliance cycle. Buyers should monitor ONC rulemaking activity in Q1 2027 and require vendors to explain how future certification changes will affect product road maps, pricing, and interoperability commitments. The rule reduces near-term compliance costs; it does not eliminate the strategic importance of standards-based interoperability for enterprise healthcare IT buyers.