Built for HIPAA, with the work shown.
Every clinic signs our BAA before its first real patient, and every record anyone opens goes in the audit log.
The Security Rule, clause by clause.
Each technical safeguard of the HIPAA Security Rule, put plainly, and what Anatomia does about it.
§ 164.312(a)(1)
Access control
- The rule
- Allow access only to the people and software that have been granted it.
- Anatomia
- Five roles, each seeing what its work needs. Every query is scoped to your clinic, and another clinic's records answer as not found.
§ 164.312(a)(2)(i)
Unique user identification
- The rule
- Give each user a unique name or number to track them by.
- Anatomia
- Everyone is invited by email and signs in as themselves, so every line of the audit log names a person.
§ 164.312(a)(2)(ii)
Emergency access
- The rule
- Have a way to reach the records you need in an emergency.
- Anatomia
- A restricted record opens under emergency access, for a while and with a stated reason, and someone else reviews it afterwards.
§ 164.312(a)(2)(iii)
Automatic logoff
- The rule
- End a session after a set time of inactivity.
- Anatomia
- Idle sign-out after 15, 30 or 60 minutes, as your admin sets.
§ 164.312(a)(2)(iv)
Encryption and decryption
- The rule
- Have a way to encrypt and decrypt health information.
- Anatomia
- Built to encrypt the database, files and backups at rest, with keys in AWS KMS.
§ 164.312(b)
Audit controls
- The rule
- Record and examine activity in the systems that hold health information.
- Anatomia
- An append-only log of each record opened, search run and export made, with who and why. Your admins read it and export it in the Trust Center.
§ 164.312(c)(1)
Integrity
- The rule
- Protect health information from improper alteration or destruction.
- Anatomia
- The app never deletes a clinical record. Changing a priority takes a reason and goes on the case's timeline.
§ 164.312(d)
Person or entity authentication
- The rule
- Verify that whoever seeks access is the one claimed.
- Anatomia
- A second factor on every staff account, an authenticator app or a passkey. Five wrong passwords lock the account, longer each time.
§ 164.312(e)(1)
Transmission security
- The rule
- Guard health information sent over a network against unauthorized access.
- Anatomia
- TLS on every connection. In production the app refuses to start unless the database's certificate checks out.
Every record opened, with who and why.
- Opened the chart of Walter BrooksJordan Reyes, RN · treatment
- Searched patients by phone numberJordan Reyes, RN · treatment
- Read case 4821 and its triageDr. Amara Okafor · treatment
- Exported the triage note as a PDFJordan Reyes, RN · treatment
- Exported the audit log as CSVDana Whitfield, admin · operations
- Opened a restricted recordKim Alvarez, security officer · emergency access
Five roles, each seeing what its work needs.
| Feature | Front desk | Nurse | Doctor | Admin | Security officer |
|---|---|---|---|---|---|
| Logs calls | Included | Included | Included | Not included | Not included |
| Works the inbox | Requests only | Included | Included | Included | Not included |
| Opens charts and triage | Not included | Included | Included | Included | Emergency access |
| Signs off on a plan | Not included | Not included | Included | Not included | Not included |
| Opens a restricted record | Not included | Emergency access | Emergency access | Emergency access | Emergency access |
| Manages staff, hours and queues | Not included | Not included | Not included | Included | Not included |
| Opens the Trust Center | Not included | Not included | Not included | Included | Included |
| Reopens locked accounts and ends sessions | Not included | Not included | Not included | Included | Included |
HIPAA has no official certification.1 We sign a BAA with every clinic2 and show each safeguard's state in your Trust Center.
What security reviews ask.
Every clinic signs our business associate agreement before its first real patient. A vendor handles patient data only once its BAA with us is in place.
Anatomia is built to run in Amazon Web Services: the database on RDS, files on S3, email and texts through AWS. Patient data goes to no vendor without a signed BAA.
Triage and drafts run on Amazon Bedrock, inside AWS and under its BAA. Bedrock doesn't use what is sent to train models, and doesn't share it with Anthropic, the model's maker.
Admins see it in the Trust Center under Compliance: each safeguard, who owns it and where it stands, with the team's training records beside it.
Write to security@anatomia.health. A person reads every report and replies.
Send us your security questionnaire.
We answer it in writing and walk your security officer through the Trust Center.