Skip Headers
Oracle® Device and Drug Adverse Event Data Integration Pack for Siebel Adverse Event Complaint Management and Oracle Argus Safety Implementation Guide
Release 11.1
E26803-01
Home
Book List
Contact Us
Next
PDF
·
Mobi
·
ePub
Contents
List of Figures
Title and Copyright Information
Preface
Audience
Oracle AIA Guides
Additional Resources
Documentation Accessibility
Part I Understanding the Delivered Integration
1
Understanding the Device and Drug Adverse Event: Siebel AECM and Argus Safety PIP
Overview
Key Benefits of the PIP
Participating Applications Overview
Siebel Adverse Event and Complaint Management System
Oracle Argus Safety
Business Process Flow
Description
Logical Data Model Diagram
Solution Assumptions and Constraints
2
Understanding the Synchronization of Siebel AECM Product Issue with Oracle Argus Safety System Case
Overview
Description
Functional Process Flow
Flow Diagram
Description
Participating Siebel AECM Interfaces
Participating Oracle Argus Safety Interfaces
Industry AIA Components
Integration Services
Part II Implementing the Delivered Integration
3
Implementing the Device and Drug Adverse Event: Siebel AECM and Argus Safety PIP
Prerequisites
Data Requirements
Setting up Participating Applications
Setting up Oracle Argus Safety
Setting up Siebel AECM
Siebel AECM to Oracle Argus Safety Field Mapping
Configuration Properties for the Device and Drug Adverse Event: Siebel AECM and Argus Safety PIP
Updating Server Information for Siebel AECM and Oracle Argus Safety
Identifying Cross-References
Working with Domain Value Maps
Handling Errors
Using the Message Resubmission Utility
Extending the Device and Drug Adverse Event: Siebel AECM and Argus Safety PIP
Configuring Multiple Siebel AECM Servers to a Single Instance of SOA Server
Monitoring Instances on SOA Server