Instance Availability Notification - dcm4che/dcm4chee-arc-light GitHub Wiki

Overview

As per IHE, in the Instance Availability Notification transaction (RAD-49), an archive sends message to relevant actors informing them of availability status of newly stored DICOM objects.

For more information, one may also refer Instance Availability Notification Information Object Definition and Service Class.

Basic Configuration

Configure a polling interval for IAN tasks.

  • Using Archive UI Go upto archive device extension level Configuration page -> Devices tab -> dcm4chee-arc -> Device Extension -> Archive Device Extension and configure a value for IAN Task Polling Interval.

  • Using LDAP

          version: 1
          dn: dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
          changetype: modify
          add: dcmIanTaskPollingInterval
          dcmIanTaskPollingInterval: PT1M
    

Configure a Remote Application Entity for each of the system(s) acting as an IAN destination(s). (In below example, IANSCP)

Reference this IAN destination :

  • Using Archive UI - Can be configured either on :
    • Archive Device level (Send IAN for instances received by any Application Entity of the Archive) :

      Go upto archive device extension level Configuration page -> Devices tab -> dcm4chee-arc -> Device Extension -> Archive Device Extension. Select one or more Ian Destination(s).

    • Archive Application Extension level (Send IAN for instances received by this Application Entity of the Archive) :

      Go upto archive AE extension level Configuration page -> Devices tab -> dcm4chee-arc -> Child Objects Network AEs -> Network AE Extension -> Archive Network AE Extension. Select one or more Ian Destination(s).

OR

  • Using LDAP - One may either create a LDIF file to add attributes either on :

    • Archive Device level (e.g.):

        version: 1
        dn: dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
        changetype: modify
        add: dcmIanDestination
        dcmIanDestination: IANSCP      
      

    OR

    • Archive AE level (e.g.):

        version: 1
        dn: dicomAETitle=DCM4CHEE,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
        changetype: modify
        add: dcmIanDestination
        dcmIanDestination: IANSCP
      

    and import it to the LDAP Server by using the ldapmodify command line utility.

    OR use the Add Attribute... and Add Value... function of Apache Directory Studio to add attributes on Device Level (e.g.: dicomDeviceName=dcm4chee-arc) or on Application Entity Level (e.g: dicomAETitle=DCM4CHEE) of the Archive Configuration.

One may refer to Archive Device or Archive Network AE to understand the description of attributes.

Refer ISO-8601 Duration format for more know-how on Durations.

Go to the Control tab on Configuration page in archive UI and reload the configuration.

Testing

Required dcm4che Tool for all use cases

  • ianscp simulating the Service Class Provider (SCP) for the Instance Available Notification (IAN) SOP Class.

Use Cases

⚠️ **GitHub.com Fallback** ⚠️