Guide

TEFCA and HIEs: what participation gets a practice of one

Summary

No — a solo practice already meets its legal floor through the information-blocking rule's portal and API requirements without joining anything. TEFCA and regional HIEs are additive, not required: they're worth evaluating for the care-coordination payoff, mainly visibility into ED visits and hospital discharges you'd otherwise never see, not for compliance. Whether you can join is often decided by your EHR vendor's existing network participation before you make an active choice at all.

By Gale Editorial · Updated 2026-07-27. Every figure cited to a dated source. How we write.

Not required — this is additive, not compliance

TEFCA and regional health information exchanges sit on top of the baseline obligation the information-blocking rule already imposes on you through your portal and patient-directed API — joining a network isn't a separate legal requirement layered on that baseline, it's an optional expansion of who can see your data and whose data you can see 1Ref 1Office of the National Coordinator / ASTP (2026).Information Blocking.That the information-blocking rule's portal and API requirements are the compliance floor a solo practice must meet independent of any HIE or TEFCA network participation.. A solo practice that has never joined an HIE and never will can be fully compliant with information blocking simply by keeping its own portal and API working correctly.

That distinction matters because vendors and consultants sometimes present HIE participation as something you're behind on, when for a genuinely solo outpatient practice it's closer to an optional productivity tool than an obligation.

What TEFCA actually establishes

TEFCA sets a national floor for network-to-network exchange: Qualified Health Information Networks (QHINs) connect to each other under one common agreement, so a query from one QHIN's participant can reach patient data sitting behind any other QHIN, rather than requiring a separate bilateral agreement with every regional network in the country 2Ref 2Office of the National Coordinator / ASTP (2026).TEFCA — Office of the National Coordinator for Health Information Technology.That TEFCA establishes a national floor for network-to-network exchange via QHINs, connecting regional networks under one common agreement.. Before TEFCA, HIE participation meant joining whichever regional network your area happened to have; TEFCA is designed to make that patchwork interoperable.

A regional HIE and a QHIN aren't necessarily different things — many regional HIEs are becoming QHIN participants themselves, which is what actually delivers the reach TEFCA promises down to an individual solo practice's EHR.

You may already be "in" without deciding anything

Check your EHR contract and vendor relationship before assuming participation is a decision still in front of you — many EHR vendors, especially ones built for a platform of many small practices rather than a true solo build, already participate in a QHIN or regional HIE on behalf of every practice on their system, sometimes as a default with an opt-out rather than an opt-in. Whether platforms vs true solo software makes this automatic or manual is worth confirming directly with your vendor rather than assuming either way.

If your vendor already participates, the practical question shifts from "should I join" to "is my configuration exposing or receiving what I actually want," which is a settings conversation, not a new agreement to sign.

Where the real payoff shows up for a solo practice

The clearest value for a behavioral health or primary care solo practice is visibility into care that happens outside your walls entirely — an ED visit, a psychiatric hospitalization, a discharge summary from a facility that has no reason to fax you anything unless you ask. HIE participation can surface that automatically instead of leaving you to find out weeks later from the patient, which is exactly the gap the discharge stream describes from the referral-relationship side.

If your patient population rarely touches other care settings — a stable private-pay caseload with infrequent hospitalizations — the payoff is smaller, and the administrative overhead of managing a new network connection may not be worth it yet.

How this differs from direct secure messaging

Direct secure messaging and HIE/TEFCA participation solve different problems and aren't substitutes for each other: what is direct secure messaging comes down to sending a specific document to a specific known recipient, like a referral letter to a colleague, while network participation is about discoverability — pulling relevant records from wherever they exist, from clinicians you may not have a prior relationship with at all.

A solo practice with strong direct-messaging relationships with its regular referral partners may get less incremental value from full HIE participation than one whose patients frequently show up in facilities the practice has no existing relationship with.

Security and contract questions before opting in

Joining a network is a new channel PHI moves through, which means it belongs in your next security risk assessment rather than being treated as a pure IT switch flipped by your vendor — confirm what data flows out by default, what you can restrict, and who at your practice can see incoming records from other participants 3Ref 3HHS Office for Civil Rights (2026).Summary of the HIPAA Security Rule.That the Security Rule requires a risk analysis covering each channel PHI moves through, including a new network connection created by joining an HIE or QHIN.. The participation agreement itself, usually routed through your EHR vendor's own QHIN or HIE relationship, is a contract worth reading rather than accepting as boilerplate 4Ref 4Office of the National Coordinator (2016).EHR Contracts Untangled: Selecting Wisely, Negotiating Terms, and Understanding the Fine Print.ONC's guidance on negotiating EHR and vendor contract terms, used here for reviewing an HIE or QHIN participation agreement's fee and data terms before opting in..

Ask specifically whether joining changes your BAA relationship with the vendor, whether there's a fee tied to query volume, and whether you can pull records without also pushing your own patients' data out by default — the answer varies by vendor and is worth confirming rather than assuming.

A simple way to decide

Ask three questions: does your EHR already participate somewhere, does your patient population regularly touch care settings you have no existing relationship with, and does the security and contract review clear without surprises. Two or three "yes" answers make participation worth pursuing actively; a practice answering "already participating" to the first question often has nothing further to decide beyond configuration.

Revisit the question periodically rather than deciding once — a solo practice's referral pattern and its EHR vendor's network relationships both change over a few years, and a "not worth it" answer today isn't permanent.

Common questions

As of mid-2026, TEFCA participation remains voluntary for individual clinicians and practices; it isn't a separate legal mandate the way the information-blocking rule's portal and API requirements are. Certain federal programs and larger health systems face different incentives to participate, but a solo outpatient practice isn't independently required to join.

No — most networks operate on a query basis where a requesting participant needs a permitted purpose (typically treatment) and pulls only what's relevant to that purpose, not your entire record by default. Configuration varies by network and vendor, which is exactly why reviewing the specific participation terms before joining matters.

It depends entirely on your vendor and network — some EHR vendors include HIE or QHIN connectivity in a standard subscription tier, while others charge separately or tie fees to query volume. Confirm the specific cost structure in your contract rather than assuming it's bundled or free.

Some networks and vendor configurations support a query-only or asymmetric arrangement, but it isn't universal — many participation agreements expect reciprocal availability of your own patients' data as a condition of pulling others'. Ask your vendor directly whether an asymmetric setup is available before assuming it is.

Run your practice on Gale

The software is free. Gale earns one flat 3.5% all-in per paid transaction — only on transactions that actually pay. No subscription, no setup fee, no network cut.

Start or manage a practice →

References

1.Office of the National Coordinator / ASTP (2026). Information Blocking. HealthIT.gov. link ✓That the information-blocking rule's portal and API requirements are the compliance floor a solo practice must meet independent of any HIE or TEFCA network participation.
2.Office of the National Coordinator / ASTP (2026). TEFCA — Office of the National Coordinator for Health Information Technology. HealthIT.gov. link ✓That TEFCA establishes a national floor for network-to-network exchange via QHINs, connecting regional networks under one common agreement.
3.HHS Office for Civil Rights (2026). Summary of the HIPAA Security Rule. U.S. Department of Health and Human Services. linkThat the Security Rule requires a risk analysis covering each channel PHI moves through, including a new network connection created by joining an HIE or QHIN.
4.Office of the National Coordinator (2016). EHR Contracts Untangled: Selecting Wisely, Negotiating Terms, and Understanding the Fine Print. HealthIT.gov (ONC). link ✓ONC's guidance on negotiating EHR and vendor contract terms, used here for reviewing an HIE or QHIN participation agreement's fee and data terms before opting in.

https://www.gale.care/for-providers/cde-tefca-hie-participation · 4 sources. Competitor details are cited to dated public sources and maintained as they change; figures are estimates, not commitments. Synthetic demonstration.

← Back to for providers