Coerce outgoing C STORE requests on sending studies from archive - dcm4che/dcm4chee-arc-light GitHub Wiki
Content
Following fields of an archive attribute coercion rule determine whether a particular rule will get applied or not. To coerce outgoing studies, fields should be configured as
Coercion Rule field | Value / Notes |
---|---|
DIMSE | C_STORE_RQ |
Role | SCP |
SOP Class UID | May be configured to one of Query Retrieve SOP Classess to limit the rule only to certain Q/R types |
Conditions | May be configured according to requirement, to limit the rule only to certain conditions. eg. SendingApplicationEntityTitle=MOD_US01 or Modality=CR|CT (specifying multiple values separated by | ) or Modality!=CR|CT (specifying multiple values separated by | with not equals condition) |
Rule Priority | If multiple coercion rules with exact values for above 4 fields are configured, higher rule priority coercion rule takes precedence |
Outgoing studies sent by archive can be coerced using one or more coercion features available in a coercion rule as shown below.
- eg. If corresponding shown fields are configured, anonymization of studies sent from archive is applied last
Note : Each coercion type gets applied only if corresponding fields are configured. Examples shown for some fields.
Coercion Feature | Description |
---|---|
Retrieve as Received | Retrieve study from local archive to be sent to destination, as it was received from the source. Retrieve as Received feature redundant if any of the below coercion features are applied |
Coerce attributes from Leading archive | Query Leading archive for study using Study UID (of study retrieved from local archive) and coerce dataset of retrieved study objects based on configured Attribute Update Policy |
Nullify Tags | Used for nullifying values of one or more DICOM tags in dataset of retrieved study objects eg. To nullify OriginalAttributesSequence use 04000561 |
Merge Attributes | Used for merging values of one or more DICOM tags in dataset of retrieved study objects using different Attribute Formats - eg. PatientID=JMS{PatientID} (eg. if sending to AGFA) or by specifying static values in combination with received values. - eg. SpecificCharacterSet=ISO_IR 100 |
Coerce from XSL | Coerce one or more attributes using XSL stylesheet for more customization. Vendor may create customized stylesheets and configure this field to use it from the path specified in vendor's file system. |
Deidentify | Anonymize dataset of retrieved study objects (retrieved from local archive) according to one or more Deidentification profiles. One or more of above coercions may become redundant, as anonymization may get applied on them. |