HIPAA for AI agents
HIPAA audit trails must record (agent identity, human authorizer, operation, PHI records touched, policy context, tamper-evident timestamp). Ujex's AAT row carries all six in a single chained record.
Field mapping
| HIPAA audit attribute | Ujex field |
|---|---|
| Agent identity | payload.agentId (NHI) |
| Human authorizer | aat.parent_record_id → approval row's payload.actorId |
| Operation | payload.action + aat.action_type |
| PHI records | payload.target (record id) + meta (without raw PHI) |
| Policy context | aat.parent_record_id → policy_decision row |
| Tamper-evident timestamp | timestamp (unix ms) hashed into audit.{seq}.hash |
BAA considerations
- Cloud KMS for at-rest encryption of long-lived per-agent secrets.
- Firebase Auth + Cloud Functions are in scope under Google Cloud's BAA when configured properly.
- Inbox attachments and evidence files must live in a BAA-covered Cloud Storage bucket — see Inbox for storage config.
- Do not store raw PHI in
meta— store record IDs and pull on demand under an audited read.
Disclaimer
Ujex provides technical controls aligned with the HIPAA Security Rule (45 CFR §164.312(b) audit controls). A full HIPAA compliance program requires policy, BAAs with every sub-processor, incident response, and workforce training. This is engineering documentation, not legal advice.