Hi Josina,

My comments about 'pure' and 'pragmatic' modelling were regarding archetypes
rather than templates.

It is the archetypes that need governance to support interoperability, and
in general for this we need a 'purer' approach.  But there are times when an
archetype can be built for a specific local purpose for which there is no
need to share, or something practical and purpose-driven like the (now
famous) example of the Barthel index - utilizing a more pragmatic approach.

Templates don't need governance in quite the same way.  It is true that
anyone can build any template for any purpose, and as long as they use
widely accepted/agreed archetypes then the template can achieve its purpose.
Hence governance for archetypes is the key.

But in a practical sense, a discharge summary and a prescription and an
antenatal consultation all have very similar component archetypes wherever
they might be used.  It would make sense that we don't have every ward in
every hospital in every country create a discharge summary template from
scratch.  That would be duplicating work in a hugely inefficient way.  So
from my point of view it should be our goal to facilitate the sharing
templates - so that a hospital might take an existing discharge summary
template and then each ward or consultant can use this as the basis for
their own preferred way of representing patient discharge data.  

I definitely don't think we will get agreement on 'THE discharge summary
template' - and we will not be seeking to do so.  However I will be seeking
to collect examples of 'good' templates in use from diverse use-cases,
domains and geographical locations so that these can potentially be shared
and adapted for local use.  This is proposed as (not too far in the) future
functionality for the openEHR knowledge repository.

Hope this helps


-----Original Message-----
From: openehr-technical-boun...@openehr.org
[mailto:openehr-technical-bounces at openehr.org] On Behalf Of J.P. Freriks
Sent: Tuesday, 1 July 2008 12:24 AM
To: For openEHR technical discussions
Subject: Re: GUI-hints in openEHR templates? (Was: PatientOS archetype to
form demo (of sorts))

Is it true that there are two types of templates: generic ones like 'lab 
request' (which contains a combination of several archetypes), and a 
further constrained version for local usage?
If so, this might mean that clinicians that are trained in openEHR could 
design the first kind of templates (like Heather Leslie proposed); while 
'local' clinicians will decide in (I believe, but correct me if I'm 
wrong: preferably) one and the same session about the local template and 
UI features.
Or, are templates generally speaking too specific to local practice (so 
that each template has to be designed locally) to make the above 


Gerard Freriks schreef:
> My spectrum:
> - Archetypes (generic documentation patterns)
> - Templates (context dependent documentation patterns)
> - Generic User Interfaces (generic presentation patterns)
> - User Interface (context dependent presentation patterns)
> Gerard
> -- <private> --
> Gerard Freriks, MD
> Huigsloterdijk 378
> 2158 LR Buitenkaag
> The Netherlands
> T: +31 252544896
> M: +31 620347088
> E:     gfrer at luna.nl <mailto:gfrer at luna.nl>
> Those who would give up essential Liberty, to purchase a little temporary 
> Safety, deserve neither Liberty nor Safety. Benjamin Franklin 11 Nov 1755
> On Jun 30, 2008, at 3:19 PM, Erik Sundvall wrote:
>> Hi!
>> Thanks for a lot of interesting response regarding "GUI-hints" and 
>> other things.
>> Please excuse a little left-to-right analogy below:
>> There seems too be a scale or spectrum of detail level and use case
>> specificity going from...
>> Left: purely semantic (maximum data set) models = archetypes
>> ...via the nearby...
>> openEHR templates (still purely semantic if we skip the "hide_in_ui"
>> to keep the template artifacts)
>> ...further far away to...
>> Right: actual GUI in an implemented system with specific widgets 
>> positioning etc
>> Currently openEHR specifications describe artifacts at the "left" side
>> of the spectrum. This discussion has interestingly been broadened
>> further to the "right" than I was thinking of in my initial questions.
>> If we look at a tool like the Template Designer from Ocean Informatics
>> there is an immediate jump from templates (close to the left) to
>> detailed GUI layout (far right), that jump could be divided into more
>> steps (possibly with some steps persisted and reusable) as suggested
>> by some in this discussion.
> ------------------------------------------------------------------------
> _______________________________________________
> openEHR-technical mailing list
> openEHR-technical at openehr.org
> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
openEHR-technical mailing list
openEHR-technical at openehr.org

Reply via email to