Hi Shinji, I've created a script to traverse an OPT and generate paths like this: /content[archetype_id=openEHR-EHR-SECTION.referral_details.v1]/items[archetype_id=openEHR-EHR-INSTRUCTION.request-referral.v1]/protocol[at0008]/items[archetype_id=openEHR-EHR-CLUSTER.individual_professional.v1]/items[archetype_id=openEHR-EHR-CLUSTER.person_name.v1]/items[at0013]/items[at0002]/items[at0003]/value DV_TEXT This path was generated from the "Demo hide-on-form" OPT that is in the CKM. Don't know if the syntax is 100% valid, but changing the algorithm is easy. Algorithm: https://github.com/ppazos/cabolabs-ehrserver/blob/master/src/groovy/com/cabolabs/archetype/OperationalTemplateIndexer.groovyTest: https://github.com/ppazos/cabolabs-ehrserver/tree/master/testOPTs: https://github.com/ppazos/cabolabs-ehrserver/tree/master/opts
-- Kind regards, Eng. Pablo Pazos Guti?rrez http://cabolabs.com > From: skoba at moss.gr.jp > Date: Fri, 15 Nov 2013 10:55:49 +0900 > Subject: Re: Ocean's Template Designer and allowedType rules > To: openehr-implementers at lists.openehr.org > CC: openehr-technical at lists.openehr.org > > Hi Heath, > > I have a related question about OPT. > Could you explain path calculation algorithm for OPT? > > Best wishes, > Shinji KOBAYASHI > > 2013/11/15 Heath Frankel <heath.frankel at oceaninformatics.com>: > > 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: > > > > > > > > <Rule path="/data[at0001]/events[at0006]"> > > > > <eventConstraint> > > > > <allowedType>PointInTime</allowedType> > > > > </eventConstraint> > > > > </Rule> > > > > > > > > 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-implementers mailing list > > openEHR-implementers at lists.openehr.org > > http://lists.openehr.org/mailman/listinfo/openehr-implementers_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/20131128/e95c0335/attachment-0001.html>
