Load Smart Event Encoding model

About Smart Event Encoding

The Smart Event Encoding feature enables automatic event coding when verbatim or event descriptions deviate from an exact Preferred Term (PT) or Lowest Level Term (LLT) match. This feature works only when the Smart Event Encoding Model is available in the system. You can upload the Smart Event Encoding Model through the Dictionary Management menu.

Tip:

Oracle recommends you to update the Smart Event Encoding Model post each MedDRA dictionary release. This feature works best, when you use same version of MedDRA dictionary and Smart Event Encoding Model.

Prerequisites

• Set the Maintenance Mode to System down for Maintenance. For more information, see Configuring System Maintenance.
• Download the latest Smart Event Encoding Model (.zip file) from My Oracle Support (Patch ID 36147492).

  Note:

  This .zip file is password-protected. Log a Service Request (SR) to obtain the password.

Note:

• The Smart Event Encoding Model will be optimized to the latest MedDRA version.
• Make sure that the Smart Event Encoding Model being uploaded is not already loaded in the system to avoid errors.

To load the Smart Event Encoding Model:

1. From Argus Console, go to Tools, click Dictionary Management and select Dictionary Loader.
2. Select Load New.

   Note:

   The Overwrite feature is not available for Smart - Event Encoder Dataset.
3. In the Dictionary Type drop-down, select Smart - Event Encoder Dataset.
4. In the Dictionary File (.zip file containing dictionary data) field, select the local path to the Smart Event Encoding Model ZIP file.
   The version is automatically populated based on the selected ZIP file.

   Note:

   • If any mandatory file is missing from the .zip file, an error message listing the missing files appears.
   • If the model version being uploaded matches the version already loaded in the database, an error message appears.
5. In the Notification Email Address field, set the email address to receive an update on the status of the load operation after completion. This field is auto-populated with the email address of the logged-in user from the user setup in Access Management.

   Note:

   You can provide multiple email addresses separated by semicolon (;).
6. Click Load.
   The Status section will display the progress of the load. Once the load is complete, the log file is available for download.

   Note:

   For troubleshooting, refer to the CMN_Error log and Argus logs.