UML diagrams from https://neoehr.com/openehr/uml/rm110
openEHR allows INSTRUCTIONS and subsequent ACTIONS to be linked so that the process of each INSTRUCTION can be tracked through a number of related ACTIONS.
The ‘correct’ openEHR approach is to hook up the ACTION and its ‘parent’ INSTRUCTION via the INSTRUCTION_DETAILS object via an AQLPath
The full AQL path is needed when the ACTIONS and INSTRUCTIONS are in 2 different compositions, whereas the short wtPath can be used if ACTIONS and INSTRUCTION are in the same composition.
When using INSTRUCTIONs and ACTIONs it is necessary to link ACTIONs to INSTRUCTIONs.
Attributes that allow this linking are all under _instruction_details on the ACTION node.
Different sets of attributes can be used depending on the operational template.
This is the simplest case for linking with the following attributes:
|composition_uid :UID of the COMPOSITION with the target INSTRUCTION. A special value $selfComposition can be used when INSTRUCTION and ACTION both appear in the same composition and when using the EHR Server REST API.|instruction_uid :UID of the target INSTRUCTION (this is needed when there are several INSTRUCTIONs in the target COMPOSITION). UID is created by default when using web templates to create compositions.|instruction_index: index of the INSTRUCTION - needed only when multiple INSTRUCTIONs appear in a COMPOSITION, if possible use instruction_uid|wt_path: web template ID (path) to the target INSTRUCTION|activity_id : AQL path from INSTRUCTION to the target ACTIVITY (i.e. activities[at0001]). Needed only when there is more than one ACTIVITY in an INSTRUCTION.