Wednesday, June 13, 2012

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?


  1. While I don't have the complete context, I can certainly appreciate the complexity of making any suggestions around "thought-process" vs. jumping to the psychology to jump to the solution space. I would also suggestion to add the "who" question to your key questions of "what are the considerations, and how to choose the applicable standards, and how to adopt and implement". Getting the "who" needs to ask and "who" needs to answer what question and "why" is probably going to give a different result :-) Callum

  2. ood suggestions though I don't fully understand your comments, maybe because it is late night :) But I guess you are referring to the stakeholders.

    In fact in order to ask some questions for Martin Folwer's talk the week after, btw this is the first time he came to Singapore, huge turnout. I reread some of this old articles, so I was probably influenced by him. His points are still very valid after 10 years.

    I suggest everyone who involved or intends to be involved in interoperability standards should read his articles.