ANALYSIS INFORMATION MANAGEMENT SYSTEM

Abstract

In the case where a plurality of analysis data files which respectively contain analysis results and data-analyzing process results for a plurality of samples should be managed as one lot, a portion of the information contained in those analysis data files is extracted and compiled into a final result record report file. This file is registered in a database. A supervisor views the final result record report on a client terminal, evaluates the validity of the analysis result and other contents for each sample, and performs a predetermined operation to execute the signature of approval or other evaluations. Signature information, including the signer's name, date and time of the signature, etc., is recorded for the final result record report file. The same signature information is also recorded for each of the analysis data files located by referring to link information.

Claims

1. An analysis information management system including a communication network, an analytical instrument connected to the communication network, a database server connected to the communication network, as well as a client terminal connected to the communication network and provided with an operation unit and a display unit, the analysis information management system configured to register, in a database constructed on the database server, a data file containing analysis data acquired by performing an analysis on a sample with the analytical instrument and/or data-analyzing process result acquired by performing a data-analyzing process based on the analysis data using the client terminal, and to manage the registered data file, wherein: the client terminal includes: a) an integrated file creator for extracting at least a portion of a plurality of pieces of information respectively contained in a plurality of data files registered in the database or a plurality of pieces of information respectively associated with the data files, for compiling the extracted pieces of information into one integrated file, and for storing the integrated file in the database; b) a signature-receiving processor for reading the integrated file from the database and displaying the pieces of information contained in the integrated file on the display unit, and for receiving a predetermined operation with the operation unit by a user viewing the displayed information, as a command to execute a signature for the integrated file; and c) a signature-executing processor for performing a recording of the signature for the integrated file and for performing a recording of the signature for each of the data files from which the integrated file is created, when the command to execute the signature is received by the signature-receiving processor.

2. The analysis information management system according to claim 1, wherein: The integrated file creator creates link information showing a correspondence relationship between the integrated file and the data files from which the integrated file is created, and stores the link information in the database.

3. The analysis information management system according to claim 2, wherein: the signature-receiving processor prepares a list of information for identifying the data files corresponding to the integrated file or information related to the data files, with reference to the link information, and displays the list on the display unit.

Description

BRIEF DESCRIPTION OF DRAWINGS

[0027] FIG. 1 is a schematic configuration diagram of one embodiment of the analysis information management system according to the present invention.

[0028] FIG. 2 is a flowchart showing the final result record creation process in the analysis information management system according to the present embodiment.

[0029] FIG. 3 is a model diagram showing one example of the form of a final result record report.

[0030] FIG. 4 is a model diagram showing one example of a data manager window for final result record creation.

[0031] FIG. 5 is a model diagram showing another example of the data manager window for final result record creation.

[0032] FIG. 6 is a conceptual diagram showing the relationship of files in the case of handling a plurality of analysis data files as one lot.

[0033] FIG. 7 is a diagram illustrating an operation of a signature-executing process in the case of handling a plurality of analysis data files as one lot.

[0034] FIG. 8 is a diagram showing one example of a display window for viewing the link between a plurality of analysis data files and a final result record report file.

[0035] FIG. 9 is a diagram showing one example of an analysis report.

[0036] FIG. 10 is a diagram showing one example of an audit trail report.

[0037] FIG. 11 is a diagram showing one example of a data list.

DESCRIPTION OF EMBODIMENTS

[0038] One embodiment of the analysis information management system according to the present invention is hereinafter described with reference to the attached drawings.

[0039] FIG. 1 is a schematic configuration diagram of the main components of the analysis information management system according to the present embodiment.

[0040] The analysis information management system according to the present embodiment includes: one or more analytical instruments 2 for performing a predetermined analysis on a sample and collecting measurement data; a database server 1 which is actually a computer; and a client terminal 4 which is actually a personal computer. These three kinds of devices are connected to each other through a communication network 3, such as a local area network (LAN). An operation unit 5, which includes a mouse, keyboard and other devices, as well as a display unit 6 and a printing unit 7 are connected to the client terminal 4. Normally, an operation unit, display unit and other devices are also connected to the database server 1, although those units are not shown in FIG. 1.

[0041] Although the configuration shown in FIG. 1 has a single client terminal 4, there may be multiple client terminals. The client terminal 4 may additionally function as the database server 1. Each analytical instrument 2 may have built-in functions which effectively work similar to a computer d enable direct connection to the communication network 3. However, more typically, the analytical instrument is connected to the communication network 3 via a personal computer (not shown). In that case, two or more analytical instruments 2 may be connected to a single personal computer which is connected to the communication network 3. Such a personal computer may be configured to serve as a client terminal 4. The type of analytical instruments 2 is not specifically limited. Different types of analytical instruments may be connected to the communication network 3. For convenience of description, it is hereinafter assumed that the analytical instruments 2 are all liquid chromatograph (LC) apparatuses.

[0042] The database server 1 includes an analysis data collector 11, log information collector 12, database manager 13, database 14 and other functional blocks. The database 14 is used to register various kinds of files and information, such as the analysis data file, analysis report file, log information data file, audit trail report file, final result record report file, and parent-child file link information. The client terminal 4 includes a data analysis processor 41, analysis report creator 42, audit trail report creator 43, data list creator 44, final result record report creator 45, signature-receiving processor 46, signature-executing processor 47 and other functional blocks. As noted earlier, the database server 1 and the client terminal 4 are actually computers. Therefore, the aforementioned functional blocks are embodied by dedicated programs which are previously installed on those computers and executed on the same computers.

[0043] In the database server 1, the analysis data collector 11 collects data acquired in each analytical instrument 2 by an LC analysis on a sample as well as various items of information related to the analysis through the communication network 3. The collected data and information are registered through the database manager 13 in the database 14 as an analysis data file. When the analysis data file is registered, a data ID for uniquely identifying the file is automatically given to the file. The analysis data file normally contains various items of data. and information related to an analysis on one sample. That is to say, in addition to the analysis data acquired through an analysis, those items of data and information include: sample information, such as the name and amount of the sample; device ID for identifying an analytical instrument used for the analysis; date and time of the analysis; analyzer user ID for identifying an operator who carried out the analysis; analysis conditions applied in the analysis (e.g. the flow velocity of the mobile phase); and calibration curve information for quantitative determination. The same analysis data file may additionally be used to store various kinds of calculated values obtained through a data-analyzing process based on the analysis data by the data-analyzing processor 41 in the client terminal 4 as well as other related items of information.

[0044] The log information collector 12 collects various items of information through the communication network 3 and registers the information through the database manager 13 in the database 14 as the log information data file. The items of information include operations and tasks performed by users on all analytical instruments 2, client terminal 4 and other devices included in the present system, as well as information indicating the state of each device, such as an error which occurred in an analytical instrument 2, client terminal 4 or other devices during an execution of a measurement or data-analyzing process. For example, the operation log data file, which shows operation logs, contains various kinds of data and information related to each specific operation: content of the operation; device ID for identifying an analytical instrument 2 or client terminal 4 on which the operation was performed; date and time of the operation; and user ID for identifying an operator who performed the operation.

[0045] Next, various processing operations to be performed on the client terminal 4, with analysis data files stored in the database 14, are described.

[0046] [Analysis Report Creation Process]

[0047] The analysis report creator 42 in the client terminal 4 automatically creates an analysis report in a predetermined form based on the various data and information contained in an analysis data file, and registers the analysis report in the database 14 as an analysis report file in PDF format.

[0048] Specifically, an operator in charge of an analysis operation performs a predetermined operation with the operation unit 5 to select an analysis data file for which an analysis report should be created and a template for the same report, and issues a command to create the report. Then, the analysis report creator 42 begins to operate and accesses the database server 1 to read the report template concerned and the specified analysis data file from the database 14. A report template is a form (format) of a report in Which various report items, such as the sample information, chromatogram and peak report, are appropriately arranged. The provider (manufacturer) of the present system can previously create such templates and register them in the database 14.

[0049] The analysis report creator 42 creates an analysis report by inserting necessary information into the information presentation field of each report item in the read report template. Examples of the inserted information include: a chromatogram created from the data contained in the analysis data file; a peak table showing the information concerning the peaks on the chromatogram obtained by performing a data-analyzing process on the chromatogram; and sample information contained in the analysis data file. The analysis report may also include a check result entry field for each report item to allow a checker, who is different from the operator, to check the content of the analysis report and enter the check result as well as describe the reason for the rejection of the content if the checker has concluded that the reported content is unacceptable.

[0050] FIG. 9 is a diagram showing one example of the analysis report which is automatically created. In the present example, there are three report items, i.e. the sample information, chromatogram and peak report, in which the chromatogram and peak report are each provided with a check result entry field.

[0051] A method for creating a report template in which check result entry fields are provided is described, for example, in the Japanese Patent Application No. 2015-239016, which is a prior application filed by the applicant.

[0052] [Audit Trail Report Creation Process]

[0053] The audit trail report creator 43 in the client terminal 4 automatically collects various pieces of log information related to one or more analysis data files, creates a list showing those pieces of log information arranged in time-series order, and registers an audit trail report inclusive of the list in the database 14 as an audit trail report file in PDF format.

[0054] Specifically, an operator performs a predetermined operation with the operation unit 5 to select analysis data files for which an audit trail should be created, and issues a command to create the audit trail. Then, the audit trail report creator 43 begins to operate and accesses the database server 1 to read all log information files related to the specified analysis data files. The all log information files contain two types of log information: the log information identified by the device ID of the analytical instrument with which the data contained in the analysis data files were acquired and the user ID of an analysis operator who took charge of the analysis, obtained within a period of time from login to logout including the date and time of the creation or registration of the analysis data files; and the log information which indicates a certain kind of file operation performed on each specified analysis data file.

[0055] The former type of log information can be collected by searching the log information in the database 14 using, as search keys, the device ID, user ID as well as date and time of creation (or registration) contained in the analysis data files or associated with those files as property information for example. The latter type of log information can be collected by searching the log information in the database 14 using, as a search key, the data ID associated with each analysis data file. It is also possible to issue a login ID which allows for unique identification of a time range from a login operation to the logout on any of the devices in the present system, i.e. the analytical instruments 2, client terminal 4 and other devices, and to add the login ID to every log information data file and every analysis data file. This facilitates the extraction of the log information related to an analysis data file.

[0056] The audit trail report creator 43 creates an audit trail by organizing a large number of pieces of log information extracted in the previously described manner in time-series order, and creating a list which shows messages that briefly describe the contents of the respective pieces of log information along with a portion of the log information.

[0057] FIG. 10 is a diagram showing one example of the audit trail report which is automatically created.

[0058] [Final Result Record Report Creation Process]

[0059] Next, a processing operation for creating a final result record report is described. This report includes the information of the analysis report based on the data contained in an analysis data file and the information of an audit trail report. Although the final result record report may be created for a single sample, the following description deals with the case of creating a final result record report which reflects analysis results, data-analyzing process results and other data obtained for a plurality of samples by a continuous analysis. Such a final result record report is useful in the case where a plurality of samples which are handled as one lot should be collectively evaluated based on analysis results and data-analysis results obtained for those samples.

[0060] FIG. 2 is a flowchart showing the final result record creation process. FIG. 3 is a model diagram showing one example of the form of a final result record report. FIG. 4 is a model diagram showing one example of a data manager window for final result record creation. FIG. 5 is a model diagram showing another example of the data manager window for final result record creation.

[0061] In advance of the creation of the final result record, an operator performs a predetermined operation with the operation unit 5 of the client terminal 4 to specify the contents and form of the final result record report (Step S1). For example, in the case of FIG. 3, the final result record report can contain various items of information described in the following order: a list of analysis results and re-analysis results, audit trail report, analysis condition list, data-analysis condition list, calibration curve information, as well as analysis reports for individual samples. The items and form of the report may be appropriately changed; for example, the order of the items may be appropriately changed, some of those items may be removed, or new items may be added. Step S1 may be bypassed if the default setting of the contents and form of the final result record report can be used as it is, or if there is no need to change the previously used setting.

[0062] Subsequently, the operator performs a predetermined operation with the operation unit 5 of the client terminal 4, whereupon the final result record report creator 45 begins to operate and displays a data manager window 100 for final result record creation on the screen of the display unit 6. As shown in FIG. 4, the data manager window 100 has a file selection setting area 101 located in its left part and a data file list 102 located in its upper right part. The setting in the file selection setting area 101 can be selected from two modes: narrow down and batch data set. FIG. 4 is the case of the narrow down setting, while FIG. 5 is the case of the batch data set setting.

[0063] In the case of using the narrow down setting in the file selection setting area 101 as shown in FIG. 4, the operator sets the narrowing conditions in one or more narrowing items in the file selection setting area 101. Then, the final result record report creator 45 accesses the database 14 to search for analysis data files which satisfy the narrowing conditions, and displays a list of the thereby found analysis data files in the data file list 102. It is naturally possible to refine the search with additional narrowing conditions and decrease the number of analysis data files if there is an excessive number of analysis data files displayed in the data file list 102.

[0064] The operator specifies a plurality of analysis data files included in one lot for which the final result record report should be created among the analysis data files displayed in the data file list 102, by a clicking operation with a mouse on the screen. In FIG. 4, the six analysis data tiles denoted by reference sign 103 are selected. The selected tiles are highlighted. Then, for example, the operator presses the right button of the mouse on the selected items, whereby an operation menu 104 as shown in FIG. 4 is displayed. The operator selects the Create report set 105 in this menu and performs the clicking operation. This operation corresponds to the command to create the final result record (Step S2).

[0065] Upon receiving the command, the final result record report creator 45 reads the selected analysis data files as well as the audit trail report file and the analysis report file related to those analysis data files from the database 14 (Step S3). The correspondence relationship of the analysis data files with the audit trail report file and the analysis report file can be established by using the data ID which identifies each analysis data file as described earlier. As another possible method, when an audit trail report file or analysis report file is registered in the database 14, link information which shows the relationship with the analysis data files may be created and registered in the database 14 so that the audit trail report file and analysis report file concerned can be located by referring to this link information.

[0066] The data list creator 44 creates a data list showing the file name, sample name, sample ID and other items based on the data and information contained in the read analysis data files (Step S4). FIG. 11 shows one example of the data list (in part). It is preferable to allow users to arbitrarily set the items to be displayed in the data list.

[0067] According to the form of the final result record report specified in Step S1, the final result record report creator 45 creates an image of the final result record report in which the necessary contents are arranged, including the list of analysis results and re-analysis results prepared in Step S4, content of the audit trail report (list of the log information in time-series order) as shown in FIG. 10, content of the analysis report as shown in FIG. 9, as well as the analysis condition, data-analysis condition, calibration curve and other pieces of information contained in the analysis data files. The image of the final result record report is converted into a PDF file and registered in the database 14 (Step S5).

[0068] In this manner, a final result record report which holds an organized set of information and data related to a plurality of analysis data files selected by an operator can be created, and a PDF file of the report can be registered in the database 14.

[0069] On the other hand, in the case of using the batch data set setting in the file selection setting area 101 as shown in FIG. 5, a plurality of analysis data files to be included in one lot are previously specified and registered in a batch file. The batch file does not contain any substantial data (e.g. analysis results); it is a file which records the properties or similar information concerning a plurality of analysis data files.

[0070] The operator sets the conditions to narrow down the data sets in one or more narrowing items in the file selection setting area 101. Then, the batch files which satisfy the narrowing conditions are displayed in a batch file list 106 displayed in the file selection setting area 101. The operator indicates the target batch file among those batch files by a clicking operation with the mouse on the screen. In FIG. 5, the batch file indicated by reference sign 108 is selected. The selected file is highlighted.

[0071] Upon selection of a batch file, the analysis data files registered for the batch file are displayed in the data file list 102. The operator presses the right button of the mouse on this list, whereby an operation menu 108 as shown in FIG. 5 is displayed. The operator selects the Create report set 109 in this menu and performs the clicking operation. This operation corresponds to the command to create the final result record for all analysis data files specified in the form of a batch file. In this manner, the operator can collectively select a plurality of analysis data files to create the final result record report related to those analysis data files and register the report in the database 14.

[0072] When one final result record report corresponding to a plurality of analysis data files is created and stored in the database 14 in the previously described manner, the final result record report creator 45 creates link information showing the correspondence relationship between the final result record report and the original analysis data files. This link information is also registered in the database 14.

[0073] FIG. 6 is a conceptual diagram showing the relationship of files in the case of handling a plurality of analysis data files as one lot. As shown in FIG. 6, the information contained in one final result record report file obtained through the previously described process is composed of pieces of information A, B, . . . and X which are parts of the analysis results and data-analyzing process results stored in the analysis data files as well as a graph, table or other forms of information based on those results. Accordingly, parent-child file link information which shows the relationship between a parent file and child files is created, with the final result record report file considered as a parent file and each analysis data file as a child file. In the case of using the narrow down setting in the file selection setting area 101, the analysis data files selected on the data manager window 100 correspond to the child files. In the case of using the batch data set setting in file selection setting area 101, the analysis data files included in the previously set batch file correspond to the child files.

[0074] With the parent-child file link information prepared in this manner, a plurality of analysis data files corresponding to a final result record report file can be quickly located when the latter file is specified. The parent-child file link information can be visually checked as needed on the screen of the display unit 6 of the client terminal 4, for example, in a manner as shown in FIG. 8.

[0075] [Execution of Signature of Approval, etc.]

[0076] The final result record report created in the previously described manner corresponds to the integrated file in the present invention. The report contains information for judging whether or not the data and data-analyzing process results in the analysis data files included in one lot are valid. A supervisor having a high level of administrative authority checks this final result record report to evaluate the validity of the analysis of the entire lot, and gives his/her signature. The procedure and processing operation for the signature are hereinafter described with reference to FIG. 7.

[0077] The supervisor performs a predetermined operation with the operation unit 5 of the client terminal 4, whereupon the signature-receiving processor 46 begins to operate and displays a final result record report file selection window on the display unit 6. For example, similar to the data manager window 100 shown in FIG. 4, the final result record report file selection window may preferably be configured to allow users to set appropriate narrowing conditions so as to extract only such files that satisfy the narrowing conditions among the final result record report files registered in the database 14, and display the extracted tiles in the form of a list. The supervisor selects a final result record report tile to be checked from the list displayed on the display unit 6. The link information showing the relationship between the parent and child tiles as shown in FIG. 8 may also be displayed to help the supervisor select the correct final result record report file.

[0078] The signature-receiving processor 46 reads the selected final result record report file from the database 14 and displays, on the display unit 6, the final result record report based on the data contained in the tile. For example, a chromatogram and a peak table based on the analysis result for each sample as well as the sample information, audit trail and other related information can be viewed on this display unit 6. The supervisor evaluates the validity of the analysis result for each sample and other contents in the displayed final result record report. Then, the supervisor performs a predetermined operation with the operation unit 5 to select a reason for the signature indicative of the approval, rejection or other evaluations of the content of the report, and performs the signing operation.

[0079] Specifically, for example, the supervisor selects one of the options of the reason prepared in a dropdown list and performs the clicking operation on the Sign button, whereupon a confirmation window pops up, allowing the supervisor to complete the signature by performing the clicking operation on the OK button. Upon detecting the predetermined operation mentioned earlier, the signature-receiving processor 46 recognizes that the signing has been carried out.

[0080] When the signature has been executed, the signature-executing processor 47 obtains signature information, including the signer's name, date and time of the signature as well as reason for the signature, and records the signature information, associating this information with the currently displayed final result record report file, i.e. the parent file. The signer's name is the name registered for the user ID with which the supervisor has logged in. The date and time of the signature is the information of the date and time at which the signing was carried out. The reason for the signature is the reason selected by the supervisor. The recording of the signature information can be performed, for example, by adding the signature information to the final result record report file and newly registering this file in the database 14 as a signed final result record report file. Another possibility is to write the signature information in a signature information file associated with the final result record report file, and register that file in the database 14.

[0081] Using the parent-child file link information, the signature-executing processor 47 locates a plurality of analysis data files corresponding to the final result record report file, i.e. the analysis data files from which the information contained the report file was extracted (or analysis report files or final result record report files which respectively correspond to the individual analysis data files), and records the same signature information as used for the final result record report file, associating this information with each of those analysis data files. The recording of the signature information can be achieved in the same manner as in the case of the final result record report file. Thus, the same signature information will be assuredly recorded in the final result record report file, which is the parent file, and in the analysis data files, which are the child files.

[0082] Additionally, a file containing signature information for a plurality of lots may be created, for example, in PDF format and registered in the database 14. This facilitates the task of checking the signature which indicates, for example, whether or not the final result record report for a certain lot has been approved.

[0083] Thus, with the analysis information management system according to the present embodiment, it is unnecessary to check the content of each of the analysis data files managed in lot units and sign each individual file. The signer can give his/her signature to the files after collectively checking and evaluating their contents.

[0084] It should be noted that the previous embodiment is a mere example of the present invention, and any modification, addition or change appropriately made within the spirit of the present invention will evidently fall within the scope of claims of the present application.

REFERENCE SIGNS LIST

[0085] 1 . . . Database Server [0086] 11 . . . Analysis Data. Collector [0087] 12 . . . Log Information Collector [0088] 13 . . . Database Manager [0089] 14 . . . Database [0090] 2 . . . Analytical Instrument [0091] 3 . . . Communication Network [0092] 4 . . . Client Terminal [0093] 41 . . . Data Analysis Processor [0094] 42 . . . Analysis Report Creator [0095] 43 . . . Audit Trail Report Creator [0096] 44 . . . Data List Creator [0097] 45 . . . Final Result Record Report Creator [0098] 46 . . . Signature-Receiving Processor [0099] 47 . . . Signature-Executing Processor [0100] 5 . . . Operation Unit [0101] 6 . . . Display Unit [0102] 7 . . . Printing Unit