Security & compliance
Live HIPAA safeguards check
Instead of a certificate, we show our work. Automated tests check our HIPAA safeguards against the live service, and the record below shows when everything else was last done.
12 of 21 safeguards in place
Live tests last ran Oct 23, 2026, 22:19 UTC.
Live tests
- PassingConnections are encrypted (HTTPS only)A plain http:// request is turned away to https://, and browsers are told to use HTTPS only.45 CFR 164.312(e)(1)
- PassingThe practice workspace requires sign-inA request for workspace data without a signed-in, two-step-verified session is refused, and nothing is cached.45 CFR 164.312(a)(1), 164.312(d)
- PassingNo trackers where practice or patient information is enteredThe workspace, sign-in, sign-up, Claim Check and contact pages load scripts only from our own site.HHS guidance on tracking technologies
- PassingSensitive fields are encrypted with a key held in a key vaultA test value is encrypted and decrypted with the live data key (AES-256-GCM); a tampered copy is rejected.45 CFR 164.312(a)(2)(iv)
- PassingThe database connection is encryptedThe live database session reports TLS in use.45 CFR 164.312(e)(2)(ii)
- PassingThe database is reachable only on a private networkThe database address resolves to a private network address, not the internet.45 CFR 164.312(e)(1)
- PassingThe audit log and claim history cannot be changed or deletedAn attempt to change and to delete audit and claim history records is made and must be refused by the database.45 CFR 164.312(b), 164.312(c)(1)
- PassingActivity is being recorded in the audit logA check entry is written to the audit log and read back.45 CFR 164.312(b)
- PassingAutomatic sign-out, two-step sign-in and lockout are in forceThe running service signs people out after 15 idle minutes, ends every session within 12 hours, and locks an account after 5 wrong tries.45 CFR 164.312(a)(2)(iii), 164.312(d)
Record
- In progressA named HIPAA Security OfficialNot yet in place.45 CFR 164.308(a)(2)
- In progressWritten risk analysis, reviewed yearlyNot yet in place.45 CFR 164.308(a)(1)(ii)(A)
- In progressWritten security policies adoptedNot yet in place.45 CFR 164.316
- In progressStaff security trainingNot yet in place.45 CFR 164.308(a)(5)
- In progressIncident response and breach notification planNot yet in place.45 CFR 164.308(a)(6)
- In progressYearly evaluation of these safeguardsNot yet in place.45 CFR 164.308(a)(8)
- PassingBusiness associate agreement with our hosting provider (Microsoft)Done Oct 4, 2026. Next due Oct 4, 2027.45 CFR 164.308(b), 164.314(a)
- In progressBusiness associate agreement with our claims clearinghouseNot yet in place.45 CFR 164.308(b), 164.314(a)
- PassingEncrypted backups kept 35 days in two US regionsDone Oct 23, 2026. Next due Jan 23, 2027.45 CFR 164.308(a)(7)(ii)(A)
- PassingRestore from backup testedDone Oct 5, 2026. Next due Jan 5, 2027.45 CFR 164.308(a)(7)(ii)(D)
- In progressAutomatic alerts on suspicious activityNot yet in place.45 CFR 164.308(a)(1)(ii)(D), 164.308(a)(6)
- In progressReview of who has accessNot yet in place.45 CFR 164.308(a)(4)
How to read this page
- Live tests run against the production service at most every 15 minutes, when someone views this page. Each one tries the safeguard rather than reading a setting: for example, it tries to change the audit log and checks that the database refuses.
- The record covers what software can't test, like written policies, training and signed agreements. Each shows the date it was last done and turns to "due" when it needs redoing.
- In progress means the safeguard isn't in place yet, or a test didn't pass on its last run. We don't publish technical details of anything not yet passing.
Why not a certificate? The government doesn't certify HIPAA compliance, and HHS doesn't recognize private certifications. HIPAA does require us to evaluate our own safeguards regularly. This page is that evaluation, kept live. Each practice also has its own HIPAA duties; see Security & compliance.