Hi All, I've read similar work before starting with our design and found Thilo's prior work very relevant and well researched. This MIEUR 2006 paper describes a new layer of GUI model using Mozilla XUL - an XML based open web layout standard. AT the time of writing templates were not out there yet and from his discussion I reckon much of the GUI definition could be handled by templates. I now agree that pure GUI stuff must be represented elsewhere - but at the moment we find template annotations quite useful and sufficient. Be aware that our app is a Winforms one - not Web based. So the kind of GUI rules might differ from others which are almost all Web based.
And one note to Thomas: we actually use templates for defining a minimum data set (yes not a maximal) for the purpose of reporting...So w have both data entry/validation and reporting layout issues. Not messaging though but we are planning to transform the openEHR instance of endoscopy report into CDA and exchange with HL7 V2.x in near future. Cheers, -koray From: openehr-technical-bounces at openehr.org [mailto:openehr-technical-boun...@openehr.org] On Behalf Of pablo pazos Sent: Thursday, 9 December 2010 7:39 a.m. To: openehr technical Subject: RE: GUI-directives/hints again (Was: Developing usable GUIs) Hi Ian, If I understand what Thomas said "I would suggest that the GUI templates just reference paths found in the openEHR template", the paths in a GUI Template will come "only" from openEHR templates (the structural ones), not from archetypes (this is apart from that they are technically the same thing). I think in ADL 1.4 the template specification is not complete, I would say that in 1.4 Templates are not so clear Archetype specializations. In ADL 1.5 is more clear the relationship of Templates and Archetypes. What I meant in the previous mail was: for us who have developed applications over ADL 1.4, our GUI Templates will use paths "directly" from Archetypes, instead of paths from openEHR structural Templates. -- Kind regards, A/C Pablo Pazos Guti?rrez LinkedIn: http://uy.linkedin.com/in/pablopazosgutierrez Blog: http://informatica-medica.blogspot.com/ Twitter: http://twitter.com/ppazos > From: Ian.McNicoll at oceaninformatics.com > Date: Wed, 8 Dec 2010 17:30:38 +0000 > Subject: Re: GUI-directives/hints again (Was: Developing usable GUIs) > To: openehr-technical at openehr.org > > Hi Pablo, > > In both ADL1.4 and 1.5 every path is still an archetype-based path. > The proposed schema for an operational template is very similar to the > XML schema of an individual archetype but obviously includes multiple > aggregated archetypes and omits any nodes which are constrained out. > > Templates are technically identical to specialised archetypes. The > difference is that specialised archetypes support templating features > such as constraining out unwanted elements and aggregating archetypes. > > The only difference between an archetype and a template is that new > content i.e. new nodes or terms cannot be added to a template. > > Ian > > Dr Ian McNicoll > office / fax +44(0)1536 414994 > mobile +44 (0)775 209 7859 > skype ianmcnicoll > ian.mcnicoll at oceaninformatics.com > > > Clinical analyst, Ocean Informatics > openEHR Clinical Knowledge Editor www.openehr.org/knowledge > Honorary Senior Research Associate, CHIME, UCL > BCS Primary Health Care SG Group www.phcsg.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20101210/94dfad1d/attachment.html>
