Care Coordination

Multi-encounter care coordination with cross-session memory, world model data unification, and personalized patient interactions.

Use generated memory for continuity and authoritative tools for current clinical or scheduling facts.

This guide covers how Concurrence supports ongoing care coordination across multiple patient encounters. Unlike a single scheduling interaction, care coordination involves repeated touchpoints over weeks or months across voice and text channels, with the agent building context over time and personalizing each interaction.

The Challenge

Patients with chronic conditions or complex care plans interact with the health system frequently. Each interaction generates information that should inform the next one. In practice, this context is often lost: different staff members handle different calls, notes are incomplete, and patients have to repeat themselves.

Effective care coordination requires continuity. The agent must remember what happened in prior conversations - whether they occurred over phone or text - track progress against care plan goals, and adapt its approach based on what has worked (or not worked) for each patient.

Memory Across Encounters

Concurrence's memory system can turn completed conversation evidence into source-linked episodic observations and a consolidated user model for later sessions. Connected clinical records also contribute a separate deterministic clinical-state summary. Processing is asynchronous and generated memory is not guaranteed to capture every detail, so current clinical and scheduling facts still come from authoritative data tools.

Context available across encounters:

• Generated episodic observations can carry forward patient-reported barriers, preferences, and prior interaction context when memory processing succeeds.

• The bounded semantic user model can consolidate longer-lived goals, trajectories, and interaction preferences without becoming an authoritative clinical record.

• Connector-derived clinical state separately supplies current conditions, medications, and allergies with its own provenance.

• Scheduling, escalation, and care-team facts should come from current world-model records and authoritative tools rather than generated memory alone.

How memory improves coordination:

On a first call, the agent may follow a standard check-in flow. In later sessions, available memory can help it recognize that a patient prefers morning calls or wants concise explanations. Current medication and scheduling facts still come from connected records, and configured workflows decide timing and reminders.

Over longer time horizons, teams can analyze source-linked observations and explicit outcomes for patterns that are not visible in any single interaction. A suspected medication-adherence cycle, for example, should be validated against current records before it changes outreach or agent guidance.

World Model Unifies Data Sources

The world model projects supported information from multiple systems into entity views that authorized agents and tools can access during a conversation.

Data Source	What It Provides
EHR	Diagnoses, medications, lab results, care plan
Voice conversations	Patient-reported symptoms, concerns, preferences
Manual entry	Care team notes, social work assessments
Scheduling system	Appointment history, upcoming visits
Connected devices	Vitals, weight trends, activity data

When an authorized tool exposes a current fact, the workflow can avoid asking the patient to repeat it. For example, a configured device-data integration could expose a weight trend for an authored care-coordination step. Projection freshness and source authority still need to be checked before the agent treats the value as current.

This can expose conflicting information rather than hiding it. If the EHR shows a medication was discontinued but the patient mentions still taking it, the agent can preserve both sources and follow the authored escalation or verification workflow.

Personalized Interactions

Each interaction is shaped by what the platform knows about the patient. Personalization happens across several dimensions:

Communication style: Some patients want detailed explanations. Others want brief, direct updates. When generated memory captures a supported preference, the agent can use it while remaining prepared for that preference to be incomplete or outdated.

Timing and cadence: Configured triggers and scheduling rules can use known preferences and prior outcomes. A team might move a patient who consistently misses afternoon calls to a morning outreach window.

Content focus: Authored state guidance and current tool results can prioritize topics relevant to the patient's situation. A medication change or care milestone should influence the conversation only when the workflow has current, authorized evidence for it.

Barrier awareness: Available patient-reported context can inform authored recommendations or referral options. Consequential facts should be verified when they may have changed.

Operator Escalation

Not every situation is within the agent's scope. Authored context-graph instructions define when the agent should escalate to a human operator.

When the agent escalates:

• Patient reports new or worsening symptoms that require clinical assessment

• The patient's situation has changed significantly since the last care team update (new diagnosis, hospitalization, family crisis)

• The patient explicitly requests to speak with a nurse or provider

• The agent reaches an authored uncertainty or scope boundary

How escalation works:

Depending on the channel, retained evidence, and configured context, the selected run can give the operator information such as:

• Current conversation context and patient concern

• Relevant history from prior interactions

• Selected world-model or tool context made available to that operator workflow

• Reason for escalation

For voice, the operator can review available context before joining or taking over the live call. The handoff should not be treated as a guaranteed full clinical briefing; teams should keep authoritative records accessible and record the resolution through the configured workflow.

What This Looks Like Over Time

In a care coordination deployment, the agent handles routine touchpoints (medication check-ins, appointment reminders, care plan reinforcement) while care managers focus on patients who need clinical judgment.

As supported interaction history accumulates, later calls can use available memory and current world-model context for continuity. Teams should measure whether that personalization improves explicit outcomes, such as adherence or missed appointments, rather than assume improvement from history alone.

For details on how to verify clinical quality in care coordination workflows, see the Clinical Verification guide. For the memory system's layered architecture, see Memory.