The closed systems and lack of support for interoperability between EHRs upsets me the most because it leads to patient harm.As a patient here's what gets me: UNC has one EMR system, my GP has another, and Duke has yet another. I've been a patient at all 3 at various times. I also use Strava, Fitbit, and the like. Now you would think that it would be trivially easy to use an API and export and aggregate all of my lab results, for things like blood pressure, cholesterol, etc., so I can graph, say, my blood pressure and my Strava activity together. But nooooo... all of these EMR systems either have no export functionality / API, or if they do, it's something byzantine and just-short-of-impossible-to-use.
Of course not every patient is a data geek who's going to use machine learning, statistical analysis and visualizations on their own data. But for those of us who want to, the roadblocks to doing so are infuriating.
I just had a patient transferred from an outside hospital for abdominal pain and somehow their CT scan was lost in transit. Because it was an emergency we had to CT scan them again which doubled their radiation exposure and their risk for a kidney injury from the iv contrast. It was midnight so it would have taken until business hours to obtain the scans from the hospital.
The doubly sad part is that this is almost 100% a policy / business issue and not a technical one. We've known how to share data for a long time. Heck, IIRC, a scenario much like the one listed above was used as an illustrative example for justifying the WS-Federation[1] protocol way back when.
Edit: Yep, this document[2] explaining WS-Federation actually uses an emergency room scenario to justify the need for WS-Federation. Not the exact same scenario as above, but the point stands. We've had protocols and technologies for doing this stuff for a long time.
[1]: https://en.wikipedia.org/wiki/WS-Federation
[2]: http://download.boulder.ibm.com/ibmdl/pub/software/dw/specs/...