...
When a request is triggered, CONNECT will scan through the override entries first in locating endpoints
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<exchangeInfo xmlns="urn:gov:hhs:fha:nhinc:exchange" xmlns:ns2="urn:gov:hhs:fha:nhinc:exchange:directory">
<refreshInterval>1440</refreshInterval>
<maxNumberOfBackups>0</maxNumberOfBackups>
<defaultExchange>Exchange 1</defaultExchange>
<exchanges>
<exchange type="uddi">
..
</exchange>
<exchange type="overrides">
<url>https://testurl/uddi/list</url>
<organizationList>
<organization>
<ns2:name>Gateway 2</ns2:name>
<ns2:hcid>urn:oid:2.2</ns2:hcid>
<ns2:endpointList>
<ns2:endpoint>
<ns2:name>QueryForDocuments</ns2:name>
<ns2:endpointConfigurationList>
<ns2:endpointConfiguration>
<ns2:url>https://<<server-url:port>>/Gateway/DocumentQuery/2_0/NhinService/RespondingGateway_Query_Service/DocQuery</ns2:url>
<ns2:version></ns2:version>
</ns2:endpointConfiguration>
<ns2:endpointConfiguration>
<ns2:url>https://<<server-url:port>>/Gateway/DocumentQuery/3_0/NhinService/RespondingGateway_Query_Service/DocQuery</ns2:url>
</ns2:endpointConfiguration>
</ns2:endpointConfigurationList>
</ns2:endpoint>
<ns2:endpoint>
<ns2:name>RetrieveDocuments</ns2:name>
<ns2:endpointConfigurationList>
<ns2:endpointConfiguration>
<ns2:url>https://<<server-url:port>>/Gateway/DocumentRetrieve/2_0/NhinService/RespondingGateway_Retrieve_Service/DocRetrieve</ns2:url>
<ns2:version>2.0</ns2:version>
</ns2:endpointConfiguration>
<ns2:endpointConfiguration>
<ns2:url>https://<<server-url:port>>/Gateway/DocumentRetrieve/3_0/NhinService/RespondingGateway_Retrieve_Service/DocRetrieve</ns2:url>
<ns2:version>3.0</ns2:version>
</ns2:endpointConfiguration>
</ns2:endpointConfigurationList>
</ns2:endpoint>
<ns2:endpoint>
<ns2:name>PatientDiscovery</ns2:name>
<ns2:endpointConfigurationList>
<ns2:endpointConfiguration>
<ns2:url>https://<<server-url:port>>/Gateway/PatientDiscovery/1_0/NhinService/NhinPatientDiscovery</ns2:url>
<ns2:version>1.0</ns2:version>
</ns2:endpointConfiguration>
<ns2:endpointConfiguration>
<ns2:url>https://<<server-url:port>>/Gateway/PatientDiscovery/1_0/NhinService/NhinPatientDiscovery</ns2:url>
<ns2:version>2.0</ns2:version>
</ns2:endpointConfiguration>
</ns2:endpointConfigurationList>
</ns2:endpoint>
<ns2:endpoint>
<ns2:name>DocSubmission</ns2:name>
<ns2:endpointConfigurationList>
<ns2:endpointConfiguration>
<ns2:url>https://<<server-url:port>>/Gateway/DocumentSubmission/1_1/DocumentRepositoryXDR_Service</ns2:url>
<ns2:version>1.1</ns2:version>
</ns2:endpointConfiguration>
<ns2:endpointConfiguration>
<ns2:url>https://<<server-url:port>>/Gateway/DocumentSubmission/2_0/DocumentRepositoryXDR_Service</ns2:url>
<ns2:version>2.0</ns2:version>
</ns2:endpointConfiguration>
</ns2:endpointConfigurationList>
</ns2:endpoint>
</ns2:endpointList>
<ns2:targetRegion>US-NY</ns2:targetRegion>
<ns2:targetRegion>US-VA</ns2:targetRegion>
</organization>
</organizationList>
</exchange>
</exchanges>
</exchangeInfo> |
. If an entry exists that matches the HCID, service type and spec version*, the corresponding service URL (if defined) will be used as the target endpoint. If no match is made or no service URL is defined, CONNECT will continue with normal endpoint lookup processing. The following is a summary of the override process from a code perspective:
...
*spec version maps to the <version> element in the exchangeInfo.xml and not the <useSpecVersion> element from <nhinTargetCommunities>
Connection Manager to Exchange Manager conversion
...