XCA Connectors

Interoperability Connector Suite User Guide

PIX and PDQ Connectors

The Interoperability Connector Suite includes connectors for PIX and PDQ. These connectors are very similar, so they'll be grouped together here. The PIX Connectors are used for consuming and creating Patient Identifier Cross-referencing messages. The PIX Listener and PIX Sender support both PIXv2 (TCP with HL7 v2.x) and PIXv3 (SOAP with HL7 v3.x) standards. The PDQ Connectors are used for consuming and creating Patient Demographics Query messages. The PDQ Listener and PDQ Sender support both PDQv2 (TCP with HL7 v2.x) and PDQv3 (SOAP with HL7 v3.x) standards. Note: A PIXv3 and PDQv3 Listener's inbound data type is restricted to JSON and PIXv3 and PDQv3 connectors follow the interoperability message format conversion rules. Note: Since PIXv2 and PDQv2 connectors have very few configuration options, only PIXv3 and PDQv3 settings will be discussed here. PIX and PDQ Source Connectors PIX and PDQ Destination Connectors Parent topic: Connectors

Interoperability Connector Suite User Guide

XCPD Connectors

The XCPD Connectors are used for consuming and creating Cross-Community Patient Discovery messages. The XCPD Listener and Sender act as web service listeners and senders supporting HL7 v3.x and both 2010 and 2011 Patient Discovery versions. Note: An XCPD Listener's inbound data type is restricted to JSON and it follows the interoperability message format conversion rules. XCPD Source Connector XCPD Destination Connector Parent topic: Connectors

Interoperability Connector Suite User Guide

XDS.b Connectors

The XDS.b Connectors are used for consuming and creating Cross-Enterprise Document Sharing messages. The XDS.b Listener and Sender act as web service listeners and senders supporting HL7 v3.x and both Registry and Repository document modes. Note: An XDS.b Listener's inbound data type is restricted to JSON and it follows the interoperability message format conversion rules. XDS.b Source Connector XDS.b Destination Connector Parent topic: Connectors

Interoperability Connector Suite User Guide

Message Format Conversion

In some cases, to simplify working with messages in the Interoperability Connectors, messages will be converted to JSON format. This conversion is dependent on the connector's data type and connector settings. Source connectors that support HL7v3 messages (PIXv3, PDQv3, XCA, XCPD, XDS.b) with inbound datatype of JSON will receive a message in XML format which will then be converted to JSON. For all intents and purposes, the connector will show that the message came in as JSON. Source connectors that do not support HL7v3 messages (PIXv2 and PDQv2) will not have their messages implicitly converted to JSON. Destination connectors that support HL7v3 messages (PIXv3, PDQv3, XCA, XCPD, XDS.b) with outbound datatype of JSON will take the JSON outbound message and convert it to XML before sending it out to its destination. There is one caveat that if the destination connector's template setting is set to SOAP, then no conversion is done since the message is expected to be XML already. Destinat

Interoperability Connector Suite User Guide

XCA Destination Connector

XCA Sender Settings window The XCA Sender supports UDDI and WS-Security Validation and Generation. Operations The XCA Sender includes a set of standard operations that most XCA web services should support. When using the Default WSDL, you can switch between Query and Retrieve modes through the Document Mode toggle. You also have the option of entering a custom WSDL URL and fetching its specific set of operations which will be presented in the Operation dropdown. The Operation dropdown is used when generating the envelope. Envelope The XCA Sender includes useful options for generating the outbound envelope. Parent topic: XCA Connectors

Interoperability Connector Suite User Guide

XCA Source Connector

XCA Listener Settings window The XCA Listener includes a default Query WSDL and a default Retrieve WSDL for common sets of XCA operations. These can be customized, if necessary, through the Customize WSDL toggles and Schema Definitions tables. The XCA Listener simultaneously creates endpoints for Query and Retrieve operations, for both XCA versions 2.0 and 3.0, even though only the 3.0 versions are displayed in the URL fields. Specifically, it creates the following endpoints: http(s)://<host>:<port>/Gateway/DocumentQuery/2_0/NhinService/RespondingGateway_Query_Service/DocQuery?wsdlhttp(s)://<host>:<port>/Gateway/DocumentQuery/3_0/NhinService/RespondingGateway_Query_Service/DocQuery?wsdlhttp(s)://<host>:<port>/Gateway/DocumentRetrieve/2_0/NhinService/RespondingGateway_Retrieve_Service/DocRetrieve?wsdlhttp(s)://<host>:<port>/Gateway/DocumentRetrieve/3_0/NhinService/RespondingGateway_Retrieve_Service/DocRetrieve?wsdlThe XCA Listener supports WS-Security Validation and Generation. Parent t

XCA Connectors

Recommendations

PIX and PDQ Connectors

XCPD Connectors

XDS.b Connectors

Message Format Conversion

XCA Destination Connector

XCA Source Connector

XCA Connectors

PIX and PDQ Connectors

XCPD Connectors

XDS.b Connectors

Message Format Conversion

XCA Destination Connector

XCA Source Connector