Skip to main content
A scribe session can produce one or more medical record documents — one per purpose (e.g. primary for the clinician-facing record, rpa for EMR injection). Each document is the filled output of the session templates.

Listing the documents

Use the same consultationInternalId you used with the scribe session endpoint:
Response:

Diagnosis codes

Each document carries its diagnosisCodes — the diagnosis ICD-10 (CIE-10 / CID-10) codes, as the doctor-curated set (the model’s suggestions plus any codes the doctor added, minus the ones they removed). Each entry has a type of primary or secondary. The list is empty when the session has no diagnosis codes. Past medical conditions carry their own resolved codes in medicalRecordSummaryStructured.pastMedicalConditionsCoded: each entry pairs the condition content with a code object holding the best-match code and scored options. It is null until code resolution has run for the record.
Wait until the session’s status is completed or completedWithErrors (see Session lifecycle) before fetching its documents — they are only produced after the AI pipeline finishes.

CDSS alerts

When clinical decision support is enabled for the session, each document carries its cdssAlerts — corrective alerts that flag omissions, incorrect dosages, or non-pertinent orders against the record. Each alert has a stable opaque id (use it as-is; don’t parse it), the clinical elementId it refers to, an actionCategory (add | remove | replace | modify), a severity (red | orange | yellow), and a status reflecting the doctor’s decision (pending | accepted | rejected). It is null when CDSS is disabled for the session or no alerts were generated, and [] when it ran and produced none. See Clinical decision support for the full alert model.

Filtering by purpose

Pass ?purpose=primary to get only the clinician-facing document. Other valid values include rpa (for EMR injection) and emr.

Field reference