Profile picture
Don Lee @dflee30
, 24 tweets, 12 min read Read on Twitter
1/ Finally working through all my notes from the #HITExpo. The most important conversation to me was the one about “solving interoperability” with @RasuShrestha @PaulMBlack and @techguy.
2/ Rasu told the story of what UPMC accomplished using DBMotion. How it enabled the flow of data amongst the many hospitals, clinics and docs in their very large system. #hitexpo
3/ John challenged him a bit and said: it sounds like you’re saying that you’ve solved #interoperability. Is that what you’re telling us? #hitexpo
4/ Rasu explained in more detail that they had done the hard work of establishing syntactic interop amongst the various systems they dealt with (I.e. they can physically move the data from one system to another and put it in a proper place). #hitexpo
5/ He went on and explained how they had then done the hard work of establishing semantic interoperability amongst the many systems they deal with. That means now all the data could be moved, put in its proper place, AND they knew what it meant. #hitexpo
6/ Syntactic interop isn’t very useful in and of itself. You have data but it’s not mastered and not yet useable in analytics. #hitexpo
7/ Semantic interop is the mastering of the data in such a way that you are confident you can use it in analytics, ML, AI, etc. Now you can, say, find the most recent BP for a patient pop regardless of which EMR in your system it originated. And have confidence in it. #hitexpo
8/ Semantic interop is closely related to the concept of #DataFidelity that @BigDataCXO talks about. It’s the quality of data for a purpose. And it’s very hard work. #hitexpo
9/ In the end, @RasuShrestha’s answer was that UPMC had done all of that hard work and therefore had made huge strides in solving interop within their system. He said “I’m not flying the mission accomplished banner just yet”. #hitexpo
10/ Then @PaulMBlack - CEO at @Allscripts - said that @RasuShrestha was being modest and that they had in fact “Solved interoperability.”

I think he’s right and that’s what this tweet storm is about. Coincidentally, it’s a matter of semantics. #hitexpo
11/ I think Rasu dialed it back a bit because he knew that people would hear that and think it means something different. #hitexpo
12/ The overall industry conversation tends to be about ubiquitous, semantic interop where all data is available everywhere and everyone knows what it means. I believe Rasu was saying that they hadn’t achieved that. And that makes sense... because it’s impossible. #hitexpo
13/ @GraceCordovano asked the perfect question and I wish there had been a whole session dedicated to answering it: (paraphrasing) What’s the difference between your institutional definition of interop and what the patients are talking about? #hitexpo
14/ The answer to that question is the crux of our issue. The thing patients want and need is for everyone who cares for them to be on the same page. Interop is very relevant to that issue, obviously, but there’s a lot of friction and it goes way beyond tech. #hitexpo
15/ Also, despite common misconception, no other industry has solved this either. Sure, my credit card works in Europe and Asia and gets back to my bank in the US, but that’s just a use case. There is no ubiquitous semantic interop between JP Morgan Chase and HSBC.
16/ There are lots of use cases that work in healthcare too. E-Prescribing, claims processing and all the related HIPAA transactions, etc. #hitexpo
17/ Also worth noting... Canada has single payer system and they also don’t have clinical interoperability.

This is not a problem unique to healthcare nor the US. #hitexpo
18/ So healthcare needs to pick its use cases and do the hard work. That’s what Rasu described on stage. That’s what Paul was saying has been accomplished. They are both right. And you can do it too. #hitexpo
19/ So good news: #interoperability is solved in #healthcare.

Bad news: It’s a ton of work and everyone needs to do it.

More bad news: You have to keep doing it forever (it breaks, new partners, new sources, new data to care about, etc).

#hitexpo
19/ Some day there will be patient mediated exchange that solves the patient side of the problem and does it in a way that works for everyone. Maybe on a #blockchain. Maybe something else. But it’s 10+ years away. #hitexpo
20/ In the meantime my recommendation to clinical orgs - support you regional #HIE. Even UPMC’s very good solution only works for data sources they know about. Your patients are getting care outside your system and in a growing # of clinical and community based settings. #hitexpo
21/ the regional #HIE is the only near-term solution that even remotely resembles semantic, ubiquitous #interoperability in #healthcare.
#hitexpo
22/ My recommendation to patients: You have to take matters into your own hands for now. Use consumer tools like Apple health records and even Dropbox like @ShahidNShah suggested in another #hitexpo session. Also, tell your clinicians to support and use the regional #HIE.
23/ So that got long. I’ll end it here. What do you think?

P.S. the #hitexpo was very good. You should check it out in 2019.
Missing some Tweet in this thread?
You can try to force a refresh.

Like this thread? Get email updates or save it to PDF!

Subscribe to Don Lee
Profile picture

Get real-time email alerts when new unrolls are available from this author!

This content may be removed anytime!

Twitter may remove this content at anytime, convert it as a PDF, save and print for later use!

Try unrolling a thread yourself!

how to unroll video

1) Follow Thread Reader App on Twitter so you can easily mention us!

2) Go to a Twitter thread (series of Tweets by the same owner) and mention us with a keyword "unroll" @threadreaderapp unroll

You can practice here first or read more on our help page!

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just three indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member and get exclusive features!

Premium member ($3.00/month or $30.00/year)

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!