This page is part of the HL7 Terminology (v1.0.0: Release) based on FHIR R4. The current version which supercedes this version is 5.2.0. For a full list of available versions, see the Directory of published versions

ActRelationshipSplit - JSON Representation

(back to description)

Raw json

Source view

{
  "resourceType" : "ValueSet",
  "id" : "v3-ActRelationshipSplit",
  "language" : "en",
  "text" : {
    "status" : "generated",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\" xml:lang=\"en\" lang=\"en\"><h2>ActRelationshipSplit</h2><div><p>A code specifying how branches in an action plan are selected among other branches.</p>\n<p><em>Discussion:</em> 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. The splitCode specifies whether a branch is executed exclusively (case-switch) or inclusively, i.e., in parallel with other branches.</p>\n<p>In addition to exlusive and inclusive split the splitCode specifies how the pre-condition (also known as &quot;guard conditions&quot; on the branch) are evaluated. A guard condition may be evaluated once when the branching step is entered and if the conditions do not hold at that time, the branch is abandoned. Conversely execution of a branch may wait until the guard condition turns true.</p>\n<p>In exclusive wait branches, the first branch whose guard conditions turn true will be executed and all other branches abandoned. In inclusive wait branches some branches may already be executed while other branches still wait for their guard conditions to turn true.</p>\n</div><ul><li>Include all codes defined in <a href=\"CodeSystem-v3-ActRelationshipSplit.html\"><code>http://terminology.hl7.org/CodeSystem/v3-ActRelationshipSplit</code></a></li></ul></div>"
  },
  "url" : "http://terminology.hl7.org/ValueSet/v3-ActRelationshipSplit",
  "identifier" : [
    {
      "system" : "urn:ietf:rfc:3986",
      "value" : "urn:oid:2.16.840.1.113883.1.11.10355"
    }
  ],
  "version" : "2.0.0",
  "name" : "ActRelationshipSplit",
  "title" : "ActRelationshipSplit",
  "status" : "active",
  "date" : "2014-03-26T00:00:00-04:00",
  "description" : "A code specifying how branches in an action plan are selected among other branches.\r\n\r\n*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. The splitCode specifies whether a branch is executed exclusively (case-switch) or inclusively, i.e., in parallel with other branches.\r\n\r\nIn addition to exlusive and inclusive split the splitCode specifies how the pre-condition (also known as \"guard conditions\" on the branch) are evaluated. A guard condition may be evaluated once when the branching step is entered and if the conditions do not hold at that time, the branch is abandoned. Conversely execution of a branch may wait until the guard condition turns true.\r\n\r\nIn exclusive wait branches, the first branch whose guard conditions turn true will be executed and all other branches abandoned. In inclusive wait branches some branches may already be executed while other branches still wait for their guard conditions to turn true.",
  "immutable" : true,
  "compose" : {
    "include" : [
      {
        "system" : "http://terminology.hl7.org/CodeSystem/v3-ActRelationshipSplit"
      }
    ]
  }
}