Utilization Review (UR)

What utilization review is

Utilization review is the gate and throttle for covered services. A payer or delegated vendor compares clinical information against coverage rules and medical-necessity criteria to decide if a service is approved, for what dates, and at what intensity.

UR usually shows up in three flavors:

• Pre-service review: before admission or start of care, often called prior authorization.
• Concurrent review: during an ongoing stay or episode, to extend days or units.
• Retrospective review: after services, often tied to audits or payment integrity programs.

On the provider side, UR is a team or function that collects clinical data, submits it to payers on schedule, tracks approvals and end-dates, and escalates to peer-to-peer review or appeal when a payer cuts days or denies.

Why utilization review matters operationally

UR determines which days and units will ever pay. If concurrent review is late, incomplete, or misaligned with the payer's criteria, everything after the last approved date is at risk. For residential, PHP, and IOP, that can mean tens of thousands of dollars written off for a single case.

UR errors ripple into RCM in predictable ways:

• CO-50 medical-necessity denials when documentation does not support the level of care.
• CO-197 denials when the payer decides services occurred after the authorized period or without required review.
• Takebacks after retrospective review when a payer decides part of a stay was not medically necessary.

Clean claims will still deny if services are beyond the UR-approved window. That distorts denial metrics, days in A/R, and collection forecasts unless UR data is married to billing data in your reporting.

How utilization review shows up in day-to-day work

In daily operations, UR is a schedule and a checklist. The schedule is driven by payer rules: for example, "concurrent review due by day 3, then every 5 days" or "IOP review every 10 units." The checklist covers what the payer wants to see: diagnoses, symptoms, risk factors, ASAM level, medication history, and discharge planning.

UR outcomes show up as:

• Auth numbers and date ranges that must be on the claim.
• Approved units or days that must match what you bill.
• Clinical rationales and denial letters that explain why days were cut.

Effective UR teams log each decision, update the census or EHR with auth spans, and hand those dates to billing. Revenue cycle then uses those spans to scrub claims, avoid billing beyond approved days, and target appeals when payers under-approve compared to the clinical picture.

• Treating the initial prior auth as a blank check, so your team keeps a residential patient for 21 days when the payer only approved the first 7 days and required a concurrent review that never went in. All days after day 7 deny with CO-197 and never convert to cash.
• Not tying UR approval spans to actual billing dates, so IOP group claims go out for 24 units when the payer only approved 16. The overage units deny with CO-50 or CO-197 and staff burn time reworking instead of preventing the problem.
• Allowing UR to live in a separate spreadsheet that billing never sees, so your RCM reports show "mystery" CO-50 medical-necessity denials that are really missed concurrent reviews or shortened stays that UR already knew about.
• Ignoring payer-specific UM rules for carve-out behavioral health vendors, so your team follows the health plan's generic policy while the BH vendor expects different review intervals and criteria. Claims to the carve-out payer then deny on CO-50 or N130 with no clean path to appeal.
• Failing to document the clinical case in UR notes, so when a payer reduces PHP days during concurrent review you have no clear record for appeal. The denial stands even though documentation in the chart would have supported additional days at that level of care.

In behavioral health, utilization review is often more intense than in medical-surgical care. Residential, PHP, and IOP stays are long and high-cost, and many payers require frequent concurrent reviews with detailed symptom, risk, and functioning updates. If a review is late or thin on clinical detail, everything after the last approved day is exposed.

Carve-out behavioral health payers and managed Medicaid organizations often have their own UR rules and portals, separate from the medical plan. Your UR staff might be submitting to three different BH vendors, each with different intervals, forms, and clinical criteria. If those rules are not mapped into your UR workflow, you will see clusters of CO-50 and CO-197 denials tied to specific plans or programs.

State Medicaid and Medicaid MCOs commonly require strict adherence to medical-necessity criteria for each level of care, often referencing ASAM or similar frameworks. For example, a commonly mapped ASAM 3.5 residential stay might get 7 days approved and then require step-down to PHP or IOP, even if the clinical team believes residential is still appropriate. If UR does not anticipate those step-down patterns and coordinate discharge planning and authorizations, you get unpaid "extra" days at the higher level of care.

Because behavioral health episodes are long and per-diem rates are common, UR failure can swing entire months of revenue. A single missed concurrent review can zero out a week of residential charges or a block of IOP units, and payers are often rigid about not backdating authorizations in BH programs.

AI can help with utilization review by handling the tracking, pattern-recognition, and paperwork that burn your team's time. An agent can read payer policies once, store UR intervals and required elements, watch the census for upcoming review dates, and flag charts that need concurrent review two days before they are due. It can also match auth spans against scheduled services so you know in advance which days or groups will fall outside approval windows.

Supabill's benefits-verification agent can capture not just whether prior auth is needed, but also which services fall under utilization review and at what cadence. A claims-scrubbing agent can compare each claim's service dates and units against the latest UR approval in your system and stop claims that run past approved days or lack an auth number. A denials agent can read every 835, classify CO-50, CO-197, and N130 denials back to the missed UR step, and surface payer and program patterns. AI will not argue medical necessity or conduct peer-to-peer reviews, so your clinicians and UR leads still own the judgment, negotiation, and appeal strategy.

How is utilization review different from prior authorization in behavioral health?

Prior authorization is usually the first UR decision before care starts. It answers the question, "Can the patient admit to this level of care on these dates?" Utilization review continues after that initial decision, mainly through concurrent review during the stay or episode. UR determines whether the payer will extend days or units, require step-down to a lower level of care, or cut the stay short. For long residential, PHP, and IOP episodes, concurrent UR decisions have far more dollar impact than the initial prior auth. Source

Who typically performs utilization review in a behavioral health treatment center?

UR is usually handled by nurses, social workers, or clinicians who understand both clinical care and payer criteria. They gather data from the chart, align it with medical-necessity standards such as the commonly mapped ASAM levels of care, and communicate with payer UR nurses or care managers. In smaller programs, a single person might do both UR and RCM, but higher volume or higher-acuity centers often separate UR from billing and intake so each team can specialize. Source

How often are concurrent reviews required for residential, PHP, or IOP stays?

Frequency is payer and product specific, and often tighter for behavioral health. Some commercial plans require a concurrent review as early as day 3 of residential, then every 3 to 7 days. PHP might require weekly reviews. IOP is often tied to units, for example after 10 or 16 sessions. Medicaid managed care plans may follow different schedules than commercial lines. You will not find a single standard in regulation, so your UR team should maintain a payer-by-plan matrix based on payer manuals and portals and update it regularly. Source

What documentation is most important to support UR for behavioral health programs?

Payers look for clear evidence of why the current level of care is still necessary and why a lower level is not yet safe or appropriate. That usually includes current risk factors for self-harm or harm to others, recent use or withdrawal symptoms, functional impairment, failed lower levels of care, co-occurring medical or psychiatric conditions, and active participation in treatment. Using structured assessments that align with established criteria, such as the ASAM dimensions, helps UR staff present a clear story that meets payer expectations. Strong documentation during UR also supports appeals when a payer cuts days. Source

What should we do when a payer reduces approved days compared to what our team requested?

First, capture the payer's rationale and map it to specific criteria or policy language. UR should review whether the clinical documentation in the chart and UR submission clearly addressed the criteria the payer is using. If not, tighten documentation and resubmit where allowed. If you strongly disagree and policy supports your position, escalate to peer-to-peer review or a formal appeal within the payer's stated timelines. Parallel to that, RCM should mark which days are authorized and which are at risk so you do not assume payment in forecasting or accidentally bill beyond the approved span. CMS and many state Medicaid programs outline appeal rights and timelines, so your policies should mirror those requirements. You can review general Medicare appeal guidance at CMS. Source

• CMS - Utilization Review (UR) Requirements
• Medicaid - Behavioral Health Services
• SAMHSA - Behavioral Health Services
• ASAM - The ASAM Criteria