Download SlicerDicer: Data Visualization and Analysis Tool for Healthcare and more Exams Nursing in PDF only on Docsity!
What |is |a |population? |- |correct |answer |āThe |population |defines |the |data |that |will |be |used |by |the |data |model. |Criteria |can |be |added |to |further |narrow |the |data |set. SlicerDicer |respects |user |security |in |what |ways? |- |correct |answer |ā1. |Users |will |not |have |access |to |every |data |model |in |the |system. |Each |data |model |is available |to |only |a |subset |of |users.
- |When |a |user |builds |and |slices |populations, |all |of |the |data |retrieved |is |implicitly filtered |by |Service |Area |security.
- |Most |users |will |not |be |able |to |view |data |about |individual |members |of |a |population A |scheduler |wants |a |population |that |shows |how |many |appointments |there |are |today |with |a |status |of |'Scheduled.' |They |want |to |reference |this |throughout |the |day |to |keep |track |of |how |many |appointments |are |left |to |check |in. |Could |this |be |done |in |SlicerDicer? |Why? |- |correct |answer |āNo, |SlicerDicer |does |not |contain |today's |data, |so |a |list |of |scheduled |appointments |wouldn't |change |throughout |the |day. A |user |wants |a |list |of |surgical |cases |scheduled |in |the |next |week |grouped |by |procedure. |They |will |reference |this |list |at |the |start |of |each |week |to |audit |room |and |staff |usage. |Could |SlicerDicer |meet |this |need? |Why? |- |correct |answer |āYes. |Even |though |the |list |has |to |include |future |cases, |these |cases |were
|scheduled |in |advance, |and |all |such |surgeries |scheduled |at |least |a |day |earlier |will |be |displayed. True |or |False: |SlicerDicer |sessions |are |the |best |option |for |KPI |(key |performance |indicators). |- |correct |answer |āNo KPIs | ļ“¾ Key |Performance |Indicators ļ“æ |need |to |be |standardized |for |all |consumers. |Since |SlicerDicer |is |designed |to |let |every |user |adjust |and |manipulate |their |visualization |of |the |underlying |data, |it |is |not |ideal |for |this type |of |report. |Instead, |we |use |Dashboard |Metrics |as |our |primary |tool |for |distributing |KPIs |to |consumers. Data |Model |- |correct |answer |āOne |SlicerDicer |Data |Model |consists |of |a |set |of |data |that |has |been |curated |with |a |pre ā built |set |of |available filters. |Epic |releases |many |data |models, |but |an |organization |can |create |their |own |unique |data |models |as |well. SlicerDicer |respects |user |security |in |several |ways: |- |correct |answer |ā1. |Users |will |not |have |access |to |every |data |model |in |the |system. |Each |data |model |is |available |to |only |a |subset |of |users.
- |When |a |user |builds |and |slices |populations, |all |of |the |data |retrieved |is |implicitly |filtered |by |Service |Area |security.
- |Most |users |will |not |be |able |to |view |data |about |individual |members |of |a |population. SlicerDicer |and |large |data |sets |- |correct |answer |āSlicerDicer |retrieves |its |data |from |the |Caboodle |database. |This |means |it |can |filter |and |display |large |data |sets |without |affecting |your |production |database, |Chronicles. |With |the |ability |to
SlicerDicer |as |well. |In |this |section, |we |will |see |all |of |those |uses. |Another |way |to |think |about |a |SlicerDicer Filter |is |as |a |data |point. |One |SlicerDicer |Filter |contains |one |data |point |that |can |be |used |for |many |purposes. Populations |- |correct |answer |āSlicerDicer |is |a |data ā first |reporting |tool. |This |means |that |when |you |first |open |a |data |model, |you |start |with |the |entire |population |and |then |add |appropriate |criteria |to |hone |in |on |the |most |important |data. |Your |population |starts |with |a |base |and |is |refined |using |criteria. Criteria |- |correct |answer |āCriteria |are |often |the |first |pieces |of |a |population |that |a |user |modifies. |Criteria |refine |a |population |to |only |the |desired |records. |A |user |will |usually |add |new |criteria |by |clicking |Browse |in |their |Population |to |select |from |the |available |criteria. |The |list |of |available |criteria |for |a |data |model |is |defined |by |SlicerDicer |Filters. By |default, |slicing |will |always |include |a |slice |for |- |correct |answer |ā"none |of |the |above" |comparing |your |sliced |portion |of |the |population |to |the |rest |of |the |population. |To |disable |this, |click |Settings |and |clear |the |box |for |Add |"none |of |the |above" |or |"no |value" |to |slices |by |default. After |selecting |a |SlicerDicer |Filter |to |slice |on, |the |user |can: |- |correct |answer |āSpecify |what |values |for |the |SlicerDicer |Filter |should |each |get |their |own |slice Grab |the |top | 10 Grab |the |bottom | 10
Grab |the |top |or |bottom |N |records | ļ“¾ where |N |is |user |specified ļ“æ Measures |- |correct |answer |āMeasures |determine |what |function |aggregates |the |data. |This |can |be |thought |of |as |the |number |at |the |top |of |the |bar |in |a |vertical |bar |graph. |Once |again, |the |SlicerDicer |Filters |used |when |building |criteria |or |slices |are |the |same |as |those |available |when |choosing |a |measure. |Any |time |a |user |wants |to |see |their |data |expressed |as: Goals |and |Thresholds |- |correct |answer |āUse |Thresholds |to |assign |ranges |of |values |to |a |certain |color. |Bars |whose |value |for |that |measure |fall |within the |range |will |be |the |chosen |color. |One |session |can |contain |up |to | 15 |thresholds |ranges. Use |Goals |to |assign |a |single |value |to |your |measure. |Your |visualization |will |display |a |line |at |that |value. |One session |can |contain |up |to | 15 |goal |values. Goals |and |Thresholds |appearance |in |slicerdicer |- |correct |answer |āGoals |will |appear |as |a |line |for |bar |graph |and |line |graph visualizations. |In |a |pie |or |ring |chart, |a |goal |appears |as |its |own |separate |wedge. Thresholds |only |appear |in |bar |and |line |graph |visualizations. Neither |appear |in |stacked |bar |graph |visualizations. Custom |Measures |- |correct |answer |āIf |you |create |multiple |measures, |you |can |choose |which |of |them |to |use |in |your |Visual |Options, |or |you |can
on |how |these |stack |up |to |other |summaries. |Use |the |Visual |Options |to |determine |the |size |and |color |of your |populations. |Consider |the |options |for |a |vertical |bar |graph: Detail |Table |- |correct |answer |āSlicerDicer |can |render |the |results |at |a |detailed |level |in |the |Detail |Table. |Users |with |the |appropriate |security can |drill |down |to |the | recordālevel |data. |Users |can |add |new |columns |to |the |table, |sort |and |group |results, and |even |jump |right |into |a |Hyperspace |activity. |For |users |who |need |the |details |of |the |data |set |outside |of Hyperspace, |SlicerDicer |can |also |export |it |to |Excel What |is |the |only |place |users |get |to |see |identified |health |information |in |SlicerDicer |- |correct |answer |āDetail |Table Why |aren't |SliceDicer |session |not |for |KPI |(key |performance |indicators) |reporting? |- |correct |answer |āKPIs | ļ“¾ Key |Performance |Indicators ļ“æ |need |to |be |standardized |for |all |consumers. |Since |SlicerDicer |is |designed |to |let |every |user |adjust |and |manipulate |their |visualization |of |the |underlying |data, |it |is |not |ideal |for |this type |of |report. |Instead, |we |use |Dashboard |Metrics |as |our |primary |tool |for |distributing |KPIs |to |consumers. To |access |more |powerful |and |complex |ways |to |use |a |criterion, |click |on |its |customization |button. |The |button |appears |as |a |cogwheel |on |the |criterion |. |Options |for |this |criterion |incude: .. |- |correct |answer |āAdd |sequential |criteria, |which |returns |records |where |one |criterion |precedes |another
Add |overlapping |criteria, |which |returns |records |where |all |criteria |are |met |simultaneously Specify |date |range, |which |allows |each |criterion |to |use |its |own |date |range Specify |age |at |time |of |event, |which |allows |the |addition |of |an |associated |age |in |years |tied |to |a |single |event |criterion True |or |False. |Criteria |always |defaults |to |being |EXCUSIVE, |not |INCLUSIVE |- |correct |answer |āFalse Criteria |default |to |being |inclusive. |This |means |they |only |include |results |for |whom |the |criterion |is |true. |If you |wish |to |instead |create |a |population |for |whom |the |criterion |is |false, |you |can |change |from |inclusive |to exclusive |either |when |adding |the |criterion |initially, |or |by |clicking |the |customization |button | ļ“¾ | ļ“æ. |(cogwheel |button) Logical |operators |- |correct |answer |āClicking |the |logical |operators |between |criteria |can |flip |them |between |AND |and |OR |to |change |how |they |are |evaluated. |In |addition, |a |user |can |use |the |Advanced |Logic |button |to |write |their |own |logical |expression combining |the |different |criteria. What |is |the |only |place |that |users |can |see |PHI |data? |- |correct |answer |āThe |"Detail |Table" |view |under |Visual |Options.
