MajwareMAJWARE
SIU
^S17
Scheduling2 required / 2 optional segments

SIU^S17Notification of Appointment Deletion

SIU^S17 instructs downstream systems to delete an appointment record entirely. It is a data correction event used when an appointment was created in error and needs to be completely removed from the receiving system's database, not just cancelled.

When Is This Sent?

When an appointment is deleted from the scheduling system due to a data entry error or system correction — the appointment should never have existed. This is distinct from cancellation, which preserves the cancelled record for auditing.

Real-World Usage

SIU^S17 is rarely used in routine scheduling but is important for interface maintenance and data cleanup. It typically originates from an IT administrator correcting erroneous appointment records. Most downstream systems handle S17 by marking the appointment as deleted or removing it from active views. Confirm with the RIS vendor whether S17 triggers a physical deletion or a logical soft-delete.

Message Structure

Segment names link to their field-level reference pages.

#SegmentPurpose in this messageReqRepeat
1MSHMessage header with SIU^S17 in MSH.9R
2SCHAppointment identification — minimal payload with just the appointment ID to deleteR
3PIDPatient demographics (for confirmation/logging)O
4NTEReason for deletionOYes

Example Message

Realistic example with fake patient data. Paste into the HL7 Message Viewer to explore interactively.

HL7 v2.x Message
1MSH||^~\&|EPIC_SCHED|HOSPITAL_A|MIRTH_PROD|RIS|20260315090000||SIU^S17^SIU_S17|SCH00025|P|2.5.1
2SCH||APT20260314ERR^EPIC_SCHED

Troubleshooting Scenarios

SIU^S17 received but appointment still visible in downstream system

Cause

The downstream system does not implement S17 deletion logic — it may only process S12, S13, S14.

Fix

Check downstream system's SIU event support list. If S17 is unsupported, use S13 (cancel) as the equivalent. Contact the vendor about S17 support or use an admin tool to manually remove the erroneous record.

S17 deletes appointment but associated DICOM studies are orphaned

Cause

Deleting an appointment in the RIS via S17 did not trigger removal of the associated worklist entry or DICOM study link.

Fix

Verify the RIS S17 handler also removes MWL entries and unlinks associated DICOM studies. For DICOM studies that were already acquired, manual retraction via PACS admin may be required.

Common Confusions

SIU^S17 (Delete) vs SIU^S13 (Cancel). Cancellation preserves the appointment record with a cancelled status — useful for audit trails. Deletion removes the record entirely. Use S13 for routine patient-requested cancellations; use S17 only for erroneous records that should not have been created. Most scheduling interfaces only implement S12/S13/S14.

Related Message Types

Segment Reference

Paste this message into our viewer

Interactive HL7 parser. Decodes every field, validates structure, highlights errors. Free, no signup.

Open HL7 Message Viewer →

Need mapping templates?

The HL7 Integration Toolkit includes field mapping worksheets and interface spec templates for every major HL7 message type including SIU^S17.

View HL7 Integration Toolkit →
← Back to HL7 Message Types Reference