
TL;DR: Hubble gives your product a patient's medical records through a single API. Your user verifies their identity once, and we assemble their records from across the providers they've seen and return them for your AI agent to use. Where APIs are not sufficient, we keep going with AI (browser and voice agents). Every request runs on the patient's individual right of access.
The problem
If you're building something that needs a patient's records, there's no clean way to get them. A patient's history is scattered across every provider they've ever seen, and each system is its own island. Most APIs returns the patient-portal subset rather than the full record, and coverage is inconsistent because every health system sets up its integration differently. So most teams either build per-provider integrations for months, fall back to faxes and manual portal logins, or push the problem back onto the patient by asking them to track down their own records or remember a login they set up years ago and have long since lost.
What Hubble does
Your user verifies their identity once, and we go get their records so you don't have to.
About the team
We're the team behind the AI agents at Grow Therapy and Amazon's One Medical, used by millions of patients. Prabha was Grow's first PM building and scaling their AI agents. Aaron built the AI infrastructure at One Medical serving 1M+ clients. (Fun fact: we've known each other for over a decade.)
Our ask
Sign up at hubble.ai