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.
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 [email protected] and I'll get you set up.)
The fallback chain is the interesting part: API first, then browser agents through provider portals, then voice agents calling records departments. I build voice AI in the aging-in-place space, daily check-in calls with older adults, so I have some scar tissue around that last step. Records departments tend to be IVR trees, long holds, and a human who ultimately wants a fax number.
Two questions. Does the voice agent disclose it's an AI to the clerk up front, and did that move your success rate either way? And when two sources return the same encounter with conflicting data, does the API hand back both versions or reconcile them for you?
Literally happened to me with Kaiser last week and it was a nightmare! Excited to see a product fixing these critical dependencies.
This is awesome! It would be great it this paired with prehospital records (on an ambulance) because those interventions/vitals are often lost in the patient care journey
One of your fallbacks is a voice agent phoning a records department on the patient's behalf. That call is the unglamorous part of this problem. Congrats on taking it on instead of leaving it to patients.
@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)?
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?
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
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?
this is huge — going to different doctors always meant starting from scratch and they never had the full context. this is key to better patient outcomes 🔑
Hey team! It sounds awesome. How do retrieve those records and why other APIs can't? Anyway, wish you all the best here!
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.
Congrats on the launch
The problem you are solving is genuinely interesting especially with patient records being scattered across providers
Curious to see how Hubble handles the messy real world edge cases here and excited to see where this goes
About Hubble on Product Hunt
“Retrieve medical records other APIs can't”
Hubble launched on Product Hunt on August 18th, 2026 and earned 199 upvotes and 58 comments, placing #4 on the daily leaderboard. 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 was featured in SaaS (43.9k followers), Developer Tools (518.4k followers), Artificial Intelligence (477.3k followers) and Health (6.8k followers) on Product Hunt. Together, these topics include over 259.9k products, making this a competitive space to launch in.
Who hunted Hubble?
Hubble was hunted by Garry Tan. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Hubble stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Garry Tan
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 [email protected] and I'll get you set up.)