About Data Extract

Oracle Clinical's Data Extract subsystem is a set of facilities to present patient and clinical study data that meets the demands of external applications related to statistical analysis and reporting. Data is presented for external access via standard and custom views (that is, database views) created in study access accounts.

Oracle Clinical stores data in tables that are normalized and generic, in that the underlying table structure of the data is the same from one study to another.

This chapter describes those data extract features and processes that fall under the heading "Conducting a Study". For data extract tasks performed in the Global Library and Definition subsystems, see Data Extract in the manual Oracle Clinical Creating a Study. See the Utilities chapter of the Oracle Clinical Administrator's Guide for information on regenerating and updating views.

Views created before Oracle Clinical V3.1 ("pre-3.1 views") continue to be supported, although you cannot have pre-3.1 views in the same study as views created in V3.1 and later. As of V3.1, views are created by the View Builder, which is a toolkit that provides the means to:

• Customize and interactively view default, DCM-based views.
• Create questions derived at the time of data extract.
• Customize how views are created by, for example:
  • controlling the view mode
  • controlling the view granted for view access
  • controlling the default attributes of the view's questions
• Create cross-study views by program, project, or user-defined study set.

View data can be transferred into database tables for better system performance during user analysis, reporting, and browsing operations. You also can create in-study unions within a study; these union all the data extract views that use the same key and view templates across the study.