Redox
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.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Redox the way a machine reads it — 48 machine-readable artifacts across 4 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Redox scores 31.3/100 (thin), with a separate agent-readiness read of 10/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Redox
Each block below is one kind of artifact we hold for Redox. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 4
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Redox FHIR R4 API
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 a...
Redox Data Model API
The Redox Data Model API is Redox's proprietary JSON-based healthcare data exchange surface, organized around standardized event types (PatientAdmin, ClinicalSummary, PatientQue...
Redox Platform API
The Redox Platform API manages Redox organization configuration as code, exposing endpoint categories for access control, alerts, audit events, configs, config modifiers, creden...
Redox HL7 v2 Library
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...
Features 10
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Healthcare Data Normalization
Universal translation across HL7v2, CDA, X12, DICOM, and HL7 FHIR R4 so vendors write one integration and reach any connected EHR or network.
100+ EHR Connections
Pre-built connectivity to Epic, Oracle Health/Cerner, MEDITECH, Athenahealth, eClinicalWorks, NextGen, Allscripts/Veradigm, and dozens of other EHRs.
Clinical Network Onramps
Integrated access to Carequality, CommonWell, TEFCA, DirectTrust, and other clinical exchange networks through a single Redox connection.
Patient Identity (EMPI)
Redox EMPI powered by Verato links patient records across disparate sources to support longitudinal patient views and matching.
Cloud Connectivity
Direct ingestion onramps into AWS, Microsoft Azure, Google Cloud, Databricks, and Snowflake for analytics, ML, and warehouse use cases.
Data Operations
Filters (allow/block rules), translation sets (value mappings), and config modifiers let teams customize processing logic without code deploys.
Subscriptions and Orchestration
Event subscriptions and conditional routing govern how and when data moves across the connected ecosystem.
Bulk and Real-Time Delivery
Real-time message streaming plus bulk and batch delivery modes to fit both transactional and analytics workloads.
Environments and Promotions
Development, staging, and production environments with promotion workflows for safe configuration rollout.
HITRUST and SOC 2
HITRUST r2 certified on AWS and GCP and SOC 2 Type 2 compliant security posture across the platform.
Scroll within the panel for all 10 ·
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Use Cases 10
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Digital Health EHR Integration
Digital health startups embed Redox to reach hospital and clinic EHRs without building one-off interfaces per customer.
Patient Access and Engagement
Patient-facing apps pull longitudinal records over FHIR and write encounter data back to provider EHRs.
Care Coordination and Discharge
Providers exchange ADT, discharge, and referral messages with downstream partners in real time.
Population Health and Registries
Aggregate clinical data across networks for registry submission, public health reporting, and population analytics.
Payer Data Exchange
Payers run prior authorization, HEDIS reporting, member data standardization, and care-gap workflows on top of Redox-mediated provider data.
Lab Order and Result Routing
Labs and diagnostic vendors route orders and results bi-directionally across EHRs through standardized event types.
Medical Device Data Capture
Device manufacturers stream telemetry and observations into EHR charts via the same integration surface.
EHR Migration and Conversion
Health systems lift-and-shift between EHRs by replaying historical data through Redox during cutover.
Life Sciences Real-World Data
Pharma and life sciences teams pull de-identified real-world data for clinical research and post-market surveillance.
Cloud Data Warehouse Hydration
Hydrate Snowflake, Databricks, BigQuery, S3, and Azure data lakes with normalized clinical data for analytics and ML.
Scroll within the panel for all 10 ·
Integrations 18
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Epic
Bi-directional connectivity to Epic EHR for clinical, ADT, scheduling, orders, and results workflows.
Oracle Health (Cerner)
Connection to Oracle Health Millennium for FHIR, HL7v2, and Data Model traffic.
MEDITECH
Integration with MEDITECH Expanse and MAGIC for ambulatory and acute care data exchange.
Athenahealth
Connectivity to athenaOne for ambulatory and revenue-cycle workflows.
eClinicalWorks
Integration with eClinicalWorks ambulatory EHR.
NextGen Healthcare
Connection to NextGen ambulatory EHR.
Allscripts (Veradigm)
Integration with Veradigm/Allscripts ambulatory and acute EHRs.
Carequality
Onramp to the Carequality national interoperability framework for document and FHIR exchange.
CommonWell Health Alliance
Onramp to the CommonWell network for cross-vendor patient record exchange.
TEFCA
Connectivity to the Trusted Exchange Framework and Common Agreement (TEFCA) network.
DirectTrust
Secure Direct messaging through the DirectTrust network.
Verato EMPI
Redox EMPI powered by Verato for enterprise master patient indexing and identity resolution.
IMO
IMO codeset normalization for diagnosis and procedure terminology.
AWS
Direct cloud connectivity into Amazon Web Services accounts and AWS Marketplace listing.
Microsoft Azure
Cloud connectivity into Microsoft Azure and Azure Marketplace listing.
Google Cloud
Cloud connectivity into Google Cloud Platform and GCP Marketplace listing.
Snowflake
Native onramp into Snowflake for clinical data warehousing.
Databricks
Native onramp into Databricks for healthcare lakehouse and AI workloads.
Scroll within the panel for all 18 ·
Solutions 5
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
Vendors
Connect digital health products to providers and payers, integrate with EHR systems, and access clinical networks through a single API.
Providers
Real-time data exchange for discharge coordination, infection risk detection, capacity management, registry submission, payer data exchange, lab order routing, and EHR migration.
Payers
HEDIS reporting, member data standardization, care gap identification, and prior authorization workflows powered by provider-sourced clinical data.
EHRs
EHR vendors expose modern API surfaces to their ecosystems through Redox-mediated integration tooling.
Life Sciences
Real-world data acquisition, clinical trial recruitment, and post-market surveillance built on top of normalized healthcare data.
Resources
Every other property we hold for Redox — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 6
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 3
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/redox-engine · machine-readable index on apis.io