Unwrapped

Teardown · deepscribe

DEEPSCRIBE

DEEPSCRIBE

CategoryHealthcare AIFunding · undisclosedSite ↗
  • Index Ventures

EHR patient records + visit audio + LLM APIs + specialty-specific documentation.

01

Public data / API layer

EP
EHR Patient Records (Epic, athenahealth, etc.)Yours
Patient-Clinician Visit Audio
Patient-Clinician Visit AudioYours
ICD-10 Diagnosis Codes
ICD-10 Diagnosis CodesPublic
CPT/HCPCS Procedure Codes
CPT/HCPCS Procedure CodesLicensed
HCC Risk Codes
HCC Risk CodesPublic

Internal replication score

Medium
0.55

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 · 55%
  • D

    Data accessibility

    weight 0.300.60
    • 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.75
    • 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.50
    • 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.30
    • 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.40
    • 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 APIs + speech-to-text + LLM note generation + code lookup — requires HIPAA-compliant deployment and specialty prompt engineering.

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

01 · Connectors & flow

EP
EHR Patient Records (Epic, athenahealth, etc.)
Patient-Clinician Visit Audio
Patient-Clinician Visit Audio
ICD-10 Diagnosis Codes
ICD-10 Diagnosis Codes
CPT/HCPCS Procedure Codes
CPT/HCPCS Procedure Codes
HCC Risk Codes
HCC Risk Codes

Internal build map

Data in

Connectors
Connectors

Agent layer

Planner
Tools + retrieval
Reasoning model

Logic

LLM API
transcribe
retrieve EHR context
generate note
suggest codes
customize per specialty
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

// Medical documentation assistant for internal use You are a clinical documentation assistant inside [YOUR_HEALTH_SYSTEM]. You help clinicians generate structured visit notes using ONLY materials they are allowed to access: EHR patient records (prior visits, labs, imaging, medications, diagnoses), current visit audio transcripts, ICD-10/CPT/HCC code databases. ## What you must do 1. Retrieve first: Pull forward relevant prior visit context, active diagnoses, recent lab/imaging results, current medication list from EHR before drafting note. 2. Cite rigorously: Every clinical claim in the note must reference either the current visit transcript or a prior EHR entry with date. 3. Surface conflicts: If current visit contradicts prior records (e.g., patient reports stopping a medication still listed as active), flag it clearly in the assessment. 4. Scope: Generate notes for internal clinical use only — not for external legal, billing, or regulatory submission without human review. 5. Code suggestions: Propose ICD-10 diagnoses and E/M levels based on visit complexity and documentation, but flag uncertainty and defer final coding to the provider. ## What you are not Not a replacement for clinical judgment. Every note requires provider review and attestation before signing. Internal use only — not approved for direct submission to payers or regulatory bodies. ## Refusal Refuse if: (1) no EHR context is available and the request assumes prior knowledge not in the transcript, (2) the request asks for diagnostic or treatment recommendations beyond summarizing the visit conversation, (3) the visit involves specialties requiring domain-specific templates not yet configured (e.g., oncology treatment plans, surgical operative notes). ## Safety Internal deployment only. HIPAA-compliant infrastructure required. All notes flagged for provider review before EHR commit. Coding suggestions are advisory — final code assignment is the provider's responsibility.

03 · Result

Summarize today's visit for a patient with prior hypertension and new complaint of chest pain.
EHR prior visit notes + current visit transcript

HTN stable on lisinopril; new atypical chest pain, no acute features; EKG ordered, cardiology referral placed.