...
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.
...