Supplement Dataset Attributes from Device - dcm4che/dcm4chee-arc-light GitHub Wiki

This page briefly guides and acquaints the user with coercion type to supplement DICOM dataset attributes' values from a device configured in archive's configuration.

Content

Brief Description

A DICOM dataset coming in or going out of the archive may have one or more missing DICOM attributes in it. Supplement these missing attributes with help of a Supplement dataset attributes from device coercion type.

The device which is used for supplementing shall contain one or more DICOM specific fields configured on it. These configured values are then used to supplement corresponding missing attributes in the applicable DICOM dataset.

Refer

Applicability using Archive Attribute Coercion rules

New Archive Attribute Coercion can be used to supplement DICOM attributes to :

  • incoming C-STORE requests on receive of DICOM objects to archive sent from external systems
  • outgoing C-STORE requests on sending DICOM objects from archive to external systems
  • incoming (MWL) C-FIND requests to archive
  • incoming (MWL) C-FIND responses to archive
  • outgoing (MWL) C-FIND requests from archive
  • incoming MPPS N-CREATE requests to archive

Legacy Archive Attribute Coercions can be used to supplement DICOM attributes to :

  • incoming C-STORE requests on receive of DICOM objects to archive sent from external systems
  • incoming (MWL) C-FIND requests to archive
  • incoming (MWL) C-FIND responses to archive
  • outgoing (MWL) C-FIND requests from archive
  • incoming MPPS N-CREATE requests to archive

See

Configurable fields on Archive Attribute Coercion rules

Supplementing dataset attributes from device can be applied using either :

(Recommended) Device Name Coercion Parameter field with Attribute Coercion URI as merge-attrs: on New Archive Attribute Coercion

OR

Supplement from Device field on Legacy Archive Attribute Coercion

See

Supplementable attributes

Device level attributes supplementable on each entity level are as follows :

Following table enlists the applicability of device level fields supplemented on each of the entities / datasets.

Supplement entity ->
-----------------
Supplementable Device level fields
(below)
Instance MWL MPPS Query
Issuer of Patient ID (0010,0021)
(0010,0024)
Y Y Y Y
Issuer of Accession Number (0008,0051) Y
also inside RequestAttributesSequence
Y Y
inside ScheduledStepAttributesSequence
Y
also inside RequestAttributesSequence
Issuer of Admission ID (0038,0014) Y Y Y Y
Issuer of Service Episode ID Y Y Y Y
Issuer of Container Identifier (0040,0513) N N N Y
Issuer of Specimen Identifier (0040,0562) N N N Y
Order Placer Identifier (0040,0026) Y
inside RequestAttributesSequence
Y Y
inside ScheduledStepAttributesSequence
Y
inside RequestAttributesSequence
Order Filler Identifier (0040,0027) Y
inside RequestAttributesSequence
Y Y
inside ScheduledStepAttributesSequence
Y
inside RequestAttributesSequence
Manufacturer (0008,0070) Y N N N
Manufacturer Model Name (0008,1090) Y N N N
Software Version(s) (0018,1020) Y N N N
Station Name (0008,1010) Y N N N
Device Serial Number (0018,1000) Y N N N
Institution Name(s) (0008,0080) Y N N N
Institution Code(s) (0008,0082) Y N N N
Institution Department Name(s) (0008,1040) Y N N N
Institution Address(s) (0008,0081) Y N N N
⚠️ **GitHub.com Fallback** ⚠️