Skip Headers

Oracle® Argus Insight Extensibility Guide Release 7.0.3 E48114-01 |
Home | Book List | Contents | Index | Contact Us

Previous | Next
| PDF · Mobi · ePub

# 3 Code List Extensibility

Flexible Data Recategorization is an Argus Safety functionality through which users can define code list display values in different languages, whether natural human languages like English or artificial ones like E2B.

Argus Safety maintains the data for supported languages and Argus Insight ETL populates this code list data in the corresponding tables as listed below:

Table 3-1 Code List Data Tables

Argus Safety Table | Argus Insight Table
--- | ---
CODE_LIST_MASTER | DM_CODE_LIST_MASTER
CODE_LIST_CODE_ATTRIBUTES | DM_CODE_LIST_CODE_ATTRIBUTES
CODE_LIST_DETAIL_DISCRETE | DM_CODE_LIST_DETAIL_DISCRETE

Customer-specific changes, such as new values for the existing code lists as well as completely new code lists, are made in Argus Safety. These values are then fetched into Argus Insight through the ETL. Users can then create advanced condition queries in Argus Insight that reference the fields in the Flexible Data Recategorization Code List.

The following sections explain how to configure a code list display value in a new language for an already existing code in Argus Safety:

- Configuring Flexible Data Recategorization with a New Natural Language

- Configuring Flexible Data Recategorization with a New Custom Language

## 3.1 Configuring Flexible Data Recategorization with a New Natural Language

You can configure a code list display value in a new Natural language for an already existing code in Argus Safety.

For example, assume that for the code list GENDER, data in the table CODE_LIST_DETAIL_DISCRETE for code 1 is available in the following three decode contexts (languages):

Figure 3-1 Original Decode Contexts (Languages)

To configure the same code 1 in the code list GENDER for a new language such as GERMAN (decode context 'ge'):

1. Populate the table CODE_LIST_DETAIL_DISCRETE in Argus Safety with required values in the GERMAN language

       INSERT INTO CODE_LIST_DETAIL_DISCRETE (CODE_LIST_ID, DECODE_CONTEXT, CODE, DISPLAY_VALUE, PREFERRED, SORT, LAST_UPDATE_TIME, ENTERPRISE_ID) VALUES ('GENDER', 'ge', 1, 'männlich', 0, null, sysdate, 1);

   Figure 3-2 New Decode Contexts (Languages)

2. After the Argus Insight ETL runs, to create an Advanced Condition field which displays the GENDER value in the GERMAN language, add a new row in the CMN_FIELDS table in Argus Insight with values similar to the example shown below:

   Column | Value
   --- | ---
   ENTERPRISE_ID | 1
   FIELD_ID | New field ID that must be unique and must be in the following range: For customers: 30000000 - 39999999 For partners: 40000000 - 49999999 All other IDs are reserved for Oracle.
   FIELD_LABEL | Gender German
   TABLE_NAME | V_RPT_CASE
   COLUMN_NAME | GENDER_ID
   JOIN_FIELD |
   SELECT_TABLE |
   SELECT_COLUMN |
   ADV_COND_FIELD | 1
   TREE_VIEW | PATIENT:Patient Information
   UNIQUE_FIELD_LABEL | Gender German
   SQL_SELECT | SELECT CODE ID, DISPLAY_VALUE STATUS from DM_CODE_LIST_DETAIL_DISCRETE WHERE CODE_LIST_ID = GENDER AND DECODE_CONTEXT = 'ge'
   FIELD_TYPE | 1
   HIDDEN | 0
   TYPE_AHEAD |
   BLINDED_FIELD |
   CONTROL_TYPE_ID | 2
   FIELD_LENGTH | 255
   ADDITIONAL_TABLE_LIST |
   ADDITIONAL_WHERE |

## 3.2 Configuring Flexible Data Recategorization with a New Custom Language

You can configure a code list display value in a new Custom language for an already existing code in Argus Safety.

For example, assume that for the code list CAUSALITY, the following data is available in the table CODE_LIST_DETAIL_DISCRETE for 'en' decode context (English language):

Table 3-2 Original Display Values

CODE_LIST_ID | DECODE_CONTEXT | CODE | DISPLAY_VALUE | PREFERRED | SORT | LAST_UPDATE_TIME | ENTERPRISE_ID
--- | --- | --- | --- | --- | --- | --- | ---
CAUSALITY | en | 1 | Definitely Not | 0 | (null) | 9-Jul-13 | 1
CAUSALITY | en | 2 | Unlikely | 0 | (null) | 9-Jul-13 | 1
CAUSALITY | en | 3 | Possible | 0 | (null) | 9-Jul-13 | 1
CAUSALITY | en | 4 | Probable | 0 | (null) | 9-Jul-13 | 1
CAUSALITY | en | 5 | Highly Probable | 0 | (null) | 9-Jul-13 | 1
CAUSALITY | en | 6 | Definite | 0 | (null) | 9-Jul-13 | 1

To configure the same code list CAUSALITY for the custom values Related and Unrelated, which are used as buckets or categories to group the already existing values:

1. Add a new language such as CUSTOM (decode context CUSTOM) by populating the table CODE_LIST_DETAIL_DISCRETE in Argus Safety with required values in the CUSTOM language.

       INSERT INTO CODE_LIST_DETAIL_DISCRETE (CODE_LIST_ID, DECODE_CONTEXT, CODE, DISPLAY_VALUE, PREFERRED, SORT, LAST_UPDATE_TIME, ENTERPRISE_ID) VALUES ('CAUSALITY', 'CUSTOM', 1, 'Related', 0, null, sysdate, 1);

   Table 3-3 New Display Values

   CODE_LIST_ID | DECODE_CONTEXT | CODE | DISPLAY_VALUE | PREFERRED | SORT | LAST_UPDATE_TIME | ENTERPRISE_ID
   --- | --- | --- | --- | --- | --- | --- | ---
   CAUSALITY | en | 1 | Definitely Not | 0 | (null) | 9-Jul-13 | 1
   CAUSALITY | en | 2 | Unlikely | 0 | (null) | 9-Jul-13 | 1
   CAUSALITY | en | 3 | Possible | 0 | (null) | 9-Jul-13 | 1
   CAUSALITY | en | 4 | Probable | 0 | (null) | 9-Jul-13 | 1
   CAUSALITY | en | 5 | Highly Probable | 0 | (null) | 9-Jul-13 | 1
   CAUSALITY | en | 6 | Definite | 0 | (null) | 9-Jul-13 | 1
   CAUSALITY | CUSTOM | 1 | Unrelated | 0 | (null) | 9-Jul-13 | 1
   CAUSALITY | CUSTOM | 2 | Unrelated | 0 | (null) | 9-Jul-13 | 1
   CAUSALITY | CUSTOM | 3 | Related | 0 | (null) | 9-Jul-13 | 1
   CAUSALITY | CUSTOM | 4 | Related | 0 | (null) | 9-Jul-13 | 1
   CAUSALITY | CUSTOM | 5 | Related | 0 | (null) | 9-Jul-13 | 1
   CAUSALITY | CUSTOM | 6 | Related | 0 | (null) | 9-Jul-13 | 1

2. After the Argus Insight ETL runs, to create an Advanced Condition field which displays custom CAUSALITY values, add a new row in the CMN_FIELDS table in Argus Insight with values similar to the example shown below:

   Column | Value
   --- | ---
   ENTERPRISE_ID | 1
   FIELD_ID | New field ID that must be unique and must be in the following range: For customers: 30000000 - 39999999 For partners: 40000000 - 49999999 All other IDs are reserved for Oracle.
   FIELD_LABEL | Custom Reported Causality
   TABLE_NAME | RPT_EVENT_ASSESS
   COLUMN_NAME | RPT_CAUSALITY_ID
   JOIN_FIELD |
   SELECT_TABLE |
   SELECT_COLUMN |
   ADV_COND_FIELD | 1
   TREE_VIEW | ANALYSIS:Case Assessment
   UNIQUE_FIELD_LABEL | Custom Reported Causality
   SQL_SELECT | SELECT DISTINCT DISPLAY_VALUE ID, DISPLAY_VALUE STATUS FROM DM_CODE_LIST_DETAIL_DISCRETE WHERE CODE_LIST_ID = 'CAUSALITY' AND DECODE_CONTEXT = ' CUSTOM'
   FIELD_TYPE | 1
   HIDDEN | 0
   TYPE_AHEAD |
   BLINDED_FIELD |
   CONTROL_TYPE_ID | 2
   FIELD_LENGTH | 255
   ADDITIONAL_TABLE_LIST |
   ADDITIONAL_WHERE |

3. Now, insert a new row to the table CMN_COMPLEXFIELDS_CONFIGURATION.

   Column | Value
   --- | ---
   ENTERPRISE_ID | 3
   FIELD_ID | <Same Field ID as in the CMN_FIELDS table>
   OPERATOR | equal to
   SORT_ORDER | 1
   REQ_TABLE_LIST |
   WHERE_QUERY | RPT_EVENT_ASSESS.RPT_CAUSALITY_ID IN (SELECT CODE FROM DM_CODE_LIST_DETAIL_DISCRETE WHERE DISPLAY_VALUE = 'PARAM_VALUE' AND CODE_LIST_ID = 'CAUSALITY' AND DECODE_CONTEXT = 'CUSTOM')