Alphabet is spending billions to become a force in health care
As someone who worked in this area:<p>&gt; Google is also giving health records another whirl. The new initiative, called Care Studio, is aimed at doctors rather than patients. Google’s earlier efforts in this area were derailed in part by hospitals’ sluggishness in digitising their patient records.<p>Not just digitizing but also in sharing them.  Hospital systems are very very reluctant to send out a copy of their records, or even to let you query their system.  Especially in the early days of EHRs there was very much a sense that it was <i>their</i> data and they didn&#x27;t want to let data out because interoperability was a threat to their data moats.<p>That&#x27;s good in a privacy sense, but it really did slow down adoption of interoperability initiatives.  Finally Medicare&#x2F;Medicaid basically forced it iirc... if you want Medicare dollars you will send Medicare your encounter data.  So now you have to code your records at least good enough to at least get your medicare reimbursements.<p>&gt; That problem has mostly gone away but another has emerged, says Karen deSalvo, Google’s health chief—the inability of different providers’ records to talk to each other. Dr de Salvo has been vocal about the need for greater interoperability since her days in the Obama administration, where she was in charge of co-ordinating American health information technology. Until that happens, Care Studio is meant to act as both translator and repository (which is, naturally, searchable).<p>Dead on.  It&#x27;s a hard hard problem though because during the early days we went through a Cambrian explosion in data diversity.  Data is often coded very inconsistently or in ways that make it &quot;invalid&quot; to modern schemas.  The &quot;miracle of HL7&quot; is basically just a fancy text format, and like the on-table records or XML documents it&#x27;s still possible to code things in ways that still won&#x27;t be parseable even if they&#x27;re syntactially&#x2F;lexically correct.<p>There are standardized schemas (f.ex NEDSS schema) available, but they are super over-engineered for a lot of use-cases and can perform quite poorly due to excessive &quot;anything can map to anything&quot; design and field-table-value formats.  And again, they suffer from the &quot;there&#x27;s multiple ways you could code this&quot; thing, just using NEDSS doesn&#x27;t mean you interoperate with anyone, not close.  Not sure what EHRs typically have underneath but it wouldn&#x27;t surprise me if they all had their own solutions too, EHR software is universally dogshit.<p>Handling poorly-validated&#x2F;normalized data from tens of thousands of facilities all doing their own things is a very tough problem, and honestly the only solution is to decentralize it a little bit, facilities have to look at their own data and see if it makes sense the way they&#x27;re sending it or even if they&#x27;re storing it wrong.  Once it&#x27;s just another record in a database, if it&#x27;s not consistent and accurate it likely never will be.   It&#x27;ll just be yet another System-Specific-Record-Identifier in the list for that record, and since it&#x27;s not coded right nobody will ever be able to read it unless it&#x27;s patched by someone&#x2F;some layer.<p>Data clearinghouses are uniquely positioned to gatekeep that a little bit, and over time there are tools getting written to help various facilities validate their data and see whether it&#x27;s semantically reasonable.  Almost everybody has errors especially if this is their first integration, but they can be brought up to speed on their ongoing record submissions, at least.<p>I&#x27;m sure google would love to be in charge of everyone&#x27;s health data, or at least to get to see it.  Commercial activity isn&#x27;t notionally allowed but I wonder if HIPAA applies to aggregated data like that, they can probably set up The Business-Purpose Side with a firewall from the Gets To Make Money Querying Anonymized Data side.<p>It&#x27;s true that this is a thing where there are intellectual economies-of-scale though.  If you can get to One Standard To Rule Them All and actually make it work and not suck, that&#x27;s useful, everyone just agrees to adopt Google Validation Rules and a shit-ton of terrible mapping&#x2F;correcting labor gets saved once people get on board.  There&#x27;s just also not really anyone trustworthy enough to handle being the One Giant Repository Of Health Data, Google owning it eventually ends up in massive data mining of sensitive PHI.