Outbound Envelope

Interoperability Connector Suite User Guide

Source Connector Options

Option Name Description Convert to JSON If enabled, automatically convert SOAP response payloads to JSON. Expanded JSON Envelope If enabled, the JSON version of the incoming envelope will always use an expanded format where all children are expanded into arrays and objects. The JSON document will be larger and more verbose, but it will also be in a more consistent structure which can make transformation easier. Convert JSON Response to XML If enabled, responses will be converted from JSON to XML. Must Understand If enabled, the mustUnderstand attribute will be added to the To, RelatesTo, Action, and MessageID header elements on all SOAP responses. Validate WS-Security If enabled, a Security section must be present in the SOAP header of any incoming requests. The SAML Assertion and Timestamp will be validated according to NHIN standards. If the Security node isn't present or doesn't pass validation, the request will not be processed through the channel. See WS-Security for more informat

Interoperability Connector Suite User Guide

Destination Connector Options

Option Name Description Use Default WSDL If enabled, will use standard WSDL and operations. To use custom operations, disable this option, provide a WSDL URL, and select Get Operations. WSDL URL The full URL to the WSDL describing the web service method to be called. Select the Get Operations after entering a URL. Use UDDI Select Yes to use a UDDI provider to determine the Location URI. Select No to use the default Location URI or provide your own. See UDDI for more information. Location URI The dispatch location for the port / endpoint defined in the Connector. This field is filled in automatically when you select Get Operations and does not usually need to be changed. If left blank, the default URI defined in the WSDL will be used. Convert Response to JSON If enabled, responses will be converted from XML to JSON. Expanded JSON Response If enabled, the JSON version of the response envelope will always use an expanded format where all children are expanded into arrays and objects. The

Mirth® Connect by NextGen Healthcare User Guide

Web Service Sender

This destination connector connects to a SOAP endpoint via JAX-WS and invokes a defined operation. When configuring this connector you can automatically fetch the WSDL from the remote server, and all the services / endpoints / operations will be filled out and modifiable from drop-down menus. Automatic generation of a sample SOAP envelope is supported too. Custom headers and MTOM attachments can be added to each request as well. Supported property groups: Destination Settings Item Name Default Value Description A WSDL URL The URL to the WSDL describing the web service and available operations. Select Get Operations after entering the WSDL to automatically fill out the Service, Port, Location URI, and available Operations. B Service The service name for the WSDL defined above. This field is filled in automatically when the Get Operations button is selected and does not usually need to be changed, unless multiple services are defined in the WSDL. C Port / Endpoint The port / endpoint nam

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

XDS.b Destination Connector

XDS.b Sender Settings window The XDS.b Sender supports UDDI and WS-Security Validation and Generation. Operations The XDS.b Sender includes a set of standard operations that most XDS.b web services should support. When using the Default WSDL, you can switch between Registry and Repository 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 XDS.b Sender includes useful options for generating the outbound envelope. Parent topic: XDS.b Connectors

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

Outbound Envelope

Recommendations

Source Connector Options

Destination Connector Options

Web Service Sender

Message Format Conversion

XDS.b Destination Connector

XCA Destination Connector

Source Connector Options

Destination Connector Options

Web Service Sender

Message Format Conversion

XDS.b Destination Connector

XCA Destination Connector