What is Redox?

Redox allows you to connect with healthcare organizations, EHR systems, medical device manufacturers, health tech companies, or payers, to name a few. With Redox, you can compose data and services to fit the healthcare business needs of your organization. Explore Redox connections, which include 5,800 possible organizations that you can work with.

Once you configure your own setup with Redox, you can use the same code to integrate with multiple connections. And regardless of connectivity requirements, Redox helps you exchange healthcare data via our HITRUST-certified platform. See a technical overview of Redox.

To make integration work, Redox normalizes data between systems. Normalizing means changing how data is represented, or mapped, into a consistent schema. Check out our API reference to see what data we normalize.

However, there may also be a need to translate either values or data standards. Learn about translation sets or review FHIR® translation options.

Normalization and translation are just the start. Explore data exchange basics for more.

No matter where you operate in healthcare, we help you complete your unique workflow.

• Redox for Vendors: Integrate smarter to deliver more product value, faster. Connect to EHR systems, clinical networks, payers, cloud repositories, and other digital tools in a fraction of the time and effort it takes for DIY integrations. See why to use Redox for Vendors.
• Redox for Providers: Exchange real-time data with your connections so you can take immediate action and improve health outcomes. See why to use Redox for Providers.
• Redox for Payers: Access your members’ critical data to reveal where value comes from and where to go from there. See why to use Redox for Payers.

You may also find these popular features helpful:

• Network Onramps: Integrate with clinical networks like the Carequality Interoperability Framework. Learn about Network Onramps.
• Cloud connectivity: Connect with cloud providers like GCP, AWS, and Microsoft Azure. Learn about cloud connectivity.
• Redox EMPI powered by Verato: We partnered with Verato to provide a single source of truth for patient identity so you know who is who. You can link patient identity records within and across multiple disparate data sources for better decision-making, operational efficiency, and an improved user experience. Learn how to match patients.

  Beta feature: Support for Verato's Active Search

  We also support using Verato's Active Search with your Redox implementation. To do this, we support synchronous responses of MLLP HL7v2 (i.e., PDQ or PIX) requests. It goes a little like this:

  1. Redox receives an incoming HL7v2 message and converts the message to our data model format.
  2. Redox delivers the message to the designated destination.
  3. The destination returns results.
  4. Redox processes and returns the synchronous response. However, Redox can only process responses from one destination at a time.

  Talk with your Verato rep to learn more.

Once you establish your setup with Redox, you can use one of our APIs to integrate with your connections. You can use one or a combination of these:

• Redox Data Model API: Use JSON data models and corresponding event types to communicate with your integrations. Learn about the Data Model API.
• Redox FHIR® API: Use FHIR® resources and corresponding interactions or operations to communicate with your integrations. Learn about the FHIR® API.
• Redox Platform API: Use the Platform API to automate or perform actions within your Redox platform. Learn about the Platform API.

Or, review alternative integrations if you’re looking for other options.

No matter your integration method, you may find customized data operations useful. Check out filters or learn about translations.

Regardless of your integration type, we offer an interactive UI to configure, troubleshoot, and understand the health of your integrations. We call this the Redox dashboard.

You must create a Redox account to log in to the Redox dashboard. Learn how to use the dashboard.

As a heads up, the dashboard times out after 15 minutes of inactivity, whether you use single sign-on (SSO) or not. We implemented this timeout to meet HITRUST standards, which include specific requirements for timeout mechanisms. You must re-authenticate your session any time your session times out or is closed.

So your company has security guidelines—so do we! Review our security and compliance practices.

You may also be interested in how we handle these basic security measures:

• Rate limiting
• Allow-listing for Redox

Or, you may want to limit access to assets within your Redox organization. Learn how to control access in your organization.