Interface Engine

From HL7Wiki
Revision as of 15:26, 7 March 2006 by Rene spronk (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Discussion

  • (Miroslav) The same interface engine can sometimes play a role of a Gateway, and in other scenarios just be a Bridge or an Intermediary. The key distinction are the business level scenarios, interactions and use cases. 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 is yet again another interface engine that distributes the incomming messages to specified destinations according to the business rules. A Message Broker is usually required to perform a Bridge functionality. However, the question is, what role the Message Broker is playing if it needs to send an incomming HL7 message to x locations (e.g. as the notification that an lab order took place). It needs to change a HL7 message, list itself as the sender - therefore it's the Gateway role?

Copyright © Health Level Seven International ® ALL RIGHTS RESERVED. The reproduction of this material in any form is strictly forbidden without the written permission of the publisher.