On 14/06/2013 10:54, Gerard Freriks wrote: > Templates are mostly EHR-EXtracts with Compositions inside.
I imagine that is probabaly true in 13606-land. It's so far uncommon in openEHR, but should be used more, and I think will become common with the growing use of the openEHR EHR Extract <http://www.openehr.org/wiki/display/spec/openEHR+EHR+Extract>. There is an example of a templated openEHR Extract <https://github.com/openEHR/adl-archetypes/tree/master/Example/openEHR/ehr_extract_template> in the openEHR test archetypes. > >> > > When specializing an archetype the name (and meaning) changes. > When originally the Name node is ENTRY it can be changed in > specialization to ENTRY:Observation > Or into ENTRY:Observation:ClinicalFinding > Or into ENTRY:Observation:ClinicalFinding:BodyTemperature > > The names are different and therefore their meanings. > Although all names are related to each other. In openEHR, the name attribute is not what is being constrained; it is the archetype_node_id, i.e. the coding of each attribute. That guarantees that specialisation is computable, and not a function of language or string processing (I'm not sure if that is what you are implying with things like "ENTRY:Observation:ClinicalFinding:BodyTemperature" above). - thomas -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130614/02143ac8/attachment.html>
