Message Format Conversion

Interoperability Connector Suite User Guide

Example Message Format Conversion

You want to create a channel for PIX that takes a message, adds or manipulates some message nodes, then forwards the message to its actual destination. You create a new channel with a PIXv3 source connector (JSON inbound and outbound datatypes) and PIXv3 destination connector (JSON inbound and outbound datatypes) with Use SOAP Template set to No. You add a transformer step that manipulates the JSON message, then deploy it. The channel receives a HL7v3 (XML) message. That message is converted to JSON, then travels through the channel as JSON, having transformations applied in the transformer, then leaving the destination where it is, lastly, converted back to HL7v3 (XML) before being sent to its final destination. Parent topic: Message Format Conversion

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

Mirth® Connect by NextGen Healthcare User Guide

Select Data Types

The table at the top of the dialog shows all currently configured connectors for your channel. Since response transformers have their own inbound / outbound data types, for destination connectors you can expand the node in the tree and view the Response row underneath a particular destination. For a new channel, all data types are set to HL7 v2.x by default. This can be changed in two ways: The Connector table has Inbound and Outbound columns with drop-down menus. Select the drop-down arrow inside of the cell to make a selection: Use the drop-down menu in the Inbound Properties or Outbound Properties sections: Note: Since a message flows from the source connector directly to each destination connector, every destination inbound data type is always equal to the source outbound data type. Therefore, you may notice that the inbound data type is not editable for destination rows. In order to change the destination inbound data type, change the source outbound data type. Parent topic: Set D

Mirth® Connect by NextGen Healthcare User Guide

Destination Processing Steps

Note: These steps are repeated for each destination connector that a message flows through. The encoded content from the source connector is used by each destination connector as its raw data. The content is serialized (converted) to the internal representation of the inbound data type (e.g. XML). The content runs through the filter, and the message is either accepted or filtered. If the message gets filtered, flow stops for the current destination here. If there are additional destinations in the current chain, these steps are repeated for the next destination. Otherwise, assuming all other destination chains have finished, flow jumps down to the Final Processing Steps. The content runs through the transformer, where it may be modified. The post-transformer content is stored as the transformed data. The content is deserialized (converted) from the outbound data type's internal representation (e.g. XML) into the actual outbound format (HL7, EDI, etc.). The content is stored as encoded

Mirth® Connect by NextGen Healthcare User Guide

About Data Types

A data type tells a filter / transformer how to parse a certain format. The inbound data type serializes the incoming raw data into its internal representation. Then the filter / transformer executes, possibly modifying this internal representation, or even completely overwriting it with a different internal representation. Finally, the outbound data type takes this transformed data and deserializes it into the proper outbound format (the encoded data) . For example, the HL7 v2.x data type serializes ER7 data from this: into this: In this case, the internal representation is XML, because, for HL7 v2.x, the message object you use or manipulate in a filter / transformer is an E4X XML object. However not all data types use XML for their internal representation. The JSON data type uses JSON as you might expect, and the object you use in a filter / transformer is a regular JavaScript Object. The Raw data type does no serialization or deserialization, so its internal representation is identi

Mirth® Connect by NextGen Healthcare User Guide

Source Processing Steps

A message or stream of data is received by the source connector. The batch processor decides whether to split the message into multiple messages. If so, the below steps are repeated for each message returned by the batch processor. The attachment handler extracts and/or stores all attachment data. The post-attachment-handler content is stored as raw data. The content runs through the preprocessor script and is stored as processed raw data. The content is serialized (converted) to the internal representation of the inbound data type (e.g. XML). The content runs through the filter, and the message is either accepted or filtered. If the message gets filtered, flow stops here and jumps down to the Final Processing Steps. The content runs through the transformer, where it may be modified. The post-transformer content is stored as the transformed data. The content is deserialized (converted) from the outbound data type's internal representation (e.g. XML) into the actual outbound format (HL7

Message Format Conversion

Recommendations

Example Message Format Conversion

PIX and PDQ Connectors

Select Data Types

Destination Processing Steps

About Data Types

Source Processing Steps

Message Format Conversion

Example Message Format Conversion

PIX and PDQ Connectors

Select Data Types

Destination Processing Steps

About Data Types

Source Processing Steps