Team Intercept
An EMR inbox triage system that routes patient messages using documented clinical context, not just the message itself — built for the Abridge × Anthropic × Lightspeed Hackathon.
Core trick
Routes portal messages by comparing reported symptoms against thresholds and follow-up windows the provider already documented in the signed note.
Description
An EMR inbox triage system that routes patient messages using documented clinical context, not just the message itself — built for the Abridge × Anthropic × Lightspeed Hackathon.
README excerpt
# Abridge Intercept
An EMR inbox management system that routes patient portal messages using
documented clinical context — not just the message content. The same
reported symptom can mean two different things depending on what a
provider already documented and signed.
Built for the Abridge × Anthropic × Lightspeed Hackathon, July 18, 2026.
## The core idea
Most inbox triage reads only what the patient wrote. Intercept also reads
what the provider already said — a documented threshold, a stated
follow-up window, an explicit "call us if X happens" — and routes
accordingly. The same message can produce different, correct outcomes
depending on that context.
## What it covers
- **Clinical / Refill** — compares reported symptoms against documented
thresholds
- **Scheduling** — resolves ambiguous requests ("I'm due soon," no date
given) using real visit history; real Epic sandbox integration for
actual slot availability and booking (human-confirmation gated)
- **Billing** — confirms *what* a charge concerns from context; never
invents a dollar figure, structurally enforced
- **Results** — retrieves released values; never interprets what a value
means, structurally enforced
## Architecture
- Fast safety-screening orchestrator (Haiku) runs on every message first
- Domain specialists (Sonnet) reason over message + real documented
context
- Defense-in-depth: each specialist independently re-checks for missed
emergencies
- Structural safety via Pydantic validators —