CMS-0057-F · January 1, 2027

The Prior Authorization API in 2027: accept a request without a human

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.

By January 1, 2027 an impacted payer must take a FHIR Prior Authorization Support request, decide it, and return the decision with a specific reason — no portal, no fax, no phone call. The 72-hour expedited and 7-day standard clocks are already live.

By Charles Trinh · Last updated 2026-11-15

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

What has to be true on the day

A PAS endpoint that accepts a Claim with the prior authorization profile and returns a response resource.

Coverage Requirements Discovery answering whether authorization is required at all, before a request is built.

Documentation Templates and Rules supplying the payer's own questionnaire, so the request carries what the reviewer needs the first time.

A denial reason on every adverse decision, specific enough to act on.

Prior authorization data persisted and exposed to the Patient Access API, because the same rule requires it there.

Where implementations break

CRD and DTR treated as optional, so PAS receives requests missing the payer's own documentation and queues them for a human anyway.

PAS wired to the existing portal rather than a real endpoint — the portal still exists, the API is decorative.

Denial reasons left as a free-text field nobody populates, which fails the written-reason requirement on the first audit.

No test evidence: the endpoint answers a happy path request and nothing else.

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

How it gets tested

Da Vinci PAS STU 2.0.1 against Inferno and Touchstone, covering submit, inquire, and the response profiles.

Negative paths: missing documentation, unsupported service, expired coverage.

The clock: measure expedited at 72 hours and standard at 7 calendar days from receipt, not from triage.

Implementation in six weeks

Sequence it CRD, then DTR, then PAS. CRD decides whether authorization applies before a request is built; DTR returns the payer's own documentation rules; PAS carries the submission and the decision. Building PAS first produces an endpoint that receives requests the payer cannot answer automatically.

Six weeks assumes the payer owns the IG mapping and the test environment exists. Where the sandbox is shared or the vendor controls the interface, add two weeks rather than compressing the test pass.

The deliverable each week is a tested endpoint, not a status update.

Testing, sandbox and conformance

Inferno and Touchstone cover the published conformance suites; neither proves the workflow. Run the happy path, then the three negatives that matter: missing documentation, unsupported service, expired coverage.

A sandbox is not a test plan. The payer's own examples belong in the suite, because they are what the production reviewers will see.

Frequently asked

Do we need CRD and DTR as well as PAS?

They are the recommended guides, not separate regulations, but a PAS implementation without CRD and DTR tends to reproduce the manual review the rule exists to remove.

Can we keep using X12 278?

Yes — the rule allows a FHIR-only or a FHIR plus X12 278 hybrid. What is not allowed is a portal standing in for an API.

What does the assessment cost?

$12,000 fixed for ten business days, all five APIs, written findings.

What if we can only ship PAS this year?

Shipping PAS alone still requires CRD to decide whether authorization applies and DTR to carry the payer's documentation; a PAS-only endpoint tends to queue requests for manual review, which is the failure the rule targets.

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