Sunday, June 17, 2012

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!

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?

Tuesday, June 12, 2012

HL7 CDA Narrative Text

How do you handle narrative text in HL7 CDA? see discussion at the following blog
CDA Narrative Text

Monday, June 4, 2012

Discrepancy in HITSP C83 CDA Content Modules

I am reading through HITSP C83 - HITSP_v2.0.1_2010_C83_-_CDA_Content_Modules.pdf.  In section MEDICATION, it specifies the following mapping for medication,

A sample XML snippet is given below in 'additional specification'.

Based on the mapping table, I will assume that the correct XML snippet should be as following, with the 'code' element describing that this observation is for medication type data , and 'value' element describing the actual type of medication.

<entryRelationship typeCode='SUBJ'>
       <observation classCode='OBS' moodCode='EVN'>
           <templateId root='2.16.840.1.113883.' />
           <code code='xxxx' displayName='Medication Type'
                      codeSystem='xxxx' codeSystemName='xxxx' />
           <value xsi:type='CE' code='73639000' displayName='Prescription Drug'       
                                          codeSystem='2.16.840.1.113883.6.96' codeSystemName='SNOMED CT'/>

I think the sample medication XML needs to be updated.