Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

NONE = do not replace Patient IDs in MPPS N-CREATE requests from any MPPS SCU.

Default Value: NONE

#PatientMatching
Anchor
PatientMatching
PatientMatching

Defines which Patient Attributes in received MPPS 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 MPPS 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 MPPS 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 MPPS 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 MPPS N-CREATE request and in the matching Patient Record.

Default Value: pid,issuer?[familyname,givenname,middlename?,birthdate]

#AcceptedTransferSyntax
Anchor
AcceptedTransferSyntax
AcceptedTransferSyntax

...