Healthcare Overview

Healthcare workflow patterns showing how agents, data, channels, testing, and external integrations can be composed.

These guides apply Concurrence's data, agent, channel, and operational capabilities to healthcare workflows. Each scenario identifies work that can be configured, the external systems it depends on, and the evidence needed to evaluate the result.

Voice, text, and messaging workflows can reuse compatible agent and Context Graph definitions and selected world-model context. Their runtimes, delivery rules, and operator controls differ. A workflow that combines a phone call, a form, and a reminder needs explicit routing and verification at each step. See Reasoning Engine for execution behavior and Channels for transport differences.

Use a Scenario as a Design Exercise

For each scenario, identify the operational outcome, source data, allowed actions, confirmation evidence, and exception owner. Then map those needs to the platform components introduced in Core Concepts. The end-to-end example shows the method for an appointment change.

Keep the workflow's business result separate from its conversation metrics. A recorded referral request, a delivered reminder, and a completed visit are different outcomes with different sources of evidence.

Scenarios

Each guide walks through a healthcare workflow pattern. Some steps require customer-authored automation, configured external systems, or explicitly labeled sample-data previews; treat the guides as design patterns rather than proof that every capability is enabled in every workspace.

Use Case	What It Covers	Primary Channel
Patient Scheduling and Outreach	Inbound scheduling, outbound appointment campaigns, insurance capture, gap closure	Voice + SMS
Care Coordination	Multi-encounter follow-up, cross-session memory, personalized interactions, adherence tracking	Voice + SMS
Clinical Verification	Safety testing frameworks, simulation-based validation, metric design, human review processes	Testing + evaluation
Population Health and Risk Management	Risk stratification, prediction, evidence-based outreach across clinical indications using clinical and sociodemographic data	Voice + SMS + Surfaces
Healthcare Contact Center	Conversational routing, quality evidence, call intelligence, operator workflows, and integration boundaries	Voice

Channel Selection

The guides target Platform API concepts. Channel support and external delivery still depend on workspace provisioning, service configuration, consent, and the selected runtime:

• Scheduling, outreach, care coordination, contact center - Phone and SMS workflows using the voice pipeline, world model, EHR connectors, and operator escalation.
• Patient-facing chat, digital health coaching, in-app messaging - Text sessions through the Platform API's text channel with the same memory system, context graphs, and world model integration.
• Multi-channel deployments - Compatible agent and Context Graph versions can be reused across supported channels, with channel-specific configuration and testing. Agent Forge manages the supported Platform configuration resources.