Skip to Main Content
Publications

HIPAA's New 15-Day Clock: Action Plans for Covered Entities and Business Associates

The U.S. Department of Health and Human Services (HHS) Office for Civil Rights (OCR) has issued its long-awaited final rule, Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule: Changes to Support Coordinated Care and Individual Engagement and Reduce Regulatory Burdens (the Final Rule), which OCR announced on November 16, 2026. The Final Rule applies to covered entities (health plans, health care clearinghouses, and most health care providers) and to their business associates (vendors and others that handle protected health information (PHI) on a covered entity's behalf under a business associate agreement (BAA)). The Final Rule strengthens the individual right of access, including access to electronic PHI (ePHI) through personal health applications. At the same time, the Final Rule eases several administrative requirements. Health care providers no longer need to make a good faith effort to obtain a written acknowledgment of the Notice of Privacy Practices (NPP) as part of their intake paperwork. The Final Rule also expands permissible information sharing for care coordination. The access changes impose shorter deadlines, new fee limitations, website posting obligations, and new NPP content, each of which will require operational, technical, and contractual work before the compliance date. The central takeaway: This is both an access-expansion rule and a workflow-redesign rule.

Key Dates

The Final Rule is scheduled for Federal Register publication on November 19, 2026. It takes effect 60 days later, on January 18, 2027. Regulated entities must comply with most provisions by July 17, 2027, which is 180 days after the effective date. Under revised 45 CFR 164.532(e), a written BAA qualifies for a transition period if it was in place and compliant with the prior rules before November 19, 2026, and is not renewed or modified between January 18, 2027, and July 17, 2027. A qualifying BAA is deemed compliant until the earlier of (1) its renewal or modification on or after July 17, 2027, or (2) January 18, 2028. A BAA that renews automatically with no change in terms remains eligible, but verbal arrangements do not qualify. The transition applies only to the requirement to amend BAAs, not to any other compliance obligation. If the publication date shifts, the effective and compliance dates shift with it.

Strengthened Individual Right of Access

Response time cut in half. Covered entities must act on an access request as soon as practicable, and no later than 15 calendar days after receipt, compared with 30 days historically. One extension of up to 30 calendar days remains available, but the written explanation and expected completion date must be provided within the initial 15 days. Where another federal or state law requires access in fewer than 15 days, the Final Rule deems that shorter period practicable, so it must be met (with the existing HIPAA preemption analysis). The same 15-day standard applies when an individual directs an electronic copy of PHI in an electronic health record (EHR) to a third party.

Access through personal health apps. The right of access now expressly includes obtaining a copy of ePHI to or through a personal health app when the copy is readily producible that way. The Final Rule adds definitions of "electronic health record" and "personal health application," the latter being an app the individual uses to access their own health information that is managed, shared, and controlled by or primarily for the individual, not by or primarily for a covered entity. HHS explains that an app supplied to a participant but managed primarily for an organization, such as a clinical trial sponsor, falls outside the definition. Many individuals use apps with limited security controls, and while that is a concern to consider, it cannot be a barrier: A covered entity may not deny access because it doubts an app will protect the data.

Right to direct narrowed. Consistent with the Health Information Technology for Economic and Clinical Health (HITECH) Act and Ciox Health, LLC v. Azar (D.D.C. 2020), an individual's right to direct PHI to a third party is limited to electronic copies of PHI in an EHR. The individual's own right to inspect and obtain copies still extends to the full Designated Record Set (as defined in the Privacy Rule). As a practical matter, we generally advise against offering a summary in lieu of a copy. When a covered entity does offer a summary, it must tell the individual that they retain the right to the copy.

Fees, fee schedules, and identity verification. A reasonable, cost-based fee remains permitted for copies, but the Final Rule bars fees where a covered entity is unlikely to incur costs. No fee may be charged for inspection or when an individual accesses ePHI through an internet-based method, such as a personal health app, a patient portal's view-download-transmit function, or an application programming interface (API), regardless of how the request is made. HHS explains that an online request for a copy that still requires workforce labor, mailing, or media is not, by itself, in the free category. A covered entity that charges for copies must post a fee schedule on its website, if it has one, and make it available at the point of service and on request. The schedule must list free access options and standard fees for copies under the right of access, directed copies, and authorizations. OCR did not adopt the proposed individualized estimates and itemized bills. The Final Rule also prohibits unreasonable identity verification measures, meaning those that cause an individual to spend unnecessary effort or resources when a less burdensome measure is practicable, taking into account the covered entity's technical capabilities, its privacy and security obligations, and cost.

Implications for Digital Health

The Final Rule makes personal health apps a formal part of the HIPAA access framework. For covered entities, the obligation turns on whether a copy is "readily producible" through an app. HHS treats a copy as readily producible in three situations: (1) other federal or state law requires access in that electronic format; (2) the covered entity has chosen to implement the enabling technology, such as a secure, standards-based API, or participates in TEFCA or the Centers for Medicare & Medicaid Services (CMS) Aligned Networks; or (3) the covered entity already makes the PHI available to others in that format at no greater security risk. In those cases, the covered entity must send the copy through the individual's app, without a fee. The Final Rule does not require covered entities to build an app or adopt an API, and no BAA is needed before sending records to a personal health app. Covered entities may limit app connections that pose an unacceptable risk to their own systems, as shown by their Security Rule risk analysis, but not because of concerns about what the app will do with the data. HHS also cautions that, for entities subject to the information blocking regulations, a delay can count as interference even within the 15-day deadline. We will address the Final Rule's implications for app developers and other digital health companies, including the personal health app definition, business associate status, and other privacy laws that may apply, in a separate alert.

Operationally, covered entities should be prepared to accept access requests through any channel they can practicably support, such as a portal, personal health app, or health information network, and to make sure app registration processes do not screen out secure apps, require a BAA, or delay the 15-day clock. Release-of-information (ROI) and health information management (HIM) teams will also need to sort requests into three categories: a request to send records to a personal health app is a standard access request; a request to send an electronic copy from an EHR to another app or third party is a request to direct; and a request to send paper copies or non-EHR records to a third party is treated as an authorization request. HHS calls 15 days an outer limit and notes that app-based access may be almost instantaneous, so workflows built for paper, portals, and a 30-day clock will likely need to be redesigned, and outsourced ROI arrangements renegotiated.

Identity verification. Verification remains permissible, but HHS's examples set the outer bounds. Requiring notarization, wet signatures, or in-person proof is unreasonable when remote verification is practicable, as is refusing a TEFCA request, or a request through the CMS Aligned Networks from a Medicare App Library app, that is supported by a validated identity token and a demographic match. Covered entities should test each existing check against these examples rather than assuming all survive or all are prohibited.

Implications for Business Associate Agreements

The shorter deadline turns access into an end-to-end operations problem. Covered entities should map each stage of the access process (intake, identity checks, record collection, fee communications, delivery, and escalation) against the 15-day clock to find where time is lost. Many BAAs were drafted around the old 30-day outer limit and give vendors turnaround times that will leave the covered entity little or no time to comply. Business associate arrangements should be reviewed alongside the Final Rule's contract-transition provisions for access turnaround times, fee pass-through and fee schedule provisions, cooperation on app-based and directed-access requests, and identity verification practices. The BAA transition period provides contractual relief only; business associates must still comply operationally by July 17, 2027.

Telecommunications Relay Services (TRS) arrangements can also be removed from BAA inventories. HHS previously took the position in guidance that TRS providers were not business associates, reasoning that individuals could agree or object to the communications assistant at the start of a call. HHS now recognizes that this reasoning no longer holds. TRS connections are often seamless, so the other party may not know a communications assistant is involved, and TRS is increasingly used by deaf, hard of hearing, deaf-blind, or speech-disabled workforce members, not just patients. The Final Rule therefore excludes TRS providers from the business associate definition, with respect to enabling communications through Federal Communications Commission (FCC)-regulated relay services, and expressly permits both covered entities and business associates to disclose PHI to TRS communications assistants as necessary to conduct covered functions, regardless of what their BAAs say. TRS providers remain subject to FCC confidentiality standards for relayed communications. Because the exclusion is limited to relay services, any other services a TRS provider performs that involve PHI should still be evaluated for business associate status.

Care Coordination and Reduced Regulatory Burdens

The Final Rule clarifies, rather than expands, covered entities' ability to share PHI for care coordination. The definition of "health care operations" now confirms that it covers all care coordination and case management by health plans and covered health care providers, whether individual-level or population-based. A new express permission allows covered entities to disclose PHI, without authorization, to social services agencies, community-based organizations, Medicaid home and community-based services (HCBS) providers, and similar third parties that provide health or human services to specific individuals, for individual-level care coordination and case management that constitutes treatment or health care operations.

HHS describes both changes as confirming what the Privacy Rule already permitted, so organizations that have been requiring authorizations for these disclosures may be able to drop them. HHS gives several examples. A provider may share information with a social service agency that arranges housing and day programs for a patient leaving a long-term care facility, with a community-based organization that provides transportation and nutrition services, or with a food bank that needs to accommodate a patient's diabetes. A health plan may share information with a senior wellness center that runs a plan wellness program. Important limits remain. HHS declined to finalize its proposed exception to the minimum necessary standard, so disclosures to non-provider third parties, and all health care operations disclosures, must be limited to the minimum necessary PHI. The permission does not authorize disclosures to law enforcement or child welfare agencies for investigatory purposes, and it does not override stricter state laws or 42 CFR Part 2 consent requirements for substance use disorder records. Disclosures should also be consistent with the covered entity's NPP.

At the same time, HHS declined to require consent, care plans, screening, data-sharing agreements, or recipient privacy and security vetting, and it stated that a covered entity is not liable for a recipient's later misuse or breach of the information. A business associate agreement is needed only if the recipient is acting on the covered entity's behalf. Because the permission is tied to the care of a specific individual, it should not be read as authority for unrelated commercialization, research, or artificial intelligence (AI) model development; that is a scope-based reading of the permission HHS describes.

Separately, providers with direct treatment relationships no longer must make a good faith effort to obtain written acknowledgment of NPP receipt, and NPP content must explain individuals' rights, including a new right to discuss the notice with a designated contact person or office. The exception that denied NPPs to inmates of correctional institutions is also removed. The NPP revision, removal of the acknowledgment requirement, fee changes, and website fee disclosures should be handled as one coordinated update to notices, forms, and fees, not just a revised privacy notice. The Armed Forces disclosure permission now covers all Uniformed Services, adding the U.S. Public Health Service and National Oceanic and Atmospheric Administration Commissioned Corps.

Action Items for Covered Entities

  1. Map intake, identity checks, record collection, fee communications, delivery, and escalation against the 15-day standard, including directed electronic copies; set up a process to sort requests into access, right-to-direct, and authorization categories; and build tracking for extensions and timely written notice.
     
  2. Update right of access policies and test existing identity verification and app registration practices against HHS's examples to determine which remain permissible.
     
  3. Treat the NPP revision, removal of the acknowledgment requirement, fee changes, and website fee-schedule disclosures as one coordinated update to notices, forms, and fees, identifying no-fee scenarios along the way.
     
  4. Assess personal health app and API readiness with IT and EHR vendors, document security-based limitations, and coordinate with your information blocking compliance program.
     
  5. Review  business associate arrangements alongside the Final Rule's contract-transition provisions, confirm which agreements qualify for the transition period, and update BAA templates.
     
  6. Coordinate the NPP update with the Part 2-related NPP changes that took effect February 16, 2026, and redistribute the revised notice.
     
  7. Revisit referral pathways with social-service and community partners, drop authorization requirements the Privacy Rule does not impose, apply the minimum necessary standard, confirm whether any recipient is acting as a business associate, and limit these disclosures to individual-level care coordination and case management rather than commercialization, research, or AI model development. HHS did not require recipient vetting or data-sharing agreements, although organizations may choose to use them.
     
  8. Train health information management, front-desk, call center, and privacy staff on the new timelines, fee rules, and verification limits before July 17, 2027.

Action Items for Business Associates

  1. Identify every BAA under which you handle access requests, and measure your turnaround times against what covered entities will need to meet the 15-day standard.
     
  2. Prepare for BAA renegotiation on response deadlines, fee pass-through and fee schedules, and cooperation on app-based and directed-access requests, and confirm which agreements fall within the transition period.
     
  3. Update access fees and billing so no fee is charged where the Final Rule prohibits one, including app-based delivery.
     
  4. EHR, portal, and API vendors should confirm their platforms can deliver copies to personal health apps and directed electronic copies within the new timelines.
     
  5. Align identity verification procedures with the new limits on unreasonable measures, and train staff before July 17, 2027. The BAA transition period does not delay these operational obligations.

For more information or assistance on this topic, please contact Layna Cook Rush, Alisa L. Chestler, Alexandra P. Moylan, or any member of Baker Donelson's Health Law or Data Privacy and Cybersecurity team.

Email Disclaimer

NOTICE: The mailing of this email is not intended to create, and receipt of it does not constitute an attorney-client relationship. Anything that you send to anyone at our Firm will not be confidential or privileged unless we have agreed to represent you. If you send this email, you confirm that you have read and understand this notice.
Cancel Accept