Primary region
Security
Primary region · Council Bluffs, Iowa
Security built into the chart.
EMRDesk encrypts most chart content, like notes, history, and vitals, before saving it, on top of encryption in transit and at rest. Passkeys, session timeouts, sign-in checks, and activity logs protect access around it.
Exact controls can vary by deployment, integrations, and customer configuration.
How a chart stays protected
From sign-in to saved chart.
- 01
Sign in
Passkeys or a password. Staff can add an authenticator app, and sign-ins from unsupported countries or known VPN or Tor networks are asked for an emailed code.
- 02
Access check
In the app, chart records open only for signed-in members of the practice that owns them, and for patients viewing their own record in the portal.
- 03
Encrypt
Most chart content is encrypted by EMRDesk's servers before it's stored, on top of encryption in transit and at rest.
- 04
Log
Edits to core chart sections, file uploads, and sign-ins are recorded in activity logs your practice can review.
Safeguards
Controls built into the EMR.
Passkeys
Staff can sign in without a password, which reduces phishing risk.
Authenticator codes
Staff can add authenticator-app codes, with one-time recovery codes.
Session timeouts
Practices set idle and maximum session timeouts and can sign out every session at once.
Sign-in checks
The sign-in screen asks for an emailed code when a sign-in comes from an unsupported country or a known VPN or Tor network.
Practice scoping
Chart records are scoped to each practice's account. Staff get individual logins, with roles and clinic assignments that shape what they see in the app.
Separate patient portal
Patients use a separate portal sign-in scoped to their own record, not the clinic workspace.
Protected file storage
Uploads stay in access-controlled storage for your practice's account, with file-type and size limits.
Admin audit log
The Admin Console keeps a read-only log of organization setup, accepted invites, and member sign-in access changes.
Hosting
Where EMRDesk runs.
Primary U.S. application services run in Google Cloud's us-central1 region in Council Bluffs, Iowa.
Encrypted in transit and at rest
Traffic to EMRDesk is encrypted with TLS, and stored data is encrypted at rest by Google Cloud.
Paperwork and support
Security questions? We'll answer them.
Business Associate Agreement
U.S. practice owners e-sign EMRDesk's Business Associate Agreement during onboarding.
TermsSecurity details
Ask the support team for security documentation, or start free and review the controls in your own account.