LAB400 EPIC EXAM Questions and
Answers Latest Updates 2025 TOP
GRADED A+
What controls where you can use a rule? Choose only one answer. - ANSWER -Rule Context
What does rule evaluation logic control? Choose all that apply. - ANSWER -How conditions are
grouped
Which conditions need to be true for the rule to be true
What is true about the rule tester? Choose all that apply. - ANSWER -It only allows records that
meet the context of the rule
It shows if each condition passes or fails
It shows if the rule passed or failed as a whole
Khalil, an analyst at your organization, has built a new lab specimen context rule that has a true
statement of, "this rule should evaluate to true for blood specimens in either red top plain or SST
containers that were collected over 1 week ago". Based on the parameters that Khalil has
entered for this new rule, and the rule's true statement, how should Khalil set up the evaluation
logic for this rule? - ANSWER -1 and 2 and (3 or 4)
You are reviewing Khalil's rule, and although it will work as intended, you believe Khalil could
have built his rule more efficiently. What could Khalil change to achieve a more efficient rule
build? Chose only one answer. - ANSWER -He could delete one of his Specimen Type
parameters and add the value that was listed in it to his other Specimen Type parameter.
You are trying to link a rule to determine the turnaround time (TAT) for specimens in your lab.
However, you cannot link your rule to this field. What might be causing this issue? Choose only
ONE answer. - ANSWER -The rule you are trying to link has the wrong rule context.
System - ANSWER -The system automatically applies these holds based on defined events
and rules.
The system automatically clears these holds when the evaluation of the rule changes.
,Users with the appropriate security can also clear these holds manually.
User - ANSWER -Users apply these holds manually through the Holds activity.
Users clear these holds manually.
Creating a new hold involves the following steps: - ANSWER -Create a value on the Holds
category list (LDF 51860).
Define the hold in the Beaker facility record (LDF 1) on the Holds Definitions form.
, Create a rule in the Rule Editor.
Attach the hold at any level of the hierarchy to automatically apply it using an event and a rule.
The system searches the following records: Test (OVT) > Laboratory (LDF) > Beaker Facility
(LDF 1).
User holds only need steps 1&2, because users decide when to apply the hold.
System Category List - ANSWER -Uneditable, controlled by Epic. Release Range: All
Categories
Extendible Category List - ANSWER -These category lists are partially controlled by Epic,
meaning certain values on the list are uneditable. The Epic-reserved values on these category
lists are used by configuration elsewhere in the system.
Customer Category List - ANSWER -These category lists are entirely controlled by the
customer organization. Epic might have values loaded into the category list, but each
organization can choose to add, remove, or change these values on its own.
Hard Hold - ANSWER -Prevents specimen processing.
Warning (delta) - ANSWER -Presents a warning and requires acknowledgement, but does not
prevent user from verifying.
FYI - ANSWER -Does not present a warning or prevent specimen processing. Used to record
additional information about patient or specimen.
Persistence - ANSWER -Controls whether a hold must be cleared by a user (persistent) or
whether it can be cleared by a background job (not persistent)
Batching - ANSWER -Controls if a test with this hold can be added to batches
Outstanding List (O.L.) - ANSWER -Controls if a test with this hold appears on the Outstanding
List (this can be overridden in the Outstanding List report settings)
Answers Latest Updates 2025 TOP
GRADED A+
What controls where you can use a rule? Choose only one answer. - ANSWER -Rule Context
What does rule evaluation logic control? Choose all that apply. - ANSWER -How conditions are
grouped
Which conditions need to be true for the rule to be true
What is true about the rule tester? Choose all that apply. - ANSWER -It only allows records that
meet the context of the rule
It shows if each condition passes or fails
It shows if the rule passed or failed as a whole
Khalil, an analyst at your organization, has built a new lab specimen context rule that has a true
statement of, "this rule should evaluate to true for blood specimens in either red top plain or SST
containers that were collected over 1 week ago". Based on the parameters that Khalil has
entered for this new rule, and the rule's true statement, how should Khalil set up the evaluation
logic for this rule? - ANSWER -1 and 2 and (3 or 4)
You are reviewing Khalil's rule, and although it will work as intended, you believe Khalil could
have built his rule more efficiently. What could Khalil change to achieve a more efficient rule
build? Chose only one answer. - ANSWER -He could delete one of his Specimen Type
parameters and add the value that was listed in it to his other Specimen Type parameter.
You are trying to link a rule to determine the turnaround time (TAT) for specimens in your lab.
However, you cannot link your rule to this field. What might be causing this issue? Choose only
ONE answer. - ANSWER -The rule you are trying to link has the wrong rule context.
System - ANSWER -The system automatically applies these holds based on defined events
and rules.
The system automatically clears these holds when the evaluation of the rule changes.
,Users with the appropriate security can also clear these holds manually.
User - ANSWER -Users apply these holds manually through the Holds activity.
Users clear these holds manually.
Creating a new hold involves the following steps: - ANSWER -Create a value on the Holds
category list (LDF 51860).
Define the hold in the Beaker facility record (LDF 1) on the Holds Definitions form.
, Create a rule in the Rule Editor.
Attach the hold at any level of the hierarchy to automatically apply it using an event and a rule.
The system searches the following records: Test (OVT) > Laboratory (LDF) > Beaker Facility
(LDF 1).
User holds only need steps 1&2, because users decide when to apply the hold.
System Category List - ANSWER -Uneditable, controlled by Epic. Release Range: All
Categories
Extendible Category List - ANSWER -These category lists are partially controlled by Epic,
meaning certain values on the list are uneditable. The Epic-reserved values on these category
lists are used by configuration elsewhere in the system.
Customer Category List - ANSWER -These category lists are entirely controlled by the
customer organization. Epic might have values loaded into the category list, but each
organization can choose to add, remove, or change these values on its own.
Hard Hold - ANSWER -Prevents specimen processing.
Warning (delta) - ANSWER -Presents a warning and requires acknowledgement, but does not
prevent user from verifying.
FYI - ANSWER -Does not present a warning or prevent specimen processing. Used to record
additional information about patient or specimen.
Persistence - ANSWER -Controls whether a hold must be cleared by a user (persistent) or
whether it can be cleared by a background job (not persistent)
Batching - ANSWER -Controls if a test with this hold can be added to batches
Outstanding List (O.L.) - ANSWER -Controls if a test with this hold appears on the Outstanding
List (this can be overridden in the Outstanding List report settings)
