This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Sender"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) |
|||
| Line 1: | Line 1: | ||
[[Image:Ats msg traversal New.gif|275px|right|thumb|HL7 Messaging Architecture]] | [[Image:Ats msg traversal New.gif|275px|right|thumb|HL7 Messaging Architecture]] | ||
| − | A Sender embeds the sending | + | A Sender in the context of HL7 embeds the sending HL7 Application and the [[Messaging Adapter]] responsible for [[Messaging Protocol]] configuration. A Sender implements business rules according to the HL7 Trigger Event and Interaction definition, and prepares the HL7 message for the delivery facilitated by the [[Messaging Protocol]] in the [[Messaging Infrastructure Layer]]. |
| + | |||
| + | == Notes == | ||
| + | *Question: "Why do we embed Messaging Adapter in the concepts of the Sender and Receiver as well?" | ||
| + | **Answer: "The reason why we have included the Messaging Adapter to the Sender and Receiver is very simple - without the Messaging Adapter the HL7 Application, which is able to produce and consume HL7 message (including object representation and serialization using the ITS) is not able to send the message anywhere, so no point of calling something "a Sender" where there's no sending or receiving associated to it. | ||
Revision as of 11:05, 2 May 2007
A Sender in the context of HL7 embeds the sending HL7 Application and the Messaging Adapter responsible for Messaging Protocol configuration. A Sender implements business rules according to the HL7 Trigger Event and Interaction definition, and prepares the HL7 message for the delivery facilitated by the Messaging Protocol in the Messaging Infrastructure Layer.
Notes
- Question: "Why do we embed Messaging Adapter in the concepts of the Sender and Receiver as well?"
- Answer: "The reason why we have included the Messaging Adapter to the Sender and Receiver is very simple - without the Messaging Adapter the HL7 Application, which is able to produce and consume HL7 message (including object representation and serialization using the ITS) is not able to send the message anywhere, so no point of calling something "a Sender" where there's no sending or receiving associated to it.
