4 ms·
I think this is exactly how health/medical data should exist. My family should have their own health/medical network node and only my direct healthcare provider
by thephyber 9y ago
I think this is exactly how health/medical data should exist. My family should have their own health/medical network node and only my direct healthcare providers should be able to access the data from it and only after I authorize them with a digital signature. Whatever data they generate about my person (or persons in my family) should be owned by me, stored in my family network, and only available to others after I explicitly authorize it.
The massive collections of monolith data sets for financials, health/medical, credit history, employment records, taxes, census, etc are far too valuable to not be highly valuable to criminal orgs and/or government entities. Centralization into monolithic organizations will lead to irreversible issues of data non-privacy for a generation or more..
- saganus 9y agoUhmmm...just thinking out loud here. How feasible do you think it would be to use Mastodon for this? If you have a "Medical Node" as you put it (which I find apt btw), you could share it with your doctor(s) and provide access (maybe using Keybase? Auth0?) for them to either add "their own posts" with the analysis results, their findings, etc, or just to read the relevant data (e.g. for a dentist). Again, just thinking out loud, but they way you put it sounded interesting :)
- ams6110 9y agoDoctors make notes by dictation, which is transcribed to patient charts by medical secretaries. So you'd need to authorize those people as well.
- wilde 9y agoDoes Mastodon have a fax interface? https://www.vox.com/health-care/2017/10/30/16228054/american-medical-system-fax-machines-why https://www.vox.com/health-care/2017/10/30/16228054/american...
- HillaryBriss 9y agonice article. "It turns out there are strong economic incentives for doctors to keep patient information to themselves — and even stronger incentives for electronic medical records not to play nicely with each other." "While patients might want one hospital to exchange information with another hospital, those institutions have little incentive to do so. A shared medical record, after all, makes it easier to see a different doctor. A walled garden — where records only get traded within one hospital system — can encourage patients to stick with those providers."
- iambateman 9y agoI love this and I want it to be real but it won’t work. Here’s why... As an individual, I won’t lose my medical records because I have three backups and offsite and whatever. You probably do too. But how do you remain really decentralized when the system has to work for a 76-year-old who can’t even remember what Google is, much less his password. Will this work in the golden hour after a stroke, when literally every minute matters? So we would make a medical record “bank”, which is federated sensibly, and require everyone to use it. And eventually we end up with a similar system that we have now.
- naasking 9y ago> So we would make a medical record “bank”, which is federated sensibly, and require everyone to use it. And eventually we end up with a similar system that we have now. Except accessing your encrypted records require the presentation a doctor's key and your key, which might be a standardized health card with a chip. So not entirely similar to what we have now, it could be considerably safer.
- dllthomas 9y ago> it could be considerably safer. If my card is lost or broken? The system you describe seems clearly at less risk of inappropriate disclosure. Whether it's safer is perhaps another question.
- naasking 9y agoa) You still need physical access to a terminal to use the key, and b) you revoke the key when it's reported lost.
- dllthomas 9y agoThose are just more reasons why it's harder to inappropriately access the data. My point was that you may need access to the key fast for health-related reasons, and so from that perspective it may reasonably be deemed "less safe" even if it's more secure. cf. the difference between "fail safe" and "fail secure", in a slightly different context
- ams6110 9y agoWho would develop and market and support this, and who would pay for it?
- secstate 9y agoIncidentally, I'm working in healthtech right now and I have looked at this a million different ways, and the first and biggest problem is the quality of the data and trust of the data. You make a big deal about after I explicitly authorize access, but once you've granted access, that's it ... what's to stop the doc from copying some info from your chart? More relevant, what happens if you lose access to your data? Or it becomes corrupted? Now, because you owned your data, it's only your responsibility. You know who's not going to put up with that? Anyone who can afford to hire someone else (like a doctor) to keep track of their chart for them so that stupid stuff doesn't happen. Most people don't realize that many of the connected health record problems have already had high quality solutions provided in the form of VistA (https://www.wikiwand.com/en/VistA https://www.wikiwand.com/en/VistA). It's interface would make a startup designer cry, but medical professionals find it highly effective. Especially the network effect of being able to hand charts off and coordinate care, which would be very difficult in a decentralized health record world.
- hvidgaard 9y agoThe average Joe will never manage to do that. So unless the state develop, maintain, and make available free of charge, such a service, it will never happen.
- marcinzm 9y agoIn which case you've now built a centralized medical record storage system. And since people lose their keys all the time and you don't want that to cause them to lose all their medical records you also now have access to their medical records in plain text.
- hvidgaard 9y agoI completely agree, and I'd rather that it's done this way, I believe the benefits far out weight the risk of abuse. On the other hand, with old fashioned paper journals, you could get all copies and store them yourself. If you lose them they're gone too. If there was a cryptographic construct where the access of data would require a public action, i.e. "to assemble the key to decrypt this data, I need to broadcast this to the world", then I can think of a number of good ways to store things with a robust accountability feature.