RegulationAnalysis
HHS finalizes HIPAA Privacy Rule changes: 15-day deadline for record requests, new health app definition
HHS's Office for Civil Rights finalized changes to the HIPAA Privacy Rule that cut the deadline to answer patient access requests from 30 days to 15 and define personal health apps, whose developers the rule says are generally outside HIPAA.
The Department of Health and Human Services has finalized changes to the HIPAA Privacy Rule that cut the deadline for answering a patient's request for their records from 30 days to 15 calendar days and add the first regulatory definition of a "personal health application." The Office for Civil Rights' final rule, document 2026-23429, was scheduled for Federal Register publication on November 19, 2026. Healthcare Dive reported the finalization on November 17.
What changes for patient record requests?
The rule's summary of major provisions lists the access changes. Covered entities must respond to an access request as soon as practicable and no later than 15 calendar days after receipt, down from the current 30 days, with the opportunity for one extension of no more than 30 calendar days. The rule also:
- adds definitions of "electronic health record" and "personal health application";
- clarifies the form and format of responses and reduces the burden of identity verification on individuals;
- limits the right to direct PHI to a third party to electronic copies of PHI in an electronic health record, which the rule says follows a binding court decision (the preamble's history refers to Ciox Health, LLC v. Azar);
- amends the permissible fee structure, including when electronic PHI must be provided free of charge;
- requires covered entities with a website to post a fee schedule for copies obtained under the right of access.
Beyond access, the rule clarifies that covered entities may disclose PHI to social services agencies, community-based organizations and home and community-based services providers for care coordination, and it ends the requirement that a provider get a patient's written acknowledgment of the Notice of Privacy Practices. Healthcare Dive reports the identity-verification change bars "unreasonable" measures such as requiring in-person verification when remote options exist.
Are personal health apps covered by HIPAA?
This is the part of the rule that bears most on how health data moves into software. The preamble defines a personal health app by who controls it: an app that lets the individual manage, share and control the health information in it, and that is managed, shared and controlled by or primarily for the individual. The rule says the developer of such an app, which is not acting on behalf of a covered entity or business associate, would not be a business associate and so would not be subject to the federal privacy and security obligations of the HIPAA Rules.
In practice the preamble describes a handoff. A covered entity's patient portal is run for the covered entity, so its developer is likely a business associate. An app the patient picks is governed instead by "the app's terms and conditions or consumer privacy policy," in the rule's words. The Department declined to name specific technologies in the regulatory text, saying a flexible definition accelerates innovation. Healthcare Dive reports HHS finalized the definition without adding security or privacy standards for apps, which it describes as a broader approach than some commenters wanted. Commenters on the earlier proposal, the preamble notes, raised concerns about the ability of non-HIPAA recipients to safeguard and redisclose information.
For readers working out where HIPAA stops, see the glossary entries on HIPAA and protected health information. The rule does not mention generative AI tools; whether a given AI product qualifies as a personal health app would turn on the definition above, and the Department did not address it.
When does it take effect?
The rule's dates section sets an effective date 60 days after Federal Register publication and a compliance date 240 days after publication. If publication occurred on November 19, as scheduled, those fall on January 18, 2027 and July 17, 2027, by this newsroom's count. Healthcare Dive reports a compliance deadline of about July 10, roughly six months after the effective date, so the two accounts differ by about a week; the rule text controls and counts from the actual publication date.
What does it cost, and who objected?
Healthcare Dive reports that HHS estimates $784 million in new costs in the first year, then net savings of $703 million a year in years two through five, with most savings coming from ending the signed-acknowledgment requirement. It also reports that a coalition of healthcare executives wrote to HHS before finalization asking it not to finalize the rule, arguing that provisions would make it hard to confirm a patient authorized a third-party app and opposing looser verification. OCR Director Paula Stannard said at HLTH 2026 that "we are convinced that this will provide individuals with faster access to health information," according to the same report.
What is unresolved?
The rule does not say which security expectations apply to apps that hold records once a patient has directed them there. The preamble leaves that to the app's own terms. State access deadlines also still matter: the rule's preamble lists states with periods as short as 15 days for some records, and for the shorter period it says the Department will deem fewer than 15 days practicable where federal or state law requires it. For how HIPAA applies to common AI tools, see this site's HIPAA and ChatGPT explainer.
Sources
- 1HIPAA Privacy Rule: Changes to Support Coordinated Care and Individual Engagement and Reduce Regulatory Burdens (final rule, FR Doc. 2026-23429, public inspection copy)
Federal Register / HHS Office for Civil Rightspublished read public-inspection.federalregister.gov
- 2Updated HIPAA privacy law sets rules for sharing health data with apps
Healthcare Divepublished read healthcaredive.com
How this story was checked
Automated source check, . Each claim below was compared with the source it cites before publication. Read our standards for what that check does and does not cover.
- The final rule reduces the time covered entities have to respond to an access request to no more than 15 calendar days, from 30, with one extension of up to 30 calendar days. Source 1
- The rule is effective 60 days after Federal Register publication, with a compliance date 240 days after publication. Source 1
- Developers of personal health apps used by individuals for their own purposes are not business associates and so are not subject to the HIPAA Rules, according to the rule's preamble. Source 1
- HHS estimates $784 million in new costs in the first year and net savings of $703 million annually in years two through five. Source 2
Tags: HIPAA · PHI · Healthcare · Business Associate Agreement
From the publisher
Sonomos publishes this newsroom and makes Locke, which detects patterns consistent with protected health information on a clinician's device and masks it before a prompt reaches an AI service.
Locke for healthcareGeneral information about privacy, security and AI, not legal advice. Laws and guidance change; check the dates above and the sources cited before relying on anything here.