Automatic management and control method for sample container and experimental task

Abstract

The invention provides an automatic management and control method for sample containers and test tasks, and the method comprises the following steps: S1, a client sends a to-be-tested task list to a control end, and the to-be-tested task list comprises a target sample container and a paired target test task; s2, the control end reads the task pool and judges whether the to-be-tested task list exists in the task pool or not, if yes, the control end outputs feedback information to the client side, and if not, the control end adds the to-be-tested task list composed of the target sample container and the target test task in the task pool; and S3, the control end sequentially executes the sample test tasks according to the priorities of the sample containers in the task pool and the paired test tasks. According to the invention, the automatic matching and binding function of the sample container and the test task can be realized, and the flexible scheduling of target test tasks with different priorities can be satisfied.

Description

Technical Field

[0001] The present invention belongs to the technical field of laboratory sample test management, and particularly relates to an automatic control method for sample containers and test tasks. Background Art

[0002] In modern laboratories, sample test tasks are usually entered and generated by a laboratory information management system (LIMS). In the pre - sequence time of sample test operations, after obtaining samples, operators need to manually pair and bind sample containers with corresponding test tasks in the laboratory information management system, and then place these samples on the production line to complete subsequent automated detection processes.

[0003] In the prior art, the allocation operation of sample containers and test tasks mainly relies on manual operation. When the sample quantity is large, operators need to spend a lot of time on manual pairing and binding of sample containers and test tasks, which greatly increases the work burden and affects the sample test efficiency. At the same time, due to the possibility of human operation negligence, especially when facing a large number of samples, it is easy to have the situation of incorrect binding between sample containers and test tasks, resulting in problems in subsequent detection processes. And once an error occurs, due to the lack of effective data tracking means for manual binding, it is very difficult to quickly locate the problem, increasing the time cost of problem - solving. Summary of the Invention

[0004] The present invention aims to provide an automatic control method for sample containers and test tasks to solve the technical problems that in the prior art, the pairing and binding of sample containers and test tasks are carried out manually, with low operation efficiency and easy occurrence of binding errors.

[0005] To solve the above problems, the technical solution of the present invention is: an automatic control method for sample containers and test tasks, including the following steps: S1: The client sends a list of test tasks to be performed to the control end, and the list of test tasks to be performed includes target sample containers and paired target test tasks; S2: The control end reads the task pool, determines whether the list of test tasks to be performed already exists in the task pool. If it exists, the control end outputs feedback information to the client. If it does not exist, the control end adds the list of test tasks to be performed composed of the target sample containers and the target test tasks to the task pool; S3: The control end sequentially executes sample test tasks according to the priorities of various sample containers and paired test tasks in the task pool.

[0006] Preferably, when the client sends a list of test tasks to be performed to the control end in S1, it further includes the following steps: S11: a plurality of sample containers to be used are stored in the control terminal, and the type codes of the sample containers to be used are pre-entered in the control terminal; S12: After the control end obtains the type data of the target sample container, the type of the target sample container is compared with the types of several sample containers to be used. If the type of the target sample container exists in the sample containers to be used, step S2 is executed; if the type of the target sample container does not exist in the sample containers to be used, step S2 is terminated.

[0007] Preferably, the test tasks include high-priority test tasks and low-priority test tasks.

[0008] Preferably, in S2, the control end determines whether the task list to be tested already exists in the task pool, further comprising the following steps: S21: When the target test task is marked as a high priority test task, if the list of tasks to be tested already exists in several test task lists in the task pool, the control end enables the execution order of the list of tasks to be tested in the task pool to be increased according to the priority order, and outputs the first feedback information to the client.

[0009] Preferably, in S2, the control end determines whether the task list to be tested already exists in the task pool, further comprising the following steps: S22: When the target test task is marked as a high-priority test task, if the list of tasks to be tested does not exist in several test task lists in the task pool, the control end selects a group of target stand-by sample containers of the same type as the target sample container, pairs the target test task with the target stand-by sample containers, and then updates the newly created test task list consisting of the target test task and the target stand-by sample containers to the task pool, and the control end enables the execution order of the newly created test task list in the task pool to be increased according to the priority order, and outputs second feedback information to the client.

[0010] Preferably, in S22, the control end determines whether the task list to be tested already exists in the task pool, further comprising the following steps: S23: When a group of target standby sample containers of the same type as the target sample container are selected for the control terminal and the number of the target standby sample containers is unique, if a group of low-priority test tasks in the task pool have paired and occupied the target standby sample containers, the control terminal enables the target standby sample containers to be preferentially paired with the target test task to form the new experiment task list and outputs third feedback information to the client; if a group of high-priority test tasks in the task pool have paired and occupied the target standby sample containers, the control terminal terminates the pairing of the target test task and the target standby sample containers and outputs fourth feedback information to the client.

[0011] Preferably, when the control terminal in S2 determines whether the to-be-tested task list already exists in the task pool, it further includes the following steps: S24: When the target test task is marked as a low-priority test task, if the to-be-tested task list already exists in several test task lists in the task pool, the control terminal only outputs fifth feedback information to the client.

[0012] Preferably, when the control terminal in S2 determines whether the to-be-tested task list already exists in the task pool, it further includes the following steps: S25: When the target test task is marked as a low-priority test task, if the to-be-tested task list does not exist in several test task lists in the task pool, the control terminal selects a group of target standby sample containers of the same type as the target sample container. After pairing the target test task with the target standby sample containers, the control terminal updates the new test task list formed by the target test task and the target standby sample containers to the task pool and outputs sixth feedback information to the client.

[0013] Preferably, when the control terminal in S25 determines whether the to-be-tested task list already exists in the task pool, it further includes the following steps: S26: When a group of target standby sample containers of the same type as the target sample container are selected for the control terminal and the number of the target standby sample containers is unique, if the target standby sample containers have been paired and occupied by a group of low-priority test tasks or high-priority experiment tasks in the task pool, the control terminal terminates the pairing of the target test task and the target standby sample containers and outputs seventh feedback information to the client.

[0014] Preferably, in the task pool, several test task lists with the same priority are sorted in the execution order according to the time sequence of entering the task pool.

[0015] Due to the adoption of the above technical solutions, the present invention has the following advantages and positive effects compared with the prior art: The present invention provides an automated control method for sample containers and test tasks. After the operator inputs the list of test tasks to be performed through the client, the control terminal automatically accesses and queries the existing list of test tasks in the task pool. If the list of test tasks to be performed does not exist in the task pool, the control terminal automatically selects the required sample containers and pairs them with the test tasks to form the required list of test tasks and updates it to the task pool, realizing the automatic pairing and binding function of sample containers and test tasks, meeting the efficient allocation of sample containers and test tasks and the rational utilization of resources. At the same time, the control terminal can also automatically adjust the formation method of the test task list and its execution sequence in the task pool according to the priority of the target test task in the list of test tasks to be performed, flexibly accelerating the disposal speed of urgent tasks. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 A flowchart of an automated control method for sample containers and test tasks provided by the present invention; Figure 2 A schematic structural diagram of the client and the control terminal provided by the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0017] The following further describes in detail an automated control method for sample containers and test tasks proposed by the present invention with reference to the accompanying drawings and specific embodiments. The advantages and features of the present invention will be clearer according to the following description and the claims.

[0018] Refer to Figures 1 to 2 , this embodiment provides an automated control method for sample containers and test tasks, which is used to realize the automated pairing and binding function of sample containers and test tasks in the laboratory intelligent control system.

[0019] In this embodiment, the automated control method for sample containers and test tasks includes the following steps: S1: The operator sends a list of test tasks to be performed to the control terminal through the client. The list of test tasks to be performed includes two sets of data, namely the target sample container and the target test task, and the target sample container and the target test task are in a corresponding pairing relationship, that is, during the subsequent sample test process, the test operation of the target test task is performed on the sample in a single target sample container.

[0020] S2: After receiving the list of tasks to be tested, the control terminal obtains two sets of paired data of the target sample container and the target test task, and then reads the test task list already existing in the task pool. If there is a set of test task lists in the task pool, and the sample container type and test task content recorded therein are completely consistent with the sample container type and test task content recorded in the task list to be tested, it proves that the task list to be tested has been entered into the task pool in advance and will not be repeated. If there is no set of test task lists in the task pool, and the sample container type and test task content recorded therein are completely consistent with the sample container type and test task content recorded in the task list to be tested, it proves that the task list to be tested is a new set of sample test tasks, so the control terminal will add the task list to be tested consisting of the target sample container and the target test task in the task pool. It can be seen from this that in this embodiment, the operator sends the task list to be tested to the control terminal through the client, which can include the function of querying the existing test task list in the task pool, and can also include the function of creating a new set of test task lists in the task pool.

[0021] S3: The control end executes the sample test tasks in sequence according to the priorities of the sample containers and paired test tasks in the task pool.

[0022] The specific steps of the method for automated control of sample containers and test tasks provided in this embodiment are described in further detail below: Preferably, in this embodiment, in S1, the client sends a list of tasks to be tested to the control end, further comprising the following steps: S11: A number of sample containers to be used are stored in the control terminal, and coding information corresponding to the sample container type is pasted on the surface of the sample container. The control terminal can enter the type code of the sample container to be used in advance. It is worth noting that the sample containers to be used include two types, one is the one that has completed the pairing operation with the test task, that is, it exists in the task pool but has not yet been subjected to the subsequent sample test operation, and the other is the one that has not yet been paired with the test task.

[0023] S12: After the client sends the list of tasks to be tested to the control end, the control end obtains the type data of the target sample container, and compares the type of the target sample container with the types of several sample containers to be used. If there is a type consistent with the target sample container among the sample containers to be used, the subsequent S2 step can be executed. If there is no type consistent with the target sample container among the sample containers to be used, it is proved that the sample test task corresponding to the target sample container cannot be achieved, and the subsequent S2 step is terminated. The control end can feedback to the client the information that the target sample container type is temporarily missing in the current control end, and remind the operator to promptly add sample containers of the relevant type to the control end, or replace the content of the list of tasks to be tested.

[0024] Preferably, in this embodiment, the test tasks include high-priority test tasks and low-priority test tasks. It should be noted that the priority can be marked only in the target test tasks sent by the client to the control end. Therefore, when the test task list to be tested already exists in the task pool, the original test task list in the task pool that is consistent with the test task list to be tested is automatically adjusted in priority. When the test task list to be tested does not exist in the task pool, the newly created test task list based on the test task list to be tested in the task pool also automatically has a priority mark.

[0025] Specifically, in this embodiment, in S2, the control end determines whether the test task list to be tested already exists in the task pool, which further includes the following steps: S21: When the target test task is marked as a high-priority test task, if the test task list to be tested already exists in several test task lists in the task pool, the control end enables the original test task list that is consistent with the test task list to be tested, and the execution order in the task pool is adjusted upward according to the priority order, and the first feedback information is output to the client. The first feedback information includes indicating that there is already a test task list in the task pool that is consistent with the test task list to be tested, and the specific execution order position of the original test task list that is consistent with the test task list to be tested after adjustment in the task pool.

[0026] Further, in this embodiment, in S2, the control end determines whether the test task list to be tested already exists in the task pool, and further includes the following steps: S22: When the target test task is marked as a high-priority test task, if the test task list to be tested does not exist in several test task lists in the task pool, the control end selects a group of target standby sample containers of the same type as the target sample container from several standby sample containers, pairs and binds the target standby sample containers with the target test task, and updates the newly created test task list composed of the target standby sample containers and the target test task to the task pool. At the same time, the control end enables the execution order of the newly created test task list in the task pool to be adjusted upward according to the priority order of the target test task. Finally, the control end outputs the second feedback information to the client. The second feedback information includes indicating that a newly created test task list that is consistent with the test task list to be tested has been established in the task pool, and the specific execution order position of the newly created test task list in the task pool.

[0027] Furthermore, in this embodiment, in S22, the control end determines whether the test task list to be tested already exists in the task pool, and further includes the following steps: S23: When a set of target standby sample containers of the same type as the target sample container are selected for the control end, but the number of target standby sample containers is unique, that is, when there is only one target standby sample container corresponding to the target sample container type among several standby sample containers, if the target standby sample container has been paired and occupied by a set of low-priority test tasks in the task pool at this time, the control end enables the target standby sample container to be preferentially paired and bound with the target test task to form a new experimental task list. Finally, the control end outputs the third feedback information to the client. The third feedback information includes indicating that a new test task list consistent with the list of tasks to be tested has been established in the task pool, and that there is a set of low-priority test tasks paired and unlocked with the target standby sample container, and relevant types of sample containers need to be supplemented to the control end.

[0028] It should be noted that at this time, a set of low-priority test tasks paired and unlocked with the target standby sample container are in a pending state. When the target standby sample container is supplemented to the control end subsequently, this set of low-priority test tasks are preferably paired and bound with the target standby sample container and updated to the task pool again.

[0029] If the target standby sample container has been paired and occupied by a set of high-priority test tasks in the task pool at this time, the control end terminates the pairing and binding operation of the target test task and the target standby sample container. At the same time, the control end outputs the fourth feedback information to the client. The fourth feedback information includes indicating that the pairing and binding of the target standby sample container and the target test task fails, and the reason is that there are not enough target standby sample containers in the control end, and relevant types of sample containers need to be supplemented to the control end, or the content of the list of tasks to be tested needs to be replaced.

[0030] Furthermore, in this embodiment, when the control end in S2 determines whether the list of tasks to be tested already exists in the task pool, it includes the following steps: S24: When the target test task is marked as a low-priority test task, if the list of tasks to be tested already exists in several test task lists in the task pool, the control end only needs to output the fifth feedback information to the client. The fifth feedback information includes indicating that there is already a test task list consistent with the list of tasks to be tested in the task pool.

[0031] Furthermore, in this embodiment, when the control end in S2 determines whether the list of tasks to be tested already exists in the task pool, it includes the following steps: S25: When the target test task is marked as a low-priority test task, if the to-be-tested task list does not exist in several test task lists in the task pool, the control terminal selects a group of target standby sample containers of the same type as the target sample container from several standby sample containers, pairs and binds the target standby sample containers with the target test task, updates the new test task list composed of the target standby sample containers and the target test task to the task pool, and finally the control terminal outputs the sixth feedback information to the client. The sixth feedback information includes indicating that a new test task list consistent with the to-be-tested task list has been established in the task pool.

[0032] Furthermore, in this embodiment, when the control terminal determines whether the to-be-tested task list exists in the task pool in S25, the following steps are further included: S26: When the control terminal selects a group of target standby sample containers of the same type as the target sample container, but the number of target standby sample containers is unique, that is, when there is only one target standby sample container corresponding to the target sample container type in several standby sample containers, if the target standby sample container has been paired and occupied by a group of low-priority test tasks or high-priority test tasks in the task pool at this time, the control terminal terminates the pairing and binding operation of the target test task and the target standby sample container. At the same time, the control terminal outputs the seventh feedback information to the client. The seventh feedback information includes indicating that the pairing and binding of the target standby sample container and the target test task fails, and the reason is that there are not enough target standby sample containers in the control terminal, and relevant types of sample containers need to be supplemented to the control terminal, or the content of the to-be-tested task list needs to be replaced.

[0033] Preferably, in this embodiment, in the task pool, several test task lists with the same priority are sorted according to the time order of entering the task pool. That is, if there are high-priority test tasks set in multiple groups of test task lists, the order of executing the sample test tasks of multiple groups of test task lists is determined according to the time order of their entering the task pool, that is, the principle of first in, first out is adopted for the sample test tasks.

[0034] In summary, this embodiment provides an automated control method for sample containers and test tasks. Based on the inventory of the test task list in the task pool, the control end automatically compares whether the to-be-tested task list input by the client has been constructed in the task pool. If it has not been constructed, the control end can automatically implement the pairing and binding function of the target sample container and the target test task, form the required to-be-tested task list in the task pool, effectively improve the sample test efficiency, and the pairing and binding log of the target sample container and the target test task is clearly recorded and queryable. At the same time, for the target test task, there are classifications of high priority and low priority. The control end can dynamically adjust the pairing and binding operation of the target sample container and the target test task based on the priority setting, ensure that high-priority test tasks are preferentially allocated and executed, and fully ensure the efficient allocation of sample containers and test tasks and the rational utilization of resources.

[0035] The embodiments of the present invention have been described in detail above in conjunction with the accompanying drawings, but the present invention is not limited to the above embodiments. Even if various changes are made to the present invention, if these changes fall within the scope of the claims of the present invention and its equivalent technologies, they still fall within the protection scope of the present invention.

Claims

1. A method for automated control of sample containers and test tasks, characterized in that: The steps include: S1: The client sends a list of tasks to be tested to the control end, wherein the list of tasks to be tested includes target sample containers and paired target test tasks; S2: The control end reads the task pool to determine whether the task list to be tested already exists in the task pool. If so, the control end outputs feedback information to the client. If not, the control end adds the task list to be tested consisting of the target sample container and the target test task to the task pool. S3: The control end executes the sample test tasks in sequence according to the priorities of the sample containers and paired test tasks in the task pool.

2. The method for automated control of sample containers and test tasks according to claim 1, characterized in that: In S1, the client sends a list of tasks to be tested to the control end, which further includes the following steps: S11: a plurality of sample containers to be used are stored in the control terminal, and the type codes of the sample containers to be used are pre-entered in the control terminal; S12: After the control end obtains the type data of the target sample container, the type of the target sample container is compared with the types of several sample containers to be used. If the type of the target sample container exists in the sample containers to be used, step S2 is executed; if the type of the target sample container does not exist in the sample containers to be used, step S2 is terminated.

3. The method for automated control of sample containers and test tasks according to claim 2, characterized in that: The test tasks include high priority test tasks and low priority test tasks.

4. The method for automated control of sample containers and test tasks according to claim 3, characterized in that: In S2, the control end determines whether the task list to be tested already exists in the task pool, further comprising the following steps: S21: When the target test task is marked as a high priority test task, if the list of tasks to be tested already exists in several test task lists in the task pool, the control end enables the execution order of the list of tasks to be tested in the task pool to be increased according to the priority order, and outputs the first feedback information to the client.

5. The method for automated control of sample containers and test tasks according to claim 3, characterized in that: In S2, the control end determines whether the task list to be tested already exists in the task pool, further comprising the following steps: S22: When the target test task is marked as a high-priority test task, if the list of tasks to be tested does not exist in several test task lists in the task pool, the control end selects a group of target stand-by sample containers of the same type as the target sample container, pairs the target test task with the target stand-by sample containers, and then updates the newly created test task list consisting of the target test task and the target stand-by sample containers to the task pool, and the control end enables the execution order of the newly created test task list in the task pool to be increased according to the priority order, and outputs second feedback information to the client.

6. The method for automated control of sample containers and test tasks according to claim 5, characterized in that: In S22, the control end determines whether the task list to be tested already exists in the task pool, further comprising the following steps: S23: When the control end selects a group of target stand-by sample containers of the same type as the target sample containers, and the number of the target stand-by sample containers is unique, if the target stand-by sample containers have been paired and occupied by a group of low-priority test tasks in the task pool, the control end enables the target stand-by sample containers to be paired with the target test tasks first to form the newly created experimental task list, and outputs third feedback information to the client; if the target stand-by sample containers have been paired and occupied by a group of high-priority test tasks in the task pool, the control end terminates the pairing of the target test tasks with the target stand-by sample containers, and outputs fourth feedback information to the client.

7. The method for automated control of sample containers and test tasks according to claim 3, characterized in that: In S2, the control end determines whether the task list to be tested already exists in the task pool, further comprising the following steps: S24: When the target test task is marked as a low-priority test task, if the to-be-tested task list already exists in several test task lists in the task pool, the control end only outputs fifth feedback information to the client.

8. The method for automated control of sample containers and test tasks according to claim 3, characterized in that: In S2, the control end determines whether the task list to be tested already exists in the task pool, further comprising the following steps: S25: When the target test task is marked as a low priority test task, if the list of tasks to be tested does not exist in several test task lists in the task pool, the control end selects a group of target stand-by sample containers of the same type as the target sample container, pairs the target test task with the target stand-by sample container, updates the newly created test task list consisting of the target test task and the target stand-by sample container to the task pool, and outputs the sixth feedback information to the client.

9. The method for automated control of sample containers and test tasks according to claim 8, characterized in that: In S25, the control end determines whether the task list to be tested already exists in the task pool, further comprising the following steps: S26: When the control end selects a group of target stand-by sample containers of the same type as the target sample containers, and the number of the target stand-by sample containers is unique, if the target stand-by sample containers have been occupied by a group of low-priority test tasks or high-priority test tasks in the task pool, the control end terminates the pairing of the target test tasks with the target stand-by sample containers, and outputs the seventh feedback information to the client.

10. The method for automated control of sample containers and test tasks according to claim 1, characterized in that: In the task pool, several test task lists of the same priority are sorted in execution order according to the time sequence of entering the task pool.

Images