Change record: ASTP/ONC confirms HTI-2 final scope and withdrawn proposals
The final HTI-2 action centers TEFCA-related definitions and 45 CFR Part 172; unfinalized proposals were withdrawn and the TEFCA Manner Exception remains unchanged.
What changed
The final HTI-2 action centers TEFCA-related definitions and 45 CFR Part 172; unfinalized proposals were withdrawn and the TEFCA Manner Exception remains unchanged.
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
Compliance summaries and product roadmaps must remove broad proposed provisions that did not become final requirements and add TEFCA governance controls where applicable.
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
TEFCA And QHIN Connectivity
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 TEFCA and QHIN connectivity.
Consent, Authorization, And Data Segmentation
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 consent, authorization, and data segmentation.
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.
Data Quality, Lineage, And Provenance
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 data quality, lineage, and provenance.
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 final-rule summary. 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.