Faegre Drinker Biddle & Reath LLP, a Delaware limited liability partnership | This website contains attorney advertising.
November 18, 2026

HHS Office of Civil Rights Revises the HIPAA Privacy Rule

Effective on January 18, with compliance required by July 17, 2027

At a Glance

  • The stated purpose is to remove Privacy Rule standards that may impede the transition to value-based care or that impose unnecessary burdens, while continuing to protect the privacy and security of protected health information.
  • We enumerate seven key considerations for covered entities to ensure compliance with the new Final Rule by July 17, 2026.

The US Department of Health and Human Services (HHS) Office for Civil Rights (OCR) has issued a Final Rule modifying the HIPAA Privacy Rule (45 CFR pts. 160, 164), which is scheduled for publication in the Federal Register on November 19, 2026. The rule finalizes a subset of the proposals in the January 2021 Privacy Rule notice of proposed rulemaking (NPRM) (86 Fed. Reg. 6446), together with certain Notice of Privacy Practices (NPP) proposals from the 2022 42 CFR part 2 NPRM. Its stated purpose is to remove Privacy Rule standards that may impede the transition to value-based care by limiting or discouraging individual access, care coordination, and case management, or that impose unnecessary burdens, while continuing to protect the privacy and security of protected health information (PHI).

The Final Rule will be effective on January 18, 2027. Compliance with the Final Rule is required by July 17, 2027.

The principal changes include:

  • Right of access: Covered Entities and their Business Associates will have a 15-calendar-day response deadline (down from 30), with one 30-calendar-day extension, for providing individuals with access to PHI in a designated record set.

    Additional changes affecting the right of access include new definitions of "electronic health record" and "personal health application"; clarified form-and-format rules; limits on burdensome access-request and identity-verification measures; codification of the narrower, Ciox-compliant "right of access to direct"; a revised fee structure (free inspection and free internet-based access); and a required public fee schedule.
  • Care coordination: HHS revised the punctuation in the definition of "health care operations" to confirm it covers individual-level care coordination and case management, and included a new express permission (45 CFR § 164.506(c)(6)) to disclose PHI to social service agencies, community-based organizations, home- and community-based services (HCBS) providers, and similar third parties.
  • Notice of Privacy Practices: The Final Rule eliminates the written acknowledgment requirement for NPPs. It also includes a new requirement granting individuals the right to discuss the NPP with a designated person or office. It also requires a revised header and content to the NPP, and removal of the inmate exception.
  • Other: Telecommunications relay services (TRS) providers are excluded from the definition of business associate, and disclosures are permitted without authorization to TRS communications assistants. In addition, the Armed Forces permission is expanded to all Uniformed Services (adding the US Public Health Service (USPHS) and National Oceanic and Atmospheric Administration (NOAA) Commissioned Corps). Any required revisions to business associate agreements must be made by January 18, 2028.

HHS declined to finalize several significant 2021 proposals, including the exception to the minimum necessary standard for care coordination, the "good faith" standard for disclosures to family and caregivers, the "serious and reasonably foreseeable" threat standard, the expanded right to inspect, the provider-to-provider "Requestor-Recipient" access pathway, mandatory acceptance of oral requests to direct, and individualized fee estimates and itemized statements.

Summary of Finalized Changes and Rationale

New Definitions (45 CFR § 164.501)

Electronic Health Record

The Final Rule revises the definition of electronic health record (EHR) to include "an electronic record of health-related information on an individual that is created, gathered, managed, and consulted by authorized health care clinicians and staff."

  • "Clinicians" include providers with direct or indirect treatment relationships.
  • "Health-related information on an individual" covers the same scope as individually identifiable health information.

In a change from the NPRM, the final definition covers indirect treatment providers (e.g., durable medical equipment (DME) suppliers, device providers, clinical laboratories). The term is not tied to any particular system. It includes billing and other nonclinical information and can include records a business associate maintains for the covered entity.

The HITECH Act right of access to direct applies to PHI "in an electronic health record," but the Privacy Rule never defined the term. HHS adopted the statutory definition to clarify the scope of that right. It added indirect treatment providers because commenters showed that such providers do not always pass all of their data to the ordering provider, and leaving them out would have limited the PHI that individuals can direct and created uncertainty where direct and indirect providers share a record.

Personal Health Application

The Final Rule defines a personal health app as "an electronic application an individual uses to access health information about that individual, which can be drawn from multiple sources, if the information is managed, shared, and controlled by or primarily for the individual, and not by or primarily for a covered entity or another person."

A request to receive a copy through a personal health app is treated as an exercise of the right to obtain a copy, not the right of access to direct.

Timeliness and Manner of Access Requests (45 CFR § 164.524(b), (c)(3))

  • Covered entities must provide access "as soon as practicable," and no later than 15 calendar days after receiving the request (previously 30 days). One extension of up to 30 calendar days is allowed if the individual is told in writing, within the initial 15 calendar days, the reasons for the delay and the expected completion date. The NPRM had proposed a 15-day extension.
  • If other federal or state law requires access in fewer than 15 calendar days, the shorter period is deemed "practicable." A failure to meet the timing requirements of that other law may therefore also violate the Privacy Rule.
  • The same timelines apply to the right of access to direct (new § 164.524(d)(5)).
  • The clock starts on receipt of the request, including receipt by a business associate responsible for responding. Discussions about scope or format, identity verification, obtaining missing information, and coordinating with business associates do not stop the clock.
  • "In writing" means the request itself documents the individual's exercise of the right. This can be a letter, email, portal message, secure message, or a transmission from a personal health app, including through a TEFCA QHIN or CMS Aligned Networks.
  • New § 164.524(b)(1)(iii) prohibits measures that impede access when a less burdensome measure is practicable for the entity (e.g., accepting requests only on paper, only in person, or only through a portal).

HHS points to continuing barriers and delays in access (right of access was among the top five issues in HIPAA complaints resolved in 2024), state laws already requiring faster access, patient expectations of immediate electronic access, and existing CMS API timelines (for example, one business day for plan Patient Access APIs). Allowing a 30 calendar day extension instead of the proposed 15 days responds to commenter concerns about archived paper records and small, state, and Tribal entities. HHS concluded that the benefits to individuals outweigh the remaining burden.

HHS did not adopt the proposed requirement for a written policy prioritizing urgent requests, finding that entities already prioritize urgent requests and that the policy could push individuals to disclose why a request is urgent. HHS also cautions that responding within 15 calendar days may still be information blocking if a practice causes unnecessary delay, and says it plans future rulemaking on shorter deadlines for electronic copies.

Form and Format; Summaries (45 CFR § 164.524(c)(2))

  • New § 164.524(c)(2)(iii): If other federal or state law requires access in a particular electronic form and format, that form and format is deemed "readily producible."
  • PHI is also readily producible in a form and format the entity already makes available to others (e.g., other covered entities) when doing so poses no greater security risk. A secure, standards-based API that can transmit PHI to a personal health app is an example. The rule does not require entities to adopt new technology.
  • New § 164.524(c)(2)(iv)(B) and (d)(4)(ii): When an entity offers a summary instead of a copy, it must tell the individual that they keep the right to the copy (or to direct it). This does not apply when the summary is offered as part of a denial.

HHS determined that aligning the Privacy Rule with other applicable laws supports access and care coordination, reduces burden, and makes covered entities' obligations clearer. HHS considered limiting the deeming rule to federal law only but rejected that approach as confusing for entities operating in multiple states.

Right of Access to Direct (New 45 CFR § 164.524(d))

  • The right to direct a covered entity to send PHI to a designated person is limited to electronic copies of PHI that are both in an electronic health record and in a designated record set. Paper records and PHI outside an electronic health record now require a valid authorization or another permission.
  • The request must be "clear, conspicuous, and specific," and the entity may require it in writing. HHS did not finalize the proposal to require covered entities to accept oral requests; they may accept a qualifying verbal request but are not required to.
  • The right applies to any covered entity subject to the right of access that has an electronic health record (not only providers). It mirrors the general right's exclusions, denial grounds, and timelines. "Third party" is replaced with "a person designated by the individual."
  • A HIPAA authorization may not be required to exercise the right, and an entity may not deny a request because it disagrees with the designee (e.g., an attorney) or the purpose.

In Ciox Health, LLC v. Azar, 435 F. Supp. 3d 30 (D.D.C. 2020), the court vacated the 2013 Omnibus Rule's extension of the right to all PHI in any format. HHS determined that it must implement HITECH section 13405(e) consistently with that decision and has not enforced the broader right since. HHS dropped oral requests because they would be hard to verify and could cause misdirected disclosures and breaches. HHS acknowledges that individuals may now need both an access request and an authorization to send a complete record, but it cites improved clarity for covered entities.

Access Fees and Fee Schedule (45 CFR § 164.524(c)(4); New § 164.525)

  • A reasonable, cost-based fee may include only (A) labor for copying (paper or electronic); (B) supplies for nonelectronic copies; (C) postage for mailed nonelectronic copies or summaries; and (D) preparing an agreed-upon summary or explanation. Electronic media and postage for electronic copies may not be charged.
  • No fee may be charged for (1) inspection or (2) access to ePHI through an internet-based method (e.g., View, Download, and Transmit (VDT) in a portal or a personal health app connected to a certified or standards-based API). "Internet-based method" means automated processes; emailing a manually prepared PDF is not included.
  • The rule supersedes the 2016 guidance's three fee methods (actual, average, or a $6.50 flat fee). The permitted fee is a ceiling, and more stringent state law still applies.
  • HHS did not address fees for the right of access to direct.
  • New § 164.525: Covered entities must post a fee schedule on their website (if they have one) and make it available at the point of service. The schedule must identify free-access options and standard fees for copies under the right of access, the right of access to direct, and authorizations. HHS did not finalize the proposed individualized estimates and itemized statements.

The fee changes rest on a plain reading of HITECH section 13405(e) and on HHS's view that inspection and automated electronic access cost covered entities little or nothing. They also align with the information blocking Fees Exception. HHS cites a 2018 US Government Accountability Office report finding that high fees deter access, and it encourages covered entities to consider individuals' financial circumstances, including for public-benefits applications. Requiring a fee schedule supports price transparency, reduces surprise charges, and encourages compliance through public disclosure. HHS dropped individualized estimates and itemized statements as too burdensome. HHS also states that access may not be withheld because an individual has unpaid bills.

Business Associate Disclosures for Access (45 CFR § 164.502(a)(4)(ii))

The Final Rule clarifies that a business associate must provide PHI to the covered entity or, when the business associate agreement (BAA) specifies, directly to the individual or the individual's designee, as necessary to satisfy the covered entity's access obligations. HHS describes this as a codification of its longstanding interpretation. BAAs should specify which party responds, and the covered entity remains ultimately responsible. BAA restrictions may also raise information-blocking issues.

Identity Verification (New 45 CFR § 164.514(h)(2)(v))

Covered entities may not impose unreasonable verification measures that impede an individual's exercise of a Privacy Rule right. An unreasonable measure is one that causes unnecessary effort or resources when a less burdensome measure is practicable, taking into account technical capabilities, Privacy and Security Rule obligations, and cost. The preamble gives a nonexhaustive list of examples of unreasonable measures, including: requiring in-person proof of identity when remote verification is practicable; requiring "wet" signatures when e-signatures are valid; requiring notarization; and refusing TEFCA or CMS Aligned Networks requests from personal health apps backed by an IAL2/AAL2-certified credential token whose demographics match the record.

HHS continues to receive complaints about burdensome verification measures such as notarization and in-person pickup requirements. It placed the examples in the preamble so they would not be read as exhaustive and would not become outdated as technology changes. The Final Rule does not require entities to relax verification or to fulfill requests they cannot verify.

Health Care Operations and Disclosures to Third Parties for Care Coordination

Definition of Health Care Operations

Commas in paragraph (1) are changed to semicolons so that "case management and care coordination" is a standalone activity and is not limited by "population-based activities." This confirms that the definition covers both individual-level and population-based care coordination by health plans and providers. HHS describes this as a clarification, not a substantive change, made in response to entities that read the definition as limited to population-based activities.

New 45 CFR § 164.506(c)(6)

Covered entities may disclose PHI, without authorization, to social service agencies, community-based organizations, HCBS providers, or 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. The minimum necessary standard still applies where it otherwise would; and Part 2, stricter state law, and the right to request restrictions are unaffected. The permission does not cover law enforcement or child welfare investigations and imposes no new BAA or written-agreement requirement.

HHS has long allowed these disclosures, but entities have been uncertain and have often required authorizations. HHS cites evidence that Health Information Exchange use and care coordination reduce readmissions and costs, and studies showing that fear of violating HIPAA is a common barrier to sharing. Limiting the permission to individual-level activities keeps it consistent with what individuals expect. HHS rejected added conditions (care-plan documentation, screening, consent, or a safe harbor) because they would impede timely coordination.

Notice of Privacy Practices (45 CFR § 164.520)

  • The requirement for direct treatment providers to make a good faith effort to obtain a written acknowledgment of NPP receipt is eliminated, along with the related documentation of efforts and six-year retention. Covered entities must still retain copies of the notices they issue.
  • New § 164.520(b)(1)(iv)(G) gives individuals the right to discuss the NPP with a designated person or office, which may be supported by compliant technology as long as a knowledgeable workforce member is available. The contact person or office, with email address, must be listed.
  • The header is revised to describe how to access health information, how to file a HIPAA complaint, and the individual's rights, including the right to discuss the notice. "Medical" is changed to "Health" to align with the Part 2 Patient Notice.
  • The right-of-access description must explain how to obtain copies at limited cost or free of charge and how to use the right of access to direct. A new optional element can explain alternatives (an authorization, or obtaining the PHI personally) when a request falls outside the right to direct.
  • The inmate exception (former § 164.520(a)(4)) is removed, so correctional institutions that are covered entities must provide the NPP to inmates.

Based on what HHS describes as overwhelming feedback, the acknowledgment requirement imposes burden without meaningful benefit and confuses individuals, some of whom believe they must sign to receive care. HHS considers a designated contact a better way to help individuals understand their rights. The content and inmate changes implement CARES Act section 3221 alignment with the Part 2 Patient Notice, and HHS no longer sees a security risk in providing the NPP to inmates. HHS plans to update its model NPPs before the compliance date.

Telecommunications Relay Services and Uniformed Services

TRS

TRS providers are excluded from the definition of business associate (45 CFR § 160.103, para. (4)(v)). New 45 CFR § 164.512(m) permits covered entities, and business associates regardless of BAA terms, to disclose PHI to TRS communications assistants as necessary to conduct covered functions.

Existing guidance assumed the individual could agree or object at the start of a call, but that assumption does not hold when a workforce member uses TRS. HHS found that requiring BAAs would add burden with little benefit, because TRS providers already have FCC confidentiality obligations. HHS states that the change promotes access to care and employment for people who are deaf, hard of hearing, deaf-blind, or speech-disabled, and supports compliance with disability laws.

Uniformed Services

The 45 CFR § 164.512(k)(1) permission for Armed Forces personnel is extended to all Uniformed Services, adding the USPHS and NOAA Commissioned Corps. Covered components of HHS and Commerce may disclose PHI to the US Department of Veterans Affairs when a member separates.

Commissioned Corps members face medical-readiness and fitness obligations comparable to those of the Armed Forces. The change removes burdens and facilitates care coordination and mission readiness, as requested by the Corps directors.

Business Associate Agreement Transition (45 CFR § 164.532(e))

A written BAA that complied with the HIPAA Rules before the publication date, and is not renewed or modified between the effective date and the compliance date, is deemed compliant until the earlier of (i) renewal or modification on or after the compliance date or (ii) January 18, 2028. Evergreen agreements that roll over automatically qualify. The extension covers only the obligation to amend the BAA. For example, business associates that handle access requests must meet the 15 calendar day deadline starting on the compliance date.

HHS did not propose this change but adopted it in response to comments, recognizing that 240 days may not be enough time to renegotiate BAAs while implementing the rest of the rule.

Key Compliance Considerations

To ensure compliance with the new Final Rule, covered entities must:

  1. Revise right-of-access policies, workflows, and business associate service levels for the 15 calendar day deadline, the new extension notice, and intake through electronic channels, and audit verification practices against the preamble examples.
  2. Map which records fall within the "electronic health record" and designated record set for the right to direct, and update forms to separate access requests from authorizations.
  3. Reprice access requests under the four permitted cost categories, stop charging for internet-based access and inspection, and post a compliant fee schedule.
  4. Revise and repost the NPP (header, right to discuss, contact person or office with email, access description). Stop collecting acknowledgments if desired, and update procedures for correctional settings.
  5. Inventory BAAs to identify those eligible for deemed compliance through January 18, 2028, and address which party responds to access requests.
  6. Update care-coordination disclosure guidance for § 164.506(c)(6), remembering that minimum necessary, Part 2, and stricter state law continue to apply. Note the TRS and Uniformed Services permissions.
  7. Train the workforce before July 17, 2027.
The material contained in this communication is informational, general in nature and does not constitute legal advice. The material contained in this communication should not be relied upon or used without consulting a lawyer to consider your specific circumstances. This communication was published on the date specified and may not include any changes in the topics, laws, rules or regulations covered. Receipt of this communication does not establish an attorney-client relationship. In some jurisdictions, this communication may be considered attorney advertising.