PHI Events

Mirth® Connect by NextGen Healthcare User Guide

Custom Metadata Columns

Custom Metadata Columns for the current channel also show up in the metadata table. These columns vary depending on the channel. By default the Source and Type columns are added for all new channels, though this can be changed in the Server Settings. Column Description Source Depends on the inbound data type for the connector. For HL7 v2.x messages this will usually be the Sending Facility value in MSH.4.1. Type Depends on the inbound data type for the connector. For HL7 v2.x messages this will usually be the Type and Trigger values in MSH.9.1 and MSH.9.2. Version Depends on the inbound data type for the connector. For HL7 v2.x messages this will usually be the Version value in MSH.12.1. Note that this custom metadata column is not added to new channels by default, though this may be changed in the Server Settings Tab. Note that the above values are only the defaults, and that users can change those values inside of a transformer. Parent topic: Metadata Table

Mirth® Connect by NextGen Healthcare User Guide

General Channel Properties

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 St

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

Metadata Table Columns

Column Description ID The unique ID of the event in the database. This column is hidden by default. For additional information, see Working With Tables. Level An icon indicating the event's severity level ( Information, Warning, or Error) . Date & Time The date and time the event was logged. Name The name of the logged operation, or a description of the warning/error. Server ID The unique ID of the server from which the event was logged. User If the event originated from a user action, this will be both the user ID and user name. If no user is associated with the event, it will show 0 (System). Outcome For user requests and server tasks, this icon indicates whether the action was successful or not. For example a failed user login attempt will show a failure icon. IP Address For user requests, the IP address of the originating client. Channel ID - Message ID If the event occurs in a specific channel, the channel ID will be logged. If the event occurs due to a specific message, a dash wi

Mirth® Connect by NextGen Healthcare User Guide

Events Table

This table shows metadata (ID, timestamp, operation name) about each event that has been stored by the server. The Page Size option dictates the number of events shown in the table simultaneously (for additional information, see Searching Events) . When you first enter the Event Browser, by default the latest 100 events appear. For general information about working with tables in Mirth® Connect, see Working With Tables. Metadata Table Columns PHI Events Parent topic: Events View

Mirth® Connect by NextGen Healthcare User Guide

§170.315(d)(2) Auditable Events and Tamper-Resistance, §170.315(d)(3) Audit Report(s), and §170.315(d)(10) Auditing Actions on Health Information

Cures criteria 170.315(d)(2) Auditable Events and Tamper-Resistance and §170.315(d)(10) Auditing Actions on Health Information. These criteria are interrelated and therefore addressed together. (d)(2) Auditable events and tamper-resistance establishes which actions must be audited, what must be included in the audit records, and required protections around the audit log, including detecting if the audit log has been changed outside of normal processes. (d)(10) Auditing actions on health information establishes which actions must be audited, what must be included in the audit records, and required protections around the audit log, including detecting if the audit log has been changed outside of normal processes. (d)(3) Audit Report(s) requires the ability of health information systems to sort the audit logs. Note: In Mirth® Connect by NextGen Healthcare, the audit log is referred to as Event Log/Browser. Required Extensions Role-Based Access Control Cures Certification Support Features

PHI Events

Recommendations

Custom Metadata Columns

General Channel Properties

Variable Maps

Metadata Table Columns

Events Table

§170.315(d)(2) Auditable Events and Tamper-Resistance, §170.315(d)(3) Audit Report(s), and §170.315(d)(10) Auditing Actions on Health Information

Custom Metadata Columns

General Channel Properties

Variable Maps

Metadata Table Columns

Events Table

§170.315(d)(2) Auditable Events and Tamper-Resistance, §170.315(d)(3) Audit Report(s), and §170.315(d)(10) Auditing Actions on Health Information