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

Difference between revisions of "Composite Message Type"

From HL7Wiki
Jump to navigation Jump to search
 
Line 1: Line 1:
The set of static model definitions (wrappers and message types) that define the structures of the data that is transmitted by the [[Interaction]].  Committees will explicitly identify all message types (transmission wrapper, control act wrapper and payload) associated with a particular interaction.
+
The set of static model definitions (wrappers and message types) that define the structures of the data that is transmitted by the [[Interaction]].  Committees will explicitly identify all message types (e.g. transmission wrapper, control act wrapper and payload) associated with a particular interaction.
  
 
In terms of structure an Interaction can be either a [[Message Based Interaction|Message-based Interaction]] or a [[Batch Based Interaction|Batch-based Interaction]]. Interactions consist of:
 
In terms of structure an Interaction can be either a [[Message Based Interaction|Message-based Interaction]] or a [[Batch Based Interaction|Batch-based Interaction]]. Interactions consist of:
Line 6: Line 6:
 
#a [[Trigger Event Control Act Wrapper]] (conditional)
 
#a [[Trigger Event Control Act Wrapper]] (conditional)
 
#[[Domain Content]] (optional)
 
#[[Domain Content]] (optional)
 +
#[[Query Definition]] (conditional)
 +
 +
In the future, additional levels of wrappers may be supported.  For example, a "claims" message might be define as a wrapper which itself wraps an Act representing the billable act for which an insurance claim is being made.

Latest revision as of 15:59, 14 December 2005

The set of static model definitions (wrappers and message types) that define the structures of the data that is transmitted by the Interaction. Committees will explicitly identify all message types (e.g. transmission wrapper, control act wrapper and payload) associated with a particular interaction.

In terms of structure an Interaction can be either a Message-based Interaction or a Batch-based Interaction. Interactions consist of:

  1. a Batch Wrapper (conditional upon it being a Batch)
  2. a Transmission Wrapper
  3. a Trigger Event Control Act Wrapper (conditional)
  4. Domain Content (optional)
  5. Query Definition (conditional)

In the future, additional levels of wrappers may be supported. For example, a "claims" message might be define as a wrapper which itself wraps an Act representing the billable act for which an insurance claim is being made.