We support a variety of communication methods, data formats, and authentication schemes to enable you to compose your own connectivity and interactions with nearly any data system in healthcare. Several of our customers choose the Data Model API as a single point of communication for all of their integrations. But check out the table below to see other popular options used by our customers:
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, all data payloads sent via Redox are converted with the Data Model API or FHIR® API so that your system can integrate with any other.
But let’s say 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 with you 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 integration, we have other tools that allow for a polling type of exchange. For example, we have services that can ask your integration, “What changed since I last called you last night?” Then, each poll for new data is processed into what-has-changed events that are delivered to your endpoints as if the EHR system we polled 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.