2026 OPPS Rule: PHP and IOP Rate Changes Explained for Behavioral Health
The CY 2026 Hospital Outpatient Prospective Payment System (OPPS) and Ambulatory Surgical Center (ASC) final rule (CMS-1809-FC) carries direct financial consequences for every behavioral health facility operating a Partial Hospitalization Program or Intensive Outpatient Program. The rule updates PHP per-diem rates, corrects the longstanding CMHC cost inversion, refines IOP reimbursement based on the first full year of claims data since IOP became a Medicare benefit, and reinforces billing requirements around Condition Code 92. This article explains each change in plain language, quantifies the revenue impact by facility type, and provides a step-by-step action plan for billing teams.
What Changed
- Hospital-based PHP rates increased with market basket adjustment to approximately $290-$310 per day
- CMHC PHP rates corrected downward to approximately $200-$220 per day, fixing the longstanding cost inversion where CMHCs were paid more than hospitals
- IOP rates refined based on first year of actual claims data: hospital-based ~$180-$200/day, CMHC ~$120-$140/day
- Condition Code 92 requirements reinforced for IOP claim identification on institutional billing
- CMHC IOP costs now set at approximately 40% of hospital-based rates, reflecting actual cost differentials
- IOP service hour minimums confirmed: 9 hours/week for adults, 6 hours/week for adolescents
2025 Behavioral Health Integration CPT Codes, Billing, and Reimbursement
Effective Date: January 1, 2026
All rate changes and billing requirements in the CY 2026 OPPS/ASC final rule (CMS-1809-FC) apply to dates of service on or after January 1, 2026. Facilities should have updated charge masters, billing configurations, and staff training completed before the effective date. Claims for 2026 dates of service will be adjudicated under the new rate structure regardless of when they are submitted.
PHP Per-Diem Rate Updates
Partial Hospitalization Programs have been a cornerstone of Medicare behavioral health coverage for decades, but the reimbursement structure has carried a significant distortion that the CY 2026 rule finally addresses. Understanding the rate changes requires context on both the hospital-based and CMHC-based PHP rate trajectories.
Hospital-Based PHP Rates
Hospital-based PHP programs, operated by hospital outpatient departments, receive per-diem rates under the OPPS that are calculated based on the hospital market basket update and the APC (Ambulatory Payment Classification) assignment for PHP services. For CY 2026, hospital-based PHP per-diem rates fall in the range of approximately $290 to $310 per day, reflecting the annual market basket adjustment applied to the 2025 base rate.
The market basket adjustment for CY 2026 incorporates hospital input price inflation, productivity adjustments, and any statutory payment update factors. For hospital-based PHP programs, this translates to a modest but positive rate increase that keeps pace with operational cost growth. The exact per-diem amount varies by geographic region due to the wage index adjustment that accounts for local labor cost differences.
The CMHC Cost Inversion: What It Was and How It Got Fixed
For years, Community Mental Health Centers received higher PHP per-diem rates than hospital-based programs despite having lower operating costs. This anomaly, known as the cost inversion, occurred because CMHC PHP rates were calculated using a cost-based methodology that relied on outdated and unrepresentative cost report data. The result was perverse: CMHCs, which have lower overhead, lower staffing ratios, and lower facility costs than hospital outpatient departments, were being paid more per day for PHP services.
CMS has acknowledged this distortion in multiple rulemaking cycles but had not fully corrected it until the CY 2026 rule. The correction recalculates CMHC PHP rates based on updated cost data that more accurately reflects the actual resource costs of delivering PHP services in a CMHC setting. The result is a meaningful rate decrease for CMHCs:
| Setting | 2025 Approximate PHP Per-Diem | 2026 Approximate PHP Per-Diem | Change |
|---|---|---|---|
| Hospital-Based | $275-$295/day | $290-$310/day | +5% to +6% |
| CMHC | $260-$285/day | $200-$220/day | -20% to -25% |
For CMHCs, this rate correction is significant. A CMHC PHP program treating an average daily census of 25 patients at 230 operating days per year would see annual revenue decrease by approximately $345,000 to $460,000 based on the rate difference. This is not a surprise for organizations that have been tracking the rulemaking process, but it requires immediate financial planning and potential operational restructuring.
What PHP Programs Need to Know About the Rate Structure
Beyond the headline rate changes, several structural elements of PHP per-diem billing remain important for accurate revenue modeling:
- Per-diem, not per-service: PHP reimbursement under OPPS is a per-diem payment that covers all services delivered during the program day. Individual therapy, group therapy, medication management, psychoeducation, and therapeutic activities are all bundled into the per-diem rate. Facilities cannot separately bill for individual services delivered within the PHP day under Medicare.
- Three-service threshold: Medicare requires that a PHP patient receive a minimum of three distinct services per day to qualify for the PHP per-diem. If a patient attends the program but receives fewer than three qualifying services, the day may not meet the billing threshold and individual services may need to be billed under standard outpatient codes at lower rates.
- Discharge day billing: The day of discharge from PHP is generally not billable as a PHP day unless the patient received a full program day of services. This affects end-of-month and discharge-day revenue calculations.
- APC assignment: PHP per-diem rates are determined by the APC to which PHP services are assigned. CMS reviews APC assignments annually, and changes to the APC grouping can affect the per-diem rate independent of the market basket update. Verify the current APC assignment in the OPPS Addendum A for your specific PHP service configuration.
IOP Rate Updates and Stabilization
Intensive Outpatient Programs became a Medicare-covered benefit for the first time under the CY 2024 OPPS rule. The CY 2025 rates were preliminary, set before CMS had meaningful claims data to calibrate the rates. With approximately 18 months of IOP claims data now available, the CY 2026 rule refines the IOP per-diem rates to better reflect actual service delivery costs.
2026 IOP Per-Diem Rates
| Setting | 2026 Approximate IOP Per-Diem | Notes |
|---|---|---|
| Hospital-Based | $180-$200/day | Rates stabilized from 2025 preliminary values; wage index adjusted |
| CMHC | $120-$140/day | Approximately 40% of hospital-based rate; cost inversion correction applies |
The IOP rate refinement represents a stabilization rather than a dramatic shift for most programs. Hospital-based IOP programs will see rates that are relatively consistent with 2025 values after accounting for the market basket adjustment. CMHC-based IOP programs are subject to the same cost inversion correction logic that affects PHP rates, placing CMHC IOP rates at approximately 40% of hospital-based rates.
IOP Service Requirements
The CY 2026 rule confirms the IOP service delivery requirements that were established when the benefit was created in 2024:
- Adult programs: Minimum of 9 hours of structured clinical programming per week. This typically translates to 3 hours per day across 3 days per week, though facilities have flexibility in scheduling as long as the weekly minimum is met.
- Adolescent programs: Minimum of 6 hours of structured clinical programming per week. The lower threshold reflects the shorter attention spans and academic scheduling constraints of adolescent patients.
- Service composition: IOP programming must include a combination of individual therapy, group therapy, psychoeducation, and other evidence-based clinical interventions delivered under an individualized treatment plan. Activities that are primarily recreational, social, or occupational in nature do not count toward the minimum hour threshold.
- Treatment plan requirements: Each IOP patient must have an individualized treatment plan developed by a multidisciplinary treatment team, updated at clinically appropriate intervals, and documenting measurable treatment goals. The treatment plan must support the medical necessity of IOP-level services versus standard outpatient treatment.
Condition Code 92: IOP Claim Identification
Condition Code 92 is the mechanism by which IOP claims are identified on institutional billing. This code was introduced alongside the IOP benefit in 2024 and tells the Medicare Administrative Contractor (MAC) that the services on the claim were delivered as part of a structured Intensive Outpatient Program rather than standard outpatient services.
Why Condition Code 92 Matters
Without Condition Code 92 on the claim, IOP services will be adjudicated under standard outpatient OPPS rates rather than IOP per-diem rates. In most cases, this results in lower reimbursement because the per-diem IOP rate bundles multiple services into a single payment that is typically higher than the sum of individual outpatient service payments for the same service mix. Conversely, including Condition Code 92 on non-IOP claims is a billing error that can trigger audits.
Configuration Requirements
- Billing system setup: Condition Code 92 must be configured to automatically populate on claims generated from IOP encounters. This is typically done at the program or department level in the billing system, so that any encounter tagged as an IOP visit inherits the condition code. Manual entry of condition codes is error-prone and should be avoided.
- Claim form placement: On the UB-04, Condition Code 92 appears in Form Locators 18-28 (Condition Codes). It should be present on every claim that includes IOP services. If the claim includes both IOP services and non-IOP services (which would be unusual but possible in transition scenarios), the billing must be structured to correctly identify which services are IOP-related.
- Verification testing: Before the first IOP claim of 2026 is submitted, facilities should generate test claims in their billing system and verify that Condition Code 92 appears in the correct field. This is particularly important for facilities that updated their billing software or changed EHR systems since 2024.
Common Billing Error
The most common Condition Code 92 error is omission rather than misuse. Facilities that manually enter condition codes or that have incomplete billing system configurations frequently submit IOP claims without Condition Code 92, resulting in claims being processed at lower outpatient rates. This error is often not caught until revenue reports show unexpectedly low IOP reimbursement, at which point the facility must resubmit corrected claims within the timely filing deadline.
PHP vs. IOP: 2026 Rate and Requirement Comparison
Understanding the differences between PHP and IOP billing is critical for facilities that operate both programs, and for facilities considering adding an IOP program. The following comparison highlights the key billing and operational differences under the 2026 OPPS rule.
| Dimension | PHP | IOP |
|---|---|---|
| Hospital per-diem (2026) | ~$290-$310/day | ~$180-$200/day |
| CMHC per-diem (2026) | ~$200-$220/day | ~$120-$140/day |
| Daily programming hours | 4-6 hours/day typical | 3+ hours/day typical |
| Weekly minimum hours | 20+ hours/week typical | 9 hours/week (adults), 6 hours/week (adolescents) |
| Minimum services per day | 3 distinct services | Defined by treatment plan |
| Condition code | Not required (program identified by TOB and revenue codes) | Condition Code 92 required |
| Medicare benefit established | Longstanding benefit | CY 2024 (new) |
| Type of Bill | 0831 (hospital) or 0761 (CMHC) | 0831 (hospital) or 0761 (CMHC) with Condition Code 92 |
For facilities operating both PHP and IOP, the step-down pathway from PHP to IOP is a key clinical and billing workflow. When a patient's clinical status improves to the point where PHP-level intensity is no longer medically necessary, stepping the patient down to IOP maintains treatment continuity while generating IOP per-diem revenue rather than losing the patient to standard outpatient. Proper documentation of the level-of-care transition, updated treatment plans, and correct billing code changes are essential to avoid denials during the transition. For a comprehensive guide to IOP and PHP program billing, see our RCM guide for IOP and PHP programs.
What Your Billing Team Needs to Do
The following action items address the specific changes in the CY 2026 OPPS rule that affect PHP and IOP billing operations. They are prioritized by urgency and revenue impact.
- Update the charge master with 2026 OPPS rates (immediate). Load the CY 2026 PHP and IOP per-diem rates into the charge master. For hospital-based programs, apply the market basket-adjusted rates. For CMHC programs, apply the corrected rates that reflect the cost inversion fix. Verify that wage index adjustments are correctly applied for your facility's geographic location.
- Verify Condition Code 92 configuration for IOP (immediate). Generate a test IOP claim in the billing system and confirm that Condition Code 92 appears in the correct UB-04 field (Form Locators 18-28). If Condition Code 92 is not automatically populated for IOP encounters, configure the billing system to apply it based on the encounter type, department, or program designation. Do not rely on manual entry.
- Retrain billing staff on PHP vs. IOP claim requirements (within 30 days). Conduct a focused training session covering the distinct billing requirements for PHP and IOP claims: per-diem structure, Type of Bill codes, Condition Code 92 for IOP, minimum service thresholds for PHP, and the documentation required to support each program level. Emphasize the prohibition on billing both PHP and IOP for the same patient on the same day.
- Model revenue under the new rates (within 30 days). For each PHP and IOP program, recalculate projected annual revenue using the 2026 per-diem rates and your average daily census. CMHC programs should model the revenue decrease from the cost inversion correction and identify operational adjustments needed to maintain financial viability. Hospital-based programs should verify that the modest rate increase offsets operational cost growth.
- Review IOP weekly hour documentation (within 30 days). Verify that IOP programs are consistently documenting the minimum weekly service hours (9 hours for adults, 6 hours for adolescents) in a format that supports claim audits. If documentation does not clearly demonstrate that the weekly threshold was met, claims are vulnerable to post-payment audit recoupment.
- Audit PHP three-service-per-day compliance (within 60 days). Pull a sample of PHP claims from Q4 2025 and verify that each billed PHP day included documentation of at least three distinct qualifying services. If any days fall below the threshold, determine whether it was a documentation issue or a service delivery issue and implement corrective workflows.
- Update PHP-to-IOP step-down billing workflows (within 60 days). For facilities operating both PHP and IOP, review the billing workflow for patients stepping down from PHP to IOP. Ensure that the billing system correctly transitions from PHP billing codes and configuration to IOP billing codes and Condition Code 92 on the date of transition. Verify that treatment plan documentation supports the level-of-care change.
- CMHC financial contingency planning (within 90 days). CMHCs affected by the cost inversion correction should develop a financial impact assessment and contingency plan. Options include increasing patient volume to offset the rate decrease, renegotiating commercial payer contracts to maintain blended rates, reducing operating costs, or expanding IOP services (which, while also at lower CMHC rates, may attract additional patient volume due to lower cost-sharing for beneficiaries).
Revenue and Financial Impact
The revenue impact of the CY 2026 OPPS rule varies dramatically depending on whether the facility is a hospital-based program or a CMHC, and whether it operates PHP, IOP, or both.
Hospital-Based PHP Program
A hospital-based PHP program with an average daily census (ADC) of 20 patients operating 250 days per year under the 2026 rates:
- Revenue at $300/day per-diem: 20 patients x $300 x 250 days = $1,500,000 annually
- Compared to 2025 at $285/day: 20 x $285 x 250 = $1,425,000
- Net increase: approximately +$75,000 per year (+5.3%)
CMHC PHP Program
A CMHC PHP program with an ADC of 25 patients operating 230 days per year:
- Revenue at $210/day per-diem (2026): 25 x $210 x 230 = $1,207,500 annually
- Compared to 2025 at $272/day: 25 x $272 x 230 = $1,564,000
- Net decrease: approximately -$356,500 per year (-22.8%)
This is the cost inversion correction in dollar terms. For a CMHC whose PHP program represents a significant portion of total revenue, this decrease requires strategic planning and potentially operational restructuring. Some CMHCs may need to evaluate whether their PHP programs remain financially viable at the corrected rates, or whether shifting resources toward IOP, outpatient, or other service lines offers better financial sustainability.
Hospital-Based IOP Program
A hospital-based IOP program with an ADC of 15 patients operating 250 days per year:
- Revenue at $190/day per-diem (2026): 15 x $190 x 250 = $712,500 annually
- IOP rates are stabilized from 2025 preliminary values; the change from 2025 is modest
- Net change: approximately flat to +3%
CMHC IOP Program
A CMHC IOP program with an ADC of 20 patients operating 230 days per year:
- Revenue at $130/day per-diem (2026): 20 x $130 x 230 = $598,000 annually
- CMHC IOP rates reflect the cost inversion correction at approximately 40% of hospital-based rates
- Revenue is lower than hospital-based IOP but may represent a growth opportunity if CMHC PHP volume is redirected to IOP
Strategic Note for CMHCs
CMHCs facing the cost inversion correction on PHP rates should evaluate their IOP programs as a partial offset strategy. While CMHC IOP rates are also lower than hospital-based rates, IOP programs have lower staffing requirements and can serve higher patient volumes per clinician. Expanding IOP capacity while right-sizing PHP capacity may help CMHCs maintain total program revenue despite the per-diem rate decrease. Model both scenarios before making operational changes.
EHR and Technology Implications
The CY 2026 OPPS changes require specific configurations and capabilities in EHR and billing systems. Facilities should verify the following with their technology vendors or internal IT teams.
- Per-diem rate tables: The EHR and billing system must support per-diem rate tables that differentiate between PHP and IOP, and between hospital-based and CMHC settings. Rates should be loaded at the program level so that encounters within each program automatically inherit the correct per-diem rate. Platforms like AZZLY Rize that support configurable program-level billing rules can automate this differentiation and reduce manual billing errors.
- Condition Code 92 automation: The billing system must automatically apply Condition Code 92 to claims generated from IOP encounters. This requires a reliable link between the clinical encounter (tagged as IOP) and the claim generation process. Systems that require manual condition code entry are a significant source of billing errors.
- Three-service tracking for PHP: The EHR should track the number of distinct services delivered to each PHP patient on each program day. Ideally, the system generates an alert if a patient has fewer than three documented services on a PHP day, because that day may not meet the billing threshold. This real-time validation prevents billing for days that do not meet the PHP service requirement.
- IOP weekly hour tracking: The system should aggregate service hours per patient per week for IOP programs and flag weeks where the minimum threshold (9 hours for adults, 6 hours for adolescents) is not met. This supports both clinical compliance and billing audit defense.
- PHP-to-IOP transition workflow: When a patient transitions from PHP to IOP, the EHR should support a level-of-care transition that updates the billing configuration (program designation, per-diem rate, Type of Bill adjustments, Condition Code 92 activation) as of the transition date. Ease offers workflow tools that can help streamline these program-level transitions, ensuring that billing changes are synchronized with clinical level-of-care decisions.
- Charge master version control: The charge master must support date-effective rate changes so that 2025 rates apply to 2025 dates of service and 2026 rates apply to 2026 dates of service. This is critical for claims submitted in early 2026 for late-2025 dates of service and vice versa. Verify that the system correctly applies the rate based on date of service, not date of claim submission.
- Reporting and analytics: Update financial reports to reflect the new rate structure. CMHC programs should build reports that compare actual per-diem revenue against the 2025 baseline to track the financial impact of the cost inversion correction in real time. Hospital-based programs should verify that the market basket increase is flowing through to actual paid claims.
Frequently Asked Questions
What is the CMHC cost inversion and how does the 2026 OPPS rule fix it?
The CMHC cost inversion refers to a longstanding anomaly where Community Mental Health Centers received higher per-diem PHP rates than hospital-based programs despite having lower operating costs. This occurred because CMHC rates were calculated using a cost methodology that did not accurately reflect the lower overhead and staffing costs at CMHCs. The CY 2026 OPPS rule corrects this by recalculating CMHC PHP rates based on updated cost data, resulting in CMHC PHP per-diem rates approximately 30% lower than hospital-based PHP rates. CMHCs will see a rate decrease, while hospital-based programs see a modest increase.
What are the 2026 PHP per-diem rates for hospitals vs. CMHCs?
Under the CY 2026 OPPS rule, hospital-based PHP per-diem rates are approximately $290 to $310 per day, reflecting a market basket adjustment increase. CMHC PHP per-diem rates are approximately $200 to $220 per day, reflecting the cost inversion correction. The exact rate depends on the APC assignment and geographic wage index adjustment. These rates represent the Medicare payment amount before beneficiary cost-sharing.
What is Condition Code 92 and why does it matter for IOP billing?
Condition Code 92 is used on institutional claims to identify services delivered as part of a structured Intensive Outpatient Program. Without it, IOP claims are processed under standard outpatient rates, which typically results in lower reimbursement. The 2026 OPPS rule reinforces billing requirements around Condition Code 92. Facilities must configure their billing systems to automatically apply this code to all IOP claims to avoid under-reimbursement.
What are the minimum service hour requirements for IOP under Medicare?
Adult IOP programs must provide a minimum of 9 hours of structured clinical programming per week, and adolescent programs must provide a minimum of 6 hours per week. These hours must include individual therapy, group therapy, psychoeducation, and other evidence-based interventions under an individualized treatment plan. If the weekly minimum is not met, the facility may need to bill individual services under standard outpatient codes rather than the IOP per-diem.
How does the 2026 OPPS rule affect IOP programs that started billing in 2024?
The CY 2026 rule refines IOP rates based on approximately 18 months of actual claims data collected since the benefit launched in 2024. For most hospital-based IOP programs, the 2026 rates represent a stabilization rather than a significant change. For CMHC-based IOP programs, the cost inversion correction applies and rates are adjusted downward relative to hospital-based rates. IOP programs should model their 2026 revenue based on the updated per-diem rates.
Can a facility bill PHP and IOP for the same patient on the same day?
No. PHP and IOP represent different levels of care intensity, and a patient cannot receive both on the same day under Medicare billing rules. When a patient transitions between programs, the transition must be documented with updated treatment plans, and billing must reflect the correct program level for each date of service. Billing both PHP and IOP on the same day will result in denials and potential audit exposure.
Need Help Navigating This Change?
Regulatory changes like CY 2026 OPPS Rule affect your EHR configuration, billing workflows, and compliance posture. Tell us about your organization and we'll help you assess the impact and identify what needs to change.
Get a Free Compliance AssessmentEditorial Standards
Last reviewed:
Methodology
- PHP and IOP per-diem rate ranges derived from CMS-1809-FC final rule rate tables, OPPS Addendum A, and geographic wage index adjustment methodology
- CMHC cost inversion analysis based on CMS rulemaking history, MedPAC reports on CMHC payment adequacy, and published CMHC cost report data
- IOP benefit requirements sourced from CY 2024 OPPS final rule establishing the IOP benefit and CY 2026 refinements
- Revenue impact calculations based on average daily census benchmarks, standard operating day assumptions, and published OPPS per-diem payment rates
- Condition Code 92 requirements validated against CMS Claims Processing Manual, Chapter 4, and Medicare Administrative Contractor billing guidance