# Supported methods and specifications

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

[Talk to a Redoxer](https://redoxengine.com/forms/contact-us/) about which methods fit 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 Hooks
- clinical networks ([see Network Onramps](/how-to-use-redox/interact-with-clinical-networks))
- cloud storage ([see supported cloud products](/basics/connecting-to-the-cloud-with-redox))
- DICOMweb
- Direct Secure Messaging
- FHIR services (Redox FHIR API, [FHIR Subscriptions](/basics/redox-fhir-api/supporting-fhir-subscriptions), FHIR normalizer, FHIR passthrough)
- HL7v2 over HTTPS
- HTTPS (REST, SOAP; HTTPS over VPN not supported)
- IHE XDR, PDQ, XCPD, XDS/XCA
- generic polling ([learn about polling](/basics/data-exchange-with-redox/using-polling-for-notifications))
- generic web services (XML wrapper)
- generic webhook
- MLLP
- 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 to the Data Model API or FHIR API format so your system can integrate with any other system.

> **System adapters for communication methods**
>
> We build a system adapter to support each type of communication method.
>
> Don’t see a communication method you need? [Learn about adding a new system adapter](/implementation-guide/add-a-new-system-adapter-to-redox).

> **Quotas and constraints**
>
> Different communication methods have different restrictions. [Review technical quotas and constraints](/api-reference/quotas-and-constraints) for data exchange, including message, file, and rate limits.

## Authentication

Redox supports multiple authentication schemes to authorize your system to Redox. [Learn more about authentication](/basics/data-exchange-with-redox/authenticating-and-sending-data-via-redox).

- 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 (SigV4)
- 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 proprietary and FHIR APIs from EHR and other systems. 

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](https://redoxengine.com/forms/contact-us/) to see what works for you.

- AdvancedMD
- AliveCor
- Altera Sunrise (formerly Allscripts Sunrise)
- Altera TouchWorks (formerly Allscripts TouchWorks)
- athenahealth (acquired Virence Health) 
- athenaIDX
- athena FHIR Subscription
- Azalea Health
- Brightree
- CareCloud
- CGM Aprima
- Charm EHR
- CMS ACCESS
- CollaborateMD
- Community Health Centers (CHC)
- DrChrono
- eClinicalWorks (eCW)
- Elation Health
- Envi Health Solutions
- Epic
- Ero Health (eCW)
- Flatiron Health
- Greenway Intergy
- Greenway PrimeSuite
- Healow
- HospiceMD
- IntakeQ
- Kipu
- Kno2
- Liberty Mutual
- MatrixCare
- Meditab
- ModMed
- NAATP
- Netsmart
- Nextech
- NextGen
- NikoHealth
- Oracle Health (formerly Cerner)
- PointClickCare
- Practice Fusion
- Salesforce
- Sigmund AURA
- Tebra (formerly Kareo)
- Therigy
- Veradigm EHR (formerly Allscripts Professional)
- Veradigm Practice Management (formerly Allscripts PM)
