Clinical
A session, a note, and a claim — from one link.
Video that starts from the appointment already on the schedule, opens the right note type, and produces a claim with the correct place-of-service and modifier when the session ends.
Included, not per-seat. No separate video subscription for you to manage.
One session, end to end
From the reminder text to the submitted claim.
The appointment already knows who the patient is, which note type applies, and what the payer expects to see. Video is a step in that sequence rather than a separate product bolted to the side of it.
Text and email with the join link, 24 hours and 1 hour ahead.
T−24hBrowser only. No download, no account, no waiting-room phone call.
10:02Chart and video side by side. Start, end, and participants logged.
51 minThe note type for that appointment opens automatically.
Same dayPlace of service and telehealth modifier applied from the encounter.
NightlyWhere telehealth claims die
The clinical part is easy. The coding is what gets denied.
Telehealth rejections are almost never about the care. They are about place of service, modifiers, consent documentation, and the originating-site rules that vary by payer and by state.
Set from the encounter type, not typed by a biller reading a schedule after the fact.
95, GT, and payer-specific modifiers applied by rule, per payer.
Telehealth consent captured once and attached to every session that needs it.
Attendance
Hybrid IOP exists because the drive is the barrier.
Programs running some groups remotely see fewer no-shows, and a no-show is an unbillable hour a clinician already blocked. The scheduling and the video being the same system is what makes the hybrid track manageable.
Privacy and security
The session is part of the record, and protected like it.
Telehealth runs inside the same platform, under the same agreement, as the chart it opens. The video vendor is on our published subprocessor list, and substance use records keep their 42 CFR Part 2 consent controls on a video visit.
Video runs on Twilio Programmable Video, a HIPAA-eligible service, under a signed business associate agreement between Unisona Health and Twilio.
Session audio and video are encrypted in transit.
[Sessions are not recorded / Recordings are stored encrypted in the United States with access logged – confirm which]
Patients join in the browser through a unique link that expires. Room names and participant identities use internal IDs, never patient names.
Reminder texts and emails contain no clinical details and do not name the program’s substance use treatment services. [confirm the actual reminder wording]
Telehealth sessions, notes, and consent records are covered by the same business associate agreement as the rest of the platform, and 42 CFR Part 2 consent controls apply to them.
Questions
Common questions.
Do I need a separate video subscription?
No. Video is included, not per-seat, and starts from the appointment already on the schedule — the appointment knows who the patient is, which note type applies and what the payer expects, so there is no separate video subscription for you to manage. The video itself runs on Twilio Programmable Video, which is listed with our other subprocessors.
Do patients need to download anything to join?
No. Patients join from the browser with a link sent by text and email 24 hours and 1 hour ahead — no download, no account, no waiting-room phone call.
How do telehealth claims get the coding right?
Telehealth rejections are almost never about the care — they are about place of service, modifiers and consent. Place of service (02) is set from the encounter type, modifiers (95, GT, payer-specific) are applied by rule per payer, and telehealth consent is captured once and attached to every session that needs it.
Is telehealth HIPAA and 42 CFR Part 2 compliant?
Telehealth is covered by the same business associate agreement as the rest of the platform. Video runs on Twilio Programmable Video, a HIPAA-eligible service, under a signed BAA between Unisona Health and Twilio, and session media is encrypted in transit. Patients join through a unique, expiring link, and rooms and participants are identified by internal IDs, never patient names. Reminders contain no clinical details. Session notes and consent records sit in the same record as everything else, so 42 CFR Part 2 consent controls apply to them. [Sessions are not recorded / Recordings are stored encrypted in the United States with access logged – confirm which] The platform provides these safeguards; compliance also depends on how your organization configures and uses them.
Works with
It runs on the same record as the rest of the platform.
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.
Coming soonClinical
Charting & forms
Most systems give you their note types and wish you luck.
Read more →Revenue cycle
Claim scrubbing
Validation runs before the claim leaves, highlights the exact field that will get it kicked back, and says why in plain language — not a rejection code you have to look up.
Coming soonGet 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.