# Healthcare Overview

Amigo is purpose-built for healthcare. The platform is designed around the requirements that healthcare organizations face: clinical safety, regulatory compliance, patient privacy, and the need to prove that systems work before they touch real patients.

The platform's [reasoning engine](/agent/reasoning-engine.md) processes patient interactions across multiple channels through a unified pipeline. The Platform API supports voice (phone calls), SMS/text conversations, and API-driven workflows - all sharing the same context graphs, tool execution, safety rules, and world model integration. A single healthcare workflow can span multiple channels: an agent handles a phone call, texts the patient a data collection form, and sends an SMS reminder before their appointment - all orchestrated by the same reasoning engine.

## Scenarios

Each guide walks through a specific healthcare workflow showing how the platform's capabilities come together in practice.

| 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 |
| [Contact Center Replacement](/use-cases/use-cases/contact-center.md)               | Full contact center architecture, IVR/ACD replacement, quality scoring, call intelligence, operator workflows                 | Voice                  |

{% content-ref url="/pages/B2ioPgPl356PSnN7kByq" %}
[Patient Scheduling and Outreach](/use-cases/use-cases/scheduling-outreach.md)
{% endcontent-ref %}

{% content-ref url="/pages/lh3JAooUE3smqxwLsp6z" %}
[Care Coordination](/use-cases/use-cases/care-coordination.md)
{% endcontent-ref %}

{% content-ref url="/pages/XHxqQxRseTMTgzNkJOL8" %}
[Population Health](/use-cases/use-cases/population-health.md)
{% endcontent-ref %}

{% content-ref url="/pages/tHO7p2KbgOCvb9XcyBYq" %}
[Clinical Verification](/use-cases/use-cases/clinical-verification.md)
{% endcontent-ref %}

{% content-ref url="/pages/vBqoMBtJ2LFBqwPiOTHK" %}
[Healthcare Contact Center](/use-cases/use-cases/contact-center.md)
{% endcontent-ref %}

## Channel Selection

All use cases run on the Platform API. The channel depends on the workflow:

* **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** - A single agent configuration handles voice, SMS, and text. Agent Forge ([Agent Forge](/reference/agent-forge.md)) manages configuration across all channels.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.amigo.ai/use-cases/use-cases.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.