This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Messaging Protocol"
Jump to navigation
Jump to search
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | Definition: Messaging Protocol refers to the rules, formats, and functions implemented by the [[Messaging Infrastructure Layer]] for exchanging HL7 messages | + | Definition: Messaging Protocol refers to the rules, formats, and functions implemented by the [[Messaging Infrastructure Layer]] for exchanging HL7 messages. Messaging Protocol examples include Web Services, ebMS and MLLP. |
<p> | <p> | ||
Addtional notes: | Addtional notes: | ||
| − | * | + | *Process walkthrough: HL7 application will assemble the message according to the HL7 standard, and format it according to the rules of an HL7 ITS. As the next step message gets passed on to the [[Messaging Infrastructure Layer]], which will use Messaging Protocol for the message delivery from [[Source]] to the [[Destination]]. The same process takes place on the [[Destination]] side. |
| + | *Messaging protocol term is often used to refer email protocols such as SMTP, IBM's SNADS, etc (see [http://www.answers.com Answers.com]). From the HL7 perspective, we refer to these technologies as the application transport (or transfer) protocols, to distinguish the ability of a messaging protocol (such as ebMS) to use any application transport protocol to which the binding is defined (e.g. FTP, HTTP, JMS) | ||
*The messaging system usually includes messaging agents (which in this case would be the HL7 [[Sender]] and [[Receiver]]), transfer agents and the messaging store that together are facilitated by the [[Messaging Infrastructure Layer]] in the HL7 Application architecture. | *The messaging system usually includes messaging agents (which in this case would be the HL7 [[Sender]] and [[Receiver]]), transfer agents and the messaging store that together are facilitated by the [[Messaging Infrastructure Layer]] in the HL7 Application architecture. | ||
| − | --[[User:Miroslav|Miroslav Koncar]] | + | --[[User:Miroslav|Miroslav Koncar]] 13:00, 10 September 2006 (CDT) |
Latest revision as of 18:04, 10 September 2006
Definition: Messaging Protocol refers to the rules, formats, and functions implemented by the Messaging Infrastructure Layer for exchanging HL7 messages. Messaging Protocol examples include Web Services, ebMS and MLLP.
Addtional notes:
- Process walkthrough: HL7 application will assemble the message according to the HL7 standard, and format it according to the rules of an HL7 ITS. As the next step message gets passed on to the Messaging Infrastructure Layer, which will use Messaging Protocol for the message delivery from Source to the Destination. The same process takes place on the Destination side.
- Messaging protocol term is often used to refer email protocols such as SMTP, IBM's SNADS, etc (see Answers.com). From the HL7 perspective, we refer to these technologies as the application transport (or transfer) protocols, to distinguish the ability of a messaging protocol (such as ebMS) to use any application transport protocol to which the binding is defined (e.g. FTP, HTTP, JMS)
- The messaging system usually includes messaging agents (which in this case would be the HL7 Sender and Receiver), transfer agents and the messaging store that together are facilitated by the Messaging Infrastructure Layer in the HL7 Application architecture.
--Miroslav Koncar 13:00, 10 September 2006 (CDT)
