CDW110 Questions with verified answers
CHAPTER 1-Briefly define the roles of the Caboodle report writer, administrator,
and developer. Ans✓✓✓ · The Caboodle report writer queries data that already
exists in the database. They use their knowledge of the tools and the source
database(s) to conduct research into the necessary data points required for a
given report.
· The Caboodle administrator uses the Caboodle Console to manage and monitor
the ETL process. They troubleshoot ETL errors and handle configuration steps for
the database.
· The Caboodle developer designs custom DMCs (Data Model Components) and
writes SSIS packages to bring additional data into the warehouse. This may be
additional Epic data from Clarity or non‐Epic data from 3rd party sources.
CHAPTER 1-Caboodle Console Ans✓✓✓ The Caboodle Console is a web
application housed on the Caboodle server. It includes the following:
Dictionary
Dictionary Editor
Executions
Work Queue
Configuration
CHAPTER 1-Data Lineage Ans✓✓✓ Generally, data lineage refers to the process
of identifying the source of a specific piece of information. In Caboodle, data
lineage is defined at the package level.
,CHAPTER 1-Data Warehouse Ans✓✓✓ In a data warehouse, multiple sources
may load data pertaining to a single entity. This means that more than one
package may populate a given row in a Caboodle table. As a result, there may be
multiple business key values associated with a single entity in a Caboodle table.
CHAPTER 1-Dbo Schema Ans✓✓✓ STAGING DATABASE
Import tables and Mapping tables live here. This is
primarily used by administrators for moving data into Caboodle.
REPORTING DATABASE
The dbo schema stores reporting data and acts as the
data source for SlicerDicer. The Caboodle Dictionary reflects the contents of the
dbo schema.
CHAPTER 1-DMC Ans✓✓✓ DATA MODEL COMPONENT
No table in Caboodle "stands alone." Each is considered part of a Data Model
Component, which refers to the collection of metadata tables that support the
ETL process and reporting views stored in the FullAccess schema.
Each DMC gets a type. Strict table naming conventions are followed in Caboodle,
so that a table's suffix provides information about its structure and purpose.
These suffixes are:
· Dim for dimensions (e.g. PatientDim)
· Fact for facts (e.g. EncounterFact)
· Bridge for bridges (e.g. DiagnosisBridge)
· DataMart for data marts (e.g. HospitalReadmissionDataMart)
· AttributeValueDim for EAV tables (e.g. PatientAttributeValueDim)
, · X for custom tables (e.g. CustomFactX)
CHAPTER 1-ETL Ans✓✓✓ Extract, Transform, Load
CHAPTER 1-FullAccess Schema Ans✓✓✓ STAGING DATABASE
The FullAccess schema does not exist on the Staging database.
REPORTING DATABASE
The FullAccess schema houses views that simplify reporting. FullAccess should be
your default schema when reporting.
CHAPTER 1-How does Epic data flow into Caboodle Ans✓✓✓ Epic data moves
between several databases before it gets to Caboodle.
CHRONICLES flows into CLARITY via ETL. After transformation, the data is stored in
a relational database on a separate server. Even though the structure of the
Chronicles and Clarity databases differ significantly, the ETL process preserves the
relationships mapped in Chronicles.
CLARITY flows into Caboodle data is extracted
from Clarity, transformed in the staging database, and presented for users in the
reporting database. This movement of data is realized via a set of SQL Server
Integration Services (SSIS) packages.
CHAPTER 1-How does Non-Epic data flow into Caboodle Ans✓✓✓ The Caboodle
developer designs custom DMCs (Data Model Components) and writes SSIS
CHAPTER 1-Briefly define the roles of the Caboodle report writer, administrator,
and developer. Ans✓✓✓ · The Caboodle report writer queries data that already
exists in the database. They use their knowledge of the tools and the source
database(s) to conduct research into the necessary data points required for a
given report.
· The Caboodle administrator uses the Caboodle Console to manage and monitor
the ETL process. They troubleshoot ETL errors and handle configuration steps for
the database.
· The Caboodle developer designs custom DMCs (Data Model Components) and
writes SSIS packages to bring additional data into the warehouse. This may be
additional Epic data from Clarity or non‐Epic data from 3rd party sources.
CHAPTER 1-Caboodle Console Ans✓✓✓ The Caboodle Console is a web
application housed on the Caboodle server. It includes the following:
Dictionary
Dictionary Editor
Executions
Work Queue
Configuration
CHAPTER 1-Data Lineage Ans✓✓✓ Generally, data lineage refers to the process
of identifying the source of a specific piece of information. In Caboodle, data
lineage is defined at the package level.
,CHAPTER 1-Data Warehouse Ans✓✓✓ In a data warehouse, multiple sources
may load data pertaining to a single entity. This means that more than one
package may populate a given row in a Caboodle table. As a result, there may be
multiple business key values associated with a single entity in a Caboodle table.
CHAPTER 1-Dbo Schema Ans✓✓✓ STAGING DATABASE
Import tables and Mapping tables live here. This is
primarily used by administrators for moving data into Caboodle.
REPORTING DATABASE
The dbo schema stores reporting data and acts as the
data source for SlicerDicer. The Caboodle Dictionary reflects the contents of the
dbo schema.
CHAPTER 1-DMC Ans✓✓✓ DATA MODEL COMPONENT
No table in Caboodle "stands alone." Each is considered part of a Data Model
Component, which refers to the collection of metadata tables that support the
ETL process and reporting views stored in the FullAccess schema.
Each DMC gets a type. Strict table naming conventions are followed in Caboodle,
so that a table's suffix provides information about its structure and purpose.
These suffixes are:
· Dim for dimensions (e.g. PatientDim)
· Fact for facts (e.g. EncounterFact)
· Bridge for bridges (e.g. DiagnosisBridge)
· DataMart for data marts (e.g. HospitalReadmissionDataMart)
· AttributeValueDim for EAV tables (e.g. PatientAttributeValueDim)
, · X for custom tables (e.g. CustomFactX)
CHAPTER 1-ETL Ans✓✓✓ Extract, Transform, Load
CHAPTER 1-FullAccess Schema Ans✓✓✓ STAGING DATABASE
The FullAccess schema does not exist on the Staging database.
REPORTING DATABASE
The FullAccess schema houses views that simplify reporting. FullAccess should be
your default schema when reporting.
CHAPTER 1-How does Epic data flow into Caboodle Ans✓✓✓ Epic data moves
between several databases before it gets to Caboodle.
CHRONICLES flows into CLARITY via ETL. After transformation, the data is stored in
a relational database on a separate server. Even though the structure of the
Chronicles and Clarity databases differ significantly, the ETL process preserves the
relationships mapped in Chronicles.
CLARITY flows into Caboodle data is extracted
from Clarity, transformed in the staging database, and presented for users in the
reporting database. This movement of data is realized via a set of SQL Server
Integration Services (SSIS) packages.
CHAPTER 1-How does Non-Epic data flow into Caboodle Ans✓✓✓ The Caboodle
developer designs custom DMCs (Data Model Components) and writes SSIS
