x_ActMoodEvnOrdPrmsPrp

{
  "compose" : {
    "exclude" : [ ],
    "include" : [ {
      "system" : "http://terminology.hl7.org/CodeSystem/v3-ActMood",
      "extension" : [ {
        "extension" : [ {
          "valueString" : "concept",
          "url" : "path"
        }, {
          "url" : "count",
          "valueInteger" : 4
        } ],
        "url" : "http://health-samurai.io/extensions/excised-data"
      } ]
    } ]
  },
  "date" : "2014-03-26",
  "name" : "XActMoodEvnOrdPrmsPrp",
  "resourceType" : "ValueSet",
  "title" : "x_ActMoodEvnOrdPrmsPrp",
  "extension" : [ {
    "extension" : [ {
      "valueString" : "Name:Class",
      "url" : "name"
    }, {
      "valueString" : "ProposeProcess",
      "url" : "value"
    } ],
    "url" : "http://terminology.hl7.org/StructureDefinition/ext-mif-assocConceptProp"
  }, {
    "url" : "http://health-samurai.io/extensions/source",
    "valueCode" : "db"
  } ],
  "status" : "active",
  "language" : "en",
  "id" : "61438777-48a2-41d4-84c7-42ba5e5ca9fc",
  "url" : "http://terminology.hl7.org/ValueSet/v3-xActMoodEvnOrdPrmsPrp",
  "identifier" : [ {
    "system" : "urn:ietf:rfc:3986",
    "value" : "urn:oid:2.16.840.1.113883.1.11.18965"
  } ],
  "immutable" : true,
  "version" : "2.0.0",
  "text" : {
    "div" : "<div xml:lang=\"en\" xmlns=\"http://www.w3.org/1999/xhtml\" lang=\"en\"><ul><li>Include these codes as defined in <a href=\"CodeSystem-v3-ActMood.html\"><code>http://terminology.hl7.org/CodeSystem/v3-ActMood</code></a><table class=\"none\"><tr><td style=\"white-space:nowrap\"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td><a href=\"CodeSystem-v3-ActMood.html#v3-ActMood-EVN\">EVN</a></td><td>event (occurrence)</td><td>**Definition:** An act that actually happens (may be an ongoing act or a documentation of a past act).</td></tr><tr><td><a href=\"CodeSystem-v3-ActMood.html#v3-ActMood-PRMS\">PRMS</a></td><td>promise</td><td>**Definition:** A commitment to perform an act (may be either solicited or unsolicited). The committer becomes responsible to the other party for executing the act, and, as a consequence, the other party may rely on the first party to perform or cause to perform the act.<br/><br/>**UsageNotes:** Commitments may be retracted or cancelled.</td></tr><tr><td><a href=\"CodeSystem-v3-ActMood.html#v3-ActMood-PRP\">PRP</a></td><td>proposal</td><td>**Definition:** A suggestion that an act might be performed. Not an explicit request, and professional responsibility may or may not be present.</td></tr><tr><td><a href=\"CodeSystem-v3-ActMood.html#v3-ActMood-RQO\">RQO</a></td><td>request</td><td>**Definition:** A request act that is specialized for an event request/fulfillment cycle.<br/><br/>**UsageNotes:** The fulfillment cycle may involve intermediary fulfilling acts in moods such as PRMS, APT, or even another RQO before being fulfilled by the final event.<br/><br/>**UsageNotes:** The concepts of a &quot;request&quot; and an &quot;order&quot; are viewed as different, because there is an implication of a mandate associated with order. In practice, however, this distinction has no general functional value in the inter-operation of health care computing. &quot;Orders&quot; are commonly refused for a variety of clinical and business reasons, and the notion of a &quot;request&quot; obligates the recipient (the fulfiller) to respond to the sender (the author). Indeed, in many regions, including Australia and Europe, the common term used is &quot;request.&quot;<br/><br/>Thus, the concept embodies both notions, as there is no useful distinction to be made. If a mandate is to be associated with a request, this will be embodied in the &quot;local&quot; business rules applied to the transactions. Should HL7 desire to provide a distinction between these in the future, the individual concepts could be added as specializations of this concept.<br/><br/>The critical distinction here, is the difference between this concept and an &quot;intent&quot;, of which it is a specialization. An intent involves decisions by a single party, the author. A request, however, involves decisions by two parties, the author and the fulfiller, with an obligation on the part of the fulfiller to respond to the request indicating that the fulfiller will indeed fulfill the request.</td></tr></table></li></ul></div>",
    "status" : "extensions"
  }
}