Index in array's in ADL
On 19/11/2013 20:08, Bert Verhees wrote: > Hi Alessandro, > > I think you propose this? > > /items[at0008,1]/value/value = Mark > /items[at0009,2]/value/value = Rutte Either this or Bert's original (if it's legal Xpath) is correct, assuming the data look something like (I just added the outer bit and header to make it work in a tool): http://www.w3.org/2001/XMLSchema-instance"; archetype_node_id="openEHR-EHR-CLUSTER.bert.v1" xmlns="http://schemas.openehr.org/v1";> Jan Peter Balkenende I'm just messing around in Oxygen with some Xqueries and Xpaths. - thomas -- next part -- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20131119/cb317c8a/attachment-0001.html>
Index in array's in ADL
Hi Alessandro,
I think you propose this?
/items[at0008,1]/value/value = Mark
/items[at0009,2]/value/value = Rutte
regards
Bert Verhees
Alessandro Torrisi schreef op 19-11-2013 20:19:
> i would say
>
> /items[at0008,1]/value/value = Mark
> /items[at0008,2]/value/value = Rutte
>
> Alessandro
>
>
>
> On 19 November 2013 13:57, Diego Bosc? <mailto:yampeku at gmail.com>> wrote:
>
> Hi Bert,
>
> Personally I would use:
>
> /items[at0008]/value[1]/value = Jan
> /items[at0008]/value[2]/value = Peter
> /items[at0009]/value/value = Balkenende
>
> Regards
>
> 2013/11/19 Bert Verhees <mailto:bert.verhees at rosa.nl>>:
> > Hi all,
> >
> > I had following interesting discussion.
> >
> > Suppose we have a cluster containing name of a person.
> >
> > There is a field called firstname, and a field called lastname.
> >
> > The problem is concerning the ADL-path, what should be used.
> >
> > This is a part of the archetype:
> >
> > CLUSTER[at0007] occurrences matches {0..1} matches {-- voornamen
> >items cardinality matches {0..*; ordered}
> matches {
> >ELEMENT[at0008] occurrences matches
> {0..*}
> > matches {-- firstname
> >value matches {
> >DV_TEXT matches {*}
> >}
> >}
> >ELEMENT[at0009] occurrences matches
> {0..1}
> > matches {-- lastname
> >value matches {
> >DV_TEXT matches {*}
> >}
> >}
> >}
> >
> >
> > This is a hypothecical example, only to explain:
> >
> > Because at0008 has upper-occurrences of more then 1 ( a person
> can have more
> > then one firstnames)
> > And at0009 has upper-occurrences of 1 (people only have one
> last-name (in
> > this hypothetical country))
> >
> > If we want to express data in a path/value combination, what
> would be the
> > best solution?
> >
> > /items[at0008][1]/value/value = Jan
> > /items[at0008][2]/value/value = Peter
> > /items[at0009]/value/value = Balkenende
> >
> > /items[at0008][1]/value/value = Jan
> > /items[at0008][2]/value/value = Peter
> > /items[at0009][1]/value/value = Balkenende
> >
> > /items[at0008][1]/value/value = Jan
> > /items[at0008][2]/value/value = Peter
> > /items[at0009][3]/value/value = Balkenende
> >
> > Or would another solution be better?
> > Thanks in advance for suggestions.
> >
> > Kind regards
> > Bert Verhees
> >
> > ___
> > openEHR-technical mailing list
> > openEHR-technical at lists.openehr.org
> <mailto:openEHR-technical at lists.openehr.org>
> >
>
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>
> ___
> openEHR-technical mailing list
> openEHR-technical at lists.openehr.org
> <mailto:openEHR-technical at lists.openehr.org>
>
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>
>
>
>
> --
> Alessandro Torrisi
>
>
> ___
> openEHR-technical mailing list
> openEHR-technical at lists.openehr.org
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20131119/15339995/attachment.html>
XML COMPOSITIONS for OPT testing
Hi all, I'm adding support for Operational Templates (OPTs) to the EHRServer. I'm using the current templates in the CKM as test cases: eReferral, Heart Failure and Demo with hide-on-form. Does anyone have a XML COMPOSITON instance created for any of those templates? The idea is to use those instances to commit them to the server and verify that all the data is queryable without human intervention. If anyone has other OPTs with sample XML COMPOSITION instances, is also good! Thanks for your collaboration! -- Kind regards, Eng. Pablo Pazos Guti?rrez http://cabolabs.com -- next part -- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20131119/37cb98cd/attachment.html>
Index in array's in ADL
i would say
/items[at0008,1]/value/value = Mark
/items[at0008,2]/value/value = Rutte
Alessandro
On 19 November 2013 13:57, Diego Bosc? wrote:
> Hi Bert,
>
> Personally I would use:
>
> /items[at0008]/value[1]/value = Jan
> /items[at0008]/value[2]/value = Peter
> /items[at0009]/value/value = Balkenende
>
> Regards
>
> 2013/11/19 Bert Verhees :
> > Hi all,
> >
> > I had following interesting discussion.
> >
> > Suppose we have a cluster containing name of a person.
> >
> > There is a field called firstname, and a field called lastname.
> >
> > The problem is concerning the ADL-path, what should be used.
> >
> > This is a part of the archetype:
> >
> > CLUSTER[at0007] occurrences matches {0..1} matches {-- voornamen
> >items cardinality matches {0..*; ordered} matches
> {
> >ELEMENT[at0008] occurrences matches {0..*}
> > matches {-- firstname
> >value matches {
> >DV_TEXT matches {*}
> >}
> >}
> >ELEMENT[at0009] occurrences matches {0..1}
> > matches {-- lastname
> >value matches {
> >DV_TEXT matches {*}
> >}
> >}
> >}
> >
> >
> > This is a hypothecical example, only to explain:
> >
> > Because at0008 has upper-occurrences of more then 1 ( a person can have
> more
> > then one firstnames)
> > And at0009 has upper-occurrences of 1 (people only have one last-name (in
> > this hypothetical country))
> >
> > If we want to express data in a path/value combination, what would be the
> > best solution?
> >
> > /items[at0008][1]/value/value = Jan
> > /items[at0008][2]/value/value = Peter
> > /items[at0009]/value/value = Balkenende
> >
> > /items[at0008][1]/value/value = Jan
> > /items[at0008][2]/value/value = Peter
> > /items[at0009][1]/value/value = Balkenende
> >
> > /items[at0008][1]/value/value = Jan
> > /items[at0008][2]/value/value = Peter
> > /items[at0009][3]/value/value = Balkenende
> >
> > Or would another solution be better?
> > Thanks in advance for suggestions.
> >
> > Kind regards
> > Bert Verhees
> >
> > ___
> > openEHR-technical mailing list
> > openEHR-technical at lists.openehr.org
> >
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>
> ___
> openEHR-technical mailing list
> openEHR-technical at lists.openehr.org
>
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>
--
Alessandro Torrisi
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20131119/340e95c9/attachment.html>
Index in array's in ADL
Hi Bert,
Personally I would use:
/items[at0008]/value[1]/value = Jan
/items[at0008]/value[2]/value = Peter
/items[at0009]/value/value = Balkenende
Regards
2013/11/19 Bert Verhees :
> Hi all,
>
> I had following interesting discussion.
>
> Suppose we have a cluster containing name of a person.
>
> There is a field called firstname, and a field called lastname.
>
> The problem is concerning the ADL-path, what should be used.
>
> This is a part of the archetype:
>
> CLUSTER[at0007] occurrences matches {0..1} matches {-- voornamen
>items cardinality matches {0..*; ordered} matches {
>ELEMENT[at0008] occurrences matches {0..*}
> matches {-- firstname
>value matches {
>DV_TEXT matches {*}
>}
>}
>ELEMENT[at0009] occurrences matches {0..1}
> matches {-- lastname
>value matches {
>DV_TEXT matches {*}
>}
>}
>}
>
>
> This is a hypothecical example, only to explain:
>
> Because at0008 has upper-occurrences of more then 1 ( a person can have more
> then one firstnames)
> And at0009 has upper-occurrences of 1 (people only have one last-name (in
> this hypothetical country))
>
> If we want to express data in a path/value combination, what would be the
> best solution?
>
> /items[at0008][1]/value/value = Jan
> /items[at0008][2]/value/value = Peter
> /items[at0009]/value/value = Balkenende
>
> /items[at0008][1]/value/value = Jan
> /items[at0008][2]/value/value = Peter
> /items[at0009][1]/value/value = Balkenende
>
> /items[at0008][1]/value/value = Jan
> /items[at0008][2]/value/value = Peter
> /items[at0009][3]/value/value = Balkenende
>
> Or would another solution be better?
> Thanks in advance for suggestions.
>
> Kind regards
> Bert Verhees
>
> ___
> openEHR-technical mailing list
> openEHR-technical at lists.openehr.org
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
Index in array's in ADL
Hi all,
I had following interesting discussion.
Suppose we have a cluster containing name of a person.
There is a field called firstname, and a field called lastname.
The problem is concerning the ADL-path, what should be used.
This is a part of the archetype:
CLUSTER[at0007] occurrences matches {0..1} matches {-- voornamen
items cardinality matches {0..*; ordered} matches {
ELEMENT[at0008] occurrences matches {0..*} matches
{-- firstname
value matches {
DV_TEXT matches {*}
}
}
ELEMENT[at0009] occurrences matches {0..1} matches
{-- lastname
value matches {
DV_TEXT matches {*}
}
}
}
This is a hypothecical example, only to explain:
Because at0008 has upper-occurrences of more then 1 ( a person can have
more then one firstnames)
And at0009 has upper-occurrences of 1 (people only have one last-name
(in this hypothetical country))
If we want to express data in a path/value combination, what would be
the best solution?
/items[at0008][1]/value/value = Jan
/items[at0008][2]/value/value = Peter
/items[at0009]/value/value = Balkenende
/items[at0008][1]/value/value = Jan
/items[at0008][2]/value/value = Peter
/items[at0009][1]/value/value = Balkenende
/items[at0008][1]/value/value = Jan
/items[at0008][2]/value/value = Peter
/items[at0009][3]/value/value = Balkenende
Or would another solution be better?
Thanks in advance for suggestions.
Kind regards
Bert Verhees
Index in array's in ADL
Agree with Diego, I would use indexes only for repeatable data.
--
Kind regards,
Eng. Pablo Pazos Guti?rrez
http://cabolabs.com
> From: yampeku at gmail.com
> Date: Tue, 19 Nov 2013 13:57:43 +0100
> Subject: Re: Index in array's in ADL
> To: openehr-technical at lists.openehr.org
>
> Hi Bert,
>
> Personally I would use:
>
> /items[at0008]/value[1]/value = Jan
> /items[at0008]/value[2]/value = Peter
> /items[at0009]/value/value = Balkenende
>
> Regards
>
> 2013/11/19 Bert Verhees :
> > Hi all,
> >
> > I had following interesting discussion.
> >
> > Suppose we have a cluster containing name of a person.
> >
> > There is a field called firstname, and a field called lastname.
> >
> > The problem is concerning the ADL-path, what should be used.
> >
> > This is a part of the archetype:
> >
> > CLUSTER[at0007] occurrences matches {0..1} matches {-- voornamen
> >items cardinality matches {0..*; ordered} matches {
> >ELEMENT[at0008] occurrences matches {0..*}
> > matches {-- firstname
> >value matches {
> >DV_TEXT matches {*}
> >}
> >}
> >ELEMENT[at0009] occurrences matches {0..1}
> > matches {-- lastname
> >value matches {
> >DV_TEXT matches {*}
> >}
> >}
> >}
> >
> >
> > This is a hypothecical example, only to explain:
> >
> > Because at0008 has upper-occurrences of more then 1 ( a person can have more
> > then one firstnames)
> > And at0009 has upper-occurrences of 1 (people only have one last-name (in
> > this hypothetical country))
> >
> > If we want to express data in a path/value combination, what would be the
> > best solution?
> >
> > /items[at0008][1]/value/value = Jan
> > /items[at0008][2]/value/value = Peter
> > /items[at0009]/value/value = Balkenende
> >
> > /items[at0008][1]/value/value = Jan
> > /items[at0008][2]/value/value = Peter
> > /items[at0009][1]/value/value = Balkenende
> >
> > /items[at0008][1]/value/value = Jan
> > /items[at0008][2]/value/value = Peter
> > /items[at0009][3]/value/value = Balkenende
> >
> > Or would another solution be better?
> > Thanks in advance for suggestions.
> >
> > Kind regards
> > Bert Verhees
> >
> > ___
> > openEHR-technical mailing list
> > openEHR-technical at lists.openehr.org
> > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>
> ___
> openEHR-technical mailing list
> openEHR-technical at lists.openehr.org
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20131119/6abf6b62/attachment-0001.html>
Ocean's Template Designer and allowedType rules
Hi folks, We used opt to feed in the model to software, especially the GUI generator in GastrOS. We added a few GUI Directives to get the desired looks... I reckon the new version of TD now supports those directives :) For those interested it is open source at: http://gastros.codeplex.com Cheers, -koray -Original Message- From: openEHR-implementers [mailto:openehr-implementers-boun...@lists.openehr.org] On Behalf Of Ian McNicoll Sent: Friday, 15 November 2013 8:31 p.m. To: For openEHR technical discussions Cc: openehr implementers Subject: Re: Ocean's Template Designer and allowedType rules Hi Pablo, I just want to re-emphasise Heath's point for anyone looking to implement openEHR template support. Your start point should be the .opt 'Operational template' format. This is what is used by a number of developers to generate downstream artefacts such asd code fragments, xsd schema and GUI generation. The official openEHR templates will be fully based on ADL1.5, rather than the current mix of ADL1.4 and Ocean .oet, but the eventual ADL 1.5 .opt output will be very similar to the current .opt, so this is a good 'junction point' for transition from ADL1.4 -> ADL 1.5 Ian On 14 November 2013 21:27, Heath Frankel wrote: > Hi Pablo, > > The OET format is an internal format. You should export the template > as an OPT and you will get a AOM and RM based output. > > > > Heath > > > > From: openEHR-technical > [mailto:openehr-technical-bounces at lists.openehr.org] > On Behalf Of pablo pazos > Sent: Friday, 15 November 2013 1:06 AM > To: openeh technical; openehr implementers > Subject: Ocean's Template Designer and allowedType rules > > > > Hi all, > > > > I'm playing with the TD v2.7.60Beta to include openEHR template > support to CaboLabs EHRServer > (http://www.youtube.com/watch?v=D-hs-Ofb8SY) > > > > I opened the Blood Pressure archetype and tryied to constraint the Any > Event node of type EVENT to allow only POINT_EVENT, and I get this rule: > > > > > > > > PointInTime > > > > > > > > Shouldn't "PointInTime" be "POINT_EVENT"? > > > > Is there any reason for the TD to not use openEHR datatype names? > > > > Where can I find all the names used to constraint allowedTypes in TD? > > > > Thanks! > > > -- > Kind regards, > Eng. Pablo Pazos Guti?rrez > http://cabolabs.com > > > ___ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.open > ehr.org -- Dr Ian McNicoll office +44 (0)1536 414 994 fax +44 (0)1536 516317 mobile +44 (0)775 209 7859 skype ianmcnicoll ian.mcnicoll at oceaninformatics.com Clinical Modelling Consultant, Ocean Informatics, UK Director openEHR Foundation www.openehr.org/knowledge Honorary Senior Research Associate, CHIME, UCL SCIMP Working Group, NHS Scotland BCS Primary Health Care www.phcsg.org ___ openEHR-implementers mailing list openEHR-implementers at lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-implementers_lists.openehr.org
