OHMPI Weighted Queries Returning Fewer Rows Than Exist
(Doc ID 2759949.1)
Last updated on MARCH 19, 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 184.108.40.206 version, Master Index Main Component
When doing a weight search in the GUI where the number of matching records in the database is greater than the configured search limit, the number of records returned in the GUI can be less than the configured search limit instead of equal to that search limit.
The issue can be reproduced at will with the following steps:
1. Configure the OHMPI GUI to make the ALPHA search a weighted search (midm.xml).
2. Configure the OHMPI GUI to set the search limit to a low number (such as 5)
3. Use a matching algorithm that includes a child object (such as the AUPatient model that includes the name as a child object)
4. Create data so that there are multiple matching EUIDs, each with multiple instances of matching names. For example, using the AUPatient mode, set up multiple patients all with last names
starting with S. Give the patients multiple names, each with a last name starting with S.
5. Do an ALPHA search in the GUI for the records created. Observe that even though more records than the search limit exist in the database, the number of records returned by the query is
less than the search limit.
This can also be shown by searching using a non-child object field, such as Date of Birth -- the search criteria doesn't have to be from the child object. What's required is that the query generated will return multiple records for a single EUID because all of those values are passed to the matching algorithm (eg. the AUPatient matching algorithm that includes matching against the NAME child object).
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