Concurrent Review: The UR Nurse's Workflow Guide

A concurrent review is the payer's ongoing check, during an active stay, that a patient still meets medical necessity for their current level of care, and the concurrent review nurse is the person who gathers the clinical evidence, submits it, and defends it. This guide walks through that workflow step by step, with a worked example.

What Is Concurrent Review in Healthcare?

Concurrent review is the utilization review process that runs while a patient is still actively receiving care. A reviewer, usually an RN, checks the chart against the payor's medical necessity criteria and confirms the current level of care is still warranted, often while managing dozens of open cases and payor timelines at once.

Concurrent review meaning in plain terms

You gather clinical documentation, submit or update a service request, track the authorization window, take peer-to-peer calls when a reviewer pushes back, and repeat at every payor-mandated interval until discharge or step-down.

How it differs from prior auth and retrospective review

The stakes differ too: a concurrent review failure can stop reimbursement mid-stay. We break the full workflow down further in our concurrent review guide for behavioral health.

Why Concurrent Review Matters in Behavioral Health

Concurrent review carries higher stakes in behavioral health because authorization is the revenue. A residential stay, PHP, or IOP episode only gets paid while an active authorization covers it, and payors re-approve it in short increments based on medical necessity under ASAM 4th Edition or similar criteria.

Medical necessity and continued-stay criteria

Every continued-stay request must show the client still meets level-of-care criteria: acute withdrawal risk, relapse risk, functional impairment. A single missing note or delayed assessment can trigger an automatic denial, and UR nurses juggling dozens of cases across payors know how easily that happens.

The cost of a missed review window

Miss the authorization window and you face a denial, a peer-to-peer call to schedule, and days of A/R aging while the client keeps occupying a bed. Behavioral health practices lose a meaningful share of revenue to preventable denials like these, which is why tracking tools built for UR workflows matter (Utilization Review Software Guide | CriteriaIQ).

What Does a Concurrent Review Nurse Actually Do?

A concurrent review nurse at a behavioral health facility runs the ongoing case for medical necessity: gathering clinical data, writing the continued-stay narrative, and tracking each payor's authorization window. Miss a deadline or omit a note, and the result is rework or a denial that adds to the 10-20% of potential revenue behavioral health practices lose to preventable billing mistakes and claim denials (Pimsy).

Chart review and clinical data gathering

Each morning you pull new clinicals from Kipu: nursing notes, provider progress notes, ASAM dimension updates, medication changes, and any incidents. You're building the evidence trail that justifies the current level of care, whether residential, PHP, IOP, or detox.

Writing the continued-stay narrative

You translate that chart into a payor-facing summary: criteria met, barriers to step-down, treatment plan response, and projected length of stay. If the payor pushes back, you prep for the peer-to-peer call (our P2P guide).

Tracking authorization windows across payors

You monitor concurrent review due dates, determination timelines, and A/R exposure across every payor, often in spreadsheets alongside the EMR.

The Concurrent Review Workflow, Step by Step

Every concurrent review follows the same five steps, whether you run detox or residential. The payor changes; the workflow does not.

Step 1: Gather clinical documentation from the EMR

Pull the chart pieces the payor will ask for: the biopsychosocial, nursing notes, the most recent ASI or equivalent assessment, medication administration records, and the treatment plan. In Kipu, this means hopping between tabs and exporting PDFs. Most UR teams supplement with spreadsheets tracking which documents each payor already has.

Step 2: Apply payor criteria (ASAM, InterQual, MCG, or proprietary)

Match the clinical picture to the criteria the payor uses. ASAM 4th Edition governs most SUD reviews; some payors run InterQual or MCG; others use proprietary medical necessity checklists they may not share. This is where a missed criterion, an outdated risk assessment, or a note that never made it into the chart becomes an automatic denial later.

Step 3: Submit the review and log the reference number

Send the service request form through the payor portal or fax, then log the authorization window, reference number, and reviewer name. If you do not write down the reference number, every follow-up call starts with ten minutes of verification.

Step 4: Follow up, respond to pend requests, and document the determination

Check status before the initial determination window closes. Pend requests usually mean one specific document is missing; respond the same day. When the determination arrives, log the approved units, the level of care, and the next review date. As Steven Cavan writes at CriteriaIQ, the determination log is what protects you at step-down and at appeal.

Step 5: Escalate to peer-to-peer when the initial review is denied

Request the P2P within the payor's deadline, often 24 to 72 hours. Prepare the physician with the exact criteria the denial cites, the CARC or RARC code if issued, and the two or three chart facts that answer it. A focused P2P turns many denials into approvals; an unprepared one burns your clinician's hour for nothing.

A Concurrent Review Example: Residential SUD, Day 12

The clinical picture and chart pull

A 34-year-old client is on day 12 of residential treatment for alcohol use disorder. ASAM Dimension 4 shows active withdrawal risk at admission, now managed; Dimensions 5 and 6 show relapse at 10 days sober after an IOP step-down failed in March. You pull the intake assessment, nursing notes, the ASAM-informed treatment plan, and group attendance records.

The continued-stay narrative, annotated

Your continued-stay request maps each dimension to criteria: "Client requires 24-hour structure (Dim 4: seizure history at last taper attempt 3/2); outpatient step-down attempted and failed (Dim 6)." You attach the medication log, the 3/14 nursing note documenting craving escalation, and the revised discharge plan targeting PHP. One missing sleep-study note from day 3 is flagged before submission, not after a denial.

The payor response and next actions

The payor approves 4 additional days, ending 3/21, and requests a peer-to-peer if stay extends further. You calendar the new authorization window, notify the clinical director, and set the day-18 review. Tools like CriteriaIQ assemble this packet against payor criteria inside Kipu, cutting the chart chase; the peer-to-peer prep and the clinical judgment stay yours.

Where Concurrent Reviews Break Down (and How to Fix It)

Spreadsheet and shared-inbox tracking gaps

When you run dozens of concurrent reviews across payors, a spreadsheet row or inbox thread becomes the system of record. Determination dates get buried, follow-up windows slip, and nobody notices until a payor closes an authorization window. The fix is a single tracker where every case has a next-action date, not a note someone has to remember.

Missing notes and late assessments

Most denials at this stage are documentation failures: a nursing note not filed before the review call, or an assessment pushed a day past the payor's look-ahead. Build a checklist per level of care (residential, PHP, IOP, detox) tied to ASAM 4th Edition criteria, and confirm chart completeness the day before each review, not the hour of.

When to move tracking into your EMR or a UR tool

If you are re-keying the same data into Kipu and a spreadsheet, or missing P2P deadlines weekly, manual tracking has hit its ceiling. Kipu covers documentation; dedicated UR tools like Ritten and Behave Health add payor-specific tracking. CriteriaIQ runs on top of Kipu or BestNotes, flagging upcoming review dates and missing-document risks per case. Its honest limit: it is UR-specific, so billing and claims still live elsewhere.

Concurrent Review Nurse Jobs: Requirements and Remote Path

Typical licensure and experience requirements

Most concurrent review nurse roles require an active RN license, and many payors and facilities prefer a BSN plus several years of direct clinical experience. Behavioral health UR positions usually ask for familiarity with ASAM criteria and payor-specific medical necessity policies, since you will be arguing level-of-care decisions against them daily. Some roles accept LPNs for tracking and documentation support, but peer-to-peer calls and determinations generally sit with RNs or licensed clinicians. Employers also tend to look for candidates who can show a track record of clean, well-documented authorization submissions, because a pattern of avoidable denials is the fastest way to lose a UR role. If you are coming from bedside care, expect the interview to probe how you prioritize competing deadlines across multiple payors rather than your clinical depth alone.

Remote vs on-site roles and what payors and facilities look for

Remote concurrent review jobs are common because the work is chart-driven: you read documentation, call providers, and log determinations, none of which requires a bedside. Treatment centers hiring remote UR nurses look for self-direction across multiple payor timelines, comfort working inside their EMR, and reliable availability during authorization windows. Payor-side roles emphasize criteria application and call documentation.

Skills that transfer from bedside to UR

Chart assembly, clinical reasoning under time pressure, and concise communication all carry over from direct care. Fluency with ASAM's dimension-based framework is the specific gap most bedside nurses close first.

How to Run Concurrent Reviews Across Multiple Payors Without Losing Track

A comparison of tracking approaches, honestly scored

Most UR teams still track concurrent reviews in spreadsheets and shared inboxes. That works at five active cases; it fails at fifty, when each payor has its own authorization window, medical necessity criteria, and P2P scheduling quirks.

Score the options honestly:

• Spreadsheets and manual UR tracking. Free and familiar, but nothing flags a review due tomorrow or logs a payor's verbal determination. Every follow-up lives in someone's memory.
• Kipu Health. Your EMR holds the clinical chart and some UR documentation, but payor-by-payor tracking across levels of care still leans on exports and side systems.
• Ritten and Behave Health. Broader behavioral health operations platforms; UR is one module among many.
• CriteriaIQ RCM. Built for UR staff on Kipu, tracking each case's authorization window, criteria set, and P2P status, with denial codes like CARC/RARC logged for appeals.

Where we fall short: if you run BestNotes or an EMR outside our integrations, or you want UR bundled with billing and admissions, CriteriaIQ is narrower than a full-platform build. Choose accordingly.

FAQ

Is concurrent review the same as utilization review?

Utilization review is the umbrella; concurrent review is one stage of it. UR covers the whole authorization lifecycle, while concurrent review specifically runs during an active stay to confirm continued medical necessity. Prior authorization happens before admission and retrospective review after discharge, so all three sit under UR but answer different questions.

How often does a payor require a concurrent review during residential treatment?

There is no single fixed interval; each payor sets its own review cadence, and behavioral health payors typically approve short increments of days rather than the full stay. Residential and detox cases often require re-authorization every few days to a week, so calendar each payor's next review date the moment a determination arrives.

Can a concurrent review denial be appealed, or is peer-to-peer the only option?

Peer-to-peer is usually the first response, requested within the payor's deadline, often 24 to 72 hours, and a focused call can reverse many denials. If the P2P fails, a formal appeal is still available, which is why logging the determination, approved units, and any CARC or RARC codes matters for your appeal.

Do concurrent review nurse jobs require RN licensure, or can an LPN or clinician do them?

Most roles require an active RN license, and many employers prefer a BSN plus several years of direct clinical experience. LPNs can sometimes take tracking and documentation support roles, but peer-to-peer calls and determinations generally sit with RNs or licensed clinicians. Behavioral health UR positions also expect fluency with ASAM criteria.

What is the difference between concurrent review and continued utilization review?

They describe the same activity from different angles. Concurrent review is the stage name for the process running during an active stay; continued utilization review, sometimes called continued-stay review, is the specific task of re-proving medical necessity at each payor-mandated interval. In practice, UR nurses use the terms interchangeably.