ASAM Criteria and Levels of Care

What it is

ASAM Criteria is a clinical decision framework created by the American Society of Addiction Medicine that organizes substance use disorder treatment into standardized levels of care. Levels range from early intervention and outpatient services to intensive outpatient, partial hospitalization, and multiple tiers of residential and inpatient withdrawal management.

Commonly referenced levels include, for example:

• Level 0.5: Early intervention
• Level 1: Outpatient services
• Level 2.1: Intensive outpatient services (IOP)
• Level 2.5: Partial hospitalization services (PHP)
• Level 3.1, 3.3, 3.5, 3.7: Residential and inpatient services with increasing intensity
• Level 4: Medically managed intensive inpatient services

ASAM Criteria also uses six clinical dimensions, such as withdrawal potential and relapse risk, to determine which level is medically appropriate. The framework is copyrighted and licensing controlled by ASAM, so payers, states, and providers usually reference it by level and dimension rather than reproducing the full tool.

In revenue cycle, ASAM levels are not billing codes by themselves. They are clinical labels that are commonly mapped to specific HCPCS/CPT codes, revenue codes, and state-defined rate codes that drive what pays and what denies.

Why it matters operationally

For behavioral health and substance use treatment centers, ASAM Criteria sit behind several revenue-critical steps: benefits verification, prior authorization, ongoing utilization review, and audit defense. If the level of care documented or authorized under ASAM does not match the level you bill, you invite medical-necessity denials, non-covered service denials, and recoupments.

Common operational uses:

• Intake and clinical assessment teams determine ASAM level and severity, then request authorization tied to that level.
• Authorization teams submit level-specific requests, including ASAM level language, to the payer or behavioral health carve-out vendor.
• Billing teams map the authorized ASAM level to allowed billing codes and revenue codes on the claim.
• Utilization review teams document continued stay using ASAM dimensions to support concurrent auth and avoid units denied beyond the last approved date.

If any of those handoffs break, dollars sit in AR for months or get written off. For example, billing residential Level 3.5 services under an IOP or PHP code that was authorized for Level 2.1 will often produce CO-50 (not medically necessary) or CO-197 (authorization exceeded) denials, and sometimes post-payment audits with takebacks.

How it is used or read

You will see ASAM Criteria referenced in several places:

• State Medicaid manuals and SUD waivers, which often define coverage and rate tiers by ASAM level.
• MCO and commercial medical-necessity policies, which specify that SUD treatment will be reviewed using ASAM Criteria.
• Prior auth responses or clinical guidelines from carve-out vendors that list the approved ASAM level and, sometimes, the ASAM dimensions that justified the decision.
• Internal clinical documentation and treatment plans that state something like "Client meets ASAM 3.5 criteria based on Dimensions 1, 3, and 5."

Operationally, reading ASAM correctly means:

• Knowing which ASAM level your clinicians say the patient meets.
• Confirming which ASAM level the payer actually authorized and for what date range and units.
• Knowing how your state or payer maps that ASAM level to HCPCS/CPT, revenue codes, and place-of-service for billing.

Those three items must line up on every long episode of care. If the authorization reads "ASAM 3.1" and your team later documents the patient as meeting "ASAM 3.5" but does not update the payer, a change in billed codes or rate can trigger concurrent denial of days past the last reviewed date, or retroactive recoupment after a utilization audit.

• Billing an ASAM 3.5 residential stay with per-diem codes that your state or MCO reserves for ASAM 3.1, then being surprised when the payer pays at a lower rate or recoups after audit because the billed code did not match the authorized level of care.
• Submitting an initial authorization for ASAM 2.1 IOP, then stepping the patient up to ASAM 2.5 PHP mid-episode without a new auth and continuing to bill the higher-intensity code, which often leads to CO-197 denials for days beyond the last approved level.
• Using generic "residential" language in clinical notes without explicitly tying documentation back to an ASAM level and dimensions, which weakens medical-necessity support when the payer applies its ASAM-based policy and issues a CO-50 denial.
• Assuming all payers interpret ASAM levels the same way and using a single internal crosswalk for every plan, which results in mismatched HCPCS and revenue codes for certain state Medicaid or carve-out plans that have their own ASAM-to-code grids.
• Ignoring that a behavioral health carve-out vendor requires the ASAM level to be listed on the auth request and in progress notes, leading to CO-16 or N130 denials for missing information when the vendor tries to reconcile the claim to its ASAM-based utilization records.

In behavioral health, ASAM Criteria are most embedded in substance use disorder programs, especially IOP, PHP, residential, withdrawal management, and some community-based services. Many state Medicaid programs and SUD waivers adopt ASAM levels as the reference standard and then build custom billing code sets and rates for each level. That creates a tight chain: ASAM level informs auth, which informs allowed codes and rates.

Carve-outs add another layer. A commercial plan might outsource SUD management to a behavioral health vendor that uses ASAM Criteria very strictly, while the medical plan handles other MH services on different guidelines. If a claim reaches the wrong payer bucket or the ASAM level on the auth does not match the level implied by the billed code, you can see CO-96 or CO-97 denials and long back-and-forth between the main plan and the carve-out.

Long episodes and per-diem models are especially exposed. Residential stays at ASAM 3.1 or 3.5 can run 30, 60, or 90 days. If concurrent auth and ASAM documentation are not kept current, a payer can approve only the first portion of the stay or later decide that the client should have been stepped down sooner under ASAM. That often shows up as CO-197 on back-end units and, in Medicaid, can drive retrospective utilization reviews that claw back large blocks of revenue.

Managed Medicaid and MCOs often publish ASAM-aligned provider manuals, but the details differ. Some define separate billing codes and daily rates for ASAM 3.1 versus 3.5, others bundle all residential into a single code but use ASAM only for auth. Knowing which model applies by plan is critical for accurate benefits verification, correct auth requests, and clean claims.

AI can help with ASAM-related work by reading intake and clinical notes, identifying the documented ASAM level and key dimensions, and comparing that to the level, dates, and units on the authorization and benefit plan. That lets an agent flag mismatches before submission, such as a claim that uses a residential per-diem code commonly mapped to ASAM 3.5 when the auth is for ASAM 3.1, which is a classic setup for CO-50 or CO-197 denials.

Supabill can keep payer-specific ASAM-to-code rules and state Medicaid grids in memory, then apply those rules at claims-scrub time and during benefits verification. A Supabill denials agent can also read every 835, classify CO-16, CO-50, CO-96, CO-197, N130, and MA130 denials back to ASAM or auth misalignment patterns, and surface which payers or programs are out of sync. Humans still own clinical judgment about the correct ASAM level, direct conversations with utilization reviewers, and any appeal letters that argue medical necessity using ASAM dimensions.

What are the main ASAM levels of care that affect billing for SUD services?

For revenue cycle purposes, the ASAM levels you will see most often are: 0.5 (early intervention), 1 (outpatient), 2.1 (intensive outpatient), 2.5 (partial hospitalization), 3.1/3.3/3.5/3.7 (various intensities of residential and inpatient withdrawal management), and 4 (medically managed intensive inpatient). You do not bill the ASAM level itself. Instead, each level is commonly mapped by state or payer to specific HCPCS or CPT codes and revenue codes, such as per-diem H-codes for residential or time-based psychotherapy codes for outpatient. The mapping is payer-specific and you should always confirm it in the payer or Medicaid provider manual rather than assuming that ASAM 3.5, for example, is billed the same way across plans. Source

Are payers required to use ASAM Criteria for substance use disorder coverage decisions?

Many state Medicaid programs and managed care organizations adopt ASAM Criteria in state plans, waivers, or medical-necessity policies for SUD services, but the exact requirement and implementation vary by state and program. Some commercial payers and behavioral health carve-out vendors also use ASAM Criteria or a closely related framework for level-of-care decisions. From an operational standpoint, you should treat the payer's published policy as the rulebook: if the policy references ASAM, your documentation, auth requests, and continuing stay reviews should explicitly use ASAM levels and dimensions; if it references another tool, you may need to align to that instead. Source

Is ASAM Criteria only for substance use disorder, or can it apply to mental health treatment too?

ASAM Criteria are primarily designed for substance use disorder and withdrawal management. Many clients in SUD programs have co-occurring mental health diagnoses, and the ASAM dimensions take psychiatric conditions into account when determining level of care, but the framework itself is not a general psychiatric level-of-care tool. Some payers use different guidelines, such as proprietary behavioral health criteria, for non-SUD mental health services. For operations, that means you might have one set of documentation and authorization expectations for SUD services that reference ASAM, and a separate set for pure mental health services that follow a different clinical framework. Source

How should clinical documentation reference ASAM to support claims and avoid denials?

Clinical notes should clearly state the ASAM level of care (for example, "Client meets ASAM 2.1 Intensive Outpatient"), reference at least the key ASAM dimensions driving the decision, and tie those to observable symptoms, risks, and supports. For continued stay or step-down, notes should explain why the client continues to meet the current level or why a different ASAM level is now appropriate. From a billing standpoint, this lets you show auditors and medical reviewers that the level billed and the level authorized are both supported by ASAM-based documentation. Many teams use structured templates or tools, such as Supanote-style documentation frameworks, to prompt clinicians to include ASAM level and dimensions consistently. Source

What if a payer uses different language than ASAM levels in its manuals or authorizations?

Some payers, especially commercial plans and older contracts, describe services using terms like "IOP," "PHP," or "residential" without explicitly naming ASAM levels, even when they are effectively applying ASAM-like criteria. In those cases, crosswalk the payer's service descriptions to your internal ASAM understanding and confirm with the payer or rep when in doubt. For example, a plan might call a service "high-intensity residential" that functionally matches ASAM 3.5, but the billing codes allowed under that benefit could differ from your state's ASAM-based Medicaid grid. When you see frequent CO-50 or CO-96 denials around those services, it is a sign that your internal mapping to the payer's service categories may not match how the plan actually interprets level of care. Source

• ASAM, The ASAM Criteria
• SAMHSA, Substance Use Treatment
• Medicaid, Benefits