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.
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.
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.
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.
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.
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.
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 notes can’t be changed; corrections are addenda. Clinical data is never hard-deleted; mistakes are marked “entered in error”.
Amounts are stored as exact whole cents in an append-only ledger. Corrections are reversing entries, not edits.
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.
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 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.
HIPAA asks every practice to assess its own risks. We’ll send our security details, these safeguards and our list of subprocessors for yours.
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.
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.
A unique sign-in for every staff member, roles checked on the server, automatic lock when idle, and encryption of stored data.
Every read of patient data logged by the API; every change written to an append-only audit table by the database.
Signed notes are locked, clinical data is never hard-deleted, and money is kept in an append-only ledger.
Password plus an authenticator code for every staff sign-in; a server-checked PIN to unlock.
HTTPS for every connection; nothing private in emails or texts; files shared only by short-lived links.
A managed database with point-in-time recovery and backups on Google Cloud.
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.
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.
The same HIPAA-eligible infrastructure trusted by hospitals and health systems, sized for your practice.
Enterprise-grade security, at small-practice prices.
A 30-minute walkthrough on your kind of visits — in-office, video and async. We’re onboarding a small group of founding practices now.