Medically Significant Field on the Events Tab not Always Populated Correctly on E2B Import with Custom Code (Doc ID 1438761.1)

Last updated on APRIL 13, 2012

Applies to:

Oracle Argus Interchange - Version: 4.2.1 and later   [Release: 4.2 and later ]
Information in this document applies to any platform.

Symptoms

When E2B import mapping code exists which updates the Medically Significant field for an event from more than one DTD element, this field is not always populated correctly during E2B import.

Steps to Reproduce:

  1. Login to the ESM Mapping Tool, create a new message profile by copying a standard message profile
  2. Select the new message profile
  3. In the XML tree view, highlight the following element by expanding the XML tree: SAFETYREPORT > PATIENT > REACTION > TERMHIGHLIGHTED (B.2.i.3)
  4. Click on the 'Receive' tab on the right side of the screen
  5. Replace the existing code for this element with custom code which updates CASE_EVENT.MED_SERIOUS
  6. Leave the 'Receive' code for SAFETYREPORT > PATIENT > REACTION > PRIMARYSOURCEREACTION (B.2.i.0) as shipped
  7. In Argus Console, configure a Reporting Destination to use this new message profile
  8. Import an ICSR (E2B) XML file containing values for <seriousnessother> and <termhighlighted> which will both update CASE_EVENT.MED_SERIOUS
  9. In Argus, Reports, E2B Pending, right click and 'Accept E2B' to create a new case
  10. Open the imported case, select the Events tab, and note that sometimes the Medically Significant field for the event is NOT checked when it should be based on the xml file contents and E2B import mapping code for the message profile
  11. This occurs intermittently even for the same XML file

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms