Complaint Process: A complaint route patients can actually use

45 CFR 164.530(d) sets the expectation for complaint process. 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

(1) Standard: Complaints to the covered entity. A covered entity must provide a process for individuals to make complaints concerning the covered entity's policies and procedures required by this subpart and subpart D of this part or its compliance with such policies and procedures or the requirements of this subpart or subpart D of this part. (2) Implementation specification: Documentation of complaints. As required by paragraph (j) of this section, a covered entity must document all complaints received, and their disposition, if any.

That is the text of 45 CFR 164.530(d). Read each condition in it: it says what must be in place, and the method is yours only where the text leaves it open.

What this looks like in practice

In an assessment, 45 CFR 164.530(d) 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 process for individuals to file privacy complaints and a prohibition against retaliation for doing so?

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 privacy complaint process with clear submission channels, including written and online options.
2. Inform individuals of their right to raise complaints with the organization and with the Secretary of HHS (§164.520(b)(1)(vi)).
3. Prohibit retaliation or intimidation against individuals who file complaints or exercise their rights.
4. Document, investigate, and resolve complaints.

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.530(d) 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.

None of this makes complaint process 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

• Administrative Safeguards for Privacy: Safeguarding PHI in paper and conversation
• Refraining from Retaliation: The anti-retaliation and no-waiver rules
• Privacy Training: The privacy half of workforce training, which security training misses

References

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