Decision owner
Nurse navigator
The named role remains accountable for the consequential decision.
Healthcare Providers
Designed for Patient
Guide a patient through the next steps of their care plan by combining appointments, referrals, benefits, and approved education content into plain-language instructions, escalating clinical questions to the care team.
Contract HEA-02 · primary aggregate PatientJourney · 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
Nurse navigator
The named role remains accountable for the consequential decision.
Governed evidence
6 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.
A patient recovering from a knee replacement asks why physical therapy has not started; the assistant shows the therapy order is open, the referral needs prior authorization, explains the 30 dollar in-network copay, offers two nearby appointment slots, and routes the patient's new swelling complaint to a nurse for same-day triage..
Guide a patient through the next steps of their care plan by combining appointments, referrals, benefits, and approved education content into plain-language instructions, escalating clinical questions to the care team.
Triage decision and human response to the patient gives Nurse navigator 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.
Nurse navigator 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: Patient performs ask a question about the next care step using Plain-language question in the patient portal or SMS and produces Classified navigation intent. The transition is deterministic and does not require autonomous model approval.
Why it matters: Classified navigation intent gives Care plan service the evidence needed to begin Resolve the active pathway and due steps, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/ask-a-question-about-the-next-care-step
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Automated stage
What happens: Care plan service performs resolve the active pathway and due steps using Patient identifier and pathway state and produces Ordered CarePlanStep list with due windows. The transition is deterministic and does not require autonomous model approval.
Why it matters: Ordered CarePlanStep list with due windows gives Benefits agent the evidence needed to begin Check coverage and preparation requirements, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/resolve-the-active-pathway-and-due-steps
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Automated stage
What happens: Benefits agent performs check coverage and preparation requirements using Planned service and payer coverage facts and produces Cost and prior-authorization expectation. The transition is deterministic and does not require autonomous model approval.
Why it matters: Cost and prior-authorization expectation gives Navigation assistant the evidence needed to begin Explain the step in approved plain language, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/check-coverage-and-preparation-requirements
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Automated stage
What happens: Navigation assistant performs explain the step in approved plain language using Care step, appointment, coverage facts, education content and produces Cited plain-language instruction at the patient's reading level. The transition is deterministic and does not require autonomous model approval.
Why it matters: Cited plain-language instruction at the patient's reading level gives Nurse navigator the evidence needed to begin Escalate clinical or urgent concerns, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/explain-the-step-in-approved-plain-language
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Human approval required
What happens: Nurse navigator performs escalate clinical or urgent concerns using Symptom report or clinical question and produces Triage decision and human response to the patient. A named human approver must review the evidence before the transition completes.
Why it matters: Triage decision and human response to the patient gives Nurse navigator 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/escalate-clinical-or-urgent-concerns
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 PatientJourney evidence.
Select a starter question or enter your own.
Loaded live from /api/config, /api/domain/model, and
/api/domain/sample.
patientJourneys/tenantId + /patientIdA patient recovering from a knee replacement asks why physical therapy has not started; the assistant shows the therapy order is open, the referral needs prior authorization, explains the 30 dollar in-network copay, offers two nearby appointment slots, and routes the patient's new swelling complaint to a nurse for same-day triage.
| Container | Role | Hierarchical partition key | Document types |
|---|---|---|---|
patientJourneys |
Primary | /tenantId + /patientId |
PatientJourney, CarePlanStep, AppointmentSlot, BenefitCoverageFact, CareTeamEscalation |
patientEducationLibrary |
Reference | /tenantId + /contentId |
EducationContent |
| Type | Container | Partition key | Identifier pattern | Embedding fields |
|---|---|---|---|---|
PatientJourney |
patientJourneys |
/tenantId + /patientId |
journey::{patientId} |
None |
CarePlanStep |
patientJourneys |
/tenantId + /patientId |
careplanstep::{patientId}::{stepId} |
None |
AppointmentSlot |
patientJourneys |
/tenantId + /patientId |
appointment::{patientId}::{appointmentId} |
None |
BenefitCoverageFact |
patientJourneys |
/tenantId + /patientId |
benefit::{patientId}::{coverageFactId} |
None |
EducationContent |
patientEducationLibrary |
/tenantId + /contentId |
education::{contentId}::{chunkIndex} |
bodyVector |
CareTeamEscalation |
patientJourneys |
/tenantId + /patientId |
escalation::{patientId}::{escalationId} |
patientMessageVector |
Assemble the patient's upcoming steps and appointments in one partition read.
patientJourneys
single-partition
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.patientId = @patientId AND c.type IN ('CarePlanStep','AppointmentSlot') AND c.completionState != 'completed' ORDER BY c.dueWindowEndUtc ASC
Partition-key fan-out control-plane query: find steps past their due window so the navigator can intervene. It cannot carry the second partition key because population health outreach is a panel-level view across patients, so it runs as a tenant-scoped scheduled sweep off the interactive path, bounded by steps whose due window closed inside the last 30 days, executed with MaxItemCount paging and continuation tokens.
patientJourneys
partition-key-fan-out
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.type = 'CarePlanStep' AND c.completionState = 'open' AND c.dueWindowEndUtc < @nowUtc ORDER BY c.dueWindowEndUtc ASC
Identify planned services that need payer approval before scheduling.
patientJourneys
single-partition
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.patientId = @patientId AND c.type = 'BenefitCoverageFact' AND c.priorAuthRequired = true ORDER BY c.copayAmount DESC
Partition-key fan-out control-plane query: show the care team escalations still awaiting a human response by urgency. It cannot carry the second partition key because the nurse triage queue is shared across the panel rather than per patient, so it runs as a tenant-scoped scheduled sweep off the interactive path, bounded by escalations awaiting response inside the 24-hour response standard, executed with MaxItemCount paging and continuation tokens.
patientJourneys
partition-key-fan-out
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.type = 'CareTeamEscalation' AND c.responseState = 'awaitingResponse' ORDER BY c.triageUrgency DESC