Listen for scheduling updates

You may want to listen for scheduling updates if you want information about a patient appointment, like the type of visit, provider name, location, or date. Typically, you can use this API action so that you are notified when any of these events occur within your connection’s EHR system:

  • An outpatient appointment is created.
  • A scheduled outpatient appointment is modified, rescheduled, or canceled.

You can use this API action if your system does any pre-visit work, like sending a preparatory patient questionnaire, helping with patient check-in prior to the appointment, updating patients about appointment changes.

Supported systems

You can receive notifications like this with the Redox FHIR® API.

Your connection's system can push notifications with a polling or subscription type of system. 

Lightweight or detailed notification

Depending on your connection’s capabilities, you can opt in for lightweight or detailed notifications. 

Typically, a lightweight notification is a bare bones message that says “something is new” or “something has changed,” along with the relevant identifier (e.g, patient, visit #). Lightweight notifications generally trigger you to do something within your own workflow or to query for more information. 

On the other hand, a detailed notification means that you receive all the data about what’s new or what has changed. This might be useful if you need to persist all that data in your system to complete your own unique workflow.

Things you need to know

What's next?

Does this API action seem like a good fit for your unique workflow? If so, let your Redox rep know! You can begin development by downloading the relevant resource schema (which is noted in the relevant action step below), and deciding which data elements you need. Then head over to our Quickstart guide to dive right in.

If you're not engaged with our sales team yet, talk to a Redoxer to get started.

Action steps

Listen for booked appointment notifications

The EHR system sends a notification for each individual appointment that’s created. To review technical specifications for this notification, refer to the Scheduling Appointment Booked schema.

How to respond to FHIR notifications

Upon receiving this type of message, you only need to respond with the relevant HTTP status code. After that, you decide what your system should do with the notification.

Notification

Listen for modified appointment notifications

The EHR system sends a notification whenever an aspect of the appointment (other than the time) has changed from the original booking. To review technical specifications for this notification, refer to the Scheduling Appointment Updated schema.

How to respond to FHIR notifications

Upon receiving this type of message, you only need to respond with the relevant HTTP status code. After that, you decide what your system should do with the notification.

Notification

Listen for rescheduled appointment notifications

The EHR system sends a notification whenever a scheduled appointment time has changed from the originally booked time. To review technical specifications for this notification, refer to the Scheduling Appointment Updated schema.

How to respond to FHIR notifications

Upon receiving this type of message, you only need to respond with the relevant HTTP status code. After that, you decide what your system should do with the notification.

Notification

Listen for cancelled appointment notifications

The EHR system sends a notification for each appointment that is cancelled. No-shows are considered "cancelled" appointments as well. To review technical specifications for this notification, refer to the Scheduling Appointment Cancelled schema.

How to respond to FHIR notifications

Upon receiving this type of message, you only need to respond with the relevant HTTP status code. After that, you decide what your system should do with the notification.

Notification