1. Caboodle Dictio- Basic metadata for tables. Find Descriptions of tables and
nary columns available in data model. Identify tables that can
be linked together.
2. Caboodle Dictio- In depth view of Caboodle ETL packages and data lin-
nary Editor eage. Shows Clarity tables data that extracted from when
populating tables, which ETL packages are used by Ca-
boodle tables and dependencies amongst the tables in
Caboodle.
3. Caboodle Execu- Where Caboodle administrators can create, edit, run and
tions monitor executions. Can be used to schedule recurring
executions.
4. Caboodle Logs the different types of issues that can occur during the
Workqueues ETL process that require manual intervention to resolve.
5. Caboodle config- modify settings, perform customizations such as adding
urations attributes to the data model and view reports related to
Caboodle configuration and operation.
6. Caboodle BI De- write Caboodle reports and should have access to the
velopers Caboodle Dictionary on the Console. Dictionary provides
table descriptions, data lineage for tables and columns
and foreign key information. BI Developers should be fa-
miliar with Caboodles dimensional data model and at least
one area of healthcare reportings such as revenue or
clinical reporting.
7. Caboodle Admin- have access to all activities on the Caboodle Console. Ad-
istrators ministrators monitor executions, troubleshoot work queue
errors and establish system level configurations.
8. Caboodle ETL create custom EPIC and n on Epic content for extrac-
Developers tion into the data warehouse, document their work in the
dictionary editor and test their work using the ETL tools
available in the console. Custom development notes and
documentation relevant to report writers will be visible in
the dictionary.
1/7
, CDW110v Caboodle Data Model Fundamentals Exam Test with Answers
9. Why use Caboo- Accessibility, Efficiency and fewer tables and simpler joins.
dle
10. SSIS package SQL Server Integration packages : Data is extracted from
source systems (Clarity) transformed in the staging data-
base and presented for users in the reporting database.
11. DMCs Data Model Components
12. Data Model Com- collection of metadata tables that support the ETL process
penents and reporting views stored in the FullAccess schema.
13. DMC type and Each DMC gets a type and suffix. Dim for dimensions,
suffixes Fact for facts, Bridge for bridges, Datamart for data marts,
AttributeValueDim for EAV tables, X for custom tables
14. Caboodle Star where one central fact table will join to many associated
Schema lookup or dimension tables.
15. Dimensional This structure intentionally makes some compromises to
Data Model the normalized data model used by Clarity in order to
facilitate report writing. The trade off is that it requires more
complicated ETL process to maintain.
16. Caboodle con-
sists of a report-
ing database and
a staging data-
base
17. dbo Staging database: import tables and mapping tables live
here. Used by administrators for moving data into Caboo-
dle. Reporting Database: dbo schema stores reporting
data and acts as the data source for SlicerDicer. Caboodle
Dictionary reflects the contents of the dbo schema
18. EPIC Staging Database: Epic schema on the staging database
contains the _IdLookup tables, which map source IDs to
system-generated Caboodle primary keys in the reporting
database. Reporting Database: Prior to Epic 2018 this
2/7