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

Difference between revisions of "Transport"

From HL7Wiki
Jump to navigation Jump to search
m
Line 1: Line 1:
−
'''Transport''' is an ambiguous term, which is used in HL7 to identify the following:
+
In HL7 '''Transport''' is an ambiguous term, which so far has been used to identify one of 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 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 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).
  
−
:(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.  
+
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.
 +
 
 +
--[[User:Miroslav|Miroslav Koncar]] 05:56, 2 May 2007 (CDT)
  
 
[[Category:ATS Glossary]]
 
[[Category:ATS Glossary]]

Revision as of 10:56, 2 May 2007

In HL7 Transport is an ambiguous term, which so far has been used to identify one of the following:

  1. 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
  2. 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)

Retrieved from "https://wiki.hl7.org/w/index.php?title=Transport&oldid=12425"