Requests for Restrictions: The self-pay restriction you cannot refuse

45 CFR 164.522 sets the expectation for requests for restrictions. The text is brief; the evidence it implies is not, and the difference between the two is where most remediation time goes.

What the rule says

45 CFR 164.522 governs requests for restrictions. 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.

Outside the self-pay case a covered entity is not required to agree to a restriction (164.522(a)(1)(ii)). One it does agree to binds it, except that restricted PHI may be used or disclosed to provide emergency treatment the individual needs (164.522(a)(1)(iii)).

What this looks like in practice

In an assessment, 45 CFR 164.522 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 accommodate reasonable individual requests to receive communications by alternative means or at alternative locations?
• Does the organization have a process for honoring individual requests to restrict the use or disclosure of their protected information, including any mandatory restriction the organization must accept?

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. Establish a process for individuals to request alternative communication methods or locations.
2. Accommodate reasonable requests. A health care provider may not require an explanation of the reason (§164.522(b)(2)(iii)). A health plan must accommodate a reasonable request where the individual clearly states that disclosure could endanger them, and may require that statement in the request (§164.522(b)(1)(ii), (b)(2)(iv)).
3. Define any conditions, such as a method to contact the individual.
4. Record and apply accommodations across communication channels.
5. Establish a process for receiving, evaluating, and responding to restriction requests.
6. Document which requests the organization may decline and which it must honor, such as a request not to disclose to a health plan, for payment or health care operations and where no law requires the disclosure, information that pertains solely to a health care item or service for which the individual, or a person other than the health plan on the individual's behalf, has paid the covered entity in full (§164.522(a)(1)(vi)).

Evidence an assessor asks for

For this requirement the evidence types that satisfy it are policy and 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.522 that means a signed, dated policy with a named owner and a review date and 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.
• Re-read it when something changes. A new system, a new vendor or a departure is what makes a correct control stale. Tie the review to those events as well as to the calendar, and date the result.

None of this makes requests for restrictions harder than it is. The requirement asks for a decision, an implementation, and a record. Organizations that struggle at assessment time are rarely the ones without controls; they are the ones that cannot show when a control started or who owns it now.

Related requirements

• Notice of Privacy Practices: What the notice must say and where it must appear
• Right of Access: The 30-day clock, the fee cap and the format rules
• Verification Requirements: Verifying identity and authority before disclosing

References

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