You may want to listen for encounter updates to follow up with patients after an outpatient visit.
This API action may be a good fit for your organization if you want to be notified about these events in 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.
After getting these notifications, you can query for more information or kick off your post-visit or general population health workflow, like these types of use cases:
- Send a customer survey.
- Provide post-appointment information.
- Offer patient services after an appointment.
Ultimately, this API action is useful if your organization cares that a patient showed up 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 patient that checks in for a hospital or outpatient visit. To review technical specifications for this notification, refer to the Patient Arrived schema.
This step is required if you're listening for outpatient encounters.
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.