{"content_id":"bc8rjiqmz6","slug":"google-gemini-for-healthcare-us-preview","locale":"en","schema_type":"NewsArticle","category":"news","category_name":"News","title":"Google Gemini for healthcare US preview announced","summary":"Google Cloud announced Gemini for healthcare, which supports healthcare data integration and multistep workflows. The preview is for Gemini Enterprise Standard and Plus customers in the US. The launch timeline and terms of availability in South Korea have not been disclosed.","sponsorship_disclosure":null,"affiliate_disclosure":null,"commerce_disclosure":null,"author":{"name":"Injoys Editorial Team","url":"https://injoys.com/ko/about"},"key_points":["Google Cloud announced Gemini for healthcare on November 10, 2026.","The preview is for Gemini Enterprise Standard and Plus customers in the US.","Supported tasks include medical record synthesis and prior authorization review.","Google said it does not use clinical data, prompts, or generated outputs to train its base models.","The launch timeline in South Korea and additional fees and usage limits for healthcare-specific features have not been disclosed."],"content_markdown":"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.\n\nGoogle’s official announcement and product page were checked as of November 11, 2026.\n\n## Healthcare AI that connects clinical, operational, and administrative systems\n\nGemini 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](https://blog.google/innovation-and-ai/infrastructure-and-cloud/google-cloud/gemini-for-healthcare/).\n\nEpic 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.\n\n### Principles for handling clinical data and generated outputs\n\nGoogle 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](https://cloud.google.com/blog/products/ai-machine-learning/gemini-for-healthcare).\n\n## Preview available to Standard and Plus customers in the US\n\nThe currently specified audience is Gemini Enterprise Standard and Plus customers in the US. The [Google Cloud product page](https://cloud.google.com/gemini/healthcare) outlines the scope of preview availability. The published conditions alone do not establish whether healthcare institutions in Korea can use it.\n\n| Item to check | Officially stated scope |\n| --- | --- |\n| Availability stage | Preview |\n| Available region | US |\n| Eligible products | Gemini Enterprise Standard and Plus |\n| Conditions for use by healthcare institutions in Korea | Not disclosed |\n| General availability timeline | Not disclosed |\n\nThe 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.\n\n## Additional fees and limits for healthcare-specific features remain undisclosed\n\nAdditional 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.\n\nTo 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.\n\n## Support for Korean-language records and a separate API remain unconfirmed\n\nThe 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.\n\n- The launch timeline for Korea and conditions for use by healthcare institutions in Korea have not been disclosed.\n- The extent of support for Korean-language clinical records has not been specified.\n- The scope of integration with healthcare information systems in Korea remains unconfirmed.\n- The availability of a separate API and the API model name have not been disclosed.\n\n## Check eligibility and integration scope before adoption in Korea\n\nHealthcare 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.\n\n1. 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.\n2. Check additional fees and usage limits for healthcare-specific features. Budget planning should be based on confirmed billing terms.\n3. Check support for Korean-language records and the institution’s healthcare information systems. If API integration is needed, ask whether it is available.\n\nIf considering an Epic connection, its read-only scope must be reflected in workflow design. The [Epic connector documentation](https://docs.cloud.google.com/gemini/enterprise/docs/connectors/epic) explains that it reads the data needed to answer questions. Record retrieval and modification of original records must be considered separately.","content_html":"\u003cp\u003eGoogle 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.\u003c/p\u003e\n\u003cp\u003eGoogle’s official announcement and product page were checked as of November 11, 2026.\u003c/p\u003e\n\u003ch2\u003e\n\u003ca href=\"#healthcare-ai-that-connects-clinical-operational-and-administrative-systems\" class=\"anchor\" id=\"healthcare-ai-that-connects-clinical-operational-and-administrative-systems\"\u003e\u003c/a\u003eHealthcare AI that connects clinical, operational, and administrative systems\u003c/h2\u003e\n\u003cp\u003eGemini 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 \u003ca href=\"https://blog.google/innovation-and-ai/infrastructure-and-cloud/google-cloud/gemini-for-healthcare/\"\u003eGoogle’s official announcement\u003c/a\u003e.\u003c/p\u003e\n\u003cp\u003eEpic 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.\u003c/p\u003e\n\u003ch3\u003e\n\u003ca href=\"#principles-for-handling-clinical-data-and-generated-outputs\" class=\"anchor\" id=\"principles-for-handling-clinical-data-and-generated-outputs\"\u003e\u003c/a\u003ePrinciples for handling clinical data and generated outputs\u003c/h3\u003e\n\u003cp\u003eGoogle 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 \u003ca href=\"https://cloud.google.com/blog/products/ai-machine-learning/gemini-for-healthcare\"\u003eGoogle Cloud announcement\u003c/a\u003e.\u003c/p\u003e\n\u003ch2\u003e\n\u003ca href=\"#preview-available-to-standard-and-plus-customers-in-the-us\" class=\"anchor\" id=\"preview-available-to-standard-and-plus-customers-in-the-us\"\u003e\u003c/a\u003ePreview available to Standard and Plus customers in the US\u003c/h2\u003e\n\u003cp\u003eThe currently specified audience is Gemini Enterprise Standard and Plus customers in the US. The \u003ca href=\"https://cloud.google.com/gemini/healthcare\"\u003eGoogle Cloud product page\u003c/a\u003e outlines the scope of preview availability. The published conditions alone do not establish whether healthcare institutions in Korea can use it.\u003c/p\u003e\n\u003cdiv class=\"overflow-x-auto\"\u003e\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eItem to check\u003c/th\u003e\n\u003cth\u003eOfficially stated scope\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd data-label=\"Item to check\"\u003eAvailability stage\u003c/td\u003e\n\u003ctd data-label=\"Officially stated scope\"\u003ePreview\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd data-label=\"Item to check\"\u003eAvailable region\u003c/td\u003e\n\u003ctd data-label=\"Officially stated scope\"\u003eUS\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd data-label=\"Item to check\"\u003eEligible products\u003c/td\u003e\n\u003ctd data-label=\"Officially stated scope\"\u003eGemini Enterprise Standard and Plus\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd data-label=\"Item to check\"\u003eConditions for use by healthcare institutions in Korea\u003c/td\u003e\n\u003ctd data-label=\"Officially stated scope\"\u003eNot disclosed\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd data-label=\"Item to check\"\u003eGeneral availability timeline\u003c/td\u003e\n\u003ctd data-label=\"Officially stated scope\"\u003eNot disclosed\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\u003c/div\u003e\n\u003cp\u003eThe 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.\u003c/p\u003e\n\u003ch2\u003e\n\u003ca href=\"#additional-fees-and-limits-for-healthcare-specific-features-remain-undisclosed\" class=\"anchor\" id=\"additional-fees-and-limits-for-healthcare-specific-features-remain-undisclosed\"\u003e\u003c/a\u003eAdditional fees and limits for healthcare-specific features remain undisclosed\u003c/h2\u003e\n\u003cp\u003eAdditional 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.\u003c/p\u003e\n\u003cp\u003eTo 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.\u003c/p\u003e\n\u003ch2\u003e\n\u003ca href=\"#support-for-korean-language-records-and-a-separate-api-remain-unconfirmed\" class=\"anchor\" id=\"support-for-korean-language-records-and-a-separate-api-remain-unconfirmed\"\u003e\u003c/a\u003eSupport for Korean-language records and a separate API remain unconfirmed\u003c/h2\u003e\n\u003cp\u003eThe 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.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eThe launch timeline for Korea and conditions for use by healthcare institutions in Korea have not been disclosed.\u003c/li\u003e\n\u003cli\u003eThe extent of support for Korean-language clinical records has not been specified.\u003c/li\u003e\n\u003cli\u003eThe scope of integration with healthcare information systems in Korea remains unconfirmed.\u003c/li\u003e\n\u003cli\u003eThe availability of a separate API and the API model name have not been disclosed.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2\u003e\n\u003ca href=\"#check-eligibility-and-integration-scope-before-adoption-in-korea\" class=\"anchor\" id=\"check-eligibility-and-integration-scope-before-adoption-in-korea\"\u003e\u003c/a\u003eCheck eligibility and integration scope before adoption in Korea\u003c/h2\u003e\n\u003cp\u003eHealthcare 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.\u003c/p\u003e\n\u003col\u003e\n\u003cli\u003eCheck 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.\u003c/li\u003e\n\u003cli\u003eCheck additional fees and usage limits for healthcare-specific features. Budget planning should be based on confirmed billing terms.\u003c/li\u003e\n\u003cli\u003eCheck support for Korean-language records and the institution’s healthcare information systems. If API integration is needed, ask whether it is available.\u003c/li\u003e\n\u003c/ol\u003e\n\u003cp\u003eIf considering an Epic connection, its read-only scope must be reflected in workflow design. The \u003ca href=\"https://docs.cloud.google.com/gemini/enterprise/docs/connectors/epic\"\u003eEpic connector documentation\u003c/a\u003e explains that it reads the data needed to answer questions. Record retrieval and modification of original records must be considered separately.\u003c/p\u003e\n","tags":["Productivity","Generative AI","Personal data protection","AI Agents"],"faqs":[{"question":"Can healthcare institutions in Korea use Gemini for healthcare right away?","answer":"It has not been confirmed whether healthcare institutions in Korea can use it. The official guidance is for Gemini Enterprise Standard and Plus customers in the United States. The launch schedule for Korea and terms of use in Korea have not been disclosed."},{"question":"If you are using Standard or Plus, can you also use the healthcare features at no additional cost?","answer":"There is no basis for concluding that there is no additional cost. Additional fees and usage limits for healthcare-specific features have not been disclosed. You need to check availability in Korea and billing terms with Google Cloud."},{"question":"Does it also support Korean-language clinical records and healthcare information systems in Korea?","answer":"The scope of support for Korean-language clinical records and healthcare information systems in Korea has not been disclosed. The Epic connector is described as read-only. This description alone is not enough to determine whether integration with systems in Korea is possible."}],"sources":[{"url":"https://blog.google/innovation-and-ai/infrastructure-and-cloud/google-cloud/gemini-for-healthcare/","title":"Google Cloud launches Gemini for healthcare. - Google","type":"source"},{"url":"https://cloud.google.com/blog/products/ai-machine-learning/gemini-for-healthcare","title":"Introducing Gemini for healthcare - Google Cloud","type":"source"},{"url":"https://docs.cloud.google.com/gemini/enterprise/docs/connectors/epic","title":"Overview | Gemini Enterprise | Google Cloud Documentation - Google Cloud","type":"source"},{"url":"https://cloud.google.com/gemini/healthcare","title":"AI for healthcare | Google Cloud - Google Cloud","type":"source"}],"images":[{"id":2705,"url":"https://injoys.com/rails/active_storage/blobs/proxy/eyJfcmFpbHMiOnsiZGF0YSI6NDE1NzMsInB1ciI6ImJsb2JfaWQifX0=--e954660d3fb6ce0dbfd6ba112b049934593fe5b6/ai-cc820f0c.webp","is_representative":true,"generation_method":"ai_photo","license":"ai_generated","mime_type":"image/webp","width":1536,"height":1024,"translations":{"ko":{"alt":"병원 복도 옆 서버실에서 초록색 셔츠를 입은 기술자가 랙 서버를 다루고 있다.","caption":"Gemini for healthcare는 의료 데이터 통합과 다단계 업무를 지원한다.","description":null},"en":{"alt":"A technician in a green shirt handles a rack-mounted server beside a hospital corridor.","caption":"Gemini for healthcare supports medical data integration and multistep workflows.","description":null},"ja":{"alt":"病院の廊下に隣接するサーバー室で、緑のシャツを着た技術者がラック型サーバーを扱っている。","caption":"Gemini for healthcareは医療データの統合と複数段階の業務を支援する。","description":null},"es":{"alt":"Un técnico con camisa verde manipula un servidor en un rack junto a un pasillo hospitalario.","caption":"Gemini for healthcare permite integrar datos médicos y facilitar flujos de trabajo de varios pasos.","description":null},"id":{"alt":"Teknisi berbaju hijau menangani server pada rak di ruang server di samping koridor rumah sakit.","caption":"Gemini for healthcare mendukung integrasi data medis dan alur kerja bertahap.","description":null},"pt":{"alt":"Um técnico de camisa verde manuseia um servidor em um rack ao lado de um corredor hospitalar.","caption":"O Gemini for healthcare apoia a integração de dados médicos e fluxos de trabalho com várias etapas.","description":null},"zh-hant":{"alt":"一名穿著綠色襯衫的技術人員在醫院走廊旁的機房內操作機架式伺服器。","caption":"Gemini for healthcare 支援醫療資料整合與多步驟工作流程。","description":null},"de":{"alt":"Ein Techniker im grünen Hemd hantiert mit einem Rack-Server neben einem Krankenhausflur.","caption":"Gemini for healthcare unterstützt die Integration medizinischer Daten und mehrstufige Arbeitsabläufe.","description":null}}},{"id":2706,"url":"https://injoys.com/rails/active_storage/blobs/proxy/eyJfcmFpbHMiOnsiZGF0YSI6NDE1NzksInB1ciI6ImJsb2JfaWQifX0=--8df7f7dcb67348a80bd852d46090d55675bd9fac/ai-017dea00.webp","is_representative":false,"generation_method":"ai_semi","license":"ai_generated","mime_type":"image/webp","width":1536,"height":1024,"translations":{"ko":{"alt":"태블릿을 앞에 두고 대화하는 여성 의사와 남성 간호사, 진료·검사·투약 정보를 하나로 모으는 도식","caption":"Gemini for healthcare의 지원 업무에는 의료기록 종합이 포함된다.","description":null},"en":{"alt":"A physician and nurse beside a tablet, with a graphic combining clinical, lab and medication records.","caption":"Medical-record synthesis is among the tasks supported by Gemini for healthcare.","description":null},"ja":{"alt":"タブレットを前に話す女性医師と男性看護師、診療・検査・投薬情報を一つにまとめる図","caption":"Gemini for healthcareの対応業務には、医療記録の要約・統合が含まれる。","description":null},"es":{"alt":"Una médica y un enfermero junto a una tableta, con un diagrama que unifica datos clínicos, de laboratorio y medicación.","caption":"Gemini for healthcare permite sintetizar historiales médicos.","description":null},"id":{"alt":"Dokter dan perawat di dekat tablet, dengan diagram penggabungan catatan klinis, hasil laboratorium, dan obat.","caption":"Gemini for healthcare mendukung penyusunan rangkuman rekam medis.","description":null},"pt":{"alt":"Uma médica e um enfermeiro junto a um tablet, com um diagrama que reúne dados clínicos, laboratoriais e de medicação.","caption":"A síntese de prontuários médicos está entre as tarefas apoiadas pelo Gemini for healthcare.","description":null},"zh-hant":{"alt":"女醫師與男護理師在平板電腦旁交談，旁邊的圖示將診療、檢驗與用藥資料彙整為一份紀錄","caption":"Gemini for healthcare 支援的工作包括醫療紀錄彙整。","description":null},"de":{"alt":"Ärztin und Pfleger am Tablet; eine Grafik führt Behandlungs-, Labor- und Medikationsdaten zusammen.","caption":"Gemini for healthcare unterstützt unter anderem die Zusammenfassung von Patientenakten.","description":null}}}],"published_at":"2026-11-11T14:01:14+09:00","updated_at":"2026-11-11T14:01:14+09:00","license":"cc_by","translation_status":"reviewed","available_locales":["ko","en","ja","es"],"data_locales":["ko","en","ja","es","id","pt","zh-hant","de"],"url":"https://injoys.com/en/articles/google-gemini-for-healthcare-us-preview"}