Rule at a glance
- Rule
- CMS-0057-F
- Status
- Final rule (published February 8, 2024)
- Key dates
- January 1, 2027: federal requirements for new and expanded payer interfaces generally begin; the exact date depends on the payer type
Some practices can already submit electronic requests and appeal a decision from the original case. Other organizations are still choosing technology or arranging tests with partners. Under CMS-0057-F, federal requirements for new and expanded payer interfaces generally begin January 1, 2027. The exact date depends on the payer type. CMS rule summary
Each entry below summarizes the development, names the players involved and their role (payer, provider, vendor, regulator, standards body), and states its significance for the January 1 timeline. Each colored block is tagged with the CMS-0057-F component it relates to: Prior Authorization API, Provider Access API, Payer-to-Payer API, or Patient Access API. Green blocks mark developments that advance the January 1 journey; red blocks mark developments that signal schedule risk or delay.
November 16 | UnitedHealthcare links appeals to the original authorization
When UnitedHealthcare denies a request or approves only part of it, providers can now start an appeal from the case details page. The portal carries information from the original request into the appeal. A separate update lets providers begin certain post-acute care requests before an attending physician has been assigned. Why it matters for January 1: It shows electronic workflows expanding beyond initial requests, reducing manual re-entry as adoption grows.
▲ PROGRESS TO 1/1 | Prior Authorization API
Players: UnitedHealthcare (national payer); providers using its portal.
Significance: The largest national payer is extending electronic workflow beyond the initial request to appeals and post-acute care, going past the rule's minimum API requirements.
UnitedHealthcare portal update
November 15–18 | HLTH exhibitors address the paperwork behind electronic requests
At HLTH USA in Las Vegas, exhibitors are showing how software can extract information from incoming documents and route it to staff. For authorization teams, that work often happens before a request is ready to send. The conference runs through November 18. Why it matters for January 1: It highlights document intake and routing as upstream bottlenecks organizations need to address before go-live.
▲ PROGRESS TO 1/1 | Prior Authorization API
Players: HLTH conference exhibitors (health IT and document-automation vendors); provider authorization teams.
Significance: The vendor market is targeting the upstream paperwork that the new payer interfaces do not solve on their own.
HLTH event details · Exhibitor guide
November 12 | ONC and CMS open testing to providers and payers
The federal health IT office and CMS announced voluntary 10- to 12-week sprints in Drummond Group’s FHIRplace environment, with support from MITRE. Participants will trace a request across systems, from discovering a payer’s requirements to submitting clinical records and receiving a response. First-round expressions of interest are due November 20. Why it matters for January 1: The sprints give payers and providers a near-term opportunity to test end-to-end workflows before production use.
▲ PROGRESS TO 1/1 | Prior Authorization API
Players: ONC (ASTP) and CMS (federal regulators); Drummond Group and MITRE (test infrastructure); participating payers and providers.
Significance: The federal government is supplying a neutral test bed, giving the industry its first coordinated end-to-end testing opportunity before the compliance date.
November 12 | Hospital association publishes a go-live guide
The American Hospital Association released a handbook for hospitals preparing to connect to payer systems. It gives clinical IT and revenue cycle teams a shared reference for planning how staff will use electronic prior authorization in daily work. Why it matters for January 1: The guide turns federal requirements into concrete hospital planning and implementation steps.
▲ PROGRESS TO 1/1 | Prior Authorization API · Provider Access API
Players: American Hospital Association (provider trade group); hospital clinical IT and revenue cycle teams.
Significance: A provider-side body is translating the regulation into an operational playbook, signaling that hospitals are moving from awareness to implementation.
November 6 | Geisinger outlines what providers can expect in 2027
Geisinger Health Plan described upcoming connections that will let providers retrieve member information and exchange prior authorization data electronically. Its notice gives practices an overview of how these changes will affect their work with the plan. Why it matters for January 1: The notice gives practices a payer-specific preview they can use to plan connections, workflows, and staff training.
▲ PROGRESS TO 1/1 | Provider Access API · Prior Authorization API
Players: Geisinger Health Plan (regional payer, Pennsylvania); its network practices.
Significance: A regional plan setting expectations early, illustrating that payer-specific notices, not just federal guidance, will drive provider preparation.
November 3 | Humana and athenahealth report results from clinical use
Humana and athenahealth announced an expansion across athenahealth’s national network of more than 180,000 clinicians. In September, more than 6,000 providers processed nearly 35,000 electronic authorization transactions with Humana. More than 70% were completed without a request for additional information from the practice. The figure measures follow-up, rather than the share approved. Why it matters for January 1: The results show electronic authorization operating at scale with fewer follow-up requests for clinical information.
▲ PROGRESS TO 1/1 | Prior Authorization API
Players: Humana (national payer); athenahealth (EHR vendor); more than 6,000 participating providers.
Significance: The largest published production volume to date, demonstrating that payer-to-EHR integration works at scale and reduces follow-up requests.
Humana and athenahealth announcement
November 1 | Availity identifies planned connections for 24 payers
Nine organizations listed all three connections through Availity: payer-to-payer exchange, provider access, and prior authorization. Six listed provider access and prior authorization, six listed prior authorization alone, and three listed payer-to-payer exchange alone. Availity expects rolling launches during the first half of 2027. Why it matters for January 1: The roster shows broad platform activity, but staggered 2027 launches mean readiness will vary by payer.
▼ RISK TO 1/1 | Payer-to-Payer API · Provider Access API · Prior Authorization API
Players: Availity (clearinghouse and network intermediary); 24 payers using its platform.
Significance: Intermediaries are aggregating payer connections, but the first-half-2027 rollout schedule shows many payers will phase in after January 1.
November 1 | Capital Blue Cross outlines two January launches
Capital Blue Cross told providers to expect two new interfaces in January. One will let eligible providers retrieve information the plan holds about a patient. The other will support the exchange of information about an authorization request. Why it matters for January 1: The January launch window gives providers a concrete target for completing connectivity and workflow preparation.
▲ PROGRESS TO 1/1 | Provider Access API · Prior Authorization API
Players: Capital Blue Cross (regional Blue plan, Pennsylvania); its provider network.
Significance: A firm January date for both Provider Access and Prior Authorization interfaces, giving providers a concrete deadline rather than a general compliance window.
November 1 | UnitedHealthcare drops selected Nebraska Medicaid requirements
Selected procedure codes stopped requiring prior authorization for Nebraska Community Plan members. UnitedHealthcare also outlined changes for New Jersey and Tennessee. Practices working across state lines can use the notice to check the effective date for each plan. Why it matters for January 1: A smaller authorization list may reduce migration volume, while state-by-state variation still requires careful tracking.
▲ PROGRESS TO 1/1 | Prior Authorization (scope reduction)
Players: UnitedHealthcare Community Plan (Medicaid managed care) in Nebraska, New Jersey, and Tennessee; state Medicaid programs.
Significance: Medicaid managed care plans fall within the rule's scope; reducing authorization lists in parallel with technology buildout lowers the volume that must migrate to electronic channels.
UnitedHealthcare Medicaid notice
October 29 | AmeriHealth Caritas D.C. alerts its provider network
The District of Columbia Medicaid plan issued a provider alert on the federal requirements. It directed practices to coordinate with electronic health record vendors ahead of changes to how they retrieve payer data and submit authorization requests. Why it matters for January 1: The alert puts pressure on practices to engage their health record vendors and confirm technical readiness now.
▲ PROGRESS TO 1/1 | Provider Access API · Prior Authorization API
Players: AmeriHealth Caritas District of Columbia (Medicaid managed care plan); EHR vendors; network practices.
Significance: Payers are shifting part of the readiness burden to providers and their EHR vendors, who must confirm connectivity on their side.
AmeriHealth Caritas D.C. provider alerts
October 28 | HL7 convenes payers, clinicians, and developers
The HL7 Da Vinci community roundtable focused on bringing electronic prior authorization into routine use. Its program drew on perspectives from CMS, Aetna, Cleveland Clinic, and Epic about how an electronic request moves between a care team and a payer. Why it matters for January 1: Cross-industry alignment is essential for turning common standards into reliable day-to-day workflows.
▲ PROGRESS TO 1/1 | Prior Authorization API
Players: HL7 Da Vinci Project (standards body); CMS (regulator); Aetna (payer); Cleveland Clinic (provider); Epic (EHR vendor).
Significance: The group that authored the implementation guides referenced by CMS-0057-F brought all four stakeholder types together, which is the alignment needed to make the standards work in practice.
October 28 | D.C. Medicaid reaches a procurement deadline
The District’s solicitation for an Interoperability and Patient Access System listed an October 28 bid deadline, following earlier October procurement activity. The records document the purchasing stage. A contract award and a production launch are separate milestones. Why it matters for January 1: Procurement still in progress signals schedule risk because contracting, implementation, and production launch remain ahead.
▼ RISK TO 1/1 | Patient Access API · Provider Access API · Prior Authorization API
Players: District of Columbia Department of Health Care Finance (state Medicaid agency); bidding technology vendors.
Significance: State Medicaid fee-for-service programs are also covered by the rule; a procurement still open in late October signals that some government payers may not be in production by January 1.
October 27 | Cohere backs clearer documentation for 66 services
Cohere Health endorsed AHIP’s effort to clarify the clinical documentation needed for 66 medical services. Knowing which records a payer expects at the time of ordering could spare a practice a second submission while a patient waits to schedule care. Why it matters for January 1: Clearer evidence requirements can reduce incomplete submissions and avoid delays in electronic workflows.
▲ PROGRESS TO 1/1 | Prior Authorization (documentation requirements)
Players: Cohere Health (prior authorization technology vendor); AHIP (health insurer trade association).
Significance: Industry voluntary commitments on documentation complement the regulation; clearer evidence requirements feed directly into the documentation step of the electronic workflow.
October 26–29 | WEDI examines how clinical findings connect to billing codes
The Workgroup for Electronic Data Interchange included prior authorization on its national conference agenda in Washington, D.C. One session examined how to connect SNOMED CT, which describes clinical findings, with CPT, which identifies procedures and services. Why it matters for January 1: Reliable links between clinical findings and service codes are foundational to automating authorization decisions.
▲ PROGRESS TO 1/1 | Prior Authorization API
Players: WEDI (statutory advisor to HHS); terminology stewards for SNOMED CT and CPT; payer and provider coding staff.
Significance: Mapping clinical terminology to service codes is a technical foundation for automated decisions and will determine how much of the new workflow can run without manual review.
October 21 | Five employers back electronic authorization for self-funded plans
Amazon, Axon Enterprise, Google, Meta, and Oracle signed a statement supporting access to prior authorization improvements for employers that fund their own health benefits. CMS and the U.S. Department of Labor announced the voluntary commitment. Why it matters for January 1: Employer support extends momentum to self-funded plans, even where participation remains voluntary.
▲ PROGRESS TO 1/1 | Prior Authorization API (voluntary, self-funded plans)
Players: Amazon, Axon Enterprise, Google, Meta, and Oracle (self-funded employers); CMS; U.S. Department of Labor.
Significance: Self-funded employer plans are outside the direct scope of CMS-0057-F, so this voluntary commitment extends the rule's reach into a large segment of commercial coverage.
October 20 | MCG and Itiliti partner on clinical documentation
MCG and Itiliti Health announced plans to connect clinical guidance with authorization software so plans can communicate the evidence a provider needs to submit. Why it matters for January 1: Embedding evidence requirements earlier can reduce incomplete requests and repeated provider follow-up.
▲ PROGRESS TO 1/1 | Prior Authorization API (documentation requirements)
Players: MCG (clinical guideline publisher); Itiliti Health (prior authorization software vendor).
Significance: A vendor partnership operationalizing the documentation-requirements concept by delivering evidence criteria into the authorization workflow.
October 16 | Highmark explains how medical records systems can connect
Highmark briefed providers on electronic medical record capabilities planned for January 1, including access to payer-held data and support for electronic authorization requests. Why it matters for January 1: Highmark’s stated launch date gives providers a direct deadline for connection testing and operational preparation.
▲ PROGRESS TO 1/1 | Provider Access API · Prior Authorization API
Players: Highmark (regional Blue plan across Pennsylvania, West Virginia, Delaware, and New York); providers and their EMR vendors.
Significance: Another large regional payer committing publicly to a January 1 launch, adding to the list of payers whose dates providers must track.
October 15 | Point32Health outlines changes for its provider networks
Point32Health described upcoming ways for Harvard Pilgrim and Tufts Health Plan providers to retrieve information held by the payer and complete administrative tasks electronically. Why it matters for January 1: Providers need payer-specific instructions to configure access and adapt daily administrative workflows.
▲ PROGRESS TO 1/1 | Provider Access API
Players: Point32Health (parent of Harvard Pilgrim Health Care and Tufts Health Plan); New England provider networks.
Significance: A multi-brand payer coordinating a single approach across its plans, simplifying preparation for providers contracted with both.
Point32Health provider updates
October 9 | WEDI closes its fall readiness survey
WEDI asked organizations how prepared they were for the new interfaces. It said the responses would inform recommendations to CMS and help identify gaps in industry guidance. Why it matters for January 1: The survey can expose unresolved readiness gaps while time remains for guidance and remediation.
▲ PROGRESS TO 1/1 | All four APIs
Players: WEDI; CMS; responding payers, providers, and vendors.
Significance: A formal feedback channel to the regulator that could shape additional guidance or enforcement expectations in the final stretch.
October 1 | UnitedHealthcare cuts requirements as California evaluates vendors
UnitedHealthcare began removing prior authorization requirements for roughly 1,700 procedure codes across parts of its business. California’s Medicaid agency published answers to vendor questions about interoperability technology. Blue Cross NC also made guidance available for organizations registering to connect to its interfaces. Why it matters for January 1: The updates show authorization scope changes and technology buildout happening simultaneously, requiring payer-specific tracking.
▲ PROGRESS TO 1/1 | Prior Authorization API · Provider Access API
Players: UnitedHealthcare (national payer); California Department of Health Care Services (Medi-Cal); Blue Cross NC (regional Blue plan); technology vendors.
Significance: Sets the pattern for the period: payers trimming authorization scope and building interfaces at the same time, with state agencies procuring technology alongside them.
UnitedHealthcare code changes · California vendor bulletin · Blue Cross NC guidance
Upcoming deadlines
November 20 is the deadline to express interest in the first federal testing sprint. November 30 is the submission deadline for the KLAS Points of Light Awards for payer, provider, and vendor partnerships.