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; or
  • 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 event notifications for this API action with the Redox FHIR® API.

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

Special considerations

Listening for some updates 

Keep in mind that this API action comprises a handful of separate steps. You don’t have to sign up for every patient record update if it’s not pertinent to your workflow. For example, you may not need new patient updates if you’re only interested in insurance updates for existing patients or if you’re only maintaining a patient database for the short-term. 

Listening for all updates

Conversely, if you do want every patient update, you must combine all the steps; in other words, one step won’t get you all of the patient updates. You must process all record updates if you want to maintain the most accurate representation of the current state of a patient. 

Each of the steps in this action are triggered by an event within the EHR system. Those trigger points are configured in your connection’s system. But you can filter these incoming data payloads if you don’t want a particular set of patient updates. Learn more about filters.

Insurance data

Since a patient can have multiple types of insurance, there may be a prioritization of which insurance to bill first, or which one applies to a given visit. If you want to distinguish insurance priority, talk to a Redoxer about your options.

Merging patient records

Currently, you're not able to merge records with our FHIR® API. But stay tuned for this.

When it is supported, we recommend that you merge patient records in your system if you’re maintaining any kind of patient database. If you’re only receiving ad hoc notifications, then a patient merge may not be critical to your workflow.

If you opt in for patient merge updates, you receive a notification when multiple records are merged for a patient. The notification includes the old patient identifiers and the new combined identifier that the EHR system plans to use for that patient going forward. Then, you decide what your system does upon receiving the notification of a patient merge.

Action steps

Listen for patient registration notifications (patient context)

How to respond to event notifications

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

The EHR system sends an event notification whenever:

  • a patient record is created; or
  • 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 steps:

  • Listen for new patient notifications, and
  • 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.

Event notification

Listen for new patient notifications

How to respond to event notifications

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

The EHR system sends an event notification whenever a patient record is created.

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.

Event notification

Listen for patient update notifications

How to respond to event notifications

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

The EHR system sends an event notification whenever a patient's record is updated (e.g., a patient's phone number is updated to a new number).

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.

Event notification