As of CONNECT 5.1, both files have been replaced with the more versatile exchangeInfo.xml and internalExchangeInfo.xml files. For users of CONNECT 5.0 and earlier versions, substitute references to these new files with the original uddiConnectionInfo.xml and internalConnectionInfo.xml files
Overview
ValidateConnectionManagerForAllService project is used to verify HCID (urn:oid) namespace for all CONNECT Services (DS, PD, DQ, DR, AD). This test ensures that the ExchangeManager component is able match HCID with and without namespace (urn:oid) for InternalExchangeInfo, ExchangeInfo and Service Request (HCID) messages (DS, PD, DQ, DR, AD). This test should be run in Standard and capability of running in Passthrough. The Test Case are configured to send service request message HCID with and without namespace (urn:oid), copy files (InternalExchangeInfo, ExchangeInfo) with and without HCID namespace (urn:oid) into CONNECT Properties folder and verify that the request did not Fail.
Test case description and what it does described below:
Test Details
All services much passed the request message with and without HCID namespace (urn:oid), and ExchangeManager much be able to match the request HCID with InternalExchangeInfo and ExchangeInfo with and with HCID namespace (urn:oid).
Document Submission Deferred Req
Sending DS Deferred (Request) message with and without HCID Namespace, copy the InternalExchangeInfo and ExchangeInfo with and without to CONNECT Property folder, config the service for passthrough or standard, and verify request did not Fail (status, relatesTo).
Doc Submission Deferred Resp
Sending DS Deferred (Response) message with and without HCID Namespace, copy the InternalExchangeInfo and ExchangeInfo with and without to CONNECT Property folder, config the service for passthrough or standard, and verify request did not Fail (status).
Document Submission
Sending DS Request message with and without HCID Namespace, copy the InternalExchangeInfo and ExchangeInfo with and without to CONNECT Property folder, config the service for passthrough or standard, and verify request did not Fail (status).
Patient Discovery Deferred Req
Sending PD Deferred (Request) message with and without HCID Namespace, copy the InternalExchangeInfo and ExchangeInfo with and without to CONNECT Property folder, config the service for passthrough or standard, and verify request did not Fail (status, reciever, sender, relatesTo).
Patient Discovery Deferred Resp
Sending PD Deferred (Response) message with and without HCID Namespace, copy the InternalExchangeInfo and ExchangeInfo with and without to CONNECT Property folder, config the service for passthrough or standard, and verify request did not Fail (acknowledgement status, typeCode).
Patient Discovery
Sending PD request message with and without HCID Namespace, copy the InternalExchangeInfo and ExchangeInfo with and without to CONNECT Property folder, config the service for passthrough or standard (skip mock adapter), and verify request did not Fail (controlActProcess, family name, given name).
Document Query
Sending DQ request message with and without HCID Namespace, copy the InternalExchangeInfo and ExchangeInfo with and without to CONNECT Property folder, config the service for passthrough or standard, update table (Patient Correlation, AA Mapping), and verify request did not Fail (Document Id).
Document Retrieve
Sending DR request message with and without HCID Namespace, copy the InternalExchangeInfo and ExchangeInfo with and without to CONNECT Property folder, config the service for passthrough or standard, and verify request did not Fail (Document Id, Document Respository, Document Data).
Admin Distribution
Sending AD request message with and without HCID Namespace, copy the InternalExchangeInfo and ExchangeInfo with and without to CONNECT Property folder, and config the service for passthrough or standard.
Request (HTTP 202) Accept