Workflow involving Compass and Navigator is failing

/Workflow involving Compass and Navigator is failing

Workflow involving Compass and Navigator is failing

Compass

  • Failure stops traffic – this is on by default. Try disabling.
  • Retention time for HL7 messages – if retention time is too long, the limit (e.g., 100K messages) may be reached and HL7 processing will stop. Try adjusting retention time for HL7 messages.
  • Disk filling up – if Compass is running on a system with a modest size disk drive, and images and/or logging is enabled, the drive may be filling up. Suggest turning off images or logging, if applicable, or using a larger disk drive.
  • Sources and destinations – although HL7 input or output may be enabled (“running”), if HL7 traffic is not processing look for sources or destinations that are not “started”. Look for pertinent status in one of the HL7 display screens.
  • Loopbacks – verify that source and destination HL7 ports for Compass (and Navigator) are not configured to create a loopback condition in Compass.

Navigator

  • Automatic start – verify that”automatically start worklist item processing” is enabled, if appropriate. This is near the top of the screen in Configuration -> General Settings.
  • Study Rules – if a study rule was added, make sure that that rule is referenced by the appropriate worklist-reader, and that the list of rules for the worklist reader is in the proper order. Note that every Navigator study rule is “stop on match” in Compass terminology.
  • Running status – view status indicators in the dashboard area. Navigator notes when the HL7 service is running and indicates status via red or green HL7 display.

General

  • Command prompt diagnosis – to determine whether or not DICOM or HL7 listeners are working correctly, from a command prompt run:  netstat -ano
    Explanation: “a” means all, including unconnected listening ports, “n” means don’t delay things by trying to get dns name for every ip addr, “o” means show the process id for the app on this side of the connection. You can check the process-id against task manager to make sure its who you think it should be.
2018-01-31T07:49:18+00:00 January 29th, 2018|