COG170
Dashboard - ANSfirst thing users see when they log into EPIC. Centralize content from around
Hyperspace.
Report Listing Component - ANSin the left column of the dashboard.
Personalization - ANSWhen an end user selects a source dashboard from the Analytics
CAtalog, a personalized copy is created just for them. End user personalized copies of these
source dashboards & components are considered personalization records. P. 2-23
Dashboard Editor - ANSUsed to create & edit source dashboard records.
Easiest way to select Dashboard editor:
1) Dashboard Options menu in upper right corner of the dashboard
2) via chart search, editing a dashboard from the Analytics Catalog
3) editing a dashboard from the Proxy Dashboard prompt
Component Editor Forms - ANS1) Basic Information
2) Display
3) Data Source
4) Output Format
5) Access
Activity Descriptor of an Active Hyperspace Activity - ANSUse the about Hyperspace information
window in the activity you are currently accessing. P. 2-21
The Report Listing Component - ANSLists Reports that are ready to run. When the report is
finished running, the status changes to "Ready to View." Then click View.
After clicking View, you are taken to the Results of the Report.
To return to the Dashboard, close the Reports workspace. P. 2-11
Link Component - ANSRadar link components with Hyperspace activity links can save clicks by
no longer requiring you to locate activities from within the Epic button. P. 2-11
Types of Components available in Radar - ANS1) Report Listing Component
2) Link Component
3) Graph & Table Component
What controls the population of your component record? - ANSthe Data Source P. 2-17
,What happens when a user creates or launches a personalized record? - ANSReconciliation. P.
2-24
Reconciliation checks the ass source dashboard & components underlying the personalization
to determine what has changed. If the source record's change does not conflict with the
personalized settings, the change in the source is reflected in the personalizatin and a message
is displayed to the user saying what was updated.
If the source's change conflicts w/ the personalized settings, the personalized settings are used
instead. --> No end-user settings are lost during this process.
What will happen if a component or dashboard is not marked ready for use? - ANSUsers will not
have access to the component/dashboard if Ready for Use is not checked. P. 2-18
Data Model - ANS
The many data points that can be used as criteria, slices, measures, and display columns. -
ANSThe many data points that can be used as criteria, slices, measures, and display columns.
Population - ANSThe population of the data model. Starts with a base & is refined using criteria.
The available criteria come from the list of filters. P. 3-14
Base - ANSUsed to define the population in your SlicerDicer session. P. 3-14 - 3-15
Ex: Patients data model. Users can narrow down the population to only include patients with
specific relationships to them.
Criteria - ANSOften times the 1st pieces of the population that a user modifies. They refine the
population to only the desired records. P. 3-16
Measures - ANSDetermine what function aggregates the data.
Ex: # at the top of the bar in a vertical bar graph. P. 3-18
Any time a user wants to see their data expressed as: A FUNCTION of a FILTER they can
accomplish this by adding a measure.
Slices - ANSDivides up the population into the appropriate buckets so you can view & compare
populations quickly.
Users select slices from the lsit of filters. After selecting a filter to slice on, they can either:
1) specify what values for the filter should each get their own slice
, 2) Grab the top 10
3) Grab the bottom 10
4) Grab the top or bottom N records (where N si user specified) p. 3-17
Exclusive Criteria - ANSA population for whom the criterion is false. P. 3-16
Database - ANSAn organized collection of data. P. 4-4
AKA: Data sources
The purpose of the database defines its structure.
All of Epic's data is stored in either Chronicles, Clarity, or Caboodle.
Data Lineage - ANSThe origin of data as it flows from 1 database to another. Epic data lineage
starts with Chronicles.
1) Epic users enter data into Chronicles through Hyperspace
2) Clarity ETL transfers data from Chronicles to Clarity
3) Caboodle ETL transfers data from Clarity to Caboodle the same night as Clarity ETL. P. 4-4
Chronicles - ANSDesigned to be efficient for daily healthcare operations. Tree-like structure. P.
4-4
Master File - ANSChronicles is first divided into master files. These contain information about a
broad subject. Ex: the patient master file(INI) contains all patients' medical records in Epic. P.
4-4
Record - ANSContain information about individual entities within a master file. P. 4-4
Contact - ANSContain information about points in time for a record.
Ex: the patient master file uses contacts for patient encounters. P. 4-4
Item - ANSIndividual data points within a record or contact. P. 4-5
Clarity - ANSStores data in the tables that look like 2D grids with rows & columns. Each row
represents an entity in the table, its columns each holds a piece of information about the row. P.
4-5
Row: Entity
Column: Attribute
Dashboard - ANSfirst thing users see when they log into EPIC. Centralize content from around
Hyperspace.
Report Listing Component - ANSin the left column of the dashboard.
Personalization - ANSWhen an end user selects a source dashboard from the Analytics
CAtalog, a personalized copy is created just for them. End user personalized copies of these
source dashboards & components are considered personalization records. P. 2-23
Dashboard Editor - ANSUsed to create & edit source dashboard records.
Easiest way to select Dashboard editor:
1) Dashboard Options menu in upper right corner of the dashboard
2) via chart search, editing a dashboard from the Analytics Catalog
3) editing a dashboard from the Proxy Dashboard prompt
Component Editor Forms - ANS1) Basic Information
2) Display
3) Data Source
4) Output Format
5) Access
Activity Descriptor of an Active Hyperspace Activity - ANSUse the about Hyperspace information
window in the activity you are currently accessing. P. 2-21
The Report Listing Component - ANSLists Reports that are ready to run. When the report is
finished running, the status changes to "Ready to View." Then click View.
After clicking View, you are taken to the Results of the Report.
To return to the Dashboard, close the Reports workspace. P. 2-11
Link Component - ANSRadar link components with Hyperspace activity links can save clicks by
no longer requiring you to locate activities from within the Epic button. P. 2-11
Types of Components available in Radar - ANS1) Report Listing Component
2) Link Component
3) Graph & Table Component
What controls the population of your component record? - ANSthe Data Source P. 2-17
,What happens when a user creates or launches a personalized record? - ANSReconciliation. P.
2-24
Reconciliation checks the ass source dashboard & components underlying the personalization
to determine what has changed. If the source record's change does not conflict with the
personalized settings, the change in the source is reflected in the personalizatin and a message
is displayed to the user saying what was updated.
If the source's change conflicts w/ the personalized settings, the personalized settings are used
instead. --> No end-user settings are lost during this process.
What will happen if a component or dashboard is not marked ready for use? - ANSUsers will not
have access to the component/dashboard if Ready for Use is not checked. P. 2-18
Data Model - ANS
The many data points that can be used as criteria, slices, measures, and display columns. -
ANSThe many data points that can be used as criteria, slices, measures, and display columns.
Population - ANSThe population of the data model. Starts with a base & is refined using criteria.
The available criteria come from the list of filters. P. 3-14
Base - ANSUsed to define the population in your SlicerDicer session. P. 3-14 - 3-15
Ex: Patients data model. Users can narrow down the population to only include patients with
specific relationships to them.
Criteria - ANSOften times the 1st pieces of the population that a user modifies. They refine the
population to only the desired records. P. 3-16
Measures - ANSDetermine what function aggregates the data.
Ex: # at the top of the bar in a vertical bar graph. P. 3-18
Any time a user wants to see their data expressed as: A FUNCTION of a FILTER they can
accomplish this by adding a measure.
Slices - ANSDivides up the population into the appropriate buckets so you can view & compare
populations quickly.
Users select slices from the lsit of filters. After selecting a filter to slice on, they can either:
1) specify what values for the filter should each get their own slice
, 2) Grab the top 10
3) Grab the bottom 10
4) Grab the top or bottom N records (where N si user specified) p. 3-17
Exclusive Criteria - ANSA population for whom the criterion is false. P. 3-16
Database - ANSAn organized collection of data. P. 4-4
AKA: Data sources
The purpose of the database defines its structure.
All of Epic's data is stored in either Chronicles, Clarity, or Caboodle.
Data Lineage - ANSThe origin of data as it flows from 1 database to another. Epic data lineage
starts with Chronicles.
1) Epic users enter data into Chronicles through Hyperspace
2) Clarity ETL transfers data from Chronicles to Clarity
3) Caboodle ETL transfers data from Clarity to Caboodle the same night as Clarity ETL. P. 4-4
Chronicles - ANSDesigned to be efficient for daily healthcare operations. Tree-like structure. P.
4-4
Master File - ANSChronicles is first divided into master files. These contain information about a
broad subject. Ex: the patient master file(INI) contains all patients' medical records in Epic. P.
4-4
Record - ANSContain information about individual entities within a master file. P. 4-4
Contact - ANSContain information about points in time for a record.
Ex: the patient master file uses contacts for patient encounters. P. 4-4
Item - ANSIndividual data points within a record or contact. P. 4-5
Clarity - ANSStores data in the tables that look like 2D grids with rows & columns. Each row
represents an entity in the table, its columns each holds a piece of information about the row. P.
4-5
Row: Entity
Column: Attribute
