Redox API
Redox is a healthcare data interoperability platform that enables real-time exchange of clinical and administrative data across EHRs, providers, payers, and digital health systems through a single standardized API. An unofficial API lets you programmatically pull patients, encounters, appointments, clinical results, medications, and documents—and push updates like new orders, scheduling changes, and care-coordination events—across the EHRs and clinical networks Redox connects, including Carequality, TEFCA-CommonWell, FHIR, and Data Model surfaces.
What is Redox?
Redox is a healthcare data interoperability platform that enables real-time exchange of clinical and administrative data across EHRs, providers, payers, and digital health systems. Customers use Redox to connect to 100+ EHR systems through a single standardized API, normalizing data across both a proprietary JSON Data Model and a FHIR REST interface, and to reach clinical networks such as Carequality and TEFCA-CommonWell—powering thousands of live integrations across the healthcare ecosystem.
Core product areas include:
- Redox Platform (core data exchange and integration engine across EHR, provider, and payer systems)
- FHIR API (FHIR resources exposed through a REST interface for patients, scheduling, and clinical data)
- Data Model API (proprietary JSON data models for clinical, administrative, and scheduling exchange)
- Platform API (manage your Redox organization, sources, destinations, and configuration programmatically)
- Clinical network onramps (Carequality, TEFCA-CommonWell) for nationwide record retrieval
- Managed Services and Connected Solutions (implementation, support, and pre-built integrations)
Common data entities:
- Patients, Demographics, Encounters, Visits
- Appointments, Scheduling, Admissions, Discharges, Transfers (ADT)
- Clinical Results, Vitals, Lab Orders, Observations
- Medications, Orders, Patient Monitoring data
- Clinical Summaries, Transition of Care plans, Notes
- Documents, Attachments, and FHIR resources
The Redox Integration Challenge
Health systems and digital health vendors run mission-critical workflows through Redox, but turning connection- and configuration-driven exchange into API-driven automation is non-trivial:
- Connection-by-connection variability: Each EHR connection has its own configuration, supported data models, and field coverage—generic integrations break across destinations
- Dual API surfaces: The FHIR API and the proprietary Data Model API expose overlapping but distinct object shapes, IDs, and lifecycle semantics
- Partnership and onboarding gates: Access to live EHR connections and clinical network onramps (Carequality, TEFCA-CommonWell) requires organization setup, source/destination configuration, and approvals
- Authentication complexity: OAuth 2.0 with JWT-based assertions, key rotation, and legacy-to-new auth migrations complicate headless automation
- Webhook and async delivery: Much clinical data arrives as pushed messages to subscribed endpoints, requiring careful subscription, replay, and deduplication handling
- PHI and compliance: Clinical data exchange demands strict HIPAA handling, audit trails, and minimum-necessary scoping on every call
- Document and binary workflows: Clinical summaries, notes, and attachments need careful retrieval, format handling, and reconciliation back to the patient record
How Supergood Creates Redox APIs
Supergood reverse-engineers authenticated flows, the Redox FHIR API, the Data Model API, and webhook delivery to deliver a resilient API layer for your Redox organization—across every EHR connection and clinical network onramp you operate.
- Handles OAuth 2.0 and JWT-based authentication, key rotation, and legacy-to-new auth migrations securely
- Maintains session and token continuity with automated refresh and change detection
- Normalizes responses across the FHIR API and Data Model API so you integrate once and rely on consistent patient, encounter, result, and document objects
- Aligns with your connection-specific configuration, supported data models, and entitlements to ensure compliant, minimum-necessary access
Use Redox with AI agents: Redox MCP Server →
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your EHR connections, data models, and authentication model.
- Supergood Generates and Validates Your API
We deliver a production-ready Redox adapter tailored to your organization's connections and entitlements.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as Redox evolves.
API Endpoints
Authentication
/authenticateAuthenticate to a Redox organization using OAuth 2.0 with a JWT assertion and obtain an access token for downstream calls.
Patient Operations
/patientsSearch and retrieve patient demographics and identifiers across connected EHRs via the FHIR API or Data Model API.
Scheduling
/appointmentsList appointments and scheduling data, including admissions, discharges, and transfers, with filters for patient, provider, and date range.
Scheduling
/create_appointmentCreate or update a scheduling event against a connected destination using the configured data model.
Clinical
/encountersRetrieve encounters, clinical results, vitals, medications, and transition-of-care summaries for a patient.
Clinical
/submit_orderSubmit clinical or lab orders and patient-monitoring instructions to a connected EHR destination.
Use Cases
Sync patient and clinical data across EHR connections
- Pull patient demographics, encounters, and clinical results from connected EHRs into a single warehouse - Stream lab results, vitals, and medication data to downstream analytics and care-coordination tools - Reconcile patient identifiers across the FHIR API and Data Model API for a unified record
Automate scheduling and patient throughput workflows
- Pull appointments, admissions, discharges, and transfers to drive real-time throughput dashboards - Push scheduling updates and new appointments back to connected destinations without portal clicks - Trigger discharge-coordination and follow-up workflows from ADT events
Route documents and clinical summaries at scale
- Retrieve clinical summaries, notes, and document attachments for automated triage and routing - Normalize transition-of-care plans across connections for downstream registries and care teams - Submit structured data and AI outputs back into the EHR via the appropriate data model
Reach nationwide records through clinical networks
- Query Carequality and TEFCA-CommonWell onramps for patient records beyond direct connections - Normalize retrieved records into consistent patient, encounter, and result objects - Surface gaps and matched records to care-coordination and HEDIS reporting workflows
Technical Specifications
Authentication
OAuth 2.0 with JWT assertions, key rotation, and legacy-to-new auth migration handled in a managed session
Connectivity
Redox FHIR API, Data Model API, Platform API, and webhook delivery surfaced across your EHR connections
Response format
Normalized JSON across patient, encounter, result, medication, and document objects from both FHIR and Data Model surfaces
Rate limits
Adaptive throttling tuned to your organization and per-connection limits to avoid downstream EHR rejection
Session management
Automatic token refresh, JWT re-signing, and credential rotation
Data freshness
Near real-time pulls for patient, encounter, and result data plus webhook-driven push delivery, with optional scheduled batch syncs
Security
HIPAA-aligned controls, encrypted credential vault, scoped access tokens, minimum-necessary access, and audit logging
Webhooks
Subscription, replay, and deduplication for pushed clinical messages and ADT, result, and document events
Latency
Sub-second reads on cached entities; multi-second responses when querying clinical networks or posting orders
Throughput
Horizontally scaled workers sized to multi-connection clinical message volume
Reliability
Retry, backoff, and idempotency keys for order submission, scheduling, and document delivery
Adaptation
Continuous monitoring of Redox releases, data-model changes, and per-connection configuration drift
Frequently asked questions
Yes. Supergood normalizes data across both the Redox FHIR API and the proprietary Data Model API, so you integrate patient, encounter, result, and document entities once regardless of which surface a given connection uses.
No. Supergood works with your existing Redox organization, sources, and destinations. New connections are only required when you want to reach an EHR or network you have not yet onboarded.
Supergood manages OAuth 2.0 with JWT assertions, including key rotation and the migration from legacy API keys to the newer JWT-based authentication, so your automation stays connected without manual token handling.
Yes. Where your organization is provisioned for the clinical network onramps, Supergood queries Carequality and TEFCA-CommonWell and normalizes retrieved records into the same patient, encounter, and result objects as your direct connections.
Clinical data is exchanged under HIPAA-aligned controls with encrypted credentials, scoped tokens, minimum-necessary access, and full audit logging on every call.