Yes they are still 0.97 archetypes, but shouldn't they contain EVENT_CONTEXT 
according to the old 0.9 specifications? Anyway, I'm glad that the release 1.0 
archetypes are being published soon. I've had a look at some of the new 
COMPOSITION archetypes and they seem to follow the specifications better.

Thanks,

Mattias
  ----- Original Message ----- 
  From: Sam Heard 
  To: openehr-technical at openehr.org 
  Sent: Wednesday, April 12, 2006 2:27 PM
  Subject: Re: Question about Composition archetypes


  Mattias
  The Ocean archetypes are still 0.97 - we have updated all of them and will 
have the release 1.0 tools and archetypes available very shortly. 
  The editor, alpha, on the Ocean site will create them in the release 1.0 form.
  Cheers, Sam

  Mattias Forss wrote: 
    Hello, 

    I've just compared some Composition archetypes from Ocean Informatics with 
the specifications at openEHR.org and I have some questions. The specifications 
from 0.9 to 1.0 all agree about one thing for COMPOSITION classes and that is 
that the attribute "context" in the COMPOSITION class should point to a class 
called EVENT_CONTEXT. 

    However, this is not the case for the archetypes I've seen so far. Instead, 
the "context" attribute in the archetypes matches subclasses of ITEM_STRUCTURE 
e.g. ITEM_TREE. These classes should instead be referred by an optional 
attribute called "other_context" inside the EVENT_CONTEXT class. Can anyone 
please explain to me why this is the case? 

    Regards, 

    Mattias 




  -- 

  Dr. Sam Heard
  MBBS, FRACGP, MRCGP, DRCOG, FACHI
  CEO and Clinical Director
  Ocean Informatics Pty. Ltd.
  Adjunct Professor, Health Informatics, Central Queensland University
  Senior Visiting Research Fellow, CHIME, University College London
  Chair, Standards Australia, EHR Working Group (IT14-9-2)
  Ph: +61 (0)4 1783 8808
  Fx: +61 (0)8 8948 0215



-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20060412/86e6edde/attachment.html>

Reply via email to