Kontakt.io integration reference
HL7 ADT (Admit, Discharge, and Transfer) messages are among the most widely-used and high-volume message types in healthcare. They cover numerous trigger events related to patient admission, transfer, discharge, and updates to patient information.
In healthcare settings, patient information is typically recorded within a Hospital Information System (HIS) or Electronic Medical Record (EMR). These systems serve as centralized repositories for patient data. When new patient records are created or existing records are updated, ADT messages are used to distribute this information to ancillary systems. This ensures that all systems maintain synchronized and up-to-date patient data.
A diverse array of patient and event information is exchanged through over 50 different types of ADT messages. These messages serve distinct purposes and facilitate the seamless flow of data.
Below are some of the most common HL7 ADT messages.
|
Trigger Event |
Description |
|---|---|
|
ADT^A01 |
Patient Admit/Visit; Triggered when a patient is admitted to a healthcare facility. |
|
ADT^A02 |
Patient Transfer; Triggered when a patient is transferred between different locations or units within a healthcare facility or between different facilities. |
|
ADT^A03 |
Patient Discharge; Triggered when a patient is discharged or released from a healthcare facility. |
|
ADT^A04 |
Patient Registration (Pre-admit); Triggered when a patient's registration is created prior to admission. |
|
ADT^A05 |
Patient Pre-Admit (same as A04 with visit number = 0); Triggered when a patient's registration is created prior to admission without assigning a visit number. |
|
ADT^A08 |
Patient Information Update; Triggered when there is a change or update in patient information. |
|
ADT^A09 |
Patient Departing - tracking: Triggered when a patient leaves a facility without being formally discharged (e.g., elopement). |
|
ADT^A11 |
Cancel Patient Admit; Triggered when an admission or visit notification is canceled. |
|
ADT^A12 |
Cancel Patient Transfer; Triggered when a patient transfer is canceled. |
|
ADT^A13 |
Cancel Patient Discharge; Triggered when a discharge or end visit event is canceled. |
The composition of segments within an ADT message can vary based on the type of ADT event as well as the HL7 version.
The below is a sample of an HL7 version 2.4 ADT^A04 message, which represents a patient registration (Pre-admit).
MSH|^~\&|SendingApp|SendingFac|ReceivingApp|ReceivingFac|||ADT^A04|123456789|P|2.4||||||| EVN||200007010800||||200007010800 PID|||123456^^^ADT1||Doe^John||19610615|M-||2106-3|123 Main St^^Anytown^NC^12345-6789|USA|(555)555-5555|||(555)555-1234~(555)555-5678||S||123456789^2^M10|987654321|9-87654^NC NK1|1|Smith^Mary^L|SPO|||||20011105 PV1||E||||||Doctor^John^D^^Dr|||||||||||V1295^^^ADT1|||||||||||||||||||||||||200007010800|||||||| PV2|||^ABDOMINAL PAIN OBX|1|HD|SR Instance UID||1.123456.2.2000.31.2.1||||||F|||||| AL1|1||^PENICILLIN||PRODUCES HIVES~RASH AL1|2||^CAT DANDER DG1|001|I9|1550|MAL NEO LIVER, PRIMARY|19880501103005|F|| PR1|2234|M11|111^CODE151|COMMON PROCEDURES|198809081123 ROL|45^RECORDER^ROLE MASTER LIST|AD|CP|Smith^Kate^E|199505011201 GT1|1122|1519|Gates^Bill^A IN1|001|A357|1234|BCMD|||||132987 IN2|ID1551001|SSN12345678
In this sample message:
|
Segment |
Description |
Occurrence |
|---|---|---|
|
MSH |
Message Header The header contains information about the sending system and location, the receiving system and location, the date and time of when the message was created, the type of trigger event being communicated, and the HL7 message version being used. |
1 |
|
EVN |
Event Type Communicates the event that occurred in order for the message to be generated. This segment is a crucial part of the data flow, as it indicates where and when a message is sent based on the type of event. |
1 |
|
PID |
Patient Identification Important patient identification information, including patient demographics. |
1 |
|
NK1 |
Next of Kin / Associated Parties Contact information of the patient’s closest living relative(s) in case they need to be contacted. This segment can be repeated as necessary. |
0-n |
|
PV1 |
Patient Visit Contains information about patient visit details such as servicing facility, attending doctor, and visit ID. |
1 |
|
PV2 |
Patient Visit - Additional Information This segment is a continuation of information specific to the patient’s visit, and is the segment where the Admit Reason is communicated. It is an optional segment if a DG1 segment is included in the message. If there is no DG1 segment, then the PV2 segment is required. |
0-1 |
|
OBX |
Observation/Result Each OBX segment carries information about a single medical observation or result. This segment is more frequently used in ORU (Observational Report) messages. It can be repeated as necessary. |
0-n |
|
AL1 |
Patient Allergy Information Contains information about a patient’s allergies including allergen type, reaction and severity. This segment can be repeated as necessary. |
0-n |
|
DG1 |
Diagnosis Provides details about the patient’s diagnosis and uses ICD coding standards to communicate specific diseases, signs, symptoms, abnormalities, patient complaints, etc. |
0-n |
|
PR1 |
Procedures Holds information about the various procedures that can be performed on a patient, and can be repeated to communicate information about multiple procedures. |
0-n |
|
ROL |
Role Provides information about roles associated with individuals or organizations in relation to a specific event or activity. It includes details such as the identifier, name, contact information, and role/function code of the person or organization involved in the event described in the message. |
0-n |
|
GT1 |
Guarantor Contains information about the guarantor or responsible party associated with the patient's account. |
0-1 |
|
IN1 |
Insurance The insurance policy coverage information, such as plan and provider identifiers, necessary to produce patient and insurance bills. |
0-1 |
|
IN2 |
Insurance Additional Information |
0-1 |
Occurrence column indicates the possible number of times a segment may appear within a single message.
1 = must occur exactly once in the message
0-n = may occur zero or more times within the message
0-1 = may occur zero or one time within the message
For more information on implementing various HL7 message types, refer to the HL7 Messaging Standard Implementation Guides corresponding to your required version.