Read Access Rights:
|
Write Access Rights:
|
A message on the Error Queue or Hold Queue becomes 'orphaned' when the input communication point, or indeed the entire locker that the message arrived on has been deleted. At this point of having been orphaned, locker access rights can no longer be determined for the message, so the only users with the 'Manage orphaned messages' access right can administer these messages. Orphaned messages will still appear in the Error Queue or Hold Queue, but users without this right will not be able to see these messages, in the same way that they cannot see messages that originated from lockers they do not have permission for.
Search Results
Because the messages are on the Error Queue or Hold Queue, the buttons for some actions may be enabled when the action is not actually possible, particularly in the case where there are also non-orphaned messages on the queue. All actions on the Error and Hold Queues check permissions for the selected messages and will fail to complete if the user does not have the correct access rights.
The following table describes the actions available on the Error Queue and Hold Queue pages, and what happens when these are used on orphaned messages.
Field/Action |
Description |
|---|---|
Reinject |
It is not possible to reinject an orphaned message. |
Redirect |
The message is redirected to a selected filter or communication point. To redirect messages, select one or more messages in the queue, then click the Redirect button. The message can only be redirected to components that the user has the 'Locker view' access right for. If the message is being redirected to a different locker (which is highly likely for an orphaned message), a warning will be displayed to the user so they are aware that there are potential consequences, for example users with permissions to that locker may then be able to see the message body and thus PHI. |
Reprocess |
The message is sent back to the filter on which the error originally occurred. Selected messages can be reprocessed by selecting the Reprocess button. If the filter has been deleted, which may be the case with orphaned messages, the reprocess will fail, and the message will be sent back to the Error Queue. Only available for orphaned messages on the Error Queue. |
Release |
The message is released from the Hold Queue and sent to the filter following the Hold Queue filter. To release messages, select one or more messages in the queue, then select the Release button. If the filter has been deleted, which may be the case with orphaned messages, the reprocess will fail, and the message will be sent to the Error Queue.
Only available for orphaned messages on the Hold Queue.
|
Delete |
The message is removed (deleted) from the queue and no additional processing is performed on the message. To delete messages, select one or more messages in the queue, then click the Delete link. Alternatively, to delete all the messages from this queue, click the Delete All link. When using the Delete All link, the operation will proceed, but it will only delete messages that the user has permission to delete. This will be determined either by the user having the 'Delete held/errored messages' access right on the locker that the message originated from, or in the case of orphaned messages, the user having the 'Manage orphaned messages' access right. |
Download |
The message body is downloaded as a compressed file. To download messages, select one or more messages in the queue, then click the Download link to save the file to a convenient location. Alternatively, to download all the messages from this queue, click the Download All link. Downloading a large number of messages may take an extended period of time, especially when the Engine is under high load. It is recommended you perform this operation during off-peak time. When using the Download All link, the operation will proceed, but it will only download messages that the user has permission to download. This will be determined either by the user having the 'Download messages' access right on the locker that the message originated from, or in the case of orphaned messages, the user having the 'Manage orphaned messages' access right. |
| Export | The message metadata is exported as a compressed file. To export messages, select one or more messages in the queue, then click the Export link to save the file to a convenient location. Alternatively, to export all the messages from this queue, click the Export All link. The exported data includes the message search information, as well as the message properties, and error information. Exporting a large number of messages may take an extended period of time, especially when the Engine is under high load. It is recommended you perform this operation during off-peak time. When using the Export All link, the operation will proceed, but it only exports messages that the user has permission to export. This is determined either by the user having the 'Export messages' access right on the locker that the message originated from, or in the case of orphaned messages, the user having the 'Manage orphaned messages' access right. |