Re: Templates for application form development

On 18-02-18 23:09, GF wrote: Is it an idea to annotate nodes with instructions for display. Personally I think having special templates/archetypes for display is better. Templates are create per purpose, and mixing purposes in a single template does  seem good idea to me

Re: Templates for application form development

Personally I would prefer if no visualization attributes ended up in the EHR RM, but I'm fine if we want to create an additional RM to handle visualization (and we create templates of that model that point to the EHR model) 2018-02-19 10:15 GMT+01:00 Bert Verhees : > On

Re: Templates for application form development

On 19-02-18 10:21, Diego Boscá wrote: Personally I would prefer if no visualization attributes ended up in the EHR RM, but I'm fine if we want to create an additional RM to handle visualization (and we create templates of that model that point to the EHR model) I agree on this! (again

Re: Templates for application form development

It can be that Compositions appear in a single GUI-form (in GP applications this happens regularly), but there is still no need to to show them from a single template. That can be up to the GUI-designer, he can use HTML-features to handle one or more entries in a single GUI-view. Having the

Re: Templates for application form development

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 gf...@luna.nl Kattensingel 20 2801 CA Gouda the Netherlands > On 19 Feb 2018, at 07:00, Erik Sundvall

Re: Templates for application form development

Hi! I agree that in many use-cases it is better to have a separate template intended for GUI/application hints overlayed on a "normal" data content definition template. (Quick experimentation may be an exception.) That is why I added "layers of templates" in my previous comment - sorry for not

Re: Templates for application form development

note that a key problem I want to address is that templates based on COMPOSITIONs don't really make sense as models of data retrieval/display forms - they are really only useful for data capture forms (or messages, or documents), because COMPOSITION is a container for committing data to the

Re: Templates for application form development

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 design). Under this approach, if we have UITemplates on top of openEHR

Re: Templates for application form development

Yes, this is about two different problems 1. having extra RM structures tree be used to group RM data in different ways than the one defined for a composition, in order to use y as a data retrieval for APIs and GUI. 2. another level of definition, above OPTs, to specify GUI structures and

Re: Templates for application form development

Often Spanish is not always a big problem, let us try drag through Google translate to make it al readable Bert On 19-02-18 17:37, David Moner wrote: We also have a Final Degree Project where a student made a proposal for a Visual Template Model. It's from 2012, for ISO 13606, and also in

Re: Templates for application form development

We also have a Final Degree Project where a student made a proposal for a Visual Template Model. It's from 2012, for ISO 13606, and also in Spanish, but the main idea probably remains the same :-) I've been always in favor of having a third layer for visualization purposes that defines some of

Re: Templates for application form development

I was reviewing that work, and I found it cited this reference. This is an old topic... H. van der Linden, T. Austin, J. Talmon, Generic screen representations for future-proof systems, is it possible? There is more to a GUI than meets the eye, Comput Methods Programs Biomed. 95 (2009) 213–226.

Re: Templates for application form development

In fact David, the work is about how an interface should look like, that is interesting for GUI designers. But the discussion here is not about GUI design but about offering a technical environment to GUI designers. Bert Op 19 feb. 2018 17:57 schreef "David Moner" : I was