This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Interface Engine"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) |
Rene spronk (talk | contribs) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | An Interface Engine ( | + | '''Glossary Definition:''' An Interface Engine (a.k.a. Message Broker) is a term used to refer to a kind of middleware application which is used to transform, route, clone and translate messages. |
| − | + | == Details == | |
| − | + | One and the same interface engine can play multiple [[Middleware Role]]s, e.g. it can be a [[Gateway]], be a [[Bridge]], a [[Transformer Bridge]] or an [[Intermediary]]. The key distinction is the business level scenario. If an interface engine is required to perform business rules and application level responsibilities, than it's a [[Gateway]] and is listed as the [[Receiver]] in the HL7 Message. If it just needs to transform from one [[ITS]] to another, it's a Bridge. If it needs to transform from one [[Transport Protocol]] to another, it's an Intermediary. | |
| − | *(Miroslav) Message Broker | + | The roles that an interface engine plays depend on the use cases encountered in the healthcare enterprise. If a role conforms to one of the [[Middleware Role]]s they need to comply to certain rules for these roles which are listed and specified in the [[Abstract Transport Specification]]. |
| + | |||
| + | == FAQ == | ||
| + | *(Miroslav) Imagine that the interface engine (or: Message Broker) distributes the incomming messages to specified destinations according to predefined business rules. What role does the Message Broker play if it needs to send an incoming HL7 message to x additional locations (e.g. as the notification message to 3rd party that a lab order took place). It needs to change a HL7 message, list itself as the sender - therefore it's the Gateway role? | ||
| + | **Yes. The interface engine performs a business process, therefore it is a [[Gateway]]. [[User:Rene spronk|Rene spronk]] 13:41, 18 Mar 2006 (CST) | ||
| + | |||
| + | [[Category:INM Glossary]] | ||
| + | [[Category:ATS Glossary]] | ||
Latest revision as of 06:43, 21 March 2006
Glossary Definition: An Interface Engine (a.k.a. Message Broker) is a term used to refer to a kind of middleware application which is used to transform, route, clone and translate messages.
Details
One and the same interface engine can play multiple Middleware Roles, e.g. it can be a Gateway, be a Bridge, a Transformer Bridge or an Intermediary. The key distinction is the business level scenario. If an interface engine is required to perform business rules and application level responsibilities, than it's a Gateway and is listed as the Receiver in the HL7 Message. If it just needs to transform from one ITS to another, it's a Bridge. If it needs to transform from one Transport Protocol to another, it's an Intermediary.
The roles that an interface engine plays depend on the use cases encountered in the healthcare enterprise. If a role conforms to one of the Middleware Roles they need to comply to certain rules for these roles which are listed and specified in the Abstract Transport Specification.
FAQ
- (Miroslav) Imagine that the interface engine (or: Message Broker) distributes the incomming messages to specified destinations according to predefined business rules. What role does the Message Broker play if it needs to send an incoming HL7 message to x additional locations (e.g. as the notification message to 3rd party that a lab order took place). It needs to change a HL7 message, list itself as the sender - therefore it's the Gateway role?
- Yes. The interface engine performs a business process, therefore it is a Gateway. Rene spronk 13:41, 18 Mar 2006 (CST)
