2020-03-21 17:04:01 (106)    ROR LOG (798.7)

Location: CHECKMSG+55^ROR10

HL7 batch messages created by the Clinical Case Registries 
 1. Check that the HL7 logical link, associated with 
    the registry is not disabled. Start the link if
    necessary.
 
 2. It is possible that the message queue got stuck.
    Please try to restart the link.
 
 3. Contact the group that supports the local Vitria 
    Interface Engine and coordinate troubleshooting
    efforts with them.
have not been transmitted after 28 attempt(s). The CCR
 
 4. If nothing helps and you continue getting this
    message, then call the Help Desk or create a
    Remedy Help Desk ticket.
 
List of messages in question:

  Message ID....... 505552
  Message status... Waiting in queue
  Status updated... 
software will NOT extract any new data from the VA HEPC
  Error message.... 
  Error type....... 
  # of retries..... 
  Queue position... 1
  # Open failed.... 
  ACK timeout...... 
registry until all messages listed below are successfully
sent!
 
Please follow these steps to troubleshoot the problem as soon 
as possible:
 

HL7 batch messages created by the Clinical Case Registries 
 1. Check that the HL7 logical link, associated with 
    the registry is not disabled. Start the link if
    necessary.
 
 2. It is possible that the message queue got stuck.
    Please try to restart the link.
 
 3. Contact the group that supports the local Vitria 
    Interface Engine and coordinate troubleshooting
    efforts with them.
have not been transmitted after 28 attempt(s). The CCR
 
 4. If nothing helps and you continue getting this
    message, then call the Help Desk or create a
    Remedy Help Desk ticket.
 
List of messages in question:

  Message ID....... 505552
  Message status... Waiting in queue
  Status updated... 
software will NOT extract any new data from the VA HIV
  Error message.... 
  Error type....... 
  # of retries..... 
  Queue position... 1
  # Open failed.... 
  ACK timeout...... 
registry until all messages listed below are successfully
sent!
 
Please follow these steps to troubleshoot the problem as soon 
as possible: