Built for HIPAA compliance.BAAs available.
These are the controls in the product today, each with a plain description of what it does. For a BAA or a security questionnaire, talk to us.
Sign-in
Accounts that can see patient data across a brand need more than a password.
-
Mandatory MFA for admins
Platform admins and partner admins must add a passkey or an authenticator app. Until they do, every page except setup and sign-out sends them to enroll.
-
Passkeys (WebAuthn)
Use Face ID, Touch ID, Windows Hello or a hardware key as your second factor. Phishing-resistant, with no code to retype.
-
Recovery codes
Issued once when the first second factor is added, and shown only once. Regenerating them retires the old set.
-
Lockouts and rate limits
After five failed sign-in attempts, further tries are blocked. Magic-link emails and invalid API keys are rate limited per address too.
Sessions
You can see where you are signed in, and end it from anywhere.
-
Active-session management
Your profile lists each signed-in device with its IP address, browser and last activity. Sign out one device, or every device but this one.
-
Session IDs stay server-side
Raw session IDs never leave the session service. The page that lists your devices only ever sees an opaque handle.
Patient data
Who saw a record, who changed it and why are written down, and you can read it.
-
PHI access logging
Staff and API views of patient data are recorded in a dedicated PHI access log, separate from the general audit log.
-
Audit trail for partners
Partner admins can filter the audit trail by date, record type, action and person, and export it and the access report to CSV.
-
Encounter edit guard
Treatment changes run under a lock on the encounter. A refused change is rolled back completely, so nothing half-saved is left behind.
-
Status change log
Every encounter status change is recorded with the old and new status, who made it, why and when. Partners can read the history through the API.
Integrations
Your systems talk to ours over authenticated, verifiable, retry-safe calls.
-
API keys, stored hashed
Every API call carries your key in the X-API-Key header. Keys are compared against a hash, and an IP is blocked after repeated invalid keys.
-
Idempotency keys
Send an Idempotency-Key on create calls and a retried request returns the original response instead of creating a duplicate patient or encounter.
-
HMAC-signed webhooks
Each webhook carries a timestamp and an HMAC-SHA256 signature made with your webhook secret, so you can confirm it came from us and was not altered.
Need a BAA? Ask for one.
BAAs are available to partner brands. Ask for one when you talk to us, and send your security questionnaire along with it.
- BAAs availableFor partner brands, on request.
- Security questionnairesSend yours and we’ll go through it with you.
- Your audit dataPHI access and audit reports export to CSV from the portal.
Launch with the controls in place.
Tell us what you sell and where. We'll cover the BAA, the controls on this page and how your team will use them.