Two of the four CMS-0057-F APIs are brand new for most payers: Provider Access and Payer-to-Payer. Here is what each one does and what it takes to build them.
The Provider Access API
The Provider Access API lets in-network providers pull a patient’s claims, encounter, and clinical data directly from the payer using FHIR, so they have the full picture at the point of care. Unlike the Patient Access API, which the member drives, this one is provider-initiated — so the payer has to handle provider attribution (confirming the provider actually treats the patient) and give members a way to opt out. It must be in production by January 1, 2027.
The Payer-to-Payer API
The Payer-to-Payer API moves a member’s data between health plans when they change or hold concurrent coverage, so their history follows them instead of starting over. When a member opts in, their new plan requests claims, encounter, clinical, and prior-authorization data from the old plan over FHIR. It is the API that finally makes “your records follow you” real — and it too is due by January 1, 2027.
What they share with the other APIs
Both run on the same foundation as the Patient Access and Prior Authorization APIs: a conformant FHIR R4 server, data mapped from your claims and clinical systems into FHIR resources, and the US Core and Da Vinci profiles. Building all four as a set, rather than four separate projects, is what keeps the January 2027 timeline realistic.
What makes these two tricky
- Attribution and consent. Provider Access requires verifying the treatment relationship; Payer-to-Payer requires member opt-in and a clean handoff between plans.
- Identity matching. Finding the same member across two payers’ systems is harder than it sounds.
- Data completeness. You can only share what you have mapped to FHIR, so the quality of your data pipelines shows up here first.
How EIXSYS helps
EIXSYS builds the Provider Access and Payer-to-Payer APIs alongside the rest of the CMS-0057-F set — the FHIR server, the data mapping, and the attribution, consent, and identity-matching logic they depend on — for health plans and TPAs. Delivery is SOC 2 Type II, HIPAA, and ISO 27001 aligned.