Datasources

We added a new Potential matches tab for Account datasources, put logic in place to limit searching extremely large datasources, and added helper text to the study datasources page.

Account datasources

New Potential matches tab

Identifying matching sites to eliminate duplicate sites in Oracle Site Select and maintaining site history across studies is important, and with release 24.2, we enhanced the Account datasources detail page to add a new Potential matches tab that helps you manage these records. On the new tab, you can review the disambiguation potential matches and duplicates for sites you’ve imported into a datasource.

You must have the existing Data Source Management business role permission to access the new tab and to use the functionality granted to you with this permission (i.e., some functionality is available only to Oracle administrators).

The new Potential matches tab loads when you click on the number of potential matches for a datasource from the account datasource list page. You can also access the tab when you click the Potential matches tab on the datasource details page. The tab itself shows a badge with total actionable potential matches.

You’ll see three subtabs displayed above the grid on the Potential matches tab:

1. Total potential matches – shows the number of records in the datasource that potentially matched a record in Oracle Site Select across all accounts. This tab is visible to you, but the content is enabled only for Oracle administrator use.
2. Actionable potential matches – shows the number of potential match records in the datasource that match against a datasource record within this account. This tab is enabled for your use and Oracle administrator use.
3. Oracle-actionable potential matches – shows the number of potential match records in the datasource that match against a datasource record outside this account. This tab is visible to you, but the content is enabled only for Oracle administrator use.

Only an Oracle administrator can see and act on potential matches or duplicates in a site profile datasource.

By default, the Potential matches grid shows both potential duplicates and potential matches (i.e., filtering is off). If preferred, filter the displayed records using the “Filter by match type” drop-down to select Potential or Duplicate. You can also search records in the list. Search will return string matches in any of the following grid columns:

• Last name
• First name
• PI email
• Institution
• City
• State
• Zip
• Address 1
• Address 2
• NPI
• Country
• Datasource
• Match type
• Master profile id

All records in the potential match grid are site records, and you’ll see a double row for each. The top record is the current datasource record; the bottom is the record matched record. The row for the record existing in Oracle Site Select has an inbox icon.

The Actionable potential matches tab shows the message “No potential matches were found for datasource” instead of an empty grid if no potential matches or duplicates are scoped to the account. This is the case regardless of whether there are potential matches or duplicates with a record in another datasource.

We also made the following related enhancements in this release:

• The potential matches link on the Account datasource list page now navigates to the new Potential matches tab instead of the previous potential matches page
• The Account datasources page now has a filter that allows you to filter the display to only those datasources with at least one pending potential match or at least one pending potential duplicate.
• Datasources listed on the Account datasources page will have an additional “<number> potential duplicates” detail line if the datasource has a potential duplicate.

Resolve potential matches

All records in the potential match grid are site records; you’ll see a double row for each. The top record is the current datasource record, and the bottom is the record matched record. The row for the record existing in Oracle Site Select has an inbox icon.

Delete record for a potential duplicate match

To take action on a duplicate record, you may delete it from the datasource Records tab. You must have the existing Edit Datasource Record business role permission to delete one of the duplicate records.

Resolve a potential match

When you select at least one match pair in the grid, you can click the button above the table to Resolve as Match (default) or Resolve as Not a match.

If you choose Resolve as Match, Oracle Site Select updates the records as it did previously, meaning:

• For potential matches: The master profile IDs of the individual sites are updated to match the existing site so that the inbound site matches the site existing in Oracle Site Select. The site pairs are marked as resolved, and the potential matches grid updates to remove the potential match pair.
• For potential duplicates: The master profile IDs of the individual sites are NOT updated. The pairs are marked as DUPLICATES of each other, and the potential matches grid updates to remove the potential duplicate pair.

If you choose Resolve as Not a Match, Oracle Site Select updates the records as it did previously, meaning:

• For both potential matches and potential duplicates: The master profile IDs of the individual sites are NOT updated. The site pairs are marked as resolved, and the potential matches grid updates to remove the potential match pair.

Note that you can resolve rows of sites as matches and not matches, alternating, without needing to reload the page. You can also use the Resolve as Match action to resolve potential matches and potential duplicates as matches at the same time. There is a limit of 25 match-pairs allowed to be resolved at one time. Any additional pairs will not be resolved.

Epic: SEL-17268

Account datasource search

We updated datasource search behavior to prevent performance issues when you query large datasources. Now Oracle Site Select disables the search field when a flat datasource or composite datasource entity (i.e., investigators) has more than 50,000 records. In this case, a new message, “Searching is disabled for entities with greater than 50,000 records,” is displayed.

Epic: SEL-17230

Study datasources

We added new helper text to the study datasources page that advises you to rebuild study master list criteria filters if you remove a study datasource. The new helper text is: “After removing a datasource from a study it is important to rebuild the filters on the study master list criteria page. Please navigate to and re-save the master list criteria page so the study can properly rebuild the master list using the remaining datasources.”

Epic: SEL-17268