Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Context Bindings to concept domain(s):
  ActMood in Realm: UV as CNE

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.

Constraints: An Act-instance must have one and only one moodCode value.

The moodCode of a single Act-instance never changes. Mood is not state.

To 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.)

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Description:

A planned Act for a specific time and place.

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Description:

A request for the booking of an appointment.

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Description:

These are moods describing activities as they progress in the business cycle, from defined, through planned and ordered to completed.

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Description:

A criterion or condition over actual and potential services that must apply for an associated service to be considered. Matches records any ActMoodCompletionTrack moods.

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Description:

A definition of a service (master).

Historical note: in previous RIM versions, the definition mood was captured as a separate class hierarchy, called Master_service.

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Description:

A criterion or condition over service events that must apply for an associated service to be considered.

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Description:

A service that actually happens, may be an ongoing service or a documentation of a past service.

Historical note: in previous RIM versions, the event mood was captured as a separate class hierarchy, called Patient_service_event, and later Service_event.

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Description:

Definition:An act that is considered likely to occur in the future. The essential feature of an act expressed in expectation mood is that it is likely to occur. An expectation may be desirable, undesirable or neutral in effect.

Examples:Prognosis of a condition, Expected date of discharge from hospital, patient will likely need an emergency decompression of the intracranial pressure by morning.

Discussion:INT (intent) reflects a plan for the future, which is a declaration to do something. This contrasts with expectation, which is a prediction that something will happen in the future. GOL (goal) reflects a hope rather than a prediction. RSK (risk) reflects a potential negative event that may or may not be expected to happen.

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Description:

Definition:An observation that is considered to be desirable to occur in the future. The essential feature of a goal is that if it occurs it would be considered as a marker of a positive outcome or of progress towards a positive outcome.

Examples:Target weight below 80Kg, Stop smoking, Regain ability to walk, goal is to administer thrombolytics to candidate patients presenting with acute myocardial infarction.

Discussion: INT (intent) reflects a plan for the future, which is a declaration to do something. This contrasts with goal which doesn't represent an intention to act, merely a hope for an eventual result. A goal is distinct from the intended actions to reach that goal. "I will reduce the dose of drug x to 20mg" is an intent. "I hope to be able to get the patient to the point where I can reduce the dose of drug x to 20mg" is a goal. EXPEC (expectation) reflects a prediction rather than a hope. RSK (risk) reflects a potential negative event rather than a hope.

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Description:

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.

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Description:

An option is an alternative set of property-value bindings. Options specify alternative sets of values, typically used in definitions or orders to describe alternatives. An option can only be used as a group, that is, all assigned values must be used together.

Historical note: in HL7 v2.x option existed in the special case for alternative medication routes (RXR segment).

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Description:

A kind of service which is authorized to be performed.

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Description:

A request for authorization to perform a kind of service.

This is distinct from RQO which is a request for an actual act. PERMRQ is merely a request for permission to perform an act. Discussion:

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Description:

Any of the above service moods (e.g., event, intent, or goal) can be turned into a predicate used as a criterion to express conditionals (or queries.) However, currently we allow only criteria on service events.

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Description:

An intent to perform a service that has the strength of a commitment, i.e., other parties may rely on the originator of such promise that said originator will see to it that the promised act will be fulfilled. A promise can be either solicited or unsolicited.

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Context Bindings to concept domain(s):
  ActMoodProposal in Realm: C1 as CNE

Description:

A non-mandated intent to perform an act. Used to record intents that are explicitly not Orders. Professional responsibility for the 'proposal' may or may not be present.

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Description:

A non-mandated intent to perform an act where a level of professional responsibility is being accepted by making the proposal.

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Description:

A request or order for a service is an intent directed from a placer (request author) to a fulfiller (service performer).

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."

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.

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Description:

Periods of time on a schedule for a resource. Appointments occupy sets of one or more booked slots. A slot that is open for appointments is considered available and a slot that is held back for administrative purposes is considered blocked. A Resource slot that is "tentatively" booked is referred to as reserved.

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Description:

Definition:An act that may occur in the future and which is regarded as undesirable. The essential feature of a risk is that if it occurs this would be regarded as a marker of a negative outcome or of deterioration towards a negative outcome. Recording a risk indicates that it is seen as more likely to occur in the subject than in a general member of the population but does not mean it is expected to occur.

Examples:Increased risk of DVT, at risk for sub-acute bacterial endocarditis.

Discussion:Note: An observation in RSK mood expresses the undesirable act, and not the underlying risk factor. A risk factor that is present (e.g. obesity, smoking, etc) should be expressed in event mood. INT (intent) reflects a plan for the future, which is a declaration to do something. This contrasts with RSK (risk), which is the potential that something negative will occur that may or may not ever happen. GOL (goal) reflects a hope to achieve something. EXPEC (expectation) is the prediction of a positive or negative event. This contrasts with RSK (risk), which is the potential that something negative will occur that may or may not ever happen, and may not be expected to happen.

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Description:

Description:These are moods describing activities as they progress in the business cycle, from defined, through planned and ordered to completed, and any applicable criterion or condition over actual and potential services that must apply for an associated service to be considered.

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Description:

A grouping of Definition, Event. These specific moods are used in control wrapper override acts. The domain is restricted to acts that are possible to occur or have already occurred.

Has Associated Concept Properties:
  Name:Class: DefinitionOrEvent

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Has Associated Concept Properties:
  Name:Class: DefinitionEventOrder

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Description:

Used to enumerate the moods that an observation can take within the body of a clinical document.

Has Associated Concept Properties:
  Name:Class: DocumentProcess

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Has Associated Concept Properties:
  Name:Class: ProposeProcess

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Description:

A constraint domain for RMIM design.

Has Associated Concept Properties:
  Name:Class: Process

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Description:

A grouping of Order, Promise. These specific moods are used in orders.

Has Associated Concept Properties:
  Name:Class: OrderPromise

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Description:

A grouping of Order, Promise and Event moods.

Has Associated Concept Properties:
  Name:Class: ProcessPromise

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Description:

Enumerates the moods that an Act can take when describing privileges.

Has Associated Concept Properties:
  Name:Class: Permission

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Has Associated Concept Properties:
  Name:Class: AppointmentCycle

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Description:

Used to enumerate the moods that an act can take within the body of a clinical document.

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Description:

Used to enumerate the moods that an encounter can take within the body of a clinical document.

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Description:

Used to enumerate the moods that a procedure can take within the body of a clinical document.

Content from code system(s):
1  ActMood [2.16.840.1.113883.5.1001]

Description:

Used to enumerate the moods that a substance administration can take within the body of a clinical document.