← All posts

Uses and Disclosures Requiring an Opportunity to Object: Facility directories and family involvement

April 21, 2026 · Ken Armstrong

45 CFR 164.510 is the requirement on uses and disclosures requiring an opportunity to object. It is short to read and easy to underestimate, because satisfying it means producing evidence rather than holding an intention.

What the rule says

45 CFR 164.510 governs uses and disclosures requiring an opportunity to object. 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.510 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 policy governing disclosures of protected information to family members, friends, or others involved in an individual's care, and for disaster-relief purposes?
  • Does the organization have a policy governing facility-directory disclosures and the limited information included, with individuals given the opportunity to object?
  • Does the organization have a policy governing disclosures of protected information to family members, friends, or others involved in an individual's care, including how it handles the individual's agreement or objection?

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. Define when protected information may be shared with family members, friends, or others involved in an individual's care.
  2. Where the individual is present and has capacity, obtain agreement, give an opportunity to object, or reasonably infer no objection (§164.510(b)(2)), and where the individual is not present or is incapacitated, or in an emergency, disclose only what is directly relevant and only on a professional judgment that it is in the individual's best interests (§164.510(b)(3)).
  3. Address disclosures to disaster-relief organizations.
  4. Train staff on verifying involvement and limiting information to what is relevant.
  5. Establish a facility-directory policy specifying what information may be included and to whom it may be released.
  6. Provide individuals the opportunity to agree to or restrict directory inclusion.

Evidence an assessor asks for

For this requirement the evidence type that satisfies it is a policy. 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.510 that means a signed, dated policy with a named owner and a review date. 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 uses and disclosures requiring an opportunity to object 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

References

  • 45 CFR 164.510, in 45 CFR 164.510 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).