HIPAA Updates 2026: What the Privacy Rule Final Rule Changes

Doctor showing a patient her health records on a tablet during an exam room visit

Table of Contents

Patients’ requests for their own records now come with a 15-day deadline. That is the headline of the HIPAA Privacy Rule final rule HHS released on November 16, 2026, and it applies to covered entities and to the vendors that handle requests for them. Compliance is required by July 19, 2027.

HHS calls the rule burden reduction, and for patients it is. For the team that runs record requests, it halves the clock, makes app-based copies free, and limits the reasons you can give for holding back the app a patient picks.

What does the 2026 HIPAA Privacy Rule final rule change?

The 2026 HIPAA Privacy Rule final rule shortens the deadline to act on patient access requests from 30 to 15 calendar days, makes app-based electronic access free, requires posted fee schedules, drops the signed notice acknowledgment, and expressly permits care coordination disclosures to social services and community organizations. Compliance is required by July 19, 2027.

HHS released the rule on November 16, 2026, and the Federal Register published it on November 19, 2026 as document 2026-23429 (opens in a new tab). It adopts many of the proposals HHS first published in January 2021. The table compares the main obligations before and after the rule.

HIPAA Privacy Rule obligations before and after the 2026 final rule
Obligation Before the final rule Under the final rule
Time to act on an access request 30 calendar days, plus one 30-day extension 15 calendar days, plus one extension of up to 30 days. A shorter federal or state deadline governs.
Fees for access Reasonable, cost-based fee. No posting requirement. No fee for inspection or for electronic access through an internet-based method such as a personal health app. Fee schedule posted on the website.
Identity verification Verify identity, with no express limit on the burden Unreasonable verification measures prohibited
Notice acknowledgment Direct treatment providers make a good-faith effort to get a written acknowledgment Requirement eliminated
Notice content Existing required statements New statement on getting copies at limited cost or free. Right to discuss the notice with a designated contact.
Disclosures to social services and community organizations No express permission Expressly permitted for individual-level care coordination and case management
Existing business associate agreements Not applicable Qualifying agreements deemed compliant until renewal on or after July 19, 2027, or January 18, 2028, whichever comes first

Source: HHS, Federal Register document 2026-23429, 45 CFR 164.514, 164.520, 164.524, 164.525, and 164.532 as amended.

Nearly every row touches the same process: getting a patient’s records out the door, priced correctly, inside the new deadline.

When do the HIPAA Privacy Rule changes take effect?

The rule takes effect January 19, 2027, and covered entities must comply by July 19, 2027, 180 days later.

Existing business associate agreements get more time, with conditions. An agreement qualifies if it was in place before November 19, 2026 and is not renewed or modified between January 19 and July 19, 2027. A qualifying agreement is deemed compliant until it is next renewed or modified on or after July 19, 2027, or until January 18, 2028, whichever comes first.

That extra time covers contract language only. The rule says the transition does not change a covered entity’s duty to meet the access requirements for PHI a business associate holds. A release-of-information vendor working under an old contract still has to hit the new deadline for you from July 19, 2027.

Put all three dates on your HIPAA compliance program calendar now, because six months between the effective date and the compliance date is short for contract, policy, and system changes at once.

Why does a burden-reduction rule add risk to your access process?

The rule adds risk because it shortens the deadline while making requests easier to submit and sending records to more destinations, including apps and people the patient designates.

Under the amended right of access, a covered entity must act on a request as soon as practicable and no later than 15 calendar days after receiving it. If your state already requires faster access, the rule treats that shorter period as the practicable one, so your state timeline may now be your HIPAA timeline too.

Your vendors are on the same clock. When a business associate agreement makes the vendor responsible for responding, HHS says the 15 days start when the vendor receives the request. A week of backlog in a vendor’s intake queue is now half your window.

The rule also limits what you can ask of the patient. Covered entities may not impose unreasonable verification measures, which the rule defines as measures that make an individual spend unnecessary effort or resources. Extra identity steps added to protect the organization now carry compliance risk of their own.

Patients get fewer hoops, and your team gets half the time to work each request.

Can you refuse a patient’s chosen health app under the new rule?

Not for the reason most organizations would give. HHS says a personal health app developer is not acting on a covered entity’s behalf, so it is not a business associate, and a provider may not block an app solely because no business associate agreement exists.

A personal health application, as the rule now defines it, is an electronic application an individual uses to access health information about themselves, where that information is managed, shared, and controlled by or primarily for the individual. Access through an app like that must be free.

HHS goes further in the preamble. Turning down an app’s registration, and with it the patient’s request, may violate the access requirements. You can still require apps to register, as long as the process does not exclude an app that can connect securely to your API. You may also tell the patient about the risks of sending records to an app.

That puts the security question on your side of the connection. HHS notes that HIPAA gives it no authority to set security standards for apps outside HIPAA, and it states that covered entities remain responsible for assessing security risks. The final rule does not require security testing. It does route new traffic through your APIs, portals, and export jobs, and your Security Rule risk analysis should account for those pathways. That obligation is separate from the proposed HIPAA Security Rule update, which is still a proposal and is not part of this final rule.

The patient now largely decides which app gets the records, and you remain accountable for the door it connects through.

What changes in your notice of privacy practices and fee schedule?

Direct treatment providers no longer have to seek a signed acknowledgment of the notice of privacy practices, and every covered entity must revise the notice to explain access rights and post a fee schedule.

The revised notice must tell individuals how to get copies of their records at limited cost or, in some cases, free of charge. It must also tell them they can discuss the notice with a designated contact person or office. The old exclusion that kept inmates of correctional institutions from receiving a notice is gone.

The fee schedule is new. A covered entity with a website must post it there and make it available at the point of service and on request. It must list every type of access available free of charge and the standard fees for access copies and for copies disclosed under a patient’s authorization.

A posted fee schedule is a public commitment, so it has to match what your release-of-information vendor actually charges.

Do disclosures to social services and community organizations need a business associate agreement?

Usually not. The rule permits covered entities to disclose PHI to social services agencies, community-based organizations, home and community-based services providers, and similar third parties for individual-level care coordination and case management. A recipient that is not performing a function on your behalf is not a business associate.

The permission is optional, and health plans also get express authority to use and disclose PHI for population-based and individual care coordination as health care operations. Without a contract, your own procedure does the protecting: who can approve a disclosure, what information goes out, and how it is documented.

Fewer contracts means your internal disclosure procedure has to carry more of the safeguards.

HIPAA updates 2026 checklist: what to finish before July 19, 2027

Use the months before January 19, 2027 to map your current process, then use the six months that follow to change policies, contracts, notices, and systems. This HIPAA compliance checklist groups each task by the date it supports.

Phase 1 of 3

Before January 19, 2027: map and measure

  • Map every channel where access requests arrive (portal, mail, fax, email, phone, vendors) and time each step. Evidence it is done: Intake map with an owner and turnaround for each channel
  • Measure the past year of requests against a 15-day standard. Evidence it is done: Baseline showing how many requests would have missed
  • Inventory business associate agreements and flag any renewing or changing between January 19 and July 19, 2027. Evidence it is done: Agreement register with transition status for each contract
  • Inventory the APIs, portals, and export jobs that send electronic PHI to apps and third parties. Evidence it is done: Data-flow diagram of each pathway

Phase 2 of 3

By July 19, 2027: change policies, contracts, notices, and systems

  • Rewrite the access policy for 15 days, one extension of up to 30 days, and any shorter state deadline. Evidence it is done: Approved policy and updated request tracking
  • Set turnaround terms with every vendor that responds to requests for you. Evidence it is done: Amended agreement or written service level
  • Remove business associate agreement demands and other blocks on personal health apps. Document registration criteria and a patient risk notice. Evidence it is done: App registration standard and notice script
  • Set a zero fee for inspection and internet-based electronic access, and post the fee schedule. Evidence it is done: Live fee schedule on the website and at the point of service
  • Remove identity verification steps that make patients spend unnecessary effort. Evidence it is done: Revised verification procedure
  • Revise the notice of privacy practices, name the designated contact, and retire the acknowledgment step. Evidence it is done: Updated notice posted and intake forms revised
  • Write a procedure for care coordination disclosures to social services and community organizations. Evidence it is done: Approved procedure with approvers named
  • Update the Security Rule risk analysis to cover new app, API, and export pathways. Evidence it is done: Updated risk analysis
  • Train release-of-information, front desk, and privacy staff. Evidence it is done: Training records

Phase 3 of 3

By January 18, 2028: close out the contract transition

  • Move every remaining legacy business associate agreement onto updated terms. Evidence it is done: Register shows no agreement still relying on the transition

A HIPAA risk and compliance assessment covers the first phase in one pass. TestPros maps the access workflow end to end, tests it against the 15-day clock, reviews your notice, fee schedule, and business associate agreements, and reviews the security of the app and data-sharing pathways.

TestPros is an independent data privacy assessment firm and sells no software, so our findings are about your process, not a product.

Teams that finish discovery before January 19, 2027 have two full quarters to fix what they find.

Compliance date: July 19, 2027

Test your access workflow against the 15-day clock before the rule takes effect.

The HIPAA Privacy Rule final rule takes effect January 19, 2027. TestPros runs an independent gap assessment of your right-of-access workflow, notice of privacy practices, fee schedule, and business associate agreements, plus a security review of the app and data-sharing pathways the rule opens. Starting now leaves six full months to fix gaps before compliance is due.

Book a HIPAA Privacy Rule gap assessment

Frequently asked questions

Is the 2026 HIPAA Privacy Rule final rule the same as the HIPAA Security Rule update?

No. The final rule HHS released on November 16, 2026 amends the Privacy Rule: access rights, fees, the notice of privacy practices, and care coordination disclosures. The HIPAA Security Rule update HHS proposed in January 2025 is a separate rulemaking and is still a proposed rule. The current Security Rule stays in force, including its risk analysis requirement. Because the Privacy Rule changes route more electronic PHI through APIs and personal health apps, those pathways belong in your existing risk analysis, even though the final rule does not require new security testing.

Do business associates have to meet the 15-day access deadline?

Yes, when the business associate agreement makes the vendor responsible for responding to access requests. In that case, HHS says the 15 calendar days start when the business associate receives the request. The covered entity stays responsible for timely access to PHI its business associates hold, even when an older agreement qualifies for the transition period under 45 CFR 164.532(e). Release-of-information vendors and other partners that handle requests should have their intake and turnaround measured against the new deadline well before July 19, 2027.

Can a covered entity charge for records sent to a personal health app?

No. Under amended 45 CFR 164.524(c)(4), a covered entity may not charge a fee when an individual inspects their PHI or accesses electronic PHI through an internet-based method such as a personal health application. Reasonable, cost-based fees remain allowed for other copies. A covered entity with a website must post a fee schedule listing every free form of access and the standard fees for access copies and for copies disclosed under an authorization, and must make it available at the point of service and on request.

Do existing business associate agreements have to be updated by July 19, 2027?

Not always. An agreement in place before November 19, 2026 that is not renewed or modified between January 19 and July 19, 2027 is deemed compliant until the earlier of its next renewal or modification on or after July 19, 2027, or January 18, 2028. An agreement renewed or modified inside that window does not qualify, so update its terms during the renewal. The transition covers contract terms only, and the covered entity must still meet the access rules for PHI the business associate holds. TestPros reviews agreements against these dates as part of a HIPAA gap assessment.

Sources

SHARING IS CARING
What Challenges
Are You Facing?

Recent Posts