Data on Demand
Events that are Data on Demand enabled represent a universal query that can be used across any EHR, regardless of how the data is made available from their system. There are two general ways to incorporate the use of this feature into your integration workflow.
In-App Initiated Workflows
Actions taken in your product trigger a query to Redox and retrieve the data needed to move on to the next step. This data is always accessible via Redox and will be continually updated based on what we receive from the healthcare organization over time.
Example: A patient logs into your application and schedules a telehealth visit. You initiate a PatientSearch Query via Redox to determine if this is a known patient and to gather pertinent demographics and identifiers. You display the information for the patient to review and they complete their appointment. When the patient initiates another visit next month, you can use the same flow to collect and display their information.
EHR Initiated Workflows
If you need to be notified at the point that an event occurs in a healthcare organization’s source system, Redox can send the event notification to your organization’s Destination immediately when we receive it. Upon receipt or at any point in the future, you can trigger a Data on Demand query from their Source to collect additional data. Redox will send the event notification immediately allowing you to kick off your workflow. This can include querying for additional data via Redox or sending information back to the healthcare organization. Any Redox data model event enabled with Data on Demand can consistently be used as a query across any EHR. This data is always accessible via Redox and will be continually updated based on what we receive from the healthcare organization over time. If the event you want to use is not yet enabled for Data on Demand, please reach out here to let us know.
Example: You have a product that allows community physicians to request specialty referrals. The physician opens your product and locates the patient they want to place a referral for. PatientSearch query is initiated to identify if the patient has been seen at the healthcare organization the physician is referring them to and to return demographics. The physician places the referral and your product uses either a scheduled or end-user initiated Booked query to track the fulfillment of the referral.