This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Transport"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) |
|||
| Line 1: | Line 1: | ||
'''Transport''' is an ambiguous term, which is used in HL7 to identify the following: | '''Transport''' is an ambiguous term, which is used in HL7 to identify the following: | ||
| − | #The entire infrastructure that serves the HL7 messages transfer from the Sending [[Application Role]] to the Receiving [[Application Role]]. In other words: all transport activities supported by OSI layers 1-6. The OSI layers 1-6 are perceived by the [[HL7 Application]]s as the unified interface for message transfer, meaning that an [[HL7 Application]] is not required to (and usually doesn't) posses any specific knowledge for technology components residing at OSI layers 1-5 | + | #The [[Messaging Infrastructure Layer]] which contains the entire infrastructure that serves the HL7 messages transfer from the Sending [[Application Role]] to the Receiving [[Application Role]]. In other words: all transport activities supported by OSI layers 1-6. The OSI layers 1-6 are perceived by the [[HL7 Application]]s as the unified interface for message transfer, meaning that an [[HL7 Application]] is not required to (and usually doesn't) posses any specific knowledge for technology components residing at OSI layers 1-5. |
| − | #A specific [[Transport Protocol]] (OSI layer 1-4) that facilitates the routing, switching and transparent transfer of data between end systems, or hosts, and is responsible for end-to-end error recovery and flow control (for example TCP/IP, UDP/IP, NETBEUI). | + | #A specific [[Transport Protocol]] (OSI layer 1-4) that facilitates the routing, switching and transparent transfer of data between end systems, or hosts, and is responsible for end-to-end error recovery and flow control (for example FTP, MLLP ''based on'' TCP/IP, UDP/IP, NETBEUI). |
| − | + | ||
| − | + | :(Miroslav) Additional comment - we need to ensure that SOA SIG and other Messaging Infrastructure technologies use the word transport in the right manner as well. | |
| − | |||
Revision as of 05:43, 13 April 2006
Transport is an ambiguous term, which is used in HL7 to identify the following:
- The Messaging Infrastructure Layer which contains the entire infrastructure that serves the HL7 messages transfer from the Sending Application Role to the Receiving Application Role. In other words: all transport activities supported by OSI layers 1-6. The OSI layers 1-6 are perceived by the HL7 Applications as the unified interface for message transfer, meaning that an HL7 Application is not required to (and usually doesn't) posses any specific knowledge for technology components residing at OSI layers 1-5.
- A specific Transport Protocol (OSI layer 1-4) that facilitates the routing, switching and transparent transfer of data between end systems, or hosts, and is responsible for end-to-end error recovery and flow control (for example FTP, MLLP based on TCP/IP, UDP/IP, NETBEUI).
- (Miroslav) Additional comment - we need to ensure that SOA SIG and other Messaging Infrastructure technologies use the word transport in the right manner as well.
Back to the Open_ATS_Issues
