Payer-to-Payer: Assessing the Complete CMS-0057-F Workflow Before January 1

CMS-0057-F's Payer-to-Payer API requires more than an accessible endpoint. Impacted payers must support affirmative member opt-in, prior and concurrent payer identification, requests and responses, exchange of maintained data within a five-year scope, and incorporation of received information. With compliance approaching, the readiness review should test the complete enrollment-to-exchange workflow, including recurring exchanges for concurrent coverage.

the-stack
10-12-2026

CMS-0057-F requires four FHIR API implementations by 01-01-2027: the provider access API, the prior authorization APIs covering decision and documentation requirements, electronic prior authorization support, and the payer-to-payer data exchange API. Considerable implementation attention has gone to the prior authorization and provider access requirements, which are the APIs most discussed in vendor communities and Da Vinci Implementation Guide documentation.

The payer-to-payer requirement is worth a separate assessment. It is not a variation on the other three. It is a two-sided operational workflow that begins at member onboarding, requires trading-partner identification, involves both outbound and inbound data exchange, and continues with recurring exchanges as long as concurrent coverage persists. Endpoint availability alone does not establish compliance.

Who Must Comply

The payer-to-payer API requirement applies to:

  • Medicare Advantage organizations
  • State Medicaid and CHIP fee-for-service programs
  • Medicaid and CHIP managed care plans
  • Qualified Health Plan issuers on Federally-Facilitated Exchanges

If your organization falls into one of these categories, the January 1, 2027 deadline applies. A January 1 effective date means the complete workflow must be operational before enrollment transitions from the Annual Enrollment Period, which closes 12-07-2026, take effect.

What the Complete Workflow Requires

The payer-to-payer exchange is triggered when a member switches from one impacted payer to another, or when a member has concurrent coverage with more than one impacted payer. The workflow covers the following:

Member identification and opt-in. When a new member enrolls, the plan must provide plain-language materials explaining the payer-to-payer exchange and obtain the member's affirmative opt-in consent before initiating any exchange [verify: confirm whether the final rule uses opt-in or opt-out framing for member consent, and the specific timing requirements for notice delivery]. Member enrollment workflows need to identify whether the member has prior or concurrent coverage with another impacted payer, which requires either member self-disclosure or matching against eligibility data, and to record consent decisions in a way that is auditable and can be updated if the member withdraws.

Trading-partner identification and authentication. The receiving plan must be able to identify that a new member's prior coverage was with another impacted payer, initiate a data request to that prior payer, and authenticate as a legitimate trading partner [verify: confirm CMS's specified mechanism for how receiving plans identify prior payers and initiate requests]. The sending plan must authenticate incoming requests and verify that the requesting plan is an impacted payer before transmitting data.

Data exchange scope. The exchange covers up to five years of claims and encounter data, USCDI elements, and prior authorization information for the member, within applicable exclusions [verify: confirm exclusions from the exchange, including which prior authorization categories are excluded]. The data must be returned in FHIR R4 format using the applicable implementation specifications.

Concurrent coverage. Where a member has concurrent coverage with two or more impacted payers, the exchange obligation is ongoing. Plans must exchange data within one week of the concurrent coverage start date and at least quarterly thereafter [verify: confirm the one-week and quarterly timing requirements against the final rule text]. This is not a one-time trigger. It requires recurring exchange management for the duration of concurrent coverage.

Data incorporation. Receiving plans must incorporate the exchanged data into their systems, not only receive it. The compliance obligation includes ingesting the data in a usable form, not only providing an endpoint that accepts it.

The Gaps to Assess Before Deployment

Readiness depends on the organization's existing infrastructure, data completeness, trading-partner integration, consent workflow, and testing evidence. Assess the actual critical path rather than infer readiness from the time remaining.

A requirements-based assessment should cover:

  • Has the organization confirmed it is an impacted payer type and that the January 1, 2027 date applies?
  • Does member onboarding identify whether a new enrollee has prior or concurrent coverage with another impacted payer?
  • Does onboarding present required plain-language materials and seek affirmative opt-in consent within the applicable timing?
  • Does each outbound data request carry the required enrollment and opt-in attestation?
  • Can the organization authenticate trading partners and match the member accurately across payer systems?
  • Can it initiate data requests to prior payers and receive inbound requests from receiving plans?
  • Can it return maintained data within the five-year scope, with required exclusions applied and documented?
  • Does it meet applicable request and response timing requirements?
  • Can it execute concurrent-coverage exchanges and manage the quarterly refresh obligation for the duration of that coverage?
  • Are member opt-out and consent-withdrawal workflows built and tested?
  • Are failure modes, retry logic, missing data handling, and audit evidence addressed?
  • Has testing covered actual trading partners and representative historical records, not only internal test data?

If the implementation is incomplete, document each gap against the applicable requirement, assign an accountable owner, quantify the member and operational risk, and obtain compliance review of the remediation plan. Concurrent coverage and quarterly exchange are explicit requirements, not optional features that can be deferred. Do not describe missing required functionality as compliant because a roadmap exists.

Building the Assessment

The strongest framing for internal compliance review is not "how close are we to done" but "is the complete enrollment-to-exchange workflow functional for a representative member journey." That means testing the case where a member enrolls, discloses prior coverage, opts in, the plan initiates a data request to the prior payer, receives and ingests the prior data, and then also manages the quarterly refresh if the member has concurrent coverage.

A functional endpoint that has never exchanged data with an actual trading partner is not a compliance posture. Audit evidence, including logged requests, responses, consent records, and incorporated data, supports the organization's position as the compliance date approaches.


Sources: CMS, "CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F)," Fact Sheet, January 2024 (cms.gov); CMS, CMS-0057-F informational session slides, January 2024; CMS-0057-F final rule, 89 Fed. Reg. 8758 (February 8, 2024).

Transforming Healthcare with AI Technology

Discover how Addie helps health systems, post-acute providers, and payers improve throughput, reduce avoidable days, and deliver better transitions of care.

Get Started