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) (add secondary usage of word as well) |
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 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 session-level | + | #A specific session-level [[Transport Protocol]] (OSI layer 1-3), for example TCP/IP, SMTP, RS232 or LU6.2. |
Revision as of 15:07, 8 March 2006
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 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 session-level Transport Protocol (OSI layer 1-3), for example TCP/IP, SMTP, RS232 or LU6.2.