When do I need to use the Order Data Model?
Applications use the Redox Order data model to transmit a request for services or from an EHR. The Order Data Model is the message conveying the electronic entry of medical practitioner instructions for the treatment of patients. EHRs generally send an order when the a physician places the order. They may also send the order when a user releases it (after ordering, a user takes action on a worklist of pending orders to say “it’s time to do this”).
Lab orders are a common workflow involving the Order Data Model. In this case, when a physician places an order for a glucose test, for instance, the EHR sends a message with an expected date and time. When a nurse doing lab rounds (inpatient) or at a collection center (outpatient) collects the specimen, the EHR might send Order.Update with additional information about the collection, such as collection user or collection date/time.
When and where can the Order Data Model be found?
Almost anywhere! Physicians place all sorts of orders, ranging from specialty diagnostic tests like EEGs, cardiac echos, or X-Rays, to more administrative functions, such as discharge orders or referral orders. It is a fairly standard feed for EHRs to have set up and that we would expect it to be available to license if not already active at the healthcare organizations you are considering as partners. Typically EHRs will make this data available via an HL7v2 ORM interface or a vendor-specific API.
What are Order-specific questions?
Order specific or Ask at Order Entry (AOE) questions are information that a provider must provide to give additional clinical context. For instance, certain lab tests require race and whether the patient has eaten recently to know the appropriate reference range for results (i.e. an Asian who ate this morning might have a different reference range than an African American who did not eat).
How is the Order Data Model different from the Medications data model?
The Medications data model is in some ways a sort of order, in that physicians place orders for medications (prescriptions). However, Redox offers the Medications Data Model separately because a prescription has standard data elements that aren’t found in other types of orders, such as medication frequency, dose, and route.
The main event as an outcome of most orders that Redox customers are looking for is diagnostic test completion and physician interpretation (using the Results Data Model). For Medications, outpatient dispense/usage or inpatient dispense/administration are the relevant outcomes (also using the Medications Data Model).
How is the Order Data Model different from the Referral Data Model?
An Order can be thought of as a request for Referral when it pertains to specialty care. When a healthcare organization receives an order for a referral, it creates a referral record. The appropriate administrative staff then work these records in terms of getting approval from insurance, scheduling, etc. These concepts can vary per EHR. Redox will help you determine the best path forward as you move through your implementations.