1. Release Notes
  2. Enhancements to Oracle Argus Safety
  3. Code list updates

Code list updates

Oracle Safety One Intake and Oracle Argus Safety share the Oracle Argus Safety Console. Oracle Safety One Intake uses the code lists from Oracle Argus Safety where applicable.

The following changes have been made to the Oracle Argus Safety Console code lists. For more information, refer to the eTRM document Argus_Safety8.4.1-S1A23.3_CaseForm_Console_Updates_Summary.xls. See How to obtain eTRM documents.

Attachment classification

New values have been added to the Attachment Classification code list to support Oracle Safety One Intake.
  • Source File
  • Supporting
  • Other Document Imported

You can access this code list from Argus Safety > Console > Code Lists > Argus > Attachment Classification.

Media Type

The following attachment types have been added to the Media Type standard code list to support additional media types accepted in Oracle Safety One Intake.

Attachment Type Media Type
PD application/pdf
ZIP application/zip
DCM application/dicom
CSV text/csv

The mapping of these values with agencies is NULL as these will not be used for outgoing AE reports to the agencies.

You can view the MIME type from Argus Safety > Console > Code Lists > Flexible Data Re-Categorization > Flexible Data Re-Categorization > MEDIATYPE > en (column).

Justification

When an invalid document is rejected, a justification must be provided. To support this behavior, the following values have been introduced for type Intake Rejection Justification in the Justifications codelist:
  • No Company Product
  • Non-AE Document
  • Other

Intake Source

A new flexible code list named INTAKE_SOURCE has been introduced to add external third-party systems and applications as sources. Additionally, this code list facilitates the configuration of processing rules for AE documents received from these sources.. You can view this code list and its values in Argus Safety > Console > Code Lists > Flexible Data Re-Categorization > Flexible Data Re-Categorization.

Note:

Safety One Intake accepts AE documents for automatic ingestion only from the sources that have been added to the Intake Source code list.
Source name Source type
User Upload 0
The attributes Triage Required and Multi-Case are used to configure processing rules.
  • When Triage Required is set for a source, the processing skips the Check Validity step.
  • If Multi-Case is set for a source, each document is treated as a separate potential case; otherwise, all documents correspond to one potential case.