Alternative integration methods

We support multiple communication methods, data formats, and authentication schemes for you to compose your own connectivity with nearly any healthcare data system. Several of our customers choose either the Redox Data Model API or Redox FHIR® API as a single point of communication. But here are other common options:

Communication methods
Data formats
Authentication
HTTPS (REST, SOAP)
MLLP
SFTP
Direct Secure Messaging
JSON
FHIR®
XML
HL7v2
X12
CSV
PDF
VPN
Basic auth
Bearer auth (OAuth2.0)

All of the formats listed above use the event types for data models appropriate to the integrated system. Regardless of the method and format, Redox converts all data payloads with the Data Model API or FHIR® API so that your system can integrate with any other.

What if you want to integrate with a proprietary EHR system or device manufacturer API that doesn’t “speak” any of the popular options listed above? We can still help! Thankfully, our “vocabulary” extends to less popular methods, data formats, or authentication schemes, so we can discuss other options if you need them.

Also, if the whole I-send-you-requests and you-send-me-requests doesn’t make sense for you and your connection, we support a polling type of exchange. For example, we have services that can ask your integration, “What changed since I last called you last night?” Each poll for data is processed into what-has-changed events that are delivered to your destination(s) as if the EHR system sent the update themselves. Neat, huh?

Talk to a Redoxer if you want to talk through different methods for your integration, or if you need support for an existing alternative integration.