JavaScript Writer

Mirth® Connect by NextGen Healthcare User Guide

Database Writer

This destination connector connects to an external database and performs an INSERT/UPDATE statement (or any other statement, like calling a stored procedure). This can be done using a SQL statement, or by using JavaScript mode to execute the statement manually. The database connection will automatically be kept open across multiple dispatches. Supported property groups: Destination Settings Item Name Default Value Description A Driver Specifies the type of database driver to use to connect to the database. The following values are supported by default: Sun JDBC-ODBC Bridge MySQL Oracle PostgreSQL SQL Server / Sybase SQLite Additional drivers can be added by editing the dbdrivers.xml File. B URL The JDBC URL to connect to the database with. This is not used when "Use JavaScript" is checked. However, it is used when the Generate Connection / Insert feature is used to generate code. Use the Insert URL Template button to populate the URL field with a starting template. C Username The usern

Mirth® Connect by NextGen Healthcare User Guide

JMS Sender

This destination connector connects to an external JMS provider and writes messages to a queue or topic. It supports both JNDI and specifying a specific connection factory. Once this connector dispatches a message, the connection to the JMS provider will be kept open and cached until the connector is stopped or an error occurs. The properties view also includes a mechanism to save configuration templates for common provider types, so that creating a new JMS Sender is as quick and easy as possible. Note: Depending on the JMS connection provider you are using, you may need to include some external libraries (JARs) as a Library Resource and include them using the Set Dependencies dialog on the Channel Summary tab. For example, to use connection templates included for ActiveMQ and JBoss, you should download the libraries from their official site in order to use them with the JMS connectors. Supported property groups: Destination Settings Item Name Default Value Description A Use JNDI No Se

Mirth® Connect by NextGen Healthcare User Guide

Channel Writer

The Channel Writer is a connector that simply dispatches messages to other internal channels. This can be useful if you split your message workflow into multiple channels, where one sends to another. If no target channel is specified, the connector acts as a "sink" where no message dispatching is done. Note that a channel does not need to use a Channel Reader source for a Channel Writer to be able to send messages to it. The connector also has options to inject source map variables into the downstream message of the target channel. Supported property groups: Destination Settings Item Name Default Value Description A Channel Id <None> The unique ID of the target channel to send messages to. This may be a hard-coded ID, or may be a Velocity Variable Replacement. Use the drop-down menu to the right to quickly select a particular channel. If <None> is selected, the destination will act as a "sink" where messages are not dispatched anywhere. B Message Metadata The map variables entered here

Mirth® Connect by NextGen Healthcare User Guide

JavaScript Writer Return Values

When you return from your script, you can choose to set a custom Response that will be stored for the destination. The following return values are accepted: String: Any string returned will be stored as the Response content for the destination, with a status of SENT. Status: An instance of the Status enum (for additional information, see The User API (Javadoc)) will cause no response content to be stored, but the connector message status will be updated to SENT, QUEUED, or ERROR depending on the status returned. Note that the status can only be set to QUEUED if queuing is enabled in the Destination Settings. Response: A Response object contains a status, status message, error message, and the actual response content. If this object is returned, all of these things will be stored in the Response content, and the connector message status will be updated accordingly. For additional information, see The User API (Javadoc). Empty String / null / undefined: Returning any of these (including

Mirth® Connect by NextGen Healthcare User Guide

DICOM Sender

This destination connector works in conjunction with the DICOM Attachment Handler Properties and the DICOM Data Type to allow Mirth® Connect to send DICOM data. This connector supports the C-STORE operation as a Service Class User (SCU). Additional options are available with the SSL Manager extension. Supported property groups: Destination Settings Item Name Default Value Description A Remote Host 127.0.0.1 The remote IP to send to. B Local Host The local address that the client socket will be bound to. C Remote Port 104 The remote port to send to. D Local Port The local port that the client socket will be bound to. E Remote Application Entity The Application Entity title to sent to. F Local Application Entity The Application Entity title to identify the local client with. G Max Async operations 0 Maximum number of outstanding operations performed asynchronously. Enter 0 for unlimited. H Priority Medium Priority of the C-STORE operation. I Request Storage Commitment No Request storage

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

JavaScript Writer

Recommendations

Database Writer

JMS Sender

Channel Writer

JavaScript Writer Return Values

DICOM Sender

Web Service Sender

JavaScript Writer

Database Writer

JMS Sender

Channel Writer

JavaScript Writer Return Values

DICOM Sender

Web Service Sender