Siemens Advia Centralink Data Management System Networking Solution Operators Guide
Siemens Advia Centralink Data Management System Networking Solution Operators Guide
The information in this manual was correct at the time of printing. However,
Siemens continues to improve products and reserves the right to change specifications, equipment,
and maintenance procedures at any time without notice. If the system is used in a manner differently
than specified by Siemens, the protection provided by the equipment may be impaired. See warning
and hazard statements.
3
Browsing All Samples ...................................................................51
Viewing the First, Previous, Next, and Last Sample ..................52
Querying Specific Samples ..........................................................54
Finding out More Information about Each Sample ....................66
Finding a Single Sample ...............................................................69
Viewing the Sample Status Overview ..........................................70
Understanding the Diff Pad ..........................................................73
Understanding Slide Requirements ............................................75
Resolving Scheduling Issues .......................................................81
Viewing the Sample Log Records ................................................84
Generating a Sample Report ........................................................86
Generating and Printing Sample Labels .....................................91
Supported Two-Way Communication ...............................................92
Communication: LIS and the ADVIA CentraLink Software .......92
Communication: ADVIA CentraLink System and the LAS ........94
Update LAS Info Upload: ADVIA CentraLink Software to LIS ...100
Understanding the Review and Edit Window ...................................102
Review and Edit Access through Sample Query Window .........102
Review and Edit Window Refresh Using the
Request Query Option ..................................................................106
Review and Edit Access through Configured Toolbar Icon .....107
Areas and Fields of the Review and Edit Window .....................112
Tests and Results Area .................................................................116
Disposition Area ...........................................................................126
Disposition Buttons Functions ....................................................132
Right-Selecting Functions ............................................................142
Viewing Test Request Information ..............................................164
5
Adding a Test Definition ...............................................................243
Defining Test Groups ....................................................................261
Adding a Test to a Test Group .....................................................262
Editing a Test Definition ...............................................................262
Deleting a Test Definition .............................................................262
Setting a Test Unit .........................................................................263
Assigning a Unit to a Test ............................................................265
Setting a Dimension for a Unit .....................................................266
Setting Result Choices .................................................................267
Setting Test Norms .......................................................................269
Setting Delta Norms ......................................................................272
Defining Test Aspects ...................................................................276
Creating Panels for Requestables ...............................................276
Deleting a Panel .............................................................................278
Adding Tests to Requestables .....................................................279
Defining Instruments ..........................................................................280
Understanding Instrument Types ................................................286
Instrument Logs ............................................................................291
Instrument Setup Targeting .........................................................293
Instrument Retarget Function ......................................................294
Configuring Moving Average Batch Size for an Instrument .....295
Enabling Moving Average for a Method ......................................295
Setting up QC Populations for Moving Average Data ...............295
Creating or Modifying Instrument Groups .......................................298
Configuring Instrument Tests (Methods) and Flags .......................300
Setting Instrument Flags ..............................................................300
7
Manually Starting the Database ...................................................360
Understanding the Watchdog Service and Dashboard ...................361
Watchdog Service .........................................................................361
Watchdog Dashboard ..................................................................362
Configuring the Watchdog Service and Dashboard ........................368
Starting Watchdog Service Independent of Other Services .....368
Configuring Watchdog Dashboard ..............................................371
Checking Database Storage ..............................................................375
Purging Data from the Database ..................................................377
Scheduling Tasks ...............................................................................378
Backing Up and Restoring the Software ..........................................380
Backing Up the Databases ...........................................................380
Performing a Backup ....................................................................382
Compatibility of Backup Tapes ....................................................383
Restoring the Databases from a Tape Backup ...........................384
Restoring the Databases from a Disk Backup ............................387
Selecting and Adding Languages .....................................................391
Understanding User Interface Languages ..................................391
Changing User-Defined Languages ............................................391
Defining Languages for Users .....................................................393
Setting the Language for Add-on Programs ...............................393
Printing ................................................................................................395
Customizing Reports ....................................................................398
Customizing the Toolbars ..................................................................399
Troubleshooting .................................................................................402
Error Messages .............................................................................402
9
10 ADVIA CentraLink Operator’s Guide
Overview
Section 1:Overview
Introduction ........................................................................................13
Operator Functions ............................................................................15
System Functions ...............................................................................16
Data Communication ..........................................................................17
ADVIA Modular Automation System .................................................19
LineMaster and Router Software .................................................19
LIS Software ...................................................................................19
Getting Started ....................................................................................20
Logging On and Off .......................................................................20
Using the Workspace ....................................................................22
Using Toolbar ................................................................................24
Using ToolTips for Quick Help .....................................................25
Working with Functions and Windows .......................................26
Scrolling to a Data Item ................................................................38
Using the ADVIA CentraLink Software ........................................39
Using the Online Version of this Guide .......................................39
Installing the Operator’s Guide on Another Computer ...................40
11
12 ADVIA CentraLink Operator’s Guide
Introduction
This Operator’s Guide is applicable to ADVIA CentraLink® System Software 13.0
and higher.
The ADVIA CentraLink system software is your network solution provider and
multi-system data manager for the instruments and laboratory automation
systems (LAS) in your lab.
The ADVIA CentraLink software consolidates data from all connected
instruments so that an operator can review and edit patient and quality control
results from a single location.
13
concurrent uploading data to and downloading data from the LIS. With this
configuration, the communication channels consist of one channel for
downloading test orders from the LIS and another for uploading results from the
ADVIA CentraLink software. The 2 separate communication channels ensure
continuous communication flow of information from the LIS to the
ADVIA CentraLink software and from the ADVIA CentraLink software to the LIS.
For LIS that do not support more than one channel for communication to the
same host, the upload and download communication can be achieved using a
single connection.
The ADVIA CentraLink software supports the ability to configure either one or two
lab automation systems.
Upon receipt of workorder download from the LIS, the ADVIA CentraLink
software automatically downloads all received workorders to the LAS. Upon
sample checkin to the LAS and during the physical routing of samples to the
analyzers, Sample Managers, and Cold Storage for archival of samples, LAS
status update messages are uploaded from the LAS to the ADVIA CentraLink
software to provide accessioning and sample location information. The
ADVIA CentraLink software also provides the ability to manually query the LAS
for sample location information.
When 2 lab automation systems are configured, the ADVIA CentraLink software
downloads all workorders and queries to both lab automation systems. If one lab
automation system is temporarily not accepting orders, the ADVIA CentraLink
software sends previously unsent orders to the LAS after the connection is
reestablished with the associated lab automation system. Accordingly, the
ADVIA CentraLink software receives updates from both lab automation systems
upon a LAS status update.
The ADVIA CentraLink software can support a maximum of 32 connections.
These connections can include a maximum of 32 instrument connections or 30
instrument connections and 2 lab automation system connections. The total
number of combined instrument and LAS connections cannot exceed 32.
The ADVIA CentraLink software supports a maximum of 15 client computers or
workstations, of which a maximum of four clients may be remote clients.
15
System Functions
A system manager is the person who configures and monitors ADVIA CentraLink
software for the operators who perform routine operations.
The system manager uses the ADVIA CentraLink software to do the following
tasks:
• Verify that initial settings are properly configured for instruments, tests,
patients, physicians, QCs, and related data
• Add new users
• Set up security for all users
• Customize ADVIA CentraLink software toolbars
• Monitor communication with the LIS, lab automation system (LAS), and
instruments
• Monitor instrument and QC status
• Back up and restore the system
17
Data Collection and Transfer Points Workflow Paths
G Sample location information from the
LAS
3 Lab automation system (LAS) C Tube Transfer Communication
4 Instruments D Sample Query Communication
E Sample Results
F Results from the ADVIA CentraLink
system to the LIS
The ADVIA CentraLink software receives downloaded workorders from the LIS
and downloads them to the LAS. The instrument queries the ADVIA CentraLink
software for test selectivity for specific bar-coded sample IDs. When the tests are
completed for a sample, the instrument sends the results to the
ADVIA CentraLink software. Normal results can be automatically validated and
sent to the LIS.
LIS Software
Use the LIS software to manage the following items:
• Order entry
• Dilutions ordered at the LIS
• Long term result storage
• Reporting
19
Getting Started
In this section, you learn about the following features and functions:
• Log on to the ADVIA CentraLink software
• Work with the ADVIA CentraLink system workspace
• Use the toolbar to access the data you need
• Use ToolTips to help you understand the meaning of a data field
• Execute a command using the menus or right mouse button
• Use the online version of this guide
1 Start menu
2 Name of current user
21
Using the Workspace
The ADVIA CentraLink system workspace consists of different areas.
1 Menu Bar. Displays the ADVIA CentraLink software menus. Some menu items
vary depending on the windows open in the workspace. For example, the
Record menu is not active until a window, such as the Samples window, is open.
The items on the Edit menu (Cut, Copy, Paste) are active for an open window.
23
NOTE:You can restore the default window size by double-selecting the title
bar of the window when the resize setting is active.
Using Toolbar
When the ADVIA CentraLink software is initiated, only the menus and toolbars
are displayed. To start your work, which can include reviewing and editing results
or checking QC, you can select a toolbar icon.
The toolbar contains the most frequently used functions. By hovering over the
toolbar, the name of each operation displays. Each of the toolbar functions are
described later in this guide.
1 Instrument
2 Tests
3 Order Entry
4 Patients
5 Physicians
6 Samples
7 Review and Edit
8 Results Entry Grid
9 QC
10 System Manager Functions
25
Working with Functions and Windows
The ADVIA CentraLink software offers several ways for you to do your work,
including menus, context menus, selection from the ? symbol, and keyboard
shortcuts.
Using Menus
The menus on the top of the ADVIA CentraLink system window contain functions
that you can use as an alternative to using the toolbar.
The main functions for routine operations can be initiated as follows:
1. On the menu bar, select Start > Routine menu.
27
Browser Window
A browser allows you to view data.
29
Editor Window
An editor allows you to enter data. To submit the data, select OK.
31
Using the ? Symbol Placeholder
On many ADVIA CentraLink system windows, a ? symbol displays.
The ? symbol can have different meanings depending on the field in which it
displays.
NOTE: Before making changes to a field that contains the ? symbol, ensure that
you fully understand the acceptable values.
To use the ? symbol placeholder, perform the following steps:
1. Rest your mouse on a field that contains the ? symbol.
2. If your cursor changes to a hand shape, double-select the ? symbol.
Another window opens with a list of acceptable data for the field.
If the field is not required, the ? symbol is a default value, and you do not
have to change it. In some cases, such as search queries, the ? symbol is an
indication that the system does not use the field to filter results. Leaving the ?
symbol returns items regardless of what they contain for the field.
33
NOTE: In some cases, the ? symbol is necessary if no entry is made in a field.
Removing the ? symbol and leaving the field blank can cause system errors.
For example, if your cursor changes to a hand shape when the mouse rests in
the Method test field, you can double-select the ? symbol to view a selection list.
Upon selecting the appropriate test and double selecting, the QC Population
editor window redisplays.
35
The Method test field is populated with the selected test, RBC.
37
Window Keyboard Keys to Press Description of Action
CTRL+ R Recall
39
Installing the Operator’s Guide on Another Computer
You may need to install the ADVIA CentraLink system Operator’s Guide on a
computer that is not running the ADVIA CentraLink software. The installation
procedure installs the following items:
• Adobe Reader 9.0
• ADVIA CentraLink Operator’s Guide
To install the Operator’s Guide:
1. Close all Windows programs before beginning the installation.
2. Insert the ADVIA CentraLink Operator’s Guide CD in the CD drive.
The installation starts automatically.
3. On the Welcome window, select Next.
4. Leave both options selected on the Choose options window and select Next.
A Choose Destination Location window displays with the following text:
“WARNING: CentraLink Server software has not been installed on this
computer.
5. If you wish to continue installing the ADVIA CentraLink Operator’s Guide, you
must select a destination folder using Browse.
6. If you do not want to continue the installation, select Cancel.
Select Next to agree to the default destination folder: C:\CentraLink\Doc.
7. Select Yes if asked to create the C:\CentraLink\Doc folder.
The Adobe Reader 9.0 install runs. When the installation is complete, the
CentraLink Install window displays. The Adobe License Agreement and the
Software License Agreement displays.
8. Select Accept.
The ADVIA CentraLink Operator’s Guide installation runs. After the
Operator’s Guide is installed, a Setup Complete window displays a message
to reboot to complete setup. I want to restart my computer now is selected
by default.
9. Select Finish to restart the computer and complete the installation.
41
Review and Edit Access through Configured Toolbar Icon .....107
Areas and Fields of the Review and Edit Window .....................112
Tests and Results Area .................................................................116
Disposition Area ...........................................................................126
Disposition Buttons Functions ....................................................132
Right-Selecting Functions ............................................................142
Viewing Test Request Information ..............................................164
Understanding Quality Control .........................................................172
QC Lots ..........................................................................................173
QC Populations .............................................................................177
Evaluating QC Results ..................................................................193
Accessing the QC Results (Across controls view) Window .....194
Right-Selecting Functions ............................................................207
Omitting a QC Data Point .............................................................216
Reinstating an Omitted QC Data Point ........................................216
Auditing a QC Data Point ..............................................................217
Adding a Comment to a QC Data Point .......................................217
Uploading QC Results to the LIS .................................................217
Closing Out QC ..............................................................................219
Importing ADVIA 120/2120 QC Data ............................................220
Generating QC Reports ................................................................220
Manually Entering a Result ................................................................226
Printing a Worklist .........................................................................229
Manually Entering a Workorder .........................................................231
Creating a New Workorder ...........................................................231
Merging a New Test into an Existing Workorder ........................235
43
44 ADVIA CentraLink Operator’s Guide
How Do I?
For a quick answer, go to the page for a specific task:
Task Go to
Review and Edit
Review sample results page 47
Review results for specific samples page 54
Validate and Invalidate results page 132
Rerun a test page 134
Edit a result page 152
Print a sample report page 86
Append a comment to a result page 152
Interpret result severities page 125
Display result flag details page 137
Revert a result page 135
Omit a test page 149
QC Results
Review QC results page 193
Interpret QC from results or Levey-Jennings plots page 184
Omit a QC data point page 216
Reinstate a QC data point page 216
Audit a QC data point page 217
Reset QC severity page 205
45
Task Go to
Close out QC page 219
Print QC results page 220
Add a new QC lot page 173
Miscellaneous
Create a workorder page 231
Use Diff Pad page 73
Manually enter results and send to the LIS page 226
Merge a workorder with unsolicited results from an instrument page 235
Purge Function
Purging the sample database removes all samples from the database with status
Uploaded, Omitted, and Unknown; that is, the purge function deletes those
samples that do not have Pending, Rerun, Scheduled, or Review status test
requests. Refer to Purging Sample and Worklist Data from the Database‚
page 72.
Those samples with status Pending, Rerun, Scheduled, and Review are not
purged from the database upon executing the Purge function. These samples
have active workorders and outstanding test requests within the
ADVIA CentraLink system and as such, the sample IDs that identify them are not
typically candidates for reuse. It is important to note, therefore, that if they were
reused without first being deleted from the system, the results for the new
physical sample would merge with the results of the original, different physical
sample.
If your lab requires the reuse of sample IDs that are associated with samples in
Pending, Rerun, Scheduled, and Review status, however, you must take the
47
additional step of executing an Omit command to ensure that these sample IDs
are deleted from the database.
Omit Command
The Omit command changes the status of samples that exceed the sample
retention time period requirements of your lab to Omitted.
Your local technical support provider can configure the Omit command to change
the status of samples that existed in the database for a user-specified number of
days from Pending, Rerun, Scheduled, and Review to Omitted.
Once configured, the Omit command can be scheduled to run as a task as per
your lab’s requirements. The next time the Purge function is initiated after the
Omit command is executed, the sample IDs associated with these samples in
status Omitted are deleted from the database along with the sample IDs
associated with other samples in status Uploaded, Omitted, and Unknown.
49
If your lab requirements dictate that you reuse a sample ID that references a
sample for which results exceeded the sample reuse period, upload the sample
results to the LIS. This upload changes the sample status to Uploaded.
The next time the Purge function is initiated, the sample ID associated with this
sample in status Uploaded is deleted from the database along with the sample
IDs associated with other samples in status Uploaded, Omitted, and Unknown.
After the sample reuse period has elapsed and the sample ID is purged from the
system, the same sample ID can be reused in the ADVIA CentraLink software as
a unique sample ID.
51
NOTE: If the sample list is very large, the display could take a long time. If it takes
too long to display a sample list, press CTRL+BREAK to cancel the query.
53
Querying Specific Samples
The ADVIA CentraLink system database may contain thousands of samples.
Most of the time you do not want to see all samples, but rather a subset of
samples based on specified criteria.
You can specify criteria on the Sample Query window to restrict the samples that
are accessed. The more selection criteria specified, the smaller the resulting
record set. Leaving a ? symbol in a field indicates that the field is not used to filter
the record set the query returns.
You have the option of viewing your query results in standard data view or
alternate data view:
• Selected samples with standard data view. The listed data includes sample
ID, priority, patient ID, collection date/time, physician ID, and status.
• Selected samples with alternate data view. The listed data includes Sample
ID, Priority, Patient ID and name, Status, LAS seq no, LAS general area, LAS
specific area, LAS tray id, LAS tray position, and LAS time.
Regardless of the view in which you want to see your sample result set, you can
enter search criteria by setting one or more of the fields on the Basic and
Advanced tabs of the Sample Query window.
55
Basic Tab of Sample Query Window
Field Description
Sample ID When Sample ID is specified, only one single sample
can be returned by the query.
The ADVIA CentraLink software supports Sample IDs
with a maximum of 16 characters.
NOTE: Use caution when using sample ID values
consisting of 16 uppercase alpha characters. While the
sample ID is accepted by the ADVIA CentraLink
software, the 15th and 16th, uppercase, alpha
characters display as if they were truncated in the
ADVIA CentraLink software. Upon subsequent retrieval
of the sample ID at the Sample browser window, the
16th character does not display, and at the Review and
Edit window, both the 15th and 16th characters do not
display. For example, if you enter a sample ID value of
“ABCDEFGHIJKLMNOP," the sample ID value
"ABCDEFGHIJKLMNO" would display at the Sample
browser window and the sample ID value
"ABCDEFGHIJKLMN" would display at the Review and
Edit window.
You can enlarge the size of the Sample browser
window or Review and Edit window to increase the
Sample ID field and display the full Sample ID value.
NOTE: For information on resizing windows in the
ADVIA CentraLink software, refer to Using the
Workspace‚ page 22.
NOTE: The ADVIA CentraLink system is designed to
operate in a unique environment. All sample IDs must
be unique.
57
Field Description
Minimal status and Restricts the eligible sample statuses to a from and to
Maximal status range.
All samples with a status between the Minimal status,
which is the “from” status value, and Maximal status,
which is the “to” status value, are returned. For example
if PND and REV are selected in the Minimal status and
Maximal status range fields respectively, all samples
with the following statuses are returned: PND, SCH,
RRN, REV.
When the At least one test in Status field is selected
and the Minimal status and Maximal status fields are
populated, then all samples with at least one test in the
status range are returned to the Sample browser
window.
When you enter a Minimal status value, the Maximal
status field is automatically assigned the same status
value.
When you enter a Maximal status value, the Minimal
status value is not affected.
As a convenience, the Maximal status field value
automatically changes to Validated (VAL), when any
restrictions are provided on the following: Instrument or
Instrument Group; Test or Test Group; Aspiration From
and To dates. You can modify this automatically
populated value of VAL to any other status value
including the ? symbol.
You are not required to enter a Maximal status value
when the At least on test in Status checkbox is
selected.
59
Field Description
Patient last name Restricts the result set to patient last name.
Type Restricts the result set to those of a specified sample
type.
Instrument group Restricts the result set to those containing at least one
request referencing the specified instrument group.
Instrument Restricts the result set to those having at least one
request for the selected instrument.
When searching for test requests or results when a
normal instrument is specified, the query searches for
the instrument that equals the normal instrument.
When searching for test requests or results when a
concentrator is specified, the query searches for the
instrument and the parent instrument that equals the
concentrator.
For details on normal and concentrator instrument
types, refer to Understanding Instrument Types‚
page 286.
61
Advanced Tab of Sample Query Window
Field Description
Minimal status minutes Entering a time in minutes restricts the result set to
those having the specified status for equal to or more
than the specified time in minutes.
NOTE: Exercise caution when entering a Minimal
status minutes value. You can enter a Minimal status
minutes value >= Maximal status minutes value. Under
these conditions, the query returns 0 samples.
Maximal status Entering a time in minutes restricts the result set to
minutes those having the specified status for less than or equal
to the specified time in minutes.
Physician identifier Restricts the result set to those associated with the
physician ID.
Physician last name Restricts the result set to those associated with the
physician’s last name.
Patient location Restricts the result set to those associated with the
patient’s location.
Slide request Slide request parameters include the following choices:
• Not Required - No restriction to the result set based
on slide when Not required is selected.
• Required - Restricts the result set to those with a
slide request.
• Result Required - Restricts the result set to those
with a resulted slide request.
See Understanding Slide Requirements‚ page 75 for
information on slide processing.
63
Field Description
Filter A filter is a logical-valued, sample site function.
Restricts the result set to those samples for which the
function returns the value True.
Here you can select from a list of filters or create a new
filter.
NOTE: Specifying filters can degrade performance.
Max sample count Restricts the maximum number of samples that can be
returned by the query. Restricting the number of
returned samples can improve response time for
queries that result in large test results.
Sort criterion Specifies the sorting order of the search results. You
have three sort options:
• Sample ID – default
• Priority – Creation time
• Instrument time
65
includes sample ID, priority, patient ID and name, status, LAS SeqNo, LAS
general area, LAS specific area, LAS tray ID, LAS tray position, and LAS time.
Function Description
Check results Applies an automatic check to the results. This function
is useful when norms or delta norms were modified
after result entry.
Container type Specifies tube or other container that contains the
sample.
Diff Pad Opens the Diff Pad, which allows you to perform a
manual diff using the keyboard.
See Understanding the Diff Pad‚ page 73.
Dispatch to LAS Sends an updated workorder to the LAS. Normally,
updated workorders are sent to the LAS automatically
by a task scheduler, which is set up by an administrator.
See Viewing the Sample Status Overview‚ page 70.
You can bypass the automatic process with the
Dispatch to LAS option.
See Workorder Download‚ page 95 and Dispatch to
LAS Function‚ page 96.
See Addressing Perpetual Pending Issues through the
Dispatch to LAS Function‚ page 83.
Instrument Last instrument to process the sample.
Patient Specifies demographic information.
Patient location If specified, displays patient locations such as ER.
Physician ID If specified, displays physicians.
Report Generates a report for a sample. An administrator can
define report generation to run when all results of a
sample are validated.
See Generating a Sample Report‚ page 86.
67
Function Description
Print label Generates and prints a sample label.
See Generating and Printing Sample Labels‚ page 91.
Rerun Reruns all tests in the sample.
NOTE: When you manually initiate a Rerun by right-
selecting the sample or samples, the Dispatch to LAS
task must be running for the order to be downloaded to
the LAS.
Review and Edit Opens the Review and Edit window
See Understanding the Review and Edit Window‚
page 102.
Set Slide Suppression Enables the creation or removal of a suppression
request for the ADVIA CentraLink system slide test.
See Setting Slide Suppression‚ page 79.
Species Opens the Species window and displays the species
name and description.
Type Opens the Sample Type window and displays the
sample type name and description.
Upload result Opens the Upload results window allowing for you to
specify the test for upload.
Upload validated Uploads validated results to the LIS. A system
results administrator can define automatic upload of the
validated results to run when all results of a sample are
validated.
View image If a sample has an image, you can use this function to
view it.
69
Viewing the Sample Status Overview
The Sample Status Overview window allows you to verify the number of samples
in each status category as well as the total number of samples in the
database.The Sample Status Overview window displays sample counts grouped
by status and priority.
The counter values indicate the number of samples in a given status at a given
point of time. These values, however, do not always represent the exact quantity
of samples in a given status particularly when there is concurrent activity in other
sessions or batch processes. During the counting process, other processes may
add or delete samples or change their status. For performance, uploaded
samples are not counted directly; their number is obtained by subtracting the
other counters from the total sample count maintained explicitly in the database.
Consequently, negative counter values sometimes display on the Sample Status
Overview window.
Each possible status value is represented in a row. The unknown row is for
samples without any associated requests. The right-most column lists the same
counters, but only displays counter values for samples with priority STAT.
To ensure that the ADVIA CentraLink system database does not grow too large,
you can monitor it and purge results as necessary.
Access the Sample status overview window:
1. At the menu bar, select Start > Routine > Samples > Status Overview.
NOTE: When the Sample status overview window displays initially, all fields are
populated with the ? symbol until you select the Refresh button.
To initiate the count and update the view, select the Refresh button.
To remove sample and/or worklist records from the database, select the Purge
button. The Purge data window displays.
71
Purging Sample and Worklist Data from the Database
You can access the Purge data window through the Sample status overview
window or you can access it as a pulldown option from the System Management
function.
NOTE: As an audit log is generated and written to during the manual purge
process, system performance can be significantly degraded when initiating a
manual purge. If you purge on a regular basis, contact your local technical
support provider to configure a task, which can be scheduled to purge
automatically during off hours so as not to impact response time during peak
operating hours. Task based purges are not audited.
Access the Purge data window:
1. At the Sample status overview window, select Purge.
To access the window from the System Management window, see Purging
Data from the Database‚ page 377.
The Purge data window displays.
Field Description
Days to keep The period of time, starting from the current date back,
for which the data is not purged.
Samples When selected, samples with status Uploaded, Omitted
or Unknown, that is, those samples without requests,
and their dependent data are purged.
Worklists When selected, worklists and their dependent data are
purged.
At the Purge data window, purge samples from the database as follows:
1. At the Days to keep field, enter the period of time in days for which data is not
purged.
2. Select the Samples checkbox.
NOTE: If the Samples checkbox is not selected, no sample records are
purged from the database.
3. Select OK.
73
Upon display of this window, available results are displayed first. These results
can include those obtained from a real instrument. You can select Reset to reset
all counters to zero.
Navigate to the Diff Pad:
1. At the Sample browser window, right-select the selected entry and select Diff
pad.
The Diff Pad window displays.
2. While looking through the microscope, use the keyboard to count the different
cell types.
Press the appropriate key to increment the cell count by one. If you make a
mistake or want to restart the count, select the Reset button on the counter
window to set all the counts to zero.
When a total of 100 cells has been counted, you hear a signal indicating that
sufficient data is available.
75
“Whole blood” is typically configured as the sample type that allows for
processing slide requests and displaying slide information. You can configure
only one sample type to the test that is specified as the slide test.
For example, define the slide processing test with a sample type of Whole blood:
Field Description
Test Reference to the name of the test defined for
representing slide preparation.
In the above example, Slide is the name of the slide
test.
Allow LIS download If selected, the ADVIA CentraLink system accepts slide
requests from the LIS.
If not selected, the ADVIA CentraLink system does not
accept slide requests from the LIS. You must enter slide
requests manually or through reflex testing.
77
Field Description
LIS upload mode Select one of the following options:
• Suppress – Do not allow slide upload information to
the LIS.
• Allow manual only – Allow slide upload information
to the LIS from the Review and Edit window via the
Upload button or from the Sample window via right-
selecting and accessing the Upload result window.
• Allow always – Allows automatic slide upload
information to the LIS.
NOTE: The instrument sends the following slide test
result values back to the ADVIA CentraLink system:
Req., Prod., and Fail. Based on predefined result
choices, the ADVIA CentraLink system converts these
result values to the following: Requested, Produced,
and Failed.
Affects sample status If selected, the presence of a slide test within a sample
does not prevent auto validation of all tests within that
sample.
If not selected, the presence of a slide test within a
sample prevents auto validation of all tests within that
sample.
NOTE: The Affect sample status functionality is not
retroactive. If the Affects sample status checkbox is
selected or unselected within the life cycle of a given
sample, the changed functionality does not affect the
existing slide or its test requests.
79
Field Description
Suppress If selected, slide suppression is enabled for the current
sample. A NoSlide command is sent to the SMS
instrument upon instrument query for the respective
SID. Even if the sample meets the slide criteria, the
SMS instrument does not make a slide for the sample.
If not selected, slide suppression is reenabled if
previously enabled for the current sample. If the sample
meets the slide criteria, the SMS instrument can make
a slide for the sample.
81
• Test requests that have previous results are demoted from status Scheduled
to status Rerun.
• Upon reschedule, the ADVIA CentraLink system sends an updated message
to the LAS, which reroutes the samples to the instrument.
You can specifically query the number of Scheduled requests for which results
have not been returned for a specified amount of time from the Sample query
window. On the Basic tab of the Sample Query window, select Scheduled in the
Minimal status and Maximal status fields. On the Advanced tab of the Sample
Query window, enter the minimum amount of time for which a request must be in
status Scheduled and for which no results are received from the instrument. Test
requests that are in status Scheduled for longer than the specified time are
displayed through the Sample browser window.
Unschedule a test request for which results have not been received from the
instrument:
1. At the Sample browser window, right-select the selected entry and select
Unschedule.
The Unschedule requests window displays.
Field Description
Instrument The instrument for which you want to unschedule
requests.
If the instrument is not specified, all scheduled requests
for the sample are unscheduled.
Field Description
Target Determines to which LAS system the sample workorder
is dispatched.
Valid values include the following:
1 – Dispatched to LabCell 1.
2 – Dispatched to LabCell 2.
All – Dispatched to both LabCell systems.
83
Field Description
Include dispatched If selected, the message to the LAS includes requests
that were previously dispatched to the instrument and
are not in status Review.
Field Description
Sample Reference to the containing sample.
85
Field Description
Effective time This value is used to sort the logs. The effective time
value can either be the time that is transmitted by the
LAS or the actual transmission time.
Instrument Reference to the instrument.
Instrument rack Instrument rack as received from the referenced
instrument.
Instrument position Instrument position as received from the referenced
instrument.
LAS seq. no. Identifies which LAS supplied the message: LAS1 or
LAS2.
Status, tray id, tray Values as reported by the LAS.
position, general area,
shelf, door, area, gate
87
Field Description
Format Select HTML or Text.
The text format requires a line width of up to 132
characters. Ensure that your Windows font or page
orientation settings are properly set to avoid text
wrapping.
Graphs are available in HTML format only. The graphs
might not display properly when scrolling during
preview.
NOTE: This field is disabled and Text displays when the
Via fax checkbox field is selected.
Preview If selected, a screen preview of the generated report is
displayed.
When the specified format is HTML, a web browser is
used for previewing the generated HTML report.
89
Field Description
Fax number By default when one sample is selected, the fax
number specified in the Fax number field at the
Physicians window automatically populates this field.
You can also enter a different fax number, which
overrides the fax number specified in the Fax Number
field at the Physicians window.
When more than one sample is selected, the ? symbol
populates the Fax number field. If you do not enter a fax
number value, the fax is sent to the fax number
specified in the Fax number field at the Physicians
window for the sample.
Refer to Accessing Physician Records‚ page 239.
NOTE: Do not specify special characters, for example,
+ or -, among the numerical values specified in the fax
number field. Spaces are permitted between numbers,
for example, 0032 9 220 48 10.
Mark as reported If selected, the sample record is marked as having
been reported.
When a sample record is marked as reported, it is not
accessed when a sample query is initiated from the
Sample Query window and the Not reported parameter
on the Advanced tab is selected.
Field Description
Preview A preview of the expanded label displays before the
sample label is printed.
Printer Specifies the printer to which the generated sample
label is output.
NOTE: Upon sample label print, the dynamic text within
the label definition defined on the More tab of the
system Options window is expanded and the output is
stored in a .lbl file before the label output is sent to the
specified printer.
91
Supported Two-Way Communication
The ADVIA CentraLink software supports two-way communication between the
following interfaces:
• The LIS and the ADVIA CentraLink software
• The ADVIA CentraLink software and the LAS
• The ADVIA CentraLink software and the instruments
NOTE: The units of measure for a given test must be defined identically at the
LIS, in the ADVIA CentraLink software, and at the instruments. The units for test
results uploaded from the instrument are not read by the ADVIA CentraLink
software. You must predefine the units for tests in the ADVIA CentraLink software
to match the units for tests on the instrument. If units of measure of results are
manually changed on an instrument, you must change the units of measure for
the test in the ADVIA CentraLink software at that time. In addition, you must
purge all existing results for the test from the ADVIA CentraLink software. Units of
measure are not uploaded to the LIS from the ADVIA CentraLink software.
93
The ADVIA CentraLink software can be configured to upload to the LIS sample
archive and location information for each sample for which it receives information
from the LAS. You have the ability to upload this sample archive and location
information as many times as the ADVIA CentraLink software receives cold
storage message updates from the LAS.
Refer to Update LAS Info Upload: ADVIA CentraLink Software to LIS‚ page 100.
Workorder and Query Download from ADVIA CentraLink Software to the LAS
The communication between the ADVIA CentraLink system and the LAS consists
of workorder downloads, query downloads, and LAS sample status update
uploads.
Each of these communication messages uses a separate translator–order
translator, status query translator, and status update translator–which are defined
on the LAS tab of the system Options window.
Workorder Download
Workorders that are created within the LIS or within the ADVIA CentraLink
system are sent to the LAS. Workorder messages sent to the LAS do not contain
an instrument specification unless an instrument was explicitly specified when
95
initiating an Advanced Rerun. See Setting Up Advanced Reruns‚ page 157 for
information on Advanced Reruns.
Field Description
Target Determines to which LAS system the sample workorder
is dispatched.
Valid values include the following: 1, 2, All.
Include dispatched If selected, the message to the LAS includes requests
that were previously dispatched to the instrument and
are not in status Review.
Query Download
A query download consists of a request for the status of samples on the LAS.
Sample status query messages are sent directly from the ADVIA CentraLink
system to the status query translator. No status update response is expected on
the query channel. The sample status update message is received into the
database from the sample status update translator and translator server running
in batch mode at a later time.
NOTE: The Record Passed message that displays after a query is run indicates
that the sample status query message was sent to the LAS. It does not indicate
that an update message was uploaded from the LAS to the ADVIA CentraLink
system.
97
Send a Query Download Message to the LAS
You can send a query to the LAS requesting an update on the selected sample
records or on the focused sample record.
Initiate a LAS status query:
1. At the Sample browser window, right-select a selected entry and select
Query LAS status.
The Query LAS status window displays.
Field Description
Target Determines to which LAS system the sample workorder
is dispatched.
Valid values include the following: 1, 2, All.
LAS Sample Status Update Upload from the LAS to the ADVIA CentraLink Software
A LAS sample status update message consists of the current status of a sample
on the LAS. This LAS sample status update message is uploaded from the LAS
to the ADVIA CentraLink system.
The LAS sample status update upload is initiated in response to a Query LAS
status request or is uploaded automatically when a sample is checked in to the
LAS; reaches an end of route location, such as a Sample Manager Unload tray;
or is archived to Cold Storage within the LineMaster software.
The LAS status information is stored in the Sample Log table and displays
through the following windows:
• Sample Editor window
• Review and Edit window at the Advanced tab and the LAS tab
• Logs of sample browser window
• Sample log editor window
• Sample Query (Alternate View) window
The SeqNo field value of the following windows in the ADVIA CentraLink
software are updated automatically and identify the LAS system that updated the
LAS information:
• Sample Editor window. This window is also referred to as the Manual Order
Entry window. Refer to Updated LAS Information Uploaded to Fields on LAS
Tab‚ page 236.
• Review and Edit window. Refer to Advanced Tab‚ page 114 and LAS Tab‚
page 115.
• Logs of sample browser window. Refer to Accessing Logs of Sample
Window‚ page 84.
• Sample Log editor. Refer to Accessing Sample Log Editor Window‚ page 85.
• Sample Query (Alternate View). Refer to Viewing the Sample Browser
Alternate View‚ page 65.
99
Update LAS Info Upload: ADVIA CentraLink Software to LIS
You have the ability to upload accessioning information, which is also known as
inlabbing information, as well as sample archive and location information, which
is also referred to as cold storage information, from the ADVIA CentraLink
software to the LIS. While inlabbing information can only be uploaded once,
sample archive and location information can be uploaded as many times as the
ADVIA CentraLink software receives cold storage message updates from the
LAS.
The ADVIA CentraLink software could receive an additional cold storage update
from the LAS, for example, when a sample tube is removed from cold storage,
rechecked into the track, and returned to cold storage after sample testing is
complete.
Field Description
Include shelf Determines whether the sample tube’s cold storage
shelf is included in the upload message.
Include door Determines whether the sample tube’s cold storage
door is included in the upload message.
Include area Determines whether the sample tube’s cold storage
area is included in the upload message.
NOTE: To prevent the occurrence of a deadlock caused by attempts to access
the same data, do not initiate a manual Upload LAS info function while an
automatic LIS Upload task is running.
101
Understanding the Review and Edit Window
You can review, modify, and disposition test results from connected instruments
through the Review and Edit window.
Several options exist for accessing the Review and Edit window. Those options
that include entering criteria to restrict the display on the Review and Edit window
for a given sample set include the following:
103
The Sample query window displays.
For details on the fields of the Sample query window, refer to Basic Tab of
Sample Query Window‚ page 56 and Advanced Tab of Sample Query
Window‚ page 62.
2. After entering the parameters and selecting OK, the Review and Edit window
displays.
Only one sample ID with all of its associated test results displays on the
window at any given time. Using the navigation buttons on the toolbar, you
105
For details on the areas and fields of the Review and Edit window, see Areas and
Fields of the Review and Edit Window‚ page 112.
For details on the fields of the Request query window, refer to Fields of the
Request Query Window‚ page 140.
2. After entering the test request criteria that will restrict the test results within
the sample set, select OK.
The refreshed Review and Edit window displays.
The results that display in the Test and Results area are restricted to meet the
request query parameters entered to the Request Query window. The
parameters for this restricted sample result set apply until the current Review
and Edit window session ends.
For details on the areas and fields of the Review and Edit window, see Areas
and Fields of the Review and Edit Window‚ page 112.
107
The Function table field and Function mnemonic fields are populated with the
values that you had just entered: gp_Site and ReivewAndEdit respectively.
9. At the Short description field, enter a descriptive term.
The maximum number of characters for the Short Description field is 50
characters.
Enter a descriptive term that accurately reflects the function of the toolbar.
The term should signify the sample set that is accessed as per the predefined
sample query and test query parameters that are automatically referenced
upon toolbar icon selection and that will populate the Review and Edit
window.
For example, if you are creating the toolbar button to view a prepopulated
Review and Edit window that contains current sample query and test request
criteria for chemistry samples, enter ReviewCHEM.
Define and Associate Sample Query and Test Request Criteria to Toolbar Icon
Define sample query and test request criteria and associate these parameters to
the created toolbar icon:
1. At the Actual parameter sets of function browser, highlight the newly created
parameter set, right-select, and select Setup.
2. At the Basic and Advanced tabs, enter the sample query parameters that will
restrict the sample set as per your requirements.
The Basic and Advanced tabs of the Review and Edit - Query setup window
contain each of the fields of the Basic and Advanced tabs of the Sample
query window.
For details on the fields of the Sample query window, refer to Basic Tab of
Sample Query Window‚ page 56 and Advanced Tab of Sample Query
Window‚ page 62.
109
NOTE: On the Basic tab of the Review and Edit - Query setup window, the
status values do not display to the right of the Minimal and Maximal status
fields although these values do display on the Basic tab of the Sample Query
window.
3. At the Requests tab, enter the test request parameters that will restrict the
test results within the restricted sample set.
The Request tab of the Review and Edit - Query setup window contains each
of the fields of the Request query window.
For details on the fields of the Request query window, refer to Fields of the
Request Query Window‚ page 140.
4. After entering all of the sample query and test request parameters at the
Review and Edit - Query setup window, select OK.
The Actual parameter sets of function browser displays.
5. At the Actual parameter sets of function browser window, select OK.
The Toolbar button editor window displays.
The Function parameter set field is populated with the Short description field
value that you entered at the Actual function parameter set editor window.
111
Areas and Fields of the Review and Edit Window
The Review and Edit window is comprised of three areas:
Demographics Area
The Demographics area of the Review and Edit window includes a Basic,
Advanced, and LAS tab. This Demographics section displays sample-specific
information.
If the sample contains a request with associated instrument flags, a warning
triangle displays in the upper right corner of the section.
Field Description
Sample ID Identification number of the displayed sample.
The ADVIA CentraLink software supports Sample IDs
with a maximum of 16 characters.
NOTE: Use caution when using sample ID values
consisting of 16 uppercase alpha characters. While the
sample ID is accepted by the ADVIA CentraLink
software, the 15th and 16th, uppercase, alpha
characters display as if they were truncated in the
ADVIA CentraLink software. Upon subsequent retrieval
of the sample ID at the Sample browser window, the
16th character does not display, and at the Review and
Edit window, both the 15th and 16th characters do not
display. For example, if you enter a sample ID value of
“ABCDEFGHIJKLMNOP," the sample ID value
"ABCDEFGHIJKLMNO" would display at the Sample
browser window and the sample ID value
"ABCDEFGHIJKLMN" would display at the Review and
Edit window.
You can enlarge the size of the Sample browser
window or Review and Edit window to increase the
Sample ID field and display the full Sample ID value.
NOTE: For information on resizing windows in the
ADVIA CentraLink software, refer to Using the
Workspace‚ page 22.
113
Field Description
Priority Displays the following priority of the sample:
• Routine
• Stat
• ASAP
Age Age of the patient in years.
Patient ID Patient ID number.
Patient name Name of the patient
Sex Sex of the patient.
DOB Patient date of birth.
Patient location Place where patient is located, for example, ER.
Collection D/T Date and time of the sample collection.
Sample comment Comment associated with the sample.
Patient comment Comment associated with the patient.
Advanced Tab
The Advanced tab includes the following fields:
Field Description
Physician ID Identification number of the associated physician.
Physician name Name of the physician.
Species Species associated with the sample or patient.
LAS Tab
The LAS tab includes the following fields:
Field Description
Seq No The sequence number of the LAS system that
uploaded the LAS information.
Time Time the sample was last detected at the LAS.
General area A location field as reported by the LAS. The General
area field includes the following application codes:
• CS – Cold storage
• MT – Main track
• SC – Side car
• OT – Off track
115
Field Description
Shelf, Door, Area, Location fields as reported by the LAS.
Gate, Tray id, Tray See Viewing the Sample Status Overview‚ page 70.
position
Field Description
Test Name of the requested test.
NOTE: If a test name that consists of 20 characters was
entered at the Test window, the test name value
appears to be truncated in the Test field at the Review
and Edit window. To verify the entire test name, put
your cursor in the Test field and press the right arrow
key until each of the remaining characters of the test
name display. Avoid entering test names that consist of
20 characters.
Sts The status of the request: Pending (PND), Rerun
(RRN), Scheduled (SCH), Review (REV), Validated
(VAL), Uploaded (UPL), Omitted (OMT).
See Understanding Result Status‚ page 124.
117
Field Description
Current (Cont’d) - Ambiguous result as per comparator– Patient
result has a comparator that renders the result
value ambiguous with relation to the normal
range. As per the comparator, you cannot
definitively determine whether the result value
falls within the normal range or whether it falls
outside the normal range.
Norm records are checked in sequence according
to their evaluation order.
If a result falls outside the range defined by the Low
and High Limit values, then the Severity value of the
Norm is applied to the result.
If the result does not fall outside the range, the norm
with the next highest evaluation order is checked.
Consider another example, for which the Low Limit
and High Limit normal range values of a test are set
from 0.02 to 10.0:
– If the result value <0.02, the result value is not
ambiguous because the result is definitively outside
the norm range.
– If the result value >10.0, the result value is not
ambiguous because the result is definitively outside
the norm range.
– If the result value <0.19, the result value is
ambiguous because the values may or may not
exceed the norm range. The value <0.19 may be on
either side of the Low Limit of 0.02.
– If the result value >9.99, the result value is
ambiguous because the values may or may not
exceed the norm range. The value >9.99 may be on
either side of the High Limit of 10.0.
119
Field Description
Prev Samp Contains the most recent result value on a different
sample for the same patient. This value is used for delta
checking.
Date/Time Contains the date and time in which the Prev Samp
value was recorded. Depending on the settings on the
Options window, this date/time stamp may originate
from the LIS or from the ADVIA CentraLink system
database.
Norm Displays the normal range of acceptable values that
have a corresponding severity of 1.
NOTE: If a normal range is not defined or if the defined
range has a corresponding severity value that is not
equal to 1, the ? symbol displays in this field.
121
Field Description
NS, DS, QS, and IS Quality Control Severity
(cont’d) The QC severity value can equal a warning or
moderate or severe control failure depending on how
you group and define the severities relative to the
following:
• Westgard severity
• Instrument severity
• QC severity on type error
• QC severity on invalid reference
For information on setting method severities, refer to
Autovalidation Tab‚ page 309.
Instrument Flag Severity
blank =No flag exists
1-999 = Flag exists. Severity level is user-defined.
The following colors are displayed in the severity
columns:
• Red - Displayed when greater than or equal to 3.
Severe severity outside of normal range.
• Yellow - Displayed when equal to 2. High severity
outside of normal range.
• Green - Displayed when equal to 1. Moderate
severity outside normal range.
See Understanding Review and Edit Severity Columns‚
page 125.
123
Understanding Result Status
You can review results according to their status. A test result can have any of the
following statuses:
Status Description
1 Pending When a test request is created, its status
(PND) is Pending.
2 Rerun A request is demoted from status Review
(RRN) to status Rerun when a manual Rerun is
initiated for the request or an automatic
rerun is initiated.
3 Scheduled When the request is downloaded to an
(SCH) analysis instrument as a workorder in
response to an instrument query, it is
promoted to status Scheduled.
4 Review A request is promoted to status Review
(REV) when a result value gets assigned to it. A
request can also be demoted to status
Review from status Validated by
executing the Invalidate command.
5 Validated A request is promoted to status Validated
(VAL) when its result value is validated through
manual or automatic validation.
6 Uploaded A request is promoted to status Uploaded
(UPL) when it is successfully uploaded to the
LIS, either explicitly by the operator or
through automatic uploading.
7 Omitted A request enters status Omitted when the
(OMT) Omit command is executed on it.
125
Disposition Area
Actions Description
Select Selecting a status from this drop down menu and
selecting Apply, applies a selection arrow (>) next to
each result with the chosen status in the first column
of the Tests and Results area. This allows you to
disposition all tests with the same status.
To disposition all tests in view in the Tests and
Results area, select All from the Select field drop
down menu and select Apply.
A selection arrow displays next to each result in the
first column of the Tests and Results area.
To remove the selection arrows from the results in
view in the Tests and Results area, select None
from the Select field drop down menu and select
Apply. The selection arrows are removed from the
first column of the Tests and Results area for each
result.
To simultaneously clear selected results and select
unselected results in view in the Tests and Results
area, select Invert from the Select field drop down
menu and select Apply.
NOTE: To select a single result in the Tests and
Results area, highlight the result and press Space
Bar.
127
Actions Description
Validate (Scroll) Validates results of selected tests, changing the
status from Review to Validated.
The Validate (Scroll) button serves as both a Scroll
button and a Validate button depending on whether
all the pages associated with the test results for this
sample display. The label on the Validate (Scroll)
button displays initially as Scroll. After selecting the
Scroll button, the remaining tests display and the
label on the Validate (Scroll) button changes to
Validate.
In this dual function, the Validate (Scroll) button
eliminates the need for manual scrolling through all
of the pages of test results to activate the Validate
button.
When the Auto-Next after Validation parameter is
selected on the Review and Edit tab of the system
Options window, the next sample in the current
sample query automatically displays after the
current sample is validated.
See Considering Validate Scroll Functionality‚
page 132.
Rerun Submits selected tests for rerun, which changes the
status from Review to Rerun.
When the Allow manual rerun all parameter is
selected on the Review and Edit tab of the system
Options window, all selected tests including those in
status Validated and Uploaded are rerun.
When Rerun is executed, the result value from the
Current field displays in the Prev Run field. The
current result value from the rerun displays in the
Current field.
See Rerunning a Test‚ page 134.
129
Actions Description
Revert Reverts the result of a selected request back to the
result value of a previous run. Only samples in
Review status that have previous results can be
reverted.
Reverting to a previous result actually creates a new
result, which is a copy of the original result record.
The reverted record, however, contains the
following updated field values:
• The user and time fields are updated with the
reverting user and time values.
• The comment field is updated with any auto-
generated comments appended with the
reverted comment value.
You cannot revert calculated results; however, in
reverting the inputs to calculated results, these
results are automatically recalculated. Validated and
uploaded results cannot be reverted.
See Reverting to a Previous Test Result‚ page 135.
Upload Manually sends the validated results to the LIS.
The Upload button is activated when at least one
validated request is visible in the Tests and
Requests section. Upon selecting the validated
tests and selecting the Upload button, all selected
results with a status of Validated are uploaded to the
LIS.
See Manually Uploading Validated Results to the
LIS‚ page 136.
You can also initiate the upload function for selected
results by right-selecting and selecting the Upload
option from the pop-up request menu.
131
Disposition Buttons Functions
Validating Results of One or More Tests
A test can be validated only if it has a status of Review. You can validate all
results with a status of Review, or you can select certain results to validate.
WARNING: If you attempt to validate a result that is already validated, the
ADVIA CentraLink system allows the validation attempt without warning that the
result is in the incorrect status for validation.
By default, all tests with a status of Review have a selection arrow in the first
column of the Review and Edit window. If each of these tests require validation,
simply select Validate to change the status for all at once.
133
Rerunning a Test
You can rerun tests by selecting the following buttons:
• Rerun – The Rerun button submits selected tests for rerun.
• Rerun All – The Rerun All button reruns all status Review tests that are in
view in the Tests and Results area browser regardless of whether the tests
are selected.
Omitted tests, which do not display in the Tests and Results area, are exempt
from rerun.
NOTE: You can also manually initiate a rerun from a test request at the
Review and Edit window by right-selecting the test request and selecting
Sample > Rerun. In initiating this manual rerun, the Dispatch to LAS task
must be running for the order to be downloaded to the LAS.
NOTE: See Setting Up Advanced Reruns‚ page 157 for information on
Advanced Reruns, which is available through right-selecting on a selected
test result.
When a test request participating in a calculation is rerun, any dependent
calculated result requests are automatically rerun along with it. Consider the
following:
• If a test is a component of a calculation defined in the ADVIA CentraLink
system, such as Albumin for the A/G ratio, then the component test and the
ratio test are both rerun when the ratio is scheduled for a rerun. The ratio test
is automatically recalculated upon receipt of all component test results from
the instrument.
• If a test is a component of a calculation that is defined only at the instrument,
the ADVIA CentraLink system is unaware of any connection between
components and calculations and is unable to perform the component test
when only the ratio is scheduled for a rerun.
• Morphology flags associated with the previous result are updated by the
system when the test is rerun.
135
The Results of request window displays.
2. Select the result to copy back into the Current column and select OK.
NOTE: Reverting to a previous result actually creates a new result, which is a
copy of the original result record. The reverted record, however, contains updated
user, time, and comment field values.
Field Description
Include Uploaded If selected, matching requests are uploaded regardless
of whether they were already uploaded.
137
The Instrument Flag window displays. On this window, lists of flagged tests
that are grouped by instrument and by flag display.
Viewing Images
The Image button allows you to view any images associated with the selected
result.
To access the image associated with a selected result select the following button:
1. Select the Images button.
139
Access the Request Query Window
At the Review and Edit window, access the Request query window:
1. Select the Options button.
The Request query window displays.
Field Description
Status from and to Restricts the result set to a specific status range.
For example, if you are not interested in viewing
requests already validated, specify the following status
in the Status from and to fields respectively: Pending
and Review.
To view only Omitted results, specify Omitted in both
the Status from field and the to field.
Test group Restricts the result set to requests belonging to the
specified test group.
On re-display of the refreshed Review and Edit window,
only the test requests within the current sample that
belong to this test group display.
Instrument group Restricts the result set to requests belonging to the
specified instrument group.
2. Select OK.
Auto Skipping Sample Records that Do Not Match Test Request Criteria
When you enter test request criteria to the Request query window, you further
restrict the test results that display for the sample(s) that met the sample query
criteria entered to the Sample Query window.
When the Auto-skip sample feature is enabled on the Review and Edit tab of the
system Options window, those sample records with result records that do not
match the test request query criteria and would otherwise display as empty
sample records on the Review and Edit window are skipped. The empty sample
records are skipped and the next sample record that contains result records that
match the test request criteria displays. By default, the Auto-skip sample feature
is enabled on the Review and Edit tab of the system Options window.
If the Auto-skip Then...
sample feature...
is enabled those sample records with result records that do not
match the test request query criteria do not display as
empty sample records on the Review and Edit window.
These empty sample records are skipped, and the next
sample record that contains result records that match
the test request criteria displays.
In addition to automatically displaying only those
sample records with result records that match the test
request criteria entered on the Request query window,
the Auto-skip feature also skips the display of empty
sample records when you navigate as follows:
• Select the Next page/Previous page or Next record/
Previous record buttons of the toolbar.
• Select the Validate button on the Review and Edit
window.
• Press the Page Up or Page Dn buttons on the
keyboard.
141
If the Auto-skip Then...
sample feature...
is not enabled those sample records with result records that do not
match the test request query criteria display as empty
sample records on the Review and Edit window.
You must manually navigate past these empty sample
records by doing one of the following:
• Selecting the Next page or Next record buttons of
the toolbar.
• Pressing the Page Up or Page Dn buttons on the
keyboard.
Right-Selecting Functions
Viewing Results of Requests
Although the most current 2 results display on the Review and Edit window for a
given sample, every test request can have multiple result records associated with
it. You can view each of the result records associated with a test request on the
Results of request window. New result values are uploaded from an instrument,
or they can be entered manually.
A new result value for a given test request is saved as a new record when it is
received within the sample reuse period, which is a configurable time period,
known as the sample reuse period.
If the last result date + Then the new result value is...
Sample reuse period...
is greater than the date of saved.
the new result The last result date is updated with the current
date.
You can view the new result value in the Results of
request window; the last result date does not
display on the window, but is stored in the Sample
table.
is equal to or less than the not saved.
date of the new result An error message is logged in the instrument
Service log.
The following comment is added to the sample
specifying that results were discarded due to
results extending beyond the Sample reuse
period: “Results discarded – sample reuse time
has elapsed for sample <Sample.Identifier>
(<Instrument.Name>-<CurrentDateTime>).”
This comment displays in the Sample Comment
field of the Review and Edit window.
143
At the Review and Edit window, access the Results of request window:
1. Right-select a result and select Related > Result.
The Results of request window displays.
NOTE: If you right-select a result of the Results of request window, the View
result option is available from the dropdown menu. This View result option
allows for you to view either hematology results that contain cytograms as a
cytogram image or to view electrophoresis results of type Graph as a
graphical display. When the Upload graphs option on the LIS 2 tab of the
systems Option window is selected, electrophoresis results are uploaded to
the LIS. While electrophoresis is supported, the functionality is not currently
used in the ADVIA CentraLink software.
2. To access the details of a listed result, double-select the result.
General Tab
Field Description
Status The status of the test request:
• Pending - Status when a test request is
downloaded to an instrument as a workorder in
response to an instrument query. A value is
expected from the instrument that queried for
the sample.
• Available - Status when a result value is
assigned to a test request.
145
Field Description
Schedule user Reference to the user who created the result
record that exists in status Scheduled. As this is
typically performed by a background process, the
user is usually set to batch.
Schedule time The date and time when the result record was
created in status Scheduled.
Method Reference to the method record, and thereby the
associated instrument and test, through which the
result was obtained.
For manually entered results, this field is not
populated.
Aspiration time Date and time the sample was aspirated at the
instrument.
Test completed time Date and time in which the test was completed at
the instrument.
Availability user Reference to the user who entered the result
record.
For values obtained from instruments by a
background process, the user is typically set to
batch.
Availability time Time when the result value was stored to the
database.
Value Raw text value supplied by the user or by the
instrument. Unlike the string value associated with
the request record, no rounding or expansion is
applied to this value.
Auto dilution coefficient Dilution coefficient uploaded by the instrument
with the result.
147
Comments Tab
Field Description
Instrument comment Comment uploaded by the instrument along with the
result value.
Parse comment Comment generated by the result value parser.
Range comment Comment generated during automatic application of
norms and delta norms.
User comment Comment a user added to the Edit request comment
window.
2. At the Omit window, type a comment into the Note field to record the reason
the test was omitted.
3. Select OK.
149
Viewing the Omission Note through the Request Window
1. At the Review and Edit window, double-select the selected test.
The Request window displays.
2. Select the Audit tab.
The text populates the Omission note field.
Invalidating Results
To change the status of a request from Validate back to Review, select one or
more results with status Validate, right-select on the Review and Edit window,
and select the Invalidate option.
If any request participating in a calculation is invalidated, the calculated result
request is automatically invalidated with it.
151
Editing Test Results
You can manually edit a test result. If the edited result value exceeds the normal
range, the severity fields are updated with the appropriate severity value; the
color of the severity column and of the result value changes according to the
severity.
Access the Edit result window from a selected test on the Review and Edit
window:
1. Right-select the selected test and select Edit Result.
The Edit Result window displays.
NOTE: Editing results causes ratios to be recalculated when the test is defined as
a component of a ratio test. For example, if you manually edit an RBC result, the
HCT result is recalculated since the RBC value is a component of the HCT ratio
test.
Field Description
Mnemonic The code that uniquely identifies the comment text.
The maximum number of characters for the Mnemonic
field is 60 characters.
For example, enter the code RR. This is the code that is
associated with the text: Rerun Request.
Class Classification string for use in queries.
Description Describes the text.
153
Field Description
Table Refers to the table to which the comment text is linked.
The maximum number of characters for the Text field is
31921 characters.
Mandatory field entry.
Text This is the comment text that is associated with the
comment code, otherwise referred to as the mnemonic,
and displays as a comment through the Comment field
of the Review and Edit window.
For example, enter the text: Rerun Request. This is the
comment text that is associated with the code RR.
Start / End Dates Dates specifying the time period in which the code and
associated text can be used.
2. To associate the comment text with the comment code, select OK.
Append a coded comment to a test result on the Review and Edit window:
1. Right-select the selected test and select Edit Result Comment.
The Edit Comment window displays.
2. In the comment field of the Edit Comment window, enter a forward slash:(/)
followed by the comment code, which was entered to the Mnemonic field of
the Text editor window. In this example, enter the value ‘/RR.’
155
• Upload parse comments – Determines whether parse comments, which are
generated by the result value parser, are included with result and QC result
comments uploaded to the LIS on patient result upload or QC result upload.
Field Description
Coefficient Depending on the instrument, leave as the default ?
symbol or enter the desired dilution coefficient to be
included in the workorder downloaded to the
instrument.
Condition Depending on the instrument, leave as the default ?
symbol or double-select to select from a list of pre-
defined Dilution conditions to be included in the
workorder downloaded to the instrument.
157
feature allows for entry of a manual or automatic dilution factor and for
instrument-specific reruns.
NOTE: The Advanced Rerun function is multi-record enabled. The Advanced
Rerun applies to all selected requests on the Review and Edit window, not just
the highlighted test request.
Manual Dilution
To accommodate the concept of manual dilutions for reruns, you must specify a
Dilution type of Manual at the Advanced Rerun window. For the test request, you
enter a dilution coefficient, also known as a factor.
The condition field is not used for a Manual Dilution and the field displays
containing a gray ? symbol. In selecting a Dilution type of Manual, the Dilution
coefficient field is not downloaded to the instrument with the workorder. As such,
the dilution must be performed manually at the instrument to reflect the dilution
coefficient field value entered on the Advanced rerun window. The actual dilution
completed on the sample must correspond to the manual dilution coefficient
value.
When the ADVIA CentraLink software receives a result for a manual dilution test
from an instrument, the received result is multiplied by the manual dilution
coefficient value that was entered on the Advanced Rerun window.
Auto Dilution
To accommodate the concept of automatic dilutions for reruns, you must specify
a Dilution type of Auto at the Advanced Rerun window.
In selecting a Dilution type of Auto, the Dilution coefficient and condition fields are
downloaded to the instrument with the workorder. The auto dilution occurs
automatically at the instrument without manual intervention. The actual dilution
completed on the sample directly corresponds to the dilution coefficient value that
was downloaded from the ADVIA CentraLink software.
When the result is uploaded from the instrument to the ADVIA CentraLink
software, the result is not altered by the ADVIA CentraLink software.
In addition, your local technical support provider can implement a MISPL site
function to automatically apply the desired dilution based on your workflow.
You can also specify automatic dilutions on first dilution requests through the Set
auto dilution window. See Setting Up Auto Dilution‚ page 156.
159
The Advanced rerun window displays.
Field Description
Instrument Instrument to which you explicitly target the rerun.
This instrument overrides the default LAS rerun routing.
NOTE: The Instrument field on the Advanced Rerun
window, which is designed to explicitly specify the
instrument where the rerun is to be performed, is
scheduled to be supported in a future release of the
LAS software.
161
Field Description
Dilution coefficient Manual Dilution
When dilution type of Manual is specified prior to rerun,
the dilution coefficient value indicates how much the
sample must be diluted.
After rerun, this value is multiplied against the result
received from the instrument to correct the result for
dilution.
For example, you enter the value 2 for the manual
dilution coefficient. Prior to rerun, the sample must be
manually diluted with an equal amount diluent. After
rerun, the incoming instrument result is automatically
multiplied by 2 to correct for dilution.
The specified manual dilution coefficient is not
communicated to the instrument for automatic onboard
dilution.
The dilution coefficient must be at least 1.
Upon entering a change to the Dilution coefficient field
for a manual dilution, a message displays warning that
after upload from the instrument, the result will be
multiplied by the Manual dilution coefficient. You are
prompted to select Yes to confirm that after upload from
the instrument, the result will be multiplied by the
Manual dilution coefficient.
Auto Dilution
When dilution type of Auto is specified, the dilution
coefficient value is downloaded with the workorder to
the instrument.
The instrument dilutes the sample as per the value in
the dilution coefficient field without manual intervention.
When the result is uploaded from the instrument after
an auto dilution, the ADVIA CentraLink software does
not modify this instrument result value.
You can also view manual and auto dilution data through the Dilution tab on the
Request window by double-selecting the request.
163
Viewing Test Request Information
View the details of a test request on the Review and Edit window:
1. Double-select the selected test.
The Request window displays.
The top part of the Request window displays the following fields:
Field Description
Test Requested test name.
Origin The origin of the request can be External when the
LIS downloads the order for the request, Internal
when the test was requested through the
ADVIA CentraLink system manual order entry,
reflex testing, or a component from a ratio test, or
Unsolicited when a test result was received from
the instrument without a request available in the
ADVIA CentraLink system. Normally the origin is
External.
165
Dilution tab
Field Description
Coefficient The dilution coefficient as requested through the
workorder downloaded from the LIS or as
specified using the Advanced rerun or Set auto
dilution functions.
Condition The dilution condition, such as Neat, Down, or Up,
as requested through the workorder downloaded
from the LIS or as specified using the Advanced
rerun or Set auto dilution functions.
Result coefficient The dilution coefficient as reported by the
instrument.
Result condition The dilution condition (Neat, Down or Up) as
reported by the instrument.
167
Severity Tab
Field Description
Norm Displayed when the result is outside the norm ranges. The
scale of the severity number reflects your range severity
definitions.
It is positive when the result is above the high limit, or
negative when the result is below the low limit.
Delta norm A delta check severity is assigned only if a previous sample
result matching the same patient and test can be found and,
depending on how the delta norm is defined, if the maximum
percent difference or absolute difference is exceeded.
QC The QC severity value can equal a warning, moderate or
severe control failure depending on how you group and define
the severities relative to the available Westgard rules.
Comment tab
The Comment field of the Comment tab includes free text that is received from
the LIS with the request.
169
Audit tab
Field Description
Validation time Date and time the result was validated by the
validation user.
Upload time Date and time the result was uploaded to the LIS
by the Upload user.
Omission time Date and time the request was omitted by the
Omission user.
Omission note Contains the reason for omission, if applicable.
Validation user User who initiated the validation.
Upload user User who initiated the upload.
Field Description
Date/Time Lists the date and time in which each previous
result value for the request was transmitted by the
LIS.
Result value Sorted in order of the most recently received
result, lists all previous results transmitted by the
LIS for the request.
171
Understanding Quality Control
The Quality Control (QC) function allows you to view and print the QC data
collected from all connected instruments. The data can represent control samples
or patient samples. In either case, each group of QC results pertaining to a given
sample is represented by a dedicated QC population to which you can apply
Westgard rule-based control checking and define hold upon failure criteria. You
can view the QC results of a sample in numerical-tabular format or Levey-
Jennings graphical format through the QC Results (Across controls view) window
and through the QC Populations window. You can generate printed reports that
contain graphs and numerical data and statistics by lot or by population.
Control-Based QC Results
Control-based QC results are obtained from tests on samples drawn from QC
material. They are received in populations identified by instrument and QC lot.
For each QC lot record that you create, you must create population records to
hold the target values and ranges per test. You can access other populations
using the QC Lot window.
QC results are included in Westgard checking when they have a numeric value
other than unknown and an Instrument Severity of 0.
QC results that contain a supported comparator can be configured to participate
in Westgard checking, however, these results do not participate in statistics.
Patient-Based QC Results
Patient-based QC results, also called moving average results, are obtained by
averaging test results from patient samples. They are received in populations
defined by instrument and patient species. Moving average populations are
created automatically as incoming results are stored.
Patient results uploaded from an instrument are used for patient-based QC only
when the Check moving average checkbox of the Method window is selected.
When selected, Bull's algorithm smooths the incoming data and generates a new
QC result per instrument batch. You can influence the smothing level by
increasing the value of the Moving average batch size field on the Instrument
window. The larger the batch, the fewer the number of QC results generated and
the less they vary.
Patient results that contain a comparator do not participate in moving averages.
Field Description
Name The name of the QC lot.
Include expired If selected, expired QC lots as well as current QC lots
are included in the display on the QC Lots browser.
If not selected, only current QC lots are included in the
display.
2. To initiate the query and populate the QC Lots browser with the relevant QC
Lots, select OK.
173
Upon display, the QC Lots browser is automatically sorted by Name followed
by Lot Number.
Field Description
Lot Number Unique identifier of the QC lot.
Name Name of the QC lot.
Level Value that describes the lot level. Required for Bio-Rad,
a manufacturer of control material, and other
manufacturers.
This alphanumeric field has a default value that
displays as the ? symbol.
NOTE: This field must be populated with a QC lot level
value, if you plan to export QC results using the Bio-
Rad point data format. If a level value is not entered, an
error message displays informing you that the lot level
is empty.
See Exporting QC Populations to Text and XML Files‚
page 189.
Description Free text area for describing the QC lot.
175
Field Description
Start Date Start date before which the lot cannot be used.
Expiration Date End date after which the lot cannot be used.
QC Populations
The QC Populations window provides access to the QC population table, which
stores records representing statistical populations of QC results sharing the same
instrument, test, and either QC lot, if the result is control based, or species, if the
result is patient based.
All QC results associated with the same QC test of a specific QC lot or species
are grouped in a QC population. The QC population maintains statistics of the
values of its contained results.
To contribute to the statistics, QC results must meet the following criteria:
• The result must have a numeric value.
• The result value must be within the range defined by the Ignored deviation
count. Any result value outside the ignored deviation count value is not used
in statistics.
• The result cannot be flagged by an undefined flag or by a flag with a severity
greater than zero.
• The result must not be omitted.
You can see a graphical display of these statistics through the Levey-Jennings
graph.
Populations can be manually or automatically created within the
ADVIA CentraLink software. If you do not manually create populations prior to
processing controls, populations are automatically created upon receipt of the
first QC result for the respective method and control lot being used. If you choose
to have your populations automatically created, you must still manually specify
the target and reference mean and deviation in order for Westgard checks to be
applied and for QC results to affect autovalidation of patient results.
177
QC populations can be accessed from the main menu, from the Method window,
and from the QC Lot window. When accessed from the main menu or the QC Lot
window, the QC population window displays first.
Access the QC Populations window from the main menu:
1. At the menu bar, select Start > Routine > Quality Control > QC
populations.
The QC population query window displays. You can also access the QC
population query window from the QC Lots window by right-selecting a lot
number row and selecting Populations.
Field Description
Test Limits QC data to a specific test. Double-select the field
to select from a list.
179
The QC Populations browser displays. Depending on the criteria you entered,
this browser displays a range of QC populations.
Field Description
Method Test Method test identifies the test associated with the
the method to which the population applies.
When inserting a new QC population, first specify
the test with the instrument field unspecified.
Setting the test restricts instrument lookup to only
those instruments that support the test.
181
Field Description
Method Instrument Method instrument identifies the instrument
associated with the method to which the
population applies.
Moving average Moving average indicates whether this is a patient-
based population.
When selected, this moving average checkbox
specifies that a species, not a QC Lot, is grouped
with the test and instrument within the QC
population.
Target value The target value for the control product.
NOTE:
When setting the target value to assign population
reference values, the specified value should be
within the range of the assay. A reference value
outside the assay range will cause a severity to be
generated for an invalid reference result if a
control result with a comparator (< or >) is
received.
Target Deviation (1SD) The target deviation for the control product.
NOTE: If the manufacturer supplies the deviation
as 2SD, you must divide that number by 2 to
derive the 1SD value.
Cumulative N The number of results for this test that were closed
out.
Current N The number of results for this test that have not
been closed out.
183
Viewing QC Results for a Population
View QC results for a population from the Results of QC Population window:
1. Right-select the selected population and select Related > Results.
The Results of QC population window displays. From this window, you can
investigate the date and time the QC was assessed, the QC value, and the
QC severity.
185
Levey-Jennings graphs display the following:
• comparator results with a half-open straight line.
• instrument log events associated with an instrument and a method and for
which a QC population exists with a dotted vertical line. Refer to Instrument
Logs‚ page 291.
1-2s A control result exceeds the reference value (mean) plus or minus 2 SDs.
1-3s A control result exceeds the reference value mean plus or minus 3 SDs.
2-2s Two consecutive control results fall on the same side of the reference
value mean plus or minus 2 SDs.
4-1s Four consecutive control results fall on the same side of the reference
value mean plus or minus 1 SD.
10-x Ten consecutive control results fall on the same side of the mean and are
within 1 SD of the reference value mean.
R-4s Two consecutive control results that are on opposite sides of the
reference value (mean) plus or minus 2SD apart.
TIP: Rest your mouse on a plotting dot to see detailed information about it.
- X = sequential number of the value
- Y = value of point
- Test
187
- Assessed time
- Severity
- Cumulative Westgard errors up to that point
The target value and target deviation displayed are values defined on the QC
population window. The cumulative and current N, Mean, SD, and CV%
displayed are the actual calculated statistics.
Change the date interval:
1. Type in a start date in the Since field using the format M/D/YY.
2. Type in an end date in the Until field using the same date format.
3. Select Draw to display the new data for the new date range.
NOTE: Double-selecting either of date fields opens a calendar from which you
can select the date.
189
Access the Export window from the QC Population editor window:
1. Right-select the selected population and select Export.
Field Description
Accessed From Specify the starting time frame from which QC data is
accessed for export.
You can select from the dropdown menu and specify a
date value or choose from among listed relative date
values. By selecting Other, you can customize your
own entry by entering a number, a time interval of day,
week, month, quarter, or year, and by specifying
whether this is in the past or the future.
NOTE: Ensure that the Accessed From value is older
than the Accessed To value. An invalid date range
prevents the successful export of QC data.
191
Field Description
Format Select from the following options:
• XML – All summary data (lot number, expiration
date, target, target deviation, and test value) are
exported at the same time as the point data. An
output file can contain multiple population records
each with multiple result records.
NOTE: If the specified Accessed From value is
more recent than the specified Accessed To value
and you choose XML as the format type, the export
process initiates upon selecting OK, an output file is
created, but the output file does not contain QC
results. No error message displays.
• Bio-Rad point data – Results are output one per line
with the following data per result: Instrument Name,
Lot Number, Test Name, AssessmentDate,
AssessmentTime, Lot Level, QC String Value. Non-
numerical results are skipped.
NOTE: To successfully export data in the Bio-Rad
point data format, a lot level must be specified on
the QC Lots editor window.
NOTE: If the specified Accessed From value is
more recent than the specified Accessed To value
and you choose Bio-Rad point data as the format
type, the following error message displays when
you select OK: Nothing to Export.
Evaluating QC Results
You can obtain QC results in the following ways:
• Uploaded directly from instruments. These results are associated with a
method and with a QC lot.
• Calculated from uploaded results. These results are associated with a
method on a calculated test and with a QC lot.
NOTE: To be used in a calculation, input QC results must share instrument,
QC lot, and assessment time.
• Generated by the patient Moving Average algorithm. These results are
associated with a method and with a species.
QC Results have the following three associated severities:
• Westgard severity
• Instrument severity
• Method severity
To investigate a QC issue, you might have to consider several QC populations.
Querying provides you with a comprehensive view of QC results because you
can access results from across different populations, control lots, or species.
193
Results are displayed on the QC Results (Across controls view) window. You can
also access a specified result set through the QC Results window.
QC Result Parsing
QC results with a supported comparator are parsed into a numerical value and a
comparator as is done with patient results.
QC results with a comparator are handled as numeric results and can be
configured to participate in Westgard checking.
Consider the following examples:
• Result sent by instrument is “<0.02”: This value is saved to the database as
QCResult.NumericValue = 0.02, QCResult.StringValue = <0.02 and
QCResult.Comparator = <.
• Result sent by instrument is “>10.0”: This value is saved to the database as
QCResult.NumericValue = 10.0, QCResult.StringValue = >10.0 and
QCResult.Comparator = >.
NOTE: Patient results with an associated comparator, which could be rendered
after applying method detection limits, are not eligible to contribute to the moving
average.
195
The QC Results (Across controls view) window displays.
197
Field Description
Type The type of control result. The options are as
follows:
• Control – Restricts the result set to those
obtained from QC material, which references
a QC lot.
• Patient – Restricts the result set to only those
obtained from a moving average of patient
results, which references some species.
• Any – No type restriction imposed on the
result set.
Lot Restricts the result set to only those referencing
the specified QC lot.
Species Restricts the result set to those referencing the
specified species.
Include Closed Out Determines whether results that have already
been closed out are included in the result set.
Sort by Determines the relative order of importance of
the following fields for sorting the result set in the
browser: test, instrument, assessment time, and
lot number.
The last sort by value you specify is applied
automatically in your next session.
Select from the following sort by selections:
• Test-Lot-Assessed-Instrument
• Test-Instrument-Assessed-Lot
• Test-Lot-Instrument-Assessed
To initiate the query and populate the result set in the QC Results browser, select
Apply.
Field Description
Test This column is highlighted when the associated method
is determined to be critical as per processing the result.
Instrument This column is highlighted when the associated method
is determined to be critical as per processing the result.
Lot/Species Either the QC lot or the species displays.
Assessed Date and time the result was processed.
C Contains an asterisk when a comment is associated
with the result. The expanded comment is displayed at
the bottom of the screen when the result is highlighted
in the browser.
String Value This column is highlighted when the associated method
is determined to be critical as per processing the result.
QC results with a supported comparator are parsed into
a numerical value and a comparator as is done with
patient results.
The String Value field contains the complete string:
comparator and numeric value.
The Comparator field contains the comparator; the
Numeric value field contains the numeric value.
F Contains an asterisk when a flag is associated with the
result. The expanded meaning of the flag is displayed
at the bottom of the screen when the result is
highlighted in the browser.
199
Field Description
MS This Method Severity field value is set to the highest
absolute value of the following QC severities:
• Westgard severity
NOTE: If a QC result has an associated flag and the
instrument flag control severity is greater than zero,
Westgard checks are not performed and no
Westgard severities are applied. In this case, the
Method Severity field value is set to the instrument
flag control severity even if the flag has a lower
severity than the Westgard severity for the violated
Westgard rule.
• QC severity on type error
• QC severity on invalid reference
Type errors occur when the received result value
cannot be converted to the result type of the
corresponding test.
On receipt of an unexpected non-numeric value, the
Westgard severity is set to 0 and the QC severity on
type error is applied.
Invalid reference error occurs when the QC result
numeric value contains a comparator and the QC result
is not definitively on the same side of the population
reference value.
QC results with an associated flag where the
instrument flag control severity is greater than the value
specified within the QC maximal instrument severity
field on the More tab of the system Options window are
automatically omitted.
This MS value can be reset using the Reset Severity
function. See Resetting QC Severity‚ page 205.
See Understanding Color Display in the Result
Browser‚ page 201 for details on color assignments.
201
Red also displays within the Current column of Review and Edit with a type error
QC result or an invalid reference QC result with comparator.
• A type error QC result occurs when the type of the result value cannot be
converted to the type of the corresponding test.
• An invalid reference QC result occurs when a comparator of a numeric result
is inconclusive regarding the relative position of the value with respect to the
population reference value.
When the QC severity exceeds the QC severity limit, the test, instrument, and
string value columns continue to display in red until the QC problem is addressed
and the Reset Severity function is executed.
Statistics Area
The Statistics area of the QC Results (Across controls view) window allows for
you to see population statistics for the QC result selected within the Result
Browser area.
To contribute to the statistics, QC results must meet the following criteria:
• numeric value
• empty comparator field
• not omitted
• exist inside the range defined by the qc population Ignored deviation count
203
Field Description
Target Value The target value of the QC population for the
selected QC result.
NOTE: The evaluation of the QC result for
Westgard checks is performed against the QC
population reference value and deviation and not
the Target value and deviation.
Target Deviation The target deviation value of the QC population for
the selected QC result.
NOTE: The evaluation of the QC result for
Westgard checks is performed against the QC
population reference value and deviation and not
the Target value and deviation.
N The number of QC results contributing to the
statistics of the QC Population of the selected QC
result.
Mean The mean value of the statistics of the QC
Population of the selected QC result.
SD The standard deviation of the statistics of the QC
population of the selected QC result.
CV % The coefficient of variation of the statistics of the
QC population of the selected QC result.
Current This row displays the current statistics of the QC
population of the selected QC result.
Cumulative This row displays the cumulative statistics of the
QC population of the selected QC result.
205
The Reset QC Severity window displays and is automatically populated with
the Instrument and Test value of the QC result highlighted in the QC Results
browser and is the instrument and test reference for the method for which you
are clearing the severity.
2. Enter a comment.
3. Select OK.
NOTE: The change is not automatically reflected in the QC Results (Across
Controls View) window. To display the reset severity, press F5 to refresh the
window or close the window and reopen it.
207
The QC Result window displays with the Failed Westgard Checks tab
selected.
Field Description
Population QC lot The QC Lot value indicates that the result is part of a
control population. Specifies the QC lot from which the
result was obtained.
Population species The species value indicates that the result is part of a
patient moving average population.
Assessment time The date and time when either a control-based, QC lot
result was assessed on the instrument or a patient-
based, moving average result was generated.
209
Field Description
Method severity The Method severity is the highest QC severity
received on a result since the last QC reset. A QC
result severity is determined by the highest absolute
value of either the Westgard severity, the instrument
severity, the QC severity on type error fields. If the QC
severity of a result exceeds the current method
severity, this value is copied into the Method severity
field.
NOTE: If a QC result has an associated flag and the
control severity that was defined for that flag is greater
than zero, Westgard checks are not performed and no
Westgard severities are applied, even if the flag has a
lower severity than the Westgard severity for the
violated Westgard rule.
See Configuring Instrument Tests (Methods) and Flags‚
page 300.
211
Field Description
Reagent information When a QC result is received from an instrument and
ADVIA CentraLink driver that support the upload of
reagent information, the reagent information is saved
directly to this field
The reagent information can consist of the reagent lot
number, reagent expiration date, and the reagent
sequence number.
The reagent information value stored in this field can
also be inherited from the Reagent information field of
the Method; however, reagent information received at
the result level has priority over global reagent
information stored at the Method.
If the Reagent information field on the LIS 2 tab at the
systems Option window is enabled, result specific
reagent information is uploaded to the LIS.
1-2s, 1-3s, 10-x, 2-2s, If selected, the check boxes indicate the available
4-1s, R-4s Westgard checks that the result failed.
Field Description
Instrument comment Comment received with the result from the instrument.
Parse comment Comment generated by the system. Parse comments
are comments separated by commas.
User comment Free flow text area.
213
1. Right-select the selected QC result and select Related > Flags.
The Flags of QC result browser window displays.
Field Description
QC result population References the applicable QC lot.
QC lot
QC result population References the applicable species.
species
QC result assessment References the date and time that the result was
time accessed.
Instrument flag References the instrument flag defined on the
instrument.
215
Non-numeric QC results are excluded from the statistics but they are not auto
omitted.
In the QC Results (Across controls view) window, non-numeric results are not
assigned a point in the Levey-Jennings -3 to +3 fields.
217
Upload QC results by lot to the LIS from the QC lots window:
1. Right-select the selected lot and select Upload results.
The Upload results window displays.
Field Description
Max Days Specifies the maximum number of days back from the
current day from which to collect results.This value
limits the size of upload messages. If left unspecified,
no day limit applies.
NOTE: If this is the very first time that QC data are
being uploaded, select 1 for 1 day in the Max Days field
to limit the amount of QC data uploaded to the LIS and
to avoid impacting communication with a large amount
of data at one time.
Include not closed out If selected, QC results that are not closed out are
eligible for upload.
If not selected, QC results that are not closed out are
not eligible for upload.
Closing Out QC
Performing the QC Close Out procedure removes all QC data from the Current
QC calculations and includes the closed-out data in the Cumulative QC
calculations.
219
Importing ADVIA 120/2120 QC Data
1. Place the ADVIA 120/2120 QC floppy disk into the disk drive.
2. At the menu bar, select Start > Routine > Quality Control > ADVIA 120 QC
Configuration Import.
The ADVIA 120 QC Import window displays.
3. Double-select the Data file field to specify the data file name.
The Control file field is automatically populated. Do not change this value.
4. Optionally you can enter the Name of the supplier and a Description.
5. Double-select the Instrument field and select from the list.
6. Select OK.
Generating QC Reports
You can generate the following QC reports:
• QC lots
• QC populations
• QC results
221
Field Description
Format Select HTML or Text.
The text format requires a line width of up to 132
characters. Ensure that your Windows font or page
orientation settings are properly set to avoid text
wrapping.
Graphs are available in HTML format only. The graphs
might not display properly when scrolling during
preview.
Instrument The instrument from which you want to include QC
populations in the report.
When a value is entered into the Instrument field, the
Instrument group field is disabled.
Instrument group The instrument group from which you want to include
QC populations in the report.
When a value is entered into the Instrument group field,
the Instrument field is disabled.
From and To Delimit the from and to dates and time. Only QC results
assessed within the specified time frame are used in
the report.
You can enter a range of dates and times or you can
select the dates from the Calendar window.
Entering a date range determines whether current,
cumulative, and report statistics are displayed in the
report heading.
Sort by Select Instrument or Test.
The Sort by field determines the sequencing of the QC
populations displayed in the report.
Preview If selected, a preview of the report is displayed on
screen prior to printing.
223
The Report window displays.
Field Description
Format Select HTML or Text.
The text format requires a line width of up to 132
characters. Ensure that your Windows font or page
orientation settings are properly set to avoid text
wrapping.
Graphs are available in HTML format only. The graphs
might not display properly when scrolling during
preview.
From and To Delimit the from and to dates and time. Only QC results
assessed within the specified time frame are used in
the report.
You can enter a range of dates and times or you can
select the dates from the Calendar window.
225
Manually Entering a Result
Manual result entry is available when you must enter results from a non-
connected instrument.
Access the Result entry window:
1. At the menu bar, select Start > Routine > Result entry.
You can also select the Result entry icon on the toolbar.
The Result entry window displays.
227
Field Description
Clear To clear the Test selection list area, select Clear.
Sample list Select Sample list to enable sample lookup in the
Sample ID field.
Sample ID Double-select to display a list of samples. Select a
sample ID, then OK. Repeat as needed to select more
samples.
Clear button Select to clear the selection in the Sample ID field.
Collected from / to Double-select to display a calendar or enter a date and
time interval to limit the samples selected in MM/DD/YY
format.
Max samples Enter a number to set the maximum number of entries
in the Result Entry window.
Grid type The style in which the result entry grid displays:
• Standard - All selected tests display next to each
other.
• Tiled - New rows are automatically added within the
associated area when the number of tests exceeds
the space allotted for one row of tests.
• Dynamic - Each test displays vertically. The test
name displays next to the associated result.
2. Select OK.
Printing a Worklist
1. At the Result entry grid display, select Print from the tool bar or select the
Print icon.
The Worklist printing window displays.
Field Description
Report type The generated worklist can be of the following types:
Full - All rows and columns of the worklist display.
Rows - Only rows of the worklist display.
Columns - Only columns of the worklist display.
Printer Reference to the printer to which the generated worklist
is output.
229
Field Description
Set as default If selected, the specified Report Type is saved as the
default.
Preview If selected, a preview of the worklist is displayed on
screen prior to printing.
231
The Order Entry window displays.
233
If... Then...
you want to enter multiple tests select each test and press the
SPACEBAR.
Select OK to transfer the selected list to
the Order Entry editor. When a test is
selected, the leftmost column displays a
> character.
NOTE: Sample ID and Requests are the only required fields on the window.
NOTE: If a test name that consists of 20 characters was entered at the Test
window, the test name value appears to be truncated in the Requests field at
the Order Entry window. To verify the entire test name, put your cursor in the
Requests field and press the right arrow key until each of the remaining
characters of the test name display. Avoid entering test names that consist of
20 characters.
4. Enter the Collection D/T.
If the Collection Date and Time values are specified, these values are
automatically populated in the Collection D/T field for the next manual work
order. You can override or clear the value in the Collection D/T field, however,
for each new manual work order created. Once the Order Entry window is
closed, the value in the Collection D/T field is cleared.
5. Double-select Sample types to display a list of sample types.
6. Double-select Container type to display a list of container types.
7. Double-select Patient ID to display a list of patients.
8. At the list of patients, double-select the appropriate patient to enter patient
information on the order in most of the remaining fields.
NOTE: If the patient is not on the list, you can manually add the new patient
information. When you select OK to submit the order, the system prompts
whether you want to create the new patient record. If a patient record already
exists with the Patient ID that you are specifying, a popup window prompts
you to confirm whether you want to update the patient record. If you select
Yes, the patient record is updated and all sample records that reference the
patient record are updated. If you select No because you do not want to
235
Ratio and Component Tests Ordered Manually
A ratio test is a test whose result is calculated from the results of other test
results. A component test is a test whose result can be used in the result
calculation of a ratio test. A test is set up as a ratio test by your administrator. An
example of a ratio test that could be defined is HCT, where RBC and MCV are the
component tests used to calculate the ratio test.
If you order a ratio test manually, the component tests are automatically ordered.
You can also manually order a component test only.
If you delete a component test from the order, the ratio test is automatically
deleted.
If you delete a ratio test from the order, the component tests remain in the order.
237
Accessing Patient Records
Depending on the security parameters defined by your administrator, you could
have limited access to patient information.
1. At the menu bar select Start > Routine > Patients > By birth date / By ID /
By Lastname, Firstname.
You can also select the Patients icon on the tool bar.
The Patients browser window displays.
2. Double-select a patient to access the Patient editor window.
The Patients editor window displays.
3. Modify information in the editor and select OK.
NOTE: Depending on the size setting in use for the Review and Edit window,
the patient name may not display in full. To display the full patient name either
enlarge the size of the Review and Edit window or right-select on the request
and select Related > Patient.
Field Description
Physician ID Identification number that uniquely identifies the
physician.
Last name, First name, Physician name and address information.
Title, Address
239
Field Description
Phone The phone number at which the physician can be
reached.
Fax The fax number to which reports, which are Via fax
enabled as specified at the Report window, can be sent.
NOTE: This fax number value serves as the default to
which files are sent when the Via fax checkbox at the
Report window is selected. Refer to Generating a
Sample Report‚ page 86.
Report model The name of the template in which the physician report
is based.
Language The language used when printing reports for samples
for this physician.
241
Configuring Instrument Tests (Methods) and Flags .......................300
Setting Instrument Flags ..............................................................300
Setting Instrument Tests (Methods) ............................................302
Configuring Westgard Rules ........................................................315
Method Setup Targeting Function ...............................................319
Setting Up Coding Systems ...............................................................320
Using Coding Systems .................................................................320
Setting Up a Test Code .................................................................320
Setting up a Sample Type Code ...................................................321
Setting Up a Container Type Code ..............................................322
Setting Up a Species Code ...........................................................323
Defining Sample Sources .............................................................324
Setting Up a Sample Source Code ..............................................325
Configuring Patient Locations ..........................................................327
Configuring a Report Model ..............................................................328
Defining Print Commands ..................................................................331
243
The Tests browser window displays.
The Test editor window displays with the Basic tab activated.
Field Description
Name A unique identifier for the test
Upon entering a change to the Name field, a message
displays warning that modifying the Name of the test
does not modify the corresponding requestable name.
If necessary, update the Name of the corresponding
requestable
NOTE: Do not enter a test name value of 20 characters
or more. While the test name is accepted by the
ADVIA CentraLink software, the test name value
appears to be truncated when it displays at the Order
Entry and Review and Edit windows.
245
Field Description
Sample type Whole blood, serum, plasma, or other.
Upon entering a change to the Sample type field, a
message displays warning that modifying the Sample
type can affect how the test is processed at the
instrument.
Description Description of the test.
Group Reference to the Test Group, which represents the
name of the group into which tests are organized.
Patient data type The acceptable patient data type values that apply to
patients results include the following:
• Numeric - Numeric results are expressed in a given
Control Unit and can be used in numerical
computation; for example, in comparisons against
normal ranges and statistics.
• String
• Enumerated - Enumerated results must match one
of a fixed set of result choices, for example, +, ++,
+++.
• Image - Image results can reference image data on
the file system.
• Complex result values are composed of individual
pieces of arbitrary labeled information, which allows
for loss-less forwarding from the instrument to the
LIS. You cannot view or edit these result values.
• Graph - Electrophoresis results can display online
as graphical representations and can be printed on
sample reports of type HTML.
• NOTE: While electrophoresis is supported, the
functionality is not currently used in the
ADVIA CentraLink software.
247
Field Description
Patient unit Reference to the unit in which the patient results of
numeric tests are expressed.
WARNING: The units of measure for a given test must
be defined identically at the LIS, in the
ADVIA CentraLink software, and at the instruments.
The units for test results uploaded from the instrument
are not read by the ADVIA CentraLink software. You
must predefine the units for tests in the
ADVIA CentraLink software to match the units for tests
on the instrument. If units of measure of results are
manually changed on an instrument, you must change
the units of measure for the test in the
ADVIA CentraLink software at that time. In addition,
you must purge all existing results for the test from the
ADVIA CentraLink software. Units of measure are not
uploaded to the LIS from the ADVIA CentraLink
software.
Control unit Reference to the unit in which the QC results of
numeric tests should be expressed.
Alternate unit Set an alternate unit if the unit used in the
ADVIA CentraLink software is different from the one
reported by the instrument.
Upon entering a change to the Alternate unit field, a
message displays warning that modifying the Alternate
unit can affect the reporting of new results.
Unit coefficient Coefficient (factor) for converting from the standard to
the alternate unit.
Upon entering a change to the Unit coefficient field, a
message displays warning that modifying the Unit
Coefficient can affect the reporting of new results.
249
Field Description
Control reported The number of decimals used to represent instrument,
decimals patient moving average, and calculated QC results is
configurable. The Control reported decimal value
determines the number of decimals to which the QC
result is rounded.
Upon entering a change to the Control reported
decimals field, a message displays warning that
reported decimals of a numeric test can round both new
and existing QC results.
If you enter a value less than 2, a message displays
warning that the precision level of QC results being
registered will be reduced.
For instrument QC results, refer to Affects of Control
Reported Decimals on Instrument QC Results‚
page 250.
For patient moving average QC results, refer to Affects
of Control Reported Decimals on Patient Moving
Average Results‚ page 253.
For calculated QC results, refer to Affects of Control
Reported Decimals on Calculated QC Results‚
page 254.
251
• Control reported decimal default value (?)
When the ? symbol populates the Control reported decimals field for
instrument QC results, the decimal precision of the instrument QC result
uploaded to the LIS is the same as the decimal precision received from the
instrument. No rounding occurs except when more than 9 decimals are
received from the instrument. Under this circumstance, the numeric QC result
value is rounded to 9 decimal places.
• Control reported decimal value (0)
When you enter a Control reported decimals value of 0, the decimal precision
of the instrument QC result uploaded to the LIS is 0 decimal places.
• Control reported decimal value (1)
When you enter a Control reported decimals value of 1, the decimal precision
of the instrument QC result uploaded to the LIS is 1 decimal place.
• Control reported decimal value (2-9)
When a Control reported decimals value of 2-9 is entered, the decimal
precision of the instrument QC result uploaded to the LIS is the specified
number of decimals: 2, 3, 4, 5, 6, 7, 8, or 9.
? * * 2 2 * *
0 * 0 2 2 0 0
1 * 1 2 2 1 1
2-9 * 2-9 2-9 2-9 2-9 2–9
* = whatever value comes from the Instrument
Table 1: Decimal Places for Instrument QC result
253
Mean and SD
When the Control reported decimal value is set to 0, 1, or the ? symbol, the
displayed value on the QC Across Controls View window of the Mean and SD
fields is 2 decimal places.
When the Control reported decimal value is set between 2 and 9 inclusive, the
displayed decimal precision of the Mean and SD fields is the specified number of
decimal places.
Target Value and Target Deviation
On the QC Across Controls View window, the Target value and Target Deviation
value are displayed as entered without rounding.
Upload to LIS
Regardless of the value that populates the Control reported decimals field for
patient moving average QC results, no patient moving average QC result is
uploaded to the LIS.
255
Mean and SD
When the Control reported decimal value is set to 0, 1, or ?, the displayed value
on the QC Across Controls View window of the Mean and SD fields is 2 decimal
places.
When the Control reported decimal value is set between 2 and 9 inclusive, the
displayed decimal precision of the Mean and SD fields is the specified number of
decimal places.
Target Value and Target Deviation
On the QC Across Controls View window, the Target value and Target Deviation
value are displayed as entered without rounding.
Upload to LIS
• Control reported decimal default value (?)
If the ? symbol populates the Control reported decimals field for calculated
QC results, the decimal precision of the calculated QC result uploaded to the
LIS is the variable result length of the calculation, which is the string value.
• Control reported decimal value (0)
When you enter a Control reported decimals value of 0, the decimal precision
of the calculated QC result uploaded to the LIS is 0 decimal places.
• Control reported decimal value (1)
When you enter a Control reported decimals value of 1, the decimal precision
of the calculated QC result uploaded to the LIS is 1 decimal place.
• Control reported decimal value (2-9)
When a Control reported decimals value of 2-9 is entered, the decimal
precision of the calculated QC result uploaded to the LIS is the specified
number of decimals: 2, 3, 4, 5, 6, 7, 8, or 9.
Control Numeric Across Mean/SD Levy BioRad Sent to
Reported Value Control Jennings Data LIS
Decimal (String (Y value)
Value)
Result
0 length of 0 2 2 0 0
calc.
Result
1 length of 1 2 2 1 1
calc.
Result
2-9 length of 2-9 2-9 2-9 2-9 2-9
calc.
* = varying result value of the calculation
Table 3: Decimal Places for Calculated QC result
257
3. Select the Advanced tab.
4.
Field Description
Omit on LAS update Select this checkbox for external tests for which no
results are expected. Upon receipt of an external test
request, the ADVIA CentraLink system forwards it to
the LAS for sorting and subsequently omits it.
If only one LAS Order Translator is specified on the
LAS tab of the system Options window, the test request
is omitted after it is sent to the configured LAS.
If two LAS Order Translators are specified on the LAS
tab of the system Options window, the test request is
omitted after it is sent to both configured LAS.
Default value Pertains to morphology flags. When specified, a default
value such as “negative” is automatically assigned to
results missing in a message from an instrument with
“Full sample upload” set.
259
5. Select the Calculation tab for additional fields.
Field Description
Calculation A MISPL program used to calculate the result of a ratio
test based on the results of the component tests. Your
local technical support provider defines this program.
The program contains a calculation formula, which you
can view in this field. If this formula is changed, only the
future ratio tests are affected. The test results available
in the database stay the same.
Upon entering a change to the Calculation field, a
message displays warning that modifying the
calculation can affect the reporting of new and existing
results.
Norm severity limit This normal severity limit is one of the values against
which auto validation of calculated test results is
determined when a method is not associated with the
calculated test.
Defining Calculations
A calculation is a string-valued MISPL program that is used to calculate the result
of a test from the results of other tests. The formula is compiled against the
sample class for calculations involving patient results and against the QC result
class for calculations involving QC results. As such, the calculation includes
reference only shared members like functions NumericValue() and StringValue().
If this calculation is changed, only future results are affected.
261
1. At the menu bar, select Start > Configuration > Test groups.
The Test groups window displays.
2. Select the New icon to access the Test group editor window.
3. Enter the name of the test group.
4. Select OK.
Field Description
Name Name of the test group.
263
The Unit editor window displays.
Field Description
Name A unique name for the unit, such as mL. This is a
required field.
Dimension The dimension of the unit, such as Volume. Double-
select to display a list of dimensions and make a
selection. This is a required field.
Upon entering a change to the Dimension field, a
message displays warning that modifying units can
affect the reporting of new results.
265
Setting a Dimension for a Unit
A dimension is a measure for a unit that is used in a test.
1. At the menu bar, select Configuration > Dimensions.
The Dimensions browser window displays.
2. Double-select the appropriate dimension.
The Dimension editor window displays.
267
7. Upon completion, close the open windows.
Field Description
Code Unique identifier for the result.
Expansion Description of the result choice. If an expansion value is
defined, it displays on the Review and Edit window and
is transmitted to the LIS.
Severity Norm severity value that is assigned when this result is
received.
269
The Norm editor window displays.
Field Description
Evaluation order Required when you are adding additional ranges to the
default range. Defines the order in which ranges are
evaluated. Ranges with higher severity levels are
assigned a lower evaluation order so that they are
evaluated first. After the first non-zero severity is
identified, normal ranges are not evaluated.
Method The norm applies only to results obtained from the
instrument associated with the method.
Sex Patient sex.
271
Setting Delta Norms
A delta norm specifies the normal variation in results between two successive
instances of the same test performed on different samples from the same patient.
The delta norm table stores threshold values for result changes between
consecutive tests on the same patient using different samples.
A delta norm value can be expressed as either of the following:
• Percentage change from the earlier result. Each result is verified against any
delta norms that were defined for that test when a previous result is available
for the same patient and when the time lapse between the two results does
not exceed the delta check limit specified for the test.
• If the Limit is absolute field is enabled, the absolute value of the difference
between the current result value and a previous result value are evaluated. If
the absolute difference exceeds the value specified within the Limit field, the
Delta norm severity is applied.
Access the Delta norms editor window:
1. At the menu bar, select Start > Configuration > Tests.
The Tests browser window displays.
2. Select the appropriate test.
3. Right-select the selected test and select Delta norms.
273
The Delta norm editor window displays.
Field Description
Test The test for which Delta norm check is configured and
based.
Evaluation order Defines the order in which delta limits are evaluated.
Limits with higher severity levels are assigned a lower
evaluation order so that they are evaluated first.
After the first non-zero severity is identified, normal
ranges are not evaluated.
Species Patient species. If specified, the delta norm applies only
to this species.
NOTE: You set the time interval for delta checking on the Tests window. For
more information, see Configuring Test Settings‚ page 243.
275
Defining Test Aspects
You can define multiple result aspects or characteristics for a result from the
ADVIA Centaur® system.
The Patient result selector configured on the Basic tab of the Method is the
instrument result aspect that displays on the Review and Edit window. The
Control result selector configured on the Basic tab of the Method is the
instrument result aspect that displays on the QC Results window.
Although only one aspect displays on the Review and Edit window and on the QC
Results window, the ADVIA CentraLink system transmits all defined aspects to
the LIS.
1. Select the Instruments icon.
The Instruments browser window displays.
2. Select the appropriate instrument.
3. Right-select the selected instrument and select Aspects.
4. Select New on the toolbar to add a new Aspect.
For more information on supported result aspects, see Result Detail tab‚
page 165.
Field Description
Name Unique identifier of the requestable.
Explicit When selected, the requestable is visible in the list of
requestables on the Order Entry window and can be
manually requested. Simple requestables, which are
not explicit, can still be requested as part of a panel
requestable.
Type of Requestable Valid values include the following: Simple and Panel.
Test Reference to the test which can be requested through
this requestable.
277
The Description field displays in place of the Test field.
5. Type a description of the panel, and select OK.
The new name is added to the list of requests.
6. In the Requestables browser, select the new panel name.
7. Right-select the selected panel and select As panel requestable >
Members.
The Panel members browser window displays.
8. Select the New icon on the toolbar.
The Panel member editor window displays.
9. Double-select the Requestable field on the Panel member editor window.
A new Requestables browser window displays.
10. Highlight the test or panel that you want to include in the new panel and select
OK.
The newly opened Requestables browser window closes. The selected name
displays on the Panel member editor window.
11. To add the name to the Panel members browser, select OK.
12. Repeat steps 9 - 11 until all panel members are selected.
Deleting a Panel
1. At the menu bar, select Start > Configuration > Requestables.
The Requestable browser window displays.
2. Select the panel to delete.
3. Right-select the selected panel and select As panel requestable >
Members.
The Panel members browser window displays.
4. Select the test or panel to delete and select Delete.
5. Select Yes to delete the panel member.
6. Select Close on the Panel members browser to return to the Requestables
browser window.
279
Defining Instruments
The Instruments editor window defines the instruments connected to the
ADVIA CentraLink system.
1. At the menu bar, select Start > Configuration > Instruments.
You can also select the Instruments icon on the toolbar. The Instruments
browser window displays.
2. At the editing toolbar, select the New icon.
The Basic tab of the Instrument editor window displays.
Field Description
Name The unique identifier of the instrument.
281
Field Description
Parent Instrument Only instruments of type Normal can be associated to a
Parent Instrument. A Parent Instrument must always
refer to an instrument of type Concentrator.
NOTE: If you specify a parent instrument value, you
cannot specify a translator value. This safeguard is
employed to ensure that communication for instruments
defined to a concentrator is managed by the translator
of the concentrator.
Group Reference to the containing instrument group.
NOTE: All instrument records, that is, those of type
Normal and of type Concentrator, can refer to an
instrument group. No restriction is imposed on an
instrument’s reference to an instrument group.
In a concentrator configuration the following applies:
• For test requests that are scheduled against the
concentrator, the instrument group references the
instrument group of the concentrator.
• For test requests that contain a result from the
concentrator, the instrument group references the
normal instrument that generated the result.
Translator References the translator record, which defines
communication with the instrument.
NOTE: If you specify a translator value, you cannot
specify a parent instrument value. This safeguard is
employed to ensure that communication for instruments
defined to a concentrator is managed by the translator
of the concentrator.
Coding system References the coding system record, which defines
the mapping of tests and other codes between the
ADVIA CentraLink system and the instrument.
Refer to Setting Up Coding Systems‚ page 320.
283
3. Select the Advanced tab.
The Advanced tab of the Instrument window displays.
Field Description
Barcode translation References a string-valued, instrument-based MISPL
function. The MISPL function is to determine whether
an incoming barcode identifies a patient sample, a
control sample, or a sample with an unreadable
barcode and to translate the incoming barcode into
either a sample barcode or a QC lot code that matches
a database record.
Upon entering a change to the Barcode translation
field, a message displays warning that modifying the
Barcode translation can affect sample identification.
285
Field Description
Full sample upload If selected, a patient result upload is considered final;
that is, no additional results for the sample are
expected from the instrument. If some results are
missing upon result upload, their default values as
defined in the test record are automatically assigned.
NOTE: Full sample upload does not apply to QC
results.
On end result Reference to a MISPL function, which is executed
message when a complete result message is received from the
instrument.
287
• Coding system
• Default sample type
NOTE: When a sample type is not defined for the sample in the
ADVIA CentraLink software, the sample type of the concentrator is
downloaded to the normal instrument in the Workorder message.
• Default container
• Enable rescheduling parameter
NOTE: When replying to a Query message, the Enable rescheduling
parameter of the concentrator is used because tests are scheduled against
the concentrator. The ADVIA CentraLink software cannot determine
beforehand which of the normal instruments connected to the concentrator
will receive and execute a test request.
• Download by worklist
• On All query match target
• On All query max samples
Test requests are scheduled to the concentrator, which targets the connected
normal instruments for processing.
289
workorder information for a given sample was sent to the concentrator previously
by checking the Sample log table for applicable concentrator instrument records.
Moving averages
Moving averages refer to the normal instrument. To enable moving averages,
select the Check moving average checkbox on the method of the normal
instrument.
QC Results
At the QC Results (Across controls view) window, QC results received from the
concentrator are associated with the normal instrument from which they were
generated, not the concentrator. These QC results display with the normal
instrument. The QC flags attached to the QC results refer to the flags of the
normal instrument. QC severities raised for these results correspond to those
defined on the Method records of the normal instrument.
291
NOTE: You can also access this window through the Method window.
The Instrument logs browser window displays.
2. At the Instrument logs browser window, select the New icon or press Insert.
The Instrument logs editor window displays.
Field Description
Instrument Instrument to which the log applies.
When the Instrument log browser is accessed through
the Method window, this field is automatically populated
with the instrument value on the Method window.
Method Reference to a specific method.
When the Instrument log browser is accessed through
the Method window, this field is automatically populated
with the test value on the Method window.
293
2. Right-select the appropriate instrument and select Setup targeting.
Field Description
Enable Determines whether requests for the instrument's tests
can be targeted to the instrument.
Seq no Determines the order, among all eligible instruments, in
which the current instrument is considered as target for
a matching request.
Field Description
Delete ready worklists If selected, all Ready status worklists targeted to the
instrument are deleted.
295
The QC population query window displays.
2. Select OK.
The QC Populations browser displays.
3. Select New on the editing toolbar.
The QC Population editor window displays.
4. Enter the Method test.
5. Select Moving average.
By selecting Moving average, you are specifying that this is a patient-based
population. The selected moving average checkbox specifies that a species,
not a QC Lot, is grouped with the test and instrument within the QC
population.
6. Enter the remaining data and select OK.
See QC Populations‚ page 177 for details on defining QC populations.
Automatically Creating QC Populations for Moving Average Data
If you did not create QC Populations for the moving average data, the
populations are automatically created when patient results are received from the
instruments. Once these populations exist, however, you must define the
Reference value and Reference deviation in order for Westgard checks to apply.
NOTE: Westgard rules are applied using the Reference value and Reference
deviation rather than the Target value and Target deviation.
To initially set the Target value and Target deviation as the Reference value and
Reference deviation:
1. At the QC Population browser window, select the population for which you
want to define the Reference value and Reference deviation.
2. Right-select the selected population and select Set Target.
The Set Target window displays.
3. Enter the Target value and Target deviation.
4. Select Set as reference.
5. Select OK.
297
Creating or Modifying Instrument Groups
You can create groups of instruments. An instrument can belong to one
instrument group only. You can add instruments to a group through the
Instruments editor window.
References to the containing instrument group are automatically created
whenever new requests or QC results are created, which improves query
performance. When an instrument changes groups, however, requests and QC
results are not synchronized.
NOTE: When instrument groups are created, patient results received prior to
instrument group creation are not returned in queries for the specified group.
NOTE: If referenced by requests, QC results, or other instrument groups, an
instrument group should not be deleted. Deleting an instrument group that is
referenced can result in the generation of empty audit logs. Instead of deleting
instrument groups that are referenced by requests, QC results, or other
instrument groups, reassign them.
Access the Instruments Groups editor window and enter or modify an instrument
group:
1. At the menu bar, select Start > Configuration > Instrument groups.
The Instrument groups browser window displays.
2. To create a new instrument group, select the New icon or press Insert.
3. To access an existing instrument group, double-select the appropriate
instrument group.
The Instrument Group editor window displays.
4. Enter or modify the Name and Description of the instrument group.
5. Select OK.
Assign an instrument to an instrument group:
1. At the menu bar, select Start > Configuration > Instruments.
The Instruments browser window displays.
2. At the Instruments browser window or the Instrument editor window, right-
select the instrument and then select Set Group.
The Set Group editor window displays.
299
Configuring Instrument Tests (Methods) and Flags
Setting Instrument Flags
You define Instrument flags for every new instrument configured in the
ADVIA CentraLink system. The ADVIA CentraLink system only receives flags
that are already defined. Instrument flags that are not configured in the
ADVIA CentraLink system are ignored.
NOTE: QC results received with undefined instrument flags are automatically
omitted from the ADVIA CentraLink software.
An instrument flag has a code, explanatory text (expansion), and two severity
flags. You can define the severity that is assigned when an instrument flag is
associated with a QC result, and you can define the severity that is assigned
when an instrument flag is associated with a patient result. Defining these flags
independently allows for more precise instrument severity determinations
between QC result and patient results respectively.
To see the flags on the Review and Edit window, you must define the instrument
flags.
Access the Instruments window:
1. At the menu bar, select Start > Configuration > Instruments.
The Instruments browser window displays.
2. Select the instrument for which you are defining flags.
3. Right-select the selected instrument and select Related > Flags.
The Flags defined on instrument browser window displays.
4. Double-select the appropriate flag.
Field Description
Instrument This field is automatically filled with the name of the
instrument you are modifying.
Code Unique identification for the flag. This code must match
the code used by the instrument.
Expansion Determines the flag description on the Review and Edit
window and on reports.
Patient severity The overriding patient severity flag value applicable to
patient results, which automatically sets the Instrument
value on the Severity tab of the Request window to the
highest severity.
NOTE: If the patient severity flag value is greater than
the instrument severity value on the Severity tab of the
Request window, then this patient severity flag value
overwrites the instrument severity value on the Request
window.
301
Field Description
Control severity The overriding QC severity flag value applicable to
control samples, which automatically sets the
Instrument severity field value of the QC results window
to the highest severity.
If this control severity flag value is greater than the
Instrument severity field value of the QC results
window, then this control severity flag value overwrites
the Instrument severity field value of the QC results
window.
NOTE: If the instrument severity flag is not relevant to
QC results, set the Control severity at the Instrument
Flag window to 0. If the instrument severity flag is
relevant to QC results, set the Control severity at the
Instrument Flag window to equal the highest value of
the Westgard rules applicable to that method.
If an unknown flag is received, the field value is set to
-5.
303
The top portion of the Method window includes the following fields:
Field Description
Test Reference to the test that can be performed on the
instrument.
NOTE: If the test is a calculated test, the
ADVIA CentraLink software does not download orders
or accept results from the instrument.
Instrument This field is automatically filled with the name of the
instrument.
Basic Tab
The Basic tab fields include the following:
Field Description
Patient result selector This selector is a reference to one of the instrument’s
aspects. The Patient result selector determines the
aspect that represents the actual result value for patient
results.
This aspect displays on the Review and Edit window.
The ADVIA Centaur system is an example of a system
that makes use of this field value.
Commonly used aspects are DOSE (concentration)
and INTR (interpretation). For information on defining a
result selector see Defining Test Aspects‚ page 276.
305
Field Description
Low detection limit Linearity Range: If results fall outside the delimited
range, they are converted to the detection limit,
preceded by a <, and displays on the Review & Edit
window. The value displayed on the Review & Edit
window is the value uploaded to the LIS.
Upon entering a change to the Low detection limit field,
a warning message displays. The message prompts
that modifying the Low detection limit will change new
results from the instrument that are less than the Low
detection limit to the Low Limit value, preceded by the
“<” symbol.
High detection limit Linearity Range: If results fall outside the delimited
range, they are converted to the detection limit,
preceded by a >, and displays on the Review & Edit
window. The value displayed on the Review & Edit
window is the value uploaded to the LIS.
Upon entering a change to the High detection limit field,
a warning message displays. The message prompts
that modifying the High detection limit will change new
results from the instrument that are greater than the
High detection limit to the High Limit value, preceded by
the “>” symbol.
Enable targeting Select this checkbox if requests for the method's test
are targeted to the method's instrument.
307
Field Description
Counter key label Specify the key to be used for counting test results in
the Diff Pad. Do not edit the field for tests that do not
use the Diff Pad. Ensure that the ? symbol displays in
the field.
Upon entering a change to the Counter key label field, a
message displays warning that modifying the Counter
key label can affect the manual entry of results using
the Diffpad.
Reagent information Upon receipt of a global reagent information message
from an instrument, the reagent information is stored in
this field.
If result-specific reagent information does not exist for
the result associated with this method, global reagent
information is also saved to the Reagent information
field of the Request or QC request window for the
result.
NOTE: Reagent information received at the result level
has priority over global reagent information stored at
the Method.
309
Field Description
QC severity This field is automatically filled with the highest QC
severity of the method since the last QC reset and can
be one of the following: Westgard QC severity,
instrument flag control severity, QC type error severity,
QC severity on invalid reference.
See Resetting the QC Severity from the QC Results
(Across Controls View) Window‚ page 205.
QC severity on type The value assigned to the QC severity when a control
error result is received that cannot be converted to the test's
control data type.
This integer value defaults to 5.
Refer to Type Error QC Result‚ page 194.
QC severity on invalid QC severity on invalid reference is the value assigned
reference to the QC severity when a control result is received with
a comparator that prevents it from being
unambiguously positioned with respect to the
population reference value.
For example:
Control result value <10
Population reference value 5
This integer value defaults to 5.
Refer to Invalid Reference QC Result‚ page 195.
Allow on type error Allow on type error determines whether automatic
validation proceeds when a patient result is received
that cannot be converted to the test's patient data type.
311
severity limit of the method, the result is automatically validated. If any of the
limits are left unspecified, no auto validation occurs.
Westgard Tab
By default, Westgard checks are enabled. You have the option, however, of
disabling individual Westgard checks.
When any of the fields of the Westgard tab is set to 0, the individual Westgard
check is disabled. To the right of a disabled Westgard field, the label “(disabled)”
displays. When a Westgard check is disabled, no Westgard comment is added to
the QC result and no Failed Westgard comment is uploaded to the LIS.
The Westgard tab includes the following fields:
313
Field Description
Include comparator Determines whether comparator QC results contribute
QC results to Westgard checks.
• When the checkbox is selected, the comparator QC
results contribute to Westgard checks.
• Default - When the checkbox is not selected, the
comparator QC results do not contribute to
Westgard checks. The type error severity is raised
for the Method, which prevents autovalidation of all
patient results for the specified method. This QC
result is not taking into account for Westgard
checks of subsequent QC results.
When a comparator QC result does not contribute to
Westgard checks, a comment displays in the Comment
field of the QC Result (Across controls view) window.
This additional comment is added to existing
comments. The comment is not uploaded to the LIS
and is not listed on reports. Refer to the description for
the Comment field in the Statistics Area‚ page 202.
To enable this feature for all methods of an instrument
or test, refer to Configuring Westgard Rules for an
Instrument‚ page 316 or Configuring Westgard Rules
for a Test‚ page 317.
By default, the checkbox is not selected.
315
Configuring Westgard Rules for an Instrument
You can simultaneously setup Westgard checking for all methods of an
instrument through the Setup Westgard window.
Customize the QC severity level for all Westgard checks performed on all results
from a single instrument:
1. At the menu bar, select Start > Configuration > Instruments.
The Instruments browser window displays.
2. Select the instrument for which you are setting limits.
3. Right-select the selected instrument and select Related > Tests.
The Tests on instrument browser window displays.
4. Double-select the appropriate test.
The Method editor window displays.
5. Select the Westgard tab.
6. Enter the new severity level for each Westgard check.
When any of the fields of the Setup Westgard window is set to 0, the
individual Westgard check is disabled. To the right of a disabled Westgard
field, the label “(disabled)” displays. When a Westgard check is disabled, no
Westgard comment is added to the QC result and no Failed Westgard
comment is uploaded to the LIS.
7. Select Apply westgard checks.
If this check box is not selected, the Westgard rules are not applied to the
method.
If you select Include comparator QC results, comparator QC results
contribute to Westgard checks for all methods of a test. When a comparator
QC result does not contribute to Westgard checks, a comment displays in the
Comment field of the QC Result (Across controls view) window. Refer to the
description of the Comment field in the Statistics Area‚ page 202.
8. Select OK.
317
If this check box is not selected, the Westgard rules are not applied to the
method.
6. If you select Include comparator QC results, comparator QC results
contribute to Westgard checks for all methods of a test.
When a comparator QC result does not contribute to Westgard checks, a
comment displays in the Comment field of the QC Result (Across controls
view) window. Refer to the description of the Comment field in the Statistics
Area‚ page 202.
7. Select OK.
Field Description
Enable Determines whether matching test requests can be
targeted to the instrument.
Seq no Determines the order, among all instruments capable of
performing the associated test, in which the associated
instrument is considered as target for a matching
request.
319
Setting Up Coding Systems
The ADVIA CentraLink system typically communicates with many different
applications using different names for the same item. To avoid naming conflicts,
you can set up coding systems.
A coding system is a set of names used by a given application to denote
equivalent ADVIA CentraLink system names. Coding systems are stored in the
ADVIA CentraLink system database and can be modified or expanded at any
time. in order for the changes to take effect after modifying a coding system, you
have to stop and restart the services and translators.
Coding systems can contain codes for the following items
• Tests
• Sample types
• Container types
• Species
• Sample source
321
the serum sample type. If this occurs, you can create a sample type code that
associates the abbreviation “Sr” with the ADVIA CentraLink system’s serum.
NOTE: If you do not specify a LIS code for serum, the ADVIA CentraLink system
expects the LIS to use and understand the ADVIA CentraLink system identifier
“Serum.”
Upon entering a change to any field of the Sample type code window, a message
displays warning that modifying Code values can affect the reporting of new
results.
1. At the menu bar, select Start > Configuration > Coding Systems.
The Coding system browser window displays.
2. Select the appropriate instrument.
3. Right-select the selected instrument and select Related > Sample type
codes.
The Sample type codes in coding system browser window displays.
4. Select New on the toolbar to add a new sample type code.
The Sample type code editor window displays.
Coding system is populated automatically and refers to the coding system to
which the test belongs.
5. Enter the Sample type.
6. Enter the Value.
This code is the value recognized by the LIS, LAS, and instrument.
7. Enter Match order.
Match Order is an integer value used when a single code value is mapped to
multiple sample types and unsolicited results are uploaded from the
instrument. The ADVIA CentraLink system picks up the mapping with the
lowest match order.
8. Select OK.
323
5. After entering the relevant field values, select OK.
Field Description
Name Unique identifier of the sample source.
Description Free text description of the sample source.
325
The Sample source code window displays.
Field Description
Coding system Reference to the coding system that contains the code.
Sample source Reference to the sample source that is identified by the
code.
Value Code identifying the sample source within the coding
system.
327
Configuring a Report Model
Report models are templates for reports. Report models allow you to configure
header, body, and footer information. If a report model is not defined, a default
report style is used.
1. At the menu bar, select Start > Configuration > Report models.
The Report model browser window displays.
2. To add a new Report model, select New on the toolbar.
The Report model editor window displays.
Field Description
Name Unique identifier for the report model.
Comment Full name or explanation of the report model.
Define a report model through the report model editor window by completing the
following steps:
1. Enter or modify the Name and Comment.
2. Double-select Header.
The Texts based on table browser window displays. You can select from the
available header designations. If you need a customized header, contact your
local service provider for assistance.
329
Right-select the selected header and select Preview to display the header.
3. Double-select Column heading list.
The Multi-lingual text editor window displays.
a. Select New to create a new column heading list or Edit to modify an
existing one.
b. Enter or modify the comma-separated list of column headings in the
bottom Editor field.
The list of headings must be in the same order as the list of column types.
c. Select a language.
d. Select Save to record the list in the Report model editor.
4. In the Column type list field, specify each column type in a comma-separated
list using only the specified types.
NOTE: The order of the column types must correspond to the order of the
column headings.
5. Double-select Footer.
The Texts based on table browser window displays. You can select from the
available footer designations. If you need a customized footer, contact your
local service provider or distributor for assistance.
6. Select OK.
NOTE: For information on printing a report, see Generating a Sample Report‚
page 86 and Generating QC Reports‚ page 220. For information on assigning a
report model to a physician, see Accessing Physician Records‚ page 239. For
information on setting a report model as the default, see Customizing Reports‚
page 398.
Field Description
Selection only If selected, print only the selected records.
331
Field Description
Device type The options include the following: File, Terminal,
Printer, Clipboard, Excel, or Word.
The default for printing is Printer.
Format The options include the following: Text or HTML.
Printer Reference to the printer to which output is directed.
Set as default If selected, allows you to save the value in the Printer
field as the default user printer.
Directory Target location for generated files.
File Name of the generated target file.
Copies Number of copies to be printed.
333
Restoring the Databases from a Tape Backup ...........................384
Restoring the Databases from a Disk Backup ............................387
Selecting and Adding Languages .....................................................391
Understanding User Interface Languages ..................................391
Changing User-Defined Languages ............................................391
Defining Languages for Users .....................................................393
Setting the Language for Add-on Programs ...............................393
Printing ................................................................................................395
Customizing Reports ....................................................................398
Customizing the Toolbars ..................................................................399
Troubleshooting .................................................................................402
Error Messages .............................................................................402
Troubleshooting and Tips ............................................................403
3. At the toolbar, select the New icon or at the keyboard, press Insert.
335
The User editor window displays.
Field Description
Initials User’s initials.
Last name User’s last name.
First name User’s first name.
Login name Unique identifier for the user. When a user first logs in
to the ADVIA CentraLink system, the password is the
same as this login name.
Type Possible values in increasing order of authority are
Guest, User, System manager, and Developer.
Siemens strongly recommends that you select “User”
as the type for all operators. For more information on
using types, see Assigning Privileges‚ page 342.
Language User’s preferred language. This setting overrides the
site default specified in application-level settings.
Enabled Determines whether or not a user is allowed to log in.
You cannot delete user records. Mandatory field entry.
337
Setting a User Password
If you assign a password to a user, the user must type it in the password field on
the Logon window when logging on.
Define a user password on the User window:
1. Right-select and select Change Password.
2. Enter the new password.
The system has a six password memory; you cannot reuse a password until it
has been changed six times.
3. Enter the password again in the verification field.
4. Select OK.
5. In the Printer field at the Printer assignment editor window, double-select the
? symbol.
339
The Printers browser window displays and lists all of the printers defined to
the system.
6. At the Printers browser window, select the printers that will be assigned to the
given user.
341
Assigning Privileges
You can create privileges and associate them with operators, functions, and data.
The high level steps for assigning privileges are as follows:
1. Add new operators as type User.
2. Add a new privilege.
3. Define the privilege by adding functions and data to it.
This is known as protecting the functions and data. If functions and data are
assigned to a privilege, no operator of type “User” has access to them unless
assigned to the privilege.
4. Assign an operator to the privilege, giving the operator access to the
functions and data.
NOTE: The following users types are not associated with privileges: Guest,
System Manager, and Developer. Guests are never granted any privileges.
System managers and developers never require any privileges. Only for the
generic type User are privileges taken into account.
Each function has a minimal user type assigned to it. This is the minimal authority
or experience level a user has to activate that function.
Consider the following table that depicts the relationship among functions,
privileges, and users.
Functions are assigned to privileges and then users are assigned to privileges. In
the above scenario, only a user assigned to “Senior” can validate a sample. You
can assign one function or one user to two different privileges.
343
The Function Privilege window displays.
345
• QCResult – Population
• Request – CheckResult, DiscontinuationUser, Discontinue, EditComment,
Invalidate, Patient, Rerun, Results, Revert, Sample, UploadUser, Validate,
ValidationUser, ViewImage
• Requestable – PanelMembership
• Result – AvailabilityUser, AddComment, Method, Request, ViewImage,
ScheduleUser
• Sample – CheckResults, DiffPad, Patient, PatientLocation, Physician,
Report, Requests, Rerun, ReviewAndEdit, Type, UploadResults, ViewImage
• SampleType – Description
Services – CheckActivity
• Site – Calculator, Calendar, InstrumentsByName, OrderEntry,
PatientsByLastNameFirstName, PhysiciansByLastNameFirstName,
QCLotsByNumber, QCPopulationQuery, RequestablesByMnemonic,
ResultEntry, SampleQuery, SamplesByIdentifier, SampleTypesByMnemonic,
ServicesByName, SpeciesByName, TestsByMnemonic, ReviewAndEdit
• Species – Patients
• Test – Instruments, Norms, SampleType, ResultChoices, DeltaNorms,
Requestables
347
2. Right-select and select Fields protected.
349
• Modification to Instrument records
• Modification to Instrument Groups
• Modification to Test Groups
• Modification to Requestables
• Modification to Patients
• Modification to Patient Location
• Modification to Physicians
• Modification to Sample Types
• Modification to Species
• Modification to Specific-Self (Options)
• Test and Method table modification
• Audit Trail purge
The tables that are audited by default are listed as follows:
• Aspect
• bt_ActualFunctionParameter
• bt_ActualFunctionParameterSet
• bt_ActualQueryParameter
• bt_ActualQueryParameterSet
• bt_Command
• bt_Task
• CodingSystem
• ContainerType
• ContainerTypeCode
• DeltaNorm
• DilutionCondition
• Dimension
• gp_Site
• gp_SiteFunction
• gp_Text
• Instrument
351
• Unit
Audit logs contain the following information:
• Changed fields with From and To values
• Date and time the change was made
• User who initiated the change
• Action performed by the user who initiated the change
Audit information can be exported and can be purged. Automated tasks,
executed by the user “Batch,” are excluded from auditing.
NOTE: User actions are audited, batch actions are not audited.
Field Description
From Parameter that limits the display of audit log entries to
those that have a date stamp value equal to or greater
than this From date value.
This is a required field.
NOTE: The number of days between the From date and
the To date values cannot exceed 60 days.
To Parameter that limits the display of audit log entries to
those that have a date stamp value less than or equal
to this To date value.
NOTE: The number of days between the From date and
the To date values cannot exceed 60 days.
User Parameter that limits the display of audit log entries to
those initiated by this user.
NOTE: Either a User or Table name value must be
entered.
Table Parameter that limits the display of audit log entries to
those applicable to this table.
NOTE: Either a User or Table name value must be
entered.
2. After entering the parameters, select OK.
353
The Log entries window displays.
The audit information that displays is restricted to meet the audit query
parameters entered to the Audit overview query window. The parameters for
this restricted audit set apply until the current Log entries window session
ends.
Field Description
Creation Time Displays the creation date of a log entry.
S Displays the severity of the entry.
Login Displays the name of the user.
355
Field Description
Group by record If selected, groups all transaction records within the
current view to the record to which the transaction audit
log entries apply. Groups of transaction records are
distinguished from each other by a different background
display after each transaction group.
For example, within the current view, all records that
pertain to User A would be grouped together against a
white background; all records that pertain to User B
would be grouped together and these records would be
distinguished from those of the previous group with a
grey background; all records that pertain to User C
would be grouped together against a white background,
and so on.
Show subject record If selected, transfers control to the applicable editor
window in which the transaction was entered and saved
and displays the details of the transaction record within
this editor window.
NOTE: If the first record of the transaction record
grouping is a deleted record and you select Show
subject record, the corresponding editor window does
not display because the deleted record does not exist.
Export to browser If selected, exports the displayed audit log data to an
XML-based file that can be printed.
Options If selected, displays the Audit overview query window,
which allows for you to update the parameters of the
query.
Upon redisplay of the Log entries window, the audit log
data is refreshed to reflect records that meet the
entered audit criteria.
Refer to Entering Auditing Criteria that Restricts the Log
Entries Display‚ page 357.
357
Checking Log Files and Starting and Stopping the Server
The ADVIA CentraLink system maintains log files that track database activity.
You can monitor the log files and then stop and re-start the ADVIA CentraLink
software and its databases.
In the Log Folder field of the General tab of the system Options window, a root
folder directory for all log files is specified. This root folder contains subfolders for
service logs, which are named svc, and translator logs, which are named trl,
respectively. These subfolders are again subdivided in subfolders dedicated to
individual services and translators. If the ? symbol is specified in the Log Folder
field of the General tab of the system Options window, the log file folder defaults
to <CentraLink>\log.
The ADVIA CentraLink system server is the computer containing the
ADVIA CentraLink databases:
• Genro: Generic, Read-only data (for example, scheme info)
• CentraLink: Specific, Read-write data (for example, tests, samples, etc.)
These databases are installed as part of the ADVIA CentraLink application and
are in Progress database format. Some Progress commands, including the
Progress Explorer Tool, display in your Start menu. The Progress Explorer Tool
allows you to manually start or stop the two databases that the ADVIA CentraLink
system uses.
During the ADVIA CentraLink system installation procedure, the databases are
set up to automatically start and stop upon system startup and shutdown.
However, you may need to manually start or stop the database. For example, you
may need to stop the database to upgrade the ADVIA CentraLink system to a
newer version then restart it after the upgrade is complete.
In addition to starting and stopping the database servers, other services, such as
those used for instrument communication, need to be started and stopped as
well.
If changes are made to a translator, for example, you must stop and start the
translator for the changes to take effect.
CAUTION: Be sure to stop all the ADVIA CentraLink system services before
making any system changes, such as changing the system date and time.
359
Manually Starting the Database
You must start the ADVIA CentraLink server from the computer on which the
ADVIA CentraLink server software is installed. Do not start the server from any
other computer.
1. Start all databases:
a. At the ADVIA CentraLink server Windows Start menu, select Programs >
OpenEdge > Progress Explorer Tool.
b. Using the tree view, go to the ADVIA CentraLink databases: Console
Root > Progress Explorer > localhost > Databases.
c. Right-select the Samplenet database and select Start.
Repeat these startup procedures for the CentraLinkgenro database.
2. Start the services and translators on the ADVIA CentraLink session server:
a. At the menu bar, select Start > System management > Services >
Startup.
This procedure only starts services and translators with the AutoStart attribute
selected. Verify that services and translators are selected correctly. You must
start any unselected required services and translators individually.
Watchdog Service
The Watchdog service is a background program that monitors connectivity and
availability. The Watchdog service monitors the following items:
• Connection status of translator services and their associated translators
• Availability of the LIS FTP service
• Connection status of the Database server
• Availability of space on disk drive used for image storage
All incoming information is gathered, interpreted, and dispatched to the
Watchdog Dashboards. Information related to connectivity and availability is
posted as messages in the Message log of the Dashboard and are broadcast as
alerts via email to system managers.
361
Watchdog Dashboard
The Watchdog Dashboard connects to the Watchdog service. Through its
graphical interface, the Watchdog Dashboard displays the monitoring results of
the Watchdog service.
The Watchdog Dashboard displays the status of communication with the
connected translator services and translators and displays log messages. You
can filter the displayed translator services and translators by name or by
instrument group.
Through the Send QC Warnings to Watchdog checkbox on the Watchdog tab of
the system Options window, you can configure sending QC severity change
messages to the Watchdog Dashboard.
Translator services are located on the left side of the Watchdog Dashboard
window. The associated translators are located on the right.
Dashboard Toolbar
The Watchdog Dashboard window toolbar contains the following:
• About button - Displays the About dialog box, which displays product version
and copyright information.
• View button - As per a dropdown menu selection, allows you to sort the
display of services and translators as follows:
363
- Show all items - Displays all the services and translators.
- Hide inactive - Displays only the active services and translators.
- Show specific set - Displays services and translators by instrument group.
• Setup button - Accesses the Watchdog Dashboard Preferences window.
Through the Watchdog Dashboard Preferences window, you can configure
the Watchdog Dashboard to connect at Watchdog startup to a specific host
and port, which is the default and is recommended, or to search for and
display all available Watchdog services on the network upon Watchdog
Dashboard startup.
• Filter field - As per translator name values entered to this field, you can filter
the display of translator service and translator information by translator name.
Dashboard Tabs
The Watchdog Dashboard window consists of two tabs: Communication Monitor
tab and Message Log tab.
365
Status of Communication
The status of communication with the connected servers and translators displays
through color codes.
Color Service Status / Meaning Translator Status / Meaning
Green Active Active
Sent activity confirmation less Started and connected to
than 1 minute ago. external application.
Gray Inactive Inactive
Defined in database, but not Defined in database, but not
started. started.
Red Undetermined Disconnected
Did not send an activity Started but not connected to
confirmation for more than one external application.
minute because the service is NOTE: Translators that use FTP
inactive or busy. as the low-layer protocol, for
example, the LMX LIS translator,
do not have a status of
Connected or Disconnected.
The status of these translators is
either Active or Inactive.
QC Severity Messages
Through the Send QC Warnings to Watchdog checkbox on the Watchdog tab of
the system Options window, you can configure sending QC severity change
messages to the Watchdog Dashboard.
These QC severity message displays are compatible with both Normal and
Concentrator instrument types.
For QC messages from a concentrator translator, the value of the sender is the
name of the concentrator translator; the warning displays as a light bulb icon on
the concentrator translator rectangle. Upon selecting the light bulb icon on the
concentrator translator rectangle, the QC message text displays in the
Information area of the Watchdog Dashboard and contains a reference to the
normal instrument.
367
Configuring the Watchdog Service and Dashboard
Starting Watchdog Service Independent of Other Services
The Watchdog Startup window allows you to configure a control service that
communicates with the Dashboard. Unless the control service is started
manually, the control service starts automatically when the Watchdog starts.
To start the Watchdog service independent of other services, do the following:
1. At the menu bar, select Start > System Management > Services >
Watchdog > Start.
The Start window displays.
Field Description
Log file keep The recommendation is to leave this field value defined
as the ? symbol.
NOTE: The field value on this Start window is not used.
Your technical support provider configures this value in
the watchdog.dashboard.log4j.properties file.
Log file keep is the numerical value associated with the
unit of time in which the log file is kept.
You can view the current configuration of the Watchdog, which includes the fields
and values of the Startup window as well as the Server and Port fields, through
the Watchdog tab of the system Options window. These values can only be
changed on the Register Watchdog window or the Startup window.
369
Registering and Unregistering Watchdog
Before you can start the Watchdog service, you must register it with Windows.
You must register Watchdog on the ADVIA CentraLink system server.
NOTE: After registering the Watchdog service, always start the Watchdog service
to avoid delays in communication with the instrument translators.
Register the Watchdog service:
1. At the menu bar, select Start > System Management > Services >
Watchdog > Register.
The Register Watchdog window displays.
Field Description
Service name Name of the Windows service to be registered.
Folder The folder where the Watchdog is installed. The default
is the Watchdog subfolder of the application root folder.
Server Contains the name or IP address of the
ADVIA CentraLink system server.
Port Specifies the TCP/IP port where the Watchdog is
listening.
371
Access the Watchdog Dashboard Preferences window:
1. At the Watchdog Dashboard, select Setup.
The Watchdog Dashboard Preferences window displays.
NOTE: Each of the parameters defined on the Watchdog Dashboard
Preferences window is a global setting. The selections made to the Watchdog
Dashboard Preferences window affect each Watchdog Dashboard connected
to this Watchdog service.
If another Watchdog Dashboard is open and active at the time the
preferences are reset, however, the other Watchdog Dashboard does not
reflect the changed preferences until you exit this Watchdog Dashboard and
subsequently reopen this Watchdog Dashboard.
2. At the topmost radio buttons area, select Always connect to the Watchdog
Services running.
NOTE: The default option upon Watchdog Dashboard Preferences display is
Display ZeroConf-enabled discovery dialog at startup. The recommendation,
however, is to select the Always connect to the Watchdog Service running on
option in order to always connect to the Watchdog service.
373
Start and Stop Translator Services and Translators
At the Dashboard, you can start and stop the translator services and translators
from the following two areas:
• Translator service and translator rectangle
• Information panel
At the translator service or translator rectangle, start or stop services and
translators as follows:
1. Right-select the corresponding translator service or translator rectangle.
2. From the dropdown menu, select Start or Stop.
At the information panel, start or stop services and translators as follows:
1. Select the translator service or translator.
At the information panel at the bottom of the window, the data of individual
translator services and translators displays.
2. In the Actions field at the Information panel, select Start or Stop.
Field Description
Backup maximal days A warning is generated when more days have elapsed
passed since the latest Progress database backup than the
specified Backup maximal days passed.
375
Field Description
Disk minimal Minimal amount of megabytes that must be available to
megabytes free prevent a warning.The recommended setting is 200.
This warning may trigger either before or after the
maximal usage value is set. For example, if you set this
value to 200 MB, and set the maximal usage to 80%,
but only 75% of the disk has been used, this warning is
triggered first.
Disk maximal Maximum percentage of used disk space to prevent a
percentage used warning. The recommended setting is 80. This warning
may trigger before or after the minimal disk space value
is set. For example, if you set this value to 80% and the
disk has 500 MB free, and minimal free megabytes is
set to 100 MB, this warning is triggered first.
Area minimal Minimal amount of megabytes that must be available
megabytes free per storage area to prevent a warning.
Area maximal Maximum percentage of used space per storage area
percentage used that must be maintained to prevent a warning.
Check overflow extent When selected, a warning message displays when the
overflow extent is in use.
Enables an advanced check on database size. The
ADVIA CentraLink system database consists of 55
extents, each of which has a 2 gigabyte limit.
Support email address Sets the system to forward a copy of the warning to the
specified address. This feature requires that an Email
host and port were configured in the email address field
of Mail tab on the system Options window.
Warnings are displayed to the current user and mailed to all enabled users of
type “System Manager.”
System managers can schedule the storage check function to run automatically.
377
Scheduling Tasks
A task specifies that a command is launched automatically at a specific time and
perhaps on a recurring basis.
Scheduled tasks might include uploading and downloading:
• Uploading QCs to the LIS
• Automatically uploading samples to the LIS
• Download workorders to the LAS
Set up a scheduled task:
1. At the menu bar, select Start > System management > Commands >
Commands
The Commands browser window displays.
2. Select the appropriate command.
3. Right-select the selected command and select Tasks.
The Task browser window displays.
4. Select New on the toolbar.
5. Enter the Name value, the From value, which is the start date, and the Until
value, which is the to date.
6. Specify the Recurrence pattern information to automatically perform the
specified command.
7. Select OK.
379
Backing Up and Restoring the Software
Backing Up the Databases
Do not shut down the databases before making a backup. You can continue
working while the backup is being made. You can launch the ADVIA CentraLink
database backup utility from the ADVIA CentraLink system.
NOTE: The recommendation is to perform a database backup once a day.
To launch the ADVIA CentraLink database backup utility from the
ADVIA CentraLink system complete the following steps:
1. At the ADVIA CentraLink menu, select Start > System Management >
Database > Backup.
The ADVIA CentraLink backup utility window displays.
The Write to tape checkbox field allows for you to write the database to tape
or to file. When selected, the database backup is written to tape. When not
selected, the database backup is written to a file on disk in the path specified
within the Temporary backup directory.
3. Select Start.
Progress messages display on the screen throughout the backup process.
NOTE: When the possibility of insufficient disk space exists while performing
a manual backup, the following message displays: "You probably don't have
enough disk space on your temporary drive to do the backup. Are you sure
you want to proceed? (Y/N)"
381
If you select Yes and sufficient disk space does not exist, the database locks.
Under these circumstances, you would have to reboot the ADVIA CentraLink
server to resolve the problem.
Always terminate the backup by selecting No.
A complete backup operation is done in several steps. Three major operations
are performed during a backup:
• A database image is written to the spare disk on the server
• The database image is written to the tape
• Cytograms are written to the tape
The current step is marked by the yellow arrow. Steps that are completed are
marked with a green check mark. A backup is successful when all check boxes
are marked with a green check mark. Steps that failed are marked with a red
cross. If a step fails, examine the log at the bottom of the backup window. A
status window displays while the data is written to the tape.
After a successful backup operation, the backup tape is ejected automatically.
Take it out and keep it in a safe place. In case of an error, you can select the Eject
button to remove the tape.
Performing a Backup
The only difference in the operation of the low-end server and the high-end
server is a minor distinction in the operation of the tape drive.
Performing a backup on the low-end server involves a waiting period. Insert the
tape and wait for the tape drive to complete its initialization. This takes
approximately 2 minutes. Wait until the Ready light has stopped flickering before
starting the ADVIA CentraLink system backup procedure.
If the backup procedure is started without waiting, the ADVIA CentraLink system
backup application reports one of the following errors: No Media or Device not
ready. If the error is posted, cancel the backup, wait for the tape drive to complete
its initialization, and restart the backup.
383
The DLT/VS tape drive does not read or write to the VS1 tapes used by the DLT/
VS160 tape drive. Tapes from Dell PowerEdge 1800 or 2800 servers cannot be
restored to the Dell PowerEdge 2500 or 2600 servers.
Windows 2000 and Windows 2003 Restore Procedure from a Tape Backup
1. At the Windows Start menu, select Programs > Accessories > System
Tools > Backup.
2. Insert the backup tape.
If a New Import Media window displays, select Allocate this media to
Backup now and then select OK.
This window displays only when you are moving tapes from one system to
another or when the operating system was reinstalled on the server.
3. At the Backup window toolbar, select Tools > Options.
The Options window displays.
4. Select the Restore tab.
5. Select Always replace the file on my computer.
6. Select OK.
7. At the Backup window, select the Restore tab.
8. At the left pane of the restore window, select the tape named CentraLink
backup in your backup media section.
9. In the right pane, if you do not see two backup sets for the ADVIA CentraLink
system databases and cytograms, double-select CentraLink backup in the
left pane.
A catalog of the tape is made and the two sets display in the right pane.
10. Select both backup sets and select Start Restore.
A message displays prompting if you want to continue.
11. Select OK.
A message displays prompting if you want to overwrite the files.
12. Select OK.
A status window displays. Allow the restore operation to run to completion.
13. Close the Backup application.
385
Step 2: Rebuild the Database from the Image
ADVIA CentraLink software is shipped with a utility that makes it easy to
reconstruct the database starting from the backup image that you just restored.
1. At the Windows Start menu, select Run.
2. Type d:\centralink\bin\restore.exe.
3. Select OK.
4. If the path displayed in the image file field is exactly the same as the location
where the image file is restored, you need not modify this field.
Through Windows Explorer, verify that the following files are in this location:
centralink1, centralink.inp and centralink.st. Typically the files are located in
the following directory: F:\CentraLink\Tmp\Backup. If you do not know the
temporary directory name, search for the files on another drive. Do not
confuse these files with the actual databases, each of which has an
extension: db, d1, d2, d3, b1.
387
NOTE: Restore works only with a backup from the same ADVIA CentraLink
system version. The backup version must have the first digit in the three-digit
version identification.
Ensure that no ADVIA CentraLink system client, even the one on the server, is
running when the restore operation is underway. It is not necessary to manually
shut down the databases; the restore program shuts down the databases
automatically.
5. Ensure that the value in the Database image files: field is the path of the
default restore directory where you copied the database backup files.
6. Select Start to start rebuilding the database.
The restore operation is done in several steps. The current step is marked by
the yellow arrow. Steps that are completed are marked with a green check
mark. A restore is successful when all check boxes are marked with a green
check mark. Steps that failed are marked with a red cross.
7. If a step fails, examine the log at the bottom of the Restore window.
After a successful restore operation, the newly restored databases are
started. It can take several minutes before the databases are fully started.
Wait at least 3 minutes before starting the ADVIA CentraLink software again.
You did not wait long enough, if the following error message displays: There
is no server for database.
389
8. To restore the cytograms files from disk, copy the files to the Cytogram
directory in the CentraLink folder.
391
The Languages window displays.
Field Description
Name Unique name for the language, such as French.
Code Unique identifier for the language.
System language Associated user interface language, which can be used
for retrieving translations of non-multilingual strings.
393
The Regional Settings Properties window displays.
2. To limit the display of printers to those assigned to your user name, select
Show my printers only.
395
For information on assigning printers to a user, see Assigning Printers to a
User‚ page 338.
3. To define a new printer, select the New icon on the toolbar.
The Printer editor window displays.
Field Description
Name A unique name for the printer.
397
Customizing Reports
The ADVIA CentraLink system generates reports according to report models.
When the system generates a report, it uses the default report model from the list
of available models. Every sample or test in the report follows the default report
model unless a different model is associated with the requesting physician.
For more information on report models, see Configuring a Report Model‚
page 328.
Change the default report model by completing the following steps:
1. At the menu bar, select Start > System management > Options.
The Options editor window displays.
2. Select the More tab.
The name of the current default report model displays in Report model.
3. Double-select Report model.
The Report models window displays and lists the available models.
4. Select the appropriate report and select OK.
Report model is populated with the selected report model name.
Reports generated after this change use this report model.
NOTE: Your system administrator can establish automatic reporting by defining a
reporting command to run automatically. Commands are always associated with
a table and reference both a query, which determines the records for processing,
and a function, which determines how to process the records. The format setting
of text or HTML is specified through command parameters. When a command is
defined, your system administrator can create associated task records, which are
scheduled for execution by a task scheduler service.
399
The Toolbar button editor window displays.
Field Description
Row Determines the relative vertical position of the button.
Sequence Determines the relative horizontal position of the
button.
401
Troubleshooting
The following information may be helpful in troubleshooting system problems and
in everyday operation of the ADVIA CentraLink system.
Error Messages
ADVIA CentraLink Client/Workstations Sessions
The ADVIA CentraLink system supports up to 15 open sessions at one time. If
you attempt to open more than 15 sessions, an error message displays. The
content of this message differs depending on whether the session is opened on
the ADVIA CentraLink system server or on a client/workstation. To close the error
message, press CTRL+BREAK.
QC lot results are not recognized when the expiration date is older than the start
date.
Problem: When the ADVIA CentraLink system imports controls, it does not
check the expiration date. If control samples with an old expiration date are sent
to the ADVIA CentraLink system from an instrument, the ADVIA CentraLink
system reports that the control does not match a lot.
Solution: Using the QC Lot window, change the expiration date to a later date
than the start date. When you change the date, the ADVIA CentraLink system
recognizes the control and creates a population for it.
403
Error message received for aspiration time
Problem: When attempting to display a list of samples based on a query for
“Aspiration time,” you may receive the error message, “Invalid range for
aspiration time.”
Solution: When filling in the Sample Query window, be sure to type in the
aspiration time in 24-hour format (for example, 20:00).
405
406 ADVIA CentraLink Operator’s Guide
Index
Section 5: Index
Symbols C
? placeholder, using 32 Closing Out QC 219
A Coding systems
container type 322
Add-on programs
sample type 321
setting the language for 393
setting up 320
Advanced privilege 346 species 323
ADVIA 120 QC data, importing 220 test codes 320
ADVIA CentraLink system using 320
introduction 13 Comment tab of Request window
logging on and off 20 169
operator functions 15 Comments
system management functions appending to a request 152
16 coded comments 152
tips 39 viewing 123
toolbar 24
Component test 236
using the workspace 22
Concentrator
ADVIA Modular Automation System
overriding values 287
19
workorder processing 287
Allow on type error 121
Concentrator instrument type 281
Ambiguous result
Container type code
patient 118
setting up 322
ambiguous result
Context menus 30
patient 119
Cytogram images
Aspect, defining 276
restoring 387
Audit tab of Request window 170
Autovalidation, Configuring 311 D
Dashboard
B using 362
Backing up ADVIA CentraLink 380 Databases
Binocular icon, using 39 checking storage 375
Browser windows 27 purging data 377
restoring 384, 387
407
restoring images 385 tutorial 20
Default privilege 346 H
Default report model Help, using 39
changing 398
How Do I (list of quick tasks) 45
Delta Norm 121
Delta norms 272 I
Diff Pad Ignored deviation count 183
using 73 Images
Dilution tab of Request window 166 viewing 131, 138
Dimension editor, using 266 Importing ADVIA 120 QC data 220
Dimension, setting 266 Instrument flags
setting 300
Double-select menus 30
viewing 137
E Instrument Groups
Editing test results 152 Creating and Modifying 330
Editor windows 27 Instrument parameters
Enter results manually 226 specifying for a QC Lot 176
Error Messages 402 Instrument tests (methods) 302
Instrument tests (methods) and flags
F
300
Feature
Instrument types
Auto-skip sample 141
Normal and Concentrator 286
Field access
Instruments
controlling 347
viewing information 280
Field data
Invalidating results 150
protecting 347
Find function, using 39 K
Flags Keyboard shortcuts 37
viewing 119, 137 L
Functions Languages
adding to privileges 343 changing 391
G defining 393
Generating 1 selecting and adding 391
setting for add-on programs 393
Getting started
409
QC Close Out 219 Report model 240
QC Data Point changing the default 398
auditing 217 configuring 328
comment 217 Reports 398
omitting 216 printing a sample report 86
reinstating 216 Request
QC Data, viewing 193 appending comments to 152
QC lot Request window 164
adding 176 Audit tab 170
specifying test and instrument Comment tab 169
parameters 176 Dilution tab 166
viewing 173, 221 LIS Previous Result tab 171
QC population query 177 Result Detail tab 165
QC population report Severity tab 168
generating QC population re- Requestables
ports. 223 adding tests to 279
QC Results creating panels for 276
QC result flags 213 Rerun
QC results advanced reruns 157
viewing 184 manual dilution 157
viewing Levey-Jennings graph Rerun status, defined 124
184 Rerunning a test 134
QC Results (Across Controls View) Restoring the database 380, 385
window 194 Restoring the database from disk
QC severity, resetting 205 387
query 102 Restoring the database from tape
question mark (?), using 32 384
Result choice editor, using 267
R
Result choices, setting 267
Ratio test 152, 236
calculation for 260 Result Detail tab of Request window
165
Rebuilding the database from an im-
age 386 Result status, defined 124
Report formats Results
selecting 240 editing 152
411
Table data U
protecting 347 Unit
Tasks dimensions for 266
scheduling 378 setting 263
Test Unit editor, using 264
configuring 243 units of measure
merging into workorder 235 defined 92
viewing test list and test details identical definition 248
243 LIS, software, instrument 92
Test and instrument parameters Upload results 136
specifying for a QC Lot 176 Uploaded status, defined 124
Test aspects, defining 276 User interface languages 391
Test code User-defined languages 391
setting up 320
Users
Test request information adding to a privilege 345
viewing 164 setting up 335
Test, configuring
adding test to list 243 V
creating panels 276 Validated results
deleting test from list 262 uploading 136
editing a test definition 262 Validated status
setting delta norms 272 changing 150
setting morphology flags 268 definition 124
setting norms 269 W
setting result choices 267
Watchdog
setting units 263
alerts 361
using the test editor 245
registering 370
Tips for using the ADVIA CentraLink starting and stopping 371
system 39
Westgard Rules
Toolbar configuring for instrument 315
adding buttons 399 configuring for method 318
using the function toolbar 24 configuring for test 317
ToolTips, using 25 Windows
Troubleshooting 402 browsers and editors 27
Type error 117
413