Skip to content
Elite Mind EHR
ProductSecurityPricing

Security architecture

The clinical record has its own house.

Most EHRs put booking, billing and clinical data in one database and call it secure. Elite Mind EHR separates them at the architecture level — and can show you where each line is drawn.

Where a psychiatric record sits, and what is kept away from itBooking, identity and the patient app sit outside the clinical store. Nothing clinical is cached on a phone, and every read of a chart lands in an append-only trail.OUTSIDEPatient appiOS · Android · webno clinical data on the deviceBookingidentity · schedulingstate-matched, checked server-sideProvider consolethe chart, in the browserProvider’s own AI keyheld by the practice, not by usENCRYPTED CLINICAL BOUNDARYDEDICATED CLINICAL DATA SERVICEThe chartnotes · scales · safety plans · medications · planstenant 1 — row-level isolation, fail-closedtenant 2 — row-level isolation, fail-closedtenant 3 — row-level isolation, fail-closedField encryptionversioned keys, overencrypted storageAudit trailhash-chained, append-onlyThe safety pathscreener → deterministic scoring → crisis event → the provider’s bannerscreenerscoredcrisis eventbannerno model anywhere on this line

Booking, identity and the patient app sit outside the clinical store. Nothing clinical is cached on a phone, and every read of a chart lands in an append-only trail.

01

Separation

  • Booking, identity, and scheduling are separated from the clinical record by design.
02

Tenant isolation

  • Every clinic's data is isolated by tenant ID and enforced by PostgreSQL row-level security as a second line of defense, verified fail-closed.
03

Encryption

  • PHI fields are encrypted at the application layer with versioned keys on top of encrypted storage, and all traffic is TLS.
04

Audit trail

  • Every write and every patient-record read is logged to a hash-chained, append-only audit trail that is verified daily and never purged.
05

Sessions & identity

  • Sessions use asymmetric-signed tokens, 15-minute access windows, and single-use refresh tokens that are revoked as a family if replayed.
  • Authenticator-app MFA with backup codes is available for provider accounts.
06

Edge

  • All traffic passes through a CDN edge with a managed web application firewall, injection and bad-input rules, IP-reputation blocking, and rate limits on login endpoints.
07

Operations

  • Production is monitored with health and security alarms that page the operator, and deploys fail closed if code and database schema disagree.
  • Third-party webhooks are signature-verified before any processing, and secrets are held in a managed secrets store rather than in code.
08

AI

  • AI features run only on the provider's own API key, stored encrypted; the platform holds no AI keys and no clinical data is sent to an AI vendor without the provider's key and consent.
09

Program

  • Elite Mind EHR is built on a HIPAA-oriented architecture: minimum-necessary data handling, encrypted PHI, tamper-evident audit logs, and documented breach-response and disaster-recovery procedures.
  • The platform undergoes independent adversarial security reviews before safety-critical changes ship, with findings tracked to closure.

Security architecture

Walk through the architecture with the founder.

Bring the question you have not been able to get a straight answer to.

Request a demo