CDW110v Caboodle Data Model Fundamentals

CDW110v Caboodle Data Model Fundamentals 1. Caboodle Dictionary: Basic metadata for tables. Find Descriptions of tables and columns available in data model. Identify tables that can be linked together. 2. Caboodle Dictionary Editor: In depth view of Caboodle ETL packages and data lineage. Shows Clarity tables data that extracted from when populating tables, which ETL packages are used by Caboodle tables and dependencies amongst the tables in Caboodle. 3. Caboodle Executions: Where Caboodle administrators can create, edit, run and monitor executions. Can be used to schedule recurring executions. 4. Caboodle Workqueues: Logs the different types of issues that can occur during the ETL process that require manual intervention to resolve. 5. Caboodle configurations: modify settings, perform customizations such as adding attributes to the data model and view reports related to Caboodle configu- ration and operation. 6. Caboodle BI Developers: write Caboodle reports and should have access to the Caboodle Dictionary on the Console. Dictionary provides table descriptions, data lineage for tables and columns and foreign key information. BI Developers should be familiar with Caboodles dimensional data model and at least one area of healthcare reportings such as revenue or clinical reporting. 7. Caboodle Administrators: have access to all activities on the Caboodle Con- sole. Administrators monitor executions, troubleshoot work queue errors and es- tablish system level configurations. 8. Caboodle ETL Developers: create custom EPIC and n on Epic content for extraction 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. 9. Why use Caboodle: Accessibility, Efficiency and fewer tables and simpler joins. 10. SSIS package: SQL Server Integration packages: Data is extracted from source systems (Clarity) transformed in the staging database and presented for users in the reporting database. 11. DMCs: Data Model Components 12. Data Model Components: collection of metadata tables that support the ETL process and reporting views stored in the Full Access schema. 13. DMC type and suffixes: Each DMC gets a type and suffix. Dim for dimensions, Fact for facts, Bridge for bridges, Datamart for data marts, AttributeValueDim for EAV tables, X for custom tables 14. Caboodle Star Schema: where one central fact table will join to many associ- ated lookup or dimension tables. 15. Dimensional Data Model: This structure intentionally makes some compro- mises to 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 consists of a reporting database and a staging database: 17. Dbo: Staging database: import tables and mapping tables live here. Used by administrators for moving data into Caboodle. Reporting Database: dbo schema stores reporting data and acts as the data source for SlicerDicer. Caboodle Dictionary reflects the contents of the dbo schema