ADVERSE EVENT Checkbox Value Population After E2B Import On Analyis->MedWatch Screen
Last updated on MARCH 08, 2017
Applies to:Oracle Argus Safety - Version 7.0.3 and later
Information in this document applies to any platform.
Oracle Argus Safety Version 7.0.3
ADVERSE EVENT Check-box value population after E2B import on Analysis->MedWatch screen - what is the logic ?
The Adverse Event Check-box on the Argus case form Analysis->MedWatch tab is checked sometimes and not checked other-times after E2B import.
Request is to clarify the logic on which this check-box is population is driven.
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