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

Difference between revisions of "Bridge"

From HL7Wiki
Jump to navigation Jump to search
(add image)
m (typo)
Line 1: Line 1:
A[[Image:Ats_nonpeer.gif|275px|right|thumb|Application Architecture]]
+
[[Image:Ats_nonpeer.gif|275px|right|thumb|Application Architecture]]
'''Bridge''' is an application that contains 2 or more [[Message Adapter]]s: it provides message protocol translation (i.e. relaying) and/or message routing capabilities. The primary purpose of HL7 Bridges is to provide transports protocol translation management (i.e. relaying) in heterogeneous healthcare communication environments. An example would be the relaying of messages from Web Services to ebXML transport and vice versa.
+
A '''Bridge''' is an application that contains 2 or more [[Message Adapter]]s: it provides message protocol translation (i.e. relaying) and/or message routing capabilities. The primary purpose of HL7 Bridges is to provide transports protocol translation management (i.e. relaying) in heterogeneous healthcare communication environments. An example would be the relaying of messages from Web Services to ebXML transport and vice versa.
  
 
----
 
----
  
 
Back to the [[Open ATS Issues]]
 
Back to the [[Open ATS Issues]]

Revision as of 15:59, 10 March 2006

Application Architecture

A Bridge is an application that contains 2 or more Message Adapters: it provides message protocol translation (i.e. relaying) and/or message routing capabilities. The primary purpose of HL7 Bridges is to provide transports protocol translation management (i.e. relaying) in heterogeneous healthcare communication environments. An example would be the relaying of messages from Web Services to ebXML transport and vice versa.


Back to the Open ATS Issues