To All Articles

TEFCA’s Second Job

Michael Nikitin

CTO & Co-founder AIDA, CEO Itirra

Published on November 16, 2026

SSA’s disability-claims use case shows what a defined TEFCA exchange purpose actually buys a hospital — and what it still doesn’t do on its own.

Somewhere right now, someone is waiting to find out if they qualify for disability benefits. Not long ago, that wait depended on a caseworker chasing down a fax. Now, for a growing number of hospitals, it depends on whether anyone bothered to build the workflow.

Key takeaways

  • What it is: TEFCA’s Government Benefits Determination exchange purpose is a formal, governed category that lets SSA request hospital records for disability-claim decisions.
  • The numbers: as of Aug 13, 2026, SSA had connected to 84 healthcare entities and made 60,595 data requests through TEFCA, per Nextgov/FCW reporting.
  • Baptist Health’s experience: staff needed to handle SSA record requests dropped from 3 full-time employees to roughly half a person after moving to electronic exchange.
  • Not the same as CMS-0057-F: that rule sets its own API-development requirements (compliance mainly from Jan 1, 2027) and doesn’t require any hospital to join TEFCA.
  • What’s still not automatic: every request still depends on consent and authorization, participation terms, technical connectivity, and what records the responding organization makes available.
  • What to check: whether anyone at your hospital owns this exchange purpose by name, or it defaults to whoever picks up the phone that day.
Graphic titled TEFCA's Second Job, showing two exchange-purpose lanes, routine treatment and payment versus Government Benefits Determination, converging on one hospital connection point.
SSA now runs disability-claim record requests through a formally defined TEFCA exchange purpose — a governed, specific use case, not an open pipe.

In February 2026, the Social Security Administration picked eHealth Exchange as its Qualified Health Information Network (QHIN) and said it expected to go live on TEFCA by early spring. SSA’s own framing was modest: electronic exchange, the agency said, can cut disability-claim processing time by more than 50% in many cases. Six months later, that’s not a projection anymore. By August 13, SSA had connected to 84 healthcare entities and made 60,595 data requests through TEFCA. (Those figures come from Nextgov/FCW reporting based on an SSA official — not yet a public SSA dashboard.)

This isn’t a workaround. TEFCA built a door for exactly this. In December 2025, ASTP/ONC, SSA, and TEFCA’s Recognized Coordinating Entity published the Government Benefits Determination Exchange Purpose SOP — a formal category for eligibility decisions on government benefits, with a named sub-purpose for SSA’s Title II (SSDI) and Title XVI (SSI) disability programs. ASTP/ONC says all 11 QHINs will implement updates to align with it. That’s an obligation, not a finish line — but it means a federal agency reading your hospital’s records for a disability decision is now a governed, defined use case. Not an open door. A specific one, with a lock and a key.

Timeline showing SSA selecting eHealth Exchange as its QHIN in February 2026, ASTP/ONC publishing the Government Benefits Determination Exchange Purpose SOP in December 2025, and SSA's reported operating figures in August 2026.
From a named exchange purpose on paper to 84 entities and 60,595 requests in under a year — governance came first, volume came after.

Why Should a Hospital That Isn’t SSA’s Customer Care?

Because it’s a preview of what a shared exchange framework is actually for: adding a new, defined use case to infrastructure that already exists, instead of making every organization build a separate pipe for every new purpose. That’s the promise. It isn’t automatic. Every request still depends on the applicable exchange purpose, the claimant’s consent and authorization, the organization’s participation terms, technical connectivity, and what records the responding organization actually makes available.

Two-box comparison card titled Governed, Not Automatic, contrasting what TEFCA's Government Benefits Determination exchange purpose defines against the consent, participation, and connectivity conditions that still have to be met on every request.
A defined exchange purpose is permission to build the workflow — not proof the workflow runs itself.

So the real question for a hospital isn’t “are we connected.” It’s “who owns this when it shows up.” A named person. A workflow that knows the difference between a routine record request and a disability determination. Someone watching the volume before it becomes a backlog. Baptist Health’s story is the clearest public answer to what happens when that ownership exists.

What Three People Used to Do, Half a Person Does Now

Baptist Health in Jacksonville, Florida started sharing records with SSA through TEFCA at the end of July 2026. Its chief digital and information officer told Nextgov/FCW the system had sent several thousand electronic medical records — and that the staff needed to handle SSA requests dropped from three full-time employees to essentially half a person.

That’s one organization’s story, not an industry average. But it’s a real one: three people used to spend their days pulling records, faxing them, and confirming receipt, so that someone waiting on a disability decision could eventually get an answer. Now it takes half a person, and the record moves in minutes instead of weeks.

Metric Before electronic exchange Baptist Health, reported Aug 2026
Staff dedicated to SSA record requests3 full-time employees~0.5 FTE
Record delivery methodFax, mailed copiesElectronic, seconds to minutes
Records sent (since late July 2026)—Several thousand
National SSA/TEFCA volume (as of Aug 13, 2026)—84 entities connected, 60,595 requests; 11 QHINs implementing alignment updates for the Government Benefits Determination purpose
Somewhere, a disability claimant is waiting on a fax. TEFCA just made that wait optional — if your hospital knows how to use it.

Where CMS-0057-F Fits — and Where It Doesn’t

CMS-0057-F and TEFCA are not the same rule wearing two names. CMS-0057-F sets API-development and enhancement requirements for impacted payers, with compliance dates primarily beginning January 1, 2027. It doesn’t require a hospital to join TEFCA or keep a “live TEFCA pipe.” They push the same direction — more standardized, machine-readable exchange — but neither one makes the other mandatory.

Here’s the payoff of that direction, in plain terms: once an organization can move records electronically through an approved pathway, a brand-new, federally defined use case can cost far less to support than building a new fax-and-follow-up process from scratch. That’s the whole argument for treating interoperability as real infrastructure, owned by someone, instead of a box you checked once for a deadline.

What to Check Before This Becomes a Cost Instead of a Win

  • Does your organization know which TEFCA Exchange Purposes and workflows it’s actually configured to support — including, where applicable, Government Benefits Determination?
  • Is there a named owner for new, non-routine request types, or does it default to whoever picks up the phone that day?
  • Do your consent and authorization processes tell one exchange purpose from another, or does every request get handled the same way regardless of who’s asking?
  • If SSA’s request volume showed up at your door tomorrow, would anyone notice — or would it just quietly become next month’s backlog?

These aren’t technology questions. The technology exists; TEFCA’s governing bodies did that work. What varies, hospital to hospital, is whether anyone actually owns what comes through the pipe.

TEFCA built the door. Nobody walks through it for you.

Frequently Asked Questions

Is my hospital required to share records with SSA through TEFCA?

No separate SSA-specific mandate applies to hospitals simply because they’re TEFCA-connected. Whether an organization can exchange records with SSA depends on its exchange pathway, participation arrangements, technical readiness, the applicable exchange purpose, the claimant’s consent and authorization, and organizational policy. Confirm current status with your QHIN, EHR/network provider, and legal or privacy team.

Does this replace HIPAA-authorized record requests?

It changes the transport and workflow, not the underlying privacy and authorization obligations. For SSA disability determinations, public reporting indicates claimant consent is part of the exchange process. HIPAA, applicable state privacy law, TEFCA participation terms, and organizational policy all still govern what can be disclosed and how.

Which EHR vendors currently support this?

Epic publicly reported that more than 65% of its customers were already sharing records with SSA across TEFCA, Carequality, and eHealth Exchange combined. An Epic spokesperson projected that more than 550 hospitals and nearly 20,000 clinics would use TEFCA to exchange data with SSA by the end of August 2026. Nextgov/FCW reported that eClinicalWorks and NetSmart were in development and testing stages with SSA as of August. Check directly with your vendor for a current timeline.

Does higher SSA request volume mean my hospital is doing something wrong?

No. Higher volume can mean the workflow is working. It should still be monitored — turnaround time, exceptions, consent or authorization issues, staffing load — but volume by itself isn’t a red flag. It’s a sign someone is actually asking.

Does your organization know which TEFCA Exchange Purposes and workflows it’s actually configured to support, including, where applicable, Government Benefits Determination?

Ready to talk?

Let’s talk about your project.

If nobody owns what comes through your TEFCA pipe yet, we can help you build that ownership — before volume turns into backlog.

Contact Itirra →

Sources

  1. “TEFCA Government Benefits Determination Implementation Is Here!” — ASTP/ONC, Dec 9, 2025 — official source for the Government Benefits Determination Exchange Purpose SOP, its SSA Title II/Title XVI sub-categories, and the 11 QHINs’ implementation obligation under QHIN Technical Framework v2.1.
  2. “Social Security Joins TEFCA Network to Improve Disability Decision Processing” — Social Security Administration, Feb 17, 2026 — source for SSA’s QHIN selection (eHealth Exchange), its expected spring 2026 go-live, and the “more than 50%” processing-time claim.
  3. “Social Security expands electronic health record sharing to speed up disability claims adjudication” — Nextgov/FCW, Aug 2026 — reporting based on an SSA official, Baptist Health’s CDIO, and an Epic spokesperson; source for the 84-entity/60,595-request figures, Baptist Health’s staffing experience, Epic’s rollout projection and the 65% cross-network sharing figure, and eClinicalWorks/NetSmart status.
  4. “Social Security expands electronic health record sharing to speed up disability claims adjudication” — Government Executive, Aug 2026 — companion reporting, same underlying figures.
  5. “What Is TEFCA? How Will It Change the Healthcare Industry?” — Itirra — earlier explainer, internal continuity, not a source for the new claims above.