2
Beaker Clinical Pathology Administration CPL250(Lab350 &
|| || || || ||
Lab400) Exam with verified detailed answers
|| || || || || ||
Interface Engine - ✔✔Has powerful tools for manipulating interface messages
|| || || || || || || || ||
Middle Tier Device - ✔✔Helps route interface messages to appropriate instrument.
|| || || || || || || || || || ||
Typically one per organization || || ||
An advance framework for managing interfaces with third party systems called... -
|| || || || || || || || || || || ||
✔✔Bridges
Triggers - ✔✔Applications that cause an event to happen (Some are hard coded, and some
|| || || || || || || || || || || || || || ||
are configurable based on workflow)
|| || || ||
Mapping - ✔✔Decides how values should be interpreted on an interface
|| || || || || || || || || ||
Translation table - ✔✔Takes a value and translates it to another value
|| || || || || || || || || || ||
Identity - ✔✔Framework used for mapping master file records on interfaces
|| || || || || || || || || ||
Facility (Chapter 2.3) - ✔✔The most general, all-encompassing level in Epic and refers to
|| || || || || || || || || || || || || ||
an entire organization or enterprise. (Backbone of the admin build)
|| || || || || || || || ||
Levels on which Beaker CP facility structure is organized... - ✔✔Facility (LDF)-
|| || || || || || || || || || ||
>Laboratory->Section
,2
Overall facility structure - ✔✔Facility (General)->Service area->Location->Department-
|| || || || || ||
>Room
->Bed(Specific)
HOD - ✔✔Hospital Outpatient Department. Used in areas that schedule patient
|| || || || || || || || || || ||
appointments and admitted patients || || ||
Virtual Departments - ✔✔Patients are not scheduled or admitted here
|| || || || || || || || ||
Outpatient Department - ✔✔Used in areas that only schedule patient appointments
|| || || || || || || || || ||
Hospital Unit - ✔✔Necessary for areas where patients are admitted ADT(Admission,
|| || || || || || || || || || ||
Discharge, and Transfer) || ||
Records for configuration hierarchy - ✔✔Test>Lab>Facility. This means that to find
|| || || || || || || || || || ||
specific settings, the system will look to the test record first, then the laboratory record, and
|| || || || || || || || || || || || || || || ||
finally the facility record.
|| || ||
Receiving extensions (2.7) - ✔✔Used to prevent lab techs from receiving specimens that do
|| || || || || || || || || || || || || ||
not meet certain criteria (i.e. missing information)
|| || || || || ||
Receiving behavior (2.7) - ✔✔Specify whether specimens should be received in their
|| || || || || || || || || || || ||
destination lab or into the lab you are logged into(this is the default and recommended
|| || || || || || || || || || || || || || ||
option)
TAT Basis (2.7) - ✔✔The TAT Basis field indicates how the turnaround time should be
|| || || || || || || || || || || || || || ||
calculated when a test is from one lab to another. || || || || || || || || || ||
, 2
1. First Received Instant (When the test is first received into the initial lab)
|| || || || || || || || || || || || ||
2. Last Received Instant (When the test is last received into the final lab)
|| || || || || || || || || || || || ||
Default Turnaround Time (TAT) Values - ✔✔The turnaround time you enter in the TAT
|| || || || || || || || || || || || || ||
field reflects the amount of time that can elapse before results are expected for tests of a
|| || || || || || || || || || || || || || || || ||
certain priority ||
Clinical Administration - ✔✔Set of text-based menus used to configure applications (mouse
|| || || || || || || || || || ||
does not work in this field)
|| || || || || ||
Admins utilize this || ||
Hyperspace - ✔✔Graphical user interface (GUI) Used to configure and perform end-user
|| || || || || || || || || || || ||
workflows
Clinical Administration & Hyperspace - ✔✔Through these two applications is how we see
|| || || || || || || || || || || || ||
chronicles (epic's database management system) || || || ||
Filing Cabinet - ✔✔Chronicles - Epic's database management system; like a filing cabinet ,
|| || || || || || || || || || || || || ||
where all the information is stored
|| || || || ||
Master file - ✔✔Drawer || || ||
Record - ✔✔File in the drawer || || || || ||
Contact - ✔✔A dated, or versioned, paper form
|| || || || || || ||
Beaker Clinical Pathology Administration CPL250(Lab350 &
|| || || || ||
Lab400) Exam with verified detailed answers
|| || || || || ||
Interface Engine - ✔✔Has powerful tools for manipulating interface messages
|| || || || || || || || ||
Middle Tier Device - ✔✔Helps route interface messages to appropriate instrument.
|| || || || || || || || || || ||
Typically one per organization || || ||
An advance framework for managing interfaces with third party systems called... -
|| || || || || || || || || || || ||
✔✔Bridges
Triggers - ✔✔Applications that cause an event to happen (Some are hard coded, and some
|| || || || || || || || || || || || || || ||
are configurable based on workflow)
|| || || ||
Mapping - ✔✔Decides how values should be interpreted on an interface
|| || || || || || || || || ||
Translation table - ✔✔Takes a value and translates it to another value
|| || || || || || || || || || ||
Identity - ✔✔Framework used for mapping master file records on interfaces
|| || || || || || || || || ||
Facility (Chapter 2.3) - ✔✔The most general, all-encompassing level in Epic and refers to
|| || || || || || || || || || || || || ||
an entire organization or enterprise. (Backbone of the admin build)
|| || || || || || || || ||
Levels on which Beaker CP facility structure is organized... - ✔✔Facility (LDF)-
|| || || || || || || || || || ||
>Laboratory->Section
,2
Overall facility structure - ✔✔Facility (General)->Service area->Location->Department-
|| || || || || ||
>Room
->Bed(Specific)
HOD - ✔✔Hospital Outpatient Department. Used in areas that schedule patient
|| || || || || || || || || || ||
appointments and admitted patients || || ||
Virtual Departments - ✔✔Patients are not scheduled or admitted here
|| || || || || || || || ||
Outpatient Department - ✔✔Used in areas that only schedule patient appointments
|| || || || || || || || || ||
Hospital Unit - ✔✔Necessary for areas where patients are admitted ADT(Admission,
|| || || || || || || || || || ||
Discharge, and Transfer) || ||
Records for configuration hierarchy - ✔✔Test>Lab>Facility. This means that to find
|| || || || || || || || || || ||
specific settings, the system will look to the test record first, then the laboratory record, and
|| || || || || || || || || || || || || || || ||
finally the facility record.
|| || ||
Receiving extensions (2.7) - ✔✔Used to prevent lab techs from receiving specimens that do
|| || || || || || || || || || || || || ||
not meet certain criteria (i.e. missing information)
|| || || || || ||
Receiving behavior (2.7) - ✔✔Specify whether specimens should be received in their
|| || || || || || || || || || || ||
destination lab or into the lab you are logged into(this is the default and recommended
|| || || || || || || || || || || || || || ||
option)
TAT Basis (2.7) - ✔✔The TAT Basis field indicates how the turnaround time should be
|| || || || || || || || || || || || || || ||
calculated when a test is from one lab to another. || || || || || || || || || ||
, 2
1. First Received Instant (When the test is first received into the initial lab)
|| || || || || || || || || || || || ||
2. Last Received Instant (When the test is last received into the final lab)
|| || || || || || || || || || || || ||
Default Turnaround Time (TAT) Values - ✔✔The turnaround time you enter in the TAT
|| || || || || || || || || || || || || ||
field reflects the amount of time that can elapse before results are expected for tests of a
|| || || || || || || || || || || || || || || || ||
certain priority ||
Clinical Administration - ✔✔Set of text-based menus used to configure applications (mouse
|| || || || || || || || || || ||
does not work in this field)
|| || || || || ||
Admins utilize this || ||
Hyperspace - ✔✔Graphical user interface (GUI) Used to configure and perform end-user
|| || || || || || || || || || || ||
workflows
Clinical Administration & Hyperspace - ✔✔Through these two applications is how we see
|| || || || || || || || || || || || ||
chronicles (epic's database management system) || || || ||
Filing Cabinet - ✔✔Chronicles - Epic's database management system; like a filing cabinet ,
|| || || || || || || || || || || || || ||
where all the information is stored
|| || || || ||
Master file - ✔✔Drawer || || ||
Record - ✔✔File in the drawer || || || || ||
Contact - ✔✔A dated, or versioned, paper form
|| || || || || || ||
