Live data from Hacker News

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

news.ycombinator.com

31–40 of 103 posts

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

#31

Can I make an App that can show a person their own medical data? i.e, user-provisioned access.

Yes. In the US, this is part of the EHR push, each EHR is supposed to accept any outside application. Here are some docs on how it works with Epic: https://open.epic.com/Home/InteroperabilityGuide?whoAmI=deve...

A big tricky part is understanding all the different health systems that have part of the patient's record. Typically speaking you can scrape all health system FHIR access point's and perform some geo matching to offer the ones they likely have seen. From there you do the Oauth2 dance with each health system where the patient authenticates (if they remember their login) and your app gets a token good for a certain time period after which the patient has to log in again.

The advantage of Metriport's approach is that they are getting a hook into the vendor operated HIEs. The patient doesn't have to remember/select which health care systems that have records for them since the VOHIEs have all that. The big hurdle is managing some authentication on behalf of the patient to a third party that they don't have a direct relationship to, the VOHIE. I suppose the VOHIE can pass the patient off to one of the member health systems and do the same Oauth dance but instead of just getting one health systems data, you get the whole enchilada.

The evil part of the operation is that now Metriport has proxy access to the data and eventually will get hacked and bought by private equity that will sell the data to TransEquirian Insurance Score agencies.

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

#32
post #8

Congrats on the launch. I work in healthtech and I'm always shocked by how fragmented and siloed the technology is in my industry. Both at the application level (EHR) and data level, leading to general inefficiency, high costs and innovation that do not always benefit the patients. Glad Metriport is addressing this! I hope you will drive a new level of standardization on an open and modern data exchange protocol. One…

more data does not always mean good data. Health systems have varying level of quality and accuracy and in some cases, wrong information affects patient outcomes. The idea of connecting sparse systems has pros and cons. Consider someone who is misdiagnosed and switching doctors because they can't get the medical staff to believe them. They would be served by a fresh set of data and if re-diagnosed, so be it.

Interesting case, inaccurate data aside, I imagine medical staff form diagnoses objectively.

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

#33

Can I make an App that can show a person their own medical data? i.e, user-provisioned access.

I'm working on something in this space right now, would be really interesting to use Metriport for this. Though I believe that it's currently outside scope

>Additionally, using Metriport for patient data exchange today requires a Treatment purpose of use under HIPAA - which means that only Covered Entities, or Business Associates who work with Covered Entities, can use Metriport. This means that companies doing things such as clinical trials recruitment, for example, can’t use Metriport, but a primary care provider, or a clinical decision support vendor, can. This is due to current requirements set forth by HIEs, which may open up to support alternative use cases in the future, such as Individual Access Services (IAS).

Would love clarification.

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

#35
post #31

Can I make an App that can show a person their own medical data? i.e, user-provisioned access.

Yes. In the US, this is part of the EHR push, each EHR is supposed to accept any outside application. Here are some docs on how it works with Epic: https://open.epic.com/Home/InteroperabilityGuide?whoAmI=deve... A big tricky part is understanding all the different health systems that have part of the patient's record. Typically speaking you can scrape all health system FHIR access point's and perform some geo matchin…

> In the US, this is part of the EHR push, each EHR is supposed to accept any outside application

To be explicit for readers here, outside applications can connect to some EHR systems using SMART on FHIR, but not all (this is what Apple Health supports in their PHR) - and this is separate from HIEs. For reasons OP mentioned, this is impractical for treatment at scale, but is currently the best way to get your health records in your pocket, or to insurance companies, for example.

Fasten is a great OSS project that facilitates this flow for individuals, and I'd suggest you check them out: https://github.com/fastenhealth/fasten-onprem

> getting a hook into the vendor operated HIEs

This is a only part of the equation - for example, one of the biggest networks we connect with is Carequality, and this is more of a framework that's not operated by any vendors. Rather, vendors connect to a shared directory and speak the same language for medical data exchange.

> The evil part of the operation is that now Metriport has proxy access to the data and eventually will get hacked

This just speaks even more volumes to our open source approach - we're not hiding behind obscurity for security.

> and bought by private equity that will sell the data to TransEquirian Insurance Score agencies.

Only if someone wants spend a long time in prison! We can not legally do anything with the data we have proxy access to, except deliver it to the healthcare organizations we work with that are involved with treating the patient - nor would we want to. There are acquisition events with healthcare organizations all the time, and the HIPAA rules protecting the data do not change.

Hopefully you can agree that, especially with us being the only vendor in the space that's open source, there is no evil at play.

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

#36
post #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 f…

Thank you - it's a difficult problem for sure, but that makes it all the more fun and rewarding.

> should be handled on state level

Many of the aforementioned HIEs in the US are actually offshoots of state, or federal, government initiatives like TEFCA. We didn't go into details in the post, but the main HIEs are definitely not privately held startups - mostly nonprofit state sponsored organizations.

> we pretty much have any government service available over the web, and yes, we also get to enjoy state provided health care

There are pros/cons of state run centralized government systems for sure - with Metriport as a communication layer, we're hoping to bring providers in the US the best of both worlds for data exchange.

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

#38
post #22

Apart from your new product, the old metriport app I found very intresting. If you ever considered to make it opensourced, I would be glad to contribute.

We'd love to open source it - but are too strapped for time to do so. Perhaps one day in the future.
Post reply on HN