A policy acknowledgement attached to “the latest policy” is the same as no acknowledgement. Policy Acknowledgement ties each person’s attestation to the exact policy version in force at that time, with the per-person, per-version record §164 expects.
What it does
- Captures acknowledgement per policy version, with the hash of the file acknowledged.
- Triggers re-acknowledgement on material change, role change, and annual schedule.
- Produces the per-person history: policy, version, date, who requested, who completed.
- Flags workforce members whose acknowledgements are stale against the current version.
How it maps to HIPAA
The feature supports §164.530(a) (Privacy Officer) and §164.530(b) (training), §164.308(a)(1)(ii)(C) (sanction policy — predicated on acknowledgement), and §164.316 (documentation requirements) with the retention the rule specifies.
Where it fits
Policy Acknowledgement is a Workforce module capability, pulls content from Compliance Policies, and runs alongside Employee Training.