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.
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.
For patient registration, the EHR system sends a notification when a patient's demographics are updated during an inpatient or outpatient visit.
To review technical specifications for this notification, refer to the Patient Registered schema.
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.
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.
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.