Skip to content

Coerce incoming MPPS N CREATE requests to archive

Vrinda edited this page Mar 27, 2023 · 1 revision

Content

Overview

Following fields of an archive attribute coercion rule determine whether a particular rule will get applied or not. To coerce incoming MPPS N-CREATE requests, fields should be configured as

Coercion Rule field Value / Notes
DIMSE N_CREATE_RQ
Role SCU
SOP Class UID May be configured to one of MPPS SOP Class
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

Cascaded Sequence of application of multiple coercions using one coercion rule

Incoming MPPS requests received by archive can be coerced using one or more coercion features available in a coercion rule as shown below.

  • eg. If all shown fields are configured, nullifying attributes 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
Nullify Tags Used for nullifying values of one or more DICOM tags in received MPPS dataset
Merge Attributes Used for merging values of one or more DICOM tags in received MPPS dataset using
different Attribute Formats
- eg. PatientID={PatientID,slice,3}
or by specifying static dummy values in combination with received values.
- eg. PerformedProcedureStepID=PPS-{PerformedProcedureStepID}
Supplement from device Supplement one or more attributes in received MPPS dataset
Coerce from XSL Coerce one or more attributes using XSL stylesheet for more customization
Clone this wiki locally