Google Cloud announced Gemini for healthcare on November 10, 2026, opening a U.S. preview for providers and payers. The industry-specific system extends the Gemini agent with healthcare skills and data connectors to assemble clinical evidence and coordinate administrative work across existing systems.
The launch addresses the time spent assembling information across records, claims and coverage tools. In a 2024 study conducted by The Harris Poll for Google, clinicians reported nearly 28 hours of administrative work per week, compared with 34 hours for medical office staff and 36 hours for claims staff. Conducted online in the United States from August 26 to September 9, 2024, among 821 healthcare providers, 209 payors and 2,079 adults, the survey supplies pre-launch workload context rather than a performance result for Gemini.
Gemini for healthcare extends the universal Gemini agent instead of operating as a standalone application. It is available during preview to Gemini Enterprise Standard and Gemini Enterprise Plus customers. Google Cloud introduced the underlying agent on October 8, 2026, when healthcare was still listed as coming soon.
Clinical and Coverage Workflows
Healthcare skills package instructions and relevant context from domain experts so Gemini can execute defined multi-step tasks. Organizations can also create custom versions based on their own policies and standard operating procedures.
For providers, the system can combine electronic health record (EHR) data with outside records into a cited patient history across care settings. It can separate active problems from resolved ones, list allergies and identify medication discrepancies. Before a scheduled visit or procedure, another workflow checks for intervening events, current medications, and outstanding clearances, laboratory work or consents.
For authorizations and appeals, Gemini assembles chart evidence against payer policy and identifies documentation gaps before submission. Following a denial, it drafts an appeal with citations only when the clinical record and plan policy support one. For payers, it checks requests against medical policy and organizes traceable findings for clinical reviewers. Member-service workflows can also estimate out-of-pocket costs, track deductibles and verify network status using plan documents and eligibility data.
Read-Only Connections and Launch Customers
The initial Epic and Oracle Health integrations are read-only. Epic connects through open.epic APIs, while Oracle Health uses Ignite APIs for FHIR, a clinical-data interoperability standard. Neither integration writes back to the underlying patient chart. The product documentation specifies that chart entries, orders and final sign-off remain clinician-led.
Beyond the two EHRs, the connector catalog includes Keragon connectivity to more than 400 healthcare applications, current Centers for Medicare & Medicaid Services coverage determinations, the National Provider Identifier registry, the RxNorm drug vocabulary and ICD-10-CM diagnosis codes. Availability is uneven: Optum Network Eligibility and Coordination of Benefits are in limited release and testing. Google says NextGen Healthcare connectivity remains in development and is slated for release in the coming months.
Google names Blue Cross Blue Shield of Massachusetts, Hartford HealthCare, HCA Healthcare, Highmark Health, Northwell Health, Optum and Stanford School of Medicine as launch customers, with the American Society of Clinical Oncology listed as a contributor. HCA Healthcare said it is exploring how Gemini could synthesize patient information across multiple EHR systems and care settings.
“Our clinical data is only as useful as researchers’ ability to ask questions of it,” said Todd Ferris, deputy chief information officer at Stanford School of Medicine. He described researchers using plain language to query an Observational Medical Outcomes Partnership database without first requiring SQL and data-model expertise.
Governance, Model Choice and Pricing
Google says the platform is built to support HIPAA compliance. Patient records, clinical data, prompts and outputs remain within the customer’s governed Google Cloud environment and are not used to train or fine-tune Google’s foundation models. Connectors inherit existing identity and role-based permissions, while citations and audit logging let reviewers inspect outputs and activity. Customer-managed encryption keys and VPC Service Controls are also included among its security controls.
Customers can choose models from Google, Anthropic and OpenAI under one governance framework. Google says its routing sends high-volume administrative tasks to faster, lower-cost models while reserving higher-reasoning models for complex analysis. Pricing is available through per-user seat subscriptions or pay-as-you-go. Healthcare connectors support global and U.S. locations during preview.
The launch puts agentic AI into the assembly work around care and coverage, while leaving chart entries, orders, clinical review and final sign-off to people. The preview’s practical test is whether those cited, permission-aware workflows save time without weakening oversight, particularly while parts of the connector catalog remain incomplete.
