Roche cobas 6800 User manual

Type
User manual

This manual is also suitable for

cobas
®
6800/8800 Systems
cobas p 680 instrument
cobas omni Utility Channel IVD
Software version 1.2 - Known issues version 1.1
Roche Diagnostics
cobas® 6800/8800 Systems · Software version 1.2 · Known issues · version 1.1
2
Publication information
Edition notice Every effort has been made to ensure that all the
information contained in this publication is correct at the
time of publishing. However, the manufacturer of this
product may need to update the publication information
as output of product surveillance activities, leading to a
new version of this publication.
Intended use
The cobas
®
6800/8800 Systems support an automated
and integrated workflow to run Polymerase Chain
Reaction (PCR) based Nucleic Acid Testing (NAT).
The cobas
®
6800/8800 Systems combine the
functionalities of instrumentation, consumables, reagents,
and data management to provide an efficient workflow
from sample processing to result interpretation.
The cobas p 680 instrument is an optional instrument
used for the pipetting of liquid sample material to form
pools of samples as the front-end to the
cobas
®
6800/8800 Systems for blood screening
laboratories.
The cobas omni Utility Channel suite of products are
intended for use with the open channel functionality of
the cobas
®
6800/8800 Systems.
Disclaimer Not every software version applies to all markets. Some
content in this publication is related to products,
configurations, or tests which are not available in all
markets.
Screenshots The screenshots in this publication have been added
exclusively for illustration purposes. Configurable and
variable data in screenshots, such as tests, results, or
path names visible therein must not be used for
laboratory purposes.
Copyright © 2014-2017 F. Hoffmann-La Roche Ltd. All rights
reserved.
Trademarks The following trademarks are acknowledged:
Publication version Software version Revision date Change description
1.0 1.2 September 2016 First version
1.1 1.2 August 2017 Changed intended use statements.
New instrument approvals.
Added US distributor address.
Added and updated issues.
Added recommendations for
maintenance actions.
u What is new in publication version
1.1 (6)
Roche Diagnostics
cobas® 6800/8800 Systems · Software version 1.2 · Known issues · version 1.1
3
COBAS, COBAS OMNI, COBAS P, TAQMAN, AMPERASE,
and LIFE NEEDS ANSWERS are trademarks of Roche.
All other trademarks are the property of their respective
owners.
Instrument approvals for the
cobas
®
6800/8800 Systems
The cobas
®
6800/8800 Systems meets the requirements
laid down in:
Directive 98/79/EC of the European Parliament and of the
Council of 27 October 1998 on in vitro diagnostic medical
devices.
Directive 2011/65/EU of the European Parliament and of
the Council of 8 June 2011 on the restriction of the use of
certain hazardous substances in electrical and electronic
equipment.
Directive 2014/53/EU of the European Parliament and of
the Council of 16 April 2014 on the harmonization of the
laws of the Member States relating to the making
available on the market of radio equipment and repealing
Directive 1999/5/EC.
To view the full text of the 2014/53/EU declaration of
conformity, go to the Roche DiaLog Global Web Site
(https://dialog1.roche.com/) and choose the eLabDoc
link.
If you are unable to access Roche DiaLog, contact a
Roche Service representative.
Compliance with the applicable directive(s) is provided by
means of the Declaration of Conformity.
The following marks demonstrate compliance:
Complies with the provisions of the applicable EU
directives.
For in vitro diagnostic use.
Issued by Underwriters Laboratories, Inc. (UL) for
Canada and the US.
Issued by CSA Group for Canada and the US.
CUS
Roche Diagnostics
cobas® 6800/8800 Systems · Software version 1.2 · Known issues · version 1.1
4
Instrument approvals for the cobas p 680
instrument
The cobas p 680 instrument meets the requirements laid
down in:
Directive 98/79/EC of the European Parliament and of the
Council of 27 October 1998 on in vitro diagnostic medical
devices.
Directive 2011/65/EU of the European Parliament and of
the Council of 8 June 2011 on the restriction of the use of
certain hazardous substances in electrical and electronic
equipment.
Directive 2014/53/EU of the European Parliament and of
the Council of 16 April 2014 on the harmonization of the
laws of the Member States relating to the making
available on the market of radio equipment and repealing
Directive 1999/5/EC.
To view the full text of the 2014/53/EU declaration of
conformity, go to the Roche DiaLog Global Web Site
(https://dialog1.roche.com/) and choose the eLabDoc
link.
If you are unable to access Roche DiaLog, contact a
Roche Service representative.
Compliance with the applicable directive(s) is provided by
means of the Declaration of Conformity.
The following marks demonstrate compliance:
'Laboratory Equipment' is the product identifier as
shown on the type plate.
Complies with the provisions of the applicable EU
directives.
For in vitro diagnostic use.
Issued by CSA Group for Canada and the US.
'Laboratory Equipment' is the product identifier as
shown on the type plate.
CUS
Roche Diagnostics
cobas® 6800/8800 Systems · Software version 1.2 · Known issues · version 1.1
5
Approvals for the cobas omni Utility Channel The cobas omni Utility Channel Reagent Kit meets the
requirements laid down in:
Directive 98/79/EC of the European Parliament and of the
Council of 27 October 1998 on in-vitro diagnostic medical
devices.
Compliance is provided by means of the Declaration of
Conformity.
The following marks demonstrate compliance:
Contact addresses for the cobas
®
6800/8800 Systems
Contact addresses for the cobas p 680 instrument
For in-vitro diagnostic use.
Complies with the IVD directive 98/79/EC.
Roche Diagnostics GmbH
Sandhofer Strasse 116
68305 Mannheim
Germany
Made in Switzerland
Distributed in the United States by Roche Diagnostics
9115 Hague Road
Indianapolis
Indiana, USA
Roche Diagnostics GmbH
Sandhofer Strasse 116
68305 Mannheim
Germany
Made in Switzerland
Roche Diagnostics
cobas® 6800/8800 Systems · Software version 1.2 · Known issues · version 1.1
6
Contact addresses for the cobas omni Utility Channel
What is new in publication version 1.1
Intended use
The intended use statement for the cobas
®
6800/8800
Systems was updated. The intended use statement for the
cobas omni Utility Channel was changed.
u Intended use (2)
Disclaimers Disclaimers were added.
u Disclaimer (2)
u Screenshots (2)
Instrument approvals New directive added to the instrument approval sections.
u Instrument approvals for the cobas
®
6800/8800
Systems (3)
u Instrument approvals for the cobas p 680
instrument (4)
Distributor address The US distributor address for the
cobas omni Utility Channel was added.
Additional issues
More issues affecting the cobas
®
6800/8800 Systems
were added.
u List of known issues affecting the cobas
®
6800/8800
Systems (8)
Updated issue An issue affecting the cobas omni Utility Channel was
updated.
u List of known issues affecting the cobas omni Utility
Channel (13)
Maintenance actions Recommendations for maintenance actions were added.
u cobas
®
6800/8800 Systems maintenance action
recommendations (14)
Roche Diagnostics GmbH
Sandhofer Strasse 116
68305 Mannheim
Germany
Reagent kit made in USA
Distributed in the United States by Roche Diagnostics
9115 Hague Road
Indianapolis
Indiana, USA
Roche Diagnostics
cobas® 6800/8800 Systems · Software version 1.2 · Known issues · version 1.1
7
T
able of contents
List of known issues affecting the
cobas
®
6800/8800 Systems . . . . . . . . . . . . . . . . . . . . . 8
List of known issues affecting the cobas p 680
instrument . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
List of known issues affecting the cobas omni Utility
Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
cobas
®
6800/8800 Systems maintenance action
recommendations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Roche Diagnostics
cobas® 6800/8800 Systems · Software version 1.2 · Known issues · version 1.1
8 List of known issues affecting the cobas
®
6800/8800 Systems
List of known issues affecting the
cobas
®
6800/8800 Systems
# Issue When can you encounter this problem Workaround
1
IG server or instrument stays in
Maintenance mode after a failed
maintenance action. It is not possible to
perform any other maintenance action.
Sporadically, when a maintenance
action fails.
Restart the IG server and all the
instruments. If it is still not possible to
repeat or perform a maintenance action
after the execution of a maintenance
action failed, contact your Roche
Service representative.
2
The initialization of the
cobas
®
6800/8800 Systems cannot be
completed. The analytic module goes
into Error status.
When the user chooses the button to
open the amplification plate drawer
during the initialization of the
instrument and there are no
amplification plates to be discarded.
Do not choose the button to open the
amplification plate drawer until the
system is in Standby status.
In case of error, restart the instrument.
3
The transfer module is in error status
and it is not possible to perform a
cleanup maintenance action. The
output buffer of the sample supply
module is full.
When the output buffer is full and the
instrument is idle for more than six
hours with racks in the transfer module.
Always empty the output buffer before
starting an overnight run. In error case,
unload all racks from the output buffer
and restart the instrument.
4
A maintenance action has been
successfully executed but its status in
the maintenance action overview does
not change to Upcoming after
refreshing its window. Also, the task
informing the customer of an overdue
maintenance action does not disappear
after executing it successfully.
Sporadically after performing
successfully a maintenance action.
Restart all the instruments and the IG
server. If the status of the maintenance
action is Due or Overdue, it should be
repeated. If this happens for the
periodic maintenance of a cobas p 680
instrument, the action must be
repeated regardless of its status.
5
The maintenance action wizard
disappears when the user interface is
refreshed and the maintenance action
remains in Executing status.
Always when a maintenance action
with a wizard is started and the user
refreshes the user interface while the
action is still being executed.
Restart the IG server and all
instruments and repeat the
maintenance action. To prevent this
issue, it is recommended to avoid
refreshing the user interface while
executing a maintenance action with a
wizard.
6
Test orders cannot be reset. Message
states: “The instrument is online”.
When the system is not in Standby or
Error status and the user resets the test
orders
Only reset test orders when the system
is in Standby or Error status.
7
Maintenance action tasks are not
displayed in the maintenance
processing settings view
(Administration > Settings
> Processing > Settings
> Maintenance actions).
Sporadically, the view is empty. Restart the IG server.
8
There is no task created to empty the
solid waste container. This can cause a
run abort with sample loss.
When the solid waste container needs
to be emptied (capacity is less than for
a full run batch) and the instrument is
started.
Ensure that the solid waste container is
empty at the beginning of the day.
9
The instrument reaches the Ready
status, but no run can be started due to
an overdue maintenance action. The
user has no indication except an
overdue maintenance action in the
Monitoring > Maintenance actions
view.
When a maintenance action becomes
Overdue while the instrument is in
Preparing status.
Choose the Stop button, and then
execute the overdue maintenance
action.
y cobas
®
6800/8800 Systems known issues
Roche Diagnostics
cobas® 6800/8800 Systems · Software version 1.2 · Known issues · version 1.1
List of known issues affecting the cobas
®
6800/8800 Systems 9
10
The New update package available
task remains displayed.
After a new software update package is
successfully installed.
Restart the IG server.
11
The Resume button is not available
after pressing the Stop button.
When a scheduled run is stopped. Refresh the user interface.
12
There is no way to check if the Axeda
connection is successfully established.
When the Axeda service is started. When the Axeda service is not
successfully started during the IG
server startup, the customer will only
realize once the creation of a remote
connection fails. In this case, restart the
IG server.
13
The message list displays no message
warning about the detection of a clot.
When a clot is detected. Remove all filter settings in Monitoring
> WSIM [instrumentID]
> Messages to also display
information messages.
14
The maintenance action task starts
from the beginning.
When the user leaves the maintenance
wizard during the execution of a
maintenance action task.
Perform the maintenance action task
again and do not leave the wizard.
15
There are no test results available for
processed samples. Samples stay in
Calculating status.
When controls are released before the
samples of the control batch are
calculated.
Release test results from the control
batch view. Ensure that all test results
are available before releasing any to the
LIS.
16
Samples are loaded, but not added to
batch and not processed.
When a barcode is reused for a sample
of different sample type and test.
Do not reuse sample barcodes.
17
The control batch ID of the negative
and positive batches differs from the
ones in the HL7 message.
When test results for ResP1 pools
processed directly on the
cobas
®
6800/8800 Systems are
released.
Check the control batch ID on the UI.
18
The instrument status on the UI
remains Updating.
When the connection to one or more
instruments in the cluster is lost or if
the instrument is in Error status and a
language package is installed.
Restart the IG server.
19
The user interface crashes. When the load list (Routine > Load
list) is sorted by the Test column.
Restart the user interface. From the
drop-down list, choose Test to sort.
20
Despite a failed validity check, a
corrupted backup file can be restored.
Result database is corrupted.
When the validity check of the backup
file fails.
There is a notification in case of a
corrupted backup file. Always check
the messages on the user interface.
21
No task is shown in the tasklist for
overdue automated archiving
maintenance.
Always. Overdue maintenance tasks are visible
in the Maintenance actions panel.
22
Risk of injury due to the sharp edges of
the Hitachi sample rack tray.
When sample rack trays are cleaned. Clean racks according to the
instructions provided by your Roche
Service representative.
23
Exported test results are wrongly
displayed by the archive viewer.
When a sample has more then one test
assigned and the test results are
displayed via archive viewer.
The correct test results are available on
the user interface and LIS.
24
Archive and backup maintenance is not
possible anymore.
When an IG archive maintenance action
fails.
Restart the IG server and trigger the
automatic archiving manually.
25
The Resume button is not available. When the instrument is in Stopping
status.
Restart the user interface.
# Issue When can you encounter this problem Workaround
y cobas
®
6800/8800 Systems known issues
Roche Diagnostics
cobas® 6800/8800 Systems · Software version 1.2 · Known issues · version 1.1
10 List of known issues affecting the cobas
®
6800/8800 Systems
26
The onboard stability of the reagents is
not subtracted from the elapsed time
when the instrument was shut down
but not powered off. In case of a
shutdown via power switch, the
onboard time is calculated correctly.
When the system is shut down (not
hibernated) via user interface and the
system is started up again.
Note that there is a shutdown message:
In case of a shutdown without power
off, please check the onboard time of
the reagents.
27
The expiry date on the control batch
report is not the same expiry date than
the one displayed on the user interface
and the archive viewer.
Example:
o Expiry date on RFID tag/user
interface/archive viewer:
2017-08-31 00:00 am
o Expiry date on control batch report
in Canada (UTC -08:00):
2017-08-30 4:00 pm
The time shift is not considered during
report creation.
When the local time is not equal to
UTC.
The expiry date displayed on the user
interface and the archive viewer is the
correct one.
28
The user interface is non responsive
and cannot be restarted.
When the instrument is left in status
Standby for more than 36 hours.
Restart the instrument via powercycle.
29
The instrument prepare fails with
exception “Washbuffer on slot 1 on
PCA and PCB are in wrong state”,
although valid wash buffer containers
are loaded on different slots of both
processing modules.
When there is an invalid wash buffer
container loaded on slot 1 of both
processing modules.
Load a valid wash buffer container on
slot 1 for both processing modules and
restart the prepare.
30
The gripper rotation movement motor
of the main handler blocks and gets
damaged.
Sporadically, when the main handler
crashes against an obstacle during the
initialization of the gripper rotation axis
during instrument initialization.
Always push the main handler to a
position where it can turn around
during initialization without touching
anything (e.g. in the center of the
sample transfer/processing module or
into the consumable module).
31
The high priority task indicating to
empty AD stacker is still displayed on
the user interface although it was
solved.
Sporadically, after AD plates are
removed from the AD waste drawer.
Verify that the AD waste drawer has
been emptied. If so, the task message
may be ignored and should disappear
upon a powercycle.
32
No error message is generated
indicating the reason for the soft stop
(the system went into Stopping status).
When the rack IDs of the loaded
RD5/MPA racks are not within the rack
range for false button tubes; but false
bottom sample tubes are loaded and
the pipettor crashes into tube bottom
due to wrong pipetting parameters.
Ensure that the correct tubes are used.
33
The pooling run report contains
incorrect and incomplete information
about sample pipetting status.
When a PP1/PP6 pooling run is
completed with pipetting errors.
Do not use the report in this pooling
workflow combination. Refer to the user
interface.
# Issue When can you encounter this problem Workaround
y cobas
®
6800/8800 Systems known issues
Roche Diagnostics
cobas® 6800/8800 Systems · Software version 1.2 · Known issues · version 1.1
List of known issues affecting the cobas
®
6800/8800 Systems 11
34
The expiry dates of consumables and
reagents are handled differently.
Example:
o Reagents:
expiry date July 30, 2017
usable until end of July 29, 2017
o Consumables:
expiry date July 2017
usable until end of June 30, 2017
You cannot load expired reagents or
consumables on the system.
Always. No workaround available.
Use reagents and consumables earlier
than indicated on the expiry date.
# Issue When can you encounter this problem Workaround
y cobas
®
6800/8800 Systems known issues
Roche Diagnostics
cobas® 6800/8800 Systems · Software version 1.2 · Known issues · version 1.1
12 List of known issues affecting the cobas p 680 instrument
List of known issues affecting the
cobas p 680 instrument
# Issue When can you encounter this problem Workaround
1
Sample with pipetting error is not
pipetted to aliquot plate even after
reloading.
When a pipetting error (aspiration or
dispense) occurs while creating an
aliquot plate.
Affected samples cannot be transferred
to an aliquot plate anymore.
2
The measured titer of the test result is
correctly displayed on the UI, but
compared against a wrong calculated
cutoff value (initial pool size: 6, 24, 96,
480; instead of operating pool size: 1).
In some cases, this leads to a false
positive result calling.
When a sample which is part of an
unfinished pooling workflow is directly
tested on the cobas
®
6800/8800
Systems using the DPX test.
Do not process samples which are part
of an unfinished pooling workflow
directly on the cobas
®
6800/8800
Systems.
3
The cobas p 680 instrument starts
pipetting without having loaded
secondary tubes and the aspirated
pipetting volume is discarded.
When more than one pool size is done
in a run and the deck is fully loaded.
Always load full sample racks instead
of partially loaded racks. In case of
error, stop the pooling run immediately
and reload the samples that have not
been pipetted yet.
4
Two pooling requests for the same
sample, but different pooling types.
When a sample with an existing test
order is reloaded on the cobas p 680
instrument without final result creation
in-between.
Before starting the second pooling
workflow for a sample with an existing
test order, reject the test orders that will
not be processed.
5
A user assigned to the Operator user
group can reject pools and pooling
requests. This can result in sample loss
if no sufficient sample material is
available.
When selecting pools and pooling
requests in the Pooling run history or
Pooling orders panels.
No workaround available.
y cobas p 680 instrument known issues
Roche Diagnostics
cobas® 6800/8800 Systems · Software version 1.2 · Known issues · version 1.1
List of known issues affecting the cobas omni Utility Channel 13
List of known issues affecting the
cobas omni Utility Channel
# Issue When can you encounter this problem Workaround
1
Usage of UCAPs containing pipetting
parameter file version 3.0.0 can lead to
falsely flagged samples for
underaspiration resulting in sample
loss.
When UCAPs are generated with the
Utility Channel Tool and a sample
volume of 200 μL and 16 mm sample
tubes are used.
Potential sample loss. Use 13 mm outer
/ 11mm inner diameter sample tubes
for an input volume of 200 μL.
2
False bottom tubes with 850 μL transfer
volume are not supported, but
selectable. Sample orders but no test
orders are created. Sample orders
remain open.
When a false bottom tube rack range
for UC analysis package is chosen and
850 μL is selected as input volume.
Do not use 850 μL as input volume for
false bottom tubes using UCAPs.
y cobas omni Utility Channel known issues
Roche Diagnostics
cobas® 6800/8800 Systems · Software version 1.2 · Known issues · version 1.1
14 cobas
®
6800/8800 Systems maintenance action recommendations
cobas
®
6800/8800 Systems maintenance
action recommendations
Intended use The following information summary shall help affiliates
and customers to schedule the maintenance actions to
their needs while considering known issues, best practice
recommendations, and workarounds.
Data maintenance actions and recommended
interval
Instrument maintenance actions and
recommended interval
Data maintenance action Recommended interval
Backup maintenance action Daily
Automated archiving maintenance action Weekly
Manual archiving maintenance action Not functional, perform the automated archiving maintenance
action manually instead.
IG server cleanup Weekly
Purge archived data Weekly
IG server restart Weekly (default time: Monday 3 AM, can get changed by RSR)
y Data maintenance actions and recommended interval
Instrument maintenance action Recommended interval
Periodic maintenance Weekly
Sample pipetter tightness check Weekly
Teach instrument As required
Clean up As required
Periodic maintenance of pooling instrument Weekly
y Instrument maintenance actions and recommended interval
Roche Diagnostics
cobas® 6800/8800 Systems · Software version 1.2 · Known issues · version 1.1
cobas
®
6800/8800 Systems maintenance action recommendations 15
Maintenance scheduling example (including
the cobas p 680 instrument)
Maintenance scheduling rules The following general rules were applied in the
scheduling example above:
Recommended intervals
No scheduling conflicts
Furthermore, the following additional rules should be
applied when scheduling the maintenance actions:
Keep the notification period short (e.g., between
1-6 hours).
Cluster installations: Schedule the periodic
maintenance, sample pipetter tightness check, and
the periodic maintenance of pooling instrument
actions to a day and time when all systems within the
cluster are in Standby status.
Change the start date of the teach instrument
maintenance action to the year 2025. Only perform
this action when all instruments of the cluster are in
Standby status.
Time Monday Tuesday Wednesday Thursday Friday Saturday Sunday
00:00
03:00 IG server
restart
Automated
archiving
maintenance
action
06:00 Sample
pipetter
tightness
check
09:00 Periodic
maintenance
of pooling
instrument
12:00 Periodic
maintenance
15:00 IG server
clean up
Purge
archived data
18:00
21:00 Backup
maintenance
action
Backup
maintenance
action
Backup
maintenance
action
Backup
maintenance
action
Backup
maintenance
action
Backup
maintenance
action
Backup
maintenance
action
y Maintenance scheduling example (including the cobas p 680 instrument)
Roche Diagnostics
cobas® 6800/8800 Systems · Software version 1.2 · Known issues · version 1.1
16 cobas
®
6800/8800 Systems maintenance action recommendations
Maintenance execution rules Before executing the maintenance action...
Check that no module(s) is/are masked when starting
an instrument maintenance action.
Check the instrument maintenance action status
(Due/Overdue/Upcoming/...) under Monitoring
> Maintenance actions and ONLY perform it when
it is in status Overdue.
While executing the maintenance action...
Do not leave the maintenance wizard by clicking
outside of the wizard window.
Do not leave the maintenance wizard by refreshing
the user interface (UI).
Do not leave the maintenance wizard by getting
locked out by the automatic system lock function of
the software. This function can be enabled or disabled
and the time of inactivity can be configured.
The instruction text of the periodic maintenance
wizard is not fully visible. Use the wizard only in
conjunction with the printed Periodic maintenance
section of the User Assistance / User Guide.
After execution of the maintenance action...
Confirm the sporadic incorrect error message
“Reading of instrument event report
'ReagentSupply_ProcessCellA/B.UnhandledErrorOccu
red' failed.”
If an instrument maintenance action is stuck in
Executing status (Monitoring > Maintenance
actions) follow the below-mentioned instructions:
1) Use the Skip button to clear the status Executing.
2) Shutdown the instrument using the Shutdown
button in the Monitoring tab.
3) Start up the system.
4) Repeat the instrument maintenance action.
If these steps do not work, a restart of the IG server
and all the instruments in the cluster is needed.
History entries for executed, skipped, and failed
maintenance activities are no longer available after IG
restart.
Roche Diagnostics
cobas® 6800/8800 Systems · Software version 1.2 · Known issues · version 1.1
cobas
®
6800/8800 Systems maintenance action recommendations 17
Additional information If a maintenance action becomes overdue at a day
and time different to scheduled under
Administration > Settings > Processing settings
> Maintenance proceed with the following steps:
1) Perform the maintenance action.
2) Save a new maintenance schedule for the affected
maintenance action (e.g. change the start date of
this maintenance action under Administration
> Settings > Processing settings
> Maintenance to the current date).
There is no message created in Administration
> Message list when the automated archiving
maintenance action failed. Check the status in
Monitoring > Maintenance actions. Perform the
automated archiving maintenance action manually.
The accurate status of a maintenance action is
available in Monitoring > Maintenance actions.
(The task list may not provide the accurate task
message for maintenance actions. E.g. tasks can be
missing and/or not disappear after successful
execution.)
Restart the IG server when a high priority task
regarding an overdue maintenance action does not
disappear after successful execution of the
maintenance action and a user interface refresh.
Roche Diagnostics
cobas® 6800/8800 Systems · Software version 1.2 · Known issues · version 1.1
18 cobas
®
6800/8800 Systems maintenance action recommendations
  • Page 1 1
  • Page 2 2
  • Page 3 3
  • Page 4 4
  • Page 5 5
  • Page 6 6
  • Page 7 7
  • Page 8 8
  • Page 9 9
  • Page 10 10
  • Page 11 11
  • Page 12 12
  • Page 13 13
  • Page 14 14
  • Page 15 15
  • Page 16 16
  • Page 17 17
  • Page 18 18

Roche cobas 6800 User manual

Type
User manual
This manual is also suitable for

Ask a question and I''ll find the answer in the document

Finding information in a document is now easier with AI