Archive Coercions Basic Overview - dcm4che/dcm4chee-arc-light GitHub Wiki
Content
- What is an Archive Attribute Coercion rule?
- Types of Archive Attribute Coercion rules
- Where to configure Archive Attribute Coercion rules?
- Usage of Archive Attribute Coercion rules
- Types of Coercion
- Application of Coercion Types by Archive Attribute Coercion rules
- Important Notes
An archive attribute coercion rule is used to coerce DICOM attribute values on datasets coming in and / or going out of the archive.
Archive configurations currently contain 2 types of Archive Attribute Coercion rules :
Configure archive attribute coercion rules either on
- Archive Device Extension level : Applicable to DICOM datasets received or sent by any archive application entity. May be supplemented by attribute coercions configured for particular archive network AEs.
OR on
- Archive Network AE Extension level : Applicable to DICOM datasets received or sent by this archive application entity. Supplements attribute coercions configured on archive device extension level.
OR on both of the above, i.e.
- Archive Device Extension level + Archive Network AE Extension level
Configurations in specific howtos shows the user how and what to configure using archive user interface and / or using Apache Directory Studio / ldif scripts.
Archive Attribute Coercions can be used to alter :
- Incoming datasets of
| DIMSE Transaction | External Client DICOM Transfer Role | Archive Function |
|---|---|---|
| DICOM MPPS N_CREATE_RQ | SCU | Archive receives MPPS requests from external systems |
| DICOM C_STORE_RQ / STOW | SCU | Archive receives DICOM objects via C_STORE / STOW from external systems |
| DICOM C_FIND_RQ / QIDO | SCU | Archive receives DICOM C_FIND or QIDO requests from external systems |
| DICOM C_FIND_RSP / QIDO | SCP | Archive receives DICOM C_FIND or QIDO responses from external systems |
- Outgoing datasets of
| DIMSE Transaction | External Client DICOM Transfer Role | Archive Function |
|---|---|---|
| DICOM C_STORE_RQ / WADO | SCP | Archive sends DICOM objects via C_STORE / WADO to external systems |
| DICOM C_FIND_RQ / QIDO | SCP | Archive sends DICOM C_FIND or QIDO requests to external systems |
| DICOM C_FIND_RSP / QIDO | SCU | Archive sends DICOM C_FIND or QIDO responses to external systems |
using one or more Coercion Types as described below.
| Coercion Type | Description |
|---|---|
| Merge from MWL | Search for MWL in external or local archive based on specific matching key (typically set to AccessionNumber or PatientIDAccessionNumber) and coerce attributes according to configured / customized stylesheet specified in the URI field. |
| Merge or Nullify Dataset Attributes | Used for merging or nullifying values of one or more DICOM attributes in a dataset using different Attributes Formatting Options on Coercions |
| Coerce from XSL | Coerce one or more attributes using XSL stylesheet. Can be customized as per vendor's requirements. |
| Supplement Dataset Attributes from Device | The device which is used for supplementing shall contain one or more DICOM fields configured on it, whose values are used for supplementing missing attributes in the dataset |
| Anonymize or Deidentify Data | Anonymize one or more attributes in a dataset according to one or more Supported De-identification Profiles |
| Use Calling AE Title as | Typically useful to set Sending Application Entity Title of Series DICOM field to calling AET of equipment storing studies to archive |
| Coerce attributes from Leading archive | Query Leading archive for study using Study UID in received dataset and coerce based on configured Attribute Update Policy |
| Trim ISO 2022 Character Sets using Coercions | Used for replacing single code for Single-Byte Character Sets with Code Extensions with code for Single-Byte Character Sets without Code Extensions in a dataset. |
| Retrieve as Received | Retrieve object's dataset from local archive to be sent to a destination, as it was received from the source. |
| Nullify Pixel Data | Nullifies Pixel Data (7FE0,0010) in the dataset. |
For each combination of DIMSE transactions with incoming / outgoing datasets, multiple Types of Coercion can be applied
- Using multiple New Archive Attribute Coercion rules, in any sequence and without the dependency on hardcoding of coercions' application as present in legacy archive attribute coercions above.
OR
- Using a single Legacy Archive Attribute Coercion rule following a cascaded sequence depending on configured fields.
- Over long term, the Legacy Archive Attribute Coercion rules will be purged from archive code.
- If archive configuration contains matching rule for both New Archive Attribute Coercion and Legacy Archive Attribute Coercion for a particular dataset combination, only the New Archive Attribute Coercion will get applied.