...
Supplement received GP-PPS N-CREATE message containing a Patient ID, but no Issuer Of Patient ID, with a value for Issuer Of Patient ID, if such is associated with the GP-PPS SCU AE by its AE Configuration entry.
Default Value: true
#PatientMatching
| Anchor | ||||
|---|---|---|---|---|
|
Defines which Patient Attributes in received GP-PPS N-CREATE requests shall be considered for the selection of an existing
Patient record in the archive.
Format: 'pid' ['?'] ',issuer' ['?'] [','<demograhic-match>]
<demograhic-match> ::= '[' <demograhic-fields> ']' | <demograhic-fields>
<demograhic-fields> ::= <demograhic-field> ['?'] [',' ...]
<demograhic-field> ::= 'familyname' | 'givenname' | 'middlename' | 'birthdate'
A question mark('?') after a attribute name specifies that a missing value in received GP-PPS 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 MPPS N-CREATE requests. Attribute names without question marks specifies, that GP-PPS N-CREATE requests without values for such attributes will not match any existing Patient Record, as Patient Records without values for such attributes will not get selected on receive of any GP-PPS 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 GP-PPS N-CREATE request and in the matching Patient Record.
Default Value: pid,issuer?[familyname,givenname,middlename?,birthdate]
#AcceptedSOPClasses
| Anchor | ||||
|---|---|---|---|---|
|
...