Attributes Modification SCP Service. Updates Study/Series/Instance attributes of stored DICOM Composite Objects on receive of Attribute Modification Notifications. org.dcm4chex.archive.dcm.modify.AttributesModificationScpService The default constructor AttributesModificationScpService List of accepted called AE titles, separated by \ (backslash). CalledAETitles java.lang.String ANY = accept any.
CONFIGURED_AETS = accept any configured AE Title. ]]> CallingAETitles java.lang.String AcceptedTransferSyntax java.lang.String Original Attributes Sequence (0400,0561) on instance level.]]> UpdateOriginalAttributesSeq boolean return Success Status in that case. See also attribute NoRetryErrorCode of the Attributes Modification SCU Service.]]> EntityNotFoundErrorCode java.lang.String In regular workflows the patient should already exists with unique identifier]]> CreatePatientOnMoveStudy boolean Format: 'pid'['?']',issuer'['?'][',' ['['] demograhic-matches [']'] ]
demograhic-matches ::= demograhic-match['|' ...]
demograhic-match ::= [ignore',']demograhic-fields
ignore ::= 'ignore("' regular-expression '")'
demograhic-fields ::= demograhic-field['?'][',' ...]
demograhic-field ::= 'familyname'['(1)'] | 'givenname'['(1)'] | 'middlename'['(1)'] | 'nameprefix'['(1)'] | 'namesuffix'['(1)'] | birthdate | sex

Multiple alternative demograhic-matches can be specified using '|' as delimiter.

Substrings specified by 'ignore("' regular-expression '")' will be ignored for matching patient name components.

A '(1)' suffix of the attribute name specifies that only the first character need to match.

A question mark('?') after a attribute name specifies that a missing value in received DICOM objects will match with any value for that attribute in existing Patient Records, as Patient Records with missing values for that attribute will match with any value for that attribute in received DICOM objects. Attribute names without question marks specifies, that DICOM objects without values for such attributes will not match any existing Patient Record, and Patient Records without values for such attributes will not get selected on receive of any DICOM Composite Object.

With 'pid?', you have to configure the Patient's family name complex ('familyname') as additional matching criterium.

Surrounding demograhic-matches by brackets('[]') defines, that demographic fields shall *not* be considered for the selection of an existing Patient record, if the Patient ID is qualified by an Issuer/Authority in the received DICOM Composite Object *and* in the matching Patient Record.

Warning: Improper configuration may cause assignment of moved studies to wrong patient.

Default: pid,issuer?[familyname,givenname,middlename?,birthdate] ]]> PatientMatching java.lang.String Used internally. Do NOT modify. AEServiceName javax.management.ObjectName Used internally. Do NOT modify. DcmServerName javax.management.ObjectName &defaultAttributes; &defaultOperations;