Burden of Proof: Documenting why notification was not required

45 CFR 164.414 sets the expectation for burden of proof. 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.414 governs burden of proof. 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.414 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 retain the documentation needed to demonstrate that required breach notifications were made, or that an impermissible use or disclosure did not rise to a notifiable breach?

Ownership usually sits with the privacy and security officials, 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. A business associate is bound directly by this provision; it is not only a contract term.

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. Document each impermissible use or disclosure and the four-factor risk assessment used to determine whether it compromised the security or privacy of the information.
2. Retain evidence of any notifications made to individuals, regulators, and the media, including dates and content.
3. Retain the analysis supporting any determination that notification was not required.
4. If the organization is a covered entity, retain this documentation for six years from the date of its creation or the date when it last was in effect, whichever is later (45 CFR 164.530(j)(2), applied by § 164.414(a)). A business associate, which § 164.414(a) does not reach, bears the same burden of proof under § 164.414(b), so retain the documentation long enough to meet it and for any period its business associate agreements require; where the event was a security incident involving ePHI, the business associate's record of the incident and its outcome is kept for six years under 45 CFR 164.308(a)(6)(ii) and 164.316(b)(2)(i), which bind it directly.

Evidence an assessor asks for

For this requirement the evidence type that satisfies it is a log. 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 (applied to a covered entity by 164.414(a)) 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

In our question bank this is weighted Critical: a gap here is raised as a critical finding (a partial answer as high). The usual cause of a gap is drift: the control was implemented once, the environment changed, and nothing re-checked it. A dated review on a fixed cadence is cheaper than the remediation.

What to do about it

• Produce the evidence, not the intention. For 45 CFR 164.414 that means retained logs plus evidence somebody actually reviewed them. 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 and security officials should be recorded as the owners. A control with no owner stops working the month the person who quietly maintained it changes roles, and nobody notices.
• Review it on a fixed date, not when you remember. In our question bank this is weighted Critical: a gap here is raised as a critical finding (a partial answer as high). Put the review on the calendar with an owner, and keep the dated output of each one.

The recurring lesson with burden of proof 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

• Business Associate Breach Notification: What a business associate owes the covered entity
• Notification to the Secretary: The two HHS deadlines and which applies
• Media Notification: The more-than-500-residents threshold

References

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