This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Transport"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| − | In HL7 '''Transport''' is an ambiguous term, which so far has been used to identify one of the following: | + | In HL7, '''Transport''' is an ambiguous term, which so far has been used to identify one of the following: |
#The technologies and protocols at the [[Messaging Infrastructure Layer]] which provide the infrastructure that serves the HL7 messages transfer from the HL7 [[Sender]] to HL7 [[Receiver]] (see also [[Application Architecture]]). In other words, once the message has been serialized using one of the HL7 ITS's available, it the the responsibility of "transport" to provide the machinery to get the message from A to B. The examples include MLLP, Web Services, ebXML | #The technologies and protocols at the [[Messaging Infrastructure Layer]] which provide the infrastructure that serves the HL7 messages transfer from the HL7 [[Sender]] to HL7 [[Receiver]] (see also [[Application Architecture]]). In other words, once the message has been serialized using one of the HL7 ITS's available, it the the responsibility of "transport" to provide the machinery to get the message from A to B. The examples include MLLP, Web Services, ebXML | ||
#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). | #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). | ||
Revision as of 10:58, 2 May 2007
In HL7, Transport is an ambiguous term, which so far has been used to identify one of the following:
- The technologies and protocols at the Messaging Infrastructure Layer which provide the infrastructure that serves the HL7 messages transfer from the HL7 Sender to HL7 Receiver (see also Application Architecture). In other words, once the message has been serialized using one of the HL7 ITS's available, it the the responsibility of "transport" to provide the machinery to get the message from A to B. The examples include MLLP, Web Services, ebXML
- 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).
The suggesttion is to add the first bullet as the defintion of the Transport to HL7 Glossary, and discourage any other usage of the term.
--Miroslav Koncar 05:56, 2 May 2007 (CDT)
