On November 16, 2026, the HHS Office for Civil Rights (OCR) filed its final rule, "HIPAA Privacy Rule: Changes to Support Coordinated Care and Individual Engagement and Reduce Regulatory Burdens" (FR Doc. 2026-23429), for public inspection. It finalizes, with changes, a proposal OCR published in January 2021. Much of it is about how individuals get their own health information, which makes it directly relevant to anyone building on patient access APIs.
For app developers, the headline is one sentence of regulatory text: a covered entity may not charge an individual who accesses their electronic records "using an internet-based method, such as a personal health application." This post explains what that sentence covers, what it does not, and the other changes that come with it.
Key dates
The public inspection copy leaves its effective and compliance dates as placeholders that count from publication (PDF p.1). The dates below assume the scheduled November 19 publication. Select a date for details.
Timeline
From proposal to compliance
PassedUpcoming
The rule takes effect
The rule is effective 60 days after publication. If it publishes on November 19 as scheduled, that is January 18, 2027.
The fee rule in its own words
(ii) A covered entity may not impose a fee in either of the following circumstances:
(A) An individual inspects the protected health information about the individual, as described at (a)(1) of this section.
(B) 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.
Two things set the reach of that sentence: who is protected, and how the records travel.
The protected party is the individual, or their personal representative. The sentence limits what a covered entity can charge them. It does not mention anyone else.
The method is defined by labor, not by the wire. OCR reads "internet-based method" to mean "technology that relies on the internet, such as patient and health plan member portals, personal health apps, and APIs, as well as similar successor technologies, to obtain a copy of PHI without requiring a member of the covered entity's workforce to invest labor in making such a copy" (PDF p.173). So a PDF that staff prepare and email at the individual's request is not an internet-based method, even though it arrives over the internet (PDF p.169).
Where a fee is still allowed, it must be reasonable and cost-based, covering only the labor of copying, supplies for a non-electronic copy, postage when the individual asks for mail, and preparing a summary the individual agreed to (§ 164.524(c)(4)(i)). This replaces OCR's 2016 fee guidance, including its $6.50 flat fee option (PDF p.170). A covered entity that charges for copies must also post a fee schedule on its website, if it has one, listing every free type of access and its standard fees (§ 164.525).
Can they charge for this
The answer depends on two things: who would pay, and how the records are accessed. Pick a combination to see what the rule says, with links to the pages it comes from.
Interactive
Pick a scenario
Pick who the health plan or provider would charge, and how the records are accessed.
Free
Access through a personal health app, a patient or member portal, or an API is an internet-based method. OCR reads that term to cover technology that gets a copy to the individual without a workforce member having to make it. OCR’s own fee chart lists a personal health app connection through a secure, standards-based API as free. This covers records that are already electronic: paper records that staff must copy into electronic form for the app are not internet-based access.
“A covered entity may not impose a fee ... [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.”
OCR summarizes the same rules in a chart (PDF pp.181 to 182). In short:
| How the records are accessed | Who receives them | Fee under the final rule |
|---|---|---|
| In-person inspection | The individual | Free |
| Internet-based method, such as a personal health app over an API | The individual | Free |
| Electronic copy made by staff, such as on a USB drive | The individual | Cost-based, limited to labor |
| Paper copy | The individual | Cost-based: labor, supplies, postage |
| Electronic copy from an EHR, sent to a designated third party | The third party | Not addressed by this rule |
What changed from the 2021 proposal
OCR proposed these changes in January 2021 (86 FR 6446). Nearly six years later, the free-access proposal survives in substance. Several others did not. Filter the list to see each group.
2021 proposal vs. final rule
What OCR kept, changed, and dropped
Showing 10 of 10
Free electronic access
Adopted- Proposed in 2021
- Free for in-person inspection and for internet-based access, including a personal health app connecting to a secure, standards-based API.
- Final rule
- Free for inspection and for access “using an internet-based method, such as a personal health application.”
Response deadline
Changed- Proposed in 2021
- 15 calendar days, with one 15-day extension.
- Final rule
- 15 calendar days, with one 30-day extension. A shorter deadline in other federal or state law is treated as the practicable one.
Personal health application
Adopted- Proposed in 2021
- A new definition, excluding apps run by or primarily for a covered entity or “another party such as the application developer.”
- Final rule
- Defined in § 164.501, with the developer example removed and “party” replaced by “person.”
Fee notice
Changed- Proposed in 2021
- A posted fee schedule, plus individualized estimates and itemized statements on request.
- Final rule
- A fee schedule on the website and at the point of service. Estimates and itemized statements are not required.
Fees for third-party copies
Dropped- Proposed in 2021
- Limit fees for electronic copies sent to a person the individual designates, by a non-internet method, to labor costs.
- Final rule
- Not addressed. OCR says it will keep monitoring these fees.
Right to inspect
Dropped- Proposed in 2021
- Add the right to view, take notes, and take photographs during in-person inspection.
- Final rule
- Not finalized. The existing right to inspect stays as it is.
Oral requests to direct copies
Dropped- Proposed in 2021
- Require covered entities to act on oral requests to send records to a third party.
- Final rule
- Not finalized. A request must be clear, conspicuous, and specific, and may be required in writing.
Requests relayed by another provider
Dropped- Proposed in 2021
- Require providers and plans to submit an individual’s request to another provider on their behalf.
- Final rule
- Not finalized.
Minimum necessary for care coordination
Dropped- Proposed in 2021
- An exception to the minimum necessary standard for individual-level care coordination and case management.
- Final rule
- Not finalized. The minimum necessary standard still applies.
Notice of Privacy Practices acknowledgment
Adopted- Proposed in 2021
- Remove the requirement to get a written acknowledgment that the patient received the notice.
- Final rule
- Removed.
Personal health apps, defined
The new definition in § 164.501 decides which path an app request takes.
Personal health application means an electronic application used by an individual to access health information about that individual, which can be drawn from multiple sources, provided that all of the following conditions apply:
(1) Such information is managed, shared, and controlled by or primarily for the individual.
(2) Such information is not managed, shared, or controlled in any of the following manners: (i) By or primarily for a covered entity. (ii) Primarily for another person.
A personal health app
The information is managed, shared, and controlled by or primarily for the individual.
- An app the individual picks for their own purposes
- A fitness tracker or wellness app they chose themselves
- A TEFCA IAS Provider, or a patient-facing app on CMS Aligned Networks, used for their own purposes
A copy sent through it is a copy to the individual, and internet-based access is free.
Not one: run for a covered entity
The information is managed, shared, or controlled by or primarily for a covered entity or its business associate.
- A health plan’s or provider’s own portal app
- A fitness tracker app a covered entity provides
The developer is likely a business associate, inside HIPAA.
Not one: primarily for another person
The information is managed, shared, or controlled primarily for someone other than the individual.
- A clinical trial app
- An app run for a medical product company’s research
A request to send data there may be a right of access to direct request, with its limits.
The distinction has real consequences. OCR treats a copy sent through a personal health app as a transmission to the individual: an exercise of the right to get a copy, not the right of access to direct (PDF p.141). That keeps it inside the free-access rule and the 15-day clock.
OCR also closes off a familiar objection. A covered entity may not deny access through a personal health app "based solely on the covered entity's concerns that the app developer will not adequately protect the privacy of the individual's ePHI or because the app does not encrypt the individual's data at rest" (PDF p.111).
What it means for developers building patient access apps
Free to the patient
When a member connects an app to their health plan's Patient Access API, or a patient connects an app to a provider's FHIR API, they are accessing electronic records through an internet-based method. Under the final rule, the plan or provider may not charge them for it.
API formats count as readily producible
When other federal or state law requires access in a particular electronic form and format, the rule deems that format readily producible (§ 164.524(c)(2)(iii)). OCR applies the same treatment where a covered entity has chosen, or is required, to implement technology such as a secure, standards-based API, or to participate in TEFCA or CMS Aligned Networks (PDF p.143). By that reading, a payer that CMS requires to run a Patient Access API, under the Interoperability and Patient Access rule or the Interoperability and Prior Authorization rule (CMS-0057-F), cannot refuse an app request on format grounds for records the API can produce. OCR notes that not all records will be readily producible in the requested format, giving images as an example, and those may come in another format (PDF p.143). The rule does not, on its own, require any covered entity to build an API (PDF p.141).
Faster than 15 days where other law says so
Where other federal or state law requires access in fewer than 15 days, OCR treats the shorter period as the practicable one. It names the CMS Interoperability and Patient Access rule and the Interoperability and Prior Authorization rule among those regulations (PDF pp.133 to 134). OCR adds that a delay can still be interference under the information blocking regulations even when the request is filled within 15 days (PDF p.134).
Requests through apps and networks are written requests
A request counts as "in writing" when it documents the individual's exercise of the right of access. OCR gives two examples: a request sent through a QHIN from a TEFCA IAS Provider that is also a personal health app, and a request from a patient-facing app on CMS Aligned Networks that is a personal health app. Covered entities also may not impose measures that impede access when a less burdensome measure is practicable for them (PDF p.123).
Know whom your app works for
An app run for a covered entity, or primarily for another person such as a research sponsor, is not a personal health app. A request to send records to it may be a right of access to direct request, which reaches only electronic copies of records in an EHR, and whose fees this rule leaves open (PDF p.106, § 164.524(d)(1)).
Developer fees are a question for other rules
The rule does not address what plans, providers, or their vendors charge developers. In its discussion of fees, OCR cites ONC's view that charging "an individual, their personal representative, or another person designated by the individual for electronic access to the individual's EHR would be inherently suspect under an information blocking review," and notes that CMS's Interoperability and Patient Access rule "also includes certain fee limitations" (PDF p.175).
Where Flexpa fits
Flexpa provides one FHIR API for patient-authorized records from health insurers, medical record systems, and TEFCA Individual Access Services, with Flexpa Consent handling sign-in and authorization. Flexpa was selected as a CMS Aligned Network early adopter in 2025. The final rule does not change how those connections work. It does settle HIPAA's terms for the patient's side of them: no fee to the individual for internet-based access, a 15-day initial deadline with one possible 30-day extension, and a defined meaning for personal health application.
Frequently asked questions
Does the rule ban charging for app access?
Partly. It bars a covered entity from charging an individual who accesses their electronic records through an internet-based method, such as a personal health app. It does not address fees charged to app developers, and it leaves fees for right of access to direct copies sent to a third party unaddressed. Disclosures under the individual's authorization keep their own limit, generally a reasonable, cost-based fee to prepare and transmit the records.
Does the rule require providers or plans to build an API?
No. OCR says the rule "does not independently require the implementation of technology or policies" for providing copies through a personal health app. Where a covered entity already has that technology, or other law requires it, the format is treated as readily producible.
Can a covered entity refuse an app because of the app's privacy practices?
Not on that basis alone. OCR states that a covered entity may not deny access through a personal health app based solely on concerns that the developer will not adequately protect the data, or because the app does not encrypt data at rest.
Are personal health app developers business associates?
Not because of the personal health app. OCR states that a personal health app developer is not a business associate, because in offering the app it does not act for or on behalf of a covered entity. The same developer may still be a business associate for other products or services it offers, and a developer who builds apps for or on behalf of a covered entity likely is one.
When do covered entities have to comply?
240 days after the rule is published in the Federal Register. If it publishes on November 19, 2026 as scheduled, that is July 17, 2027. The rule takes effect 60 days after publication, and entities may comply earlier.
Sources
- FR Doc. 2026-23429, HIPAA Privacy Rule: Changes to Support Coordinated Care and Individual Engagement and Reduce Regulatory Burdens, public inspection copy, filed November 16, 2026.
- Federal Register public inspection listing for FR Doc. 2026-23429, with the scheduled publication date.
- Proposed Modifications to the HIPAA Privacy Rule To Support, and Remove Barriers to, Coordinated Care and Individual Engagement, 86 FR 6446, January 21, 2021.
Page numbers refer to the 363-page public inspection copy and will differ from the published Federal Register pages. This post is general information, not legal advice.



