CMS-0057-F · January 1, 2027

The Patient Access API in 2027: prior authorization data joins the record

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.

The API already returns claims and clinical data. From January 1, 2027 it must also carry prior authorization information, and it must do so under the same FHIR, SMART and US Core expectations that were tested the first time.

By Charles Trinh · Last updated 2026-11-15

Book the 10-day gap assessment $12,000 fixed · written findings

What changes

Prior authorization resources join claims, encounters, formulary and USCDI clinical data in the member-facing API.

Third-party applications register and authenticate against it, so scope handling is part of the surface you are measured on.

Usage metrics are reported to CMS, which makes the endpoint's real traffic part of the compliance story.

Where implementations break

A retrofit: claims pass, but there is no prior authorization resource path at all.

Old API versions left running beside the new one, so two behaviours answer the same question.

Scopes that were never tightened — an app that asked for everything still gets everything.

No bulk export path, so a member's full record cannot leave in one request.

Book the 10-day assessmentTen business days, $12,000 fixed, written findings per API.Start a fractional architecture engagement

How it gets tested

CARIN Blue Button STU 2.0.0 and US Core 3.1.1 against the conformance suites.

SMART App Launch and OpenID Connect token flows, including refusal cases.

Bulk FHIR $export, timed and validated for completeness against the member's record.

Third-party application registration and attestation

Applications register, are authenticated, and are held to the scopes they requested. Registration without scope review is how an API passes conformance and still leaks more than it should.

Usage metrics are reported, which means the endpoint's traffic becomes evidence. Instrument it before the first reporting period, not after.

Frequently asked

Is this new or an update?

An update. The Patient Access API exists; the prior authorization data is what is new, and it lands on the same day as the other four.

What standards are named?

FHIR R4, US Core 3.1.1, SMART App Launch, Bulk FHIR and OpenID Connect, with CARIN Blue Button as the recommended guide.

How long does the assessment take?

Ten business days, $12,000 fixed, written findings per API.

Do we rebuild the API from scratch?

Usually no. The assessment establishes which resources, scopes and export paths are missing, and the retrofit is scoped against the existing service rather than a rewrite.

Sources

Related

Last updated 2026-11-15

Book the 10-day assessmentTen business days, $12,000 fixed, written findings per API.Start a fractional architecture engagement
← All five APIs