Security controls
The access checks and review tools visible in the current product.
Access starts with identity
Clinical routes use the signed-in user's session and active organization. Role and permission checks determine which actions a person can take. A record ID or organization ID supplied by a browser is not, by itself, permission to view or change that record.
Private-file access has an additional check: the storage key's organization must match the viewer's active organization. Patient-scoped files have further checks for patient accounts.
Roles and accounts
Understand the account types and permissions used by clinical and administrative teams.
Organization boundaries
See how workspace context and private-file authorization work together.
Audit and review
The application records selected administrative and clinical actions in an audit collection. Its model prevents updates and deletes through normal application model operations. This is not the same as a cryptographically signed, externally immutable ledger, and this guide does not claim that every read or failed login is recorded.
Encryption, retention, backups, hosting region, incident response, and contractual safeguards depend on the deployed environment and approved agreements. Refer to the current security and compliance pages for the organization's published position.
Certification status
Do not treat design goals as certifications. The public security page lists SOC 2 Type II and ISO 27001 as roadmap items, not certifications already obtained. HIPAA applicability and any business associate agreement must be confirmed for the specific customer and deployment.