Stream: patient empowerment
Topic: Consumers rolling their own?
Dave deBronkart (Feb 07 2020 at 03:40):
Everyone who's talked to me about this at (and since) last June's DevDays, I know you may have already said "I do that!" At the time I didn't have context for it to sink in, nor a place to catalog it. Repeat it please!
@John Keyes @Kristina Sheridan I saw the announcement post today about developer.commure.com, "The FHIR-native open Platform for healthcare developers."
I'm clueless enough to be intensely curious about what steps lie between an interface like this (or perhaps 1upHealth) and someone like me being able to create my own set of "datums" that I want to track, to pull down into my own dashboard, a la Sheridans or Mike Morris.
That may be a hopelessly vague desire but let's talk about it. I speculate that functions like this would be needed:
- What stuff do you want to retrieve? (Specify, or browse a generic list, or browse what's available at your specific providers)
- What do you want to do with it? (Track its value over time (e.g. my A1c), graph it with other variables, just capture in a diary...)
- Offer some standard packages that normal people want to do - perhaps in a free / lite version
- But also (perhaps in paid version) enable someone like y'all to create their own dashboard
I could go on and on but the real question is - okay, things like Commure handle a first step, but it's not ready for use by (e.g.) my sister who's tracking Mom's stuff.
Dave deBronkart (Feb 07 2020 at 03:44):
The Commure "about" page says
**Built by doctors and developers
for doctors and developers.**We built this platform to support the work of software engineers and teams who are looking to move the needle in healthcare. We built it for doctors who code and who are intimately acquainted with the challenges their profession faces in the day to day. ...
This is fine with me. I'm asking, what sort of layer would need to be bolted on to enable one particular use case - the consumer/patient with a significant need unanswered by mass market apps?
Brendan Keeler (Feb 07 2020 at 04:53):
Could be wrong but quick read suggests it's not patient app focused (HCO and provider apps) and that 1up, Apple, HumanAPI all still better for patient use case, if youre not DIY
Brendan Keeler (Feb 07 2020 at 04:54):
Some light reading about the three trust paradigms of healthcare for you, Dave: https://link.medium.com/wv9nouzmS3
John Keyes (Feb 07 2020 at 13:43):
This is fascinating: "We built it for doctors who code ". Doesn't seem like patients (who code) are also part of their target market (which is fine, of course; it's just interesting to note).
Dave, it may well be that this platform could be used to build useful patient-focused web applications. I need to take a little more time to understand what added value their APIs and platform provide.
Also, as an independent app developer, I tend to be leery of two things:
- Enterprise-style pricing models ("contact us for pricing"), rather than transparent published pricing.
- Adding too many third-party dependencies to my app. Platform services have a history of changing or going away.
That said, this still looks quite interesting, and I'll be watching what they do.
Bart Carlson (Feb 07 2020 at 17:13):
Brendan, Great overview article on where interoperability is today!
Brendan Keeler (Feb 08 2020 at 17:17):
Thanks Bart!
Last updated: Apr 12 2022 at 19:14 UTC
