In Simple Interop: Use Cases we have made a somewhat unorthodox proposition, to support mixed communication between people and automatic computer processing programs. We have done so because of the issues raised in Rant on Heath Information Technology Asynchrony . This proposition entails solving some issues. For example, what if
- The email is never delivered to the recipient?
- The email is delivered but cannot be processed?
- The email is delivered but some of the attachments cannot be processed?
- A recipient later claims it never got a message and cannot be liable for not having acted on it?
- A sender later claims that it never sent a certain message, so it cannot be liable for erroneous contents?
- Some of the attachments associated with the message don’t contain a structured patient ID? How do we know they are all about the same patient? Is there a way to allow the same message to contain information about different patients?
- An automated message is routed to a recipient that is a person and needs some context to understand the messages.
There are probably other issues as well, and I look forward to hearing about them in the comments to this posting.
We believe that there are straightforward solutions to these issues that can be introduced without greatly adding to the amount of new technology that must be introduced to get started with this approach.
Read Complimentary Relevant Research
Predicts 2017: Artificial Intelligence
Artificial intelligence is changing the way in which organizations innovate and communicate their processes, products and services. Practical...
View Relevant Webinars
The Education CIO Challenge: IT Is a Team Sport
This video will outline key Education CIO challenges and recommendations based on business and technology trends in education as well...
Category: healthcare-providers interoperability vertical-industries
Tags: arra ehr health-information-exchange health-internet health-it healthcare-interoperability healthcare-providers hie meaningful-use nhin
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.