> For the complete documentation index, see [llms.txt](https://docs.concurrence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.concurrence.com/use-cases/use-cases.md).

# 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](/agent/reasoning-engine.md) for execution behavior and [Channels](/channels/conversations.md) 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](/platform-overview/core-concepts.md). The [end-to-end example](/platform-overview/how-it-works.md) 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](/use-cases/use-cases/scheduling-outreach.md)     | Inbound scheduling, outbound appointment campaigns, insurance capture, gap closure                                            | Voice + SMS            |
| [Care Coordination](/use-cases/use-cases/care-coordination.md)                     | Multi-encounter follow-up, cross-session memory, personalized interactions, adherence tracking                                | Voice + SMS            |
| [Clinical Verification](/use-cases/use-cases/clinical-verification.md)             | Safety testing frameworks, simulation-based validation, metric design, human review processes                                 | Testing + evaluation   |
| [Population Health and Risk Management](/use-cases/use-cases/population-health.md) | Risk stratification, prediction, evidence-based outreach across clinical indications using clinical and sociodemographic data | Voice + SMS + Surfaces |
| [Healthcare Contact Center](/use-cases/use-cases/contact-center.md)                | 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 integrations, 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](/reference/agent-forge.md) manages the supported Platform configuration resources.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.concurrence.com/use-cases/use-cases.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.