Adjusting System Access Flashcards
Security Structure, Editing Willow Security Class
Define: Security Class
SECURITY CLASS - security points grouped together as are appropriate for a particular group of users.
The security class is attached to the template that represents that group.
Security classes can be shared between multiple User templates, or specific to a single template.
i.e. Pharmacy technicians all share a Willow security class name “RX technicians” - The security class is attached toe the Willow Inpatient Technician Template
Define: Security Point
Access to activities and functionality in Epic is controlled by SECURITY POINTS (access!)
There are thousands of security points used by Epic’s various applications, and any given user might need a few hundred specific points.
Some security points control access to entire activities (i.e. verify)
Other security points control discrete functionality within an activity (i.e. dispense)
(i.e. Willow Security point 1 - Verify Orders for pharmacists and Willow project team but not for Technicians)
Difference between security point and security class
The ability to manually dispense a dose of a medication order is controlled by Willow security point 7 – Dispense order. If a user has that security point, they can click the Dispense button in the Medications activity, the Order Hx activity, or the In Basket.
But a user could have access to the In Basket and not have Willow security point 7. This means they could read In Basket messages but they wouldn’t see the Dispense button on any medication messages.
Identify which Willow security class is affecting a user
Identify all the templates and users affected by a security class
Edit the points that a security class contains
Explain the difference between security points and security classes
Explain The relationship between security points, security classes, templates, and users
Explain why you may need to edit a security class
Explain when you might need to duplicate and edit a security class
How does a security class get attached to a user?
via the user’s template
How can you tell what templates and users will be affected by changing a security class?
Open the security class and look at the Usage Report tab.
Imagine that your organization does a tech-check-tech workflow, and so you want all your technicians to have access to the Dispense Checking and Compound and Repackaging Check activities.
Which of the follow would you need to EDIT?
A. Each technician’s User (EMP) record
B. The Willow Inpatient Technician template record
C. The Rx Technician security class record
D. All of the above
C. The Rx Technician security class record.
Changing a security class will affect everyone who uses it, and all the technicians should be using that security class (because it’s linked via their template).
You can’t assign individual security points directly to individual users. All security points must be assigned via security classes.
Each template (and thus each user) can be linked to only one of each type of security class.
Thus, any given user must get all their Willow security points from one and only one Willow security class. If you have two groups who need access to a similar-but-not-identical set of activities, then you need two separate security classes.
A new feature is released, and you want all your technicians and pharmacists to have access to it. It’s controlled by Willow security point 999. Which of the following records do you need to EDIT to make this happen?
a. The pharmacists’ individual User (EMP) records
b. The pharmacists’ template
c. The pharmacists’ Willow security class
d. The technicians’ individual User (EMP) records
e. The technicians’ template
f. The technicians’ Willow security class
C and F. You need to add point 999 to both security classes.
Each group of users is already linked to the appropriate template, which is already linked to the appropriate security class. Changing the class will thus affect all the users. (You might open an example user from each group to figure out what security classes to edit, but you don’t need to actually CHANGE anything in those records.)