LOCAL_A
- The source record submitted from a third party system, representing the $input
recordMASTER_A
- The master/golden record established by SanteMPI's master data management layer for LOCAL_A
(note there may be multiple locals attached to this record)LOCAL_B
- The source record submitted from a third party system, representing the $block
recordMASTER_B
- The master/golden record established by SanteMPI's master data management layer for LOCAL_B
(note: there may be multiple locals attached to this record)Detected Duplicates
table in excel format$input or LOCAL_A
patient which was being registered$block or MASTER_B
patient which was scored0.0 .. 1.0
) that the patient represented in Patient A is the same as Patient B.LOCAL_A
from MASTER_A
(i.e. detaches the patient in Patient A column from its current master / golden record)LOCAL_A
to MASTER_B
(i.e. attaches the Patient A column to the Patient B master / golden record)MASTER_A
then MASTER_A
is obsoleted.ADT^A40
or PMIR Merge
LOCAL_A
and MASTER_B
Ignore
instruction which instructs all future detections between LOCAL_A
and MASTER_B
to be ignored.View
option, will display a more detailed analysis of the match pair. This view assists data administrators in determining the validity of the match, such that the match can be verified or ignored.View
option.Matched Entities
tab shows summary information of the two patients which have been flagged as potential matches. However, there are times when a more holistic view of a patient match pair is desired. Some reasons the A/B compare may be used:0 .. 1
what the match agreement was.whenNull
action was taken on the score.whenNull
score was applied.