IMO annotating templates with UI info is not a good idea. A layered
approach is much cleaner and scalable, i.e. to define a new artifact on top
of current templates / archetypes / RM (these are also examples of layered
Under this approach, if we have UITemplates on top of openEHR Templates,
when we generate Operational UITemplates, that will contain UI + structure
(template and archetype constraints) + RM references. This would be the
final element to be used to feed software. but the underlying models are
all separated and have a specific responsibility.
If we go ahead, we can add another level for workflow, defining an order
and conditions under which each "screen" should be displayed, like a
WFTemplate, having an Operational WFTemplate that will include all WF + GUI
+ structure + RM references.
We can continue adding layers :)
On Mon, Feb 19, 2018 at 10:23 AM, GF <gf...@luna.nl> wrote:
> Is there a terminology with concepts we can use to annotate?
> Probably there is and there are more.
> Which one, will be the question.
> Gerard Freriks
> +31 620347088 <+31%206%2020347088>
> Kattensingel 20
> 2801 CA Gouda
> the Netherlands
> On 19 Feb 2018, at 07:00, Erik Sundvall <erik.sundv...@liu.se> wrote:
> sön 18 feb. 2018 kl. 23:10 skrev GF <gf...@luna.nl>:
>> Is it an idea to annotate nodes with instructions for display.
> Yes, using (mostly shared/standardised) annotations for GUI-rendering
> hints in templates (or layers of templates) has been a major idea in
> previous GUI-related discussions in openEHR mailing lists.
> (We should link to some old list posts on the topic in that wiki page Tom
> openEHR-technical mailing list
Ing. Pablo Pazos Gutiérrez
+598 99 043 145
Subscribe to our newsletter <http://eepurl.com/b_w_tj>
openEHR-technical mailing list