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 (typo)
Line 1: Line 1:
'''Transport''' is the abstract term used by the HL7 community for the infrastructure serving the HL7 messages transfer from the Sending Application Role to the Receiving Application Role. In other words, from the HL7 perspective transport refers to OSI layers 1-6. The OSI layers 1-6 are perceived by the HL7 applications as the unified interface for message transfer, meaning that a HL7 application is not required to (and usually doesn't) posses any specific knowledge for technology components residing at OSI layers 1-5.
+
'''Transport''' is the abstract term used by the HL7 community for the infrastructure that serves the HL7 messages transfer from the Sending Application Role to the Receiving Application Role. In other words, from the HL7 perspective transport refers to OSI layers 1-6. The OSI layers 1-6 are perceived by the HL7 applications as the unified interface for message transfer, meaning that a HL7 application is not required to (and usually doesn't) posses any specific knowledge for technology components residing at OSI layers 1-5.

Revision as of 09:11, 8 March 2006

Transport is the abstract term used by the HL7 community for the infrastructure that serves the HL7 messages transfer from the Sending Application Role to the Receiving Application Role. In other words, from the HL7 perspective transport refers to OSI layers 1-6. The OSI layers 1-6 are perceived by the HL7 applications as the unified interface for message transfer, meaning that a HL7 application is not required to (and usually doesn't) posses any specific knowledge for technology components residing at OSI layers 1-5.