Google announced Gemini for healthcare on November 10, 2026, a U.S. preview designed to help clinical and administrative staff assemble patient summaries and insurance-approval paperwork. The offering connects records and coverage rules so staff can prepare evidence for review, according to Google.
Access is for Gemini Enterprise Standard and Plus customers, with organizations directed to their Google Cloud account team for deployment options. Google’s launch release describes per-user subscriptions or pay-as-you-go billing, but gives no numerical healthcare-specific rates.
Preparing a request is not approving it
One target is prior authorization: seeking a coverage decision before a service is provided. Under CMS’s Medicare prior-authorization initiatives, for example, providers submit supporting medical records for a contractor to review. Preparing those records is separate from deciding whether the request meets coverage requirements.
Google says Gemini can gather relevant chart material, compare it with a health plan’s requirements and flag missing documentation. It can also draft an appeal when the record supports one. These are announced capabilities; the launch materials do not establish independently measured reductions in denials or total staff time.
According to Google’s product FAQ, its Epic and Oracle Health connections cannot change the patient chart. Clinicians retain responsibility for chart entries, orders and sign-off, while coverage decisions remain with expert reviewers.
What the Epic connection can miss
A connector is the link that lets the service retrieve records from another system. Google’s Epic documentation lists limits that matter when reviewing a summary:
PDF documents are not readable through this connector.
Notes and reports are cut off beyond roughly 20,000 characters.
Search results arrive in pages of up to 50 records, with no total count supplied. Google cautions that answers needing many records may be incomplete; this is not a 50-record overall ceiling.
Excluded categories include care plans, consents, family history and imaging studies.
The practical implication is that read-only access does not guarantee a complete summary. If an authorization packet needs a PDF attachment or a consent record, the documented Epic connector alone cannot supply all the evidence. Staff would need another authorized source or manual retrieval.
For an organization choosing a pilot, that makes the required records a useful starting point: can staff retrieve everything the task needs? Any estimate of time saved should include checking and supplementing the draft, not just producing it.