XCA Testable Assertions
From IHEWiki
XCA Assertions and Connectathon test assumptions ****DRAFT***
| Assertion | Reference | Connectathon Test | Comment |
|---|---|---|---|
| Initiating Gateway Actor | |||
| (simple test, part 1) shall respond to a Registry Stored Query received from a local Document Consumer by initiating a Cross-Gateway Query to a single Responding Gateway | ITI TF-1:18.2.1 & ITI TF-2:3.18.4.1.3 | XCA_Simple_Query_XDS_Option | XDS Affinity Domain option |
| (simple test, part 2) shall respond to a Retrieve Document Set transaction received from a local Document Consumer by initiating a Cross-Gateway Retrieve to a single Responding Gateway | ITI TF-1:18.2.1 | XCA_Simple_Retrieve_XDS_Option | XDS Affinity Domain option |
| (multi-Responding GW test, part 1) Documents for an identified patient reside in 2-3 different remote communities. Doc Consumer in local Community queries the Initiating Gateway by Patient ID. Initiating Gateway shall do a PIX query to the PIX Manager to determine the correct Patient ID in the 3 remote communities. The Initiating Gateway shall query the 3 Responding Gateways using the correct Patient ID in each query. The Initiating Gateway shall consolidate the responses received from the 2-33 Responding Gateways and return the consolidated response to the Doc Consumer. | ITI TF-1:18.3.3 & ITI TF-2:3.18.4.1.3 | XCA_Multi_Query_XDS_Option | XDS Affinity Domain option |
| (multi-Responding GW test, part 2) Documents for an identified patient reside in 2-3 different 'remote communities'. Doc Consumer in local Community requests a retrieve of a document in one of the remote communities. (Initiating Gateway will successfully handle/route successive retrieve request of each of the 2-33 individual documents, and combinations documents.) | ITI TF-1:18.3.3 | XCA_Multi_Retrieve_XDS_Option | XDS Affinity Domain option |
| shall query a local Registry (in addition to Responding Gateway(s)) in response to a Registry Stored Query received from a local Doc Consumer | ITI TF-1:18.2.2.1 | XCA_Init_GW_Doc_Consumer_Grouping | Rqmt for grouping with an XDS.b Doc Consumer |
| shall initiate a retrieve to a local Repository (in addition to Responding Gateway(s)) in response to a Retrieve Doc Set-b received from a local Doc Consumer | ITI TF-1:18.2.2.1 | XCA_Init_GW_Doc_Consumer_Grouping | Rqmt for grouping with an XDS.b Doc Consumer |
| shall return zero documents, but not an error code, when it receives a query for a Patient ID it does not know about | ITI TF-1:18.4.2 (M6) | XCA_Simple_Query_XDS_Option | |
| shall send an audit message when it receives a Registry Stored Query request from a local Document Consumer | ITI TF-2:3.38.4.1.4 | ATNA_Inquisition, ATNA_Logging | audit test |
| shall send an audit message when it initiates a Cross Gateway Query | ITI TF-2:3.38.4.1.4 | ATNA_Inquisition, ATNA_Logging | audit test |
| shall send an audit message when it receives a Retrieve Document Set | ITI TF-2:3.39.4.1.4 | ATNA_Inquisition, ATNA_Logging | audit test |
| shall send an audit message when it initiates a Cross Gateway Retrieve | ITI TF-2:3.39.4.1.4 | ATNA_Inquisition, ATNA_Logging | audit test |
| shall | ITI TF-1: | XCA_ | |
| Responding Gateway Actor | |||
| shall respond to a Cross Gateway Query by returning the results from its local community | ITI TF-2:3.38.4.1.3 | XCA_Simple_Query_XDS_Option, XCA_Multi_Query_XDS_Option | |
| shall respond to a Cross Gateway retrieve by returning the requested documents from its local community | ITI TF-2:3.39.4.1.3 | XCA_Simple_Retrieve_XDS_Option, XCA_Multi_Retrieve_XDS_Option | |
| shall query a local Registry in response to a Cross Gateway Query | ITI TF-1:18.2.2.1 | XCA_Simple_Query_XDS_Option, XCA_Multi_Query_XDS_Option | Rqmt for grouping with an XDS.b Doc Consumer |
| shall initiate a retrieve to a local Repository in response to a Cross Gateway Retrieve | ITI TF-1:18.2.2.1 | XCA_Simple_Retrieve_XDS_Option, XCA_Multi_Retrieve_XDS_Option | Rqmt for grouping with an XDS.b Doc Consumer |
| shall send an audit message when it receives a Cross Gateway Query | ITI TF-2:3.38.4.1.4 | ATNA_Inquisition, ATNA_Logging | audit test |
| shall send an audit message when it receives a Cross Gateway Retrieve | ITI TF-2:39.4.1.4 | ATNA_Inquisition, ATNA_Logging | |
| shall | ITI TF-1: | XCA_ | |
| Test set-up and other micellany | |||
| Unlike the majority of connectathon tests where vendors pick their partner and work to complete their assigned tests throughout the course of the week, XCA tests will likely be held at defined times with all XCA test participants, and under the direct supervision of a connectathon monitor. For example, we would run XCA tests on Tues morning from 8:30-9:30, and again on Wed or Thursday to allow for a fix/re-test cycle. | |||
| For NA2008 Connectathon, each XDS.b (and .a) Document Registry will represent its own affinity domain. Each Registry’s Affinity Domain will be pre-assigned a unique value for (1) the Assigning Authority for the Patient IDs in its domain, and (2) homeCommunityId. In order to succeed & be efficient, XDS and XCA test participants will have to pay attention to which 'affinity domain' they’re testing in at a given time. | |||
| The method the Initiating Gateway uses to reconciles patient IDs in different domains is not mandated in the profile. We will use PIX (and advertise it) as part of the test scenario. The Initiating Gateways registered for Jan 08 support either PIX or PIXv3 as a Consumer. We have 2 PIX Managers registered who are PIX Managers for both v2 and v3. More details to come.... | |||
| We will publish values for homeCommunityId that identifies each connectathon XCA 'community'; One homeCommunityId per Responding Gateway registered to test (which maps to a single URL for that Resp. Gatetway). | |||
| Although this is not specified in the profile, for the January Connectathon, we will require that Responding Gateways support query and retrieve from the same URL. | |||
| The XCA profile does not mandate that either the Initiating or Responding Gateway's communitity be an XDS.b affinity domain. I am trying to avoid waving my hands in a test and saying "some magic happens" and then an Initiating Gateway queries a Responding Gateway. For NA2008 January Connectathon, all Initiating Gateways support the XDS Affinity Domain option, so, in the tests, all 'queries' and 'retrieves' will be initiated by an XDS.b Document Consumer drafted to help with XCA testing. | |||
| Likewise, I am trying to avoid waving my hands in a test and saying "some magic happens" and then a Responding Gateway has query or retrieve results from its own community. For NA2008 January Connectathon, all but one Responding Gateway is grouped with an XDS.b Document Consumer, so, in the tests, all 'queries' and 'retrieves' received by the Responding Gateway will be directed at an XDS.b Registry or Repository drafted to help with XCA testing. | |||
| We will create XCA 'test' patient(s) with documents residing in multiple Responding Gateways' communities | |||
| Unless we are trouble-shooting, we are *not* looking inside Cross-Gateway Query and Retrieve messages (eg looking for homeCommunityId) ... This is a pre-Connectathon-type of test. | |||
