







Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Community
Ask the community for help and clear up your study doubts
Discover the best universities in your country according to Docsity users
Free resources
Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors
A comprehensive overview of the various components and best practices for configuring and managing an epic training environment. It covers the facility structure hierarchy, user and provider records, security-related records, and the different types of training environments (mst, ref, prep, ace, ply, exam). The document also discusses the importance of a training environment, the steps involved in building and maintaining it, and the tools and resources available to support the process. It addresses common issues that can arise in the mst environment and provides guidance on how to resolve them. Overall, this document serves as a valuable reference for epic administrators and trainers responsible for setting up and maintaining an effective training environment to support user education and skill development.
Typology: Exams
1 / 13
This page cannot be seen from the preview
Don't miss anything!
User Role - ANS-What controls the Startup Activities a user sees when logging in to Hyperspace? Mitosis - ANS-Tool that duplicates patients daily and keeps them looking fresh for training Manual Duplication - ANS-Tool used to move your patients through time to make encounters appear over the course of time Chronicles - ANS-The database management system used by all of Epic's applications Master Files - ANS-Holds information about a particular type of data and designated by a three- letter abbreviation or INI Records - ANS-Holds information about a particular data entity and has a unique identification number Contacts - ANS-Holds date-specific information about a particular data entity allowing you to keep track of changes over time Items - ANS-Hold discrete pieces of information (question)
Values - ANS-Discrete information stored in response to prompts in Epic (answer) Facility Structure - ANS-Represents physical arrangements of your organization's hospitals, clinics, units, departments, and business entities. Facility - ANS-Highest level of the facility structure hierarchy and each organization can only have one Service Area - ANS-Used to separate distinct business entities within an organization Parent Revenue Location - ANS-Used to group multiple revenue locations together for billing purposes Revenue Locations - ANS-Represent the hospitals and clinics within your organization and are generally physical locations where revenue is generated Departments or Units - ANS-Represent places where users work and patients receive care Rooms - ANS-Allows you to restrict the level of privacy and available services offered and is when a patient needs to be admitted but not yet assigned to a bed Beds - ANS-Used to track patient movement once they are admitted Rule of Specificity - ANS-If a setting is configured at multiple levels of the setting's hierarchy, the most specific level setting is used. If nothing is set at that level, the system looks to the next most specific level's setting User records - ANS-Used by anyone who will log in to Epic at your organization and determines what a person can see or do in Epic, including which activities are available for the user, the layout of Hyperspace and the default login department Provider records - ANS-Required for any person or resource that meets the CARS criteria: Credentials, Authorizations, Referrals, Schedules Security-related records - ANS-Considered to be the keys for users to access specific activities Security class - ANS-Group of security points which gives users access to every piece of functionality they need. User role - ANS-Determines the look and feel of Hyperspace for a user by controlling the home workspace that appears when the user logs in and the application toolbar options that are available.
Dynamic records - ANS-Created by end users as they follow workflows Orders, Inbasket messages, patients - ANS-Examples of dynamic records Static data, including facility structure, procedures, medications, providers, users, contact types, forms and form groups - ANS-What remains in MST after the dynamic data wipe? Manual and automatic build migration - ANS-To keep MST workflows in sync with TST and PRD, your organization will use a combination of: Analyst or build team - ANS-Who updates MST manually? Data Courier - ANS-Data migration tool used to move static build from your POC environment to your TST environment for testing and then to PRD To prepare for ways it can change records in your training and be aware of what data is moving into MST and when - ANS-As a Principal Trainer, why do you need to understand how Data Courier works? Static data; Dynamic data - ANS-Data Courier can move _____ but cannot move _____. Training team representatives - ANS-Who should attend change control meetings? Upgrade, Refresh, or Rebuild - ANS-MST maintenance options Upgrade - ANS-Changing MST to a newer version of Epic Refresh - ANS-Use Data Courier and manual build to bring MST in sync with production Rebuild - ANS-Erase the existing MST environment, create a new copy of MST from TST or PRD Broken or missing environment configuration. Broken or incorrect patients. Environment performance issues. - ANS-MST core problems usually stem from one of three sources: Environment build issue - ANS-Use Data Courier or manual build to fix application these issues Patient build issue - ANS-Fix problematic patients and re-duplicate if necessary for these type of issues Mitosis performance issue - ANS-Review and revise Mitosis spreadsheets and Mitosis start times for these issues Severing the link between MST and REF environment but linking one ACE environment directly to MST - ANS-Before beginning an upgrade, refresh or rebuild, Epic recommends:
Reusability, stability, and safety - ANS-What are the three main reasons you need a training environment? No, you can apply an upgrade directly to your existing MST build without rebuilding the entire environment - ANS-Do you have to totally rebuild MST to apply an upgrade? To avoid conflicts, you should only train out of an environment used only for training, so an ACE. All ACE environments contain the same content, so you can use them interchangeably. - ANS-Your organization has a large wave of classes for a specific role coming up and will be training this role multiple times in a single day. You typically train out of ACE 3. What other environments could you train out of without disruption? During an upgrade, the code in the environment is upgraded, enabling new features and potentially changing the look and feel of the software to greater or lesser extents. All of your organization's configuration AND your training build remains afterwards. It does NOT need to be rebuilt with each upgrade. - ANS-What happens when your organization upgrades MST? Data Courier will either overwrite your build if the items/master file has not been locked down by your DC admin or the update will just not come over to MST and is blocked. - ANS-You have modified a procedure record in MST to fit the needs of your training program. Which of the following will happen when your analyst moves a modification to this procedure from TST to MST again using Data Courier? Cookbooks - ANS-Used as a tool to guide you through the process of training environment build. Training Wheels Application Cookbook - ANS-Detailed list of application-specific environment tasks, and steps to complete the tasks. Training Coordination Cookbook - ANS-Detailed list of cross-application environment build tasks, and steps to complete the tasks and is shared by all PTs on a training team. Patient Build Documentation - ANS-Detailed instructions for completing patient build for lesson plans Pre-copy tasks tab - ANS-Contains a list of tasks in the application cookbook that need to be completed before building in the MST environment Users and Patient Info tab - ANS-Tables of user, patient, department, and ACE planning information in the application cookbook that helps to calculate the number of duplicates you will need and provides a place to keep track of your patient build progress ANN and ANN-Specialist tabs - ANS-A list of unique names and IDs in the application cookbook for all users and patients you will need to create when you build your training environment
building master patients; end users to log in for training - ANS-Historical build users are used for _____, and training users are used for ______. You will indicate you are finished on the Tasks Signoff Tab of the Training Coordination Cookbook. - ANS-How will the Facility Structure Coordinator know that you have filled out your portion of the Master Room and Department tab? A pool room allows for many training patients to be admitted to the same room. Using training built pool rooms also prevents needing to make changes to the real rooms and beds. - ANS- Explain why you need pool rooms to be added by the Facility Structure Coordinator for the admitted patients for your app. Any person who logs in to Hyperspace - ANS-Who needs a record in the User (EMP) master file? Any person or resource who meets on or more specific criteria. - ANS-Who needs a record in the Provider (SER) master file? Credentials, Authorizes, Referrals, and Schedules (CARS) - ANS-What are the criteria that must be met for a provider (SER) record? .xml - ANS-What type of file must the User Duplicator be in for the text utility to function properly? paste values - ANS-Whenever you copy from the cookbook, always use ______ so it does not bring formulas and formatting that you do not want. Fatal Errors - ANS-When using the User Duplicator what must be fixed before duplication can occur? Non-fatal Errors - ANS-When using the User Duplicator what can occur but still allow duplication? your personal login - ANS-When testing materials it is critical to not use _____ because it might have different access and tools than the user a trainee will use in class A user record is a record in the User (EMP) master file in chronicles that determines how and where a user logs in, and what access they have within Hyperspace. A provider record is a record in the Provider (SER) master file in chronicles required for certain people and resources associated with your organization. - ANS-Explain the difference between a user record and a provider record Historical Build User - ANS-What type of user do you log in as when creating historical clinical encounters in a patient's chart?
You can find the User Duplicator under the Training Tools menu in Text - ANS-Where can you find the User Duplicator in Text? True. Physicians need access to functionality that comes with the provider record (SER), such as being scheduled with patients. - ANS-T/F: Your physician training users need to have a linked provider (SER) record. False. Non-fatal errors can be skipped if they do not impact your final build. - ANS-T/F: When running your User Duplicator spreadsheet, all non-fatal errors must be fixed for users to duplicate correctly. Copying a master patient - ANS-How are training patients created? Zz + app abbreviation + master - ANS-What is the master patient naming convention for the patient's last name? One - ANS-How many master patients are there for each unique scenario? Manual build, teleportation, and teleportation with additional manual build - ANS-What are the three methods for creating master patients? Publishes instructions for building the master patient - ANS-For any patient that are unable to be teleported with Scott, what does Epic do? Create spinoff patients - ANS-If you have two patients who look almost identical to a point, but require different documentation for their scenarios what can you do? A capital letter at the beginning of the first and last names - ANS-When you create a patient with Manual Patient Duplication, the system will only accept names with: Date sliding - ANS-This allows you to move duplicate patients forward or backward in time to help you build out their history. Duplicating - ANS-You can only date slide when: Step patients - ANS-Duplicate patients used to create a patient with a robust history are called Principles of date sliding - ANS-1. Always begin with the oldest encounters and build to the newest.
Ignore - ANS-Scotty always accepts what it initially suggested when you click dynamic; static - ANS-Scotty can move _____ records but cannot move _____ records. Soft-deleted records - ANS-Records that are retired from use, but still exist in your system for historical purposes Test the curriculum that uses the patient - ANS-After you have imported your Scotty patient, how would you test to make sure that the mappings were correct? Rename or delete the current master patient, re-import the .ept and update mappings, and test the new master patient - ANS-What would you do to fix mistakes made in teleportation? Same version - ANS-If you rebuild MST, make sure you're exporting patients on the _____ _____ you'll be importing them Epic .ept files can be found in your Training Wheels package in the Training Environment Build folder. You can also search for them directly on Galaxy. - ANS-Where can you find Epic-built .ept files? The source environment is the environment where a patient was exported from, resulting in an .ept file. The target environment is where Scotty will create a patient using the .ept file. - ANS- Describe the difference between a source and target environment False. .ept files are XML exports of patient data and should not be manipulated directly as it could cause corruption - ANS-T/F: You can and should open and modify .ept files directly to make changes to patient details False. EPTs generated on one version of Epic should only be used with environments on that version of Epic. - ANS-T/F: An EPT file generated from a source environment on Epic 2015 can safely be used with a target environment on 2018 Order Snipper - ANS-This tool is used to disassociate order from a patient. Delete Notes - ANS-This utility can be used to completely disassociate a note from a patient's chart. Patient age and sex, historical encounters, and diagnosis - ANS-If you're editing an existing master patient, what are some patient details that Epic recommends you do NOT change? Ordering & administering medications, adding problems to the problem list, flowsheet documentation, procedural documentation, etc. - ANS-What are some examples of clinical documentation updates that require date sliding? Reasons for using Mitosis - ANS-1. Utility for duplicating multiple master patients at once.
False. To a department not used in training - ANS-T/F: Master patients should be admitted into the same department as your training patients. Issues are the differences between the source environment and the target environment - ANS- Why does Scotty find "issues?" Ignore, Autogenerate, or Verify - ANS-How do you fix an issue found by Scotty when teleporting a patient? True. It could create clinical inaccuracies visible to end users - ANS-T/F: You should not manually edit the patient sex or age of a master patient teleported in from Epic. False. It is only necessary for time-sensitive changes - ANS-T/F: Regardless of what level change is needed to a master patient, you must slide the master patient back to today, make the changes, and slide the patient back to the same date in the future. Manual Duplication (single & copy/paste) & Mitosis (run & load) - ANS-What are the different types of patient duplication methods? False. Some will use Manual Duplication - ANS-T/F: Every application uses Mitosis to duplicate patients for class. Open the rule and click the Usage button - ANS-How can you see where else a rule is used in a workqueue? Property, Operator and Value - ANS-What are the three parts of a rule