Tools3 min read

Gemini for healthcare: US preview access and data limits

Google opened Gemini for healthcare to Enterprise Standard and Plus customers in the US. Epic connector limits matter when planning a clinic pilot.

Prepared by the NADALI editorial team using AI

AI illustration: folders, a document tray and a magnifying glass, with a long sheet and closed folder set aside.
Nadali editorial illustration created with OpenAI gpt-image-2-2026-04-21 · Original AI-generated editorial illustration created for Nadali; use subject to applicable OpenAI terms; no exclusive copyright claim; no third-party input images used. · 1440 × 960

Author: Nadali. Prepared with AI assistance.

What Google announced

On November 10, 2026, Google introduced Gemini for healthcare in US preview. The solution helps assemble information for clinical and administrative workflows, including visit preparation and insurance coverage review. These are the provider’s stated capabilities; Nadali has not tested them in a clinic.

Who can access it

The product page limits the preview to Gemini Enterprise Standard and Plus customers. It extends the enterprise platform rather than operating as a standalone application. The Epic and Oracle Health connectors only read health records; chart entries, orders and final sign-off remain with clinicians.

For a Ukrainian clinic, the first step is to confirm eligibility for its own organization, compatibility with its systems and the full implementation cost. An announcement of a US preview does not establish availability in Ukraine. The product page we checked does not list a separate public price for this solution.

An important boundary: incomplete data

The Epic connector documentation, updated November 10, specifies single-patient searches, with no cross-patient analysis. Each results page contains at most 50 records without a total count, so answers relying on many records may be incomplete. The connector cannot read PDFs, and note or report text longer than roughly 20,000 characters is truncated. These specific limitations apply to Epic; they should not automatically be attributed to other connectors.

For a manager, the practical question is: who will notice that a required document is missing from the summary?

What to check before a pilot

Nadali’s suggested sequence for an administrative pilot:

  1. Select one workflow and name the person responsible for checking it. Until use of health data is approved, work with synthetic examples involving no real patients.
  2. Create the expected inventory of documents, formats and dates. Include a PDF and a long note to see how the system reports omissions.
  3. Compare the output with that inventory. Check the source link for each finding, and record missing information separately from a negative finding.
  4. Specify when a staff member must return to the original system and who authorizes the next action. Do not enable automated messages or changes to health records as part of this trial check.

Google describes the solution as built to support HIPAA compliance. A clinic still needs its own review of terms, access and data requirements before connecting it. We have not evaluated clinical effectiveness, legal compliance or actual time savings.

The useful result of the first test is an inventory of verified sources, detected omissions and owners for manual review. That provides a basis for deciding whether the tool helps with the selected workflow.

Sources checked on November 11, 2026.

Cover: an original conceptual AI illustration for this article, not a product interface, medical record or evidence of testing. 

Sources and verification

  1. Google Cloud: Introducing Gemini for healthcare, November 10, 2026 ↗
    Source checked: 2026-11-11
  2. Google Cloud: AI for healthcare, product page and preview FAQ ↗
    Source checked: 2026-11-11
  3. Google Cloud documentation: Epic EHR connector overview and limitations, updated November 10, 2026 ↗
    Source checked: 2026-11-11