Decision owner
Clinician
The named role remains accountable for the consequential decision.
Healthcare Providers
Designed for Clinician
Reduce clinician documentation burden by turning an ambient or dictated encounter into a structured, coded clinical note grounded in the patient chart, with clinician attestation required before anything enters the medical record.
Contract HEA-01 · primary aggregate EncounterDocumentation · mode loading
Decision brief
This brief starts with the decision, evidence, and accountable owner. The guided workflow then shows how the recommendation was produced.
The evidence and control points that shape this recommendation.
Decision owner
Clinician
The named role remains accountable for the consequential decision.
Governed evidence
5 record types
Structured records and cited text ground the recommendation.
Workflow
5 controlled stages
Each transition records its input, output, status, and audit context.
Human controls
1 approval gate
Approval gates prevent the copilot from making consequential decisions.
During a 12 minute follow-up for uncontrolled type 2 diabetes, the copilot drafts HPI, assessment, and plan from the ambient transcript, pulls the latest A1c and metformin dose from the chart, flags one plan sentence with no supporting evidence, suggests a more specific diagnosis code, and files the note only after the clinician edits and signs it..
Reduce clinician documentation burden by turning an ambient or dictated encounter into a structured, coded clinical note grounded in the patient chart, with clinician attestation required before anything enters the medical record.
Signed note written to the EHR encounter gives Clinician the evidence needed to begin the final governed business outcome, with the decision trail retained for review.
Step 1 of 5
| Field | Value |
|---|
| Field | Value |
|---|
The output appears here immediately. More technical evidence remains available below.
The demonstration keeps deterministic controls, AI assistance, and approval separate.
Source systems enforce identity, workflow order, policy filters, and record updates.
Retrieval and generation assemble relevant evidence into a cited recommendation or draft.
Clinician verifies material claims and approves the consequential action.
Run the stages in order before using the Copilot. Every stage explains what happens, why it matters, the evidence it uses, and the complete API request and response.
Automated stage
What happens: Clinician performs capture the encounter conversation using Ambient audio or dictation with patient consent and produces Diarized TranscriptSegment stream. The transition is deterministic and does not require autonomous model approval.
Why it matters: Diarized TranscriptSegment stream gives Chart context service the evidence needed to begin Assemble relevant chart context, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/capture-the-encounter-conversation
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Automated stage
What happens: Chart context service performs assemble relevant chart context using Patient identifier and encounter reason and produces ChartContextSnapshot of problems, meds, allergies, results. The transition is deterministic and does not require autonomous model approval.
Why it matters: ChartContextSnapshot of problems, meds, allergies, results gives Documentation agent the evidence needed to begin Draft the structured clinical note, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/assemble-relevant-chart-context
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Automated stage
What happens: Documentation agent performs draft the structured clinical note using Transcript segments and chart snapshot and produces NoteDraft with per-statement evidence links. The transition is deterministic and does not require autonomous model approval.
Why it matters: NoteDraft with per-statement evidence links gives Coding agent the evidence needed to begin Suggest diagnosis and procedure coding, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/draft-the-structured-clinical-note
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Automated stage
What happens: Coding agent performs suggest diagnosis and procedure coding using Note assessment and plan sections and produces CodingSuggestion set with specificity warnings. The transition is deterministic and does not require autonomous model approval.
Why it matters: CodingSuggestion set with specificity warnings gives Clinician the evidence needed to begin Attest and file to the medical record, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/suggest-diagnosis-and-procedure-coding
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Human approval required
What happens: Clinician performs attest and file to the medical record using Edited note and accepted codes and produces Signed note written to the EHR encounter. A named human approver must review the evidence before the transition completes.
Why it matters: Signed note written to the EHR encounter gives Clinician the evidence needed to begin the final governed business outcome, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/attest-and-file-to-the-medical-record
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Run a stage to see its explanation, evidence, full request, and full response.
Ask a question and receive an answer grounded in retrieved EncounterDocumentation evidence.
Select a starter question or enter your own.
Loaded live from /api/config, /api/domain/model, and
/api/domain/sample.
encounterDocumentations/tenantId + /encounterIdDuring a 12 minute follow-up for uncontrolled type 2 diabetes, the copilot drafts HPI, assessment, and plan from the ambient transcript, pulls the latest A1c and metformin dose from the chart, flags one plan sentence with no supporting evidence, suggests a more specific diagnosis code, and files the note only after the clinician edits and signs it.
| Container | Role | Hierarchical partition key | Document types |
|---|---|---|---|
encounterDocumentations |
Primary | /tenantId + /encounterId |
EncounterDocumentation, TranscriptSegment, ChartContextSnapshot, NoteDraft, CodingSuggestion |
| Type | Container | Partition key | Identifier pattern | Embedding fields |
|---|---|---|---|---|
EncounterDocumentation |
encounterDocumentations |
/tenantId + /encounterId |
encounter::{encounterId} |
None |
TranscriptSegment |
encounterDocumentations |
/tenantId + /encounterId |
transcript::{encounterId}::{segmentSeq} |
segmentVector |
ChartContextSnapshot |
encounterDocumentations |
/tenantId + /encounterId |
chart::{encounterId}::{snapshotVersion} |
None |
NoteDraft |
encounterDocumentations |
/tenantId + /encounterId |
note::{encounterId}::{draftVersion} |
noteVector |
CodingSuggestion |
encounterDocumentations |
/tenantId + /encounterId |
coding::{encounterId}::{suggestionId} |
None |
Load transcript, chart snapshot, and current draft for the note editor in one partition read.
encounterDocumentations
single-partition
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.encounterId = @encounterId AND c.type IN ('EncounterDocumentation','TranscriptSegment','ChartContextSnapshot','NoteDraft') ORDER BY c.segmentSeq ASC
Partition-key fan-out control-plane query: show the clinician every draft still awaiting signature within the compliance window. It cannot carry the second partition key because a clinician's backlog spans all of the encounters they saw, so it runs as a tenant-scoped scheduled sweep off the interactive path, bounded by one clinicianId and the 24-hour attestation compliance window, executed with MaxItemCount paging and continuation tokens.
encounterDocumentations
partition-key-fan-out
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.type = 'EncounterDocumentation' AND c.clinicianId = @clinicianId AND c.attestationStatus = 'pending' ORDER BY c.serviceDateUtc ASC
Highlight generated sentences that lack a transcript or chart evidence link.
encounterDocumentations
single-partition
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.encounterId = @encounterId AND c.type = 'NoteDraft' AND ARRAY_LENGTH(c.unsupportedStatements) > 0 ORDER BY c.draftVersion DESC
Partition-key fan-out control-plane query: list suggested codes flagged for insufficient specificity before claim submission. It cannot carry the second partition key because the coding integrity queue is owned by the health information management team across encounters, so it runs as a tenant-scoped scheduled sweep off the interactive path, bounded by proposed codes on encounters inside the 72-hour pre-bill window, executed with MaxItemCount paging and continuation tokens.
encounterDocumentations
partition-key-fan-out
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.type = 'CodingSuggestion' AND c.specificityWarning = true AND c.acceptanceState = 'proposed' ORDER BY c.codeValue ASC