This data model allows for easy patient selection, application scheduling, and check-in workflows by providing an up-to-date list of patients being seen in any given hospital or clinic. Redox does this by listening to a health systems scheduling feed and posting to your endpoint whenever an appointment is made, canceled, or no-showed. If your app uses a scheduling workflow, Redox will alert the EHR of appointments made in-app to ensure a cohesive, integrated schedule. It’s important to note that this model is not query based; rather, it is designed to infer open times by listening to a provider’s schedule using either an HL7 scheduling feed or web-based services. If a health system uses an HL7 scheduling feed, we would recommend they designate slots for your application. If they use the Provider Schedule web service, Redox can also query using Available Slots to populate theschedule in your application
Functionality: Read and/or Write
Type: Event Based
Key Information Included:
- Patient Identifiers (such as MRN)
- Patient Demographics
- Provider location and information
- Visit Information: date, time, and reason
In the clinic or outpatient setting, the Scheduling data model is commonly used to generate a list of patients in the application that can easily be selected by a user, or to facilitate check-in workflows for a patient.
In the hospital or inpatient setting, the Scheduling data model is less common, as some EHRs have the capability to handle inpatient scheduling workflows for ancillary services such as physical therapy, diagnostic testing, or imaging. If the health system’s EHR has a scheduling feed for the patients, this could be used to populate a patient’s daily schedule.
Subscribe for updates
Never miss an important Redox Changelog announcement. Sign up to have new posts emailed directly to your inbox.