Author: Tom Jessessky

Queuing

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

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

Queries

To query Redox for data, such as in a PatientSearch or ClinicalSummary – PatientQuery, you should POST to https://api.redoxengine.com/query and include the parameters identifying the patient in the body of the request, as indicated in the data model documentation. You can see a

Messages & Transmissions

Messages are sent from your Source to an authorized Destination. Transmissions are received by your Destination from an authorized Source. For all intents and purposes: Messages are what you send to other members of the Redox Network. Transmissions are what receive from other members of

Receive a Transmission with Dev Tools

Now that you have configured a Destination on Redox, you are able to receive test messages using our Dev Tools. The Redox Dev Tools will send an example message showing what data will look like when received from a Source. When logged

Send a Message With Dev Tools

After you have set up your Source you are now ready to send a message! All requests to the Redox API are POST requests to endpoints that live under https://api.redoxengine.com/ To send data to Redox, POST to https://api.redoxengine.com/endpoint To query Redox for

Create a Source

In order to send data to another member of the Redox network, you will need to acquire an API Key and authenticate with us. We call this a Source record and it allows you to not only POST data to partners but

Create a Destination

Working with Redox’s EHR Integration API starts with setup of your connections in the Redox Dashboard. In order for your application to receive messages, you need to establish a URL to which Redox can POST. We call this a Destination record. Destinations

Data Models Explained

Overview The Redox Engine platform allows you to access and interact with a wide variety of healthcare-related data via a consistent, normalized, API. Our platform is based on a truly standardized format and uses HTTPS communication with JSON to allow you to

Sources and Destinations

On the Redox network, you can be a Destination, a Source, or both – it all depends on whether you’re are consuming or sending data, or both. Sources Sources initiate data pushes and requests. If you want to send data, or if