Supported methods and specifications

Last updated: Sep 11, 2025
PRODUCT OWNER
HEALTH TECH VENDOR
IMPLEMENTATION

There are lots of pieces to data exchange. This article outlines protocols, methods, and systems Redox supports.

Talk to a Redoxer if you want to talk through different methods for your integration.

Data formats

Redox supports multiple data formats, which define how data is structured and organized. You can use one or a combination of these data formats, depending on your unique workflow needs:

  • binary (e.g., PDF, PNG)
  • C-CDA
  • CSV
  • DICOM
  • FHIR®
  • HL7v2
  • JSON
  • multipart form data
  • URL-encoded form data
  • X12
  • XML

Communication methods

Redox supports multiple communication methods, which define how data is transmitted and delivered.

  • CDS service
  • clinical networks (see Network Onramps)
  • DICOMweb
  • FHIR® services (Redox FHIR® API, FHIR® Subscription, FHIR® normalizer, FHIR® passthrough)
  • HL7v2 over HTTPS
  • HTTPS (REST, SOAP)
  • IHE XDR, PDQ, XCPD, XDS/XCA
  • MLLP
  • generic polling (learn about polling)
  • generic web services (XML wrapper)
  • generic webhook
  • Public Health Information Network Messaging System (PHINMS)
  • Redox Data Model API
  • SAML (SSO data model)
  • SFTP, SFTP polling
  • SMART on FHIR®

Regardless of 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.

Authentication

Redox supports multiple authentication schemes to authorize your system to Redox. Learn more about authentication.

  • legacy API keys
  • OAuth API keys (OAuth 2.0)
  • SFTP username and password
  • VPN

We also support these authentication schemes to authorize Redox to your partner:

  • API key
  • AWS Signature Version 4 (AwsSigv4)
  • Basic auth
  • Basic with client certificate
  • Google Workload Identity Federation (WIF)
  • JWT Bearer
  • mutual TLS
  • OAuth 2.0 2-legged
  • OAuth 2.0 2-legged with JWT Bearer for GCP
  • SMART Backend
  • Three-legged OAuth
  • TLS client certificate

EHR and other system APIs

Redox connects to various EHR or other system APIs, both proprietary and FHIR® APIs.

We’ve connected with several of these APIs, but the scope and support might vary. In other words, we may support some workflows but not others—yet. Talk to a Redoxer to see what works for you.

  • AdvancedMD
  • AliveCor
  • Altera Sunrise (formerly Allscripts Sunrise)
  • Altera Touchworks (formerly Allscripts Touchworks)
  • athenaHealth
  • athenaIDX
  • Azalea Health
  • Brightree
  • CareCloud
  • Cerner
  • CGM Aprima
  • Charm EHR
  • Community Health Centers (CHC)
  • CollaborateMD
  • DrChrono
  • eClinicalWorks (eCW)
  • Elation Health
  • Envi Health Solutions
  • Epic
  • Ero Health (eCW)
  • Flatiron Health
  • Greenway Intergy
  • Greenway PrimeSuite
  • Healow
  • HospiceMD
  • IntakeQ
  • Kipu
  • Liberty Mutual
  • MatrixCare
  • Meditab
  • ModMed
  • Netsmart
  • NextGen
  • Nextech
  • NikoHealth
  • PointClickCare
  • Practice Fusion
  • Salesforce
  • Sigmund AURA
  • Tebra (formerly Kareo)
  • Veradigm EHR (Allscripts Professional)
  • Veradigm Practice Management (formerly Allscripts PM)
  • Virence Health