Skip to main content

HL7 Connection Monitor

  1. Last updated
  2. Save as PDF

Stop, start, or restart HL7 connections that have been defined and enabled as well as view transaction logs for a specified date range. This form can be useful if myAvatar has not received messages from an external system or if an external system reports they are not receiving messages from myAvatar .

Avatar PM > HL7 Interface > System Maintenance > HL7 Connection Monitor

  • This form is only available in myAvatar  HL7 2014 and later.
  1. The Currently Defined Connections field displays the following information for each connection that is defined in the system:
    • Message direction - Indicates whether messages are being sent out of myAvatar (Outbound) or sent into myAvatar (Inbound).
    • Connection ID - How the connection is identified by the system.
    • Mode - Indicates whether the connection is considered a 'test' connection or a 'production' connection.
    • Connection Description - An option way of identifying a connection.
    • Status - Each connection is either enabled or disabled. For those connections that are enabled, they are either running (on) or stopped (off). By default, the system will only display connection that are enabled.
    • # Messages In Queue - Indicates how many messages are queued up waiting to be transmitted to some ancillary system (e.g. lab, dietary, etc.). This is specific to outbound connections only.
      Under normal circumstances, there should be very few, if any, messages in the queue. A large number of messages in the queue may be an indication that the HL7 process is not running on either the myAvatar or ancillary system side. Or it could be the result of a data dump (e.g. client data push) that occurs most often at go-live.
    • Server - The name or ip of the server to which messages will be sent. This is specific to outbound connections only.
    • Port - For outbound connections, this is the port number on the server to which messages will be sent. For inbound connections, this is the port number on the myAvatar DB server to which information should be sent.
    • Events Supported - A list of the message events supported (e.g. P03 = Billing, R01 = Results, O01 = Orders, etc.).
  2. In the Show Connections That Are Currently Disabled field, select whether or not to include connections that are current disabled in the connection display. By default, the system only displays connections that are enabled.
  3. In the Select Row field, choose a specific connection to either report on, and/or start or stop it.
  4. Click Refresh Monitor to refresh the connection grid. This will also clear the selected row and the Last Message Processed field.
    This is primarily used in situations where there are several messages in an outbound queue and you are trying to determine if the message count is going up or down (e.g. ancillary system was restarted and you restart periodically to see that the message count eventually starts going down).
  5. Click the Start and Stop Connection buttons to start or stop the currently selected connection if it is not already running. Only connections that are enabled can be started or stopped. Any connection that is disabled must first be enabled by Netsmart before it can be started or stopped. the connection will remain stopped until it is either started manually or cache is restarted.
  6. The Last Message Processed field displays the last message that was sent or received for the currently selected connection and the date when it was processed.
  7. In the Transaction Log From and Through Date fields, enter the first and last dates to include when reporting on messages either sent or received for the currently selected connection.
  8. The Outbound Error Log Entries field displays the 100 most recent entries on file for the connection selected. For outbound connections only, there is an error log that captures all unexpected issues that could arise (e.g. no connectivity, timeout waiting for acknowledgement response, disconnections, etc).
  9. Click Show Transaction Log to run a report showing all of the HL7 messages either sent or received during the indicated time period.