AW: Unique paths for slots problem if slots are filled with same archetype

Hi Ian, Yes, it is not many cases where this is really required, but in the Service Request archetype, it is fairly likely to happen and anybody creating a template without your, Diego’s, David’s, Heath’s etc. cutting edge top-level expert knowledge around this will quite likely run into a trap

Re: Unique paths for slots problem if slots are filled with same archetype

Discussing this with David we have another solution to this problem: one thing you could do and would completely work without breaking anything is to specify some kind of empty specializations of the include archetype, and giving as the name of the specialization the node_id code. something like th

Re: Unique paths for slots problem if slots are filled with same archetype

Hi Sebastian, This is 'known issue' but not one that we had really thought too carefully about. We 'solve' it right now by renaming the slotted in archetype root node at template level but others have already pointed out that this is less than ideal. Adding an intermediate cluster would solve thi

AW: Unique paths for slots problem if slots are filled with same archetype

Thanks Diego, Yes, I think Heath has suggested a path similar to your second suggestion, just with a comma as separator and in a different order: [at0008,openEHR-EHR-INSTRUCTION.service_request.v1]/protocol[at0008]/items[at0141,openEHR-EHR-CLUSTER.service_request_information.v1] I would probably