Health Data, Technology, and Interoperability: Trusted Exchange Framework and Common Agreement
HTI-2 finalizes TEFCA-related definitions, establishes 45 CFR Part 172 provisions supporting TEFCA reliability, privacy, security, trust, and transparency, and leaves the TEFCA Manner Exception unchanged.
What the authority record establishes
HTI-2 finalizes TEFCA-related definitions, establishes 45 CFR Part 172 provisions supporting TEFCA reliability, privacy, security, trust, and transparency, and leaves the TEFCA Manner Exception unchanged.
Binding within the finalized provisions, including new 45 CFR Part 172 requirements and amended definitions
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 final rule makes regulatory status and formal network governance a first-class buying question. It also demonstrates why withdrawn proposals cannot be presented as current requirements.
Affected operating stages
- Network Governance
- Participation Agreements
- Privacy And Security
- Information-Blocking Analysis
- Transparency
- Change Management
Capabilities to examine
TEFCA And QHIN Connectivity
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 TEFCA and QHIN connectivity.
Patient Identity And Record Matching
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 patient identity and record matching.
Provider Directory And Endpoint Discovery
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 provider directory and endpoint discovery.
Consent, Authorization, And Data Segmentation
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 consent, authorization, and data segmentation.
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
- QHINs
- TEFCA participants and subparticipants
- health information networks
- health IT developers
- privacy and compliance teams
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
HTI-2 does not establish a universal TEFCA product requirement or prove one organization's compliance or exchange availability.