Source Map

Mirth® Connect by NextGen Healthcare User Guide

Connector-Specific Properties

Every connector has its own custom set of properties. The properties you configure for a TCP Listener will be different from a Database Writer and so on. Here is a list of source and destination connectors supported by Mirth® Connect: Source Connectors Channel Reader DICOM Listener Database Reader File Reader HTTP Listener JMS Listener JavaScript Reader TCP Listener Web Service Listener Destination Connectors Channel Writer DICOM Sender Database Writer Document Writer File Writer HTTP Sender JMS Sender JavaScript Writer SMTP Sender TCP Sender Web Service Sender Additional connectors are made available as extensions: Email Reader Serial Connector NextGen Results CDR Connector FHIR Connector Interoperability Connector Suite Parent topic: Connector Components

Mirth® Connect by NextGen Healthcare User Guide

Source Connector Properties

This section refers to the actual connector-specific settings. The sections are labeled according to the connector types, for example, "HTTP Listener", "JavaScript Reader". For additional information on connectors in general, refer About Channels and Connectors. Here is a list of source connectors supported by Mirth® Connect Source Connectors Channel Reader DICOM Listener Database Reader File Reader HTTP Listener JMS Listener JavaScript Reader TCP Listener Web Service Listener Additional source connectors are made available as extensions: Email Reader Serial Connector FHIR Connector Interoperability Connector Suite Parent topic: Source Tab

Mirth® Connect by NextGen Healthcare User Guide

Response Map

This map is isolated to the current message as it processes through a channel. Unlike the channel map, this one is specifically used for storing Response objects. When a destination finishes processing, its Response will automatically be stored in the response map. Subsequent destinations and the Postprocessor Script will have access to these values. The source connector can also use values stored in the response map to send responses back to the originating system (set in the Source Settings) . Get response map value: var value = responseMap.get('key'); var value = $r('key'); Put response map value: responseMap.put('key', 'value'); $r('key', 'value'); Parent topic: Variable Maps

Mirth® Connect by NextGen Healthcare User Guide

Connector Map

This map is isolated to the current message, and the current connector the message is processing through. For example, if you store a connector map variable in Destination 1, you will not be able to access that value in Destination 2. This is useful to avoid conflicts among common variable names, and to reduce message storage. Get connector map value: var value = connectorMap.get('key'); var value = $co('key'); Put connector map value: connectorMap.put('key', 'value'); $co('key', 'value'); Parent topic: Variable Maps

Mirth® Connect by NextGen Healthcare User Guide

Channel Map

This map is isolated to the current message as it processes through a channel. If you store a connector map variable in the source connector, you will have access to that value in all subsequent destinations. However when the current message finishes and the next one begins, that next message will not have access to the value you stored for the previous message. The channel map is useful for anything that needs to be shared among multiple destinations, or the source connector and all destinations. For example, you might have one HTTP Sender destination that makes a request to a remote service, and then in the Response Transformer you store a particular response HTTP header in the channel map. As long as the next destination connector is in the same chain, it will have access to that channel map variable, and can do something else with it, like include it on a subsequent HTTP request. Get channel map value: var value = channelMap.get('key'); var value = $c('key'); Put channel map value:

Mirth® Connect by NextGen Healthcare User Guide

The Variable Map Lookup Sequence

In many cases when referencing map variables in Mirth® Connect, you do not call out to a specific map, but instead use the generic lookup function: var value = $('variableName'); Or, you might reference a variable using Velocity Variable Replacement: ${variableName} When you do this, Mirth® Connect will automatically look that key up in all available maps. That may only be the configuration/global map (in the case of the global scripts) , or it may be all maps (in the case of a filter / transformer script) . This sequence is followed: Response Map Connector Map Channel Map Source Map Global Channel Map Global Map Configuration Map For example, if you have stored a variable called "dataSource" in both the Connector Map and the Global Channel Map, the one from the Connector Map will be used. If you want the value specifically from the Global Channel Map instead, you can use the map-specific get function shown in the Variable Maps section: var dataSource = globalChannelMap.get('dataSource

Source Map

Recommendations

Connector-Specific Properties

Source Connector Properties

Response Map

Connector Map

Channel Map

The Variable Map Lookup Sequence

Source Map

Connector-Specific Properties

Source Connector Properties

Response Map

Connector Map

Channel Map

The Variable Map Lookup Sequence