HL7 Terminology
2.1.19 - Continuous Process Integration (ci build)

HL7 Terminology, published by HL7 International - Vocabulary Work Group. This is not an authorized publication; it is the continuous build for version 2.1.19). This version is based on the current content of https://github.com/HL7/UTG/ and changes regularly. See the Directory of published versions

: ActMood - JSON Representation

Raw json | Download

  "resourceType" : "ValueSet",
  "id" : "v3-ActMood",
  "language" : "en",
  "text" : {
    "status" : "generated",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\" xml:lang=\"en\" lang=\"en\"><ul><li>Include all codes defined in <a href=\"CodeSystem-v3-ActMood.html\"><code>http://terminology.hl7.org/CodeSystem/v3-ActMood</code></a></li></ul></div>"
  "url" : "http://terminology.hl7.org/ValueSet/v3-ActMood",
  "identifier" : [
      "system" : "urn:ietf:rfc:3986",
      "value" : "urn:oid:2.16.840.1.113883.1.11.10196"
  "version" : "2.0.0",
  "name" : "ActMood",
  "title" : "ActMood",
  "status" : "active",
  "date" : "2014-03-26",
  "description" : "A code distinguishing whether an Act is conceived of as a factual statement or in some other manner as a command, possibility, goal, etc.\r\n\r\n*Constraints:* An Act-instance must have one and only one moodCode value.\r\n\r\nThe moodCode of a single Act-instance never changes. Mood is not state.\r\n\r\nTo describe the progression of a business activity from defined to planned to executed, etc. one must instantiate different Act-instances in the different moods and link them using ActRelationship of general type \"sequel\". (See ActRelationship.type.)",
  "immutable" : true,
  "compose" : {
    "include" : [
        "system" : "http://terminology.hl7.org/CodeSystem/v3-ActMood"