This wiki has undergone a migration to Confluence found Here
Transport
Revision as of 06:41, 21 March 2006 by Rene spronk (talk | contribs)
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.
- (Miroslav) Question - does this refers to the MLLP transport only? Do we have anywhere in the standard that we use the word transport for 1-3 OSI layers in SOA environments (which would be a potential problem in interpretation of the term)?
- All the above states is that there are 2 known usages of the word "Transport". If SOA environments have a third one (which is different) then it should simply be added. The word "Transport" is too generic to assign 1 single meaning to it within HL7. Rene spronk 09:27, 10 Mar 2006 (CST)
Back to the Open_ATS_Issues
