Generating Specific Prior Authorization Denial Reasons From AI Recommendations Under CMS-0057-F
Treat the denial reason as a controlled output, not a generated explanation. The AI recommendation carries a policy criteria reference and the case facts relied on. A clinician or authorized reviewer confirms it. Runtime enforcement blocks, redacts or escalates anything that lacks support before the reason is issued. Each step leaves evidence an auditor can examine.
- {"title":"Criteria reference","description":"An identifier for the specific policy criterion applied, tied to a versioned policy text."}
- {"title":"Supporting case facts","description":"The clinical and administrative facts relied on, each pointing to a location in the submitted documentation."}
- {"title":"Gap statement","description":"For documentation denials, the specific information that was missing or inadequate."}
- {"title":"Confidence","description":"A score or band used only to route the case, never shown as the reason."}
- {"title":"Reviewer action","description":"Confirmed, edited or rejected, with reviewer identity and time."}
- The model returns a structured recommendation, not final reason text.
- Validation checks that a criteria reference and mapped case facts are present.
- The reviewer sees the criterion, the facts and the source documents side by side.
- The reviewer confirms, edits or rejects, and the action is recorded under their identity.
- The reason text is composed from approved criterion language and confirmed facts.
- One approved record feeds the API response, portal, fax and other channels so the reason stays consistent.
- {"title":"Allow","description":"A recommendation with a valid criteria reference, mapped facts and sufficient confidence proceeds to the reviewer queue."}
- {"title":"Redact","description":"PHI not needed for the reason is removed, for example from text bound for patient-facing channels where detailed clinical criteria are not required."}
- {"title":"Block","description":"A draft reason with no criteria reference, or with facts that do not map to the case data, is stopped before release."}
- {"title":"Escalate for approval","description":"Low-confidence or unsupported outputs go to a human approver before any reason is issued."}
Evidence records that support audit readiness
- The structured AI recommendation as received, with the policy version in force
- The reviewer's identity, action and any edits to the reason
- The final reason text as issued, with the channel and timestamp
- Every enforcement decision on the interaction: allow, redact, block or escalate
- Blocked or escalated drafts, and the approver's disposition
- A case identifier that links these records to the original request and decision timeframe
What CMS-0057-F requires of a denial reason
CMS-0057-F requires impacted payers to send providers a notice when they make a prior authorization decision. When the decision is a denial, the notice must include a specific reason. The duty is codified for Medicare Advantage at 42 CFR 422.122, for QHP issuers on the federally-facilitated exchanges at 45 CFR 156.223, and for CHIP fee-for-service at 42 CFR 457.732. Each provision applies from January 1, 2026, requires the reason regardless of the method used to communicate it, and excludes drugs. The MA response follows the timeframes in 422.568(b)(1) and 422.572(a)(1). The CHIP FFS response follows 457.495(d).
The rule says "specific" without listing required elements. CMS's stated purpose supplies the practical test: a specific reason lets a provider resubmit with updated information, appeal, or identify alternative treatments. CMS gives examples of reasons, including that the service is not considered medically necessary, that limits on covered care were exceeded, or that supporting documentation was missing or inadequate. A model score or a generic category code does not let a provider do any of those things.
A defensible design target follows from this: a reason that names the criterion applied and the case facts it was applied to. That target is an implementation inference from CMS's stated purposes, not a codified element list.
From January 1, 2027, the MA and CHIP FFS Prior Authorization APIs must also carry the specific reason on a denial. CMS finalized the reason as a requirement separate from the API content requirements, and payers must also give a specific reason through the Patient Access API. CMS did not require detailed clinical criteria for these decisions to be shared with patients through that API.
Scope and rollout decisions
Map each denial pathway to the provision and timeframe that govern the payer type: 422.122(a) for MA, 156.223(a) for QHP issuers on the federally-facilitated exchanges, and 457.732(a) for CHIP FFS. Confirm the numeric deadlines in the full regulations before encoding them as workflow timers.
Keep the drug exclusion in scope tracking. The current provisions exclude drugs. A 2026 proposed rule, noticed in April 2026, would require a specific reason for any drug denial from October 1, 2027 for state Medicaid and CHIP FFS programs, Medicaid managed care plans, CHIP managed care entities and QHP issuers on the federally-facilitated exchanges. As of November 2026 it is not final and does not list MA organizations.
Build reason categories around CMS's examples, such as medical necessity, coverage limits and missing documentation, and require each to resolve to a criterion and case facts. Then test each reason against its purpose: could the provider resubmit, appeal or identify an alternative from this text alone?
Path from recommendation to issued reason
Structured recommendation
Criteria reference, case facts, confidence and gaps in one record.
Runtime enforcement
Allow, redact, block or escalate for approval before release.
Reviewer confirmation
A named reviewer confirms, edits or rejects the reason.
Evidence record
Recommendation, decision, final text and enforcement outcomes retained.
Review enforcement and evidence for your denial workflow
Walk through how allow, redact, block and escalate-for-approval enforcement and audit-ready evidence apply to AI interactions and tool calls in prior authorization.
Explore Agent and Tool-Call Enforcement