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

Difference between revisions of "Control Act"

From HL7Wiki
Jump to navigation Jump to search
(add CACT definition)
m (typo)
Line 4: Line 4:
 
#The [[Trigger Event Control Act Wrapper]], a Control Act used to convey details of the [[Trigger Event]] which caused the [[Interaction]] to be sent.
 
#The [[Trigger Event Control Act Wrapper]], a Control Act used to convey details of the [[Trigger Event]] which caused the [[Interaction]] to be sent.
 
#A Control Act contained in the [[Domain Payload]] to convey change tracking information (historic trigger events) related to an [[Act]]. These control acts are used as references to triggers that have happened related to the focal act at an earlier point in time. All of them will be in [[Event Mood]].
 
#A Control Act contained in the [[Domain Payload]] to convey change tracking information (historic trigger events) related to an [[Act]]. These control acts are used as references to triggers that have happened related to the focal act at an earlier point in time. All of them will be in [[Event Mood]].
#A Control Act contained in the [[Domain Payload]] (or possibly [[Trigger Event Control Act Wrapper]]) to reference "a trigger event has not happened yet" (i.e. in [[RQO Mood]]). The underlying use-cases still have to be discussed.
+
#A Control Act contained in the [[Domain Payload]] (or possibly [[Trigger Event Control Act Wrapper]]) to reference "a trigger event that has not happened yet" (i.e. in [[RQO Mood]]). The underlying use-cases still have to be discussed.

Revision as of 12:32, 2 March 2006

A Control Act (to quote the definition of the CACT classcode) is an Act representing a system action such as the change of state of another act or the initiation of a query. All control acts represent trigger events in the HL7 context. ControlActs may occur in different moods.

The following use cases for Control Acts are known to exist:

  1. The Trigger Event Control Act Wrapper, a Control Act used to convey details of the Trigger Event which caused the Interaction to be sent.
  2. A Control Act contained in the Domain Payload to convey change tracking information (historic trigger events) related to an Act. These control acts are used as references to triggers that have happened related to the focal act at an earlier point in time. All of them will be in Event Mood.
  3. A Control Act contained in the Domain Payload (or possibly Trigger Event Control Act Wrapper) to reference "a trigger event that has not happened yet" (i.e. in RQO Mood). The underlying use-cases still have to be discussed.