Data on demand, a capability that allows you to request your connection's data “on demand” from Redox, offers:
Data on demand may be useful if your connection's system doesn't support query-based (or synchronous) exchanges, but they're still willing to provide data with a push-based (or asynchronous) method.
Using a push-based method may mean that there's a high volume of incoming messages that you may not need until tomorrow (or even next month). But you still must build, implement, and maintain the necessary business logic to parse and store all the data.
We can already hear you saying: but wait, what if I don't want all that data?? Don't worry, that's why we offer data on demand.
With data on demand, the integrated system pushes data to Redox, which we ingest and organize for you. Then, you can query for specific data only when you need it. This allows you to focus on getting the data you want, when you want it, without the overhead in between.
Check out this diagram for the types of messages and data exchange you can do with data on demand:
So, when we set up data on demand for you, the EHR system's event-based messages actually look like queries on your end. Essentially, an EHR system's event-based message goes to a Redox data on demand instance, which you can query directly whenever you need to. Bonus: there's no difference in how you send a query to a data on demand instance versus to an EHR system directly. Mind-blowing, right?
If data on demand seems like a good fit for your organization, talk to a Redoxer (or your Redox rep) about configuring this for your system.
Now that you're sold on data on demand, let's drill down into some specifics.
When you query data on demand, the returned results are based on exact matching. This means that all fields must match your search criteria exactly.
For example, let’s say you search for a patient with demographics. You provide a name, birthdate, gender, and phone number for the patient. The EHR locates a patient with the same name, birthdate, and gender, but there’s a different phone number listed. Based on exact matching, no results would be returned.
As you can imagine, this can get dicey if patients have different phone numbers, email addresses, or nicknames throughout different systems. Or, if different systems use nonidentical formats for any of these fields—for example, 555-555-0000 instead of (555) 555-0000 for a phone number—then they still won’t match.
Exact matching may still return multiple matches. This can happen if:
If you use data on demand for any patient admission, discharge, or transfer (ADT) data, you likely need a backfill of data prior to going live. Learn about backfilling.
No matter the backfilling option you use, your connection's system continues to push patient ADT data to Redox after going live, so that it's available to you via data on demand.