THE DEFINITIVE COG170 STUDY
GUIDE
200 Essential Questions, Answers, and
Rationales for the Epic Cogito
Fundamentals Exam
SECTION 1: DASHBOARDS AND COMPONENTS (Q1–Q40)
Q1. What is a dashboard in Epic's Cogito ecosystem?
Answer: A dashboard centralizes content from around Hyperspace,
the graphical user interface which allows users to enter, access, and
interact with Epic data.
Rationale: Dashboards serve as the hub of reporting and analytics in
Epic, consolidating data from all corners of a healthcare system. They
are often the first thing users see when they log into Epic.
Q2. What is a component in the context of Radar dashboards?
Answer: Each section of content on a dashboard is a component.
Components built by administrators are source records.
Rationale: Components are the building blocks of dashboards. They
can be graphs, tables, links, message boards, or other content types
that display specific data.
,Q3. Which of the following is NOT a form available in the Dashboard
Editor?
A. Resource Settings
B. Content
C. Personalization
D. Access
Answer: C. Personalization
Rationale: The six forms in the Dashboard Editor are Basic
Information, Layout, Content, Resource Settings, Parameters, and
Access. Personalization is not a form; it refers to end-user copies of
source records.
Q4. What two dashboard settings control whether a dashboard is
available for viewing, assuming the user has the appropriate role?
Answer: The "Ready for use" and "Enabled for user selection" check
boxes.
Rationale: Both settings must be enabled for a dashboard to appear
to users. "Ready for use" marks the dashboard as complete, while
"Enabled for user selection" makes it available in the Analytics Catalog.
Q5. How can you change the DISPLAY title of a component?
Answer: Using the Component Editor, update the Display title field on
the Display form. You can also change the display title through
personalization.
Rationale: The Display title is what users see on the dashboard. It can
be modified by administrators via the Component Editor or by end
users through personalization.
Q6. What is a personalization record?
, Answer: When an end user selects a source dashboard from the
Analytics Catalog, a personalized copy is created just for them. End-
user personalized copies of source dashboards and components are
considered personalization records.
Rationale: Personalization allows users to customize their dashboards
without affecting the source records that other users see.
Q7. True or False: Components require a defined Display title on the
Display form.
Answer: True
Rationale: The Display title is a required field for components.
Without it, the component cannot be properly displayed on a
dashboard.
Q8. What are the seven types of component records in Radar?
Answer: Graph, Link, Message Board, Native HTML, Report Listing,
Table, Tranche (not currently used).
Rationale: Each component type serves a different purpose—graphs
visualize data, links provide navigation, message boards display
messages, tables show structured data, etc.
Q9. A component has been built but does not appear on a specific
dashboard. What could be the reasons? (Select all that apply)
A. The component is not set as ready for use.
B. The component is not listed on the Content form of the dashboard.
C. The component and the dashboard do not share any report groups.
D. The component has not been marked as enabled for user selection.
Answer: A and B
Rationale: For a component to appear on a dashboard, it must be
marked as ready for use AND be listed on the Content form of that
, dashboard. Report groups and user selection settings are not required
for appearance.
Q10. What key can you use on any record select field to pull the most
recent record accessed by your user?
Answer: The = key
Rationale: Using the = key on the Content form of the Dashboard
Editor quickly pulls in the component you just built or the most
recently accessed record.
Q11. What is a Link Component?
Answer: A list of links to Hyperspace activities, reports, or external
URLs.
Rationale: Link components provide navigation from dashboards to
other parts of the system, improving workflow efficiency.
Q12. How could you find out what options are available for dividing
up a pie chart, choosing categories for a bar graph, or setting up levels
of a grouped summary?
Answer: By exploring the component's configuration settings in the
Component Editor, specifically the options for grouping and
categorization.
Rationale: The Component Editor provides various configuration
options for visualizing data, including grouping, categorization, and
summarization settings.
Q13. What do you need to do to build a link to a Hyperspace activity?
Answer: You need to identify the activity descriptor, which is the
unique identifier of that activity.
GUIDE
200 Essential Questions, Answers, and
Rationales for the Epic Cogito
Fundamentals Exam
SECTION 1: DASHBOARDS AND COMPONENTS (Q1–Q40)
Q1. What is a dashboard in Epic's Cogito ecosystem?
Answer: A dashboard centralizes content from around Hyperspace,
the graphical user interface which allows users to enter, access, and
interact with Epic data.
Rationale: Dashboards serve as the hub of reporting and analytics in
Epic, consolidating data from all corners of a healthcare system. They
are often the first thing users see when they log into Epic.
Q2. What is a component in the context of Radar dashboards?
Answer: Each section of content on a dashboard is a component.
Components built by administrators are source records.
Rationale: Components are the building blocks of dashboards. They
can be graphs, tables, links, message boards, or other content types
that display specific data.
,Q3. Which of the following is NOT a form available in the Dashboard
Editor?
A. Resource Settings
B. Content
C. Personalization
D. Access
Answer: C. Personalization
Rationale: The six forms in the Dashboard Editor are Basic
Information, Layout, Content, Resource Settings, Parameters, and
Access. Personalization is not a form; it refers to end-user copies of
source records.
Q4. What two dashboard settings control whether a dashboard is
available for viewing, assuming the user has the appropriate role?
Answer: The "Ready for use" and "Enabled for user selection" check
boxes.
Rationale: Both settings must be enabled for a dashboard to appear
to users. "Ready for use" marks the dashboard as complete, while
"Enabled for user selection" makes it available in the Analytics Catalog.
Q5. How can you change the DISPLAY title of a component?
Answer: Using the Component Editor, update the Display title field on
the Display form. You can also change the display title through
personalization.
Rationale: The Display title is what users see on the dashboard. It can
be modified by administrators via the Component Editor or by end
users through personalization.
Q6. What is a personalization record?
, Answer: When an end user selects a source dashboard from the
Analytics Catalog, a personalized copy is created just for them. End-
user personalized copies of source dashboards and components are
considered personalization records.
Rationale: Personalization allows users to customize their dashboards
without affecting the source records that other users see.
Q7. True or False: Components require a defined Display title on the
Display form.
Answer: True
Rationale: The Display title is a required field for components.
Without it, the component cannot be properly displayed on a
dashboard.
Q8. What are the seven types of component records in Radar?
Answer: Graph, Link, Message Board, Native HTML, Report Listing,
Table, Tranche (not currently used).
Rationale: Each component type serves a different purpose—graphs
visualize data, links provide navigation, message boards display
messages, tables show structured data, etc.
Q9. A component has been built but does not appear on a specific
dashboard. What could be the reasons? (Select all that apply)
A. The component is not set as ready for use.
B. The component is not listed on the Content form of the dashboard.
C. The component and the dashboard do not share any report groups.
D. The component has not been marked as enabled for user selection.
Answer: A and B
Rationale: For a component to appear on a dashboard, it must be
marked as ready for use AND be listed on the Content form of that
, dashboard. Report groups and user selection settings are not required
for appearance.
Q10. What key can you use on any record select field to pull the most
recent record accessed by your user?
Answer: The = key
Rationale: Using the = key on the Content form of the Dashboard
Editor quickly pulls in the component you just built or the most
recently accessed record.
Q11. What is a Link Component?
Answer: A list of links to Hyperspace activities, reports, or external
URLs.
Rationale: Link components provide navigation from dashboards to
other parts of the system, improving workflow efficiency.
Q12. How could you find out what options are available for dividing
up a pie chart, choosing categories for a bar graph, or setting up levels
of a grouped summary?
Answer: By exploring the component's configuration settings in the
Component Editor, specifically the options for grouping and
categorization.
Rationale: The Component Editor provides various configuration
options for visualizing data, including grouping, categorization, and
summarization settings.
Q13. What do you need to do to build a link to a Hyperspace activity?
Answer: You need to identify the activity descriptor, which is the
unique identifier of that activity.
