LAB400 Epic Exam Questions & Answers
Epic Print Service - ANSWER -Facilitates transfer of data between Epic and physical printers
Often handled by client systems team
Device (EPR) - ANSWER -1 per label printer
Represents an individual printer in Epic
Workstation (LWS) - ANSWER -1 per label printer
Defines device as a label printer
Label Printer Setup (RXD 1) - ANSWER -List of all label printer workstation (LWS) records
Defines the label properties
Owned by Willow
To print to an actual label printer, you'd list Generic Printer in the - ANSWER -Device Type
field.
What kind of record did you pull into the Printer field? - ANSWER -Device (EPR)
To automatically print a label, what does the system need to know? - ANSWER -Label/Report
to print
Printer
Number of copies
When it should print
At which level of the hierarchy (test, performing lab, or Beaker facility) should you configure the
label setup? - ANSWER -Lab
,In any given record, you should map each printer class to - ANSWER -only one printer.
Which records could the system check to find print event setup when Susie accessions the
specimen? Choose ALL that apply. - ANSWER -EMH Hospital Lab laboratory (LDF) record
BMP test (OVT) record
Beaker facility (LDF 1) record
When a label printing event occurs in Beaker, which of the following records might Beaker
check for printing event configuration? Choose ALL answers that apply. - ANSWER -Test (OVT)
Laboratory (LDF)
Beaker Facility (LDF 1)
True or False: Print event setup in the Beaker facility record specifies the exact printer to be
used for specific types of labels. - ANSWER -False
A test will be resulted in the EMH Reference Lab, but the specimen is being collected in the
EMH Hospital Lab. Which record will be used to determine what labels should print? - ANSWER
-EMH Reference Lab, laboratory record
Which of the following records might the system search to translate a generic printer class to a
specific label printer device? Choose ALL answers that apply. - ANSWER -Workstation (LWS)
Department (DEP)
Location (EAF)
Property - ANSWER -Item in a record to test
Operator - ANSWER -=,<,>, Does Not Equal, Contains, etc.
Value - ANSWER -Specific response tested against
, Thinking about which dynamic record is used to store collection information, which rule context
should we use? - ANSWER -Lab Specimen Context
True statements - ANSWER -are a summary of all conditions in the rule. You should then
record the true statement in the description of the rule record in addition to any other helpful
information about the rule's purpose or function.
AND: - ANSWER -all conditions must be true for the rule to be true
OR: - ANSWER -any condition must be true for the rule to be true
NOT/AND NOT - ANSWER -all but <x> must be true for the rule to be true
custom evaluation logic, - ANSWER -you can use different logical operators together.
What important info is included in the help text for a rule field? - ANSWER -This typically
includes the context a rule must have to be linked here and the outcome if the rule evaluates to
true.
How are filter rules different from most other rules in Epic? - ANSWER -In filter rule fields, for
the action to occur, the rule must evaluate to false
Think about which dynamic record is used to store information regarding an organism that was
identified in a culture test. What should the context of your rule be? - ANSWER -Lab Result
Context
When does this property return "Yes" as its value? (Hint: read the help text for this property.) -
ANSWER -When the same organism has been previously identified for this patient within the
Lookback window
Think about which dynamic record is used to store a Pap interpretation. What should the
context of your rule be? - ANSWER -Lab Result Context
Rule cannot be linked - ANSWER -Make sure the rule context matches the context for the field.
Epic Print Service - ANSWER -Facilitates transfer of data between Epic and physical printers
Often handled by client systems team
Device (EPR) - ANSWER -1 per label printer
Represents an individual printer in Epic
Workstation (LWS) - ANSWER -1 per label printer
Defines device as a label printer
Label Printer Setup (RXD 1) - ANSWER -List of all label printer workstation (LWS) records
Defines the label properties
Owned by Willow
To print to an actual label printer, you'd list Generic Printer in the - ANSWER -Device Type
field.
What kind of record did you pull into the Printer field? - ANSWER -Device (EPR)
To automatically print a label, what does the system need to know? - ANSWER -Label/Report
to print
Printer
Number of copies
When it should print
At which level of the hierarchy (test, performing lab, or Beaker facility) should you configure the
label setup? - ANSWER -Lab
,In any given record, you should map each printer class to - ANSWER -only one printer.
Which records could the system check to find print event setup when Susie accessions the
specimen? Choose ALL that apply. - ANSWER -EMH Hospital Lab laboratory (LDF) record
BMP test (OVT) record
Beaker facility (LDF 1) record
When a label printing event occurs in Beaker, which of the following records might Beaker
check for printing event configuration? Choose ALL answers that apply. - ANSWER -Test (OVT)
Laboratory (LDF)
Beaker Facility (LDF 1)
True or False: Print event setup in the Beaker facility record specifies the exact printer to be
used for specific types of labels. - ANSWER -False
A test will be resulted in the EMH Reference Lab, but the specimen is being collected in the
EMH Hospital Lab. Which record will be used to determine what labels should print? - ANSWER
-EMH Reference Lab, laboratory record
Which of the following records might the system search to translate a generic printer class to a
specific label printer device? Choose ALL answers that apply. - ANSWER -Workstation (LWS)
Department (DEP)
Location (EAF)
Property - ANSWER -Item in a record to test
Operator - ANSWER -=,<,>, Does Not Equal, Contains, etc.
Value - ANSWER -Specific response tested against
, Thinking about which dynamic record is used to store collection information, which rule context
should we use? - ANSWER -Lab Specimen Context
True statements - ANSWER -are a summary of all conditions in the rule. You should then
record the true statement in the description of the rule record in addition to any other helpful
information about the rule's purpose or function.
AND: - ANSWER -all conditions must be true for the rule to be true
OR: - ANSWER -any condition must be true for the rule to be true
NOT/AND NOT - ANSWER -all but <x> must be true for the rule to be true
custom evaluation logic, - ANSWER -you can use different logical operators together.
What important info is included in the help text for a rule field? - ANSWER -This typically
includes the context a rule must have to be linked here and the outcome if the rule evaluates to
true.
How are filter rules different from most other rules in Epic? - ANSWER -In filter rule fields, for
the action to occur, the rule must evaluate to false
Think about which dynamic record is used to store information regarding an organism that was
identified in a culture test. What should the context of your rule be? - ANSWER -Lab Result
Context
When does this property return "Yes" as its value? (Hint: read the help text for this property.) -
ANSWER -When the same organism has been previously identified for this patient within the
Lookback window
Think about which dynamic record is used to store a Pap interpretation. What should the
context of your rule be? - ANSWER -Lab Result Context
Rule cannot be linked - ANSWER -Make sure the rule context matches the context for the field.
