πŸ”©Webhook Examples

Webhook Overview

{
  "payload": {
    "event": "live_queue_updated",
    "timestamp": "2024-01-17T00:35:22+08:00",
    "data": {
        "id": 19242,
        "appointment_id": null,
        "appointment_date": null,
        "appointment_time": null,
        "registered_client_id": 3734,
        "registered_client_name": "Saad",
        "registered_client_phone": "923093927454",
        "client_name": "Saad",
        "state": {
          "name": "ARRIVED",
          "value": 3
        },
        "state_name": "Arrived",
        "service_id": 220,
        "service_name": "Registration",
        "staff_id": 246,
        "staff_name": "Registration",
        "notes" : {
          "items": [],
          "escapeWhenCastingToString": false
        },
        "created_at": "2024-01-17T00:35:22+08:00",
        "updated_at": "2024-01-17T00:35:22+08:00"
      }
  },
  "signature": "e43bbd70a719bc9cd51be1122cc170d6ec43dd16918b163311be622a042bcd39"
}

1. Join Live Queue

The diagram depicts a healthcare queue system where a patient joins a live queue via Chup Online, which sends the queue data to the HIS backend for processing, followed by a response confirming the patient's status in the queue.

2. Appointment

The flow diagram shows a queue and appointment management where a patient books an appointment via 'Chup Online, which then sends the details to the HIS backend for processing. After processing, HIS sends a confirmation response back to Chup Online, with real-time appointment queue management implied.

3. Alert

The diagram shows a healthcare alert system where staff create an alert in Chup Online, which then sends this alert data to the HIS backend. HIS processes the alert, and a response is generated, likely to acknowledge the alert and possibly trigger further actions.

4. Serving

In the diagram, healthcare staff input a 'Serving' status into Chup Online, which then relays this status to the HIS backend through a webhook. The backend processes this information, and a response is issued, likely indicating that service is underway for a patient or client.

5. Served

The diagram depicts a workflow where healthcare staff mark a patient as 'Served' on the Chup Online system. This status update is then sent to the HIS backend through a webhook, which processes the served data. A response is then generated, completing the process and likely updating the patient's service status in the system.

6. No Show

The diagram describes a healthcare process where staff record a patient 'No Show' in Chup Online, which sends the Information to HIS backend for processing, leading to a system response.

No Show (Canceled by System)

No Show - Back To Live Queue (Patient Arrived From No Show)

7. Move

The diagram outlines a healthcare workflow where staff mark a patient as 'Moved' on Chup Online, which sends this status to the HIS backend for processing, after which a response is generated.

8. Cancel / Delete

The diagram displays a workflow for when a client or patient decides to cancel or leave a queue on the Chup Online system. Upon cancellation, Chup Online sends the cancel payload to the HIS backend through a webhook. The HIS backend then processes this cancellation data, and a response is generated to confirm the action.

9. Reschedule

The diagram illustrates a workflow where a patient reschedules an appointment using Chup Online, which then communicates the reschedule information to the HIS backend, triggering a system response.

10. Pharmacy (Received)

The diagram outlines a process where healthcare staff update the status of a patient to 'Received' in the Chup Online system, which then sends this update to the HIS backend. The HIS backend processes the receive data, leading to a generated response in the system.

11. Pharmacy (Dispense)

The diagram outlines a pharmacy workflow where staff mark a medication as dispensed in Chup Online, which sends the dispensary data to the HIS backend, leading to a response from the system.

12. Billing Mark as Paid

The diagram illustrates a healthcare billing workflow where staff mark a service as paid in Chup Online, which then transmits this billing information to the HIS backend. Upon processing, the HIS backend generates a response to confirm the payment status.

13. End Visit

The diagram shows a healthcare process where staff record an 'End Visit' status in Chup Online, which then sends this update to the HIS backend, resulting in a system response to conclude the visit.

Last updated

Was this helpful?