Feature
Nothing leaves the building, every read is logged
You keep every page, recording, and message on a GPU you own. None of it goes to a cloud service to be read. And you can see every read of a record logged at the database, not just in the app, so the account of who saw what holds up beneath the UI as well as inside it.
What it does today
Read on your own hardware
You keep every page, recording, and message on a GPU you own, inside the building. Cloud services are never in the path, by design: nothing is sent off-site to be read.
Why PHI stays on-premA database-level audit floor
You can see who opened which chart-bound record, and when, because every PHI read is logged at the data, not just on a click in the web UI. The record sits beneath the app where it can’t be quietly stepped around.
How reads are loggedStays running
Active-active media keeps the trunk up: two FreeSWITCH instances behind a proxy, so a single box going down loses at most the call in flight while the next fax routes to the survivor.
How high availability worksNothing silently dropped
You see held, quarantined, and failed as states you can act on. A fax that can’t be delivered is surfaced for you to requeue, never a quiet loss no one finds until a patient asks.
Block a senderRelated
How a document gets read on your own hardware, and how that history stays findable later.