Updated Record Is Not Moved To ASSUMEDMATCH Even If It's Weight Is Beyond matchThreshold (Doc ID 2076114.1)

Last updated on APRIL 25, 2017

Applies to:

Oracle Healthcare Master Person Index - Version 2.0.0 to 3.0.0 [Release 2.0 to 3.0]
Information in this document applies to any platform.

Symptoms

After a record was updated, it is not moved to Assumed Matches, even if is the same person and the weight is greater than matchThreshold.

Scenario:

1. We have 2 records (same person with different Family Name):

e.g: 

After the update, the records are Potential Duplicates and not Assumed Matches, although their weight (31) is beyond matchThreshold.

e.g.:

duplicateTreshold = 18

matchThreshold = 25

 

As per OHMPI documentation, Potential Duplicates are the records who's weight fall between duplicate and matchTresholds.

Any record with the weight beyond matchTreshold should be moved to SBYN_ASSUMEDMATCH table.

Changes

Looking at the master.xml file, it seems the Project's thresholds were modified. Initial thresholds were like:

duplicateTreshold = 4.18

matchThreshold = 48.75

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms