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

Difference between revisions of "Gateway"

From HL7Wiki
Jump to navigation Jump to search
m
 
(9 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{INM Workitem}}
+
'''Gateway'''
[[Image:Ats_nonpeer.gif|275px|right|thumb|Application Architecture]]
+
==SAIF-CD Definition==
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]]).
+
*A process [[Flow_elements|flow element]] that controls the divergence and/or convergence of [[Sequence_flow|sequence flows]].
*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?
+
**It allows branching, forking, merging, and joining of process flow.
**(Miroslav) I feel that this should be out of the scope of the ATS discussion, since this very much depends on the business scenarios. For the sake of the argument, I see Gateways the same way like any other HL7 applications, which should but don't have to be trusted in all the cases. This depends on business level contracts, netowork and application configuration, security provisioning etc. If we need to put something in the doc, I'd suggest that we say that "the Gateways, like any other sending HL7 applications should always be trusted, however this depends on many different network/application configuration parameters. What implementors need to be aware of is that if a Gateway is not trusted, Receivers will probably drop all further communication with the Gateway from their side.
+
**REF: [[SAIF-CD|SAIF-CD]]:Figure 11:  BF language concepts and relationships for describing process semantics
*Question - what is the difference between a "gateway" and a "registry"? [[User:Charliemccay|Charliemccay]] 05:17, 10 Aug 2006 (CDT)
+
 
 +
[[Category:SAIF Glossary]]
 +
 
 +
==HL7 Abstract Transport Definition==
 +
[[Image:Ats_gateway_bridge_inter.gif|275px|right|thumb|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. From the Sender's point of view, the Gateway is considered as the consumer of the HL7 message produced and sent by the original [[Sender]]. Consequently, Gateway is always the HL7 application that is listed as the [[Receiver]] of the incoming interactions and [[Sender]] of the outgoing interactions (just like any other [[HL7 Application]]). What happens with the message once it has been consumed by the Gateway depends on the business rules.
 +
 
 +
=== Notes ===
 +
 
 +
*Question - Are the Gateways always trusted? Is there a use case or a possibility of a highly distributed environment where Gateways are *not* trusted?
 +
**This is out of the scope of the ATS and is listed in the Known Issues section of the ATS R1 C2 ballot edition. HL7 Gateways behave the same as like any other HL7 application, where security and trust issues depend on the business level contracts, network and application configuration, security provisioning etc. We do not (nor we should) elaborate this on the level of HL7v3 normative specs.
 +
*Question - what is the difference between a "Gateway" and a "Registry"? [[User:Charliemccay|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.
 +
*Question - if I have an Intermediary that is responsible to transform HL7 Version X messages to HL7 Version Y, is that a Gateway or not?
 +
**Answer - no. If an Intermediary provides the fucntionality of tranforming a message from one flavour of the HL7 standard to another, without any change to semantic meaning to the message, it is a [[Bridge]] and not a Gateway
  
 
----
 
----

Latest revision as of 16:46, 10 November 2011

Gateway

SAIF-CD Definition

  • A process flow element that controls the divergence and/or convergence of sequence flows.
    • It allows branching, forking, merging, and joining of process flow.
    • REF: SAIF-CD:Figure 11: BF language concepts and relationships for describing process semantics

HL7 Abstract Transport Definition

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. From the Sender's point of view, the Gateway is considered as the consumer of the HL7 message produced and sent by the original Sender. Consequently, Gateway is always the HL7 application that is listed as the Receiver of the incoming interactions and Sender of the outgoing interactions (just like any other HL7 Application). What happens with the message once it has been consumed by the Gateway depends on the business rules.

Notes

  • Question - Are the Gateways always trusted? Is there a use case or a possibility of a highly distributed environment where Gateways are *not* trusted?
    • This is out of the scope of the ATS and is listed in the Known Issues section of the ATS R1 C2 ballot edition. HL7 Gateways behave the same as like any other HL7 application, where security and trust issues depend on the business level contracts, network and application configuration, security provisioning etc. We do not (nor we should) elaborate this on the level of HL7v3 normative specs.
  • 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.
  • Question - if I have an Intermediary that is responsible to transform HL7 Version X messages to HL7 Version Y, is that a Gateway or not?
    • Answer - no. If an Intermediary provides the fucntionality of tranforming a message from one flavour of the HL7 standard to another, without any change to semantic meaning to the message, it is a Bridge and not a Gateway

Back to the Open ATS Issues