Redox

aid: redox
name: Redox
description: Redox is a healthcare data interoperability platform, founded in 2014 and headquartered in Madison, Wisconsin,
  that enables secure, real-time exchange of clinical and administrative data across the healthcare ecosystem. Through a single
  API and a network of 100+ EHR connections and 12,000+ connected healthcare organizations, Redox lets digital health vendors,
  providers, payers, EHRs, and life-sciences companies integrate once and reach the entire network. The platform offers a
  modern FHIR API, the legacy Redox Data Model (Redox Messages) event-based API, and a Platform API for managing organizations,
  sources, and destinations. Redox is HITRUST r2 and SOC 2 Type 2 certified and HIPAA, GDPR, and CCPA aligned, processing
  tens of billions of healthcare transactions annually.
url: https://raw.githubusercontent.com/api-evangelist/redox/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- battery-ventures
x-tier: stub
x-tier-reason: portfolio-lead
deliveryModel:
  model: saas
  license_evidence:
    not_product:
    - redoxengine/redox-hl7-v2
  open_source: unknown
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: low
  source:
  - pricing
  - repository-not-product
  generated: '2026-09-25'
  method: derived
accessModel:
  pricing: enterprise
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Enterprise
  confidence: high
  source:
  - plans
  - authentication
  - scopes
  - rate-limits
  - security
  - sandbox
  generated: '2026-11-02'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-08-14'
image: https://redoxengine.com/wp-content/uploads/2023/01/redox-logo.png
tags:
- Company
- Healthcare
- Interoperability
- FHIR
- Electronic Health Records
- Health Data
- Integration
- HL7
- Digital Health
- Healthcare API
tags_raw:
- Company
- Healthcare
- Interoperability
- FHIR
- EHR
- Health Data
- Integration
- HL7
- Digital Health
- Healthcare API
apis:
- name: Redox FHIR API
  description: Redox's modern FHIR API for exchanging clinical and administrative healthcare data across the Redox network
    using HL7 FHIR resources and notifications, authenticated with OAuth2.
  humanURL: https://docs.redoxengine.com/api-reference/fhir-api-reference/
  baseURL: https://api.redoxengine.com
  tags:
  - FHIR
  - Healthcare
  - Interoperability
  properties:
  - type: Documentation
    url: https://docs.redoxengine.com/api-reference/fhir-api-reference/
- name: Redox Data Model API
  description: Redox's legacy event-based Data Model API (Redox Messages) for exchanging structured healthcare data across
    the network via JSON message payloads.
  humanURL: https://docs.redoxengine.com/api-reference/data-model-api/
  baseURL: https://api.redoxengine.com
  tags:
  - Healthcare
  - Interoperability
  properties:
  - type: Documentation
    url: https://docs.redoxengine.com/api-reference/data-model-api/
- name: Redox Platform API
  description: The Redox Platform API for managing organizations, sources, destinations, and platform settings via user-level
    API keys.
  humanURL: https://docs.redoxengine.com/api-reference/platform-api/
  baseURL: https://api.redoxengine.com
  tags:
  - Healthcare
  - Platform
  properties:
  - type: Documentation
    url: https://docs.redoxengine.com/api-reference/platform-api/
  - type: MCPServer
    url: mcp/redox-mcp.yml
- aid: redox:redox-fhir-r4-api
  name: Redox FHIR R4 API
  tags:
  - FHIR
  - HL7
  - Healthcare
  - Notification
  - Patient Access
  - Query
  - R4
  - USCDI
  - Writebacks
  tags_raw:
  - FHIR
  - HL7
  - Healthcare
  - Notifications
  - Patient Access
  - Queries
  - R4
  - USCDI
  - Writebacks
  humanURL: https://docs.redoxengine.com/api-reference/fhir-api-reference/
  baseURL: https://api.redoxengine.com/fhir/R4/{destination-slug}/{environment-type}
  properties:
  - url: https://docs.redoxengine.com/api-reference/fhir-api-reference/
    type: Documentation
  - url: https://docs.redoxengine.com/api-reference/fhir-api-reference/
    type: APIReference
  - url: https://docs.redoxengine.com/api-reference/redox-data-model-api/authenticate-an-oauth-api-key/
    type: Authentication
  - url: https://docs.redoxengine.com/api-reference/error-handling-and-responses/
    type: ErrorCodes
  - url: https://docs.redoxengine.com/api-reference/quotas-and-constraints/
    type: RateLimits
  description: The Redox FHIR R4 API exposes HL7 FHIR R4 resources for healthcare data exchange between connected systems,
    supporting FHIR notifications, queries, and writeback messages over an OAuth 2.0-secured base URL templated per destination
    and environment (Development, Staging, Production). Resources align with USCDI requirements and let digital health vendors
    search, read, create, and update Patient, Practitioner, Observation, Condition, MedicationRequest, Encounter, DocumentReference,
    and other clinical resources against EHRs and networks connected through Redox.
- aid: redox:redox-hl7-v2-library
  name: Redox HL7 v2 Library
  tags:
  - HL7
  - HL7v2
  - JavaScript
  - Open Source
  - Parser
  tags_raw:
  - HL7
  - HL7v2
  - JavaScript
  - Open Source
  - Parser
  - Open-Source
  humanURL: https://github.com/RedoxEngine/redox-hl7-v2
  properties:
  - url: https://github.com/RedoxEngine/redox-hl7-v2
    type: GitHubRepository
  - url: https://github.com/RedoxEngine/redox-hl7-v2
    type: SDKs
  description: redox-hl7-v2 is Redox's open-source JavaScript library for parsing and generating HL7 v2 messages, useful for
    teams integrating with legacy hospital interfaces or building tools that bridge HL7v2 and JSON-based pipelines outside
    of the hosted Redox platform.
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: VulnerabilityDisclosure
  url: security/redox-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/redox-domain-security.yml
- type: DeveloperPortal
  url: https://docs.redoxengine.com/
- type: Documentation
  url: https://docs.redoxengine.com/
- type: APIReference
  url: https://docs.redoxengine.com/api-reference/
- type: GettingStarted
  url: https://docs.redoxengine.com/basics/
- type: Blog
  url: https://redoxengine.com/blog/
- type: GitHubOrganization
  url: https://github.com/RedoxEngine
- type: Pricing
  url: https://redoxengine.com/forms/pricing
- type: SignUp
  url: https://dashboard.redoxengine.com/#/signup/
- type: StatusPage
  url: https://status.redoxengine.com/
- type: TrustCenter
  url: https://redoxengine.com/platform-security/
- type: Security
  url: https://docs.redoxengine.com/security/responsible-disclosure
- type: Compliance
  url: https://redoxengine.com/platform-security/
- type: Authentication
  url: authentication/redox-authentication.yml
- type: OAuthScopes
  url: scopes/redox-scopes.yml
- type: WellKnown
  url: well-known/redox-well-known.yml
- type: Conformance
  url: conformance/redox-conformance.yml
- type: Lifecycle
  url: lifecycle/redox-lifecycle.yml
- type: Conventions
  url: conventions/redox-conventions.yml
- type: Packages
  url: packages/redox-packages.yml
- type: SDKs
  url: packages/redox-packages.yml
- type: LLMsTxt
  url: llms/redox-llms.txt
- type: MCPServer
  url: mcp/redox-mcp.yml
- type: RateLimits
  url: rate-limits/redox-rate-limits.yml
- type: ErrorCatalog
  url: errors/redox-problem-types.yml
- type: Sandbox
  url: sandbox/redox-sandbox.yml
- type: ChangeLog
  url: changelog/redox-changelog.yml
- type: Webhooks
  url: asyncapi/redox-webhooks.yml
- type: Plans
  url: plans/redox-plans-pricing.yml
- type: TermsOfService
  url: https://redoxengine.com/legal/terms-of-use/
- type: PrivacyPolicy
  url: https://redoxengine.com/legal/privacy-policy/
- type: DomainSecurity
  url: security/redox-domain-security.yml
- type: Website
  url: https://www.redoxengine.com
- type: DeveloperPortal
  url: https://developer.redoxengine.com
- type: Documentation
  url: https://docs.redoxengine.com
- type: GettingStarted
  url: https://docs.redoxengine.com/quickstart-for-redox/
- type: GettingStarted
  url: https://docs.redoxengine.com/basics/what-is-redox/
- type: Authentication
  url: https://docs.redoxengine.com/api-reference/redox-data-model-api/authenticate-an-oauth-api-key/
- type: Console
  url: https://dashboard.redoxengine.com
- type: Sandbox
  url: https://docs.redoxengine.com/quickstart-for-redox/
- type: Pricing
  url: https://www.redoxengine.com/contact/
- type: Signup
  url: https://www.redoxengine.com/contact/
- type: Support
  url: https://docs.redoxengine.com/troubleshooting/
- type: StatusPage
  url: https://status.redoxengine.com
- type: ChangeLog
  url: https://redoxengine.com/blog/category/changelog/
  note: Corrected 2026-08-14 — the previous docs.redoxengine.com/product-changelog/ URL 404s; the real dated changelog surface
    is this blog category (see changelog/redox-changelog.yml).
- type: Security
  url: https://docs.redoxengine.com/security/
- type: Compliance
  url: https://www.redoxengine.com/trust/
- type: Blog
  url: https://www.redoxengine.com/blog/
- type: Customers
  url: https://www.redoxengine.com/customers/
- type: Partners
  url: https://www.redoxengine.com/partners/
- type: LinkedIn
  url: https://www.linkedin.com/company/redox-inc-
- type: X
  url: https://x.com/RedoxEngine
- type: YouTube
  url: https://www.youtube.com/c/RedoxEngine
- type: Features
  data:
  - name: Healthcare Data Normalization
    description: Universal translation across HL7v2, CDA, X12, DICOM, and HL7 FHIR R4 so vendors write one integration and
      reach any connected EHR or network.
  - name: 100+ EHR Connections
    description: Pre-built connectivity to Epic, Oracle Health/Cerner, MEDITECH, Athenahealth, eClinicalWorks, NextGen, Allscripts/Veradigm,
      and dozens of other EHRs.
  - name: Clinical Network Onramps
    description: Integrated access to Carequality, CommonWell, TEFCA, DirectTrust, and other clinical exchange networks through
      a single Redox connection.
  - name: Patient Identity (EMPI)
    description: Redox EMPI powered by Verato links patient records across disparate sources to support longitudinal patient
      views and matching.
  - name: Cloud Connectivity
    description: Direct ingestion onramps into AWS, Microsoft Azure, Google Cloud, Databricks, and Snowflake for analytics,
      ML, and warehouse use cases.
  - name: Data Operations
    description: Filters (allow/block rules), translation sets (value mappings), and config modifiers let teams customize
      processing logic without code deploys.
  - name: Subscriptions and Orchestration
    description: Event subscriptions and conditional routing govern how and when data moves across the connected ecosystem.
  - name: Bulk and Real-Time Delivery
    description: Real-time message streaming plus bulk and batch delivery modes to fit both transactional and analytics workloads.
  - name: Environments and Promotions
    description: Development, staging, and production environments with promotion workflows for safe configuration rollout.
  - name: HITRUST and SOC 2
    description: HITRUST r2 certified on AWS and GCP and SOC 2 Type 2 compliant security posture across the platform.
- type: UseCases
  data:
  - name: Digital Health EHR Integration
    description: Digital health startups embed Redox to reach hospital and clinic EHRs without building one-off interfaces
      per customer.
  - name: Patient Access and Engagement
    description: Patient-facing apps pull longitudinal records over FHIR and write encounter data back to provider EHRs.
  - name: Care Coordination and Discharge
    description: Providers exchange ADT, discharge, and referral messages with downstream partners in real time.
  - name: Population Health and Registries
    description: Aggregate clinical data across networks for registry submission, public health reporting, and population
      analytics.
  - name: Payer Data Exchange
    description: Payers run prior authorization, HEDIS reporting, member data standardization, and care-gap workflows on top
      of Redox-mediated provider data.
  - name: Lab Order and Result Routing
    description: Labs and diagnostic vendors route orders and results bi-directionally across EHRs through standardized event
      types.
  - name: Medical Device Data Capture
    description: Device manufacturers stream telemetry and observations into EHR charts via the same integration surface.
  - name: EHR Migration and Conversion
    description: Health systems lift-and-shift between EHRs by replaying historical data through Redox during cutover.
  - name: Life Sciences Real-World Data
    description: Pharma and life sciences teams pull de-identified real-world data for clinical research and post-market surveillance.
  - name: Cloud Data Warehouse Hydration
    description: Hydrate Snowflake, Databricks, BigQuery, S3, and Azure data lakes with normalized clinical data for analytics
      and ML.
- type: Integrations
  data:
  - name: Epic
    description: Bi-directional connectivity to Epic EHR for clinical, ADT, scheduling, orders, and results workflows.
  - name: Oracle Health (Cerner)
    description: Connection to Oracle Health Millennium for FHIR, HL7v2, and Data Model traffic.
  - name: MEDITECH
    description: Integration with MEDITECH Expanse and MAGIC for ambulatory and acute care data exchange.
  - name: Athenahealth
    description: Connectivity to athenaOne for ambulatory and revenue-cycle workflows.
  - name: eClinicalWorks
    description: Integration with eClinicalWorks ambulatory EHR.
  - name: NextGen Healthcare
    description: Connection to NextGen ambulatory EHR.
  - name: Allscripts (Veradigm)
    description: Integration with Veradigm/Allscripts ambulatory and acute EHRs.
  - name: Carequality
    description: Onramp to the Carequality national interoperability framework for document and FHIR exchange.
  - name: CommonWell Health Alliance
    description: Onramp to the CommonWell network for cross-vendor patient record exchange.
  - name: TEFCA
    description: Connectivity to the Trusted Exchange Framework and Common Agreement (TEFCA) network.
  - name: DirectTrust
    description: Secure Direct messaging through the DirectTrust network.
  - name: Verato EMPI
    description: Redox EMPI powered by Verato for enterprise master patient indexing and identity resolution.
  - name: IMO
    description: IMO codeset normalization for diagnosis and procedure terminology.
  - name: AWS
    description: Direct cloud connectivity into Amazon Web Services accounts and AWS Marketplace listing.
  - name: Microsoft Azure
    description: Cloud connectivity into Microsoft Azure and Azure Marketplace listing.
  - name: Google Cloud
    description: Cloud connectivity into Google Cloud Platform and GCP Marketplace listing.
  - name: Snowflake
    description: Native onramp into Snowflake for clinical data warehousing.
  - name: Databricks
    description: Native onramp into Databricks for healthcare lakehouse and AI workloads.
- type: Solutions
  data:
  - name: Vendors
    description: Connect digital health products to providers and payers, integrate with EHR systems, and access clinical
      networks through a single API.
  - name: Providers
    description: Real-time data exchange for discharge coordination, infection risk detection, capacity management, registry
      submission, payer data exchange, lab order routing, and EHR migration.
  - name: Payers
    description: HEDIS reporting, member data standardization, care gap identification, and prior authorization workflows
      powered by provider-sourced clinical data.
  - name: EHRs
    description: EHR vendors expose modern API surfaces to their ecosystems through Redox-mediated integration tooling.
  - name: Life Sciences
    description: Real-world data acquisition, clinical trial recruitment, and post-market surveillance built on top of normalized
      healthcare data.
- type: DomainSecurity
  url: security/redox-domain-security.yml
x-enrichment:
  date: '2026-08-14'
  status: enriched
  artifacts_added: 8
  pass: local-v1