On October 21, 2026, the Departments of Labor and Health and Human Services announced that five large employers with self-funded group health plans signed a statement of support for expanding electronic prior authorization (ePA) into the ERISA market. DOL’s release names Amazon, Axon Enterprise, Google, Meta, and Oracle as signatories. CMS and HHS posted matching announcements the same day.

If you administer medical benefits for self-insured employers, this is not a new federal mandate for your book of business—but it is a clear nudge from EBSA and CMS that fax-and-phone prior auth is on the way out for large commercial payers, and self-funded sponsors do not want to be the last workflow standing.

What actually happened (and what did not)

The October 21 package is a voluntary employer statement, not a proposed or final ERISA rule. No compliance date applies to every self-funded plan in the country.

What it does do:

DOL’s release summarizes six pledge reforms, including standardizing prior authorization submissions, reducing the volume of procedures that require preapproval, and ensuring clinical professionals review clinical denials. It also explicitly calls on TPAs to improve transparency and communication around authorization decisions and appeals.

Employers that did not sign are unaffected on Day One. Employers that did sign—or that compete for talent with companies that did—will start asking vendors hard questions anyway.

Why self-funded plans sit in a different lane than CMS “impacted payers”

Most self-funded arrangements are ERISA welfare plans. They are not the same population as the “impacted payers” subject to CMS-0057-F (the Interoperability and Prior Authorization final rule published at 89 FR 8758 on February 8, 2024).

That rule requires certain Medicare Advantage, Medicaid/CHIP, and FFE qualified health plan issuers to stand up FHIR-based APIs and related prior-auth operations. CMS’s fact sheet states that many API requirements land on compliance dates beginning January 1, 2027, with operational provisions phasing in around January 1, 2026 for some payer types.

Self-funded ERISA plans generally sit outside those CMS payer regulations. Your medical TPA might still be building CMS-style ePA pipes because the same vendor administers fully insured or government lines—or because providers demand one electronic front door regardless of funding type.

The October 21 statement is the administration’s attempt to pull self-funded volume into the same modernization lane without waiting for a separate ERISA rulemaking.

Scale: why TPAs feel this even when the law does not change

HHS cites U.S. Census figures that more than 53% of Americans—180 million-plus people—get coverage through employers sponsoring self-funded plans. DOL repeats that self-funded sponsors “frequently rely on third-party administrators” for prior authorization.

Translation for TPAs:

How this connects to the 2025 insurer pledge and 2027 payer APIs

The employer statement tracks the 2025 Prior Authorization Pledge, where national carriers committed to standardize electronic prior auth, shrink the prior-auth universe, improve transparency, and increase real-time responses. CMS’s October release ties that voluntary market work to the mandatory 2027 API work for impacted payers.

For a self-funded employer, the practical path usually runs through the TPA or utilization-management vendor, not through a CMS compliance calendar. But providers experience one patient, one prior-auth workflow. When Medicare Advantage and Marketplace issuers go electronic on January 1, 2027, hospitals and specialists will push every payer—including your ASO clients—to meet them in the same channels.

CMS also notes the Health Tech Ecosystem’s Electronic Prior Authorization Acceleration initiative for implementation pain points. TPAs evaluating new platforms should ask vendors which HL7 FHIR prior-auth implementation guides they support and whether self-funded ASO blocks are on the roadmap.

What employers should do now

  1. Treat the statement as a vendor RFP question, not a panic. Ask your TPA or UM partner whether self-funded plans can already submit prior auth electronically, what turnaround metrics they publish, and how denials and appeals are communicated to members and providers.
  2. Map behavioral-health prior auth separately. Even if medical ePA is modernizing, MH/SUD lines remain under enhanced EBSA scrutiny. Compare your auth patterns to the red-flag examples in DOL’s Identifying Potential Problems tool.
  3. Watch January 1, 2027 on your fully insured and government blocks. If you bundle self-funded and insured business, CMS API deadlines for impacted payers may hit the same vendor stack you use for ASO clients—even when ERISA funding is different.
  4. Interested sponsors can contact CMS at ePAPledgeEmployers@cms.hhs.gov for the employer statement materials (per the HHS release). That inbox is for organizations considering their own signature, not for participant grievances.

We help employers with COBRA, FSA/HSA/HRA administration, and consolidated billing—not medical prior auth—but we watch these crossovers because delayed care and bad auth letters still land in HR’s inbox. If you need a partner for cafeteria and continuation coverage while your medical vendor retools prior auth, contact CBA.