Digest HTTP Authentication

Item	Name	Description
A	Realm	The protection space for this server.
B	Algorithms	Specifies the digest algorithms supported by this server. MD5: The security data A1 contains the username, realm, and password. MD5-sess: The security data A1 will also contain the server and client nonces. Both: Both MD5 and MD5-sess.
C	QOP Modes	The quality of protection modes to support. auth: Regular authentication with client nonce and count in the digest. auth-int: Same as auth (regular authentication), but also with message integrity protection enabled.
D	Opaque	A string of data that should be returned by the client unchanged. Velocity Variable Replacement is supported in this field. The default value, ${UUID}, means that a randomly generated universally unique identifier will be sent back on each digest challenge.
E	Credentials	Use Table: When selected, use the Credentials table (E) to populate credentials. To Use the Table Select New Double-click the Username field and enter a username for the credential. Double-click the Password field and enter a password for the credential. Note: At least one username/password pair is required for the credentials. Use Map: When selected, the Java map specified by the following variable will is used to populate credentials. The map must have String keys and either String or List<String> values.

Mirth® Connect by NextGen Healthcare User Guide

Variable Maps

Throughout the Message Processing Lifecycle, your channels and messages have access to various maps. Depending on the scope, the map may only be available in the current channel/connector, or may be globally available across your entire system. These variable maps allow you to store a piece of information that can be used later (in a downstream channel, connector, or somewhere else). A common use for these variables is to provide easy drag-and-drop for connector properties. The Destination Mappings list will display all available connector/channel map variables for example. They are also used in other ways, such as populating Custom Metadata Columns. The following variable maps exist throughout Mirth® Connect: Name JavaScript Variable Get/Put Shortcut Variable Response Map responseMap $r Connector Map connectorMap $co Channel Map channelMap $c Source Map sourceMap $s Global Channel Map globalChannelMap $gc Global Map globalMap $g Configuration Map configurationMap $cfg The table above

Mirth® Connect by NextGen Healthcare User Guide

Alert Actions

This section of the Edit Alert View allows you to decide what actions to take after your alert has been triggered. You can take multiple actions all at once for a single trigger event, which may include sending e-mails to multiple users and dispatching messages to multiple channels. Protocols All protocols also support Velocity Variable Replacement, you can use any of the Alert Variables below, or any Global Map variable. Channel: The template is sent as a message to the channel selected in the Recipient column. The subject is not used for this protocol. Email: The subject and template is used to send an e-mail to the address specified in the Recipient column. User: Same as the Email protocol, the e-mail address used is the one configured for the selected user. Role: E-mails will be sent to all users within a particular Role-Based Access Control role. Only visible when User Authorization is installed. Alert Variables Parent topic: Edit Alert View

Mirth® Connect by NextGen Healthcare User Guide

HTTP Sender

This destination connector sends an HTTP request to an external web server. The method, parameters, and headers can all be fully customized. Both Basic and Digest authentication (preemptive or reactive) are supported. Sending requests through a proxy server is also supported, even when using HTTPS. The HTTP payload can be written out as raw bytes, or converted using a specified charset. Responses can be automatically converted to XML, allowing multipart payloads to be parsed in a consistent and easy-to-use way. Additional options are available with the SSL Manager extension. Supported property groups: Destination Settings Item Name Default Value Description A URL The URL of the HTTP server to send each message to. B Use Proxy Server No If enabled, requests are forwarded to the proxy server specified in the address/port fields below. C Proxy Address The domain name or IP address of the proxy server to connect to. D Proxy Port The port on which to connect to the proxy server. E Method PO

Mirth® Connect by NextGen Healthcare User Guide

Archive Settings

Item Name Description I Enable Archiving Determines whether message / attachment data is saved to disk before being pruned. Select Yes to save message / attachment data to disk prior to being pruned. Select No to perform a prune without saving message / attachment data. J Archiver Block Size The number of messages that will be cached by the archiver. Increase this value to improve performance. Decrease this value to reduce memory usage. This value must be between 1 and 1,000. The recommended value for most servers is 50. K Content The type of content that is exported from the messages. Note: XML serialized message is the only type that can be re-imported, and it includes all content across the message in a single XML file. Encrypt: Check Encrypt to encrypt the exported message content with the server's encryption key. Include Attachments: Check Include Attachments to include all attachments associated with the message in your exported file. Note that the content type must be set to XML

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

Basic HTTP Authentication

Provides Basic Authentication support for HTTP-based source connectors. Item Name Description A Realm The protection space for this server. B Use Table Use Table: When selected, use the Credentials table (B) to populate credentials. To Use the Table Select New Double-click the Username field and enter a username for the credential. Double-click the Password field and enter a password for the credential. Note: At least one username/password pair is required for the credentials. Use Map: When selected, the Java map specified by the following variable will is used to populate credentials. The map must have String keys and either String or List<String> values. Parent topic: HTTP Authentication Settings

Digest HTTP Authentication

Recommendations

Variable Maps

Alert Actions

HTTP Sender

Archive Settings

DICOM Sender

Basic HTTP Authentication

Digest HTTP Authentication

Variable Maps

Alert Actions

HTTP Sender

Archive Settings

DICOM Sender

Basic HTTP Authentication