Recommendations
Mirth® Connect by NextGen Healthcare User Guide
Channel Scripts can be configured on the Scripts Tab within the Edit Channel View. There are four special scripts associated with a channel: Deploy Script: This runs once right before a channel is deployed. Preprocessor Script: This runs once for every message, after the source connector sends a message to the channel and after the Attachment Handler Properties has optionally extracted data, but before the message has reached the source filter/transformer. The job of the preprocessor is to modify the incoming message. Post Processor Script: This runs once for every message, after the source connector and all destinations have completed (excluding asynchronous processes like the destination queue), but before the source connector sends a response back to the originating system. The postprocessor script has access to responses from all executed destination, and can return custom response that the source connector can use. Undeploy Script: This runs once right before a channel is undeployChannel Scripts
Mirth® Connect by NextGen Healthcare User Guide
Every channel has at least one destination connector that sends data out to an external system. Destination connectors are configured on the Destinations Tab within the Edit Channel View. In addition to the standard Connector Components, destination connectors include: An Enabled flag that determines whether the destination is currently being used. A channel must have at least one destination enabled at any given time. A Wait for previous destination setting that determines what chain a destination connector belongs to. (For additional information, see Destination Chains. ) A Response Transformer. This is like a regular transformer, except it has its own response inbound data type and response outbound data type, and does the job of modifying the response that an external system returned to a destination connector. It also allows you to decide when to queue / force-error a message. See Response Transformers for additional information. Parent topic: Channel ComponentsDestination Connectors
Mirth® Connect by NextGen Healthcare User Guide
General Connector Properties Connector-Specific Properties Filter Transformer General Connector Properties Connector-Specific Properties Filter Transformer Parent topic: About Channels and ConnectorsConnector Components
Mirth® Connect by NextGen Healthcare User Guide
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 alSource Connector
Mirth® Connect by NextGen Healthcare User Guide
General Channel properties are configured on the Summary Tab within the Edit Channel View and include: Unique ID, name, and description. Links to Code Template Libraries: These let the channel know which custom functions are available in specific JavaScript contexts. Links to Library Resources: These let the channel know which custom Java classes are available in specific connectors and/or JavaScript contexts. Deploy/Start Dependencies: These determine which channels are dependent on this one, and also which channels are dependencies for this one. This way you can have some channels deploy and start before others. Attachment Handler: This allows you to extract pieces of any incoming message and store them separately. As a message processes through a channel, multiple copies of it will be held in memory at once (for the raw / transformed / encoded versions of a message). Attachments are stored only once, so by using them you can greatly reduce your channels' memory footprint. Message StGeneral Channel Properties
Mirth® Connect by NextGen Healthcare User Guide
Channel Performance Channel Configuration Other Tips Channel Performance Channel Configuration Message Integrity Other Tips