Hi Dileep, In the EHRServer we use the template path as an absolute path for each node in the template, that allows to identify each node in the OPT even if different nodes hang from the same archetype root (have the same archetype path). This allows querying for the right node.
Also there is another case when nodes with the same path but different data type are in a composition instance. We use the path + type to identify those node alternatives. Best, Pablo. On Fri, Jul 6, 2018 at 6:07 AM, Dileep V S <[email protected]> wrote: > Hi, > > We are trying to create a service request template using the following > structure > > [openEHR-EHR-COMPOSITION.request.v1] > [openEHR-EHR-INSTRUCTION.request.v0] > [openEHR-EHR-CLUSTER.organisation.v0] > [openEHR-EHR-CLUSTER.person_name.v1] > [openEHR-EHR-CLUSTER.organisation.v0] > [openEHR-EHR-CLUSTER.person_name.v1] > > The first set of organization & person name archetypes are for the > requester and the second set for the receiver. > > However in the template editor, the paths for the nodes of both these > instances are the same(Eg. Orgaization name, Identifier, unstructured name > etc). This, we feel, will create problems in the AQL as we cannot uniquely > identify the nodes. How do we solve this problem. Is there any better way > to model the template > > I m attaching the template file set for reference > > Regards > > Dileep V S > *Founder* > HealtheLife Ventures LLP > m: +91 9632888113 > a: 103, Innovation Centre, IIIT, Electronics City, Bangalore 560100 > w: healthelife.in e: [email protected] > > _______________________________________________ > openEHR-technical mailing list > [email protected] > http://lists.openehr.org/mailman/listinfo/openehr- > technical_lists.openehr.org > > -- *Ing. Pablo Pazos Gutiérrez* [email protected] +598 99 043 145 skype: cabolabs Subscribe to our newsletter <http://eepurl.com/b_w_tj> <https://cabolabs.com/> http://www.cabolabs.com https://cloudehrserver.com
_______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
