Appointment Scheduling – SIU^S12

The Message

A real SIU^S12 message, as shipped with ZiKiT’s built-in examples (line breaks added for readability – the actual HL7 file uses segment terminators):

MSH|^~\&|ATHENANET|99999^MA - athenahealth Testing^1^Test Clinic|TestInterface||201505181411||SIU^S12|185M90009|T|2.3.1
SCH|33910|33910||||RWMA-FOLLOWUP|Test Appointment|POSTHOSP^FOLLOWUP|15|minutes|^^^201505191300|||||username|||||||||BOOKED
PID|105613|105613|105613|105613|LASTNAME^FIRSTNAME^MIDDLENAME^SUFFIX||19880601|M|PREFERREDNAME|2028-9^Asian|ADDRESS^CITY^STATE^ZIPCODE^COUNTRY|US|(111)111-1111|(333)333-3333|EN|Married|||345789456|DL00001
PV1|||2^TEST DEPARTMENT^^TEST DEPARTMENT||3535464564||1022^HARPER^JOHN^MD|1022^HARPER^JOHN^MD|||||||||0052^JILL^ANDERSON^MD||33910
AIG|33910|requested_procedure_description|resource^providername|||||201505191300|||15|minutes
AIL|33910||TEST DEPARTMENT|OT||201505191300|||15|minutes

How ZiKiT Handles It

1. Open the built-in inbound mapping rule for SIU^S12 in ZiKiT Mapper.
2. Run an inbound test against the sample message – the built-in databases (SQLite by default, or MS SQL Server / MySQL) already have the required tables.
3. ZiKiT parses the SCH, PID, PV1, AIG, and AIL segments and writes the appointment into MESSAGES, N_PATIENT, SERVICE_REQUEST, REQUESTED_PROCEDURE, and SCHED_PROC_STEP – the same tables the DICOM Modality Worklist Server reads from, so the scheduled procedure is immediately available to modalities querying the worklist.
4. For a live test, start the ZiKiT Runtime Service and send the message with ZiKiTSender – the same path a real scheduling feed would take.

Try It Yourself

This example ships with every ZiKiT evaluation copy – open the mapping, run the test, and see exactly which fields land in which tables before you touch a production interface.