HL7 ADT Message Specifications & Data Flow

HL7 ADT Message Specifications & Data Flow

Explore the technical details of HL7 ADT Message Specifications and Data Flow, as well as the sample messages for the TS Mirth Interface Generator.

HL7 ADT Message Specifications

The Interface generated by the TS Mirth Interface Generator is based on the TS Standards HL7. TS Standards are a subset of the full standard, as it is defined in the HL7 manual. It generates the outgoing as well as registration interface, which receives the HL 7 message containing demographic, registration, patient visit, next of kin, and insurance information.

The following are the triggering events supported by the interface generated by the TS Mirth Interface Generator. The notation for describing the message structure is explained in Chapter Two of the HL7 manual, “Format for Defining Abstract Messages.”

• ADT^A01 Admit/Visit Notification: This trigger event is used when a patient is admitted.
• ADT^A02 Transfer a Patient: This trigger event is used when a patient is transferred.
• ADT^A03 Discharge/End Visit: This trigger event is used when a patient is discharged.
• ADT^A04 Register a Patient: This trigger event is used when a patient is checking into a specific visit or registered for a Hospital Outpatient Visit within the application.
• ADT^A05 Pre-admit a Patient: This trigger event is used when a patient is pre-admitted.
• ADT^A08 Update Patient Information: This trigger event is used extensively for all the updates to a patient’s demographics, registration, and visit information.

Deploy Interface/Channel

Segments Implementation Detail

Segment Columns Legend

• SEQ: The SEQ column indicates the ordinal position of each data field within a segment, following the HL7 convention. In this convention, the segment name at the beginning of each segment is considered field 0.
• Element: The Element Name column corresponds to the Element Name within the HL7 standard
• Data Type: The Data Type column contains restrictions on the constraints of the data field. These data types follow the HL7 conventions. For more information, refer to Chapter 2 of the HL7 standard.
• Length: The Length column contains the numeric length used by the interface. It is calculated to include the component and sub-component separators. Repetition characters are not included in calculating the maximum length. These values may vary from the HL7 standard.
• Required: A value of $R$ is placed in this column to indicate that it is a required field.
• Comments: The Comments column describes the details of the field, specific values allowed, description of conditions, constant values, and mapping table references.
• Fields shaded Grey: All HL7 fields are listed in the following section; however, data for the fields shaded grey will only be sent through this interface.

Segment Listings

Below are the segments of the ADT message.

MSH – Message Header

EVN – Event Type

PID – Patient Identification

PD1 – Patient Demographic Information

NK1 – Next of Kin

PV1 – Patient Visit

Insurance Segment

Acknowledgment

Data Flow Details of Interfaces

Outbound Interface Overall Data Flow

Following is a rough diagram that shows all the systems involved in the data flow from source system to destination system.

Data Flow Details

Technosoft Outbound Interface Implementation Workflow.

Data Flow Steps In Detail

• Step 1: Insert the data that needs to be sent into the source database tables.
• Step 2: Mirth Engine will periodically check for new records in the interface out tables.
• Step 3: If a new record is found, then the interface engine fetches data from the database.
• Step 4: Interface Engine transforms data into HL7 format and performs any lookup translations, ID padding, etc.
• Step 5: Interface Engine transmits data to the other vendor System in HL7 Format using TCP/IP Sockets.
• Step 6 Path A: The other vendor accepts the message and sends back a positive acknowledgement.
• Step 7 Path A: The Interface Engine changes the status of the record to Successful.
• Step 6 Path B: The other vendor accepts the message and sends back a Negative acknowledgment.
• Step 7 Path B: The Interface Engine changes the status of the record to Failed. Outbound – Source Database

Outbound – Source Database

Inbound Interface Overall Data Flow

The following is a rough diagram that shows all the systems involved in the data flow from the source system to the destination system.

Data Flow Details

Technosoft Inbound Interface Implementation Workflow.

Data Flow Steps In Detail

• Step 1: The External System will send an HL7 message to Mirth (Destination Interface Engine).
• Step 2: Mirth Engine will send a positive acknowledgment to the external system if the message is in proper HL7 format and the Interface supports that HL7 event.
• Step 3: Parse the message and create Insert SQL statement(s) from the message data.
• Step 4: Insert data in the database table(s) set up during the Interface generation.
• Step 5: Now, further processing can be performed on the stored message information.

Sample Message

Would you like to explore further?

Would you like to read through the entire process again?