People didn't like the idea then, and I'm not sure they will adopt it this time around...
[0] https://googleblog.blogspot.com/2011/06/update-on-google-hea...
> https://en.wikipedia.org/wiki/Microsoft_HealthVault
Apple have been trying similar with the Health app too I'd argue, even if it's not nearly as integrated with medical records yet. Why does no one ever succeed?
Hospitals and service providers in America have no incentive to do anything that would reduce switching costs and increase the quality of care that you get if you do switch. Moreover, since this is a low-information landscape with respect to both pricing and outcomes, consumers have little way of differentiating and thus service providers also have less incentive to adopt practices that improve outcomes.
Then you have to consider multiple decades of paper records, and records from other systems. Then there's many hospital systems composed of multiple health entities (hospitals, clinics, stand-alone emergency rooms). Some hospital systems span across multiple states and each state have their own set of rules (don't forget about the federal rules as well - HIPAA).
Then when you are building out your EHR system. You have to take into consideration the aspect from the doctor. There are many specialties within medicine. An EHR record from the point of view of an emergency medicine doctor vs a radiologist is very different.
I hate to say it (because it makes me groan) but I really think a trustless blockchain based solution would work best where medical professionals/researchers require active consent before pulling your records, a trustless form of anonymization/pseudonymization is built into the platform and an immutable record of every query made and why is held forever.
I wonder if the product managers know that Google tried this.
I’m not sure I’d ever trust Google again with a health record. Also since they can de-identify and advertise based on health condition across all of Google that’s a privacy nightmare for me. And I think since a health record where you enter your data isn’t HIPAA protected, then who knows what they’ll do with the data.
It's honestly the sort of thing where you should have a standard created by an independent group designing a standard, which is then implemented by the government (handling storage and release of records to local providers).
this is actually the perfect breeding ground for a highly serviceable solution. thousands of at-bats to solve a thorny complicated problem. the challenge is bringing that whole breadth of knowledge to bear on said standards-making process. inter-/intra-group politics often gets in the way, but that is also solvable with good leadership and trust-making processes.