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

Difference between revisions of "Communication Process Model"

From HL7Wiki
Jump to navigation Jump to search
(add figure)
(add detail)
Line 1: Line 1:
[[Image:Dynamic_patterns.gif|300px|right|thumb|Interaction and Transmission Patterns]]
+
[[Image:Dynamic_patterns.gif|300px|right|thumb|Interaction and
 +
Transmission Patterns]]
  
An Interaction Pattern is a sequence of interactions that are related because they belong to one and the same business process. An Interaction Pattern consists of 1 or more [[Transmission Pattern]]s. The interactions may be linked by business process identifiers such as "Placer Order ID", "queryId", "PrescriptionID".
+
An Interaction Pattern is a sequence of interactions that are related
 +
because they belong to one and the same business process. An Interaction
 +
Pattern consists of 1 or more [[Transmission Pattern]]s. The
 +
interactions may be linked by business process identifiers such as
 +
"Placer Order ID", "queryId", "PrescriptionID".
  
*Whether or not [[Syntax Level Acknowledgement]] interactions are used is not relevant for an Interaction Pattern, this is relevant at the Transmission level only.  
+
At this level of abstraction the delivery method of the interactions is of no relevance whatsoever.
*Most [[Storyboard Diagrams]] in the HL7 v3 standard describe an Interaction Pattern.  
+
 
 +
*The use of some Interactions (e.g. [[Syntax Level Acknowledgement]],
 +
[[Polling Interaction]], [[Query Continuation/Abort Interaction]] and
 +
[[Batch Based Interaction]]s) is not relevant for an Interaction
 +
Pattern, this is relevant at the Transmission level only.
 +
*Most [[Storyboard Diagrams]] in the HL7 v3 standard describe an
 +
Interaction Pattern.
  
 
=== Examples ===
 
=== Examples ===
  
A Laboratory Order, followed by a Promise, a modification of the Order by the Laboratory,  and a final labresult constitutes an interaction. The interaction pattern consists of 3 Transmission Patterns. The initiating interaction of each Transmission Pattern results in messages linked to it by means of the Transmission Wrapper.
+
A Laboratory Order, followed by a Promise, a modification of the Order
 +
by the Laboratory,  and a final labresult constitutes an interaction.
 +
The interaction pattern consists of 3 Transmission Patterns. The
 +
initiating interaction of each Transmission Pattern results in messages
 +
linked to it by means of the Transmission Wrapper.

Revision as of 00:03, 17 December 2005

Interaction and Transmission Patterns

An Interaction Pattern is a sequence of interactions that are related because they belong to one and the same business process. An Interaction Pattern consists of 1 or more Transmission Patterns. The interactions may be linked by business process identifiers such as "Placer Order ID", "queryId", "PrescriptionID".

At this level of abstraction the delivery method of the interactions is of no relevance whatsoever.

Polling Interaction, Query Continuation/Abort Interaction and Batch Based Interactions) is not relevant for an Interaction Pattern, this is relevant at the Transmission level only.

Interaction Pattern.

Examples

A Laboratory Order, followed by a Promise, a modification of the Order by the Laboratory, and a final labresult constitutes an interaction. The interaction pattern consists of 3 Transmission Patterns. The initiating interaction of each Transmission Pattern results in messages linked to it by means of the Transmission Wrapper.