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

Difference between revisions of "Trigger Event Control Act Wrapper"

From HL7Wiki
Jump to navigation Jump to search
(new item)
 
(update)
Line 1: Line 1:
A [[Wrapper]] that contains domain specific administrative information related to the "[[Controlled Event]]" which is being communicated as a messaging [[Interaction]]. The control event wrapper is used only in messages that convey status, or in commands for logical operations being coordinated between applications (e.g., the coordination of query specification/query response interactions).  
+
A [[Wrapper]] that contains domain specific administrative information related to the "Controlled [[Trigger Event]]" which is being communicated as a messaging [[Interaction]]. The control event wrapper is used in messages that convey status, or in commands for logical operations being coordinated between applications (e.g., the coordination of query specification/query response interactions).
 +
 
 +
The core of the wrapper is formed by a Control Act (CACT) class. If it is related to a trigger event which has happened, the Control Act will be in EVN mood.
 +
 
 +
Note that Control Acts also appear in the payload of an interaction. 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.
 +
 
 +
In general Control Acts are always in Event mood, unless they reference "a trigger event has not happened yet". There are some (exotic) use-cases for this however.  
  
 
{{Category:Glossary}}
 
{{Category:Glossary}}
{{Category:CQ}}
 

Revision as of 06:29, 15 November 2005

A Wrapper that contains domain specific administrative information related to the "Controlled Trigger Event" which is being communicated as a messaging Interaction. The control event wrapper is used in messages that convey status, or in commands for logical operations being coordinated between applications (e.g., the coordination of query specification/query response interactions).

The core of the wrapper is formed by a Control Act (CACT) class. If it is related to a trigger event which has happened, the Control Act will be in EVN mood.

Note that Control Acts also appear in the payload of an interaction. 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.

In general Control Acts are always in Event mood, unless they reference "a trigger event has not happened yet". There are some (exotic) use-cases for this however.

This glossary item is based on v3. The wording may have been extended by later edits to provide additional detail.