HL7 Trigger Events: What Sets a Message in Motion

What Is a Trigger Event?

Imagine walking into a hospital, and the moment you register at the front desk, the pharmacy, lab, and billing department all instantly know you arrived without anyone picking up a phone. That is, HL7 trigger events doing their job silently in the background.

HL7 (Health Level Seven) is a set of international standards that lets healthcare software systems talk to each other. It is the shared language spoken between a hospital’s registration software, its lab systems, its pharmacy, and its billing software.

A trigger event is simply a real-world happening inside a hospital that causes one system to send a message to another. Every trigger event has a short code (like A01, O01, R01). The letter indicates the message type, and the numbers identify the specific event.

How HL7 Message Flow Works

The basic flow is always the same:

• Something happens in the real world (a patient is admitted, a test is ordered)
• That event triggers a specific code in the sending system
• An HL7 message is generated and sent to receiving systems
• Each receiving system acts on the information automatically

Example: A nurse admits a patient → the ADT system fires trigger A01 → an HL7 ADT^A01 message is sent → the lab and pharmacy systems update their records automatically.

What Does an HL7 Message Look Like?

Every HL7 message has a header segment called MSH. Field 9 in that header contains the message type and trigger event. Here is a real patient admission message:

MSH|^~&|RegSystem|CityHospital|LabSystem|CityHospital|
20240315083000||ADT^A01|MSG001|P|2.5
EVN|A01|20240315083000
PID|1||P12345^^^HospID||Sharma^Rahul||19850412|M
PV1|1|I|Ward3^Bed7^CityHospital|||Dr.Mehta

The key part is ADT^A01 in the MSH segment. ADT = Admit, Discharge, Transfer (the message family). A01 = Patient Admitted (the specific trigger event).

The Most Commonly Used Trigger Events

HL7 v2 has hundreds of trigger events, but in day-to-day hospital operations a small set does most of the work.

ADT Messages — Patient Movement

ADT (Admit, Discharge, Transfer) messages track every step of a patient’s physical journey. These are the most common HL7 messages in any hospital.

Tip: A01 through A04 cover over 70% of real-world ADT traffic in most hospitals. Learn these four first.

ORM & ORU Messages — Orders and Results

Once a patient is in the system, clinicians start placing orders. The ORM and ORU families handle everything from order placement to result delivery.

MFN & SIU Messages — Reference Data and Scheduling

Hospitals maintain master lists of doctors, drugs, wards, and fee codes. MFN messages keep these reference tables consistent across all systems. SIU messages handle appointment scheduling.

A Complete Patient Visit — Trigger by Trigger

Here is how trigger events fire across a typical patient visit from arrival to discharge:

Common Misconceptions

Misconception: A01 and A04 are the same thing.

They are not. A01 creates an inpatient visit with a bed assignment. A04 creates an outpatient visit without one. Using the wrong trigger causes billing errors because inpatient and outpatient carry different fee structures.

Misconception: HL7 is only needed for admissions.

ADT messages are just the most visible part. HL7 trigger events cover the full patient journey including scheduling, orders, lab results, billing, referrals, and master data management.

HL7 v2 vs FHIR: HL7 v2 uses pipe-delimited text messages. FHIR uses REST APIs and JSON. The concept is identical: something happens, broadcast it but FHIR calls them subscription notifications instead of trigger events.