...
This project is used for testing Document Query (DQ) service in multiple scenarios by passing document entry (Stable, Dynamic, Both or None ) in XDSDocEntryType, Invalid creation time in XDSDocumentEntryCreationTimeFrom and XDSDocumentEntryCreationTimeTo of request message. It is accomplished by processing Document Query request message by passing test case specific home community id in NHIN target communities. In order to do Query for DocumentsDQ, it is required to have patient correlation and aa_to_home_community mapping entry in database. There is an in a script in each test case which will clear and insert required test data in patientcorrelationdb.correlatedidentifiers , and assigningauthoritydb.aa_to_home_community_mapping tables. Each On-Demand document entry describes what type of content will be returned in response. Below described briefly about On-Demand document entry types.
Testing will be done in standard mode.
...
DQ - XDSDocEntryType Not Set:
This test case is used to test DQ service without setting XDSDocEntryType. First, script will clear correlation and add correlation, aa_to_home_community mapping in database for the home community that is passed in NHIN target communities. When DQ request is processed, it is expected to get all the documents that are present for the patientID which is passed in DQ request message from the responding gateway (ex: 2.2). This test case is for testing without XDSDocEntryType slot value and by default CONNECT uses stable entry type. Since there is no entry type passed in this test case, though there are more than 2 rows with same patientId (ex: D123401) in responding gateway, DQ request response shows two extrinsic objects (onDemand=0) in AdhocQueryResponse message. Using assertions, script will verify documentId and number of extrinsic objects matches to the expected count in returned response.DQ - XDSDocEntryType Both Set:
This test case is used to test DQ service by passing both(Stable and Dynamic) values values in XDSDocEntryType. First, script will clear correlation table and add correlation, one aa_to_home_community mapping in database for the home community that is passed in NHIN target communities. When DQ request is processed, it is expected to return all the documents that are present for the patientID (passed in DQ request) with entry type as Stable are Dynamic from the responding gateway (ex: 2.2). DQ request response shows three extrinsic objects in AdhocQueryResponse message (2 stable, 1 dynamic). Using assertions, script will verify documentId and number of extrinsic objects matches to the expected count in returned response.DQ - XDSDocEntryType Stable Set:
This test case is used to test DQ service by passing XDSDocEntryType as stable document document. First, script will clear correlation table and add correlation, one aa_to_home_community mapping in database for the home community that is passed in NHIN target communities. When DQ request is processed, it is expected to return all the documents that are present for the patientID (passed in DQ request) with entry type as Stable from the responding gateway (ex: 2.2). DQ request response shows two extrinsic objects in AdhocQueryResponse message. Using assertions, script will verify documentId and number of extrinsic objects matches to the expected count in returned response.
DQ - XDSDocEntryType Dynamic Set:
This test case is used to test DQ service by passing XDSDocEntryType as dynamic document document. First, script will clear correlation table and add correlation, one aa_to_home_community mapping in database for the home community that is passed in NHIN target communities. When DQ request is processed, it is expected to return all the documents that are present for the patientID (passed in DQ request) with entry type as Dynamic from the responding gateway (ex: 2.2). DQ request response shows one extrinsic objects in AdhocQueryResponse message. Using assertions, script will verify documentId and number of extrinsic objects matches to the expected count in returned response.
DQ - Both Set, Invalid Creation Time To:
This test case is used to test DQ service by passing both (Stable and Dynamic) entries in XDSDocEntryType along with Invalid Creation time to in XDSDocumentEntryCreationTimeTo slot element. First, script will clear correlation table and add correlation, one aa_to_home_community mapping in database for the home community that is passed in NHIN target communities. When DQ request is initiated, it is expected to return all the documents that are present for the patientID (passed in DQ request) whose documents creation time is not in the range of creation time to and below. (Ex: If creation time to is 2000-09-11 04:00:00 then results will have all the documents from this time to above for this test case). Using assertions, script will verify documentId and number of extrinsic objects matches to the expected count in returned response. NOTE: CreationTimeTo is from given time to below.
...