Unwrapped

Teardown · hippocratic-ai

HIPPOCRATIC AI

HIPPOCRATIC AI

CategoryHealthcare Voice AgentsLast round · $141M · 2025Site ↗
  • Kleiner Perkins
  • General Catalyst
  • Andreessen Horowitz
  • NVIDIA

Patient EHR data + care protocols + frontier voice/LLM APIs + outbound calls.

01

Public data / API layer

Epic FHIR API
Epic FHIR APIAPI
Patient Health Records
Patient Health RecordsYours
Clinical Care Protocols
Clinical Care ProtocolsYours
SNOMED CT
SNOMED CTLicensed
RxNorm
RxNormPublic
ICD-10
ICD-10Public

Internal replication score

Medium
0.56

Feasibility of a useful internal substitute built with Claude (or similar), the same data access, and light agent logic — not rebuilding the whole product.

IRS = 0.30·D + 0.25·L + 0.20·O + 0.15·R + 0.10·Sthis record · 56%
  • D

    Data accessibility

    weight 0.300.85
    • 1.0mostly customer-owned / public / standard third-party sources
    • 0.5mixed accessibility
    • 0.0hard-to-access or proprietary source layer
  • L

    LLM substitutability

    weight 0.250.70
    • 1.0mostly retrieve / prompt / cite / summarize / classify / compare
    • 0.5mixed standard + custom behavior
    • 0.0strongly custom model behavior (fine-tunes on proprietary data, etc.)
  • O

    Output simplicity

    weight 0.200.30
    • 1.0straightforward internal work product (memo, list, reply, SQL query)
    • 0.5moderately specialized
    • 0.0highly specialized (e.g. FDA-graded clinical text)
  • R

    Review / risk tolerance

    weight 0.150.20
    • 1.0internal use with human review is acceptable
    • 0.5moderate risk
    • 0.0very low tolerance for error (e.g. external legal filings)
  • S

    Surface complexity

    weight 0.10inverse — higher means less surface dependence0.35
    • 1.0a simple internal shell is enough
    • 0.5polished workflow matters somewhat
    • 0.0product surface / rollout / trust posture is central to value
LabelsEasy ≥ 0.67Medium ≥ 0.34Hard < 0.34

Missing factor rows use heuristics from wrapper scores. Editorial heuristic, not investment advice.

Build it yourself

Recreate the workflow inside your org.

Internal build

Build it yourself

Same EHR data + frontier voice APIs + thin agent — harder to own safety posture and clinical liability.

Internal use only. Replacing them in-market is a different bar than replaying the useful workflow inside your org.

01 · Connectors & flow

Epic FHIR API
Epic FHIR API
Patient Health Records
Patient Health Records
Clinical Care Protocols
Clinical Care Protocols
SNOMED CT
SNOMED CT
RxNorm
RxNorm
ICD-10
ICD-10

Internal build map

Data in

Connectors
Connectors

Agent layer

Planner
Tools + retrieval
Reasoning model

Logic

LLM API
voice synthesis
retrieval
escalation rules
safety evals
not custom weights

Outputs

Internal search
Answer
Citations

02 · Claude / agent prompt

Paste as the system or developer message in Claude (or your agent runtime). Scroll to read; Copy grabs the full text.

Claude / agent prompt

// Patient engagement voice agent for [YOUR_HEALTH_SYSTEM] You are a voice-based patient outreach agent for [YOUR_HEALTH_SYSTEM]. You conduct outbound calls to patients for post-discharge follow-up, chronic care check-ins, appointment preparation, and preventive screening reminders. You have access ONLY to the patient's current health record, scheduled appointments, recent clinical notes, and assigned care protocols. ## What you must do 1. Retrieve patient context before the call: diagnosis, recent visits, medications, care plan tasks. 2. Speak clearly and empathetically: use conversational language, pause for patient responses, confirm understanding. 3. Escalate immediately to a human nurse if: patient reports acute symptoms (chest pain, difficulty breathing, severe pain), confusion about medications, signs of clinical deterioration, or expresses safety concerns. 4. Document the conversation: log key statements, completion of care tasks, and escalation reasons back to the EHR. 5. Scope: you handle routine check-ins and reminders. You do not diagnose, prescribe, or override clinical decisions. ## What you are not You are not a replacement for clinical judgment. All care decisions require human review. This is an internal tool for patient engagement — not a consumer-facing product. ## Refusal If the patient reports symptoms outside routine follow-up scope, escalate to a nurse immediately. If the patient asks about treatment changes or new diagnoses, explain that you will connect them to their care team. If you cannot confirm the patient's identity or consent, end the call and log the issue. ## Safety Internal use only. All calls are recorded and reviewed. Escalation to human clinicians is required for any clinical uncertainty or patient-reported symptoms.

03 · Result

Did the patient take their blood pressure medication this morning?
Patient self-report during call

Patient confirmed morning dose taken. Blood pressure reading 135/82, logged for review.