Hi Olof, I agree but I think there are some directives that are actually not purely GUI directives but which say something meaningful about the underlying information.
For instance Koray's directive isCoreConcept (g): "This is an abstract concept; but we can say that Core Concepts are real-world entities which we can talk about their abscence (i.e. a clinical finding, a disease but not tumour grade or physical examination). The directive depicts whether a node with all its children (if any) shall be handled and repeated as a whole in an archetype (i.e. makes sense together such as a clinical finding with other attributes defining its nature). When the node and/or its children are selected, its presence information is stored in the corresponding ELEMENT node which records this (i.e. in MST Findings archetypes [Present?] node)." This seems to me to represent some sort of association between a parent concept and potential children which is independent of any GUI representation. These, I believe, should be considered for inclusion within archetypes/templates. Ian Dr Ian McNicoll office / fax? +44(0)1536 414994 mobile +44 (0)775 209 7859 skype ianmcnicoll ian.mcnicoll at oceaninformatics.com Clinical analyst,?Ocean Informatics openEHR Clinical Knowledge Editor www.openehr.org/knowledge Honorary Senior Research Associate, CHIME, UCL BCS Primary Health Care SG Group www.phcsg.org On 6 December 2010 10:36, Olof Torgersson <olof.torgersson at chalmers.se> wrote: > 5 dec 2010 kl. 18.04 skrev Thomas Beale: > > On 05/12/2010 16:49, Tim Cook wrote: > > I personally think it makes it simpler for everyone to think of templates as > only being used for 1. slot-filling 2. removal of unneeded optional data > points and 3. tightening of some leaf value constraints, nearly always coded > terms. If it turns out that data node additions make sense, we will deal > with it when a true need is clear. > > > Returning to the original topic of what should go into a template, I would > say that this statement supports that template should not > contain GUI-directives, but that such information should go into a special > visualization layer? > regards > Olof > > > - thomas > > > <ATT00001..txt> > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical > >
