For hospital IT, compliance and clinical leadership
Platform architecture
Zunoa is the operational continuity layer around the patient journey. It coordinates the workflow: video stays with your telehealth platform, messaging stays with your carrier, and documentation stays in your system of record.
01
System architecture overview
Component and ownership boundaries across the patient layer, the Zunoa controlled zone, vendor services, and the hospital zone.
02
End-to-end workflow
Core Tele-MSE, Retain engagement while the patient waits, and Recover follow-up after an early departure.
03
Patient journey swimlane
Operational ownership across the patient, the Zunoa platform, the provider, and hospital staff.
04
Encounter state machine
Every patient is a session with a current status, timestamped transitions, user actions, message events, and manual clinical overrides.
05
Security, PHI and compliance boundary
The guardrails that govern what Zunoa stores, what it sends, and what always routes to a clinician.
No PHI in QR codes
Station URLs identify site, station, location and provider queue only.
SMS is limited purpose
Status prompts, return-to-desk, call-back and safety language. No diagnoses or lab values.
Urgent results escalate to a call
Detailed or urgent clinical results route to provider review, never to routine text.
EHR integration deferred
Manual or lightweight operational input first, interfaces after proof.
Auditability
Consent, timestamps, status transitions, message events and follow-up disposition are tracked.
Bring your IT and compliance teams to the table
We will walk your architecture, security and clinical leaders through the integration surface, data flows, and pilot scope.