This page is part of the HL7 Terminology (v5.2.0: Release) based on FHIR R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions ![](external.png)
: x_ActMoodDefEvnRqo - XML Representation
Raw xml | Download
<ValueSet xmlns="http://hl7.org/fhir">
<id value="v3-xActMoodDefEvnRqo"/>
<language value="en"/>
<text>
<status value="extensions"/>
<div xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" 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-DEF">DEF</a></td><td>definition</td><td>**Definition:** A definition of a kind of act that can occur .<br/><br/>**OpenIssue:** The semantic constructs embodied in DEF and CRT moods seem indistinguishable, and their uses can readily be determined by the context in which these are used. Therefore, this OpenIssue has been created to declare that it is likely that ActMood.DEF will be "retired" in the future in favor of the more general ActMood.CRT.</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-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 "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."<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 "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.<br/><br/>The 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.</td></tr></table></li></ul></div>
</text>
<url value="http://terminology.hl7.org/ValueSet/v3-xActMoodDefEvnRqo"/>
<identifier>
<system value="urn:ietf:rfc:3986"/>
<value value="urn:oid:2.16.840.1.113883.1.11.19762"/>
</identifier>
<version value="2.0.0"/>
<name value="XActMoodDefEvnRqo"/>
<title value="x_ActMoodDefEvnRqo"/>
<status value="active"/>
<experimental value="false"/>
<date value="2014-03-26"/>
<description value="***No description***"/>
<immutable value="true"/>
<compose>
<include>
<system value="http://terminology.hl7.org/CodeSystem/v3-ActMood"/>
<concept>
<code value="DEF"/>
</concept>
<concept>
<code value="EVN"/>
</concept>
<concept>
<code value="RQO"/>
</concept>
</include>
</compose>
</ValueSet>