Right to Amend: Handling an amendment request and a denial

Auditors ask about right to amend early, because the answer tells them how the rest of the program is likely to look. The requirement is 45 CFR 164.526.

What the rule says

45 CFR 164.526 governs right to amend. 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.

A covered entity may deny an amendment only on four grounds: the information was not created by it (unless the originator is no longer available to act on the request), is not part of the designated record set, would not be available for inspection under 164.524, or is accurate and complete (164.526(a)(2)). A denial is written, in plain language, and states the basis, the individual's right to submit a statement of disagreement, that without one the individual may ask for the request and the denial to go with future disclosures, and how to complain to the covered entity or to the Secretary (164.526(d)(1)).

What this looks like in practice

In an assessment, 45 CFR 164.526 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 process for handling individual requests to amend their protected information, including granting amendments, issuing written denials, and notifying relevant parties?

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. Develop an amendment policy describing how individuals submit written amendment requests with a stated reason.
2. Act on each request no later than 60 days after receipt, with one extension of no more than 30 days only if a written statement of the reasons and the completion date is given within the 60 days (§164.526(b)(2)).
3. Define grounds for denial and the individual's right to submit a statement of disagreement.
4. Notify relevant parties when an amendment is accepted.

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.526 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.
• 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.

The recurring lesson with right to amend is that documentation is not the paperwork after the control. It is the part an assessor can read, and therefore the part that has to exist.

Related requirements

• Individual-Directed Transmission: Third-party directives after Ciox v. Azar
• Accounting of Disclosures: The six-year accounting and its exclusions
• Right of Access: The 30-day clock, the fee cap and the format rules

References

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