Each practice’s data is walled off from every other practice’s, and the controls in place today are listed on our Security page. If something isn’t listed there, ask us rather than assume.
- Your practice only. Every database query runs inside your practice’s scope, enforced by Postgres row-level security under an application role that cannot bypass it.
- Encryption. TLS 1.2 or higher on every external connection. Everything is encrypted at rest, and patient documents, the database and backups use AWS KMS keys.
- Sign-in. Multi-factor authentication with an authenticator app or a passkey, and access tokens that expire after 15 minutes.
- Access. Role-based permissions scoped to your practice. Only a provider can sign an encounter or send a prescription. Access to patient records is logged with the user, action, record, IP address and time.
- Backups. Continuous backups with 90 days of point-in-time recovery. The database runs as three copies, a primary and two replicas, in separate availability zones.
- Uploads. Files are checked by type and scanned with ClamAV.
Found a vulnerability? Email security@notivehealth.com.
Learn more: Security
Questions? Ask in How do I… or email support@notivehealth.com.