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

# Use Cases

- [Healthcare Overview](https://docs.concurrence.com/use-cases/use-cases.md): Healthcare workflow patterns showing how agents, data, channels, testing, and external integrations can be composed.
- [Patient Scheduling and Outreach](https://docs.concurrence.com/use-cases/use-cases/scheduling-outreach.md): End-to-end patient scheduling and outbound outreach workflow, from clinical data loading through interaction completion and policy-gated external updates.
- [Care Coordination](https://docs.concurrence.com/use-cases/use-cases/care-coordination.md): Multi-encounter care coordination with cross-session memory, world model data unification, and personalized patient interactions.
- [Clinical Verification](https://docs.concurrence.com/use-cases/use-cases/clinical-verification.md): Build clinical-safety evidence with representative simulations, customer-owned release criteria, and qualified human review.
- [Population Health](https://docs.concurrence.com/use-cases/use-cases/population-health.md): A configuration pattern for population outreach that combines ingestion, customer-defined risk logic, explicit outreach workflows, and agent conversations.
- [Healthcare Contact Center](https://docs.concurrence.com/use-cases/use-cases/contact-center.md): How Concurrence maps voice, text, operator, analytics, and data-collection capabilities onto contact-center workflows.


---

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