Automatic analysis system and display device

Abstract

[Problem] To provide a technique that allows users to quickly parse logs output by an automatic analysis device. [Solution] The automatic analysis system related to this invention acquires logs describing the status of the automatic analysis device and displays them in parallel on a display device: a first line indicating the timing, a second line displaying alarm markers indicating abnormal or normal actions, and a third line displaying event markers that differ from abnormal actions. When an indicator on the display device moves to one of the event markers, detailed information about that event is displayed.

Description

Technical Field

[0001] This invention relates to an automatic analysis system and a display device. Prior Technology

[0002] The automated analyzer for analyzing samples logs and stores the data internally. When the automated analyzer malfunctions, the user will inquire with the supplier about the cause of the malfunction. At this time, the supplier's representative typically retrieves the logs from the automated analyzer and analyzes their contents to determine the cause. Patent Document 1 discloses a technique that shows the detailed operational information of the device required to confirm the cause of an automated analyzer malfunction (see abstract). [Prior Art Documents] [Patent Documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2009-216705 Summary of the Invention

[0004] [Problem to be Solved by the Invention] When analyzing logs from automated analysis devices, there are no clear standards for how to proceed with the analysis steps; instead, the decision is left to the person in charge of analysis. Therefore, time is required to grasp the overall situation of the logs and the location of anomalies, and the results also take a considerable amount of time to be communicated back to the user. Prior art, such as Patent Document 1, still has room for further improvement to allow the person in charge of analysis to more quickly identify anomalies from the vast overall log data.

[0005] Therefore, the object of this invention is to provide a technique that enables users to quickly parse logs output by automated analysis devices. [Means for solving the problem]

[0006] The automatic analysis system related to this invention acquires a log recording the status of an automatic analysis device and displays it on a display device in parallel: a first line indicating the timing, a second line displaying alarm markers indicating abnormal or normal actions, and a third line displaying event markers that differ from abnormal actions. When an indicator on the display device moves to one of the aforementioned event markers, detailed information about that event is displayed. [Effects of the Invention]

[0007] According to the present invention, a technique can be provided that enables users to quickly parse logs output by an automatic analysis device. Simple Explanation of the Diagram

[0008] [Figure 1] Structure diagram of Automatic Analysis System 1. [Figure 2] UI example provided by Computer 31. [Figure 3A] Screen example displaying detailed log information. [Figure 3B] Screen example displaying detailed log information. [Figure 4] Screen example displaying log summary. [Figure 5] Example of search result display. [Figure 6] Example of highlighting the drop-down section. [Figure 7] Example of search result display. [Figure 8] Example of linking the pop-up window for detailed log information with the title in the drop-down section. [Figure 9] UI example provided by Automatic Analysis System 1. Implementation

[0009] <Implementation Form 1> Figure 1 is a structural diagram of the automatic analysis system 1 related to Implementation Form 1. The automatic analysis system 1 is a system for acquiring and parsing logs generated by the automatic analysis device 21. The automatic analysis device 21 is a device for analyzing samples and is installed within facility 2. There can be two or more facilities 2 and automatic analysis devices 21. Multiple automatic analysis devices 21 can exist within one facility 2. The server 3 is connected to the automatic analysis device 21 via a network. The automatic analysis system 1 can acquire the logs generated by the automatic analysis device 21 via the network.

[0010] The automated analysis system 1 includes a server 3, which includes a computer 31 (display device) and a database 32. The computer 31 retrieves logs from the automated analysis device 21 and stores them in the database 32. The computer 31 generates a log analysis screen (user interface, hereinafter referred to as UI) by performing the processing described later on the logs stored in the database 32. Detailed information about the processing and UI will be explained later. A single log entry recorded in the database 32 is called a record.

[0011] Figure 2 shows a UI example provided by computer 31. Computer 31 reads the logs stored in database 32 and generates the UI shown in Figure 2 based on the content recorded in the logs, and displays it on a display device such as a monitor. In addition, although the following embodiments show an example of the timeline extending horizontally (in rows) on the screen, it can also extend vertically (in columns) on the screen.

[0012] When a user specifies a facility name / model / date in the designated field 201, the computer 31 reads the record for the specified date from the log generated by the automatic analysis device 21 in the user-specified facility 2 from the database 32, and displays its contents in the display field 202. The display field 202 displays a timeline (line 1) at the top, and below it, markers visually represent the log content. That is, when a user specifies a facility name / model / date in the designated field 201, the computer 31 reads the record for the specified date from the log generated by the automatic analysis device 21 in the user-specified facility 2 from the database 32, adjusts the display position of multiple types of log information in a timeline, and displays event markers. The pull-out section 203 will be explained in Figure 4.

[0013] The automatic analysis device 21 may generate multiple types of logs. Here, it is assumed that the automatic analysis device 21 generates the following seven types of logs: device status, alarm trace, operation trace, calibration / QC trace, communication trace, motor log, and maintenance log. The display column 202 will display the log content according to the log type on each line along the timeline.

[0014] When the automatic analysis device 21 is operating, it continuously generates a log describing the internal state of the device (device status). Therefore, the device status log exists in all time periods. The device status is represented by a bar chart. The computer 31 reads the device status log from the database 32 and displays bar charts representing its contents on the device status line. The types of bar charts in the device status column correspond to the device status recorded in the device status log. For example, the device status log may record the following device statuses: initialization status (initialization), standby status, status performing reagent registration operation, status performing sample analysis operation (operation in progress), status performing maintenance, and status with abnormality or signs of abnormality (alarm).

[0015] When a user performs an operation on the automatic analysis device 21, the automatic analysis device 21 logs the contents of the operation as an operation trace. The computer 31 reads the operation trace from the database 32 and displays a white circle (event marker) as shown in Figure 2 on the operation trace line at the time when an operation trace record exists. That is, the white circle in the operation trace column indicates the time when the operation trace was generated.

[0016] When an alarm occurs inside the automatic analysis device 21 (e.g., abnormal action), it logs the contents of the alarm as an alarm trace. The computer 31 reads the alarm trace from the database 32 and displays a diagonal circle (alarm marker) as shown in Figure 2 on the alarm trace line at the time when the alarm trace record exists. That is, the diagonal circle of the alarm trace indicates the time when the alarm trace was generated.

[0017] To facilitate visual understanding of log type differences, the shape, appearance, and color of the markers (white circles and diagonal circles) on the UI in Figure 2 should ideally change according to the log type. For example, logs describing alarms (e.g., signs of abnormality) can be represented by diagonal circles, logs describing more dangerous states (e.g., abnormal actions) can be represented by black circles, while logs describing other normal actions can be represented by white circles, and so on. This distinction applies to all log types.

[0018] Figure 3A shows an example of a screen displaying detailed log information. The display method is illustrated using device status, alarm tracking, and operation tracking as examples. In individual log entries, if multiple log entries exist during the display period, one log entry can be displayed as a separate marker, or multiple log entries can be displayed as a summary. An example of alarm tracking being displayed as a separate marker is shown, while device status and operation tracking are displayed as a summary. In the UI of Figure 2, when the user selects any marker (in Figure 2, the striped marker for device status, the diagonal circle for alarm tracking, and the white circle for operation tracking) (by clicking the marker or hovering the mouse over it to focus), the computer 31 displays the detailed log information corresponding to that marker in a pop-up window as shown in Figure 3. The detailed log information is obtained simultaneously when each marker is displayed in display field 202. The marker selected by the user will be more prominent than other markers. In Figure 3A, the white circle marker selected by the user is enlarged, but other forms of emphasis can also be used (e.g., flashing display).

[0019] Figure 3B shows an example of a screen displaying detailed log information. It shows an example of the display at any given moment in the selected device state. The selected moment is highlighted with a thick outline, and the log details are displayed in a pop-up window.

[0020] Users can see the alarm tracking occurring at 13:30 on the UI shown in Figures 2 and 3. To investigate the cause of this alarm tracking, users may want to examine the contents of other logs from the same time (or nearby). In Figure 3, users can quickly examine the contents of other logs from the same time as the alarm tracking by clicking on their markers. Therefore, the actions that caused the alarm, or the device states that changed due to the alarm, can be quickly understood by starting with the alarm and grasping the relationships between logs.

[0021] Figure 4 shows an example of a log overview. When the user clicks the pull-out section 203, the hidden pull-out section is displayed on the screen. The pull-out section displays a list of the log titles and record counts shown in column 202. For example, operation tracking is displayed as five white circles in column 202, but the pull-out section shows that it contains 257 records. This means that each white circle contains multiple records, and the total number of records is 257. Clicking on each log name expands the list of its log titles. An example of the expanded display will be explained later.

[0022] Figure 5 shows an example of search results. When the user clicks the full log search button 204, enters the search keyword (here, "START"), and then clicks the search button again, the computer 31 searches for content matching the keyword from the logs stored in the database 32 (or from the logs already retrieved from the database 32). The searched records are highlighted in the display field 202. In the example of Figure 5, records in the device status and records in the operation tracker that match the search are highlighted with thick outlines. Records in the operation tracker are further enlarged for display.

[0023] Figure 6 shows an example of emphasis within the pull-out section. When a keyword search is performed as shown in Figure 5, and the user pulls out pull-out section 203, the portion of the record titles within the pull-out section that matches the search keywords is emphasized. When the user clicks on any log name displayed in the pull-out section, the list of record titles contained in that log expands. Figure 6 shows the expanded state of the operation trace. If no search is performed, the log title list is displayed, for example, in chronological order. When a search is performed, only the content in the log title list that matches the search keywords is retrieved and displayed in the pull-out section. At this time, the portion of the title that matches the search keywords is emphasized (underlined and highlighted in Figure 6). Other log names are displayed in the same way. The emphasis format is not limited to this; for example, any format such as colored markers can be used.

[0024] Figure 7 shows an example of search results. When a user clicks the search button 205 for each log entry, a field for entering search keywords for that log entry is displayed. This example shows the search keyword "START" entered for Operation Tracking. Figures 5-6 treat all log entries as search targets, while Figure 7 treats only the log entries containing the entered keyword as search targets. Here, some content in the Operation Tracking record matches the search, and the corresponding white circle is enlarged and highlighted with a thick outline. The rest is the same as in Figures 5-6.

[0025] In Figure 7, because each log name used for keyword search has a keyword input field, log names with entered keywords become search targets. That is, the specified input for the log name to be searched also serves as the keyword input. Alternatively, log names to be searched can be pre-selected from a list, and the selected logs can be used as search targets. That is, the specified input for the log name to be searched can be entered in any format.

[0026] In the keyword search examples illustrated in Figures 5 to 7, it was explained that tags matching the search query were highlighted in display field 202. Even if the user selects a tag that does not match the search query, it is recommended not to use the same highlighting and detailed information pop-up windows as shown in Figures 3 and 4. This is because when displaying detailed information, highlighting the selected tag as shown in Figure 3 would not distinguish whether the highlighting was due to matching the search query or due to user selection. Furthermore, if the user selects a tag that does not match the search query, a different highlighting method can be used.

[0027] Figure 8 shows an example of the interaction between the pop-up window displaying detailed log information and the title in the pull-out section. When the pull-out section 203 is in the pull-out state, if the user clicks on any log record (any circular marker), the detailed content of that log will be displayed in a pop-up window, and the title of the same record will also be displayed in the pull-out section. An example of clicking on an alarm tracking record is shown here. The alarm tracking record content is displayed in a pop-up window, and the same record is also displayed in the pull-out section. When the user selects another record in the display field 202, the display in the pull-out section will switch to the title of that record. Thus, by linking the pop-up window in the display field 202 with the pull-out section, the user can visually identify which log content they are viewing.

[0028] The record titles displayed in the drop-down section can be either the titles of the records shown only in the pop-up window, or the titles of the records shown in the pop-up window can be moved to the top of the list. In other words, as long as the titles of the records shown in the pop-up window are linked to the list and visually emphasized, the display format can be arbitrary.

[0029] Furthermore, when an item representing a record is selected in the drop-down section, the event markers for the same record in display field 202 can be highlighted, or a pop-up window displaying the record content of the event markers can be shown. The display between display field 202 and drop-down section 203 can also be linked bidirectionally in this way.

[0030] <Implementation Type 2> Figure 9 shows a UI example provided by the automatic analysis system 1 in Implementation Type 2. In Implementation Type 1, we illustrated an example where a user selects one of the facilities 2 from the designated fields 201, and the logs of the automatic analysis device 21 in the selected facility 2 are displayed. In Figure 9, the user selects one facility 2 for each of the two designated fields 201, and the display field 202 displays the respective logs. For ease of description, the display field 202 in Figure 9 is simplified, but the same display field 202 as in Implementation Type 1 can be used. By displaying the logs of the two automatic analysis devices 21 side by side, the user can analyze the causes of anomalies while comparing these logs.

[0031] Users can also specify different automatic analysis devices 21 within the same facility 2 for the specified field 201. For example, by comparing the automatic analysis device 21 that has been maintained and the automatic analysis device 21 that has not been maintained, it can be verified whether the cause of the alarm is whether maintenance has been performed.

[0032] Additionally, in Figure 9, the log information shows two facilities from the beginning. However, when only the log information of one automatic analysis device of one facility is displayed, a UI can also exist that allows adding log information of other automatic analysis devices and / or other facilities, or deleting log information of a certain facility and / or a certain automatic analysis device from the log information of multiple automatic analysis devices and / or multiple facilities.

[0033] <Implementation Form 3> Supplementing the above implementation forms with examples of log usage. Calibration / QC Tracking is a log of calibration or QC (Quality Control) processes performed by the automatic analysis device 21. Communication Tracking is a log of communications between the automatic analysis device 21 and other devices. Motor Log is a log of the motors equipped in the automatic analysis device 21. Maintenance Log is a log of maintenance operations performed by the automatic analysis device 21. These logs can be used using the following examples.

[0034] In alarm tracking, suppose a unit blanking anomaly alarm occurs after an alarm requesting a change of reaction tank water. In this case, if the maintenance log does not record appropriate maintenance procedures, it can be inferred that the failure to perform maintenance is the cause of the unit blanking anomaly alarm. Users can analyze the alarm causes in the above manner by checking the detailed maintenance log information near each alarm in display field 202.

[0035] In alarm tracking, suppose the calibration process of the ion-selective electrode in the automatic analysis device 21 malfunctions. If the maintenance procedures that should have been performed the day before the malfunction occurred (e.g., electrode cleaning) were not recorded in the maintenance log, it can be inferred that the failure to perform maintenance is the cause of the malfunction. Users can analyze the cause of the alarms in the above manner by checking the detailed maintenance log information near each alarm in display field 202.

[0036] <Regarding Variations of the Invention> The present invention is not limited to the embodiments described above, but includes various variations. For example, the embodiments described above are for the purpose of clearly explaining and detailing the information, and are not necessarily limited to all the components described. Furthermore, a part of the structure of one embodiment may be replaced with the structure of another embodiment, or the structure of another embodiment may be added to other components of one embodiment. In addition, regarding a part of the structure of each embodiment, other components may be added, deleted, or replaced.

[0037] In the above embodiments, the computer 31 can be composed of hardware such as circuit devices that implement its operation, or it can be composed of a computing device such as a CPU (central processing unit) that executes software that implements its operation. The database 32 can be constructed by storing recorded data in a storage device.

[0038] In the above embodiments, the automatic analysis system 1 and the automatic analysis device 21 can also be integrated to form an automatic analysis system. The automatic analysis system 1 does not necessarily need to be located in a different geographical location from the facility 2; it can be installed in any facility 2.

[0039] In the above implementation, an example of an event marker displayed in parallel with an alarm marker is shown on an operation trace line. However, records in other logs can also be displayed as the same event marker on the corresponding lines of each log.

[0040] In the above embodiments, the UI (Figures 2-9) provided by computer 31 can be provided in any form. For example, when computer 31 and database 32 constitute a client-server system, computer 31 operates as a client terminal providing the UI while retrieving records from database 32. Therefore, the UI can be displayed on a display device such as a monitor provided by computer 31. When the UI is configured as a web application, computer 31 operates as a web server and provides the UI as shown in Figures 2-9 as a web application. Therefore, computer 31 can display the UI on a display device provided by a client terminal running a web browser (i.e., by providing a web application that can be displayed by a web browser, the UI can be displayed on the client terminal). In this case, the client terminal can also be a component of automatic analysis system 1. Thus, multiple users can simultaneously access the client terminal and browse.

[0041] 1: Automated Analysis System 2: Facilities 21: Automatic Analysis Device 201: Specify field 202: Display Fields 203: Pull-out section 204: Full Log Search Button 205: Search buttons for each log entry 3: Server 31: Computer 32: Database

Claims

1. An automated analysis system for analyzing logs output by an automated analysis device for specimen analysis, wherein: The system includes a computer connected to the aforementioned automatic analysis device via a network; the computer acquires the aforementioned log recording the status of the aforementioned automatic analysis device and displays the aforementioned status recorded in the aforementioned log on a display device along a first line indicating the timing; the computer acquires the aforementioned log recording whether the aforementioned automatic analysis device is operating abnormally or normally, and displays alarm markers on the aforementioned display device along a second line parallel to the aforementioned first line, indicating the time when the aforementioned abnormal or normal operation occurred; the computer acquires the aforementioned log recording an event in the aforementioned automatic analysis device that is different from the aforementioned abnormal operation, and displays event markers on the aforementioned display device along a third line parallel to the aforementioned first and second lines, indicating the time when the aforementioned event occurred; when the operation indicator displayed on the aforementioned display device is focused on the aforementioned event marker, the computer displays detailed information about the aforementioned event on the aforementioned display device.

2. As in request item 1, an automated analysis system, wherein, The aforementioned log corresponding to the aforementioned event marker records the operations performed by the user in the aforementioned automatic analysis device; the aforementioned computer displays the aforementioned user's operation tracking record of the aforementioned automatic analysis device by displaying the aforementioned event marker in chronological order along the aforementioned third line.

3. As in request item 1, an automatic analysis system, wherein, The aforementioned computer obtains the list of record titles recorded in the aforementioned log; in addition to the aforementioned alarm markers and event markers, the aforementioned computer also displays a pull-out section on the aforementioned display device listing the aforementioned titles.

4. As in request item 1, an automated analysis system, wherein, The aforementioned computer obtains the aforementioned log and the detailed record describing the aforementioned event together; the aforementioned computer displays an input field on the aforementioned display device where a string can be entered, and the aforementioned computer compares the aforementioned string entered into the aforementioned input field with the aforementioned detailed record described in the aforementioned data; the aforementioned computer highlights on the aforementioned display device the aforementioned event marker that has a part that is consistent with or similar to the aforementioned string and corresponds to the aforementioned detailed record.

5. As in request item 4, an automatic analysis system, wherein, The aforementioned computer highlights on the aforementioned display device the portion of the aforementioned detailed record that is identical or similar to the aforementioned string.

6. As in request item 4, an automated analysis system, wherein, The aforementioned computer obtains a plurality of the aforementioned logs from the aforementioned automatic analysis device; the aforementioned computer receives a specified input specifying the type of the aforementioned log to be compared with the aforementioned string; the aforementioned computer compares the aforementioned log type specified by the aforementioned specified input, the aforementioned detailed record, and the aforementioned string, while excluding the aforementioned detailed record whose type of the aforementioned log is not specified by the aforementioned specified input from the comparison with the aforementioned string.

7. As in request item 3, an automated analysis system, wherein, When the aforementioned computer displays the aforementioned pull-out section on the aforementioned display device, and when the aforementioned event marker is focused on by the aforementioned operation indicator, detailed information of the aforementioned event marker is displayed on the aforementioned display device, and the aforementioned title of the aforementioned log corresponding to the focused aforementioned event marker is displayed in the aforementioned list.

8. The automatic analysis system as described in request item 1, wherein, The aforementioned computer obtains, as the aforementioned logs, a first log output by a first automatic analysis device and a second log output by a second automatic analysis device; the aforementioned computer displays on the aforementioned display device a selection field for selecting either the aforementioned first automatic analysis device or the aforementioned second automatic analysis device; when the aforementioned computer selects the aforementioned first automatic analysis device in the aforementioned selection field, it displays the aforementioned status, the aforementioned alarm flag, and the aforementioned event flag of the aforementioned first automatic analysis device along the aforementioned first line, the aforementioned second line, and the aforementioned third line, respectively, based on the records recorded in the aforementioned first log; when the aforementioned computer selects the aforementioned second automatic analysis device in the aforementioned selection field, it displays the aforementioned status, the aforementioned alarm flag, and the aforementioned event flag of the aforementioned second automatic analysis device along the aforementioned first line, the aforementioned second line, and the aforementioned third line, respectively, based on the records recorded in the aforementioned second log.

9. The automatic analysis system as described in request item 1, wherein, The aforementioned alarm markers may be displayed as: a marker indicating normal operation of the aforementioned automatic analysis device; a marker indicating signs of abnormality in the aforementioned automatic analysis device; or a marker indicating abnormal operation of the aforementioned automatic analysis device; any one of these.

10. The automatic analysis system as described in request item 1, wherein, The aforementioned computer obtains the first log output by the first automatic analysis device and the second log output by the second automatic analysis device, which are the aforementioned logs. The aforementioned computer displays the aforementioned alarm marker corresponding to the aforementioned first log and the aforementioned event marker corresponding to the aforementioned first log on the aforementioned display device. The aforementioned computer displays the aforementioned alarm marker corresponding to the aforementioned second log and the aforementioned event marker corresponding to the aforementioned second log on the aforementioned display device together with the aforementioned first display field.

11. The automatic analysis system as described in request item 1, wherein, The aforementioned computer, while acquiring the device status as the aforementioned log that records the internal status of the aforementioned automatic analysis device, displays the markers indicated by the aforementioned internal status recorded by the aforementioned device status on the aforementioned display device in a chronological order along the aforementioned first line, the aforementioned second line, and the aforementioned third line, in a fourth line parallel to the aforementioned first line, the aforementioned second line, and the aforementioned third line.

12. The automatic analysis system as described in request item 11, wherein, The aforementioned device states, as the aforementioned internal states, describe at least the following: the aforementioned automatic analysis device is in the initialization state; the aforementioned automatic analysis device is in the standby state; the aforementioned automatic analysis device is performing reagent registration; the aforementioned automatic analysis device is performing the aforementioned sample analysis; maintenance of the aforementioned automatic analysis device is being performed; the aforementioned automatic analysis device is in an abnormal state or shows signs of abnormality; and at least one of these states.

13. A display device for an automated analysis apparatus connected to an analysis sample via a network, the display device: simultaneously acquiring a log recording the status of the automated analysis apparatus, displaying the status recorded in the log along a first line indicating timing; simultaneously acquiring a log recording that the automated analysis apparatus is operating abnormally or normally, displaying an alarm flag indicating the time of occurrence of the abnormal or normal operation recorded in the log along a second line parallel to the first line; simultaneously acquiring a log recording an event in the automated analysis apparatus that occurs differently from the abnormal operation, displaying an event flag indicating the time of occurrence of the event recorded in the log along a third line parallel to the first and second lines; and displaying detailed information about the event when an operation indicator is focused on the event flag.

Images