Medblocks vs Flexpa

Flexpa lets a patient connect their own records through a managed API, usually across payers and providers. It sits in the patient-access circle of the healthcare integration landscape, alongside other patient-access tools like b.well, Fasten Connect, Human API, and 1up Health.

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. Medblocks HL7v2 interfacing: supported over HTTP with SMART Backend authentication, which major EHRs like Epic support natively.
3. Flexpa clinical data models: you model it yourself with SQL on FHIR. Its ViewDefinitions are more limited than a tool like dbt: one table maps from one resource, while many clinical concepts span several (tumor size can be an Observation or a Condition).
4. Export to FHIR CDR (b.well, Flexpa, Fasten Connect, Metriport): they expose FHIR APIs to read the data, but you build the pipeline to push it into your own FHIR server.
5. Flexpa pricing: based on the Omni plan, which includes unlimited data retrievals and access to all connections.
6. Fasten Connect pricing: an annual platform fee, paid upfront ($12,000, or $18,000 with TEFCA enabled), plus a per-transaction fee. A transaction is each fetch of data from one organization, so a patient who connects 5 organizations and refreshes twice a day runs 10 transactions a day. Per-transaction rates start around $2 and fall as volume rises.

† 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 Flexpa does well

Flexpa is focused. It gives a patient a clean way to authorize access to their own records across payers and providers through a single managed API. If patient-mediated data is the whole job, that focus is a strength.

It handles the messy parts of patient authorization for you, so you do not build and maintain OAuth plumbing against every payer and provider yourself.

Where Medblocks goes further

Flexpa reaches data only when a patient connects it. The moment you need organizational, backend, or network access, you start over with a different tool. Medblocks covers patient access and the other three surfaces, so the same patient base extends into facility and organization-based integration as you grow.

The authorization flow is also theirs, not yours. Their branding on the consent screen adds drop-off. With Medblocks the flow runs under your brand.

And Medblocks normalizes. Flexpa returns FHIR for you to model and deliver yourself. Medblocks deduplicates records into one per person and normalizes every source into clinically vetted models, ready to query.

Pricing

Flexpa starts around $350,000 per year, roughly six times Medblocks’ flat $60,000 per year, and for a single surface rather than all four.

Using them together

You do not have to rip out Flexpa to start. If you already use it, pipe the patient-authorized data it returns into Medblocks, where it joins every other source into one normalized record. As you need organizational, backend, or network access, you add those surfaces in Medblocks without changing your patient flow.