Disclosures Required by Law: Reading the required-by-law exception narrowly

45 CFR 164.512(a) is the disclosures required by law requirement. It is short to read and easy to underestimate, because satisfying it means producing an artifact rather than holding an intention.

What the rule says

(1) A covered entity may use or disclose protected health information to the extent that such use or disclosure is required by law and the use or disclosure complies with and is limited to the relevant requirements of such law.

That is the operative language of 45 CFR 164.512(a). Read it closely: it describes an outcome to achieve, not a product to buy, which is why two practices of the same size can satisfy it in different ways and both be right.

What this looks like in practice

In an assessment, 45 CFR 164.512(a) is not one question. It resolves into several, and each one is really asking for a different artifact:

• A documented basis for disclosures it makes because they are required by law, and does it limit each such disclosure to what the relevant law

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

Every covered entity. Business associates are directly liable for only a defined subset of these obligations, so read your business associate agreement alongside the rule rather than assuming the duty transfers. There is no scalability defense here of the kind the Security Rule offers at 45 CFR 164.306(b): a deadline is a deadline at any size. What does scale is how you meet it, and 45 CFR 164.530(i) expects your policies to be designed for the size and activities of your organization.

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. Require staff to identify and record the SPECIFIC statute, regulation, or court-ordered mandate for every required-by-law disclosure rather than citing the category. Build a short register of the mandates the organization actually operates under, state communicable-disease reporting, child-abuse reporting, vital records, FDA reporting, so the common cases are answered in advance and the unusual ones escalate to the Privacy Officer. Train staff that a government request is not self-authorizing, and that where a more specific paragraph of §164.512 applies its conditions govern instead.

What else this satisfies

The same evidence answers more than one framework. The questions behind 45 CFR 164.512(a) also map to NIST Privacy CT.PO-P1. That matters for scoping: if you are working toward SOC 2 or an ISO certification alongside HIPAA, this control is one piece of work and several answers, provided the artifact is written once and referenced rather than rewritten per framework.

Evidence an assessor asks for

For this requirement the artifact types that satisfy it are 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 artifact and keep the superseded versions. The Privacy Rule carries its own retention rule at 45 CFR 164.530(j)(2): six years from the date of 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 artifact, not the intention. For 45 CFR 164.512(a) 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 enough; what fails an assessment is a control implemented once and never re-checked against a changed environment.

Work backward from the evidence. Decide what artifact would prove disclosures required by law to someone who does not already trust you, then build the control that produces it. Programs built in that order tend to stay current, because the artifact goes stale visibly.

References

• 45 CFR 164.512(a), in 45 CFR 164.512 on eCFR. Quoted text verified against the eCFR snapshot of 2026-01-01.
• The Required and Addressable designations are defined at 45 CFR 164.306(d).
• Crosswalk references in this post are our own mapping and are not verified against the published text of those standards.
• 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).