A Clarity-based report that returned valid data for years has recently returned corrupted data. You have verified that the Chronicles data is valid. Which role would most likely be responsible for addressing the issue?
Epic ' s analytics architecture is layered: Chronicles holds operational data, Clarity is the relational reporting database that is populated from Chronicles by a nightly extract, transform and load process, and Caboodle is the enterprise data warehouse built from Clarity. Responsibility follows the layer. The stem eliminates Chronicles as the source of the problem by stating that the Chronicles data has been verified as valid, which implies the fault lies downstream in the process that moves and stores the data in Clarity. Maintaining that extract, monitoring its jobs and resolving failures or corrupted loads is the work of the Clarity administrator, who uses the Clarity Console for scheduling and monitoring. A Chronicles administrator supports the operational database and would not own a reporting extract. A Caboodle developer builds and maintains warehouse content and ETLs from Clarity into Caboodle, so the role is relevant only when the report reads from Caboodle. A business intelligence developer authors reports and dashboards, but would investigate data quality only to the point of identifying the failing layer and escalating. The Clarity administrator is therefore the most likely owner.
[Reference: Cogito Fundamentals – Epic Data Architecture: Chronicles, Clarity and Caboodle; Roles, ===============, ]
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit