Authorization determination

Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.

The determination must resolve the actual request

Match the notice to the submitted member, product, service, provider, location, code, units, date span, and request identifier. A generic “approved” status can hide a narrower service, shorter period, different provider type, or partial reduction.

Compare the decision with the original packet line by line. Record every difference rather than collapsing the result into one status.

Capture the complete decision record

A structured record should include:

• payer legal entity, product, member, and request identifiers
• submission and receipt dates
• requested service, code, modifier, units, frequency, and period
• approved scope and adverse scope
• provider, location, setting, and modality limits
• conditions, records, or progress information required later
• reason, criteria, policy version, and factual findings
• notice and effective dates
• standard and expedited review or appeal rights
• deadlines, destination, contacts, and representative rules
• document source and any portal or call confirmation

Preserve the original notice. A structured summary supports operations and cannot replace the legal document.

Federal denial-reason rules have defined scope

CMS-0057-F requires impacted payers to provide a specific reason for denied prior-authorization decisions beginning with the applicable 2026 process requirements. Impacted classes include Medicare Advantage organizations, state Medicaid and CHIP fee-for-service programs, Medicaid managed care plans, CHIP managed care entities, and QHP issuers on Federally-facilitated Exchanges.

The CMS FAQ explains the federal framework. It does not prove that another commercial or employer plan follows the same rule, and it does not replace the member notice.

Reconcile approved, denied, and pending portions

A determination may fully approve, fully deny, partially approve, request additional information, or close a request procedurally. Some notices combine several results.

Create one row per distinct service and date period. Keep pending information requests outside the approved or denied count until the payer’s source defines their status. Identify every required next action and owner.

A fictional reconciliation

A fictional clinic receives 14 determinations for a weekly review cohort. Twelve match the member, requested service rows, decision status, units, dates, and rights in the submitted packets. Reconciliation completeness is 12 of 14, or 85.7%.

One notice approves the correct units for the wrong location. One lists a date span shorter than both the approved units and stated rationale suggest. The practice holds scheduling changes, contacts the payer, and preserves both documents.

Of the 12 matched notices, nine are full approvals, two are partial approvals, and one is a denial. Those outcomes are reported separately.

Explain the result in plain language

Tell the person or family what was requested, what the payer approved, what remains adverse or unresolved, which dates apply, and what choices or rights are available. Use accessible language and the person’s preferred channel.

Avoid saying the clinician reduced care when the payer reduced authorization. The treating clinician retains responsibility for clinical recommendations within scope and decides how to address clinical risk or revise a plan with appropriate involvement and consent.

Release operations from verified fields

Scheduling should use the approved provider, location, service, date, and units. Billing should use the actual delivered service and documentation, along with the current authorization. Set alerts before units or dates expire.

Authorization does not establish eligibility on the service date, clean-claim status, coding accuracy, claim acceptance, or payment. Reverify applicable gates.

Validate implementation after the notice

Trace each approved field into scheduling, authorization balances, clinician and location assignment, claim edits, and family communication. Use a second-person check for high-risk discrepancies or large unit loads. The operational record should show who entered the decision, who verified it, the source notice, and the effective version.

When the payer corrects a notice, preserve the original and add the replacement as a new version. Identify which schedules or claims relied on the earlier information and review them. A portal display that changes without an explanation should trigger written clarification rather than silent overwrite.

Monitor units used, units remaining, days remaining, and pending services without assuming all authorized units should be delivered. Service amount and schedule remain clinical decisions within the approved coverage boundary and available resources.

Review rights and follow-up

For an adverse portion, follow the notice and governing appeal sources. 42 CFR 438.404 provides one Medicaid managed-care notice framework and is not universal.

Useful measures include notices reconciled, discrepancies resolved by target, determinations communicated accessibly, approved configurations released correctly, and adverse decisions routed before deadline. Keep pending, approved, partially approved, denied, withdrawn, and expired states distinct.

Before closing reconciliation, confirm that every requested line has an explicit payer state and that no unmentioned service was silently treated as denied or approved. Seek written clarification for omissions and preserve the original request beside the determination.