Epic uses Chronicles for most operational reports. Operational reports must reflect current activity, and Chronicles is the real-time transactional database, so it is the appropriate source. Reporting Workbench searches Chronicles directly and delivers its results within Hyperspace, which makes it the usual tool for these reports. The second option is correct. Caboodle and the Clarity data warehouse are populated by scheduled extracts and reflect data that is typically a day old, so they are suited to analytical reporting. SlicerDicer reads from Caboodle and is therefore also not a source for real-time operational lists. Operational reports are also designed to be small and focused so that they do not burden the operational system, which must remain responsive for clinical users. A report that needs to process large volumes of historical data should be moved to the reporting databases. Analysts should therefore consider the time sensitivity of a request when choosing the source and tool, and should explain the limitations of data latency to stakeholders.
[Reference: Cogito Fundamentals – Reporting Workbench: Systems for Operational Reporting, ===============, ]
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