5 ms·

Disclaimer: Engineer for the app... If you're an engineer and interested in building a little application then read on! CommonHealth is a (free, non profit) ap

Disclaimer: Engineer for the app... If you're an engineer and interested in building a little application then read on! CommonHealth is a (free, non profit) app that patients can use to download their health data from their health care providers. We're all about open interoperability with the ability to for developers to build on top of the app using the SDK to ingest the data of a patient and build any visualizations/analytics etc. There's zero backend data aggregation, all data lives ONLY on your personal device once you download it from your health provider, and all data is thus deleted if you simply uninstall the app. So that's to say, if you're in the US market and want to build your own functionality, you definitely have that opportunity, as we've done the work connecting to 1000s of providers (with 100k+ coming by end of year) Reach out if you want to get started here https://www.commonhealth.org/developers#dev-link-4 https://www.commonhealth.org/developers#dev-link-4

ambicapter 3y ago
Is this an Android-only application?
- btseytlin 3y ago
  As mentioned in the other comment, yes this is Android only as there is an Apple offering (via HealthKit https://developer.apple.com/documentation/healthkit https://developer.apple.com/documentation/healthkit)!
vladsanchez 3y ago
+1 about Android SDK. What about publishing an API? It's the most sensible and open way of attracting (ALL) developers not just Android ones.
- btseytlin 3y ago
  I'm not sure what you mean about a publishing API but on the Apple side, there's Apple HealthKit (https://developer.apple.com/documentation/healthkit https://developer.apple.com/documentation/healthkit) and we're the Android version of their offering! In the spirit of being privacy-centric, individual mobile phones storing personal health data of that patient offline is key to this approach. So no web option (i.e. no databases storing mass data).
mxuribe 3y ago
Thanks for sharing this! I'm not particularly interested in undertaking a project around this topic..but for the heck of it, glanced at the above link...and happened upon the statement on open source (https://www.commonhealth.org/developers#dev-link-2)...and https://www.commonhealth.org/developers#dev-link-2)...and was glad to have seen it! Now, having read that and CommonHealth's objective...i'm actually intrigued and may play around a bit. Kudos for working on/with CommonHealth!
- btseytlin 3y ago
  Woo! Correction incoming that the Sample app and SDK are open source, but the app itself is not yet. We ARE a 501c3 non profit so rest assured incentives are aligned, but keeping it closed source allows us to iterate quickly. Long term plan is open source. Would love to have you playing around with the SDK, and feedback/improvements can be made as we don't have any production apps using our sdk yet. I hope you find what you're looking for!
John23832 3y ago
I actually thought about building this but shyed away due to not wanting to handle hippa and being a one man shop at the moment. Good to know someone tackled this.
- btseytlin 3y ago
  It's quite a large project, so kudos to anyone who can do this as a one man shop :) We're trying to offload the heavy lifting of logistically connecting to the gajillions of health providers (via OAuth/proper channels aka SMART on FHIR connections) so that engineers can build the functionality patients could benefit from!
themantalope 3y ago
This is cool. I’m a radiologist. Do you have PACS?
- btseytlin 3y ago
  I'm not super familiar, but we have all sorts of things! It all comes down to what the US ONC (The Office of the National Coordinator for Health Information Technology) dictates is mandatory to be provided by the electronic health records companies. Here's what is upcoming in that requirement: https://www.healthit.gov/isa/united-states-core-data-interoperability-uscdi#draft-uscdi-v4 https://www.healthit.gov/isa/united-states-core-data-interop... You might be interested in the Laboratory section? But in our recent updates (in accordance with new data becoming available in FHIR R4), we have doctor's notes, care plans, goals (some of which are viewable in the original PDF form). Although some of that viewer technology is pretty advanced and wouldn't be supported by an app like ours, for example MRI viewers, personal health data is definitely moving in the right direction for patients!

ambicapter 3y ago

Is this an Android-only application?

btseytlin 3y ago
As mentioned in the other comment, yes this is Android only as there is an Apple offering (via HealthKit https://developer.apple.com/documentation/healthkit https://developer.apple.com/documentation/healthkit)!

vladsanchez 3y ago

+1 about Android SDK. What about publishing an API? It's the most sensible and open way of attracting (ALL) developers not just Android ones.

btseytlin 3y ago
I'm not sure what you mean about a publishing API but on the Apple side, there's Apple HealthKit (https://developer.apple.com/documentation/healthkit https://developer.apple.com/documentation/healthkit) and we're the Android version of their offering! In the spirit of being privacy-centric, individual mobile phones storing personal health data of that patient offline is key to this approach. So no web option (i.e. no databases storing mass data).

mxuribe 3y ago

Thanks for sharing this! I'm not particularly interested in undertaking a project around this topic..but for the heck of it, glanced at the above link...and happened upon the statement on open source (https://www.commonhealth.org/developers#dev-link-2)...and https://www.commonhealth.org/developers#dev-link-2)...and was glad to have seen it! Now, having read that and CommonHealth's objective...i'm actually intrigued and may play around a bit. Kudos for working on/with CommonHealth!

btseytlin 3y ago
Woo! Correction incoming that the Sample app and SDK are open source, but the app itself is not yet. We ARE a 501c3 non profit so rest assured incentives are aligned, but keeping it closed source allows us to iterate quickly. Long term plan is open source. Would love to have you playing around with the SDK, and feedback/improvements can be made as we don't have any production apps using our sdk yet. I hope you find what you're looking for!

John23832 3y ago

I actually thought about building this but shyed away due to not wanting to handle hippa and being a one man shop at the moment. Good to know someone tackled this.

btseytlin 3y ago
It's quite a large project, so kudos to anyone who can do this as a one man shop :) We're trying to offload the heavy lifting of logistically connecting to the gajillions of health providers (via OAuth/proper channels aka SMART on FHIR connections) so that engineers can build the functionality patients could benefit from!

themantalope 3y ago

This is cool. I’m a radiologist. Do you have PACS?

btseytlin 3y ago
I'm not super familiar, but we have all sorts of things! It all comes down to what the US ONC (The Office of the National Coordinator for Health Information Technology) dictates is mandatory to be provided by the electronic health records companies. Here's what is upcoming in that requirement: https://www.healthit.gov/isa/united-states-core-data-interoperability-uscdi#draft-uscdi-v4 https://www.healthit.gov/isa/united-states-core-data-interop... You might be interested in the Laboratory section? But in our recent updates (in accordance with new data becoming available in FHIR R4), we have doctor's notes, care plans, goals (some of which are viewable in the original PDF form). Although some of that viewer technology is pretty advanced and wouldn't be supported by an app like ours, for example MRI viewers, personal health data is definitely moving in the right direction for patients!