Trusted Exchange Framework and Common Agreement Common Agreement Version 2.1
The Common Agreement establishes the legal and governance foundation for nationwide exchange among QHINs, Participants, and Subparticipants, with operating detail supplied by the QTF and standard operating procedures.
What the authority record establishes
The Common Agreement establishes the legal and governance foundation for nationwide exchange among QHINs, Participants, and Subparticipants, with operating detail supplied by the QTF and standard operating procedures.
Contractually binding on signatories and downstream participants according to their agreements and incorporated operating procedures; not a universal mandate to participate
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
A TEFCA buying decision must identify the contracted path, participant role, exchange purpose, downstream obligations, technical services, and operating procedures rather than relying on a generic connectivity label.
Affected operating stages
- QHIN Selection
- Contracting
- Participant Onboarding
- Exchange-Purpose Governance
- Privacy And Security
- Directory Operations
- Dispute And 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
- participants and subparticipants
- health systems
- health plans
- HIEs
- public-health agencies
- health IT developers
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
TEFCA participation and QHIN designation do not establish every service, data class, exchange purpose, or buyer connection.