Billing intensive outpatient and PHP
Intensive outpatient programs (IOP) and partial hospitalization programs (PHP) sit between routine outpatient therapy and inpatient care, and they are billed differently from a single office session because they represent structured, multi-hour, multi-service programs delivered across a day. A partial hospitalization program (PHP) is generally the more intensive of the two, while IOP delivers fewer program hours per week. How each is billed—whether as a bundled per-diem, as individual service lines, on a professional or an institutional claim form—depends on the payer, the plan, the site of care, the state program, and the rules in effect on the date of service. Because these structures vary, program billing hinges on confirming eligibility verification, securing prior authorization where required, and documenting medical necessity at the level of intensity billed. Coverage and payment frameworks for these programs are set by CMS for Medicare, by state Medicaid programs, and by individual commercial payers, while clinical and program guidance is published by SAMHSA; payer-specific and state-specific terms should always be verified against the current source.
Updated 8 min read
On this page
Key takeaways
- IOP and PHP are structured, multi-service levels of care billed differently from a single outpatient session; PHP is generally more intensive than IOP.
- Program services may be billed as a bundled per-diem or as separate service lines, and may route on an institutional or professional claim form depending on the setting and payer.
- Prior authorization, concurrent review, and medical-necessity documentation tied to the billed level of intensity are common expectations, but specific criteria vary by payer, plan, and state.
- Program-hour thresholds, covered components, and reimbursement structures differ by payer, Medicare, Medicaid, and date, and must be confirmed against current authoritative sources rather than assumed.
- Accurate eligibility, benefit, and authorization checks before admission reduce denials specific to level-of-care and unit-based billing.
What IOP and PHP are as billable levels of care
IOP and PHP are defined as distinct levels of care within the behavioral health continuum rather than as individual procedures. Both deliver a coordinated bundle of services—which may include group therapy, individual therapy, family involvement, skills training, and medication management—organized into structured program days. The distinction that matters for billing is intensity: PHP typically involves more program hours per day and week than IOP, and the two are generally not billed for the same day for the same patient.
Because these are program-level services, the billing question is not only which service was rendered but at what level of intensity, for how many hours, and under what authorization. Program definitions, minimum hour expectations, and covered components are established by payers and public programs; the specifics differ across Medicare, Medicaid, and commercial plans and change over time, so they should be confirmed against current CMS and payer policy.
Level of care drives the claim
Per-diem versus per-service and claim form routing
Program services can be billed in more than one structure. Some payers expect a bundled per-diem that covers all program services delivered on a given day; others expect individual service lines; and some blend the two. The claim may route on an institutional claim form such as the UB-04 for facility-based programs, or on a professional CMS-1500 for practitioner services, depending on the site of care and the payer's rules.
| Dimension | Per-diem (bundled) | Per-service (itemized) |
|---|---|---|
| Unit billed | One program day covering all included services | Each service or component billed separately |
| Typical form context | Often institutional, facility-based programs | Often professional or component-level lines |
| Authorization matching | Authorized program days matched to billed days | Authorized units matched to each billed service |
| Where rules live | Payer, plan, and program policy on the date of service | Payer, plan, and program policy on the date of service |
This compares billing concepts generally. Which structure applies, and the covered components within it, is set by the individual payer, plan, and state program and should be verified against the current policy.
Code sets used to describe program services and revenue categories are maintained by their respective standards bodies, and payers specify which sets and formats they accept. Rather than assuming a structure, the program's expected format, accepted code families, and any bundling rules should be confirmed with each payer before claims are built. Related mechanics are covered in the claims section and the broader behavioral health code families article.
Eligibility, authorization, and concurrent review
IOP and PHP are commonly subject to utilization management. Many payers require prior authorization before admission and ongoing concurrent (continued-stay) review to keep the program authorized, though whether review is required, how often, and against what criteria varies by payer, plan, and state program.
Verify eligibility and behavioral health benefits
Confirm active coverage and the specific behavioral health benefit before admission, noting any behavioral health carve-out that routes program benefits to a separate managed entity. See behavioral health eligibility and carve-outs for detail.Obtain prior authorization for the level of care
Where required, secure authorization for the specific program level and expected number of days or units. Program-level authorization patterns are discussed in behavioral health prior authorization.Maintain concurrent review
Submit continued-stay documentation on the payer's schedule to keep authorization current as the program continues, so authorized days do not lapse mid-program.Match authorized units to billed services
Reconcile authorized program days or units against what is billed so that claims do not exceed the authorization on file, a common cause of program denials.
Coordination of benefits matters for program billing
Documentation and medical necessity at the billed intensity
Because IOP and PHP are higher-intensity levels of care, payers generally expect documentation that supports both the need for that intensity and the delivery of the program as billed. That typically includes an assessment establishing why a less intensive setting is insufficient, an individualized treatment plan, records of the services delivered each program day, and progress notes tied to measurable goals. The exact elements and how they map to the billed level are defined by each payer and program.
- Assessment and level-of-care rationale supporting the program's intensity
- An individualized, updated treatment plan with measurable goals
- Documentation of each program day's services and the time or components delivered
- Progress notes demonstrating continued need for the billed level of care
- Physician or qualified-clinician involvement as required by the payer and program
Substance use disorder programs may also carry confidentiality obligations under 42 CFR Part 2, which affects how program records are handled and disclosed. General documentation expectations are expanded in behavioral health documentation requirements, and substance-focused programs are covered in substance use disorder billing.
Medicare, Medicaid, parity, and program variation
Program benefits, definitions, and reimbursement differ substantially across public and commercial payers. Medicare defines and pays for these programs under its own coverage and payment frameworks, described in behavioral health under Medicare. State Medicaid programs may cover, define, and structure IOP and PHP differently from one another and from Medicare, as discussed in behavioral health under Medicaid. Because Medicaid is jointly funded by the federal and state governments and administered by states within federal rules, program coverage and billing rules are state-specific.
Federal mental health parity requirements can affect how program benefits and utilization management are applied relative to medical or surgical benefits; the broader framework is covered in behavioral health parity. None of these frameworks fixes a single universal program-hour threshold, per-diem amount, or authorization rule that applies everywhere—each is set by the payer, plan, program, and jurisdiction and changes over time.
Verify current, source-specific rules
Frequently asked questions
What is the difference between IOP and PHP for billing purposes?
Both are structured, multi-service behavioral health levels of care, but PHP is generally more intensive—more program hours per day and week—than IOP. For billing, the level of care drives which authorization, which claim structure, and which documentation intensity apply, and the two are generally not billed for the same day for the same patient. Exact hour thresholds and covered components are defined by each payer, plan, and state program and change over time.
Are IOP and PHP billed as a bundled per-diem or as separate services?
It depends on the payer. Some expect a bundled per-diem covering all program services on a given day, others expect individual service lines, and some blend the two. The claim may route on an institutional or a professional claim form depending on the site of care. The correct structure, accepted code families, and bundling rules should be confirmed with each payer before claims are built.
Do these programs require prior authorization?
Many payers require prior authorization before admission and ongoing concurrent review to keep the program authorized, but whether review is required, how often, and against what criteria varies by payer, plan, and state program. Verifying eligibility and authorization requirements before admission, and matching authorized days or units to what is billed, reduces level-of-care denials.
How is medical necessity documented for IOP and PHP?
Payers generally expect documentation supporting both the need for the higher intensity and delivery of the program as billed—typically an assessment with a level-of-care rationale, an individualized treatment plan with measurable goals, records of each program day's services, and progress notes showing continued need. The exact required elements are defined by each payer and program.
Do Medicare and Medicaid bill these programs the same way?
No. Medicare defines and pays for these programs under its own coverage and payment frameworks, while state Medicaid programs may cover, define, and structure them differently from Medicare and from one another. Because Medicaid is administered by states within federal rules, program coverage and billing are state-specific and should be verified against current program policy.
Related glossary terms
Definitions that recur in intensive outpatient and partial hospitalization billing. Terms and their application vary by payer, plan, and jurisdiction.
Related reading
Continue with related behavioral health billing topics that inform how IOP and PHP programs are authorized, documented, and claimed.
Behavioral health prior authorization
How authorization and concurrent review apply to behavioral health levels of care.
Behavioral health documentation requirements
Documentation elements that support medical necessity and the billed level of care.
Behavioral health eligibility and carve-outs
Confirming benefits and identifying carved-out program administrators before admission.
Substance use disorder billing
Program billing considerations specific to substance use treatment settings.
Common behavioral health denials
Frequent denial causes in behavioral health, including level-of-care and unit mismatches.
