HomeSecurity overview
Documentation & trust

Security overview

Security controls for MedSyncAI Care Vault and its Epic integration.

Per-customer isolation

Each customer has its own environment, database and Epic registration. Customer healthcare data is stored and processed in the customer's own Microsoft Azure tenant. MedSyncAI's control plane manages identity, access and audit, and does not store patient records.

Encryption

Data is encrypted in transit using HTTPS/TLS and at rest. Archived records are additionally encrypted by the archive, with keys held in a key vault.

Authentication and access control

  • Role-based access, including the Archive Provider role.
  • Workspace-level authorization limits access to approved archives.
  • Epic clinicians must be explicitly linked to authorized MedSyncAI accounts.
  • Automatic session timeout after inactivity.
  • Server-side session revocation on sign-out.

Epic integration security

  • SMART on FHIR using the OAuth 2.0 authorization code flow with PKCE.
  • Epic tokens are kept server-side and are never sent to the browser.
  • Short-lived, one-time launch codes.
  • Strict patient matching requires an exact match on first name, last name and date of birth. No archived record opens when there is no exact match or more than one match.

See the Epic launch documentation for the full flow.

Audit logging

Sign-ins, patient searches and record access are logged for audit.

HIPAA-aligned design

MedSyncAI uses a HIPAA-aligned design with per-customer isolation, encryption, access controls and audit logging.

Responsible disclosure

Report a suspected security issue to hello@medsyncai.us.

Include the affected environment, time of observation and steps to reproduce without patient details, PHI, passwords, access tokens or other secrets. Use Support for service questions.