Specialisation do we need archetype specialisations
Dear all, As an other layman my two cents to the discussion. Specialisation Since archetypes express what can be maximally documented about a topic, and because in the Template the archetype can be constrained maximally to fit the local context at that point in time, I think there is almost no need for specialization. In the example given below. It is clear that both BW and BWB example at the same time Body weight and Body weight at the time of birth can be generically handled and do not need specialization. Body weight change is always relative to an other measurement. I see no reason why these aspects of what can be documented around the topic Body weight can not be in the same archetype. At Template design time the appropriate attributes will be selected or deselected. A possible example There is the generic Weight archetype as an Observation. Expressing all that can be documented about any weight observation. And then we define a specific specialized one for Body weight or Organ weight or thumb weight or compound weight, etc, etc, etc I do not think this is the way to go. The world is large and to many specialization's will be produced. I think it is wrong to have an archetype called Body weight. We only need ONE about all aspects of WEIGHT of anything. My line of thinking is: When all that can be documented about a concept is defined in an Archetype and the concept is weight than the topic is about weight measurement of anything. Within the archetype there must be an attribute what the focus of the concept is. So we must be able to indicate in an archetype attribute whether this a person or a thing. It must be possible to indicate what is observed. At the Template level I see specialized Sections be constructed containing generic archetypes. Archetypes that define precisely in the context of measurements in newborns and grownups what will be documented about weights. I'm curious to learn what are the real use cases for Archetype specialization. I see the need for specialization in the Template phase under control of the knowledge domain. In the meantime the tools must be able to support specialization. Gerard -- private -- Gerard Freriks, MD Huigsloterdijk 378 2158 LR Buitenkaag The Netherlands T: +31 252544896 M: +31 620347088 E: gfrer at luna.nl Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. Benjamin Franklin 11 Nov 1755 On Dec 14, 2007, at 8:39 AM, Daniel Karlsson wrote: Dear Everyone, actually I was going to re-state the questions to the technical list, but will cross post it to the clincial (will I be banned???). For the clinical list read the original message below: For the technical list, I would still like to have the details of specialisation laid out. Are constraints inherited and thus implicit in the specialised archetypes' definitions? Then, in the BW/BWB example, are also the weight gain/loss inherited (which according to my layman understanding is not very sensible for birth weight). Clear semantics of specialisation would be necessary to bring further any discussion on support from tools in this area. /Daniel Daniel Karlsson, PhD Department of Biomedical Engineering/Medical Informatics Link?pings universitet SE-58185 Link?ping Sweden -- next part -- An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20071214/93e9cf9a/attachment.html
Specialisation
Daniel Karlsson wrote: Dear Everyone, actually I was going to re-state the questions to the technical list, but will cross post it to the clincial (will I be banned???). For the clinical list read the original message below: For the technical list, I would still like to have the details of specialisation laid out. Are constraints inherited and thus implicit in the specialised archetypes' definitions? Then, in the BW/BWB example, are also the weight gain/loss inherited (which according to my layman understanding is not very sensible for birth weight). Clear semantics of specialisation would be necessary to bring further any discussion on support from tools in this area. Only just saw this. This is correct, and an implementation of specialisation is underway in the Archetype Workbench, which will result in specialised archetypes being represented in a differential form rather than the present 'flat' form, where inherited constraints are copied in. The existing document on semantics will be updated to reflect details not already published. However, the basic approach is similar to object-oriented programming languages: - constraints are inherited, and can be overridden - overrides are 'covariant' i.e. the constraints are narrower than the parent, also can be thought of as 'subsumed' - new constraints can be added where allowed by the parent archetype and reference model There are of course a number of fine details that need to be documented. In the new version of the workbench tool, the entire archeytpe repository will be compiled like a system of object classes, with proper validation of specialisation relationships. hope this helps. - thomas beale
Archetype production: Types of Archetypes
A few thoughts about Types of Archetypes Archetypes are constraints on an UML model. Archetypes define what can be documented about a topic. Templates are Archetypes. Archetypes are not Templates because Templates are the aggregated archetypes, collected and further constrained to suit a specific business context. In order to reduce possibilities for confusion we need to become more clear what we mean. Semantic interoperability and confusing meanings of things do not go well together. Types of Archetypes Templates: Archetypes suiting the needs of a specific business case/context, constraining parts of the EN13606 or OpenEHR Reference Model, the Folder class, the Composition class and Section Class, plus, in addition, constrain included Entry Archetypes that are parts of the Sections. Entry Archetypes: Archetypes that in general collect what can be documented in general about a health concept using Cluster Proto-Archetypes and Element Proto-Archetypes. There are: Demographic, Observation, Evaluation, Instruction and Action Entry Archetypes. [Question: What type is a Patient Mandate Archetype?] Cluster Proto-Archetype: Archetypes that in general collect/unite two or more elementary archetypes Elementary Proto-Archetype: Archetype that defines one aspect of an Entry Archetype Re-Use Re-use will take place at the Template Level (ieTypes of documents in other documents, types of sections in other sections, etc) All these reflect business needs Re-use will take place at the Template Level by using Entry Archetypes. Reflecting interoperability needs Re-use will take place within the Entry Archetype by means of generic Proto-Archetypes. Reflecting interoperability needs. Gerard -- private -- Gerard Freriks, MD Huigsloterdijk 378 2158 LR Buitenkaag The Netherlands T: +31 252544896 M: +31 620347088 E: gfrer at luna.nl Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. Benjamin Franklin 11 Nov 1755 -- next part -- An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20071214/8b33b8b6/attachment.html
