Query+for+Documents+Page+4

= 5 Specifications =

5.1 Actor Summary

 * ** Actor Name ** || ** Role/Description ** ||
 * Initiating Gateway ||   ||
 * Responding Gateway ||   ||
 * Document Consumer ||   ||

5.2 Affinity Domain
Membership of a facility/enterprise in one community does not preclude it from being a member in another community. Such communities may be XDS Affinity Domains which define document sharing using the XDS profile or any other communities, no matter what their internal sharing structure. As such, Initiating Gateways which support the XDS Affinity Domain interact with Document Consumers within the XDS Affinity Domain served by the Initiating Gateway. The table below contains the specifications for Initiating Gateways actors which support XDS Affinity Domain.
 * ** Spec. # ** || ** Description ** || ** Source ** ||
 *  AFD1.0 ||  Initiating Gateway actors which support XDS Affinity Domain shall receive Registry Stored Query [ITI-18] transactions from a local Document Consumer 365 actor and act on those requests on behalf of the Document Consumer.  ||   ||
 *  AFD1.1 ||  When receiving a Registry Stored Query from a local Document Consumer, the Initiating Gateway actor shall require the homeCommunityId as an input parameter on relevant queries.  ||   ||
 *  AFD1.2 ||  The Initiating Gateway shall specify the homeCommunityId attribute within its Registry Stored Query responses.  ||   ||
 *  AFD1.3 ||  When an Initiating Gateway does not support XDS Affinity Domain, it is expected to be using non-IHE specified interactions to communicate remote community data to systems within its local community.  ||   ||

5.3 Asynchronous Web Services Exchange
The table below contains the specification for asynchronous web services exchange.
 * ** Spec. # ** || ** Description ** || ** Source ** ||
 *  ASE1.0 ||  Initiating Gateways which support Asynchronous Web Services Exchange shall support Asynchronous Web Services Exchange on the Cross Gateway Query [ITI-38] and Cross Gateway Retrieve [ITI-39] transactions.  ||   ||
 *  ASE1.1 ||  If the Initiating Gateway supports both the XDS Affinity Domain Option and the Asynchronous Web Services Option it shall support Asynchronous Web Services Exchange on the Registry Stored Query [ITI-18] and Retrieve Document Set [ITI-43] transactions.  ||   ||

5.4 Grouping
Grouping with a Document Consumer Actor may be used in situations where an Initiating Gateway and/or Responding Gateway are supporting an XDS Affinity Domain. This is accomplished by grouping the Initiating Gateway Actor with a Document Consumer Actor. This grouping allows Document Consumers such as EHR/PHR/etc systems to query the Initiating Gateway to retrieve document information and content from both the local XDS Affinity Domain as well as remote communities. The table below lists the specifications for grouping with a Document Consumer Actor when both the Initiating Gateway and/or Responding Gateway support an XDS Affinity Domain.
 * ** Spec. # ** || ** Description ** || ** Source ** ||
 *  GRP1.0 ||  If an Initiating Gateway supports an XDS Affinity Domain, in addition to remote communities, it can choose to query and retrieve from local actors.  ||   ||
 *  GRP1.1 ||  If an Initiating Gateway Actor is not grouped with a Document Consumer Actor, local HER/PHR/etc systems (Document Consumer Actors) must direct separate query and document retrieve transactions internally and externally.  ||   ||
 *  GRP1.2 ||  When a Responding Gateway is supporting an XDS Affinity Domain, it may resolve Cross Gateway Query and Cross Gateway Retrieve Transactions by grouping with a Document Consumer Actor and using the Registry Stored Query and Retrieve Document Set transactions.  ||   ||
 *  GRP1.3 ||  An Initiating Gateway that is grouped with Document Consumer shall support the XDS Affinity Domain option.   ||   ||
 *  GRP1.4 ||  Responding Gateways that are grouped with a Document Consumer shall initiate a Registry Stored Query [ITI-18] transaction to a local Document Registry to query local information in response to a received Cross Gateway Query [ITI-38].  ||   ||
 *  GRP1.5 ||  The Document Registry response must be augmented with the homeCommunityId of the Responding Gateway’s community prior to returning in the response to the Cross Gateway Query.  ||   ||
 *  GRP1.6 ||  Responding Gateways that are grouped with a Document Consumer shall **initiate** a Retrieve Document Set [ITI-43] transaction to a local Document Repository to retrieve local information in response to a Cross Gateway Retrieve [ITI-39].  ||   ||

5.5 Cross Gateway Query

 * ** Spec. # ** || ** Description ** || ** Source ** ||
 *  CGQ1.0 ||   ||   ||
 *  CGQ1.1 ||   ||   ||

5.6 Error Handling

 * ** Spec. # ** || ** Description ** || ** Source ** ||
 *  ERR1.0 ||   ||   ||
 * <span style="display: block; line-height: normal; margin: 0in 0in 0pt 0.5in; mso-add-space: auto; mso-list: l5 level1 lfo5; text-indent: -0.25in;"> ERR1.1 ||   ||   ||

[|[AE1]] See pg 38 – 43 of XCA supplement