Utilization management

UM can occur at different points

Prospective review occurs before the service and often includes prior authorization. Concurrent review occurs while care or an episode continues. Retrospective review examines services after delivery under the applicable plan or payment process.

These labels describe timing. They do not decide which criteria, rights, or deadlines apply. The plan source should identify the review type and authority.

UM and clinical care have different authors

The treating clinician assesses the person, recommends care, discusses options, obtains consent when required, and monitors outcomes within scope. The payer applies coverage criteria and issues an authorization or adverse decision.

A payer can reduce or deny coverage while the clinician’s recommendation remains unchanged. A clinician may also revise a plan for clinical reasons independent of payer action. Records should identify which actor made each decision.

Build a complete request record

Track:

• payer, product, member, and request identifiers
• requested service, code, provider, location, and modality
• units, frequency, duration, and date span
• clinical recommendation and supporting evidence
• criteria and policy version used by the payer
• submission, receipt, RFI, and decision dates
• standard or expedited status
• approved, adverse, and pending portions
• reason, rights, deadlines, and contacts
• implementation, appeal, and claim states

Preserve the original request, payer notices, and every submitted packet.

Criteria and evidence need current sources

Use the member’s governing plan, current medical policy, provider contract, program rules, and payer instructions. Record effective dates and product scope. A policy for one product or population should not be applied to another without authority.

Clinicians should answer clinical questions from accurate assessment and treatment records. Administrative systems may organize evidence or flag gaps. They should not generate unsupported clinical conclusions.

Maintain a versioned criteria register for each payer, product, service, and population in scope. Record the source owner, effective date, retrieval date, planned recheck, and superseded version. When a bulletin changes a requirement, identify which open requests and authorized cases are affected instead of applying the change across every record.

If two sources conflict, preserve both and pause the disputed enforcement rule. Seek written clarification through the payer’s stated channel. The system can surface the conflict, while the clinician retains authorship of clinical content and the payer retains authority over its coverage decision.

A fictional UM cohort

Silver Fern, a fictional clinic, reviews 18 prior-authorization requests that reached an internal submission date. Fifteen have current product criteria, clinician-approved rationale, complete service and unit fields, required attachments, privacy clearance, and a tested route. Submission readiness is 15 of 18, or 83.3%.

Two await clinical clarification about the requested setting. One lacks a current provider-location roster match. All three remain held with an owner and age.

Of the 15 ready requests, 13 are submitted with matched receipt. Ready-to-receipt completion is 13 of 15, or 86.7%; original-cohort completion is 13 of 18, or 72.2%.

These measures describe workflow. They do not establish medical necessity, approval, or treatment effectiveness.

Decisions should be specific and actionable

An approval should identify the covered scope and dates. An adverse decision should identify the adverse portion, reason, criteria, effective date, and available review rights under governing sources. A request for additional information should identify what is needed, where to send it, and the deadline.

Reconcile every notice to the original request. Resolve conflicting units, providers, locations, and dates before scheduling or billing changes.

Communicate with the person and family

Explain what the clinician recommended, what the payer decided, which portion remains open, and what options exist. Use accessible communication and preserve the person’s priorities, assent, dissent, and questions.

Avoid presenting a payer decision as a clinical judgment. Discuss coverage uncertainty and possible cost without promising approval or payment.

Keep CMS policy in scope

The CMS-0057-F fact sheet identifies impacted payers and federal process and API requirements. The CMS final-rule page provides current implementation resources.

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 rule’s provisions have defined dates, exclusions, and scope. Other commercial and employer plans can fall outside the mandatory payer classes.

Measure process and outcomes separately

Useful UM process measures include complete requests, matched receipts, RFIs answered, decisions by target, notices reconciled, and appeals filed. Report approvals, partial approvals, denials, pending requests, withdrawals, and expirations separately.

Clinical outcomes, access, burden, procedural fidelity, member experience, and safety require their own measures. Approval rate should never become a proxy for clinical quality.