Coerce incoming C STORE requests on receive of studies to archive
Content
Following fields of an archive attribute coercion rule determine whether a particular rule will get applied or not. To coerce incoming studies, fields should be configured as
| Coercion Rule field | Value / Notes |
|---|---|
| DIMSE | C_STORE_RQ |
| Role | SCU |
| SOP Class UID | May be configured to one of Storage SOP Classess to limit the rule only to certain types of SOP Class objects |
| 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 |
Incoming studies received by archive can be coerced using one or more coercion features available in a coercion rule in the following sequence as shown below.
- eg. If all shown fields are configured, coercing by leading archive is applied first, whereas coercing by XSL stylesheet is applied at last
Note : Each coercion type gets applied only if corresponding fields are configured. Examples shown for some fields.
| Coercion Feature | Description |
|---|---|
| Coerce attributes from Leading archive | Query Leading archive for study using Study UID in received dataset and coerce based on configured Attribute Update Policy |
| 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 |
| Trim ISO 2022 Character Set | Used for replacing single code for Single-Byte Character Sets with Code Extensions with code for Single-Byte Character Sets without Code Extensions |
| Nullify Tags | Used for nullifying values of one or more DICOM tags in received dataset. Values need to be specified always as DICOM tag of attribute to be nullified as hex string. eg. To nullify IssuerOfAccessionNumberSequence use 00080051 |
| Merge Attributes | Used for merging values of one or more DICOM tags in received dataset using different Attribute Formats - eg. PatientID={PatientID,slice,3} or by specifying static values in combination with received values. - eg. AdmissionID=ADM-{AdmissionID} |
| Nullify Issuer of Patient ID | Nullify Issuer of Patient ID ALWAYS or if Issuer of Patient ID in received dataset matches or does not match with configured Issuer of Patient ID |
| Supplement Issuer of Patient ID | Supplement value for Issuer of Patient ID based on configured format - eg. pdgen-{00100010,hash}-{00100030} |
| Supplement from device | Supplement one or more attributes in received dataset. The device which is used for supplementing shall contain one or more DICOM fields configured on it. eg Institution Name, Issuer Of Patient ID etc. |
| Merge from MWL | Search for MWL in external or local archive based on specified Merge MWL Matching Key (typically set to AccessionNumber) and coerce attributes according to configured stylesheet specified in Merge MWL Template URI (typically configured to use default mwl2series.xsl in archive's default vendor data location (i.e. ${jboss.server.temp.url}/dcm4chee-arc/mwl2series.xsl) or customized stylesheet based on default located at path specified in vendor's file system.) |
| 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. |