Hi Thomas,
Correct me if I'm wrong:
If templates can specialize templates in several generations
of inheritance/specialisation (This is the case, right?), then
we could use the same basic annotation formalism for different
purposes in different layers, only the annotation names would be
different.
So an example inheritance/specialisation hierarchy in a
running system could be:
A bunch of clinical archetypes (mostly international, and
some regional ones)
...are used as building blocks in...
a "structural" template (maybe national/regional) often
creating a composite SECTION or COMPOSITION
[add more structural layers if useful]
all correct up to here
...that is then annotated with GUI-hints by...
a set of "GUI templates" with each template fitting a
different recurring use case
not forgetting that GUI is only one place to deploy a template (e.g.
messages etc), so there might be some other kind of 'deployment
templates' as well.
...for a specific GUI, the most fitting of those GUI
templates is then picked and might be further
annotated/specialized with yet another template layer or used
directly as input to GUI-generation or GUI-building tools
You describe a very big picture and sounds logic, so we'll have:
Level 1: archetypes (for model complete data sets about a concept, general and
specialized ones)Level 2: structural templates (for localized use of
archetypes, general and specialized templates)Level 3: define the use of the
structural templatesGUI Templates: define directives over a couple of
Structural Templates to create a graphic representations of some archetyped
data.
Message Templates: define directives to structure archetyped data into messages
with some syntax (HL7 v2, v3, 13606, CCR, CCD, CDA ...).
Report Templates: create reports with aggregated data and graphic
representations like charts. Can be used by GUI Templates.
Information Aggregation Templates: to define data aggregation rules over a set
of archetyped data. Can be used by GUI Templates, Report Templates, etc.
Rule Templates: to define rules over a set of archetyped data to check
validity, consistency, etc, etc. Can be used by Decision Support Modules, e.g.
to check medication reactions.
...
If the already present annotation mechanism in templates is
powerful enough (Do you think it is, Koray, Pablo and others?)
to be clear, do you mean the annotations documented in the ADL 1.5
draft document? I.e. the new annotations section?
I have a couple ideas that can improve what we've done on the EHR-Gen
framework. If you want I can put them in the wiki.
Cheers,
-Pablo.
- thomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20101214/13dec05e/attachment.html>
