This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "Mood"

From HL7Wiki
Jump to navigation Jump to search
(new page, from RIM)
 
Line 1: Line 1:
 
The Mood of an Act Class is a code distinguishing whether an Act is conceived of as a factual statement or in some other manner as a command, possibility, goal, etc.  
 
The Mood of an Act Class is 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.  
+
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, the state of an Act-instance can go though all state transations as defined in the RIM.
 +
**Note: D-MIMs and R-MIMs may contain Acts that don't have a fixed mood. Act-instances (on the wire in an interaction) have to have a fixed mood.
  
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 ActRelationships.
  
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 ActRelationships.
+
See also: [[EVN Mood]], [[RQO Mood]].

Revision as of 06:45, 29 April 2007

The Mood of an Act Class is 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, the state of an Act-instance can go though all state transations as defined in the RIM.

    • Note: D-MIMs and R-MIMs may contain Acts that don't have a fixed mood. Act-instances (on the wire in an interaction) have to have a fixed mood.

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

See also: EVN Mood, RQO Mood.