Part ofOperational AI for healthcare Operational AI Healthcare AI

Gemini for Healthcare: What It Takes to Make AI Work in an FQHC

Google's healthcare AI launch raises a practical question for FQHCs: how do clinics and Linear turn capabilities into working referrals across their existing tools?

Linear Health Editorial Team

Editorial, Linear Health

Published November 12, 2026

Clinic colleagues mapping a referral flow with separate Gemini and Linear Health symbols

Google introduced Gemini for Healthcare on November 10, 2026, bringing healthcare-specific skills, connectors, and a partner ecosystem into its enterprise agent platform. For a federally qualified health center (FQHC), that raises a practical question: who will make the workflow work across our tools, our teams, and our definition of done? Google's announcement

That question is central to Linear Health's work with clinics. A functioning referral workflow requires both the technology provider and the clinic to contribute. The clinic knows how work moves between its locations, staff, and outside offices. Linear works with the team to translate that knowledge into a supported coordination workflow.

What Gemini for Healthcare changes

Gemini for Healthcare launched in preview with skills that organizations can tailor to their standard operating procedures, connections to existing systems, and implementation partners. Its ecosystem includes operational products: Synthpop advertises referral intake, payer verification, and patient outreach through its Careflow integration with Gemini. Google, Synthpop

Those capabilities make the evaluation more specific. An FQHC can ask a platform provider, a specialist vendor, or an implementation partner to demonstrate the same thing: one agreed workflow running through the systems and exceptions the clinic actually needs.

Linear's work starts with the clinic's actual process: which steps need support, which decisions belong to the clinic, and who takes over when an automated step cannot proceed. Those responsibilities should be explicit in the scope and demonstrated before launch.

Why an FQHC workflow extends beyond its EHR

Health centers can deliver services directly, through contracts, and through referral arrangements. Those arrangements help explain why a center's work can cross organizational boundaries as well as software boundaries. HRSA's description of service delivery arrangements

Consider an illustrative outbound referral. The order starts in the EHR. A packet goes to a specialist through a fax or referral service. Staff may need information from a payer portal. Patient contact happens by phone or message. The specialist has its own scheduling process, while the originating clinic needs a reliable record of what happened.

Each tool may hold one part of the story. A successful fax transmission establishes delivery to an endpoint. A booked appointment establishes a scheduled date. Neither, by itself, establishes that the patient attended or that the clinic received the consult note.

The Institute for Healthcare Improvement's referral-management guide describes the importance of clear roles, communication, and information exchange across the referral process. That is a useful foundation for evaluating automation: follow the handoffs and establish who is responsible at each one. IHI/NPSF, Closing the Loop

Illustrative workflow

One referral. Several systems.Shared responsibility.

Referral identifiedEHR + clinic
Before deliveryMissing informationClinic owner resolves it
Packet deliveredFax + specialist
Before bookingPatient not reachedAgreed outreach, then staff handoff
Visit bookedOutreach + specialist
Attendance confirmedSpecialist + clinic
Before note returnConsult note missingAssigned owner follows up
Note returnedSpecialist + EHR
Closure confirmedClinic + EHR

Before deliveryMissing informationClinic owner resolves it
Before bookingPatient not reachedAgreed outreach, then staff handoff
Before note returnConsult note missingAssigned owner follows up

Each milestone needs its own evidence. A booking does not confirm attendance or a returned note. Resolve exceptions before advancing and keep unresolved work visible. Systems, owners and closure criteria vary by clinic. Payer portal checks may add steps.

The clinic and implementation team agree on the systems, permissions, follow-up rules, and closure criteria.

Three exceptions make the implementation questions concrete:

The specialist needs another document. Decide where that request becomes visible, who obtains the document, and what evidence allows the referral to move forward.
The patient does not answer. Agree on the permitted outreach sequence, the point at which staff take over, and how the receiving staff member acknowledges the handoff.
The visit happened, but the note is missing. Record attendance separately from note receipt. Keep the remaining work assigned until the clinic's agreed completion requirements are met or another disposition is recorded.

These are operational design decisions. They need to survive the transition between systems, a change of coordinator, and the next shift. Our guide to FQHC referral coordination explores the shared handoff record in more detail.

What Linear and the clinic need to decide together

The clinic contributes its operating knowledge and decisions about responsibilities. Linear contributes the supported automation and integration work needed to carry out the agreed scope. Both sides need a way to check that the result matches what they intended.

Use the following framework to agree on the proposed deployment.

Agree on the meaning of each status

Start with observable milestones: sent, received, booked, attended, and note received. Define the evidence required for each status and the clinic's criteria for closing the work. A dashboard label should have a meaning that coordinators at different locations can explain consistently.

Map the exact records and actions

Identify where each piece of information originates, where it needs to appear, and which system takes precedence when records disagree. Confirm the supported read and write actions for the proposed configuration. Name any step that remains manual, including the person responsible for it.

Make exceptions assignable

Agree on outreach permissions, follow-up timing, escalation routes, and staff coverage. Then test a case that needs help. An exception should expose the unresolved task, the reason it stopped, and the next responsible person.

Verify the workflow together

Use agreed test cases to check both the normal path and the exceptions. Confirm that an update reached the intended record and that a staff handoff was accepted. Decide who reviews changes when the clinic adjusts its process or a connected system changes.

Shared implementation

A working workflow is designed together.

Decision	Clinic decides	Linear configures	Both verify
Completion	Define milestones and owners.	Map agreed statuses and actions.	Test booking, attendance and note receipt separately.
System mapping	Identify the source of record.	Map supported reads, writes and unresolved steps.	Reconcile missing or conflicting updates.
Exceptions	Approve channels and escalation owners.	Configure outreach and task routing.	Test no answer, missing information and accepted handoffs.
Launch	Agree the starting scope and staff coverage.	Configure the scoped workflow and reporting.	Validate test cases and review later changes.

Completion
Clinic decides
Define milestones and owners.
Linear configures
Map agreed statuses and actions.
Both verify
Test booking, attendance and note receipt separately.
System mapping
Clinic decides
Identify the source of record.
Linear configures
Map supported reads, writes and unresolved steps.
Both verify
Reconcile missing or conflicting updates.
Exceptions
Clinic decides
Approve channels and escalation owners.
Linear configures
Configure outreach and task routing.
Both verify
Test no answer, missing information and accepted handoffs.
Launch
Clinic decides
Agree the starting scope and staff coverage.
Linear configures
Configure the scoped workflow and reporting.
Both verify
Validate test cases and review later changes.

A framework for scoping the work. Confirm supported configuration and responsibilities before launch. The clinic and Linear agree the scope together; this diagram does not imply that every system or action is supported.

This is where collaboration becomes tangible: a clinic decision becomes a configured action, and both teams can inspect evidence that the action worked. For the wider rollout sequence, see our referral workflow implementation guide.

What the Aunt Martha's deployment demonstrates

Aunt Martha's Health & Wellness is a community health organization in the Chicago area with more than 100 providers across more than 20 locations. It uses athenahealth, with Linear Health referral coordination, care gap closure, and voice AI running across the network. Aunt Martha's case study

Linear's published case study describes work across athenahealth and payer portals, automated outreach, and coordinators handling exceptions. It provides an example of coordination operating within an existing clinical organization and its systems.

For an FQHC evaluating Linear, this provides a concrete starting point: a deployed coordination workflow in an athenahealth environment. The next step is to map the prospective clinic's own systems, responsibilities, and exceptions against the proposed scope.

Our emphasis is on doing that work with the clinic: understanding the handoffs, agreeing on the required outcomes, and confirming the supported configuration. The quality of those decisions matters when a referral leaves the EHR and begins moving through other organizations and tools.

Ask for a demonstration that includes unfinished work

A useful evaluation starts with one workflow that your team can describe. Bring a de-identified example or an agreed synthetic case, the relevant systems, and the exceptions you want to see handled.

Ask any provider, including Linear, to demonstrate:

Where the work starts. Identify the triggering record and the information the workflow needs.
What crosses each boundary. Show the document, message, or status that moves between systems, and explain how receipt is checked.
What happens when a step cannot finish. Introduce missing information, an unsuccessful outreach attempt, or an unavailable update.
Who takes the next action. Show the assigned owner and how the handoff is acknowledged.
What completion means. Distinguish a booked appointment, a confirmed visit, a returned note, and the clinic's closure decision.

Then agree on measures for the proposed workflow. These might include time to booking, staff follow-up time, unresolved exceptions, and the share of eligible referrals reaching each defined milestone. Record unknown statuses separately, and agree on the denominator and measurement period before comparing results.

The implementation discussion should also cover what happens after launch. Our EHR integration maintenance guide addresses ownership, changes, and recovery checks.

Where Linear fits

Linear Health helps FQHCs coordinate referrals and related work in the systems their teams already use. Its work with clinics brings local operating knowledge into the configuration, with the supported scope and responsibilities established together.

Gemini for Healthcare gives buyers another platform and partner ecosystem to evaluate. The decision becomes clearer when each option is assessed against the same real workflow, including the parts that stop, require a person, or wait on an outside organization.

Bring the workflow your team has to finish. Ask to see how it will run.

Frequently asked questions

Can Gemini for Healthcare automate referral workflows?

Google describes custom healthcare skills, system connectors, and operational partners. Synthpop advertises referral intake, payer verification, and patient outreach through its Gemini integration. Buyers still need to verify the systems, actions, permissions, and exception paths supported in their proposed deployment.

Does an EHR connector remove the need for workflow implementation?

A connector provides access to supported data or actions. The clinic still needs to establish how those actions fit its process: which record governs a status, what starts the next step, who handles exceptions, and what evidence confirms completion. Those decisions should be reflected in the configuration and tested.

Does an FQHC need to replace its EHR to work with Linear Health?

Linear runs on top of the clinic's existing EHR. Its established integrations are athenahealth, eClinicalWorks, NextGen, and Greenway Health. The specific workflow, connected tools, and supported actions need to be confirmed during scoping; an established EHR integration does not establish every possible workflow.

When should an automated referral be marked complete?

The clinic should define completion requirements for the workflow and preserve the underlying milestones. A booked appointment, a confirmed visit, and a received consult note are different events. The configured process should retain any unfinished work until the agreed requirements are met or another disposition is recorded.

How should an FQHC compare Linear with a Gemini-based solution?

Use the same scoped workflow and test cases for both. Compare supported system actions, staff responsibilities, handling of missing information and unsuccessful outreach, evidence of updates, implementation work, ongoing ownership, and total cost. Request relevant deployment evidence and validate fit in the proposed environment.

Sources

Healthcare AI Referral Management Operational AI