Ask the medical literature

Every claim opens to the exact passage it came from.

Decision support for clinicians, not medical advice. Questions may be published as public pages — do not include patient details.

122 million passages

Answers are built from retrieval over the medical literature — a corpus, not a model’s recollection.

Quotes, not footnotes

Each claim cites a verbatim span of its source and is checked against it before it reaches you.

Honest limits

What the corpus cannot support, Sammy says so — plainly, instead of improvising.

The Sammy suite: two products, one rule — show the source

Ask — answers you can audit

Ask a clinical question and get an answer grounded in retrieved literature, claim by claim. Open any citation and read the quoted passage yourself — no account needed to try it.

Scribe — the visit, documented

Scribe listens to the visit and drafts the note while the clinician works. Every sentence stays traceable to the recording behind it — and a sentence with nothing behind it says so on its face. In production at two Texas emergency hospitals.

Sammy also runs as a desktop app for macOS and Windows. Download the desktop app.

Scribe for iPhone: the visit, documented from the phone already in the room

Tap once to start scribing. The transcript builds live on the device, and the draft note — every sentence traceable to the recording — is ready before the clinician is back at a desk. Same access code, same per-hospital deployment as the rest of Sammy. In external beta; coming soon to the App Store.

The landing page runs an interactive demo of Scribe in the browser: a simulated visit — nothing is recorded — whose draft note lets you tap any sentence to see exactly where in the transcript it came from.

Built for hospitals: a HIPAA-first architecture, described plainly

Per-hospital isolation: Each hospital’s deployment is isolated — from every other hospital’s, and from the public service. Nothing is pooled across customers.
BAAs before data, not after: Patient data is processed only by vendors operating under a signed Business Associate Agreement — a vendor without one does not see PHI.
The public Ask carries no PHI: This page’s Ask is fenced off from hospital deployments and is not a place for patient information. It answers from the literature, never from a chart.
No borrowed badges: We claim no certification we do not hold and no partnership we do not have. What we will show a hospital’s security team is the architecture itself.