As someone who worked in this area: > 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. Not just digitizing but also in sharing them. Hospital systems are very very reluctant to send out a copy of their records,…
FHIR makes a lot of this better, but EHR vendors hate it for that reason. Also, it's complex to implement. Fortunately, we have HAPI [1] and it's very good, but has deployment complexity only a java developer could love. There's been a couple false starts on a nodejs based FHIR server, but nothing open source and production ready that I've found. [1] https://hapifhir.io/
Have you used HAPI FHIR in production at any scale? Our experience is that it completely falls over under any reasonable strain. Try working with a few thousands patents and ~100M Observations and you will see HAPI work very poorly. It's great that HAPI is very feature rich on the API side--they've implemented most of the spec. But JPA and how they're using it is not a healthcare-scale technology. Google's (Spanner based) and Microsoft's (CosmosDB & SQL Sever based) FHIR API are better at scale but have far fewer features. I'm actually ok with that because the FHIR spec's query functionality is actually much more limited. Google's BigQuery integration really helps here. I'm interested to see where AWS is going with Health Lake. In talking with them I believe they have the best paradigm for their technical implementation.
It is a shame that the open source FHIR servers haven't been great. I think they will probably improve once a scalable paradigm for working with FHIR emerges.