Data on demand

Data on demand, a capability that allows you to request your connection's data “on demand” from Redox, offers:

  • Multi-tenant, FHIR®-conformant data storage architecture with an automated scaling infrastructure. We scale your infrastructure based on your usage without charging incremental fees or requiring your team’s time.
  • Customized business logic to ensure consistent data handling. We work with your connection to determine how they make their data available. We handle the scoping, setup, and testing to make sure you get the data you need when you need it.
  • Pre-built queryable endpoints. We handle the integration to your connection and translate the output into the same Redox format every time. No need for you to do custom data mapping or creating and maintaining queryable endpoints.
  • Industry-leading security practices. We combine industry certifications with technology best practices to drive our robust security program.

Why data on demand

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.

When to use data on demand

  • An integrated system only supports push (event-based) exchange;
  • You don't want to store all the data that would come from a push-based exchange; or
  • You only want to receive data when you need it (upon request).

Check out this diagram for the types of messages and data exchange you can do with data on demand:

Messaging types
Messaging types

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?

Supported API actions

Data on demand isn't available for all API actions. Check out what we support for the Redox FHIR® API and the Redox Data Model API with data on demand.

How to get data on demand for your system

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.

Things you need to know

Now that you're sold on data on demand, let's drill down into some specifics.