Method and system for securing data, particularly biotechnology laboratory data - Patents.com
A semi-decentralized blockchain system with a central server and sub-servers secures biotechnology laboratory data by ensuring immutability and compliance, addressing unauthorized modification and regulatory needs while improving workflow efficiency.
Patent Information
- Application Number
- JP2022545124
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2020-07-29
- Filing Date
- 2020-11-16
- Publication Date
- 2024-11-19
- Estimated Expiration
- 2040-11-16
AI Technical Summary
Biotechnology laboratory data is vulnerable to unauthorized modification and forgery, necessitating a secure and immutable data storage solution that ensures authorship and compliance with regulatory standards.
A semi-decentralized blockchain system is implemented, comprising a central server and multiple sub-servers, where each sub-server controls a blockchain database, ensuring data immutability and access control through digital signatures and hash functions, with a central server periodically verifying the sub-servers.
The system provides secure, transparent, and compliant data storage that prevents unauthorized modification, meets regulatory requirements, and enhances laboratory workflow efficiency.
Smart Images

Figure 0007586917000001 
Figure 0007586917000002 
Figure 0007586917000003
Abstract
Description
[Technical field]
[0001] The present invention relates to a method for securing data, in particular biotechnology laboratory data, and a system for implementing this method. [Background technology]
[0002] Blockchain In 2008, Satoshi Nakamoto published a paper [5] describing Bitcoin, now called the first cryptocurrency in the world. The prefix cryptocurrency is derived from the word cryptography. Bitcoin is a complete and complex system that provides the ability to carry out anonymous and cashless transactions over the Internet. Bitcoin is based on a distributed payment ledger that can be managed by any of the users of the system. Such users are called miners, since their reward for management is newly mined currency. Miners collect information about transactions and verify whether they can be carried out. They then select transactions to be stored in the payment ledger. This ledger is known as the blockchain. Thanks to the cryptographic algorithms used, it is impossible to carry out a transaction as another user. Moreover, if a transaction is stored in the blockchain, no one can change or delete it.
[0003] Note that all Bitcoin transactions are stored unencrypted on the blockchain, but it is also possible to have encrypted data on the blockchain.
[0004] Bitcoin Technology There are several implementations of blockchain, we will focus on the well-known precursor Bitcoin. For more information, see [2]. A seller or payer who wants to make a transaction must submit their action to the blockchain. Everyone connected to the blockchain system receives information about the transaction. The recipients are clients, called miners, who verify the action by an algorithm. Verification by a cryptographic algorithm is performed using two calculation steps. Miners provide the computing power. The software for mining is free and simple. Moreover, no certificates are required, so everyone can volunteer with their computers. The miner must verify the presence of Bitcoins that can be used for the transaction. Then the miner checks the form and accepts the transaction. If the miner validates the entire block, the miner is awarded Bitcoins. The block contains detailed information about the transaction verification process. A block is stored in the blockchain after it has been verified by a fixed number of miners. Moreover, in every block there is a timestamp and a mathematically generated complex sum of variables, called a hash, that secures the (non)interruption in the data block. These cryptographic hashes of a block are calculated based on the previous and current blocks. This unique and unique sum constitutes the security signature that binds the block to the blockchain. The irreversibility of hash codes makes the blockchain immutable. This is how we obtain digital trust. The decentralized verification of actions and storing them in a history makes intermediary entities, like banks, unnecessary to carry out transactions. example: 1. John wants to pay Alice in Bitcoin. 2. John's transaction takes place. 3. The transactions are combined into a new block. 4. The block is broadcast to miners. 5. The miner validates and accepts the transaction. 6. The new block is encrypted using the hash of the previous block. 7. The new block becomes part of the blockchain. 8. Alice receives the Bitcoin.
[0005] Sensitive Data in the Blockchain Decentralized systems can be widely used. The biggest benefit is that there is no need for third parties. As we saw before, decentralized data can be secured and immutable. Today, most organizations collect our personal data to optimize their services. They want to predict our needs and create a digital personal picture of us, so personal information in every way is a valuable resource in today's economy. Although personalized systems have many benefits, issues about our privacy are a concern. Moreover, more often now organizations have little control over personal sensitive data. That is why this information should not be handled by third parties. Centralized systems are vulnerable to hacker attacks as well as phishing. The solution is for users to own their information and be responsible for providing it.
[0006] We can do this by applying the blockchain storage solution proposed by [8]. The authors proposed a personal data management system that has the advantages of blockchain and off-blockchain storage. It involves several main aspects, namely data ownership, data transparency audibility and fine-grained access control. The proposed platform distinguishes between users, who own and control their personal information, and services. Every user has information about the colocated data and how it is accessed by the organization. Services have delegated permissions from them to access the user’s data. Moreover, the data owner can make changes to the set of permissions to deny access to the data to the services. This solution is similar to that of a mobile app. It does not affect the user interface, since the access control policies are stored in the blockchain. Only users can make changes on the blockchain (Figure 1).
[0007] Some ideas about blockchain applications in health care can be found in [2].
[0008] Laboratory Results obtained in Good Manufacturing Practice (GMP) and Good Laboratory Practice (GLP) laboratories must be reliable. Partial result corrections can result in failure of the final result. That is why laboratory records must be collected accurately and without falsification. It is also important to remember the authorship of every record. Authorship must be unquestionable, which means that no one can create a record on behalf of another user, and no user can deny his / her authorship of any of his / her records. Moreover, documents must be immutable, so that no stored data can be modified or deleted. These requirements force users to keep strict records, which objectively increases the reliability of the laboratory.
[0009] Solving this problem required the inventors to collaborate with employees of biotechnology laboratories and diagnostics. Translating a real-life problem into an algorithmic technology approach was time-consuming.
[0010] Several key aspects regarding lab personnel: - Certain access to the warehouse, with restrictions and access rules; - Rules for handling production to improve the process; - Rules for collecting laboratory results. Authorship of the data obtained. - Rules for reporting daily activities to avoid forgery and alteration; - Communication with clients There was. All these aspects have a significant impact on laboratory workflow.
[0011] Blockchain technology is widely used in accounting and banking, but not only in those fields. There are many projects that apply this technology in many different areas of daily life. Our project, by using blockchain technology in the widely understood area of health care, is one of them.
[0012] The requirements for documentation in biotechnology laboratories cannot be enforced when records are kept on paper. However, the relevant requirements for laboratory records are met by the main features of blockchain. This patent application proposes an innovative method and system for securing biotechnology laboratory data using blockchain technology, whereby data is stored in the blockchain and the validity of newly added transactions is checked.
[0013] U.S. Patent Application Publication No. 20170364637(A1), entitled "Mobile health management database, targeted educational assistance (tea) engine, selective health care data sharing, family tree graphical user interface, and health journal social network wall feed, computer-implemented system, method and computer program product," describes a system, method and computer program product for capturing and displaying health information of a first person on an electronic computing device, where the electronic computing device can include one or more computer processors and one or more memory devices, and the computer-implemented method can include, for example, a) electronically receiving data regarding a first person user on a first client computing device, where the first person user has one or more family users, or users with whom the user may wish to share personal health data records, each having one or more computing devices, and receiving the data regarding the first person user. a) electronically receiving data about a first human user, which may include any identification data, any entered health-related data, or any captured health-related data about the first person, and which may include any health-related data, application programming interface (API) accessible data, or other health records, such as, for example, electronic medical records (EMR), scanned data, sensed data, or optical character recognition (OCR) captured data; and b) receiving data about one or more second human users, where at least one second human user may include any other user, family member, guardian, friend, individual, or caregiver with whom the first person wishes to be connected, and where the data about the second human users may include any identification data, any entered health-related data, or any captured health-related data about the first person.Disclosed are systems, methods and computer program products that may include receiving data related to one or more second human users, which may include any entered health-related data or any captured health-related data related to the second human users, and c) electronically sharing at least a portion of the data related to the first human users to the second human users. Various other embodiments may include various features, such as health magazines, targeted educational content, interactive family trees, selectable sharing, escalated alerting, notifications, and collaborative digital file cabinets. This specification focuses on the mobile application, not the technical details of how the data is stored. In particular, this specification does not disclose or suggest a system that includes a central server and two or more blockchain subsystems, each controlled by a dedicated sub-server, where the central server verifies the compatibility and immutability of the blockchain databases in the two or more subsystems. Summary of the Invention [Problem to be solved by the invention]
[0014] Thus, the object of the present invention is to provide a method and system for securing data, particularly biotechnology laboratory data, using blockchain technology, providing data safety and authenticity (as each individual data has its author), while at the same time providing users with an easy-to-manage method of data access and control. Moreover, the present invention provides a system and method that is fully compliant with the relevant provisions of the law. [Means for solving the problem]
[0015] According to the invention, there is provided a method for securing data, in particular biotechnology laboratory data, using blockchain technology implemented in a system comprising a central server and two or more subsystems, each controlled by a dedicated sub-server, each of the two or more subsystems: - a first blockchain database for storing information data, in particular biotechnology laboratory data, in which transactions in the first blockchain database are committed according to blockchain rules, including treating a first specific piece of information as a transaction, creating a digital signature of the transaction by an author of the first specific piece of information using the author's digital key, combining the transaction into a first new block, encrypting the first new block with a hash of the previous block in the first database, and storing the first new block in the first database; - a second blockchain database for storing access data, including digital keys of users having access to the first database and information regarding permissions to read data from or write data to the first database by this user associated with the digital key of each such user, wherein the second database information is stored according to blockchain rules, including treating the second specific information as a transaction, creating a digital signature of the transaction by an author of the second specific information using the author's digital key, combining the transaction into a second new block, encrypting the second new block with a hash of the previous block in the second database, and storing the second new block in the second database; Equipped with - any authorized user having access to a first database can enable another user to read data authored by the authorized user from the first database by adding the other user's digital key to the second database with corresponding authorization information; - any authorized user having access to a first database can prohibit another user from reading data authored by said authorized user from the first database by adding said other user's digital key to said second database with corresponding permission information; - any authorized user having access to the first database is capable of revoking from another user a previously granted right to access data in the first database that was authored by said authorized user; The method for securing data comprises: - collecting the hash and optionally the timestamp from a blockchain database in the two or more subsystems, preferably by collecting only the hash and optionally the timestamp; - Exchange new transactions between the central server and the subservers, using the subservers' private keys to avoid fake hashes, and independently verify the compatibility of hashes. verification by a central server of compatibility and immutability of the blockchain databases in the two or more subsystems; method.
[0016] Preferably, SHA-3 is used as a hash function for the calculation of block hashes in the first blockchain database and / or the second blockchain database.
[0017] Preferably, an RSA algorithm with a key size of 4096 bits is used to create a digital signature of the transaction using the digital key of its author in the first blockchain database and / or the second blockchain database.
[0018] Preferably, the system additionally comprises a timestamp server, which provides timestamps to the first blockchain database and / or the second blockchain database, in particular to transactions and / or blocks in the first blockchain database and / or the second blockchain database.
[0019] Preferably, the second database comprises a summary block containing hashes of the K preceding blocks and a hash of the latest summary block, the summary block containing updated information of user privileges.
[0020] In such a case, a central server monitors the summary blocks.
[0021] Preferably, the central server periodically communicates with the sub-servers, and in particular the blockchain database in each of two or more subsystems, each controlled by a dedicated sub-server, is periodically verified by the central server.
[0022] The inventive method may be run on a laboratory server or central computer without internet access.
[0023] Preferably, said first blockchain database and said second blockchain database are one and the same blockchain database for storing both information data, in particular biotechnology laboratory data, and access data, including digital keys of users having access to the first database and information regarding the authorization to read data from or write data to the first database by this user associated with the digital key of each such user.
[0024] Preferably, the data stored in the first database relates to donor registration for transplantation, biostorage or clinical trials.
[0025] According to the present invention, there is provided a system for securing data, in particular biotechnology laboratory data, comprising a central server and two or more subsystems, each controlled by a dedicated sub-server, each of the two or more subsystems comprising a first blockchain database for storing information data, in particular biotechnology laboratory data, and a second blockchain database for storing access data comprising digital keys of users having access to the first database and information regarding the authorization to read data from or write data to the first database by this user associated to the digital key of each such user, said system configured and programmed for performing the inventive method described above.
[0026] Existing blockchain-compatible systems are widely distributed. Typically, in such systems, miners all hold a portion or the entire blockchain database and perform validation. These distributed copies of transactions make them immune to hacking attacks or forgery, since it is practically impossible to marshal a sufficient amount of computing power (a “hacking force”) for almost every node in the blockchain to be falsified.
[0027] In a laboratory scenario, it is not possible to achieve that amount of computing power to verify transactions. But it is not necessary. Laboratory results are less of a target for unsolicited attacks. Results need to be protected from being falsified or corrupted by unauthorized parties. Data changes need to be tracked. Laboratory computers are usually in closed networks with no access to the Internet, and they are not open like public services.
[0028] To achieve a similar level of protection as in a decentralized blockchain, we can simulate decentralization by creating a semi-decentralized system. The idea involves one or more sub-servers that perform regular blockchain maintenance in their respective blockchain subsystems, and a central server that is the guard for the blockchain subsystem. The central server contains (only) the hash and timestamp from the blockchain subsystem. Moreover, at fixed intervals, the central server validates the sub-servers by computing their blockchain. In this scenario, the central server acts as an additional miner that simulates holding the entire blockchain.
[0029] The semi-distributed approach described above: - Less computing power required compared to fully decentralized blockchains, - Easy adaptation to laboratory diversity without additional equipment thanks to the compact network concept, - A soft copy of the blockchain held by a central server; - each of the Sub-Servers holding only their own respective data in their respective Blockchain Subsystems, This has several advantages, including: In case of a forgery attack, at least two servers have to be hacked. The system can be implemented and run in a closed network with no Internet access.
[0030] Preferred embodiments of the invention are presented below in a more detailed manner with reference to the accompanying drawings. [Brief description of the drawings]
[0031] [Figure 1] FIG. 1 presents a simplified schema of the above grant access data blockchain. [Diagram 2] FIG. 2 illustrates hash linking and RSA signatures in blocks. [Diagram 3] FIG. 1 presents the proposed laboratory blockchain platform usage, where the platform verifies and stores signed and secured transactions, additional laboratory supporting algorithms perform analysis for users based on the blockchain data, and alerts are sent when necessary. [Figure 4] FIG. 1 shows a summary-block that contains the hashes of K previous blocks and the hash of the latest summary-block. The summary-block contains updated information about user privileges, and the summary-block is a checkpoint block and does not need to be calculated to "tail" the blockchain. [Diagram 5]The diagram presents a central server that controls two or more blockchain systems, stores the hash and timestamp of every block, and periodically verifies whether the blockchains are corrupted. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0032] Preferred embodiments of the present invention are described in detail below. The examples serve for illustration only and do not limit the scope of the present invention.
[0033] Blockchain Applications The authors of Bitcoin [5] stated that there could be a central authority that produces coins and verifies transactions. That raises the problem that the authority would have infinite knowledge about every transaction. This problem could be solved in a very clever way. Before trying to explain the solution to this, we will focus on the transactions that we define in the blockchain for GMP and GLP laboratories. We want every piece of information to be immutable and have its author. In our platform, a single piece of information transaction represents a coin in the Bitcoin system.
[0034] Consider a scenario where user A created a note on some topic. Our system needs to remember the authorship of that note, as well as the fact that user A cannot negate any part of that note. That is why users certify the note by their own digital signature. A different user B states that the note has a defect and therefore he wants to make a correction. He can do this, but not in an obvious way. User B takes the note, adds a calculated hash code from the note, and adds a correction to the note. After adding his digital signature, he submits the information. In this way, any user can verify which parts belong to A and which parts belong to B. We acknowledge the compatibility between Bitcoin, crypto-coins and data-notes according to the present invention. The correction mechanism made by B is similar to the case of spending the same crypto-coin twice. It turns out that a system verifying folding signatures solves this problem similar to the Bitcoin scenario.
[0035] The different aspect is when the need to create information arises. Coins can be created in a certain normalized way. The information stored in our platform should be available for any authorized user. That is why we need a second type of coin that represents the authorized access for the user. That is why every authorized laboratory user has the ability to add his colleague's digital key, allowing him to make transitions in the blockchain. As with every authorized user, it can also deny certain users access to the system. In summary, in the Bitcoin system, information about who sends coins to whom is stored. In our inventive platform, we have - User digital keys with authorization information. We track whether a user is allowed to sign a transaction, - Data information. We track the authorship of laboratory data, and the solution is general, so any type of laboratory data can be stored. The information relating to the above is stored.
[0036] Therefore, in the inventive solution, both data and proofs are collected in a blockchain database. From this point of view, the inventive system can be considered to consist of two parts:
[0037] Technical details Programming languages and libraries. We choose a specific cryptography package and the programming language Python3 so that we can create the application for any system (in any technology). Python apps are not as efficient as C apps, but they are more portable. Python is also valued among professional programmers working with cybersecurity. In the prototype, we used the Django framework and the cryptography Python package for the SHA-3 implemented hash function. It allows simple and effective programming and is spreading rapidly. These algorithms are sufficient for our needs.
[0038] Block Hash Function. A basic and essential component of a blockchain is a well-defined hash function. The National Institute of Standards and Technology (NIST) has published two papers [1] and [3], where it certified only three hash functions: SHA-1, SHA-2 and SHA-3.
[0039] SHA-3 is technically quite different from the other two. SHA-1 and SHA-2 are based on a common mathematical mechanism. In 2017, Google announced that SHA-1 had been broken and should not be used for security purposes [7]. Compared to SHA-1 and SHA-2, we chose SHA-3 as a newer and bug-free algorithm.
[0040] User digital signature. The next important step in creating a blockchain is the algorithm for digital signatures and their verification. Here, the main solution is an asymmetric one-way encryption function. The National Institute of Standards and Technology (NIST) in [4] defined three encryption algorithms with digital signatures: RSA, DSA and ECDSA.
[0041] Due to the controversy over elliptic curves proposed by cryptography authority Bruce Schneier [6], we chose the RSA algorithm with a key size of 4096 bits.
[0042] Block implementation details. To avoid future problems, we designed blocks in the form of dictionaries with a predefined set of keys. These objects can be easily In JSON format Serialized , De It can be serialized. Listing 1.1 shows seven keys for the dictionary block. class BlockField(Enum): BLOCK_TYPE = 0 TIMESTAMP = 1 AUTHOR = 2 SIGNATURE = 3 OBJECT = 4 PREVIOUS_HASH = 5 NONCE = 6 Listing 1.1. An Enum describing all the parameters in a block object. We also defined five types of blocks, which are shown in Listing 1.2. class BlockType(Enum): GENESIS = 0 INSERT_BLOCK = 1 UPDATE_BLOCK = 2 INSERT_KEY = 3 REVOKE_KEY = 4 Listing 1.2. An Enum describing the possible types of blocks in the chain.
[0043] The genesis block is the first one in the chain. There can only be one genesis block in a blockchain. It contains the system administrator keys and it cannot be rejected. The public key is controlled by the administrators who manage the software and is not in the hands of lab employees.
[0044] Platform We have completed the work of implementation of blockchain technology prototype, besides, we have made non-conventional modifications of blockchain technology in a manner that meets the objectives given by our theoretical analysis. We have verified the time resources saved by our system. There has been a significant improvement. The system was effective in solving time-consuming and resource-consuming problems. The designed platform has been verified in laboratory conditions. We have found that the designed solution has impacted the laboratory workflow (Figure 3).
[0045] We have verified the effectiveness in all aspects of the use cases and in the performance of our system: the processing time and memory usage of the blockchain mechanism are not computationally intensive.
[0046] The template platform we have designed with minimal customization provides the benefits widely desired in laboratories. Below is a list of advantages that will derive from the proposed blockchain system: 1. Data is secured against unauthorized modification. 2. Blockchain security of data makes them authentic and reputable. 3. Data stored in the blockchain is transparent. 4. The system allows for electronic documentation transmission in accordance with Good Manufacturing Practices regulations, i.e., US Code of Federal Regulations, Title 11, Part 11 (GMP CFR 21 Part 11). 5. The system complies with the legal requirements for biobanks. 6. The system helps physicians and dentists achieve compliant tissue and cell procurement. 7. The system meets the statutes of the Drugs Act regarding the production of advanced pharmaceutical products. 8. The system meets UE requirements for production and medical therapy (transplanting cells, tissues and organs). 9. Additional algorithms in the system archive statistics that improve laboratory workflow. 10. The system helps to ensure stable management of laboratory storage. 11. The system’s built-in analytical algorithms save employees’ time as they validate demand, enumerate production.
[0047] System Stability The authors introduce the idea of a timestamp server in [5], which binds blocks in chronological order. In our proposed system, there is only one timestamp server. Network or physical access to the server is restricted to a minimum. The system checks data created or edited in the laboratory, as well as the keys of users who can submit this data. The timestamp server sorts transactions in chronological order. When new data is added, the system checks its validity, e.g. - whether the note was created before, - whether the edited content of the note corresponds to the last one in the blockchain; - Whether the user is enabled to add notes: the system verifies whether the user's digital key is active and authorized to add content; We verify this.
[0048] We have created a stability list to determine if the blockchain is corrupted. Below is a checklist that is verified by the system when inserting a block into the blockchain. 1. The first block is not the genesis block. 2. Two or more blocks are genesis blocks. 3. The previous hash field for the genesis block is different from what is expected. 4. The timestamp from the block's name does not correspond to the block's content. 5. The previous hash value of the block does not match the block before it. 6. Hash strings do not start with a fixed length of zeros. 7. User digital keys were added twice. 8. The user digital key was deleted twice. 9. The genesis key has been removed. 10. Blocks added by unauthorized users due to lack of digital key. 11. Blocks added by unauthorized users due to digital key denial. 12. Missing required fields in a block.
[0049] We have tried to hack our system. We used brute force attacks, but fortunately we were not successful. The encryption package we chose to run our system with is dedicated to this kind of unwanted hacking access. Moreover, the SHA-3 algorithm used as the hash function is one of the safest, most secure and most efficient hashing algorithms. For non-quantum computers, the SHA-3 algorithm should not be broken within the next 20-30 years.
[0050] Semi-decentralized blockchain There is no need to split the blockchain into parts or keep the whole blockchain at every instance. That is why in a large facility with many separate laboratories it is beneficial to deploy a semi-decentralized blockchain. We use one central server that contains only the hashes of the blocks forming the laboratory blockchain and verifies if they are corrupted. - In a multi-laboratory scenario, a central authority is needed to verify laboratory activity. - A semi-decentralized blockchain is essential in a multi-laboratory scenario to increase transparency between laboratory units (Figure 4). - In a semi-decentralized blockchain scenario, there is only one central server. - The central server verifies the compatibility and immutability of the blockchains in the sub-laboratories, and each of the blockchains in the sub-laboratories is controlled by a dedicated sub-server. - The central server collects only hashes and timestamps from the sub-laboratory blockchains. - The central server and the subservers exchange new transactions and independently verify the compatibility of the hashes. The private keys of the subservers are needed to avoid fake hashes. - The entire blockchain of the sub-servers is periodically verified by the central server. - The central server monitors the digest blocks (if they are used). - The central server communicates with the sub-laboratories periodically, on a schedule defined by the administrator (Figure 5).
[0051] Platform Compatibility The following features are optional, but useful features of the present invention, which may be used as scheduling algorithms by the super user / administrator and adapted to the particular laboratory situation. - A single computer can contain and manage a simple blockchain without any additional modifications. - Laboratory results are mostly in paper format in Excel. With a user-friendly interface, the inventive platform increases the workflow. - Media consistency: only hashes of media files are stored on the blockchain. - Blockchain can be semi-decentralized. - The blockchain can run on a laboratory server or a central computer without internet access. - Periodically, the entire blockchain is computed and checked for incompatibilities. - Summary block generation can be activated to achieve smaller computation time. - In facilities with sub-laboratories, the blockchain is semi-decentralized. The central server is the adjudicator that periodically collects and validates only the hashes of the block-shaped blockchain of the subordinate sub-laboratories. - Maintenance does not allow blockchain changes.
[0052] Genesis Block Technical details of the genesis block. 1. All user information is stored in the blockchain. 2. In the UserData field is the private user key encrypted with the user's password. 3. There is only one superuser administrator. 4. Only admins are allowed to create the genesis block. 5. There is only one genesis block that starts the blockchain.
[0053] User Permissions The technical details of the user. - The genesis block is required to start the blockchain and create new users. - User authorization and private key information are checked every time. -To secure unauthorized access, permissions are stored in the blockchain as well as administrators and genesis block scenarios. - Only the Super User can add new authorized users. - Only the Super User can revoke permissions from a user. - All actual user privileges are stored in the summary block.
[0054] Summary - Blocks Except for certain computational research units, there may be a lack of high-end computers in some laboratories. That is why we introduced the summary-block idea. This simple addition is a perfect solution to reduce the computation time while still not breaking the fundamentals of blockchain. 1. Summary – The block is a shortcut block that shortens the blockchain. 2. Summary - The purpose of blocking is to improve computation time for new transactions. 3. Block computation time is analyzed. If the computation time exceeds a critical value, the administrator is notified. 4. Only superuser administrators can manually enforce summary-block. 5. Summary – Block Creation Conditions. - A new user is added. - User privileges are changed. - Algorithm constraints: current block size is too large. - The calculation time is too long. - Maintenance constraints. 6. Summary – Block Generation. (a) The blockchain is divided into K blocks. For every K blocks, there is a summary-block. (b) The entire blockchain is computed and verified for corruption by using only the summary-block and the remaining most recent blocks. (c) The new summary block is - Previous Block - Previous Summary-Block - Recent blocks (starting from previous summary-block) Contains a hash of (d) The current blockchain is backed up and replaced with the summary-block as the last block. (e) A validation of the entire classical blockchain is scheduled. (f) The genesis block remains the same.
[0055] The above described platform (comprising the inventive method and the inventive system) has been applied to selected fields related to biotechnology laboratories. Examples of such applications are described below.
[0056] Electronic Donor Registration for Transplantation The inventive platform was applied to deliver a web application for registering tissue donor patients in the laboratory and for the preparation of the appropriate documentation. The system also allows completing all the necessary data for tissue donor registration, making a decision if the patient can be allowed to donate, and registering the tests performed and the observations related to it. Thanks to the system it is easy to coordinate the work of the whole team.
[0057] The system is operated in three steps: 1. Registration of the patient in the system together with the following application, namely, personal data, type of tissue to be collected, or research program to which the collection should cover. 2. A downloadable credentialing consent form to proceed with the procedure is filled in, which must be printed and signed by the patient. The remaining elements of the credentialing data are then filled in, including, among other things, laboratory test results and past illnesses. This data is verified and a decision is made whether the patient should be enabled for tissue collection. 3. In case of positive credentials, tissue collection is performed. After tissue collection in the laboratory, the collection data is entered into the system and a number is generated for it. There is the possibility to print a protocol and send the collected tissue to one of the collaborating entities.
[0058] Biostorage The inventive platform was applied to deliver a web application for managing materials stored in the warehouse of a drug manufacturer, cytostatic drug laboratories as well as other reception drugs prepared in pharmacies, tissue and cell bank laboratories of GMP and GLP standards. The system allows to define the requirements for each item to be stored in the warehouse by preparing a material specification. Thanks to this, the application guides the user step by step through the process of releasing materials to the warehouse, storing, sending as well as ordering the missing material. A unique feature of the system is the management and documentation of intermediate materials, which are prepared from starting materials in the user's units.
[0059] The system is put into operation in five steps: 1. Define the list of materials to be stored in the warehouse. For each, specify the list of suppliers from which the material can be ordered. For each material, develop quality specifications and record templates for acquiring such materials. 2. Acquire material for storage. Document the compatibility of the received material along with its specifications by generating supplier records and history. Print the label and apply it to the released material and place it in the correct location on the storage area. 3. Check inventory. Set warning limits for materials in the warehouse and the system will notify users about materials that are nearing the end of their expiry date! Generate orders before users are surprised by too short expiry dates. 4. Get ready for production! Define the list of materials that you need to produce / process your product / implant. Check with one click if you are ready for a new order! 5. Manage material consumption. Materials stored in the warehouse can be allocated to specific products / transports that are the essence of the user's business. Thanks to this, the user knows about the use of materials and easily analyzes the costs related to product type / transport, duration of the process, amount of product received and employees.
[0060] Clinical Trials The inventive platform was applied to deliver a web application used to create and manage CRFs (Case Report Forms) in non-commercial clinical trials. The application is designed for both sponsored research / CROs (Clinical Research Organizations) and research teams. As a sponsor of a study (and / or CRO), the user can quickly create CRFs for new clinical trials and the user can track the progress of the clinical trial and conduct monitoring visits. As a research team, the user can easily fill out CRFs for trial participants.
[0061] Acknowledgements This work was supported by the Regional Operational Programme for Malopolska Region 2014-2020 as the research project namely: Development of an innovative data security system in biotechnology and diagnostic laboratories based on blockchain technologies. Contract number: RPMP.01.02.01-12-0183 / 18-00.
[0062] References 1.Secure hash standard. Federal Information Processing Standard (FIPS)180-4(2012) 2.Angraal,S.、Krumholz,H.M.、Schulz,W.L.:Blockchain technology:applications in health care. Circulation:Cardiovascular Quality and Outcomes10(9)、e003800(2017) 3.Dworkin,M.J.:Sha-3 standard:Permutation-based hash and extendable-output functions. Federal Information Processing Standards (NIST FIPS)-202(2015) 4.Gallagher,P.:Digital signature standard (dss). Federal Information Processing Stan-dards Publications、volume FIPS 186-3ページ(2013) 5.Nakamoto,S.:Bitcoin:A peer-to-peer electronic cash system(2019) 6.Schneier,B.:The nsa is breaking most encryption on the internet blog post、september 2013 7.Stevens,M.、Bursztein,E.、Karpman,P.、Albertini,A.、Markov,Y.、Bianco,A.P.、Baisse,C.:Announcing the first sha1 collision. Google Security Blog (2017) 8.Zyskind,G.、Nathan,O.ら:Decentralizing privacy:Using blockchain to protect personal data. In:2015 IEEE Security and Privacy Workshops.180-184ページ.IEEE (2015)
Claims
1. A method for securing data, in particular biotechnology laboratory data, using blockchain technology, implemented in a system comprising a central server and two or more subsystems, each controlled by a dedicated sub-server, each of said two or more subsystems: a first blockchain database for storing information data, in particular biotechnology laboratory data, in which transactions in the first blockchain database are committed according to blockchain rules, including treating a first specific piece of information as a transaction, creating a digital signature of the transaction by the author of the first specific piece of information using the author's digital key, combining the transaction into a first new block, encrypting the first new block with a hash of the previous block in the first database, and storing the first new block in the first database; a second blockchain database for storing access data including digital keys of users having access to the first database and information regarding authorization to read data from or write data to the first database by this user associated with the digital key of each such user, wherein the second database information is stored according to blockchain rules including treating a second specific information as a transaction, creating a digital signature of the transaction by an author of the second specific information using the author's digital key, combining the transaction into a second new block, encrypting the second new block with a hash of a previous block in the second database, and storing the second new block in the second database; Equipped with any authorized user having access to the first database can enable another user to read data authored by the authorized user from the first database by adding the digital key of the other user to the second database with corresponding authorization information; any authorized user having access to the first database can prohibit another user from reading data authored by the authorized user from the first database by adding the digital key of the other user to the second database with corresponding permission information; any authorized user having access to said first database is able to revoke from another user a previously granted right to access data in said first database that was authored by said authorized user; The method for securing data comprises: - collecting said hash and optionally a timestamp from a block chain database in said two or more subsystems; - exchanging new transactions between the central server and the sub-servers using the private keys of the sub-servers to avoid false hashes, and independently verifying the compatibility of hashes; verification by the central server of compatibility and immutability of the blockchain databases in the two or more subsystems; method.
2. 2. The method of claim 1, wherein SHA-3 is used as a hash function for calculating block hashes in the first blockchain database and / or the second blockchain database.
3. 3. The method of claim 1 or 2, wherein an RSA algorithm with a key size of 4096 bits is used to create a digital signature of the transaction using a digital key of its author in the first blockchain database and / or the second blockchain database.
4. 4. The method according to claim 1, wherein the system additionally comprises a timestamp server, the timestamp server providing timestamps to the first blockchain database and / or the second blockchain database, in particular to transactions and / or blocks in the first blockchain database and / or the second blockchain database.
5. 5. The method of claim 1, wherein the second database comprises a summary block containing hashes of K preceding blocks and a hash of a latest summary block, the summary block containing updated information of user privileges.
6. The method of claim 5 , wherein the central server monitors the summary blocks.
7. 7. The method according to claim 1, wherein the central server periodically communicates with the sub-servers, in particular the blockchain database in each of the two or more subsystems, each controlled by a dedicated sub-server, is periodically verified by the central server.
8. 8. The method of any one of claims 1 to 7, running on a laboratory server or a central computer without internet access.
9. 9. The method according to any one of claims 1 to 8, wherein the first blockchain database and the second blockchain database are the same blockchain database for storing both the information data, in particular biotechnology laboratory data, and the access data, including digital keys of users having access to the first database and information about the authorization to read data from or write data to the first database by this user associated with the digital key of each such user.
10. The method of any one of claims 1 to 9, wherein the data stored in the first database relates to donor registration for transplantation, biostorage or clinical trials.
11. A system for securing data, in particular biotechnology laboratory data, comprising a central server and two or more subsystems, each controlled by a dedicated sub-server, each of the two or more subsystems comprising a first blockchain database for storing information data, in particular biotechnology laboratory data, and a second blockchain database for storing access data comprising digital keys of users having access to the first database and information regarding the permissions to read data from or write data to the first database by this user associated with the digital key of each such user, the system being configured and programmed to perform the method according to any one of claims 1 to 10.
Citation Information
Patent Citations
Access restriction system, access restriction method and access restriction program
JP2019174995A
Distributed medical information sharing system, medical information provision server, and program
JP2020010267A
Control method, content management system, program, and data structure
WO2020084972A1
