Skip to main content
Patient Protect circular logo mark in purple and white used for site navigationPatient Protect
Compliance Operations

HIPAA and Personal Health Apps: When Patients Can Request PHI Through an App

When a patient wants records sent to a health app: what HIPAA's 2026 final rule says about app definitions, BAAs, readily producible formats, fees and timing.

Patient ProtectPatient Protect Editorial Team·November 17, 2026·18 min read

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.

Share
HIPAA and Personal Health Apps: Records, BAAs and Fees

A patient asks the front desk to send last month's visit notes to an app on their phone, and nobody is sure whether the practice may say no or needs a contract with the app company first. The 2026 Privacy Rule final rule answers both. We quote it where wording matters and mark our own reading as ours.

Where the rule stands

HHS announced the final rule, "HIPAA Privacy Rule: Changes to Support Coordinated Care and Individual Engagement and Reduce Regulatory Burdens," on November 16, 2026. It is Federal Register document 2026-23429, filed for public inspection and not yet published. It takes effect 60 days after publication, and compliance is required 240 days after publication; HHS says it "will not take action against them for noncompliance with the finalized requirements that occur before the compliance date." Until then the current HIPAA Privacy Rule applies, including its 30-day access deadline.

The right behind app delivery is not new. The current rule already requires an electronic copy in the form and format requested when it is readily producible, which HHS calls "a longstanding component of the individual right of access." The final rule adds a definition, names delivery "to or through the individual's personal health application" in 45 CFR 164.524(c)(3), bans fees for internet-based access, and shortens the clock. HHS said in its 2021 proposal that a personal health app developer would not be a business associate, and its position on app security concerns cites a 2019 HHS FAQ.

The full set of changes is in our guide to the 2026 HIPAA Privacy Rule final rule.

App-related changes in the 2026 final rule

  • 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)

“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.

What counts as a personal health application

The final rule adds this definition to 45 CFR 164.501:

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.

The test is who runs the information and for whose benefit. HHS says the definition "generally is technology neutral, with the caveat that the app must be electronic." The information has to be managed, shared and controlled by or primarily for the patient, and the app drops out if any of those is done by or primarily for a covered entity, or primarily for someone else. A developer can still run part of the service "primarily for the individual."

HHS's examples of what likely qualifies: an app connected to a fitness tracker the patient selected for their own use, a wellness app the patient selected, Individual Access Services from an IAS Provider in TEFCA, and a patient-facing app in the Medicare App Library. What does not: your patient portal app, whose information is managed for the practice "even though the individual may benefit from it," and an app that an entity running a clinical trial gives a participant.

HHS classifies product by product: where a developer is a business associate for one product, "other products or technologies offered by the technology developer may meet the definition."

Commenters asked whether an app a provider recommends would count; the rule does not answer directly. Our reading is that a recommendation alone does not change who manages, shares and controls the information. If you have a contract with the developer, look at what it does for you under it.

Why the patient's app is not your business associate

The preamble is direct:

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.

HHS interprets "a personal health app to be equivalent to the individual," so a request to send records to one is the patient's own request for a copy, not a directive to a third party. Such apps "are not entities that are regulated under HIPAA," though they "may be regulated by other law."

The other side of the line is just as clear. Developers of apps "for or on behalf of covered entities or business associates likely are business associates of the covered entity or subcontractors of the business associate." HHS applies that to devices: where a covered entity provides a fitness tracker, "the developer of the app connected to the fitness tracker likely would be a business associate. Thus, the app would not meet the definition of a personal health app."

One sentence holds in both directions: "The existence or absence of a business associate agreement between a covered entity and a person does not determine whether the person is a business associate of that covered entity." A signed BAA does not turn a patient's app into your vendor, and a missing one does not excuse a vendor that is. For those vendors, see our business associate agreement checklist.

Does a health app need a BAA? Classify by function

Both shortcuts are wrong. "Apps never need a BAA" fails on your vendor's portal app and the app tied to a device you issue. "Every app needs a BAA" fails on the app the patient picked.

What the app is Personal health app? The BAA question
An app the patient chose for their own use, such as a wellness app Yes, if the information is managed, shared and controlled by or primarily for the patient No BAA with your practice. The developer is not acting for you
Your patient portal app, or one your EHR vendor offers patients for you No The vendor is generally your business associate, so the relationship belongs under a BAA
An app or device you build, supply or contract for No Its developer likely is your business associate, so it belongs under a BAA
An app run primarily for someone else, such as a research organization's study app No Not settled by the definition. Treat the request as a directive or an authorization

On the last row, HHS says a request to send PHI to such an app "may constitute a request pursuant to the right of access to direct (and would be subject to that right's limitations), depending on the nature and scope of the request." That right covers an electronic copy of PHI in an electronic health record; requests outside it "should be treated as requests made pursuant to an authorization" where they qualify as one.

Demanding a BAA from a patient's app has a cost. Where a practice offers app connections, HHS lists "requiring a person who does not meet the definition of a business associate to enter into a business associate agreement with the covered entity" as an unreasonable registration requirement, and says a provider "may not prevent an app from registering solely because the app does not have a business associate relationship and agreement with the covered entity."

Readily producible: what you must do, and what you need not buy

Under § 164.524(c)(2), a practice must provide access in the form and format requested if it is readily producible that way; if not, in a readable hard copy or another agreed form and format, and for electronic records requested electronically, a readable electronic form and format both sides agree on. HHS calls this "a matter of capability, not willingness": if you can produce what the patient asked for, you cannot steer them elsewhere.

Does every practice need an API? No. 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 HHS says "we do not specifically require covered entities to adopt APIs or other technology that enables access through personal health apps."

But there is a floor. HHS says a practice that keeps PHI electronically "must have the capability to provide some form of electronic copy of PHI maintained electronically," and "email generally is considered readily producible by all covered entities (except in the limited case where email cannot accommodate the file size of requested images)." If the patient declines every electronic format you can readily produce, a readable hard copy satisfies the request.

Capability you have, or other law requires, counts. New § 164.524(c)(2)(iii) says that where another federal or state law applicable to the practice requires a particular electronic form and format, the PHI "is deemed readily producible in such form and format." Where a practice "has chosen, or is required by other Federal or state law, to implement such technology or participate in TEFCA or the CMS Aligned Networks to enable access to requested PHI," HHS says "we will deem that PHI to be readily producible in that form and format for purposes of the right of access." HHS also treats PHI as readily producible in a format you already use to send PHI to other parties, such as other providers, where sending it to the patient's app adds no more risk to your systems.

That calls for an inventory of what your EHR, portal and any network participation deliver today. Where a vendor offers an app connection you have never switched on, the rule's language about technology a practice "has chosen" or "otherwise implemented" leaves room for argument. Our advice: ask the vendor what is live for your practice and decide on purpose, with a record of why. Where some content, such as certain images, cannot go through the app, send what can and provide "the balance of the PHI in a mutually agreed upon form and format."

Your own systems' risk is part of the test, as informed by your Security Rule risk analysis: a practice "is not expected to tolerate unacceptable levels of risk to the security of the PHI on its systems," though HHS believes that when a practice controls its systems' ability to transmit to an app, that risk is generally low. What happens afterwards does not count: readily producible "is not based on the level of privacy or security risks to the PHI once it has left" the practice's systems.

To see where your practice stands on app requests and the rest of the rule, take the 2026 Privacy Rule readiness check.

What you may and may not do about app security concerns

The worry is reasonable, since a personal health app is outside HIPAA, but the decision stays with the patient.

You may tell the patient. HHS says "the covered entity may consider informing the individual of the potential risks involved when the individual makes the request." That is permitted, not required.

You may not refuse on that ground. A practice "is not permitted to deny an individual's right of access to their ePHI, where the individual requests that such access be provided 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." A patient may even ask for delivery "in an unsecure manner or through an unsecure channel."

Registration is allowed; delay is not. If you offer app connections, requiring every personal health app to register is not a denial, provided the process does not exclude an app capable of securely connecting to your secure, standards-based API. But registration "cannot be used as a basis to exceed the timeliness requirements," and onerous steps beyond what the Security Rule needs, a demanded BAA, or blocking an app because it competes with a service you or your vendor offer are among HHS's examples of going too far.

Your own security duties stay. A practice "remains responsible for maintaining awareness of and protecting ePHI in the face of new security vulnerabilities and threats." Risk to the patient's copy after it leaves is the patient's call.

What to say at the desk is our suggestion, not the rule's: "This app isn't covered by HIPAA, so once your records are in it, the app's own terms decide what happens to them. We'll send them now." Note that you said it. Do not turn it into a form or a wait; the rule bars request measures that impede access when a less burdensome one is practicable.

Fees: free through an automated connection, not free for everything

Under § 164.524(c)(4)(ii), a practice may not charge when the patient inspects PHI, or when the patient "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 says internet-based method refers "to automated processes for transmitting electronic copies," such as view, download and transmit in a portal or an app connection through certified API technology. Three things do not count:

  • A copy a staff member makes. The term "does not include circumstances that involve labor for making copies on the part of a member of the covered entity's workforce," and HHS's example is one "where a PDF is emailed to the individual at the request of the individual."
  • A request that merely arrives electronically. "The submission of an access request through an electronic method, or a request for electronic delivery of a copy, does not by itself mean that the individual is using an internet-based method for which no fee may be charged."
  • Paper records bound for an app. A workforce member has to copy them into electronic form, so the method is not internet-based.

Where a fee is allowed, it is a reasonable, cost-based fee limited to labor for copying, supplies for a non-electronic copy, postage for a mailed non-electronic copy or summary, and preparing an agreed summary. For a staff-made electronic copy that means labor only: copying records into a PDF or onto a USB drive is chargeable labor; the media and postage are not. Searching for and retrieving records never is.

The fee rule is a ceiling, not a floor. State law may set lower limits, and the 2016 methods, including the $6.50 flat fee, are superseded. If you charge anything, you must post a fee schedule on your website, if you have one, and make it available at the point of service and on request. More in our article on medical records fees under the 2026 final rule.

So: access through an automated, internet-based method such as an app connection is free; an electronic copy a staff member makes may carry a labor fee. Electronic access in general is not automatically free.

The 15-day clock applies to app requests

Section 164.524(c)(3) ties delivery, including to a personal health app, to the timeliness rule. From the compliance date a practice must act "as soon as practicable, but no later than 15 calendar days after receipt of the request," with one extension of no more than 30 calendar days, explained in writing within the first 15. A shorter deadline in other law is deemed practicable, and HHS "encourages covered entities to view the 15 calendar days as an outer limit, particularly for requests for electronic copies of ePHI."

Discussing scope and format with the patient is permitted, but "such discussion shall not extend the time allowed," and neither does app registration.

The request can come from the app itself. HHS treats it as "in writing" when the practice receives "a notification or other electronic transmission from a personal health app that contains the information necessary to document the individual's exercise of the right." Our reading is that the clock starts when that transmission arrives, as it would for an email. HHS adds that requiring requests through only one electronic method, when others are practicable, "generally would be unreasonable."

Business associates that hold the records

The system that could serve an app may belong to a vendor. The final rule codifies HHS's position that the business associate agreement decides whether the vendor answers the patient directly or hands the records to the practice, and that "In all cases, the covered entity remains ultimately responsible for ensuring that the requested PHI is provided." A practice "may not avoid its access obligations on the basis that its business associate maintains the requested PHI."

Existing business associate agreements get a transition period, but nothing in it "shall alter the requirements of a covered entity to comply with" § 164.524 for PHI a business associate holds. For each vendor that holds records, we recommend writing down which app connections are live, who answers a request, how fast, and how you learn one arrived.

A front-desk procedure for app requests

These steps are how we would run it in a small practice. None conflicts with the current rule.

  1. Date it on arrival, with the channel: in person, email, portal, paper or an app notification.
  2. Sort it. The patient's own copy, including to their app? A directive to send an electronic copy from your EHR to someone they designate? Or an authorization?
  3. Verify identity without adding friction. Verification is still required, but a practice "may not impose unreasonable verification measures on an individual that would impede the individual from exercising a right."
  4. Check the inventory. Can this record go to this app, portal or email? Send what can; agree a format for the rest.
  5. If the app concerns you, say so once and proceed.
  6. Apply the right fee rule. Nothing through an automated, internet-based method; at most a labor fee for a staff-made electronic copy.
  7. Send and record it. If you cannot finish in time, the written extension notice goes out inside the first 15 days (30 under the current rule), and there is only one per request.

What the workforce needs to know

We would train staff never to say these, because the rule contradicts each one:

  • "We don't send records to apps." Not if a copy is readily producible that way.
  • "That app isn't HIPAA compliant, so we can't." Concern about the app is not grounds to refuse.
  • "The app company has to sign our BAA first." A patient's app is not your business associate.
  • "There's a fee to send it to your app." Not through an automated, internet-based method.
  • "It takes 30 days." Thirty days is today's outer limit, not a waiting period; from the compliance date it is 15.

Under the final rule your Notice of Privacy Practices must describe the right to obtain a copy "at limited cost or, in some cases, free of charge," so the front desk should be able to explain what that means here. The wider workflow is on our HIPAA right of access page.

Apps, AI tools and which side of the line they sit on

Patient Protect welcomes patients using apps, including AI tools, to read and organize their own records. The rule shares the premise: "Individuals increasingly are choosing to use technology to access and manage their health information."

The work is knowing three things about any tool that touches a patient's records: whose tool it is, what authority moves the records (the access right, a directive or an authorization), and what governs them afterwards (the app's own terms, or your vendor under a BAA and your Security Rule program). The same questions apply when a practice adopts an AI tool for its own work: a tool that handles PHI on the practice's behalf sits on the business associate side of the line, for the reasons HHS gives about apps developed for covered entities. That is our reading of how the logic carries over; HHS does not address AI here.

Where Patient Protect fits

Patient Protect is a security-first HIPAA compliance platform for independent healthcare practices. What exists today for app requests:

  • Policy and procedure starters you can revise to cover app requests, with version history and workforce acknowledgment tracking.
  • HIPAA Foundations training for the workforce baseline, with your app-request procedure as the practice-specific layer.
  • Vendor & BAA Governance, which tracks every business associate agreement and its state, so you can see where each vendor agreement stands before you revisit it.
  • Compliance Evidence & Records for your capability inventory, fee schedule versions and the reasons behind decisions.

If the platform adds anything specific to this rule, the features page will say so. No software makes a practice compliant on its own; these decisions stay with you.

Frequently Asked Questions

Can a patient get their medical records through an app?

Yes. A patient can ask a practice to send a copy of their PHI to or through a personal health app they chose, and the practice must do it when a copy is readily producible that way.

Does a health app need a BAA?

It depends on whom the app works for. An app the patient chose for their own use is not your business associate and needs no BAA from you; an app or device your practice builds, supplies or contracts for likely has a developer that is.

Can a provider refuse to send records to an app?

Not because of concerns about the app's privacy or security alone. If a copy is not readily producible to that app, the practice provides another agreed electronic form and format, or a readable hard copy if the patient declines every electronic option.

Does every practice need an API?

No. The final rule does not require APIs or other new technology to reach patient apps, but a practice that keeps records electronically must be able to produce some electronic copy, and HHS considers email generally readily producible.

Can we charge a fee for sending records to a patient's app?

Not when the patient gets them through an automated, internet-based method such as an app connection. Where staff have to make the copy, such as an emailed PDF, a reasonable, cost-based labor fee is permitted.

Does the 15-day deadline apply to app requests?

Yes, from the compliance date, 240 days after the rule publishes. HHS will not act on it before then; until it does, keep meeting the current 30-day deadline.


Sources. Every quotation here is from the final rule as filed for public inspection, Federal Register document 2026-23429, including its regulatory text and preamble. The full source list is in our guide to the 2026 HIPAA Privacy Rule final rule.

This article is general educational information, not legal advice. Evaluate HIPAA alongside applicable state law and other federal law.

Was this useful? Share it.

Share

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.

Submit a correction →

What would an OCR investigator find on your website?

Free 30-second scan — tracking pixels, security gaps, missing policies. See what’s visible before they do.

Subscribe to HIPAA Pulse.

Breach alerts, enforcement updates, and compliance intelligence — every two weeks.

© 2026 Patient Protect LLC. All rights reserved. Content may not be reproduced, scraped, or used to train AI models without written permission. Terms · DMCA