Patient data protection
A closer look at the safeguards behind your practice's data.
Back to frequently asked questions
Protecting patient information requires multiple layers of security. Hive combines encryption, organization-level data separation, authenticated access, and network protections to help safeguard the information your practice connects to the platform. These controls address different risks and work together across storage, application access, and data processing.
Encryption in transit
Hive's public application and API endpoints use HTTPS to encrypt information exchanged with the platform. Our public entry point requires TLS 1.2 or later and redirects HTTP requests to HTTPS. Encryption helps protect information from interception or modification as it travels between your device and Hive.
Connections to the primary database also require encrypted transport. These safeguards protect both the public connection to the application and connections to its primary data store.
Encryption at rest
Encryption at rest is enabled for Hive's primary database and organization-specific document storage. This adds protection for stored information at the underlying storage layer. Database backups also inherit the database's storage encryption.
Encryption complements access controls: an encrypted storage system still needs rules governing who can retrieve information through the application. Hive combines these protections rather than relying on encryption alone.
Separation between practices
Hive uses organization-specific document storage and logical separation for organization-owned records within shared platform services. Document storage is configured to block public access.
Organization-scoped application checks and data-access controls limit which practice's records a request can retrieve. Database access policies provide an additional layer of separation for protected records. These controls are designed to keep one organization's access from extending to another organization's information.
This is a multi-tenant architecture: practices share platform infrastructure while their information is separated through storage boundaries and logical access controls. It does not require a separate physical server for each practice.
Accounts, permissions, and integrations
Hive uses authenticated accounts and permission checks for access to application features. Access decisions take organization membership and the permissions required for the requested operation into account. Administrative functions have additional role checks.
API integrations use credentials associated with their configured organization and purpose. Agent API credentials can be restricted by permitted operation and capability, and remain subject to their associated user's permissions. Supported delegated connections let users authorize an integration through the connected service; stored authorization tokens for those connections are encrypted.
Firewall and network protection
A web application firewall inspects incoming requests and applies protections against common web attacks. Traffic controls also help limit abusive request patterns. These protections add a layer of defense before requests reach the application.
Network access controls restrict direct access to backend data services. The primary database is not publicly accessible. Application permissions and organization-level checks provide further protection within the platform.
Activity records and recovery
Hive records application and workflow activity to support troubleshooting and operational review. Recorded changes can include the responsible user or automated actor, helping teams understand how supported operations were performed. Access to detailed diagnostic information is subject to additional permissions.
Automated backups of the primary database support recovery from data loss. These safeguards complement the platform's preventive controls by providing a recovery path when information needs to be restored.
Privacy and security questions
For information about how Hive collects, uses, shares, and retains personal information, read our Privacy Policy. This page describes technical safeguards; the Privacy Policy addresses our handling of information.
Evaluating Hive for your organization? Contact our team to discuss your security requirements, intended integrations, and patient-data use cases.