1upHealth Delivers CMS‑0057 APIs 8 Months Early as Epic Hits 1 Billion TEFCA Records

1upHealth ships full CMS‑0057 API stack to all payer customers

1upHealth is the first interoperability vendor to deploy all four APIs required by the CMS Interoperability and Prior Authorization Final Rule (CMS‑0057‑F) to all health plan customers, putting them fully compliant eight months before the January 1, 2027 federal deadline. The four APIs — Patient Access, Provider Access, Payer‑to‑Payer, and Prior Authorization — are now live in production across 1upHealth's payer customer base.

For payer CIOs, this changes the compliance timeline. CMS‑0057 applies to Medicare Advantage, Medicaid managed care, CHIP managed care, and Qualified Health Plan issuers. Non‑compliance carries civil monetary penalties and corrective action plans. 1upHealth's early deployment means buyers can now add "production deployment of all four CMS‑0057 APIs" as a hard requirement in RFPs, forcing vendors still in pilot or roadmap phases to accelerate or lose deals in 2026‑2027 procurement cycles.

Edifecs launched its Healthcare Interoperability Cloud earlier to support CMS‑0057 and the prior CMS‑9115‑F rule, but "tooling available" is a weaker claim than "all four APIs in production for all customers." Competing platforms — Cleo, Lyniate, Mulesoft healthcare connectors, and in‑house payer builds — now face a time‑to‑regulatory‑readiness gap.

The operational impact is budget timing. Payers can front‑load CMS‑0057 spend into 2026, consolidating legacy API gateways and point integrations into a single FHIR and OAuth/OpenID Connect platform. That frees 2027 budgets for analytics and member experience use cases built on the same APIs, rather than fire‑drill remediation work. It also proves high‑volume FHIR API scaling and established authorization workflows for prior auth and payer‑to‑payer use cases, reducing project risk versus greenfield builds.

Epic hits 1 billion TEFCA records and first SSA connection

Two related developments around Epic and the Trusted Exchange Framework and Common Agreement (TEFCA): HHS reported that national TEFCA‑based networks grew from 10 million health records exchanged to more than 1 billion in under a year. Epic customers became the first in the nation to share medical records with the Social Security Administration (SSA) through TEFCA for disability and benefits determinations.

Epic has connected over 1,000 hospitals to TEFCA. Those hospitals are contributing to the national exchange volume, which increased 100x in less than 12 months. SSA is now pulling clinical data via TEFCA to reduce manual medical evidence collection for millions of annual claims.

For provider CIOs, TEFCA connectivity is now a practical default requirement in RFPs for health information exchanges, APIs, and population‑health platforms. The scale — more than 1 billion records — plus Epic's 1,000‑hospital footprint makes TEFCA the interoperability framework large integrated delivery networks and academic medical centers depend on for federal benefits workflows. Epic strengthens its position against Oracle Health (Cerner), MEDITECH, athenahealth, and Allscripts/Veradigm, especially for organizations with high SSA disability claim volumes.

The SSA use case is a signal of TEFCA's operational maturity. SSA disability determinations are high‑stakes, high‑volume workflows with strict evidentiary requirements. If TEFCA can handle that traffic and data quality bar, it can handle care coordination and quality reporting use cases. That reduces technical risk for health systems evaluating TEFCA participation or selecting exchange partners.

TEFCA's main competitors — CommonWell Health Alliance and Carequality — have long dominated national exchange. eHealth Exchange received the 2026 KLAS Points of Light Award for advancing digital quality measurement via Bulk FHIR, signalling its own advanced capabilities. Epic's first‑mover advantage on SSA connectivity and its 1,000‑hospital footprint create network effects that make TEFCA harder for competitors to displace.

What to watch

For payers: Monitor whether 1upHealth's early CMS‑0057 compliance translates into market share gains in the next 12 months. If it does, expect Edifecs and other vendors to accelerate their own production deployments and publish customer proof points.

For providers: Watch whether other EHR vendors announce SSA connectivity via TEFCA. Oracle Health, MEDITECH, and athenahealth have TEFCA‑aligned programs, but Epic's first‑mover status creates a competitive wedge. If SSA connectivity becomes a standard RFP requirement, Epic's installed base advantage grows.

For both: The 1upHealth and Epic developments show that interoperability is no longer a roadmap item — it is production infrastructure with measurable compliance and exchange volume. Buyers should now benchmark vendors on live API performance, not future capabilities. The time‑to‑compliance window is closing, and the vendors shipping code today are building competitive moats that will be hard to breach in 2027.