Inbound Replies pane

This table shows the configurable inbound reply parameters:
Parameter Description
Await Replies

When this is enabled, the engine generates a reply message based on the returned results.

Clearing this disables all other configuration entries in this pane.

If a multi-server is configured to await replies, then for each message sent the thread enters Await Replies mode. Only the destination client of the last outbound message is read for a reply message.

Await Replies is a thread-level operation. That is, there is not a separate await reply for each client. Awaiting replies blocks all traffic through the thread until the target client responds or a time-out happens.

OBMSGID is available when Await Replies is selected.

See DICOM SCU Await Replies handling for further information.

Timeout This is the time-out limit. The default is 45. The default value for this feature can be changed on the Netconfig/NetMonitor tab of the Client Preferences dialog box. Clicking Advanced opens the Configure Default Values dialog box. Having a time-out of 45 and using hcitpsmsgkill helps to avoid unexpected transmission
Timeout Handling This opens the Timeout Handling dialog box.

Select Resend OB message to automatically resend the message on time-out until a reply is received. This is the default.

Select Reply Generation to select from three types of replies:

  • None is for no reply generation.
  • Text is for text reply generation. Click Edit to open the Tcl Script Editor. Use this dialog box to edit existing files or procs.
  • Procs is for Tcl reply generation. Click Edit to open the TPS Editor. Then, click Add to open the TPS Properties dialog box, from where you can select the procedures or Java class and arguments.
Caution: 
Be careful when using reply handling. If the receiver does not detect and handle duplicate messages, then this could potentially lead to unnecessary extra messages displaying on the receiving end.

Do not use KILL to stop inbound reply messages. KILL causes the Await Reply mode to shut down abnormally, sending you to time-out handling every time. Use KILLREPLY instead. If the reply is CONTINUE’d or ignored, then the engine automatically shuts down Await Reply mode. The inbound reply messages should never be stopped using KILL.

TPS Inbound Reply Click Edit to open the TPS Editor. Then, click Add to open the TPS Properties dialog box, where you can select the procedures or Java class and arguments for the inbound reply messages. This TPS is used to post-process the inbound reply messages after translation but before being written to the connection.

The default is hcitpsmsgkill. The default value for this feature can be changed on the Netconfig/NetMonitor tab of the Client Preferences dialog box. Clicking Advanced opens the Configure Default Values dialog box.

Trx ID Determination Format Click the arrow to select the format from the list. Then, click Edit to open the Trx ID determination dialog box. Use this dialog box to configure transaction ID information:
  • For FRL, select the offset and length.
  • For HL7, HPRIM, X12, NCPDP, and UN/EDIFACT, it is not necessary to select the version and variant. Edit is not available when any of these are selected.
  • Selecting XML disables Edit. There are no properties to edit.
  • For XML (Namespace), selecting XML (Namespace) disables Edit. There are no properties to edit.
  • Select UPOC to specify a UPoC without going through FRL. Click Edit to open the Format UPoC dialog box. Only one proc can be selected. Specify arguments for inbound data messages.