You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This document maps each TransTrack function and component to the applicable HIPAA regulatory requirements, documenting the current implementation status.
Regulatory Reference
HIPAA Security Rule: 45 CFR Part 164, Subpart C
HIPAA Privacy Rule: 45 CFR Part 164, Subpart E
FDA 21 CFR Part 11: Electronic Records and Signatures
No AATB conformance is claimed; see COMPLIANCE.md for why
that claim was withdrawn.
Function-Level Compliance
Function
HIPAA Rule
Requirement
Implementation
Status
calculatePriority.ts
164.312(b)
Audit Controls
HIPAA audit log with WHO/WHAT/WHEN/WHY, SHA-256 hash for immutability
✅
calculatePriority.ts
164.312(a)(1)
Access Control
User authentication required, UUID validation
✅
calculatePriority.ts
164.312(c)(1)
Integrity Controls
Input validation for MELD/LAS/PRA scores against medical ranges
✅
calculatePriority.ts
164.312(d)
Person Authentication
api.auth.me() validates user identity
✅
matchDonor.ts
164.312(b)
Audit Controls
HIPAA audit log with access justification tracking
✅
matchDonor.ts
164.308(a)(1)(i)
Security Management
Input validation, HLA format checking, blood type verification
✅
matchDonor.ts
164.312(e)(1)
Transmission Security
Patient names sanitized in notifications, no PHI in error messages
✅
matchDonor.ts
164.312(c)(1)
Integrity Controls
Race condition mitigation via patient freshness check