A medical records retrieval API that keeps going past the networks

Send a patient one link. Hubble verifies their identity, retrieves their records across EHRs and payers, and returns them to your app through one API.

How the Hubble API works

Patient-authorized retrieval, built on the HIPAA right of access, so there is no per-provider contract and it works on day one.

1. The patient authorizes

Your app sends a co-brandable link. The patient verifies their identity to NIST IAL2 and authorizes once, with consent they can revoke.

2. Hubble retrieves

EHRs reached directly and through HIE networks, payers for claims and coverage, and voice and browser agents for the providers those miss.

3. Your app receives

Webhooks as records arrive, delivered as raw PDFs or structured FHIR, each field traced to its source.

Common questions.

What is a medical records retrieval API?+

An API that lets an application request a patient's medical records and receive them programmatically, instead of staff requesting records by phone, fax, or portal. Hubble's API runs on patient authorization and returns records across EHRs and payers.

Which systems does the Hubble API reach?+

EHRs, reached directly and through HIE networks, including Epic, Oracle Health (Cerner), and athenahealth, and payers such as UnitedHealthcare and Aetna for claims and coverage. Voice and browser agents reach providers outside those networks.

What format are records returned in?+

Raw PDFs or structured FHIR, each traced to the source it came from.

How do we know when records arrive?+

Webhooks fire as records come in, so your app can update status without polling.

How do we try it?+

Start in the free sandbox with test data, then book a demo to scope production access.

See Hubble on your use case in 20 minutes.

Bring a real scenario and we will walk through how we would retrieve the records.