Verified steps

Register the organization as a Participant or Sub-participant with a recognized QHIN (e.g., CommonWell, eHealth Exchange, Carequality, Kno2, Epic) and complete the required TEFCA Common Agreement onboarding and identity assurance requirements
Configure the connection to the QHIN's FHIR exchange endpoint, including the required TEFCA authorization headers identifying the Participant, purpose of use (treatment), individual access, and patient consent acknowledgment
Submit a patient-level FHIR query (e.g., Patient/$everything or targeted resource queries) to the QHIN, which federates the query to connected networks and aggregates responses from responding organizations
Process the aggregated FHIR Bundle response, handling duplicate resources from multiple responding organizations by using provenance metadata and source identifiers to deduplicate and attribute data
Implement TEFCA-required audit logging capturing the query requestor identity, patient, purpose of use, timestamp, responding organizations, and data classes returned for regulatory compliance

Known gotchas

TEFCA exchange requires a signed QHIN Technical Framework (QTF) agreement and organizational identity assurance; technical integration cannot begin until legal onboarding is complete with the chosen QHIN
Query responses are not real-time aggregations; QHINs fan out queries asynchronously and some responding nodes may not respond within the timeout window, resulting in partial data sets without error indication
TEFCA treatment purpose queries do not require explicit patient consent at the time of query but do require the requestor to have a treatment relationship with the patient; querying without a valid treatment relationship violates the TEFCA Common Agreement

Request clinical documentation via Da Vinci CDex task-based exchange

hl7.org/fhir/us/davinci-cdex · 5 steps · unrated

Implement a FHIR-based care coordination workflow using Task resources to assign, track, and complete referral tasks between a referring provider and a specialist, with ServiceRequest linking the clinical order to the task

hl7.org/fhir · 5 steps · unrated

Give your agent this knowledge — and 200+ more routes

One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Implement TEFCA QHIN-facilitated exchange by submitting and receiving FHIR queries through a QHIN participant connection for a treatment purpose treatment of care use case

Verified steps

Known gotchas

Related routes

Give your agent this knowledge — and 200+ more routes