Match the software to the week you run
Withdrawal management, residential, PHP, IOP, medications for addiction treatment, co-occurring care, and adolescent substance use programs can differ in setting, staffing, service intensity, scheduling, and documentation. Use the guide for the services your organization actually operates.
What to know
Addiction treatment software should be evaluated against the programs an organization actually operates. Scheduling, documentation, medication workflows, service reviews, and billing configuration can differ across withdrawal management, residential treatment, partial hospitalization, intensive outpatient care, and other services. ASAM describes levels of care in terms of setting, staffing, service intensity, and other core elements, with reassessment informing whether a person continues or moves to a different intensity of care.
The program writes the week. The EMR has to hold it.
The key difference is not simply the program name. It is how each service is staffed and delivered. A withdrawal-management service may need workflows for frequent clinical observations and short episodes, while an IOP may rely more heavily on recurring groups, attendance changes, and repeated reviews. Residential, PHP, and medication services can introduce different schedules and documentation patterns. Co-occurring programs also need a way to address mental health conditions alongside substance use disorder; ASAM identifies that capability as an expectation in addiction treatment. For a hypothetical organization running residential care and IOP, the useful test is whether each program can have its own calendar, forms, permissions, and billing configuration without forcing staff to maintain a separate spreadsheet.
Our behavioral health EMR combines scheduling, individual and group appointments, configurable documentation, treatment plans, medication workflows, and patient information from intake through discharge. Start with the guide for the programs you operate, then identify the forms, handoffs, and payer workflows your team needs to support.
Where program types usually diverge
The calendar
Calendar needs depend on how services are delivered. An IOP with recurring groups may need editable rosters, attendance status, make-up sessions, and telehealth scheduling, while a residential or withdrawal-management program may organize work around coverage, observations, and transitions. Confirm how corrections affect documentation and downstream billing rather than assuming every calendar behaves the same way.
The notes
For group-heavy services, check whether staff can record shared session details while preserving an individual note in each participant’s chart. Programs centered on individual visits or medication services may need a different note cadence, review schedule, and set of required fields.
The bill
If reimbursement depends on attendance, documented time or units, or prior authorization, compare the schedule, clinical record, and claim before selecting a system. The relevant question is whether staff can identify and correct a mismatch under the organization’s actual payer rules.
Guides for withdrawal management, IOP, PHP, residential, medication, co-occurring, and adolescent substance use programs
One organization may use several of these services, but each can require a different schedule, documentation pattern, staffing model, and service intensity. Open the guide for the program you operate.
- Withdrawal management — consider how the system handles assessments, observations, orders when applicable, and planning for the next service.
- Intensive outpatient — examine recurring group schedules, individual documentation, attendance changes, telehealth when offered, and the units required by applicable payers.
- Medications for addiction treatment — examine medication records, orders, counseling documentation when provided, and how the configured workflow supports the services being delivered.
- Partial hospitalization — compare the daily schedule, group and individual documentation, attendance, service reviews, and payer-specific billing configuration.
- Residential treatment — consider round-the-clock staffing workflows, handoffs, recurring reviews, medication documentation when applicable, and discharge planning.
- Co-occurring substance use and mental health care — assess whether the record supports coordinated documentation for both sets of needs.
- Adolescent substance use programs — verify the consent, information-access, family-involvement, school-coordination, documentation, and payer rules that apply to the program, service, jurisdiction, and individual circumstances.
Frequently asked questions
Do I need different software for IOP than for residential?
Possibly. One system may support both programs if it can be configured for their different schedules, documentation, staffing workflows, permissions, medication processes, and billing requirements. The choice between one platform and separate systems depends on demonstrated fit, integrations, migration needs, and the organization’s operating model.
Can one EMR support withdrawal management, residential, PHP, IOP, medication, co-occurring, and adolescent substance use programs?
Some platforms are marketed for multiple addiction-treatment settings, but that does not establish fit for every program. Ask for evidence using representative workflows from the services you operate—for example, a recurring IOP group change, a residential handoff, or a medication order—and verify the resulting documentation, permissions, and billing data.
Can software choose the right level of care?
Software may help collect assessment information or produce decision support, but it should not be presented as replacing the qualified clinician’s assessment and level-of-care decision. The ASAM Criteria overview describes a clinician-centered framework for assessing needs and matching a person to a level of care. Verify the system’s role, configuration, and applicable clinical requirements.
Sources and current product pages
Sources reviewed September 9, 2026. Product capabilities, packaging, laws, and guidance can change; verify current details before purchase.
Explore Sunwave for your programs
Tell us which programs you run and where work crosses between them. If your organization offers residential treatment alongside PHP or IOP, we can focus the conversation on shared records, transitions, and the configuration each program needs.
This page provides general information about software and operational considerations. It is not legal, clinical, billing, accreditation, or compliance advice. Requirements and product capabilities vary by organization, payer, program, configuration, contract, and jurisdiction.