From patient records to coverage reviews: the scope of Gemini for healthcare

In U.S. preview, Gemini for healthcare connects patient records and coverage policies to support healthcare providers and insurers.

Patient records and insurers’ policies are becoming the working sources for a specialized agent serving healthcare organizations. Available in preview in the United States, Gemini for healthcare is intended to prepare medical summaries, assemble supporting documentation for coverage requests, and organize it for review by qualified professionals. Access is available to Gemini Enterprise Standard and Plus customers.

This Google Cloud offering extends the Gemini agent with healthcare-specific instructions and connections. Tasks draw on the software providers and health insurers already use, with human oversight. Generated documents are expected to cite the records or policy provisions supporting their contents. From patient records to coverage requests

In the detailed description of the offering, work begins by bringing together scattered information. The agent can consolidate medical histories from multiple care settings, distinguish active conditions from resolved ones, and flag medication discrepancies. Before an appointment, it is also intended to highlight recent events and missing tests or consent forms based on the organization’s procedures.

The same approach applies to prior authorizations required by some U.S. insurers. Relevant clinical evidence is assembled and checked against coverage criteria before submission to identify missing documentation. If a request is denied, the agent can draft an appeal when the record and plan terms support it. Reducing denials and administrative time remains a vendor promise, with no quantified results accompanying the announcement.

For payers, the announced capabilities prepare requests for review by qualified professionals. They also include explaining benefits and estimating out-of-pocket costs using plan documents, deductibles, and applicable provider networks. Preparing this information does not constitute a coverage determination. Medical records remain read-only

Connections to Epic and Oracle Health provide access to authorized patient information without writing back to the clinical record. Chart entries, orders, and final sign-off remain with clinicians. Prepared summaries and supporting documents can be delivered to workplace tools, including Word, Outlook, Google Docs, or Gmail.

Each agent has a distinct identity and inherits the user’s role-based permissions. Connectors are designed to respect existing access rights in source systems. The platform adds audit logs and references to supporting documents so teams can verify where information came from or trace an action.

According to the provider, clinical data, prompts, and outputs remain within the organization’s governed environment and are not used to train or fine-tune Google’s foundation models. The solution is described as designed to support HIPAA compliance, the U.S. framework for protecting health information. Instructions tailored to each organization

Tasks are guided by “skills,” reusable instructions written by domain experts, alongside each organization’s rules. Teams can create their own instructions for their procedures. Model choice is also open: the official announcement names Google, Anthropic, and OpenAI, with routing intended to match the complexity of the work.

Connections also cover Medicare coverage policies, medical terminology, and sources of clinical guidelines. Availability varies at launch: the Optum Network Eligibility and Coordination of Benefits integrations, intended to verify eligibility and identify additional coverage, are still described as being in limited release and testing.