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.
Category: Healthcare Providers Interoperability Vertical Industries Tags: ARRA, EHR, Health Information Exchange, Health Internet, Health IT, Healthcare Interoperability, Healthcare Providers, HIE, Meaningful Use, NHIN