You should not have to trust us. You should be able to verify.

Per-specialty prompt composition

Prompts are composed per encounter from (a) a specialty-specific clinical scaffold, (b) a care-setting layer (outpatient/inpatient/ED), (c) a note-type layer (H&P, progress, ED, SOAP, etc.), and (d) the organization's quality configuration.

Two-pass verification

Stage 1 generates. Stage 2 validates — calculators scored, HCC/MIPS codes anchored to specific draft sentences, quality-gap opportunities surfaced. Stage 2 outputs corrections that the Stage 1 model cannot overrule.

Chart-aware context

Prior encounters, medications, allergies, recent labs, and open quality gaps are injected as context. Context carries across encounters for the same patient.

What we do not publish

Specific prompt text is not published. Publishing verbatim prompts creates clinical risk (competitors produce lookalikes without clinical review) and no educational value. Structure is public; content is protected.

Methodology: inputs extracted by AI vs. inputs verified by attending; scored against reference implementation. Full methodology and dataset will publish with the study.

Blinded attending review: AI-drafted vs. attending-written notes, from early users who consented to participate. Results will be published on scribeable.ai/research with full methodology when complete.

We have not yet published a hallucination benchmark. We will when the methodology is reproducible — "trust me" metrics get challenged and should.

Encounter audio

On our servers, single-visit audio from the web, the browser extension, and the iPhone app is processed in memory and not written to durable storage. Rounding Mode audio is deleted once it is transcribed; audio that fails to transcribe is kept up to 7 days for retry, and audio that cannot be read or retried is held until an operator reviews it. On iPhone, the recording also stays on the device for playback until you delete it or the note. Audio retention is written into the BAA (section 3.13), which caps any retained audio at twelve months in all cases.

Generated notes

Stored encrypted for the life of the account. Exportable at any time in structured JSON or plain text.

Transcripts

Stored encrypted, linked to the associated encounter. Deletable with the encounter.

Account deletion

On account closure, all PHI is permanently deleted within 30 days. Audit-log records of access (which do not contain PHI) are retained per HIPAA minimum-retention requirements.

Export

Full account export (all notes, templates, documents) is available from the web dashboard at any time. Export is available even during cancellation.

A clinician's dictation was lost on the device before it reached us. The empty generate request was blocked, then a "Generate anyway" override built for short recordings removed the block with nothing in its place, and the draft model composed a complete telehealth encounter from no source. The verification pass asked one question and did not catch it. Contained the same day: both copies of the note and every derived document were held, none had been shared, and nothing reached the patient. What changed: before the draft model is called, the system now measures the actual source content and, if it is essentially empty, does not call the model; the clinician gets a skeleton with clarification questions and the credit back. Held notes no longer feed later notes as history.

We have not had a HIPAA-reportable breach. We commit to publishing incident summaries on this page when and if they occur, within the HIPAA-mandated notification timeline.

Starting Q4 2026 we publish an 8–10 page quarterly PDF: uptime, latency, accuracy benchmark updates, incidents, customer-count (anonymized), support response metrics, feature shipping cadence.