Healthcare Providers

Clinical Documentation Copilot

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

Attest and file to the medical record: evidence ready for review

This brief starts with the decision, evidence, and accountable owner. The guided workflow then shows how the recommendation was produced.

Decision signals

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.

Business problem

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..

Decision to make

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.

Outcome to show

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.

  1. 1Capture the encounter conversation
  2. 2Assemble relevant chart context
  3. 3Draft the structured clinical note
  4. 4Suggest diagnosis and procedure coding
  5. 5Attest and file to the medical record

Step 1 of 5

Ready: Start with the business question, then use the single button above.

The output appears here immediately. More technical evidence remains available below.

System logic, GenAI, and human accountability

The demonstration keeps deterministic controls, AI assistance, and approval separate.

System logic

Source systems enforce identity, workflow order, policy filters, and record updates.

GenAI contribution

Retrieval and generation assemble relevant evidence into a cited recommendation or draft.

Human accountability

Clinician verifies material claims and approves the consequential action.

Workflow stages

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.

Seeded record
Loading
Document type
Loading
Container
Loading
Partition key
Loading
Current stage
Loading

API demonstration guidance

Run a stage to see its explanation, evidence, full request, and full response.

Grounded chat

Ask a question and receive an answer grounded in retrieved EncounterDocumentation evidence.

Answer and evidence

Select a starter question or enter your own.

Evidence

Domain implementation workspace

Loaded live from /api/config, /api/domain/model, and /api/domain/sample.

Domain objective
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.
Primary aggregate
EncounterDocumentation
Primary container
encounterDocumentations
Hierarchical key
/tenantId + /encounterId
Schema version
1

Sample scenario

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.

Physical Cosmos DB containers

Every container provisioned for this accelerator with its hierarchical partition key.
Container Role Hierarchical partition key Document types
encounterDocumentations Primary /tenantId + /encounterId EncounterDocumentation, TranscriptSegment, ChartContextSnapshot, NoteDraft, CodingSuggestion

Document types

Contract document types, their owning container, and their identifier pattern.
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

Query patterns