...
The test case sends Patient Discovery (PD), Document Query (DQ), and Document Retrieve (DR) messages with the same transaction ID and different message IDs. The test asserts that there are 6 total items in the transaction database created by this string of related messages.
...
The test case sends Document Submission (DS) deferred request and response messages with the request message containing a unique message ID and transaction ID and the response containing a unique message ID and a relatesTo ID that equals the request messages messageID. The test asserts that there are 4 total items in the transaction database created by this string of related messages.
...
The test case sends Patient Discovery (PD) deferred request and response messages with the request message containing a unique message ID and transaction ID and the response containing a unique message ID and a relatesTo ID that equals the request messages messageID. The test asserts that there are 3 total items in the transaction database created by this string of related messages. The assertion for 3 is due to an issue that was discovered that PD Deferred response acknowledgement message does not contain a relatesTo value. The issue is reported here: GATEWAY-3029
...
The test case sends Document Submission (DS) and Admin Distribution (AD) messages with the same transaction ID and different message IDs. The test asserts that there are 3 total items in the transaction database created by this string of related messages. AD is a one way message so no response message will be logged.
...
The test case sends Patient Discovery (PD) deferred messages, 2 deferred requests and a response message. Each request message contains a unique message ID and unique transaction ID and the response contains a unique message ID and 2 relatesTo ID values that equals the 2 request messages messageIDs. The test asserts that there are 3 total items for each of the unique transaction IDs (6 altogether).
...
The test case sends Document Submission (DS) deferred messages, 2 deferred requests, and a response message. Each request message contains a unique message ID and unique transaction ID and the response contains a unique message ID and 2 relatesTo ID values that equal the 2 request messages messageIDs. The test asserts that there are 4 total items for the first unique transaction ID and 3 for the second (7 altogether).
...
The test case recreates a Document Query (DQ) fanout scenario. There is a UDDI Connection replacement file (uddiConnectionInfo_TRANS_Fanout.xml) in the regression suite containing 3 HCIDS (2.2, 6.6, 7.7) that will be targeted in the fanout. The test replaces the UDDI connection file in the server with the fanout uddi file. The Document Query message contains no targeted value, so it will fanout. The Document Query message contains a unique transaction ID and message ID. The test asserts that there are 7 total items in the transaction database, 1 for the original entity request message and 2 each (total 6) for each targeted HCID, request, and response.
...