Manage IOCM

Image object change management (IOCM) manages the synchronization of changes applied on existing imaging objects between NilRead and remote servers. IOCM uses rejection notes (DICOM key object selection documents) to ensure that remote servers are notified when studies, series or images are deleted on the NilRead server, and that the NilRead server is notified when these items are deleted on a remote server.

Replacement instances can be sent to the remote server through the NilRead data lifecycle services (for details, see Manage data lifecycle policies). Alternatively, NilRead can send instance availability notifications (IAN) to remote application entities (AE). The notification contains the AE titles of the replacement instances, from which the replacement instances can later be retrieved. For details, see Manage DICOM services.

NilRead rejection notes

If a study, series or image is deleted from the NilRead server, a rejection note is created with a list of the rejected (deleted) instances. Rejection notes are used to notify remote servers to delete these rejected instances. You can configure which remote servers receive NilRead rejection notes.

Rejection notes are created in the following scenarios:

• a user deletes a study from the Patient Study Directory
• a user edits a study and deletes the original study
• a user deletes a series from a study
• a user deletes an image from a study

By default, rejection notes generated by NilRead use the following title:

(113039, DCM, "Data Retention Policy Expired")

Received rejection notes

NilRead can also accept rejection notes from remote servers. If a study, series or image is deleted on a remote server and NilRead receives a rejection note, the rejected instances will be deleted on the NilRead server as well.

Configure IOCM settings

1. Select Settings.
2. Under Devices, select IOCM.
3. Enter the following information, then select Save.
   • Enable  Allow NilRead to send and receive rejection notes. If this option is disabled, NilRead will not create rejection notes. NilRead will still receive rejection notes from remote servers but the notes will not be applied.
   • Accept rejection notes from  Select the types of sources that NilRead will accept rejection notes from.
   • Send Nil rejection notes to  Select the remote application entities (AE) that NilRead will send rejection notes to.
   • Generate rejection notes when delete  You can choose to create rejection notes when a study is deleted (Study) and when a series or images is deleted (Series/instances).
   • Keep rejection notes for XX days  Number of days to keep rejection notes. Notes older than the retention period will be deleted the next time a scheduled data purge occurs. To remove older notes immediately, select Purge at the bottom of the page.

The Rejection Notes list contains the notes NilRead has sent and received. Rejection notes received from a remote server are applied automatically (check the timestamp in the Applied column to verify that a note has been applied). To apply a rejection note immediately, select the note, then select Apply. To delete a rejection note, select the note, then select Delete.

NilRead ignores all instances that have been rejected. If the rejected instances must be reimported, delete the corresponding rejection notes and resend the rejected instances to NilRead.

Note
Rejection notes are also shown on the DICOM Activity page.