Medblocks vs Redox

Redox connects your app to EHRs and has spent years building and maintaining those connections so you do not have to. It sits in the EHR-integration circle of the healthcare integration landscape, alongside other EHR integrators like Vim, Willow, HealthJump, Leyr, Keragon, and TietAI.

Side by side

✓ native · ~ partial · ✗ not supported

1. Medblocks brokered access: we provide extensive written guidance and one-to-one support on contracting with an organization and getting your own credentials installed. We don't do it on your behalf with our credentials.
2. Redox brokered access: Redox can broker new organization connections, a months-long setup you pay for. The connection is then shared across Redox customers, not exclusive to you, and you lose access if you leave.
3. Medblocks HL7v2 interfacing: supported over HTTP with SMART Backend authentication, which major EHRs like Epic support natively.
4. Redox treatment-use HIE: network access exchanges C-CDA documents (patient and visit summaries), not discrete FHIR. Redox's translated JSON includes only the required C-CDA sections; optional data stays in the raw XML.

† Approximate estimate based on multiple sources and industry interviews. Not publicly disclosed by the vendor.

See the full capability matrix for every row and the sources behind each rating.

What Redox does well

Redox specializes in backend connectivity, the server-to-server link between your app and a provider’s EHR. Within that slice it is excellent, with years of maintained integrations across many systems.

It also reaches proprietary surfaces that standards do not. Where an EHR exposes write or workflow features only through its own non-standard interfaces, Redox has built and maintained that access. For deep write-back into a single health system, that depth is real and hard to replicate.

Where Medblocks goes further

Redox owns the backend surface. Medblocks spans all four: patient access, clinician workflow, backend, and network. If you later need patient-mediated records, wearables, payer data, or broader network exchange, you do not start over with a different tool.

We connect on your own credentials, not a broker’s. Redox can broker access to organizations it does not already reach, but that setup is a months-long process you pay for, the connection is shared across Redox customers, and you lose it if you leave. With Medblocks you hold the direct relationship with each organization and are never locked in.

The honest gap is proprietary write-back. The standardized APIs we build on now read about as well as the proprietary ones, and write support is growing, but for the deepest proprietary write into a single EHR, Redox is still ahead.

Pricing

Redox pricing is not public. Based on multiple public sources and industry interviews, it starts around $600,000 per year, roughly ten times Medblocks’ flat $60,000 per year. Organization connections that Redox brokers add a months-long setup you fund on top of that.

Using them together

You do not have to choose one or the other. A common setup is Medblocks for the patient-access APIs, network exchange, and the data normalization layer, with Redox for organization-based access and the deep proprietary write integrations it does best.

Copy the data Redox returns into Medblocks through its APIs, and it deduplicates and normalizes that alongside every other source into one record across surfaces. You keep Redox where its depth matters, and Medblocks gives you the single patient record and the surfaces Redox does not reach.