Google Cloud has announced Gemini for healthcare. The announcement was made on November 10, 2026, local time in the US. In Korean time, it was 22:00 on the same day. It is available in preview to Gemini Enterprise Standard and Plus customers in the US.

Google’s official announcement and product page were checked as of November 11, 2026.

Healthcare AI that connects clinical, operational, and administrative systems

Gemini for healthcare is an AI solution for integrating disconnected healthcare systems. Google said it was designed to connect clinical, operational, and administrative systems. Supported multistep workflows include medical record synthesis and prior authorization review. These features are specified in Google’s official announcement.

Epic integration is limited to read-only access. Google Cloud’s Epic connector documentation explicitly states this restriction. The connector reads data when information from Epic is needed to answer a question. It should therefore not be understood as a feature for modifying original records through this connector.

Principles for handling clinical data and generated outputs

Google said that clinical data, prompts, and generated outputs remain within the organization’s managed environment. It explained that this information is not used to train Google’s foundation models. Its policy also excludes use for fine-tuning. This is the company’s explanation in the Google Cloud announcement.

Medical-record synthesis is among the tasks supported by Gemini for healthcare.AI-generated image

Preview available to Standard and Plus customers in the US

The currently specified audience is Gemini Enterprise Standard and Plus customers in the US. The Google Cloud product page outlines the scope of preview availability. The published conditions alone do not establish whether healthcare institutions in Korea can use it.

Item to check Officially stated scope
Availability stage Preview
Available region US
Eligible products Gemini Enterprise Standard and Plus
Conditions for use by healthcare institutions in Korea Not disclosed
General availability timeline Not disclosed

The US preview announcement should not be read as a launch in Korea. Being a Standard or Plus customer alone is also not enough to determine availability in Korea. Both regional and product eligibility requirements must be checked.

Additional fees and limits for healthcare-specific features remain undisclosed

Additional fees and usage limits for healthcare-specific features have not been disclosed. The names of the eligible products indicate eligibility for use. This information alone does not establish that healthcare features are included in the base price.

To assess adoption costs, organizations need to ask Google Cloud whether additional charges apply. Usage limits also need to be checked separately. Preview availability alone should not be taken to mean that use is free.

Support for Korean-language records and a separate API remain unconfirmed

The scope of support for Korean-language clinical records and healthcare information systems in Korea has not been disclosed. The availability of a separate API and the API model name are also unconfirmed. The description of Epic integration does not imply support for healthcare systems across Korea.

  • The launch timeline for Korea and conditions for use by healthcare institutions in Korea have not been disclosed.
  • The extent of support for Korean-language clinical records has not been specified.
  • The scope of integration with healthcare information systems in Korea remains unconfirmed.
  • The availability of a separate API and the API model name have not been disclosed.

Check eligibility and integration scope before adoption in Korea

Healthcare institutions in Korea should first check the conditions for their own use and whether their systems are supported. The current announcement confirms only a preview for US customers. When considering adoption, they can ask Google Cloud about conditions that have not been disclosed.

  1. Check whether institutions in Korea can participate in the preview. Even if the product in use is Standard or Plus, regional requirements must be checked separately.
  2. Check additional fees and usage limits for healthcare-specific features. Budget planning should be based on confirmed billing terms.
  3. Check support for Korean-language records and the institution’s healthcare information systems. If API integration is needed, ask whether it is available.

If considering an Epic connection, its read-only scope must be reflected in workflow design. The Epic connector documentation explains that it reads the data needed to answer questions. Record retrieval and modification of original records must be considered separately.