Skip to main content
Notifications
You're all caught up.
View all notifications
Backsplice
  • Product
  • Watney AI
  • Why us
  • Pricing
  • Docs
  • Security
  • About
  • Log in
  • Start free
Log in Start free
← All posts

Right of Access: The 30-day clock, the fee cap and the format rules

May 6, 2026 · Ken Armstrong

45 CFR 164.524 is the requirement on right of access. It is short to read and easy to underestimate, because satisfying it means producing evidence rather than holding an intention.

What the rule says

45 CFR 164.524 governs right of access. 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 fee is a reasonable, cost-based fee that includes only labor for copying, supplies, postage, and an agreed summary (164.524(c)(4)); HIPAA sets no dollar cap.

What this looks like in practice

In an assessment, 45 CFR 164.524 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 provide individuals timely access to an electronic copy of their electronic information in the form and format they request, covering the protected health information in its designated record sets?
  • Does the organization have a process for responding to individual requests to access their own protected information within the required timeframe and in the form and format requested?
  • Does the organization provide individuals with usable ways to access and amend their protected health information?

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 a process that provides individuals a copy of their electronic information in the electronic form and format they request where readily producible, or otherwise in a readable electronic form and format agreed with the individual (§164.524(c)(2)(ii)), a self-service tool being an acceptable but optional means.
  2. Cover all protected health information in the designated record sets (§164.524(a)(1)), except psychotherapy notes and information compiled in reasonable anticipation of, or for use in, a civil, criminal, or administrative action or proceeding.
  3. Verify access is provided no later than 30 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 first 30 days (§164.524(b)(2)), and that any fee charged is limited to a reasonable, cost-based fee.
  4. Document any excluded categories and the basis for exclusion.
  5. Establish an access policy describing how individuals may submit requests in writing, orally, or electronically.
  6. Track a response clock that begins on receipt of each request, and act no later than 30 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 first 30 days (§164.524(b)(2)).

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

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

Work backward from the evidence. Decide what evidence would prove right of access 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

  • Requests for Restrictions: The self-pay restriction you cannot refuse
  • Individual-Directed Transmission: Third-party directives after Ciox v. Azar
  • Notice of Privacy Practices: What the notice must say and where it must appear

References

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

HIPAA compliance and AI governance, in one program.

View our security posture →

Product

  • Why Backsplice
  • Frameworks
  • Watney AI
  • HIPAA Records
  • Review & Approval
  • Governance Registers
  • Reporting
  • Integrations & API
  • Pricing

Company

  • About Us
  • Team
  • Mission
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  • Data Processing Agreement
  • Business Associate Agreement
  • Security

Resources

  • Documentation
  • Guide to HIPAA
  • Blog
  • Status Page

© 2026 Backsplice LLC. All rights reserved.

Backsplice provides tools to run a HIPAA and AI governance program; it does not confer compliance with any law or standard and does not constitute legal advice. Consult qualified legal counsel for specific compliance guidance.