My Oracle Support Banner

OHMPI 2.0 - Issue With Twin Siblings On A Match Comparison (Doc ID 2045534.1)

Last updated on MARCH 31, 2021

Applies to:

Oracle Healthcare Master Person Index - Version 2.0.9 and later
Information in this document applies to any platform.

Goal

We are elaborating a solution to avoid assumed matchs when the patient has a twin sibling.

For example, we will use a field called 'TestComparator' with values 'true' or 'false' to verify if the object PESSOA has a twin sibling.

The solution is based on forcing a disagreement value when one of the patients on a match comparison has a twin sibling, so a match would only occur when all other fields are equal.

If you sum all fields used in the match (name, mother's name, dob, etc), we have a total of 51. Our match threshold is 41, so the disagreement value for the solution would be -10.

We created a new comparator to use the disagreement weight if one of the patients has 'TestComparator' equals 'true':

We identified two problems:

1. First one, when the values are equal, my comparator isn't called. We need a way to force the use of the comparator even when the values are equal.

2. Second one, when there's a null value. There's not a option for the third column of matchConfigFile.cfg to solve this problem. Ideally, we needed a option to force the use of the comparator even when one.

Solution

To view full details, sign in with your My Oracle Support account.

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


In this Document
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.