You've built a partial hospitalization program. Your clinicians are delivering excellent care. But when you submit claims, they bounce back denied, underpaid, or flagged for audit. The problem isn't your clinical model. It's that how to bill for PHP CPT codes requires more than knowing which code to use. It requires pairing the right code with airtight documentation that proves medical necessity to payers who scrutinize PHP claims harder than almost any other behavioral health service.
Most PHP billing guides stop at listing codes. This one goes deeper: code by code, we'll show you exactly what documentation must back up each claim, which payer-specific quirks trigger automatic denials, and the five billing errors that cause RAC audits and recoupments.
Understanding PHP Billing Codes: S9484, H0035, and Payer-Specific Variations
The most widely used code for partial hospitalization program billing is S9484, which represents crisis intervention mental health services per diem. Most commercial payers accept S9484 for PHP, but it's not universal. Some payers require H0035 (mental health partial hospitalization treatment, less than 24 hours), while Medicare and some Medicaid programs use different HCPCS codes entirely.
CMS guidance specifies that hospitals and community mental health centers must report revenue codes alongside HCPCS codes for PHP services. For Medicare, you'll often see G0176 used for activity therapy as part of PHP. The critical mistake: submitting S9484 to a payer that only recognizes H0035, or vice versa. This triggers an immediate denial because the payer's system doesn't map that code to a PHP benefit.
Before you bill a single claim, verify which PHP billing codes behavioral health payers in your market accept. Call the provider relations line for each major payer and document their PHP code requirements in your billing manual. For substance use disorder partial hospitalization, some payers require H0015 (alcohol or drug services, partial hospitalization, per diem) instead of S9484. According to Ensora Health, using the correct HCPCS or CPT code is essential for billing correctly, and mixing up mental health vs. SUD codes is a common error.
What 'Partial Hospitalization' Means to a Payer vs. What It Means Clinically
Clinically, you know PHP sits between inpatient and intensive outpatient. But payers define PHP by hours and structure, not by clinical judgment. To qualify as PHP under most payer contracts, a program must provide at least 20 hours of structured programming per week, typically across five or six days. If your program delivers 18 hours, payers will deny the claim and tell you to bill it as IOP instead.
The 20-hour threshold isn't arbitrary. It's tied to Medicare's definition of PHP, which most commercial payers have adopted. CMS requires that PHP services be provided under an individualized treatment plan and that recertification of the need for at least 20 hours per week must occur monthly. If your census fluctuates and patients drop below 20 hours in a week, you can't bill that week as PHP.
This creates a documentation burden: you need to track and document actual hours attended each week, not just scheduled hours. If a patient attends Monday through Thursday but misses Friday, and their total falls to 18 hours, that week should be billed as IOP. Billing it as PHP anyway is considered upcoding and will surface in a post-payment audit.
Daily Documentation Requirements That Support PHP Medical Necessity
Every PHP claim you submit must be backed by a daily treatment note that justifies why the patient needed PHP-level care that day. Payers audit PHP claims frequently because the per diem rate is high, and they're looking for any sign that the patient could have been treated at a lower level of care. A compliant daily note must include specific elements that prove medical necessity.
First, document the patient's current symptom severity using objective language. "Patient was anxious" doesn't cut it. "Patient reported suicidal ideation with a plan but no intent; PHQ-9 score 21; required two safety checks during group" does. Second, document the patient's response to interventions that day. What groups did they attend? How did they participate? Did symptoms escalate or de-escalate? Third, and most important, include a clinical justification for why PHP is still necessary instead of IOP or outpatient therapy.
That last element is what most programs miss. Payers want to see language like: "Patient continues to require PHP-level monitoring due to persistent suicidal ideation and inability to maintain safety in a less structured setting. Attempted step-down to IOP last week resulted in acute decompensation." Without this explicit justification, the claim looks like you're billing PHP out of habit, not medical necessity. This is a common trigger for retro-denials during audits.
If your program also provides crisis intervention services, make sure those are documented and billed separately when appropriate, rather than bundled into the PHP per diem.
Treatment Plan Requirements for PHP: What Payers Expect
PHP treatment plans aren't static documents. Payers expect them to be living, updated records that reflect the patient's current clinical status and justify continued PHP-level care. CPT codes partial hospitalization program claims will be denied if the treatment plan doesn't meet specific requirements, even if your daily notes are perfect.
First, treatment plans must be updated at least every seven days for most commercial payers, and weekly updates are the industry standard. Some Medicaid programs allow 14-day intervals, but weekly is safer. Each update should document progress toward goals, any changes in symptoms or functioning, and a reassessment of whether PHP is still the appropriate level of care. The update must be signed by a licensed practitioner (physician, NP, PA, or licensed therapist, depending on your state scope of practice rules).
Second, the problem list must align with your ICD-10 diagnosis codes. If you're billing with F32.2 (major depressive disorder, severe episode) but the treatment plan only addresses anxiety, that's a red flag in an audit. According to TriWest billing guidance, PHP claims must include the correct ICD mental health diagnosis code (F01-F99), and incomplete information may result in denial or return for correction.
Third, goals and objectives must be specific, measurable, and tied to PHP-level intensity. "Patient will reduce depression" is too vague. "Patient will report PHQ-9 score below 15 and demonstrate ability to use three coping skills independently before step-down to IOP" is what payers want to see. The goals should make it clear why 20+ hours per week of structured care is necessary.
How Prior Authorization Works for PHP: Timelines and Concurrent Review
Most commercial payers require prior authorization before you can bill for PHP services. The authorization process varies by payer, but typical initial auth lengths are 7 to 14 days for commercial plans. Medicaid programs often grant longer initial auths, sometimes 30 days, but this varies by state. If you start treating a patient without an active auth, you won't get paid, period.
The authorization request must include a clinical assessment that documents acute symptoms, recent destabilization (hospitalization, suicide attempt, severe functional impairment), and why lower levels of care are insufficient. Many payers use third-party utilization review vendors (Carelon, Optum, Magellan) who apply proprietary criteria. Know which criteria set your payers use (ASAM, InterQual, MCG) and structure your auth requests to hit the specific data points those tools require.
Once you have an initial auth, you'll need concurrent review calls or submissions to extend it. These typically happen every 7 to 14 days. The concurrent review must demonstrate continued medical necessity: what progress has the patient made, what barriers remain, and why they still need PHP instead of stepping down. If you miss a concurrent review deadline, the auth lapses, and any services you provided after the lapse won't be reimbursed.
Pro tip: Schedule concurrent reviews two days before the auth expires, not on the last day. This gives you buffer time if the reviewer needs additional documentation. For programs that also offer group health behavior assessments, make sure those are documented separately and not assumed to be covered under the PHP per diem.
PHP Documentation Requirements Insurance Companies Scrutinize Most
Payers audit PHP claims more aggressively than most outpatient services because the reimbursement is high and the potential for upcoding is significant. PHP documentation requirements insurance auditors focus on fall into three categories: proof of hours, proof of medical necessity, and proof of individualized treatment.
For proof of hours, you need a daily attendance log that shows exactly what time the patient arrived, what groups or sessions they attended, and what time they left. A roster that just says "present" isn't enough. If an auditor requests records and you can't prove the patient was there for the hours you billed, you'll have to repay the claim plus potential penalties.
For proof of medical necessity, auditors look at your daily notes and treatment plans to see if the clinical picture supports PHP-level care. They're specifically looking for whether the patient could have been treated at IOP or outpatient. If your notes are repetitive, lack symptom severity details, or don't explain why PHP is necessary, the auditor will deem the claim not medically necessary and demand repayment.
For proof of individualized treatment, auditors want to see that each patient received a unique treatment plan and interventions tailored to their needs, not a cookie-cutter program. If all your treatment plans look identical or your daily notes use template language without customization, that's a red flag. Document what makes each patient's treatment unique.
Starting January 1, 2024, CMS requires condition code 41 on all PHP claims from hospitals and community mental health centers, signaling that the program meets the 20-hour-per-week threshold and has been recertified monthly. Failing to include this code will result in claim denial.
The Top 5 PHP Billing Errors That Trigger RAC Audits and Recoupments
1. Upcoding Hours or Billing Days the Patient Didn't Attend
This is the most common PHP billing error and the easiest for auditors to catch. If you bill a full PHP day but the patient only attended half the scheduled hours, or if you bill for a day the patient was absent, that's fraud. Always bill based on actual attendance, not scheduled attendance. If a patient leaves early due to a medical appointment or personal emergency, document it and adjust the billing accordingly.
2. Missing or Inadequate Daily Notes
Every day you bill must have a corresponding daily note. If an auditor requests records and you're missing even one note, you'll have to repay that day's claim. Worse, missing notes cast doubt on all your other claims and may trigger a broader audit. Daily notes must also contain the medical necessity language described earlier. Template notes that say "patient attended groups and participated appropriately" without specifics will be denied on appeal.
3. Inadequate Medical Necessity Language
Even if you have daily notes, if they don't explain why the patient needed PHP instead of a lower level of care, the claim is vulnerable. Payers are looking for language that ties the patient's symptoms and functioning to the intensity of PHP. If your notes could describe an IOP patient just as easily, the auditor will downcode the claim or deny it entirely.
4. Billing PHP and Individual Therapy on the Same Day
Most payers consider individual therapy to be included in the PHP per diem rate. If you bill both a PHP day (S9484 or H0035) and an individual therapy session (90834, 90837) on the same date of service, the individual therapy claim will be denied as a duplicate or bundled service. The exception: some payers allow separate billing for psychiatric medication management (99213, 99214) on the same day as PHP, but you must verify this with each payer. For programs offering behavioral health integration services, clarify whether those can be billed alongside PHP.
5. Roster vs. Individual Billing Errors
Some payers accept roster billing for PHP (one claim listing multiple patients), while others require individual claims for each patient each day. Submitting a roster to a payer that requires individual claims, or vice versa, will result in rejection. Additionally, roster billing requires meticulous attention to detail: one error in a patient identifier or date of service can cause the entire roster to reject. Most billing experts recommend individual claims for PHP to reduce error risk, even if roster billing is allowed.
Partial Hospitalization Program Billing Guide: Putting It All Together
Successful PHP billing requires a system, not just knowledge of codes. Start with a pre-billing checklist that your billing staff completes before submitting each claim. The checklist should verify: correct payer-specific code, active prior authorization, 20+ hours of attendance that week, daily note for each date of service, treatment plan updated within the last seven days, and proper revenue codes if required.
Build a denial tracking system that categorizes every PHP denial by reason code. If you're seeing patterns (multiple denials for "not medically necessary" or "missing documentation"), that tells you where your clinical or billing process needs tightening. Most PHP denials are preventable if you catch the documentation gap before the claim goes out.
Train your clinical staff on billing requirements. Therapists and counselors often don't realize that their daily notes are legal documents that directly determine whether the program gets paid. A 15-minute training on what makes a daily note "audit-proof" can prevent thousands of dollars in denials. If your program also provides group health behavior interventions, ensure clinicians understand how those differ from standard PHP group therapy for billing purposes.
Finally, conduct internal audits quarterly. Pull a random sample of 10 to 20 PHP claims, review the supporting documentation as if you were a payer auditor, and score each claim for compliance. If you find gaps, fix them before a payer does. Internal audits also prepare your team for the real thing and reduce anxiety when a RAC audit letter arrives.
S9484 PHP Billing Code and Revenue Code Requirements
The S9484 PHP billing code is a per diem code, meaning it covers all services provided during a PHP day, including group therapy, individual check-ins, medication monitoring (in most cases), and activity therapy. You bill one unit of S9484 per day, regardless of how many hours the patient attended, as long as they met the minimum threshold (usually four hours to count as a PHP day).
When billing S9484 or other PHP codes to Medicare or Medicaid, you must also include the appropriate revenue code. For hospital-based PHP, the revenue code is typically 0912 (psychiatric partial hospitalization, less than 24 hours). For community mental health center PHP, the revenue code is 0513. Submitting a claim without the correct revenue code, or with a mismatched revenue code and procedure code, will result in denial.
Some payers also require a place of service code. PHP is typically billed with place of service 52 (psychiatric facility, partial hospitalization). Using place of service 11 (office) or 22 (outpatient hospital) will cause the claim to reject because it doesn't match the PHP benefit.
How to Get Paid for PHP Mental Health: Contracting and Rate Negotiation
Even if you bill perfectly, you won't get paid fairly if your contracts are weak. How to get paid for PHP mental health services starts with negotiating per diem rates that reflect the true cost of delivering 20+ hours of care per week. Many behavioral health programs accept the payer's initial rate offer without negotiation, leaving significant revenue on the table.
Research what other PHP programs in your market are getting paid. Per diem rates for PHP typically range from $300 to $600, depending on geography, payer mix, and whether your program is hospital-based or freestanding. If a payer offers you $250 per day, that's likely below cost, and you should negotiate or consider whether contracting with that payer makes financial sense.
In your contract, clarify what services are included in the per diem and what can be billed separately. Most payers bundle group therapy, case management, and nursing into the PHP rate, but some allow separate billing for psychiatric evaluations, medication management, or lab work. Get this in writing. Ambiguity leads to denials.
Also negotiate authorization timelines in your contract. Push for 30-day initial auths instead of 7-day, and try to get language that allows for retrospective auth in true emergencies. The more time you spend on auth calls, the less time you have for patient care and the higher your administrative costs.
Frequently Asked Questions About PHP Billing
What CPT code is used for partial hospitalization?
The most common codes are S9484 (crisis intervention mental health services, per diem) for commercial payers, and H0035 (mental health partial hospitalization treatment, less than 24 hours) for Medicaid and some other payers. Medicare may use G0176 for activity therapy as part of PHP. Always verify which code your specific payer requires, as using the wrong code will result in automatic denial.
How many hours per day qualifies as PHP?
Most payers require at least 20 hours per week of structured programming to qualify as PHP, typically spread across five or six days. This usually translates to four to six hours per day. If a patient attends fewer than 20 hours in a week, the services should be billed as intensive outpatient (IOP) instead of PHP. Document actual attendance hours daily to support your billing.
Can you bill individual therapy and PHP on the same day?
Generally, no. Most payers consider individual therapy to be bundled into the PHP per diem rate, so billing both S9484 (or H0035) and a therapy code like 90834 on the same date of service will result in the therapy claim being denied as a duplicate. Some payers allow separate billing for psychiatric medication management visits, but verify this with each payer before billing both services on the same day.
How often does a PHP treatment plan need to be updated?
PHP treatment plans must be updated at least every seven days for most commercial payers. Some Medicaid programs allow updates every 14 days, but weekly is the industry standard and the safest approach. Each update must document progress toward goals, current symptom status, and justification for continued PHP-level care. The update must be signed by a licensed practitioner.
What documentation do I need for PHP authorization?
For prior authorization, you need a comprehensive clinical assessment that includes current diagnosis (with ICD-10 codes), recent psychiatric history (hospitalizations, suicide attempts, medication changes), current symptom severity (using standardized scales like PHQ-9 or GAD-7), functional impairment, and a clear explanation of why lower levels of care (IOP, outpatient) are insufficient. Many payers also require a proposed treatment plan and estimated length of stay.
What is condition code 41 for PHP billing?
Condition code 41 indicates that a hospital or community mental health center is billing for PHP services that meet the 20-hour-per-week minimum and have been recertified at least monthly. As of January 1, 2024, CMS requires condition code 41 on all Medicare PHP claims. Failing to include this code will result in claim denial. Many commercial payers have adopted the same requirement.
Streamline Your PHP Billing and Get Paid Faster
PHP billing is complex, but it doesn't have to be a constant source of denials and revenue leakage. When you pair the right codes with airtight documentation and build systems to catch errors before claims go out, you protect your revenue and reduce audit risk.
If your program is struggling with PHP denials, authorization delays, or audit risk, you don't have to figure it out alone. ForwardCare specializes in behavioral health revenue cycle management, helping treatment centers optimize billing, reduce denials, and get paid faster. Our team understands the nuances of PHP billing because we've worked these claims and appeals firsthand.
Ready to clean up your PHP billing and protect your revenue? Visit ForwardCare to learn how we help behavioral health programs get paid what they've earned.
