Atellica® Solution How to Troubleshoot Errors Using the Operator Event Log Video Version 1.26 and Above

Welcome to the Itelica solution How to troubleshoot errors using the Operator Event Log video. This video will explain the details of the Operator Event Log on the Itelica solution by walking through two scenarios that use the event log to troubleshoot issues. Let's begin with an overview of the Operator Event Log. The Operator Event Log displays system events as they occur. Each event includes the severity module code, a description of the event, and the date and time of the event. To view a subset of events, use the filters on the left side of the screen. You can filter the event log based on time in order to narrow down the time frame to when the error occurred. If known, you can select the module you want to troubleshoot. You can also filter by errors, warnings, and information. Errors require immediate attention. Warnings do not require immediate attention. They can be addressed when it is convenient for the operator and the final filter option is information. These events do not require action. The system saves information events for a history of the system activity. After the appropriate filter options are selected, select Show Events. If the filter is not needed, the filter can be collapsed. An operator can add a comment to an event by selecting the event and selecting the comment button. The system allows up to three comments on each event. The online help and procedures to resolve the event can be accessed by selecting the event and then selecting the question mark for that event. Additionally, some errors when selected will show related issues that were caused from the original error. The operator should take actions to resolve the original event. So when would an operator use the event log? Know that you should use the Notification Center primarily to respond to events and only go to the operator event Log to investigate something. For example, if you wanted to see if the same event occurred in the past. Let's look at a couple examples of how to troubleshoot errors using the Operator Event Log and other troubleshooting features in the software. In this first example, the operator looked at the system status area and noticed their chapter modules were not green. The operator also noticed an alert in the Notification Center, which said the chapter analyzer cannot detect the UPS. In order to view more information on this error, the operator selected the Troubleshoot button in the Notification Center. The troubleshooting window opened with both the Operator Event Log and the online help for the alert displayed. The operator closed the Operator event log by selecting the X in the upper right corner of the screen because they decided to go directly to the online help to view troubleshooting steps. In the online help, the event code, or the number that the event is classified by, will show at the top of the window. The event description is comprised of Possible Causes, which lists the possible reasons for the event, and Corrective Actions which lists the options for the operator to correct the event for each possible 'cause. The corrective actions may include a orange hyperlink that will take you to the step by step directions on how to perform that action. There may be multiple possible causes for the selected event with multiple corrective actions. In this case, the online help listed 2 procedures to resolve the event. The operator started with the first procedure, which advised them to shut down and restart the module. The operator selected the orange hyperlink for this task and was able to read through the procedure and perform the action. By shutting down and restarting the chapter module, the operator was able to resolve the error. Let's look at another troubleshooting example, this time involving a patient sample. An operator was troubleshooting why a patient sample did not run. The operator wanted to see if there were any alerts in the event log related to the sample. They first selected the Quick Find button to do a search for the sample Sid in the system search window. The operator scanned the Sid and then selected the Search button. They next selected the Errors or Events window to view a description of errors for that Sid. The operator found the Sid in the Description column. The description stated that the sampling of the Sid was stopped due to missing reagents. The operator then selected the Open Operator Event Log button on the right side of the screen to view more information. In the operator event log, the operator saw the same message that a reagent was missing. If the operator wanted to view procedures related to this event, they could have selected the question mark. Instead, the operator went to the Reagent needs screen by selecting Reagent needs from the home screen in Reagent needs, the operator was able to see the reagent that was needed on their chapter module. By loading that reagent pack, the operator was able to run the patient sample.

How to Troubleshoot Errors Using the Operator Event Log Video Master Template HILS2218 | Effective Date: 29-Jul-2021 > Operator Event Log Only Show Found Results Module (SN) Code Even Date 24 Hours ATELLICA-SH 05 002 02 12 Closed a drawer too quickly. Cannot obtain an image of drawer contents. 12/13/2020 4:09 PM Cannot obtain an image of drawer contents. Error 05 004 02 03 Reagent Missing 12/13/2020 3.58 PM 05 002 01 17 Calibration Error Information 12/13/2020 3:19 PM Show Events The SH has a softwere error. Sample processing will continue. Count 14 1 2 3 > Advanced Filters Export System Detalls Warning Modul 12 3 > Error 1 caused by missing Reapent. LabManager Healthineers Atellica Solution Troubleshooting System SH-02 The CH Analyzer cannot detect the UPS. Shut down and restart the analyzer. If problem persists, contact the local technical service provider for assistance. Current Status Day Needs Tools Samples STAT Sample Interventions 1 Inprocess Reagent Needs QC Statistics Assay Status QC Needs 10 Activities Due IM-01 Operator Event Log Online Help No Filter Q Search Filtered Data Q Q only Show Found Results Event Operator The CH Analyzer cannot detect the UPS. Shut down and restart the analyzer. If problem persists, 12/13/2021 1:20:07 PM Module 04 801 95 24 contact the local technical service provider for assistance. Additional Details Support Operating Mode Unknown, Code 04 801 95 24 The CH Analyzer cannot detect the UPS. Shut down and restart the analyzer. If problem persists, contact the local technical service provider for assistance. Request Apply Filter Operator Event Log English Message Log QEnter your search here ... LIS Log CH Alert Troubleshooting - - Online Help Search within page Assa ? Q Clear AN 통 ? warning Enter your search here ... 04 CH Alert Troubleshooting 04 801 95 01 The CH Analyzer cannot detect the UPS. Shut down and restart the analyzer. If problem persists, contact the local technical service provider for assistance. Event description The system does not detect the UPS. a. Shut down and restart the appropriate module or analyzer. Shutting Down and Restarting Time (minutes): 10 b. If problem persists, contact the local technical support provider for assistance. -+ Contacting the Local Technical Support Provider Time (minutes): 5 SIEMENS SH-01 STATS Supply Needs Inprocess 1 Intervention Needed Callbration Due System Search Search Include Historical Results Search Results Location (4) Errors or Events (6) Screen Description Multiple entries found matching SID123456789. Navigate to the screen to see them all. Open Operator Event Log Sampling of SID123456789 was stopped on CH01 due to reson: Missing Reagents Sampling of SID123456789001 was stopped on CH01 due to reason: Low Sample Volme System Messages Log Multiple entries found matching . Navigate to the screen to see them all. Open System Messages log Sample SID123456789122 was stopped at Module CH01 31212022 9:16 AM Puck Jam carrying Sample SID123456789511 in the track Troubleshooting > Operator Event Log ATELLICA-CH 12/13/2020 3:58 PM Waming Reagent > Reagent Needs Reagent Packs to Load Inventory Reason Add To Cart DMX CH-01 TSH IM-02 Note: Home screen > Reagent Needs Add All To Cart Related Thank You! You have completed the How to Troubleshoot Errors Using the Operator Event Log Video Disclaimer Please note that the learning material is for training purposes only. For the proper use of the software or hardware, please always use the Operator Manual or Instructions for Use (hereinafter collectively "Operator Manual") issued by Siemens Healthineers. This material is to be used as training material only and shall by no means substitute the Operator Manual. Any material used in this training will not be updated on a regular basis and does not necessarily reflect the latest version of the software and hardware available at the time of the training. The Operator Manual shall be used as your main reference, in particular for relevant safety information like warnings and cautions. Please note: Some functions shown in this material are optional and might not be part of your system. Certain products, product related claims or functionalities (hereinafter collectively "Functionality") may not (yet) be commercially available in your country. Due to regulatory requirements, the future availability of said Functionalities in any specific country is not guaranteed. Please contact your local Siemens Healthineers sales representative for the most current information. The reproduction, transmission or distribution of this training or its contents is not permitted without express written authority. Offenders will be liable for damages. All names and data of patients, parameters and configuration dependent designations are fictional and examples only. All rights, including rights created by patent grant or registration of a utility model or design, are reserved. Atellica, and all associated marks are trademarks of Siemens Healthcare Diagnostics Inc. or its affiliates. All other trademarks and brands are the property of their respective owners. Product availability varies by country and is subject to varying regulatory requirements. Please contact your local representative for availability. Siemens Healthcare GmbH 2022