One common issue we hear across our customers is that they are spending an immense amount of engineering time on infrastructure support to be able to ingest, store, maintain, and recall data they’ve received during the right points in their workflow – upwards of 30%. This time is solely spent on integration infrastructure work to meet requirements for handling and storing healthcare data and to address the significant differences in how information is retrieved from different healthcare data sources, most often EHRs. This is all time that is taken away from critical work needed to make great products.
Redox introduced our Data on Demand feature as an additional way to lighten the integration load. This feature turns HL7 feeds into reusable queries to stop the firehose of data that comes with most push-based integrations. When using on-demand data, you will be able to query the Redox provided API endpoints across any EHR or healthcare data source (such as an HIE). This allows you to confidently design query-based integration workflows that don’t require ongoing customization to accommodate differences across different EHR vendors and healthcare organizations.
Please note that this is currently only enabled for certain data model events, which are specified in our API documentation.
How is Data on Demand used?
End-User Initiated Workflows
End users begin their workflow in your product and, upon reaching a specified point, trigger a query via Redox to retrieve the data needed to move on to the next step.
Event Initiated Workflows
Data on Demand queries can be initiated after an event that occurs within your product or upon notification of en event that happened within the EHR or source system.
Scheduled or Timed Processes
Data on Demand queries can also be scheduled within your application to occur at specified times, such as daily, or after a certain amount of time has passed after a specific event occurs within your product or the EHR source system.
Push-based integrations (HL7, XML, C-CDA via XDR)
About 50% of the projects we do involve some sort of push-based integration, typically HL7. In this type of integration, there is a specified event within the EHR that results in the generation and transmission of a message to another application. Redox will ingest and persist the event-based data that is pushed out of the healthcare organization’s system and provide an appropriate query for you to see the data that you need at the appropriate time in your workflow. This allows us to create a true API experience so that you can always use queries to retrieve the information you need for Redox events that are enabled for Data on Demand.
The Firehose of Information
For many of our customers, the information generated at the moment the event occurs in the EHR is important, but is not actually used for product workflows until a later time. They are forced to figure out how to ingest, persist, and recall the data when they need it. We call this the firehose of information. Depending on how specialized your product or workflow is, this information can become complicated to handle very quickly.
For example, if your product relies on knowing when patients have scheduled appointments, you will need to receive scheduling information. However, if you don’t take action on that scheduled appointment until a later time, such as when the patient requests to see their schedule, when they check in for an appointment, or to collect information after the appointment has occurred, receiving a scheduling feed can get very noisy. Appointments in healthcare can be made anywhere from hours to months in advance and it’s quite common for them to be changed, cancelled, and rescheduled frequently due to either the provider or the patient. If you’re receiving a scheduling feed, you will need to receive the initial appointment, manage logic around updates or changes made to the appointment, and have a mechanism to be able to recall the appropriate appointment details during the right time in your workflow. At large healthcare systems, you can expect to receive hundreds or thousands of scheduling messages every day.
Using Redox’s Data on Demand feature, we handle the ingestion and organization of the data allowing you to build a query workflow to recall the data that you need at the appropriate point in your product’s workflow. This reduces your overhead of managing the volume of messages and logic needed to update the information allowing you to focus on getting the data that you want, when you want it without any of the fuss in between.
What if I want it right away?
Many of our customers have workflows that rely on receiving immediate notification when a certain action occurs in the EHR. In these situations, your integration will be configured to send the data along at the point we receive it to allow you to kick off any additional workflow steps for your product or team. If you need to recall the same data later, you can simply query the Redox API for the information you need.
Query-based integrations (vendor APIs, FHIR, C-CDA via XCA)
While this feature was designed to turn HL7-based integrations into query-based integrations, we recognize the lack of consistency across vendor APIs that can result in a frustrating experience for software developers that need to interact with data across any number of EHR vendors.
If you’re interested in improving this experience, we are actively looking for more input from software vendors on how Redox can help. Reach out and let us know about your use case.
Under the Hood
Redox Data on Demand is enabled by 4 key Redox features:
- A multi-tenant, FHIR-conformant data storage architecture with an automated scaling infrastructure – We scale your infrastructure needs up and down based on your usage without charging incremental fees or requiring your team’s time.
- Pre-existing and customized business logic to ensure consistent data handling across healthcare organizations – Redox works with your partners to determine how their system makes the information you need available. Let our experts handle the scoping, set-up, and testing to make sure you’re getting the data you need when you need it.
- Pre-built queryable API endpoints – We handle the connection to your partners and translate the output into the same Redox data models every time. No need to spend time doing custom mapping of data or creating and maintaining queryable endpoints. We’ve got you covered.
- Industry leading security practices – Redox combines industry-certifications with technology best practices to drive our robust security program. We are proud that both our HITRUST and SOC2 Type 2 certifications have no findings or CAPs.
Using Data on Demand Enabled Events
For more information about how to decide when to use Data on Demand, check out our API docs.
Currently enabled Redox events allow you to:
Find the patient you’re looking for
Use the PatientSearch data model to query for the right patient. Redox provides queryable architecture that ensures you will always be able to verify that you’ve got the right patient.
Query for upcoming appointments
Increase scheduling efficiency by querying for Booked appointments at the point you need to know when the patient is being seen.