Guide · Level of care denials

How to prevent level-of-care denials in IOP and PHP.

A level-of-care denial usually starts weeks before the claim. The chart says one level, the site log another, the authorization covers a third, or it ran out before anyone asked for more days. Catch the disagreement in the week it happens and most of these never reach the payer.

By Sunny BinjolaOctober 13, 2026From our own census checks

This is the operations side. Clinicians decide the level of care; this page is about every record showing that decision on the same date.

The weekly check The five billing census checks

Four records, one levelIllustrative

PayerAuthorizationThe approved level, dates and unitsPHP to 3/14

EMRChartThe level the clinicians set, and since whenPHP since 3/2

SiteAttendance logThe program each client attended that dayIOP on 3/10

BillingClaimThe code for the level billed that dayPHP on 3/10

All four agreeBill it

One disagreesFix the record first

Fig. 1 Invented example: the log says IOP on a day the other three say PHP.

01Where it starts

Five ways the records drift apart.

None of these is a clinical mistake. Each is a record that did not catch up with a decision someone already made.

The level changed, the authorization did not: A step-up or step-down is recorded in the chart, but the authorization still covers the old level. Days billed at the new level have nothing behind them.
The log and the chart disagree: The site log records a different program than the EMR, often because the log is kept by hand and the change reached one before the other.
The authorization ran out: The approved dates or units ended before the next review was submitted. Care continued; the approval did not.
Two levels on one date: A client appears in two programs on the same day. Many payers pay one level of care per client per day, so one of the two records is usually wrong.
The claim and the approval name different services: The code on the claim belongs to one level and the approved service to another. Check your payer's policy for which codes and service types go together.

02Who owns what

Four records, four owners.

Each record has a different keeper, which is why nobody sees the disagreement until a denial arrives. Name the owner of each one, and one person who compares them.

Record	Holds	Usually kept by
Chart (EMR)	The level of care and its effective date	The clinical team
Authorization	Approved level, start and end dates, units, next reviewPayer, plan and reference number	Utilization review or admissions
Site log	Who attended which program, each day	Site staff
Claim	The level billed for each date	Billing, in house or a billing company

Fig. 2 Typical roles. Who keeps each record differs by organization; write yours down.

03The weekly check

A weekly level-of-care check, before the claims go out.

Once a week, line up the four records for every client day and list only the days where they disagree. Run it before your billing company works the week, so a fix is a correction, not an appeal.

Level-of-care check, one weekSample data

Record and date	Chart	Site log	Authorization	Claim	Flag
R-3108Tue 3/10	PHP	IOP	PHP to 3/14	PHP	Log and chart differ
R-2276Wed 3/11	IOP	IOP	PHP to 3/9	IOP	Billed level not authorized
R-5521Thu 3/12	PHP	PHP	PHP to 3/14	PHP	Review due in 2 days, none logged
R-4410Thu 3/12	IOP	IOP + PHP	IOP to 3/28	IOP + PHP	Two levels on one day
R-1987Fri 3/13	IOP	IOP	IOP to 3/28	IOP	All four agree

Fig. 3 Invented record codes and dates. Patient-level, so it stays with the operations team and never reaches a leadership board.

A flag is a question for a person, not a verdict. Sometimes the log is right and the chart is late; sometimes the reverse. The person who owns the record decides and corrects it.

04Review dates

Track three dates for every open authorization.

Concurrent review schedules depend on the payer, the plan and the level of care. Rather than relying on a rule of thumb, keep the dates the payer actually gave you.

One authorizationIllustrative

Units used: 16 of 25

Start and endThe approved dates

Next review dueThe dashed line: ask before it, not after

Units usedAgainst units approved

Fig. 4 Invented numbers. A review submitted after the end date is a gap no claim can cover.

05Step-down day

What has to change on a step-down day.

When a client moves from PHP to IOP, or up the other way, four things change. The date is what matters.

ChartThe new level, with its effective date.
Site logThe client's program from that day.
AuthorizationApproval for the new level, requested before the first day at it.
ClaimThe new level's code from that date onward.

Same effective date in all four

06Self-check

Could you answer yes to these for last week?

Tick what is true today. Nothing is saved or sent.

Every client whose level changed this week has the same effective date in the chart, the log, the authorization and the claim.
Nobody was billed at a level the current authorization does not cover.
Every open authorization has an end date and a next review date written down.
Every review due in the next three days has someone assigned to it.
Units used are tracked against units approved, by client.
No client has two levels of care on the same date.
Each site uses the same program names and row colors on its log.
A difference found this week is fixed this week, before the claim goes out.

07Where we stand

What we run, and what we do not.

Level-of-care disagreement is one of the five billing census checks. Our version compares each site's log with the EMR; a person decides each flag.

BuiltA comparison of a site's log with the EMR, client by client and day by day, that flags program differences. Used at a five-center network in October 2026.
Not builtAuthorization dates and units in the same check. That needs authorization data the engine does not read today.

Not claimed: a reduction in denials or recovered revenue. Neither has been measured. Length of stay and level of care are clinical decisions, not measures of better care.

08Questions

What operators ask about level-of-care denials.

What is a level of care denial?

A claim the payer refuses because the level of care billed does not match what it approved or what the record supports. In practice it often means two records disagree: the authorization covers one level and the claim bills another, or the authorization ran out before the next review.

What is utilization review in behavioral health?

The payer's review of whether care is medically necessary at the level being provided: before treatment starts, during treatment (concurrent review) and sometimes after discharge. Most treatment centers have staff who prepare and present these reviews.

What is concurrent review?

A review during treatment to approve more days or units at the current level. The schedule depends on the payer, the plan and the level of care, so track the next review date for every open authorization instead of relying on a general rule.

Can IOP and PHP be billed on the same day?

Treat it as a flag. Many payers pay one level of care per client per day, so two levels on one date usually means one record is wrong. Your payer's policy and contract decide.

Who decides the level of care?

Clinicians, using the criteria the payer applies, such as the ASAM Criteria for substance use treatment. Operations and billing make sure every record reflects that decision on the same date. This page is not clinical, legal or coding advice.

What has to change on a step-down day?

Four things, with the same effective date: the level in the chart, the program on the site log, the authorization for the new level, and the code on the claim from that date onward.

Do your chart, log, authorization and claim agree for last week?

Bring one week to a free 20-minute call. We will show you where the four records come from in your systems, and which checks your data supports.

Book a free 20-minute call Behavioral health operations