The following example illustrates how MRNs are merged in AutoFill Keyword Sets when MRNs are not unique. In this scenario, MRN 22 is merged into MRN 11. However, the system has two instances of MRN 22.
In this case, the HL7 Back-end Job Processor uses the assigning authority value from the HL7 merge message to merge the correct instances of MRN 22. Therefore, AutoFill Keyword Sets containing the MRN Keyword Type must also contain the MRN Assigning Authority Keyword Type in order to be updated when MRNs are merged.
If the target MRN has a different assigning authority from the source MRN, the import process will update both the MRN value and the Assigning Authority value in the affected AutoFills, regardless of the Update Secondary Keywords setting.