Your experiences are different than mine.  I must confess that I have not
been in any HL7 meeting which included shouting down.  Disagreements - yes;
but not shouting down.  In any case, The problem with kicking out the
non-modelers is that I am not sure who defines the experts - we ourselves?
I am not smart enough to think I know all the answers - or perhaps I should
say I am smart enough to know that I do not know all the answers.  I
strongly believe in the democratic process.  My knowledge of other
approaches have always lead to disaster.  mI also have no problem with
disagreements.  In fact, I think we find better solutions when we disagree.
But disagreements demand respectful discussions.  I would think much of the
world would not accept your comment about proper design.
W. Ed Hammond, Ph.D.
Director, Duke Center for Health Informatics


                                                                           
             Thomas Beale                                                  
             <thomas.beale at oce                                             
             aninformatics.com                                          To 
             >                         openehr-technical at openehr.org       
             Sent by:                                                   cc 
             openehr-technical                                             
             -bounces at openehr.                                     Subject 
             org                       Re: HL7 modelling approach          
                                                                           
                                                                           
             11/25/2010 11:40                                              
             AM                                                            
                                                                           
                                                                           
             Please respond to                                             
                For openEHR                                                
                 technical                                                 
                discussions                                                
             <openehr-technica                                             
              l at openehr.org>                                               
                                                                           
                                                                           





Ed,

that's the whole problem with these standards committees: they are full of
people whose competence is not modelling or engineering, and who don't see
the downstream consequences of their choices, and in any case, the
'democratic' committee process largely prevents proper design occurring.
People just object to whatever, country X demands that a certain attribute
be renamed... it just comes down to who came on the day and who shouts
loudest.

I came to HL7 meetings for 5 or 6 years, and followed all the required
process (well, except the shouting down in meetings, sorry I am not into
that), and it had no effect. I know many many people who have said the same
thing, including people in key positions in e-health programmes around the
world.

- thomas


On 25/11/2010 17:26, William E Hammond wrote:
      OK.  I accept the comment.  However, the problem I have is that many
      of the
      comments are a matter of opinion - that's ok, but it is not a right
      or
      wrong.  If the issues were balloted, by shere numbers HL7 would come
      out
      ahead.  The comment of attributes in quotes and the comment
      incorrectly
      named does not make your point.

      If you want HL7 to respond to your critiques, sedn them to the TSC or
      HL7
      leadership.


_______________________________________________
openEHR-technical mailing list
openEHR-technical at openehr.org
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical



Reply via email to