Partial Hospitalization Program billing shares a lot of surface-level structure with IOP billing — both are per diem, both sit in the middle of the behavioral health continuum, both require physician oversight beyond what standard outpatient therapy needs. But PHP carries something IOP doesn’t: a genuinely fraught regulatory history, a stricter legal test for medical necessity, and a level of federal scrutiny that shapes how conservatively every legitimate PHP program needs to operate.
What is PHP Billing ?
PHP billing is the process of submitting and managing insurance claims for Partial Hospitalization Program services provided to patients requiring structured behavioral health or substance use disorder treatment. It involves accurate CPT coding, medical necessity documentation, authorization, eligibility verification, daily service records, and compliance with payer-specific requirements.
At House of Outsourcing, we provide specialized PHP billing services to help treatment providers manage complex billing requirements, reduce claim denials, and improve reimbursement. Our team supports claim submission, denial management, insurance verification, and A/R follow-up to maintain an efficient revenue cycle.
Why PHP Billing Demands More Rigor Than Other Levels of Care
- PHP has a stricter legal test than IOP: A physician must certify that the patient would require inpatient psychiatric hospitalization if PHP weren’t available, this is a substitute-for-inpatient-care standard, not simply a “needs more than outpatient” standard.
- The recertification cadence is tighter and has real teeth: Initial recertification is generally required by the 18th day of treatment, with ongoing recertification at regular intervals after that — missing this isn’t a paperwork lapse, it invalidates the claim.
- Each PHP day has a minimum service composition requirement: Medicare generally requires at least three distinct, documented services per day, one of which must be a psychotherapy service (not brief psychotherapy), or the day isn’t billable at all.
- The federal government has spent over a decade actively investigating PHP fraud, particularly at community mental health centers, and specific billing patterns are documented, published red flags that auditors actively look for.
- CMHC and hospital-based PHP follow the same underlying framework but have distinct certification and payment mechanics worth understanding separately.
Where PHP Billing Commonly Breaks Down
| PHP Billing Area | What Typically Goes Wrong | Impact |
| Physician certification | Certification doesn’t clearly state the patient would need inpatient care without PHP | Claim denied for failing to meet PHP’s specific coverage standard |
| Recertification timing | Initial or ongoing recertification missed or delayed | Claims for the affected period become non-billable, retroactively |
| Daily service minimum | Fewer than three distinct services documented for a billed day, or no psychotherapy service included | Entire day’s claim denied |
| Treatment plan quality | Generic, non-individualized treatment plan not signed by a physician | Claim vulnerable to denial and audit finding |
| Length of stay | Extended courses of PHP without clear evidence of ongoing acuity | Flagged as a documented OIG red flag for questionable billing |
| PHP vs. IOP confusion | Program bills PHP-level per diem without meeting PHP’s weekly hour or certification requirements | Payment recharacterized to a lower level of care, or denied outright |
PHP vs. IOP: A Stricter Standard, Not Just More Hours
It’s tempting to think of PHP as simply “IOP with more hours,” but the two differ in kind, not just degree.
| Factor | PHP | IOP |
| Weekly treatment hours | Generally 20 or more hours per week | Generally 9–19 hours per week |
| Certification standard | Physician must certify the patient would require inpatient hospitalization without PHP | Physician certifies the patient needs a minimum of 9 hours/week of therapeutic services — no inpatient-substitution standard required |
| Historical regulatory scrutiny | Extensive documented fraud history, particularly at CMHCs | A newer Medicare benefit (since January 2024) without the same enforcement history yet |
| Recertification cadence | Initial recertification by day 18, ongoing recertification at regular intervals | Recertification at least every other month |
| Daily minimum service composition | At least three distinct services per day, including a psychotherapy service | No equivalent hard daily minimum service-count requirement under Medicare’s IOP structure |
The Regulatory History That Shapes How PHP Gets Billed Today
Understanding why PHP billing is held to such a high documentation standard requires understanding what happened when it wasn’t.
In 2010, Medicare paid an estimated $218.6 million to 206 community mental health centers for PHP services delivered to roughly 25,000 beneficiaries. A subsequent OIG review found that approximately half of those CMHCs met or exceeded thresholds indicating unusually high billing across nine specific questionable billing characteristics — patterns significant enough that CMS moved to terminate Medicare provider agreements with a number of the centers involved. Separately, four CMHC owners and managers in Miami-Dade County, Florida were criminally convicted for fraudulently billing Medicare approximately $200 million for medically unnecessary PHP services between 2002 and 2010.
The nine questionable billing characteristics the OIG identified are worth knowing, because they still inform how PHP claims get scrutinized today:
- Beneficiaries receiving only group therapy throughout their PHP stay
- Beneficiaries not referred to the program by another treating facility
- Beneficiaries never evaluated by a physician during their PHP course
- Beneficiaries with no documented mental health diagnosis in the year prior to admission
- Beneficiaries traveling outside their community to attend a specific PHP program
- Beneficiaries participating in PHP at more than one CMHC
- Beneficiaries with cognitive disorders (where PHP-level psychotherapy may not be clinically appropriate) participating in the program
- Beneficiaries remaining in PHP for unusually extended periods (historically flagged around 147+ days)
- Beneficiaries readmitted to inpatient care during or shortly after a PHP course
Physician Certification and Recertification: The Requirement That Can’t Slip
This is the single most consequential compliance element in PHP billing, and it operates on a specific, non-negotiable timeline.
- Initial certification must establish that the patient’s condition is such that, without PHP, inpatient psychiatric hospitalization would be required — not simply that outpatient care alone is insufficient.
- The regulatory recertification interval for PHP has historically required initial recertification by the 18th day of treatment — this dates back to a standard originally used for inpatient psychiatric stays, applied to PHP because it’s conceptually structured as inpatient care’s outpatient substitute. Notably, when the Consolidated Appropriations Act, 2023 revised the underlying statutory language to say recertification should occur “not less frequently than monthly,” CMS specifically declined to change the 18-day regulatory requirement in its CY 2024 rulemaking, meaning the 18-day initial recertification standard remained in place. Given how specific and technical this requirement is, and how directly it affects claim validity, confirming the current applicable standard for each program’s specific circumstances is worth doing directly rather than relying on general guidance.
- Ongoing recertification continues at regular intervals throughout the course of treatment, not just once — a program that gets the initial certification right but lets subsequent recertifications lapse is just as exposed as one that never certified at all.
- The treatment plan itself must be physician-signed and needs to reflect individualized treatment goals, coordination of services, a multidisciplinary team approach, and either progress toward discharge readiness or a clearly documented ongoing need for PHP-level intensity to prevent relapse or hospitalization.
CMS Billing Mechanics: Condition Code, Revenue Codes, and the Daily Service Minimum
- Condition Code 41 identifies a claim as being for partial hospitalization services — hospitals and CAHs report this code to flag PHP claims specifically, distinct from standard outpatient billing or the newer IOP condition code.
- Revenue codes 0912 and 0913 distinguish PHP intensity levels — 0912 for less-intensive PHP days and 0913 for more-intensive PHP days, generally based on the number of distinct services furnished that day.
- Each PHP day generally must include a mental health diagnosis and at least three distinct, documented PHP-eligible services, at least one of which must be a psychotherapy service (excluding brief psychotherapy) — a day that doesn’t meet this three-service minimum is typically not billable as a PHP day at all.
- Hospital outpatient departments are required to report HCPCS codes for each individual service alongside the condition code, while CAHs generally aren’t required to do so in the same way.
- PHP services are billed as repetitive services on a monthly claim for a continuing course of treatment, rather than claim-by-claim for each individual day, per CMS’s claims processing guidance.
- PHP and IOP are mutually exclusive on the same date of service — a patient can’t be billed for both levels of care on the same day, since they represent different, non-overlapping intensity tiers.
CMHC vs. Hospital-Based PHP
Both hospital outpatient departments and Community Mental Health Centers can furnish and bill PHP services, but each operates under its own specific conditions:
- Hospital-based PHP is billed on bill type 13X, with condition code 41 and the applicable revenue codes, following the standard OPPS payment framework.
- CMHC-based PHP is billed on bill type 76X, following a similar overall structure but with CMHC-specific payment rates and participation conditions. To be authorized to provide PHP services, a CMHC generally must also offer a broader scope of services — outpatient care, 24-hour emergency access, and day treatment or psychosocial rehabilitation services — not PHP in isolation.
- CMHCs carry the heavier historical scrutiny of the two settings, given the enforcement history described above — this doesn’t mean hospital-based PHP is immune from review, but it does mean CMHC-based programs in particular should expect (and prepare documentation for) a higher level of payer and auditor attention.
Commercial and Medicaid PHP Billing
Outside Medicare’s specific condition code/revenue code structure, commercial payers and state Medicaid programs commonly use their own per diem HCPCS codes for PHP — such as S0201 (partial hospitalization services, per diem) — often paired with payer-specific revenue codes and prior authorization requirements. As with IOP, a practice billing across Medicare, commercial, and Medicaid populations needs to maintain distinct billing logic for each, since the underlying code sets and documentation expectations aren’t interchangeable.
Medical Necessity: The “Would Require Inpatient Hospitalization” Standard
This standard deserves its own clear explanation, because it’s easy to blur with general “high acuity” language:
- The documentation needs to support that, absent PHP-level treatment, this specific patient’s condition would necessitate inpatient psychiatric hospitalization — not simply that the patient is significantly symptomatic or would benefit from more intensive treatment than standard outpatient therapy.
- Supporting evidence typically includes acute symptom severity, safety concerns, functional impairment significant enough to threaten the patient’s ability to remain safely in the community without this level of structure, and often a recent hospitalization, emergency evaluation, or clear escalation in symptoms.
- As treatment progresses, ongoing documentation needs to continue supporting either that this standard remains met, or that the patient is making progress toward a level where PHP is no longer necessary — a treatment course that continues indefinitely without either clear improvement or clear ongoing acute risk is exactly the pattern that draws the kind of scrutiny described above.
ICD-10 Coding for PHP
Diagnosis coding follows standard mental health ICD-10-CM categories, but severity and acuity documentation carry particular weight here given PHP’s inpatient-substitution standard — a diagnosis alone doesn’t establish medical necessity; the record needs to reflect the acuity level that genuinely supports the “would otherwise require hospitalization” determination, consistent with the diagnosis coding principles described throughout behavioral health billing generally.
Documentation That Supports a PHP Claim
| Documentation Element | Why It Matters | Common Gap |
| Physician certification meeting the inpatient-substitution standard | The specific legal standard PHP coverage depends on | Certification language doesn’t clearly address the “would require hospitalization” test |
| Recertification on the required timeline | Missing this invalidates otherwise appropriate claims | Recertification lapses, particularly for longer courses of treatment |
| Individualized, physician-signed treatment plan | A documented enforcement focus area | Generic or templated plans not reflecting the specific patient’s goals and multidisciplinary care |
| Daily service composition (3+ services including psychotherapy) | Required for each billable day | Days documented with only group activities or insufficient service variety |
| Physician evaluation during the course of treatment | A red flag when absent, per OIG’s questionable billing criteria | Patient’s course managed entirely by non-physician staff without documented physician involvement |
| Discharge planning and progress documentation | Shows active treatment toward a defined endpoint | Extended courses without evidence of reassessment or progress |
PHP for Substance Use Disorder
PHP is available for substance use disorder treatment as well as primary mental health conditions, generally corresponding to ASAM Level 2.5 (partial hospitalization) within the broader SUD care continuum. The same certification, recertification, and daily service composition standards generally apply, layered onto SUD-specific clinical content — individual and group substance use counseling, medication management for co-occurring conditions, and, where applicable, coordination with medication-assisted treatment delivered through a separate OTP relationship.
Telehealth and PHP
PHP components can, in many circumstances, be delivered via telehealth consistent with broader Medicare behavioral health telehealth policy, though this is an area where payer-specific verification matters more than assumption:
- Individual therapy, group therapy, and other component services within a PHP day may be telehealth-eligible under current flexibilities, but the overall certification and daily service composition requirements still apply in full.
- Commercial and Medicaid coverage for telehealth-delivered PHP varies by payer and isn’t universally aligned with Medicare’s approach.
- Given the heightened compliance profile of PHP generally, documentation of exactly which components were delivered via telehealth versus in-person is worth being especially precise about.
Insurance Verification for PHP
| Verification Question | Why It Matters | Risk If Skipped |
| Does this payer require the same inpatient-substitution certification standard as Medicare? | Commercial payers may define PHP medical necessity somewhat differently | Certification language that satisfies one payer doesn’t satisfy another |
| What is this payer’s specific recertification cadence? | May not mirror Medicare’s 18-day/ongoing structure exactly | Recertification timed to the wrong schedule for this specific payer |
| Does the payer require prior authorization, and how often must it be renewed? | Common across most payers, often requiring frequent concurrent review | Treatment continues past an authorization window without renewal |
| Is telehealth-delivered PHP covered under this specific plan? | Coverage isn’t universal | Hybrid or virtual PHP components delivered without confirmed coverage |
| Does this payer use Medicare’s condition code/revenue code structure or its own per diem HCPCS codes (e.g., S0201)? | Determines the entire billing framework | Claims submitted under the wrong structure for this payer |
Why PHP Claims Get Denied & What to Check First
PHP claims can be denied due to insufficient medical necessity documentation, incorrect CPT or ICD-10 coding, missing prior authorization, incomplete daily treatment records, or payer-specific coverage restrictions. Reviewing patient eligibility, authorization details, clinical documentation, and billing requirements before submission helps reduce avoidable denials and reimbursement delays.
| Denial Reason | Likely Cause | Prevention |
| Certification standard not met | Documentation doesn’t clearly support the inpatient-substitution test | Ensure certification language explicitly addresses why inpatient hospitalization would otherwise be required |
| Recertification lapse | Initial or ongoing recertification missed or delayed | Track recertification deadlines against each payer’s specific required cadence |
| Daily service minimum not met | Fewer than three distinct services documented, or no qualifying psychotherapy service | Confirm and document the required service composition for every billed day |
| Extended length of stay without clear justification | Documentation doesn’t show continued acuity or active progress toward discharge | Periodic reassessment explicitly documenting ongoing necessity or progress |
| Insufficient physician involvement | Little to no documented physician evaluation during the course of treatment | Ensure and document regular physician involvement, not just initial certification |
| PHP/IOP same-day conflict | Both levels of care billed for the same patient on the same date | Confirm only one level of care is billed per date of service |
Credentialing for PHP Providers and Facilities
Credentialing for PHP providers and facilities involves verifying professional qualifications, maintaining accurate documentation, completing payer enrollment, and meeting facility-specific network requirements. Proper credentialing helps prevent claim denials, enrollment gaps, billing interruptions, and reimbursement delays.
| Credentialing Step | Responsible Party | Common Delay | Impact |
| Hospital outpatient department Medicare enrollment for PHP | Facility administration + credentialing team | Standard hospital-based enrollment timelines | Program can’t bill PHP until enrollment clears |
| CMHC certification and conditions of participation | Facility administration | CMHCs must demonstrate the broader required scope of services (outpatient care, 24-hour emergency access, day treatment) beyond PHP alone | Facility can’t be authorized to bill PHP without meeting the full CMHC service scope |
| Physician availability for certification and recertification | Program administration | Ensuring consistent physician availability on the required timeline | Certification lapses that jeopardize otherwise appropriate claims |
| Individual clinician credentialing | Credentialing team | Standard behavioral health credentialing timelines for therapists and counselors delivering program components | Component services questioned if delivering clinicians aren’t properly credentialed |
PHP Across Different Practice Settings
PHP billing requirements can vary across behavioral health centers, psychiatric facilities, hospitals, and substance use disorder treatment programs. Differences in payer policies, daily service documentation, medical necessity criteria, and coding requirements make a tailored billing workflow essential for accurate claims and consistent reimbursement.
| Practice Setting | Typical Billing Framework | Compliance Profile | Revenue-Cycle Focus |
| Hospital outpatient department | Medicare condition code 41/revenue code 0912-0913 structure; commercial per diem codes | Moderate-high — standard OPPS scrutiny applies | Maintaining certification and daily service documentation consistently |
| Community Mental Health Center | Same underlying framework, CMHC-specific rates and bill type | Highest — significant historical enforcement focus | Documentation specifically designed to counter known OIG red flags |
| SUD-focused PHP program | Same PHP framework applied to ASAM Level 2.5 SUD treatment | Moderate-high — same certification rigor as mental health PHP | Coordinating PHP billing with any concurrent MAT/OTP billing |
| Freestanding behavioral health facility (non-Medicare) | Commercial/Medicaid per diem HCPCS codes (e.g., S0201) | Moderate — payer-specific rather than Medicare-specific scrutiny | Payer-by-payer verification of certification and authorization requirements |
Is Your PHP Program’s Documentation Built to Withstand the Scrutiny This Level of Care Attracts?
PHP billing rewards programs that treat documentation rigor as inseparable from clinical quality not as an administrative afterthought layered on top of good care, but as the thing that makes good care defensible when a payer or auditor looks closely. Given PHP’s history, that scrutiny isn’t hypothetical.House of Outsourcing supports PHP programs across the full revenue cycle:
| Billing Challenge | What It Costs the Practice | How House of Outsourcing Helps |
| Eligibility and benefits verification | PHP delivered before confirming payer-specific certification and authorization requirements | Payer-specific verification, distinguishing Medicare’s structure from commercial/Medicaid frameworks |
| Physician certification and recertification tracking | Claims denied for missed or improperly timed certification | Certification and recertification cadence tracked against each payer’s specific required timeline |
| Daily service composition compliance | Days billed without meeting the required service minimum | Documentation review confirming each billed day meets composition requirements before submission |
| Treatment plan quality review | Generic or templated plans creating audit exposure | Review processes that catch individualization gaps consistent with known enforcement focus areas |
| Charge entry and claims submission | Condition code, revenue code, or bill type errors | Structured workflows built specifically around PHP’s distinct billing mechanics |
| Denial management | Certification and length-of-stay denials left unappealed | Targeted appeals grounded in documentation and coverage-criteria review |
| Credentialing and payer enrollment | Delayed billing due to CMHC conditions of participation or facility enrollment gaps | Credentialing tracked across facility certification, Medicare enrollment, and individual clinician credentials |
| Reporting and revenue-cycle analysis | No visibility into whether documentation patterns resemble known risk indicators | Reporting that proactively flags patterns consistent with historical OIG red flags before a payer does |
