I definitely agree with this separation into what you call structural and visualization templates.
It would be really nice if the structural ones became a reality and were implemented into for instance the Java reference implementation. These were almost finished a couple of years ago and seem to still be almost finished. Then one could use these as the basis for looking into ways of doing the visualization templates. This would be cleaner then having many different variations on the structural templates with different kinds of hints etc. Olof Torgersson --- Olof Torgersson Associate Professor Department of Applied Information Technology Chalmers University of Technology and G?teborg University SE-412 96 G?teborg, Sweden email: oloft at chalmers.se<mailto:oloft at chalmers.se> phone: +46 31 772 54 06 1 dec 2010 kl. 23.04 skrev David Moner: We had a similar discussion at the EN13606 web page. These are the conclussions I got. We should distinguish two types of templates: - Structural templates (specific use). Artefacts that constrain archetypes for specific uses or aggregate them in order to build more complex structures. These are the current openEHR templates. - Visualization templates (local use). These are a new idea. Local templates are just for visualization configuration (for example, positioning of the elements, definition of the size of a field, selection of a visual representation for a class or selection of the interface language). 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. On the other hand, a local use is when you define constraints that are only useful for your own use or specific system. This is related to GUIs. These visualization templates are not meant to be shared outside your institution. ADL 1.5 is enough for defining the structural templates. Visualization templates needs something else to be defined. I would not recommend the use of those GUI-directives mixed with the structural templates, but to define a new level (maybe a specific model) for them. As some of you said, maybe these visualization or local templates do not need to be a part of "standardized" architecture since they are local implementations, but I think that it is possible to design a kind of common framework to deal with them together with archetypes and structural templates. David -- David Moner Cano Grupo de Inform?tica Biom?dica - IBIME Instituto ITACA http://www.ibime.upv.es<http://www.ibime.upv.es/> Universidad Polit?cnica de Valencia (UPV) Camino de Vera, s/n, Edificio G-8, Acceso B, 3? planta Valencia ? 46022 (Espa?a) <ATT00001..txt> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20101202/7126e74c/attachment.html>
