# ADT feeds
URL: https://docs.awellhealth.com/docs/automate-with-events/adt-feeds

> For the complete documentation index, see [llms.txt](https://docs.awellhealth.com/llms.txt).



An **ADT feed** carries Admission, Discharge and Transfer messages, the standard way healthcare systems
tell each other about a patient's movements and status changes within a facility.

Because the feed reflects where a patient actually is, it's a strong trigger: care can follow admission
and discharge without anyone remembering to start a flow.

## Mirth Connect processes the feed [#mirth-connect-processes-the-feed]

Awell uses **Mirth Connect** as the integration engine for ADT feeds. See
[How Awell connects to other systems](/docs/connect-systems/healthcare-interoperability).

Mirth is configured to intercept the hospital's ADT messages. When one arrives, Awell processes it,
extracts the key patient information and identifiers, and starts, updates or stops the relevant care
flow.

## The hard parts are agreements, not code [#the-hard-parts-are-agreements-not-code]

Settle these with the hospital:

* **Which message types** should act, and what each should do.
* **Which identifier** matches the patient. See
  [Patient identifiers](/docs/connect-systems/patient-identifiers).
* **What happens on a transfer**, as distinct from an admission or a discharge.

For appointment-driven rather than admission-driven enrollment, see
[Patient creation with SIU messages](/docs/connect-systems/patient-creation-with-siu-messages).

## Next steps [#next-steps]

**Next:** [Trigger with the API](/docs/automate-with-events/trigger-with-the-api) for full control.