Semantic Interoperability Part I - Architectural scalability is the primary driver for adopting standards

I am always amused by statements saying that the system is only at the level of syntactic interoperability because it is not using standards for the data exchange, and it will be at level of semantic interoperability with the adoption of standards.

This kind of statement is not entirely true especially the second part, IMO, every two interconnected systems are semantically interoperable regardless of whether the data exchange is based on industry standards or not.

Let us look the IEEE's definition of Syntactic and Semantic Interoperability in the below figure.



Based on the above definition, as long as two interconnected systems function as per requirement, and satisfy the use cases, they are obviously qualified as "Semantic Interoperability" with one caveat - whether the capability is applicable for more participating systems.

This can be easily satisfied again as long as we mandate that every integration partner follows the existing data exchange specification, and the existing in-use data exchange specification eventually becomes the de-facto standards, which again is not bad thing at all. Every standard is originated from non-standard based implementation, just like what Spanish poet Antonio Machado said - "Travelers, there is no path, paths are made by walking."

Now back to the caveat earlier mentioned - whether the capability is applicable for more participating systems. Let's list out what are the factors that will affect our ability to apply the existing capability to another system and more.

1) The development effort required to replicate the capability to another system or more in the entire healthcare ecosystem
2) The ability for the existing integrated interface to adapt for future use cases
3) How do I choose the right standards for my solution


Please tune in for the Part II  and Part III in the following weeks to analyze what is the motivation for adopting industry standards, and what kind of standards you should be adopting considering the fact that healthcare standards arena is a complicated environment, there are good ones but also a lot of shady ones, or just simply being abused or misused.

In mean time, please let me know any comment or suggestion.

Effective enagement for information modeling for clients

Recently I am reading the book "Business Dynamics", found the following two paragraphs are extremely useful for any information modeller for effective engagement with the clients
 

To be effective the modelling process must be focused on the clients' needs. The clients for a modelling process project are busy. .... The care little for the elegance of your theory or cleverness of your model. Modeling is done to help the client, not for the benefits of the modeler. The client context and real world problem determine the nature of the model, and the modelling process must be consistent with the clients' skills, capabilities, and goals. The purpose is to help the clients solve their problem. If the clients perceive your model does not address their concerns or lose confidence in it, you will have little impact. Focus your modeling work on the problems that keep the clients up at night.

 On the other hand,

 Modelers should not automatically accede to clients' requests to include more detail or to focus on one set of issues while ignoring others, just to keep the clients on board. A good modeling process challenges the clients' conception of the problem. Modelers have a responsibility to require their clients to justify their opinions, ground their views in data, and consider new viewpoints.......

For more detail, pls get your copy and reading, you will benefit tremendously from this system thinking!

http://www.amazon.com/Business-Dynamics-Systems-Thinking-Modeling/dp/007238915X

The thought process is more important than the solution

During recent Ken Rubin's trip to Singapore in May 28, I shared my views and suggestions on how to effectively adopt/develop healthcare interoperability standards.

Instead of telling the audience what standards to adopt, and how to develop or extend standards. I used the approach as illustrated in the following two slides with the intention of helping the audience understand the thought process from architect's perspective, what are the considerations, and how to choose the applicable standards, and how to adopt and implement.

The reaction from the audience is mixed,most of them fully appreciated the sharing and learning points they got from the sharing, very few of them did not understand what I am trying to convey, and it turned out that for those did not fully understand, they did not have proper technical background or no programming background. So what does it tell?