EPIC PRELUDE STUDY GUIDE
1.Ch. 2 - Facility Structure Over view:
2.Make sure you can define the following key terms:: p. 2*3
3.Facility:
4.Service Area:
5.Revenue Location:
6.Unit/Department:
7.Rule of Specificity: The system will use most specific setting_If a
setting is not found at the most specific setting, _the system looks to
the next most specifiy setting
8.Facility Structure: P 2*3
9.facility (EAF):
10.Service Area (EAF): records that represents separate businesses
within the organization (have AR)
11.Revenue Location (EAF): Location exist within the service area
12.Depts/Unit (DEP): Places where pts receive care and staff log in
13.Ch. 3 - Forms and Workflows:
14.What is the quickest way to find the ID of a subflow?: record viewer
15.Ch. 4 - Item Profiles and Defaults:
16.Finding the INI and Item Number in Hyperspace: Control + left click in
the field
17.:
18.Ch. 5 - Rule Basics: P. 5*3
19.Define Property, Operator, Value, Property Tree, Evalution Logic: P. 5*4
20.Ch. 6 - Workflow Confirmation Records:
21.The Confirmation Record: P. 6*10 (important)
22.The Finished Comfirmation Record: P. 6*10 (important)
23.Which screen allows you to create a hylerlink to the form where users
can fix the error?: In Text - Confirmation Hyperlink Specification
24.Items not stored in EPT, EAR, CVG - cannpt be required items:
25.Confirmation Record: P. 6*3
26.Validation Extension P. 6*6: The Patient Validation Extensions field
allows you to specify extensions that perform error checking.
27.: An extension is a bit of code that is saved in an Extension record
(LPP master file). Extensions are created by Epic development staff. In
this scenario, extensions perform more complex error checking.
Extensions are used across Epic applications to perform different
activities; they are not limited to just error checking.
28.Ch. 7 - Verification Confirmation Records:
29.Verification Statuses: P 7*7 - P7*8
1/
6
, EPIC PRELUDE STUDY GUIDE
30.P. 7*11 - P7*17 IMPORTANT:
31.Verification record: P. 7*3
32.Statuses: P. 7*7
2/
6
1.Ch. 2 - Facility Structure Over view:
2.Make sure you can define the following key terms:: p. 2*3
3.Facility:
4.Service Area:
5.Revenue Location:
6.Unit/Department:
7.Rule of Specificity: The system will use most specific setting_If a
setting is not found at the most specific setting, _the system looks to
the next most specifiy setting
8.Facility Structure: P 2*3
9.facility (EAF):
10.Service Area (EAF): records that represents separate businesses
within the organization (have AR)
11.Revenue Location (EAF): Location exist within the service area
12.Depts/Unit (DEP): Places where pts receive care and staff log in
13.Ch. 3 - Forms and Workflows:
14.What is the quickest way to find the ID of a subflow?: record viewer
15.Ch. 4 - Item Profiles and Defaults:
16.Finding the INI and Item Number in Hyperspace: Control + left click in
the field
17.:
18.Ch. 5 - Rule Basics: P. 5*3
19.Define Property, Operator, Value, Property Tree, Evalution Logic: P. 5*4
20.Ch. 6 - Workflow Confirmation Records:
21.The Confirmation Record: P. 6*10 (important)
22.The Finished Comfirmation Record: P. 6*10 (important)
23.Which screen allows you to create a hylerlink to the form where users
can fix the error?: In Text - Confirmation Hyperlink Specification
24.Items not stored in EPT, EAR, CVG - cannpt be required items:
25.Confirmation Record: P. 6*3
26.Validation Extension P. 6*6: The Patient Validation Extensions field
allows you to specify extensions that perform error checking.
27.: An extension is a bit of code that is saved in an Extension record
(LPP master file). Extensions are created by Epic development staff. In
this scenario, extensions perform more complex error checking.
Extensions are used across Epic applications to perform different
activities; they are not limited to just error checking.
28.Ch. 7 - Verification Confirmation Records:
29.Verification Statuses: P 7*7 - P7*8
1/
6
, EPIC PRELUDE STUDY GUIDE
30.P. 7*11 - P7*17 IMPORTANT:
31.Verification record: P. 7*3
32.Statuses: P. 7*7
2/
6
