Questions and Answers > Understanding the Redox Scheduling Data Model
Questions and Answers

Understanding the Redox Scheduling Data Model

When do I need to use the Scheduling Data Model?

Applications use the Scheduling Data Model to communicate information surrounding a patient’s appointments. At certain events in the normal scheduling process (scheduling, rescheduling, arrival/check-in, check-out), EHRs will send scheduling messages to keep the appointment status, date/time, scheduled providers, and scheduled resources in sync with third party applications. 

If your primary use case is to identify information about a booked appointment, you will use the Scheduling – Booked event to pull the data that you need using the Data on Demand feature.

If you want to know when a patient has a scheduled office or non-surgical appointment, you’ll use the Scheduling data model to either receive updates pushed updates or request a schedule via query.  

To receive OR case information, see the SurgicalScheduling Data Model.

When are the queries supported? When is a webhook supported?

EHRs typically make scheduling information available through either a standard SIU HL7v2 feed or through APIs. SIU messages will naturally follow a push model while APIs and web services will typically be queries. Pushed SIU messages can be transformed into a query using the Data on Demand feature. For applications that prefer push notifications of scheduling data, Redox can use polling for API-based integrations to push data to an application’s endpoint when it’s received.  

Can I get insurance information on the scheduling HL7 feed?

Insurance details are most reliably available through the PatientAdmin Data Models.

What is the difference between a visit/case number and an encounter number?

You may hear these two terms used during conversations with the health system. The importance of each really will depend on your workflow and your goals for tracking data. A visit/case number represents a single, specific appointment or surgical case. An encounter number can represent a single appointment but is more often used to bundle together a set of appointments related to a single event. In the case of a surgery, a patient’s pre-op evaluation, surgical case, and post-op visit could all have the same encounter number but different visit numbers. Some EHRs prefer the encounter number for them to be able to file information in a specific place in the patient charts.

Cool – visit number sounds like what I need.  Will the appointment always have the same visit number if it’s been rescheduled?

This depends on the EHR workflow for handling appointment rescheduling. If the EHR uses a true reschedule workflow, it usually retains the old visit number. If the EHR uses a cancel/new workflow where the old appointment is cancelled and then a new one is made, the visit number may change.

Will I always see a New message the first time an appointment is sent to my application?

For an SIU HL7-based scheduling integration, the New message occurs at the time the appointment is scheduled. If the appointment is scheduled prior to your go-live date or prior to the start date of the backfill you received, the first time you learn of it may be when a Modification (such as an update to scheduling notes or a check-in event) occurs. Applications typically address this by adjusting their code to evaluate based on whether or not the Visit.VisitNumber value is new to your product in addition to the event received.