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.
[[Diagram or video of HL7 SIU message sent from registration application to a patient imaging application]]
Below is an example of an HL7 version 2.3 SIU^12 message, notifying the receiving application of a new appointment booking:
MSH|^~\&|MESA_OP|XYZ_HOSPITAL|iFW|ABC_HOSPITAL|20110613061611||SIU^S12|24916560|P|2.3||||||
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|||||||||||||||||||||
PV1|1|O|||||1^Smith^Miranda^A^MD^^^^|2^Withers^Peter^D^MD^^^^||||||||||||||||||||||||||||||||||||||||||99158||
RGS|1|A
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
Segment |
Description |
| 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. This segment is required. |
| SCH | Schedule Activity Information. Contains general information about the scheduled appointment. This segment is required. |
| PID |
Patient Identification. Important patient identification information, including patient demographics. This segment is required. |
|
[PV1] |
Patient Visit. Contains information about patient visit details such as servicing facility, attending doctor, and visit ID. This segment is optional. |
|
RGS |
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. |
|
AIG |
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. |
|
AIL |
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. |
|
AIP |
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:
|
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.
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.
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.
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.