HL7 ADT Message and Event Types: A Comprehensive Overview
The HL7 (Health level Seven) is a globally accepted set of standards which governs the transfer and exchange of information about healthcare between systems used by healthcare organizations.
Standards for HL7 were developed to make the exchange of data between healthcare systems independent of the technology each one employs.
If an incident (such for instance, a patient being admitted in an institution) occurs and the system detects an event trigger, which then transmits the pertinent information (as messages) to the other systems within the company.
HL7 ADT Message and Event Types
Every HL7 message is generated in response to a trigger event, and consists of a series of segments. With the primary segment always showing the message header (MSH).
Segments are a series of lines of data or information that begin with a 3-character identification number (segment ID).
The blog that follows we’ll look at ADT messages, which play a an essential role in the HL7 processing because they are among the most commonly utilized messages.
HL7 Admit Discharge Transfer- ADT
ADT messages are a part of HL7. ADT messages are extremely important for processing HL7 and are among the most frequently used message.
They serve to relay important information, like the patient’s demographics, their states and information about visits to an health facility.
The HL7 ADT messages supply the system with information/data regarding the numerous kinds of events that trigger (registrations cancellations, registrations, patient discharges, admissions, updates or merges of patient data etc. ).
In a healthcare institution it is imperative to ensure that all patient data is recorded in the form of an Electronic Medical Record (EMR) or an Hospital Information System (HIS).
Updates and new data for patients are recorded in either the EMR as well as HIS systems, and then distributed to other systems via ADT messages. This leads to information about the patient being synchronized across systems and departments of healthcare.
HL7 ADT Message Structure
A an HL7 ADT message is comprised of segments that provide important details about trigger events. Some of the most crucial segments of an ADT message are:
The PV1 (Patient Visit) segment and PID (Patient Identification) segment, and occasionally an IN1 (insurance) segment.
HL7 ADT Message Types
ADT messages are essential in messages for HL7 messages because they provide vital information regarding the reason why the message was delivered and also regarding the patient.
For instance, an ADT-A04 (patient enrollment) message might be delivered through one of the EMR system, whereas an ADT-A05 (patient pre-admission) message could be delivered to the billing department’s system.
Speed and speed with the time a message is transmitted to a specific system could depend on the type of trigger events that are sent.
There are more than 50 kinds of ADT messages. ADT messages, which include:
- ADT-A01- patient admit
- ADT-A02- Patient Transfer
- ADT-A03- Patient Discharge
- ADT-AO4- Patient Registration
- ADT-A05- Patient Pre-administration
- ADT-A08- Patient Information Update
- ADT-A11- Cancel Patient Admit
- ADT-A12- Cancel Patient Transfer
- ADT-A13- Cancel Patient Discharge
HL7 ADT Event Types
The event type is used to convey the essential trigger event information to the receiving applications/systems. For instance, the majority of ADT trigger events are based on one object, for example, an admission event that generates a message comprised of data pertaining to one user or an account.
Additionally, some ADT events involve connections between several types of events (E.g. the merge events) and others are the collection of objects that do not have a connection at all (e.g. an event that is record-oriented query that is based on location).
Below is a listing of the ADT HL7 event types:
- A01- Admit/visit notice
- A02- Transferring to a patient
- A03- Discharge Visit
- A04- Register as a patient
- A05- Pre-admittance to for a patient
- A06- Convert from an outpatient to an inpatient
- A07- Transfer from an inpatient to an outpatient
- A08- Update patient information
- A09- Patient departing – tracking
- A10- Patient is arriving and tracking
- A11- Cancel admittance or go to notification
- A12- Cancel Transfer
- A13- Cancel discharge or end visit
- A14- Pending admit
- A15- Pending transfer
- A16- Pending discharge
- A17- Swap patients
- A18- Merge patient data
- A19- Patient query
- A20 – Bed status update
- A21- Patient takes”leave of absence.’
- A22-patient comes back from a leave of absence.’
- A23- Deleting an existing patient record
- A24- Link Patient data
- A25- Cancel pending discharge
- A26- Cancel pending transfer
- A27-Cancel pending admit
- A28- Add person data
- A29- Delete person data
- A30- Merge person data
- A31- update person data
- A32- Cancel patient’s arrival-tracking
- A33- Cancel patient departing -tracking
- A34- Merge patient data- patient ID only
- A35- Merge patient data- account number only
- A36- Merge patient informationpatient ID and account number
- A37- Unlink patient date
- A38- Cancel pre-admit
- A39- Merge patient -patient ID
- A40- Merge patient- patient identifier list
- A41- Merge account- patient account number
- A42- Visit to merge- Visit number
- A43- Move patient data- patient identifier list
- A44- Move account information- patient account number
- A45- Information-visit to move visit number
- A46- Change patient ID
- A47- Change patient identifier list
- A48- Change alternate patient ID
- A49- Change patient account number
- A50 – change visit number
- A51- alter alternative ID for a visit.
- A52 Cancel the leave the patient
- A53- Cancel patient’s return from leave of absence
- A54- Change attending doctor
- A55 Cancel change the attending physician
- A60-Update allergy data
- A61- Change consulting doctor
- A62- Cancel Change of consult with doctor
Conclusion
HL7 ADT messages serve a significant role in HL7 as they contain important information in regard to the patient including demographics of the patient and also provide crucial information on trigger events (such as visits to the patient or discharge admissions, transfers registration, insurance, etc. ).
If you’d like learn more about the integration of HL7 in your healthcare organization, click here to learn more about how our services will help you grow your healthcare company or organization.
