Skip Headers
Oracle® Health Sciences Clinical Development Analytics Release Content Document
Release 2.2 for Standard Configuration

E26020-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

Preface

This Release Content Document helps you assess the business benefits of implementing Oracle Health Sciences Clinical Development Analytics (OHSCDA) Release 2.2. For more technical information, you can refer to Release Notes of a specific release.

Purpose

The Release Content Document (RCD) communicates information about new or changed functionality in the specified release of OHSCDA. Existing functionality from prior releases is not described.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documents

The following OHSCDA Release 2.2 for Standard Configuration user documentation is available:

Conventions

The following text conventions are used in this document:

Convention Meaning

boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.
italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.
monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.
[Attribute Name] Square brackets around an attribute name indicate that the attribute is unsourced. This implies that it is present in the warehouse and CDA's OBIEE Repository, but CDA's ETL does not extract it from any source. These attributes are provided to simplify adding them to your CDA instance if you do have a source for them.