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

Gateway

From HL7Wiki
Revision as of 17:31, 30 November 2006 by Miroslav (talk | contribs)
Jump to navigation Jump to search
Application Architecture

A Gateway is an HL7-artefacts aware application which executes business rules, and forwards/ copies/ amends/ transforms interactions (messages or batched messages) based on those business rules. In order to perform those business rules, a Gateway is always an HL7 application that is listed as the receiver of the incoming interactions and sender of the outgoing interactions (just like any other HL7 Application).

  • Question (Phoenix Action Item, refering to ATS Line item 52) - Are the Gateways always trusted? Is there a use case or a possibility of a highly distributed environment where Gateways are *not* trusted?
    • (Miroslav) This is out of the scope of the ATS and is listed in the Known Issues section of the ATS R1 C2 ballot edition. Personally, I see Gateways the same way like any other HL7 applications, where security and trust issues depend on the business level contracts, network and application configuration, security provisioning etc.
  • Question - what is the difference between a "gateway" and a "registry"? Charliemccay 05:17, 10 Aug 2006 (CDT)
    • See Registry. Under some circumstances a Registry could possible deemed to be a Gateway, it depends on the functionality that is performed by the registry. Gateway is meant to be a middleware role.

Back to the Open ATS Issues