Important Note:
Since your healthcare organization is the source of the data, Kyruus Health recommends that the SIU traffic being sent to us be filtered such that we only receive SIUs for the relevant provider population being surfaced in Kyruus Connect for Providers. While you are welcome to use parameters that make the most sense for your system, we have historically seen healthcare organizations use provider identifiers in combination with practice locations to achieve the desired SIU traffic to be sent outbound to Kyruus Connect.
Supported Trigger Events:
| Trigger Event | SIU |
| Booking a New Appointment | S12 |
| Rescheduling an Existing Appointment | S13 |
| Modifying an Existing Appointment | S14 |
| Canceling an Appointment | S15 |
| No-Shows for an Existing Appointment | S26 |
Kyruus Health does not support SIU messages that represent actions (e.g. — front desk check-in, room transfer, etc.)
Additionally, Kyruus Health does not need any patient information (typically the PID segment) sent in the SIU transaction since we do not store any patient data and therefore, do not need ADT messages.
Below, you will find specification files for your reference. Note that one is specifically for healthcare organizations utilizing Cerner Millennium, while the other is for all other EHRs.