Ask HN: I want to create a personal health dashboard, what should I use?
I want to create a personal health dashboard to track regular blood work, cardiovascular data and some other health metrics. Some of these might be recorded via apps (e.g. Apple Health) others would be manually put in (e.g. blood work sheet from my doctor).
I've looked around and didn't really find any platform like this. Some options were very much geared towards the U.S. market and provided connections to health care providers. I think, what I am looking for is much more simple than this.
So far I've been putting everything in an Excel sheet but I'm not a big fan of Excel and would like something standalone that might also show me progressions and changes more easily.
Any suggestions?
40 comments
[ 4.6 ms ] story [ 86.4 ms ] threadmost medical practices have your test results available online
not sure why/how you need to merge blood tests and watch data for a meaningful benefit
otherwise, spend time cleaning up your diet and improving your exercise and sleep...you can't get healthy just moving data around
Thanks for the suggestions, however what I'm asking for here is not so much about a data-driven shortcut to "getting healthy" but a way to track specific metrics. The data is scattered around different places and I mainly want it in one place so I can have a quick overview of the numbers, spot trends and make associations where needed.
It doesn't appear you can add random things to track as a goal and chart them but there are notes which might be more appropriate for cholesterol and blood test results since those are infrequent I assume.
I'm amazed by the dedication Felix has put to even log the manual data points everyday.
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
What about publishing an API? It's the most sensible and open way of attracting (ALL) developers not just Android ones.
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).
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!
Here's what is upcoming in that requirement: 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!
I concur that fragmentation kills our ability to custom-build these tools. I'm in the same position, I want to gather and have a single glass pane view of my meds, glucose, A1C, Weight, Exercise, Doctor Visits/Notes and Lab results.
I'll jot this down on my PARA inbox. ;)
https://github.com/k0rventen/apple-health-grafana
I worked on something in the space and one of the challenges we ran into was pulling data from Apple Health. At the time there was no API (haven't checked recently) so if we wanted that data we would have needed to build an app. There were companies that had apps/APIs but the price seemed to start at $30k which didn't make sense for us.
Context: we were mostly focused on activity metrics.
Which he then turned into this: https://gyrosco.pe/home/
https://news.ycombinator.com/item?id=36025977
I even jam additional info like mood, weight, and blood pressure and other metrics into it with Shortcuts, which speeds up the process.
You automatically get:
- A Home Screen icon
- Siri support
- Ability to run on a schedule with automations
A general privacy-respecting health-oriented bucket of medical records is completely tangled in government regulations, organizational constraints, design-by-committee -- bureaucratic nonsense individuals don't need. It's easy to get lost in the weeds.
Often what you want is to know where you stand with respect to a particular condition, say, atherosclerosis and coronary artery disease.
The key thing is to build your model for evaluating that condition, e.g., LDL blood work, night-time systolic blood pressure, pulse-oximetry during exercise, exercise tolerance, etc. The model combines those things into a meaningful, actionable score. E.g., it should indicate whether to increase the statins or blood pressure medication, exercise or eat differently, investigate possible primary conditions or genetic risks, etc. I.e., the model represents the ongoing differential diagnosis, and should confirm or invalidate the hypothesis.
Then you can start to prune and evolve the model and the data. Maybe the pulse-ox data after exercise, while easy to gather, really means nothing. Maybe the blood work is sensitive to recent exercise, so you get more consistent results from take 2 days off beforehand. You compare your model to the existing models - e.g., the ASCVD risk estimator - or update it to track new studies. You start to integrate other models, tracking inflammation or oxidation. As you get trends, you'll see associations.
My point is that dashboard fly-over's are for executives/managers to make quick decisions about complex topics. We all want to simplify the complex, but sometimes it's actually better to dive into the details to get more clarity and understanding.
In that case, what might help is a way of organizing libraries of studies and presentations, building a bunch of one-off analysis tools to ingest data and compare with other models, etc. Tying them together mainly involves deciding on your data model - typically one module per source-style and another for your own integration.
wrt technologies, graph DB's are tempting, but most actual models work in excel pretty well, and pivot tables with graphs get you pretty far in analysis and visualization. Mathematica is great here for prototyping because it has proper units, sample API's, data sources, programmability, visualization, and a clean programming model and tutorials. I recommend it partly because it's a window onto everything current - LLM's, image recognition, big data, open-source data... The alternatives are to wander the wildlands of python libraries, or take the rigid Apple museum tour. Mathematica is more like wandering the museum yourself.