Live data from Hacker News

Launch HN: Metriport (YC S22) – Open-source API for healthcare data exchange

news.ycombinator.com

21–30 of 103 posts

Re: Launch HN: Metriport (YC S22) – Open-source API for healthcare data exchange

#21

Thank you for this, so much needed. I hope that you are going to come to Europe soon. Honest question, how was your experience with getting funding on an open source product within healthcare? My experience so far is that the field is, as you put it, 30 years back, also in terms of business models.

Europe is its own beast of healthcare data problems for sure - perhaps one day.

We get asked the fundraising question a lot, especially since we're open source. Once investors understood that we still have a hosted product we charge for, and that we have a large moat since someone could fork our code but it'd be very difficult to run the business (compliance, getting access to the different networks, understanding the niche space, etc) - open source wasn't a hinderance to raising.

One thing we learned though, is that even though every human interacts with the healthcare system in some capacity - very few people know how things actually work. So, we had to tailor our pitches to make investors understand why our product matters, since generally even people that have healthcare experience, have no idea what the hell an HIE is.

That, and our GTM allowed us to sell quickly, without needing to wait for slow moving hospital contracts, as are typical in healthcare - so some decent traction definitely helped.

Re: Launch HN: Metriport (YC S22) – Open-source API for healthcare data exchange

#24

Well done with the launch. This is a tricky space, but if successful you will be very successful. A health platform I helped build was open sourced[0] (the apps built on it are closed source and deployed in NHS trusts). Feel free to dig around for any inspiration :-) [0] https://github.com/polaris-foundation

Thank you! Glad to see more open-source in healthcare - was the idea here sort of like a reusable EHR backend for building digital health products? I see some mention of HAPI FHIR in the repo as well.

Re: Launch HN: Metriport (YC S22) – Open-source API for healthcare data exchange

#26

Well done with the launch. This is a tricky space, but if successful you will be very successful. A health platform I helped build was open sourced[0] (the apps built on it are closed source and deployed in NHS trusts). Feel free to dig around for any inspiration :-) [0] https://github.com/polaris-foundation

Thank you! Glad to see more open-source in healthcare - was the idea here sort of like a reusable EHR backend for building digital health products? I see some mention of HAPI FHIR in the repo as well.

Yes it was - it was internal to our company, but the apps got sold off when the business downsized. The engineering team lobbied to have the main backend open sourced, partly because it made the divestment of the apps built on it easier.

The architecture was that that was a backend for apps, and the individual apps would host a stateless BFF service to translate the backend into what they needed, and then the web/mobile apps would talk to that. HAPI FHIR was integrated for testing reasons; it also spoke HL7v2, for our sins.

Re: Launch HN: Metriport (YC S22) – Open-source API for healthcare data exchange

#27

If I understood correctly: it sounds like HIEs were supposed to solve this problem but just duplicated it, so you’re hoping to actually solve it this time?

Pretty much! We're essentially building a service that leverages multiple networks - from a modern healthcare engineer's perspective, and focusing on product/data usability.

Re: Launch HN: Metriport (YC S22) – Open-source API for healthcare data exchange

#28
I commend you trying to tackle such a challenging domain, something that feels should be handled on state level.

As a citizen of Estonia, we pretty much have any government service available over the web, and yes, we also get to enjoy state provided health care, which makes things simpler when it comes to having a single unified system for all health care workers, which we have, have had for quite a while, probably for a decade or more. And it works, including patients who can also log into the system to check any data that is collected on their behalf.

Re: Launch HN: Metriport (YC S22) – Open-source API for healthcare data exchange

#29

Nice work on the pivot + launch, team! You mention that IAS "may open up in the future." Does that mean I am not currently allowed to request my own record from an HIE?

Thank you!

That's right, we can't even request our own records using Metriport - this currently can only be done for a Treatment purpose of use (and opens up a lot gray area of what that means, as you can imagine).

The promise of TEFCA, and QHINs, is to open up more use cases for data access, like individual access, payment/operations, and etc. We're optimistic that eventually this will become a thing, but there are a lot of politics around this, and full implementation of these use cases has been getting delayed for some time now. It's technically possible today, but responding to requests outside of Treatment is not a MUST, so essentially nobody (namely the big EHRs) will actually respond to IAS requests.

In the meantime though, we're sprinting to hook as many providers up to the networks as possible, which then can share records with their patients.

Re: Launch HN: Metriport (YC S22) – Open-source API for healthcare data exchange

#30

When you say that you can use the HIE's to contribute new data to the providers in the network, is that data actually going into the EHR's as if it was a record added in the EHR directly? If not, where are these contributed documents being stored?

Yes!! A lot of folk think that the only way to get data into EHRs is by writing one-off integrations with a specific hospital IT system - but you can achieve the same thing using a single Metriport integration. We support 2 methods: (1) uploading FHIR data: https://docs.metriport.com/medical-api/api-reference/fhir/cr... , or (2) uploading documents like C-CDAs, PDFs, and images: https://docs.metriport.com/medical-api…

Thanks for your response, going to play around with your API in the next few days. This sounds like its exactly what we've been looking for.
Post reply on HN