Listen for patient record updates

Listening for patient record updates is one of the most commonly used API actions. Typically, you can use this API action so that you are notified when any of these events occur within your connection’s EHR system:

  • A new patient is added.
  • An existing patient has updates for registration or demographic information.
  • An existing patient has either new insurance or updates to existing insurance. 
  • An existing patient checks in for a specific visit or registers for an outpatient visit.
  • An existing patient cancels an outpatient visit.

This API action is useful if you want to maintain a patient database for your own system—whether for the long-term or short-term—or if you need updates on patient insurance data. 

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 patient registration notifications (patient context)

The EHR system sends a notification for these scenarios:

  • A patient record is created.
  • A patient's demographics are updated.

In the patient context, these are events that occur independently of an encounter. You can opt in for patient registration notifications related to encounters by listening for hospital admission updates (specifically the patient registration action step for that action).

Listening for patient registration notifications is a combination of these two separate action steps:

  • Listen for new patient notifications
  • Listen for patient update notifications

Depending on the EHR system and what they support, you may use this combined patient registration action step or the two separate action steps to get the same data.

To review technical specifications for this notification, refer to the Patient Registered 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 new patient notifications

The EHR system sends a notification whenever a patient record is created. To review technical specifications for this notification, refer to the Patient Created schema.

This one step is also encompassed in Listening for patient registration notifications. Depending on the EHR system and what they support, you may need to use this independent action step instead of the combined patient registration action step to get the same data.

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 patient update notifications

The EHR system sends a notification whenever a patient's record is updated (e.g., a patient's phone number is updated to a new number). To review technical specifications for this notification, refer to the Patient Updated schema.

This one step is also encompassed in Listen for patient registration notifications. Depending on the EHR system and what they support, you may need to use this independent action step instead of the combined patient registration action step to get the same data.

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 patient merge notifications

The EHR system sends a notification whenever two patients records are merged. To review technical specifications for this notification, refer to the Patient Merged schema.

This one step is also encompassed in Listen for patient registration notifications. Depending on the EHR system and what they support, you may need to use this independent action step instead of the combined patient registration action step to get the same data.

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