Andrew & Ogi, openEHR Templates are not Forms, they are aggregations of archetypes with further constraints. The scope of an openEHR template can be compared with a form but define the data structure of that form. However openEHR Templates can be used to drive the design and generation of forms as is done using the Ocean Template Designer. The designer has a Template Design panel where archetypes are dragged from a archetype repository view onto the panel building up the template structure and the archetype nodes are constrained as required in the template. The Form Design panel allows nodes from the Template to be dragged onto the Form and formatted as designed. This latter step is purely an application customisation step whereas the former template design is a knowledge development step possible used by more than one application.
Heath > -----Original Message----- > From: openehr-clinical-bounces at openehr.org > [mailto:openehr-clinical-bounces at openehr.org] On Behalf Of > Andrew Patterson > Sent: Tuesday, 20 February 2007 11:06 PM > To: Ognian Pishev; For openEHR clinical discussions > Subject: Re: CCR and openehr > > > implementation spaces. Archetypes as clinical model exist > independent > > of their potential use. Templates are the visual forms created for > > particular applications. Thus it would be possible to > create different > > versions serving the same purpose - in this case the visual > representation of a CCR form. > > Is this all that templates are though? If the distinction is > purely that templates are a method for specifying the user > interface aspects of archetyped data (i.e. this should be a > combobox pick list etc) then that is a distinction I can > understand. However, the CCR is not a specification of a > particular 'interface' or even 'form'. Its a clinical model > of data that needs to be recorded - exactly the type of thing > I would think would be archetyped first and foremost > (obviously if someone wanted to specify a 'user interface' in > some standard they could do that - but I would think the > primary artifacts that would be released by standards bodies, > NHS etc would be archetypes - vendors can work out interfaces > on their own can't they?) > > Andrew > _______________________________________________ > openEHR-clinical mailing list > openEHR-clinical at openehr.org > http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-clinical > _______________________________________________ openEHR-clinical mailing list openEHR-clinical at openehr.org http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-clinical