Redox
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.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Redox the way a machine reads it — 57 machine-readable artifacts across 5 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 61.8/100 (strong), with a separate agent-readiness read of 29/100 (agent ready). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Redox's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/redox/"
title="Redox on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/redox.svg"
alt="Redox Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/redox/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/redox/"
title="Redox on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/redox/card.svg"
alt="Redox Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
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 5
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 API
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.
Redox Data Model API
Redox's legacy event-based Data Model API (Redox Messages) for exchanging structured healthcare data across the network via JSON message payloads.
Redox Platform API
The Redox Platform API for managing organizations, sources, destinations, and platform settings via user-level API keys.
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 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...
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
Redox MCP Server
Redox MCP server: an open, model-agnostic gateway for managing, configuring, monitoring, and automating a Redox organization (built on the Redox Platform API) via any MCP-compat...
MCP SERVERPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Redox Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Redox Rate Limits
RATE LIMITSFeatures 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 ·
Event Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Redox Webhooks
ASYNCAPISecurity Posture 4
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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
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 10
Portal, sign-up, and the first successful call
Scroll within the panel for all 10 ·
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 12
Authentication, authorization, and security posture
Scroll within the panel for all 12 ·
Learn 1
Tutorials, courses, talks, and written guidance
Operate 6
Status, limits, changes, and where to get help
Commercial 5
Pricing, plans, and the legal terms of use
Company 5
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 · machine-readable index on apis.io
This is an independent, third-party profile of Redox, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.