\n\n

On November 19, 2026, the U.S. Department of Health and Human Services, Office for Civil Rights (OCR) published in the Federal Register a final rule (Final Rule) modifying the Health Insurance Portability and Accountability Act of 1996 (HIPAA) Privacy Rule to support care coordination and to give individuals faster, lower-cost access to their health information, and increasingly through applications (apps). The Final Rule, which finalizes many of the proposals OCR issued in its January 2021 proposed rule, takes effect on January 19, 2027, with compliance required by July 19, 2027.

Key Takeaways

  • Covered entities will be affected, as will business associates that handle records requests, portals, or application programming interfaces (APIs), and companies building patient-facing apps.
  • The Final Rule adopts and defines a new term, “personal health application,” to support the right of an individual to obtain a copy of their protected health information (PHI) through a personal health app pursuant to the right of access.
  • The Final Rule shortens the deadline to respond to access requests from 30 to 15 calendar days but keeps the existing 30-day extension.
  • The Final Rule prohibits the use of “unreasonable verification measures” that would impede the individual from exercising their rights, including the individual right of access.
  • The Final Rule clarifies that covered entities may disclose PHI without an authorization or a business associate agreement (BAA) to social services agencies, community-based organizations, home- and community-based services providers, and similar third parties that provide health or human services, for individual-level care coordination and case management.
  • The Final Rule clarifies that “health care operations” includes individual-level and population-based care coordination and case management.

Apps and the Right of Access

The Final Rule enhances an individual’s right to access their PHI by adopting a new term, “personal health application,” defined as an app an individual uses to access their health information, where the information is managed, shared, and controlled by or primarily for the individual. OCR treats such an app as equivalent to the individual, so a request by the individual to send records to the app is an exercise of the individual’s right to obtain a copy of their records. In other words, a request to a personal health application is treated as a first-party request rather than a third-party request. The app’s developer is not a business associate. A covered entity must send records to a personal health application when the individual asks and a copy is readily producible in that manner, although the Final Rule does not require covered entities to implement new technologies or policies in order to provide individuals with a copy of their PHI to or through a personal health application. OCR cautions that a covered entity or business associate offering a standards-based API may not, absent security concerns, refuse to register an individual’s chosen app solely because the app’s developer has no BAA or competes with its own services.

Separately, the Final Rule provides that the individual’s right to direct the covered entity to transmit a copy of PHI to a person designated by the individual covers only electronic copies of PHI in an electronic health record (EHR), and not paper copies. That largely matches how OCR has enforced the right since 2020 and is consistent with the holding in Ciox Health v. Azar. The new EHR definition, which OCR describes as consistent with the Health Information Technology for Economic and Clinical Health (HITECH) Act, counts providers with indirect treatment relationships, such as labs and durable medical equipment suppliers, as “clinicians,” so their electronic records can qualify as EHRs.

Faster, Cheaper Access

The Final Rule also shortens the deadline for a covered entity or a business associate to respond to individual access requests from 30 to 15 calendar days and keeps the existing 30-day extension. OCR explains that the clock starts when a request is received, even if it is incomplete, and that the 15-day period includes time spent obtaining records from a business associate. Where a request is sent directly to a business associate and the BAA makes the business associate responsible for responding, the clock starts when the business associate receives the request.

Covered entities may not charge individuals for access through internet-based methods such as portals, APIs, or apps, or for media or postage on electronic copies, and those that charge for other copies must post their fee schedules on their websites.

Covered entities also may not impose unreasonable identity verification measures, such as requiring notarization or a wet signature where an electronic signature would be valid, which may impede individuals from exercising their rights. For example, OCR would consider it unreasonable for a covered entity participating in the Trusted Exchange Framework and Common Agreement (TEFCA) to refuse a TEFCA request from a personal health application once it has validated an identity token from a credentialed service provider certified to the National Institute of Standards and Technology’s Identity Assurance Level 2 (IAL2) and Authenticator Assurance Level 2 (AAL2) levels and matched the verified demographics to its records. The same is true where the request is sent by a personal health application that connects to Centers for Medicare & Medicaid Services (CMS) Aligned Networks as a participant in the Medicare App Library.

Care Coordination and Notices

Several other changes ease burdens related to disclosures and notices. The Final Rule clarifies that covered entities may disclose PHI without authorization to social services agencies, community-based organizations, home- and community-based services providers, and similar third parties that provide health or human services, for individual-level care coordination, or case management. No BAA is needed where the recipient of the PHI serves on the individual’s behalf. OCR also revised the definition of “health care operations” to confirm that it encompasses all care coordination and case management activities by health plans and covered healthcare providers, whether individual-level or population-based, addressing uncertainty about health plans’ activities and value-based care models.

In addition, providers no longer need to seek written acknowledgment of the Notice of Privacy Practices, although notices need a new header, a statement of the right to discuss the notice with a designated contact, and an email address for that contact.

What This Final Rule Means for Healthcare Companies

The Final Rule’s access changes will significantly affect not only covered entities but also many of their business associates, including EHR developers, patient portal and API platforms, release-of-information vendors, and identity verification services. Companies building patient-facing apps, meanwhile, stand to gain as the Final Rule makes it harder for covered entities and their vendors to block or create obstacles for patients who are routing their records to the apps of their choice.

For covered entities, the time before the compliance date should be used to update records-release workflows to comply with the new 15-day deadline; update their billing practices for internet-based access, media, and postage on electronic copies, and post their fee schedules; revisit their identity verification policies and practices, including notarization, wet-signature, and portal-only requirements, and those of vendors that verify identity on their behalf; and revise their Notices of Privacy Practices and retire their acknowledgment forms. Health plans and value-based care organizations can also rely on the clarified definition of healthcare operations for both individual-level and population-based care coordination.

BAAs that complied with the Privacy Rule as in effect before November 19, 2026 (the Final Rule’s publication date) and were in place before that date are deemed compliant until the earlier of their first renewal or modification on or after the compliance date, or January 18, 2028 (a date fixed in the Final Rule). A BAA renewed or modified between January 19, 2027 (the Final Rule’s effective date) and July 19, 2027 (the Final Rule’s compliance date) loses that protection, and new BAAs entered into on or after November 19, 2026, do not qualify for it; both must conform to the Final Rule by the compliance date. The same rules apply to BAAs between business associates and their subcontractors. The grace period covers only contract terms; starting on the compliance date, a business associate that responds to access requests on a covered entity’s behalf must meet the 15-day deadline, even if its BAA has not been amended. In practice, some business associates will be affected by the Final Rule largely through customer contracts, as covered entities revisit turnaround times, fee practices, and responsibility for responding to individuals.

App developers should confirm whether their products meet the personal health application definition, to determine whether they can take advantage of the new access provisions. A qualifying app is treated as equivalent to the individual, so a request to send records to it is an exercise of the individual’s right to obtain a copy of their PHI, not the right of access to direct, and, according to OCR, the app’s developer is not a business associate with respect to the app. A covered entity must send records to the app at the individual’s request when a copy is readily producible that way. A copy is readily producible through the app, for example, if another federal or state law requires the covered entity to provide access in a particular electronic form and format (such as the patient access APIs CMS requires of certain health plans) and the app can receive records in that form and format, or, according to OCR, if the covered entity already shares electronic PHI with other covered entities through a secure, standards-based API that could also transmit it to the app without increasing security risk.

A non-qualifying app that is not offered by or for another HIPAA-regulated entity is generally treated as a third party designated by the individual under the right of access to direct, where the request meets that right’s requirements (e.g., it is clear, conspicuous, and specific). That right reaches only electronic copies of PHI in an EHR, and the Final Rule does not adopt the proposed fee limit for those copies. And the developer of an app that a covered entity provides to individuals, or that the developer operates on the covered entity’s behalf, is likely a business associate. Further, such an app is not a personal health application.

Wilson Sonsini routinely helps companies navigate complex data, privacy, and healthcare regulatory issues, including issues related to HIPAA. For more information or advice concerning your HIPAA compliance efforts, please contact Jodi Daniel, Tracy Shapiro, Brandon Ge, Hale Melnick, Ty Kayam, or any member of the firm’s Data, Privacy, and Cybersecurity or Healthcare and FDA Regulatory practice.