Partial hospitalization (PHP) is structured day treatment: roughly 20 or more clinical hours per week, typically five days a week, while the patient sleeps at home or in supported housing. In the ASAM Criteria it is Level 2.5 — one step below residential care, one step above intensive outpatient. Two things decide whether it is right. First, hours: if a person needs more than IOP can give but does not need 24-hour supervision, PHP is the fit. Second, and more decisive, where they sleep: PHP only works when the hours away from the programme are safe. A stable, substance-free living situation is not a nice-to-have — it is the clinical precondition. Note also that ASAM and Medicare do not define PHP the same way, and it is the payer's definition that governs what gets covered.
- PHP is ASAM Level 2.5 — commonly 20+ hours a week of clinical programming, five days a week, with the patient living off-site.
- The difference from IOP is intensity, not kind: IOP (Level 2.1) typically runs 9–19 hours a week. PHP is roughly double, with more medical and psychiatric involvement.
- Where you sleep decides more than the hour count. If the home environment is unsafe or actively using, PHP is the wrong level regardless of how well the hours fit.
- Medicare applies its own regulatory definition of PHP, including physician certification that the person would otherwise need inpatient care — clinical suitability and coverage eligibility are separate tests.
- PHP is usually a bridge, not a destination: most people step down into it from detox or residential, and step down out of it into IOP.
weekly clinical hours that define partial hospitalization
Source: ASAM Criteria
ASAM level of care assigned to PHP, between IOP (2.1) and residential (3.x)
Source: ASAM Criteria
typical weekly hours for intensive outpatient — the level PHP is confused with
Source: ASAM Criteria
PHP benefits are protected under federal mental health parity law
Source: U.S. DOL
What partial hospitalization actually is
Partial hospitalization is day treatment. A person attends a structured clinical programme for most of the working day, typically five days a week, and goes home at night. In the ASAM Criteria — the framework most clinicians and insurers use to match people to levels of care — it sits at Level 2.5, between intensive outpatient below and residential above.
The name causes most of the confusion. "Partial hospitalization" sounds like a partial hospital stay, which suggests beds and admission. There are no beds. The word "hospitalization" is a billing and regulatory inheritance, not a description of the experience. What you actually get is a full clinical day — group therapy, individual sessions, psychiatric review, medication management, family work — delivered in the same intensity a hospital programme would deliver, minus the overnight stay.
That distinction matters more than it sounds. Everything PHP does clinically, it does during daylight hours. Everything that happens at night — cravings at 2 a.m., a housemate drinking in the next room, the argument that used to trigger a relapse — happens without staff present. Which is precisely why the question of where a person sleeps turns out to be the deciding one.

The hour thresholds that define each level
Levels of care are separated by intensity, measured in structured clinical hours per week. The numbers below are the working thresholds in the ASAM framework. They are not arbitrary — they mark the points at which the amount of supervision and clinical contact changes what is realistically treatable.
The continuum by weekly clinical hours
| Level | ASAM | Structured hours/week | Where you sleep | What it can manage |
|---|---|---|---|---|
| Residential | 3.1–3.7 | 24-hour milieu | On site | Unsafe environment, needing separation from it; medical monitoring at 3.7 |
| Partial hospitalization | 2.5 | 20+ (often 20–30) | Home / supported | High clinical need with a safe environment to return to at night |
| Intensive outpatient | 2.1 | 9–19 | Home | Meaningful structure while keeping work or family commitments |
| Outpatient | 1 | Under 9 | Home | Maintenance, continuing therapy, relapse-prevention over time |
Hours are the visible difference. The invisible one is medical and psychiatric involvement, which is substantially higher in PHP than in IOP — a point that matters when there is a co-occurring psychiatric condition or active medication management.

PHP versus IOP: the comparison people actually search for
This is the single most common question about this level of care, and most answers reduce it to a number of hours. The hours are real, but they are the consequence of a clinical judgement, not the judgement itself.
Intensity
PHP runs roughly double the weekly hours of IOP — 20+ against 9–19. In practice that is a full clinical day versus three-to-four evening or morning sessions a week.
Medical involvement
PHP carries meaningfully more psychiatric and medical presence: regular prescriber contact, active medication management, closer monitoring of co-occurring conditions. IOP is more therapy-led.
Life compatibility
IOP is designed to fit around work, study, and childcare. PHP largely replaces the working day. This is the trade-off that decides it for many people — and the reason IOP is not simply "PHP-lite".
Typical position
PHP is usually a step down from detox or residential. IOP is usually a step down from PHP, or an entry point for someone whose needs never required day-long structure.
What decides between them
Not preference. Whether the person can hold stability with 9–19 hours of structure, or genuinely needs 20+ to stay safe — assessed across all six ASAM dimensions, not just severity of use.

The housing test — the thing that decides it
Here is the part that rarely appears in comparison tables, and it matters more than the hour count. PHP delegates the unsupervised hours to the environment. Sixteen hours of every day, and the whole weekend, are held not by clinicians but by wherever the person goes home to.
So the clinical question is not only "does this person need twenty hours of structure?" but "are the other hundred and forty-eight safe?" A person with a stable home, a supportive partner, and no substances in the house gets a genuine advantage from PHP over residential: they practise recovery in the actual environment they will live in, with staff available the next morning to work through what went wrong. That is real therapeutic value, not a compromise.
Reverse those conditions and the same programme becomes a liability. If the household is actively using, if housing is unstable, if the evenings are unsupervised in a way that has previously led straight back to use, then PHP is the wrong level however well the hours fit — and the honest recommendation is residential, or PHP combined with sober living. A programme that never asks in detail about your living situation before recommending PHP has skipped the most predictive question in the assessment.

Can I keep working while I do this?
Usually not full-time, and that is the honest answer. PHP typically occupies the working day — five days a week, four to six hours a day, plus travel. Some people arrange leave, some use FMLA protections, some shift to part-time. If keeping a full schedule is genuinely non-negotiable, the appropriate conversation is about intensive outpatient with evening tracks, not about squeezing PHP into evenings that do not exist. Pretending otherwise produces a programme people attend half of, which helps nobody.
Is this just a cheaper version of residential?
It is cheaper per week, but it is not residential minus the bed. Residential works partly because it removes the environment — the people, the routines, the access. PHP keeps you in that environment every evening and asks you to manage it with new skills you are still learning. For a person with stable housing and genuine support, that is an advantage: you practise recovery where you actually live. For someone whose home is where the using happens, it is not a saving. It is a setup for failure.
What if my insurer says PHP is not medically necessary?
That decision usually turns on documentation rather than on your clinical reality. Reviewers look for ASAM-based justification across all six dimensions, evidence of what has been tried, and a specific treatment plan with measurable goals. Medicare adds its own requirement — physician certification that without PHP the person would need inpatient care. A denial is appealable, and programmes experienced in concurrent review get it right more often at the first submission. Ask the admissions team directly how many hours a week they document, because a programme running eighteen hours will struggle to defend a twenty-hour benefit.
What a day in PHP actually looks like
Programmes vary, but the shape is consistent: a clinical day built around group work, with individual and medical contact threaded through it. The value is in the accumulation — the same people, the same structure, five days running, which is what makes patterns visible in a way weekly therapy cannot.
Morning check-in
Structured review of the previous evening and night — cravings, triggers, sleep, medication. This is where the unsupervised hours get processed, and it is the mechanism that makes off-site living clinically workable.
Process and skills groups
The core hours. Evidence-based modalities — CBT, DBT skills, relapse-prevention planning — delivered in a consistent group, which builds the peer accountability that solo therapy lacks.
Individual therapy
Weekly or more often, working the specific material — trauma, grief, the relationship or career pressure underneath the use — that group work surfaces but cannot address in depth.
Psychiatric and medical review
Regular prescriber contact for medication management, including medication for alcohol or opioid use disorder and treatment of co-occurring psychiatric conditions.
Family sessions
Because the person goes home each night, the household is part of the treatment rather than a distant consideration. This is a structural advantage PHP has over residential care.
Discharge planning from day one
The step-down to IOP or outpatient, and the recovery supports around it, should be under construction from the first week — not assembled in the final session.

Why Medicare defines PHP differently — and why that matters
This is where clinical suitability and coverage eligibility come apart, and it catches families out repeatedly.
The ASAM Criteria is a clinical framework. It places PHP at Level 2.5 and describes it by intensity and by patient need across six dimensions. Clinicians use it to answer: what does this person require?
Medicare operates a regulatory definition instead. Partial hospitalization is covered as a distinct benefit with its own conditions — including a requirement that a physician certify the person would otherwise require inpatient care, an individualised treatment plan, and a defined minimum of weekly programme hours. That is a narrower and differently-shaped test than "this is the clinically appropriate level".
The consequence is practical. A person can be clinically well-suited to PHP and still fail the coverage test, because the certification framing asks whether they would need hospitalisation without it — not whether PHP is simply the best fit. Commercial insurers apply their own medical-necessity criteria, often ASAM-derived but not identical. So the question to ask any programme is not just "do you take my insurance?" but "which criteria does my plan apply to PHP, and how do you document against them?"

The cost arithmetic nobody runs
PHP costs less per week than residential care, and that is how it is usually presented. The comparison is incomplete, because the two levels consume different resources.
Residential bundles everything: clinical hours, accommodation, meals, 24-hour staffing. PHP bills the clinical hours and leaves you to cover living costs — which you were covering anyway, so that genuinely is a saving. But PHP also consumes the working day for several weeks, and that cost lands on income and career rather than on the invoice. For someone salaried with leave available, the trade is favourable. For someone self-employed or hourly, five days a week away from work for a month can exceed the difference in programme fees.
Two further practicalities. Transport — five round trips a week for several weeks is a real cost, and a real barrier: attendance is the mechanism by which PHP works, and a programme ninety minutes away tends to produce gaps. Sober living — where PHP is clinically right but the home environment is not, supported housing alongside the programme is often the correct combination, and the two costs together should be compared against residential rather than against PHP alone.
Worked example — why the weekly price tells you almost nothing
| Programme A | Programme B | |
|---|---|---|
| Advertised weekly fee | Higher | Lower |
| Structured clinical hours/wk | 30 | 20 |
| Relative cost per clinical hour | Lower per hour | Higher per hour |
| Psychiatric contact | Twice weekly | On admission only |
| What you are actually buying | 50% more clinical contact | A smaller programme at a smaller price |
Both programmes may legitimately call themselves PHP — 20 hours is the threshold, not the standard. Ask three questions before comparing any two prices: how many structured clinical hours per week, how often you see a prescriber, and whether the fee includes psychiatric care and medication management or bills them separately. Divide the fee by the hours; the ranking often reverses.

PHP for co-occurring mental health conditions
Partial hospitalization did not originate in addiction treatment. It has been used for years in psychiatry — for depression, anxiety, bipolar disorder and eating disorders — and a large share of PHP programmes treat mental health conditions either alongside substance use or on their own. This matters practically, because roughly the same structure serves both, and the two so often travel together.
Where both are present, the important question is whether a programme treats them together or sequentially. Sequential treatment — get sober first, then address the depression — has a poor record, because for many people the substance use is doing work that the untreated condition created. Integrated treatment addresses both in the same programme, with one team.
Depression and anxiety
The most common co-occurring presentations. PHP's daily psychiatric contact allows medication to be started and adjusted quickly, which weekly outpatient care cannot match — useful when antidepressant response needs monitoring over weeks.
Bipolar disorder
Requires careful medication management and mood monitoring that benefits from frequent contact. Substance use commonly complicates mood stabilisation, which is an argument for integrated rather than sequential treatment.
Eating disorders
A major use of PHP outside addiction, typically with supervised meals built into the programme day. Where an eating disorder and substance use co-occur, seek a programme equipped for both — this combination is frequently mismanaged.
Trauma and PTSD
Trauma-focused work needs stability and a safe container. PHP can provide it, but trauma processing is generally paced deliberately — a programme promising intensive trauma work in week one warrants questions.
Why integrated beats sequential
One team, one treatment plan, both conditions addressed at once. Programmes that treat addiction and defer the psychiatric condition to "after" tend to produce a cycle of stabilise-relapse-stabilise.

Who PHP genuinely fits — and who it does not
Level of care is matched across all six ASAM dimensions, not by severity of use alone. Below is the shape of the judgement in plain terms.
Indicators for and against PHP
| Factor | Points toward PHP | Points elsewhere |
|---|---|---|
| Withdrawal risk | Resolved or minimal; detox already completed | Active or unstable withdrawal → withdrawal management first |
| Living situation | Stable, substance-free, supportive household | Unstable or actively using household → residential or PHP plus sober living |
| Psychiatric stability | Co-occurring conditions present but manageable in day treatment | Acute psychiatric instability or safety risk → higher level of care |
| Previous attempts | IOP or outpatient tried and not sufficient | Never tried structured care and low severity → IOP may be appropriate first |
| Daily commitments | Able to clear the working day for several weeks | Cannot step away from work or caregiving at all → IOP with evening tracks |
| Motivation and engagement | Willing to attend five days a week consistently | Attendance already erratic at lower intensity → address engagement or step up |
These are indicators, not a scoring system. The assessment belongs to a clinician who has taken a full history — including, specifically, a detailed picture of the home environment.

What comes after, and why it is decided early
PHP is rarely the whole treatment. It is the middle of a sequence: most people arrive from detox or residential care, and leave into intensive outpatient, then standard outpatient, with recovery supports running alongside throughout.
The step-down should be designed in the first week, not the last. There are two reasons. First, the drop in structure is significant — going from twenty-plus hours a week to nothing is the pattern under which relapse concentrates, and the tapered path through IOP exists precisely to prevent that cliff. Second, authorisation for the next level takes time to arrange, and a gap of even a fortnight between levels is a gap in which momentum is lost.
Alongside the clinical step-down, three things deserve explicit decisions rather than vague intentions: medication for alcohol or opioid use disorder, which should be settled during PHP rather than deferred; recovery supports in the community, which take weeks to become genuinely useful and therefore should start while the programme still provides a safety net; and the living situation, since whatever made the home environment workable during PHP needs to hold once the daily structure disappears.

This is general information, not medical advice
Clinical protocols, durations, and costs vary by individual history and by programme. Figures on this page are typical ranges and illustrative examples, not medical advice and not a quote. Withdrawal from some substances can be dangerous — decisions about level of care belong with a qualified clinician who has examined you. For free, confidential help finding treatment, call SAMHSA 1-800-662-HELP.
Partial Hospitalization (PHP) coverage, answered
What is a partial hospitalization program?
How many hours a week is PHP?
What is the difference between PHP and IOP?
Is partial hospitalization considered inpatient?
How long does PHP last?
Is PHP covered by insurance?
Can I work while in a partial hospitalization program?
What does a typical PHP day involve?
Do I need to live somewhere specific to do PHP?
Does Medicare cover partial hospitalization?
How much does partial hospitalization cost?
How much does PHP cost with insurance?
Are partial hospitalization programs effective?
What happens after PHP ends?
Is PHP used for mental health as well as addiction?
Explore the full continuum of care
Sources & references
- American Society of Addiction Medicine — The ASAM Criteria
- CMS — Medicare Benefit Policy Manual, Partial Hospitalization
- Medicare.gov — Mental health care (partial hospitalization)
- SAMHSA — National Helpline and treatment locator
- NIDA — Treatment and Recovery
- NIMH — Substance Use and Co-Occurring Mental Disorders
- U.S. Department of Labor — Mental Health Parity
- MedlinePlus — Substance use disorder treatment
- U.S. Department of Labor — FMLA leave for serious health conditions
Reviewed July 19, 2026 · Peninsula editorial standards. Partial Hospitalization (PHP)-specific facts cite Partial Hospitalization (PHP) plan documentation; regulatory facts cite U.S. federal sources.
Know your Partial Hospitalization (PHP) numbers first.
A twenty-five-minute call establishes your out-of-network residential benefit, deductible status, and whether a single-case agreement is worth pursuing — a written best, middle, and worst-case cost scenario for your specific plan.