This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Gateway"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
[[Image:Ats_gateway_bridge_inter.gif|275px|right|thumb|Application Architecture]] | [[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. | + | 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 (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? | *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. We do not (nor we should) elaborate this on the level of HL7v3 normative specs. | **(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. We do not (nor we should) elaborate this on the level of HL7v3 normative specs. | ||
Revision as of 06:46, 2 May 2007
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 (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. 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.
Back to the Open ATS Issues
