Concurrent Review Health Insurance: Stage-by-Stage Guide

Concurrent review health insurance checks are the payer's ongoing verification that an active stay, whether residential, PHP, IOP, or detox, still meets medical necessity. They trigger at admission and repeat at each continued-stay interval until discharge. This guide walks each stage and lists the documentation reviewers request at each checkpoint, so you can anticipate requests rather than chase charts later.

What is concurrent review in health insurance and when does it begin?

Concurrent review is real-time utilization review that happens while a patient is actively in treatment. Unlike prior authorization, which happens before admission, concurrent review evaluates whether an ongoing stay at residential, PHP, IOP, or detox continues to meet medical necessity criteria at defined checkpoints during care.

It typically begins shortly after admission, once initial authorization is granted. Many payers open a concurrent review case within the first few days of the authorized stay, then repeat it at intervals tied to the authorized length of stay, often every few days for residential and detox or weekly for PHP and IOP.

Payers must issue these decisions within defined turnaround windows, and Medicaid managed care rules set timeframes that vary by state (Medicaid managed care requirements). Missing one checkpoint is how a covered stay turns into a denied extension. We break the full lifecycle down stage by stage in our guide to concurrent review in behavioral health.

How does concurrent review differ from prior authorization and retrospective review?

The three UR types differ by when they happen and what the reviewer decides.

Prior authorization happens before admission: the payer approves a level of care and an initial authorized length of stay based on your service request form and assessment. Concurrent review happens during treatment, triggered at payer-set intervals, and decides whether continued stay at that level still meets medical necessity criteria. Retrospective review happens after discharge and only judges whether care already delivered was covered.

Concurrent review is where you still have leverage: a strong peer-to-peer can extend days before they're cut.

What triggers a continued-stay concurrent review and how often do payers require one?

A continued-stay review is triggered by the expiration of the authorized interval, not by a clinical event. When a payer approves residential or PHP care, the authorization covers a set number of days or a review cycle, and the concurrent review clock starts the day of admission. Miss that window and the next authorization request arrives as a new service request form, often with the stay already in question.

Review intervals by level of care

Intervals vary by payer, but the pattern follows acuity. Detox typically requires review every one to three days. Residential and inpatient psychiatric stays are commonly reviewed every three to seven days, while PHP and IOP authorizations are often issued in one-to-two-week blocks tied to attendance and step-down planning. ASAM 4th Edition criteria shape what reviewers expect at each level, since length-of-stay decisions are justified against the dimensional assessment rather than a fixed day count. Your payer contracts and UR plan override any general pattern, so confirm each payor's interval in writing.

What restarts the authorization window

Three things restart the clock: a new approved authorization, a peer-to-peer that ends in continued-stay approval, or a level-of-care change documented with updated medical necessity criteria. A significant clinical change, such as an acute event mid-stay, can also prompt an off-cycle review. Tools like CriteriaIQ track these dates per payor so a reset never slips past the authorization window.

What clinical documentation do reviewers request during a concurrent review?

Admission and first review checkpoint

The initial concurrent review leans heavily on the intake record. Expect the reviewer to ask for the ASAM assessment or equivalent level-of-care determination, the biopsychosocial completed within the payor's required window, the physician's admission order, and any medical clearance or withdrawal management notes that justify detox or residential placement. Payors also want the treatment plan with measurable goals and the first nursing notes showing acuity. A missing signature or an assessment dated outside the required window is the most common reason an initial concurrent review comes back denied, so verify dates and signatures before the call, not after.

Mid-stay continued-stay reviews

Each continued-stay checkpoint asks one question: why does this patient need this level of care today rather than a step-down, and the documentation that answers it is forward-looking. Reviewers request updated progress notes from the treating clinician, current medication administration records, nursing notes documenting ongoing symptoms or behaviors, and a treatment plan review showing goals that are still active or newly revised. Participation evidence matters too: attendance records for groups and individual sessions, any UA results, and notes from family or case management contacts. The strongest continued-stay packets also include a projected discharge date with the specific criteria the patient still must meet, because reviewers read a missing discharge plan as evidence the stay has drifted past medical necessity. If your UR coordinator is pulling this together from Kipu plus spreadsheets the night before the review, a tool like CriteriaIQ can assemble the checklist per payor so nothing gets requested twice or left out.

Step-down and discharge documentation

When the reviewer moves toward step-down or discharge, the documentation shifts from justifying care to justifying the transition. Provide the discharge summary or step-down plan, the receiving level of care, referrals or appointments already scheduled, and final progress notes showing the patient has met the goals that supported the original authorization. If the payor proposes an earlier end date than your clinical team supports, the notes you gathered at each prior checkpoint are what you will use in the peer-to-peer, so keep them organized by review date from day one.

How long does a concurrent review decision take and what are payer turnaround requirements?

Turnaround windows for concurrent review decisions vary by payor, product line, and state regulation, so your UR calendar needs each payor's clock written down, not guessed at. Commercial plans commonly commit to decisions within 24 to 72 hours of a completed continued-stay submission; Medicare Advantage and state Medicaid programs often carry their own shorter or longer windows. The practical risk is the clock running out mid-stay: if the payor misses its deadline, many contracts and some state rules treat the stay as authorized through the requested dates, but proving that requires timestamped submissions and a documented follow-up trail.

Anchor your requested days to the clinical picture, not the payor's tolerance. The ASAM Criteria 4th Edition does not set fixed length of stay ranges by level of care; reviewers test your request against the dimensional assessment instead. We built CriteriaIQ's authorization tracking around those windows; where it falls short is payor-specific contract quirks, which still need your fee schedule and policy manual. For a level-of-care breakdown, see our guide to ASAM criteria in insurance authorization.

What happens if a concurrent review determines care is no longer medically necessary?

When a reviewer denies continued stay, the determination arrives as a formal notice, not a phone call summary. The notice states the effective date coverage ends, which is rarely the same day you receive it. Payers typically allow a few days of coverage after the decision so you can arrange step-down or discharge without an abrupt break in care.

Reading the denial notice and CARC/RARC codes

The notice carries standardized codes that tell you exactly why the payer stopped covering days. Medical necessity denials usually map to CARC 50 (non-covered because not deemed a medical necessity) with a RARC explaining the specifics. The X12 code lists are public, so you can decode the denial before calling anyone. Match the code against the clinical documentation you submitted to see whether the issue is missing notes, level-of-care criteria, or dates of service.

Peer-to-peer as the first escalation

Most denial letters give you a window, often a few business days, to request a peer-to-peer with the payer's medical director. Bring the chart, the ASAM dimension summary, and a proposed step-down plan. A successful P2P reverses the denial; if it does not, the formal appeal follows the timeline stated in the notice.

How can providers prepare for concurrent reviews to reduce denials and length-of-stay disputes?

Preparation comes down to two habits: documenting to each payor's medical necessity criteria before the reviewer asks, and tracking every authorization window so no continued-stay review lapses. Most denials trace back to a missing note or a missed deadline, not a clinical judgment.

A documentation cadence that survives multiple payors

Build a daily note template per level of care that maps to ASAM 4th Edition dimensions and each major payor's criteria. Every progress note should state why the patient needs this level today and why a step-down is not yet appropriate. Before each peer-to-peer, pull the last 72 hours of notes, the treatment plan update, and the most recent assessment so you can answer the reviewer without scrambling through the chart. A single missing note can trigger hours of rework or an automatic denial.

Tracking timelines without losing cases

Spreadsheets and shared inboxes fail quietly: a row gets skipped, an inbox thread buries a review date, and you learn about it at denial. Ritten and Behave Health offer direct UR support; Kipu Health sits adjacent as an EMR platform.

Honest note on our own product: CriteriaIQ RCM tracks authorization windows and continued-stay deadlines across payors inside Kipu and BestNotes, and assembles the documentation reviewers request. It does not write your clinical notes, make medical necessity judgments, or replace your peer-to-peer calls. If your UR volume is small and single-payor, a disciplined spreadsheet may be enough.

FAQ

Does concurrent review apply to outpatient levels of care like IOP and PHP, or only inpatient stays?

It applies to both. PHP and IOP authorizations go through the same checkpoint process, usually in one-to-two-week blocks tied to attendance and step-down planning, while detox and residential are reviewed more frequently, often every few days. The level of care determines the review interval, not whether review happens at all.

Can a payer deny days already delivered during a concurrent review?

Not usually. Concurrent review decides whether care going forward stays covered; it generally approves, steps down, or terminates the remaining authorized days. Days already delivered are judged by retrospective review after discharge, where a payer can deny or recoup payment. Documenting each checkpoint protects you in both directions.

Who can conduct a concurrent review on the payer side, and must it be a licensed clinician?

The initial review is often handled by utilization review staff, but a determination that care no longer meets medical necessity typically requires input from a licensed clinician, usually a psychiatrist or other medical director. That clinician is also who you reach in a peer-to-peer, so a denial notice should identify a reviewer with clinical credentials.

What is the difference between a concurrent review and a level-of-care reassessment?

A concurrent review is the payer's coverage decision at a set interval, testing your documentation against its medical necessity criteria. A level-of-care reassessment is your clinical team's own evaluation, such as an updated ASAM dimensional assessment, determining whether the patient still fits the current level. The reassessment feeds the review; the review decides whether the payer keeps paying.