Healthcare Providers

Patient Navigation Assistant

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

Escalate clinical or urgent concerns: 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

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.

Business problem

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

Decision to make

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.

Outcome to show

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.

  1. 1Ask a question about the next care step
  2. 2Resolve the active pathway and due steps
  3. 3Check coverage and preparation requirements
  4. 4Explain the step in approved plain language
  5. 5Escalate clinical or urgent concerns

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

Nurse navigator 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 PatientJourney 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
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.
Primary aggregate
PatientJourney
Primary container
patientJourneys
Hierarchical key
/tenantId + /patientId
Schema version
1

Sample scenario

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.

Physical Cosmos DB containers

Every container provisioned for this accelerator with its hierarchical partition key.
Container Role Hierarchical partition key Document types
patientJourneys Primary /tenantId + /patientId PatientJourney, CarePlanStep, AppointmentSlot, BenefitCoverageFact, CareTeamEscalation
patientEducationLibrary Reference /tenantId + /contentId EducationContent

Document types

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

Query patterns