Google Cloud Gemini for Healthcare explained: what changes

Google Cloud announced Gemini for healthcare on November 10, 2026, as a U.S. preview: an industry layer on its Gemini agent that coordinates clinical, coverage and administrative work for payers and providers. For a small B2B software company, it changes little this month unless your customers are payers or providers and Google confirms in writing that this product is covered for protected health information (PHI).

Plainly, Gemini for healthcare is a healthcare-specific set of skills, connectors and governance that sits on top of Google's general Gemini agent, so one agent can work across an electronic health record (EHR), a claims system and a policy library under one set of permissions. TL;DR: it is a preview with no published price, its HIPAA position is stated as "built to support" compliance rather than as a listed Business Associate Agreement (BAA) product, and the real buying question is whether your product touches PHI or sells to organizations that do.

This comparison uses Google's launch page, its HIPAA and billing documentation, Zapier's pricing page, and public material from CMS, the National Association of Insurance Commissioners (NAIC) and the Kansas Legislative Research Department. I found no independent trade-press coverage of the launch in my searches on the research date, so every launch fact below comes from Google's own pages.

Key Takeaways

• Gemini for healthcare is in preview in the U.S. as of November 10, 2026, and Google's launch page publishes no price or pricing model for it.

• Google says the product is "built to support HIPAA compliance," but the Google HIPAA page I opened does not name it, and it says not to use pre-GA offerings with PHI unless their terms say otherwise.

• The Epic and Oracle Health EHR connectors are read-only with no write-back to the chart, and two Optum connectors are in limited release.

• Against the parent Gemini agent, the change is a healthcare skill set, a connector library and a governance layer; Gemini Enterprise is already named in Google's BAA product list.

• Zapier's Team plan costs $69.00 a month on annual billing, and its pricing page does not describe HIPAA terms.

• For most small B2B SaaS teams this month: get BAA scope in writing, keep PHI out of any pilot until then, and price the workflow you actually run.

The category decision: an industry agent layer or a general automation stack

The category decision comes before the product. Gemini for healthcare is an industry agent layer that Google says is configured for payers and providers, with four parts: skills written by domain experts, connectors to clinical, financial and operational systems, an open healthcare partner ecosystem, and a governed platform with open model choice. A general automation stack moves data between business tools for any buyer. Those are different purchases, and most small SaaS companies belong in the second group unless their customers are payers or providers.

The timing has a regulatory anchor. CMS requires impacted payers to decide expedited prior authorization requests within a fixed window: Expedited prior authorization decisions: 72 hours according to CMS (2024 rule). Standard requests get seven calendar days according to CMS (2024 rule). The CMS fact sheet says the timeframes take effect with a compliance date of January 1, 2026, that a prior authorization API must be in place from January 1, 2027, and that Qualified Health Plan issuers on the federally facilitated exchanges are excluded.

Industry data points the same way. Health insurers using AI/ML: 84% according to NAIC (2025). The NAIC's May 20, 2025 release says the survey included responses from 93 insurance companies. A state legislative briefing summarizes the same NAIC survey: Individual major-medical insurers using or exploring AI for prior authorization: 68% according to Kansas Legislative Research Department (2025 survey). Because the briefing reuses the NAIC data, treat the two as one survey, not two confirmations.

These figures explain why payers and providers are buying workflow tools. They do not show that a small SaaS vendor needs a healthcare agent layer, and we do not read them that way. The table below lists every figure in this post with its publisher, so you can check the origin of each one.

What Google launched, and what it has not published

Google's launch page calls Gemini for healthcare a purpose-built industry solution that extends the universal Gemini agent the company introduced last month at Gemini at Work. The page says the parent agent plans steps, keeps organizational context and routes across models, and that every agent operates with a distinct identity, inherits each user's existing role-based permissions and enforces need-to-know boundaries. The healthcare version adds the four components described above. Its skills cover medical records synthesis, pre-appointment preparation, coverage and policy review, and payer benefit determination, and teams can build custom skills for their own procedures.

The framing starts with a burden figure: Clinician reconciliation time: nearly 28 hours weekly according to Google Cloud (2026). That number is Google's own, and the launch page links it to a Google-hosted document, so treat it as the vendor's claim rather than an independent measurement.

The connectors decide whether a workflow runs at all. The launch says Epic EHR gives authorized users read-only access to patient conditions, medications, labs, clinical notes and specialist documentation, with no write-back to the underlying chart. Oracle Health EHR is described the same way. Two Optum connectors, Coordination of Benefits and Network Eligibility, are "currently in limited release and testing with Gemini for Healthcare." Other named connectors include TriZetto Provider Solutions, GoodRx, Infinitus Relay, IMO Health and ICD-10 Codes.

Two naming points matter for a purchase. First, Google's pages are not consistent about the parent product. Its Gemini Enterprise billing documentation says subscription fees are billed to a Cloud Billing account per license, while the Gemini product page carries the title "Gemini for business: The universal work agent." The launch calls the parent "the universal Gemini agent." Nothing I opened says a rename or merger happened, but the inconsistency is a reason to confirm which name and SKU a contract would cover before you compare anything. Second, the launch page does not describe a rename of the healthcare product itself.

The vendor has not published pricing for Gemini for healthcare, a general availability date, or a BAA scope entry for this product. The page says the product is "available in preview in the U.S. today" and that it is "built to support HIPAA compliance." Those phrases are not the same as a signed BAA covering the product. On data use, the page says "clinical data, prompts, and generated outputs remain within your organization's governed environment and are never used to train or fine-tune Google's foundation models."

How we evaluated these options

We weighted six criteria for a small B2B software team deciding this month. PHI and BAA coverage carries the largest weight, 25%, because a feature that cannot lawfully touch the data your customers send is not a feature you can use. Each option is scored on a 0 to 5 scale, where 0 means the public sources do not state the point and 5 means a page the buyer can check states it. The weights are our judgment, not a vendor or analyst figure, and you can change them to fit your risk.

Feature matrix: what each option states

The matrix compares the three options on the points this reader decides on. "Not checked" means the page I opened did not cover the point. It is a gap in this research, not evidence that a feature is missing.

Read the matrix as a list of what each vendor states in public, not as a score. The strongest published governance language belongs to Gemini for healthcare, but the critical HIPAA answer is missing. Zapier has the clearest published tiers and run-level terms, but its public pages do not address PHI.

Pricing and total cost, with the gaps marked

Pricing checked November 10, 2026. Google's launch page states no pricing or pricing model for Gemini for healthcare, so the vendor has not published this, and the table below shows Quote-based. For the parent agent, Google's billing documentation lists editions and bills per license, but the page I opened shows no dollar amounts and links to pay-as-you-go rates instead. A Google marketing page I tried to open was truncated, so this post prints no seat price for the parent agent.

Zapier's pricing page lists a Free plan with 100 tasks a month, a Professional tier at 750 tasks and a Team tier at 2,000 tasks. Zapier's Team plan costs $69.00 a month on annual billing and $103.50 a month on monthly billing, according to Zapier. The Enterprise tier is custom.

The Zapier annual figures are the monthly price multiplied by 12. Total cost for Gemini for healthcare cannot be computed from public data, so a pilot needs a written quote that states the fee model, any consumption charges and the systems-integrator work the launch expects. Make and n8n are the same category as Zapier, but this post did not open their pricing pages, so it prints no figures for them.

The worked example below is illustrative and uses assumed inputs. Suppose a small SaaS team wants every customer.subscription.updated event from Stripe to create a CRM task for the account owner, and assume 300 such events a month, each using 3 Zapier tasks, which you should check against Zapier's own task definition. That is 300 × 3 = 900 tasks a month, inside the Team tier's 2,000, so the plan price is the only platform cost: $69.00 × 12 = $828.00 a year on annual billing, or $103.50 × 12 = $1,242.00 on monthly billing. Monthly billing adds $414.00 a year for the same workload. Stripe lists the event type in its event type reference, which is where to confirm the exact trigger name before you build.

Per-vendor profiles: best fit, limits and evidence

Gemini for healthcare (Google Cloud, preview)

Best fit: payers and providers that run workflows across an EHR, claims and eligibility systems, and that want one governance layer for many agents. The launch's examples are chart preparation before a visit, authorization packets assembled against payer policy, and benefit explanations drawn from a member's plan documents. Choose it only if your buyers already run those systems and a compliance owner can get BAA scope in writing for this exact product.

Limitations: it is a preview, the vendor has not published pricing, two Optum connectors are in limited release, and the EHR connectors are read-only, so any workflow that must write results back needs a different path. Google's HIPAA documentation says customers should not use pre-GA offerings with PHI unless the terms say otherwise, and the page I opened does not name this product. Under that rule, an unconfirmed preview is not a PHI tool for your team.

Implementation: expect the launch's partner model to matter. The page names several systems integrators and digital health partners, and it says the partner route helps organizations connect Gemini to systems they already run without lock-in. Plan for account-team scoping, a BAA review, connector validation and a human review step before any output reaches a patient, payer or member.

Primary evidence: the Google Cloud launch page for components, connectors and preview status, and the HIPAA documentation for the pre-GA rule.

Gemini Enterprise (the parent agent)

Best fit: general knowledge-work deployments that do not need healthcare skills or EHR connectors. Google's HIPAA documentation names Gemini Enterprise among covered Google Cloud products, so the BAA position for the parent is clearer than for the new product, though you still need to confirm the edition and SKU your contract covers.

Limitations: billing is per license, with pay-as-you-go usage on top, and the billing page I opened shows no dollar amounts. The naming inconsistency noted earlier means a contract may refer to a product under a different label than the one in the launch.

Implementation: administration runs through Google Cloud identity and billing. Confirm the edition, the consumption rates and the BAA scope in the same document before any pilot. The billing documentation is the starting point for those questions.

Zapier (the DIY baseline)

Best fit: small teams automating non-PHI steps between business tools, where the owner can configure triggers, actions and error paths and accepts a published task limit. Zapier's tiers are the clearest public prices in this comparison, and its Free plan at 100 tasks a month is enough to test a single workflow.

Limitations: the pricing page does not describe HIPAA or a BAA, so it is not a PHI tool on the evidence I opened. Audit logs are not included on Free or Professional, and Team keeps logs for 6 months. Autoreplay retries temporary errors on Professional, Team and Enterprise according to Zapier, but retries are not the same as escalation, ownership or an audit record.

Implementation: a Zap or similar workflow needs a named owner, a failure alert path, a review of which fields leave your systems, and a maintenance schedule. Those are the same obligations that apply to an in-house script, which is the fair comparison for a team that does not want to pay for a platform.

Where a configurable workflow fits

A proposed, configurable design from US Tech Automations could place a gate in front of any AI step that handles patient data. The trigger is a new helpdesk ticket that a staff member tags as containing PHI. The action checks a maintained list of tools with written BAA status and routes the ticket to a named security reviewer instead of to any AI drafting step. The output is a review task that links to the ticket with a timestamp. Prerequisites are API or export access to the helpdesk, a list you maintain of tools and their BAA status, and an owner for that list. The human review point is the security reviewer, who decides whether the ticket can go to any AI tool. Nothing in this design sends a message to a customer. This is a configurable design, not a live deployment, and it has no measured results.

A second proposed design covers plan changes. The trigger is a customer.subscription.updated event from Stripe, and the action creates a CRM task for the account owner with the old and new plan fields. The output is a task the owner can close after review. Prerequisites are a Stripe webhook or trigger, CRM API access and a field mapping you agree on. The review point is the account owner, who confirms any message to the customer before it goes out.

The honest alternative for many small teams is to stitch these steps together in Zapier, Make or n8n, or to build them in-house. Those tools can support run histories, retries, error branches and audit evidence when configured. The buyer still designs and owns observability, idempotency, escalation paths, access controls and maintenance. A proposed design through US Tech Automations would differ mainly in the pre-check of BAA status and in the review task it creates, which you could also build yourself.

When NOT to use US Tech Automations

A simpler existing tool wins in three cases. A single, non-PHI notification that your CRM or helpdesk already sends natively needs no middleware. A workflow you run only a few times a month in a tool you already pay for does not justify a new layer. And a workflow that touches PHI before a BAA covers every tool in the chain should stop, not add automation.

Common mistakes

• Reading "built to support HIPAA compliance" as a signed BAA covering the product.

• Putting PHI into a pre-GA product because the pilot is "just a test."

• Comparing a list price with a workload that is billed on consumption.

• Assuming a read-only EHR connector can also write results back to the chart.

• Budgeting a Zapier plan from the tier price without counting how many tasks each run uses.

• Building an automation with no named owner for failed runs, retries and access reviews.

Decision checklist

• Do your customers include payers or providers, or do you receive PHI from them?
• Has Google confirmed in writing that the exact product and SKU sit under your BAA?
• Does each system your workflow needs appear on the connector list, and do you need read-only or write access?
• Have you priced the workflow from a written quote, or from published tiers and a task count?
• Who reviews every AI output before it reaches a patient, payer or customer?
• Who owns retries, failed runs and access reviews after the pilot?

Signal vs Speculation: what is sourced and what is our read

Sourced signals:

• Gemini for healthcare is in preview in the U.S. as of November 10, 2026.

• Google names four components, several EHR, claims and eligibility connectors, and two Optum connectors in limited release.

• Epic and Oracle Health access is read-only, with no write-back to the chart.

• The vendor has not published pricing for the product, and its HIPAA wording is "built to support HIPAA compliance."

• Google's HIPAA page I opened does not name the product and advises against pre-GA offerings with PHI.

Our read, not sourced:

• The launch is more a competitor and partner signal than a tool decision for most small SaaS teams.

• A small vendor may find the partner ecosystem expensive to reach, and the launch does not say what partner terms look like.

• Payer and provider buyers will push their SaaS vendors to connect to healthcare agents rather than build their own, but no source in this post measures that.

Who this is for

Best fit: a payer, provider or healthcare-software team whose workflow already runs in Epic, Oracle Health or another system on the connector list, with a compliance owner who can get BAA scope in writing. Choose Zapier or a similar tool if your workflow is non-PHI and you need a published price this month.

Not a fit: a general B2B SaaS team with no PHI and no healthcare customers. That team gains more from a simpler automation stack and a clear reading of what the launch means for its market than from a healthcare agent layer.

Red flags: no written BAA position for the exact product you would use; a workflow that runs in systems missing from the connector list; and a need for a fixed price this quarter, since none is published.

Frequently asked questions

Is Gemini for healthcare generally available yet?

No. Google's launch page says it is available in preview in the U.S., so plan around preview terms until Google publishes a general availability date.

Does Google publish a price for Gemini for healthcare?

No. The vendor has not published pricing or a pricing model, so the table in this post shows Quote-based and a pilot needs a written quote.

Can we put patient data into Gemini for healthcare this month?

Not on the public evidence. Google says the product is built to support HIPAA compliance, but its HIPAA page does not name it and advises against using pre-GA offerings with PHI unless the terms say otherwise, so get written BAA coverage first.

Does the EHR connector write back to the chart?

No, not for Epic or Oracle Health on the launch page, which describes read-only access with no write-back. The two Optum connectors are in limited release, so confirm their status before you plan around them.

Is Zapier enough for a small team?

Often, for simple workflows that do not involve PHI. Its pricing page lists a Free plan at 100 tasks a month and a Team plan at 2,000, with SAML single sign-on on Team, but it does not describe HIPAA terms, so it is not a PHI tool on the evidence I opened.

Should we change our stack this month?

For most small SaaS teams, no. Change the stack only if a named customer requires a payer or provider workflow and Google confirms coverage for the exact product in writing.

Decide this month

Decide this month on three checks: written BAA scope for the exact product, the EHR and payer connectors your customers actually run, and the workflow's task count against a published or quoted price. If those pass for a pilot that uses non-PHI data, see how US Tech Automations configures this with its own prerequisites and review gates before you commit. For related reading on search visibility for healthcare software, see SEO tools for healthcare SaaS and whether healthcare sites block AI crawlers, and for how SaaS content gets cited in search results, see how SaaS companies get cited in Google AI Overviews.