Revenue Cycle Management for IOP and PHP Programs (2026)

Intensive Outpatient Programs (IOP) and Partial Hospitalization Programs (PHP) occupy the critical middle of the behavioral health continuum of care, sitting between residential treatment and standard outpatient therapy. Their billing complexity reflects this position: institutional claim formats on UB-04, per-diem bundling of multiple daily services, payer-specific code requirements, weekly minimum hour thresholds that determine billing eligibility, Medicare provider-type restrictions for PHP, and authorization workflows that demand concurrent reviews as often as every 5 to 7 days. This guide covers the specific billing codes, payer rules, documentation requirements, and denial prevention strategies that define IOP and PHP revenue cycle operations in 2026.

IOP vs. PHP: Structure, Hours, and Billing Distinctions

IOP and PHP share structural similarities as multi-day, multi-service outpatient programs, but they differ in intensity, billing methodology, payer rules, and reimbursement rates. Understanding these distinctions is essential because billing errors related to IOP/PHP confusion are a top denial category. For a broader view of how IOP and PHP fit within the behavioral health revenue cycle, see our behavioral health revenue cycle guide.

Parameter IOP (Intensive Outpatient) PHP (Partial Hospitalization)
ASAM Level (SUD) 2.1 2.5
Minimum weekly hours 9 hours/week (typically 3 hrs/day, 3 days/week) 20 hours/week (typically 5-6 hrs/day, 4-5 days/week)
Primary billing codes S9480 (MH), H0015 (SUD) Revenue codes 0912/0913 with HCPCS
Claim type UB-04 (institutional) for most payers UB-04 (institutional) required
Billing model Per-diem (most payers); per-service (some commercial) Per-diem (most payers); per-service under OPPS (Medicare)
Typical program duration 6-16 weeks 2-4 weeks
Typical per-diem range $250-$650/day $450-$1,200/day
Medicare eligibility Covered since January 2024 (new benefit) Hospital-based or CMHC only
Auth frequency 7-14 day initial; concurrent every 7-14 days 5-7 day initial; concurrent every 5-7 days

Behavioral Health Billing and Coding 101: How to Get Paid — AMA

IOP Billing Codes and Revenue Codes

IOP billing uses a small number of codes, but the correct application of those codes varies significantly by payer, diagnosis type, and state. Miscoding is among the most common reasons for IOP claim denials.

S9480: Mental Health IOP Per Diem

HCPCS code S9480 (Intensive outpatient psychiatric services, per diem) is the primary billing code for mental health IOP programs. One unit of S9480 represents one full day of IOP programming. All services delivered during the IOP day, including individual therapy, group therapy, psychoeducation, family therapy, and case management, are bundled into the S9480 per-diem charge. S9480 is typically paired with revenue code 0905 (Intensive outpatient services, psychiatric) on the UB-04 institutional claim.

  • Unit definition: One unit = one day of IOP services meeting minimum hour requirements (typically 3 hours).
  • Payer acceptance: Most commercial payers and managed Medicaid plans recognize S9480. However, S-codes are not recognized by Medicare. For Medicare IOP billing, use the specific HCPCS codes for each service provided under the new Medicare IOP benefit.
  • Modifier usage: Some payers require modifiers with S9480, such as HF (substance abuse program) if the IOP serves SUD patients under a mental health code, or GT/95 for telehealth IOP sessions. Verify modifier requirements per payer.

H0015: Substance Use Disorder IOP Per Diem

HCPCS code H0015 (Alcohol and/or drug services, intensive outpatient) is used for SUD-focused IOP programs. Like S9480, it is a per-diem code that bundles all services into a single daily charge. H0015 is paired with revenue code 0906 (Intensive outpatient services, chemical dependency) on the UB-04.

  • Diagnosis alignment: H0015 should be used when the primary treatment focus is substance use disorder (ICD-10 codes F10-F19). Using H0015 for a primarily mental health IOP program is a coding error that may trigger denials or audit inquiries.
  • Co-occurring diagnoses: For patients with co-occurring MH and SUD diagnoses, the code selection should align with the primary treatment focus. If the IOP program is primarily addressing SUD with co-occurring depression treatment, H0015 is appropriate. If the program is primarily addressing depression with co-occurring SUD, S9480 may be more appropriate. Document the primary treatment focus clearly.
  • State-specific codes: Some states use alternative codes for SUD IOP. Arizona, for example, has issued coding clarifications specifying when H0015 vs. S9480 should be used. Verify state-specific requirements for Medicaid programs.

Revenue Code Pairing

Program Type Revenue Code HCPCS Code Claim Type
IOP - Mental Health 0905 S9480 UB-04 (837I)
IOP - SUD 0906 H0015 UB-04 (837I)
PHP - Mental Health 0912 Per-service HCPCS (CMS) or per-diem code (commercial) UB-04 (837I)
PHP - SUD 0913 Per-service HCPCS (CMS) or per-diem code (commercial) UB-04 (837I)

Code Selection Warning

Billing both S9480 and H0015 for the same patient on the same day is not permitted. Similarly, IOP and PHP per-diem codes cannot be billed on the same day for the same patient. CMS specifically rejects overlapping IOP (condition code 92) and PHP claims within a 7-day window. Verify that the billing system enforces these mutual exclusivity rules to prevent duplicate billing rejections. For a comprehensive reference of all behavioral health billing codes, see our mental health billing codes guide.

PHP Billing Codes and Medicare Requirements

Partial Hospitalization Programs represent the highest-intensity outpatient level of care. PHP billing carries more restrictions and complexity than IOP billing, particularly for Medicare, where provider-type eligibility limits which organizations can bill for PHP services at all.

Revenue Codes 0912 and 0913

PHP is billed on the UB-04 institutional claim using revenue code 0912 (Partial hospitalization, less intensive) or 0913 (Partial hospitalization, intensive). The distinction between 0912 and 0913 is defined by the number of services provided per day:

  • 0913 (Intensive): Used when four or more distinct services are provided during the PHP day. This is the standard revenue code for a full PHP day.
  • 0912 (Less intensive): Used when three or fewer services are provided during the PHP day. CMS pays a reduced rate for three-service days. Days with fewer than three services should be infrequent; a pattern of three-service days raises medical necessity questions.
  • Service definition for counting: Each distinct service (individual therapy, group therapy, medication management, family therapy, psychoeducation) counts as one service. Multiple group therapy sessions count as separate services only if they address different treatment modalities.

Medicare PHP Provider Eligibility

Medicare imposes a critical restriction on which provider types can bill for PHP: only hospital outpatient departments (including psychiatric hospitals and critical access hospitals) and Community Mental Health Centers (CMHCs) are eligible to bill Medicare for PHP services. Freestanding behavioral health practices that are not hospital-affiliated cannot bill Medicare for PHP regardless of clinical programming quality.

  • Hospital outpatient departments: General hospitals, psychiatric hospitals, and critical access hospitals can bill PHP under their hospital outpatient prospective payment system (OPPS). The PHP program must operate as part of the hospital's outpatient department.
  • Community Mental Health Centers (CMHCs): CMHCs that meet CMS certification requirements can bill PHP. CMHC PHP billing follows the same OPPS framework but with CMHC-specific payment rates and conditions.
  • Medicare PHP claim requirements: Each PHP day must include a mental health diagnosis and at least three distinct partial hospitalization HCPCS codes, one of which must be a psychotherapy code (other than brief psychotherapy). Claims that do not meet this three-service minimum per day will be denied.
  • Physician certification: Medicare requires physician certification that the patient would require inpatient psychiatric hospitalization if PHP were not available. This certification must be completed at admission and recertified at regular intervals. Without physician certification on file, the claim cannot be processed.

Medicare IOP Benefit (New for 2024)

Effective January 1, 2024, Medicare established a new IOP benefit category under the Consolidated Appropriations Act of 2023. This closed a longstanding coverage gap where Medicare beneficiaries who needed more than standard outpatient therapy but less than PHP had no covered middle option. The Medicare IOP benefit is available through hospital outpatient departments, CMHCs, Federally Qualified Health Centers (FQHCs), Rural Health Clinics (RHCs), and Opioid Treatment Programs (OTPs).

  • Condition code 92: Medicare IOP claims must include condition code 92 to identify the claim as IOP services. Claims without condition code 92 will not be processed under the IOP benefit.
  • Per-diem payment structure: CMS pays IOP on a per-diem basis with two rate tiers: one for days with three services, and a higher rate for days with four or more services. The per-diem rates are calculated through the OPPS methodology.
  • Minimum 9 hours per week: The CMS certification requirement specifies that the individual must receive a minimum of 9 hours of IOP services per week. Recertification must occur at intervals aligned with concurrent review requirements.

Medicare IOP Expansion Impact

The new Medicare IOP benefit represents a significant revenue opportunity for qualifying providers. Prior to 2024, Medicare beneficiaries in need of IOP-level care either paid out of pocket or went without the service. Organizations that can bill Medicare for IOP now have access to a previously unreachable patient population. For hospital-based programs, FQHCs, and CMHCs, this benefit category should be integrated into payer enrollment and billing workflows immediately if not already operational.

Per-Diem vs. Per-Service Billing for IOP and PHP

The choice between per-diem and per-service billing for IOP and PHP is determined by the payer contract, not by the provider. Applying the wrong billing model is a top-5 denial cause for these programs.

Per-Diem Model

Under per-diem billing, the facility submits one daily charge that bundles all IOP or PHP services for that day. This is the dominant model for managed Medicaid plans and many commercial payers. The per-diem rate covers individual therapy, group therapy, psychoeducation, family therapy, medication management (when delivered by program staff), case management, and crisis intervention delivered during the program day.

  • Revenue per patient per day: IOP per-diem rates typically range from $250 to $650 per day. PHP per-diem rates range from $450 to $1,200 per day. Rates vary significantly by geography, payer, and network status.
  • Revenue per patient per week: An IOP patient attending 3 days per week at $400/day generates $1,200 per week. A PHP patient attending 5 days per week at $700/day generates $3,500 per week. These per-patient-per-week benchmarks are the primary financial planning metric for IOP/PHP programs.
  • Advantages: Simpler billing with fewer claim lines. Lower denial rates because bundled per-diem claims have fewer individual service lines to adjudicate. Predictable revenue per patient-day.
  • Disadvantages: Revenue is capped regardless of service volume. High-acuity patients receiving intensive services generate the same revenue as lower-acuity patients receiving minimum services.

Per-Service Model

Some commercial payers require or allow per-service billing for IOP and PHP, where each individual service delivered during the program day is billed separately using CPT codes. Under this model, a single IOP day might generate claims for 90853 (group therapy), 90834 or 90837 (individual therapy), 90847 (family therapy), and 99213-99215 (medication management E/M).

  • Higher revenue potential: Per-service billing may yield 15% to 30% more revenue per patient-day than per-diem billing for programs that deliver a high volume of services. A PHP day with individual therapy, two group sessions, family therapy, and a medication management visit can generate $800 to $1,500 in per-service charges compared to a $700 per-diem rate.
  • Documentation burden: Every service requires individual documentation with time-based codes requiring start/stop times. Group therapy requires per-participant individualized notes. The administrative overhead is substantially higher than per-diem billing.
  • Denial risk: Each individual service line is subject to separate review and potential denial. A single per-diem claim can be either paid or denied; a per-service claim with five service lines has five opportunities for denial. Net reimbursement may not exceed per-diem reimbursement after accounting for denials and administrative costs.

Mixed-Model Billing

Some payer contracts use a hybrid approach where the IOP or PHP program per-diem is billed on the institutional claim (UB-04) and certain services that are excluded from the per-diem are billed separately on professional claims (CMS-1500). Common exclusions from the per-diem that can be billed separately include:

  • Psychiatric evaluation (90791, 90792) when performed outside the scheduled program
  • Medication management by a psychiatrist or psychiatric NP not employed by the program
  • Psychological testing (96130-96139)
  • Medical E/M services for conditions unrelated to the behavioral health treatment

Authorization Workflows for IOP and PHP

IOP and PHP authorization follows the same general pattern as other behavioral health levels of care but with level-specific timing and documentation requirements. The authorization intensity for PHP approaches that of residential treatment, with concurrent reviews as frequent as every 5 to 7 days. IOP authorization is somewhat less intensive but still requires regular concurrent reviews that outpatient therapy does not.

Initial Authorization

Initial authorization for IOP requires documentation of a DSM-5 or ICD-10 diagnosis of sufficient severity to warrant structured outpatient treatment, functional impairment that prevents the patient from maintaining stability with standard outpatient therapy alone, and a treatment plan with measurable goals. For SUD IOP, ASAM criteria dimensional assessment documenting that the patient meets ASAM Level 2.1 is typically required.

Initial authorization for PHP requires all of the above plus documentation that the patient would require inpatient hospitalization if PHP were not available. This is a higher bar than IOP and requires specific clinical indicators: active suicidal ideation without imminent plan, acute psychiatric destabilization requiring daily monitoring, recent psychiatric hospitalization with insufficient stability for IOP, or medical management needs (e.g., medication titration) that require a structured daily environment.

Concurrent Review Timing

Program Typical Initial Auth Concurrent Review Frequency Revenue at Risk per Gap Day
PHP 5-7 days Every 5-7 days $450-$1,200
IOP (commercial) 7-14 days Every 7-14 days $250-$650
IOP (managed Medicaid) 7-10 days Every 7-10 days $150-$350

Concurrent Review Documentation

Each concurrent review submission must include: updated symptom severity and functional status, documented progress toward measurable treatment plan goals, justification for continued care at the current level of intensity (why stepping down is not yet clinically appropriate), current medications and any changes, attendance record showing consistent program participation, and projected discharge date or step-down timeline. For PHP specifically, the documentation must reaffirm why the patient would require inpatient hospitalization without the PHP level of structure and monitoring.

Authorization Gap Prevention

The financial impact of authorization gaps in IOP and PHP is calculated per program day, not per calendar day. A 3-day gap in PHP with 5-day-per-week programming costs 3 program days of revenue, not 3 calendar days. For a PHP patient at $700/day, a 3-program-day gap is $2,100 in unrecoverable revenue. Prevention requires the same centralized authorization tracking and automated reminders described in residential treatment but with the IOP/PHP-specific timing parameters. For facilities that also operate residential programs, see our residential treatment center RCM guide for how to coordinate authorization tracking across levels of care.

Attendance Tracking and Billing Eligibility

In IOP and PHP, attendance is not just an operational metric; it is a billing prerequisite. A patient who does not attend programming on a given day cannot be billed for that day. A patient who attends but does not meet minimum hour requirements may not qualify for per-diem billing at the full rate. Attendance tracking must be integrated with billing to prevent claims for non-qualifying days.

Minimum Hour Requirements for Billing

  • IOP minimum per day: Most payers require a minimum of 3 hours of structured clinical programming per day for an IOP day to be billable. Some payers define the minimum as 2.5 hours. If a patient attends for only 2 hours, the day typically cannot be billed as an IOP day.
  • PHP minimum per day: PHP requires a minimum of 4 to 6 hours of structured clinical programming per day depending on the payer. CMS does not specify a minimum hourly requirement per day but requires at least three distinct services per day for the standard PHP per-diem rate.
  • Weekly hour minimums: Beyond daily minimums, the program must deliver at least 9 hours per week for IOP and 20 hours per week for PHP across all program days. A patient who attends only 2 of 3 scheduled IOP days may still meet the 9-hour weekly minimum if each attended day included extended programming. But if attendance drops below the weekly threshold, the entire week's billing may be at risk.

Partial Attendance Rules

When a patient arrives late, leaves early, or misses part of the scheduled program, the billing treatment depends on whether the remaining attended hours meet the daily minimum:

  • Meets minimum: If the patient attended for at least the required minimum hours (e.g., 3 hours for IOP), the day is billable at the full per-diem rate.
  • Below minimum: If attendance falls below the minimum, some payers deny the entire day. Others pay a reduced partial-day rate. CMS pays a reduced three-service rate for PHP/IOP days with fewer services. Verify partial-day billing rules per payer.
  • Documentation: Attendance records must show actual arrival and departure times, not just check-in/check-out. Auditors compare attendance records against billing to identify discrepancies.

No-Show and Cancellation Impact

No-shows directly reduce program revenue because unattended days are not billable. For an IOP program averaging 20 patients per day at $400/day, a 10% no-show rate represents $800 per program day or approximately $208,000 per year in lost revenue. PHP programs with higher per-diem rates face even greater no-show exposure. Strategies to minimize no-shows include: appointment reminder systems (text, phone, email), transportation assistance, childcare considerations in scheduling, and clinical engagement protocols that identify patients at risk of disengagement.

Attendance-to-Billing Reconciliation

Perform a daily reconciliation between program attendance records and generated billing charges. Every patient on the attendance roster should have a corresponding per-diem charge. No charge should exist for patients not on the attendance roster. Attendance hours should be verified against the minimum threshold before the charge is released. This reconciliation should be automated in the EHR/billing system, not performed manually. Manual reconciliation in programs serving 15 or more patients per day is error-prone and unsustainable.

Group Therapy Billing Within IOP and PHP

Group therapy is the backbone of IOP and PHP programming, typically comprising 60% to 80% of scheduled program hours. The billing treatment of group therapy varies based on whether the program uses per-diem or per-service billing. For a detailed guide on group therapy documentation and billing compliance, see our group therapy documentation and billing guide.

Under Per-Diem Billing

When IOP or PHP is billed on a per-diem basis, group therapy sessions are included in the bundled daily rate. Individual group therapy claims (CPT 90853) are not submitted. However, the documentation requirements for group therapy do not diminish under per-diem billing. Every participant must still have an individualized progress note for each group session that documents their specific participation, clinical presentation, response to the group content, and relevance to their treatment plan goals.

This documentation is essential because payers audit group therapy records during concurrent review and retrospective audit. A per-diem claim supported by group notes that are identical for all participants, that lack individualized content, or that do not exist for sessions listed on the daily schedule will be recouped on audit even though the group was not billed separately.

Under Per-Service Billing

When the payer contract requires per-service billing, each group therapy session is billed separately using CPT 90853. One 90853 claim is submitted for each participant in each group session. The billing and compliance requirements include:

  • Census validation: The number of 90853 claims must match the group attendance roster. Eight participants on the roster means eight 90853 claims for that session. Discrepancies between attendance and billing are flagged on audit.
  • Minimum participant requirements: Most payers require a minimum of 2 to 4 participants for a session to qualify as group therapy. Sessions with fewer than the minimum must be rebilled as individual therapy codes.
  • Rendering provider: The group facilitator must be the rendering provider on all 90853 claims for the session. Co-facilitated groups require determining which provider is the rendering provider for billing purposes.
  • Individualized documentation: Each patient must have a separate progress note documenting their participation. A single group note that does not address each patient individually is insufficient.

Same-Day Service Stacking

Under per-service billing, a patient in IOP or PHP may receive multiple billable services on the same day: individual therapy (90834/90837), one or more group therapy sessions (90853), family therapy (90847), and medication management (99213-99215 + 90833). Each service must be documented separately with its own clinical note, time documentation, and clinical justification. The total billed services per day must be consistent with the program schedule and attendance records.

Step-Down Billing: Residential to PHP to IOP to Outpatient

The continuum of care in behavioral health typically follows a step-down pattern: residential treatment to PHP, PHP to IOP, and IOP to standard outpatient therapy. Each transition represents a billing inflection point that requires a new authorization, new billing codes, and often a different billing methodology. Managing these transitions cleanly is essential for both revenue continuity and clinical care quality. Organizations planning to offer the full continuum should review our guide to starting a substance abuse treatment center for licensing and structural considerations.

Residential to PHP Transition

  • Authorization: A new PHP authorization must be obtained before the residential discharge date. The residential authorization does not extend to PHP. The authorization request must demonstrate that the patient has stabilized enough to leave the 24-hour residential environment but still requires the intensity and structure of a hospital-level day program.
  • Billing transition: Residential per-diem billing ends on the last residential day. PHP per-diem billing begins on the first PHP day, which is typically the residential discharge date. Do not bill both residential and PHP per-diem on the same day.
  • EHR transition: The patient's billing configuration must be updated from residential to PHP including: level of care, billing codes, revenue codes, authorization reference number, and the applicable per-diem rate. This should be automated through the level-of-care transition function in the EHR.

PHP to IOP Transition

  • Authorization: A new IOP authorization is required. The clinical documentation must demonstrate that the patient has achieved sufficient stability to step down from PHP intensity but still requires structured intensive outpatient services. IOP authorization requests should include documentation of the patient's functional improvement during PHP and the specific goals that IOP will address.
  • Billing transition: PHP billing ends; IOP billing begins. Revenue codes change from 0912/0913 to 0905/0906. HCPCS codes change from PHP-specific codes to S9480 or H0015. CMS specifically rejects overlapping PHP and IOP claims. Configure billing system rules to prevent overlap.
  • Schedule change: The patient's program schedule decreases from PHP frequency (4-5 days/week, 5-6 hours/day) to IOP frequency (3-5 days/week, 3 hours/day). Ensure attendance tracking reflects the new schedule and minimum hour requirements.

IOP to Outpatient Transition

  • Billing model change: The transition from IOP to standard outpatient therapy shifts from institutional per-diem billing (UB-04) to professional per-service billing (CMS-1500). This is a fundamental billing methodology change that requires different claim forms, different codes, and often different staff workflows.
  • Authorization: Outpatient therapy authorization is typically less intensive than IOP, often covering 10 to 20 sessions or a 90-day period rather than requiring weekly concurrent review. However, a new authorization is still required; the IOP authorization does not extend to outpatient services.
  • Revenue impact: The per-patient revenue drops significantly from IOP to outpatient. An IOP patient generating $1,200/week (3 days at $400/day) steps down to generating $150 to $250/week in individual outpatient therapy. This revenue decline is expected and clinically appropriate, but organizations should plan for it in financial forecasting.

Managed Medicaid vs. Commercial Payer Requirements

IOP and PHP billing requirements vary significantly between managed Medicaid plans and commercial payers. Maintaining payer-specific billing configurations is not optional; a single billing template applied across all payers will produce denials from both Medicaid and commercial plans.

Managed Medicaid

  • Per-diem is dominant: Managed Medicaid plans in most states require per-diem billing for IOP and PHP. Per-service billing is rarely permitted under Medicaid managed care contracts.
  • State-specific codes: Each state's Medicaid program may use different HCPCS codes, modifiers, and revenue codes for IOP and PHP. A multi-state organization must maintain separate billing configurations for each state's Medicaid program. Some states have recently updated their IOP/PHP billing codes; South Carolina, for example, added IOP and PHP program billing categories in recent years.
  • Lower reimbursement rates: Medicaid IOP per-diem rates typically range from $150 to $350/day, and PHP rates from $250 to $600/day. These are substantially below commercial rates and require higher patient volume to achieve program financial viability.
  • Authorization intensity: Managed Medicaid concurrent review frequency is often more aggressive than commercial plans, with some MCOs requiring weekly concurrent reviews for both IOP and PHP. The documentation threshold for continued stay approval may also be higher.
  • Shorter timely filing deadlines: Medicaid timely filing deadlines are typically 90 to 180 days, shorter than the 365-day standard for most commercial payers. Combined with the documentation complexity of IOP/PHP, this creates timely filing risk.

Commercial Insurance

  • Contract-specific billing model: Commercial payers may require per-diem, per-service, or hybrid billing depending on the contract. Verify the billing model for each commercial contract before submitting claims.
  • BH carve-out considerations: Many commercial plans carve out behavioral health management to a separate entity (e.g., Optum, Carelon). IOP/PHP authorization requests and claims must be directed to the carve-out entity, not the medical plan. Submitting to the wrong entity is a common denial cause.
  • Higher reimbursement, higher scrutiny: Commercial rates are higher but payers apply more rigorous utilization review, particularly for PHP. Commercial payers frequently request clinical documentation during concurrent review and deny continued stay when documentation does not clearly differentiate PHP need from IOP appropriateness.
  • Network status matters: In-network IOP/PHP rates are negotiated through contracts. Out-of-network billing introduces balance billing risk, potentially higher patient cost-sharing, and slower reimbursement. Single-case agreements may be available for out-of-network patients who require IOP/PHP at a facility without in-network alternatives.

Common Denial Reasons and Prevention Strategies

IOP and PHP denial patterns are predictable and largely preventable. The denial categories differ between IOP and PHP because of their different medical necessity thresholds, and they differ from residential treatment denials because of the attendance-based billing model.

Denial Category IOP vs. PHP Root Cause Prevention Strategy
Medical necessity not established PHP (25-30% of denials); IOP (15-20%) PHP documentation does not differentiate from IOP intensity; IOP documentation does not justify why standard outpatient is insufficient; generic clinical narratives without specific symptom severity indicators Level-specific documentation templates that prompt clinicians to address why the patient requires this specific level, not just that they need treatment. PHP templates must specifically address inpatient-alternative justification.
Authorization gap / expired auth Both (20-25%) Concurrent review not submitted before expiration; short auth periods (5-7 days for PHP) leave minimal buffer; payer decision delayed Centralized authorization tracking with automated alerts. Dedicate UR staff time specifically to PHP concurrent reviews given their 5-7 day cycle. Submit reviews 3-5 days before expiration.
Minimum hours/services not met Both (10-15%) Patient attended but did not meet daily minimum hours; weekly hours fell below 9 (IOP) or 20 (PHP); fewer than 3 services on PHP day Real-time attendance tracking with automated alerts when a patient risks falling below daily or weekly minimums. Configure billing system to hold charges for days that do not meet minimum thresholds.
Incorrect billing code or claim type Both (10-12%) IOP billed on CMS-1500 instead of UB-04; wrong revenue code for program type; S9480 used for SUD program or H0015 for MH program; missing condition code 92 for Medicare IOP Payer-specific billing configuration matrices verified at contracting and updated at least annually. Claim scrubbing rules that validate code-revenue code-claim type alignment before submission.
Group therapy documentation deficiencies Both (8-12%, higher in per-service) Identical notes for all participants; no individualized content; attendance roster does not match billed participants; rendering provider mismatch EHR-enforced individualized group note templates. Automated attendance-to-billing validation. Provider assignment verification before claim release.
Level-of-care transition errors Both (5-8%) Overlapping PHP and IOP claims; residential and PHP billed on same day; IOP authorization reference used on PHP claims after step-up; billing codes not updated at transition Automated level-of-care transition workflows in EHR that update billing codes, revenue codes, and authorization references on the transition date. Hard stop preventing overlapping level-of-care billing.

PHP Medical Necessity: The Critical Differentiator

The number-one preventable PHP denial is medical necessity. The fix is specific: PHP documentation must answer the question "Why would this patient require inpatient psychiatric hospitalization if PHP were not available?" If the clinical note does not address this question explicitly, the concurrent review will not be approved. Train clinical staff to document PHP medical necessity using the inpatient-alternative framework, not general statements about treatment intensity. The phrase "patient benefits from the structure of PHP" is not medical necessity documentation. The phrase "patient exhibits acute suicidal ideation with passive plan, labile mood with rapid decompensation when unstructured, and requires daily psychiatric monitoring for medication titration of newly initiated lithium, conditions that would require inpatient admission absent PHP-level structure" is medical necessity documentation.

Revenue and Performance Benchmarks for IOP and PHP

Financial performance in IOP and PHP programs is driven by attendance volume, per-diem rates, and denial management. These programs have lower fixed costs than residential treatment (no 24-hour staffing, no room and board) but higher per-patient revenue variability because each missed day directly reduces revenue.

Metric IOP Benchmark PHP Benchmark
Per-diem rate (commercial) $350-$650/day $600-$1,200/day
Per-diem rate (Medicaid) $150-$350/day $250-$600/day
Revenue per patient per week $750-$1,950 (3 days/week) $2,500-$6,000 (5 days/week)
Average program duration 6-16 weeks 2-4 weeks
Attendance rate target >85% >90%
Denial rate target <8% <10%
Authorization compliance rate >98% >98%
Days in A/R <40 days <42 days
Net collection rate >94% >93%

Program Capacity and Revenue Modeling

IOP and PHP programs are typically sized by maximum concurrent patient capacity rather than beds. A program with capacity for 15 patients per session running 3 IOP groups per day at $400/day per-diem generates:

  • Full capacity (100% attendance): 15 patients x 3 days/week x $400/day = $18,000/week per cohort
  • 85% attendance: 12.75 effective patients x 3 days/week x $400/day = $15,300/week
  • Annual at 85% attendance: $15,300/week x 50 weeks = $765,000 per year for a single IOP cohort
  • Multiple cohorts: Organizations running morning and evening IOP cohorts can double this capacity without additional facility space, subject to staffing and scheduling constraints

EHR and Technology Requirements for IOP/PHP RCM

IOP and PHP programs require EHR capabilities that extend beyond standard outpatient therapy workflows. The multi-service, multi-day, attendance-dependent billing model creates specific technology requirements. For a broader comparison of behavioral health EHR platforms, see our behavioral health EHR comparison.

  • Program scheduling and attendance tracking: Support for multi-day program schedules with individual session blocks. Real-time attendance recording that distinguishes between attended, partial attendance (with actual hours), no-show, and excused absence. Automated alerting when a patient's weekly attended hours approach the minimum threshold.
  • Institutional claim generation: UB-04/837I claim generation with configurable revenue codes, HCPCS codes, and type-of-bill codes per payer. Support for both per-diem and per-service billing models with payer-level configuration. Condition code 92 automation for Medicare IOP claims.
  • Group therapy workflow: Integrated group session management that captures attendance, assigns rendering providers, and generates individualized progress note shells for each participant. Census validation that prevents billing for non-attendees. Minimum participant count validation before group billing is released.
  • Per-diem charge automation: Automatic generation of per-diem charges based on attendance records and minimum hour verification. Charge holds for days that do not meet billing criteria. Daily charge reconciliation against attendance and program schedule.
  • Level-of-care transition management: Automated workflow for transitioning patients between residential, PHP, IOP, and outpatient levels of care. Hard stops preventing overlapping billing between levels. Authorization reference number updating at each transition.
  • Authorization tracking with concurrent review workflow: Dashboard showing active authorizations with remaining days, concurrent review due dates, and pending review status. Automated alerts calibrated to the specific concurrent review frequency for IOP (7-14 days) and PHP (5-7 days). Workflow for generating clinical review packets from existing documentation.
  • Multi-service day documentation: Support for documenting multiple services per day (individual therapy, group therapy, medication management, family therapy) with separate notes and time tracking per service. Validation that documented services match billed services.

Frequently Asked Questions

What is the difference between S9480 and H0015 for IOP billing?

S9480 (Intensive outpatient psychiatric services, per diem) is used for mental health IOP programs, while H0015 (Alcohol and/or drug services, intensive outpatient) is used for substance use disorder IOP programs. Both are per-diem codes that bundle all services delivered during an IOP day into a single charge. The code selection should align with the patient's primary treatment focus. When a patient has co-occurring mental health and SUD diagnoses, use the code matching the primary treatment focus as defined by the treatment plan. Billing both S9480 and H0015 on the same day for the same patient is not permitted. Some payers accept either code regardless of diagnosis while others require strict alignment.

Can PHP be billed to Medicare by any provider type?

No. Medicare limits PHP billing to hospital outpatient departments (including psychiatric hospitals and critical access hospitals) and Community Mental Health Centers (CMHCs). Freestanding behavioral health practices that are not hospital-affiliated and not certified as CMHCs cannot bill Medicare for PHP services. This is a significant constraint for organizations planning PHP programs. To serve Medicare patients in PHP, organizations must obtain hospital affiliation or CMHC certification.

How does attendance tracking affect IOP and PHP billing?

Attendance directly determines billing eligibility. For IOP, most payers require a minimum of 3 hours of structured clinical services per day for the day to be billable. For PHP, the minimum is typically 4 to 6 hours per day. If a patient does not meet minimum hours, the day may not qualify for per-diem billing or may be reimbursed at a reduced partial-day rate. Under CMS rules, PHP and IOP days with three or fewer services are paid at a reduced rate. Attendance records must match billing records exactly; claims for days the patient did not attend or did not meet minimum hours are a primary audit target.

What are the minimum weekly hour requirements for IOP and PHP?

IOP requires a minimum of 9 hours per week, typically 3 hours per day for 3 days per week. PHP requires a minimum of 20 hours per week, typically 5 to 6 hours per day for 4 to 5 days per week. Falling below weekly minimums can invalidate the level-of-care designation for the week or episode. Programs must track weekly hours per patient and have protocols for addressing partial attendance that risks dropping below the threshold. Some payers conduct retrospective reviews of weekly hours and recoup payments for weeks below the minimum.

Can individual therapy and group therapy be billed separately on the same day as IOP or PHP?

Under per-diem billing, all services are bundled and cannot be billed separately. Under per-service billing, each service is billed individually with its own CPT code and documentation. Some payer contracts use a hybrid model where the program per-diem is billed on the UB-04 and specific excluded services (psychiatric evaluation, medication management by an outside provider, psychological testing) can be billed separately on a CMS-1500. The specific services that can be split-billed vary by contract and must be verified before submitting.

What is the most common denial reason for PHP claims?

Medical necessity not established is the most common PHP denial, accounting for 25% to 30% of PHP denials. Payers deny PHP when documentation does not demonstrate why the patient requires hospital-level care intensity. The documentation must specifically address why IOP is insufficient: active symptom severity creating safety risk, need for daily medical or psychiatric monitoring, risk of decompensation, and inability to maintain stability between IOP sessions. Generic documentation stating the patient "benefits from structure" will be denied.

How does step-down billing work when transitioning from PHP to IOP?

Each level-of-care transition requires a new authorization. PHP authorization does not carry over to IOP. PHP billing ends on the last PHP day, and IOP billing begins on the first IOP day. Billing both PHP and IOP on the same day is not permitted. CMS specifically rejects overlapping PHP and IOP claims within a 7-day window. Initiate the step-down authorization 3 to 5 days before the planned transition to avoid authorization gaps between levels.

Editorial Standards

Last reviewed:

Methodology

  • IOP and PHP billing codes and revenue code pairings validated against CMS OPPS final rules, Medicare billing transmittals, and published payer guidelines
  • Medicare PHP and IOP provider eligibility requirements sourced from CMS provider-type regulations and Noridian Medicare billing guides
  • Per-diem rate ranges derived from published state Medicaid fee schedules, commercial payer reimbursement data, and industry financial benchmarking
  • Denial patterns and prevention strategies sourced from behavioral health revenue cycle operational data and claims analytics

Primary Sources