The 2026 HIPAA Privacy Rule final rule: every change practices need to make
HHS finalized a 15-day HIPAA access deadline, record-fee limits, NPP changes and app rules. What changed, what didn't, and when each part binds.
Written and reviewed by the Patient Protect team — Joseph A. Perrin, CTO (federal infrastructure background, platform security architect), Angie Perrin, CSO (CHPC, 10+ years clinical practice), and Alexander Perrin, CEO (20 years enterprise SaaS, primary author of the Secure Care Research Institute research program). See editorial standards.

The short version
The rule is called HIPAA Privacy Rule: Changes to Support Coordinated Care and Individual Engagement and Reduce Regulatory Burdens. It finishes a rulemaking HHS proposed in January 2021, and it is a Privacy Rule change only. It does not finalize anything from the separate HIPAA Security Rule proposal published in January 2025.
For an independent practice, the changes that carry real work are these:
- Access requests: 15 calendar days. Act as soon as practicable and no later than 15 calendar days after receipt, with one extension of up to 30 calendar days. A shorter state deadline becomes your deadline.
- Clarifying a request does not pause the clock. Neither does verifying identity. The time spent doing either sits inside the 15 days.
- Some access must now be free. Inspection, and access to electronic records by an internet-based method such as a portal or a patient's app, cannot carry a fee. Copies made by staff, paper or electronic, can still carry a reasonable labor fee.
- A published fee schedule, for practices that charge anything for copies: on the website if there is one, at the front desk, and on request.
- A revised Notice of Privacy Practices with a new required header, a right to discuss the notice with a designated contact, and an email address for that contact.
- No more acknowledgment signatures. The good-faith effort to get a signed acknowledgment of the notice is removed. The notice itself is not.
- Identity checks that do not get in the way. Notarization, in-person-only verification and wet signatures are named by HHS as unreasonable where a lighter check is practicable.
- Vendors do not take the obligation away. Whoever holds the records, the practice stays responsible for getting them to the patient on time.
And several things that were proposed in 2021 did not make it. There is no minimum-necessary exception for care coordination, no "good faith" standard replacing professional judgment, no change to the "serious and imminent threat" standard, no requirement for individualized fee estimates and no duty for providers to forward each other's access requests. The full list is below.
What HHS finalized, and when
HHS's Office for Civil Rights announced the final rule on November 16, 2026, and filed it for public inspection with the Federal Register that afternoon as document 2026-23429. It runs to 363 pages, much of it HHS's responses to the comments it received on the proposal.
HHS published the proposal on January 21, 2021, at 86 FR 6446. The final rule keeps some of it, changes some of it, and drops a good deal of it. That gap between proposal and final rule is the main reason to read past the headlines. A policy written to the 2021 version would be wrong in several places, and wrong in the direction of disclosing more than the rule allows.
Two other recent rulemakings sit beside this one and should not be confused with it. The 2024 reproductive-health Privacy Rule was largely vacated by a federal court in June 2025 in Purl v. HHS; the court left standing the Notice of Privacy Practices changes tied to 42 CFR Part 2, which carried their own February 16, 2026 compliance date, and this final rule says those provisions "remain in effect." The January 2025 Security Rule proposal remains a proposal. Our regulatory updates tracker keeps all three in one place.
Effective date, compliance date, and what applies today
The rule has two dates, both counted from Federal Register publication, which is scheduled for November 19, 2026.
- The effective date is 60 days after publication. That is when the amended regulatory text takes effect.
- The compliance date is 240 days after publication, which is 180 days after the effective date. This is the date the new requirements bind.
HHS is explicit about the window between them: "Regulated entities are permitted to comply earlier than the compliance date, but the Department will not take action against them for noncompliance with the finalized requirements that occur before the compliance date." Our reading: keep meeting today's 30-day deadline, fee rules and notice requirements until the compliance date.
November 16, 2026 (announced)
HHS announces the final rule
Filed for public inspection as Federal Register document 2026-23429.
November 19, 2026 (projected)
Scheduled Federal Register publication
Publication starts both clocks below.
January 18, 2027 (projected)
Effective date
60 days after publication. The amended regulatory text takes effect.
July 17, 2027 (projected)
Compliance date
240 days after publication. The 15-day access deadline, fee rules, fee schedule and new notice content bind from here. HHS will not act on noncompliance with them before this date.
January 18, 2028 (fixed in the rule)
Business associate transition ends
The latest date a qualifying pre-existing agreement can rely on the transition period.
The rule does not separately say when a requirement it removes stops applying, or when a permission it adds becomes available. Our reading is that both follow the effective date, because that is when the regulatory text containing them, or no longer containing them, takes effect. Where that matters, we say what we would do. For the signed NPP acknowledgment, for example, continuing to collect it until you are sure is never a violation; the rule expressly does not prevent it.
One date is fixed in the text itself rather than counted from publication. A qualifying existing business associate agreement can rely on the transition period no later than January 18, 2028. More on that below.
Every change at a glance
| Change | Rule today | Final rule | What a practice does | Applies from |
|---|---|---|---|---|
| 15-calendar-day access deadline45 CFR 164.524(b)(2) | Act on an access request no later than 30 calendar days after receipt. | Act as soon as practicable, but no later than 15 calendar days after receipt. | Rebuild the request workflow so a request can be logged, assigned, verified, located, produced and sent inside 15 days, including records held by vendors and in archives. | Compliance date |
| One extension of up to 30 calendar days45 CFR 164.524(b)(2)(ii) | One 30-day extension, with written notice inside the first 30 days. | One extension of no more than 30 calendar days, with a written statement of the reason and completion date sent inside the first 15 days. | Make the extension notice a step with a date on it. It has to go out by day 15, and there is only one per request. | Compliance date |
| Faster state or federal law sets the clock45 CFR 164.524(b)(2)(iii) | A shorter state deadline already applied alongside HIPAA, but HIPAA did not say so. | Where another law requires access in less than 15 calendar days, that shorter period is deemed practicable. | Check your state's records-access deadline. If it is shorter, it is your HIPAA deadline too. | Compliance date |
| Clarifying a request does not stop the clock45 CFR 164.524(c)(3) | Silent on whether back-and-forth with the patient extended the deadline. | A practice may discuss scope and format with the individual, but that discussion does not extend the time allowed. | Start the clock at receipt, by whichever channel it arrived, and treat clarification and identity checks as time spent inside the 15 days. | Compliance date |
| No unnecessary barriers to making a request45 CFR 164.524(b)(1)(ii)-(iii) | A practice could require written requests. | A practice may still require requests in writing, but writing includes electronic submissions, and it may not impose a request measure when a less burdensome, practicable one exists. | Accept requests by the channels you can practicably handle, not only one form or one portal, and say what they are. | Compliance date |
| Personal health applications defined45 CFR 164.501; 164.524(c)(3) | No definition. Delivery to an app was discussed in guidance only. | A defined term, and the rule names transmission to or through the individual's personal health application as a way to provide access when a copy is readily producible that way. | Know which of your systems can deliver to a patient's app, and train the front desk to tell a patient's app request apart from a vendor's. | Compliance date |
| No new technology required to serve appsPreamble to 45 CFR 164.524(c) | Readily producible form and format applied, without app-specific language. | App delivery is required when a copy is readily producible that way. The rule does not require a practice to buy or build technology, including an API, to gain that ability, but it must be able to produce some electronic copy of PHI it keeps electronically. | Inventory what your EHR and portal can already deliver. Capability you have, or that other law requires you to have, is capability you must use. | Compliance date |
| A patient's own app is not your business associatePreamble to 45 CFR 164.501 | Stated in earlier HHS guidance. | HHS restates that a personal health app chosen by the individual is not acting for the covered entity, while an app built or supplied for a covered entity likely is a business associate. | Classify by function. A patient-selected app needs no BAA from you; a vendor that handles records for you does. | Already HHS's position (restated) |
| App security concerns are not grounds to denyPreamble to 45 CFR 164.524 | Stated in earlier HHS guidance. | A covered entity may not deny access based solely on its concerns about how a patient-chosen app will protect the information. | You may tell a patient what concerns you about an app. You may not make that concern a reason to refuse, and app registration cannot push you past the deadline. | Already HHS's position (restated) |
| When access must be free45 CFR 164.524(c)(4)(ii) | Reasonable, cost-based fees for copies; HHS guidance discouraged charging for electronic access. | No fee for inspection, or for access to ePHI by an internet-based method such as a personal health application. Labor for making other copies, paper or electronic, may still be charged. | Stop charging for portal, API or app access and for inspection. Keep a cost-based labor fee only where staff actually make the copy. | Compliance date |
| No charge for electronic media or its postage45 CFR 164.524(c)(4)(i) | Supplies for the paper copy or electronic media could be charged. | Supplies may be charged only for a non-electronic copy, and postage only for mailing a non-electronic copy or an agreed summary. Copying ePHI onto a CD or USB drive is labor only. | Remove media and mailing charges for electronic copies from your fee list. | Compliance date |
| The 2016 fee methods, including $6.50, are supersededPreamble to 45 CFR 164.524(c)(4) | HHS's 2016 guidance described actual-cost, average-cost and $6.50 flat-fee methods. | The final rule replaces that interpretation and frames the fee provision as a ceiling, not a floor. | Recalculate any fee you justified with the 2016 methods against the new fee rule. | Compliance date |
| Fee schedule for access and authorization copies45 CFR 164.525 (new) | No requirement to publish fees. | 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. | If you charge anything, publish the schedule: what is free, and standard fees for access copies, directed copies and authorization copies, in every form you offer. | Compliance date |
| Right to direct an electronic copy in an EHR45 CFR 164.524(d); 164.501 | The third-party directive had been narrowed by the Ciox Health v. Azar decision to electronic copies of PHI in an EHR, but the regulation still read more broadly. | Codified: an individual may direct a covered entity to transmit an electronic copy of PHI in an electronic health record to a person they designate, on a clear, conspicuous and specific request, on the same 15-day clock. | Document which of your systems count as electronic health records, and route other third-party requests to the patient's own copy or to an authorization. | Compliance date |
| No unreasonable identity verification45 CFR 164.514(h)(2)(v) (new) | Verification required. No express limit in the regulation, though HHS said verification must not create barriers to, or unreasonably delay, access. | Verification is still required, but a covered entity may not impose unreasonable measures that impede an individual from exercising any right under the Privacy Rule. | Drop notarization, in-person-only and similar requirements where a less burdensome check is practicable, and apply that to every patient right, not only access. | Compliance date |
| New Notice of Privacy Practices content45 CFR 164.520(b) | Required header and contact element: name or title and telephone number. | A new required header, a statement of the right to discuss the notice with a designated contact person or office, a contact element that adds an email address, and a revised description of access rights. | Revise the notice, designate the contact, give it an email address, then repost it on site and online. HHS says it will update its model notices before the compliance date. | Compliance date |
| Written acknowledgment no longer required45 CFR 164.520(c)(2), (e) | Direct treatment providers make a good-faith effort to get a written acknowledgment of receipt and document it. | The acknowledgment requirement and its documentation are removed. Providing, posting and keeping copies of the notice are not. | Keep collecting acknowledgments until the rule is in effect. After that you may stop unless state law requires one, but you still have to give, post and retain the notice. | Effective date |
| Inmates now receive the notice45 CFR 164.520(a) | Inmates had no right to the notice. | The inmate exception is removed. Limits on an inmate's right of access remain. | Only relevant if you serve a correctional institution: provide the notice to inmate patients. | Compliance date |
| Disclosures to community and social-service organizations45 CFR 164.506(c)(6) (new) | Permitted under existing treatment and operations rules, but often misread. | Expressly permits disclosure 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. | Treat it as a permission, not a duty. Minimum necessary applies where it applied before, and stricter state law and Part 2 still govern. | Effective date |
| Health care operations: care coordination clarified45 CFR 164.501 | Commas in the definition let some read care coordination as population-based only. | Semicolons confirm that individual-level and population-based care coordination and case management are both health care operations. HHS calls this a clarification, not a substantive change. | Mostly relevant to health plans. No new step for a provider practice. | Already HHS's position (restated) |
| Business associates and access requests45 CFR 164.502(a)(4)(ii); 164.532(e)(3) | A BA disclosed to the covered entity, or to the individual if the agreement said so. | Unchanged in substance and now codified: the BA agreement decides who answers the patient, and the covered entity stays responsible either way. | For every vendor that holds records, write down who answers access requests, how fast, and how you find out a request arrived. | Already HHS's position (restated) |
| Transition period for existing business associate agreements45 CFR 164.532(e) | Not applicable. | A written BA agreement in place before publication and not renewed or modified between the effective and compliance dates is deemed compliant until it is renewed or modified after the compliance date, or January 18, 2028, whichever is earlier. | Use the time to amend agreements deliberately, not to wait. The transition covers contract wording only; the 15-day duty applies from the compliance date regardless. | Transition, ending January 18, 2028 at the latest |
| Telecommunications Relay Services45 CFR 164.512(m) (new); 160.103 | Relay providers sat awkwardly in the business associate definition. | Covered entities and business associates may disclose PHI to a TRS communications assistant as necessary to conduct covered functions, and TRS providers are excluded from the business associate definition for that service. | No BAA is needed with a relay provider for relay calls. Minimum necessary still applies. | Effective date |
| Armed Forces permission extended to all Uniformed Services45 CFR 164.512(k)(1) | Applied to Armed Forces personnel. | Applies to all Uniformed Services personnel, which adds the USPHS and NOAA Commissioned Corps. | Rarely relevant to a private practice. | Effective date |
What the 2026 final rule changes
15-calendar-day access deadline
45 CFR 164.524(b)(2)- Rule today:
- Act on an access request no later than 30 calendar days after receipt.
- Final rule:
- Act as soon as practicable, but no later than 15 calendar days after receipt.
- What a practice does:
- Rebuild the request workflow so a request can be logged, assigned, verified, located, produced and sent inside 15 days, including records held by vendors and in archives.
- Applies from:
- Compliance date
One extension of up to 30 calendar days
45 CFR 164.524(b)(2)(ii)- Rule today:
- One 30-day extension, with written notice inside the first 30 days.
- Final rule:
- One extension of no more than 30 calendar days, with a written statement of the reason and completion date sent inside the first 15 days.
- What a practice does:
- Make the extension notice a step with a date on it. It has to go out by day 15, and there is only one per request.
- Applies from:
- Compliance date
Faster state or federal law sets the clock
45 CFR 164.524(b)(2)(iii)- Rule today:
- A shorter state deadline already applied alongside HIPAA, but HIPAA did not say so.
- Final rule:
- Where another law requires access in less than 15 calendar days, that shorter period is deemed practicable.
- What a practice does:
- Check your state's records-access deadline. If it is shorter, it is your HIPAA deadline too.
- Applies from:
- Compliance date
Clarifying a request does not stop the clock
45 CFR 164.524(c)(3)- Rule today:
- Silent on whether back-and-forth with the patient extended the deadline.
- Final rule:
- A practice may discuss scope and format with the individual, but that discussion does not extend the time allowed.
- What a practice does:
- Start the clock at receipt, by whichever channel it arrived, and treat clarification and identity checks as time spent inside the 15 days.
- Applies from:
- Compliance date
No unnecessary barriers to making a request
45 CFR 164.524(b)(1)(ii)-(iii)- Rule today:
- A practice could require written requests.
- Final rule:
- A practice may still require requests in writing, but writing includes electronic submissions, and it may not impose a request measure when a less burdensome, practicable one exists.
- What a practice does:
- Accept requests by the channels you can practicably handle, not only one form or one portal, and say what they are.
- Applies from:
- Compliance date
Personal health applications defined
45 CFR 164.501; 164.524(c)(3)- Rule today:
- No definition. Delivery to an app was discussed in guidance only.
- Final rule:
- A defined term, and the rule names transmission to or through the individual's personal health application as a way to provide access when a copy is readily producible that way.
- What a practice does:
- Know which of your systems can deliver to a patient's app, and train the front desk to tell a patient's app request apart from a vendor's.
- Applies from:
- Compliance date
No new technology required to serve apps
Preamble to 45 CFR 164.524(c)- Rule today:
- Readily producible form and format applied, without app-specific language.
- Final rule:
- App delivery is required when a copy is readily producible that way. The rule does not require a practice to buy or build technology, including an API, to gain that ability, but it must be able to produce some electronic copy of PHI it keeps electronically.
- What a practice does:
- Inventory what your EHR and portal can already deliver. Capability you have, or that other law requires you to have, is capability you must use.
- Applies from:
- Compliance date
A patient's own app is not your business associate
Preamble to 45 CFR 164.501- Rule today:
- Stated in earlier HHS guidance.
- Final rule:
- HHS restates that a personal health app chosen by the individual is not acting for the covered entity, while an app built or supplied for a covered entity likely is a business associate.
- What a practice does:
- Classify by function. A patient-selected app needs no BAA from you; a vendor that handles records for you does.
- Applies from:
- Already HHS's position (restated)
App security concerns are not grounds to deny
Preamble to 45 CFR 164.524- Rule today:
- Stated in earlier HHS guidance.
- Final rule:
- A covered entity may not deny access based solely on its concerns about how a patient-chosen app will protect the information.
- What a practice does:
- You may tell a patient what concerns you about an app. You may not make that concern a reason to refuse, and app registration cannot push you past the deadline.
- Applies from:
- Already HHS's position (restated)
When access must be free
45 CFR 164.524(c)(4)(ii)- Rule today:
- Reasonable, cost-based fees for copies; HHS guidance discouraged charging for electronic access.
- Final rule:
- No fee for inspection, or for access to ePHI by an internet-based method such as a personal health application. Labor for making other copies, paper or electronic, may still be charged.
- What a practice does:
- Stop charging for portal, API or app access and for inspection. Keep a cost-based labor fee only where staff actually make the copy.
- Applies from:
- Compliance date
No charge for electronic media or its postage
45 CFR 164.524(c)(4)(i)- Rule today:
- Supplies for the paper copy or electronic media could be charged.
- Final rule:
- Supplies may be charged only for a non-electronic copy, and postage only for mailing a non-electronic copy or an agreed summary. Copying ePHI onto a CD or USB drive is labor only.
- What a practice does:
- Remove media and mailing charges for electronic copies from your fee list.
- Applies from:
- Compliance date
The 2016 fee methods, including $6.50, are superseded
Preamble to 45 CFR 164.524(c)(4)- Rule today:
- HHS's 2016 guidance described actual-cost, average-cost and $6.50 flat-fee methods.
- Final rule:
- The final rule replaces that interpretation and frames the fee provision as a ceiling, not a floor.
- What a practice does:
- Recalculate any fee you justified with the 2016 methods against the new fee rule.
- Applies from:
- Compliance date
Fee schedule for access and authorization copies
45 CFR 164.525 (new)- Rule today:
- No requirement to publish fees.
- Final rule:
- 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.
- What a practice does:
- If you charge anything, publish the schedule: what is free, and standard fees for access copies, directed copies and authorization copies, in every form you offer.
- Applies from:
- Compliance date
Right to direct an electronic copy in an EHR
45 CFR 164.524(d); 164.501- Rule today:
- The third-party directive had been narrowed by the Ciox Health v. Azar decision to electronic copies of PHI in an EHR, but the regulation still read more broadly.
- Final rule:
- Codified: an individual may direct a covered entity to transmit an electronic copy of PHI in an electronic health record to a person they designate, on a clear, conspicuous and specific request, on the same 15-day clock.
- What a practice does:
- Document which of your systems count as electronic health records, and route other third-party requests to the patient's own copy or to an authorization.
- Applies from:
- Compliance date
No unreasonable identity verification
45 CFR 164.514(h)(2)(v) (new)- Rule today:
- Verification required. No express limit in the regulation, though HHS said verification must not create barriers to, or unreasonably delay, access.
- Final rule:
- Verification is still required, but a covered entity may not impose unreasonable measures that impede an individual from exercising any right under the Privacy Rule.
- What a practice does:
- Drop notarization, in-person-only and similar requirements where a less burdensome check is practicable, and apply that to every patient right, not only access.
- Applies from:
- Compliance date
New Notice of Privacy Practices content
45 CFR 164.520(b)- Rule today:
- Required header and contact element: name or title and telephone number.
- Final rule:
- A new required header, a statement of the right to discuss the notice with a designated contact person or office, a contact element that adds an email address, and a revised description of access rights.
- What a practice does:
- Revise the notice, designate the contact, give it an email address, then repost it on site and online. HHS says it will update its model notices before the compliance date.
- Applies from:
- Compliance date
Written acknowledgment no longer required
45 CFR 164.520(c)(2), (e)- Rule today:
- Direct treatment providers make a good-faith effort to get a written acknowledgment of receipt and document it.
- Final rule:
- The acknowledgment requirement and its documentation are removed. Providing, posting and keeping copies of the notice are not.
- What a practice does:
- Keep collecting acknowledgments until the rule is in effect. After that you may stop unless state law requires one, but you still have to give, post and retain the notice.
- Applies from:
- Effective date
Inmates now receive the notice
45 CFR 164.520(a)- Rule today:
- Inmates had no right to the notice.
- Final rule:
- The inmate exception is removed. Limits on an inmate's right of access remain.
- What a practice does:
- Only relevant if you serve a correctional institution: provide the notice to inmate patients.
- Applies from:
- Compliance date
Disclosures to community and social-service organizations
45 CFR 164.506(c)(6) (new)- Rule today:
- Permitted under existing treatment and operations rules, but often misread.
- Final rule:
- Expressly permits disclosure 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.
- What a practice does:
- Treat it as a permission, not a duty. Minimum necessary applies where it applied before, and stricter state law and Part 2 still govern.
- Applies from:
- Effective date
Health care operations: care coordination clarified
45 CFR 164.501- Rule today:
- Commas in the definition let some read care coordination as population-based only.
- Final rule:
- Semicolons confirm that individual-level and population-based care coordination and case management are both health care operations. HHS calls this a clarification, not a substantive change.
- What a practice does:
- Mostly relevant to health plans. No new step for a provider practice.
- Applies from:
- Already HHS's position (restated)
Business associates and access requests
45 CFR 164.502(a)(4)(ii); 164.532(e)(3)- Rule today:
- A BA disclosed to the covered entity, or to the individual if the agreement said so.
- Final rule:
- Unchanged in substance and now codified: the BA agreement decides who answers the patient, and the covered entity stays responsible either way.
- What a practice does:
- For every vendor that holds records, write down who answers access requests, how fast, and how you find out a request arrived.
- Applies from:
- Already HHS's position (restated)
Transition period for existing business associate agreements
45 CFR 164.532(e)- Rule today:
- Not applicable.
- Final rule:
- A written BA agreement in place before publication and not renewed or modified between the effective and compliance dates is deemed compliant until it is renewed or modified after the compliance date, or January 18, 2028, whichever is earlier.
- What a practice does:
- Use the time to amend agreements deliberately, not to wait. The transition covers contract wording only; the 15-day duty applies from the compliance date regardless.
- Applies from:
- Transition, ending January 18, 2028 at the latest
Telecommunications Relay Services
45 CFR 164.512(m) (new); 160.103- Rule today:
- Relay providers sat awkwardly in the business associate definition.
- Final rule:
- Covered entities and business associates may disclose PHI to a TRS communications assistant as necessary to conduct covered functions, and TRS providers are excluded from the business associate definition for that service.
- What a practice does:
- No BAA is needed with a relay provider for relay calls. Minimum necessary still applies.
- Applies from:
- Effective date
Armed Forces permission extended to all Uniformed Services
45 CFR 164.512(k)(1)- Rule today:
- Applied to Armed Forces personnel.
- Final rule:
- Applies to all Uniformed Services personnel, which adds the USPHS and NOAA Commissioned Corps.
- What a practice does:
- Rarely relevant to a private practice.
- Applies from:
- Effective date
“Rule today” and “Final rule” paraphrase the regulation. “What a practice does” is Patient Protect’s reading of the work involved, not text from the rule.
The 15-day access deadline
The biggest change is easy to explain and harder to implement. Under 45 CFR 164.524(b)(2) as revised, a covered entity "must act on a request for access as soon as practicable, but no later than 15 calendar days after receipt of the request." Today the outer limit is 30 days.
A few details decide whether a practice actually meets it.
Fifteen days is a ceiling. HHS "encourages covered entities to view the 15 calendar days as an outer limit." The standard is as soon as practicable, and where another federal or state law requires access in fewer than 15 calendar days, the rule treats that shorter period as practicable. A practice in a state with a faster records-access statute is not getting 15 days. It is getting whatever the state allows, and missing it is now a HIPAA timeliness problem as well as a state-law one.
The clock starts at receipt. HHS says the period begins on the date the covered entity receives the request, and it includes the time needed to get any additional information from the individual and to verify identity. If a request goes straight to a vendor whose business associate agreement makes it responsible for responding, the clock starts when the vendor receives it. A request that arrives by email on a Friday and is noticed on Wednesday has already spent five days.
Talking it through does not stop it. The rule lets a practice discuss the scope, format and other aspects of a request with the patient "as necessary to facilitate the timely provision of access; however, such discussion shall not extend the time allowed." Clarification is part of the work, not a pause in it.
One extension, announced in time. If a practice cannot act within 15 days, it may extend once, by no more than 30 calendar days, and only if it sends the individual a written statement of the reason and the completion date within the original 15 days. That makes 45 calendar days the absolute maximum from receipt. HHS had proposed a 15-day extension; the final rule kept 30.
Paper and archives count. The 15 days apply to records on paper and records archived offsite or offline. There is no small-practice exception in the final rule. HHS also notes that a delay can still be a problem under the information blocking regulations even when a request is fulfilled inside 15 days.
Changing "30 days" to "15 days" in a policy is the easy part. The workflow has to actually work in 15 days, which means a practice needs to be able to do all of the following, quickly and on the record:
- Record when each request arrived, whichever channel it came through.
- Assign it to a named person.
- Verify the requester's identity, without unnecessary friction.
- Find every responsive record in the designated record set, including what a vendor holds.
- Settle the form and format, and any fee.
- Produce and send the copy, or arrange inspection.
- Document what was done and when.
- Send a written extension notice before day 15 if it will not make it.
If records requests in your practice depend on one person, the 15-day standard is a test of what happens when that person is on vacation.
How patients may make a request
A practice may still require access requests in writing, if it tells patients so. The rule now says what writing means: the request itself serves as documentation, "including when the request is submitted electronically or on paper." HHS lists a handwritten letter, a paper form, an email, a secure message and a portal request among the examples, and says requests do not need to be on any particular form.
There is a new limit on friction. A covered entity "may not impose measures on individuals making requests for access that impede an individual from obtaining access when there is a measure for making such requests that is less burdensome for the individual and practicable for the entity." HHS's example is a practice that accepts requests only on paper, or only through a portal, when emailing the staff member who handles requests would be practicable. A practice is not required to adopt any particular electronic intake mechanism. It is required not to make the request harder than it needs to be.
If a practice offers a summary instead of a copy, it now has to tell the patient that they keep the right to the copy if they do not agree to the summary.
The right to inspect records in person did not change. HHS proposed letting patients take notes, photographs and recordings during an inspection and did not finalize it, though the preamble notes that a provider may allow photographs and that the existing right "does not place limitations on an individual's ability to record their PHI while they inspect it."
Personal health applications
The rule adds a definition. A personal health application is an electronic application an individual uses to access health information about themselves, drawn from one or more sources, where the information is "managed, shared, and controlled by or primarily for the individual" and not managed, shared or controlled by or primarily for a covered entity or primarily for another person. The access provision now names transmission "to or through the individual's personal health application" as one way to deliver a copy, when a copy is readily producible that way.
This part is easy to misunderstand in both directions, so it is worth being exact about three things.
An app the patient chose is not your business associate. HHS states that "a personal health app developer does not meet the definition of a business associate because it is not acting for, or on behalf of, a covered entity or business associate." Sending a patient's records to the app they picked is a transmission to the patient. That is different from software a practice builds, supplies or contracts for: HHS says an app developer working for a covered entity likely is a business associate, and an app tied to a device the practice provides is likely not a personal health app at all. Whether a BAA is needed depends on who the app works for, not on the fact that it is an app. "Apps don't need BAAs" and "every app needs a BAA" are both wrong.
The rule does not require new technology. HHS says the final rule "does not independently require the implementation of technology or policies by covered entities for the purpose of gaining the ability to provide individuals with a copy of their PHI to or through a personal health app," and that it does not specifically require APIs. The test is whether a copy is readily producible in the form requested, which HHS calls a matter of capability, not willingness. Capability a practice already has counts, as does capability another law requires it to have. Every practice must be able to produce some electronic copy of records it keeps electronically, and HHS considers email generally readily producible by all covered entities.
Concern about an app is not a reason to refuse. A practice may not deny access based solely on its concern that the app will not protect the information well, or because the app does not encrypt data at rest. It may tell the patient about the risks it sees. It may limit a transmission method that would put its own systems at unacceptable risk, judged through its Security Rule risk analysis. And app registration processes cannot be used to push a response past the deadline.
HHS wrote this part of the rule around a plain observation: "Individuals increasingly are choosing to use technology to access and manage their health information." We are pro-technology and pro-AI at Patient Protect, and we agree. The risk is not the app. The risk is moving records without knowing what relationship you are in, what authority you are acting on and who handles the data next. Our longer piece on personal health apps and patient access covers the front-desk procedure.
Fees: what must be free, and what may still be charged
The fee rule at 164.524(c)(4) now says plainly when no fee may be charged: when an individual inspects their records, and when an individual "accesses electronic protected health information maintained by or on behalf of the covered entity using an internet-based method, such as a personal health application." HHS's examples of internet-based access include viewing, downloading and transmitting through a patient portal and connecting a personal health app through an API. Internet-based methods do not include circumstances that involve a workforce member's labor to make a copy.
That boundary is the one to get right. Not all electronic access is free. If a staff member prepares an electronic copy and emails it as a PDF at the patient's request, a reasonable, cost-based fee for that labor is still permitted. Submitting a request electronically does not by itself make the delivery internet-based.
Where a fee is allowed, it may include only:
- labor for copying, in paper or electronic form;
- supplies for a non-electronic copy;
- postage for mailing a non-electronic copy or an agreed summary;
- labor to prepare a summary or explanation the patient agreed to.
Two practical consequences follow. A practice can no longer charge for the CD or USB drive an electronic copy goes on, or for mailing it; the final rule limits fees for portable electronic media to labor. And HHS's 2016 guidance on calculating fees, including the three methods it described (actual costs, average costs, or a flat fee of $6.50), is superseded by this rule, which HHS describes as setting "a ceiling of what can be charged... rather than a floor."
Some things did not change. A practice still cannot pass on the cost of outsourcing request handling to a vendor. It cannot withhold records because a patient has an unpaid bill for care. A state law that bans fees or allows only lower ones still applies. And the rule did not settle fees for copies directed to a third party under the right to direct; HHS's proposed labor-only limit for those was not addressed. Our guide to medical records fees under the final rule works through examples.
The public fee schedule
New 45 CFR 164.525 reads: "If a covered entity imposes fees for copies of protected health information requested under this subpart, the covered entity must post a fee schedule on its website, if it has one, and make the fee schedule available to individuals at the point of service and upon request."
The conditions matter. The requirement applies to practices that charge for copies. A practice that never charges does not need a schedule. A practice without a website still has to make the schedule available at the point of service and on request; HHS gives examples such as posting it on the wall, leaving copies in the waiting room or keeping one at the reception desk, and answering over the phone counts as making it available on request.
The schedule must list:
- every type of access available free of charge;
- standard fees for copies provided under the right of access and under the right to direct, for every electronic and non-electronic form and format available;
- standard fees for copies disclosed under a patient's authorization.
HHS adds that labor may be shown as hourly charges and that the schedule must explain the charges are added together to reach the total. Posting average costs is recommended, not required. The 2021 proposals to require individualized fee estimates and itemized statements on request were not finalized.
Sending records to someone the patient chooses
The rule codifies the right of an individual to direct a covered entity to transmit "an electronic copy of protected health information about the individual... in an electronic health record to a person designated by the individual." This is narrower than the third-party directive in the 2013 Omnibus Rule. In 2020, a federal court in Ciox Health v. Azar held that the HITECH Act's right to direct reaches only electronic copies of records in an electronic health record, and vacated the broader mandate. HHS did not appeal, and the final rule writes the court's boundary into the regulation.
Three details shape the workflow:
- What counts as an EHR is broad. The new definition covers health-related information created, gathered, managed and consulted by authorized clinicians and staff, and HHS says it includes billing and other non-clinical information, regardless of which system holds it. A practice now has to document which of its electronic health records are subject to the right to direct, alongside its designated record sets.
- The request must be clear, conspicuous and specific. A practice may require it in writing, which again includes email and portal messages. HHS did not finalize the proposal to require acting on oral requests; a practice may accept one if it documents it. No HIPAA authorization is required for a request that qualifies.
- The clock is the same. Fifteen calendar days, one extension of up to 30.
A request that does not qualify, such as one asking for paper records to go to a third party, should be treated as an authorization if it meets the authorization requirements; the patient can also get the copy themselves and pass it on. The rule lets a practice explain those alternatives in its notice. HHS did not finalize its proposal requiring providers and health plans to submit access requests to other covered entities on a patient's behalf, though a practice may still help a patient do that.
Identity verification
Practices still have to verify who is asking. What changes is how much friction they may put in the way. New 45 CFR 164.514(h)(2)(v) provides that a covered entity "may not impose unreasonable verification measures on an individual that would impede the individual from exercising a right under this part," and defines an unreasonable measure as one that makes the individual spend unnecessary effort or resources when a less burdensome verification measure is practicable. Practicability takes into account the practice's technical capabilities, its privacy and security obligations and the cost of the more convenient option.
Note the scope. The provision covers any right under the Privacy Rule, not only access.
HHS's examples of unreasonable measures, given in the preamble rather than the regulatory text, include requiring proof of identity in person when remote verification is practicable, requiring a wet signature where an electronic signature is valid, requiring notarization, asking for the extensive information found on an authorization form, and accepting requests through only one electronic method. Its examples of reasonable measures include a form that asks for only the limited information needed, and asking a personal representative for a copy of a power of attorney.
The rule does not require practices to relax identity verification, and HHS says a practice is not required to fulfill a request when it cannot verify the identity of the person making it. The point is proportion, not abandonment.
The Notice of Privacy Practices
The notice requirement stays. Its content changes, and the signature that went with it goes.
The header. Every notice must open with, or prominently display, a new header. It names the covered entity and says the notice describes how health information may be used and disclosed, the individual's rights, how to get copies of records "at limited cost or, in some cases, free of charge," and how to file a complaint, and that the individual has a right to a copy of the notice and to discuss it with a named contact at a phone number and email address. The header's word "Medical" becomes "Health"; HHS says that change is not substantive.
The right to discuss the notice. The list of individual rights adds "the right to discuss the notice with a designated contact person or office." HHS did not finalize its proposal that the contact be onsite, and did not set qualifications for the role, though it encourages practices to designate someone who knows the notice rather than a general customer-service line. Having knowledgeable staff available during business hours, or offering to schedule a call, are the kinds of arrangement HHS describes.
The contact. The notice must give the name or title, telephone number and email address of the designated person or office. The email address is new.
Access rights. The description of the right of access now says copies are available at limited cost or, in some cases, free, and adds the right to direct an electronic copy of records in an EHR to a designated person.
HHS says it intends to update its model notices, and the model Part 2 patient notice, before the compliance date. Practices that use the model notice will have a starting point. They will still have to fill it in, adopt it, post it and keep it.
Do not let the update erase work that is already done. Practices that create or maintain Part 2 records were required to add Part 2 content by February 16, 2026, and those provisions remain in effect. The reproductive-health notice provisions from the 2024 rule were vacated in Purl v. HHS and should not be reintroduced. Our page on the Notice of Privacy Practices explains what belongs in a current notice.
The written acknowledgment goes away. The notice does not.
The rule removes the requirement for a provider with a direct treatment relationship to make a good-faith effort to obtain a written acknowledgment that the patient received the notice, along with the duty to document those efforts and keep that documentation. HHS did not replace it with anything. It does not prevent a practice from continuing to document that it gave patients the notice, and it noted a reason to stop asking: staff "may erroneously believe that individuals must sign the acknowledgment to obtain care."
What remains is everything else. The notice must still be provided at the first service delivery, posted in a clear and prominent location at the practice, made available on request, posted on the practice website, and delivered electronically and automatically when the first service is electronic. Copies of each version must still be kept.
As for timing: keep collecting acknowledgments for now. The requirement is in the regulation until the rule takes effect. After that, our reading is that it no longer applies, and a practice may stop, unless state law requires an acknowledgment of its own; Texas, for one, has its own rule for optometrists who communicate with patients electronically. A practice that prefers to wait for the compliance date loses nothing by doing so. Keep the acknowledgments you have already collected: the rule does not address them, and holding on to them costs little.
Inmates
The rule removes the exception that denied inmates of correctional institutions a right to the notice. It keeps the existing limits on an inmate's right of access. This matters only to practices that serve a correctional institution.
Care coordination and minimum necessary
Two care-coordination changes were finalized, and HHS presents both as clarifications of what the rule already allowed.
Health care operations. The definition of health care operations now separates its list with semicolons, so that "case management and care coordination" reads as its own activity rather than part of "population-based activities." HHS says this confirms that individual-level and population-based care coordination and case management are both health care operations, mainly so that health plans can rely on it, and that it "does not consider this clarification to be a substantive modification."
Community and social-service organizations. New 45 CFR 164.506(c)(6) provides that a covered entity "may disclose an individual's protected health information to a social services agency, community-based organization, home and community based services provider, or similar third party that provides health or human services to specific individuals," for individual-level care coordination and case management. It is a permission, not a requirement to disclose. The recipient does not have to be a health care provider, the permission creates no new business associate requirement, and it does not cover disclosures to law enforcement or child welfare agencies for investigations. Stricter state law, Part 2 consent and the information blocking rules still apply, and disclosures should stay consistent with your notice.
Minimum necessary did not change. The 2021 proposal would have exempted disclosures for individual-level care coordination and case management from the minimum necessary standard. HHS did not adopt it: "This final rule does not alter the minimum necessary requirements." Its reasons were that the exception could erode patients' confidence in the privacy of their information, that other changes in the rule already help health plans, and that sharing more than necessary increases what is exposed if something goes wrong. Disclosures to a health care provider for treatment were already outside minimum necessary and still are. Disclosures to non-provider third parties, including under the new community-organization permission, and disclosures for health care operations remain subject to it. Our care coordination guide and the minimum necessary standard page cover the detail.
The same section of the proposal would have replaced "professional judgment" with a "good faith belief" standard in several disclosure permissions, and changed the threat-to-health-or-safety standard from "serious and imminent" to "serious and reasonably foreseeable." HHS finalized neither. The existing standards stand.
Relay services and the Uniformed Services
Two smaller changes complete the list.
Covered entities and business associates may now disclose protected health information to a Telecommunications Relay Service communications assistant, as necessary to conduct covered functions, so that people who are deaf, hard of hearing, deaf-blind or have a speech disability can communicate with the practice. Relay providers are excluded from the business associate definition for that service, so no BAA is needed for it. Minimum necessary still applies.
The existing permission for Armed Forces mission-readiness disclosures now covers all Uniformed Services, which adds the U.S. Public Health Service and NOAA Commissioned Corps. Few private practices will encounter it.
Business associates
The rule clarifies, rather than changes, how business associates fit into access. Under revised 45 CFR 164.502(a)(4)(ii), a business associate must disclose records to the covered entity or, when the business associate agreement specifies, directly to the individual or their designee, as needed to satisfy the covered entity's access obligations. The agreement decides which. HHS says the clarification does not create a new requirement for business associates to respond directly to patients.
What it does not do is move the obligation. HHS is direct: "In all cases, the covered entity remains ultimately responsible for ensuring that the requested PHI is provided to the individual or individual's designee to fulfill the right of access," and "a covered entity may not avoid its access obligations on the basis that its business associate maintains the requested PHI." It suggests practices "should address in their business associate agreements which party is responsible."
A BAA is not a substitute for understanding who actually does the work. For every vendor that holds patient records, whether an EHR, imaging archive, billing service or release-of-information company, a practice should be able to say who answers an access request, how the practice learns that one arrived, and how fast it will be answered.
The transition period. Because the rule changes what agreements should say, it gives existing ones time. Under revised 45 CFR 164.532(e), a written business associate agreement entered into before the rule's publication date, and not renewed or modified between the effective date and the compliance date, is deemed compliant with the documentation and contract requirements until the earlier of the date it is renewed or modified after the compliance date, or January 18, 2028. Evergreen contracts qualify. Verbal arrangements do not.
The transition covers the paperwork, not the work. HHS states that a business associate handling access requests must respond "not later than 15 calendar days after receiving a request, even if the business associate agreement has not yet been amended," and the rule says nothing in the transition alters the covered entity's own access obligations for records a business associate holds.
What HHS proposed in 2021 and did not finalize
Each item below was proposed, or asked about, in the January 2021 proposal. HHS did not finalize any of them, and the passage saying so for each is in the rule text we cite.
Finalized
The changes with the most work attached.
- 15-calendar-day access deadline 45 CFR 164.524(b)(2)
- One extension of up to 30 calendar days 45 CFR 164.524(b)(2)(ii)
- Clarifying a request does not stop the clock 45 CFR 164.524(c)(3)
- When access must be free 45 CFR 164.524(c)(4)(ii)
- Fee schedule for access and authorization copies 45 CFR 164.525 (new)
- New Notice of Privacy Practices content 45 CFR 164.520(b)
- Written acknowledgment no longer required 45 CFR 164.520(c)(2), (e)
- Business associates and access requests 45 CFR 164.502(a)(4)(ii); 164.532(e)(3)
Proposed in 2021, not finalized
Each was proposed, or asked about, in January 2021. None of them is law.
An exception to the minimum necessary standard for disclosures for individual-level care coordination and case management.
Outcome: Not finalized. The minimum necessary standard is unchanged.
Treatment disclosures between providers were already outside minimum necessary. Disclosures to plans and non-provider third parties still have to be limited to what is needed.
Replacing "exercise of professional judgment" with a "good faith belief" standard, with a presumption of good faith, across several disclosure permissions.
Outcome: Not finalized. The existing professional-judgment standards stand.
Policies and training that describe a good-faith standard for family and emergency disclosures are describing a proposal.
Changing "serious and imminent threat" to "serious and reasonably foreseeable threat" in § 164.512(j).
Outcome: Not finalized. "Serious and imminent" remains the standard.
A threat-disclosure policy written to the proposal would permit disclosures the rule does not.
Expanding the right to inspect to include taking notes, photographs and using personal resources to capture the information.
Outcome: Not finalized. The right to inspect stays as it was.
There is no new codified right to photograph records, though HHS notes a provider may allow it and the existing right does not limit recording.
Requiring a policy to prioritize urgent or high-priority access requests.
Outcome: Not finalized.
No prioritization policy is required, and HHS worried one would push patients to justify their requests.
Requiring providers and health plans, at an individual's direction, to submit the individual's access request to another covered entity.
Outcome: Not finalized. A practice may still help a patient do this voluntarily.
No provider-to-provider request-forwarding duty exists, despite summaries that describe one.
Requiring covered entities to act on oral requests to direct records to a third party.
Outcome: Not finalized. A practice may require these requests in writing, and may accept oral ones if it documents them.
Writing still includes email and portal messages, so the requirement is easy for a patient to meet.
Individualized fee estimates and itemized statements of fees on request.
Outcome: Not finalized. The posted fee schedule is the requirement.
A practice must publish standard fees; it is not required to produce a per-request estimate or itemized bill.
Limiting fees for copies sent to a third party under the right to direct to labor only.
Outcome: Not addressed in this final rule.
Content claiming a labor-only cap on directed copies is describing a proposal HHS declined to settle here.
Asked for comment in 2021: whether to prohibit fees for copies an individual needs to support an application for public benefits.
Outcome: Not adopted.
No special free category for benefit applications was created.
Requiring the NPP contact person to be available onsite.
Outcome: Not finalized. A designated person or office is required, not an onsite one.
A small practice can designate an office or a remote contact, as long as patients can actually reach it.
If a policy, training module or vendor checklist you use describes any of these as requirements, it was written to the proposal. The most consequential is minimum necessary: a practice that relaxed it for care coordination on the strength of 2021 coverage is disclosing more than the rule permits.
What an independent practice should do now
Most of this binds at the compliance date, which leaves time. It does not leave much slack, because the access workflow, the notice and the vendor agreements all depend on each other. If you want a quick read on where you stand, the 2026 Privacy Rule readiness check takes about five minutes and asks nothing about patients.
Now, before the rule takes effect
- Measure your real turnaround on access requests over the last few months, including the slow ones.
- List every channel a request can arrive through and who watches each one.
- Check your state's records-access deadline and fee limits.
- List every vendor that holds patient records and what each agreement says about access requests.
- Decide who will be the notice's designated contact, and set up an email address someone answers.
- Write down what you charge for copies today and how you got to those numbers.
- Keep collecting NPP acknowledgments.
Between the effective date and the compliance date
- Rewrite the access policy and procedure for 15 calendar days, receipt-based timing, the extension notice and the new request rules.
- Build the extension notice so it can go out by day 15.
- Review identity verification for every patient right, not only access.
- Recalculate fees under the new limits, and if you charge, prepare the fee schedule.
- Revise the Notice of Privacy Practices, starting from HHS's updated model notice once it is published.
- Amend business associate agreements deliberately, before the transition runs out.
- Train the people whose work changes: front desk, records staff, billing, the privacy officer.
By the compliance date
- Post the revised notice in the office and on the website, and have copies available.
- Post the fee schedule, if you charge.
- Run the new access workflow on real requests and keep the evidence: the log, the timestamps, the notices sent.
The Privacy Rule already requires training for workforce members whose functions are affected by a material change in policy, within a reasonable period after the change takes effect. These changes qualify.
Checklist
A shorter version for the office wall. Each item is done when the evidence for it exists.
- Access workflow: every request is logged at receipt, assigned an owner, and tracked to a 15-day outer limit. Evidence: the request log.
- State law: your state's access deadline and fee limits are recorded, and the shorter deadline governs. Evidence: a note in the policy.
- Extension: a written extension notice states the reason and completion date and can go out by day 15. Evidence: the template and a sent example.
- Intake: patients can request access by the channels you can practicably handle, and are told what they are. Evidence: the policy and the notice.
- Formats and apps: you know what your systems can deliver electronically, including to a patient's app, and staff know a patient's app is not your vendor. Evidence: a short capability list and training record.
- Identity: verification steps are proportionate for every right. Evidence: the revised procedure.
- Fees: fees are labor-only for electronic copies, nothing for inspection or internet-based access, no media or postage charges for electronic copies. Evidence: the fee list.
- Fee schedule: if you charge, the schedule is on the website, at the front desk and available on request. Evidence: the posted schedule.
- Notice: the revised notice carries the new header, the right to discuss, the contact's email and the updated access rights, and is posted and archived. Evidence: the dated versions.
- Vendors: each vendor holding records has a documented access responsibility and an agreement on a plan for the transition. Evidence: the agreement register.
- Care coordination: policies describe the new disclosure permission as a permission, and minimum necessary unchanged. Evidence: the policy.
- Training: affected staff are trained on the changes. Evidence: the training record.
Frequently Asked Questions
Did HIPAA change in 2026?
Yes. HHS finalized changes to the HIPAA Privacy Rule on November 16, 2026. They are not enforceable yet: compliance is required 240 days after the rule is published in the Federal Register.
What is the new HIPAA medical records deadline?
As soon as practicable, and no later than 15 calendar days after the practice receives the request, with one extension of up to 30 calendar days. HHS will not act on the 15-day standard before the compliance date.
Is the 15-day rule in effect today?
No. HHS will not take action for noncompliance with the new requirements before the compliance date. A practice may adopt the 15-day standard sooner, and given the work involved, there is a good case for starting early.
When does the new HIPAA Privacy Rule take effect, and when is the compliance deadline?
It takes effect 60 days after Federal Register publication, and practices must comply 240 days after publication. The status box at the top of this article shows the dates, and will show the confirmed ones once the rule is published.
Can a provider still take an extension?
Yes, once per request, for no more than 30 calendar days, and only with a written statement of the reason and the completion date sent within the first 15 days.
Does a state law with a shorter deadline still apply?
Yes. Where another law requires access in fewer than 15 calendar days, the final rule treats that shorter period as practicable, so it becomes the HIPAA deadline too.
Can a patient receive records through a health app?
Yes, when a copy is readily producible to or through the app. The rule does not require a practice to buy or build new technology, including an API, to make that possible.
Does a personal health app need a BAA?
Not when the patient chose it; an app or vendor that works for the practice is a different relationship. More in HIPAA and personal health apps.
Can a provider refuse to send records to an app?
Not based solely on concerns about how the app will protect the information, though a practice may explain the risks it sees. More in HIPAA and personal health apps.
Is all electronic access now free?
No. Inspection and internet-based access, such as a portal or a patient's app, must be free; a copy prepared by staff can still carry a labor fee. More in medical records fees under the final rule.
Do providers have to publish their medical record fees?
Providers that charge for copies do, on their website if they have one, at the point of service and on request. More in medical records fees under the final rule.
Do patients still have to sign an NPP acknowledgment?
Not once the rule takes effect, 60 days after publication. Until then, keep collecting them, and keep doing so afterwards wherever state law requires its own acknowledgment. The notice itself is still required, posted and kept.
Does the minimum necessary rule still apply?
Yes, unchanged. HHS did not finalize the proposed exception for care coordination. Disclosures to providers for treatment were already outside it; disclosures to other third parties and for operations are not.
Does every practice need a new API?
No. The rule does not require APIs or new technology, but a practice must use the electronic capability it already has. More in HIPAA and personal health apps.
Does the rule change BAAs?
It changes what agreements should address, mainly who answers access requests, and gives qualifying existing agreements a transition period ending no later than January 18, 2028. It does not change who is responsible: the covered entity is.
Is this the HIPAA Security Rule update?
No. This final rule changes the Privacy Rule. The Security Rule changes HHS proposed in January 2025 remain a proposal.
What Patient Protect is doing
We read the rule end to end and built the coverage on this site from it: this article, the readiness check, and updates to our pages on the right of access and the Notice of Privacy Practices. The status, dates and change list on these pages come from one fact base whose quotations are tested against our stored copy of the rule text on every build, so when the Federal Register publishes the final version, they update in one place.
Inside the platform, the work this rule creates lands on things Patient Protect already does. Practices revise and version their access policy and their policy for issuing and revising the notice in Policies & Procedures and see which staff have acknowledged them. Vendor & BAA Governance tracks the business associate relationships a practice records and the state of each agreement, which is where the transition period gets managed. Training records show who has been trained. Compliance Evidence & Records holds the compliance documents you upload, with version history. Nothing in Patient Protect answers an access request itself; your EHR and your staff do that, and the platform keeps the policy, training and vendor record around it.
If the platform adds anything specific to this rule, the features page will say so.
Sources and method
We read the final rule as filed for public inspection: Federal Register document 2026-23429, 363 pages, including the regulatory text and HHS’s responses to comments. The status, dates and change list on these pages come from one fact base whose quotations are tested against our stored copy of the rule text on every build. Where a point is our reading rather than the rule’s words, we say so. Last fact-checked November 17, 2026.
- Federal Register document 2026-23429 (public inspection) — full text retrieved and read 2026-11-17
- Final rule text, public-inspection PDF (363 pages) — retrieved 2026-11-17
- HHS OCR: 2026 Privacy Final Rule — HHS blocks automated retrieval; nothing here relies on this page's wording
- HHS OCR: HIPAA Privacy Rule: Changes to Support Coordinated Care and Individual Engagement and Reduce Regulatory Burdens Final Rule — HHS blocks automated retrieval; nothing here relies on this page's wording
- HHS press release, November 16, 2026 — HHS blocks automated retrieval; nothing here relies on this page's wording
This article is general educational information, not legal advice. Evaluate HIPAA requirements together with applicable state law and other federal law governing specific categories of health information, including 42 CFR Part 2.
Corrections & Updates
Healthcare security data changes as investigations progress, vendors update systems, and laws and guidance evolve. If you see something outdated, incomplete, or incorrect — or have newer source material — we’d appreciate hearing from you.
