LOCUS and CALOCUS
LOCUS and CALOCUS are structured behavioral-health assessment tools that score clinical severity and support level-of-care decisions for adults (LOCUS) and children and adolescents (CALOCUS). Many Medicaid programs and commercial behavioral-health carve-outs require LOCUS or CALOCUS scoring to justify authorization and payment for specific levels of care.
What it means
What LOCUS and CALOCUS are
LOCUS (Level of Care Utilization System) and CALOCUS (Child and Adolescent Level of Care Utilization System) are standardized clinical tools used to rate symptom severity, functional impairment, risk, and support needs. Scores roll up into a recommended level of care, such as outpatient, intensive outpatient, partial hospitalization, residential, or inpatient.
LOCUS is designed for adults. CALOCUS is the child and adolescent version, with criteria tuned for developmental stage, family context, and school functioning. Payers often treat the LOCUS or CALOCUS score as the bridge between the clinical record and the requested level of care on an authorization.
In behavioral health revenue cycle, LOCUS and CALOCUS are not billing codes. They are clinical scoring frameworks that support medical-necessity and level-of-care determinations, which then drive prior authorization, continued-stay review, and payment decisions.
Why LOCUS and CALOCUS matter operationally
For many Medicaid and Medicaid-managed-care plans, a specific LOCUS or CALOCUS score range is required for admission and continued stay at higher levels of care such as PHP, IOP, or residential. If the score does not support the billed level, payers may deny for medical necessity (often with CO-50) or for exceeding an authorized level of care.
Concurrent review teams on the payer side frequently request updated LOCUS or CALOCUS scores at set intervals, such as every 7 or 14 days for residential or PHP. If the updated score is late or missing, claims past that date are exposed to denial. That can turn into 10 to 30 days of unpaid per-diem revenue stuck in appeals.
LOCUS and CALOCUS also matter for contract compliance. Behavioral-health carve-out vendors and state Medicaid programs often hardwire these tools into their utilization-management policies. If clinical teams use a different internal level-of-care rubric, the gap shows up as mismatched authorizations, under-authorized units, and higher denial rates on longer episodes.
How LOCUS and CALOCUS are used and read
Clinicians complete LOCUS or CALOCUS using a multi-domain scale. Each domain receives a score, which then aggregates into a total score or a level-of-care recommendation that maps to service intensity. Many payers publish crosswalks from LOCUS or CALOCUS scores to covered services and expected place-of-service or revenue-code combinations.
Operationally, the key data points are: the date the LOCUS or CALOCUS was completed, the score or recommended level of care, and the link to the specific authorization number and level of care that was requested. Revenue-cycle teams need those elements visible at scheduling, at admission, and before billing.
On the billing side, LOCUS or CALOCUS results should be reflected indirectly: in the documented medical necessity, in the service type authorized (for example, residential treatment versus IOP), and in the level-of-care indicators that show up in the authorization, the claim, and the utilization-review record. In appeals, attaching the scoring sheet and showing how the score lines up with the payer's own criteria is often the difference between a lost day rate and a reversed CO-50 or CO-197 denial.
Common mistakes
- Treating LOCUS or CALOCUS as optional documentation for residential stays, then getting CO-50 medical-necessity denials for days 15 and beyond because the payer's continued-stay policy explicitly requires updated scores every 7 days.
- Using an adult LOCUS score for a 16-year-old member even though the Medicaid contract requires CALOCUS for anyone under 18, which gives the payer a clean opening to deny or downgrade the level of care at concurrent review.
- Not tying the LOCUS or CALOCUS score date to the authorization span in the system, so the team bills per-diem residential days past the last documented score and runs into CO-197 for days that technically needed a new assessment.
- Upcoding the level of care based on program capacity instead of score-driven need, for example billing PHP (per diem) when the LOCUS supports IOP only, which leads to recurring CO-50 denials and potential audit exposure.
- Letting LOCUS or CALOCUS live only inside the clinical EHR without surfacing the score or level in the scheduling and RCM views, so front office and billing staff cannot quickly see whether a scheduled admission or step-up in care is supported by current scoring.
Why it matters in behavioral health
In behavioral health, LOCUS and CALOCUS are deeply tied to how payers manage intensity of services over long episodes. State Medicaid and Medicaid-managed-care plans often specify, in policy, which LOCUS or CALOCUS scores justify admission to IOP, PHP, or residential, and what score changes are expected before step-down. That scoring logic directly drives whether a 30-day residential stay is seen as medically necessary day by day.
Behavioral-health carve-out vendors commonly require LOCUS or CALOCUS as part of prior authorization and concurrent review. For example, a residential substance-use program might also be expected to show LOCUS scores if the member has co-occurring mental-health conditions. If the LOCUS does not support the higher mental-health level of care, the behavioral carve-out may authorize only SUD services, creating a split-payment situation and more complex billing.
For per-diem programs such as residential, PHP, and some IOPs, the LOCUS or CALOCUS update cadence becomes a financial control point. A missed reassessment can lead to CO-197 denials on dozens of days, even if the clinician notes support continued care. RCM teams need clear workflows so that LOCUS and CALOCUS updates are treated like expiring authorizations.
Some state Medicaid agencies and MCOs tie rate tiers to LOCUS or CALOCUS bands. A higher score may support a higher per-diem rate or an enhanced service package. If scores are not documented or transmitted correctly in utilization review, providers may be underpaid at a lower tier without realizing that their clinical data supported a higher one.
How AI can help with LOCUS and CALOCUS
AI can help with LOCUS and CALOCUS by capturing, structuring, and surfacing the key score and level-of-care data points so humans do not have to hunt through long progress notes. An AI agent can read clinical assessments, extract the LOCUS or CALOCUS domain scores and overall level, compare them against payer-specific level-of-care grids, and flag mismatches before an authorization request or a high-dollar admission goes out.
Supabill's claims-scrubbing and denials agents can hold payer rules for when LOCUS or CALOCUS is required, check that an up-to-date score exists for the billed dates and level of care, and flag claims that are headed toward CO-50 or CO-197 before submission. A benefits and auth agent can prompt staff for a new LOCUS or CALOCUS when an authorization is approaching its review date. What AI cannot own is the clinical judgment itself. Clinicians still have to perform and sign off on the scoring, and human utilization-review and appeals staff still need to argue the nuances of medical necessity with payer clinicians on peer-to-peers and appeals calls.
FAQ
Are LOCUS and CALOCUS required for every behavioral-health patient, or only certain levels of care?
LOCUS and CALOCUS are generally required where a payer's policy or contract says they are. In practice, that is most common for higher-intensity levels of care such as IOP, PHP, residential, and some intensive outpatient psychiatry. Many outpatient therapy claims are paid without LOCUS or CALOCUS. For Medicaid and Medicaid-managed-care plans, check the behavioral-health utilization-management manual. If the manual names LOCUS or CALOCUS as the standard for admission and continued stay, treat them as required for those services. Source
How do LOCUS and CALOCUS relate to ASAM Criteria for substance use treatment?
LOCUS and CALOCUS were developed for mental-health level-of-care decisions, while ASAM Criteria focuses on substance use and co-occurring disorders. Some payers and state agencies use ASAM for SUD services and LOCUS or CALOCUS for mental-health services, especially in youth. For co-occurring programs, utilization review often expects to see both frameworks used and documented in parallel. When in doubt, follow the state Medicaid or MCO policy on which framework governs which benefit. Source
Do LOCUS and CALOCUS scores need to be sent on the claim itself?
Most payers do not require the raw LOCUS or CALOCUS score on the 1500 or UB-04 claim, and there is no standard X12 segment dedicated to these scores. Instead, payers expect the scoring to appear in the clinical record and in prior authorization and concurrent-review submissions. The claim must align with the authorized level of care that was supported by the scores. If you submit a claim for residential days that go beyond the last authorized period supported by LOCUS or CALOCUS, expect CO-197 or CO-50 even if the claim passes EDI edits. Source
How often should LOCUS or CALOCUS be updated during a residential or PHP stay?
The correct interval is set by payer policy, not by a universal rule. Many Medicaid managed-care plans require updated LOCUS or CALOCUS scores at specific utilization-review checkpoints, such as day 7, day 14, or every 30 days for residential. Some PHP contracts expect weekly updates. The safest operational approach is to align your internal reassessment schedule with the tightest requirement among your top payers for each program and clearly document each score and date in the chart and in your utilization-review tracking. Source
Can LOCUS or CALOCUS alone guarantee payment for a higher level of care?
No. A score that supports a higher level of care is necessary but not sufficient. Payers still apply broader medical-necessity standards, benefit limits, and network rules. For example, a LOCUS score may support residential, but the member's plan may not cover that level of care, or may require treatment at an in-network facility. LOCUS or CALOCUS should line up with the documentation, the diagnosis, and the benefit, so that when denials occur you are arguing policy and benefit issues rather than basic clinical necessity. Source
Related terms
ASAM Criteria and Levels of Care are a nationally used clinical framework that defines severity and standardized levels of addiction treatment, from early intervention through intensive residential services. Payers and regulators rely on ASAM levels to set medical-necessity, prior-authorization, and coverage rules for substance use disorder services.
Residential Treatment (RTC) is a 24-hour behavioral-health level of care where patients live on site and receive structured clinical services but do not require acute inpatient hospital care. In revenue cycle terms, residential treatment usually bills on a per-diem basis and sits between inpatient hospitalization and partial hospitalization or intensive outpatient care.
A Medicaid Managed Care Organization (MCO) is a private or nonprofit health plan that contracts with a state Medicaid agency to deliver Medicaid-covered services to enrolled members, usually for a fixed per-member-per-month payment. In behavioral health revenue cycle, a Medicaid MCO is the billed payer and follows plan-specific coverage, authorization, and billing rules that differ from fee-for-service Medicaid.
Medical necessity is the payer standard that a service must be clinically appropriate, consistent with accepted standards of care, and not primarily for convenience in order to be covered. Medical necessity is defined in federal and state rules and in individual payer policies, and it is the core reason behind many behavioral health authorization requirements and denials.
Related denial codes
Not deemed a medical necessity
Precertification, authorization, or notification absent
Claim lacks information or has a submission error