TED300 - Training Environment Build
Epic TED Exam Review Questions and
Answers 100% Pass
David Mungai [Date] [Course title]
,TED300 - Training Environment Build
Epic TED Exam Review Questions
and Answers 100% Pass
Pool Rooms
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
1. To be in control of changes trainees see
2. Re-usability
3. Stability
4. Safety - no real patient data
Production Stream Environments
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
1. Standard list of values for a specific Item
(ex marital status)
Training Environment Structure
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)
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)
, 1. Where analysts do the build
2. Then move to TST for testing
MST (Master Train)
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?
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?
A combination of Data Courier and Manual Build
MST- What happens to MST when and Upgrade happens?
1. All build (training and analyst) remains, but MST is on a newer
version of Epic
Dynamic Data Wipe
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)
1. Environment end users log into at go-live and beyond
REF (Refresh)
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
Epic TED Exam Review Questions and
Answers 100% Pass
David Mungai [Date] [Course title]
,TED300 - Training Environment Build
Epic TED Exam Review Questions
and Answers 100% Pass
Pool Rooms
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
1. To be in control of changes trainees see
2. Re-usability
3. Stability
4. Safety - no real patient data
Production Stream Environments
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
1. Standard list of values for a specific Item
(ex marital status)
Training Environment Structure
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)
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)
, 1. Where analysts do the build
2. Then move to TST for testing
MST (Master Train)
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?
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?
A combination of Data Courier and Manual Build
MST- What happens to MST when and Upgrade happens?
1. All build (training and analyst) remains, but MST is on a newer
version of Epic
Dynamic Data Wipe
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)
1. Environment end users log into at go-live and beyond
REF (Refresh)
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
