SlicerDicer is intended for exploration of data within a single data model, and it does not support constructing complex joins that connect Epic and non-Epic databases. That kind of requirement is handled with SQL against Clarity or Caboodle, where an analyst can join tables from different sources, or with an ETL that brings external data into the warehouse. The second option therefore describes what SlicerDicer is not used for. The other options are standard functions. SlicerDicer can display results as bar and pie charts, among other visualizations, so the first option describes a typical use. Grouping patients by provider is achieved by adding a slice, and filtering by demographics such as age, sex or race is accomplished with criteria and filters. Recognizing the limit matters when a stakeholder request is evaluated. If the question involves a single Epic data model and can be framed in terms of a population, measure and slices, SlicerDicer is efficient. If it requires custom joins, calculated logic beyond the model or data from outside Epic, the analyst should use a more flexible tool and expect a longer development effort.
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