EHR Compliance / Comments

VA and Department of War Go Live on Oracle Health Information Network: What Federal TEFCA Exchange Means for Your EHR Team

A glowing map of the United States with connected network hubs linking health care facilities, with a workstation in the foreground merging incoming records into one chart.

On November 5, 2026, the U.S. Department of Veterans Affairs (VA) and the Department of War (DoW) began participating in Oracle Health Information Network, a designated Qualified Health Information Network (QHIN) under the Trusted Exchange Framework and Common Agreement (TEFCA). Oracle announced the go-live on November 13 (Oracle). Some coverage still refers to the Department of Defense (DoD), and the health care side of that department is the Military Health System (MHS).

The practical change is simple to state. Federal clinicians now have a single connection point to community health data from TEFCA participants, beyond what the existing Joint Health Information Exchange (JHIE) already provided (HIT Consultant). If your organization treats veterans, service members, or their beneficiaries, the federal side of that relationship just became easier to reach. Whether you can reach it back depends on your own connections, and that is the part worth checking now.

At a glance

What changed: VA and DoW went live on Oracle Health Information Network, a TEFCA QHIN, on November 5, 2026. Federal clinicians can query TEFCA participants through one connection.

Who should care: Any hospital, clinic, or practice that shares patients with VA or military treatment facilities, regardless of which EHR you run.

What to do, in order:

  1. Confirm whether your organization participates in TEFCA, and through which QHIN or intermediary.
  2. Confirm which exchange purposes your connection supports and how you respond to each.
  3. Review how incoming external records are reconciled into your chart.
  4. Bring your privacy and security officers into the conversation before volume grows.

What actually went live

Oracle Health Information Network is the QHIN Oracle operates under TEFCA. VA and DoW connect to it once, and through it they can exchange with participants across other QHINs (ExecutiveGov). The connection builds on JHIE rather than replacing it, so existing federal exchange arrangements continue alongside the new path (HIT Consultant).

On the ingestion side, the federal deployment pairs the network with Oracle Health Seamless Exchange. Oracle describes Seamless Exchange as the layer that deduplicates incoming records and lets clinicians review and selectively reconcile them into the primary EHR chart (Oracle). That matters more than it sounds. Anyone who has supported a clinical team flooded with duplicate CCDs from an HIE feed knows that more data is not automatically better data. A reconciliation step that lets the clinician decide what lands in the chart separates useful interoperability from a cluttered record nobody trusts.

One detail deserves caution. Coverage of the go-live describes clinicians reviewing items such as medical images and medications over time. The same source material also describes images, medications, and other high-bandwidth artifacts as a future expansion, with longitudinal clinical records from TEFCA participants as the initial scope. Until VA, DoW, or Oracle publishes a clearer scope statement, treat image exchange in particular as a roadmap item rather than something your radiology team should plan around today.

Why a single connection matters

For non-technical readers, here is the short version. TEFCA is a "network of networks." Instead of every organization building and maintaining point-to-point interfaces with every other organization it shares patients with, each participant connects to a QHIN, and the QHINs exchange with each other under a common set of rules (ASTP/ONC).

For a federal system the size of VA and MHS, that is a significant reduction in interface sprawl. It also connects them to a large existing network. Reporting on the HHS announcement states that TEFCA has supported billions of exchanges since late 2023 and now includes nearly 25,000 organizations and roughly 110,000 connections (HIT Consultant; ExecutiveGov).

The go-live also fits within VA's ongoing move to the Oracle Health EHR, which has included multiple site deployments in 2026 (GovCIO Media). Choosing the same vendor's QHIN is a logical fit for VA and DoW. It does not mean community providers need to be on Oracle Health to exchange with them, because TEFCA is designed for exchange across QHINs.

The benefits determination angle

The detail community providers are most likely to miss is in the federal health IT office's own write-up. VA participation is expected to extend to the Government Benefits Determination exchange purpose, for example in support of the Veterans Benefits Administration (HealthIT.gov).

Exchange purposes are defined in TEFCA's standard operating procedures (SOPs), and treatment, health care operations, and Government Benefits Determination are among them. Each one is a separate reason a request can arrive at your organization. If your TEFCA connection was set up primarily with treatment queries in mind, a benefits determination request is a different kind of request, and your release of information, privacy, and HIM staff should know how your organization handles it before one shows up. The research available at publication does not confirm when this use case will be live, so this is preparation rather than an emergency.

If you are not on Oracle Health

Most readers are not running Oracle Health, and many smaller organizations are not sure whether they participate in TEFCA at all. The federal go-live does not connect you to anything by itself. Direct participation depends on your own connection, which typically comes through your EHR vendor, a regional HIE, or another intermediary that participates through a QHIN.

Consider a 25-bed Critical Access Hospital in a county with a sizable veteran population, with one IT generalist and an EHR hosted by its vendor. That hospital may already be connected to TEFCA without anyone on staff knowing it, because the vendor enabled it. Or it may be connected only to a regional HIE that does not reach federal systems. The only way to know is to ask, and to get the answer in writing: who is your QHIN, which exchange purposes are enabled, and who in your organization is notified when external requests are answered.

For Oracle Health customers, Oracle states that connecting to its QHIN is a free opt-in through its Connection Hub (Oracle). That is a vendor claim about its own offering, so confirm contract terms and any implementation effort with your account team. Customers of other EHR platforms should ask their vendors the same questions about their own TEFCA path.

What to do now

  1. Inventory your current federal exchange. Document any existing JHIE connectivity, direct interfaces, or HIE feeds that touch VA or military treatment facilities, and note your TEFCA participation status.
  2. Map your exchange needs to TEFCA exchange purposes. List what you actually need (treatment, health care operations, responding to benefits determination requests) and confirm each is supported and governed by policy.
  3. Look at reconciliation, not just connectivity. Whether you use Seamless Exchange or another platform's tooling, decide how external records, medications, and documents get reviewed before they become part of the chart.
  4. Watch volume and performance after any new connection. Monitor query volume, document counts, and any slowdown in clinician-facing workflows, and set a baseline before you turn anything on.
  5. Involve compliance and clinical informatics early. Incoming data and outgoing responses both carry protected health information, so privacy and security controls need to be reviewed alongside the technical setup.
  6. Track updates from ASTP/ONC and The Sequoia Project. New SOPs and QHIN changes can affect what requests you receive and how you are expected to respond.

Regulatory and compliance context

TEFCA operates under the nationwide interoperability framework established by the 21st Century Cures Act (ASTP/ONC). Participating does not replace HIPAA. Protected health information exchanged through a QHIN remains subject to the HIPAA Privacy and Security Rules in 45 CFR Part 164, and TEFCA participants must also meet the Common Agreement's requirements for secure exchange.

In practical terms, a new exchange pathway is a change to how electronic protected health information enters and leaves your environment. Treat it the way you would treat any new interface: update your risk analysis and system inventory, confirm who can access the exchange tooling, and make sure your policies cover each exchange purpose you have enabled.

What we do not know yet

Public detail beyond vendor and agency statements is thin. Commentary on X has come mostly from Oracle Health and stock-focused accounts, and we found no independent practitioner feedback on integration challenges or data volume. Open questions include the technical integration between VA and DoW EHR systems and the network, current exchange volume since go-live, any implementation issues reported by federal IT teams, the timeline for image and medication payloads, and when the benefits determination use case goes live. We will update coverage as federal IT teams or community participants report real-world results.

This article is for informational purposes only and does not constitute legal or compliance advice. Covered entities and business associates should consult qualified legal counsel or compliance professionals before making decisions pertaining to HIPAA or IT infrastructure.

Sources

  • Oracle, "Dept. of Veterans Affairs and Dept. of War Go Live on Oracle Health Information Network": oracle.com
  • HIT Consultant, VA and Department of War go live on Oracle Health Information Network TEFCA QHIN: hitconsultant.net
  • HIT Consultant, HHS welcomes VA and Defense to TEFCA network: hitconsultant.net
  • ExecutiveGov, VA, DoW, HHS TEFCA health information network: executivegov.com
  • HealthIT.gov, VA joins TEFCA to advance health information exchange for veterans: healthit.gov
  • HealthIT.gov, Trusted Exchange Framework and Common Agreement (TEFCA): healthit.gov
  • Oracle Health, QHIN interoperability: oracle.com
  • GovCIO Media, VA and DoW join TEFCA to expand nationwide health data exchange: govciomedia.com
  • Electronic Code of Federal Regulations, 45 CFR Part 164: ecfr.gov
TEFCA
QHIN
Oracle Health
Oracle Health Information Network
Department of Veterans Affairs
Military Health System
Joint Health Information Exchange
Health Information Exchange
interoperability
HIPAA

About the Author

Health Tech Authority Editorial Team

Health Tech Authority is a publication covering the technology side of health care organizations. We exist for the people in the mix - the systems administrators keeping servers online at 2 AM, the network engineers segmenting clinical VLANs on a shoestring budget, the security officers trying to hold the HIPAA line with half the resources a comparably sized non-health care organization would have, and the IT managers and administrators making technology decisions that directly affect patient care.

Content published under this account represents collaborative editorial work produced by the Health Tech Authority team. That includes original reporting, technical analysis, regulatory coverage, and practitioner-focused guidance across our core coverage areas: infrastructure and systems administration, networking, security and compliance, cloud and Microsoft 365 administration, clinical systems and health data, and the broader technology landscape serving health care organizations.

We cover what health care IT professionals actually need to know, written in a way that respects both their time and their intelligence. No fluff, no vendor press release rewrites, no thought leadership buzzword soup - just straightforward coverage of the systems, tools, and decisions that keep health care organizations running.

If you have a topic suggestion, a correction, or want to contribute, reach out through the Contact page.