Rejection IAN - dcm4che/dcm4chee-arc-light GitHub Wiki

Testplan for Instance Availability Notifications for Rejected Instances

This page gives a brief overview of tests to be done to send out notifications of availability of rejected instances.

Notifications about instance availability when studies are stored to the archive or when a MPPS referencing the stored objects is received is already explained

IHE framework specifies notifying configured IAN destinations about rejected instances. This has been implemented in the archive with some open questions solved as per a certain understanding of the specification.

Configuration

The only configuration necessary to send out Instance Availability Notification for rejected Instances are

Remote Application Entity for each of the system(s) acting as an IAN destination(s).
Configuring these application entities as IAN Destination(s) on archive device extension level. Configuration page -> Devices tab -> dcm4chee-arc -> Device Extension -> Archive Device Extension -> IAN Destination

Tests

For each use case, start ianscp simulating the Service Class Provider (SCP) for the Instance Available Notification (IAN) SOP Class
```
  ianscp -b IANSCP:11117
```
For each use case, verify in Monitoring page -> Queues tab -> IAN Tasks queue, that IAN sent out has been COMPLETED. Additionally, the SOP Instance UID from the queue message should match with the value of Media Storage SOP Instance UID in the dataset of IAN.

Use Cases

Activate Purge instance records from DB feature and repeat the tests. Trigger complete / partial rejections of studies after the series metadata is aggregated and instance records are purged from the database. The IAN dataset for each of the rejection use cases post purging of instance records from DB should be identical to the IAN datasets of rejection use cases when purging instance records was not activated.