The Definition of Medical Necessity for UR Staff

Medical necessity is the payer's test of whether a behavioral health service, at a given level of care, is required to assess, diagnose, or treat a patient's condition within generally accepted standards of care. If your documentation fails that test, the authorization or claim is denied. This article translates the major payer definitions into a concrete checklist you can apply during concurrent reviews and P2P calls.

What does medical necessity mean in plain language?

Medical necessity means the care you're providing is the right level of care, at the right intensity, for this patient, right now — and that a reasonable clinician would agree based on accepted standards. Payers formalize this. Centene, for example, defines services as medically necessary when they are consistent with generally accepted standards of medical practice, not primarily for the convenience of the patient or provider, and delivered at the least intensive level that can be delivered safely (Centene clinical policy). In a behavioral health UR context, that last clause is the one that decides your concurrent review: the payor is asking whether residential is still safer than PHP, or whether the patient could step down without risk. That question is separate from eligibility, which you confirm earlier through VOB and eligibility verification.

How do major payers define medical necessity, and where do their definitions differ?

Most payers share one skeleton: a service is medically necessary when it is clinically appropriate, consistent with accepted standards of practice, and not more intensive than the condition requires. The differences sit in the details, and those details decide whether your concurrent review documentation clears the bar.

Centene and Medicaid definitions

Centene and state Medicaid programs lean on "generally accepted standards of medical practice" and require care to be delivered at the least intensive level that is safe. For behavioral health, that language is what drives step-down decisions: a payer reading that definition wants your notes to show why residential is still needed instead of PHP or IOP, not just that the member continues to meet ASAM dimensions.

Cigna and commercial definitions

Cigna's coverage policy language emphasizes services that are "clinically appropriate in type, frequency, extent, and duration" and explicitly excludes care for custodial or convenience reasons. In practice, commercial reviewers scrutinize frequency and duration, so your service request form and concurrent notes should tie both to the ASAM 4th Edition dimensions you track in your ASAM criteria software.

NAIC and AAFP model definitions

The NAIC and AAFP publish model definitions that many payers copy, framing necessity around the treating provider's judgment plus payer review. That dual framing is why peer-to-peer calls matter: the model definition gives your clinician standing to argue the case.

How is medical necessity applied differently in behavioral health versus medical care?

In medical care, medical necessity often hinges on a procedure, an imaging study, or a lab result tied to a diagnosis. Cigna's provider guidance frames it as services that are clinically appropriate in type, frequency, and duration for the condition being treated (Cigna coverage policies). In behavioral health, the question is different: not "is this procedure indicated?" but "what level of care does this person need right now, and are they improving fast enough to justify continued days?"

Level-of-care criteria: ASAM and LOCUS

Payors borrow standardized frameworks rather than procedure lists. For SUD treatment, ASAM's criteria place the patient along a continuum from outpatient to medically managed intensive inpatient. For mental health, many payors apply LOCUS, which scores risk, function, and comorbidity to justify residential, PHP, or IOP placement. Your documentation should map directly to those dimensions; a LOCUS refresher is at CriteriaIQ's LOCUS assessment tool.

Concurrent review and length of stay

Concurrent review then asks whether continued stay still meets criteria. A payer will not authorize a length of stay up front; they authorize days at a time, and each extension demands documented progress, not just continued symptoms.

What documentation proves medical necessity in a utilization review?

A concurrent review is won or lost on the chart, not the phone call. The reviewer reading your submission needs to see the level of care, the clinical reasoning behind it, and the risk of stepping down, all evidenced in dated notes. If a payor's reviewer has to infer any of that, you are one missing assessment away from a denial.

Dimension-by-dimension documentation checklist

For each concurrent review, confirm the chart contains:

• Level of care justification mapped to ASAM 4th Edition dimensions, stating explicitly why residential, PHP, or IOP is the appropriate setting.
• A current treatment plan with measurable goals tied to the diagnosis, updated within the payor's required interval.
• Progress notes from the authorization window showing active participation, not just attendance.
• Risk documentation: recent use, overdose history, withdrawal risk, or psychiatric symptoms that make a lower level of care unsafe.
• Step-down planning: what has been tried, what progress justifies a transition, and the target date. Reviewers ask for this on every call.
• Service request forms and clinical attachments matched to the payor's own template, submitted inside the authorization window.

Common documentation gaps that trigger denials

The gaps repeat across facilities. A nursing note that says "patient doing well" supports step-down, not continued stay. A treatment plan last updated 40 days ago reads as stalled care. A peer-to-peer call where the clinician cannot cite the specific ASAM dimension on the spot tends to end in an adverse determination, because the payor's reviewer is scoring the conversation the same way they score the chart.

The fix is not more documentation, it is documentation aimed at the criteria. Every note written during an authorized stay is either building your case for continued stay or quietly building the payor's case to deny it. Before submitting a concurrent review, read the chart as the payor reviewer would: can you point to the dimension, the date, and the risk in under a minute? If not, close that gap before the reviewer finds it. The same discipline applies upstream, at initial authorization, where most denials are actually seeded; our guide to prior authorization in behavioral health billing covers how to structure that first submission so concurrent reviews start from a defensible base.

What happens when a service is denied as not medically necessary?

A medical necessity denial arrives with a CARC code (often 50, "non-covered services because not deemed a medical necessity") and sometimes a RARC code pointing to the specific reason. Under the NAIC Utilization Review Model Act, payers must give written notice with the specific reason and the clinical rationale, plus instructions for appealing. The model act text spells out those notice and appeal obligations.

Appeal timelines are short. Internal appeals often run 180 days from the denial, but the practical deadline is the peer-to-peer window: many payers offer a phone review between the treating clinician and the plan's medical director within days of the initial denial, and skipping it means appealing blind.

Track both dates on the same board as your authorization windows. If the denial cites a missing note or an unstated ASAM dimension, CriteriaIQ's documentation checklist shows what to pull before the call.

When should a provider write a letter of medical necessity, and what must it include?

Write one when a payer asks for more information before approving a level of care, when a concurrent review is denied or pended, when you are requesting continued stay beyond an authorized length of stay, or when you are appealing a medical necessity denial. A peer-to-peer call that ends without resolution should be followed by a letter that puts your clinical argument on the record.

The AAFP describes medical necessity as health care services consistent with the diagnosis, appropriate for the patient's condition, and not solely for the convenience of the provider. Mirror that structure in the letter.

Include five things: the specific ASAM 4th Edition or payer criteria you are applying; the assessment findings that meet each criterion; the risk of stepping down or discharging now; the treatment plan with start dates and frequency; and the clinician's name, license, and direct contact for the peer-to-peer. Keep it to one or two pages. Payers' reviewers skim, and a letter that buries the criteria match behind narrative loses.

How can providers avoid medical necessity denials before they happen?

Most medical necessity denials trace back to two failures: a missed authorization window and a note that never made it into the chart before the concurrent review. Both are tracking problems, not clinical ones.

Where manual tracking breaks down

When UR staff juggle dozens of cases across payors with different criteria, spreadsheets and shared inboxes break in predictable ways. A review date lives in one person's head. A service request form sits in an inbox nobody checked. A step-down recommendation from the treatment team never reaches the UR nurse until after the payor has already denied for continued stay. The fix is procedural: one calendar per payor with review dates and deadlines, a daily huddle between UR and clinical staff on upcoming reviews, and a standing rule that every medical necessity element (ASAM dimensions, level of care, measurable goals) is documented before the review date, not after.

What criteria-mapping software does and does not fix

Software like CriteriaIQ RCM, built for Kipu and BestNotes, automates the tracking layer: payor-specific criteria, authorization windows, and review timelines surfaced per case, so a missing note gets flagged before it becomes a denial. What it does not fix is the note itself. If the clinician documents "doing well" instead of continued symptoms, ASAM dimension risk, and why step-down is premature, no tool can supply that content. Software removes the deadline failures; the documentation still depends on your clinical team writing to the payor's criteria.

FAQ

What is the definition of medical necessity in simple terms?

Medical necessity means the care is the right level and intensity for this patient right now, and a reasonable clinician would agree based on accepted standards. For behavioral health UR, the practical question is whether a lower level of care, like PHP or IOP, could be delivered safely instead of the current setting.

Is medical necessity defined the same way by all insurance companies?

No. Most payers share a skeleton of clinical appropriateness, accepted standards, and the least intensive safe level, but the details differ. Centene and Medicaid emphasize the least intensive safe level, Cigna stresses type, frequency, and duration, and NAIC and AAFP model definitions frame it around provider judgment plus payer review. Those details decide whether documentation clears the bar.

What is an example of medical necessity in behavioral health?

A patient in residential treatment with recent overdose history, high withdrawal risk, and unstable psychiatric symptoms meets continued-stay criteria because residential remains the least intensive setting where those risks can be managed safely. If the chart instead showed stable attendance and no risk factors, the same stay would support step-down to a lower level of care.

Who decides whether a service is medically necessary?

The payer decides, but the treating provider's clinical judgment carries weight. A utilization reviewer scores the chart against criteria like ASAM 4th Edition or LOCUS, and on a peer-to-peer call the plan's medical director weighs the treating clinician's rationale. NAIC and AAFP model definitions formalize that dual structure of provider judgment plus payer review.