R4 Ballot #2 (Mixed Normative/Trial use)

This page is part of the FHIR Specification (v3.5.0: R4 Ballot #2). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4 R3

4.4.2.10199 HL7 v3 Value Set ActMoodIntent

Vocabulary

Work Group

Maturity Level: N/A

External

Use Context: Any

This value set (http://terminology.hl7.org/ValueSet/v3-ActMoodIntent) is defined as part of HL7 v3.

Summary

Defining URL:

http://terminology.hl7.org/ValueSet/v3-ActMoodIntent

Version:

2014-03-26

Name:

v3.ActMoodIntent

Title:

V3 Value SetActMoodIntent

Definition:

An intention or plan to perform a service. Historical note: in previous RIM versions, the intent mood was captured as a separate class hierarchy, called Service_intent_or_order.

OID:

2.16.840.1.113883.1.11.10199 (for OID based terminology systems)

Source Resource

XML / JSON

This value set is not currently used

4.4.2.10199.1 Content Logical Definition

This value set includes codes from the following code systems:

Include codes from http://terminology.hl7.org/CodeSystem/v3-ActMood where concept is-a INT

4.4.2.10199.2 Expansion

This expansion generated 19 Aug 2018

This value set contains 8 concepts

Expansion based on http://terminology.hl7.org/CodeSystem/v3-ActMood version 2018-08-12

All codes from system http://terminology.hl7.org/CodeSystem/v3-ActMood

Lvl	Code	Display	Definition
0	INT	intent	Definition: An intention or plan for an act. >UsageNotes: The final outcome of the intent, the act that is intended to occur, is always an event. However the final outcome may be reached indirectly via steps through other intents, such as promise, permission request, or an appointment that may lead to an actual event to occur. Alternatively, the intended act may never occur.
1	_ActMoodDesire	desire	Definition: A desire to have an act occur.
2	_ActMoodActRequest	act request	Definition: A request (or order) for an act that is part of a defined request/fulfillment cycle. UsageNotes: Use of an HL7 defined request/fulfillment framework is not required to use this mood code.
3	ARQ	appointment request	Definition: A request act that is specialized for the appointment scheduling request/fulfillment cycle. An appointment request is fulfilled only and completely by an appointment (APT), i.e., all that the appointment request intends is to create an appointment (the actual act may well not happen if that is the professional decision during the appointment).
3	PERMRQ	permission request	Definition: A request for a permission to perform the act. Typically a payer (or possibly a supervisor) is being requested to give permission to perform the act. As opposed to the RQO, the requestee is not asked to perform or cause to perform the act but only to give the permission.
3	RQO	request	Definition: A request act that is specialized for an event request/fulfillment cycle. 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. 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." 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. 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.
2	PRP	proposal	Definition: A suggestion that an act might be performed. Not an explicit request, and professional responsibility may or may not be present.
3	RMD	recommendation	Definition: A suggestion that an act should be performed with an acceptance of some degree of professional responsibility for the resulting act. Not an explicit request. . UsageNotes: Where there is no clear definition or applicable concept of "professional responsibilityâ€?, RMD becomes indistinguishable from PRP. .
1	PRMS	promise	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. UsageNotes: Commitments may be retracted or cancelled.
2	APT	appointment	Definition: An act that has been scheduled to be performed at a specific place and time.