CLN 251/252 Flashcards

Question

Profiles (LRP)

Answer 1

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.

Answer 2

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.

Answer 3

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.

Answer 4

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?

Answer 5

Make the right changes for the users who need them. Don't make changes for users who don't need them.

Answer 6

**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 visi**t: 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

Answer 7

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.

Answer 8

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

Answer 9

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.

Answer 10

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.

Answer 11

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

Answer 12

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.

Answer 13

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.

Answer 14

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

Answer 15

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

Answer 16

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.

Answer 17

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

Answer 18

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.

Answer 19

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

Answer 20

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.

Answer 21

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

Answer 22

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.

Answer 23

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

Answer 24

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!

Answer 25

False, in the Navigator masterfile (LVN)

Answer 26

The end user as as topic in the navigators template

Answer 27

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.

Answer 28

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

Answer 29

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

Answer 30

In the user (EMP) template

Answer 31

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.

Answer 32

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.

Answer 33

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.

Answer 34

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.

Answer 35

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

Answer 36

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

Answer 37

A, B and D

Answer 38

Everyone at your organization who logs in to Epic

Answer 39

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

Answer 40

MRI machines and classrooms are scheduled resources.

Answer 41

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":

Answer 42

CTRL + Click in the item field

Answer 43

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)

Answer 44

User (EMP)

Answer 45

Report (LRP)

Answer 46

Navigator (LVN)

Answer 47

Workflow Engine Rule (LOR)

Answer 48

Profile (LPR)

Answer 49

Security Class (ECL)

Answer 50

Provider (SER)

Answer 51

Role (E2R)

Answer 52

User Template (EMP)

Answer 53

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

Answer 54

B. Print Groups

Answer 55

C. Session Information Report

Answer 56

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

Answer 57

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

Answer 58

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

Answer 59

False. The profile controls the options available within activities.

Answer 60

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.

Answer 61

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

CLN 251/252 Flashcards

(88 cards)