Order webhook events
Based on the status present inOrder Lifecycle,
Junction will trigger two kinds of webhook events, labtest.order.created and
labtest.order.updated.
The labtest.order.created event is triggered when an order is created in the system,
having the ordered status, and all subsequent status changes will trigger a labtest.order.updated event in the system.
The
partial_results status does not trigger a Webhook unless specifically requested from Junction.completed status:
Walk-in Order Updated
Appointment webhook events
Based on the status present inOrder and Appointment Lifecycle - Appointment Lifecycle,
Junction will trigger the labtest.appointment.updated webhook event.
If the ability to schedule appointments before a requisition has been created is enabled for your team, and you intend to send patient communications for appointment updates, use the
labtest.appointment.updated event. See more on communications for this feature here.If Arizona Scheduling is enabled for your team, subscribe to
labtest.appointment.updated for Sonora Quest appointment status changes. The Order and Appointment lifecycles are
managed separately for this flow, and the Order status updates for appointment_pending and appointment_scheduled
are emitted only after Sonora Quest confirms the appointment. An endpoint subscribed only to labtest.order.* will
not receive Appointment status changes such as scheduled or cancelled.scheduled status, after a reschedule has happened:
Walk-in Appointment Updated
The
event_data field contains relevant information regarding the current appointment status, and may be specific for each provider.