Launched this week
Hubble
Retrieve medical records other APIs can't
321 followers
Retrieve medical records other APIs can't
321 followers
Medical records still live behind fax lines, phone trees, and portal logins nobody remembers. A patient verifies their identity once, and Hubble assembles their records from across their providers and returns them through one API, for your AI agent to use.
Hubble
Hey Product Hunt 👋
I'm Prabha, one of the founders of Hubble.
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 seen, and each system is its own island. Most APIs return the patient-portal subset rather than the full record, so teams either build per-provider integrations for months, fall back to faxes and manual portal logins, or push the problem onto the patient.
Hubble is the layer that goes and gets the rest. Your user verifies their identity once, and we assemble their records from across their providers and return them through one API. We connect into EHRs and HIEs where they work, and when an API comes back empty we keep going with browser agents that submit the request through provider portals and voice agents that call records departments on the patient's behalf. Every request runs on the patient's individual right of access, they review every source, and they can revoke at any time.
We're the team behind the AI agents at Grow Therapy and Amazon's One Medical, used by millions of patients. We kept hitting this wall ourselves, so we built the layer that gets past it.
Would love your feedback, especially from anyone who has fought with records retrieval before. I'll be here in the comments all day.
(PH exclusive: 7 days free. Reach out and mention this post, or email me at prabha@hubble.ai and I'll get you set up.)
@prabhadublish Great framing on the launch, giving patients control to review sources and revoke access makes compliance conversations way easier for dev teams,qq like when a voice agent calls a clinic, does it use dynamic caller ID matching the patient's area code?
Hubble
@vikramp7470 Great question! This is something that we're actively exploring. Fundamentally our goal is to drive conversion of record retrieval via our voice agents and we believe localizing the numbers will help increase the odds that we retrieve records.
@prabhadublish Really interesting approach to making patient record access much easier, all the best🙌
Hubble
@vikramp7470 Appreciate the interesting question!
GIPHY
@prabhadublish @aaronleon thx for making this. Sounds like it could be really powerful for builders. Curious about its application for caregivers. I’m a caregiver for my partner, building a a medical “bible” of sorts across notion and Dropbox of every visit, surgery, consult, rx, test, procedure etc…. Once Hubble locates and compiles a patients full record history and normalizes it, is it downloadable as readable files (PDF’s etc)?
Hubble
@aaronleon @adamcl yes! we totally agree re: value to builders. our core belief is not just retrieving the data but making it easy to understand. We allow for PDF downloads!
GIPHY
@aaronleon @prabhadublish great! Thanks for the quick answer.
Hubble
@aaronleon @adamcl love what you are building! let us know if we can support at all.
GIPHY
@aaronleon @prabhadublish I will prob test the product on myself first before pointing at my Partners’s records. Better to see how it goes on me before trying to make Hubble compile decades of records.
By the way, Hubble works regardless of what US states you received care in? Assuming so if it’s compatible with epic, Athena, etc
Hubble
Aaron here, co-founder of Hubble. The reason we built this: AI is going to transform healthcare. I launched Amazon One Medical's first production AI agent and found that the key limiting factor was context. Getting a patient's history meant tons of broken integrations with upstream systems like EHRs and payers. Prabha and I realized everyone (even ourselves!) was rebuilding the same broken pipe, every time. Hubble is that context layer built once for all builders who need access to patient records across domains (care delivery, insurance, consumer health, life sciences research, legal, etc).
Ask me anything about what we learned trying to do this the hard way first.
Hubble
@aaronleon The problem always hits different when you have lived it yourself!
the voice agents calling records departments is the part I'd want fail-tested. what happens when the person on the other end gets suspicious it's not a human and throws an unscripted question at it?
Hubble
@sabber_ahamed Totally hear you on that. You're flagging two valid concerns: 1/ will people be suspicious that it's not a human and 2/ how do we handle different unscripted questions. For 1, we are seeing more providers start adopting AI for these workflows. In addition we also have escalation paths to humans if needed. For 2, we are constantly improving our prompts to handle these different paths as well!
@prabhadublish the escalation path is the part that matters most honestly, providers adopting AI is only half the trust problem if there's no clean handoff when it breaks
Hubble
@sabber_ahamed yup totally makes sense
the voice agents calling records departments is the interesting part to me - what happens when a provider's line dumps into a callback queue or wants live verbal ID verification? does it hand off to a human or just keep retrying
Hubble
@sabber_ahamed love these questions! the callback queue is one where can track & follow up on. We haven't seen examples of verbal ID verification, what's more common is requesting an authorization form being faxed over, which we can handle. I think we'll have more signal on this as we continue to scale
@prabhadublish faxes still being the fallback in 2026 is wild but not surprising. makes sense you'd want more scale before generalizing past that
Hubble
@sabber_ahamed yeah it's wild but not surprising given the state of healthcare :(
Awesome product - I was just switching primary care providers and had to stitch all my records together. How can I ensure that my records are safe with Hubble? Is it easy for me to remove any of the records I don't want Hubble to hold?
Hubble
@christinagee12 Great questions & know how frustrating it is to stitch records together. We take privacy seriously at Hubble, we know how sensitive this data is so it's a core principle as we built the product. Every patient has agency to remove records that they don't want Hubble to hold as well.
Hey team! It sounds awesome. How do retrieve those records and why other APIs can't? Anyway, wish you all the best here!
Hubble
@german_merlo1 Great questions - we use other methods like voice and browser agents to go beyond what the APIs have available. Our core thesis is that we should pursue multiple methods in order to build a more complete record. Our goal is to reduce the burden on consumers and businesses who need this context.
@prabhadublish that's awesome! I'm sure you'll rock it
Hubble
@german_merlo1 appreciate the thoughtful questions!