C_ARCHETYPE_ROOT.slot_node_id in OPT files

I found slot_node_id when Converting OPT14 to OPT2.

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):

use_archetype CLUSTER[at0002, openEHR-EHR-CLUSTER.medication_item.v1] occurrences matches {0..1} matches {    -- Medication item

@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:

<children xsi:type="C_COMPLEX_OBJECT">
  <rm_type_name>ITEM_TREE</rm_type_name>
  <node_id>at0001</node_id>
  <attributes xsi:type="C_MULTIPLE_ATTRIBUTE">
    <rm_attribute_name>items</rm_attribute_name>
    <children xsi:type="C_ARCHETYPE_ROOT" slot_node_id="at0002">
    <children xsi:type="ARCHETYPE_SLOT">
    <children xsi:type="ARCHETYPE_SLOT">
    </children>
  </attributes>
</children>

@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 :thinking: