Admit, Discharge, Transfer (ADT) | Medplum
ADT Overview
ADT stands for "Admit, Discharge, Transfer." It is a type of HL7 message used in electronic health records systems to communicate changes in a patient's demographic or visit status. This includes registration, admission, discharge, and transfer information about a patient.
This guide assumes you have already set up a Medplum agent or aggregator equivalent to connect to the legacy healthcare application that you want to interface with and are able to receive the feed.
The following are a subset of the event types for ADT:
A01: Admit/visit notificationA02: Transfer a patientA03: Discharge a patientA04: Register a patientA05: Pre-admit a patientA06: Change an outpatient to an inpatientA07: Change an inpatient to an outpatientA08: Update patient informationA09: Patient departing - trackingA10: Patient arriving - trackingA11: Cancel admit/visit notificationA12: Cancel transferA13: Cancel dischargeA14: Pending admitA15: Pending transferA16: Pending dischargeA17: Swap patients
Consuming ADT
This example synchronizes data with your FHIR datastore on register and update messages. This example ignores message types other than A04 and A08.
TODO: Create an example that throws away all of the message types except for A04 and A08 and update demographic in case of A04 and A08
Publishing ADT
This example publishes an A04 event when a Patient is created and an A08 when the Patient resource is updated. No other message types are created as part of this feed.
TODO: Create an example that throws away all of the message types except for A04 and A08 and update demographic in case of A04 and A08
Related Reading
- Agent enables connectivity at the edge for HL7 feeds and more
- Bot setup for HL7 a guide for a hello world bot to parse HL7
- Enterprise Master Patient Index implementations often use ADT as part of the deduplication architecture
- Medplum Agent Demo on Youtube - 15 min
- HL7 Bot Demo Video on Youtbve - 2 min
- Consuming ADT
- Publishing ADT
- Related Reading