TED300 QUESTIONS AND ANSWERS
Pool Rooms - Answers- 1. Records in master file that serve as "holding pens" for
admitted patients
2. They have a number of generic beds and Epic won't ask an end user to specify which
one the patient is in
Training Environment - 3 Main Reasons you need one - Answers- 1. To be in control of
changes trainees see
2. Re-usability
3. Stability
4. Safety - no real patient data
Production Stream Environments - Answers- 1.POC (analysts build) --> TST
2. (POC moved to TST to make sure everything works -
3. MST and PRD-->or PRD to MST
Category List Address - Answers- 1. Standard list of values for a specific Item
(ex marital status)
Training Environment Structure - Answers- 1. TST-->MST (regular Data Courier to keep
up to date)
2. MST-->REF (backup daily during install usually, weekly after that)
3. REF-->PREP (daily refresh of patients)
4. PREP-->ACEs and PLY
TST (Test) - Answers- 1. Contains all application build that will be migrated to the
Production (PRD) environment prior to go-live. (Ex Service areas, departments,
medications)
2. It is not refreshed, just a one-time copy to create the MST environment
POC (Proof of Concept) - Answers- 1. Where analysts do the build
2. Then move to TST for testing
MST (Master Train) - Answers- 1. Where all training specific build is done: master
patients, training users, additional rooms etc.
2. Never refreshed! rebuilt from scratch as needed, and kept up to date by using Data
Courier from TST or manual build where Data Courier is not available
3. It's an exact copy of the test environment
MST - Which environments can be copied to create MST? - Answers- 1. TST
2. PRD
TST is copied if organization is pre-live as PRD is not available to copy
Once live, PRD would be copied for any future MST rebuilds
, MST- How Will it Stay Updated? - Answers- A combination of Data Courier and Manual
Build
MST- What happens to MST when and Upgrade happens? - Answers- 1. All build
(training and analyst) remains, but MST is on a newer version of Epic
Dynamic Data Wipe - Answers- 1. Once MST is created, this removes all test patients
from MST
2. Gives a clean slate to start training environment build
3. Training master patients and user logins are then created by principal trainers in build
4. Takes what is in TST "static data" and then dynamic data wipe wipes out all orders or
other dynamic data
5. Delete all dynamic records before MST build begins
PRD (Production) - Answers- 1. Environment end users log into at go-live and beyond
REF (Refresh) - Answers- 1. Backup of MST in case of problems, also used for rebuil.
2. Refreshed daily during build/rebuild of MST, and weekly following go-live
PREP - Answers- Mitosis patient duplication for all patients in Mitosis Load
EXAM - Answers- 1. Trainees take EUPAS here.
2. Refreshed daily
ACE - Answers- 1. Actual Classroom Environment where end user training takes place.
2. Refreshed daily
PLY - Answers- 1. End user after-class practice.
2. Refreshed daily
Training Coordination Cookbook - Answers- 1. Overarching tasks, or those that need to
be coordinated.
2. Contains Day 0
3.Shared tasks
4.Historical Build Users
5.Master Room and Department
6. Patient Library
Historical Build Users - Answers- 1. Used to create realistic documentation as part of
Master patient build
2. Building or Editing master patients manually in MST you log in as a Historical Build
User
3.A list of all users/providers that principal trainers need to create in MST, and steps to
create these users.
4. Found in Training Coordination Cookbook
5. "Fake" names so your actual name does not appear in training environment
Pool Rooms - Answers- 1. Records in master file that serve as "holding pens" for
admitted patients
2. They have a number of generic beds and Epic won't ask an end user to specify which
one the patient is in
Training Environment - 3 Main Reasons you need one - Answers- 1. To be in control of
changes trainees see
2. Re-usability
3. Stability
4. Safety - no real patient data
Production Stream Environments - Answers- 1.POC (analysts build) --> TST
2. (POC moved to TST to make sure everything works -
3. MST and PRD-->or PRD to MST
Category List Address - Answers- 1. Standard list of values for a specific Item
(ex marital status)
Training Environment Structure - Answers- 1. TST-->MST (regular Data Courier to keep
up to date)
2. MST-->REF (backup daily during install usually, weekly after that)
3. REF-->PREP (daily refresh of patients)
4. PREP-->ACEs and PLY
TST (Test) - Answers- 1. Contains all application build that will be migrated to the
Production (PRD) environment prior to go-live. (Ex Service areas, departments,
medications)
2. It is not refreshed, just a one-time copy to create the MST environment
POC (Proof of Concept) - Answers- 1. Where analysts do the build
2. Then move to TST for testing
MST (Master Train) - Answers- 1. Where all training specific build is done: master
patients, training users, additional rooms etc.
2. Never refreshed! rebuilt from scratch as needed, and kept up to date by using Data
Courier from TST or manual build where Data Courier is not available
3. It's an exact copy of the test environment
MST - Which environments can be copied to create MST? - Answers- 1. TST
2. PRD
TST is copied if organization is pre-live as PRD is not available to copy
Once live, PRD would be copied for any future MST rebuilds
, MST- How Will it Stay Updated? - Answers- A combination of Data Courier and Manual
Build
MST- What happens to MST when and Upgrade happens? - Answers- 1. All build
(training and analyst) remains, but MST is on a newer version of Epic
Dynamic Data Wipe - Answers- 1. Once MST is created, this removes all test patients
from MST
2. Gives a clean slate to start training environment build
3. Training master patients and user logins are then created by principal trainers in build
4. Takes what is in TST "static data" and then dynamic data wipe wipes out all orders or
other dynamic data
5. Delete all dynamic records before MST build begins
PRD (Production) - Answers- 1. Environment end users log into at go-live and beyond
REF (Refresh) - Answers- 1. Backup of MST in case of problems, also used for rebuil.
2. Refreshed daily during build/rebuild of MST, and weekly following go-live
PREP - Answers- Mitosis patient duplication for all patients in Mitosis Load
EXAM - Answers- 1. Trainees take EUPAS here.
2. Refreshed daily
ACE - Answers- 1. Actual Classroom Environment where end user training takes place.
2. Refreshed daily
PLY - Answers- 1. End user after-class practice.
2. Refreshed daily
Training Coordination Cookbook - Answers- 1. Overarching tasks, or those that need to
be coordinated.
2. Contains Day 0
3.Shared tasks
4.Historical Build Users
5.Master Room and Department
6. Patient Library
Historical Build Users - Answers- 1. Used to create realistic documentation as part of
Master patient build
2. Building or Editing master patients manually in MST you log in as a Historical Build
User
3.A list of all users/providers that principal trainers need to create in MST, and steps to
create these users.
4. Found in Training Coordination Cookbook
5. "Fake" names so your actual name does not appear in training environment
