EPIC CERTIFICATION EXAM 2026 FULL
QUESTIONS AND CORRECT ANSWERS
GRADED A+
◉ User Record Answer: -The basis of all staff‐related configuration
-Each staff member who can log in to Epic has
a unique user record.
-contains your login ID and password as well as security settings that
determine what functionality you can access.
◉ Configuration of user records and user templates Answer: -Much of
the configuration of individual user records can be accomplished via
user templates, which can be assigned to individual user records to apply
a set of shared configuration.
-done in User Security. This configuration is done by
your organization's security team.
◉ User master file (EMP) Answer: contains one record for every person
who logs in to your instance of Epic
◉ If someone needs to log in to the Epic system to complete their job...
Answer: they need a user record.
, ◉ User role record ﴾E2R﴿ Answer: -defines the visual appearance ﴾or
layout﴿ of Hyperspace.
-works closely with security in determining how a user can get to a
given activity. It is attached to a user or template record
and is required to log in to Hyperspace.
-Some of the things a role record controls include:
What startup activities open automatically upon logging in to
Hyperspace
What buttons you have across your Hyperspace toolbar and under the
Epic menu
How long the system will stay idle before logging you out
◉ User templates Answer: -EMP records that are used to configure
groups of users. They allow for build and maintenance of user settings in
one location that is linked to by other user records. This helps ensure
consistency across those who do the same work and allows for easier
maintenance. Linkable templates are stored in the EMP master file along
with user records.
-A template record is assigned to a user record on the Linked Template
form of User Security (ex. all inpatient nurses can be assigned the same
template which controls their security, user role, and more.)
-Changes can be made once in the template instead of needing to update
each nurse's user record individually.
QUESTIONS AND CORRECT ANSWERS
GRADED A+
◉ User Record Answer: -The basis of all staff‐related configuration
-Each staff member who can log in to Epic has
a unique user record.
-contains your login ID and password as well as security settings that
determine what functionality you can access.
◉ Configuration of user records and user templates Answer: -Much of
the configuration of individual user records can be accomplished via
user templates, which can be assigned to individual user records to apply
a set of shared configuration.
-done in User Security. This configuration is done by
your organization's security team.
◉ User master file (EMP) Answer: contains one record for every person
who logs in to your instance of Epic
◉ If someone needs to log in to the Epic system to complete their job...
Answer: they need a user record.
, ◉ User role record ﴾E2R﴿ Answer: -defines the visual appearance ﴾or
layout﴿ of Hyperspace.
-works closely with security in determining how a user can get to a
given activity. It is attached to a user or template record
and is required to log in to Hyperspace.
-Some of the things a role record controls include:
What startup activities open automatically upon logging in to
Hyperspace
What buttons you have across your Hyperspace toolbar and under the
Epic menu
How long the system will stay idle before logging you out
◉ User templates Answer: -EMP records that are used to configure
groups of users. They allow for build and maintenance of user settings in
one location that is linked to by other user records. This helps ensure
consistency across those who do the same work and allows for easier
maintenance. Linkable templates are stored in the EMP master file along
with user records.
-A template record is assigned to a user record on the Linked Template
form of User Security (ex. all inpatient nurses can be assigned the same
template which controls their security, user role, and more.)
-Changes can be made once in the template instead of needing to update
each nurse's user record individually.
