Access control
Every user has their own account. Sign-in is by email and password. Two-factor authentication is available per user under Security in your profile. When a user has enrolled, their session must satisfy that second factor before it can reach practice data. Enrolment is not a badge, it is enforced. Roles decide what a user can see. See Roles and permissions. Enforcement is in the database. Access is checked row by row when data is read or written, not by hiding menu items. A user who navigates directly to a page they should not have gets an empty page rather than a leak. Hidden navigation is a convenience; the data layer is the boundary.What is logged
Configuration changes and access to sensitive records go to the audit log, which is append-only. No one can edit or delete an entry, including admins. Every message sent to a patient is recorded in Settings → Notification Log. Every call is recorded, transcribed, and stored in Calls.What your practice is responsible for
Individual accounts
No shared logins. A shared account destroys the audit log’s usefulness and outlives the person who set it up.
Prompt offboarding
Remove access the day someone leaves.
Two-factor for admins
Admins can change integrations, routing, and billing. Enrol them.
Service accounts for integrations
Connect your PMS with an account created for VoxHealth, not a staff member’s personal login.
Access review
Review who has access, and at what role, on a schedule. The audit log is the record you review against.
Portal credentials
If you use portal automation, those are real payer credentials. Treat them accordingly.
Reporting a problem
Email support@voxhealth.ai. If you believe patient data has been exposed, say so in the first line so it is triaged as an incident rather than a support question.Related
- Patient privacy: how PHI is handled specifically
- Audit log