Permissions: Users must have the System Admin privilege to create and manage Data Stores.
Data Stores provide logical methods for storing data within elluminate and are organized into three types: Staging Areas, Data Marts, and Global Data Stores. Each type serves a specific purpose.
- Staging Areas are where source data are imported and stored.
- Data Marts contain mapped data ready for reporting and analysis.
- Global Data Stores hold data that can be used across multiple studies.
Staging Areas and Data Marts operate at the study level, meaning each study's data is stored separately. For example, nearly all studies use the Clinical data store as their Staging Area but can access only the records imported for their specific study. The same holds true for the default Reporting data store for Data Marts, which contains mapped, study-specific data for use in analytics and reporting tasks.
This structure keeps data securely siloed per study, while enabling efficient workflows from initial ingestion to final reporting.
When working within different elluminate modules, there are options to select the staging area or data mart to import into or pull data from.
Modules where a data store can be selected include:
- Importer
- Exporter
- Data Quality
- Validator
- Metadata
- Mapper
Staging Areas
A Staging Area is where the source, or raw, data is imported. By default, the Clinical and Operational Staging Areas are available. Clinical is set up as the default staging area. Additional staging areas can be created to accommodate data needs. For example, lab data may be imported into its own staging area, such as a Labs staging area. When importing lab data, specify the Labs staging area.
A user must have the System Configure privilege to create staging areas or change the default staging area.
If data is imported from the Rave ODM Adapter, an ODM_Stage staging area is created automatically. ODM_Stage is the required name for the ODM staging area and should not be changed. Imports of ODM data to a data store other than ODM_Stage will fail.
Note: When working in an elluminate module that requires selection of a staging area, only staging areas that contain data display.
Data Marts
A Data Mart is where data resides after mapping has taken place and is ready for reporting and analysis. By default, the Reporting and SDTM Data Marts are available. Reporting is set up as the default data mart. Additional data marts may be created to meet study needs.
When working in Analytics Visualizations, data is always pulled from the Reporting Data Mart. If no data exists in the Reporting Data Mart, visualizations are not populated.
A user must have the System Configure privilege to create data marts or change the default data mart.
When data is mapped from the ODM_Stage staging area, an ODM_Mapped data mart is created.
Note: When working in an elluminate module that requires the selection of a data mart, only data marts that contain data display.
Who can use Data Stores?
By default, users with access to a study have access to all data stores for that study. During user setup in elluminate, access to specific Staging Areas or Data Marts can be restricted.
Global Data Stores
To facilitate aggregating and managing data from multiple studies or programs, elluminate provides the ability to create a Global Data Store. Similar to a regular study, you can configure the Importer, Exporter, Tasks and use the Mapper on data in a Global Data Store.
A Global Data Store can be associated with a compound, a therapeutic area, and / or a program which defines which studies these data stores will be available in (for the Mapper).
For example, if the data store is associated with the Oncology TA, when using the Mapper in an oncology study, the domains from this global data store will be available to be mapped. If no Therapeutic Area, program, or compound is associated with the global data store, domains in the global data store will be available to all studies.