Case study

A medical assistant clinicians can check

Answers grounded in trusted sources, with the citations to prove it.

Client
Hippocrates
Timeline
6 weeks · Aug 2026 – Oct 2026
Scope
AI, Product
Ask a medical question, get a sourced answer.
Ask a medical question, get a sourced answer.

Ask a medical question, say the first-line treatment for hypertension, and Hippocrates answers from a curated medical knowledge base, citing its sources so a clinician can check every claim.

The brief

An assistant clinicians can ask medical questions in plain language, and trust. Not a general chatbot with a medical skin, but a tool that answers from vetted sources and shows its work.

The hard part

In medicine a fluent answer is a liability if it cannot be checked. Every claim needs a source, every source needs to be current, and the source has to actually say what the answer claims.

On top of that, health data needs stricter access than a typical app, and clinicians bring records in formats few tools read.

  • Answers that cite and can be verified
  • Access rules fit for a hospital
  • Real-world records: PDF, FHIR, HL7, CDA

What we designed

A calm chat with suggested questions to start from, pinned conversations, saved artifacts and a knowledge base each institution can curate. Patient cases keep context across conversations, and a patient timeline and case summary turn uploaded records into something readable.

What we built

Every citation is checked twice: once that the source exists and is active, and again that its excerpt supports the claim it is attached to. Bad citations are kept in the record but never shown. While the answer streams, a guard holds back a short tail of text so safety checks can catch problems before they reach the screen.

Uploaded documents are treated strictly as data, never as instructions to the model. The knowledge base ingests public references such as DailyMed and MedlinePlus, chunked and embedded for search, with a job to re-embed stale chunks when models change.

  • Two-step citation verification
  • Guarded streaming with retraction
  • Record import for PDF, FHIR, HL7 and CDA
  • Knowledge ingestion, chunking and embeddings
  • Model routing by question type

The handoff

The project closed with a full handoff: a platform handbook, a route and code reference, the access rules, and the deployment and operations guide, so the client's team can run and extend it without us.

Built with

  • React
  • TanStack Start
  • NestJS
  • FastAPI
  • LangGraph
  • PostgreSQL
  • pgvector
  • Redis
  • Drizzle

Shipped

  • Medical chat with citations
  • Curated knowledge base
  • Patient cases and artifacts
  • Institution workspaces and roles
  • Web app, API and AI service

Read more about this build