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

Welcome to the Italica solution, how to troubleshoot errors using the operator event log video. This video will explain the details of the operator event log on the Italica 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. And 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 Ch modules were not green. The operator also noticed an alert in the Notification Center which said the CHT 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 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 ACH module, the operator was able to resolve the error. Let's look at another troubleshooting example, this time involving a patient sample. And 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 said. The operator found the SSID in the description column. The description stated that the sampling of the SSID 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 Ch module. By loading that reagent pack, the operator was able to run the patient sample.

Master Template HILS2218 | Effective Date: 29-Jul-2021 How to Troubleshoot Errors Using the Operator Event Log Video Time: 24 Hours Only Show Found Results Module (SN) Code Event Date 24 Hours ATELLICA-CH 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 05 004 02 03 12/13/2020 3:58 PM Warning 05 002 01 17 Calibration Error Information 12/13/2020 3:19 PM Show Events Count 14 Export System Detalls NI Error LabManager SIEMENS Troubleshooting System 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 QC Needs Operator Event Log Online Help Filter Clear No Filter Q Q only Show Found Results Severity Operator 04 801 95 24 The CH Analyzer cannot detect the UPS. Shut down and restart the analyzer. If problem persists, 12/13/2021 1:20:07 PM Support Request Apply Filter Log LIS Log CH Alert Troubleshooting - - Online Help Search within page Assay Operator Event 04 501 95 05 04 001 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 04 801 95 02 ass stance. 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 probiem persists, contact the local technical support provider for Time (minutes): 5 Service ? Q SH-01 CH-01 STATs Supply Needs 1 Intervention Needed Callbration Due Assay Status System Search Search Search Results Location (4) Errors or Events (6) Open Operator Event Log Sampling of SID123456789001 was stopped on CH01 due to reason: Low Sample Volme 312 2022 8:10 AM 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 Troubleshooting > Operator Event Log Filters: Module 1 2 3 > Reagent Packs to Load Reason Add To Cart DMX TSH M-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 91052 Erlangen, Germany\Telephone: +49 9131 84-Olsiemens-healthineers.com