Add template capability to AM


A formal definition of the template model is required in the openEHR
AM to enable software to be built on archetype and template
principles already described.


(Sam Heard) inactive
July 14, 2009, 5:34 AM

I want to push for a clear separation of templates and archetypes. I understand the technical benefits from a single constraint model - but I want to make sure that we have two distinct processes:

1. Clinical models: Archetypes: Semantics for interoperability - fixing the absolute limits of what can be recorded - these have to be shared to achieve semantic interoperability
2. Messages, documents, encounter records, questionnaires: Templates: Limiting scope of what is to be shared for communication or for a specific use, data entry, integration or other scenario

In particular I propose that:
1. There are no ontologies in templates (translation via the C_STRING attribute)
2. Embedded templates and further constraints on embedded templates are legal (ie not a differential)
3. Template process is kept as simple and clean as possible

Thomas Beale
May 16, 2016, 2:23 PM

Implemented within AOM in 2014


Thomas Beale

Raised By

Thomas Beale


Affects versions