CLN 251/252

Question 1

What is Chronicles?

Answer 1

Epic’s database management system. Often referred to as the “database”.
All the data that users access in Hyperspace is stored in Chronicles.
It’s the master filing cabinet

Question 2

What is Hyperspace?

Answer 2

Epic’s front-end user interface.
Where users complete their work.
It basically asks Chronicles for data or to edit existing or save new data.

Question 3

What is hyperdrive?

Answer 3

The wedbased platform that launches Hyperspace. (Similar to Chrome, edge etc..)

Question 4

What is Classic?

Answer 4

The original Hyperspace.
You can build or configure records or utilities here (or in text).

Question 5

What is Text?

Answer 5

Is a text-based back-end interface with Chronicles data.
Used solely by administrators for creating, editing and analyzing records.
Text includes a number of applications such as:
*Clinical Administration (for various clinical apps)
*Chronicles (for importing, duplicating, hiding, searching for or otherwise managing records)
* Training Tools (which includes things like patient duplication)

Question 6

Master files

Answer 6

Chronicles is organized in master files. Each master file stores all the data about one thing.
Ie:
* Info about patients is stored in the patients master file.
* Info about users is stored in the users master file.

Think of Chronicles as the filing cabinet
Master files is the cabinet drawer

Question 7

Records

Answer 7

A record stores information about one specific entity in the master file.
Think of Chronicles as the filing cabinet
Master files is the cabinet drawer
Records are the file folder

Each Record has a unique ID number

Note: A master file’s record can network to one another record for efficient data storage and maintenance. (ie an employees record (Dr Small) (in the Employee master file) may link to the department’s record (pedatrics) where he /she works (with in the Departments master file)

Question 8

A Contact

Answer 8

In Chronicles, date sensitive information about a record is stored within a “contact”.
A contact is a date specific snapshot of the data within a record allows for changes to the record to be effective on a specific date.

NOTE: not all data in a record is a contact (Date specific)

Think of a contact as the new or changed data at each encounter.

Think of Chronicles as the filing cabinet
Master files is the cabinet drawer
Records are the file folder
The contact (encounter) is the piece of paper for that new data.

Question 9

Items and Values

Answer 9

individual pieces of data are stored as items and values.
An ITEM is like a question on a standardized form.
A VALUE is like the answer

Every record contains the same ITEMS, but the values in each record will likely be different.
Each record will contain lots of items, but very few records will have a value for every item (Ie; a patient may not have a home phone #, just a cell #, but there is a question for a home number in every record.)

Items have numbers associated with them as unique identifiers as well a name to help you understand the purpose of the item.

Question 10

All of the information that you enter in Hyperspace is stored in ____________________ , Epic’s database management system.

Answer 10

Chronicles

Question 11

A(n) __________________________is a date-specific snapshot of the data within a record.

Answer 11

Contact

Question 12

Each ________________________ stores all of the data about one type of thing.

Answer 12

Master file

Question 13

A(n) ________________________ is a discrete field within a record.

Answer 13

Item

Question 14

Each _____________________________ stores information about one specific entity in the master file.

Answer 14

Record

Question 15

A(n) _______________________ is the data that is stored in an item.

Answer 15

Value

Question 16

A dynamic master file

Answer 16

One that grows and changes (Ie the patient master file)
Users (mostly) and builder can make changes.

Not every record will have a name…. dynamic records often do not.

Note: A master file’s record can network to one another for efficient data storage and maintenance. (ie an employees record (Dr Small) (in the Employee master file) may link to the department’s record (pedatrics) where he /she works (with in the Departments master file)

Question 17

A static master file

Answer 17

One that can be changed or updated, but mostly stay the same.
(Ie User (Employee) master files).
Mostly builders make changes here.

Note: A master file’s record can network to one another for efficient data storage and maintenance. (ie an employees record (Dr Small) (in the Employee master file) may link to the department’s record (pedatrics) where he /she works (with in the Departments master file)

Question 18

Record viewer

Answer 18

Record Viewer is a tool that allows you to take a read-only look at a record in Chronicles.
When looking at records behind the scenes, while all the same components are there (records, items, values, etc.), you might note that the naming of records and the data they contain are quite different.

Record Viewer can show every item programmed into a master file. Some master files have thousands of items, but very few records in a master file have a value specified for every item.

For efficiency, most users leave the Include Blanks check box cleared, so Record Viewer only shows items in a particular record that have a value. This can greatly reduce the amount of scrolling needed. To see all the items that exist within a master file, select the Include Blanks check box from the Item Filters on the right.

After making any change to a lookup in Record Viewer, remember to click View Record.

Question 19

Report (LRP)

Answer 19

Is a master file
Provides information for the End User.
Often these reports provide the user with information that helps them stay informed about a patient. Reports are comprised of one or more print groups. Reports are used across Epic in a variety of clinical and non-clinical activities.
For example, reports are used to format In Basket messages, as printouts for prescriptions, for read-only sections in navigators, and many other places.

Each record in the Report (LRP) master file links to, or is networked to, one or more records in the Print Group (LPG) master file

Question 20

Print Groups (LPG)

Answer 20

Is a Masterfile
Print group records are shared.
This means they can be reused across many different reports. For example, many different reports may all use the same print group to display patient demographics.

Question 21

Steps for editing a report (5):

Answer 21

1. Determine how a report needs to change: What information is missing? What information is not needed? (ie Pediatricians want a snapshot report to provide additional information compared to others in the department)
2. Identify the report record (name and ID) you want to edit.
   (i.e. Use session information report to show report and print group ID #’s)
3. Identify (or create) the print groups (Name and ID’s) that need to be added, edited or removed. (ie. what info (Print groups) do they want added)
4. Edit the report by adding, modifying, or removing print groups as needed. (ie Duplicate the current report and add the necessary print groups to create the desired report for the peditricians)
5. Confirm that the report is linked in the appropriate place so that it affects the desired users. Done by linking to a profile. (ie. linked to right heirarchy in profiles so it affects only the necessary users)

Question 22

Clinical Administration (In text)

Answer 22

Is a tool for administrations/builders to modify content in Chronicles
This controls how hyperspace behaves for end users.

The first page in Clinical Administration shows a listing groups of related Master Files (ie: Medication, Allergies and immunizations are all together so are all the procedures etc..)

Question 23

An Activity

Answer 23

A space in Hyperspace that allows you to perform a task or enter data

Question 24

What are the six levels of the profile hierarchy?

Answer 24

The profile hierarchy allows administrators to make profile settings to best fit a users’ needs in the most efficient way possible. The profile hierarchy consists of profiles attached to six records, listed below in order of most specific to least specific (most general):

1. User/User Template: For profile settings common to a specialized group of users.
2. EpicCare Security Class: For profile settings common to people with the same job duties or scope of practice, like all ambulatory physicians or all pharmacy technicians.
3. Login Department: For profile settings common to people who have different job duties but who work in the same department.
4. Login Revenue Location: For profile settings common to everyone who works in a particular hospital or clinic, regardless of job duties.
5. Login Service Area: For profile settings common to everyone who works in a particular billing entity, regardless of job duties.
6. EMR System Definitions: For global profile settings that apply to every clinical user in your system unless overridden at a more specific level.

Question 25

Profiles (LRP)

Answer 25

Is a Masterfile
Allow activities to adapt for various users, particularly users with different specialties.
They configure the options within activities.
One example is the SnapShot activity. While both an obstetrician and a cardiologist may have access to this activity, the obstetrician may want to see OB history reports, while the cardiologist may want to see an EKG results report. Profiles make this flexibility possible. (building modifying a report happens in reports, but is linked to profiles in the end)

The last step of building a new report is making it available to users. You do that by linking it to a profile.
When a user opens the activity that needs that report, the profile (LPR) tells the system what report to load. Then the report tells the system what print groups to display.

Profile records configure options within activities. The system looks to profiles to determine how the activity looks, behaves, and what options are available within that activity.

A profile is a profile is a profile…

Every profile record contains the same screens and items. The differences among profile records affecting a user are the values they contain and where on the hierarchy they are linked. Any profile record can be linked to any level of the profile hierarchy.

Question 26

A compiled Profile

Answer 26

It represents the collection of profile settings that will impact a user.

You build from the most general profile up.

The system reads from the most specific down when determining what profiles a user needs.

Note: in Session Information you can veiw the profile compilation for each level of the profile heirarcy:
(user, Sec class, depat, rev location, service area, facility) which will form the compiled profile.

Question 27

The rule of Specificity/ Building by exception

Answer 27

refers to the method of making general settings in the broadest levels of a hierarchy and overriding individual settings in more specific levels of the hierarchy. By making fewer setting changes and avoiding duplicate work across records, building by exception allows for efficient build that is easier to maintain over time.

Question 28

What questions will help you identify the best level to deliver changes to profile settings:

Answer 28

What setting needs to change?
Which users need the change?
What do the users who need the change have in common?
What’s the most general hierarchy level that could deliver this change to the correct users?

Question 29

Two goals should be considered whenever you are asked to change any shared record

Answer 29

Make the right changes for the users who need them.

Don’t make changes for users who don’t need them.

Question 30

What are some possible settings that are configured in a profile record.

Answer 30

Reports: Incorporated into several activities across clinical applications

• Schedule reports
• Available reports in the Patient Lists, as well as the columns a user can select when creating a new My List
• Chart Review reports for each type of encounter and each type of order
• Synopsis Views

Orders-related settings:

• Orders preference lists
• Default order mode, such as verbal
• Whether the system tries to have the ordering and/or authorizing provider appear by default when you place an order
• Which order types require an associated diagnosis
• What validation extensions are checked when signing an order (to check for duplicates, make sure that an admitted patient has a hospital account, etc.)

Vitals: Units of measure used when displaying a patient’s height or weight

Signing a visit: What information must be charted before an encounter can be closed

Flowsheets: Default buttons and preference list items

Navigators: Which navigators you see when you log in to Hyperspace (these settings may be overridden by Workflow Engine rules)

Workflow Engine Rules:

A Workflow Engine rule is a set of conditions that will change a patient workspace based on certain conditions

Question 31

Facility (EAF) Record

Answer 31

A facility record is not the same thing as System Definitions. While both can impact an organization, System Definitions impacts clinical settings, while facility records impact other organizational settings. A profile is linked to System Definitions (LSD), not the facility (EAF) record. You can’t link a profile to the facility (EAF) record.
The facility structure forms the backbone of your administrative build. Without it, you would be unable to determine where patients are being seen, where users are working, and what settings should apply. Designing and building your facility structure is one of the first tasks in an implementation.

Question 32

Service Area

Answer 32

Service areas represent the accounts receivable and/or business entities of your organization. This level in the hierarchy exists for the purposes of Epic’s billing applications. If a patient could receive care from two places and still get a single bill, those two places would be part of the same service area.

Depending on the financial reporting needs of your organization, a service area might represent a geographical region, a previously independent organization that your organization has acquired, or simply your entire organization. The need for multiple service areas is determined by the billing or access management teams. Many customers have just one service area

Question 33

Revenue Location (More commonly called Locations)

Answer 33

Represent entities that exist within each of your service areas.

Locations are typically physical buildings, freestanding clinics, and hospitals. Locations can also represent groups of departments.

Question 34

Department (DEP)

Answer 34

The Department (DEP) master file contains records for the hospital units and departments. They belong to the revenue location you link them to, so you can NOT reuse these records across revenue locations even if the same kind of department exists at different revenue locations.

A department record exists for one of the following reasons:

It’s a place where patients receive care from healthcare providers. Patients are scheduled or admitted in such a department every time they have a clinical encounter.
Often users have the ability to choose a department when they log in to Hyperspace after entering an ID and password. The login department controls a variety of settings, such as which department is displayed for your schedule and which reports are available.

Question 35

Preference Lists

Answer 35

These are the only ones that combine all the option at each hierarchy.

Question 36

Work flow Engine Rule (LOR)

Answer 36

Is a Masterfile
A Workflow Engine rule runs when a user opens a patient workspace and provides the appropriate tools to fit the user’s needs.

The system looks to the Workflow Engine rule defined in the user’s compiled profile, which can then link out to the tools a user needs, such as activities or navigators. Workflow Engine rules can also point to other Workflow Engine rules, which can help reduce the overall size of your rules and make for more ease of maintenance and updates.

Question 37

How the workflow engine rule works:

Answer 37

What does workflow engines do? The same user could open a chart, but based on what that patient is scheduled for they will see a different work space (Ie a pediatrician see an patient in an outpatient clinic will see the “this visit” tab open first, whereas the same pediatrician doing round on an inpatient will see the “summary” tab open first. It automatically brings them to the workspace they need first to do their work best with that patient.

A Workflow Engine rule (LOR) record, sometimes called a WE rule, is linked to a profile and evaluates more information than the profile hierarchy alone can, like patient encounter type or patient age. Think of this part of the rule as an If statement, such as “If the patient is an outpatient…”. A Workflow Engine rule also sets the overall patient workspace with the activities that are appropriate for that context of care. Think of this part as the Then statement, such as “…then give the This Visit activity as the default activity”. What you can set in a Workflow Engine rule is limited to only the patient workspace and includes:
(A) The Storyboard report that appears on the left of the patient workspace.

(B) The activity tabs across the top of the patient workspace, including which navigators appear within the activity tabs.

(C) Which activity the user is brought to when the patient workspace opens.

(D) The activities available in the More menu (the drop down menu next to the wrench)

(E) The activity tabs in the Sidebar and whether the sidebar opens when the patient workspace opens.

Question 38

Condition Statement

Answer 38

A Workflow Engine rule is written as a set of condition statements. These condition statements evaluate information about the user, the patient, or the type of encounter (admission, office visit, etc.). The line of a condition statement that starts with “IF” is referred to as a condition. A condition contains one property. Properties are “what” is being evaluated, such as encounter type, patient age, or specialty
Consists of a If than statement

Question 39

What is the operator in a condition statement?

Answer 39

Is the:
equals to,
less than,
is greater than,
is null
etc..
Statements.

Question 40

The value in the condition statement?

Answer 40

The value(s) finish setting up the logical expression in a condition statement. This determines whether the condition statement is true for a given patient or situation. If there are multiple values, they are always automatically connected by “OR” logic.

Question 41

Nested condition statements:

Answer 41

When the rule evaluates a condition statement as TRUE for a patient context, the rule continues by following that node. Often another condition statement will appear “nested” underneath, indented in the rule under the previous condition statement(In Classic)
Nested condition statements allow the system to evaluate multiple condition statements for setting tools for very specific patient care contexts. Nested condition statements allow for “AND” logic.
If one of the nested condition statements in false, the system will not proceed with that original condition statement in which contained a false “nested condition statement. I will skip this condition statement and move on to the next condition statement. and

Question 42

A Work Engine Subrule

Answer 42

A subrule is a smaller Workflow Engine rule that can be reused across other rules whenever the same context of care needs to be evaluated and tools given. Multiple Workflow Engine rules can point to the same subrule. This allows for fewer rules set at more general profiles that “triage” to these smaller subrules. Pointing to the same smaller subrule records mean less large and redundant rules, and thus less overall rule build.

Question 43

Workflow engine rule build steps:

Answer 43

1. Look into the workflow engine rule explanation.
2. Identify your targeted change and appropriate location in the rule.
3. Update the workflow engine rule.
4. Link the workflow engine rule to a profile (For new builds if it isn’t already linked)
5. Test

Question 44

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.

Answer 44

False: Only the workflow engine rule found in the 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.

Question 45

In which record do you link a Workflow Engine rule? Choose only ONE answer.
Report
Profile
Navigator
Print Group

Answer 45

Profile

Question 46

Navigators (LVN)

Answer 46

Navigators are designed to organize a workflow in a logical format. For example, a medical assistant rooming patients in a clinic needs to enter a chief complaint, vitals, and perhaps begin a short note. A physician rounding on a patient in the hospital wants to review the previous day’s information, then modify, discontinue, or place new orders, and write a note.

Users see navigators because of the Workflow Engine rule in their compiled profile. The goal is for end users to see the navigator that is best suited for their workflow every time they open a patient’s chart.

The Navigator master file has different types of records. Record types determine how and where a record can be used. Navigators are composed of three types of records: templates, topics, and sections. All Navigator types are part of the LVN master file

Question 47

Directives in the condition statement:

Answer 47

If condition statements are the “If”, the “Then” is the directives. After matching on condition statements that are TRUE, the directives either do one of two things:

1. Arrange the “Clinical Workspace” with the appropriate tools, such as adding a navigator or menu.
2. “Go to” another Workflow Engine rule.

Question 48

Naming of navigator records:

Answer 48

T identifies a template record
TOPIC identifies a topic record
and
SEC identifies a section record

Question 49

What to consider when building Navigators:

Answer 49

1. When do clinicians need this navigator? Is it only for certain encounter types or patient
   populations?
   This helps you identify the kind of properties, operators and values you need to set in your
   conditions.
2. How do I make this navigator apply in those situations and not others?
   A Workflow Engine rule! Avoid building net new overriding Workflow Engine rules
   whenever an existing rule can be modified to work!
3. What workflows do clinicians have in those situations? What will clinicians be documenting and in
   what order do they need to complete their workflow?
   This helps you identify how you need to build the topics and the order of their sections.
4. Is there an existing navigator template to meet those workflow needs?
   If an existing navigator template meets your need, you can specify it in the Workflow
   Engine rule, and be done with your build!
   If there is one that is close to what you need, you can duplicate it and modify the copy.
5. What topics does the template need?
   Do the topics already exist?
   Do I need to build any new ones? If so, there is one more step!
6. If a new topic is needed, what sections should it contain?
   In the Navigator Editor, you can search for sections using keywords. If you aren’t sure what a
   section to use or think you may need a new section, your Epic representative can help!

Question 50

True or False: To create a navigator, you work in the following master files: Section (SEC), Topic (TPC), and Template (TMP).

Answer 50

False, in the Navigator masterfile (LVN)

Question 51

Fill in the blank: A navigator topic record contains navigator __________ records. Choose only ONE answer.
Template
Topic
Section

Answer 51

Section

Question 52

True or False: A navigator template record can link to more than one topic record.

Answer 52

True

Question 53

IF you type a caption of ‘Charting’ into a navigator topic record, who will see that in Hyperspace, and in what place will they see it?

Answer 53

The end user as as topic in the navigators template

Question 54

What does a role record (E2R) control?

Answer 54

It controls the layout and behaviour of hyperspace.
A role record controls what activities (E2N) a user sees immediately upon logging in, called Startup Activities.
Activities have default menus and toolbars (E2U). Often users need slightly different options or buttons to be available. The role masterfile can be used to add or replace options a user sees within menus or toolbars (E2U) within their activities. (these options can be found in the menu under the Epic button or the Hyperspace Toolbar they see immediately upon logging in).

A role record controls the maximum number of workspaces you can have opened at a time, including patient charts. Since startup activities cannot be closed, you will need to account for them whenever determining the maximum number of workspaces allowed. Regardless of the total number a user has, the startup activities always count as one open workspace.

Question 55

What are two ways to limit patient workspaces?

Answer 55

1) Specify an overall limit for workspaces of any type or
2) Base your limit on the type of workspace, for example, one patient chart, plus up to three other non-patient workspaces

Question 56

Role records refer to

Answer 56

the descriptors of activities (E2N) and menus (E2U) that should display.

Question 57

Where are roles set up

Answer 57

In the user (EMP) template

Question 58

Security Class

Answer 58

Is a Masterfile
Access to activities and tools in Epic is controlled by records in the security class (ECL) master file.
There are many different types of security: one for almost every Epic product (e.g., EpicCare Inpatient, ASAP, and Home Health), and additional types for features shared across multiple products (e.g.; In Basket).

Commonly used Security Types:
1. In Basket: In Basket is the electronic messaging system used within Epic applications. All users need some access to these tools.

2. Reporting Workbench: Reporting Workbench is a tool that provides flexible, template-based reporting integrated with Hyperspace. All users need some access to these tools.
3. Shared: Shared security controls functions that are found in some or all Epic products. For example, a user’s ability to create SmartText records or find providers. All users need access to some of these tools.
4. EpicCare (also called EpicCare Ambulatory): EpicCare controls universal clinicals tools needed by clinicians providing patient care. Only users who will use clinical tools need access to these tools.
5. Inpatient (also called EpicCare Inpatient): EpicCare inpatient controls clinical tools only needed for working in an inpatient (or hospital) setting. Only those who work at hospitals need access to these tools.

Having different types of security has several benefits:

Facilitate sharing: Categorization by security types makes sharing security more feasible, decreasing the amount of build needed to accommodate each user’s unique combination of security needs.

Ease of maintenance and troubleshooting: When security-related issues arise, administrators can pinpoint where to make changes based on the type of access.

Current and future security changes: With every release, new security is added to grant access to new functionality. It is easier to find the security that needs updating based on their types or give a new type of security to a user.

Question 59

Security Points

Answer 59

Security points are the keys, or discrete points of access to Epic functionality. Each activity (like Chart Review) is associated with one or more security points. If users have the security point, they have access to the functionality. If they do NOT have the required security point, then they will not be able to use that feature. Security points are often referred to by type (Inpatient, EpicCare, Shared, etc.) and ID.

In some of Epic’s applications, security points can be either permissive or restrictive. Permissive security works as described in this section-it gives you access to a piece of functionality. A restrictive security point works the opposite way-if you have the point, then you LOSE access to the activity or piece of functionality.

Assigning these points uniquely to every user would be time consuming and require significant maintenance over time. Administrators must determine which security points are appropriate for different groups of users at an organization. Instead of giving individual security points directly to users, security points of the same type are collected into security class (ECL) records and shared among a group of users with the same access needs.

Users will need security classes based on the types of security they need for their job. Users who have the same security type needs can share the same security class (ECL) record. If they do not need a type of security, they will not be assigned a class for it. Across all security types, only one security class per type will affect a user at a given time.

If a group of users needs a security point added or removed, administrators adjust the appropriate security class and all the users linked to it are automatically affected.

Security point is the key, Security Class is the key ring.

Question 60

User and Providers

Answer 60

Each is a separate masterfile.
Depending on the type of work a user does in Hyperspace, users may need a provider record. Users who need a provider record have at least one of the following criteria: credentials should display after their name, authorized to place orders, will be scheduled with patients, or are referred to or from within your organization.

However, anyone who will log in to Epic will need their own user record. User records determine how and where a user logs in as well as many other important settings.

While all users need security to access activities, only some clinicians will need records that reflect their medical training. These are the kind of clinicians that will directly document in a patient’s chart, be scheduled (or assigned) to care for patients, and do other clinical tasks based on the training they have gotten.

Question 61

Who needs a provider record?

Answer 61

A person or resource (non-human provider) will need a provider record if at least one of the following criteria is met:

Scheduled with patients
Completes clinical documentation/has credentials
Authorizing provider
Referrals to/from

Use the acronym SCAR to remember who or what needs one. Your clinical users will need both a provider (SER) record and appropriate security to complete certain tasks such as ordering a medication.

Question 62

User Templates

Answer 62

Everyone at your organization who logs in to Epic will need a user (EMP) record. However, user records also control many more settings. To help be efficient with user build, there is another type of record in the EMP master file called a user template.

User templates, or linkable templates, are linked to user records (Sec Class, Roles, and User profile). They allow you to create a single record to maintain shared settings for multiple user records. User templates are created for a particular group of users based on their shared job responsibilities. Changing a user template changes all of the linked users. Having one record impact multiple users makes it much easier to maintain user records

Question 63

True or False: In the provider record, you can choose to link to either the corresponding user record or a user template.

Answer 63

False: you can only link a provider to a user record

Question 64

Which of the following is a setting made in an individual user record which cannot be set with user templates? Choose all that apply.
a. Default login department
b. Link to user template
c. EpicCare security class
d. ID/password
e. Reporting Workbench security class

Answer 64

A, B and D

Question 65

Who needs a user record at your organization?

Answer 65

Everyone at your organization who logs in to Epic

Question 66

Give an example of someone who would need a provider record but NOT a user record and explain why.

Answer 66

A physician in the community who gets referral from physicians, but who does not have access to log in to your Epic system

Question 67

Why do MRI machines and classrooms need to have records in the Provider master file?

Answer 67

MRI machines and classrooms are scheduled resources.

Question 68

Category Lists

Answer 68

A category list is a defined set of possible values for a particular item. With the example of Marital Status, the category list contains choices like Married, Divorced, and Widowed.

Category lists are used in the system for these purposes:

• Standardization of responses for reporting
• Typing time is reduced since you can select from category lists by completion matching
• Triggering other functionality in the system (for selected values)

As a builder, you will encounter three types of category lists, which differ in your ability to customize the list.
1. System
Some category lists are entirely controlled by Epic. In these cases, configuration in the software is driven by the values on that category list and should not be changed. The yes or no category list is one example. To make sure that the configuration continues to work properly, this list is not editable by customer organizations.

2. Extendible
   Some category lists are partially controlled by Epic, meaning certain values on the list are read-only. The Epic-reserved values on these category lists are used by configuration elsewhere in the system.

When working in the Category List Maintenance activity, you will know that a list is an extendible list when you see the Add New Category button but a message in the sidebar of “Release Range: Up to ##”, where ## could be any number: For example, the Gender Identity category list has 8 values controlled by Epic, with the possibility of up to 99. Administrators can add and edit other values on the list, but those IDs must be >99.

3. Customer
   Customer category lists are entirely controlled by your organization. Epic might have values loaded into the category list, but each organization can choose to add, remove, or change these values.

When working in the Category List Maintenance activity, you can identify a category list as customer-controlled when you see the Add New Category button but a message in the sidebar of “Release Range: All Custom”:

Question 69

How to find an Item # in Hyperspace

Answer 69

CTRL + Click in the item field

Question 70

How to find an Item # in Text

Answer 70

While in the item line Press Home + F8 (an info box appears with the information, press “enter” to get the box to disappear when you are finished)

Question 71

Which Masterfile is responsible for:
Needs to log in to Hyperspace

Answer 71

User (EMP)

Question 72

Which Masterfile is responsible for:
When residents access the SnapShot activity or the Summary activity, they should have access to a read-only view of all obstetric-related information on one page. It should appear to users as (your initials) OB Info.

Answer 72

Report (LRP)

Question 73

Which Masterfile is responsible for:
When documenting “Initial Prenatal visits for OB patients, the residents should see the <your>_T_OB_INITIAL_VISIT_RES navigator with one topic, <your>_Topic_OB_Initial_Visit_Res.</your></your>

Answer 73

Navigator (LVN)

Question 74

Which Masterfile is responsible for:
When seeing a patient in a clinic with an encounter type of “Initial Prenatal,” the following navigator should appear:

<your>_T_OB_INITIAL_VISIT_RES
The residents will have clinic visits of the encounter type "Routine Prenatal" the following navigator should appear:

T_MODEL_OB_CHARTING_RPV_MD
When seeing any patient in this clinic with an encounter type of "Office Visit" the following navigator should appear:

T_MODEL_MR_PROVIDER_OFFICE_VISIT
</your>

Answer 74

Workflow Engine Rule (LOR)

Question 75

Which Masterfile is responsible for:
These existing reports should always be available from the SnapShot or Summary:
18054-PATIENT SNAPSHOT (HTML/CSS)
75050-ED ENCOUNTER SUMMARY (PATIENT SUMMARY)
The residents will also find it helpful to have two shortcut buttons to the following reports:

18054-PATIENT SNAPSHOT (HTML/CSS)

<your> OB Info
</your>

Answer 75

Profile (LPR)

Question 76

Which Masterfile is responsible for:
Residents should be able to access a patient’s chart and use Order Entry. They should not be able to edit their own Order Sets.

Answer 76

Security Class (ECL)

Question 77

Which Masterfile is responsible for:
Should be set up to be designated as an ordering provider in the hospital but NOT as the authorizing provider for medication orders or procedure orders.

When marking the navigator sections as reviewed, the resident’s name should be followed by “MD.”

Answer 77

Provider (SER)

Question 78

Which Masterfile is responsible for:
Residents will spend a few weeks reading diagnostic images (x-rays) in the radiology department and a few weeks working in the emergency department (ED). When they log into the EMH X-Ray Imaging department, they should have the Reading Work List (the resulting tools for diagnostic studies) in their startup activities. When they log into the EMH Emergency Department, they should have the ED Track Board as their only startup activity.

When they log into all other departments, they should have the Schedule and Patient Lists as their startup activities.

Answer 78

Role (E2R)

Question 79

Which Masterfile is responsible for:
Upon logging in, they should have access to the same startup activities when logged into the same department. Once logged in, they should see the same clinical content within activities.

They should have access to:

In Basket, Reporting Workbench, and shared functionality
Clinical functionality
Hospital functionality
Imaging department functionality
Emergency department functionality

Answer 79

User Template (EMP)

Question 80

Are print groups shared between the SnapShot and Sidebar reports?

Answer 80

Yes! Immunizations/Injections, Specialty Comments, Reminders and Results

Question 81

A report is a collection of individual _________________. Choose only ONE answer.
Flowsheets
Print Groups
SmartTexts
Smart Data Elements

Answer 81

B. Print Groups

Question 82

What activity should an end user use to view the names and ID numbers of print groups in Hyperspace? Choose only ONE answer.
Reporting Workbench
Print Group Information
Session Information Report
Record Viewer

Answer 82

C. Session Information Report

Question 83

True or False: You should always create a copy of existing records to make changes for your users.

Answer 83

False. When all users who use that record need the change, you should edit the existing record whenever possible

Question 84

What is a compiled profile?

Answer 84

It represents the collection of profile settings that will impact a user.

Question 85

Based on compiling profiles, what do you think is the most efficient level to start profile build and why?

Answer 85

The most general level in the hierarchy to make settings that will apply to the most people.

Question 86

True or False: The profile controls access to activities in Hyperspace.

Answer 86

False. The profile controls the options available within activities.

Question 87

Pharmacists, pharmacy techs, and pharmacy managers all work in the same department, but each have different security classes. The pharmacy managers need a different set of Chart Review tabs than other users. At which level of profile should you configure these Chart Review tabs for them? Choose only ONE answer.
a. EpicCare Security Class
b. Department
c. Revenue Location
d. EMR System Definitions

Answer 87

A. The pharmacy managers should get their reports from an EpicCare security class profile because they all share a login department and thus all other profile levels listed with other users.

Question 88

A user logs in and is affected by two profiles: a department level and an EMR System Definitions level. When the two both have values for the same items, which profile level’s values will the user see? Choose only ONE answer.
a. Department
b. EMR System Definitions
c. They will see values from both profiles.

Answer 88

The more specific level profile settings will override the more general. The department profile’s values would override the System Definitions profile’s values.