Concurrent Review

What concurrent review is

Concurrent review is a utilization management process that happens while a patient is still in treatment. A payer nurse or clinical reviewer evaluates new clinical information, compares it to the plan's criteria, and decides whether to continue, modify, or end authorization for the current episode.

In behavioral health, concurrent review usually applies to per-diem and high-frequency services. Think inpatient psych, detox, residential, PHP, and IOP. The payer grants an initial authorization for a set number of days or units, then requires regular concurrent reviews to renew that approval for the next block.

Operationally, concurrent review sits between clinical care and billing. Clinicians generate notes and treatment plans, utilization review staff submit them to the payer, and your billing team relies on those approvals to bill without medical-necessity or no-auth denials.

Why concurrent review matters operationally

Every missed or late concurrent review risks an avoidable denial for some or all days in an episode. Common outcomes:

• Services beyond the last approved date deny as no auth or not medically necessary (often CO-197, CO-50, or CO-16 supported by N130 or MA130 in the remit).
• Only a subset of days gets paid if the payer back-dates or partially approves the review.
• Accounts get stuck in AR while your team scrambles for retro auth or appeals, which jeopardizes timely filing limits.

For long behavioral-health episodes, concurrent review directly shapes revenue. Residential or PHP per-diem rates multiplied by 5 to 10 denied days can mean tens of thousands of dollars written off. A smooth concurrent review process keeps clinicians, UR staff, and billers aligned on:

• Next review due dates and required documents.
• Exactly which days or units are approved.
• When treatment continues as self-pay or charity care if the payer stops approving.

Supabill's agents help by tracking approval ranges at the patient-authorization level, comparing them against scheduled days, then flagging upcoming concurrent review windows before they threaten revenue.

How concurrent review is used and how to read it

In practice, concurrent review plays out as a repeating cycle:

• Payer grants initial authorization for a defined period or unit count.
• Before the last approved day, your UR team submits updated clinicals for concurrent review.
• Payer issues a decision that extends, modifies, or ends the auth, usually documented in a portal, fax, letter, or 278 response.

RCM teams need to translate that into billing rules. Key details to capture and review every time:

• Start and end dates of the new approved period, or exact unit counts.
• Levels of care or CPT/HCPCS codes tied to the approval (for example authorization tied to ASAM level, or to H0010 vs H0011).
• Any stated clinical criteria that justify ending coverage.

When remits arrive, you tie concurrent review decisions to denial patterns. If days 1 to 7 pay but days 8 to 12 deny with CO-197 and N130, you likely missed a review deadline or billed beyond the approved range. If days beyond an approved date deny with CO-50, the payer is signaling a medical-necessity issue rather than pure missing auth.

Supabill's claims and denials agent reads each 835, recognizes when a CO-197 or CO-50 is tied to days past the last approved concurrent review, and classifies that as a concurrent-review failure instead of a generic auth or medical-necessity denial. That lets you fix workflows at the source. Humans still have to handle the clinical conversations with payer reviewers and decide when to appeal versus shift to self-pay or discharge.

• Letting concurrent review dates live only in a paper calendar or a clinician's email, so the team misses the review deadline and days 8 to 14 of a residential stay deny with CO-197 and N130 as no authorization on file.
• Assuming an initial 7-day inpatient psych auth covers the full expected 14-day stay, so billing submits all 14 days and only finds out at remit time that days 8 to 14 were never approved and are now outside timely filing for retro review.
• Not updating the billing system with shortened concurrent approvals, for example when a payer approves only 3 more PHP days instead of the 5 requested, leading to CO-50 or CO-197 denials on the last 2 days.
• Ignoring level-of-care changes during concurrent review, such as a payer shifting a patient from residential to PHP level, and then continuing to bill H0010 per diem instead of the newly approved partial hospitalization codes.
• Treating concurrent review denials as generic auth errors in reporting, which hides the pattern that specific payers or certain ASAM levels are consistently getting cut short at the second or third review.

Behavioral health is heavily exposed to concurrent review because treatment often runs weeks or months and is structured as per-diem or high-frequency services. Inpatient psych, detox, residential, PHP, and IOP are typically carved out to behavioral-health vendors that run their own utilization management criteria and review cycles separate from the medical plan.

Carve-outs create a double-administration problem for your RCM team. The medical payer coverage might show as active at benefits verification, but the behavioral-health vendor controls the concurrent review clock, clinical criteria, and approval windows. If your UR staff misses the vendor's specific review timing or documentation requirements, you can see clean-claim denials for days well inside coverage dates because the concurrent review lapsed.

State Medicaid and Medicaid MCOs often use very structured concurrent review schedules for behavioral health, for example reviews every 3, 7, or 14 days depending on level of care. Approval ranges can change with each review as the member steps down from inpatient to residential to PHP to IOP. Your system has to track each pivot or you risk billing the wrong revenue codes or days beyond the last approved segment.

Long episodes create outlier financial exposure. A 45-day residential SUD stay billed at a per-diem rate becomes a major write-off if concurrent review stops at day 21 and no appeal is filed. Getting concurrent review right in behavioral health is not just compliance, it is core to protecting revenue on your highest-dollar episodes.

AI can help with concurrent review by doing the tedious tracking and cross-checking that humans struggle to keep current across hundreds of patients. An agent can watch auth start and end dates, compare them against scheduled or actual days of service, mine payer portals and faxes for new approval letters, and flag accounts that are approaching or past the last approved day so UR staff can submit clinicals on time.

Supabill's authorization and denials agents keep state at the patient-episode level, store payer-specific rules for concurrent review timing, and read 835 remits to tag when CO-197, CO-50, N130, or MA130 point to a failed concurrent review. That gives your team a prioritized queue of cases to fix before claims go out or before appeal windows close. The limit is clinical judgment and negotiation: AI cannot attend peer-to-peer calls or decide when treatment is still clinically appropriate, so human clinicians and UR leads still own the conversation with payers and the decision to appeal, discharge, or move to self-pay.

Is concurrent review the same as prior authorization in behavioral health?

Concurrent review and prior authorization are related but not the same. Prior authorization is the initial approval that allows treatment to start for a defined number of days or units. Concurrent review happens during the episode, before the last approved day or unit, and decides whether to extend or end that authorization. In behavioral health, inpatient, residential, PHP, and IOP often require both an initial auth and then multiple concurrent reviews as the stay continues. Source

How often do payers require concurrent review for inpatient or residential behavioral health stays?

Frequency varies by payer, plan, and level of care. Some commercial plans review every few days early in an inpatient psych admission, then every week or two once the case stabilizes. State Medicaid and Medicaid MCOs often publish structured schedules, such as an initial block of days followed by reviews at set intervals for continued stay. Your UR team should build payer-specific rules into workflows instead of assuming a standard 7- or 14-day pattern. Source

What should RCM teams capture from each concurrent review decision for billing accuracy?

At minimum, RCM should capture the authorization number, the exact approved date range or unit count, the level of care tied to the approval, and any stated limitations or step-down requirements. That information should update your practice management or billing system so claims only bill approved days and appropriate codes. Tracking these details also helps your denials team connect CO-197 or CO-50 denials to specific missed or shortened concurrent reviews rather than treating them as generic auth issues. Source

Can payers approve fewer days than requested during concurrent review?

Yes. Payers often grant fewer days than requested, especially as a case progresses. For example, your UR team may request 7 more residential days and the payer may approve only 3, or may condition approval on a step-down to a lower level of care. Billing must match what is actually approved, not what was requested, or you risk partial payment and denials for the non-approved days. Source

What are common denial indicators that point to concurrent review problems rather than pure lack of coverage?

Watch for patterns where earlier days in a stay pay, but later days deny with CO-197, CO-50, or CO-16, often with remark codes like N130 or MA130 that mention missing authorization or medical necessity. When coverage is active and only the tail end of an episode is denied, that usually indicates a missed or adverse concurrent review decision, not a generic eligibility issue. Source

• CMS, Utilization Review Information
• Medicaid.gov, Managed Care and Utilization Management
• SAMHSA, Behavioral Health Services Coverage