Serious Threat to Health or Safety: The narrow safety exception

45 CFR 164.512(j) covers serious threat to health or safety. In most assessments the control itself is present and the record proving it is not, which is why this requirement produces findings at organizations that are, in practice, doing the work.

What the rule says

45 CFR 164.512(j) governs serious threat to health or safety. 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.

What this looks like in practice

In an assessment, 45 CFR 164.512(j) 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:

• When disclosing PHI to avert a serious and imminent threat under §164.512(j), does the organization limit the disclosure to a person reasonably able to prevent or lessen the threat, and does it apply the good-faith presumption correctly?

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. Give clinical and front-line staff a short written standard covering both limbs of the test, with the emphasis on the second, the recipient must be someone reasonably able to prevent or lessen the threat. Require a contemporaneous note recording the threat, the basis for the belief, who was told, and why that recipient was chosen, since the §164.512(j)(4) good-faith presumption is only useful if the basis was captured at the time. Reconcile the procedure with state duty-to-warn law, which may compel a disclosure HIPAA merely permits.

Evidence an assessor asks for

For this requirement the evidence type that satisfies it is a procedure. 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.512(j) that means a step-by-step procedure someone unfamiliar with the task could follow. 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.

The practical test for 45 CFR 164.512(j) is whether someone unfamiliar with your organization could read your documentation and tell what you do, who does it, and when it last happened. If they can, the documentation will hold up; whether the requirement is met is a judgment about what it shows, and your counsel owns that conclusion. If they need you in the room to explain it, it will not.

Related requirements

• Law Enforcement Purposes: What you may disclose, and what you must not
• De-identification: The two lawful methods and their limits
• Judicial and Administrative Proceedings: Responding to a subpoena or court order

References

• 45 CFR 164.512(j), in 45 CFR 164.512 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).