This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Requirements-Dynamic Model"

From HL7Wiki
Jump to navigation Jump to search
Line 23: Line 23:
 
| Identifies a possible set of actions to be taken in response to the receipt of an interaction
 
| Identifies a possible set of actions to be taken in response to the receipt of an interaction
 
|}
 
|}
 +
 +
'''Interaction'''
 +
Interactions are at the heart of messaging. The formal definition of an interaction is:
 +
 +
A unique association between a specific message type (information transfer), a particular trigger event that initiates or "triggers" the transfer, and the Receiver Responsibilities (in terms of response interactions) associated with the receipt of the Interaction.
 +
 +
A single Interaction explicitly answers the questions:
 +
 +
1.What the particular message type is
 +
 +
2.What caused the message to be sent
 +
 +
3.How a receiving system knows when it has to send a particular type of response message.
 +
 +
As the list above indicates, each interaction is related to a trigger event, a message type and receiver responsibilities. In the Version 3 specification, the Interactions are presented with a name, the artifact ID, and a table that lists the sending and receiving application roles, the trigger event, the message type, the Event type and the Wrapper types. The sending and receiving application roles as well as the event type are listed in the Version 3 specification for information only
 +
 +
The Event type is the Trigger Event type. Valid values are interaction-based, state-transition based, user-based or unspecified.
 +
 +
The Wrapper types refer to the Transmission Wrapper and the Trigger Event Control Act Wrapper. The Trigger Event Control Act wrapper is a conditional wrapper which contains domain specific administrative information related to that which triggered the interaction. This type of wrapper does not appear with HL7 messages where there is no additional context that is needed to be exchanged dynamically, or with HL7 messages that are carrying commands to coordinate the operation of message handling services.
  
 
'''Trigger Event'''
 
'''Trigger Event'''
Line 32: Line 51:
  
  
{| border="2" cellspacing="0" cellpadding="3" width="400"
+
{| border="2" cellspacing="0" cellpadding="3" width="500"
 
| '''Type'''  
 
| '''Type'''  
 
| '''Description'''
 
| '''Description'''
Line 50: Line 69:
  
 
Most trigger events are State-Transition based and will be encountered when reading the dynamic message model information defined to support a particular message interaction. Some trigger events may be based on more than one state transition, which are assumed to occur simultaneously. In some cases, trigger events may not fall into any of the three categories defined in the above list. In these cases, Unspecified will appear as the Type. The trigger event Type, when specified, affects the responsibilities of the interactions initiated by that trigger event.  
 
Most trigger events are State-Transition based and will be encountered when reading the dynamic message model information defined to support a particular message interaction. Some trigger events may be based on more than one state transition, which are assumed to occur simultaneously. In some cases, trigger events may not fall into any of the three categories defined in the above list. In these cases, Unspecified will appear as the Type. The trigger event Type, when specified, affects the responsibilities of the interactions initiated by that trigger event.  
 +
  
  

Revision as of 16:15, 19 October 2009