TEFCA federal agency onboarding lands on CIO desks
HHS says the Department of Veterans Affairs and the Department of War are joining the TEFCA network, handing health system CIOs an exchange partner, and a purpose-of-use question, they did not plan for this budget year.

TEFCA federal agency onboarding stopped being a theoretical question this month. ASTP/ONC published an announcement that HHS welcomed the Department of Veterans Affairs and the Department of War onto the TEFCA network, pitched around faster, more secure exchange for veterans and service members. Federal News Network followed within days with its own coverage, framed less around connectivity and more around health information security. For hospital and health system CIOs, the practical effect is simple and unwelcome: a new category of exchange partner arrived without a line item in the fiscal year plan.
Why a federal participant changes the math
Treatment exchange under TEFCA was an easy yes for most organizations. A clinician at another provider needs the chart, the purpose of use is clean, and the legal and ethical case writes itself. Government participants do not fit that pattern as neatly. Federal agencies bring benefits determination, eligibility verification, service-connected disability review and defense-adjacent workflows, each with its own disclosure logic, minimum-necessary analysis and audit expectation.
The federal government is now both a participant in the framework and the party that sets its rules. That dual role is not inherently a problem, but it does remove the comfortable distance CIOs have had from TEFCA policy decisions. When the rule-setter is also a requester, governance questions that were previously academic become operational ones with a counterparty attached.
None of this is unprecedented. Healthcare IT News reported earlier this year that some Epic health systems already connect to the Social Security Administration through TEFCA, largely to support disability determination records. That was the first clear signal that non-treatment, government-driven use cases would move through the same pipes. The VA and Department of War announcement makes the trend explicit rather than exceptional.
When the rule-setter is also a requester, governance questions that were previously academic become operational ones with a counterparty attached.
The purpose-of-use question most governance documents never asked
Most internal TEFCA governance packets were written to answer a narrower question: do we participate, and through which QHIN. Very few anticipated a request type taxonomy that includes federal benefits adjudication alongside clinical continuity of care. The question leaders need answered in the next quarter is specific. Which federal purposes of use does our organization actually accept, and who signs off, per request type, when a response is contested?
That decision cannot sit with a single function. Health information management owns the release-of-information workflow. Compliance owns minimum-necessary and disclosure accounting. Legal owns the state-law overlays on behavioral health, substance use and reproductive care records. The CIO owns the QHIN configuration that operationalizes whatever the other three decide. If those four are not in the same room with a written matrix, the default configuration becomes the policy by accident.
Leaders should also verify where the Common Agreement stands. The Sequoia Project, acting as recognized coordinating entity, has moved the agreement to Version 2.1, which pushes FHIR-based exchange expectations onto QHINs and their participants. Confirm the current version and effective dates with your QHIN directly rather than relying on summaries, because contractual obligations flow through that document and not through press releases.
Response volume is the second exposure
Records teams at most health systems were sized for a predictable mix of payer audits, provider-to-provider requests, patient access requests and attorney demands. A federal requester with statutory deadlines behaves differently. Volume can arrive in batches, timelines are not negotiable in the way commercial timelines sometimes are, and the reputational cost of a slow response to a veterans benefits query is not comparable to a late payer packet.
The staffing conversation needs to happen before the first large batch, not after a backlog report surfaces it. That means modeling plausible query volume with your QHIN, checking whether automated response rules actually cover the new request types, and deciding in advance which responses require human review. Organizations that treat this as a throughput problem will solve it late and expensively.
There is a related timing problem. Provider IT teams are already absorbing CMS-0057 FHIR API work and ongoing certification churn from the HTI rules. Federal TEFCA onboarding is landing on top of a roadmap that was already full. Something has to be resequenced, and that is a governance decision, not an engineering one.
Standardization is still the constraint underneath all of it
The broader federal health technology ecosystem ambition, and TEFCA within it, keeps running into the same wall: data standardization. Reporting from TechTarget's SearchHealthIT identifies it as the practical bottleneck, and nothing about adding two large federal agencies makes that easier. Agency data models, identity matching practices and document conventions were not built for a shared national framework.
For CIOs, the realistic read is that connectivity will arrive faster than usability. Expect early federal exchange to produce documents that technically satisfy a request while generating downstream manual work on both sides. Plan for reconciliation effort, not for a clean handoff.
What this asks of the CIO role
Healthcare IT News reported this week that CIOs are increasingly being repositioned as enterprise productivity leaders rather than throughput owners. TEFCA federal onboarding is a useful test of whether that framing holds. A throughput owner connects to the network, confirms uptime and reports completion. A value owner asks what the organization is agreeing to disclose, to whom, under what legal theory, and at what operating cost.
The second posture is harder to staff and harder to explain in a board update. It is also the one that prevents a configuration default from becoming a compliance finding. Leaders should treat the VA and Department of War announcement as a prompt to reopen the TEFCA governance file rather than as a news item to forward and forget.


