Scheduling Information Unsolicited

HL7 Scheduling Information Unsolicited (SIU) messages are used to exchange patient appointment schedule information between clinical and administrative systems. Typically, HL7 SIU messages are generated by the hospital scheduling system and sent to a clinic or physician practice to request, reschedule, cancel or update outpatient services and provide updated patient medical record information.

There are 14 different trigger events for the SIU message, each sharing the same message format.

      • SIU^S12 – Notification of New Appointment Booking
      • SIU^S13 – Notification of Appointment Rescheduling
      • SIU^S14 – Notification of Appointment Modification
      • SIU^S15 – Notification of Appointment Cancellation
      • SIU^S16 – Notification of Appointment Discontinuation
      • SIU^S17 – Notification of Appointment Deletion
      • SIU^S18 – Notification of Addition of Service/Resource on Appointment
      • SIU^S19 – Notification of Modification of Service/Resource on Appointment
      • SIU^S20 – Notification of Cancellation of Service/Resource on Appointment
      • SIU^S21 – Notification of Discontinuation of Service/Resource on Appointment
      • SIU^S22 – Notification of Deletion of Service/Resource on Appointment
      • SIU^S23 – Notification of Blocked Schedule Timeslot(s)
      • SIU^S24 – Notification of Opened (“un-blocked”) schedule time slot(s)
      • SIU^S26 – Notification that Patient did not show up for Scheduled Appointment

Below is an example of an HL7 version 2.3 SIU^12 message, notifying the receiving application of a new appointment booking:

SCH|10345^10345|2196178^2196178|||10345|OFFICE^Office visit|reason for the appointment|OFFICE|60|m|^^60^20110617084500^20110617093000|||||9^DENT^ARTHUR^||||9^DENT^COREY^|||||Scheduled
PID|1||42||SMITH^PAUL||19781012|M|||1 Broadway Ave^^Fort Wayne^IN^46804||(260)555-1234|||S||999999999|||||||||||||||||||||
AIG|1|A|1^White, Charles|D^^
AIL|1|A|OFFICE^^^OFFICE|^Main Office||20110614084500|||45|m^Minutes||Scheduled
AIP|1|A|1^White^Charles^A^MD^^^^|D^White, Douglas||20110614084500|||45|m^Minutes||Scheduled





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. This segment is required.

SCH Schedule Activity Information. Contains general information about the scheduled appointment. This segment is required.

Patient Identification. Important patient identification information, including patient demographics. This segment is required.


Patient Visit. Contains information about patient visit details such as servicing facility, attending doctor, and visit ID. This segment is optional.


Resource Group. Identifies relationships between resources required for a scheduled event. This can include groups of resources that are used together in an event or to describe some other relationship between resources. Each group of RGS segments are followed by Appointment Information Segments. Every SIU message requires at least one RGS segment.


Appointment Information - General Resource. Captures information about various kinds of resources that require scheduling through a schedule filler application. For example, required equipment would be identified with an identification code. This segment is required.


Appointment Information - Location. Captures information about location resources that require scheduling through a schedule filler application, such as meeting, operating and examination rooms, or other locations. This segment is required.


Appointment Information - Personnel Resource. Captures information about the healthcare personnel resources which require scheduling on a schedule filler application. This includes any type of healthcare provider at the institution, such as technicians, physicians, nurses, surgeons, anesthesiologists, etc. This segment is required.

[ ] = optional, { } = repeating


For more information on implementing various HL7 message types, please refer to the HL7 Messaging Standard Implementation Guides corresponding to your required version. 



Other HL7 Message Types:

      • HL7 ADT (Admit, Discharge and Transfer)
      • HL7 ORM (Order Entry)
      • HL7 ORU (Observation Result)
      • HL7 MDM (Medical Document Management)
      • HL7 DFT (Detailed Financial Transactions)
      • HL7 BAR (Billing Account Record)
      • HL7 SIU (Scheduling Information Unsolicited)
      • HL7 RDS (Pharmacy/treatment Dispense)
      • HL7 RDE (Pharmacy/Treatment Encoded Order)
      • HL7 ACK (Acknowledgement Message)


Integration with HL7

HL7 is great standard, but anyone with first hand experience knows it's not without its challenges. We're here to help!

Let's talk

The ''non-standard" Standard

In practice, you'll find that everyone formats HL7 messages slightly different, even though it has a standard structure in place. With iNTERFACEWARE's integration engine, you can ensure that all data is normalized as intended for full compliance.


Version Compatiblity

What happens when the source destination is sending one version of HL7, while the recipient's system can only handle an older version of HL7? With Iguana you can convert HL7 versions on the fly.


Data Extraction

As you've seen, HL7 messages can contain a lot of information -- sometimes much more than you need. Simplify things using Iguana, by extracting the data from the specific HL7 fields you need. 


Future Proofing

The HL7 organization is always working on improving the standard and new versions will keep coming in the future. Ensure that your data always remains compatible with iNTERFACEWARE's integration engine, Iguana.