CodeSystem Comparison between http://terminology.hl7.org/CodeSystem/v3-ActRelationshipJoin vs http://terminology.hl7.org/CodeSystem/v3-ActRelationshipJoin

Messages

InformationCodeSystem.copyrightValues for copyright differ: 'This material derives from the HL7 Terminology THO. THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license' vs 'This material derives from the HL7 Terminology THO. THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html'

Metadata

NameValueComments
.caseSensitivetrue
    .compositional
      .contentcomplete
        .copyrightThis material derives from the HL7 Terminology THO. THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/licenseThis material derives from the HL7 Terminology THO. THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html
        • Values Differ
        .date2019-03-20
          .descriptionA 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.
            .experimentalfalse
              .hierarchyMeaningis-a
                .jurisdiction
                  .nameActRelationshipJoin
                    .publisherHealth Level Seven International
                      .purpose
                        .statusactive
                          .titleActRelationshipJoin
                            .urlhttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipJoin
                              .version3.0.0
                                .versionNeeded

                                  Concepts

                                  CodeDisplaySpecializesGeneralizesinternalIdstatusSpecializesGeneralizesinternalIdstatusComments
                                  .Ddetached1036410364activeactive1036410364activeactive
                                    .Kkill1036210362activeactive1036210362activeactive
                                      .Wwait1036110361activeactive1036110361activeactive
                                        .Xexclusive wait1036310363activeactive1036310363activeactive