Data on demand is a Redox repository that ingests and stores data from systems that only support asynchronous, push-based data exchange. This allows you to perform synchronous queries to retrieve specific data when you need it, avoiding the overhead of processing and storing a high volume of unnecessary messages.
In other words, you can request your connection’s data “on demand” with these benefits:
- 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 find out how they provide data. 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. This means you don’t have to do custom data mapping or create and maintain queryable endpoints.
- Industry-leading security practices. We combine industry certifications with technology best practices to drive our robust security program.
Let’s say your connection doesn’t support synchronous queries, but they’re willing to provide data asynchronously with a push-based method.
A push-based method can mean a high volume of incoming data in your system. Data you might not need until tomorrow—or even next month. You would have to build, implement, and maintain the necessary business logic to parse and store all the data.
With data on demand, your connection can push data to Redox, which we ingest and organize for you. Then, you can query for specific data only when you need it. That way, you can focus on getting the data you want, when you want it, without the overhead.
- Your connection only supports push (event-based) exchange.
- You don’t want to store all the data that would come from a push-based exchange.
- You only want to receive data when you need it (upon request).
- You want to test your API workflows before go-live.
Check out this diagram for the types of messages and data exchange you can do with data on demand:
When we set up data on demand for you, your connection’s event-based messages look like queries on your end. Essentially, your connection’s event-based message goes to a Redox data on demand repository, which you can query directly whenever you need to. Bonus: There’s no difference in how you query data on demand versus your connection.
You can also use data on demand to test your workflows.
If data on demand seems like a good fit, talk to a Redoxer about configuring this for your system.
If you use data on demand for patient admission, discharge, or transfer (ADT) data, you likely need a backfill of data before going live. Learn about backfilling.
No matter the backfilling option you use, your connection’s system continues pushing patient ADT data to Redox after go-live. This ensures data is available to you via data on demand.
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. Learn more about performing a patient search with data on demand.
Per our data retention policy, Redox stores protected health information (PHI) you exchange via data on demand for the duration of your contract. If you end your contract for any reason, data is purged within 30 days of your account closure.
Review our data retention policy for more details about how and why we store data.