When two or more records have a comparison score greater than the clerical review threshold and less than the auto-link threshold, and the records are from different sources, the MDM operational server joins them into a potential linkage task.
This action means that the records within the task possibly represent the same member. A potential linkage task can have an indefinite number of records from multiple sources. For example, Jon Public was entered as such in Source A during the first visit, and then as John Q. Public in Source B when he was admitted to the hospital. A comparison then determines a high likelihood that they are the same person and creates a potential linkage task.
Source | Source ID | Score | Name | Personal Identification Number | Gender | Phone | Date of Birth |
---|---|---|---|---|---|---|---|
SYS B | 895677 | 15.0 | John Q. Public | 482-89-1822 | M | 1230004 | 12/3/50 |
SYS A | 895688 | 15.0 | Jon Public | 422-89-1822 | M | 1230004 | 12/3/50 |
The MDM operational server differentiates between suspected duplicates and potential linkages because, in most instances, a duplicate within a source system is a higher priority issue than duplicates across multiple systems in an enterprise.