Is there an template in CKM where CKM creates this?
I don’t think CKM does this.
Having said this, I believe that this attribute may aim to solve the problem that the original SLOT’s at code is not carried through otherwise.
Without it may not be possible to know downstream what the SLOT’s text/description was, especially relevant if there are multiple SLOTs to choose from as in e.g. the following excerpt from https://ckm.openehr.org/ckm/archetypes/1013.1.611/adl)
When the slot_node_id is used instead of node_id, it is converted to this OPT2 representation (which seems consistent with ADL2 and OPT2 files produced by Archie):
@sebastian.garde The use of slot_node_id is what makes it work. The template says it was created with: Ocean Template Designer Version 2.7.87Beta.
There is another version of the IDCR Medication List.v0 OPT which was created with a newer version: 2.8.94Beta and doesn’t use slot_node_id.
The linked IDCR Medication List.v0.opt is the only OPT file with slot_node_id that has a value. There are a few others without the value (slot_node_id=""). This is a collapsed excerpt:
@sebastian.garde I couldn’t find an OPT that uses the linked eReferral archetype. There is an eReferral OPT but it uses only the first allow_archetype INSTRUCTION[at0001]. It would be interesting to see how the linked eReferral archetype is presented in an OPT when exported from the CKM.
p.s.
OPTs shown in CKM don’t provide the generator version - only: Ocean OPT Generator webservice. This would be a useful information
Agree. Whether it may be should be is a different story.
That said, @borut.jures I have used the ereferral archetype to create an oet template.
Whatever I do, it does not create an opt with a slot_node_id, neither in the current version of Template Designer nor when uploading the oet to a CKM.
This may of course be my lack of understanding of when or why this slot_node_id is added and when not. However, 2.7.x of Template Designer is roughly a decade old I believe, so whatever it may or may not have produced, I have no idea.
So unless someone can produce a template file set (archetype + oet) that leads to the generation of an opt with slot_node_id either in CKM or an up-to-date (or even an older version) of TD, not sure what else we can do.
In summary, as far as I can see, this is not an issue of CKM.
Thank you @sebastian.garde for investigating this. I guess this is an old OPT as Ian mentioned and we don’t have to worry about it. It is probably only found as a test in EHRbase.
However as you mentioned slot_node_id or something similar might be needed as it was discussed in the linked post.