aid: redox-engine url: https://raw.githubusercontent.com/api-evangelist/redox-engine/refs/heads/main/apis.yml name: Redox tags: - Bulk Data - CDA - Carequality - CommonWell - DICOM - Data Model API - Digital Health - EHR - EMPI - Electronic Health Records - FHIR - HL7 - HL7v2 - Healthcare - Healthcare Interoperability - Integration Platform - OAuth 2.0 - Patient Data - Payers - Platform API - Providers - R4 - SMART on FHIR - TEFCA - X12 type: Index image: https://kinlane-productions.s3.amazonaws.com/apis-json/apis-json-logo.jpg access: 3rd-Party created: '2026-05-25' modified: '2026-05-25' position: Consumer specificationVersion: '0.19' description: Redox is a healthcare interoperability platform that lets digital health vendors, providers, and payers send, receive, process, and act on healthcare data at scale. Redox sits between digital health applications and the broader healthcare ecosystem, normalizing data across HL7v2, CDA, X12, DICOM, and HL7 FHIR R4, with 100+ EHR connections (Epic, Oracle Health/Cerner, MEDITECH, Athenahealth, eClinicalWorks, NextGen, Allscripts/Veradigm, etc.) and onramps into clinical networks like Carequality, CommonWell, TEFCA, and DirectTrust. Redox exposes three primary APIs — the FHIR R4 API for standards-based exchange, the Redox Data Model API for the platform's proprietary JSON event types (PatientAdmin, ClinicalSummary, Orders, Results, Scheduling, Notes, Media, PatientSearch, Provider, etc.), and the Platform API for managing organizations, sources, destinations, subscriptions, environments, credentials, filters, translation sets, and OAuth API keys. Authentication is OAuth 2.0 (machine-to-machine) for FHIR and Data Model traffic and user-level API keys for the Platform API. The platform is HITRUST r2 certified and SOC 2 Type 2 compliant, processes 20B+ healthcare transactions a year across 12,200+ connected organizations, and offers cloud connectivity onramps into AWS, Azure, GCP, Databricks, and Snowflake. apis: - aid: redox-engine:redox-fhir-r4-api name: Redox FHIR R4 API tags: - 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: Errors - 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-engine:redox-data-model-api name: Redox Data Model API tags: - Clinical Data - Data Model - Healthcare - JSON - Notifications - Orders - Queries - Results - Scheduling humanURL: https://docs.redoxengine.com/api-reference/redox-data-model-api/ baseURL: https://api.redoxengine.com/endpoint properties: - url: https://docs.redoxengine.com/api-reference/redox-data-model-api/ type: Documentation - url: https://docs.redoxengine.com/api-reference/redox-data-model-api/ 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: Errors - url: https://docs.redoxengine.com/api-reference/quotas-and-constraints/ type: RateLimits description: The Redox Data Model API is Redox's proprietary JSON-based healthcare data exchange surface, organized around standardized event types (PatientAdmin, ClinicalSummary, PatientQuery, VisitQuery, DocumentQuery, DocumentGet, Media, Notes, Orders, PatientSearch, Provider, Results, Scheduling, Booked, Financial, Inventory, Referral, SurgicalScheduling, etc.). Connections send notifications, receive notifications (push or poll), query for data on demand, and write data back, while Redox handles translation across HL7v2, CDA, X12, DICOM, and FHIR at the boundary. The platform publishes per-field reliability ratings (Reliable >90%, Probable >50%, Possible <50%) and offers downloadable JSON Schema v4 and TypeScript definitions from the Redox dashboard. - aid: redox-engine:redox-platform-api name: Redox Platform API tags: - Audit Events - Configuration - Connections - Destinations - Environments - Filters - Management - Sources - Subscriptions - Translation Sets humanURL: https://docs.redoxengine.com/api-reference/platform-api/ baseURL: https://api.redoxengine.com/platform properties: - url: https://docs.redoxengine.com/api-reference/platform-api/ type: Documentation - url: https://docs.redoxengine.com/api-reference/platform-api/ type: APIReference - url: https://docs.redoxengine.com/api-reference/platform-api/authenticate-a-user-level-api-key/ type: Authentication - url: https://docs.redoxengine.com/api-reference/error-handling-and-responses/ type: Errors - url: https://docs.redoxengine.com/api-reference/quotas-and-constraints/ type: RateLimits description: The Redox Platform API manages Redox organization configuration as code, exposing endpoint categories for access control, alerts, audit events, configs, config modifiers, credentials, destinations, environments, filters, logs, OAuth API keys, promotions, sources, subscriptions, translation sets, and VPNs. Requests authenticate with user-level API keys issued from the Redox dashboard, and responses use a wrapper envelope with `meta` and `payload` (single `record` or plural `records`) fields, supporting GitOps-style management of integration topology across development, staging, and production environments. - aid: redox-engine:redox-hl7-v2-library name: Redox HL7 v2 Library tags: - HL7 - HL7v2 - JavaScript - Open Source - Parser 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: SDK 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. common: - type: Website url: https://www.redoxengine.com - type: DeveloperPortal url: https://developer.redoxengine.com - type: Documentation url: https://docs.redoxengine.com - type: APIReference url: https://docs.redoxengine.com/api-reference/ - type: Quickstart 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://docs.redoxengine.com/product-changelog/ - 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: GitHubOrganization url: https://github.com/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. maintainers: - FN: Kin Lane email: kin@apievangelist.com