By level of care
Group-heavy days, per-diem billing, and a roster that becomes the claim.
Structured day programs run on attendance. When the sign-in sheet, the twelve notes, and the claim come from three systems, they disagree — and per-diem days get denied on the disagreement rather than on the care.
Built for group. Write the shared content once, individualise per participant.
What this level of care needs
6 things, and most platforms give you three.
The right-hand column is what an outpatient-built system typically offers for this level of care. It is not a criticism of those products — they were designed for a different job.
What it costs
A 22-person PHP/IOP program.
Support staff are not priced like clinicians. Admin and billing seats are $60, student interns are $25, and everyone counts toward the band that sets the clinical rate.
Illustrative. Your mix will differ, and metered add-ons — SMS, e-prescribing, eFax, the training library — are billed separately. Every rate above is published on the pricing page.
Where the day gets lost
A twelve-person group is twelve notes and twelve claim lines. Every place those three records can drift apart is a place a per-diem day quietly stops being billable.
The fastest way to test whether that describes your program is an hour with your own workflows rather than a feature list.
Questions
Common questions.
How does Unisona Health handle group-based PHP and IOP billing?
Attendance is the billing record: present, late or excused is timestamped per participant and drives the per-diem claim directly, so the sign-in sheet, the notes and the claim are the same record rather than three that disagree.
Do I have to write a separate group note for every participant?
No. You write the shared clinical content once and individualise each participant’s response, with the roster, shared content and individual responses on one screen. Similarity flagging catches twelve near-identical notes internally before a payer does.
Can it tell me whether a day meets per-diem minimums before I bill it?
Yes. Per-diem minimums are checked on the day, so whether the day qualifies is answered before the claim goes out, and continued-stay authorizations are surfaced before they expire rather than on a remittance.
The workflows that matter here
Where this level of care actually lives in the platform.
Clinical
Group notes & rosters
Group is where PHP and IOP programs spend most of their clinical hours and most of their documentation time — so the roster, the shared content, and each individual response live on one screen.
Read more →Operations
Scheduling & groups
Individual sessions, recurring groups, and full IOP tracks on one calendar — with authorization status, clinician credentials, and telehealth links attached to the appointment itself.
Read more →Revenue cycle
Prior authorization tracking
Dollars authorized, dollars used, visits remaining, and expiration date — live while the appointment is being scheduled.
Read more →Revenue cycle
Payer contracts & rates
Contracted rates stored per payer and per service, so the expected payment is on the claim before it goes out and underpayments are visible the moment the remittance posts.
Read more →Get started
Start today, or take a look first.
Create your workspace in minutes and try the whole platform free for 14 days — no credit card. Or book a one-hour walkthrough first.