OHMPI Isn't Deleting Potential Duplicates When An EUID Is Deactivated As A Result Of A Merge
(Doc ID 2732629.1)
Last updated on APRIL 02, 2021
Applies to:Oracle Healthcare Master Person Index - Version 188.8.131.52 and later
Information in this document applies to any platform.
On Oracle Healthcare Master Person Index (OHMPI) 184.108.40.206 version, Master Index Main Component
Normally, when an EUID is deactivated, potential duplicates are deleted for that EUID.
However, when an EUID is deactivated because the last active local id on that EUID is merged into a local id on a different EUID, leaving behind only non-active local ids, the EUID is deactivated, but the potential duplicates are not deleted.
Recalculating potential duplicates using the calculatePotentialDuplicates also does not delete the potential duplicates as it successfully recalculates the potential duplicates for the inactive EUID
The issue can be reproduced at will with the following steps:
1. Create an EUID that has potential duplicates and two source system records.
2. Deactivate one of the source system records
3. Merge the other source system record into a different EUID
4. The original EUID should now be deactivated, but if you check the potential duplicates tab in the GUI you'll still see potential duplicates for them.
More importantly, you'll get an error if you try to merge the potential duplicates (which is why this is a problem)
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