EPIC CLN 251/252 LATEST 2026 STUDY GUIDE QUESTIONS
AND ANSWERS RATED A+
✔✔Explain the difference between a security class and a security point. - ✔✔A security
point grants access to a single piece of functionality; it's like a key. A security class is a
collection of security points, like a key ring. Users are linked to security classes either
directly or via a template; users are not linked directly to security points.
✔✔What function does security perform in Epic? - ✔✔Security controls access to
functionality— what a user is or is not allowed to do in the system.
✔✔Who (or what) needs a provider record? - ✔✔A person or resource if at least one of
the following criteria are met:
• Credentials to display or a specialty/discipline
• Authorizing and/or ordering provider for orders
• Referred-to or referred-by providers for referrals
• Scheduled with patients or appointments in Epic
✔✔Who needs a user record? - ✔✔Everyone at your organization who uses Epic will
need a user record. The User (EMP) master file needs a record for each end user-
doctors, nurses, front desk staff, billers, etc. The user record is a starting place for
successfully getting staff started with Epic because it acts as a hub where several other
important settings are made.
✔✔Default login department - ✔✔A user will be assigned a default log in so that
whenever the user logs into EPIC the defaulted log in will occur, but will still have the
option to manually choose if needed.
✔✔Linkable Template - ✔✔• User templates (or linkable templates) are records in the
User (EMP) master file that allow you to create a single record to maintain shared
settings for multiple user records. You create a user template for a particular group of
users (for example, medical assistants). In the template, you assign the access to
activities, Hyperspace configuration, profiles, and other settings appropriate to that
group.
✔✔User Record - ✔✔Anyone who needs to log in to Hyperspace needs his/her own
user record. User records determine login IDs, passwords, default login departments,
security (access to functionality), and many other settings.
✔✔True or False: In the provider record, you can link to the corresponding user record
or a user template. - ✔✔False. The linking is established in the user record. Multiple
users may not be linked to the same provider record.
✔✔Why do MRI machines and classrooms need to have records in the Provider master
file? - ✔✔The MRI machines and classrooms are scheduled resources.
,✔✔Give an example of someone who would need a provider record but NOT a user
record. Explain why. - ✔✔A physician in your community who gets referrals from your
physicians, but who does not have access to log in to your Epic system.
✔✔What are some settings you must make in an individual user record which cannot be
set with linkable templates? - ✔✔Default login department, link to templates,
ID/password information
✔✔True or False: You can link a user to multiple linkable templates. - ✔✔True. You can
assign more than one template to a user, and that user can choose the template they
want to affect them when they log into Hyperspace.
✔✔What four patient workspace settings is the Workflow Engine configured to control? -
✔✔1. Activity tabs (to the left of the patient chart)
2. More Activities menu (formerly known as the action menu)
3. Navigators
4. Sidebars (when using widescreen view)
Workflow Engine rules don't eliminate the need for assigning role and profile records to
users. Those records contain many more settings that aren't included in the Workflow
Engine.
✔✔How does the Workflow Engine evaluate properties? - ✔✔The conditions evaluate
properties about the user, the patient, or the type of encounter (admission, office visit,
etc.). After matching on conditions, the directives then arrange the patient workspace.
✔✔Rule Hierarchy - ✔✔Stops the workflow engine from searching past what it needs to
after the conditions are met - works in correlation with the profile hierarchy.
✔✔Property - ✔✔• Property= Relevant Information
• Every clinical workspace has many properties, such as encounter type, patient age,
and provider specialty.
• Each property used in the Workflow Engine is defined by a property record in the
Properties (LRC) master file. Epic programmers build these records.
✔✔Conditions - ✔✔The "If..." portion of a rule (condition) specifies which properties and
values the "then..." portion applies to. The rows that start with "if" evaluate properties.
• These nested conditions allow for a more refined search.
• When evaluating a rule, the system looks to the top condition first.
• If a condition is not true, the rule skips any conditions nested under it. It moves down
the rule to the next value for that condition, or the next entirely new condition
✔✔Directive - ✔✔The "then..." portion of the rule (directive) tells the Workflow Engine
what to do if the rule matches the conditions specified in the "If..." portion.
, • Normally, once a rule matches on a true condition, it executes whatever directives are
there and then stops processing the rule. It's done searching.
• However, if a set of directives says, "continue afterwards," then the system will
continue reading the rule and processing conditions and directives.
• Directives found later in the rule can add to previous directives.
• If later directives found by continuing afterwards conflict with previous directives, the
later directives will trump the previous.
✔✔Workflow Engine - ✔✔• A type of rule used to define the activities and navigators
available when a clinician opens an encounter in the unified clinical workspace.
• Workflow Engine rules are built in the Workflow Engine Rule Editor.
✔✔True or False. Once a rule matches on conditions and carries out directives, the
system always keeps looking for more conditions to evaluate. - ✔✔False. The system
will only continue evaluating the rule if the first set of directives specifies "continue
afterwards.
✔✔True or False. If the patient encounter does not match conditions in a Workflow
Engine rule, the system looks for a rule in the next level of the profile hierarchy. -
✔✔False. Settings found in the role and compiled profile for the patient encounter will
be used. The system will not look for additional Workflow Engine rules at other levels in
the profile hierarchy.
✔✔What are three aspects of a patient encounter that can be altered based on a rule
match? - ✔✔Some include: Override or Append More Activities menu, Change default
activity when a workspace opens, Change available navigators.
✔✔How does the system know which Workflow Engine rule to use? - ✔✔The Workflow
Engine rule linked to the most specific level in the profile hierarchy is the rule that will be
consulted.
✔✔Where do you link to a Workflow Engine rule? - ✔✔Profile
✔✔How do you build a Navigator Template? - ✔✔• Build in Hyperspace using Template
Editor (LVN) - Create a new navigator record using the prefix "T" to represent "template"
in its name
• Add existing topics, A template must contain at least one topic to function.
• Sections can't be added to a template directly.
• Add a section by typing in the "Search for a section" field at the bottom of the
appropriate topic, or click the Add button to the left of that field
✔✔Navigator: Template Record - ✔✔• The most general type of navigator record.
Within the template record, administrators can define one or more topics, which are
groupings of navigator sections. The template, thus, defines a single, complete
navigator.
AND ANSWERS RATED A+
✔✔Explain the difference between a security class and a security point. - ✔✔A security
point grants access to a single piece of functionality; it's like a key. A security class is a
collection of security points, like a key ring. Users are linked to security classes either
directly or via a template; users are not linked directly to security points.
✔✔What function does security perform in Epic? - ✔✔Security controls access to
functionality— what a user is or is not allowed to do in the system.
✔✔Who (or what) needs a provider record? - ✔✔A person or resource if at least one of
the following criteria are met:
• Credentials to display or a specialty/discipline
• Authorizing and/or ordering provider for orders
• Referred-to or referred-by providers for referrals
• Scheduled with patients or appointments in Epic
✔✔Who needs a user record? - ✔✔Everyone at your organization who uses Epic will
need a user record. The User (EMP) master file needs a record for each end user-
doctors, nurses, front desk staff, billers, etc. The user record is a starting place for
successfully getting staff started with Epic because it acts as a hub where several other
important settings are made.
✔✔Default login department - ✔✔A user will be assigned a default log in so that
whenever the user logs into EPIC the defaulted log in will occur, but will still have the
option to manually choose if needed.
✔✔Linkable Template - ✔✔• User templates (or linkable templates) are records in the
User (EMP) master file that allow you to create a single record to maintain shared
settings for multiple user records. You create a user template for a particular group of
users (for example, medical assistants). In the template, you assign the access to
activities, Hyperspace configuration, profiles, and other settings appropriate to that
group.
✔✔User Record - ✔✔Anyone who needs to log in to Hyperspace needs his/her own
user record. User records determine login IDs, passwords, default login departments,
security (access to functionality), and many other settings.
✔✔True or False: In the provider record, you can link to the corresponding user record
or a user template. - ✔✔False. The linking is established in the user record. Multiple
users may not be linked to the same provider record.
✔✔Why do MRI machines and classrooms need to have records in the Provider master
file? - ✔✔The MRI machines and classrooms are scheduled resources.
,✔✔Give an example of someone who would need a provider record but NOT a user
record. Explain why. - ✔✔A physician in your community who gets referrals from your
physicians, but who does not have access to log in to your Epic system.
✔✔What are some settings you must make in an individual user record which cannot be
set with linkable templates? - ✔✔Default login department, link to templates,
ID/password information
✔✔True or False: You can link a user to multiple linkable templates. - ✔✔True. You can
assign more than one template to a user, and that user can choose the template they
want to affect them when they log into Hyperspace.
✔✔What four patient workspace settings is the Workflow Engine configured to control? -
✔✔1. Activity tabs (to the left of the patient chart)
2. More Activities menu (formerly known as the action menu)
3. Navigators
4. Sidebars (when using widescreen view)
Workflow Engine rules don't eliminate the need for assigning role and profile records to
users. Those records contain many more settings that aren't included in the Workflow
Engine.
✔✔How does the Workflow Engine evaluate properties? - ✔✔The conditions evaluate
properties about the user, the patient, or the type of encounter (admission, office visit,
etc.). After matching on conditions, the directives then arrange the patient workspace.
✔✔Rule Hierarchy - ✔✔Stops the workflow engine from searching past what it needs to
after the conditions are met - works in correlation with the profile hierarchy.
✔✔Property - ✔✔• Property= Relevant Information
• Every clinical workspace has many properties, such as encounter type, patient age,
and provider specialty.
• Each property used in the Workflow Engine is defined by a property record in the
Properties (LRC) master file. Epic programmers build these records.
✔✔Conditions - ✔✔The "If..." portion of a rule (condition) specifies which properties and
values the "then..." portion applies to. The rows that start with "if" evaluate properties.
• These nested conditions allow for a more refined search.
• When evaluating a rule, the system looks to the top condition first.
• If a condition is not true, the rule skips any conditions nested under it. It moves down
the rule to the next value for that condition, or the next entirely new condition
✔✔Directive - ✔✔The "then..." portion of the rule (directive) tells the Workflow Engine
what to do if the rule matches the conditions specified in the "If..." portion.
, • Normally, once a rule matches on a true condition, it executes whatever directives are
there and then stops processing the rule. It's done searching.
• However, if a set of directives says, "continue afterwards," then the system will
continue reading the rule and processing conditions and directives.
• Directives found later in the rule can add to previous directives.
• If later directives found by continuing afterwards conflict with previous directives, the
later directives will trump the previous.
✔✔Workflow Engine - ✔✔• A type of rule used to define the activities and navigators
available when a clinician opens an encounter in the unified clinical workspace.
• Workflow Engine rules are built in the Workflow Engine Rule Editor.
✔✔True or False. Once a rule matches on conditions and carries out directives, the
system always keeps looking for more conditions to evaluate. - ✔✔False. The system
will only continue evaluating the rule if the first set of directives specifies "continue
afterwards.
✔✔True or False. If the patient encounter does not match conditions in a Workflow
Engine rule, the system looks for a rule in the next level of the profile hierarchy. -
✔✔False. Settings found in the role and compiled profile for the patient encounter will
be used. The system will not look for additional Workflow Engine rules at other levels in
the profile hierarchy.
✔✔What are three aspects of a patient encounter that can be altered based on a rule
match? - ✔✔Some include: Override or Append More Activities menu, Change default
activity when a workspace opens, Change available navigators.
✔✔How does the system know which Workflow Engine rule to use? - ✔✔The Workflow
Engine rule linked to the most specific level in the profile hierarchy is the rule that will be
consulted.
✔✔Where do you link to a Workflow Engine rule? - ✔✔Profile
✔✔How do you build a Navigator Template? - ✔✔• Build in Hyperspace using Template
Editor (LVN) - Create a new navigator record using the prefix "T" to represent "template"
in its name
• Add existing topics, A template must contain at least one topic to function.
• Sections can't be added to a template directly.
• Add a section by typing in the "Search for a section" field at the bottom of the
appropriate topic, or click the Add button to the left of that field
✔✔Navigator: Template Record - ✔✔• The most general type of navigator record.
Within the template record, administrators can define one or more topics, which are
groupings of navigator sections. The template, thus, defines a single, complete
navigator.
