A blockchain-based LIMS report management method, device and medium

Abstract

The application discloses a blockchain-based LIMS report management method, device and medium, relates to the technical field of computers, and comprises the following steps: obtaining management report data of a laboratory, and performing chain hash calculation on the management report data to obtain a report hash value; taking the report hash value as a chain request, and determining a consensus report based on the chain request through PBFT consensus; performing audit signature processing on the consensus report to obtain a consensus report associated with a node digital signature; determining a Merkle root hash written into a blockchain through Merkle tree construction according to the consensus report associated with the node digital signature; and performing chain collaborative traceability analysis on the management report data to obtain a mapping relationship between the consensus report and content addressing hash. The application solves the technical problems of data credibility and cross-institution trust in the report management of the existing LIMS system through the above method.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computers, and in particular to a LIMS report management method and device based on a blockchain and a medium. BACKGROUND

[0002] At present, the traditional laboratory information management system (LIMS) is facing inherent technical bottlenecks in the management of report data, and the core problem lies in the dependence on a centralized database architecture and a weak trust mechanism. First, in terms of data security, report data is stored centrally on a central server, and system administrators or internal personnel with high-level permissions can easily tamper with or delete key records, and such operations are difficult to be effectively traced and evidenced. Secondly, in the cross-agency collaboration scenario, it must go through a tedious and high-cost third-party repeated verification, which seriously hinders the collaborative efficiency, which is particularly prominent in the fields of environmental monitoring and food safety testing.

[0003] Due to the serious lack of existing data traceability, the modification records of data are usually stored in the form of scattered and isolated logs, making it difficult to accurately locate the responsible person, time and reason of data change in compliance review, resulting in compliance risks, and the existing consensus algorithm has problems such as large communication overhead and rigid view switching, which is difficult to adapt to the specific scene of high-frequency generation of laboratory reports, low-delay consensus and strong compliance requirements. SUMMARY

[0004] The embodiments of the present application provide a LIMS report management method and device based on a blockchain and a medium, which solves the technical problems of data credibility and cross-agency trust existing in the report management of the existing LIMS system.

[0005] In a first aspect, the embodiments of the present application provide a LIMS report management method based on a blockchain, characterized in that the method comprises: obtaining management report data of a laboratory, and performing chain hash calculation on the management report data to obtain a report hash value; taking the report hash value as a chain request, and determining a consensus report based on the chain request through PBFT consensus; performing audit signature processing on the consensus report to obtain a consensus report associated with an audit node digital signature; determining a Merkle root hash written into a blockchain through Merkle tree construction according to the consensus report associated with the audit node digital signature; and performing chain collaborative traceability analysis on the management report data to obtain a mapping relationship between the consensus report and a content addressing hash.

[0006] In an implementation manner of the present application, the management report data is subjected to chain hash calculation to obtain a report hash value, specifically including: performing original data binding on the management report data to obtain an original data hash; performing metadata fusion on the original data hash to obtain a metadata fusion hash; performing structured report binding on the metadata fusion hash and generating a node digital signature to obtain the report hash value.

[0007] In an implementation manner of the present application, the original data hash is subjected to metadata fusion to obtain a metadata fusion hash, specifically including: obtaining laboratory key parameters and binding the laboratory key parameters with the original data hash to obtain a fusion hash; wherein the laboratory key parameters include: instrument number, operator, timestamp, and environmental parameters; and the fusion hash is subjected to random number configuration to obtain a data fusion hash.

[0008] In an implementation manner of the present application, based on a chain request, a consensus report is determined through PBFT consensus, specifically including: submitting the chain request to a consortium chain network and performing batch processing optimization on the report hash value based on the consortium chain network to obtain a report request package; performing formula state monitoring on the report request package to determine a dynamic view of master node switching; and determining the consensus report according to the dynamic view through node public key lightweight verification.

[0009] In an implementation manner of the present application, the consensus report is subjected to audit signature processing to obtain a consensus report associated with an audit node digital signature, specifically including: performing smart contract analysis on the consensus report according to a report type to determine an audit process; wherein the audit process is a multi-level audit process; obtaining private keys of auditors at each level based on the audit process and performing digital signature on the consensus report through the private keys to obtain the consensus report associated with the audit node digital signature.

[0010] In an implementation manner of the present application, according to the consensus report associated with the audit node digital signature, a Merkle root hash written into a blockchain is determined through Merkle tree construction, specifically including: obtaining Merkle tree leaf nodes through rehashing of key elements based on the consensus report associated with the audit node digital signature; determining intermediate nodes through hash updating of adjacent node splicing according to the Merkle tree leaf nodes; and in the case that a unique root hash is generated at the intermediate nodes, determining the Merkle root hash written into the blockchain through batch information binding.

[0011] In an implementation form of the present application, the chain collaborative traceability analysis is performed on the management report data to obtain the mapping relationship between the consensus report and the content addressing hash, specifically including: performing original file fragmentation on the management report data, and storing the file data obtained by the original file fragmentation in a distributed file to obtain the content addressing hash; performing information correlation matching on the content addressing hash to obtain the mapping relationship between the consensus report and the content addressing hash.

[0012] In an implementation form of the present application, after the chain collaborative traceability analysis is performed on the management report data to obtain the mapping relationship between the consensus report and the content addressing hash, the method further includes: based on the mapping relationship between the consensus report and the content addressing hash, obtaining the supervision traceability information through the blockchain verification.

[0013] In a second aspect, the embodiments of the present application further provide a LIMS report management device based on a blockchain, characterized in that the device comprises: at least one processor; and a memory in communication connection with the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to: obtain management report data of a laboratory, and perform chain hash calculation on the management report data to obtain a report hash value; take the report hash value as a chain request, and determine a consensus report through PBFT consensus based on the chain request; perform audit signature processing on the consensus report to obtain a consensus report associated with an audit node digital signature; determine a Merkle root hash written into a blockchain through Merkle tree construction according to the consensus report associated with the audit node digital signature; and perform chain collaborative traceability analysis on the management report data to obtain a mapping relationship between the consensus report and a content addressing hash.

[0014] In a third aspect, the embodiments of the present application further provide a non-volatile computer storage medium for LIMS report management based on a blockchain, which stores computer executable instructions, characterized in that the computer executable instructions are configured to: obtain management report data of a laboratory, and perform chain hash calculation on the management report data to obtain a report hash value; take the report hash value as a chain request, and determine a consensus report through PBFT consensus based on the chain request; perform audit signature processing on the consensus report to obtain a consensus report associated with an audit node digital signature; determine a Merkle root hash written into a blockchain through Merkle tree construction according to the consensus report associated with the audit node digital signature; and perform chain collaborative traceability analysis on the management report data to obtain a mapping relationship between the consensus report and a content addressing hash.

[0015] The embodiment of the present application provides a kind of based on the LIMS report management method, equipment and medium of blockchain, through chain Hash calculation, PBFT consensus and the chain coordination traceability analysis of Merkle tree construction, the data credibility and cross-institutional trust technical problems existing in the report management of existing LIMS system are solved, the security, reliability and report management process efficiency of laboratory report management are improved. BRIEF DESCRIPTION OF DRAWINGS

[0016] The drawings described herein are used to provide further understanding of the present application, and form part of the present application, the illustrative embodiments of the present application and its description are used to explain the present application, and do not constitute undue limitation on the present application.In the drawings:

[0017] Figure 1 A kind of based on the LIMS report management method flow chart provided for the embodiment of the present application based on blockchain;

[0018] Figure 2 The internal structure schematic diagram of a kind of based on the LIMS report management equipment provided for the embodiment of the present application based on blockchain. DETAILED DESCRIPTION

[0019] To make the purpose, technical scheme and advantage of the present application more clear, the technical scheme of the present application will be described clearly and completely with the specific embodiment of the present application and corresponding drawings below.It is obvious that the described embodiment is only a part of the present application, not all the embodiments.Based on the embodiment in the present application, all other embodiments obtained by those skilled in the art without making creative labor are within the scope of protection of the present application.

[0020] The embodiment of the present application provides a kind of based on the LIMS report management method, equipment and medium of blockchain, through chain Hash calculation, PBFT consensus and the chain coordination traceability analysis of Merkle tree construction, the data credibility and cross-institutional trust technical problems existing in the report management of existing LIMS system are solved, the security, reliability and report management process efficiency of laboratory report management are improved.

[0021] The technical scheme of the embodiment of the present application will be described in detail below with the drawings.

[0022] Figure 1 A kind of based on the LIMS report management method flow chart provided for the embodiment of the present application based on blockchain.As shown in Figure 1 The LIMS report management method based on blockchain provided by the embodiment of the present application specifically includes the following steps:

[0023] Step 101, obtain the management report data of the laboratory, and perform chain hash calculation on the management report data to obtain a report hash value.

[0024] Specifically, the chain hash calculation on the management report data to obtain the report hash value includes: performing raw data binding on the management report data to obtain a raw data hash; performing metadata fusion on the raw data hash to obtain a metadata fusion hash; performing structured report binding on the metadata fusion hash and generating a node digital signature to obtain the report hash value.

[0025] Specifically, the metadata fusion on the raw data hash to obtain the metadata fusion hash includes: obtaining laboratory key parameters and binding the laboratory key parameters with the raw data hash to obtain a fusion hash; wherein the laboratory key parameters include: instrument number, operator, timestamp, environmental parameters; and performing random number configuration on the fusion hash to obtain a data fusion hash.

[0026] In one embodiment, raw data is collected from laboratory instruments, static metadata and dynamic metadata are fused, and a final hash value of a report is generated through chain hash calculation.

[0027] The raw data and its format identifier are hashed to obtain a first-level hash (H1), the first-level hash (H1), static metadata, dynamic metadata, and an anti-replay random number are hashed to obtain a second-level hash (H2), and the second-level hash (H2) and the structured data of the report file are hashed to obtain a final hash value (H_final).

[0028] Raw data (such as peak value, retention time, concentration value, etc.) collected from instruments such as chromatographs and mass spectrometers through OPCUA protocol, wherein, : raw data (binary stream) output by the instrument, such as the "time-intensity" array [(t1, i1), (t2, i2),..., (tn, in)] of the chromatograph; : data format identifier (such as "CSV_v1.0" "JSON_v2.1"), which solves the hash conflict caused by the difference in data format of different instruments; : instrument built-in check code (partially included in high-end instruments, such as "data integrity check value" of Agilent chromatograph), which enhances the credibility of the raw data.

[0029] The second-level hash (H2) is obtained by first-level hash + dynamic metadata (including instrument state, environmental parameters, operator information, etc.), ; wherein, is static metadata (fixed and unchanged), including:

[0030] Instrument number (e.g. "MS-2023-005");

[0031] Operator digital certificate public key (blockchain address, e.g. "0x5F3a...");

[0032] Business system association number (e.g. "Detection task-T20251010-001");

[0033] Dynamic metadata (real-time changes), including:

[0034] Data collection timestamp (precise to milliseconds, e.g. "20251010143025.123");

[0035] Laboratory environment parameters (temperature, humidity, e.g. "25.5℃|50%RH");

[0036] Instrument running status code (e.g. "normal=0|calibrating=1");

[0037] : Random number (32-bit integer, e.g. "1048576"), generated by the system in real time, to prevent replay attacks (the same data + metadata will be different due to the random number, must be different).

[0038] Final hash value , second-level hash + structured data of standardized report file (PDF / XML). Among them, is the structured extraction value of the report file, which guarantees the integrity of the file and avoids the influence of file format differences on the hash. Specifically, it includes: key detection results (e.g. "lead content=0.01mg / kg"); report title, version number, is the digital signature of the report generation node (signed by the node private key , e.g. "0x3d4f..."), proving the legitimacy of the generation node identity.

[0039] Step 102, the report hash value is used as a chain request, and based on the chain request, the consensus report is determined through PBFT consensus.

[0040] For example, the PBFT algorithm realizes Byzantine fault tolerance through a three-stage protocol of pre-preparation-preparation-commitment. Through PBFT consensus, the application determines the consensus report, realizes the definition of view and message, and processes data after the triggering of the consensus phase.

[0041] Specifically, based on the upper chain request, the consensus report is determined through PBFT consensus, including: submitting the upper chain request to the alliance chain network, and based on the alliance chain network, the report hash value is optimized in batches to obtain a report request package; formula state monitoring is performed on the report request package to determine the dynamic view of the master node switching; and the consensus report is determined based on the dynamic view through node public key lightweight verification.

[0042] Consensus phase trigger condition, pre-preparation phase, master node (p= mod ) calculation determination) receiving client request , generating a pre-preparation message , and broadcasting to all nodes. The preparation phase generates a preparation message after verifying the legality of the pre-preparation message (signature, view number, sequence number is valid) from the node , broadcast to other nodes. When the node receives matching preparation messages (including itself), it enters the preparation state ( is the maximum fault-tolerant node number, ).

[0043] The submission phase generates a submission message by the node in the preparation state, broadcast to other nodes. When receiving matching submission messages (including itself), the request is executed and the result is returned to the client.

[0044] Step 103, auditing and signing the consensus completion report to obtain a consensus report associated with the audit node digital signature.

[0045] Specifically, the consensus completion report is audited and signed to obtain a consensus report associated with the audit node digital signature, including: performing report type smart contract analysis on the consensus completion report to determine the audit process; wherein the audit process is a multi-level audit process; based on the audit process, obtain the private key of each level of audit personnel, and perform digital signature on the consensus completion report through the private key of each level of audit personnel to obtain the consensus report associated with the audit node digital signature.

[0046] In one embodiment, the set of alliance chain nodes is , where is the total number of nodes, and in the system 4, corresponding to detection agencies, regulatory departments and other nodes), the view number is (integers, initial value is 0, and increases when the view is switched), and the client request is (such as report generation, audit triggering and other operations).

[0047] Node The generated message format is: ;

[0048] Wherein: is the message type, pre-preparation = 0, preparation = 1, submission = 2;

[0049] is the sequence number, uniquely identifying the order of the request within the view, preventing replay attacks;

[0050] is the digital signature of the node , using ECC elliptic curve encryption, private key signature and public key verification.

[0051] Step 104, according to the consensus report of the associated audit node digital signature, through the construction of Merkle tree, determine the Merkle root hash written into the blockchain.

[0052] Specifically, according to the consensus report of the associated audit node digital signature, through the construction of Merkle tree, determine the Merkle root hash written into the blockchain, including: based on the consensus report of the associated audit node digital signature, through the rehashing of the key elements, get the Merkle tree leaf node; According to the Merkle tree leaf node, through the hash update of the adjacent node splicing, determine the intermediate node; In the case of generating a unique root hash in the intermediate node, through the binding of batch information, determine the Merkle root hash written into the blockchain.

[0053] In one embodiment, a laboratory generates 3 heavy metal detection reports (numbered R01, R02, R03) within 1 hour, needs to construct Merkle tree and chain the root hash, the specific steps are as follows:

[0054] First, generate leaf nodes, from 3 reports to 4 leaf nodes, complete for odd number, as shown in Table 1.

[0055] Table 1 Relationship between leaf node and report number

[0056]

[0057] Then, calculate the intermediate node, intermediate node (calculated by L01, L02):

[0058] ;

[0059] Wherein, is .

[0060] Intermediate node (Computed by L03, L04):

[0061] ;

[0062] wherein, That is, 。

[0063] Then, the root node is calculated, and the above , is calculated:

[0064] .

[0065] The root node ( ) is associated with the "batch information" (batch number B001, generation time 202510101100), and is written into the block header of the current block of the blockchain, completing the construction and evidence storage of the Merkle tree

[0066] Step 105, chain collaborative traceability analysis is performed on the management report data to obtain a mapping relationship between the consensus report and the content addressing hash.

[0067] Specifically, the chain collaborative traceability analysis is performed on the management report data to obtain a mapping relationship between the consensus report and the content addressing hash, including: performing original file fragmentation on the management report data, and storing the file data obtained by the original file fragmentation in a distributed file to obtain a content addressing hash; performing information association matching on the content addressing hash to obtain a mapping relationship between the consensus report and the content addressing hash.

[0068] Further, after the chain collaborative traceability analysis is performed on the management report data to obtain a mapping relationship between the consensus report and the content addressing hash, the method further includes: based on the mapping relationship between the consensus report and the content addressing hash, obtaining supervision traceability information through blockchain verification.

[0069] In one embodiment, when the report needs to be modified due to audit opinion supplement, data correction, etc., the full hash does not need to be recalculated, and efficient updating is realized only through the "incremental hash chain": let the original report final hash be , and the modification content be (such as "audit opinion: agree to publish").

[0070] The incremental hash is calculated as: , wherein is the modification timestamp, is the modification person address; the new version final hash is: ; and the on-chain storage And By associating historical versions through a hash chain, the modified content and the modifier are supported to be traced back.

[0071] The report hash value (256 bits) is much smaller than general transaction data, so the message signature verification process is simplified: the node locally caches the public keys of all nodes of the alliance chain, and verifies When directly decrypting through the public key, the certificate chain verification step in the traditional PBFT is omitted, and the single message verification time is reduced from 0.8 ms to 0.3 ms, which improves the consensus efficiency.

[0072] The above is the method embodiment of the present application. Based on the same inventive concept, the present application also provides a blockchain-based LIMS report management device, the structure of which is shown in Figure 2 .

[0073] Figure 2 The present application provides a blockchain-based LIMS report management device internal structure diagram. As shown in Figure 2 , the device includes:

[0074] at least one processor 201;

[0075] and a memory 202 in communication connection with the at least one processor;

[0076] The memory 202 stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor 201 to enable the at least one processor 201 to:

[0077] Obtain the management report data of the laboratory, and perform chain hash calculation on the management report data to obtain the report hash value; take the report hash value as a chain request, and based on the chain request, determine a consensus report through PBFT consensus; perform audit signature processing on the consensus report to obtain a consensus report associated with the audit node digital signature; according to the consensus report associated with the audit node digital signature, through Merkle tree construction, determine the Merkle root hash written into the blockchain; perform chain collaborative traceability analysis on the management report data to obtain the mapping relationship between the consensus report and the content addressing hash.

[0078] Some embodiments of the present application provide a non-volatile computer storage medium for blockchain-based LIMS report management corresponding to Figure 1 , which stores computer executable instructions, and the computer executable instructions are set to:

[0079] Obtaining management report data of a laboratory, performing chain hash calculation on the management report data to obtain a report hash value, taking the report hash value as a chain request, and determining a consensus report through PBFT consensus based on the chain request; performing audit signature processing on the consensus report to obtain a consensus report associated with a node digital signature; determining a Merkle root hash written into a blockchain through Merkle tree construction based on the consensus report associated with the node digital signature; and performing chain collaborative traceability analysis on the management report data to obtain a mapping relationship between the consensus report and a content addressing hash.

[0080] Each of the embodiments in the present application is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other. Each of the embodiments mainly describes the difference from other embodiments. In particular, for the Internet of Things device and medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the part of the method embodiments.

[0081] The system and medium provided by the embodiments of the present application are one-to-one corresponding to the method, and therefore, the system and medium also have similar beneficial technical effects to the method. Since the beneficial technical effects of the method have been described in detail above, the beneficial technical effects of the system and medium will not be described here.

[0082] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0083] The present application is described with reference to flowcharts and / or block diagrams of the method, device (system), and computer program product according to the embodiments of the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and the combination of the flows and / or blocks in the flowcharts and / or block diagrams can be implemented by computer program instructions. These computer program instructions can be provided to a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to produce a machine, so that the instructions executed by the computer or other programmable data processing devices produce a device that implements the functions specified in the flowcharts and / or block diagrams. Figure 1 The device that implements the functions specified in one or more flows and / or blocks. Figure 1 The device that implements the functions specified in one or more flows and / or blocks.

[0084] These computer program instructions can also be stored in a computer- readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instructions which implement the Figure 1 function specified in the flow or flows and / or blocks Figure 1 of the block or blocks.

[0085] These computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the Figure 1 function specified in the flow or flows and / or blocks Figure 1 of the block or blocks.

[0086] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0087] The memory can include non-persistent memory and / or volatile memory, such as random access memory (RAM) about which the computer stores information about an operating system, application software, and / or the like. Memory is an example of computer readable media.

[0088] Computer readable media includes permanent and non-permanent, moveable and non- moveable media that can be implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile discs (DVDs) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that is accessible to a computing device. According to the definition provided herein, computer readable media excludes transitory media, such as modulated data signals and carrier waves.

[0089] It should also be noted that the terms "comprising", "comprises" or other variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but can also include other elements not expressly listed or inherent to such process, method, article, or apparatus.

[0090] The above embodiments are only used to illustrate the present application, but not to limit it. Instead of the above, various modifications and changes can be made to the application by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the application shall fall into the scope of the claims of the application.

Claims

1. A blockchain-based LIMS report management method, characterized by, The method comprises: obtaining management report data of a laboratory, and performing chain hash calculation on the management report data to obtain a report hash value; the report hash value is taken as a chain request, and based on the chain request, a consensus report is determined through PBFT consensus; the consensus report is subjected to audit signature processing to obtain a consensus report associated with a node digital signature; based on the consensus report associated with the node digital signature, a Merkle root hash written into a blockchain is determined through Merkle tree construction; chain collaborative traceability analysis is performed on the management report data to obtain a mapping relationship between the consensus report and a content addressing hash; chain hash calculation is performed on the management report data to obtain a report hash value, specifically including: the management report data is subjected to original data binding to obtain an original data hash; the original data hash is subjected to metadata fusion to obtain a metadata fusion hash; the metadata fusion hash is subjected to structured report binding, and a node digital signature is generated to obtain the report hash value; the original data hash is subjected to metadata fusion to obtain a metadata fusion hash, specifically including: obtaining laboratory key parameters and binding the laboratory key parameters with the original data hash to obtain a fusion hash; wherein the laboratory key parameters include instrument number, operator, timestamp, and environmental parameters; the fusion hash is subjected to random number configuration to obtain the data fusion hash; based on the chain request, a consensus report is determined through PBFT consensus, specifically including: the chain request is submitted to a consortium chain network, and based on the consortium chain network, a report request package is obtained through batch processing optimization of the report hash value; formula state monitoring is performed on the report request package to determine a dynamic view of master node switching; based on the dynamic view, the consensus report is determined through node public key lightweight verification; the consensus report is subjected to audit signature processing to obtain a consensus report associated with a node digital signature, specifically including: the consensus report is subjected to smart contract analysis of the report type to determine an audit process; wherein the audit process is a multi-level audit process; based on the audit process, private keys of auditors at each level are obtained, and the consensus report is digitally signed through the private keys to obtain the consensus report associated with the node digital signature.

2. The blockchain-based LIMS report management method of claim 1, wherein, based on the consensus report associated with the node digital signature, a Merkle root hash written into a blockchain is determined through Merkle tree construction, specifically including: based on the consensus report associated with the node digital signature, a Merkle tree leaf node is obtained through rehashing of key elements; based on the Merkle tree leaf node, an intermediate node is determined through hash updating of adjacent node splicing; in the case that a unique root hash is generated at the intermediate node, the Merkle root hash written into the blockchain is determined through batch information binding.

3. The blockchain-based LIMS report management method of claim 1, wherein, The management report data is analyzed by chain coordination traceability to obtain the mapping relationship between the consensus report and the content addressing hash, specifically including: The management report data is divided into original file fragments, and the file data obtained by the original file fragments is stored in a distributed file to obtain a content addressing hash; The content addressing hash is matched by information correlation to obtain the mapping relationship between the consensus report and the content addressing hash.

4. The blockchain-based LIMS report management method of claim 1, wherein, After the management report data is analyzed by chain coordination traceability to obtain the mapping relationship between the consensus report and the content addressing hash, the method further includes: Based on the mapping relationship between the consensus report and the content addressing hash, the supervision traceability information is obtained through blockchain verification.

5. A blockchain-based LIMS report management device, characterized by, The device includes: At least one processor; And a memory connected in communication with the at least one processor; Wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to: Obtain the management report data of the laboratory, and perform chain hash calculation on the management report data to obtain a report hash value; The report hash value is used as a chain request, and based on the chain request, a consensus report is determined through PBFT consensus; The consensus report is audited and signed to obtain a consensus report associated with an audit node digital signature; According to the consensus report associated with the audit node digital signature, the Merkle tree is constructed to determine the Merkle root hash written into the blockchain; The management report data is analyzed by chain coordination traceability to obtain the mapping relationship between the consensus report and the content addressing hash; The management report data is analyzed by chain coordination traceability to obtain the mapping relationship between the consensus report and the content addressing hash, specifically including: The original data of the management report data is bound to obtain an original data hash; The metadata of the original data hash is fused to obtain a metadata fusion hash; The metadata fusion hash is bound to a structured report to generate a node digital signature to obtain the report hash value; The metadata of the original data hash is fused to obtain a metadata fusion hash, specifically including: Obtain the laboratory key parameters and bind the laboratory key parameters to the original data hash to obtain a fusion hash; wherein the laboratory key parameters include: instrument number, operator, timestamp, environmental parameter; The fusion hash is configured with a random number to obtain the data fusion hash; Based on the chain request, the consensus report is determined through PBFT consensus, specifically including: The chain request is submitted to the alliance chain network, and based on the alliance chain network, the report hash value is optimized by batch processing to obtain a report request package; The formula state of the report request package is monitored to determine the dynamic view of the master node switching; According to the dynamic view, the consensus report is determined through node public key lightweight verification; The consensus completion report is subjected to an audit signature process to obtain a consensus reached report associated with a digital signature of an audit node, specifically including: The consensus completion report is subjected to an intelligent contract analysis of the report type to determine an audit process; wherein the audit process is a multi-level audit process; Based on the audit process, private keys of auditors at various levels are obtained, and the consensus completion report is subjected to a digital signature through the private keys of the auditors at various levels to obtain the consensus reached report associated with the digital signature of the audit node. 6.A non-transitory computer storage medium storing computer-executable instructions for blockchain-based LIMS report management, the computer-executable instructions comprising: The computer executable instructions are configured to: Obtain management report data of a laboratory, and perform chain-wise hash calculation on the management report data to obtain a report hash value; The report hash value is taken as a chain request, and based on the chain request, a consensus reached report is determined through PBFT consensus; The consensus completion report is subjected to an audit signature process to obtain a consensus reached report associated with a digital signature of an audit node, specifically including: According to the consensus reached report associated with the digital signature of the audit node, a Merkle tree is constructed to determine a Merkle root hash written into a blockchain; The management report data is subjected to chain collaborative traceability analysis to obtain a mapping relationship between the consensus reached report and a content addressing hash; The management report data is subjected to chain-wise hash calculation to obtain a report hash value, specifically including: The original data hash is subjected to metadata fusion to obtain a metadata fusion hash; The metadata fusion hash is subjected to structured report binding, and a node digital signature is generated to obtain the report hash value; The original data hash is subjected to metadata fusion to obtain a metadata fusion hash, specifically including: Obtain laboratory key parameters, and bind the laboratory key parameters with the original data hash to obtain a fusion hash; wherein the laboratory key parameters include: instrument number, operator, timestamp, and environmental parameters; The fusion hash is subjected to random number configuration to obtain the data fusion hash; Based on the chain request, a consensus reached report is determined through PBFT consensus, specifically including: The chain request is submitted to a consortium chain network, and based on the consortium chain network, batch processing optimization is performed on the report hash value to obtain a report request package; The report request package is subjected to formula state monitoring to determine a dynamic view of master node switching; According to the dynamic view, the consensus reached report is determined through node public key lightweight verification; The consensus completion report is subjected to an audit signature process to obtain a consensus reached report associated with a digital signature of an audit node, specifically including: The consensus completion report is subjected to an intelligent contract analysis of the report type to determine an audit process; wherein the audit process is a multi-level audit process; Based on the audit process, private keys of auditors at various levels are obtained, and the consensus completion report is subjected to a digital signature through the private keys of the auditors at various levels to obtain the consensus reached report associated with the digital signature of the audit node. ​

Images