Partial hospitalization programs (PHP) need EMR and billing software built for daily multi-service billing, frequent authorization review, and group-based documentation, not a generic medical EMR. Benji Health is purpose-built for these needs, giving behavioral health teams one platform for day treatment scheduling, documentation, billing, and census management.
Partial hospitalization program (PHP) vs. Intensive outpatient program (IOP): What's the difference?
PHP and IOP are both structured day treatment levels, but they differ in intensity, scheduling, and billing. Leaders deciding which service line to offer, or which level to recommend for a patient, usually start with hours per week.
Programs choose a level based on community need, payer contracts, and available clinical staffing, and they recommend a level based on symptom severity, safety, and support at home. The same operational questions shape IOP software and PHP EMR requirements.
| PHP | IOP | |
|---|---|---|
| Hours per week | 20 or more hours per week, typically across five to seven days | 9 to 19 hours per week, typically across three to five days |
| Typical session structure | Full-day programming with multiple group sessions, individual therapy, nursing oversight, medication management, and structured breaks | Shorter blocks of group therapy with individual check-ins, letting patients return home or attend work between sessions |
| Step-down/step-up relationship | Usually a step-down from inpatient or residential care, or a step-up from IOP when symptoms escalate | Usually a step-down from PHP as the patient stabilizes, or a step-up from weekly outpatient therapy |
| Best for | Patients who need structured daily care and medical oversight without 24-hour supervision | Patients who can maintain safety and daily routines at home while attending structured treatment several days a week |
Benji Health supports both levels in one platform, so PHP and IOP programs can document, bill, and track patients without switching systems.
Why PHP programs need specialized EMR software
The daily volume of multi-service activity does not fit a general medical EMR or a lightweight practice-management tool designed for weekly outpatient appointments. The daily rhythm spans several clinicians and service types, which multiplies the documentation and billing touchpoints a system must handle.
Daily multi-service billing means H-codes and institutional claims on a UB-04 or 837i form, formats that many ambulatory systems do not support natively. Concurrent authorization reviews arrive every seven to 14 days, so utilization review staff need a current view of authorizations, units used, and units remaining. Census changes daily as patients admit, step down, or discharge, and group-based documentation must be captured at volume without slowing clinicians down.
PHP EHR software should be evaluated against daily operational needs rather than weekly visit volume, and behavioral health level of care software should support the whole program, which is exactly how Benji Health was built.
Billing and authorization management for PHP
PHP billing and revenue cycle management work differently from standard outpatient billing. A single day can generate several billable services across different clinicians, and many programs bill a per-diem or multi-service model on institutional claim forms. Outpatient-only workflows do not map cleanly onto that reality. Per-diem structures reward programs for keeping documentation aligned to the exact services delivered, so revenue integrity and clinical documentation stay inseparable.
The right PHP billing software ties time-based documentation to the services being billed, so the note supports the claim before submission. Authorization tracking software behavioral health teams use should surface expiring authorizations and the documentation each re-review requires. Payer-specific rules, such as which services can be billed together or which codes a payer accepts, belong in the claim scrubber, not in a staff member’s memory.
Benji integrates directly with Hansei Solution’s robust RCM database, giving your team a platform for easy workflows and clean claims.
Group therapy documentation and census management
Group therapy is the backbone of PHP and generates documentation at volume. A group note must capture the session, while attendance tracking confirms who was present, who was billed, and who missed the session. Electronic medical records built for PHP let clinicians complete group notes quickly and attach the right attendance roster.
Benji keeps group notes, attendance, and utilization review in one connected record. Our EMR extends that connection to every service on the daily schedule, from nursing to medication management to individual therapy.
Step-down and step-up care: Connecting PHP to other levels of care
PHP rarely operates alone. Patients step down from residential treatment centers into PHP as they build independent daily-living skills, and they step down from PHP into IOP or outpatient care as they stabilize. The reverse also happens: a patient who struggles in IOP may step up to PHP for more structure and oversight.
Each transition carries risk when documentation, treatment plans, and authorizations do not follow the patient. A single record that spans levels of care preserves the clinical narrative and prevents duplicate work. Teams can see where the patient came from, their treatment plan, and what the next clinical step should be.
Benji Health connects residential, PHP, IOP, and outpatient documentation in one platform, so step-down and step-up decisions rest on complete records. The same record helps when a PHP graduate returns for a step-up, because the history is already in the chart. Continuity across transitions also keeps continued-stay reviews moving, since utilization review staff can pull the full treatment history without chasing paper.
Schedule a demo
See how Benji Health supports PHP documentation, billing, authorizations, and census management in one connected platform. Bring your current pain points around authorizations, group notes, or census, and our team will show how the platform addresses each one.
Frequently asked questions
A partial hospitalization program is a structured day treatment level of care that typically provides 20 or more hours of clinical programming each week, often across five to seven days, while the patient returns home each evening.
PHP operates at a density that general medical EMRs were not designed for: high-density scheduling, multi-service daily billing, frequent concurrent authorization reviews, and group-based documentation.
A system built for weekly individual visits cannot keep pace with a full day treatment schedule or the institutional claim formats PHP requires. Specialized tools match the level of care instead of forcing the program to adapt.
Look for group therapy management, recurring schedule templates, census dashboards, authorization tracking, ASAM/LOCUS-aware utilization review, and RCM or billing support for coding and per-diem structures.
A well-designed EMR keeps one continuous record across levels of care, so treatment plans, progress notes, medications, and authorizations follow the patient. When a patient steps down from residential into PHP or moves between PHP and IOP, the clinical team sees the full history without re-entering intake data. That continuity supports safer transitions and faster continued-stay reviews.