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 N-CREATE requests 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 UPS N-CREATE request. Attribute names without question marks specifies, that DICOM UPS N-CREATE requests 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 UPS N-CREATE request.
With 'pid?', you have to configure the Patient's family name complex ('familyname') as additional matching criterium.
Surrounding demograhic-match 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 UPS N-CREATE request *and* in the matching Patient Record.
Warning:Improper configuration may cause UPS assignments to wrong patient.
Default: pid,issuer?[familyname,givenname,middlename?,birthdate]
]]>
Example: 5x1m,10x10m
=> retry a total of 5 times, one minute apart for each retry; then retry
a total of 10 times, 10 minutes apart for each retry.
Example:
[AET1]2x1m,3x10m
[AET2]NEVER
5x1m,10x10m
=> for destination AET1 retry a total of 2 times, one minute apart for
each retry; then retry a total of 3 times, 10 minutes apart for each retry.
Retries are disabled for destination AET2. For all other destinations retry a
total of 5 times, one minute apart for each retry; then retry a total of 10
times, 10 minutes apart for each retry. ]]>