Admission & Continuing Auth
Secure initial authorization and track renewal dates across detox, residential, PHP, and IOP—before census outruns approved days.

Utilization review
Cipher's UR specialists collaborate with your clinical team daily—securing authorizations, extending stays when medically necessary, and aligning documentation to the level of care you bill.
Get started
Talk to a billing specialist
Why Cipher
Residential, PHP, and IOP programs live on authorization windows—not monthly billing cycles. When concurrent review lapses or documentation gaps appear mid-stay, claims stop paying while patients remain in care.
Cipher's daily utilization review collaboration—described in our onboarding Phase two materials—tracks expirations, escalates before auth lapses, and supports clinical documentation so billed program days match payer medical necessity rules.
What's included
Secure initial authorization and track renewal dates across detox, residential, PHP, and IOP—before census outruns approved days.
Weekly and per-diem payer touchpoints aligned to your billed dates—so authorization stays active through the stay.
Support treatment plans, progress notes, and level-of-care documentation before review windows close—not after denials arrive.
Peer-to-peer support when payers challenge medical necessity—aligned to the 82% peer review approval rate Cipher publishes on its homepage benchmarks.
New authorization numbers when patients step between detox, residential, PHP, and IOP—preventing overlap denials.
Visibility into auth expirations, extension outcomes, and payer patterns affecting length of stay and cash flow.
Process
Document each plan's concurrent review cadence, documentation requirements, and extension pathways during onboarding.
Match UR calendars to billed program days—daily touchpoints for high-acuity residential and weekly cycles for PHP/IOP.
Engage payers before authorization expires—submitting clinical updates and extension requests with defensible documentation.
Ensure auth numbers on claims match active approvals—UR and billing share one workflow, not separate silos.
Effective behavioral health UR is a daily operating rhythm, not a weekly checklist. Each morning starts with a census-to-authorization reconciliation: which patients have approved days remaining, which authorizations expire within 48 to 72 hours, and which extension requests are already in flight with each payer. High-acuity detox and residential patients get daily payer touchpoints; PHP and IOP run on weekly or per-diem cycles matched to each plan's review cadence.
Daily census-to-auth reconciliation
48–72 hour expiration watchlist
Clinical packets in payer-specific medical-necessity language
Same-day escalation and peer-to-peer scheduling
Auth numbers synced to claims daily
82% peer review approval rate on escalations
Before every review window, the UR specialist assembles the clinical packet — treatment plan progress, current symptoms, level-of-care justification in the payer's own medical-necessity language — and submits it early enough that a denial can still be peer-to-peered before the authorization lapses. When payers push back, escalation runs the same day: peer-to-peer scheduling, supervisor review, and commissioner escalation where warranted.
Every outcome lands in the billing crosswalk the same day: new authorization numbers, approved day counts, and level-of-care changes sync to claims before submission. This is the operational difference between UR as a clinical courtesy and UR as a revenue function — Cipher's programs run the second.
Concurrent review happens while the patient is in care — the payer evaluates medical necessity in real time and approves or denies continued days. Retrospective review happens after discharge, when the payer re-examines days already delivered and claws back payment for days it decides were not justified. Concurrent review is where behavioral health revenue is protected; retrospective review is where it is lost.
Concurrent review
Where revenue is protected
The payer evaluates medical necessity in real time while the patient is in care — approving or denying continued days.
Retrospective review
Where revenue is lost
After discharge, the payer re-examines days already delivered and claws back payment for days it decides were not justified.
Programs without disciplined concurrent UR discover their denials in the remittance — weeks after the clinical decisions that caused them. By then the documentation window has closed and the appeal is an uphill fight. Daily concurrent review flips that: medical necessity is defended while the clinical record is still being written, and days that payers will not approve are identified early enough for step-down planning instead of write-offs.
Most behavioral health denials trace back to authorization events: no auth on file, auth expired mid-stay, level-of-care mismatch, or medical-necessity documentation the payer rejected. Systematic UR attacks each cause upstream — authorizations are secured before admission, tracked through the stay, extended with defensible documentation, and synced to claims so billed days never exceed approved days.
No authorization on file
Authorization expired mid-stay
Level-of-care mismatch
Medical-necessity documentation rejected
Systematic UR attacks each cause upstream — authorizations are secured before admission, tracked through the stay, extended with defensible documentation, and synced to claims so billed days never exceed approved days.
The denial library on this site catalogs what happens when that discipline is missing: CO-197 (absence of precertification), authorization-expired adjustments, and medical-necessity denials that turn into appeals or write-offs. Cipher's UR workflow exists specifically to keep your claims out of those categories — and when denials do arrive, the UR record becomes the foundation of the appeal.
Levels of Care
FAQ
Utilization review (UR) is the ongoing process of securing and maintaining payer authorization for treatment services—initial approval, concurrent review during the stay, and extensions when medical necessity supports continued care.
Cipher connects UR outcomes directly to billing—authorization numbers, billed dates, and documentation requirements stay synchronized so claims do not deny for auth lapses your clinical team thought were handled. Our UR specialists work with your clinical team daily, as described in our onboarding process.
Yes. Behavioral health RCM includes peer-to-peer assistance when payers challenge medical necessity. Cipher coordinates clinical packet preparation and follow-up documentation to defend continued level of care.
A new authorization is typically required—even within the same agency. Cipher tracks LOC transitions and opens new auth workflows before billing codes change on the transition date.
Cipher averages a 8-minute eligibility turnaround for benefits verification—compared to an industry-standard 30 minutes—supporting faster admission decisions alongside UR workflows.
Schedule a complimentary revenue cycle analysis and identify opportunities to optimize your revenue
Fill out the form below and we'll contact you within 24 hours.