To support duplicate events resolution, the query to search for the duplicates is executed again to get the latest data associated with the duplicate claims.

1. FetchDuplicateClaimDetails is the pre-processing data transform for PR_DuplicateClaimLevel flow action, which is triggered to show the resolve event details for the header level dupe.
   1. Prepares the ESStandarQuery and Header query by reusing PrepareESStandardQuery and PrepareESHeaderQuery.
      1. Checks whether the dupes exist on the data page.
      2. If duplicates are present, then the system iterates through the duplicate hits.
      3. Refreshes the associated data of the possible duplicate edits.
      4. If there is no associated data which means the duplicates are absent at the present so pyIsTagged is set to False on the TempEventListPage.
      5. Iterate through the configured claim duplicate properties and compare the claim values with the dupe claim values, if they are equal DuplicateClaimInfo is populated and MatchedThresholdValue is added to contain the matched properties.

   

2. FetchDuplicateClaimLineDetails is the activity, which trigger the FetchDuplicateClaimLineDetails collection, which populate the resolve event details for the line level dupe.
3. FetchDuplicateClaimLineDetails
   1. Set the temp properties on the Declare_CE_Global which will be used in Preparing queries.
      1. PrepareESStandardQuery prepare the standard query on the claim.
      2. If it’s a dupe within claim lines GetDupeClaimLineWithinClaimDetails prepares the claim line query and sets it to a temp page.
      3. If it’s a dupe with other than its own claim lines GetDupeClaimLineOutsideClaimDetails dos the following to prepare the query.
         • Calls the DuplicateEditsTempPageClaimLineSetup to prepare the temp page.
         • PrepareESClaimLineQuery prepares the claim line query on Work Level.

         If there is a possible duplicate found on the hits, we will take the first claim ID and prepare the query for the claim line level and set it to a temp page.

      4. CE_NRTIndexClaim is the activity which opens the duplicate claim ID which is considered and runs the NRT to make the claim lines available for querying.
      5. AddDuplicateClaimLineData, if the ClaimLineQuery is not empty, this triggers the search and iterates through the configured claim line duplicate properties and compares them to the current claim line values with the dupe claim line values. If they are equal DuplicateClaimInfo is populated and MatchedThresholdValue is added for the matched properties.
   2. If there is no associated data, this means that the duplicates are absent, so pyIsTagged is set to False on the TempEventListPage.

   

4. DupClaimCompare is the section, which shows the relevant data to the user for both the header level and line level dupe resolution.
   1. If the TempEventListPage.pyIsTagged Boolean value is false, a message is displayed that no current duplicates are found.
      • Header level / Line level dupes DuplicateClaimLineInfo is shown in the grid on the UI. The grid holds the property name, value, threshold weight and the matched weight.

• Claims business audits