Integrity¶
Last 1 Enterprises LLC / LastVet Safeguard category: Technical HIPAA Security Rule citation: 45 CFR §164.312(c)(1) Status: Scaffold (Bucket 1c). Not approved for enforcement until Ryan review.
Document metadata¶
| Field | Value |
|---|---|
| Policy owner | TODO (Ryan) |
| Version | 0.1-scaffold |
| Effective date | TODO (Ryan) |
| Review cadence | Annual (TODO: Ryan confirm) |
| Approver | TODO (Ryan) |
| Last reviewed | 2026-08-26 (scaffold only) |
1. Purpose¶
Protect ePHI from improper alteration or destruction.
2. Scope¶
Database records, imaging objects, consent state, audit logs.
3. Policy statements¶
- Mechanisms shall verify ePHI is not improperly altered or destroyed.
- Database migrations on production shall follow controlled one-off task policy (no auto-migrate).
- Imaging objects shall use envelope encryption with wrapped DEKs stored in Postgres.
- Application shall use transactions and integrity checks appropriate to clinical and consent data.
4. Roles and responsibilities¶
| Role | Responsibility |
|---|---|
| Security Officer (Ryan) | TODO (Ryan): assign formal Security Rule responsible person per §164.308(a)(2) |
| Workforce members | TODO (Ryan): acknowledge policy when hired / annually |
| Contractors / BAs | TODO (Ryan): flow-down via BAA and agreements |
5. LastVet-specific context (from existing docs)¶
SECURITY_POSTURE_DATABASE_ACCESS.md: production migration discipline; ensureCoreSchema gated off prod. Imaging envelope v1 implemented. Consent tables integrity relies on app layer until RLS batch 2.
6. Related documents¶
../HIPAA_ARCHITECTURE.md— asset inventory and data flows (Bucket 1a)../HIPAA_RISK_ANALYSIS.md— risk register (Bucket 1b)../../security/POSTURE.md— canonical security posture
7. Ryan TODO (substantive content deferred)¶
- Checksum or versioning policy for critical documents if not already enforced.
- Integrity monitoring for MinIO objects.