Reject Instances of Study
DCM4CHEE Archive implements the Imaging Object Change Management profile for the following :
- Rejection Note Stored (for Quality Reasons)
- Rejection Note Stored (for Patient Safety Reasons)
- Rejection Note Stored (for Incorrect Modality Worklist)
- Rejection Note Stored (for Data Retention Expiry)
The rejection note may be stored before (using C-Store) or after (using C-Store or Archive UI) the objects have been stored to the archive.
By default configuration, archive is already configured to receive above mentioned 4 rejection notes.
One may also view the configuration by going to Menu -> Configuration -> Devices -> dcm4chee-arc -> Device Extension -> Archive device Extension -> Child Objects -> Rejection Note.
To enable storing rejection note before objects to archive are stored, configure Accept Rejection before Storage
The below mentioned tests may also be performed with Purge instance records from DB enabled.
The instances are accepted by the archive on C-Store. On receive of rejection note after the objects have been received, the rejected instances are hidden. The rejected instances can be viewed using IOCM_PAT_SAFETY Application Entity.
The instances are accepted by the archive on C-Store. On receive of rejection note after the objects have been received, the rejected instances are hidden. The rejected instances can be viewed using IOCM_WRONG_MWL Application Entity.
The instances are accepted by the archive on C-Store. On receive of rejection note after the objects have been received, the rejected instances are hidden. The rejected instances can be viewed using IOCM_QUALITY Application Entity.
The instances are accepted by the archive on C-Store. On receive of rejection note after the objects have been received,
the rejected instances are marked for deletion. The rejected instances can be viewed using IOCM_EXPIRED Application Entity.
By default configuration, the rejected instances and rejection notes are deleted by scheduler configured for Deletion of Rejected Instances
after 1 day. The only reason to not immediately delete the rejected instances is to provide the user with opportunity
to revoke the rejection of instances, if required.
Rejection Note is accepted by the archive. If instances are received within the configured Accept Rejection before Storage time interval, these are accepted and hidden from the main view. The rejected instances can be viewed using IOCM_PAT_SAFETY Application Entity.
Rejection Note is accepted by the archive. If instances are received within the configured Accept Rejection before Storage time interval, these are accepted and hidden from the main view. The rejected instances can be viewed using IOCM_WRONG_MWL Application Entity.
Rejection Note is accepted by the archive. If instances are received within the configured Accept Rejection before Storage time interval, these are accepted and hidden from the main view. The rejected instances can be viewed using IOCM_QUALITY Application Entity.
Rejection Note is accepted by the archive. If instances are received within the configured Accept Rejection before Storage
time interval, these are accepted, rejected and marked for deletion. The rejected instances can be viewed using IOCM_EXPIRED Application Entity.
By default configuration, the rejected instances and rejection notes are deleted by scheduler configured for Deletion of Rejected Instances
after 1 day. The only reason to not immediately delete the rejected instances is to provide the user with opportunity
to revoke the rejection of instances, if required.
Rejection Note is accepted by the archive. If instances are received after the configured Accept Rejection before Storage
time interval, these are rejected with the reason A771 - Subsequent occurrence of rejected Object. The rejected
instances can be viewed using IOCM_PAT_SAFETY Application Entity.
Rejection Note is accepted by the archive. If instances are received after the configured Accept Rejection before Storage
time interval, these are rejected with the reason A771 - Subsequent occurrence of rejected Object. The rejected
instances can be viewed using IOCM_WRONG_MWL Application Entity.
Rejection Note is accepted by the archive. If instances are received after the configured Accept Rejection before Storage time interval, these are accepted and hidden from the main view. The rejected instances can be viewed using IOCM_QUALITY Application Entity.
Rejection Note is accepted by the archive. If instances are received after the configured Accept Rejection before Storage time interval, these are accepted and are accessable in the main view. The effect is same as if the rejection note was not received. The archive chooses to decide that the Data Retention Policy Expired rejection is no longer in force.
DCM4CHEE 5 Documentation