CN112559627A - Alliance chain-based on-chain-under-chain collaborative electronic medical record data sharing method - Google Patents
Alliance chain-based on-chain-under-chain collaborative electronic medical record data sharing method Download PDFInfo
- Publication number
- CN112559627A CN112559627A CN202011449779.7A CN202011449779A CN112559627A CN 112559627 A CN112559627 A CN 112559627A CN 202011449779 A CN202011449779 A CN 202011449779A CN 112559627 A CN112559627 A CN 112559627A
- Authority
- CN
- China
- Prior art keywords
- medical record
- hospital
- data
- block
- user
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2365—Ensuring data consistency and integrity
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
- G06F21/6245—Protecting personal data, e.g. for financial or medical purposes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/64—Protecting data integrity, e.g. using checksums, certificates or signatures
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H10/00—ICT specially adapted for the handling or processing of patient-related medical or healthcare data
- G16H10/60—ICT specially adapted for the handling or processing of patient-related medical or healthcare data for patient-specific data, e.g. for electronic patient records
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- General Health & Medical Sciences (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Health & Medical Sciences (AREA)
- Bioethics (AREA)
- Data Mining & Analysis (AREA)
- Medical Informatics (AREA)
- Computer Hardware Design (AREA)
- Software Systems (AREA)
- Computing Systems (AREA)
- Epidemiology (AREA)
- Primary Health Care (AREA)
- Public Health (AREA)
- Medical Treatment And Welfare Office Work (AREA)
Abstract
The invention provides a federation chain-based on-chain and-down-chain collaborative electronic medical record data sharing method, and relates to the technical field of computer data sharing. The method comprises the steps of establishing a block chain distributed hyper folder Fabric block chain network by establishing a block chain platform; designing a medical record writing function of the electronic medical record system; selecting a MySQL database as a block chain database for storing the electronic medical record; the query, modification and deletion operations of the historical medical record data of a certain patient are realized; the uploaded medical record is digitally signed by using public keys of the patient and the doctor to control the access authority of the user, so that the privacy of the patient is protected, and meanwhile, the data is prevented from being tampered. The patent establishes a multi-union chain architecture, realizes cross-hospital safe data transmission by using a channel technology of a union chain, realizes medical data conversion among different hospital databases by using a json text as a temporary carrier, and solves the problem of difficult sharing due to a data format at present.
Description
Technical Field
The invention relates to the technical field of computer data sharing, in particular to a federation chain-based on-chain and-down-chain collaborative electronic medical record data sharing method.
Background
In recent years, with the continuous development and utilization of computer functions, electronic medical records are gradually coming into the eyes of people. The electronic medical record is widely used in the medical field due to the advantages of convenient circulation, lasting preservation, resource saving and the like. But the method also has the defect of easy tampering and the like, and can cause medical disputes.
The blockchain is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, a consensus mechanism, an encryption algorithm and the like, and is essentially a decentralized database. Based on three forms of a public chain, a federation chain and a private chain of the block chain technology, the federation chain is still a private chain in nature, but is larger than the private chain developed by a single small organization, but has no scale of the public chain, and the block chain is understood to be a block chain between the private chain and the public chain. The three main characteristics of the block chain comprise decentralization, tamper resistance and traceability. Decentralized so that each node is equal, each node can modify and query information. The intermediate node and the root node of the Merkle tree in the block are obtained by carrying out hash operation on two child nodes, so that when the data of the leaf nodes are changed, the data are transmitted upwards step by step to change the value of a parent node of the leaf nodes until the hash value of the root node of the Merkle tree is changed, and thus, the nodes in the network can find that the data are changed, thereby realizing the tamper resistance. Any manipulation of the medical data results in a transaction that is uploaded into the block and thus recorded by the blockchain, which can be traced back by the query due to the uniqueness of the data information. The alliance chain is commonly maintained by participating member organizations, and provides a complete set of safety management functions of management, authentication, authorization, monitoring, audit and the like for participating members.
Therefore, the defect that the electronic medical record is easy to tamper can be improved by adopting the electronic medical record based on the medical alliance chain, the safety of the electronic medical record can be improved, and the information of the patient can be more accurately reflected by the electronic medical record.
In fact, for the block chain, the block chain is already mentioned in "notice of State Council about issuing" thirteen five "national information program", published by the State level as early as 2016 12 months. In recent years, provinces and cities are actively laying out block chains and corresponding incentive policies are issued. At present, the use amount of the tracing field accounts for 38 percent in the main project of the global medical care industry. The 'block chain + medical treatment' ground projects in China are mostly in Shanghai, Beijing, Zhejiang, Jiangsu and the like, and mainly comprise application scenes of medical apparatus/medicine/vaccine anti-counterfeiting traceability, electronic prescription circulation, electronic medical records, hospital electronic bills, medical insurance and the like.
As the block chain is a new shared account book and database concept which is proposed only in the last decade, the block chain also has a plurality of fields which are not developed and researched, and the properties of centralization, distributed data storage, whole-course trace retention, collective maintenance and the like of the block chain just meet the development requirement of electronic medical records which are gradually identified as EHRs in connotation at present, namely the information integration between medical institutions including between the medical institutions by taking individuals as centers. Therefore, the common point is used as a starting point to integrate the block chain technology and the electronic medical record.
Disclosure of Invention
Aiming at the defects of the prior art, the invention provides a federation chain-based on-chain and-down-chain collaborative electronic medical record data sharing method.
A federation chain-based on-chain and-chain-down collaborative electronic medical record data sharing method comprises the following steps:
step 1: building a block chain platform, and building a block chain distributed hyper-hedge fabric block chain network;
step 1-1: configuring an environment by utilizing an open source code of a HyperLedgerFabric platform and setting a block data model;
step 1-2: designing a generating block function CreatBlock of a generating block, calculating a hash value function Calculatehash and a checking function amine for checking whether data are tampered;
the generate block function CreatBlock is as follows:
Newblock＝CreateBlock(blockHeaders,blockBody)
wherein Newblock is a created new block; CreatBlock is a block function created and is executed by a peer node (intelligent contract) module in a super ledger book; the block consists of a block header and a block body, wherein the block header (block headers) comprises the height (block height) of the block, the Hash value (Hash) of the block, the Hash value (prevBlockHash) of the previous block, a timeStamp (timeStamp) and the Hash value (merkleRoot) of the Merkle tree root; the block body (blockBody) includes transactions (transactions) within the block and transaction numbers (numTransactions) of the block.
The calculate hash value function calllatehash is as follows:
Hash＝SHA(h)
wherein SHA is a SHA256 function; h includes a predecessor chunk hash value (prevBlockHash), Merkle root hash value (merkleRoot), timeStamp (timeStamp); the Hash is the current block Hash value.
The test function, Examine, is shown below:
Consistent＝Examine(thash(a),dhash(a))
the Examine is a function for checking whether the two parameters are equal, the return value is of a Boolean type, and the result of the return of the constant is True, which indicates that the medical record data are Consistent and are not tampered; returning to False indicates that the medical record data is inconsistent and is tampered. the thash is a hash value stored in a leaf node where the patient a is located; and dhash is a hash value obtained by the medical record data of the patient a in the local database through an SHA256 algorithm.
Step 1-3: by utilizing a HyperLegger Fabric multi-channel scheme, nodes of a medical organization are positioned in the same channel, and all medical organization election main nodes are added into one channel to realize data sharing;
step 2: designing a medical record writing function of the electronic medical record system; selecting a MySQL database as a block chain database for storing the electronic medical record; the storage of the electronic medical record is divided into on-chain storage and off-chain storage, and the content of the electronic medical record comprises basic information of a patient, a record of admission and discharge, a consultation record, an operation record, a death record and informed consent information;
performing hash operation on the electronic medical record input by the user to form an abstract, and simultaneously performing digital signature on the abstract by using public keys of the patient and the doctor, wherein the signature result is used for verifying the identity of the user and controlling the access right of the user; storing the abstract, the signed result, the identity information of the patient and the medical record uploading time as transaction contents on a block chain;
storing unprocessed original medical record information of the reserved user in a MySQL database under the chain, extracting the medical record requested by the user from the database, calculating to obtain a summary, and comparing the summary with the summary stored in the block chain to verify the integrity of the data;
the on-chain storage comprises the following steps:
step S1: when a user stores an electronic disease in a link, a client node sends transaction content to an endorsement node, and the endorsement node performs signature verification;
step S2: after the signature is verified to be correct, the transaction is simulated and executed through an intelligent contract, and the transaction endorsement is returned;
step S3: the client node sends the transaction endorsement to an order node Orderer, the Orderer node orders and packages all transactions through an internal card consensus mechanism kafka and broadcasts blocks to all nodes, and the host node saves the blocks and updates the world state;
and step 3: for the query, modification and deletion operation of the historical medical record data of a certain patient, the data sharing and storage between two hospitals are realized;
step 3-1: before a user requests to inquire, modify and delete medical record data, identity information and a signature of a patient and a signature of a doctor mainly treating the requested medical record need to be sent to a cooperation network formed by verification nodes to verify the identity, the verification nodes decrypt signature results in the transactions by traversing the transactions stored in the Mercker tree merkle of all blocks and using the sent user signature and the signature of the doctor mainly treating the blocks, the access authority is controlled by comparing whether the decrypted digest and the uploaded digest are consistent, if so, the identity verification is passed, otherwise, the identity verification fails, and the user is denied access;
step 3-2: the cooperative network selects a main node from all nodes, the main node replaces a user to perform query, modification and deletion operations on data in a database, each operation is divided into two conditions of a home hospital and a cross-hospital, wherein a json text is used as a temporary storage carrier when all the cross-hospital operations perform data transfer, and data sharing and storage between two hospitals are realized through a json parser and a Map function;
the inquiry data is that a user initiates an inquiry request through a client and provides a patient signature, a signature of an attending doctor, keywords of medical record information to be modified and a home hospital of the medical record, and since the selected host nodes of each hospital are positioned in the same channel, namely, the host nodes carry out data interaction through the channel, the user can inquire the medical record information of the required patient through crossing the hospitals after passing the identity authentication; the main node of the local hospital judges whether the attribution of the inquired medical records is the home hospital or not, if so, the home hospital is inquired, and if not, the cross-hospital is inquired;
the hospital queries the identity information of the user and selects the main node in the step 3, after the user identity verification is passed, the main node inputs any keyword query of the patient name, the identity card, the treatment date and the disease condition type provided by the user in a query plate of the database to obtain corresponding data, and after the medical record integrity verification is passed, the main node sends the medical record data to the client and generates corresponding transaction to upload to the block;
the cross-hospital query is characterized in that a main node of a hospital sends medical record keywords and signatures of a patient to which the medical record belongs and a main treating doctor to the main node of a requested hospital through a channel, the identity of the main node of the requested hospital is verified through two signatures, after the verification is passed, the main node acquires information to be queried from a database and verifies the integrity, after the integrity verification is passed, the acquired data is transferred and stored into a db.json text and is sent to the main node of a hospital where a current user is located and then deleted, query transactions are generated and uploaded to a block, the main node of the hospital where the current user is located obtains the db.json text and then sends the db.json text to a client, and the query transactions are generated and uploaded to the block.
The modified data is that a user initiates a modification request through a client and provides a patient signature, a signature of a doctor for treating the patient, keywords of medical record information to be modified and a home hospital of the medical record, and since the selected host nodes of each hospital are positioned in the same channel, namely, the host nodes perform data interaction through the channels, the user can modify the medical record information of the requested patient across hospitals after passing identity verification, the host node of the local hospital judges whether the home location of the modified medical record is the home hospital, if so, the modified medical record is modified across hospitals, and if not, the modified medical record is modified across hospitals;
the home node verifies the identity information of the user and selects the main node in the step 3, after the user identity verification is passed, the main node acquires the requested medical record data from the database and returns the data to the client for the user to modify after the data integrity verification is passed, the data modified by the user is sent to the main node through the client and stored in the local database module, and the main node uploads the generated transaction to the block;
the cross-hospital modification is implemented, a main node of a local hospital sends a modification request, medical record keywords and two signatures to a main node of a requested hospital through a channel, the requested hospital main node verifies the identity of the requested hospital through the two signatures, after the access authority and the data integrity pass, required medical record data are transferred and stored into a db.json text, the text is sent to the requested hospital through the channel, the requested hospital stores data stored in the text into a local database through a json parser and a Map mapping function, corresponding transactions are uploaded to a block, then the db.json text is deleted, meanwhile, a signal which is written successfully is returned to the requested hospital, the requested medical record is deleted from the local database after the requested hospital receives the signal, and the generated transaction is uploaded to the block;
the data deletion is that a user initiates a deletion request through a client and provides a patient signature, a signature of an attending doctor, keywords of medical record information to be deleted and a home hospital of a medical record, and since the selected host nodes of each hospital are positioned in the same channel, namely, the host nodes carry out data interaction through the channels, the user can delete the medical record information of the requested patient across hospitals after passing identity verification, the host node of the local hospital judges whether the home location of the deleted medical record is the home hospital, if so, the home hospital is deleted, and if not, the home hospital is deleted across hospitals;
and the home node deletes the data by verifying the identity information of the user and selecting the main node in the step 3, after the user identity verification is passed, the main node inquires related medical record data of the patient through the keywords provided by the main node, deletes the data after the data integrity verification is passed, returns a result of successful deletion to the client side, and uploads the generated transaction to the block.
The cross-hospital deletion data is that the main node of the local hospital sends a deletion request, medical record keywords and two signatures to the main node of the requested hospital through a channel, the requested hospital main node verifies the identity of the requested hospital through the two signatures, relevant data are deleted after the identity verification and the data integrity verification are passed, generated transactions are uploaded to a block, a successful deletion result is returned to the requesting hospital, the requesting hospital uploads the generated transactions to the block and returns a successful deletion signal to a client.
Adopt the produced beneficial effect of above-mentioned technical scheme to lie in:
the invention provides a federation chain-based on-chain and off-chain collaborative electronic medical record data sharing method, which adopts a mode of storing abstracts of medical information on a chain and storing original medical data under the chain to verify the integrity of data during downloading and ensure the safety of the data. The uploaded medical record is digitally signed by using public keys of the patient and the doctor to control the access authority of the user, so that the privacy of the patient is protected, and meanwhile, the data is prevented from being tampered. The patent establishes a multi-union chain architecture, realizes cross-hospital safe data transmission by using a channel technology of a union chain, realizes medical data conversion among different hospital databases by using a json text as a temporary carrier, and solves the problem of difficult sharing due to a data format at present.
Drawings
FIG. 1 is a general flow chart of a method for sharing medical record data according to the present invention;
FIG. 2 is an overall architecture diagram of a system according to an embodiment of the present invention;
FIG. 3 is a flowchart illustrating a process for storing medical record data according to an embodiment of the present invention;
FIG. 4 is a flowchart illustrating operation of medical record data according to an embodiment of the present invention;
fig. 5 is a diagram illustrating cross-hospital data sharing between a database and json text conversion according to an embodiment of the present invention.
Detailed Description
The following detailed description of embodiments of the present invention is provided in connection with the accompanying drawings and examples. The following examples are intended to illustrate the invention but are not intended to limit the scope of the invention.
A federation chain-based on-chain and-chain-down collaborative electronic medical record data sharing method is disclosed, a general flow chart is shown in FIG. 1, a software platform in the embodiment is Hyperhedger Fabric, and the method comprises the following steps:
step 1: building a block chain platform, and building a block chain distributed hyper-ledger Fabric block chain network;
step 1-1: configuring an environment by utilizing an open source code of a HyperLegendr Fabric platform and setting a block data model;
in this embodiment, Go language is used to build a block chain. After the development environment is installed and configured, a structural body Block is defined as a data model of a Block, and data members of the structural body Block comprise Block height, Hash (Hash value), PrevBlockhash (previous Block Hash value), Timestamp (Timestamp), Merkle root, transactions (transactions within the Block) and numTransactions (transaction number of the Block). And defining a structure body Chain to represent the whole block Chain.
Step 1-2: designing a generating block function CreatBlock of a generating block, calculating a hash value function Calculatehash and a checking function amine for checking whether data are tampered;
the generate block function CreatBlock is as follows:
Newblock＝CreateBlock(blockHeaders,blockBody)
wherein Newblock is a created new block; CreatBlock is a block function created and is executed by a peer node (intelligent contract) module in a super ledger book; the block consists of a block header and a block body, wherein the block header (block headers) comprises the height (block height) of the block, the Hash value (Hash) of the block, the Hash value (prevBlockHash) of the previous block, a timeStamp (timeStamp) and the Hash value (merkleRoot) of the Merkle tree root; the block body (blockBody) includes transactions (transactions) within the block and transaction numbers (numTransactions) of the block.
The calculate hash value function calllatehash is as follows:
Hash＝SHA(h)
wherein SHA is a SHA256 function; h includes a predecessor chunk hash value (prevBlockHash), Merkle root hash value (merkleRoot), timeStamp (timeStamp); the Hash is the current block Hash value.
The test function, Examine, is shown below:
Consistent＝Examine(thash(a),dhash(a))
the Examine is a function for checking whether the two parameters are equal, the return value is of a Boolean type, and the result of the return of the constant is True, which indicates that the medical record data are Consistent and are not tampered; returning to False indicates that the medical record data is inconsistent and is tampered. the thash is a hash value stored in a leaf node where the patient a is located; and dhash is a hash value obtained by the medical record data of the patient a in the local database through an SHA256 algorithm.
Step 1-3: by utilizing the HyperLegendric multichannel scheme, the nodes of one medical organization are positioned in the same channel, and all the medical organization election host nodes are added into one channel to realize data sharing;
in this embodiment, a configxgen tool is used to generate a configuration transaction file of a newly created channel using a template in a configx.yaml configuration file. The anchor node configuration update file is used for configuring anchor nodes of the organization, and new channel files are generated based on the configx.yaml configuration file, and each organization needs to generate and pay attention to appoint a corresponding organization name. The network is started, a docker container is entered and a channel is created using a Peer channel create command. And adding the member node into the channel by using a Peer channeljoin command, and updating the configuration of the anchor node. And repeating the operations to establish a channel network of each medical institution. Therefore, the basic architecture of the multi-chain multi-channel blockchain network covering a plurality of medical structures is built.
Step 2: designing a medical record writing function of the electronic medical record system; selecting a MySQL database as a block chain database for storing the electronic medical record; the storage of the electronic medical record is divided into on-chain storage and off-chain storage, and the content of the electronic medical record comprises basic information of a patient, a record of admission and discharge, a consultation record, an operation record, a death record and informed consent information, as shown in fig. 3;
the on-chain storage is used for carrying out Hash operation on the electronic medical record input by the user through an SHA256 algorithm to form an abstract, meanwhile, public keys of a patient and a doctor are used for carrying out digital signature on the abstract, and a signature result is used for verifying the identity of the user, controlling the access authority of the user and ensuring the data security; storing the abstract, the signed result, the identity information of the patient and the medical record uploading time as transaction contents on a block chain;
storing unprocessed original medical record information of a reserved user in the chained MySQL database, extracting the medical record requested by the user from the database, performing SHA256 operation on the medical record to obtain a summary, and comparing the summary with the summary stored in the block chain to verify the integrity of the data so as to prevent the data from being tampered;
the on-chain storage comprises the following steps:
step S1: when a user stores an electronic disease in a link, a client node sends transaction content to an endorsement node, and the endorsement node performs signature verification;
step S2: after the signature is verified to be correct, the transaction is simulated and executed through an intelligent contract, and the transaction endorsement is returned;
step S3: the client node sends the transaction endorsement to an order node Orderer, the Orderer node orders and packages all transactions through an internal card consensus mechanism kafka and broadcasts blocks to all nodes, and the host node saves the blocks and updates the world state;
and step 3: for the query, modification and deletion operation of the historical medical record data of a certain patient, the data sharing and storage between two hospitals are realized; as shown in fig. 4;
in this embodiment, user n, hospital A, B, patients 1 and 2, and master nodes a and B are taken as examples, and it is assumed that user n is from hospital a, medical record information of patient 1 is stored in hospital a, and medical record information of patient 2 is stored in hospital B. The main node A is the main node of the hospital A, and the main node B is the main node of the hospital B.
Step 3-1: before a user n requests to operate certain medical record data, the identity information and the signature of a patient and the signature of a doctor mainly requesting the medical record are required to be sent to a cooperation network formed by verification nodes of a cooperation network of a hospital A through a client node in a superhedger fabric to verify the identity. The verification node controls the access authority of the transaction by traversing the transactions stored in the merkle trees of all the blocks, decrypting the signature result in the transaction by using the sent user signature and the signature of the main doctor, and comparing whether the decrypted digest is consistent with the uploaded digest. If the identity authentication is consistent, the identity authentication is passed, and the required data can be accessed; otherwise, the authentication fails, and the user is refused to access.
Step 3-2: hospital A elects a master node A from all verification nodes. The election process is realized on a Gossip layer, when a node is started, the node waits for the network to be stable and then starts to participate in the main node election, and the effective time of one main node election is 10 s. Therefore, the problem that the block cannot be distributed when the main node is forced to be set to be in fault can be effectively avoided. The main node performs related operations according to the request of the user, wherein when all the cross-hospital requests transmit medical data, the requested hospital extracts the required medical data from the database, converts the medical data into json language and stores the json language into db. And after the hospital is requested to obtain the db.json text, the data is transferred by using a json parser, the processed data is stored in the local data according to a Map mapping function, the db.json text is deleted, and the architecture diagram is shown in fig. 2.
The query data is that a user n initiates a query request through a client and provides a signature of a patient, a signature of an attending doctor, keywords of medical record information to be queried and a home hospital of the medical record. The selected host nodes of each hospital are located in the same channel, namely, the host nodes perform data interaction through the channel, so that the user n can query medical record information of a required patient in a hospital-crossing manner after passing the identity authentication. And the main node of the local hospital judges whether the attribution of the medical record to be checked is the home or not, and if so, the main node jumps to the home to check. If not, jumping to the cross-hospital query.
The home inquiry is that a user n wants to inquire the medical record of the patient 1. And (3) verifying the identity information of the user n and selecting the main node A through the step 3-1. After the identity verification is passed, the main node A enters a local database and inputs the keywords of medical record information provided by a user in a query board of the database to query so as to obtain the required electronic medical record and verify the integrity of the electronic medical record data. Under the condition of ensuring the integrity of the data, the main node A sends the electronic medical record data to the client, generates a transaction for a user n to inquire a patient 1 and uploads the transaction to a block;
the cross-hospital query is that user n wants to query the medical record of patient 2. When cross-hospital query is carried out, the main node A of the local hospital finds the medical record belonging hospital B provided by the user n through a channel, and sends the two signatures, the query request and the medical record information keywords sent by the user n to the main node B of the hospital B. And the master node B verifies the identity of the user n according to the two signatures, after the identity verification is passed, the master node B enters a database to inquire the medical record information of the corresponding patient 2 and verifies the integrity of the electronic medical record, after the integrity verification is passed, the medical record information of the patient 2 is transferred and stored into a db.json text, the text is sent to the master node A in a channel and then deleted, and meanwhile, the transaction of the user n for inquiring the patient 2 is generated and uploaded to a block. And the main node A sends the obtained db.json text to the client, and simultaneously generates a transaction for inquiring the patient 2 by the user n across hospitals and uploads the transaction to the block.
And the modification data is that the user n initiates a modification request through the client and provides the signature of the patient, the signature of the main doctor, the keywords of the medical record information to be modified and the home hospital of the medical record. The selected host nodes of each hospital are located in the same channel, namely, the host nodes perform data interaction through the channel, so that the user n can modify the medical record information of the requested patient through hospital crossing after passing the identity authentication. And the main node of the local hospital judges whether the attribution of the medical record modified by the main node is the home or not, and if so, the main node jumps to the home to modify. If not, jumping to cross-hospital modification.
The home hospital modifies, user n modifies the medical record for patient 1. And (3) verifying the identity information of the user n and selecting the main node A through the step 3-1. After the identity of the user n is verified, the main node A accesses a data plate of the hospital in the database through a medical record keyword provided by the user n, after the integrity of the medical record is verified, the historical data information of the patient 1 is returned to the client, the user n modifies the medical data to be modified through the client, the modified medical data is sent to the main node by the client after the modification is completed and stored in the data plate of the hospital A in the database, meanwhile, the transaction that the user n modifies the patient 1 is generated and uploaded to the block, and the medical record of the patient is effectively prevented from being modified;
the cross-hospital modification is that user n modifies the medical record for patient 2. When the cross-hospital modification is carried out, the main node A of the local hospital finds the medical record belonging hospital B provided by the user n through a channel, and sends two signatures, modification requests and medical record information keywords provided by the user n to the main node B of the hospital B. And the master node B verifies the identity information of the user n according to the two signatures, after the identity verification is passed, the master node B obtains historical medical record data of the patient 2 by inquiring the database, after the integrity verification of the medical record is passed, the medical record data is transferred and stored into a db.json text, and the text is sent to the master node A through a channel and then deleted. And the main node A writes the acquired db.json text information content into a local database through a json parser and a Map mapping function, deletes the text after uploading corresponding transactions to the block according to the step 2-1-1, and returns a signal of successful writing to the main node B. And after receiving the signal of successful writing, the master node B deletes the medical record data requested by the user n from the database, generates a cross-hospital transaction of the user n for modifying the patient 2 and uploads the cross-hospital transaction to the block. At the moment, the user n modifies the data through the home;
the deletion data is that the family n wants to delete the history medical record of the patient due to the death of the patient and the like, and can initiate a modification request through the client and provide the signature of the patient, the signature of the main doctor, the keyword of the medical record information to be deleted and the home hospital of the medical record. The selected host nodes of each hospital are located in the same channel, namely, the host nodes perform data interaction through the channel, so that the user n can delete the medical record information of the requested patient through hospital crossing after passing the identity authentication. The main node of the local hospital judges whether the home location of the deleted medical record is the home hospital or not, if so, the home hospital is deleted, and if not, the cross-hospital is deleted;
the deletion in the hospital is that the user n deletes the medical record of the patient 1. And (3) verifying the identity information of the user n and selecting the main node A through the step 3-1. After the identity verification is passed, the main node A queries the database through the provided medical record keywords to obtain the requested medical record data of the patient 1, verifies the data integrity, deletes the data after the verification is passed, generates a transaction that the user n deletes the patient 1, uploads the transaction to the block, and returns a message of successful deletion to the client.
The cross-hospital deletion data is that the user n deletes the medical record of the patient 2. When the hospital is deleted in a crossing way, the main node A finds the medical record provided by the user n to belong to the hospital B through a channel, and sends the two signatures, the deletion request and the medical record information keywords sent by the user n to the main node B of the hospital B. And the host node B of the hospital verifies the identity of the user n according to the two signatures, after the verification is passed, the host node B queries the local database board block through the provided medical record keywords to obtain the requested electronic medical record, deletes the requested medical record data from the database after the data integrity is verified, uploads the transaction of the user n for deleting the patient 2 to the block, and returns a message of successful deletion to the host node A through a channel. And the main node A uploads the transaction generated by the cross-hospital deletion data of the patient 2 to the block, and simultaneously returns a message of successful deletion to the client.
The foregoing description is only exemplary of the preferred embodiments of the disclosure and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the invention in the embodiments of the present disclosure is not limited to the specific combination of the above-mentioned features, but also encompasses other embodiments in which any combination of the above-mentioned features or their equivalents is made without departing from the inventive concept as defined above. For example, the above features and (but not limited to) technical features with similar functions disclosed in the embodiments of the present disclosure are mutually replaced to form the technical solution.
Claims (6)
1. A federation chain-based on-chain-under-chain collaborative electronic medical record data sharing method is characterized in that: the method comprises the following steps:
step 1: building a block chain platform, and building a block chain distributed hyper-ledger Fabric block chain network;
step 1-1: configuring an environment by utilizing an open source code of a HyperLegendr Fabric platform and setting a block data model;
step 1-2: designing a generating block function CreatBlock of a generating block, calculating a hash value function Calculatehash and a checking function amine for checking whether data are tampered;
step 1-3: by utilizing a HyperLegger Fabric multi-channel scheme, nodes of a medical organization are positioned in the same channel, and all medical organization election main nodes are added into one channel to realize data sharing;
step 2: designing a medical record writing function of the electronic medical record system; selecting a MySQL database as a block chain database for storing the electronic medical record; the storage of the electronic medical record is divided into on-chain storage and off-chain storage, and the content of the electronic medical record comprises basic information of a patient, a record of admission and discharge, a consultation record, an operation record, a death record and informed consent information;
performing hash operation on the electronic medical record input by the user to form an abstract, and simultaneously performing digital signature on the abstract by using public keys of the patient and the doctor, wherein the signature result is used for verifying the identity of the user and controlling the access right of the user; storing the abstract, the signed result, the identity information of the patient and the medical record uploading time as transaction contents on a block chain;
storing unprocessed original medical record information of the reserved user in a MySQL database under the chain, extracting the medical record requested by the user from the database, calculating to obtain a summary, and comparing the summary with the summary stored in the block chain to verify the integrity of the data;
and step 3: for the query, modification and deletion operation of the historical medical record data of a certain patient, the data sharing and storage between two hospitals are realized;
step 3-1: before a user requests to inquire, modify and delete medical record data, identity information and a signature of a patient and a signature of a doctor mainly treating the requested medical record need to be sent to a cooperation network formed by verification nodes to verify the identity, the verification nodes decrypt signature results in the transactions by traversing the transactions stored in the Mercker tree merkle of all blocks and using the sent user signature and the signature of the doctor mainly treating the blocks, the access authority is controlled by comparing whether the decrypted digest and the uploaded digest are consistent, if so, the identity verification is passed, otherwise, the identity verification fails, and the user is denied access;
step 3-2: the cooperative network selects a main node from all nodes, the main node replaces a user to perform query, modification and deletion operations on data in a database, each operation is divided into two conditions of a home hospital and a cross-hospital, json texts are used as temporary storage carriers when all the cross-hospital operations perform data transfer, and data sharing and storage between two hospitals are achieved through json resolvers and Map functions.
2. The method for sharing data of an electronic medical record in a federation chain-based uplink-downlink collaboration as claimed in claim 1, wherein the block function CreatBlock generated in step 1-2 is as follows:
Newblock＝CreateBlock(blockHeaders,blockBody)
wherein Newblock is a created new block; CreatBlock is a block function created and is executed by a peer node (intelligent contract) module in a super ledger book; the block consists of a block header and a block body, wherein the block header (block headers) comprises the height (block height) of the block, the Hash value (Hash) of the block, the Hash value (prevBlockHash) of the previous block, a timeStamp (timeStamp) and the Hash value (merkleRoot) of the Merkle tree root; the block body (blockBody) includes transactions (transactions) within the block and transaction numbers (numTransactions) of the block;
the calculate hash value function calllatehash is as follows:
Hash＝SHA(h)
wherein SHA is a SHA256 function; h includes a predecessor chunk hash value (prevBlockHash), Merkle root hash value (merkleRoot), timeStamp (timeStamp); the Hash is the Hash value of the current block;
the test function, Examine, is shown below:
Consistent＝Examine(thash(a),dhash(a))
the Examine is a function for checking whether the two parameters are equal, the return value is of a Boolean type, and the result of the return of the constant is True, which indicates that the medical record data are Consistent and are not tampered; returning False to indicate that the medical record data is inconsistent and is tampered, wherein the coast is a hash value stored in a leaf node where the patient a is located; and dhash is a hash value obtained by the medical record data of the patient a in the local database through an SHA256 algorithm.
3. The method for sharing data of the collaborative electronic medical record under the chain based on the federation chain as claimed in claim 1, wherein the step 2 of storing on the chain comprises the following steps:
step S1: when a user stores an electronic disease in a link, a client node sends transaction content to an endorsement node, and the endorsement node performs signature verification;
step S2: after the signature is verified to be correct, the transaction is simulated and executed through an intelligent contract, and the transaction endorsement is returned;
step S3: the client node sends the transaction endorsement to the order node Orderer, the Orderer node orders and packages all transactions through an internal card consensus mechanism kafka and broadcasts blocks to all nodes, and the main node saves the blocks and updates the world state.
4. The method for sharing data of an electronic medical record in an uplink-downlink collaboration based on a federation chain as claimed in claim 1, wherein the query data in step 3 is that a user initiates a query request through a client and provides a patient's signature and a signature of an attending doctor and a keyword of medical record information to be modified and a home hospital of the medical record, and since the selected host nodes in each hospital are located in the same channel, that is, the host nodes perform data interaction through the channel, the user can perform cross-hospital query on the medical record information of the patient after passing authentication; the main node of the local hospital judges whether the attribution of the inquired medical records is the home hospital or not, if so, the home hospital is inquired, and if not, the cross-hospital is inquired;
the hospital queries the identity information of the user and selects the main node in the step 3, after the user identity verification is passed, the main node inputs any keyword query of the patient name, the identity card, the treatment date and the disease condition type provided by the user in a query plate of the database to obtain corresponding data, and after the medical record integrity verification is passed, the main node sends the medical record data to the client and generates corresponding transaction to upload to the block;
the cross-hospital query is characterized in that a main node of a hospital sends medical record keywords and signatures of a patient to which the medical record belongs and a main treating doctor to the main node of a requested hospital through a channel, the identity of the main node of the requested hospital is verified through two signatures, after the verification is passed, the main node acquires information to be queried from a database and verifies the integrity, after the integrity verification is passed, the acquired data is transferred and stored into a db.json text and is sent to the main node of a hospital where a current user is located and then deleted, query transactions are generated and uploaded to a block, the main node of the hospital where the current user is located obtains the db.json text and then sends the db.json text to a client, and the query transactions are generated and uploaded to the block.
5. The method for sharing data of an electronic medical record in an uplink-downlink collaboration based on a federation chain as claimed in claim 1, wherein the modified data in step 3 is that a user initiates a modification request through a client and provides a patient's signature and a signature of a doctor in charge and keywords of medical record information to be modified and a home hospital of the medical record, because the selected host nodes of each hospital are located in the same channel, that is, the host nodes perform data interaction through the channel, thereby realizing that the user modifies the medical record information of the requested patient through hospital crossing after passing authentication, the host node of the local hospital judges whether the home location of the modified medical record is the home hospital, if so, modifies the home hospital, otherwise, modifies the medical record crossing;
the home node verifies the identity information of the user and selects the main node in the step 3, after the user identity verification is passed, the main node acquires the requested medical record data from the database and returns the data to the client for the user to modify after the data integrity verification is passed, the data modified by the user is sent to the main node through the client and stored in the local database module, and the main node uploads the generated transaction to the block;
the cross-hospital modification method comprises the steps that a main node of a local hospital sends a modification request, medical record keywords and two signatures to a main node of a requested hospital through a channel, the identity of the requested hospital main node is verified through the two signatures, after access authority and data integrity pass, required medical record data are transferred and stored into a db.json text, the text is sent to the requesting hospital through the channel, the requesting hospital stores data stored in the text into a local database through a json parser and a Map mapping function, corresponding transactions are uploaded to a block, the db.json text is deleted, meanwhile, a signal which is written successfully is returned to the requested hospital, the requested medical record is deleted from the local database after the requested hospital receives the signal, and the generated transaction is uploaded to the block.
6. The method for sharing data of an electronic medical record in an uplink-downlink collaboration based on an alliance chain as claimed in claim 1, wherein the data deletion in step 3 is that a user initiates a deletion request through a client and provides a patient's signature, a signature of an attending doctor, a keyword of medical record information to be deleted, and a home hospital of the medical record, because the selected host nodes of each hospital are located in the same channel, that is, the host nodes perform data interaction through the channel, thereby realizing that the user deletes the medical record information of the requested patient through hospital crossing after passing identity verification, the host node of the local hospital judges whether the home location of the deleted medical record is the home hospital, if yes, deletes the home hospital crossing;
the home deleted data passes through the identity information of the verification user and the selection main node in the step 3, after the user identity verification passes, the main node inquires related medical record data of the patient through keywords provided by the main node, deletes the data after the data integrity verification passes, returns a result of successful deletion to the client side, and uploads the generated transaction to a block;
the cross-hospital deletion data is that the main node of the local hospital sends a deletion request, medical record keywords and two signatures to the main node of the requested hospital through a channel, the requested hospital main node verifies the identity of the requested hospital through the two signatures, relevant data are deleted after the identity verification and the data integrity verification are passed, generated transactions are uploaded to a block, a successful deletion result is returned to the requesting hospital, the requesting hospital uploads the generated transactions to the block and returns a successful deletion signal to a client.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011449779.7A CN112559627B (en) | 2020-12-11 | 2020-12-11 | Method for sharing electronic medical record data in cooperation with each other on chain and under chain based on alliance chain |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011449779.7A CN112559627B (en) | 2020-12-11 | 2020-12-11 | Method for sharing electronic medical record data in cooperation with each other on chain and under chain based on alliance chain |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112559627A true CN112559627A (en) | 2021-03-26 |
| CN112559627B CN112559627B (en) | 2023-08-04 |
Family
ID=75061411
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011449779.7A Active CN112559627B (en) | 2020-12-11 | 2020-12-11 | Method for sharing electronic medical record data in cooperation with each other on chain and under chain based on alliance chain |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112559627B (en) |
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113223706A (en) * | 2021-05-31 | 2021-08-06 | 广东粤信智能科技有限公司 | Alliance chain data building method, storage medium and system for multiple hospitals |
| CN113658649A (en) * | 2021-07-22 | 2021-11-16 | 西安鹫一卓越软件科技有限公司 | Block chain-based electronic medical record information tamper-proofing method and system |
| CN113660206A (en) * | 2021-07-12 | 2021-11-16 | 北京理工大学 | Cross-organization access control method based on alliance chain and multiple signatures |
| CN113793665A (en) * | 2021-08-27 | 2021-12-14 | 汕头大学 | Novel electronic medical record sharing method fusing block chains and real behavior characteristics |
| CN113821564A (en) * | 2021-09-09 | 2021-12-21 | 湖南大学 | Heterogeneous parallel block chain and on-chain data and under-chain contract cooperation method thereof |
| CN114189526A (en) * | 2021-11-01 | 2022-03-15 | 北京中合谷投资有限公司 | Centralized scheduling algorithm of distributed network |
| CN114357081A (en) * | 2022-01-05 | 2022-04-15 | 南昌航空大学 | Block chain construction method of net structure |
| CN114374525A (en) * | 2021-04-14 | 2022-04-19 | 南京质子链科技有限公司 | Block chain-based electronic film secure sharing system and method |
| CN114499872A (en) * | 2021-12-24 | 2022-05-13 | 山东浪潮工业互联网产业股份有限公司 | Industrial internet-based star fire chain cross-linking method and equipment |
| CN116168794A (en) * | 2023-04-23 | 2023-05-26 | 成都本千医疗科技有限公司 | Big data supervision's electronic medical record collection management platform |
| CN117037988A (en) * | 2023-08-22 | 2023-11-10 | 广州视景医疗软件有限公司 | Electronic medical record storage method and device based on blockchain |
| CN117540432A (en) * | 2024-01-05 | 2024-02-09 | 河北数港科技有限公司 | Data privacy protection method and system for Internet |
| CN114499872B (en) * | 2021-12-24 | 2024-05-28 | 浪潮工业互联网股份有限公司 | Starfire chain crossing method and device based on industrial Internet |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109886027A (en) * | 2019-01-14 | 2019-06-14 | 湘潭大学 | A kind of medical data secure sharing method based on block chain |
| CN110135186A (en) * | 2019-04-11 | 2019-08-16 | 浙江工业大学 | Medical data transaction and sharing method based on block chain technology |
| CN110414203A (en) * | 2019-07-26 | 2019-11-05 | 郑州大学 | A kind of internet medical treatment identity identifying method based on block chain technology |
| CN110797099A (en) * | 2019-10-28 | 2020-02-14 | 河北北方学院 | Medical data sharing method and system based on block chain |
| WO2020141584A1 (en) * | 2019-01-06 | 2020-07-09 | 株式会社フューチャーアイ | Management system and program |
| CN111403009A (en) * | 2019-01-02 | 2020-07-10 | 中国移动通信有限公司研究院 | Hospital satisfaction investigation method and system based on block chain and computer readable storage medium |
| WO2020147478A1 (en) * | 2019-01-14 | 2020-07-23 | 阿里巴巴集团控股有限公司 | Block chain-based user feature value acquisition and application method and apparatus |
| CN111627542A (en) * | 2020-05-29 | 2020-09-04 | 深圳市易链信息技术有限公司 | Block chain-based medical information sharing method, system and readable storage medium |
| CN111816271A (en) * | 2020-07-03 | 2020-10-23 | 深圳市易链信息技术有限公司 | Block chain-based electronic medical record sharing method and system and readable storage medium |
-
2020
- 2020-12-11 CN CN202011449779.7A patent/CN112559627B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111403009A (en) * | 2019-01-02 | 2020-07-10 | 中国移动通信有限公司研究院 | Hospital satisfaction investigation method and system based on block chain and computer readable storage medium |
| WO2020141584A1 (en) * | 2019-01-06 | 2020-07-09 | 株式会社フューチャーアイ | Management system and program |
| CN109886027A (en) * | 2019-01-14 | 2019-06-14 | 湘潭大学 | A kind of medical data secure sharing method based on block chain |
| WO2020147478A1 (en) * | 2019-01-14 | 2020-07-23 | 阿里巴巴集团控股有限公司 | Block chain-based user feature value acquisition and application method and apparatus |
| CN110135186A (en) * | 2019-04-11 | 2019-08-16 | 浙江工业大学 | Medical data transaction and sharing method based on block chain technology |
| CN110414203A (en) * | 2019-07-26 | 2019-11-05 | 郑州大学 | A kind of internet medical treatment identity identifying method based on block chain technology |
| CN110797099A (en) * | 2019-10-28 | 2020-02-14 | 河北北方学院 | Medical data sharing method and system based on block chain |
| CN111627542A (en) * | 2020-05-29 | 2020-09-04 | 深圳市易链信息技术有限公司 | Block chain-based medical information sharing method, system and readable storage medium |
| CN111816271A (en) * | 2020-07-03 | 2020-10-23 | 深圳市易链信息技术有限公司 | Block chain-based electronic medical record sharing method and system and readable storage medium |
Non-Patent Citations (4)
| Title |
|---|
| SHUYUN SHI 等: "Applications of blockchain in ensuring the security and privacy of electronic health record systems: A survey", 《COMPUTERS & SECURITY》, pages 1 - 15 * |
| 张超 等: "Medical Chain:联盟式医疗区块链系统", 《自动化学报》, vol. 45, no. 08, pages 1495 - 1510 * |
| 潘恒 等: "一种病人可控的电子病历安全访问方案", 《应用科学学报》, vol. 38, no. 01, pages 127 - 138 * |
| 潘时清 等: "基于联盟区块链的电子病历系统模型研究", 《网络安全技术与应用》, no. 02, pages 32 - 34 * |
Cited By (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114374525A (en) * | 2021-04-14 | 2022-04-19 | 南京质子链科技有限公司 | Block chain-based electronic film secure sharing system and method |
| CN113223706A (en) * | 2021-05-31 | 2021-08-06 | 广东粤信智能科技有限公司 | Alliance chain data building method, storage medium and system for multiple hospitals |
| CN113660206A (en) * | 2021-07-12 | 2021-11-16 | 北京理工大学 | Cross-organization access control method based on alliance chain and multiple signatures |
| CN113658649A (en) * | 2021-07-22 | 2021-11-16 | 西安鹫一卓越软件科技有限公司 | Block chain-based electronic medical record information tamper-proofing method and system |
| CN113793665A (en) * | 2021-08-27 | 2021-12-14 | 汕头大学 | Novel electronic medical record sharing method fusing block chains and real behavior characteristics |
| CN113821564A (en) * | 2021-09-09 | 2021-12-21 | 湖南大学 | Heterogeneous parallel block chain and on-chain data and under-chain contract cooperation method thereof |
| CN113821564B (en) * | 2021-09-09 | 2023-08-18 | 湖南大学 | Heterogeneous parallel blockchain and method for coordinating on-chain data and under-chain contracts thereof |
| CN114189526A (en) * | 2021-11-01 | 2022-03-15 | 北京中合谷投资有限公司 | Centralized scheduling algorithm of distributed network |
| CN114499872A (en) * | 2021-12-24 | 2022-05-13 | 山东浪潮工业互联网产业股份有限公司 | Industrial internet-based star fire chain cross-linking method and equipment |
| CN114499872B (en) * | 2021-12-24 | 2024-05-28 | 浪潮工业互联网股份有限公司 | Starfire chain crossing method and device based on industrial Internet |
| CN114357081A (en) * | 2022-01-05 | 2022-04-15 | 南昌航空大学 | Block chain construction method of net structure |
| CN116168794A (en) * | 2023-04-23 | 2023-05-26 | 成都本千医疗科技有限公司 | Big data supervision's electronic medical record collection management platform |
| CN117037988A (en) * | 2023-08-22 | 2023-11-10 | 广州视景医疗软件有限公司 | Electronic medical record storage method and device based on blockchain |
| CN117037988B (en) * | 2023-08-22 | 2024-05-17 | 广州视景医疗软件有限公司 | Electronic medical record storage method and device based on blockchain |
| CN117540432A (en) * | 2024-01-05 | 2024-02-09 | 河北数港科技有限公司 | Data privacy protection method and system for Internet |
| CN117540432B (en) * | 2024-01-05 | 2024-03-19 | 河北数港科技有限公司 | Data privacy protection method and system for Internet |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112559627B (en) | 2023-08-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112559627A (en) | Alliance chain-based on-chain-under-chain collaborative electronic medical record data sharing method | |
| US11824970B2 (en) | Systems, methods, and apparatuses for implementing user access controls in a metadata driven blockchain operating via distributed ledger technology (DLT) using granular access objects and ALFA/XACML visibility rules | |
| US11899817B2 (en) | Systems, methods, and apparatuses for storing PII information via a metadata driven blockchain using distributed and decentralized storage for sensitive user information | |
| CN109791591B (en) | Method and system for identity and credential protection and verification via blockchain | |
| CN110532323B (en) | Student identity information processing method and device in block chain network, electronic equipment and storage medium | |
| US11764950B2 (en) | System or method to implement right to be forgotten on metadata driven blockchain using shared secrets and consensus on read | |
| US11431693B2 (en) | Systems, methods, and apparatuses for seeding community sidechains with consent written onto a blockchain interfaced with a cloud based computing environment | |
| CN110991622B (en) | Machine learning model processing method based on block chain network and node | |
| US20190236562A1 (en) | Systems, methods, and apparatuses for implementing document interface and collaboration using quipchain in a cloud based computing environment | |
| CN111177252B (en) | Service data processing method and device | |
| CN110599095B (en) | Block chain network-based hazardous waste treatment method and node of block chain network | |
| CN109347941A (en) | A kind of data sharing platform and its implementation based on block chain | |
| CN112069165A (en) | Document redaction and coordination | |
| CN112835612A (en) | Electronic document version management method and device based on block chain | |
| CN102170440A (en) | Method suitable for safely migrating data between storage clouds | |
| JP2008527478A (en) | Mediation server, method and network for querying and referencing medical information | |
| CN111506589B (en) | Block chain data service system, access method and storage medium based on alliance chain | |
| CN111831740A (en) | Synchronization of peers | |
| JP2013065216A (en) | Document management server system | |
| CN111798233A (en) | Linking of tokens | |
| CN115185914A (en) | Data sharing method and computing device based on uplink and downlink data cooperation | |
| Liu et al. | A consortium medical blockchain data storage and sharing model based on ipfs | |
| US11870920B2 (en) | Graph models of relationships between data stored in blocks on distributed ledgers that are learned through machine learning and platforms for creating, cataloging, and storing the same | |
| CN114911795A (en) | Medical data processing method and application | |
| CN113706283A (en) | Double-chain retrieval and tracing method based on real estate transaction |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |