- Published
- Updated
- 8 min read

TL;DR: Healthcare AI browsing falls under the same HIPAA rules as any other tool that touches patient data. If an AI browser or agent vendor creates, receives, maintains or transmits protected health information for you, it is a business associate and needs an agreement. "Anonymous" questions can still identify patients. Start with an inventory and a risk analysis.
Healthcare AI browsing is when a clinician, biller or front desk staffer uses an AI browser, assistant or agent to research, summarize, fill forms or work inside web portals. In many offices it arrives one person at a time, without anyone deciding it should.
The earlier version of this post claimed new Massachusetts rules, named hospitals that had supposedly built special systems, and quoted compliance percentages we could not trace. None of that held up, so I rewrote it around what the HIPAA regulations actually say. The good news: you do not need new rules to handle healthcare AI browsing. You need to apply the ones you already have.
What is healthcare AI browsing, and where does HIPAA come in?

HIPAA does not care what kind of software you use. It cares whether protected health information goes into it, and who holds it afterward. A typed prompt, a pasted lab result, a dictated note and a screenshot of a scheduling screen are all the same thing to the rule if they identify a patient. That is why HIPAA questions show up the moment healthcare AI browsing starts.
What counts as identifying in healthcare AI browsing
The de-identification rule lists 18 kinds of identifiers that must be removed for the Safe Harbor method. Most are what you would expect: names, dates, phone numbers, medical record numbers. A few matter more for healthcare AI browsing than people realize. The list includes "Web Universal Resource Locators (URLs)," "Internet Protocol (IP) address numbers," "Biometric identifiers, including finger and voice prints," and "Any other unique identifying number, characteristic, or code." (45 CFR 164.514, eCFR (opens in a new tab))
So a browser history full of patient portal links, or a voice command that names a patient, can carry identifiers even when nobody typed a name. We wrote about the voice side in voice-activated browsing risks.
Covered entities and the people who work for them
A practice, a health plan or a clearinghouse is a covered entity. Your staff are part of your workforce. The software they use, and the companies behind it, are where the next question comes in.
When does an AI vendor become a business associate?

The regulation defines a business associate as a person or company that, on behalf of a covered entity, "creates, receives, maintains, or transmits protected health information" for a regulated function, and it names "data analysis, processing or administration" among those functions. (45 CFR 160.103, eCFR (opens in a new tab))
An AI service that receives a patient's details in a prompt and keeps the conversation fits that description on its face. The Privacy Rule then says a covered entity may let a business associate "create, receive, maintain, or transmit protected health information on its behalf" only if it "obtains satisfactory assurance" in a written agreement. (45 CFR 164.502, eCFR (opens in a new tab))
The practical test for healthcare AI browsing tools
Ask one question about every AI tool your team uses: will the vendor sign a business associate agreement for the plan we are on? If the answer is no, or "not on that tier," patient information does not go into it. That one rule settles most healthcare AI browsing questions before they start. MyRHC keeps a plain reference on HIPAA business associate requirements (opens in a new tab) if you want the full text and obligations.
What to ask before you sign
- Where are prompts, files and browsing history stored, and for how long?
- Is our data used to train or improve models, and can that be turned off in writing?
- Which subcontractors process the data, and do they sign agreements too?
- Can we export and delete everything when we leave?
- What logs do we get, so we can see what the agent did and when?
Can "anonymous" questions still identify a patient?

Yes, and this is the part of the old post that was right in spirit. Leaving out the name is not the same as de-identifying.
Latanya Sweeney's well-known analysis of 1990 census data found that "87% (216 million of 248 million) of the population in the United States had reported characteristics that likely made them unique based only on {5-digit ZIP, gender, date of birth}." (Data Privacy Lab, Simple Demographics Often Identify People Uniquely (opens in a new tab)) The HIPAA rule reflects the same idea. Under Safe Harbor, ZIP codes go except "the initial three digits," and only where that three-digit area is large enough by Census data. (45 CFR 164.514, eCFR (opens in a new tab))

What that means for healthcare AI browsing
A question like "treatment options for a 34-year-old woman in a small town with this rare condition, seen last Tuesday" names nobody and may still point to one person. The other route the rule allows is expert determination: a qualified person "with appropriate knowledge of and experience with generally accepted statistical and scientific principles" finds the risk of re-identification "very small." (45 CFR 164.514, eCFR (opens in a new tab)) A clinician typing into a chat box is not doing that analysis. Treat detailed clinical questions as PHI and send them only to tools covered by an agreement.
What does the Security Rule already require?

More than most practices use. Three requirements map straight onto healthcare AI browsing.
Risk analysis
The Security Rule requires an "accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity, and availability of electronic protected health information." (45 CFR 164.308, eCFR (opens in a new tab)) If staff use AI browsers with patient data, those tools belong in the analysis. NIST's resource guide for the Security Rule, SP 800-66 Revision 2, maps each standard to practical controls. (NIST SP 800-66 Rev. 2 (opens in a new tab))
Audit controls and minimum necessary
The rule requires "mechanisms that record and examine activity in information systems that contain or use electronic protected health information." (45 CFR 164.312, eCFR (opens in a new tab)) An AI agent that clicks through your portal is activity, and you want a record of it. The Privacy Rule adds that you make reasonable efforts to limit PHI "to the minimum necessary to accomplish the intended purpose." (45 CFR 164.502, eCFR (opens in a new tab)) For healthcare AI browsing, that means pasting the one value a task needs, not the whole chart.
The 2025 Security Rule proposal is still a proposal
HHS published proposed Security Rule changes in the Federal Register on January 6, 2025, with comments due March 7, 2025. The Federal Register still lists that document's legal status as a proposed rule. (Federal Register (opens in a new tab)) The federal regulatory agenda now lists it under "Long-Term Actions," with final action shown for July 2027. (Reginfo.gov, RIN 0945-AA22 (opens in a new tab)) The current rule is what applies today. I wrote more on what the proposed HIPAA Security Rule changes mean for a small practice (opens in a new tab).
Where does prompt injection fit in healthcare AI browsing?

An AI agent that browses for you reads everything on the page, including text a person never sees. OWASP describes indirect prompt injection as what happens "when an LLM accepts input from external sources, such as websites or files." (OWASP GenAI Security Project, LLM01:2025 (opens in a new tab))
In healthcare AI browsing, picture an agent logged in to your billing portal that also opens an outside web page with hidden instructions. The agent now holds access to PHI and is reading text written by a stranger. Keep agents that browse the open web out of sessions that are logged in to patient systems. Our general guide to AI browser safety risks covers the basics, and identity and access management for AI navigation covers separating accounts.
What is a sensible healthcare AI browsing plan for a small practice?

Here is a hypothetical. A four-provider physical therapy practice in Northborough finds that its front desk uses one AI assistant for insurance research and a provider dictates notes into another. Nobody signed anything. A plan that fits a practice that size:
- Inventory. List every AI tool and browser extension in use, who uses it, and what data goes in. Ask staff directly; this is not a blame exercise.
- Sort by agreement. Tools with a signed business associate agreement can see PHI under your policy. Tools without one get none.
- Write a one-page rule. What may go into which tool, in plain words, with two examples of each.
- Separate sessions. A browser profile logged in to the EHR or billing portal does not run an agent that browses the open web.
- Turn on logs. Keep a record of what agents did, so you can answer questions later.
- Add it to the risk analysis. Write down the risks you found and what you did about them, and revisit it when tools change.
This is the same thinking behind zero trust for medical offices: check every request, give each tool only what it needs, and keep one compromised account from reaching everything.

Frequently asked questions
Is healthcare AI browsing allowed under HIPAA?
HIPAA does not ban any kind of software. It sets rules for protected health information. If a tool will hold PHI for you, the vendor is a business associate and you need a written agreement first.
Do I need a business associate agreement with an AI vendor?
If the vendor creates, receives, maintains or transmits PHI on your behalf, yes. If it will not sign one for your plan, keep patient information out of that tool.
Is removing the patient's name enough to make a question safe?
No. HIPAA lists 18 identifier types, including dates, small-area geography, URLs and voice prints, and combinations of details can point to one person. Treat detailed clinical questions as PHI.
Has the new HIPAA Security Rule taken effect?
No. HHS published proposed changes in the Federal Register in January 2025, and they are still listed as a proposed rule. The current Security Rule is what applies.
What should a small practice do first?
Inventory every AI tool staff use and what data goes in. Then sort them by whether a business associate agreement is in place, and add them to your risk analysis.
This article is general information, not legal advice. Kief Studio is not a law firm, and reading it does not create an attorney-client relationship. Laws and regulations change, so check the current text and talk with a licensed Massachusetts attorney about your situation.
Where we fit

Healthcare AI browsing is a data flow problem first and a paperwork problem second. Our HIPAA and compliance consulting starts by mapping the rules that apply to you and where regulated data actually lives, then reviews controls and system design against those rules and against real attack paths. We close the gaps in the systems first, then bring the documentation in line. We are not your auditor of record, and we keep those roles apart.
If the issue is how access is designed, a security architecture review or zero trust architecture work puts identity checks and least privilege in front of each system. We are in Shrewsbury and work with practices across Massachusetts.
First conversation is free. No commitment.




