Last verified: September 16, 2026. Vendor coverage changes without notice, so this post is checked and dated on a standing schedule. Updates are logged at the bottom.
Every Medicare agent has run into the same wall. A client emails about a new diagnosis and whether the plan covers the specialist. The agent wants to draft a clear reply, or summarize the plan documents, or pull a follow-up list out of a messy set of notes. And somewhere in the back of their head is the rule they have heard at every carrier training for three years running: do not put client information into AI.
That rule was doing real work. It was also blunt enough that it stopped a lot of people from using AI for anything at all.
Google just changed one of the documents that rule was built on. What changed is narrower than "go ahead now," and the narrow version is the useful one. The same logic then applies to every other AI subscription your agency pays for, and the answer for most of them is probably not what you would guess from the price on the invoice.
First, the contract nobody explains
HIPAA does not care what software you like. It cares about a contract.
The law splits the world into covered entities and business associates. A covered entity is a health plan, a health care provider, or a clearinghouse. Medicare, Medicaid, and the carriers whose plans you sell are health plans, so they are covered entities. You almost certainly are not one.
What you are, in most cases, is a business associate. When a carrier or a plan hands you protected health information so you can do work on its behalf, you are handling that information as an extension of them, and since the HITECH Act you are directly liable for protecting it. That relationship gets written down in a Business Associate Agreement, a BAA. The BAA is the piece of paper that says: I am handling your clients' health information, here is what I will do with it, here is how I will protect it, and here is what happens if I do not.
Now apply that one level down. When you type client information into a piece of software, that vendor is handling PHI on your behalf, which makes the vendor a business associate too. Which means the vendor needs a BAA with you.
That is the whole mechanism. A tool is not HIPAA compliant or not compliant as a feature of the software. It is either a tool you hold a BAA with, configured the way that agreement requires, or it is not. Everything else is marketing.
What Google actually did
Google publishes a list called HIPAA Included Functionality. It is the list of services that fall inside the BAA Google offers its Workspace customers. Gmail has been on it for years. So have Calendar, Drive and the editors, Chat, Meet, Keep, Tasks, Groups, Sites, Voice for managed users, and Vault.
As of the list's August 31, 2026 revision, three more entries sit alongside them: the Gemini app, the Gemini Mac app, and Gemini in Workspace.
Gemini in Workspace is the one that changes how you work. That is the AI sitting inside Gmail and Docs and Meet, the one that offers to draft the reply or summarize the thread you already have open. Until now an agency with a Google BAA had a strange split: the email carrying a client's health question was covered, and the AI button three inches to the right of it was not. That split is gone.
One absence on the list is as important as the additions. Gemini in Chrome is explicitly excluded, and the exclusion is written right into the entry.
Paying Google is not the same as being covered
This is the part that catches the most people, and it caught me when I checked my own account.
Google One is not Google Workspace. Google One is the consumer subscription attached to a personal Google account. It is where Google AI Plus, Google AI Pro, and Google AI Ultra live. Those plans give you the best Gemini models, generous storage, and deep integration into Gmail and Docs. They are excellent products. They come with no BAA, no Admin console, and no HIPAA coverage of any kind, because they are consumer services sold to an individual.
Workspace is the business product. Your domain, your admin, per-user licensing, and the Admin console where the BAA actually gets accepted. Gemini has been bundled into the Workspace business tiers since early 2025, so a Workspace subscriber generally already has the Gemini that is now covered.
If you pay Google every month and you are not sure which one you are on, look at your email address and your admin access. A personal gmail.com address with an AI Pro subscription is Google One. An address at your agency's domain, managed by someone with an Admin console, is Workspace.
The awkward edge is the solo producer. Google sells Workspace editions aimed at individuals without a full Admin console, and a subscription with no Admin console has nowhere to accept a BAA. If you are a one-person shop, confirm your exact edition with Google directly rather than assuming that paid means eligible.
Three conditions before any of this applies to you
You need a paid Workspace edition, not a consumer plan. See above. This is the single most common gap in small agencies.
A super administrator has to actually accept the BAA. It is not automatic and it is not retroactive. Someone signs in to the Admin console, goes to Account settings, then Legal and compliance, and accepts it. If nobody at your agency has ever done that, you do not have a BAA with Google, whatever the list says.
You have to keep PHI inside the covered services. Google is explicit that determining whether you are subject to HIPAA is your job, not theirs. A BAA on the account does not stop anyone from pasting a client's medication list into a surface that is not on the list. That is a configuration and training problem, and it belongs to you.
The Gemini Notebook question, and why it is a good example
NotebookLM was renamed Gemini Notebook in July 2026. Notebooks now sync with the Gemini app and can be created from inside it, which makes it reasonable to assume the coverage travels with the rebrand.
It is not that simple, and the reason is worth understanding because it repeats everywhere.
Gemini Notebook is not named on the Included Functionality list. Google's own announcement still calls it a standalone product with a standalone experience, and the list Google publishes is a list of named surfaces, not a list that assumes inheritance. Google listed the Gemini Mac app separately from the Gemini app rather than folding one into the other, and it carved Gemini in Chrome out of coverage even though Chrome's Gemini is every bit as much a part of Gemini as notebooks are. A list that names surfaces one at a time and excludes one of them by name is not operating on inheritance.
There is a second thing worth separating out, because Google uses three different phrases that sound interchangeable and are not. A core service is a Workspace service governed by your Workspace agreement. Enterprise-grade data protection means your data is not used to train models and stays inside your tenant. HIPAA Included Functionality is the list that sits under the BAA. NotebookLM became a core service with enterprise-grade data protection back in 2025. Neither of those put it under the BAA.
So the honest answer today: Gemini Notebook is not named, the reasoning that it should be covered is plausible, and plausible is not a standard you want to defend to a carrier. If your agency wants to use it with PHI, get Google to confirm coverage in writing before you do. That written answer is worth more than any blog post, including this one.
How the other tools compare
The same three questions apply everywhere. Is there a BAA, which plan does it require, and what does it leave out. Here is where the major tools stand as documented today.
Google. BAA available to paid Workspace editions, accepted by a super admin in the Admin console. Gemini in Workspace, the Gemini app, and the Gemini Mac app are covered. Gemini in Chrome is excluded. Gemini Notebook is not named. Google One consumer plans, including AI Pro and AI Ultra, have no BAA.
OpenAI. This one surprises people who assume a business plan is enough. ChatGPT Business is not BAA-eligible. OpenAI offers a BAA for ChatGPT Enterprise and Edu only on sales-managed accounts, plus purpose-built products including ChatGPT for Healthcare and ChatGPT for Clinicians, which has its own in-product BAA flow for individual clinicians. The API is the more accessible route: a BAA there does not require an enterprise agreement, though it does require Modified Retention. ChatGPT Plus and Free are not eligible.
Anthropic. Claude's BAA covers Claude Enterprise and the API, and the organization's Primary Owner activates it in settings. The exclusion list is long and specific, which is to Anthropic's credit and worth reading before you rely on it: Claude Console and Cowork sit outside the BAA, as do Claude Design, Slides and Docs in beta, and third-party integrations including MCP connectors, Enterprise Search, and Claude in Chrome. On the API side, Batch, Files, Skills, Code Execution, Computer Use and Web Fetch are not available to HIPAA-ready users. Claude Team is not listed as eligible.
Microsoft. Microsoft's HIPAA BAA lives inside the Online Services Data Protection Addendum and is available by default to commercial customers who are covered entities or business associates. Microsoft's own published list of in-scope services names Teams and Office 365. It does not name Microsoft 365 Copilot, and the Copilot it does name is Copilot for Security, which is a different product. Plenty of guides assert that Microsoft 365 Copilot is covered; confirm that against your own agreement rather than taking anyone's word for it. Microsoft 365 Personal and Family are consumer subscriptions with no BAA available. GitHub Copilot does not inherit the Microsoft 365 agreement either, which trips people up because both carry the Copilot name.
The pattern is consistent enough to be the real takeaway. Coverage lives on business and enterprise tiers and often on a specific configuration inside them. The consumer version of the same brand name is almost always outside the agreement, and the brand name on the screen tells you nothing about which side of the line you are standing on.
The one most agencies are missing
Nothing above covers the tool most likely to be sitting on your PHI right now, which is the AI notetaker joining your client calls.
An enrollment call where a beneficiary talks through their conditions and medications produces a transcript, a summary, and often an automatic email to whoever was on the invite. That transcript lives with a vendor that is almost never on a plan with a BAA, and the recording usually starts before anyone thinks about it. It is a bigger exposure than Gemini for most agencies, and it deserves its own treatment.
Is your AI notetaker HIPAA compliant? The question most agencies haven’t asked.
The part a BAA does not do
This is where I would slow down, because it is the mistake that survives everything above.
A BAA governs how the vendor handles what you send. It has no opinion on whether you should have sent it. Minimum necessary is still your standard, and it applies to a Gemini prompt exactly as it applies to an email. Covered does not mean unlimited.
HIPAA may not even be your binding constraint. Your carrier and FMO contracts carry their own data handling terms, CMS has its own rules for how you market and what you do with beneficiary information, and your state has privacy law of its own. Any one of those can be stricter than HIPAA. An agency that clears the HIPAA bar and violates a carrier's data policy has still lost the appointment.
None of this is legal advice, and it does not replace your compliance officer or your attorney. What it gives you is enough understanding to ask them a precise question instead of a vague one.
What if we have already been doing this?
A fair number of agencies reading this are going to realize they have been pasting client information into an uncovered tool for a while. That is a common situation and it is not a reason to panic, but it is a reason to stop guessing and get a professional involved today rather than next quarter.
Two things to do first. Stop the ongoing use, right now, before you investigate anything. And do not start deleting. Whether records need to be preserved is a question for counsel, and cleaning up before anyone has assessed it makes every later conversation harder.
Then bring your compliance officer or attorney a clear picture rather than a vague worry. They will want to know which tool, on which plan, whether any agreement was ever in place. What information went in, and whether it was genuinely identifiable. Roughly when it started and who was doing it. What the vendor's terms say about retention and training. And what your carrier and FMO contracts require you to report, because that obligation is often faster and stricter than anything in HIPAA itself.
Whether this rises to a breach requiring notification is a legal determination with real deadlines attached, and it depends on facts only your own review can establish. It is not something a blog post can answer for you, and any post that tries to is one you should not trust. What you can do today is stop the bleeding, preserve what exists, and make the call.
What to do with this
If you want AI on work that touches client health information, the sequence is short.
- Confirm what you are actually on. Workspace or Google One. Business Microsoft or Personal. Check today, because the invoice amount will not tell you.
- Have your super admin accept the BAA in the Admin console, or confirm someone already did.
- Write down which surfaces are inside the agreement and which are not, and make that list something your team can see. Gemini in Chrome belongs on the excluded side. So does Gemini Notebook, until Google says otherwise in writing.
- Set a standing rule for what never goes into any AI tool regardless of coverage, and train to it. Diagnoses not needed for the task. Full member IDs. Anything you could not defend as minimum necessary.
- Run the same three questions against every other AI subscription your agency pays for, including the notetakers and the ones individual producers expensed themselves.
Step five is usually the one that turns something up.
Questions agents ask
Is Google Workspace HIPAA compliant?
It can be, on a paid Workspace edition where a super administrator has accepted the BAA in the Admin console, and where your team keeps protected health information inside the services on Google’s Included Functionality list. None of that is automatic. Free personal Gmail and Google One consumer plans, including AI Pro and AI Ultra, have no BAA available at any price.
Is Gemini HIPAA compliant?
Gemini in Workspace, the Gemini app and the Gemini Mac app are covered under Google's BAA as of the list's August 31, 2026 revision, on a paid Workspace edition where an admin has accepted the BAA. Gemini in Chrome is excluded. No software is compliant on its own, so the accurate question is whether your account is covered.
Does Google One include a BAA?
No. Google One is a consumer subscription on a personal account, and that includes the Google AI Plus, Pro and Ultra plans. There is no BAA and no HIPAA coverage regardless of what you pay.
Is Gemini Notebook, formerly NotebookLM, covered?
It is not named on Google's Included Functionality list. Until Google confirms otherwise in writing, treat it as outside the agreement.
Is ChatGPT HIPAA compliant?
Only on specific products. ChatGPT Enterprise and Edu on sales-managed accounts, ChatGPT for Healthcare, and ChatGPT for Clinicians can have a BAA, as can the API with Modified Retention. ChatGPT Business, Plus and Free cannot.
Are insurance agents even covered by HIPAA?
Usually as business associates rather than covered entities. When a carrier gives you protected health information to do work on its behalf, you are handling it as an extension of them and you are directly liable for protecting it. Your carrier and FMO contracts may also impose stricter terms than HIPAA does.
Is my AI notetaker covered?
Almost certainly not, unless you deliberately put it on a business plan with a signed BAA. This is the most common gap in agencies right now.
Does a BAA mean I can put anything into the tool?
No. A BAA governs how the vendor handles what you send. Minimum necessary still applies to every prompt.
The larger point
Governance is a property of how the work is set up, and no vendor can sell it to you.
A Digital Crew works because every seat has a named role, a defined job, a human who owns it, and a decision it never makes. "No client health information goes into a tool outside the agreement" is exactly that kind of standing rule, written down before the agent runs rather than discovered afterward. That is also how you bring Shadow AI into the light instead of pretending it is not happening. Google's change did not make your agency compliant. It widened the space your crew is allowed to work inside, and the boundary still gets drawn by you.
Your producers did not get licensed to spend their week on paperwork. The legal envelope just got big enough to let a crew take some of it. Draw the line clearly, then let them work.
Updates
- September 16, 2026 - First published. Verified against vendor documentation on this date.
