Your systems stay in control
Emma integrates with the following system types, consuming the context each platform provides and returning the outcomes each workflow produces.Two ways to start a workflow
Event-Driven
Your system notifies Emma when something happens. Emma automatically starts the matching workflow. Supported events include intake abandoned, appointment created, appointment approaching, payment failed, prescription or fulfillment status changed, and patient follow-up required.
Request-Driven
Your application calls Emma directly to start an action. Use the REST API to initiate a patient call, start a workflow, perform a scheduling action, or retrieve status.
Context in, outcome out
Context In
- Patient or external system identifiers
- Contact information
- Workflow or event type
- Appointment or form context
- Transaction or payment context
Outcome Out
- Workflow status
- Call status
- Patient disposition
- Appointment action taken
- Form completion status
- Payment recovery outcome
- Escalation status
- Interaction metadata
Augment, don’t replace
Your platforms keep owning their data. Each platform keeps its data domain. Emma is designed to consume the context a patient engagement workflow needs and send the resulting actions and outcomes back to the right system — so you add AI-powered patient engagement without changing your clinical or operational stack.