CMS-0057-F · January 1, 2027
The Provider Access API in 2027 fails on attribution, not on endpoints
Applies to Medicare Advantage, Medicaid and CHIP (fee-for-service and managed care), and qualified health plans on the federal exchanges — not traditional Medicare, not employer plans. Prescription drug prior authorization is excluded.
In-network providers must be able to pull a member's claims and encounter data without the member doing anything. The endpoint is the easy half; deciding who is in-network for which member, and matching them to the right NPI, is where projects stall.
What has to be true
A provider-facing API returning claims and encounter data for members attributed to that provider.
Attribution logic that reflects the payer's actual network and product rules, not a spreadsheet.
NPI matching that survives organisational hierarchies, group NPIs and locum arrangements.
An authentication model suitable for backend provider systems, not a member login.
Where implementations break
Attribution built once and never reconciled with network changes.
No bulk path, so a large system cannot pull at the volume it actually needs.
The authentication model copied from the member API, which the provider's system cannot use.
How it gets tested
Da Vinci PDex STU 2.0.0 conformance for the returned resources.
Attribution samples checked against the network file, member by member.
Bulk access under load, timed.
Attribution and NPI matching
Attribution is a payer rule, not an API feature: product, network, effective dates and delegation decide which provider may see which member. Test it against the network file on the day, member by member.
NPI matching has to survive group NPIs, locum arrangements and organisational hierarchies; a flat practitioner-to-NPI table fails on the first large system.
Frequently asked
Does the member have to consent?
No — this is the provider access path, not the member-mediated one. Consent and member matching are the Payer-to-Payer problem.
Which guide applies?
Da Vinci PDex, on FHIR R4, tested against its conformance suite before the deadline.
What does the assessment cost?
$12,000 fixed for all five APIs, ten business days.
How is attribution tested?
Against the network file on the day of the test: a member sample is walked from the payer's attribution table to the provider record and the claim returned by the API must belong to that member.