Docsity
Log inSign up
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
Sell on Docsity
Sell on Docsity
Log inSign up

Prepare for your exams

Study with the several resources on Docsity

Find documents

Prepare for your exams with the study notes shared by other students like you on Docsity

Search Store documents

The best documents sold by students who completed their studies

Search through all study resources
Docsity AINEW

Summarize your documents, ask them questions, convert them into quizzes and concept maps

Explore questions

Clear up your doubts by reading the answers to questions asked by your fellow students

Earn points to download

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

Share documents
download point icon20 Points

For each uploaded document

Answer questions
download point icon5 Points

For each given answer (max 1 per day)

All the ways to get free points
Get points immediately

Choose a premium plan with all the points you need

Study Opportunities

Choose your next study program

Get in touch with the best universities in the world. Search through thousands of universities and official partners

Community

Ask the community

Ask the community for help and clear up your study doubts

University Rankings

Discover the best universities in your country according to Docsity users

Free resources

Our save-the-student-ebooks!

Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors

From our blog

Exams and Study
Go to the blog

Epic Security and Reporting Workbench: A Guide to User Access and Configuration, Exams of Medicine

Pacific Lutheran University (PLU)Medicine

A comprehensive guide to understanding and configuring user access and security within the epic system, specifically focusing on the reporting workbench functionality. It covers key security concepts, user roles, security classes, report groups, and user types, explaining how they interact to control access to dashboards, reports, and data models. The document also includes practical examples and instructions for configuring security settings, assigning user permissions, and managing report templates.

Typology: Exams

2024/2025

Available from 01/23/2025

smart-scores
smart-scores 🇺🇸

5

(2)

7K documents

1 / 8

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Before |a |user |can |access |dashboards, |SlicerDicer |and |reports, |they |need |to |be |-
|correct |answer |✔assigned |security |to |the |proper |functionality
A |user |should |only |be |granted |access |to |the |content |- |correct |answer |✔that
|your |organization |feels |they |should |be |using.
The |basis |of |all |staff-related |build |are |the |________ |and |__________records.
|Each |staff |member |has |a |unique |provider |and/or |user |record. |- |correct |answer
|✔provider |(SER); |user |(EMP)
The |_______ |master |file |can |be |thought |of |as |a |directory |of |clinicians |who |are
|affiliated |with |your |organization. |The |______ |master |file |includes |one |record
|for |every |clinician |who |provides |care |to |your |patients. |- |correct |answer
|✔Provider; |Provider
Remember |that |the |term |"provider" |in |Epic |means |both |- |correct |answer
|✔clinicians |and |resources.
The |_________master |file |contains |one |record |for |every |person |who |logs |in |to
|your |instance |of |Epic. |- |correct |answer |✔User
User |templates |are |_______ |that |are |used |to |configure |groups |of |users. |-
|correct |answer |✔EMP |records
pf3
pf4
pf5
pf8

Partial preview of the text

Download Epic Security and Reporting Workbench: A Guide to User Access and Configuration and more Exams Medicine in PDF only on Docsity!

Before |a |user |can |access |dashboards, |SlicerDicer |and |reports, |they |need |to |be |- |correct |answer |✔assigned |security |to |the |proper |functionality A |user |should |only |be |granted |access |to |the |content |- |correct |answer |✔that |your |organization |feels |they |should |be |using. The |basis |of |all |staff-related |build |are |the |________ |and |__________records. |Each |staff |member |has |a |unique |provider |and/or |user |record. |- |correct |answer |✔provider |(SER); |user |(EMP) The |_______ |master |file |can |be |thought |of |as |a |directory |of |clinicians |who |are |affiliated |with |your |organization. |The |______ |master |file |includes |one |record |for |every |clinician |who |provides |care |to |your |patients. |- |correct |answer |✔Provider; |Provider Remember |that |the |term |"provider" |in |Epic |means |both |- |correct |answer |✔clinicians |and |resources. The |_________master |file |contains |one |record |for |every |person |who |logs |in |to |your |instance |of |Epic. |- |correct |answer |✔User User |templates |are |_______ |that |are |used |to |configure |groups |of |users. |- |correct |answer |✔EMP |records

____________records |are |used |in |conjunction |with |user |and |provider |records |to |give |employees |access |to |activities |in |the |system. |- |correct |answer |✔Security |and |Role ____________ |is |used |to |give |"access" |or |"permission" |to |activities |and |information |within |Epic |- |correct |answer |✔Security There |are |two |key |security |concepts: |- |correct |answer |✔security |points |and |security |classes. Grants |access |to |one |feature |within |Epic. |Think |of |these |like |a |key |that |grants |you |access |to |one |room. If |a |user |has |a |security |point, |they |have |access |to |an |activity. |If |they |do |NOT |have |the |required |security |point, |then |the |activity |will |not |be |available |to |them; |they |won't |even |see |it. |- |correct |answer |✔Security |Point Grouping |of |security |points |that |grant |access |to |related |activities |and |functionality |in |an |Epic |application. |Think |of |this |as |a |ring |of |keys |(security |points). |- |correct |answer |✔Security |Class The |__________ |defines |the |visual |appearance |or |layout |of |Hyperspace. |- |correct |answer |✔User |Role Three |things |a |user |role |controls: |- |correct |answer |✔1. |What |activities |open |upon |logging |in

  1. |What |buttons |you |have |across |your |top |toolbar |and |under |the |Epic |button
  2. |How |long |the |system |will |stay |idle |before |logging |you |out

The |___________in |a |report |is |a |shortcut |to |the |menu |listing |in |the |Epic |menu. |- |correct |answer |✔action ____________ |actions |are |records |in |the |HGA |master |file. |They |execute |M |code |when |clicked. |This |could |include |setting |a |flag |in |a |record |or |populating |data |in |a |record. |- |correct |answer |✔Extension-based Not |every |__________ |can |view |the |same |dashboards, |query |the |same |SlicerDicer |data |models, |and |run |the |same |reports. |- |correct |answer |✔user Report |groups |are |the |- |correct |answer |✔primary |means |of |distributing |Cogito |content. A |user |is |granted |access |to |content |if: |- |correct |answer |✔1. |The |user |has |a |security |class |that |grants |them |the |appropriate |functionality |to |view/run |that |content

  1. |The |user |and |content |share |at |least |one |report |group Assign |users |their |report |groups |on |the |Reporting |Workbench |form |of |the |- |correct |answer |✔User |Security |activity. If |a |user |and |a |Workbench |report |share |any |report |group, |then |the |user |can |- |correct |answer |✔find |the |report |in |the |Library |and |the |Analytics |Catalog To |define |a |template's |report |type |and |report |group(s), |find |and |select |that |template |on |the |- |correct |answer |✔Configuration |tab |of |the |Template |Manager.

Select |type |- |correct |answer |✔Which |type |filter |can |be |used |to |find |the |report |template |in |the |Library. Select |groups |- |correct |answer |✔Which |users |have |access |to |the |template |in |the |Analytics |Catalog |and |Library. New |in |February |2019, |if |a |user |and |a |dashboard |share |any |report |group, |the |user |can |- |correct |answer |✔view |the |dashboard. You |can |distribute |____________ |to |large |groups |of |users |with |the |same |report |groups |or |user |type, |and/or |assign |individual |dashboards |to |specific |users |for |ease |of |setup |and |maintenance. |- |correct |answer |✔dashboards Assign |report |groups |to |dashboards |either |by: |- |correct |answer |✔1. |editing |the |dashboard's |details |in |the |Metadata |Editor, |or

  1. |listing |the |report |group |on |the |Access |form |in |the |Dashboard |Editor. Epic |builds |and |maintains_____________. |They |are |used |to |broadly |describe |a |user's |responsibilities |and |capabilities |in |the |system. |- |correct |answer |✔user |types If |a |user |and |a |dashboard |share |a |user |type, |the |user |can |access |- |correct |answer |✔the |dashboard. For |most |users, |the |system |automatically |assigns |user |types |upon |login, |but |your |organization |can |also |explicitly |assign |user |types |to |user |records. |This |is

|employee |records |in |one |place. |- |correct |answer |✔RW |User |Security |Management True |or |False. |A |new |Reporting |Workbench |security |class |must |be |created |for |each |user. |- |correct |answer |✔False True |or |False. |Only |administrators |with |the |right |security |can |build |a |report |from |an |unconfigured |template. |- |correct |answer |✔False What |must |be |assigned |to |a |template |so |that |the |template |is |considered |configured? |- |correct |answer |✔To |be |considered |configured |a |template |must |have |one |and |only |one |type |assigned |to |it |and |at |least |one |group |assigned |to |it. What |activity |can |you |use |to |find |a |list |of |all |configured |templates? |- |correct |answer |✔template |manager Which |of |the |following |is |a |way |to |grant |users |access |to |a |specific |dashboard |in |Hyperspace? (

  1. |Alter |the |Radar |security |class |of |the |users |who |should |see |the |dashboard
  2. |List |appropriate |user |types |on |the |dashboard |in |the |Dashboard |Editor
  3. |By |listing |a |dashboard |directly |in |a |user |record |or |linked |template
  4. |List |appropriate |report |groups |on |the |dashboard |in |the |Dashboard |Editor ) |- |correct |answer |✔2. |List |appropriate |user |types |on |the |dashboard |in |the |Dashboard |Editor
  5. |By |listing |a |dashboard |directly |in |a |user |record |or |linked |template
  1. |List |appropriate |report |groups |on |the |dashboard |in |the |Dashboard |Editor