HL7 SIU_S17 Appointment Deletion

HL7 message structure SIU_S12 groups and segments from HL7 v2.5.1 Hide structure

These are the generated groups and segments for the version selected at the top of the page. The article explains the workflow, and this panel follows the chosen HL7 version.

Message Structure

SegmentNameRequiredRepeatable
Message Header Yes No
Scheduling Activity Information Yes No
Timing/Quantity No Yes
Notes and Comments No Yes
SIU_S12.PATIENT
Patient group No Yes
Patient Identification Yes No
Patient Additional Demographic No No
Patient Visit No No
Patient Visit - Additional Information No No
Observation/Result No Yes
Diagnosis No Yes
SIU_S12.RESOURCES
Resources group Yes Yes
Resource Group Yes No
SIU_S12.SERVICE
Service group No Yes
Appointment Information Yes No
Notes and Comments No Yes
SIU_S12.GENERAL_RESOURCE
General Resource group No Yes
Appointment Information - General Resource Yes No
Notes and Comments No Yes
SIU_S12.LOCATION_RESOURCE
Location Resource group No Yes
Appointment Information - Location Resource Yes No
Notes and Comments No Yes
SIU_S12.PERSONNEL_RESOURCE
Personnel Resource group No Yes
Appointment Information - Personnel Resource Yes No
Notes and Comments No Yes

SIU_S17 notifies receivers that an appointment has been deleted. In HL7 scheduling language, deletion is for appointments that were entered in error and need to be removed from the schedule so they do not affect schedule statistics or normal workflow.

S17 uses SIU^S17^SIU_S12. It shares the same SIU_S12 structure as booking, rescheduling, modification, cancellation, and no-show notification, but the business meaning is very different.

A small SIU S17 example

MSH|^~\&|SCHED|CITYHOSP|EHR|CITYHOSP|20260717103000||SIU^S17^SIU_S12|SIU170042|P|2.5.1 SCH|A100045|F100045||ERROR^Entered in error^L|DELETED|OFFICE^Office visit^L|30|min|^^^20260719113000^20260719120000|||||12345^Careful^Clara NTE|1||Appointment was created on the wrong patient and removed from the schedule. PID|1||123456^^^CITYHOSP^MR||Smith^Jane^Anne^^Ms^^L||19800314|F RGS|1 AIS|1||CARDREV^Cardiology review^L|20260719113000|30|min AIL|1||CARD^ROOM2^^CITYHOSP|20260719113000|30|min

What systems do with it

The sender is the filler schedule. Receivers remove or mark the appointment as entered-in-error, depending on their audit model. The key action is different from cancellation: the appointment should not count as a patient cancellation, clinic cancellation, no-show, or completed visit.

Systems still need to identify the appointment through SCH. Optional patient and resource groups help with audit and reconciliation, but the appointment identifiers usually drive the delete action.

How to read the structure

S17 uses the SIU_S12 structure. MSH and SCH are required, and the resource group is required. Patient details may be present when the appointment was patient-specific, but some deletion workflows may send only enough data to identify the schedule item.

If your receiver keeps deleted appointments as audit records, define whether later messages can reference the same appointment identifiers. HL7 scheduling guidance warns that delete actions can have different consequences across applications.

Implementation traps

The biggest trap is treating S17 like S15. A cancellation is normal scheduling history. A deletion is correction of an erroneous schedule entry. If analytics, reminders, or billing treat them the same, reporting gets muddy.

Deletion can also be hard to undo. Some systems physically remove the record; others keep an audit row and reject reuse of the appointment ID. Agree on that behavior before sending delete events in production.

Reference notes

Caristix describes S17 as a deletion notification for an appointment that must be removed from the schedule. HL7 Chapter 10 scheduling emphasizes that delete differs from cancel because delete corrects an erroneous entry. iNTERFACEWARE lists S17 among the shared-format SIU notification events.