Use this patch set to install Oracle® Health Sciences Adverse Event Integration Pack for Oracle Health Sciences InForm and Oracle Argus Safety (Adverse Event: InForm and Argus Safety) Release 1.0.2.
Contents: Overview | Problems Addressed | List of Files Delivered in the Patch | Downloading the Patch | Installing the Patch | Uninstalling the Patch
This patch set includes support for InForm 6.0, Oracle Argus Safety 6.0.7 (includes Argus J), Argus 7.0.2, and Argus 7.0.3 (includes Argus J).
This section describes the bugs fixed in this patch and the previous patch to Oracle® Health Sciences Adverse Event Integration Pack for Oracle Health Sciences InForm and Oracle Argus Safety (Adverse Event: InForm and Argus Safety) Release 1.0.
The descriptions include two subsections: Before and After.
The Adverse Event: InForm and Argus Safety integration 1.0.2 patch set includes the following bug fixes:
When Autopsy Performed was sent as true but autopsy results were not available for the initial case, if the autopsy results became available during a follow-up, Argus Safety would still show autopsy results available as No. However, the autopsy results would appear properly.
If autopsy results are sent as part of follow-up, Argus Safety shows autopsy results available as Yes.
InForm Requester ABCS sent empty tags for fields that were not mapped or populated in InForm.
Only fields that contain values are sent from InForm to Argus.
Entering onset age in decades prevented the case from appearing in the Pending E2B Reports screen.
Entering onset age in decades sends the appropriate E2B code to Argus.
Because the PMDA profile was not supported, Argus J was not supported.
The integration supports the PMDA profile and can import data from InForm into the Argus J fields.
If a study product has only an investigational license in Argus, the import of the data from InForm did not recognize the study product name as the study product.
Study product matching works correctly when only investigational licenses exist.
Argus 7.0.1 and Argus 7.0.2 were supported by the integration.
Argus 6.0.7, including Argus J 6.0.7, is also supported by the integration.
Argus 7.0.1 and Argus 7.0.2 were supported by the integration.
Argus 7.0.3, including Argus 7.0.3 J, is also supported by the integration.
No indication was given if an error occurred when calling InForm Adapter to update the case id and status in InForm.
An error is raised and the call fails if there is an error when calling InForm Adapter to update the case id and status in InForm.
The Adverse Event: InForm and Argus Safety integration 1.0.1 patch set includes the following bug fixes:
An additional product tab was created during E2B imports. The second product tab contained the information about the product such as, dosing. Follow-up would go into the first tab that had information entered in the Argus Product setup.
An additional product tab is not created during E2B imports.
E2B follow-up import did not work for the CASE_PROD_DEVICES.UD_TEXT_7 extension field. When data for this field is populated and you send information from InForm to Argus for this user-defined field, you will not be able to accept the follow-up into the case.
E2B follow-up can now be accepted when it contains information for the CASE_PROD_DEVICES.UD_TEXT_7 extension.
When InForm user reports multiple primary causes of death and autopsy-determined causes of death for a given subject, the integration was interspersing each type of cause in the E2B. This resulted in a message that does not conform to the underlying message schema definition.
Note: There is no impact on the functionality of the integration.
When InForm user reports multiple primary causes of death and autopsy-determined causes of death for a given subject, the integration writes all primary causes of death followed by all autopsy-determined causes of death. These message conforms to the underlying message schema definition.
Integration writes an empty extension element < regsubmitindicator_extension/ > in the E2B file to Argus Safety. This extension element was not used by InForm to Argus Safety integration and hence there is no impact on functionality.
Integration does not write empty extension element < regsubmitindicator_extension/ > in the E2B file.
When dosage unit values were not specified in InForm (for example, grams or milligrams), Argus Safety E2B import process did not display an import warning. It imported dosage values without units to Argus Case Form.
When dosage unit values are not specified in InForm, Argus Safety E2B import process displays an import warning for missing unit values. Dosage values without units are not imported into Case Form fields > Products > < Product Name > > Dosage Regimens > Dose and Daily Dosage.
Argus 7.0.2 was not supported by the integration.
Argus 7.0.2 is now supported in addition to Argus 7.0.1.
During InForm trial design, study designer mapped Subject_AdverseEvent/RelatedtoStudyDrug indicator to a form field to indicate whether an adverse event was caused by the study drug.
During the trial run time, when InForm user selected a value that sets Subject_AdverseEvent/RelatedToStudyDrug indicator to True, the integration interpreted the study drug to be interacting and it incorrectly assigned study drug�s characterization code as 3.
Interacting does not mean that the study drug was related to the adverse event. An interacting drug is a non-study drug that interacted with the study drug and is believed to have caused the adverse event.
During InForm trial design, study designer maps Subject_SuspectDrug/SuspectDrug_Interacting indicator to a form field to indicate whether a given non-study drug caused the adverse event by interacting with the study drug.
During the trial run time, when InForm user enters a value that sets Subject_SuspectDrug/SuspectDrug_Interacting indicator to True, the integration assigns non-study drug�s characterization code as 3.
InForm 6.0 was not supported by the integration.
InForm 6.0 is now supported in addition to InForm 4.6 and InForm 5.5.
This patch is distributed as a zip file. To locate and download this patch:
Sign in to My Oracle Support at http://support.oracle.com
.
Click the Patches & Updates tab.
The Patches and Updates page opens and displays the Patch Search region.
In the Patch Name or Number field, enter the primary bug number (16949125) fixed by this patch.
Click Search to execute your query.
The Patch Search Results page opens.
Click the patch ID number.
The system displays details about the patch. In addition, you can view the Readme file before downloading the patch.
Click Download.
A dialog box opens.
Choose to save the file, browse to a temporary directory where the file is to be downloaded, and click Save.
Transfer the patch zip file to the necessary servers.
This section contains the following topics:
On Unix, execute the following commands:
$ cd < AIA_HOME >
$ chmod -R 777 services/
$ chmod -R 777 data/
On Windows, navigate to the following directories. Right-click on the directory name, select Properties, and deselect Read-only attribute in the context menu.
For example,
On Linux: /slot/ems####/oracle/16949125
On Windows: D:\oracle\16949125
On Linux: source aiaenv.sh
On Windows: aiaenv.bat
For Unix:
$ export OPATCH_HOME=$AIA_HOME/OPatch
$ export PATCH_HOME=< location where you unzipped patch >
$ export PATH=$OPATCH_HOME:$PATH
For Windows:
$ set OPATCH_HOME=%AIA_HOME%/OPatch
$ set PATCH_HOME=< location where you unzipped patch >
$ set PATH=%OPATCH_HOME%:%PATH%
apply
command based on the platform:
For Unix: $ opatch apply $PATCH_HOME -invPtrLoc $AIA_HOME/oraInst.loc -oh $AIA_HOME -jre < jre location >
For Windows: C:> opatch apply %PATCH_HOME% -invPtrLoc %AIA_HOME%\oraInst.loc -oh %AIA_HOME% -jre < jre location >
Note: jre_location is: < Middleware_Home > /jdk/jre or $JAVA_HOME.
For any questions or problems, contact Oracle Support for AIA.
To deploy the changes, perform the following:
The patch deployment plan is available at $PATCH_HOME/custom/scripts/Patch_16949125DP.xml
To run this, navigate to the $PATCH_HOME location and execute the following commands:
On Linux: $ ant -f
$AIA_HOME/Infrastructure/Install/AID/AIAInstallDriver.xml
-DDeploymentPlan=$PATCH_HOME/custom/scripts/Patch_16949125DP.xml
-DPropertiesFile=$AIA_INSTANCE/config/AIAInstallProperties.xml -l
$PATCH_HOME/16949125.log
On Windows: % ant -f
%AIA_HOME%\Infrastructure\Install\AID\AIAInstallDriver.xml
-DDeploymentPlan=%PATCH_HOME%\custom\scripts\Patch_16949125DP.xml
-DPropertiesFile=%AIA_INSTANCE%\config\AIAInstallProperties.xml -l
%PATCH_HOME%\16949125.log
For any questions or problems, contact Oracle Support for AIA.
This patch provides new scripts to run for Argus. Follow the steps in the sections titled Setting Up Argus Safety for Integration and Configuring Argus Safety to Use Extension Profiles in Chapter 8 of the Oracle� Health Sciences Adverse Event Integration Pack for Oracle Health Sciences InForm and Oracle Argus Safety Installation Guide Release 1.0.2.
If you ran the customization deployment plan steps listed below before applying this patch, you must run the customization deployment plan again. Follow these steps.
On Windows:
ant -f
%AIA_HOME%\Infrastructure\Install\AID\AIAInstallDriver.xml
-DPropertiesFile=%AIA_INSTANCE%\config\AIAInstallProperties.xml
-DDeploymentPlan=%AIA_HOME%\ data\AEInFormandArgus\customization\
AEInFormandArgusCustomMappingDP.xml -l %AIA_HOME%\data\
AEInFormandArgus\customization\AEInFormandArgusCustomMappingDP.log
On Linux:
ant -f
$AIA_HOME/Infrastructure/Install/AID/AIAInstallDriver.xml
-DPropertiesFile=$AIA_INSTANCE/config/AIAInstallProperties.xml
-DDeploymentPlan=$AIA_HOME/data/AEInFormandArgus/customization/
AEInFormandArgusCustomMappingDP.xml -l $AIA_HOME/data/
AEInFormandArgus/customization/AEInFormandArgusCustomMappingDP.log
On Linux:
source aiaenv.sh
$ export OPATCH_HOME=$AIA_HOME/OPatch
$ export PATCH_HOME=< location where you unzipped patch >
$ export PATH=$OPATCH_HOME:$PATH
% opatch rollback -id < patchnumber > -invPtrLoc $AIA_HOME/oraInst.loc -oh $AIA_HOME -jre < jre location >
$ ant -f
$AIA_HOME/Infrastructure/Install/AID/AIAInstallDriver.xml
-DDeploymentPlan=$PATCH_HOME/custom/scripts/Patch_16949125DP.xml
-DPropertiesFile=$AIA_INSTANCE/config/AIAInstallProperties.xml -l
$PATCH_HOME/16949125.log
ant -f
$AIA_HOME/Infrastructure/Install/AID/AIAInstallDriver.xml
-DDeploymentPlan=$PATCH_HOME/custom/scripts/Patch_16949125RollBackDP.xml
-DPropertiesFile=$AIA_INSTANCE/config/AIAInstallProperties.xml -l <
location and name where you want the log file written >
On Windows:
aiaenv.bat
$ set OPATCH_HOME=%AIA_HOME%/OPatch
$ set PATCH_HOME=< location where you unzipped patch >
$ set PATH=%OPATCH_HOME%:%PATH%
% opatch rollback -id < patchnumber > -invPtrLoc %AIA_HOME%\oraInst.loc -oh %AIA_HOME% -jre < jre location >
% ant -f
%AIA_HOME%\Infrastructure\Install\AID\AIAInstallDriver.xml
-DDeploymentPlan=%PATCH_HOME%\custom\scripts\Patch_16949125DP.xml
-DPropertiesFile=%AIA_INSTANCE%\config\AIAInstallProperties.xml -l
%PATCH_HOME%\16949125.log
ant -f
%AIA_HOME%\Infrastructure\Install\AID\AIAInstallDriver.xml
-DDeploymentPlan=%PATCH_HOME%\custom\scripts\Patch_16949125RollBackDP.xml
-DPropertiesFile=%AIA_INSTANCE%\config\AIAInstallProperties.xml -l
For questions or problems, contact Oracle Support for AIA.
Copyright © 2013 Oracle Corporation
All Rights Reserved