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

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

What the rule says

Standard: Uses and disclosures required by law. (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. (2) A covered entity must meet the requirements described in paragraph (c), (e), or (f) of this section for uses or disclosures required by law.

That is the text of 45 CFR 164.512(a). It is a permission with conditions: the conditions are what make the use or disclosure lawful, so a summary is not a safe substitute for the text.

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 different evidence. These are among the questions asked about it:

• Does the organization have 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 actually compels?

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. 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. If the organization is a business associate, disclose only as its business associate agreement permits or as required by law, apply the §164.512 conditions as the covered entity would, and notify the covered entity where the agreement requires.

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(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 a common floor; what fails an assessment is a control implemented once and never re-checked against a changed environment.

Work backward from the evidence. Decide what evidence 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 evidence goes stale visibly.

Related requirements

• Uses and Disclosures Requiring an Opportunity to Object: Facility directories and family involvement
• Public Health Activities: Reporting to public health authorities
• Psychotherapy Notes: The separate authorization standard

References

• 45 CFR 164.512(a), in 45 CFR 164.512 on eCFR. Quoted text verified against the eCFR text current as of 2026-10-06.
• 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).