Know what is on your site before a plaintiff’s firm does.Free website scanScan Your Site
Log in Sign up Book a demo
Home› Editorial› HIPAA’s 15-Day Access Clock Is Coming: What HHS’s…
DATA

HIPAA’s 15-Day Access Clock Is Coming: What HHS’s Final Privacy Rule Changes in Your Records Workflow

For more than a decade, the HIPAA right of access has run on a 30-day clock.

Nov 17, 2026 9 min read

Know what’s on your site before a plaintiff’s firm does

A free privacy audit shows which cookies, pixels and trackers are running — and which ones commonly appear in privacy claims.

Get My Free Audit

For more than a decade, the HIPAA right of access has run on a 30-day clock. That changes in 2027. On November 16, 2026, the HHS Office for Civil Rights announced a final rule, “HIPAA Privacy Rule: Changes to Support Coordinated Care and Individual Engagement and Reduce Regulatory Burdens,” that halves the time covered entities have to answer patients, limits what they can charge, and puts boundaries on how hard they can make people work to prove who they are. It also quietly drops a long list of ideas HHS floated in its 2021 proposal. For records teams, release-of-information vendors and the business associates behind patient portals, the practical question is what has to change in the access workflow before the compliance date.

TL;DR

  • Covered entities will have to act on access requests within 15 calendar days of receipt, with one extension of up to 30 calendar days, instead of today’s 30 plus 30.
  • The rule is scheduled for Federal Register publication on November 19, 2026, takes effect 60 days later, and requires compliance 240 days after publication, with up to one extra year for qualifying existing business associate agreements.
  • HHS did not finalize several 2021 proposals, including an expanded in-person inspection right, a shorter 15-day extension, individualized fee estimates and a minimum necessary exception for care coordination.

Bauhaus-style geometric composition of a red medical cross, a blue folder shape and a yellow key form with a clock-like circle on a cream grid

What HHS finalized, and when it applies

The rule went on public inspection at the Federal Register on November 16 and is scheduled to be published on November 19, 2026. The dates are tied to publication: the rule is effective 60 days after publication, and regulated entities must comply 240 days after publication. If publication happens on the scheduled date, that works out to an effective date of January 18, 2027 and a compliance date of July 17, 2027. Treat those as calculated dates until the published version fills in the brackets.

The HHS announcement frames the rule around patients. Secretary Robert F. Kennedy Jr. said Americans “should never have to fight for access to their own health records,” and OCR Director Paula M. Stannard described faster, easier access alongside reduced burdens for providers. Some early summaries said the rule requires organizations to “authorize” requests in a timely way. That is imprecise: patients need no one’s authorization to use the right of access. What changes is the deadline to act on the request and deliver the records.

Beyond access, the rule clarifies care coordination and case management disclosures, including to social services agencies and community-based organizations, and removes the requirement to try to obtain a written acknowledgment that a patient received the Notice of Privacy Practices. It also updates NPP content, permits disclosures to relay-service communications assistants, and extends a military command permission to all Uniformed Services.

The new clock: 15 days, one 30-day extension

Under the final text, a covered entity must act on a request for access as soon as practicable, and no later than 15 calendar days after receiving it. If it cannot, for example because records are archived offsite on paper, it may take one extension of no more than 30 calendar days, but only if it tells the individual in writing, within the first 15 days, why there is a delay and when access will be provided. Only one extension is allowed per request.

Two details matter. First, where another federal or state law requires access faster than 15 days, HHS will treat that shorter period as what is “practicable.” Teams that already juggle state medical records statutes, such as California’s medical privacy rules, should map the shortest applicable deadline per state rather than default to the federal outer limit. Second, HHS kept the 30-day extension it had proposed to shorten to 15 days, responding to commenters’ concerns about complex requests.

The differences between GDPR and HIPAA still run deep, but a 15-day HIPAA target is now tighter than the GDPR’s one-month baseline.

Identity verification: what counts as too much

The rule adds a new paragraph at 45 CFR 164.524(b)(1)(iii) barring covered entities from imposing measures that impede an individual from obtaining access, including measures for making the request, when a less burdensome measure is practicable for the entity.

HHS chose not to write examples into the regulation, but the preamble lists measures it currently considers unreasonable:

  • requiring proof of identity in person when remote verification is practicable for the entity and more convenient for the individual;
  • requiring a “wet” signature when an electronic signature is valid under applicable law; and
  • requiring notarization of a written access request, including a request to direct records to a third party.

The preamble also addresses personal health apps. HHS says it would consider it unreasonable for a covered entity participating in TEFCA to refuse an app’s access request sent through TEFCA when the entity has validated a cryptographically signed token from a credential service provider certified for identity assurance level 2 and authenticator assurance level 2 under NIST SP 800-63, and confirmed that the verified demographics match its records. A similar point is made for requests sent through CMS Aligned Networks. That is the scenario a provider coalition had warned about before publication, as we covered when health groups pushed back on the app verification changes.

Apps, formats and the right to direct records

The rule adds definitions of “electronic health record” and “personal health application.” Requests still may be required in writing, but HHS clarifies that “in writing” covers a letter, a paper form, an email, a secure message, a portal request or an electronic transmission from a personal health app that documents the request. No particular form is required.

On delivery, if other federal or state law already requires an entity to use a technology that gives individuals access in a particular electronic form and format, such as a standards-based API, that form and format is deemed “readily producible.” A copy sent through a personal health app is treated as a copy to the individual, not a third-party disclosure. The rule does not by itself require buying new technology to support apps.

The separate right to direct a copy to a designated person is limited, consistent with the court’s decision in Ciox Health v. Azar, to electronic copies of PHI in an electronic health record. Paper copies and records outside the EHR still need a valid authorization to go to a third party, unless another permission applies. When a covered entity offers a summary instead of a copy, it must now tell the individual that they keep the right to a copy or to direct an electronic copy.

Fees and the posted schedule

Fee rules get stricter and more transparent. Covered entities may not charge for in-person inspection or for access through an internet-based method, which HHS describes as automatic processes such as viewing or downloading through a portal or connecting an app via certified API technology. Where fees are allowed, they are limited to labor for copying, supplies for non-electronic copies, postage, and preparing a summary or explanation the individual agreed to. The rule supersedes the 2016 guidance that described an optional $6.50 flat fee for electronic copies.

New 45 CFR 164.525 requires covered entities to post a fee schedule on their website, if they have one, and make it available at the point of service. Anyone who has priced out the cost of handling access requests will recognize that a published schedule is easier to audit than case-by-case quotes.

What HHS left out of the 2021 proposal

The 2021 notice of proposed rulemaking was broader than the final rule. HHS said it is not finalizing:

  • changes to the right to inspect, which commenters said would be overly burdensome;
  • the proposed 15-day extension (the 30-day extension stays);
  • a required policy to prioritize urgent requests;
  • a duty to act on oral requests to direct records to a third party;
  • a requirement for providers and plans to submit a patient’s request to another provider and pull records on the patient’s behalf;
  • individualized fee estimates and itemized statements on request;
  • an exception to the minimum necessary standard for care coordination and case management; and
  • changes to the “good faith” and professional judgment standards for disclosures to family and caregivers.

The minimum necessary decision matters: care coordination has clearer footing as a health care operation, but those uses and disclosures must still be limited to the minimum necessary.

A right-of-access workflow update, step by step

  1. Reset the clock. Change intake systems, queues and service levels from 30 to 15 calendar days, measured from receipt, and keep a stricter state deadline where one applies.
  2. Rewrite the extension letter. Make sure it goes out within 15 days, states the reason and the delivery date, and is used only once per request.
  3. Audit verification steps. Remove default notarization, wet-signature and in-person requirements where remote or electronic options are practicable, and document why any heavier step is needed.
  4. Accept requests through every written channel you support. Train staff that an email, portal message or app transmission can be a valid request, without a proprietary form.
  5. Separate the two rights. Route copies to the patient, including via apps, differently from requests to direct EHR copies to another person, and route paper or non-EHR requests to the authorization process.
  6. Update summaries. Add the required notice that the patient keeps the right to a full copy.
  7. Publish the fee schedule. Zero out portal and API access and in-person inspection, and limit other fees to allowed costs.
  8. Review business associate agreements. HHS codified at 45 CFR 164.502(a)(4)(ii) that the agreement controls whether the business associate discloses PHI directly to the individual or designee, so say clearly who fulfills requests.

There is a transition period: a compliant business associate agreement in place before publication that is not renewed or modified between the effective date and the compliance date is deemed compliant until it is renewed or modified after the compliance date, or until one year after the effective date, whichever comes first. Evergreen contracts that roll over automatically qualify. Organizations that also live under GLBA or state privacy laws can use the same review to look for gaps between HIPAA, GLBA and state law.

Frequently asked questions

Do we have to follow the 15-day deadline now?

No. The current rules apply until the compliance date, which is 240 days after publication. Starting early helps because the change touches staffing and vendor contracts.

Can we still require requests in writing?

Yes, but “in writing” includes email, portal messages and qualifying app transmissions, and you cannot insist on a specific form when a less burdensome option is practicable.

Is the release-of-information vendor responsible for the deadline?

The covered entity remains directly responsible for providing access. The business associate agreement decides whether the vendor sends records to the patient or back to the covered entity, so the deadline needs to be built into that contract.

Fifteen days is a design problem, not a staffing problem

Halving the clock will not be solved by asking a records team to work faster. It will be solved by fewer manual steps between the request and the record: lighter verification where it is safe, electronic channels that count as written requests, fees that do not need a calculator, and contracts that say who presses send. Organizations that redesign the flow now will find July 2027 uneventful.

Put this into practice

Turn privacy guidance into working controls.

Captain Compliance helps teams discover tracking technologies, enforce consent, manage privacy requests and document the evidence behind every decision.

Book a demo Run a free scan