Download Hyperspace Dashboard & Component Editor: A Guide and more Exams Medicine in PDF only on Docsity!
Review Questions Chapter| 2
- |Assuming |a |user |has |the |appropriate |user |role |to |access |a |dashboard, |what |other |dashboard |settings |control |whether |the |dashboard |is |available |for |viewing? |- |correct |answer |✔The |Ready |for |use |and |Enabled |for |user |selection |check |boxes.
- |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.
- |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 |✔Both: | a. |The |component |is |not |set |as |ready |for |use. | b. |The |component |is |not |listed |on |the |Content |form |of |the |dashboard. True |or |False: Components |require |a |defined |Display |title |on |the |Display |form. |- |correct |answer |✔True: |this |is |a |required |field. Study |Checklist: |Chapter | 2 |- |correct |answer |✔ Define: |Dashboard |- |correct |answer |✔Dashboards |centralize |content |from |around |Hyperspace, |the |graphical |user |interface |which |allows |users |to |enter, |access |and |interact |with |Epic |data. Define: |Component |- |correct |answer |✔Each |of |the |sections |of |content |on |the |dashboard |is |a |component. | Components |built |by |administrators |are |source |records Components |built |by |end-users |are |personalization |records. Define: |Personalization |- |correct |answer |✔Dashboards |and |components |which |are |created |by |an |administrators |are |referred |to |as |source |records. |
|-Dashboards |must |have |a |defined |target |audience | |-Each |user |in |that |audience |must |have |security/access |for |all |components |and |reports |on |dashboard Define: |Component |Editor |- |correct |answer |✔Accessed |via |Chart |Search |for |Component |Editor |- |Six |types |of |component |records |in |Radar |1. |Graph |2. |Link |3. |Message |Board |4. |Native |HTML |5. |Report |Listing |6. |Table Additional |Information: |Component |Editor |- |correct |answer |✔Components |have |Five |Forms
- |Basic |Information
- |Display
- |Data |Source
- |Output |Format
- |Access Similar |to |the |Dashboard |Editor, |each |form |controls |your |component's |content |and |its |metadata.
Define |Activity |Descriptor |- |correct |answer |✔The |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. Hyperspace |workflow |1: |Find |Activity |Descriptor |- |correct |answer |✔Activity: |Create |a |component |which |has |a |header |that |is |able |to |take |you |to |the |Component |Editor |directly |from |your |Radar |dashboard. |
- |Access |the |about |Hyperspace |information |window |
- |Double-check |that |you |are |currently |in |the |Component |Editor |activity |
- |Access |the |About |Hyperspace |window |by |navigating |to |the |Epic |button |> |Help |> |About |Hyperspace. |
- |The |Active |activity |descriptor |field |displays |for |your |currently |active |Hyperspace |activity. Hyperspace |workflow |2: |Find |Activity |Descriptor |- |correct |answer |✔Activity |Descriptor |in |the |Menu |Summary: | End-users |often |request |links |to |activities |that |you |lack |the |security |to |access. |Thus |you |can |not |determine |the |activity |descriptor |from |the |About |Hyperspace |workflow. |For |these |instances, |use |the |following |workflow. |
- |Use |Chart |Search |to |launch |the |Menu |Summary |activity. |
- |Refer |to |pg. |2-22 |for |scenario. |
- |To |remove |a |line, |select |the |line |and |press |SHIFT+F
- |To |move |a |selected |component |higher |or |lower |in |the |component |list, |use |the |up |and |down |arrows |to |the |right |of |the |component. Perform |Task: |Configure |a |component |header |to |launch |an |activity |- |correct |answer |✔1. |Via |the |Component |Editor |go |to |the |Display |section
- |Enter |the |activity |descriptor |for |the |Hyperspace |activity |that |launches |if |a |user |clicks |the |clicks |the |component |header. |
- |To |find |the |activity |descriptor |(refer |to |previous |cards, |14, |15, |and |16) Perform |Task: |Configure |a |link |component |pt |1. |- |correct |answer |✔Two |Methods: |
- |Linking |from |the |component |header
- |Listing |multiple |activities |in |a |Link |component Jumping |to |a |Hyperspace |activity |isn't |like |linking |to |a |website, |it |requires |a |unique |link |to |identify |a |single |Hyperspace |activity. | Two |work |flows |to |find |the |activity |descriptor |for |a |given |activity. |(refer |to |previous |cards, |14, |15, |& |16) Perform |Task: |Configure |a |link |component |pt |2. |- |correct |answer |✔1. |Use |the |Component |Editor |to |create |a |new |component |called |"your |initials" |link |Component
- |Fill |out |the |appropriate |Display |Format |for |a |link |component | -2 |options |for |Data |Source
- |Component |Record: |specify |links |in |the |component |you |are |currently |building
-Code |Template: |specify |a |code |template |and/or |routine |to |populate |your |links, |not |used |by |analysts |
- |Choose |a |Data |source |of |"Component |Record"
- |Give |your |component |help |test, |a |meaningful |Display |title |and |a |default |Color
- |On |the |Output |Format |form, |Insert |a |new |URL |of |your |choice |to |your |Link |component. |(give |the |new |URL |a |label. | |- |Web |site |URLs |should |include |http:// |or |https// |- |Enter |a |Tooltip |for |your |URL
- |Add |"Administration" |to |the |Allowed |report |groups |so |you |will |be |able |to |add |this |component |through |personalization |
- |Make |sure |you |component |is |marked |as |READY |FOR |USE
- |Close |out |the |Component |Editor
- |Open |your |Dashboard |via |the |Dashboard |Editor
- |Add |the |component |to |the |Content |form |of |your |dashboard
- |Launch |the |dashboard |to |view |the |component |( |Refresh |with |ALT+= Explain |Concept: |Dashboard-level |personalization |- |correct |answer |✔Several |dashboard |attributes |can |be |customized |by |any |end |user |with |personalization |security. |Including |the |following: | |- |Changing |the |display |title |- |Changing |the |dashboard |description |- |Rearranging |the |components |- |Add |new |components |from |the |Analytics |Catalog |-Change |the |names |and |colors |of |components |on |a |dashboard
- |Data |Source
- |Output |Format
- |Access General |Settings |for |Components: |Basic |Information |- |correct |answer |✔Basic |Information:
- |Source |Record- |Read |only |if |copied |component
- |Display |Format- |Component |Type |-Graph |-Link |-Message |Board |-Native |HTML |-Report |Listing |-Table
- |Data |Source-Choose |source, |options |vary |per |component |type
- |Owning |Application-Application |team |responsible |for |maintenance |of |this |component General |Settings |for |Components: |Display |- |correct |answer |✔Display: |contains |two |sections, |General |Settings |and |Custom |Messages. |
- |General |settings |controls |the |display |title, |color |of |the |component |header |and |the |Hyperspace |activity |to |launch |when |clicking |the |header |of |the |component. | 2.Custom |Messages |section |controls |custom |headers |or |footers |you |want |to |display |on |the |component.
General |Settings |for |Components: |Data |Source |- |correct |answer |✔Controls |what |is |used |to |populate |your |component |record.
- |Refresh |interval-how |often |to |refresh |in |minutes 2.Allow |users |to |refresh-allows |users |to |refresh |data 3.Show |last |refresh |time-Display |the |last |time |the |component's |data |was |refreshed General |Settings |for |Components: |Output |Format |- |correct |answer |✔The |output |format |form |will |vary |depending |on |which |component |type |you |are |editing. |There |are |no |general |setting |that |apply |to |all |component |types General |Settings |for |Components: |Access |- |correct |answer |✔The |access |form |is |where |you |specify |this |component |is |ready |for |use |and |control |which |users |can |add |the |component |through |personalization. |The |Ready |for |use |check |box |must |be |selected |before |any |end |user |can |use |it. |
- |Allowed |report |groups End |users |with |a |report |group |listed |here |can |add |this |component |to |personalized |copies |of |their |dashboards.
- |Ready |for |use Select |if |the |component |is |ready |for |use. Review |Questions |Chapter | 3 |- |correct |answer |✔
- |True |or |False: |SlicerDicer |can |be |used |to |report |on |any |data |that |has |ever |been |entered |into |Epic. |- |correct |answer |✔False: |
Perform |Task: |Create |a |SlicerDicer |population |- |correct |answer |✔ Perform |Task: |Share |a |SlicerDicer |session |- |correct |answer |✔ Explain |Concept: |What |is |SlicerDicer |for? |- |correct |answer |✔ Explain |Concept: |What |is |SlicerDicer |not |used |for? |- |correct |answer |✔ Review |Questions |Chapter | 4 |- |correct |answer |✔
- |Which |of |Epic's |database |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 |✔Both: b. |Clarity c. |Caboodle
- |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. Study |Checklist: |Chapter | 4 |- |correct |answer |✔ Define: |Database |- |correct |answer |✔A |database |is |an |organized |collection |of |data. |The |purpose |of |a |database |defines |its |structure. | Chronicles, |Clarity |and |Caboodle |each |have |different |purposes, |thus |each |has |a |different |structure, |and |each |is |separate |from |each |other. | Also |known |as |data |sources Define: |Chronicles |- |correct |answer |✔Transactional |Database. | Structure |of |Chronicle |is |Tree-like |with |every |branch |of |the |tree |becoming |progressively |more |granular. | It |is |a |hierarchical |database |with |real-time |information |used |for |daily |operations. | No |tables |in |Chronicles, |the |tree |structure |is |divided |into |the |following |groupings
Records |contain |many |contacts Define: |Contact |- |correct |answer |✔Contacts |are |time-based They |contain |information |about |points |in |time |for |a |record. | Example The |patient |master |file |uses |contacts |for |patient |encounters. | Individual |data |within |a |record |or |contact |are |stored |in |items. Define: |Item |- |correct |answer |✔Individual |data |within |a |record |or |contact |are |stored |in |items. | They |are |data |points |(discrete |data |points) Examples |of |items |in |a |patient |master |file |include |social |security |number |and |admission |date. Define: |Lines |- |correct |answer |✔Items |that |store |multiple |pieces |of |information |at |a |time |have |multiple |lines. | Example There |is |an |item |for |diagnoses |that |has |one |line |for |each |diagnosis |entered.
Define: |Clarity |- |correct |answer |✔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). Data |is |stored |in |tables |with |two |dimensional |grids, |rows |and |columns. | Each |column |holds |a |piece |of |information, |similar |to |an |item |in |Chronicles. |Each |row |represents |an |entity |that |the |data |in |the |columns |are |about. | Example: |a |table |has |one |row |for |every |patient |encounter, |and |each |column |has |information |about |that |patient |encounter. | Clarity |data |is |accessed |using |SQL |or |tools |that |use |SQL. | Data |for |Clarity |is |extracted |nightly |thus, |it |does |not |contain |today's |data. Define: |Caboodle |- |correct |answer |✔Similar |to |Clarity, |relational |database |with |tables |of |rows |and |columns |accessed |via |SQL Designed |to |make |reporting |simpler |and |efficient |than |Clarity. | As |a |data |warehourse, |it |contains |both |Epic |and |non-Epic |data Clarity |holds |more |data/information |than |Caboodle. |
--Ex: |open |Lana |Aquagirl's |5-31-2017 |office |visit
- |In |the |INI |field |, |enter |EPT
- |In |the |ID |field, |enter |"Lana |Aquagirl"
- |In |the |contact |field, |select |Lana's |5-31-2017 |Office |Visit |
- |Click |View
- |Look |for |items |or |information, |items |are |the |numbers |to |the |left |of |each |line |item. | --Names |and |numbers |are |listed |in |blue --Values |stored |in |items |are |yellow Perform |Task: |Find |Clarity |tables |and |columns |that |extract |a |Chronicles |item |- |correct |answer |✔The |Clarity |Dictionary |lists |all |tables |that |extract |an |item. |Click |on |a |table |to |further |investigate, |report |writers |can |use |these |tables |to |find |the |information |they |need |to |build |reports |in |Clarity. |
- |Open |an |internet |browser
- |Log |in |to |the |UserWeb |(userweb.epic.com)
- |On |the |right |side |of |the |screen, |under |documentation |click |on |Data |Handbook
- |Click |on |Clarity |Dictionary |on |the |top |right
- |Select |the |appropriate |Epic |version |
- |Search |Clarity |columns, |enter |INI |and |item |number |of |the |item |you |want |to |find
- |Search
Perform |Task: |Find |Caboodle |tables |and |columns |that |extract |a |Chronicles |item |- |correct |answer |✔Use |Caboodle |Dictionary |to |find |tables |and |columns |in |Caboodle. |Search |INI |and |item |number |or |by |Clarity |table |and |column |
- |Open |the |Caboodle |Dictionary
- |Either |type |INI |and |item |number |separated |by |a |space, |or |type |a |Clarity |table |and |column |as |TABLE. |COLUMN |
- |Search |for |"EPT |7070" Notes: | --Search |results |display |table |as |red |heading --The |table |name |is |a |description |of |the |table --The |load |packages |(Clarity |Column/Chronicles |Item) |are |in |green Explain |Concepts: |What |makes |each |Epic |database |unique? |- |correct |answer |✔Chronicles: |Tree-like |structure --Transactional |database --Operational |database --Hierarchical |database --Real |Time |for |Daily |Operations Clarity --Data |Store --Relational |database --For |Reporting
