Our engine connects and enables communication between organizations across the world. With part of that communication containing information that’s linked to or dependent on time, it’s natural to wonder how we manage differences in time zones. This is something we had to…

One thing that sets the Redox API apart from APIs like HL7 FHIR is our ability to rapidly support newly emerging use cases and get them live in production quickly. As our data models evolve with new data points, our first focus…

After years of little regulation surrounding EHR data integration, a health system may send data to an integration partner using any number of methods, formats, and value sets. A big value our engine provides is standardizing the data we receive from EHR…

The Redox API makes ID management straightforward. Here’s a breakdown of a few different IDs you’ll be using and interacting with while using the Redox API. Source and Destination IDs Application developers can sometimes confuse the Source and Destination IDs of the…

Application Queuing Applications should have queuing infrastructure in place so that received messages are managed and stored appropriately. Redox won’t send subsequent messages to an application’s endpoint until a 200 success response has been received for the previous message; we recommend sending…

HTTP Status Codes: What They Mean and How We Use Them When using our API, you may sometimes run into HTTPS status codes. Since status codes are an important way our API communicates, we want to clearly document what HTTP status codes…