Table of Contents
- Title and Copyright Information
- Preface
-
1
What's New?
- Introduction
- New in Oracle Argus Mart Signal Management for the Oracle Empirica Signal 9.2.2.1 Release
- New in Oracle Argus Mart Signal Management for the Oracle Empirica Signal 9.2.2 Release
- New in Oracle Argus Mart Signal Management for the Oracle Empirica Signal 9.2 Release
- New in Oracle Argus Mart Signal Management for the Oracle Empirica Signal 9.1 Release
- New in Oracle Argus Mart Signal Management for the Oracle Empirica Signal 9.0 Release
- New in Oracle Argus Mart Signal Management for the Oracle Empirica Signal 8.1 Release
- 2 MedDRA Standardized MedDRA Query (SMQ) Support
- 3 Oracle Argus Mart Data Tables and Views
- 4 Argus Mart Data Configurations
-
5
Data Mining Table Schema
- About the Data Mining Table Schema
- SM_CASE Table
- SM_CAUSE_OF_DEATH Table
- SM_DOSE Table
- SM_EVENT View
- SM_EVENT_PLUS_SMQ Table
- SM_EVENT_PLUS_SMQ_NARROW View
- SM_EVENT_PRODUCT Table
- SM_INDICATIONS Table
- SM_INGREDIENTS Table
- SM_LAB Table
- SM_NARRATIVE Table
- SM_NEONATES Table
- SM_PARENT_INFO Table
- SM_PAT_HIST Table
- SM_PREGNANCY Table
- SM_PRODUCT Table
- SM_REPORTERS Table
-
6
Argus Signal Management
- About Argus Signal Management
- Argus Signal Management Configuration
- Standard Argus Subpopulations
- Case Scoring
- Standard Data Mining Runs
- Data and Scores in Signal Management
-
7
Fixed in Previous Versions
- 16391714 - Support for Argus multi-enterprise signal analysis in the Oracle Cloud
- 22011001 - Preferred PSUR Product Name variable references wrong table
- 29179497 - SIGNALDRUGCOLVIEW entries for NEW alert reference wrong views
- 33074218 - Signal refresh does not include cases with valid start date equal to ASOFDATE
-
8
Known Issues
- 17340200 - Argus Mart - UVT tables created by Oracle Empirica Signal will not have ENTERPRISE_ID: ETL will fail
- 21915410 - Selecting non-default view for SMC before first refresh throws error
- 22456788 - Auto-Assign Reviewers with Argus SMC references wrong variables
- 32573765 - Duplicate records exist in SM views
- 9 Change Log