← All posts

Administrative Safeguards for Privacy: Safeguarding PHI in paper and conversation

May 14, 2026 · Ken Armstrong

Auditors ask about administrative safeguards for privacy early, because the answer tells them how the rest of the program is likely to look. The requirement is 45 CFR 164.530(c).

What the rule says

(1) Standard: Safeguards. A covered entity must have in place appropriate administrative, technical, and physical safeguards to protect the privacy of protected health information. (2)(i) Implementation specification: Safeguards. A covered entity must reasonably safeguard protected health information from any intentional or unintentional use or disclosure that is in violation of the standards, implementation specifications or other requirements of this subpart. (ii) A covered entity must reasonably safeguard protected health information to limit incidental uses or disclosures made pursuant to an otherwise permitted or required use or disclosure.

That is the text of 45 CFR 164.530(c). 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(c) 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 an inventory of the PHI it creates, receives, maintains or transmits, and document how it flows through its systems, processes, and business associates?
  • Does the organization periodically assess the privacy risks in how it uses and discloses PHI, and act on what it finds?
  • Does the organization maintain administrative, technical, and physical safeguards protecting the privacy of protected information in all formats, including paper records and verbal communications?

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. Build and maintain an inventory of PHI the organization collects, processes, stores, and shares.
  2. Map data flows across systems, processes, and third-party recipients, including collection points outside direct service encounters.
  3. Record the purpose, categories, and recipients for each flow.
  4. Review and update the inventory on a defined cadence and after changes.
  5. Record how the measure chosen meets the cited provision: the Privacy Rule states the outcome it requires and does not name this practice, so the method is the organization's choice.
  6. Conduct a periodic privacy risk assessment evaluating how PHI is collected, used, disclosed, retained, and shared.

Evidence an assessor asks for

For this requirement the evidence types that satisfy it are inventory, policy, procedure, and risk assessment. 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(c) that means an inventory with an owner and a last-reviewed date on every row, a signed, dated policy with a named owner and a review date, a step-by-step procedure someone unfamiliar with the task could follow, and a completed assessment showing the method, the findings and the date. 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 administrative safeguards for privacy 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

References

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