Skip to content
Now onboarding founding practices. Book a walkthrough →
Security & HIPAA

Built for HIPAA from the first line of code.

Protecting patient data isn’t a setting you turn on later. These rules are built into how CliniReady stores, shows and sends information, and they apply to every practice from day one.

Each practice walled off in the database

Every record belongs to one practice. The database itself enforces that, so one practice’s data can’t be read by another even if the application code has a bug.

Two-factor sign-in for every staff member

Staff sign in with an authenticator app. Roles and permissions are checked on our servers for every request, never taken on trust from the browser.

Screens that lock themselves

After 10 idle minutes by default (each practice picks 2 to 60), or at once with the Lock button. A personal PIN, checked on our servers, unlocks it, and five wrong tries end the session.

Encrypted in transit and at rest

Every connection uses HTTPS. Stored data and files are encrypted by Google Cloud, and secrets such as your clearinghouse key are sealed for your practice alone with Cloud KMS.

Every chart view logged

Each time someone opens patient data, we record who, what and when. Changes are captured in an append-only audit trail that can’t be edited.

Signed means signed

Signed notes can’t be changed; corrections are addenda. Clinical data is never hard-deleted; mistakes are marked “entered in error”.

Money you can audit

Amounts are stored as exact whole cents in an append-only ledger. Corrections are reversing entries, not edits.

Nothing private in a notification

Emails and texts never contain names, dates, times, amounts or visit details. They say what kind of notice it is and ask the patient to log in.

Card numbers never touch our servers

Cards are entered in your processor’s hosted form and saved in its vault. Line items sent to the processor are generic, like “Office visit”.

AI under BAAs

AI and speech services run under business associate agreements. Note drafts leave out names, birth dates, MRNs and contact details, and recordings are deleted at signing.

Help with your risk assessment

HIPAA asks every practice to assess its own risks. We’ll send our security details, these safeguards and our list of subprocessors for yours.

Hosted on Google Cloud

Patient data stays on Google Cloud: a private database with point-in-time recovery, and files behind short-lived links that are never public. Development and testing use synthetic patients only.

HIPAA’s Security Rule

The safeguards it asks for, and how CliniReady meets them.

These are the software’s part. Your practice’s part, such as training, policies and your risk assessment, stays with you, and we’ll help with the details.

Access control§164.312(a)

A unique sign-in for every staff member, roles checked on the server, automatic lock when idle, and encryption of stored data.

Audit controls§164.312(b)

Every read of patient data logged by the API; every change written to an append-only audit table by the database.

Integrity§164.312(c)

Signed notes are locked, clinical data is never hard-deleted, and money is kept in an append-only ledger.

Person or entity authentication§164.312(d)

Password plus an authenticator code for every staff sign-in; a server-checked PIN to unlock.

Transmission security§164.312(e)

HTTPS for every connection; nothing private in emails or texts; files shared only by short-lived links.

Contingency plan§164.308(a)(7)

A managed database with point-in-time recovery and backups on Google Cloud.

Business associate agreements

A BAA from day one, on infrastructure built for healthcare.

We sign a BAA with every practice before any real patient data goes into CliniReady. Every service we use that handles patient data is under a BAA with us. The rest, like card processing and patient notices, never receive clinical details.

Need our security details for your risk assessment? Ask us and we’ll send them.

BAA · Day one

Your BAA is signed before your first patient.

No upgrade tier, no paperwork chase. Every practice is covered from the start, and every vendor behind us that handles patient data signs one too.

Built on
Google Cloud
AWS

The same HIPAA-eligible infrastructure trusted by hospitals and health systems, sized for your practice.

AES-256
Encryption at rest
TLS
On every connection
US only
Data centers
Private
Network database
Cloud KMS
Sealed practice keys
Rewind
Point-in-time recovery

Enterprise-grade security, at small-practice prices.

See your practice’s day in CliniReady.

A 30-minute walkthrough on your kind of visits — in-office, video and async. We’re onboarding a small group of founding practices now.