Docsity
Docsity

Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity


Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan


Guidelines and tips
Guidelines and tips

Epic Training COG170 Cogito Fundamentals exam with verified answers, Exams of Nursing

Epic Training COG170 Cogito Fundamentals exam with verified answers

Typology: Exams

2024/2025

Available from 01/23/2025

smart-scores
smart-scores 🇺🇸

5

(2)

7K documents

1 / 107

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Radar |dashboards |- |correct |answer |are |often |the |first |thing |users |see |when
|they |log |into |Epic |every |day. |Dashboards |are |the |hub |of |reporting |and |analytics
|in |Epic, |and |consolidate |data |from |all |corners |of |your |healthcare |system. |I
Chart |Search. |- |correct |answer |The |easiest |way |to |access |an |activity |in
|Hyperspace
Analytics |Catalog |- |correct |answer |is |a |central |repository |of |all |reporting
|content.
A |component |- |correct |answer |is |a |single |graph |or |table |or |other |piece |of
|functionality |that |your |users |will |interact |with |on |the |dashboard. |Components
|are |the |building |blocks |of |a |dashboard, |and |are |the |primary |way |you |will |add
|new |content |or |remove |content |from |a |dashboard.
guiding |principles |when |creating |or |editing |Radar |content: |- |correct |answer |-
Any |dashboard |available |to |a |user |must |work |
-Each |component |on |a |dashboard |must |work |
-All |dashboards |should |have |a |defined |target |audience |-Each |user |in |that
|audience |must |have |the |security |to |use |every |component |on |the |dashboard
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff
pf12
pf13
pf14
pf15
pf16
pf17
pf18
pf19
pf1a
pf1b
pf1c
pf1d
pf1e
pf1f
pf20
pf21
pf22
pf23
pf24
pf25
pf26
pf27
pf28
pf29
pf2a
pf2b
pf2c
pf2d
pf2e
pf2f
pf30
pf31
pf32
pf33
pf34
pf35
pf36
pf37
pf38
pf39
pf3a
pf3b
pf3c
pf3d
pf3e
pf3f
pf40
pf41
pf42
pf43
pf44
pf45
pf46
pf47
pf48
pf49
pf4a
pf4b
pf4c
pf4d
pf4e
pf4f
pf50
pf51
pf52
pf53
pf54
pf55
pf56
pf57
pf58
pf59
pf5a
pf5b
pf5c
pf5d
pf5e
pf5f
pf60
pf61
pf62
pf63
pf64

Partial preview of the text

Download Epic Training COG170 Cogito Fundamentals exam with verified answers and more Exams Nursing in PDF only on Docsity!

Radar |dashboards |- |correct |answer |✔are |often |the |first |thing |users |see |when |they |log |into |Epic |every |day. |Dashboards |are |the |hub |of |reporting |and |analytics |in |Epic, |and |consolidate |data |from |all |corners |of |your |healthcare |system. |I

Chart |Search. |- |correct |answer |✔The |easiest |way |to |access |an |activity |in |Hyperspace

Analytics |Catalog |- |correct |answer |✔is |a |central |repository |of |all |reporting |content.

A |component |- |correct |answer |✔is |a |single |graph |or |table |or |other |piece |of |functionality |that |your |users |will |interact |with |on |the |dashboard. |Components |are |the |building |blocks |of |a |dashboard, |and |are |the |primary |way |you |will |add |new |content |or |remove |content |from |a |dashboard.

guiding |principles |when |creating |or |editing |Radar |content: |- |correct |answer |✔- Any |dashboard |available |to |a |user |must |work |

-Each |component |on |a |dashboard |must |work |

-All |dashboards |should |have |a |defined |target |audience |-Each |user |in |that |audience |must |have |the |security |to |use |every |component |on |the |dashboard

The |Dashboard |Editor |has |up |to |six |forms |that |control |the |dashboard's |content

|and |its |metadata: |- |correct |answer |✔-Basic |Information |

-Layout |

-Content |

-Resource |Settings |

-Parameters

-Access

T/F |The |Dashboard |Editor |can |be |used |to |view |the |settings |of |any |dashboard |in |your |system, |but |only | custom‐built |dashboards |can |be |modified. | Epic‐released

|dashboards |will |be | read‐ |only. |- |correct |answer |✔True

Basic |Information |- |correct |answer |✔The |Basic |Information |form |records |the |purpose, |ownership, |and |general |information |of |a |dashboard.

Display |title |- |correct |answer |✔End |users |see |the |display |title |in |the |Analytics |Catalog |and |when |they |view |a |dashboard.

Description |- |correct |answer |✔End |users |may |read |this |description |about |the |dashboard |in |the |Analytics |Catalog.

Owning |application |- |correct |answer |✔The |application |responsible |for |maintaining |this |dashboard.

Layout |- |correct |answer |✔The |Layout |form |controls |the |number |and |position |of |regions |that |present |the |components |in |your |dashboard.

This |must |be |selected |for |any |user, |even |the |dashboard |builder, |to |open |and |view |the |dashboard. |In |addition, |all |components |on |a |dashboard |must |be |marked |as |Ready |for |use |before |the |dashboard |can |be |marked |as |Ready |for

|use. |- |correct |answer |✔Ready |for |use

Select |this |when |you |want |the |dashboard |to |be |available |in |the |Analytics

|Catalog. |- |correct |answer |✔Enabled |for |user

selection

T/F |End |users |cannot |see |your |dashboard |from |the |Analytics |Catalog |until |you |select |both |the |Ready |for |use |and |Enabled |for |user |selection |checkboxes. |-

|correct |answer |✔True

  1. |Save |your |settings |in |the |Dashboard |Editor

The |easiest |way |to |save |your |settings |is |to |navigate |to |another |form |in |the

Dashboard |Editor.

Settings |are |also |saved |when |you |click |Accept |to |close |the |Dashboard

Editor, |but |doing |so |means |it |will |take |longer |to |return |to |this |record |if |you

wish |to |make |further |edits.

  1. |Hard |refresh |your |dashboard.

While |viewing |your |dashboard, |use |the |keyboard |shortcut |of |ALT |+ |= | Mac

users: |Option |+ |Command |+ |= ﴿. |- |correct |answer |✔To |view |a |dashboard |as |you |are |making |changes |to |it, |you |will |need |to:

The |Analytics |Catalog |can |be |used |to |find |which |of |the |following |reporting |resource?a) |Workbench |reports, |b) |saved |SlicerDicer |sessions, |c) |Radar |dashboards, |d) |Dashboard |components, |e) |Workbench |templates, |f) |Epic-

Crystal |reports. |- |correct |answer |✔a) |Workbench |reports, |c) |Radar |dashboards, |d)Dashboard |components, |f) |Epic-Crystal |reports

Assuming |a |user |has |the |appropriate |report |group |to |access |a |dashboard, |what |other |dashboard |settings |control |whether |the |dashboard |is |available |for

|viewing? |- |correct |answer |✔Appropriate |Report |Group; |The |Ready |for |use |and |Enabled |for |user |selection |check |boxes

Every |Report |model |is |a |record |in |which |Master |File? |- |correct |answer |✔HSQ

Which |of |the |following |do |you |need |to |create |a |link |from |a |dashboard |to |a |given |Hyperspaceactivity?

a. |The |activity |descriptor |for |the |activity

b. |The |menu |descriptor |of |the |activity

c. |The |user-facing |name |of |the |activity

d. |The |parent |menu |of |the |activity |record |- |correct |answer |✔The |activity |descriptor |for |the |activity

You |have |built |a |component |record. |Which |of |the |following |could |explain |why |the |component |does |not |appear |on |a |specific |dashboard?

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 |- |correct

|answer |✔a. |The |component |is |not |set |as |ready |for |use

b. |The |component |is |not |listed |on |the |Content |form |of |the |dashboard

Which |of |Epic's |databases |contains |real-time |data?

a. |Chronicles

b. |Clarity

c. |Caboodle |- |correct |answer |✔a) |Chronicles

Which |of |Epic's |databases |are |relational |databases?

a. |Chronicles

b. |Clarity

c. |Caboodle |- |correct |answer |✔b. |Clarity

c. |Caboodle

Do |item |numbers |necessarily |carry |meaning |across |master |files? |- |correct

|answer |✔No, |item |numbers |do |not |necessarily |carry |meaning |across |master |files.

True |or |False. |You |can |use |the |Record |Viewer |to |look |up |the |definition |of |a

|table |in |Clarity. |- |correct |answer |✔False. |Use |the |Record |Viewer |to |view |data |from |a |record |in |Chronicles. |Use |the |Clarity |Dictionary |to |look |up |the |definition |of |a |table |in |Clarity.

What |is |the |difference |between |a |record |and |a |contact? |- |correct |answer |✔A |record |is |a |single |entity. |What |kind |of |thing |depends |on |the |master |file |- |a |record |in |the |patient |master |file |is |a |patient, |a |record |in |the |provider |master |file |is |a |provider, |etc. |

A |contact |represents |a |single |set |of |data |(usually |representing |a |unique |time |period) |on |that |record.

What |is |the |difference |between |a |multiple |response |item |and |a |response |each

|time |item? |- |correct |answer |✔These |refer |to |different |item |characteristics. |"Multiple |response" |refers |to |a |particular |Response |Type. |A |multiple |response |item |can |hold |multiple |answers |on |one |contact. |"Response |each |time" |refers |to |a |particular

True |or |False: |A |patient |who |has |been |seen |twice |at |your |facility |should |have

|two |records |in |the |Patient |master |file. |- |correct |answer |✔False |- |The |patient |should |only |have |one |record, |but |that |record |will |have |two |contacts.

A |user |shows |you |a |field |in |Hyperspace |that |they |want |to |report |on. |How |can

|you |find |wherein |Chronicles |that |field |files |to? |- |correct |answer |✔Control |left- click |it. |If |that |doesn't |work, |try |using |the |Record |Viewer.

When |you |allow |multiple |summary |locations |in |a |metric-based |component, |how |many |resources |(IDK) |can |be |added |to |the |component? |How |can |you |tell

|from |the |Data |Source |form |in |Component |Editor? |- |correct |answer |✔One, |the |resource |field |becomes |single |response.

How |could |you |add |more |summary |targets |to |the |component? |What |did |this

|button |control |before? |- |correct |answer |✔Clicking |the |Add |button. |This |used |to |be |how |you |added |multiple |resources |to |the |component.

What |master |file |stores |dashboard |resources? |- |correct |answer |✔IDK

What |master |file |stores |metric |definitions? |- |correct |answer |✔IDN

What |should |you |do |before |creating |a |new |display |column? |- |correct |answer

|✔Check |to |make |sure |there |isn't |a |column |already |created |that |you |can |use.

If |you |want |to |build |a |dashboard |containing |a |metric-based |component, |what |records |do |you |need, |and |in |what |order |must |they |be |built? |- |correct |answer

|✔IDN(Metrics |definition), |then |IDK(Dashboard |resources), |then |IDB(Radar |component |that |pulls |together |IDK |records), |then |IDM(Radar |dashboard |record |this |the |frame |for |metric-based |components)

True |or |False. |A |new |Reporting |Workbench |security |class |must |be |created |for

|each |user. |- |correct |answer |✔False. |Security |classes |should |be |reused |as |often |as |possible.

True |or |False. |Only |administrators |with |the |right |security |can |build |a |report

|from |an |unconfigured |template. |- |correct |answer |✔False. |No |one |can |see |a |template |if |it |is |unconfigured.

True |or |False: |You |are |not |able |to |run |a |report |while |viewing |another |user's

|library? |- |correct |answer |✔True. |You |cannot |run |a |report |while |you |are |viewing |another |user's |library

True |or |False. |Your |Chronicles |Administrator, |Clarity |Administrator, |and |Caboodle |Administrator |will |always |be |three |separate |people. |- |correct |answer

|✔False. |Database |administrators |sometimes |oversee |operation |of |more |than |one |database.

What |activity |can |you |use |to |find |a |list |of |all |configured |templates? |- |correct

|answer |✔Template |Manager.

What |controls |the |list |of |available |measures |in |SlicerDicer? |- |correct |answer

|✔Measures |are |chosen |from |the |list |of |filters |(FDS |records) |available |in |a |given |data |model.

What |is |an |HRX |record? |- |correct |answer |✔A |Workbench |report, |a |SlicerDicer |session, |or |an |Epic-Crystal |report.

What |is |the |difference |between |a |parameter |and |a |display |column? |- |correct

|answer |✔A |parameter |is |used |by |the |query. |It |will |determine |which |results |are |found |at |run |time. |A |display |column |is |used |to |display |information |about |the |results |that |are |found.

What |is |the |difference |between |operational |and |analytical |reports? |- |correct

|answer |✔Operational |reports |are |real-time |reports |needed |by |end |users |to |do |their |jobs. |Analytical |reports |are |over-time |reports |that |show |long-term |trends |and |data.

What |is |the |name |of |the |tool |used |to |look |up |information |about |Epic-released |reporting.

a) |Analytics |Installer, |

b) |Clarity |Compass, |

c) |Report |Repository, |

d) |Reporting |Workbench |- |correct |answer |✔c) |Report |Repository

What |Master |file |stores |one |record |for |every |display |column |in |Chronicles?

a) |HRX, |b) |COL, |c) |PAF, |d)HGR, |e) |IDB |- |correct |answer |✔c) |PAF

c) |Caboodle

Which |of |Epic's |databases |contains |real-time |data?

a) |Chronicles, |

b) |Clarity,

c) |Caboodle. |- |correct |answer |✔a) |Chronicles

Which |of |the |following |is |the |Master |File |for |dashboards?

a) |IDB, |b) |IDM, |c) |DBD, |d) |None |of |the |above |- |correct |answer |✔b) |IDM

Which |of |the |following |would |you |enter |in |the |Parameters |field |of |an |activity |link |to |open |a |Hyperspace |activity?

a) |The |activity |descriptor |and |any |required |parameters |for |the |activity, |b) |The |menu |descriptor |of |the |activity, |

c) |The |user-facing |name |of |the |activity, |

d) |The |parent-menu |of |the |activity |record. |- |correct |answer |✔a) |The |activity |descriptor |and |any |required |parameters |for |the |activity

Which |summarization |function |would |best |meet |'How |many |patients |were |see |in |each |Clinic?

a) |Sum, |

b) |Percentage, |

c) |Count |Unique, |

d) |Count |- |correct |answer |✔c) |Count |Unique

Which |summarization |function |would |best |meet |'How |many |visits |happen |each |month?

a) |Sum, |

b) |Percentage, |

c) |Count |Unique, |

d) |Count |- |correct |answer |✔d) |Count

Which |summarization |function |would |best |meet |'How |much |money |did |we |charge |in |2011'?

a) |Sum, |b) |Percentage, |c) |Count |Unique, |d) |Count |- |correct |answer |✔a) |Sum

Which |summarization |function |would |best |meet |'How |much |of |our |total |revenue |is |created |by |AA |Clinic?

a) |Sum, |b) |Percentage, |c) |Count |Unique, |d) |Count |- |correct |answer |✔b) |Percentage

Scenario: |Would |the |following |report |be |Operational |or |Analytical? |Create |a |report |that |counts |the |number |of |logs |each |surgeon |has |been |documented |as |performing |in |during |the |past |year. |Display |the |log |ID, |the |name |of |the

|surgeon, |and |the |log's |primary |procedure. |- |correct |answer |✔Analytical

Scenario: |You |have |built |a |component |record. |Which |of |the |following |could |explain |why |the |component |does |not |appear |on |a |specific |dashboard?

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

b) |Component |Editor

c) |SlicerDicer |session

d) |Personalization |- |correct |answer |✔b) |Component |Editor

d) |Personalization

True |or |False: |All |reports |can |be |written |from |Caboodle |- |correct |answer |✔False

In |Chronicles, |the |tree |structure |is |divided |into |which |of |the |following |groupings. |Select |all |that |apply:

a) |Master |files

b) |Records

c) |Contacts

d) |Resources |- |correct |answer |✔a) |Master |files

b) |Records

c) |Contacts

True |or |False |Clarity |is |a |relational |database |designed |to |be |efficient |and |flexible |for |reporting |on |large |amounts |of |data |over |long |periods |of |time. |It |is

|normalized |and |compact |(small |and |efficient). |- |correct |answer |✔True

For |dashboard |components, |what |is |the |term |used |to |describe |how |end-users |can |create |an |individual |copy |of |a |dashboard |source |to |be |customized |for |their |own |use.

a) |Reconciliation

b) |Personalization

c) |Resourcing

d) |Benchmarking |- |correct |answer |✔b) |Personalization

A |user |wants |to |have |component |display |either |a |workbench |summary |or |a |metric-based |resources |on |a |dashboard |in |a |format |that |easily |accessible. |Based |on |the |user's |needs, |you |choose |to |create |a |SlicerDicer |session |to |obtain |the |requested |data. |Which |display |format |must |be |used |for |the |component |that |will |be |created |and |added |to |the |user's |dashboard?

a) |Table

b) |Graph

c) |Link |component

d) |Workbench |report |- |correct |answer |✔b) |Graph

Which |types |of |component |records |can |be |used |in |the |Component |Editor? |Select |all |that |apply:

a) |Graph

b) |Report |Listing

c) |Table

d) |Link |- |correct |answer |✔a) |Graph

b) |Report |Listing

c) |Table

d) |Link

Scenario: |A |user |reports |that |they |can |access |the |Analytics |Catalog, |but |are |unable |to |see |any |dashboards |listed. |They |ask |to |be |given |access |so |that |they |can |review |dashboards |and |templates |that |they |can |use |to |meet |reporting |needs |in |their |department. |What |would |need |to |be |modified |for |this |user |to |give |them |this |access?

The |Dashboard |resources |reside |in |which |master |file?

a) |IDM

b) |IDK

c) |PAF

d) |IDN |- |correct |answer |✔b) |IDK

True |or |False. |Only |one |type |of |data |can |be |stored |in |a |given |item. |- |correct

|answer |✔False. |Data |type |controls |and |determines |what |kind |of |data |can |be |stored |in |a |given |item. |For |example: |String, |number, |date, |time, |instant, |category.

Scenario: |On |a |patient's |chart, |there |is |an |encounter |from |two |months |ago |where |the |patient's |blood |pressure |was |recorded. |During |their |last |encounter, |a |blood |pressure |reading |was |not |recorded. |What |add |type |would |this |be |considered |from |the |choices |listed |below?

a) |Lookback

b) |Response |each |time

c) |No-add |- |correct |answer |✔a) |Lookback

A |patient |can |have |multiple |symptoms |and |multiple |diagnoses |listed |for |them. |This |response |type |is |known |as |which |of |the |following:

a) |Single |response

b) |Multiple |response

c) |Related |group

d) |Encounter |- |correct |answer |✔b) |Multiple |response

True |or |False. |During |ETL |each |night, |data |transfers |directly |from |Chronicles |to |Caboodle |and |provides |real-time |data |throughout |a | 24 |hour |period. |- |correct

|answer |✔False. |Data |transfers |from |Chronicles |to |Clarity |to |Caboodle |and |is |not |real-time |data. |It |is |always |a |day |behind.

True |or |False. |The |data |displayed |in |a |graph |component |comes |from |the |grouping |and |summarizing |performed |by |the |Workbench |summary |or |IDM

|record. |- |correct |answer |✔False |IDK |record

An |item |stores |individual |data |within |a |record |or |contact. |Which |examples |of |the |items |below |would |be |considered |a |part |of |a |patient |master |file?

a) |SSN

b) |Provider |ID

c) |Billed |charges

d) |On-time |surgical |cases |- |correct |answer |✔a) |SSN

Which |of |the |following |must |a |user |locate |before |they |are |able |to |run |a |report |or |add |a |report |as |a |favorite?

a) |Library

b) |Analytics |Catalog

c) |Report |Repository

d) |Clarity |Dictionary |- |correct |answer |✔a) |Library

Which |of |the |following |allows |you |to |share |with |other |Epic |Community |members |and |compare |your |performance |against |your |peers?

a) |Personalization