Source Settings

Item	Name	Description
A	Source Queue	This determines whether the source queue is enabled. It also determines when the selected response will be sent back to the originating system. OFF (Respond after processing): Selecting OFF will process the message before sending the response. In this scenario you may use the response from destinations, the response map, or the post-processor. This is the Default selection. ON (Respond before processing): Selecting ON will queue messages and immediately send a response. In this scenario you may only choose to not respond with anything, or to use an auto-generated response.
B	Queue Buffer Size	The buffer size for the source queue, only apply when Source Queue = ON. Up to this many connector messages may be held in memory at once when queuing. Default = 1000.
C	Response	Determines what response to send back to the originating system. You may choose a destination's response, the post-processor return value, a response map variable, an auto-generation option, or None indicating that you do not want to send a response back at all. Select Auto-generate to send a response generated by the inbound data type using the raw message: Before processing: Response generated before the channel processes the message (SENT status) After source transformer: Response generated after the channel processes the message (source connector status) Destinations completed: Response generated after the channel processes the message, with a status based on the destination statuses, using a precedence of ERROR, QUEUED, SENT, FILTERED.
D	Process Batch	Select Yes to enable batch processing. Batch messages are only supported if the source connector's inbound properties contains a Batch section. For additional information see Batch Processing
E	Batch Response	Each message in the batch contains its own response that is generated via the method selected above. Select either the response from the first or last message in the batch to be sent back to the originating system.
F	Max Processing Threads	The maximum number of messages that can be processed through the channel simultaneously. By default this is set to 1, meaning that only one message can bd processed through a channel at any given time (does not include asynchronous processes like the destination queue). Increasing this setting can greatly improve channel performance / throughput, at the cost of message order preservation. Note: When this value is greater than 1, message order is NOT guaranteed.

Mirth® Connect by NextGen Healthcare User Guide

Source Connector

Every channel has exactly one source connector which gets data into Mirth® Connect from an external system. The source connector is configured on the Source Tab within the Edit Channel View. In addition to the standard Connector Components, source connectors include: A Source Queue that can be enabled or disabled. When enabled, the channel acts as a store-and-forward service that can receive messages and send acknowledgements immediately to the originating system, without having to wait for the message to process through the entire channel. A Batch Processor that can be enabled or disabled. When enabled, the channel takes any incoming data and splits it into multiple messages that each proceed discretely through the channel. See Batch Processing for additional information. A Response Selector that determines what response to send back to the originating system, if applicable. You can choose to auto-generate a response based on the inbound data type of the source transformer. You can al

Mirth® Connect by NextGen Healthcare User Guide

Outbound Properties

Deserialization Properties: After a transformer finishes, these properties determine how to convert data from the final internal representation (e.g. XML) into the outbound data format. If a data type doesn't have deserialization properties present, it either doesn't need any (DICOM, EDI/X12, XML, JSON) or it doesn't actually do any deserialization (Raw). Template Serialization: If an outbound template is specified for the transformer, these properties determine how to convert that template to its corresponding internal representation (e.g. XML). Mirth® Connect supports the following data types: Delimited Text Data Type DICOM Data Type EDI / X12 Data Type HL7 v2.x Data Type HL7 v3.x Data Type JSON Data Type NCPDP Data Type Raw Data Type XML Data Type An additional data type is made available as an extension: ASTM E1394 Data Type Also see: Batch Processing Parent topic: Data Types

Mirth® Connect by NextGen Healthcare User Guide

Source Map Variables

Key Description originalFilename The name of the file that was read in. fileDirectory The absolute path of the directory in which the file resides. fileSize The size of the file in bytes. fileLastModified The last modified date of the file, as an epoch time in milliseconds. pollId A unique nanosecond timestamp that uniquely identifies the current polling window. If your File Reader polls 5 files, the messages for each file will have the same pollId. pollSequenceId An integer that starts at 1 and increments for every subsequent file in the current polling window. If your File Reader polls 5 files, the message(s) for the first file will have a pollSequenceId of 1, the message(s) for the second file will have a pollSequenceId of 2, and so on. pollComplete This is only present for the last file in the current polling window. The value of this entry is always equal to true. Use this to determine programmatically whether you are currently working with the last file in a poll. Note that if yo

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

Destination Settings

These are general settings that apply to all destination connectors. They include configuring the destination queue, whether to validate responses, and whether to re-attach attachments on outbound messages. Item Name Description A Queue Messages Never: Disable the destination queue. On Failure: Attempt to send the message first before queuing it. This will allow subsequent destinations and the Postprocessor to use the response from this destination if it successfully sends before queuing. Always: Immediately queue the message. Subsequent destinations and the Postprocessor will always see this destination's response as QUEUED. B Advanced Queue Settings Configure how often to re-attempt queued messages, increase queue threads, and more. C Validate Response Select Yes to validate the response. Responses can only be validated if the response transformer's inbound properties contains a Response Validation section. If validation fails, the message will be marked as queued or errored. For add

Mirth® Connect by NextGen Healthcare User Guide

Channel Performance

Adjust the Message Storage slider so that the channel only retains the message data that you will actually need. If large messages are expected, use an Attachment Handler to improve throughput and reduce memory and disk usage. Enable source queuing if an auto-generated acknowledgement is sufficient for the upstream system. Enable destination queuing if you do not need to respond to the originating system from your destination. Increase the Max Processing Threads value if message order is not important and you may receive a large number of messages in a short time Increase the Queue Threads value if the downstream system can accept multiple concurrent connections. Clear the "Wait for previous destination" checkbox, unless you need destinations to process messages one after another. Use the "Destination Set Filter" feature in your source transformer when you need to route messages to only one (or a subset) of destinations in your channel. Adjust the Message Storage slider so that the cha

Source Settings

Recommendations

Source Connector

Outbound Properties

Source Map Variables

About Data Types

Destination Settings

Channel Performance

Source Connector

Outbound Properties

Source Map Variables

About Data Types

Destination Settings

Channel Performance