Level-of-care denial

What a level-of-care denial is

A level-of-care denial is when the payer agrees services occurred but disagrees with the intensity, setting, or program billed. The payer is saying the member did not meet criteria for that level of care on some or all of the billed days.

In remittance language, this usually appears as a medical necessity or appropriateness denial that is specific to the place of service or program intensity. Common patterns are: residential denied as only intensive outpatient appropriate, PHP cut back to standard outpatient, or detox days trimmed because acute withdrawal criteria were not met.

This is different from a pure medical-necessity denial that says the service itself was not needed. Level-of-care denials say a different, usually less intensive, service should have been provided and paid instead.

Why level-of-care denials matter operationally

Level-of-care denials hit high-dollar episodes: residential, withdrawal management, PHP, and IOP per-diem claims. A single denial can wipe out weeks of expected revenue and spike days in AR if your team chases preventable disputes.

Operationally, these denials point to gaps in three places: admission and placement decisions, documentation that ties to level-of-care criteria, and utilization management workflows like concurrent review and continued-stay reviews. If those do not line up, you end up providing a higher level of care than the payer is willing to fund.

Because level-of-care disputes often go to peer-to-peer review or formal appeal, they eat clinical and administrative time. That cost is real even if you win the money back. Tracking patterns by payer, program, diagnosis, and criteria set (ASAM, LOCUS, CALOCUS) is essential to decide whether you need to change front-end placement or push back on payer practices.

How level-of-care denials show up and how they are used

On the remit, a level-of-care denial is usually coded as a medical-necessity or appropriateness adjustment that refers to the level of care, not just the code. Common combinations are a Claim Adjustment Reason Code (CARC) like CO-50 with a Remittance Advice Remark Code (RARC) such as N130 that tells you to review the medical policy, guidelines, criteria, or plan documents.

Payers rely on internal medical policies and level-of-care criteria like ASAM, LOCUS, or plan-specific rules. For each denied day or visit, the payer utilization reviewer usually documents which criteria were not met. That internal note is what you are arguing against in peer-to-peer review or appeal.

From a process standpoint, handling a level-of-care denial typically means:

• Pulling the full clinical record for the disputed days, including nursing flowsheets, CIWA/COWS scores, safety checks, and collateral information.
• Mapping the documented symptoms and risks back to the plan's stated level-of-care criteria.
• Requesting peer-to-peer review within the plan's time window when available.
• Submitting a written appeal that cites specific criteria and clinical facts when peer-to-peer is not available or is unsuccessful.

Your workflow should separate level-of-care denials from routine coding or eligibility issues, since the fix is clinical documentation and criteria alignment, not a quick rebill.

• Treating a CO-50 with an N130 remark on a residential stay as a simple coding denial and just resubmitting the same UB-04, instead of escalating for clinical review tied to the plan's level-of-care criteria.
• Letting concurrent review fall behind during a long detox or residential episode, so days 6-10 deny as not meeting continued-stay criteria even though the documentation exists in the EMR but was never faxed or uploaded to the payer.
• Using ASAM language in notes for a substance use residential stay without actually documenting the specific ASAM dimensions and risk ratings, which leaves your appeal weak when the payer auditor has to score those criteria line by line.
• Admitting a member to PHP or IOP when the benefits were carved out to a separate behavioral TPA, then getting a level-of-care or non-covered setting denial because the contracted program type for that payer is different from your clinical model.
• Ignoring plan-specific level-of-care policies for Medicaid managed care, so you bill withdrawal management as inpatient or residential and get hit with repeated appropriateness denials that were predictable from the contract and policy bulletins.

Behavioral health is heavy with level-of-care disputes because payers use detailed criteria (ASAM, LOCUS, CALOCUS) to gate access to detox, residential, PHP, and IOP. A detox or residential admission that feels clinically obvious to your team can still deny if the note on day 1 does not hit the right dimensions, risk scores, and failed lower levels of care that the plan expects.

Carve-outs add another trap. A member may have medical benefits with one payer and behavioral benefits with a separate TPA. If your front desk or verification process misses that, you can easily admit to residential or PHP under the wrong plan and then see a denial framed as inappropriate level of care or non-covered setting.

Long per-diem episodes like residential, withdrawal management, and IOP are especially vulnerable. Payers often approve an initial span, then use concurrent and continued-stay reviews to trim back later days, claiming the member should have stepped down to PHP, IOP, or outpatient. Clean claims still deny for days beyond the last authorized level of care, which distorts your denial stats unless you track unit-level authorization alignment.

Medicaid and Medicaid managed care add state-specific rules. Some states tightly restrict IMD or residential days, require specific state assessment tools (like LOCUS or state SUD criteria), or demand documentation of failed community-based care before approving higher levels. If your team does not know those rules and align documentation and treatment planning, you see systematic level-of-care denials that are very hard to overturn after the fact.

For level-of-care denials, AI agents can scan 835 files and classify every CO-50 or similar adjustment with related remark codes, then group them by program, payer, and level of care. Agents can also read authorization spans, compare them to billed dates, and flag high-risk episodes where level-of-care disputes are likely, so your utilization review team can prioritize concurrent reviews before days start denying.

Supabill's denials agent can read each remit, tag potential level-of-care issues, pull the associated 837 data, and summarize patterns for human review, while a benefits-verification agent helps catch behavioral carve-outs before admission. The clinical judgment still belongs with humans: deciding whether the documented risk truly meets ASAM or LOCUS criteria, handling peer-to-peer reviews, and shaping appeal letters that cite the right clinical nuances and state or plan policies.

How can I tell if a denial is really about level of care and not just medical necessity?

Look for a medical-necessity style CARC, such as CO-50, paired with remark codes or payer notes that reference level-of-care criteria, setting, or intensity. If the payer says a lower or different setting would have been appropriate, that is a level-of-care denial, even if the CARC itself is broad.

Can I fix a level-of-care denial by changing the place of service or revenue code?

Usually no. If the denial is truly about appropriateness of setting, simply rebilling with a different place of service or revenue code without matching documentation and authorization can trigger new denials or audits. You typically need clinical review, possible peer-to-peer, and a documented rationale for the billed level of care.

Who should own level-of-care denials in a behavioral health facility?

Ownership should be shared: revenue cycle tracks and categorizes the denials, but utilization management and clinical leadership must handle the substance. UM staff manage concurrent reviews and criteria alignment, while clinicians participate in peer-to-peer calls and help craft appeals that reflect real risk and impairment.

Do level-of-care denials always require a peer-to-peer review?

Not always. Some plans offer peer-to-peer for these denials, others only allow written appeals, and some require both in sequence. Your team should maintain payer-specific playbooks so you know when a quick clinical call can rescue days before you move into a slower appeal cycle.

How can we prevent level-of-care denials for residential and detox stays?

Front-load criteria-based documentation at admission and throughout the stay, use structured tools like ASAM or LOCUS, and stay on top of concurrent and continued-stay reviews. Also make sure benefits-verification and authorization workflows correctly identify behavioral carve-outs and plan-specific limits before the patient starts treatment.

• X12: Claim Adjustment Reason Codes (CARC)