2 General configurations

You must perform the following configurations to use Consolidated Intake:

• Provision users
  You must create users in Oracle Identity Cloud Service (IDCS) before you can give them access to Oracle Safety One Argus. You may need to perform additional synchronization, depending on how your organization manages application access.
• Add users and assign roles
  Once you have provisioned a user in Oracle Identity Cloud Service, you can add the user to Oracle Safety One Argus and grant them access to the Consolidated Intake module.
• Configure intake numbering
  For the adverse event reports sent to Oracle Safety One Argus, a unique identifier is assigned. The default numbering format is [SSS][YY][MM]-[########], but you can customize the identifier if necessary.
• Enable reauthentication during intake
  You can configure Safety One Argus to require reauthentication with a justification when intake processors are accepting or rejecting initial, follow-up, amendment, or nullification records.
• Configure Smart Duplicate Search
  You can adjust the weights and thresholds of the smart duplicate search using a spreadsheet available for download (and modification) in Argus Console.
• Configure follow-up merge
  You can download and modify the predefined comparison logic for evaluating follow-up data against existing case information in the Default Merge Configuration spreadsheet in Argus Console.
• Configure hold follow-up merge
  You can configure your intake workflow to hold merging follow-ups of AE records until the appropriate conditions, such as workflow state or custom rules, are met.
• Configure the automatic assignment of intake records
  Automatic assignment of intake records is enabled by default, prioritizing the Intake Worklist so that intake processors can assess time-sensitive and serious records at the start of their session.