You may want to listen for encounter updates if you want to follow up with patients after an outpatient visit. 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 patient arrived for a scheduled outpatient appointment.
- A patient arrived for a telehealth appointment and is waiting for a provider.
- A patient arrived for a walk-in outpatient appointment.
You can use this API action if your system does any post-visit work, like sending a customer survey, providing post-appointment information, or offering services after an appointment. Or you may want to use this if you’re tracking general population health. The main purpose is if your system cares that a patient arrived for a visit or that there’s updated clinical information after a patient visit.
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.
The EHR system sends a notification for each individual patient that checks in for a hospital or outpatient visit. To review technical specifications for this notification, refer to the Patient Arrived schema.
If you're listening for outpatient encounters, this step is required.
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.