HL7 Terminology (THO)
5.2.0 - Publication
This page is part of the HL7 Terminology (v5.2.0: Release) based on FHIR R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions
Official URL: http://terminology.hl7.org/CodeSystem/v3-ActRelationshipJoin | Version: 2.1.1 | |||
Active as of 2019-03-20 | Responsible: Health Level 7 | Computable Name: ActRelationshipJoin | ||
Other Identifiers: id: urn:oid:2.16.840.1.113883.5.12 |
A code specifying how concurrent Acts are resynchronized in a parallel branch construct.
Discussion: This attribute is part of the workflow control suite of attributes. An action plan is a composite Act with component Acts. In a sequential plan, each component has a sequenceNumber that specifies the ordering of the plan steps. Branches exist when multiple components have the same sequenceNumber. Branches are parallel if the splitCode specifies that more than one branch can be executed at the same time. The joinCode then specifies if and how the braches are resynchronized.
The principal re-synchronization actions are (1) the control flow waits for a branch to terminate (wait-branch), (2) the branch that is not yet terminated is aborted (kill-branch), (3) the branch is not re-synchronized at all and continues in parallel (detached branch).
A kill branch is only executed if there is at least one active wait (or exclusive wait) branch. If there is no other wait branch active, a kill branch is not started at all (rather than being aborted shortly after it is started.) Since a detached branch is unrelated to all other branches, active detached branches do not protect a kill-branch from being aborted.
This Code system is referenced in the content logical definition of the following value sets:
Properties
This code system defines the following properties for its concepts
Code | URI | Type | Description |
Specializes | Coding | The child code is a more narrow version of the concept represented by the parent code. I.e. Every child concept is also a valid parent concept. Used to allow determination of subsumption. Must be transitive, irreflexive, antisymmetric. | |
Generalizes | Coding | Inverse of Specializes. Only included as a derived relationship. | |
internalId | http://terminology.hl7.org/CodeSystem/utg-concept-properties#v3-internal-id | code | The internal identifier for the concept in the HL7 Access database repository. |
status | http://hl7.org/fhir/concept-properties#status | code | Designation of a concept's state. Normally is not populated unless the state is retired. |
Concepts
This code system http://terminology.hl7.org/CodeSystem/v3-ActRelationshipJoin
defines the following codes:
History
Date | Action | Author | Custodian | Comment |
2022-10-18 | revise | Marc Duteau | TSMG | Fixing missing metadata; up-349 |
2022-02-17 00:00:32+1100 | revise | Grahame Grieve | Vocabulary WG | Populate Missing caseSensitive property; UP-286 |
2020-05-06 | revise | Ted Klein | Vocabulary WG | Migrated to the UTG maintenance environment and publishing tooling. |