CMS-0057-F · TEFCA · January 1, 2027

Your Prior Authorization API has 48 days.

Five payer APIs and TEFCA's Mode 2 demographics double-check arrive on the same morning. On that morning your PAS endpoint either accepts a FHIR Prior Authorization Support request or it does not. I will tell you which — in writing, in ten business days.

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

What must be live on January 1, 2027

Prior Authorization API

Electronic PA submission and response — no portal, no fax. Sits behind the already-live 72-hour expedited and 7-day standard clocks, and the written denial reason.

FHIR R4Da Vinci PASCRDDTR

Where it breaks: CRD and DTR treated as optional; PAS wired to a portal instead of a real endpoint; no denial-reason field populated.

Patient Access API (expanded)

Must now carry prior authorization data alongside the claims, encounters, formulary and USCDI clinical data it already returns.

FHIR R4US CoreCARIN Blue Button

Where it breaks: A retrofit: the existing API passes claims but has no prior auth resource path, and old versions stay in place.

Provider Access API

In-network providers pull individual claims and encounter data without the member doing anything.

FHIR R4Da Vinci PDex

Where it breaks: Provider attribution and NPI matching; no bulk path; the wrong authentication model.

Payer-to-Payer API

Member-requested exchange of up to five years of claims, clinical and prior authorization history, with opt-in consent.

FHIR R4PDexopt-in consent

Where it breaks: Consent capture and member matching; historical backfill depth never being scoped; no dedupe.

Provider Directory API

A refreshed, publicly accessible provider directory.

FHIR R4PDex Plan-Net

Where it breaks: Stale data, no attestation workflow, and directory drift within weeks of go-live.

What this page covers

Every API, standard, implementation guide and deadline this assessment tests against.

CMS-0057-FPrior Authorization APIPatient Access APIProvider Access APIPayer-to-Payer APIProvider Directory APIDa Vinci PASDa Vinci CRDDa Vinci DTRDa Vinci PDexPDex Plan-NetCARIN Blue ButtonUS Core 3.1.1SMART App LaunchBulk FHIROpenID ConnectX12 278TEFCAIAS SOP 3.0IAL2AAL2QHINCommon Agreement 2.1Mode 2 Demographics Double-CheckSSRA-A72-hour prior authorizationdenial reasonsfive-year claims historyopt-in consentJanuary 1 2027 deadlineCMS-0062-P

Who it applies to

Medicare Advantage, Medicaid and CHIP — fee-for-service and managed care — and qualified health plans on the federal exchanges. It does not apply to traditional Medicare or to employer-sponsored plans, and prescription drug prior authorization is excluded.

CMS-0062-P, which would extend the prior authorization APIs to medical-benefit drugs, is proposed and not final: it is not a January deadline and should not be sold as one.

TEFCA, the same date

January 1, 2027 is the Mode 2 Demographics Double-Check. An Individual Access Services provider must reject a response whose demographics do not match its IAL2-verified record, must not retain the patient identifier, and must not continue that query. July 1, 2027 then brings HL7 SSRA-A on IAS FHIR endpoints. The governing documents are Common Agreement 2.1 and the QHIN Technical Framework.

The 10-day assessment

All five APIs tested against the implementation guides — not against a vendor's claim of readiness. Ten business days, $12,000 fixed. You get:

  • A written finding per API: pass or fail, with the exact conformance gap named.
  • The shortest path to compliant for the ones that fail, sequenced by what blocks go-live.
  • The test evidence: the requests sent, the responses returned, and the guide clause each one violates.

If you need the build, not just the finding

  • Prior Authorization API build sprint — six weeks. CRD, then DTR, then PAS, tested against Inferno and Touchstone, with the denial-reason field and the 72-hour clock wired to the real workflow.
  • Payer-to-Payer and PDex build. Opt-in consent capture, member matching, and the five-year backfill — the part that always slips because historical depth is never scoped.
  • TEFCA IAS readiness review — $8,000. Mode 2 double-check logic, non-retention proof, and SSRA-A readiness ahead of July.

Each API, in detail

Frequently asked

When is the CMS-0057-F API deadline?

January 1, 2027 for the five APIs. The operational requirements — 72-hour expedited and 7-day standard prior authorization decisions, specific denial reasons and five-year retention — have applied since January 1, 2026.

Which payers does it cover?

Medicare Advantage, Medicaid and CHIP fee-for-service and managed care, and qualified health plans on the federal exchanges. Not traditional Medicare, not employer-sponsored plans. Prescription drug prior authorization is excluded unless CMS-0062-P is finalized.

What does the 10-day assessment cost?

$12,000 fixed. All five APIs tested against their implementation guides, with a written pass or fail finding per API, the exact conformance gap named, and the shortest path to compliant.

Does TEFCA change on the same date?

Yes. January 1, 2027 is the Mode 2 Demographics Double-Check for Individual Access Services, and July 1, 2027 brings HL7 SSRA-A on IAS FHIR endpoints.

Sources

Last updated

Last updated 2026-11-15

← Services