...

As of CONNECT 5.1, both files have been replaced with the more versatile exchangeInfo.xml and internalExchangeInfo.xml files. For CONNECT 5.0 and earlier versions, substitute references to these new files with the original uddiConnectionInfo.xml and internalConnectionInfo.xml files.

...

Overview

The Test Suite design to verify the Spec Version mapping for Document Query (DQ) and Document Retrieve (DR) services, used by exchange manager, exchangeInfo and NHIN target communities request message.

Bimodal tests are executed in both (Standard, PassThrough) modes and required JMX enable at the server level for SoapUI to successfully switch between Standard and PassThrough.

• g1 specify test data in exchangeInfo_g1 and internalExchangeInfo_g1

• g0 specify test data in exchangeInfo_g0 and internalExchangeInfo_g0

• a1 entity: This test suite is used to test CONNECT auditing functionality that supports the endpoints implement July-2011 specs.

...

• a0 entity: This test suite is used to test CONNECT auditing functionality that supports the endpoints implement prior to July-2011 specs.

Overview

The Test is designed to verify CONNECT Multispec Support (NhinTargetCommunities, useSpecVersion) driven by exchangeInfo configuration.

• If the spec version is supported, the service call should response with service spec (July-2011 spec, prior to July-2011 specs).

• If the spec version is unsupported, the service call should result with RegistryError response.

Test Detail

The Bimodal test are design to hit service in standard and passthrough, by calling the JMX console to switch the service mode without application server restart.

ValidateDQDRMultispecSupportTest (G1, G0, Standard and Passthrough)

Verifying the DQ and DR services with Multispec Support for both Standard and Passthrough. The service (G1, G0) implementation specify by the endpoint, exchangeInfo files specify the spec support by CONNECT and CONNECT configuration workflow and processing of the service.

Standard

• Update config: set documentQueryQuerySelf to false

• Clear Correlation Table & Add Correlation

• Clear AA Mapping Table & Add Mapping

Passthrough

• Check Passthru: set PolicyEngineProxyConfig to adapterpepnoopdeny

Assert (Support, Unsupport) spec version

• If supported, assert (Expected Document)

• If unsupported, assert (Error: Context, Severity, Location)

DQ_NoGuidance

1. ** Update config

2. ** Clear Correlation Table & Add Correlation

3. ** Clear AA Mapping Table & Add Mapping

4. ** Check Passthru

5. SOAP: Document Query

   • ** Assert (Expected Document)

   • ** Assert Unsupport (Error: Context, Severity, Location)

DQ_20Guidance

1. ** Update config

2. ** Clear Correlation Table & Add Correlation

3. ** Clear AA Mapping Table & Add Mapping

4. ** Check Passthru

5. SOAP: Document Query

   • ** Assert Support (Expected Document)

   • ** Assert Unsupport (Error: Context, Severity, Location)

DQ_30Guidance

1. ** Update config

2. ** Clear Correlation Table & Add Correlation

3. ** Clear AA Mapping Table & Add Mapping

4. ** Check Passthru

5. SOAP: Document Query

   • ** Assert Support (Document Id)

   • ** Assert Unsupport (Error: Context, Severity, Location)

DR_NoGuidance

1. ** Check Passthru

2. SOAP: Document Retrieve

   • ** Assert Support (Expected Document)

   • ** Assert Unsupport (Error: Context, Severity, Location)

DR_20Guidance

1. ** Check Passthru

2. SOAP: Document Retrieve

   • ** Assert Support (Expected Document)

   • ** Assert Unsupport (Error: Context, Severity, Location)

DR_30Guidance

...

** Check Passthru

SOAP: Document Retrieve

...

** Assert Support (Expected Document)

...

Test Cases Detail for g0, g1, a0, a1, standard and passthrough

The test cases is design to test spec version (useSpecVersion) specified by the NHIN target communities request message, matched by exchange manager and exchangeInfo endpoint version. If the match fail the expect response for the request is failure and if the match is successful the service response status should be successful. The result of the service successful or failure is decide by the exchange manager and exchangeInfo test data.

Document Query in standard mode call the patient correlation service and required additional configuration for the Patient Correlation and AA Mapping in its test case.

• DQ_NoGuidance: the test case had not useSpecVersion element and default it value to the DQ entity spec version.

• DQ_20Guidance: the test case use useSpecVersion value 2.0 and send it request to DQ service

• DQ_30Guidance: the test case use useSpecVersion value 3.0 and send it request to DQ service

• DR_NoGuidance: the test case had not useSpecVersion element and default it value to the DR entity spec version.

• DR_20Guidance: the test case use useSpecVersion value 2.0 and send it request to DR service

• DR_30Guidance: the test case use useSpecVersion value 3.0 and send it request to DR service