Tim, if someone designs a template that has say a more limited set of Snomed or other codes on a field than the original archetypes had, then querying the data may be enabled with the template at hand, since it would tell you what (reduced) set of code values could be possible in that field. This is one of the most common uses of templates we are finding. I can imagine other thing, e.g. coding of fields that were just DV_TEXT in the archetype. In ADL 1.5-land, a template is just another layer of archetyping, with some extra features. This is distinct from any 'visual template' stuff, which I agree should be a distinct artefact and probably formalism.
- thomas On 01/12/2010 23:43, Tim Cook wrote: > On Wed, 2010-12-01 at 23:04 +0100, David Moner wrote: >> The important here is to distinguish ?specific use? from ?local use?. >> In my mind, a specific use is to define a use case where only a part >> of the archetypes or several archetypes are used. This is related to >> data structures. For example, to keep only the part of the blood >> pressure archetype that is important for the Primary Care measurement >> of vital signs. This specific use further constrains archetypes and >> these kind of structural templates should be also shared as the >> archetypes themselves since they will be needed to fully interpret the >> data. > Hmmm,I am very interested in hearing about a use case where these > templates are 'needed' to 'fully interpret' the data. > * * -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20101202/b526fff3/attachment.html>
