Redox API
Redox publishes open docs for two REST surfaces: a proprietary Data Model API and a FHIR R4 API with OAuth 2.0 and webhooks. The sandbox is free and self-serve, but production means a paid Platform plus per-connection contract and hospital-side certification.
Frequently asked questions
Redox scores D+ on Supergood's API Report Card. Redox publishes open docs for two REST surfaces: a proprietary Data Model API and a FHIR R4 API with OAuth 2.0 and webhooks. The sandbox is free and self-serve, but production means a paid Platform plus per-connection contract and hospital-side certification.
Without a usable official API, teams fall back on manual exports, file drops, or one-off vendor integrations. The other option is an unofficial API layer like Supergood that automates the authenticated web app directly. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
Redox is a healthcare data interoperability and integration platform that gives digital health vendors, providers, and payers a single API to send and receive clinical and administrative data across 100+ EHRs and other healthcare endpoints.
Vertical: Healthcare (interoperability middleware sitting between EHRs and downstream apps). A digital health vendor's engineering team integrates once against Redox's Data Model or FHIR API and ships a single connector.
Redox publicly claims 12,200+ connected healthcare organizations, 14,900+ live integrations, and 20B+ transactions in the trailing 12 months, with 99.95% uptime.
Yes, by design. Redox is the live wire carrying PHI between digital health vendors and the hospital systems of record.
Founded in 2014 in Madison, Wisconsin by Luke Bonney, Niko Skievaski, and James Lloyd, all former Epic employees who saw firsthand how painful point-to-point HL7 integrations were for third-party apps trying to plug into Epic.
Production usage requires a paid Platform + Connection contract, sandbox is free, but every live hospital connection is a metered line item that recurs annually. Adding fields or message types not already modeled in the Redox Data Model requires Redox engineering / professional services rather than being self-serve. Full sourced list under Sources below.
Common alternatives include Health Gorilla, Particle Health, 1upHealth, Zus Health, Datica (now part of Rhapsody), Rhapsody (Lyniate). Graded alternatives appear under "More from the report card" below.
Supergood's grades measure one thing: can a customer's engineering team get their own data out programmatically? Supergood checks six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and rolls them into a letter grade. Supergood re-verifies grades, and they only move on evidence.
Yes, via a managed API layer. Supergood builds REST APIs and MCP servers for authenticated enterprise web apps, so AI agents and internal tools can read and write data programmatically. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
Redox scores GOOD on MCP availability. Redox publishes an official hosted MCP server at api.redoxengine.com/mcp, documented in its developer docs with connection instructions for common AI clients. It covers managing, configuring, and monitoring a Redox integration environment, and organizations must opt in to enable it.
Yes. Redox publishes an official MCP server, so MCP clients like Claude, Cursor, and Codex can connect to it directly. Setup instructions are in the vendor's documentation.