Healthcare Overview

Healthcare-specific workflows showing how the agent engine, world model, and EHR integration come together in production.

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

Inbound scheduling, outbound appointment campaigns, insurance capture, gap closure

Voice + SMS

Multi-encounter follow-up, cross-session memory, personalized interactions, adherence tracking

Voice + SMS

Safety testing frameworks, simulation-based validation, metric design, human review processes

Testing + evaluation

Risk stratification, prediction, evidence-based outreach across clinical indications using clinical and sociodemographic data

Voice + SMS + Surfaces

Full contact center architecture, IVR/ACD replacement, quality scoring, call intelligence, operator workflows

Voice

Patient Scheduling and OutreachCare CoordinationPopulation HealthClinical VerificationHealthcare Contact Center

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) manages configuration across all channels.

Last updated

Was this helpful?