Keep real patient charts out of Gemini for healthcare until Google confirms in writing that the preview is covered by your Business Associate Agreement. Google Cloud launched the product on November 10 with read-only Epic and Oracle Health connectors and seven named launch organizations, including HCA Healthcare, Northwell Health and Optum. Its launch post says the platform is "built to support HIPAA compliance." Neither that post nor the press release mentions a BAA, and Google's HIPAA guidance says: "Don't use pre-GA offerings as defined in the Service Specific Terms with PHI, unless expressly noted otherwise in a notice or other terms of the offering."
Neither the launch post nor the HIPAA page says whether this preview falls under that exclusion or carries a notice lifting it. Launch customers may hold negotiated terms that nobody outside can see. If you are deciding whether to join, you need your own answer, on paper, before your Epic analyst registers the app.
What Google Shipped on November 10
Gemini for healthcare is a set of healthcare skills, data connectors and partner integrations built on Google's general Gemini agent, and it is available in US preview to Gemini Enterprise Standard and Plus customers. The skills Google names include medical records synthesis, pre-appointment preparation, coverage and policy review, and payer benefit determination. Teams can also build their own.
The connector list is long and uneven in maturity. Epic connects through open.epic APIs and Oracle Health through Ignite APIs for FHIR, with NextGen Healthcare due "in the coming months." Optum's Coordination of Benefits and Network Eligibility connectors are still in limited release and testing. CMS coverage determinations, ICD-10, RxNorm and the NPPES registry are also listed. Customers can route work to models from Google, Anthropic or OpenAI, with cheaper models handling simple admin tasks.
Three things a buyer would want are absent from the launch post and press release. There is no general availability date. There are no dollar prices: the press release offers per-user seats or pay-as-you-go and stops there. And there are no accuracy or error figures, a gap Futurum's Keith Kirkpatrick also flagged along with the lack of production results. Futurum's disclosure says it does or has done research and advisory work for technology companies mentioned in that analysis, without naming them.
For a floor on seat cost, eWeek reported in August that Google lists Gemini Enterprise Standard and Plus as starting at $30 per user per month. At that starting price, 5,000 clinical and administrative seats would run $150,000 a month, or $1.8 million a year. Google has not said whether the healthcare skills add anything on top.
Why the Preview Label Changes Your HIPAA Position
The word "preview" puts the product in a contract category that Google treats very differently from a generally available service. A pre-GA offering, under Google's Service Specific Terms, is a feature, model, tool or service identified as "Early Access," "Alpha," "Beta," "Preview," "Experimental," or a similar designation "in related documentation or materials." Google's launch materials call Gemini for healthcare a preview. Its setup documentation for the Epic connector in Gemini Enterprise goes further, describing federated search and actions as in public preview and subject to the Pre-GA Offerings Terms.
Section 5 of those terms, checked on November 10, 2026, reads as follows:
| Term | What it says | What it means in a hospital |
|---|---|---|
| Changes | Pre-GA Offerings "may be changed, suspended or discontinued at any time without prior notice" | A chart-prep workflow can disappear with no notice period |
| SLA and indemnity | "not covered by any SLA or Google indemnity" | No uptime remedy, and no Google indemnity to lean on |
| Liability | Capped at the lesser of your agreement's limit or $25,000 | Carve-outs exist, including death or personal injury from negligence |
| Data processing | Unless a written notice or Google documentation says otherwise, "no data processing terms" apply and customers "should not use Pre-GA Offerings to process personal data or other data subject to legal or regulatory compliance requirements" | PHI is the textbook case of regulated data |
| Termination | Either party may end use with written notice | Plan a fallback for anything clinicians come to rely on |
IBM's 2026 study puts the average healthcare breach at $6.64 million, about 265 times that $25,000 cap.
Google has a reasonable counterargument. Its HIPAA page lists both Gemini Enterprise and Gemini Enterprise Agent Platform as services supported under the BAA, and Google says patient data, prompts and outputs stay in the customer's environment and are never used to train its foundation models. Gemini for healthcare runs on that foundation, so a notice extending coverage is entirely plausible.
Google also knows how to write that notice. The pre-GA terms for the Cloud Healthcare API state that those preview features "are included" in the BAA and that customers "may" use them for regulated data. The compliance page for Agent Search says the same about that product's pre-GA offerings, but it never mentions Gemini Enterprise or its connectors. As of November 10, the pages we could check show nothing equivalent for this product. The HIPAA page does not name Gemini for healthcare, the Gemini Enterprise compliance page has only a link to that HIPAA page, the Epic connector pages say nothing about PHI, and the Gemini Enterprise release notes have no November entry for the launch.
A Business Associate Agreement is the written contract HIPAA requires before a vendor handles protected health information on a covered entity's behalf. The rule at 45 CFR 164.502(e) says the required assurances "must be documented through a written contract or other written agreement or arrangement." Regulators have enforced it against ordinary vendor handoffs. In 2016, Raleigh Orthopaedic Clinic paid $750,000 after releasing 17,300 X-ray films to a vendor with no BAA in place, and the director of the HHS Office for Civil Rights called the agreements "more than a mere check-the-box paperwork exercise."
The scope question runs past the core product. Google's HIPAA page says services not covered by the BAA must be disabled when working with PHI, and that a service that cannot be disabled must not be used for PHI. A deployment that combines an Epic connector, a partner model and third-party connectors such as Suki or Keragon needs a covered or not-covered answer for each piece.
A separate clause bears on clinical use. Section 20(e) of the same Service Specific Terms bars using Generative AI Services "for clinical purposes" or as a substitute for professional medical advice, and leaves "scheduling, or other administrative tasks" unrestricted. Which services count is set by a separate Google list that we could not read in full. Google's Epic connector page says it lets "clinicians ask questions about patients," so ask which side of that line chart preparation falls on.
What Read-Only Means for the Business Case
Read-only access protects the chart and limits the product to assembling work that someone else finishes. Google's post says Epic has "no write-back to the underlying chart" and that Oracle Health enforces "zero write-back." The Epic configuration page tells administrators not to enable write APIs and lists read and search access to resources including Patient, Observation, MedicationRequest, DocumentReference and Binary.
That design makes clinical safety review easier. It leaves the PHI question exactly where it was, because records still flow into Google Cloud to be reasoned over. Kirkpatrick's summary of the trade-off is the one to bring to your steering committee: "Gemini prepares work that people and other systems still have to finish."
The competition inside the chart is already shipping. Oracle's Clinical AI Agent for nurses, commercially available in the US as of September, turns dictation into "structured, discrete data fields in the EHR in near real time." HIT Consultant reported in March that Epic's Penny agent cut prior-authorization submission time by 42% at Summit Health, with 92% of AI-generated responses accepted without edits. Treat those as vendor-promoted results, though they are more than Google has published. As Futurum puts it, "the EHR vendors own the screen clinicians work in, and they can write back."
Google's counter is a layer that spans systems no single EHR vendor controls. That argument is strongest for organizations carrying several EHRs, which is the problem HCA's chief clinical officer describes in Google's launch post. A health system standardized on Epic should make Google prove what it adds beyond Epic's own tools.
Start With Payer Policy Work, Which Can Avoid PHI
Payer policy and benefit review is the best early fit, and part of it can start before the BAA question is settled. Futurum's read is that "the payer side is where it will show results first," because policy review draws on documents a plan already owns and read-only access matters less there. A pilot limited to plan documents and CMS coverage determinations can run without a member record in it.
Regulation adds a clock. Under CMS-0057-F, impacted payers have had to issue prior authorization decisions within 72 hours for urgent requests and seven calendar days for standard ones since January 1, 2026 (Exchange plans are excluded from the timeframes), and the Prior Authorization API requirement begins January 1, 2027.
The provider side of the same fight is large. Northwell CEO John D'Angelo told Fortune, "I have like 400 employees whose sole job is fighting the insurance denials, and we overturn over 90% of them." Futurum warns that if both sides use AI to generate more submissions and appeals, friction could rise. Scrutiny follows volume, too: the Blue Cross Blue Shield Association has already attributed $942 million to hospital AI coding.
What to Do Before Connecting a Chart
Treat written PHI coverage as the first deliverable of any pilot, ahead of the technical setup.
This Week:
- Ask your Google account team in writing: does our BAA and Cloud Data Processing Addendum cover Gemini for healthcare during preview, including the Epic and Oracle Health connectors, and does the Section 20(e) bar on clinical purposes reach chart preparation? Request the notice or amendment behind each answer, and cite the Cloud Healthcare API pre-GA language as the model.
- Have your privacy officer list every component in the planned flow (each connector, each model option, each partner agent) and mark its BAA status as confirmed, excluded or unknown.
- Hold production Epic and Oracle Health app registrations until the first answer arrives.
This Month:
- Run a PHI-free pilot on plan policies, benefit documents and CMS coverage text. Score whether each citation supports the claim it is attached to.
- Build your own test set on synthetic or properly de-identified charts, because Google has published no error rates. Only 44% of the 27 health systems in an August report from the Center for Connected Medicine and KLAS had a dedicated environment for validating AI models (our coverage), so settle where this runs now. Confirm whether your non-production Epic environment holds synthetic data or a copy of production before you test there.
- Have your security team review the Epic app settings. Google's configuration calls for persistent access with rolling refresh tokens, and each user authorizes the connector with their own Epic account, so token lifetime and offboarding need an owner.
Before You Sign a Production Commitment:
- Replace the preview terms in writing: an SLA, indemnity, a liability cap sized to your exposure, a notice period before discontinuation, and a price hold through general availability.
- Compare the workflow against what Epic and Oracle Health can do inside the chart today, and against third-party agents built to book directly into those EHRs. For each option, name who files the final output.
- Require production metrics from a named launch customer: turnaround time, reviewer edit rate and citation error rate.
The Bottom Line
Google has been through a public fight over patient records before. In 2019, HHS's civil rights office opened a probe into whether HIPAA was followed when Google collected millions of records through its Ascension partnership. This launch comes with user-level permissions, citations and audit logging, which give a privacy office more to review. Kirkpatrick's test is the right one: judge it within 12 months on published production metrics and on whether Epic and Oracle Health allow governed write-back.
Until then, the preview is useful for policy work and synthetic-chart testing. Get the BAA sentence from Google before your Epic analyst creates the production client.
Continue Reading
- Best Ambient AI Scribes Save 16 Minutes a Day, Not an Hour
- Hospitals Test Vendor AI. Fewer Than Half Have a Sandbox.
- Blue Cross Blames $942M on AI Coding That Treatment Never Followed
- NHS Scribes Dropped 'Null.' Patients Caught It, Not GPs.
- Best RAG Platforms for Regulated Industries: Permissions First
- Google's Antigravity Lacks SOC 2 and ISO 27001 as Code Assist Ends