All addiction-treatment program guides
Software for the IOP week you already staff
An IOP EMR should support the recurring week as a connected workflow: scheduled groups, individual appointments, attendance changes, documentation, transitions, and the billing review that follows.
What to know
Evaluate IOP EMR software against the week your program actually runs: recurring groups, individual sessions, attendance, telehealth when offered, transitions between levels of care, and the documented services used in billing review. The important question is not whether these features appear on a checklist, but how information moves between them and what happens when staff correct a record.
What an IOP week actually requires
An IOP creates a recurring set of linked events rather than a single outpatient encounter. Participants may attend several group and individual sessions during a week, enter or leave the program at different times, and join remotely when the program offers telehealth. Scheduling, documentation, attendance, and billing review therefore need to preserve what happened at each encounter and for each participant.
Hours, group mix, staffing, telehealth, payer, and licensing rules vary by program and jurisdiction. Configure the system against the week you staff and the contracts you bill—not a generic outpatient demo.
The work an IOP EMR has to hold
Recurring schedules and attendance
Test whether one recurring series can represent the actual group cadence and retain participant-level attendance. For example, in a hypothetical Monday-Wednesday-Friday group, mark one participant absent Monday and another late Wednesday, then check what changes on the roster, chart, reports, and billing work queue.
Group and individual notes
Group documentation has two layers: facts shared across the session and details specific to each participant. Review which information can be recorded once, which fields populate individual records, and how clinicians can correct one participant’s note without changing the others.
Telehealth in the same week
For remote sessions, treat identity verification, consent, privacy and security, recordkeeping, clinician licensure, and payer conditions as diligence questions rather than universal requirements. Privacy, legal, billing, and clinical reviewers should identify what applies in each jurisdiction and delivery model; the product review should then show where the applicable information is captured, updated, and retrieved.
Step-downs and step-ups
Transitions require more than changing a program label. For substance-use programs using The ASAM Criteria, ASAM describes reassessment and transition criteria for deciding whether a person continues at the current level or moves to a more or less intensive level. Evaluate whether the EMR preserves permitted history, current documentation, authorizations, and open tasks across the operational transition, subject to the organization’s access and disclosure rules.
Units that match attendance
Follow a correction through the full workflow. In a hypothetical case, change a three-hour attendance record to two hours and determine whether the documentation, authorization tracking, charge, claim status, and audit history update consistently—or require separate reconciliation.
The reports leaders already run
Leaders may review census, attendance, incomplete documentation, authorizations, and billing exceptions for different purposes. Check each report’s source fields, refresh timing, filters, correction behavior, and export format rather than assuming that similarly named reports reconcile automatically.
How Sunwave supports an IOP
An IOP week brings together group schedules, attendance, individual documentation, and billing. Our EMR includes individual and group scheduling; our telehealth tools support remote sessions and patient engagement; and our revenue-cycle tools cover the financial work. To plan your setup, map a typical week and its exceptions: late arrivals, attendance corrections, note updates, transitions, and claim edits. That map helps define the configuration and any required interfaces.
Frequently asked questions
What software does an IOP actually need?
An IOP generally needs support for recurring group and individual schedules, participant-level attendance, group and individual documentation, transitions, authorization tracking, billing review, and telehealth when offered. Evaluate these as connected workflows, not isolated features, and define requirements for the program’s population, payers, licenses, contracts, and jurisdictions.
Does Sunwave include telehealth for IOP?
Yes. Our telehealth tools support individual and group sessions, electronic forms and consents, reminders, and documentation linked to patient records. Discuss your session sizes, access needs, and program requirements with our team to confirm the appropriate configuration and what is included in your proposal.
Does every IOP use the same schedule or documentation rules?
Not necessarily. Schedule, service-intensity, documentation, telehealth, authorization, and billing requirements can depend on the population, payer contract, license, program design, and jurisdiction. Build evaluation scenarios from the week the organization actually staffs and bills.
Sources and current product pages
- ASAM — The ASAM Criteria
- Sunwave — Behavioral Health EMR
- Sunwave — Telehealth & Patient Engagement
- Sunwave — Revenue Cycle Management
Sources reviewed September 9, 2026. Product capabilities, packaging, laws, and guidance can change; verify current details before purchase.
Plan your IOP week with Sunwave
Use a real, de-identified IOP week in the demonstration: create the recurring schedule, record attendance and participant notes, correct an absence or duration, make a level-of-care transition, and trace the resulting billing and reporting records. Document any separate modules, integrations, manual steps, and exports revealed by the test.
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.