Documentation: Documentation and the six-year retention rule

45 CFR 164.316(b)(1) sets the expectation for documentation. 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

Standard: Documentation. (i) Maintain the policies and procedures implemented to comply with this subpart in written (which may be electronic) form; and (ii) If an action, activity or assessment is required by this subpart to be documented, maintain a written (which may be electronic) record of the action, activity, or assessment.

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

This is a standard, and a standard is met in full: 45 CFR 164.306(c) requires a covered entity or business associate to comply with the applicable standards.

What this looks like in practice

In an assessment, 45 CFR 164.316(b)(1) 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 maintain its security policies, procedures, and related records in written (which may be electronic) form, in a managed location from which the current versions can be retrieved?
• Does the organization protect records from loss, destruction, falsification, and unauthorized access or release in line with retention requirements?
• Does the organization document operating procedures for the activities that keep its systems holding ePHI running and make them available to those who need them?

Ownership usually sits with the security 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

Every covered entity and every business associate, at any size. 45 CFR 164.306(b) allows flexibility of approach, so a two-provider practice and a hospital system may implement this differently and both comply. What flexibility does not allow is skipping the decision: the smaller the organization, the more the written reasoning carries the weight, because there is no scale of operation to make the control self-evident.

Building it, in order

These steps are one way to meet it, drawn from our question bank. Unless a step names a provision, the Security Rule does not require that particular measure: 45 CFR 164.306(b)(1) lets you use any security measures that allow you to reasonably and appropriately implement the standards and implementation specifications, chosen with the factors in 45 CFR 164.306(b)(2).

The sequence below is the order that produces evidence as a by-product rather than as a separate documentation exercise:

1. Establish a central repository for all security policies, procedures, and related documentation.
2. Ensure each document is versioned and reflects the current approved state.
3. Assign responsibility for keeping the repository current.
4. Record security-related actions and activities alongside the governing documents.
5. Classify records and define retention, protection, and disposal requirements for each type.
6. Apply access, integrity, and backup controls appropriate to the sensitivity of the records.

Where else this maps

The questions behind 45 CFR 164.316(b)(1) also map to HHS 405(d) HICP (2023 Edition) CSP 10 and NIST SP 800-66 Rev. 2 5.5.2, which are voluntary guidance rather than law; following them does not by itself establish compliance with any law. That matters for scoping: the same evidence can be written once and referenced from each, rather than rewritten per framework.

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. 45 CFR 164.316(b)(2)(i) requires the documentation 164.316(b)(1) calls for (the Security Rule policies and procedures, and the written record of any action, activity or assessment the Security Rule requires to be documented) to be retained for six years from the date of its creation or the date when it last was in effect, whichever is later, so a policy you replaced two years ago is still part of the record.

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.316(b)(1) 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 security 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.
• There is no documented-alternative route for the requirement itself. It is required (45 CFR 164.306(d)(2) for a specification, 164.306(c) for a standard), so a risk-based decision not to meet it is not available. How you meet it is yours to choose under 45 CFR 164.306(b); the measures in this post are examples, not the rule's text.

Work backward from the evidence. Decide what evidence would prove documentation to someone who does not already trust you, then build the control that produces it. Programs built in that order tend to stay current, because the evidence goes stale visibly.

Related requirements

• Policies and Procedures: Policies and procedures that reflect what you do
• Time Limit: The six-year clock and when it starts
• Subcontractor Obligations in Business Associate Contracts: How obligations flow down the chain

References

• 45 CFR 164.316(b)(1), in 45 CFR 164.316 on eCFR. Quoted text verified against the eCFR text current as of 2026-10-06.
• The Required and Addressable designations are defined at 45 CFR 164.306(d).
• Crosswalk references in this post are the mappings in our question bank, and are not verified against the published text of those standards.
• 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 additional obligations; HIPAA preempts a State law only where it is contrary to HIPAA (45 CFR 160.202, 160.203).