AHA Shares Recommendations with ASTP/ONC on HTI-5 Proposed Rule

Why It Matters

AHA’s input could shape federal policy that determines how quickly hospitals adopt interoperable standards, directly affecting data exchange efficiency and patient care continuity.

Key Takeaways

• AHA urges phased transition to FHIR certification criteria
• Maintain existing privacy and security requirements
• Keep current information‑blocking definition and third‑party exception
• Remove provider‑centric information‑blocking penalties
• Rule aims to deregulate and boost API interoperability

Pulse Analysis

The HTI‑5 proposal represents a pivotal shift in U.S. health‑IT policy, moving away from prescriptive certification models toward a more flexible, outcomes‑driven framework. By encouraging the use of FHIR‑based APIs, the rule aligns with industry momentum toward modular, cloud‑native solutions that can exchange data across disparate electronic health record (EHR) systems. AHA’s recommendation for a reasonable glidepath acknowledges that hospitals need time and resources to re‑engineer legacy interfaces, reducing the risk of costly disruptions while still advancing national interoperability goals.

Privacy and security have remained non‑negotiable pillars of health information law, and AHA’s insistence on preserving current criteria reflects broader stakeholder concerns about data breaches and patient trust. The organization’s stance signals that any deregulation effort must retain robust safeguards, ensuring that accelerated data sharing does not compromise confidentiality. Moreover, retaining the existing information‑blocking definition, including the “third‑party seeking modification infeasibility” exception, provides clarity for providers navigating compliance while fostering a more collaborative ecosystem.

Finally, the call to repeal imbalanced provider disincentives addresses a long‑standing tension between regulatory enforcement and practical workflow realities. By removing punitive measures that disproportionately affect clinicians, the rule could encourage more proactive participation in data exchange initiatives. If adopted, these recommendations may accelerate the transition to interoperable, FHIR‑centric architectures, ultimately driving cost efficiencies, improving care coordination, and supporting the broader goal of a more connected health‑care landscape.