2026 HIPAA Privacy Rule: New 15-Day Patient Access Deadline & Other Key Changes
Key Takeaways
- HHS finalized HIPAA patient access rights and Notice of Privacy Practices changes. Healthcare providers must respond to patient records requests within 15 calendar days, down from 30 days, among other changes. The new rule also mandates Notice of Privacy Practices changes.
- New patient access and fee requirements increase compliance exposure. The rule expands free electronic access to records, requires posting fee schedules, and generally requires a request through a Personal Health Application to be treated as an access request by the patient.
- Healthcare organizations should prepare now. Covered entities should review patient access workflows, Business Associate Agreements, technology capabilities, and staff training before the July 19, 2027, compliance deadline.
What Changed and When Compliance Is Required
The U.S. Department of Health and Human Services (“HHS”) has finalized significant changes to the HIPAA Privacy Rule, focused largely on the individual right of access. The most substantial operational changes shorten the permitted time Covered Entities have to respond to patient records requests to 15 days, prohibit fees for app- and portal-based access, require providers that charge access fees to post their fee schedules, and limit a patient’s right to direct records to another person to electronic copies of protected health information (“PHI”) in an Electronic Health Record, consistent with the 2020 Ciox Health, LLC v. Azar decision. The rule also requires revisions to Covered Entities’ Notice of Privacy Practices (“NPP”) and removes the requirement to collect a written acknowledgment of receipt of the NPP.
The rule was published in the Federal Register on November 19, 2026, and will take effect on January 19, 2027, with compliance required by July 19, 2027 (with a longer transition period for revising existing Business Associate Agreements in certain scenarios).
While the rule applies directly to Covered Entities, it will also have downstream effects on Business Associates that help Covered Entities respond to right of access requests, and on developers of Personal Health Applications, as Covered Entities respond to patient requests made through apps.
Key Provisions for Patient Access and Privacy Requirements
The rule responds to years of patient complaints, litigation, and enforcement under OCR’s Right of Access Initiative, which since 2019 has produced over 50 OCR settlements and penalties against providers that delayed or overcharged for records access.
The provisions that likely will have the most direct impact on day-to-day operations include:
- 15 Days to Act on an Access Request. Providers must act on a patient’s access request, by providing access or issuing a written denial, as soon as practicable and no later than 15 calendar days after receipt. This represents a significant reduction from the 30-day period permitted under the current rule. If another federal or state law sets a shorter period, that shorter period is treated as practicable. Where a Business Associate Agreement makes the Business Associate responsible for responding, the clock starts when the Business Associate receives the request. One extension of up to 30 calendar days, for a maximum of 45 days, is available if the provider gives written notice within the original 15 days stating the reasons for the delay and the date by which it will complete action. HHS has also signaled that it may shorten the deadline further in a future rulemaking.
- No tolling. The 15 days include time spent clarifying an incomplete request, verifying the requestor’s identity or a personal representative’s authority, and obtaining records from or forwarding the request to a Business Associate. HHS expressly rejected restarting the clock when a request is incomplete.
- Broad “in writing” standard. Providers may still require access requests to be in writing, but any communication that documents the request qualifies. That includes a letter, email, portal message, or transmission from an app or through TEFCA, and providers may not require patients to use a particular form. Providers also may not impose measures that impede access when a less burdensome measure is practicable.
- Free Portal and App Access; Other Fee Limits and Posting Requirements. Providers may not charge patients who inspect their records in person or who obtain ePHI through an “internet-based method,” such as a patient portal or a Personal Health Application connected to an API. This free-access category covers only automated delivery; a copy that a workforce member must prepare, such as an emailed PDF, may still carry a fee. For other copies, fees are limited to labor for copying, supplies and postage for non-electronic copies, and preparing a summary if the patient has agreed. Providers that charge fees must post a fee schedule on their website and make it available at the point of service and upon request. The schedule must identify all free types of access and list standard fees for copies provided under the right of access, the right to direct records, and a valid authorization. Notably, the final rule supersedes HHS’ 2016 fee guidance, including the option to charge a flat fee of $6.50 for electronic copies, and the final rule instead explains how providers must calculate a reasonable, cost-based fee.
- Personal Health Applications and Identity Verification. Under the rule, a request through a Personal Health Application is generally treated as a request by the patient. If ePHI is readily producible through that application, for example through an existing secure, standards-based API, the provider must provide the requested ePHI to or through the application. Providers may not refuse an application’s registration due to lack of a Business Associate Agreement with the application developer and may not impose unreasonable identity verification measures. As a practical matter, providers will need processes for determining whether an application-submitted request is made through a Personal Health Application, which affects whether the request is treated as the patient’s own access request or as a direction to send records to a third party. A request through an app that does not qualify as a Personal Health Application is treated as a request to direct records only if it satisfies the right-to-direct requirements; otherwise, it needs another lawful basis, such as a valid authorization.
- Narrowed Right to Direct. Consistent with the court’s decision in Ciox Health, LLC v. Azar, a patient’s right to direct records to a person the patient designates is limited to electronic copies of PHI in an Electronic Health Record. Other requests may be fulfilled under a valid authorization or another applicable Privacy Rule permission, or the patient may obtain a copy of their records and share it with the third party themselves. Providers may require requests to direct records to be in writing if they inform patients of that requirement, and may, but need not, accept a clear, conspicuous, and specific verbal request, subject to reasonable safeguards and documentation.
- NPP Updates. Providers no longer need to make a good faith effort to obtain a written acknowledgment of receipt of the NPP or document those efforts. Instead, the NPP must inform patients of their right to discuss the notice with a designated contact person or office and include that contact’s phone number and email address. Providers also must revise their NPPs to include a new header and to describe how patients can obtain copies of their records at limited cost or, in some cases, free of charge, as well as the narrowed right to direct electronic copies to a person they designate.
Other Provisions of the Final Rule
In addition, several other provisions are adopted in this rule, which will be important for the providers that these provisions affect. These revisions include clarifying permitted uses and disclosures of PHI for care coordination and case management, expressly permitting disclosures to Telecommunications Relay Services, and expanding permission to use or disclose PHI of Armed Forces members in certain circumstances.
Proposals Not Adopted
Several proposals under the proposed rule ultimately were not adopted, including a minimum necessary exception for care coordination, a “good faith” standard that would have replaced professional judgment for certain disclosures to family members and caregivers, and individualized fee estimates.
What the Rule Means for Covered Entities
Patient Access Timing and Fees
The operational impact will fall most immediately on health information management and release-of-information functions. A 15-day clock that keeps running through clarification, vendor handoffs, and identity verification leaves little room for manual retrieval, mailing, or back-and-forth with patients. Intake workflows and release-of-information vendor arrangements will likely need to be redesigned, and providers may require additional staff, workflow automation, or tighter vendor audit and oversight controls.
Notably, while Covered Entities may delegate responsibility for responding to access requests to Business Associates, the Covered Entity remains ultimately responsible for compliance, and the Business Associate is directly liable under the Privacy Rule if it fails to provide the PHI needed to satisfy an access request, whether to the Covered Entity or, where its Business Associate Agreement so specifies, to the patient or the patient’s designee.
Revenue from patient-facing copy fees will likely decline, particularly where requests can be fulfilled through portals or APIs at no charge. Because fee schedules must now be publicly posted, regulators, patients, and patient advocates will be able to readily compare a provider’s fees against the rule’s limits and identify potentially non-compliant charges.
The risk landscape is also shifting. OCR’s Right of Access Initiative remains one of the most active areas of OCR enforcement, and right of access issues remain among the most common HIPAA complaints. The final rule replaces several gray areas with bright-line requirements, which may make non-compliance easier to identify and prove. Delaying or obstructing app connections may also implicate the information blocking regulations, an area HHS has identified as an enforcement priority, and a single delay in responding to an access request can potentially violate both regimes. Whether a delay also constitutes information blocking, however, is a separate analysis that applies only to entities that qualify as “actors”; a missed HIPAA deadline does not by itself establish it.
Notice of Privacy Practices
Beyond revising the NPP itself, providers should consider training front-line staff on the new right to discuss the NPP. HHS projects roughly 6.1 million patient requests to discuss NPPs nationally each year. Staff should know how to field these requests and when to route questions or complaints to the designated privacy contact.
Business Associate Agreements
Providers that have delegated the responsibility for responding to right of access requests to their Business Associates should proactively review their Business Associate Agreements to ensure that such Business Associates are contractually required to act on requests within the shortened 15-day timeframe. Existing Business Associate Agreements qualify for transition relief if they were in place and compliant before November 19, 2026, and are not renewed or modified between January 19 and July 19, 2027. Qualifying agreements may remain in place until the earlier of their renewal or modification on or after July 19, 2027, or January 19, 2028. To the extent delegated by an applicable Business Associate Agreement, Business Associates must nonetheless meet the 15-day deadline and other access requirements beginning July 19, 2027.
What Covered Entities Should Do Now
Although compliance with the final rule is not required until July 19, 2027 (except in limited instances for Business Associate Agreements, as described above), there will be significant review and revision processes that Covered Entities should undertake in advance of the compliance deadline. As initial priorities, affected organizations should:
- Map current patient access workflows and assess API and patient app registration practices. Measure actual turnaround times against the 15-day standard. To the extent that timeframe is not consistently achieved under current processes, new procedures and staff training should be implemented.
- Inventory fees charged for copies and identify which access channels must become free. Determine allowed fee amounts under HIPAA and state law, and prepare a fee schedule for posting.
- Coordinate with all stakeholders involved, including vendors supporting the patient access process. Review release-of-information vendor contracts and Business Associate Agreements, and ensure expectations on processes, including for identity verification, timing, and fees are clear.
- Prepare updated NPP, policies, and training materials. Update NPP posting and availability, adopt updated access and fee policies, post the fee schedule, train front-line staff, and audit performance after go-live.
Taken together, the changes in the final rule give regulators, plaintiffs, and patients clearer standards against which to measure compliance. For most organizations, preparing for these new standards will require planning, document revision, staff training, and coordination among multiple internal and external stakeholders.
For more information, or to discuss how the final rule may affect your organization, please contact AGG Healthcare Privacy attorneys Madison Pool, Keevana Glossin, or Vanessa Hampton.
- Madison M. Pool
Partner
- Keevana E. Glossin
Associate
- Vanessa I. O. Hampton
Associate