COG 170 Exam questions with correct
answers
Chapter |2-Dashboard |- |ANSDashboards |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.
Chapter |2-Component |- |ANSA |component |is |a |single |graph |or |table |or |other |piece |of
|functionality |that |users |will |interact |with |on |the |dashboard. |Components |are |the |building |blocks |of
|a |dashboard, |and |are |the |primary |way |to |add |new |content |or |remove |content |from |a |dashboard.
Chapter |2-Dashboard |View |- |ANSThe |ability |to |change |settings |on |the |dashboard. |Users |with
|appropriate |Radar |security |can:
*Add |new |components |to |their |dashboard
*Change |the |parameters |on |dashboard |reports |or |summaries
*Add |or |remove |links |from |individual |components
*Create |their |own |new |components
Chapter |2-Dashboard |Editor |- |ANSThe |tool |that |allows |the |ability |to |modify |a |source |dashboard.
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.
Chapter |2-Component |Editor |- |ANSComponents |are |managed |in |the |Component |Editor.
|There |are |seven |types |of |component |records |available |in |Radar. |They |are:
Graph
|Link
Message |Board
|Native |HTML
|Report |Listing
|Table
Every |component |has |five |forms:
Basic |Information
|Display
Data |Source
|Output |Format
|Access
Chapter |2-Activity |Descriptor |- |ANSThe |Active |activity |descriptor |field |displays |for |your |currently
|active |Hyperspace |activity. |There |are |two |Hyperspace |workflows |that |can |find |the |activity
|descriptor |for |a |given |activity.
,Chapter |2-View |Manager |- |ANSThe |View |Manager |allows |users |to |create |new |views, |delete
|unused |views, |or |jump |into |"Edit |Layout |mode" |on |their |existing |views.
When |a |user |clicks |the |wrench |icon |next |to |a |view, |they |are |able |to:
*Drag |and |drop |components |to |rearrange |their |dashboard |view.
*Click |on |an |individual |component |to |change |the |name, |color, |or |size |of |the |component.
*Click |and |drag |between |components |to |resize |them |within |the |layout
*When |they |are |done |editing |their |view, |the |user |clicks |Save |and |Accept |on |the |bottom |of |the
|screen.
Chapter |2-Assuming |a |user |has |the |appropriate |report |group |to |access |a |dashboard, |what |other
|dashboard |settings |control |whether |the |dashboard |is |available |for |viewing? |- |ANSThe |Ready |for
|use |and |Enabled |for |user |selection |check |boxes.
Chapter |2-Which |of |the |following |do |you |need |to |create |a |link |from |a |dashboard |to |a |given
|Hyperspace
activity?
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 |- |ANSA-The |activity |descriptor |for |the |activity
Chapter |2-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 |- |ANSB-The |component |is
|not |listed |on |the |Content |form |of |the |dashboard
Chapter |2-True |or |False. |Components |require |a |defined |Display |title |on |the |Display |form. |-
|ANSTRUE-This |is |a |required |field
Chapter |2-Data |Model |- |ANSOrganized |data |that |is |related |to |each |other
Chapter |3-Filter |- |ANSFDS |Record. |Which |is |a |record |that |can |be |used |to |filter, |slice |or |measure
|data. |The |word |filter |is |used |in |SlicerDicer |to |refer |to |the |many |data |points |that |can |be |used |as
|criteria, |slices, |measures, |and |display |columns. |The |POPULATION |starts |with |a |base |and |is
|refined |using |criteria. |The |available |criteria |come |from |filters.
Chapter |3-Base |- |ANSDepending |on |which |data |model |you |are |working |with, |SlicerDicer |will |use |a
|different |base |to |define |your |population. |For |example:
Data |Model |Base
, *Admissions—All |Admissions
*IP |Pharmacy |Medication |Orders—All |Inpatient |Medication |Orders
*Imaging |Studies—All |Imaging |Studies
Chapter |3-Criteria |- |ANSCriteria |are |often |the |first |pieces |of |a |population |that |a |user |modifies.
Criteria |refine |a |population |to |only |the
|desired |records.
Chapter |3-Measures |- |ANSMeasures |are |calculations |on |the |selected |records |- |for |instance, |the
|total |count |of |patients |matching |some |criteria, |or |the |average |duration |of |inpatient |stays.
Chapter |3-Slices |- |ANSFILTERS |THAT |ARE |USED |TO |GROUP |THE |DATA.
Slices |are |ways |to |divide |the |records |you're |searching |- |for |instance, |comparing |visits |by |departments,
|or |patients |by |age |range
Chapter |3-Exclusive |Criteria |- |ANSExclusion |criteria |are |a |set |of |predefined |definitions |that |is
|used |to |identify |data |that |will |not |be |included
Chapter |3-True |or |False: |SlicerDicer |can |be |used |to |report |on |any |data |that |has |ever |been
|entered |into |Epic |- |ANSFalse. |SlicerDicer |can |only |be |used |to |report |on |data |that |has |been
|extracted |to |the |Caboodle.
Chapter |3-A |SlicerDicer |population |is |showing |all |smokers |with |PCPs |in |your |clinic. |You |would
|like |to |see |these |patients |grouped |by |their |different |PCPs, |with |one |bar |per |provider. |How |would
|you |do |this?
Choose |only |ONE |answer.
A. |Add |a |criterion
B. |Change |your |measure
C. |Add |a |slice
D. |Change |your |visualization |- |ANSC-Add |a |Slice
Chapter |4-Database |- |ANSA |database |is |an |organized |collection |of |data. |In |many |reporting
|tools, |databases |are |also |called |data |sources. |The |purpose |of |a |database |defines |its |structure.
Chapter |4-Chronicles |- |ANSEpic |data |lineage |starts |with |Chronicles. |This |is |where |nurses, |registrars,
|doctors, |billers, |and |other |users |enter |data. |Chronicles |is |a |"Tree |Based |Database".
Chapter |4-Master |File |- |ANSChronicles |is |first |divided |into |master |files. |Master |files |contain
|information |about |a |broad |subject. |For |example, |the |patient |master |file |contains |all |patients'
|medical |records |in |Epic. |Other |examples |include |master |files |for |medications, |procedures,
|orders, |notes, |and |departments.
answers
Chapter |2-Dashboard |- |ANSDashboards |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.
Chapter |2-Component |- |ANSA |component |is |a |single |graph |or |table |or |other |piece |of
|functionality |that |users |will |interact |with |on |the |dashboard. |Components |are |the |building |blocks |of
|a |dashboard, |and |are |the |primary |way |to |add |new |content |or |remove |content |from |a |dashboard.
Chapter |2-Dashboard |View |- |ANSThe |ability |to |change |settings |on |the |dashboard. |Users |with
|appropriate |Radar |security |can:
*Add |new |components |to |their |dashboard
*Change |the |parameters |on |dashboard |reports |or |summaries
*Add |or |remove |links |from |individual |components
*Create |their |own |new |components
Chapter |2-Dashboard |Editor |- |ANSThe |tool |that |allows |the |ability |to |modify |a |source |dashboard.
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.
Chapter |2-Component |Editor |- |ANSComponents |are |managed |in |the |Component |Editor.
|There |are |seven |types |of |component |records |available |in |Radar. |They |are:
Graph
|Link
Message |Board
|Native |HTML
|Report |Listing
|Table
Every |component |has |five |forms:
Basic |Information
|Display
Data |Source
|Output |Format
|Access
Chapter |2-Activity |Descriptor |- |ANSThe |Active |activity |descriptor |field |displays |for |your |currently
|active |Hyperspace |activity. |There |are |two |Hyperspace |workflows |that |can |find |the |activity
|descriptor |for |a |given |activity.
,Chapter |2-View |Manager |- |ANSThe |View |Manager |allows |users |to |create |new |views, |delete
|unused |views, |or |jump |into |"Edit |Layout |mode" |on |their |existing |views.
When |a |user |clicks |the |wrench |icon |next |to |a |view, |they |are |able |to:
*Drag |and |drop |components |to |rearrange |their |dashboard |view.
*Click |on |an |individual |component |to |change |the |name, |color, |or |size |of |the |component.
*Click |and |drag |between |components |to |resize |them |within |the |layout
*When |they |are |done |editing |their |view, |the |user |clicks |Save |and |Accept |on |the |bottom |of |the
|screen.
Chapter |2-Assuming |a |user |has |the |appropriate |report |group |to |access |a |dashboard, |what |other
|dashboard |settings |control |whether |the |dashboard |is |available |for |viewing? |- |ANSThe |Ready |for
|use |and |Enabled |for |user |selection |check |boxes.
Chapter |2-Which |of |the |following |do |you |need |to |create |a |link |from |a |dashboard |to |a |given
|Hyperspace
activity?
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 |- |ANSA-The |activity |descriptor |for |the |activity
Chapter |2-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 |- |ANSB-The |component |is
|not |listed |on |the |Content |form |of |the |dashboard
Chapter |2-True |or |False. |Components |require |a |defined |Display |title |on |the |Display |form. |-
|ANSTRUE-This |is |a |required |field
Chapter |2-Data |Model |- |ANSOrganized |data |that |is |related |to |each |other
Chapter |3-Filter |- |ANSFDS |Record. |Which |is |a |record |that |can |be |used |to |filter, |slice |or |measure
|data. |The |word |filter |is |used |in |SlicerDicer |to |refer |to |the |many |data |points |that |can |be |used |as
|criteria, |slices, |measures, |and |display |columns. |The |POPULATION |starts |with |a |base |and |is
|refined |using |criteria. |The |available |criteria |come |from |filters.
Chapter |3-Base |- |ANSDepending |on |which |data |model |you |are |working |with, |SlicerDicer |will |use |a
|different |base |to |define |your |population. |For |example:
Data |Model |Base
, *Admissions—All |Admissions
*IP |Pharmacy |Medication |Orders—All |Inpatient |Medication |Orders
*Imaging |Studies—All |Imaging |Studies
Chapter |3-Criteria |- |ANSCriteria |are |often |the |first |pieces |of |a |population |that |a |user |modifies.
Criteria |refine |a |population |to |only |the
|desired |records.
Chapter |3-Measures |- |ANSMeasures |are |calculations |on |the |selected |records |- |for |instance, |the
|total |count |of |patients |matching |some |criteria, |or |the |average |duration |of |inpatient |stays.
Chapter |3-Slices |- |ANSFILTERS |THAT |ARE |USED |TO |GROUP |THE |DATA.
Slices |are |ways |to |divide |the |records |you're |searching |- |for |instance, |comparing |visits |by |departments,
|or |patients |by |age |range
Chapter |3-Exclusive |Criteria |- |ANSExclusion |criteria |are |a |set |of |predefined |definitions |that |is
|used |to |identify |data |that |will |not |be |included
Chapter |3-True |or |False: |SlicerDicer |can |be |used |to |report |on |any |data |that |has |ever |been
|entered |into |Epic |- |ANSFalse. |SlicerDicer |can |only |be |used |to |report |on |data |that |has |been
|extracted |to |the |Caboodle.
Chapter |3-A |SlicerDicer |population |is |showing |all |smokers |with |PCPs |in |your |clinic. |You |would
|like |to |see |these |patients |grouped |by |their |different |PCPs, |with |one |bar |per |provider. |How |would
|you |do |this?
Choose |only |ONE |answer.
A. |Add |a |criterion
B. |Change |your |measure
C. |Add |a |slice
D. |Change |your |visualization |- |ANSC-Add |a |Slice
Chapter |4-Database |- |ANSA |database |is |an |organized |collection |of |data. |In |many |reporting
|tools, |databases |are |also |called |data |sources. |The |purpose |of |a |database |defines |its |structure.
Chapter |4-Chronicles |- |ANSEpic |data |lineage |starts |with |Chronicles. |This |is |where |nurses, |registrars,
|doctors, |billers, |and |other |users |enter |data. |Chronicles |is |a |"Tree |Based |Database".
Chapter |4-Master |File |- |ANSChronicles |is |first |divided |into |master |files. |Master |files |contain
|information |about |a |broad |subject. |For |example, |the |patient |master |file |contains |all |patients'
|medical |records |in |Epic. |Other |examples |include |master |files |for |medications, |procedures,
|orders, |notes, |and |departments.
