Verification Requirements: Verifying identity and authority before disclosing

45 CFR 164.514(h) covers verification requirements. In most assessments the control itself is present and the record proving it is not, which is why this requirement produces findings at organizations that are, in practice, doing the work.

What the rule says

45 CFR 164.514(h) governs verification requirements. 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.

The rule is 45 CFR 164.514(h): before any disclosure the Privacy Rule permits, verify the identity of the person requesting PHI and their authority to have it, if either is not known to you (except for disclosures under 164.510), and obtain any documentation, statement or representation that is a condition of the disclosure ((h)(1)). You may rely, where reliance is reasonable, on documents that on their face meet the conditions, and on a badge, credentials or government letterhead to verify a public official ((h)(2)).

What this looks like in practice

In an assessment, 45 CFR 164.514(h) 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 verify the identity of individuals exercising their privacy rights and manage authorized access by personal representatives and proxies?

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 an identity-verification process for individuals requesting access to or action on their information.
2. Define how personal representatives, guardians, and caregivers may be authorized for proxy access and the scope of that access.
3. Implement controls to prevent unauthorized proxy access and to protect sensitive information where proxy rights are limited.
4. Document verification and proxy decisions.

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.514(h) 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 practical test for 45 CFR 164.514(h) is whether someone unfamiliar with your organization could read your documentation and tell what you do, who does it, and when it last happened. If they can, the documentation will hold up; whether the requirement is met is a judgment about what it shows, and your counsel owns that conclusion. If they need you in the room to explain it, it will not.

Related requirements

• Limited Data Set: When a limited data set is the right tool
• Notice of Privacy Practices: What the notice must say and where it must appear
• De-identification: The two lawful methods and their limits

References

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