PHP Billing Services that standard outpatient practices rarely encounter. PHP sits between traditional outpatient care and inpatient treatment. That middle ground creates complex payer rules, coding requirements, and authorization demands.

Even small billing mistakes can lead to denials, underpayments, authorization gaps, and longer accounts receivable cycles. Programs must use the correct codes, document medical necessity, and track payer requirements throughout treatment. PHP Billing Services can help programs manage these demands while protecting revenue and reducing preventable claim issues.

This guide explains how PHP billing works, why claims get denied, and what programs should expect from a billing partner.

PHP Billing Services: A Complete Guide for Partial Hospitalization Programs

Partial Hospitalization Programs occupy an awkward position in the payer world. They’re more intensive than standard outpatient, less restrictive than inpatient, and most payer systems weren’t built with that middle ground in mind. The result is a billing environment where the rules are specific, the authorization requirements are ongoing, and the margin for documentation error is narrow.

Programs that bill PHP services correctly — the right revenue codes, the right place of service, the right prior auth cadence — collect what they’ve earned. Programs that treat PHP billing like extended IOP billing, or that rely on generalist billing support without PHP-specific experience, routinely leave 15–25% of potential revenue uncollected. This guide covers how PHP billing works, where claims fail, and what a billing partner needs to actually handle to support a PHP program’s revenue cycle.

What Is PHP Billing and Why Is It Distinct?

A Partial Hospitalization Program (PHP) delivers structured, intensive clinical care for 20 or more hours each week. Patients can still return home or to sober living each evening. Clinically, providers generally understand how PHP works. Billing introduces additional requirements that differ from both standard outpatient and inpatient care.

Providers typically bill PHP services using HCPCS code H0035 or revenue code 0912 on a UB-04 institutional claim. H0035 covers mental health partial hospitalization treatment lasting less than 24 hours. The correct code depends on the payer and the provider’s billing structure.

Most Medicaid programs and many commercial payers use daily rate billing for PHP services. Under this model, the provider bills the entire treatment day as one unit. Some commercial plans instead require providers to bill each service separately. These services may include individual therapy, group therapy, and medical oversight.

Using the wrong billing model can quickly lead to claim denials. Payers may deny claims for improper bundling or missing service codes. Correcting these denials often requires additional documentation, claim adjustments, and valuable staff time.

The distinction between PHP and IOP also matters when submitting claims. IOPs generally provide fewer treatment hours and a lower level of clinical intensity. They also use different revenue codes and often follow different authorization requirements.

Payers review PHP claims using medical necessity criteria specific to this level of care. They may use InterQual, MCG, or their own internal guidelines. Documentation must clearly support the intensity and services associated with PHP treatment. Claims documented at IOP intensity may fail a concurrent review or audit.

How PHP Claims Are Structured

Revenue Codes and HCPCS Codes

The primary revenue code for PHP is 0912 (partial hospitalization), filed on a UB-04. H0035 is the most commonly used HCPCS code for PHP services and is recognized across Medicare, most Medicaid programs, and many commercial payers. Some payers require additional HCPCS codes to be billed alongside H0035 to represent specific service components — group therapy (H0015), individual therapy (90832–90837), or psychiatric evaluation (90792) — depending on how the plan’s contract defines PHP reimbursement.

Daily Rate vs. Per-Service Billing

Medicare and most state Medicaid programs reimburse PHP as an all-inclusive daily rate: one unit of H0035 covers the entire treatment day regardless of which specific services were provided within it. Commercial payers are less consistent. Some follow the daily rate model. Others require programs to itemize and bill each service separately, in which case the PHP program needs to maintain a service log that can support each line item on the claim. Billing a daily rate to a payer that expects itemized services — or the reverse — produces a predictable denial pattern that takes weeks to unwind.

Claim Form: UB-04 vs. CMS-1500

Facility-based PHP programs bill on the UB-04. Programs billing as professional providers — including some group practices that operate PHP without a facility license — may bill on the CMS-1500. The form determines which code set and billing conventions apply. A PHP program that switches between form types based on what’s convenient, rather than what the payer requires for that billing entity, creates credentialing and remittance problems that compound over time.

Place of Service Codes

Place of service 52 (psychiatric facility partial hospitalization) applies to facility-based PHP. POS 53 (community mental health center) applies when the program operates under a CMHC license. Office-based providers billing PHP-equivalent services may use POS 11, though most payers limit full PHP reimbursement to facility or CMHC settings. Using the wrong POS code is one of the more common reasons PHP claims are downcoded to outpatient reimbursement rates without an explicit denial — the claim pays, just at the wrong rate.

The Most Common PHP Billing Mistakes

Billing PHP at IOP rates or using IOP codes

This happens most often when a program expands from IOP to PHP and doesn’t fully update its billing setup. The staff are familiar with IOP codes, the EHR templates are built for IOP documentation, and PHP claims go out with IOP revenue codes. Payers pay at IOP rates. The program doesn’t notice for months because the claims are clearing — just underpaid.

Insufficient medical necessity documentation for daily authorization

PHP requires concurrent review, not just an admission authorization. Payers want to see clinical justification for continued PHP-level care, typically every 5–7 days depending on the plan. Documentation that doesn’t demonstrate ongoing medical necessity at the PHP level — progress notes that describe stability without explaining why step-down hasn’t occurred — gives reviewers grounds to downgrade the auth to IOP or to deny continued PHP days retroactively.

Missing concurrent review deadlines

Authorization for PHP is time-limited. Missing a concurrent review window doesn’t just delay authorization — it often results in the loss of coverage for the days between the expired auth and the approved extension. Those days become the program’s liability unless the appeal is successful, and appeals for missed auth windows are among the hardest to win because the procedural failure is hard to argue against.

Incorrect discharge coding

Discharge status codes on UB-04 claims communicate what happened at the end of the PHP episode: step-down to IOP, transfer to inpatient, discharge to outpatient, against medical advice. Incorrect discharge codes trigger payer audits and, in some cases, recoupment of payments for the entire episode. Programs that auto-populate discharge codes without clinical review are carrying a compliance risk that shows up months after the patient has left.

Not separating SUD and psychiatric PHP claims

Programs that serve both SUD and mental health populations need to bill these separately. The authorization criteria differ, the payer review standards differ, and some payers require separate benefit categories for SUD vs. psychiatric PHP. Bundling them under the same billing workflow creates authorization mismatches that generate denials for the wrong reason — making them harder to appeal correctly.

Prior Authorization and Utilization Review in PHP

PHP is one of the few outpatient-adjacent levels of care where ongoing authorization is effectively universal. Unlike standard outpatient therapy, which most payers cover without prior auth, PHP requires an admission authorization and then concurrent review at regular intervals for as long as the patient remains in the program.

Admission auth for PHP typically requires a clinical assessment, a diagnosis that supports PHP-level intensity, and documentation that lower levels of care have been considered and ruled out. The concurrent review process — usually every 5–7 days — requires updated progress notes, a treatment plan that reflects current clinical status, and a documented rationale for why the patient hasn’t stepped down. Payers using InterQual or MCG criteria have specific thresholds for what constitutes continued medical necessity at the PHP level, and reviewers check notes against those criteria directly.

Managing this well requires a billing and utilization review team that tracks auth expiration dates proactively, submits concurrent review requests before the window closes, and prepares clinical documentation packages that directly address the payer’s medical necessity criteria. Programs that manage auth reactively — submitting when they remember rather than tracking expiration dates — lose covered days regularly. Our PHP billing services include active authorization tracking and concurrent review support so programs don’t lose revenue to missed windows.

Payer-by-Payer Variations in PHP Coverage

Medicare covers PHP through different payment structures based on the type of facility providing care. Facility-based programs receive payment through the Hospital Outpatient Prospective Payment System (OPPS). Community mental health centers receive coverage through the Medicare CMHC benefit.

Medicare requires PHP programs to meet specific participation standards. These standards include minimum weekly service hours and multidisciplinary team requirements. Programs must meet these requirements to bill Medicare correctly for PHP services. Billing PHP without meeting Medicare requirements can create serious compliance concerns.

Medicaid coverage for PHP varies widely from state to state. Some states recognize PHP as a distinct level of care with its own reimbursement structure. Other states include PHP within broader outpatient behavioral health benefits and impose overall day limits. Some Medicaid programs do not recognize PHP as a separate benefit at all. In those states, providers may need to bill each covered service individually.

Providers must follow the requirements of the Medicaid program responsible for payment. They must also account for rules established by the managed care organization administering the benefit.

Commercial insurance introduces another layer of complexity. In-network and out-of-network status can significantly affect reimbursement rates. Prior authorization requirements also vary between insurers and individual plans. Plans may follow different concurrent review schedules, documentation requirements, and daily reimbursement structures.

These differences can exist even among plans offered by the same insurer. Programs with diverse commercial payer mixes need billing processes that account for each plan’s requirements. Applying the same billing rules across every commercial claim can increase denials, payment delays, and compliance risks.

What a PHP Billing Service Should Actually Handle

PHP billing services that’s worth the cost goes beyond claims submission. The programs that see the best collection rates are the ones whose billing partners are actively managing the authorization cycle, not just processing claims after the fact.

Concretely, that means payer-specific claims scrubbing that catches revenue code, HCPCS, and place-of-service mismatches before submission. An effective process starts with an authorization calendar that tracks every open PHP authorization by expiration date. The calendar should trigger concurrent review requests before coverage lapses. Denial management also requires payer-specific appeal letters rather than generic reconsideration requests. Tracking recurring denial reasons by payer helps teams identify problems and address their root causes earlier. Strong credentialing support completes the process by keeping the program enrolled with payers serving its patient population. And it means monthly reporting that shows collection rates, denial reasons, and days in A/R at the program level, not just in aggregate.

For a more detailed look at where PHP billing compliance tends to break down, see our post on PHP billing compliance pitfalls.

IOP vs. PHP Billing: Key Differences at a Glance

Working With a PHP Billing Partner

Capture RCM specializes in PHP and IOP billing for behavioral health and SUD treatment programs. We manage the full billing cycle — coding, claims submission, authorization tracking, concurrent review support, denial management, and credentialing — so programs aren’t carrying the administrative overhead of managing those functions internally while also running clinical operations.

If your program is seeing denial rates above 10%, authorization gaps, or A/R trends that don’t reflect your census, the problem is almost always in the billing workflow rather than the clinical program. Our PHP billing services include a billing review at onboarding that identifies exactly where revenue is being lost. Call us at (380) 383-6822 or schedule a consultation to get started.

Frequently Asked Questions

What is the difference between PHP and IOP billing?

PHP and IOP use different revenue codes, HCPCS codes, and authorization frameworks. PHP is billed primarily with H0035 and revenue code 0912 on a UB-04, with daily rate reimbursement under most payers. IOP uses H0015 and revenue code 0906, typically billed per session or per day at a lower rate. PHP requires more frequent concurrent review — usually every 5–7 days vs. every 7–14 days for IOP — and is held to stricter medical necessity documentation standards because of its higher intensity and cost.

What revenue code is used for PHP?

Revenue code 0912 (partial hospitalization) is the standard revenue code for PHP on UB-04 institutional claims. This is paired with HCPCS code H0035 for most payers. Some commercial payers require additional revenue codes to represent specific service components within the PHP day. The exact combination depends on the payer’s contract and coverage policy, which is why billing PHP claims without payer-specific scrubbing rules produces a predictable volume of avoidable denials.

How does prior authorization work for partial hospitalization programs?

PHP requires an admission authorization and then concurrent review at regular intervals — typically every 5–7 days — for the duration of the episode. Admission auth requires a clinical assessment, a qualifying diagnosis, and documentation that lower levels of care are not clinically appropriate. Concurrent review requires updated progress notes and treatment plan documentation that demonstrates continued medical necessity at the PHP level. Missing a concurrent review window results in a gap in authorization coverage, and the days between the expired auth and the approved extension become the program’s financial liability unless a successful appeal is filed.

Can PHP billing be done on a CMS-1500?

In most cases, no. Facility-based PHP programs bill on the UB-04. The CMS-1500 is used by professional providers billing PHP billing services without a facility license, and most payers limit full reimbursement to facility or CMHC billing entities. Using a CMS-1500 for a facility-based PHP program typically results in the claim being processed at professional outpatient rates rather than the PHP daily rate — which means the claim pays, just significantly underpaid, without generating an explicit denial that would flag the error.