I generally agree.  However, I thin k it depends on the higest level to
which the archetype is defined.  Some are carrying architypes to a complete
collection of data for a disease encounter, any encounter and a medical
record.  Obviously some data elements would appear in more than one
archetype.  I view archetypes as more for data collection and some data
presentations rather than an architectural model for the EHR, although in
some cases I would keep the data bundled.  In any case, navigation of the
database is the issue.

I have left my emeritus status and returned to full time at Duke.  I am the
Director of the Center for HEalth Informatics which involves both teaching
a informatics research.  My time with HL7 will probably be limited.  My
focus will be more on standards for the clinical commun ity.

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: Decision Support Providers      
                                                                           
                                                                           
             06/27/2010 06:00                                              
             AM                                                            
                                                                           
                                                                           
             Please respond to                                             
                For openEHR                                                
                 technical                                                 
                discussions                                                
             <openehr-technica                                             
              l at openehr.org>                                               
                                                                           
                                                                           





Ed,

 this is an interesting technical point. One key aspect of the archetype
approach is the heavy use of dependable paths through the data for
querying. It means you can always get to the finest grain item, regardless
of whether the data stay as a 'package' or not. This is the kind of
flexibility that I think would be useful in your environment.

- thomas

On 26/06/2010 22:34, William E Hammond wrote:
      Actually, my e-mail was more of a hello.  I didn't think you were
      giving
      Duke a hard time.  Our approach is similiar to what you are doing,
      however,
      we are focusing at the atomic level.  Building from that is simply a
      construct.  It will be i nteresting to find out what stays packaged
      and
      what breaks out.  My approach is to make the data independent of the
      construction.  If the data element is never dealth with without thw
      full
      structure we will keep it packaged; else not.  I think we let our
      experiences influence how we move forward.  But as you know, I try to
      pay
      attention to what everyone is doin g so I can use the best
      approaches.


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



Reply via email to