3 Argus Console configurations

Before you can begin using many of the features in the Oracle Safety One Intake interface, you need to complete the following configurations in the Argus Console:

  • 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 Oracle Safety One 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.
  • Configure a new agency
    You need to configure a new agency in Argus Console that uses the SAFETY ONE ARGUS TEMPLATE E2B R3+ profile.
  • Configure the API intake source
    You can set up external APIs that send documents to Oracle Safety One Argus to be reviewed in the Intake Worklist. In this configuration step, you need to define a source name in the INTAKE_SOURCE code list for external APIs and how the documents coming from the API will be handled.
  • Configure the email intake source name
    To be able to use email intake monitoring in the Oracle Safety One Intake module, you need to make sure the appropriate email source name has been defined in the Argus Console INTAKE_SOURCE code list before proceeding with the additional configurations in Oracle Safety One Intake.
  • 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.
  • Enable narrative processing for E2Bs
    You can enable automatic processing to extract additional product and event data from narrative information included in E2Bs during intake.
  • Publish intake records to a sponsor-owned safety database for case processing
    If you represent a Contract Research Organization (CRO), you can configure your intake workflow to publish records to a sponsor-owned safety database for case processing after intake has been completed. This option is only available when CRO mode is enabled.