Skip to content

HIPAA’s New 15-Day Deadline: Where Will You Lose the First Five Days?

Posted by Antonina McAvoy in Cybersecurity, Consulting, Risk Advisory, Healthcare.

Key points covered in this article:

  • The new HIPAA Privacy Rule shortens the standard deadline for responding to patient record requests from 30 to 15 calendar days, which means healthcare organizations need to understand exactly where delays occur in their current process.
  • Many access delays happen before the records team even begins work. Leaders should measure response time from the moment the organization first receives a request, not when a ticket is opened, and review handoffs across front desk, portal, records, IT, and vendors.
  • Readiness depends on more than policy updates. Healthcare providers should test record retrieval across current and retired EHR systems, review patient access workflows for fees and identity verification, and trace a real request end to end to identify operational gaps before the compliance deadline.

A resident asks for a copy of her medical records on a Friday before moving to another care facility. The request reaches the records team on Tuesday. By Wednesday, staff have pulled her current chart and discovered that some of the records she wants are in the electronic health record (EHR) system the facility replaced last year. Retrieving them requires a ticket with the former vendor.

Five calendar days have passed before anyone has asked the vendor for the records.

On November 16, 2026, the U.S. Department of Health and Human Services announced a final HIPAA Privacy Rule that cuts the standard deadline for acting on an individual’s request to access their protected health information from 30 to 15 calendar days. Covered entities must act as soon as practicable. If they need more time, they may take one extension of up to 30 additional calendar days. To use it, they must notify the individual in writing within the initial 15 days, explain the delay, and state when they will act on the request, as detailed in the Final rule.

For healthcare leaders, the first question is where those days go today.

Measure from the day the request arrives

A records team may report that it fulfilled a request in seven days. If the request sat in a portal inbox or at a front desk for four days before it was logged, the patient waited eleven. A report that starts when the records team opens a ticket can hide the delays leadership needs to fix.

Look at when the organization first received a request, when the records team picked it up, and when the patient received the records. If most of the delay occurs before the records team sees the request, a faster turnaround target for that team will only solve part of the problem.

Test patient access before retiring an EHR

During an EHR conversion, leadership decides what to migrate, what to archive, and when to retire the old system. Those choices also determine whether staff can fulfill a request that spans years of care. An archive may preserve the full record while giving staff limited ways to search it, export it, or combine it with information from the current system.

Before signing off on the conversion, ask the records team to work through a realistic request that spans both systems. Can staff find and prepare the records for release using the permissions and vendor support they’ll have after go-live? If the former vendor controls retrieval, can the team get the records back in time once the original contract ends?

Review what patients have to do to get their records

The rule addresses access through a patient’s chosen personal health app when the electronic information is readily producible in the requested form and format. It also changes when covered entities may charge fees and what they must disclose in advance, and limits identity verification measures that create unreasonable barriers to access. HHS summarizes these changes to the individual right of access in the HHS fact sheet.

Walk through the process from the patient’s side. Can they find the right place to ask? When do they learn whether there’s a fee? What happens if they can’t use the portal?

For post-acute and long-term care providers, discharge planning is another workflow worth reviewing. The rule allows covered entities, in specified circumstances, to share information with social service and community organizations when supporting a patient’s care coordination or case management. A discharge planner arranging support at home should know when that permission applies, what information is appropriate to share, and how to send it securely.

Providers that treat patients directly should revisit their Notice of Privacy Practices procedures, including related admission materials and staff guidance. Under the updated rule, they no longer need to seek a patient’s written confirmation that the notice was received. Both changes are outlined in the HHS announcement.

Put one request on the leadership agenda

At your next compliance or risk committee meeting, bring the timeline for a single records request that crossed a weekend, required records from multiple systems, or depended on a vendor. Show when it arrived, where it waited, and when the patient received the records. If that Friday request came in at your organization this week, who would know by Monday morning that the clock was already running?

Federal Register publication is scheduled for November 19, 2026. The Privacy Rule takes effect 60 days after publication, and regulated entities have 180 days after the effective date to comply. The separate HIPAA Security Rule cybersecurity proposal remains pending on the federal regulatory agenda.

Can you answer these five questions before the deadline?

  1. When does the clock start?
    Can you show when the organization first received a request, even if it reached the records team days later?
  2. Who sees a request that’s falling behind?
    Would someone catch it over a holiday weekend or when the usual owner is out?
  3. Where are the records?
    Can staff retrieve everything a patient is entitled to receive if it spans two EHRs or depends on a former vendor?
  4. What does the patient experience?
    Do staff give consistent answers about identity verification, fees, and electronic delivery?
  5. How do you know you’re ready?
    When did you last follow a request from the moment it arrived to the moment the patient received the records?

How PBMares can help

If your answers depend on who’s working, which system holds the records, or how quickly a vendor responds, that’s where we’d start. PBMares’ Cyber & Risk Advisory team can work with your privacy, records, and IT teams to test a representative request, pinpoint where it stalls, and help leadership decide what to fix first. Contact PBMares to discuss how the 15-day deadline would work in your organization.

 


Be sure to consult with your financial or tax advisor on this topic as individual situations may vary. The information contained in this article or webinar, and any related materials, are for informational purposes only, and cannot be relied upon for legal, financial, tax, accounting, or other professional services advice. The content is provided on an “as is” basis and PBMares makes no representations or warranties about the accuracy or sustainability of any information for your purposes. For any specific questions you may have, please contact us.

This content is accurate at the time of publication. Always ensure you are reviewing the most recent information available. Contact your tax or financial advisor if you need clarification.

Contact Us

About the Author

Antonina McAvoy
Antonina McAvoy

CISA, CISM, QSA, PCIP
Partner, Cyber & Risk Advisory
Norfolk

Antonina McAvoy specializes in cybersecurity, data protection, and privacy. She has 14 years of experience leading and performing a wide spectrum of cybersecurity reviews.

View Bio

Get News, Alerts, and Guidance

PBMares provides timely insights that help businesses build smarter, well-informed strategies. Join them.