IOP & PHP Billing: Level of Care Justification That Pays

Across the roughly 50 behavioral health practices we work with at Revenant Care Group, the single most expensive billing failure we see is not upcoding, not missing modifiers, and not credentialing gaps. It is the inability to defend level of care at the point of claim submission. PHP and IOP programs are generating tens of thousands of dollars in avoidable denials every month because the clinical documentation is not written to survive payer scrutiny, even when the care itself is entirely appropriate.

This post breaks down exactly what payers are looking for when they adjudicate H0035, H0015, S9480, and the related CPT structures for partial hospitalization and intensive outpatient services, what documentation language triggers automatic downcoding to standard outpatient, and what we do operationally to keep authorization and payment aligned from day one of a patient’s episode.

Understanding the Code Set: PHP vs. IOP in 2026

The billing landscape for these two levels of care is more nuanced than most practice administrators realize. For mental health PHP, the dominant code remains H0035 (partial hospitalization, less than 24 hours) billed per diem, while many commercial payers have migrated to accepting S9480 for intensive outpatient. For substance use disorder programs, H0015 remains the standard IOP code, billed in 15-minute increments or per diem depending on the payer contract.

Place of service matters significantly here. PHP services rendered in a hospital outpatient department use POS 52. Community-based PHP and IOP programs bill under POS 57 (non-residential opioid treatment) for SUD or POS 72 (rural health clinic, where applicable), and freestanding behavioral health programs most commonly use POS 49 or POS 53 depending on the payer’s expectations. Getting the POS wrong on an H0035 claim at a commercial payer can trigger automatic denial or a recoupment demand months after initial payment. We see this pattern regularly.

What “Level of Care Justification” Actually Means to a Payer

Payers reviewing PHP and IOP claims are not simply verifying that the patient attended the required number of hours. They are evaluating whether the submitted documentation demonstrates that the patient could not have been safely treated at a lower level of care. That is a clinical standard that has to be built into the notes from day one, not reconstructed at appeal.

Specifically, commercial payers and managed behavioral health organizations (MBHOs) using InterQual or Milliman criteria are looking for:

• Active symptom severity scores: PHQ-9, GAD-7, ASAM criteria scoring, CIWA-Ar for withdrawal, or COWS, documented at admission and updated at each concurrent review point.
• Functional impairment language: Notes must state explicitly that the patient cannot maintain safety or functional stability without structured daily programming. Vague language like “patient continues to benefit from IOP” will not survive a concurrent review.
• Step-down criteria not yet met: Clinicians must document what specific clinical thresholds the patient has not yet reached that would justify transition to standard outpatient (OP), typically coded under 90837 or 90834.
• Collateral and social factors: Housing instability, absence of sober support, ongoing occupational or family dysfunction directly supporting the need for structured care.

When these elements are absent or generic, payers downcode to 90837 at an average reimbursement of $150 to $190 per session. A single patient episode of PHP averaging $800 to $1,200 per diem represents a $600 to $1,000 per-day revenue gap when that downcode occurs. Over a 90-bed PHP program running at 70 percent census, that math gets serious very quickly.

The Authorization Gap That Bleeds Revenue Over Time

One of the patterns we see most consistently is what we internally call the “authorization cliff.” A practice obtains initial authorization for PHP, the patient continues in treatment, and the concurrent review documentation submitted to the payer repeats the admission rationale verbatim instead of reflecting the patient’s current clinical status. Payers catch this. They use it as justification to retroactively deny days two through fourteen of a twelve-day episode.

The fix is not complicated, but it requires discipline. Concurrent review packets need to show clinical movement, meaning the patient’s scores and presentation three days in should look different from admission, not because they are better but because the documentation is granular enough to show what is changing, what is not, and why continued structured care is the medically necessary response to that specific trajectory. Static notes equal denied days. We have seen practices recover 18 to 22 percent of their previously written-off PHP revenue within 90 days simply by retooling concurrent review documentation templates.

MHPAEA Parity as a Recovery Tool for Downcode Denials

When a payer systematically downcodes PHP to outpatient or applies more aggressive medical necessity criteria to behavioral health LOC than they apply to analogous medical or surgical levels of care, that is a potential parity violation. This is not a theoretical argument. It is a recoverable claim position when documented correctly.

We have covered the mechanics of parity-based appeals in depth, and if your practice is seeing consistent LOC denials from a specific MBHO, that resource is worth reviewing before your next appeal cycle: Mental Health Parity Act Appeals: How Behavioral Health Practices Are Leaving Money on the Table. The key point for PHP and IOP billing specifically is that payers must apply the same non-quantitative treatment limitations to behavioral health that they apply to medical benefits. Documenting the disparity in your appeal is what converts a soft denial into a paid claim.

SUD-Specific IOP Billing: Where the Complexity Compounds

For SUD programs billing H0015, the level of care justification challenge is compounded by the need to integrate drug testing documentation into the clinical record in a way that directly supports continued treatment authorization. Payers reviewing IOP authorization for SUD will evaluate whether drug screen results are being used to adjust treatment planning, not simply recorded. A positive UDS for alcohol metabolites on day six of IOP that does not generate a documented clinical response is both a treatment documentation failure and a billing vulnerability.

This connects directly to how you are coding your drug screening services. Many SUD programs we work with are significantly undercoding their lab and presumptive screening panels, and the revenue loss compounds across both the testing revenue itself and the treatment authorization support those results should be providing. Our breakdown of G0480 through G0483 drug screen coding for SUD practices addresses exactly how to close that gap on the lab side while also generating the clinical documentation that supports your IOP authorization narrative.

Operational Changes That Produce Measurable Recovery

Based on what we track across our client practices, the documentation and billing changes that produce the highest recovery on PHP and IOP denials are:

• Building LOC justification language directly into EHR templates at the group note level, so clinicians are documenting functional impairment and step-down criteria as part of their standard workflow rather than as an afterthought.
• Separating authorization management from claims submission as distinct roles. The person submitting concurrent review to Optum or Carelon should not also be the person submitting the claim. Oversight catches gaps.
• Running a monthly denial categorization report that isolates LOC-based denials from coding errors, credentialing issues, and timely filing. Practices that do not separate these categories cannot identify the actual scale of their LOC exposure.
• Establishing a 48-hour appeal submission standard for LOC denials, with a pre-written appeal template that incorporates ASAM criteria language and the relevant parity statute citations for your state.

A mid-size PHP program billing approximately $2.5 million annually can reasonably expect LOC-related denials to represent 12 to 17 percent of gross charges before these controls are in place. After implementation, the practices we work with typically stabilize that figure below 5 percent within two billing cycles.

Take the Next Step: A Free 30-Day Denial Audit

If your PHP or IOP program is carrying a denial rate above 8 percent on LOC-based claims, or if you have open appeals sitting beyond 60 days without a resolution strategy, the most valuable thing you can do right now is get a structured look at where the money is going. Revenant Care Group offers a free 30-day denial audit specifically designed for behavioral health, ABA, and SUD programs. We pull your denial data, categorize it by root cause, and give you a prioritized recovery plan with no obligation. Schedule your free audit here and let us show you what your current LOC documentation is actually costing you.