Thomas Beale wrote: > Williamtfgoossen at cs.com wrote: >> www.zorginformatiemodel.nl has about 85 stroke patient related >> archetypes. >> unfortunately most are in Dutch, but we have translated about 10 to >> English now, most the simple ones or the ones that explain the >> approach also in more technical way. >> >> Key is the binding knowledge, variables, vocabulary, value set and >> unique coding for each element or node. >> >> William > William, > > these are not archetypes, they are HL7v3 RMIMs. It is confusing to > people if you call these archetypes - they don't obey the archetype > model, aren't expressed in the archetype language (ADL) and aren't > processible by the archetype tools....so I suggest we refer to them by > their real name...(of course, if they were archetypes, that would be > much nicer - we could share them outside the v3 message environment).
OK, I know this is an openEHR list, but nevertheless I don't think that openEHR can claim exclusive use of the word "archetype" to refer only to artefacts which are expressed in openEHR ADL. From such a claim it is a slippery slope to having to refer to them as archetypes?, archetypes(TM) or archetypes?. Strictly speaking, an archetype is not a set of specifications or constraints at all but rather (according to WordNet) "an original model on which something is patterned" - that is, the master **instance** of a thing, a prototype, from which specifications can be derived. openEHR seems to be using the term archetype in the later, Jungian sense of "an inherited pattern of thought or symbolic image that is derived from the past collective experience of humanity and is present in the unconscious of the individual". My practice has been to refer to "openEHR Archetypes" to clearly distinguish them from other uses of the English language word "archetype". Perhaps on this and other openEHR lists, the term archetype could be taken to mean "OpenEHR Archetype", and other types of archetype could be distinguished as necessary by suitable qualification, including the generic "non-openEHR archetype". But alternative uses of the term archetype should not be denied. Tim C
