Change record: HHS releases HTI-5 proposed rule

What changed

HTI-5 proposes certification, information-blocking, and standards-based API changes but remains a proposed rule as of the publication's July 19, 2026 cutoff.

This entry preserves the event separately from maintained provider and capability conclusions. A rule, announcement, release, enforcement record, or market transaction can be material before enough evidence exists to revise a company classification or comparison.

Operating consequence

Organizations may use the proposal for scenarios, but should not record its provisions as binding requirements or treat vendor roadmaps as compliance evidence.

Teams should identify which records, populations, systems, transactions, jurisdictions, products, or decisions fall within the change. Then assign an accountable owner, response date, evidence requirement, and disposition. Broad reassessment is not always necessary, but a material event deserves a documented decision.

Capabilities to revisit

FHIR Profile And Implementation-Guide Support

Review the maintained workflow definition, then ask affected organizations to show how this event alters inputs, governed rules, human judgment, exceptions, action, evidence retention, and downstream exchange for FHIR profile and implementation-guide support.

SMART On FHIR Authorization

Review the maintained workflow definition, then ask affected organizations to show how this event alters inputs, governed rules, human judgment, exceptions, action, evidence retention, and downstream exchange for SMART on FHIR authorization.

Conformance Testing And Validation

Review the maintained workflow definition, then ask affected organizations to show how this event alters inputs, governed rules, human judgment, exceptions, action, evidence retention, and downstream exchange for conformance testing and validation.

Operational Monitoring And Exception Management

Review the maintained workflow definition, then ask affected organizations to show how this event alters inputs, governed rules, human judgment, exceptions, action, evidence retention, and downstream exchange for operational monitoring and exception management.

Questions for operating teams

• Which exact population and effective date does the source establish?
• Does the change alter authority, policy, content, workflow, integration, evidence, or only market positioning?
• What customer-controlled interpretation, configuration, or process remains outside a provider's responsibility?
• What test case would show whether the operational consequence has reached production?
• What record will close, defer, or supersede this review?

Evidence boundary

The source class is Federal proposed-rule announcement. It establishes only the statements supported by the linked record and does not, by itself, establish implementation depth, market-wide availability, transaction-specific applicability, independent efficacy, or a universal buyer conclusion.