Table of Contents


The Scheduling data model is used for communicating information about a patient’s office or non-surgical appointments. EHR systems can send Scheduling messages to update your system with the appointment status, date/time, scheduled providers, and scheduled resources.

Every appointment gets assigned a visit number and patient ID. Any changes to the appointment are made with the relevant visit number. If the appointment is canceled and later rescheduled, however, a new visit number is created. Also keep in mind that Scheduling Holds and Blocks don’t have an associated patient ID.

EHR systems typically make scheduling information available through either a standard SIU HL7v2 feed or a proprietary API. SIU messages follow a push notification model while a proprietary API and web service rely on queries. You may also have the option to use data on demand if you prefer to query but your connection only supports push notifications for scheduling data. For example, if you primarily want information about a booked appointment, you can use the Booked event type to get the information you need with data on demand. Learn more about data on demand.

If you want information about surgical appointments, check out the SurgicalScheduling data model. Or if you’re looking for insurance information for appointments, check out the PatientAdmin data model instead.

The Scheduling data model has event types that are enabled for data on demand. Learn more about data on demand.