As a side note, the “Service request” archetype has just (yesterday, in fact) 
been published as INSTRUCTION.service_request.v1.
Regards,
Silje

From: openEHR-technical [mailto:[email protected]] On 
Behalf Of Ian McNicoll
Sent: Friday, July 06, 2018 11:16 AM
To: For openEHR technical discussions <[email protected]>
Subject: Re: Unique paths for nodes in multiple instances of one archetype in 
the same OPT

Hi Dileep,

The usual approach I take here is to rename the clustered archetype to reflect 
local use, which works out as

[openEHR-EHR-COMPOSITION.request.v1]
        [openEHR-EHR-INSTRUCTION.request.v0]
[openEHR-EHR-CLUSTER.organisation.v0, 'Requesting organisation']
    [openEHR-EHR-CLUSTER.person_name.v1]
[openEHR-EHR-CLUSTER.organisation.v0, ' Receiving organisation']
    [openEHR-EHR-CLUSTER.person_name.v1]

and is queryable on AQL.

see 
https://github.com/RippleOSI/Ripple-openEHR/tree/master/docs/bindings/Current%20Ripple%20Headings/Referrals

Note that the AQL described was not working correctly on Ethercis in the past 
but that issue may have been fixed.

Ian

Dr Ian McNicoll
mobile +44 (0)775 209 7859
office +44 (0)1536 414994
skype: ianmcnicoll
email: [email protected]<mailto:[email protected]>
twitter: @ianmcnicoll

[https://docs.google.com/uc?export=download&id=0BzLo3mNUvbAjUmNWaFZYZlZ5djg&revid=0BzLo3mNUvbAjRzZKc0JpUXl2SkRtMDJ0bkdUcUQxM2dqSVdrPQ]
Co-Chair, openEHR Foundation 
[email protected]<mailto:[email protected]>
Director, freshEHR Clinical Informatics Ltd.
Director, HANDIHealth CIC
Hon. Senior Research Associate, CHIME, UCL


On Fri, 6 Jul 2018 at 10:07, Dileep V S 
<[email protected]<mailto:[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

[https://drive.google.com/uc?id=0BxQc41y9yqs6bkE5a1JQQVBjZG8]

Dileep V S

Founder

HealtheLife Ventures LLP

m:

+91 9632888113

a:

103, Innovation Centre, IIIT, Electronics City, Bangalore 560100

w:

healthelife.in<http://healthelife.in/>  e: 
[email protected]<mailto:[email protected]>

_______________________________________________
openEHR-technical mailing list
[email protected]<mailto:[email protected]>
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
_______________________________________________
openEHR-technical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Reply via email to