in a cluster
or multiplicity has been constrained.
Heath
From: openehr-technical-boun...@openehr.org
[mailto:openehr-technical-bounces at openehr.org] On Behalf Of David Moner
Sent: Thursday, 26 January 2012 9:16 AM
To: For openEHR technical discussions
Subject: Re: pass_through attribute in ADL 1.5
Hi Pablo,
If I understand correctly, the pass_through attribute is only for data
displaying on a screen (as you mention the use for data grouping or
collapsing). If that's right, I don't think that should be part of the
generic template structure, because templates are meant to represent other
In fact, the emphasis attribute of 13606 is a CV.
2012/1/26 Diego Bosc? yampeku at gmail.com
but they won't show everything on a 'full' GUI either. Maybe what is
needed is not only a boolean but a way to tell exactly the criteria
with different values of a controlled vocabulary, such as
On 25/01/2012 22:45, David Moner wrote:
2012/1/25 Thomas Beale thomas.beale at oceaninformatics.com
mailto:thomas.beale at oceaninformatics.com
Maybe another way of understanding this flag is as 'this node can
be skipped without loss of meaning'. I would be very interested to
On 25/01/2012 23:03, David Moner wrote:
Following this new sense for it, I think that the implications for a
GUI or visual representation would depend on a decision of the
implementers. If the screen space is reduced, they could opt for just
showing the clinically relevant data and leave
Hi Heath!
Just for the record, I think as Diego: I don't have a problem to have the
pass_through attr on templates right now, but we have to comment possible
issues with this and other attributes to improve templates in the future. The
pass_through view constraint is not a GUI directive, it is
If we had a 'GUI template' facility in openEHR, I am not 100% sure that
this pass-through setting would go into it. It's not GUI-specific, but I
think it probably is 'presentation-specific', i.e. GUI, reports, any
rendering of data onto a display device. Not all display devices are
active
-technical at openehr.org
Subject: Re: pass_through attribute in ADL 1.5
If we had a 'GUI template' facility in openEHR, I am not 100% sure
that this pass-through setting would go into it. It's not
GUI-specific, but I think it probably is 'presentation-specific
2012/1/25 Thomas Beale thomas.beale at oceaninformatics.com
Maybe another way of understanding this flag is as 'this node can be
skipped without loss of meaning'. I would be very interested to know if we
should make AQL queries sensitive to this flag. Has anyone thought about
that?
In this
Would this attribute value change depending on where is the archetype
used? i.e. if we use it on a GUI of a smartphone rather than a
standalone or web application
2012/1/25 David Moner damoca at gmail.com:
2012/1/25 Thomas Beale thomas.beale at oceaninformatics.com
Maybe another way of
at openehr.org] On Behalf Of pablo pazos
Sent: Thursday, 12 January 2012 9:24 AM
To: openehr technical
Subject: RE: pass_through attribute in ADL 1.5
Hi Heath,
Hi Paplo,
Your suggestion here is too oriented to GUI uses cases. As Tom indicated,
pass_through is intended to support other data oriented
Hi Diego
On 11/01/2012 03:12, Diego Bosc? wrote:
If it is really needed for the moment for representing templates then
it's OK with me (as long as we agree that this is a temporal thing),
but I still feel that having two separated places to rule UI
generation is a bad idea.
I think that
On 13/01/2012 08:46, Diego Bosc? wrote:
visible, allowed types, icon...
ok - I understood those were settings relating to the display of that
kind of node within the modelling tool, not of the data in a deployed
system so its about data? What does icon mean then?
- thomas
No, but they can be used for different things, from creating specific
editors, to mindmaps or sample GUI generation
2012/1/13 Thomas Beale thomas.beale at oceaninformatics.com:
On 13/01/2012 08:46, Diego Bosc? wrote:
visible, allowed types, icon...
ok - I understood those were settings
/
Twitter: http://twitter.com/ppazos
Date: Mon, 9 Jan 2012 19:03:32 +
From: thomas.beale at oceaninformatics.com
To: openehr-technical at openehr.org
Subject: Re: pass_through attribute in ADL 1.5
On 05/01/2012 08:54, Diego Bosc? wrote:
Put a couple
: http://twitter.com/ppazos http://twitter.com/ppazos
--
Date: Mon, 9 Jan 2012 19:03:32 +
From: thomas.beale at oceaninformatics.com
To: openehr-technical at openehr.org
Subject: Re: pass_through attribute in ADL 1.5
On 05/01/2012 08:54, Diego Bosc? wrote:
Put
Hi Heath,Hi Paplo,
Your suggestion here is too oriented to GUI uses cases. As Tom indicated,
pass_through is intended to support other data oriented contexts such as
flattening schema and class hierarchies, this is why is was generalised from
hide-on-form as used in the template designer.
In
Hi! From: yampeku at gmail.com
Date: Wed, 11 Jan 2012 10:12:39 +0100
Subject: Re: pass_through attribute in ADL 1.5
To: openehr-technical at openehr.org
If it is really needed for the moment for representing templates then
it's OK with me (as long as we agree that this is a temporal thing
On 05/01/2012 08:54, Diego Bosc? wrote:
Put a couple of comments on the wiki, but I think it is a thing that
should be discussed on the list.
In ADL 1.5 a flag 'pass_through' was added. Its definition is 'Allows
nodes required for structuring data but otherwise redundant for screen
display
: Tuesday, 10 January 2012 8:04 a.m.
To: openehr-technical at openehr.org
Subject: Re: pass_through attribute in ADL 1.5
On 05/01/2012 08:54, Diego Bosc? wrote:
Put a couple of comments on the wiki, but I think it is a thing that
should be discussed on the list.
In ADL 1.5 a flag 'pass_through
Why don't we use the new annotations feature to handle these type of
concerns? You can put pretty much anything you want into annotations
section for a node. The whole section is optional, so one can simply ignore
that section, and no concerns are mixed...
In fact, given the external ref
Put a couple of comments on the wiki, but I think it is a thing that
should be discussed on the list.
In ADL 1.5 a flag 'pass_through' was added. Its definition is 'Allows
nodes required for structuring data but otherwise redundant for screen
display and reporting to be detected by rendering
22 matches
Mail list logo
