For Important tweet chats (such as #CMIOchat) I actually prepare notes and sometimes a pre-tweetchat blog post. Unfortunately it is an hour to the chat and I forgot I have to head out the door to pick up someone at the airport!
— Charles Webster MD (@wareFLO) October 22, 2015
So, for what they are worth, here were my notes… and perhaps a bit of an X-ray inside my head re my workflow-angle on interoperability. I’m sure you’ll notice stuff is pretty good toward the beginning and falls apart toward the end… but there are some interesting links you may find interesting, such as a presentation I gave in South Africa in 2010. Anyway, I’m heading out the door. Chat is on #CMIOchat hashtag and starts at 7:00PM. I’ll try to listening via smartphone (when I’m not driving!).
Sorry for typos! Will be full present next time. But anyway, in the meantime, IF YOU HEAR WORKFLOW, TWEET @wareFLO!
Chuck, DC. Wrote 7000-word, 5-part series in Health IT News on Task & Workflow Interoperability [link] #CMIOchat
Achieving Task and Workflow Interoperability in Healthcare: All Together Now!
T1. What are the challenges we encounter as patients and informaticists in the road to interoperability? Are you optimistic that we will get to true interoperability?
I feel our major challenge is pivoting from data-centric to more workflow-centric (or at least equally workflow-centric) views and emphases regarding the purpose and design of EHRs and health IT systems.
T2. What would a truly inter-operable, unified patient medical record look like from a functionality, user interface and operational perspective?
When most folks speak of interoperability they usually talk about syntactic and semantic interoperability. Syntactic is the “shape” of messages, which determines whether they can be parsed and transmitted between systems. Semantic is the meaning of a message, and whether a message means the same thing in two different systems. However, there are a number of more levels of interoperability above syntax and semantics.
— Charles Webster MD (@wareFLO) July 16, 2015
The next level up is called pragmatic interoperability. I’m very familiar with the words syntax, semantics, and pragmatics because I am ABD (All But Dissertation) in Computational Linguistics. I’ve written (and tweeted) extensively about pragmatic interoperability, and how it requires workflow technology to be accomplished, which is why I often call it workflow interoperability.
Let’s consider what “functional”, “user interface”, and “operational” mean in the context of pragmatic/workflow interoperability.
[need more here]
T3. How would such a unified medical record support patient engagement or activation, or facilitate self management of one’s own health?
[workflow -> life-flow, my WF tech and patient engagement paper]
Patient Experience And Engagement, Workflow And Workflow Tech: What Is The Connection?
T4. How would physicians and other clinicians engage with the data from such a record to enable both personalized medicine and population health?
[closed loop model of EHR productivity, my 2010 MedInfo South Africa, Cape Town paper here]
Clinical Intelligence, Complex Event Processing and Process Mining in Process-Aware EMR / EHR BPM Systems