Other Integration Methods

We built the Redox JSON API to offer a consistent and modern interface for exchanging health data. Most Redox customers integrate with the Redox JSON API so that they have a single point of integration that works for all of their connections to disparate systems, regardless of how those systems communicate and interoperate.

As such, there are many other means of connecting a source or destination system to Redox. Specifically, Redox supports a vast array of communication methods, data formats, and authentication schemes that enable connectivity for nearly any data system in healthcare, including:

  • Communication Methods: HTTPS (REST, SOAP), MLLP, SFTP
  • Data Formats: JSON, XML, HL7v2, X12, CSV, PDF, FHIR
  • Authentication: VPN, Basic Auth, Bearer auth (Oauth)

Additionally, we have further tools and functionality that allow for scheduled updates and connectivity to proprietary EHR and device manufacturer APIs.

Universal Data Language

All integration methods are set up to utilize Redox Data Models & Event Types appropriate for the connected system. Further, all traffic sent via Redox is converted into Redox JSON such that anysystem integrated to the Redox platform can communicate with any other.

Non-standard Integrations

Setting up integrations that do not utilize the Redox JSON API will require support from the Redox implementation team.

 

See Resources & Support for more information on how to reach out.