HEALTH INTEROPERABILITYREVIEW

Move data. Preserve meaning. Prove the exchange.

United States · U.S. federal proposed rule

Health Data, Technology, and Interoperability: ASTP/ONC Deregulatory Actions to Unleash Prosperity

HTI-5 proposes changes to the ONC Certification Program, information-blocking regulations, and standards-based API foundations. Its provisions remain proposals as of the seed date.

What the authority record establishes

HTI-5 proposes changes to the ONC Certification Program, information-blocking regulations, and standards-based API foundations. Its provisions remain proposals as of the seed date.

Not a current binding requirement; existing regulations remain controlling unless and until amended by a final rule

The exact official title, issuing body, jurisdiction, version or application record, and linked source define the scope of this page. Readers should not transfer the authority's status to a commercial product or infer transaction-, patient-, system-, site-, or organization-specific applicability from this summary.

Why it matters to this market

The proposal can inform scenario planning, but vendors and buyers must not describe proposed removals or new API provisions as settled current requirements.

Affected operating stages

  • Regulatory Monitoring
  • Scenario Planning
  • Product Roadmap
  • Certification Planning
  • Information-Blocking Policy

Capabilities to examine

FHIR Server And Repository

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for FHIR server and repository.

FHIR API Gateway And Orchestration

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for FHIR API gateway and orchestration.

FHIR Profile And Implementation-Guide Support

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for FHIR profile and implementation-guide support.

Conformance Testing And Validation

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for conformance testing and validation.

Operational Monitoring And Exception Management

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for operational monitoring and exception management.

Affected buyer audiences

  • certified health IT developers
  • providers
  • networks and exchanges
  • API platform teams
  • policy and compliance leaders

Implementation questions

  • Which entities, products, populations, transactions, systems, sites, or jurisdictions are actually within scope?
  • What is binding, what is guidance, and what is a technical or consensus standard?
  • Which publication, adoption, effective, application, transition, and enforcement dates differ?
  • Who owns legal, clinical, quality, regulatory, policy, or operational interpretation?
  • How will a source revision affect open work and historical decisions?

Interpretation boundary

No proposed HTI-5 provision is recorded as a current final requirement.