Utilization review for addiction treatment.
Concurrent review is where behavioral health revenue quietly bleeds out. Revenue Logic protects authorized days through ASAM documentation coaching, payer-specific review calendars, and peer-to-peer denial support.
• Facilities using our documentation coaching typically see a measurable reduction in concurrent review denials within the first 60 days.
The bleed point
The patient is clearly still sick. They’re in residential, they’re engaged, and the clinical team knows discharge would be reckless. Then the concurrent review comes back denied for “lack of medical necessity,” and on day five the reimbursement just stops — even though the care doesn’t. That’s not a clinical failure. It’s a documentation failure, and it’s almost always preventable.
Concurrent review is where behavioral health revenue quietly bleeds out. Payers re-authorize residential every 3–7 days, PHP roughly weekly, detox every 24–48 hours. Each review is a fresh chance for a denial. Miss the window or send notes that don’t map to criteria, and you lose days of care you already delivered.
What do payers look for in ASAM criteria documentation?
Behavioral health UR runs on ASAM, and generic progress notes don’t satisfy it. Payers want the patient’s presentation mapped against all six dimensions — acute intoxication/withdrawal, biomedical conditions, emotional/behavioral/cognitive conditions, readiness to change, relapse/continued-use potential, and recovery environment. A note that says “patient attended group, mood stable, compliant with meds” tells a reviewer nothing about why this patient still needs a residential bed. The note that survives review says the patient is in Dimension 4 ambivalence with a Dimension 6 recovery environment that includes an actively using partner at home — that’s a discharge barrier, and discharge barriers are what hold the authorization.
Know which criteria the payer actually uses, because it isn’t always ASAM. Some plans run InterQual. Some run their own proprietary medical-necessity grids. Submitting ASAM-mapped documentation to a reviewer working off InterQual is a fight you started on the wrong field. After 14 years in this work, the pattern is clear: the centers that lose concurrent reviews usually lost them at intake, by not pinning down which criteria set this payer’s reviewers grade against.
Why do payers deny continued stay requests for PHP and residential?
Payers frequently push to step patients down from RTC to PHP, or PHP to IOP, long before clinical criteria support the transition. Handling this requires more than submitting notes — it requires mapping the patient’s presentation directly against the payer’s preferred medical necessity framework and explicitly documenting the barriers to discharge. If the clinical documentation does not articulate why a lower level of care is unsafe, the continued stay will be denied. The answer is not to argue louder — it’s to document the specific, clinical reason a step-down is unsafe right now, and to do it inside the review window. When a denial does land, request the peer-to-peer. Accepting a concurrent denial without a peer-to-peer is leaving recoverable revenue on the table, full stop. When the treating physician is prepped with the denial rationale and the exact ASAM dimensions that rebut it, those calls reverse at a high rate.
“Payers don’t just want to see that the patient attended groups; they want to see the specific, documented barriers preventing a safe step-down to IOP. Cigna’s concurrent review timeline for PHP is typically 3–5 days, and failing to address these barriers in every cycle guarantees a denial.”
How does Revenue Logic manage behavioral health UR?
We treat UR as revenue protection, not paperwork. Our specialists read the clinical documentation before it goes to the payer, flag the gaps a reviewer will cite, and tell the clinician precisely what’s missing. That’s not clinical supervision — it’s making sure the chart says what the care already justifies.
01
Start authorization immediately after VOB
We initiate prior auth the moment the VOB clears, using the correct criteria and level-of-care code for the payer, closing the day-one auth gap that triggers immediate denials. This builds directly on behavioral health VOB and prior authorization requirements.
02
Build a concurrent review calendar by payer
Every active patient’s review window lives on a tracked calendar by payer, patient, and level of care — residential every 3–7 days, detox every 24–48 hours, PHP weekly — so no review is ever missed.
03
Coach clinical documentation before submission
We review notes for payer-specific documentation gaps — missing discharge barriers, unmapped ASAM dimensions — before they reach the reviewer.
04
Respond to denials inside the appeal window
When a denial lands, we respond inside the window with documentation built around the specific dimension the reviewer cited — the foundation of any medical necessity denial appeal process.
05
Prepare peer-to-peer review calls
We schedule the call and brief the treating physician on the denial rationale and the exact ASAM dimensions that rebut it.
Standard UR vs. Revenue Logic UR. .
UR function
Standard industry approach
Revenue Logic approach
Prior authorization
Submit basic admission request
Match request to payer criteria and ASAM level of care
Concurrent review
Send clinical notes as provided
Review notes for payer-specific gaps before submission
Review calendar
Manual tracking by staff
Centralized deadline tracking across payer, patient, and LOC
Denial response
Appeal if time allows
Immediate denial rationale review and targeted response
Peer-to-peer
Often underused
Scheduled, prepared, supported with clinical talking points
Outcome learning
Case-by-case
Tracks payer denial patterns and documentation triggers
| UR Function | Standard Industry Approach | Revenue Logic Approach |
|---|---|---|
| Prior Authorization | Submit basic admission request | Match request to payer criteria and ASAM level of care |
| Concurrent Review | Send clinical notes as provided | Review notes for payer-specific gaps before submission |
| Review Calendar | Manual tracking by staff | Centralized deadline tracking across payer, patient, and LOC |
| Denial Response | Appeal if time allows | Immediate denial rationale review and targeted response |
| Peer-To-Peer | Often underused | Scheduled, prepared, supported with clinical talking points |
| Outcome Learning | Case-by-case | Tracks payer denial patterns and documentation triggers |
“Most billing companies treat utilization review as an administrative chore — faxing whatever notes the clinical team provides. Revenue Logic takes a proactive, clinical approach. We provide documentation coaching to your staff before the review window closes, ensuring the clinical narrative maps directly to the payer’s specific medical necessity criteria.”
When should a provider escalate to peer-to-peer review?
01
When a payer denies residential, PHP, IOP, or detox continued stay days.
02
When the denial cites medical necessity despite documented symptoms or relapse risk.
03
When the payer pushes premature step-down before discharge barriers are resolved.
04
When the reviewer ignores ASAM criteria or applies the wrong level-of-care standard.
05
When a high-dollar authorization period is at risk.
Frequently asked questions.
Concurrent review denied — patient still needs care. What first?
Request the peer-to-peer immediately and protect the appeal window — both clocks are short. Pull the exact denial rationale and identify which ASAM dimension the reviewer says isn’t met, then build the rebuttal around that single point with specific clinical evidence. Vague “patient needs treatment” appeals lose. Dimension-specific ones win.
How do I write an ASAM note that survives concurrent review?
How often will a payer review a residential or detox stay?
When is a peer-to-peer worth requesting, and who should take the call?
Almost always, on any medical-necessity denial — and the treating physician or clinical director takes it, not the biller. The reversal rate is high when the clinician walks in already knowing the payer’s stated rationale and the specific dimensions that counter it. The calls that fail are the ones where the doctor finds out the denial reason during the call.
The payer uses InterQual, not ASAM. Does that change how I document?
Yes — match the criteria set the reviewer is actually grading against. ASAM-mapped notes can still fall short of an InterQual checklist if you don’t hit the specific indicators it requires. The first thing to confirm on any new payer is which criteria they apply by level of care, because submitting to the wrong framework is an unforced error.
Can I still recover a stay after the patient discharges?
Yes — retrospective denials go through internal appeals and, when those are exhausted, external independent review. The case is built from the clinical record that justified the original authorization, so the strength of your appeal depends on how well the chart documented medical necessity in real time. This is exactly why documentation coaching upstream pays for itself downstream.
How does your UR process keep records from triggering downstream appeals?
Every concurrent review runs through a documentation QA step before submission, where we check the clinical note against the ASAM dimensions and the specific criteria that payer grades against — not just whether the words are present, but whether the record actually supports the level of care being billed. Records that match the claim don’t give the payer an opening to claw it back later.
How does multi-step QA protect authorized days?
Multi-step QA protects authorized days by checking that each UR submission matches ASAM criteria, payer medical-necessity rules, level-of-care documentation, and the actual claim being billed. Clean records support payment; thin or mismatched records create appeals that should never have happened. It’s the same discipline we bring to billing for ASAM levels of care.
UR isn’t done when the auth comes through — it’s done when the chart behind that auth would survive a second look. Our documentation QA checks the note against what the reviewer actually grades on before anything goes up, so the records support the payment instead of handing Optum or Carelon a reason to come back at it on appeal.
Send us your last ten concurrent review denials.
We’ll tell you which were recoverable, which came down to a documentation gap, and what your clinical team should change so the next ten don’t happen.