Concurrent Drug Utilization Review: A Step-by-Step Workflow

In SUD treatment, concurrent drug utilization review usually means the payer's ongoing check that a member's continued stay at residential, PHP, IOP, or detox still meets medical necessity at each review interval, and it is where most behavioral health continued-stay denials start. Strictly speaking, drug utilization review is also a pharmacy term for screening prescriptions when they are dispensed; this guide covers the stay review. This walkthrough gives UR nurses a repeatable workflow: case assignment, documentation at each interval, continued-stay determinations, peer-to-peer calls, and denial handling.

What is concurrent drug utilization review and when is it triggered?

Concurrent drug utilization review is the payor's real-time check on whether an active stay — residential, PHP, IOP, or detox — still meets medical necessity criteria. Unlike retrospective review, which examines claims after discharge, concurrent review happens while the client is still in treatment, and an unfavorable determination can cut an authorization mid-stay.

Common triggers:

• Admission and the initial service request.
• Authorization window expiry, often every 3–7 days at residential levels.
• A level-of-care change or step-down.
• Payor-specific review intervals written into the contract.

Because reviews run under tight deadlines while staff juggle dozens of cases, missed documentation becomes expensive: denials and rework directly cut into collectible revenue for behavioral health practices. A structured walkthrough of the workflow lives in our concurrent review guide.

How does concurrent review utilization management differ from prior authorization?

Prior authorization is prospective: you submit the service request form before admission, the payer approves a set number of days or visits, and nothing bills until that authorization window opens. Concurrent review utilization management starts once the patient is already in a bed. The payer re-authorizes the stay in increments, and your UR staff initiates each continued-stay review by submitting current clinicals that prove medical necessity under criteria like ASAM 4th Edition.

The stakes differ sharply. A late prior auth costs you an admission; a missed concurrent review deadline can trigger an automatic denial for days already delivered. Steven Cavan covers the workflow side of that risk in more depth.

How does the concurrent review workflow run step by step?

Step 1: Case assignment and payor criteria mapping

Assign the case to a UR nurse the day the admission note posts. Pull the payor's medical necessity criteria and, for SUD levels of care, map the client's current presentation against ASAM dimensions before anything else. With caseloads spanning dozens of concurrent cases across payors, manual tracking through spreadsheets and shared inboxes is where timelines slip.

Step 2: Chart preparation and gap check

Run a gap check against the payor's criteria: nursing notes, provider assessment, treatment plan updates, and level-of-care justification. A single missing note can trigger hours of rework or an automatic denial, so fix gaps before submission, not after.

Step 3: Submission and reviewer call

Submit the clinical packet through the payor portal or service request form, then calendar the reviewer call. Bring the chart, your ASAM dimension mapping, and a one-page summary of treatment response and barriers to step-down.

Step 4: Determination and extension documentation

Log the determination, approved dates, and reviewer name in your tracking sheet or CriteriaIQ. If extended, update the authorization window and notify the clinical team so documentation continues to match the approved length of stay. If pended, schedule the peer-to-peer immediately.

What documentation do payers require at each continued-stay review?

Reviewers check the same core elements at every interval: current ASAM 4th Edition dimension ratings, a treatment plan updated since the last review, nursing notes, physician progress notes, documented risk factors, and either step-down readiness or the barriers preventing it. Missing any one element is what turns a routine continued-stay review into a denial or a peer-to-peer call. The concurrent review workflow breaks down where each element belongs in the cycle.

Residential and detox continued-stay elements

At residential and detox levels, reviewers weight the ASAM dimension ratings most heavily, especially dimensions covering intoxication and withdrawal, biomedical conditions, and substance use related risks. They expect nursing notes that show active withdrawal management or monitoring, plus a physician note within the review window. If the chart shows a client could safely step down to PHP or IOP, the reviewer will ask why the level of care has not changed.

PHP and IOP continued-stay elements

For PHP and IOP, reviewers focus on attendance records, group participation notes, and treatment plan progress toward stated goals. They look for evidence that the client is engaging and that step-down planning is documented, not just intended. A stale treatment plan is the most common gap here.

Documenting medical necessity without over-charting

Chart more of what reviewers score, not more volume: dimension ratings tied to specific events, risk factors with dates, and explicit barriers to step-down. A single missing note can trigger hours of rework or an automatic denial, so build a checklist per level of care and run it before every review window opens.

How should clinical teams prepare for reviewer calls during concurrent review?

Treat the peer-to-peer as a scheduled clinical meeting, not an improvised call. Assign one clinician as the UR lead and a second as note-taker, since an unprepared call wastes the authorization window you fought to get and burns clinician time you cannot recover.

Before dialing, have open in Kipu: the initial assessment, the most recent nursing and therapy notes, the ASAM dimension ratings from your last continued-stay review, medication administration records, and the current service request form. Map each payer question to a note timestamp so you can answer "what changed since the last review?" in seconds.

Answer by dimension, not narrative: give the specific ASAM 4th Edition criterion, the supporting documentation, and the projected step-down date if the level of care changes.

If the reviewer signals a soft denial, ask for the exact criterion they believe is unmet, request the denial reason in writing, and log it the same day. A structured call-prep checklist inside your utilization review software keeps this routine consistent across every UR nurse on the team.

What happens when a concurrent review results in a denied continued stay?

A denied continued stay means the payer will not authorize additional days at your current level of care. You typically get the determination in writing with the effective date, which is often the same day or the day after the review. From that date, the clock starts on member and provider appeal rights, which vary by payor and plan, so confirm the deadline on the determination letter rather than assuming a standard window.

Reading the denial reason

Pull the CARC and RARC codes from the remittance advice before you react. A medical necessity denial (CARC 50, for example) needs a clinical argument with supporting documentation. An authorization-window or notification issue (CARC 197 or similar) may be an administrative fix, not a clinical fight. The code tells you which appeal to write.

Appeal and peer-to-peer options

Request the peer-to-peer immediately; it is your second chance before a formal appeal, and it puts your medical director in front of the payer's reviewer. If the P2P upholds the denial, file the written appeal with the specific documentation the CARC/RARC codes point to, and track the deadline on your UR log. If the member steps down to PHP or IOP in the meantime, document the step-down so the appeal reflects the actual length of stay and level of care.

Which metrics show whether your concurrent drug utilization review process is working?

Track five numbers monthly. First, continued-stay denial rate: denials divided by concurrent reviews submitted, broken out by payor. Second, days in A/R tied to concurrent review cases, since a denial under appeal can sit for 60-90 days or more depending on the payor's appeal windows, which are published in each payor's provider manual (for example, Aetna's health care professional resources).

Third, authorization window lapses: continued-stay requests submitted after the payor's deadline, which often forfeits coverage for the days already delivered. Fourth, length-of-stay variance against the level-of-care expectation, since drift above it predicts medical necessity pushback. Fifth, rework hours per case: time spent chasing notes, resubmitting, and preparing P2P calls.

If you can't produce these five numbers from Kipu and your spreadsheets today, that gap is the first finding.

How can EHR and RCM workflows reduce concurrent review denials?

Manual tracking fails predictably: a spreadsheet row gets missed, a shared-inbox note arrives after the authorization window closes, and the continued-stay request goes out late. Most concurrent review denials trace back to that kind of timing and documentation gap, not to a clinical judgment call.

EMR-native tooling helps by tying reviews to the chart itself. Kipu Health supports concurrent review documentation inside the record, which means nursing notes, ASAM dimension ratings, and medication administration records live where the reviewer call happens rather than in a separate tracker. Other behavioral health platforms build UR tracking into their systems in similar ways, though coverage varies by vendor. An RCM layer such as CriteriaIQ sits on top of Kipu or BestNotes, matching ASAM 4th Edition criteria to each level of care, flagging missing notes before the reviewer call, and tracking authorization windows across payors so step-down and length-of-stay decisions land on time. The practical test is simple: if your UR nurse has to leave the chart to answer a reviewer's question, the tooling has not closed the gap. Count how many times that happens per week as your baseline.

Where CriteriaIQ falls short: it does not replace your clinical judgment or write your peer-to-peer arguments, it does not cover EMRs outside Kipu and BestNotes, and it will not fix upstream intake or coding problems that surface later as CARC/RARC codes on the remittance.

FAQ

How often does insurance review concurrent utilization for residential treatment?

It depends on the payor contract, but residential and detox levels typically run on short cycles, often every 2-3 days, while PHP and IOP reviews usually happen weekly. Review intervals are also triggered by admission, authorization window expiry, or a level-of-care change. Check the payor's provider manual for the exact cadence.

Can a concurrent denial be reversed after the patient is discharged?

Yes, but your leverage drops. Once the patient is discharged, the case shifts to retrospective territory: you file a written appeal supported by the CARC/RARC codes on the remittance advice and the clinical documentation behind them. The peer-to-peer option, your strongest lever mid-stay, is generally gone, and appeal deadlines vary by payor and plan.

Who on the clinical team can speak during a concurrent review call?

A clinician with direct knowledge of the chart, typically the UR nurse or coordinator, leads the call, with a second team member taking notes. For peer-to-peer calls after a denial, the medical director speaks with the payer's reviewer. Assign roles in advance so one person answers clinical questions while the other logs determinations and reviewer names.

What is the difference between concurrent review and retrospective review?

Concurrent review happens while the patient is still in treatment, re-authorizing the stay in increments based on current clinicals. Retrospective review examines claims after discharge, when services have already been delivered. The stakes differ: an unfavorable concurrent determination can cut an authorization mid-stay, while a retrospective denial is fought through claims appeals after the fact.

How far in advance of the authorization window should a continued-stay request be submitted?

Submit early enough that the request lands before the payor's deadline, not on it. Requests that arrive after the window closes often forfeit coverage for days already delivered. Since deadlines vary by payor and level of care, confirm the interval in each payor's provider manual and calendar it at case assignment so no window lapses.