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

ActMoodRequest - JSON Representation

(back to description)

Raw json

Source view

{
  "resourceType" : "ValueSet",
  "id" : "v3-ActMoodRequest",
  "language" : "en",
  "text" : {
    "status" : "generated",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\" xml:lang=\"en\" lang=\"en\"><h2>ActMoodRequest</h2><div><p>A request or order for a service is an intent directed from a placer (request author) to a fulfiller (service performer).</p>\n<p><em>Rationale:</em> 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;</p>\n<p>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.</p>\n<p>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.</p>\n</div><ul><li>Include codes from <a href=\"CodeSystem-v3-ActMood.html\"><code>http://terminology.hl7.org/CodeSystem/v3-ActMood</code></a> where concept  is-a  <a href=\"CodeSystem-v3-ActMood.html#v3-ActMood-RQO\">RQO</a></li></ul></div>"
  },
  "url" : "http://terminology.hl7.org/ValueSet/v3-ActMoodRequest",
  "identifier" : [
    {
      "system" : "urn:ietf:rfc:3986",
      "value" : "urn:oid:2.16.840.1.113883.1.11.19947"
    }
  ],
  "version" : "2.0.0",
  "name" : "ActMoodRequest",
  "title" : "ActMoodRequest",
  "status" : "active",
  "date" : "2014-03-26T00:00:00-04:00",
  "description" : "A request or order for a service is an intent directed from a placer (request author) to a fulfiller (service performer).\r\n\r\n*Rationale:* The concepts of a \"request\" and an \"order\" 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. \"Orders\" are commonly refused for a variety of clinical and business reasons, and the notion of a \"request\" 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 \"request.\"\r\n\r\nThus, 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 \"local\" 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.\r\n\r\nThe critical distinction here, is the difference between this concept and an \"intent\", 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.",
  "immutable" : true,
  "compose" : {
    "include" : [
      {
        "system" : "http://terminology.hl7.org/CodeSystem/v3-ActMood",
        "filter" : [
          {
            "property" : "concept",
            "op" : "is-a",
            "value" : "RQO"
          }
        ]
      }
    ]
  }
}