Google Cloud Healthcare New Zealand

The Clinician

Document Processing

The Clinician needed to scale the authoring of healthcare outcome projects while enforcing PHI screening, licensing controls, and auditability across mixed workloads with very different latency and reasoning requirements.

Blocks 14 restricted instrument uses with
Saves $2.1M in annualized external costs through
Scales monthly clinical project launches from four to 47
Slashes project-authoring time from 42 days to 3.1 hours

Reported impact

Business outcome

The Clinician drastically reduced project setup time, increased project-launch volume, and replaced costly manual or outsourced steps with governed AI workflows.

  • Compliance
  • Cost Reduction
  • Productivity Improvement

Solution

The Clinician uses Google Cloud to address this challenge: The Clinician needed to scale the authoring of healthcare outcome projects while enforcing PHI screening, licensing controls, and auditability across mixed workloads with very different latency and reasoning requirements. Gemini Enterprise Agent Platform hosts the hybrid model-routing architecture that serves the application’s nine production endpoints, serving as the serving layer. Gemini Pro handles complex reasoning and document extraction inside project-authoring workflows, serving as the compute layer. Gemini Flash supports high-volume, latency-sensitive tasks such as question drafting, serving as the compute layer. Cloud Run functions provide the serverless endpoint layer for the governed healthcare workflow, serving as the serving layer.

Data flow

Project requests enter a serverless endpoint layer, Gemini Enterprise Agent Platform routes complex document extraction to Gemini Pro and drafting workloads to Gemini Flash, and governance checks screen PHI and restricted instruments before output is returned to clinicians.

Solution architecture

4 components · 2 layers
  1. Compute
    • Gemini Pro handles complex reasoning and document extraction inside project-authoring workflows
    • Gemini Flash supports high-volume, latency-sensitive tasks such as question drafting
  2. Serving
    • Gemini Enterprise Agent Platform hosts the hybrid model-routing architecture that serves the application’s nine production endpoints
    • Cloud Run functions provide the serverless endpoint layer for the governed healthcare workflow

Architecture clues

  • Licensing checks enforce the approved use of clinical instruments
  • PHI screening blocks calls that contain sensitive healthcare data
  • The architecture runs nine production endpoints with hybrid model routing

Evidence from the source

Blocks 14 restricted instrument uses with
Deployed across the architecture features a hybrid model routing pattern running nine production endpoints.
It dynamically routes complex reasoning and document extraction to Gemini Pro, while assigning high-volume, latency-sensitive tasks like question drafting to Gemini Flash.
Saves $2.1M in annualized external costs through
Scales monthly clinical project launches from four to 47
Slashes project-authoring time from 42 days to 3.1 hours
Transparency Evidence & methodology 95/100 reference value · 82% confidence · 2 sources

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value95/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth20/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    2 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence82%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability23/25
    11 of 12 key fields link to a named source.
  • Direct evidence20/20
    6 direct source quotes retained.
  • Date provenance0/10
    The publication date has no documented provenance.
  • Source transparency9/10
    2 source references document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Google Cloud

    The Clinician customer story

    First-party
    https://cloud.google.com/customers/theclinician
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
  2. The Clinician

    The Clinician

    First-party
    https://theclinician.com/

    The site labels 'Headquarters' as 'New Zealand' and lists '84 Newton Rd, Eden Terrace, Auckland 1010.'

    Source type
    Official company website
    Supports
    • Region

Date evidence

  • Sitemap last modified Jul 10, 2026 · Google Cloud · Publisher metadata Publisher-reported modification timestamp; not a publication date.
    Open date source
  • Unverified extracted date Jul 10, 2026 · Google Cloud · Unknown Legacy extracted date without source-page confirmation.
    Open date source
Not separately sourced Industry, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.