Privacy Training: The privacy half of workforce training, which security training misses

If you have been asked for evidence of privacy training, the requirement behind the question is 45 CFR 164.530(b). What follows is what it says, what satisfies it, and where organizations usually come up short.

What the rule says

45 CFR 164.530(b) governs privacy training. The operative text is not reproduced here: read it at the source linked below, because the conditions in it are the requirement and a summary of a conditional rule is not a safe substitute for the rule.

The genetic information prohibition is narrower than a training item suggests: 45 CFR 164.502(a)(5)(i) bars a health plan (other than an issuer of certain long-term care policies) from using or disclosing PHI that is genetic information for underwriting purposes. Train a health plan's workforce on it; anywhere else it is general privacy practice.

What this looks like in practice

In an assessment, 45 CFR 164.530(b) is not one question. It resolves into several, and each one is really asking for different evidence. These are among the questions asked about it:

• Does the organization provide role-appropriate privacy training to all workforce members at onboarding and when privacy policies materially change?
• Does the organization's training include instruction on the definition of genetic information and the restrictions on its use, disclosure, and access?
• Does the organization periodically review its privacy policies and training, and communicate any updates?

Ownership usually sits with the privacy official, though the evidence is often produced by someone else, which is where the trail breaks. A control that works but has no owner tends to stop working the month the person who quietly maintained it changes roles.

Who this applies to

Covered entities. A business associate is bound directly by the provisions that name it (for example 45 CFR 164.502(a)(3), the minimum necessary standard at 164.502(b), and 164.410) and otherwise through its business associate agreement, so read the provision for whom it names. The Privacy Rule has no counterpart to the Security Rule's flexibility-of-approach clause (164.306(b)). Instead, 45 CFR 164.530(i)(1) requires policies and procedures reasonably designed for the size and type of your activities, and any deadline a provision sets applies at every size.

Building it, in order

The sequence below is the order that produces evidence as a by-product rather than as a separate documentation exercise:

1. Implement a privacy training program covering all workforce members, including employees, volunteers, trainees, and contractors under direct control.
2. Tailor content to roles and the information each role handles.
3. Deliver training at onboarding and refresh it when privacy policies materially change.
4. Track completion and retain training records.
5. Develop a training module covering the definition of genetic information and the prohibited uses.
6. Deliver it to personnel with access to information that may contain genetic data.

Evidence an assessor asks for

For this requirement the evidence types that satisfy it are record and report. The distinction matters more than it looks: a policy states what you intend to do, a procedure states how, and a record proves it happened on a date. Auditors ask for all three, and a practice that has written the first two often has nothing for the third.

Date every document and keep the superseded versions. Under 45 CFR 164.530(j)(2) the documentation 164.530(j)(1) requires is kept six years from the date of its creation or the date when it last was in effect, whichever is later. It is the same period the Security Rule sets at 164.316(b)(2)(i), under a different provision, so cite the one that governs the document you are holding.

Where this usually goes wrong

The usual gap is a control that exists in practice and nowhere in writing. Someone does the work, reliably, and it has never been written down, so the organization cannot demonstrate it and cannot notice when it stops. The fix is not more control, it is a dated record and a named owner.

What to do about it

• Produce the evidence, not the intention. For 45 CFR 164.530(b) that means dated records of each occurrence, not a description of the process and a dated report with the period it covers and who reviewed it. If the only evidence is that someone knows how this works, you have a practice and not a record.
• Put a name on it. Your privacy official should be recorded as the owner. A control with no owner stops working the month the person who quietly maintained it changes roles, and nobody notices.
• Set a review cadence and keep the evidence of each review. An annual date with a dated output is a common floor; what fails an assessment is a control implemented once and never re-checked against a changed environment.

If 45 CFR 164.530(b) is new to you, the useful first step is not a policy template. It is writing down what you already do, dating it, and naming an owner. That turns an undocumented practice into evidence, and it usually reveals the real gap.

Related requirements

• Privacy Official Designation: Naming a privacy official and a contact person
• Administrative Safeguards for Privacy: Safeguarding PHI in paper and conversation
• Accounting of Disclosures: The six-year accounting and its exclusions

References

• 45 CFR 164.530(b), in 45 CFR 164.530 on eCFR.
• This post describes what a requirement asks for and what evidence documents it. It is not legal advice, and your counsel owns the conclusion. State law may impose stricter obligations (45 CFR 160.203).