PHP, IOP, and Outpatient in Oregon: Levels of Care and What Each Requires

Outpatient, intensive outpatient, and partial hospitalization are frequently treated as interchangeable terms for varying intensity of service. They are not. Each level of care carries specific ASAM clinical criteria, OHA licensing requirements, staffing standards, service hour minimums, and documentation expectations that determine whether you can bill for what you deliver. Designing a program without understanding what each level actually requires operationally is where most startup and expansion mistakes happen.

Regulations change. Verify current requirements with the Oregon Health Authority, and have final implementation reviewed by legal, compliance, and clinical leadership.

How do ASAM levels of care map to OHA licensing in Oregon?

ASAM levels of care provide the clinical framework. OHA licensing determines what you are legally permitted to provide and bill. For outpatient SUD programs in Oregon, the primary governing rule is OAR 309-018. The level of care you are licensed for determines what services you can provide, what your staffing must look like, and what your documentation must demonstrate to support medical necessity for payer reimbursement.

What does outpatient (ASAM 1.0) actually require?

Standard outpatient is fewer than 9 clinical service hours per week. This level serves clients who can maintain stability with weekly or bi-weekly sessions and whose clinical severity does not warrant more intensive programming. In Oregon, outpatient SUD programs require an OHA Certificate of Approval under OAR 309-018. Staffing must include a clinical director meeting OAR credential requirements and licensed counselors for the services provided. Documentation must support the clinical rationale for the outpatient level of care at admission and at each service date. Outpatient services generally do not require prior authorization from most commercial payers or OHP, though this varies by plan and service type.

What does IOP (ASAM 2.1) actually require?

Intensive outpatient requires a minimum of 9 structured clinical service hours per week delivered across at least 3 days per week. The programming is predominantly group-based — group therapy, psychoeducation, skill-building sessions — with individual counseling provided as clinically indicated. IOP serves clients who need more support than weekly outpatient can provide but whose clinical severity does not require residential care or near-daily PHP-level contact.

Program design errors at IOP are common. The most frequent is scheduling 9 hours per week in a way that does not actually produce 9 hours of structured clinical contact — mixing clinical groups with administrative or recreational activities, or scheduling sessions that are routinely shortened. Payers conducting utilization review evaluate whether the program is actually delivering what IOP requires — 9+ hours of clinical services — not just what it is called. Documentation must support the IOP level of care medical necessity for each client on each authorization review cycle.

What does PHP (ASAM 2.5) actually require?

Partial hospitalization requires a minimum of 20 structured clinical service hours per week, typically provided 5 days per week for 4 to 6 hours per day. PHP serves clients who need near-daily clinical contact — because their symptoms require daily monitoring, their recovery environment is not supportive enough for less intensive programming, or they are stepping down from residential treatment — but who do not need the 24-hour structure of residential care.

PHP has the most demanding operational requirements of the outpatient levels. The staffing must support medical and psychiatric access given PHP client acuity — most PHP clients have active psychiatric or medical comorbidities that outpatient or IOP programming cannot adequately address. The programming must deliver 20 meaningful hours of structured clinical services weekly — this is operationally challenging to design and maintain. Prior authorization is required from most commercial payers and is often required for OHP at PHP intensity. Concurrent review documentation must demonstrate ongoing PHP-level medical necessity at each authorization review cycle, typically every 5 to 7 days for commercial payers.

How do you design a continuum from outpatient through PHP?

Programs that provide multiple levels of care — allowing clients to step up or step down based on clinical need — create the most clinically appropriate and financially stable programs. Designing a continuum requires:

• Separate OHA certification for each level of care you intend to provide and bill
• Policies and procedures that define the clinical criteria for each level and for transitions between levels
• Documentation workflows that produce ASAM-aligned records demonstrating medical necessity at each level for each client
• Authorization management that obtains new authorization when a client transitions between levels — a PHP client stepping down to IOP needs a new IOP authorization before the transition, not after
• Billing systems that can correctly code and submit claims for each level of care separately

The ASAM criteria framework, and how to build programs that genuinely operationalize it rather than just reference it, is covered in our article on ASAM criteria and level of care design.

How does OHP reimburse IOP and PHP in Oregon?

Oregon Health Plan reimburses outpatient SUD services through CCOs using HCPCS codes aligned with the service type and level of care. IOP and PHP SUD services are typically billed using H-codes (H0015 for intensive outpatient, for example). OHP fee schedule rates for these services are published by DMAP and are distinct from commercial payer rates. CCO prior authorization requirements for IOP and PHP vary by CCO — confirm requirements with each CCO before designing your authorization workflow. For a more detailed OHP billing overview, see our guide on Oregon Medicaid behavioral health billing.

Frequently asked questions

What is the difference between outpatient, IOP, and PHP?

Outpatient (ASAM 1.0): fewer than 9 hours/week. IOP (ASAM 2.1): 9+ hours/week across 3+ days. PHP (ASAM 2.5): 20+ hours/week, typically 5 days per week.

How many hours per week is IOP in Oregon?

ASAM 2.1 IOP requires a minimum of 9 structured clinical service hours per week across at least 3 days. Delivering fewer hours while billing IOP creates medical necessity and billing compliance risk.

What is PHP and how many hours per week is it?

Partial hospitalization (ASAM 2.5) requires a minimum of 20 structured clinical hours per week, typically 5 days per week for 4 to 6 hours per day.

Does OHA license IOP and PHP separately from outpatient?

OHA licenses by level of care. A program providing IOP and PHP must ensure its COA covers both levels and that its policies, staffing, and service structures meet the requirements for each.

What staffing does a PHP program require in Oregon?

PHP requires access to medical and psychiatric services, a credentialed clinical director, and licensed counselors to support 20+ hours of structured programming weekly. OAR 309-018 specifies current requirements.

How do Oregon payers reimburse PHP and IOP?

IOP and PHP SUD services are typically billed using HCPCS H-codes at OHP fee schedule rates. Commercial payer rates vary by contract. Authorization is typically required for PHP and sometimes for IOP.

Saint Health designs behavioral health programs across ASAM levels of care — from outpatient through residential — with the licensing, documentation, and revenue cycle infrastructure each level requires. Contact us or explore our operations and program development services.