Medical privacy data storage method and device, storage medium and electronic equipment

Abstract

The invention provides a medical privacy data storage method and device, a storage medium and electronic equipment, and is applied to a block chain node, and the method comprises the following steps: receiving a medical privacy data storage request sent by a data provider; initiating corresponding identity authentication to the data provider, wherein the identity authentication is used for judging whether the data provider is a preset user; and under the condition that the data provider is determined to be a preset user according to the identity authentication, acquiring medical privacy data provided by the data provider, performing local persistent storage on the medical privacy data, and performing desensitization processing on the medical privacy data and then publishing the data to a corresponding block chain.

Description

Technical Field

[0001] One or more embodiments of the present specification relate to the field of computer technology, and in particular, to a method, device, storage medium, and electronic device for storing medical privacy data. Background Art

[0002] With the rapid development of information technology, people have gained unprecedented convenience. Taking the medical industry as an example, more and more data are transitioning from paper to electronic versions, and the way of information input has also changed from handwriting to keyboard input and voice input. Based on the rapid development of electronicization, the amount of medical privacy data is also increasing. Medical privacy data storage usually includes multimedia information in various formats such as medical records, identity information, and test results.

[0003] In related technologies, in order to store the above-mentioned medical privacy data, it is usually necessary to build an independent central database or cloud database for the hospital, but this can easily lead to data leakage and data tampering; and tertiary hospitals all have HIS (Hospital Information System), LIS (Laboratory Information Management System), PACS (Picture Archiving and Communication Systems) and other systems, but they are all responsible for independent daily work management, which makes medical privacy data limited and can often only be used within the hospital, and its data utilization rate is low. Summary of the invention

[0004] In order to overcome the problems existing in the related art, this specification provides a storage method, device, storage medium and electronic device for medical privacy data.

[0005] According to a first aspect of an embodiment of this specification, a method for storing medical privacy data is provided, which is applied to a blockchain node, and the method includes: Receiving a storage request for the medical privacy data sent by a data provider; Initiate corresponding identity authentication for the data provider, the identity authentication is used to determine whether the data provider is a preset user; When it is determined that the data provider is a preset user according to the identity authentication, the medical privacy data provided by the data provider is obtained, and the medical privacy data is locally persistently stored, and the medical privacy data is anonymized and then published to the corresponding blockchain.

[0006] According to a second aspect of the embodiments of this specification, a storage device for medical privacy data is provided, which is applied to a blockchain node, and the device includes: A receiving unit, configured to receive a storage request for the medical privacy data sent by a data provider; An authentication unit, used to initiate a corresponding identity authentication for the data provider, wherein the identity authentication is used to determine whether the data provider is a preset user; A storage unit is used to obtain the medical privacy data provided by the data provider when it is determined that the data provider is a preset user according to the identity authentication, and to locally store the medical privacy data persistently, and to publish the medical privacy data to the corresponding blockchain after desensitizing it.

[0007] According to a third aspect of the embodiments of this specification, there is provided an electronic device, including: A processor; a memory for storing processor executable instructions; wherein the processor is configured to implement the steps of the method described in the first aspect above.

[0008] According to a fourth aspect of the embodiments of this specification, a computer-readable storage medium is provided, on which executable instructions are stored; wherein, when the instructions are executed by a processor, the steps of the method described in the first aspect above are implemented.

[0009] Based on the above embodiments of this specification, it can be known that: The storage method of medical privacy data described in this specification introduces blockchain technology. For data providers who have passed identity authentication, the corresponding medical privacy data can be stored in the blockchain node (local persistence), so that the data provider does not need to store medical privacy data, which relieves the storage pressure of hospitals and other data providers. Furthermore, the security of medical privacy data is protected by the characteristics of blockchain that cannot be tampered with and decentralized. In addition, the blockchain node desensitizes the medical privacy data before publishing it to the blockchain. Even if the medical privacy data published to the blockchain is obtained by criminals, the desensitization process can avoid data leakage.

[0010] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present specification. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the specification and, together with the description, serve to explain the principles of the specification.

[0012] Figure 1 It is a schematic diagram of the architecture of a medical privacy data system provided by an exemplary embodiment of this specification.

[0013] Figure 2 It is a flowchart of a method for storing medical privacy data provided by an exemplary embodiment of this specification.

[0014] Figure 3 It is a schematic structural diagram of an electronic device provided by an exemplary embodiment of this specification.

[0015] Figure 4 It is a block diagram of a storage device for medical privacy data provided by an exemplary embodiment of this specification. Implementation

[0016] Here, exemplary embodiments will be described in detail, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementations described in the following exemplary embodiments do not represent all implementations consistent with one or more embodiments of this specification. Instead, they are only examples of devices and methods consistent with some aspects of one or more embodiments of this specification.

[0017] It should be noted that in other embodiments, the steps of the corresponding method are not necessarily performed in the order shown and described in this specification. In some other embodiments, the steps included in the method may be more or less than those described in this specification. In addition, the single step described in this specification may be decomposed into multiple steps for description in other embodiments; and the multiple steps described in this specification may also be combined into a single step for description in other embodiments. It should be understood that although the terms first, second, third, etc. may be used in this specification to describe various information, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of this specification, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein can be interpreted as "at the time of" or "when" or "in response to determination".

[0018] In order to facilitate understanding of the storage method of medical privacy data described in this specification, the following specification explains blockchain technology.

[0019] Blockchain is generally divided into three types: public blockchain, private blockchain and consortium blockchain. In addition, there can also be a combination of the above types, such as private blockchain + consortium blockchain, consortium blockchain + public blockchain, etc.

[0020] Among them, the public chain has the highest degree of decentralization. Participants who join the public chain (also known as nodes in the blockchain) can read data records on the chain, participate in transactions, and compete for the right to record new blocks. Moreover, each node can freely join or exit the network and perform related operations.

[0021] On the contrary, the private chain has a network whose write permission is controlled by a certain organization or institution, and the data read permission is regulated by the organization. In simple terms, a private chain can be a weakly centralized system with strict restrictions on nodes and a small number of nodes. This type of blockchain is more suitable for use within a specific institution.

[0022] The consortium chain is a blockchain between the public chain and the private chain, which can achieve "partial decentralization". Each node in the consortium chain usually has a corresponding entity or organization; the nodes join the network through authorization and form a stakeholder alliance to jointly maintain the operation of the blockchain.

[0023] Based on the basic characteristics of blockchain, blockchain is usually composed of several blocks. In each of these blocks, a timestamp corresponding to the creation time of the block is recorded. All blocks strictly follow the timestamp recorded in the block to form a data chain that is ordered in time.

[0024] For data generated outside the chain, it can be constructed into a standard transaction format supported by the blockchain, and then published to the blockchain. The node devices in the blockchain will reach a consensus on the transaction. After reaching a consensus, the node devices in the blockchain that serve as accounting nodes will package the transaction into a block and store it persistently in the blockchain.

[0025] Among them, the consensus algorithms supported in blockchain can include: The first type of consensus algorithm is the consensus algorithm in which node devices need to compete for the right to record in each accounting cycle; for example, consensus algorithms such as Proof of Work (POW), Proof of Stake (POS), and Delegated Proof of Stake (DPOS); The second type of consensus algorithm is the consensus algorithm that elects accounting nodes in advance for each accounting cycle (without the need to compete for accounting rights); for example, consensus algorithms such as Practical Byzantine Fault Tolerance (PBFT).

[0026] As mentioned above, no matter which consensus algorithm shown above is adopted by the blockchain, the accounting node of this round can package the received transactions to generate candidate blocks, and send the generated candidate blocks or the block headers of the candidate blocks to other node devices for consensus verification. If other node devices receive the candidate blocks or the block headers of the candidate blocks and verify that there are no problems, the candidate blocks can be appended to the end of the original blockchain as the latest blocks, thereby completing the accounting process of the blockchain. In the process of other nodes verifying the new blocks or block headers sent by the accounting nodes, they can also execute the transactions contained in the blocks.

[0027] Below, this specification describes in detail a method for storing medical privacy data described in this specification in combination with the above-mentioned blockchain technology.

[0028] Figure 1 is a schematic diagram of the architecture of a medical privacy data system provided by an exemplary embodiment of this specification, such as Figure 1 As shown, the system architecture may include a computing device 101 on the data provider side (such as a hospital), a server side 102, and at least one blockchain system; for example, blockchain system 103, blockchain system 104, and blockchain system 105.

[0029] In one embodiment, the data provider side computing device 101 may include various types of computing devices; for example, it may include PC terminal devices, mobile terminal devices, Internet of Things devices, and other forms of smart devices with certain computing capabilities. In one embodiment, at least some of the computing devices in the data provider side (or client side) terminal device 101 may be connected to the server side 102 through various communication networks; for example, Figure 1 Device 1 and device 2 shown in the figure are connected to the server 102. It is not difficult to understand that some of the terminal devices in the data provider side terminal device 101 may not be connected to the server 102, but directly connected to the blockchain system through various communication networks as blockchain nodes; for example, Figure 1 The device 4 shown in the figure can be connected to the blockchain system as a blockchain node.

[0030] Among them, the above-mentioned communication network may include wired and / or wireless communication networks; for example, it may be a local area network (LAN), a wide area network (WAN), the Internet or a combination thereof implemented based on a wired access network or a wireless access network (such as a mobile cellular network) provided by an operator.

[0031] In one embodiment, the data provider-side computing device 101 may also include one or more user-side servers; for example, Figure 1 At least some of the computing devices in the data provider-side terminal device 101 may be connected to the user-side server, and the user-side server may be further connected to the above-mentioned service end 102; for example, Figure 1 Device 1 and device 2 shown in FIG. 1 are connected to device 5 , and device 5 is further connected to server 102 .

[0032] In one embodiment, the user-side server may be implemented by a service entity that has built a user account system; the service entity may include an operating entity of a service carrier that provides various online and / or offline services to users; The service carrier may include a service carrier in the form of software or a service carrier in the form of hardware. In one embodiment, the service carrier may include various client software that provides online Internet services; for example, a website, a webpage, an APP, etc.

[0033] Correspondingly, the above-mentioned operating entity may include the operator corresponding to the above-mentioned service carrier; for example, the above-mentioned operating entity may include individuals, organizations, companies and enterprises that operate and manage the above-mentioned service carrier, etc.

[0034] In one embodiment, the server 102 may also be connected to one or more blockchain systems via various communication networks; for example, Figure 1 The server end 102 shown in the figure can be connected to the blockchain system 103, the blockchain system 104, the blockchain system 105, etc.

[0035] In one embodiment, each blockchain system may maintain one or more blockchains (e.g., a public blockchain, a private blockchain, a consortium blockchain, etc.), and include multiple blockchain nodes for hosting the one or more blockchains; for example, Figure 1 The blockchain nodes 1, 2, 3, 4, and i shown in the figure can jointly carry one or more blockchains. Cross-chain data access can also be performed between the blockchains included in each blockchain system and between each blockchain system.

[0036] In one embodiment, the blockchain node may include a full node and a light node. The full node may download all blockchain transactions contained in each block in the blockchain, and may perform consensus verification on the blockchain transactions contained in each blockchain according to the blockchain consensus algorithm installed.

[0037] Instead of downloading the entire blockchain, a light node can only download the header data of each block in the blockchain and use the data contained in the header as a verification root to verify the authenticity of blockchain transactions. Light nodes can be attached to full nodes to access more functions of the blockchain.

[0038] For example, Figure 1 Each blockchain node in the blockchain system 103 shown in FIG. 1 can serve as a full node; and Figure 1 The device 4 directly connected to the blockchain system shown in the figure can be used as a light node and attached to each full node in the blockchain system 103.

[0039] In one implementation, a blockchain node can be a physical device or a virtual device implemented in a server or server cluster; for example, a blockchain node device can be a physical host in a server cluster, or a virtual machine created by virtualizing the hardware resources of a server or server cluster based on virtualization technology. Each blockchain node can be connected to form a network through various types of communication methods (such as TCP / IP) to carry one or more blockchains.

[0040] Figure 2 This is a flowchart of a method for storing medical privacy data provided by an exemplary embodiment of this specification, which can be applied to a blockchain node and specifically includes the following steps:

[0041] Step 202: Receive a storage request for the medical privacy data sent by a data provider.

[0042] The medical privacy data described in this specification may refer to the patient's medical record data, the patient's identity data, the test result data and / or the privacy data of the diagnosis and treatment application. For example, medical record data is an electronic record of the medical activities such as the occurrence, development and prognosis of the patient's disease, examination, diagnosis and treatment by medical personnel. It is also an electronic medical health file of the patient written in the prescribed format and requirements by summarizing, organizing and comprehensively analyzing the collected data. The patient's identity data may refer to the patient's age, gender, home address, contact number and other data. The test result data may refer to the patient's blood routine test results, CT (computer tomography) results, MRI (magnetic resonance imaging) results, etc., and the privacy data of the diagnosis and treatment application can be diverse. For example, taking digital medicine as an example, in the field of insomnia correction, digital medical technology can provide patients with corresponding diagnosis and treatment applications (APP or mini-programs or H5, etc.). When the corresponding patients use the above applications for treatment, they will leave corresponding privacy data, such as sleep duration, insomnia duration, deep sleep duration, etc.

[0043] The data provider may refer to an institution such as a hospital, clinic, or enterprise that collects the above-mentioned medical privacy data. After obtaining the above-mentioned medical privacy data, the data provider may send a storage request for the medical privacy data to the corresponding blockchain node. It should be noted that because the medical privacy data described in this specification is stored locally by the blockchain node rather than the data provider, the data provider may transmit the medical privacy data to the blockchain node in real time after obtaining it, without performing storage operations, thereby saving the storage space of the data provider.

[0044] Step 204: initiate a corresponding identity authentication for the data provider, wherein the identity authentication is used to determine whether the data provider is a preset user.

[0045] After receiving the storage request for medical privacy data sent by the data provider, the blockchain node can initiate identity authentication to the data provider in order to ensure the security and privacy of the data, thereby determining that the data provider is a legitimate user. Specifically, the identity authentication method can be diverse, for example, initiating face recognition authentication, voiceprint authentication, fingerprint authentication, etc. to the data provider, or the storage request sent by the data provider can carry the corresponding identity key, and the blockchain node can store the identity key set corresponding to the authenticated user. When the identity key carried in the storage request matches the identity key set, the identity authentication can be confirmed to be passed. For another example, the storage request can carry the corresponding identity identifier. After receiving the storage request, the blockchain node can send the corresponding verification code SMS to the registered mobile phone number corresponding to the identity identifier. After the data recipient fills in the corresponding verification code in the verification code SMS, the blockchain node verifies it. This manual does not limit the method of identity authentication.

[0046] Step 206: When it is determined that the data provider is a preset user according to the identity authentication, obtain the medical privacy data provided by the data provider, store the medical privacy data locally and persistently, and publish the medical privacy data to the corresponding blockchain after desensitizing it.

[0047] After passing the identity authentication as described above, it can be determined that the data provider is the preset user. At this time, the blockchain node can obtain the medical privacy data provided by the data provider. It can be understood that because the blockchain node performs local persistence operations, the data provider may not perform local persistence operations, that is, transmit the medical privacy data to the blockchain node in real time, or the data provider may first perform temporary storage. After transmitting the medical privacy data to the blockchain node, the data provider may delete the data to save its storage space.

[0048] After receiving the medical privacy data sent by the data provider, the blockchain node can perform local persistence operations on the medical privacy data, thereby storing the medical privacy data locally. At the same time, the blockchain node can desensitize the above medical privacy data, thereby deforming the data through desensitization rules to achieve reliable protection of sensitive privacy data. Then the desensitized medical privacy data is published to the blockchain.

[0049] In one embodiment, the desensitization process described in this specification may refer to performing a hash operation, that is, performing a hash operation on the medical privacy data to obtain the corresponding summary data; and publishing the summary data to the corresponding blockchain. A hash operation is to accept an input of unlimited length and return an output of fixed length. It can be understood as a message digest algorithm that compresses the message or data to make it smaller and has a fixed format. It has three major characteristics: one is input sensitivity, that is, a slight change in the input can lead to a large difference in the output; the second is uniqueness, that is, there are basically no two different inputs that get the same output; the third is fast forward and difficult reverse, that is, the forward operation speed of the hash operation is extremely fast, but it is extremely difficult to reverse the input from the output. The specific hash algorithm may include at least one of the following: MD5, SHA-1, SHA-256, SHA-384, SHA-512, among which SHA-256 can generate a 256-bit hash value with high security. Of course, this specification does not limit the specific hash algorithm used. Through hash calculation, the blockchain node can publish the corresponding summary data instead of medical privacy data, thereby improving the security of the data. Of course, the blockchain node locally stores the medical privacy data that has not been desensitized.

[0050] In one embodiment, the blockchain node described in this specification can publish the anonymized medical privacy data to the blockchain by initiating a transaction as described above, that is, the blockchain node can initiate a medical privacy data storage transaction to the blockchain, so that the blockchain calls the corresponding smart contract to store the anonymized medical privacy data to the blockchain. In other words, after the transaction is initiated, the node devices in the blockchain can reach a consensus on the transaction, and after reaching a consensus, the node device serving as the accounting node in the blockchain will package the transaction into a block and store it persistently in the blockchain.

[0051] As mentioned above, in the relevant technology, medical privacy data has limitations and can often only be used within the hospital, and its data utilization rate is low. In view of this, this specification proposes a medical privacy data sharing method, that is, the blockchain node can respond to the data acquisition request sent by the data demander and initiate a security identity authentication to the data demander; if the security identity authentication is passed, the corresponding medical privacy data and the hash algorithm corresponding to the desensitization processing are sent to the data demander. The method of security identity authentication can be the same as the identity authentication method described above. Alternatively, the data provider can specify the data demander, that is, only the data demander recognized by the data provider can access and obtain the medical privacy data provided by the data provider. The reason why the corresponding hash algorithm is provided to the data demander is that the data demander can determine the data reliability. That is, after the data demander receives the medical privacy data sent by the blockchain node and the corresponding hash algorithm for desensitization processing, the data demander can perform a hash operation to obtain the corresponding hash value (summary information). The data demander can then compare the hash value calculated by itself with the hash value stored on the blockchain. Assuming the results are consistent, it can be ensured that the medical privacy data obtained by the data demander has not been tampered with and is the original data originally received by the blockchain node; assuming the results are inconsistent, it can be considered that the medical privacy data received by the data demander is not the original data, thereby further improving the reliability of the data.

[0052] Based on the above embodiments, it can be seen that the storage method of medical privacy data described in this specification introduces blockchain technology. For data providers who have passed identity authentication, the corresponding medical privacy data can be stored in the blockchain node (local persistence), so that the data provider does not need to store medical privacy data, which relieves the storage pressure of hospitals and other data providers. Furthermore, the security of medical privacy data is protected by the characteristics of blockchain that cannot be tampered with and decentralized. In addition, the blockchain node desensitizes the medical privacy data before publishing it to the blockchain. Even if the medical privacy data published to the blockchain is obtained by criminals, the desensitization process can avoid data leakage.

[0053] Corresponding to the above method embodiments, this specification also provides device embodiments.

[0054] Figure 3 This is a schematic structural diagram of an electronic device provided by an exemplary embodiment. Please refer to Figure 3At the hardware level, the electronic device includes a processor 301, a network interface 302, a memory 303, a non-volatile memory 304, and an internal bus 305, and may also include hardware required for other functions. The processor reads the corresponding computer program from the non-volatile memory into the memory and then runs it. Of course, in addition to the software implementation, this application does not exclude other implementation methods, such as logic devices or a combination of software and hardware, etc., that is to say, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

[0055] Please refer to Figure 4 , Figure 4 is a block diagram of a storage device for medical privacy data provided by an exemplary embodiment. Figure 4 As shown, the device comprises: The receiving unit 402 is used to receive a storage request for the medical privacy data sent by a data provider; An authentication unit 404 is used to initiate a corresponding identity authentication for the data provider, wherein the identity authentication is used to determine whether the data provider is a preset user; The storage unit 406 is used to obtain the medical privacy data provided by the data provider when it is determined that the data provider is a preset user according to the identity authentication, and to locally store the medical privacy data persistently, and to publish the medical privacy data to the corresponding blockchain after desensitizing it.

[0056] Optionally, the medical privacy data includes at least one of the following: Patient’s medical history data, patient’s identity data, test result data, and / or private data of diagnosis and treatment applications.

[0057] Optionally, the storage unit 406 is specifically used for: Hash processing is performed on the medical privacy data to obtain corresponding summary data; The summary data is published to the corresponding blockchain.

[0058] Optionally, the hash algorithm corresponding to the hash processing includes: MD5, SHA-1, SHA-256, SHA-384, SHA-512.

[0059] Optionally, the storage unit 406 is specifically used for: Initiate a medical privacy data storage transaction to the blockchain, so that the blockchain calls the corresponding smart contract to store the desensitized medical privacy data in the blockchain.

[0060] Optionally, the device further comprises: The sending unit 408 is used to initiate a security identity authentication to the data requester in response to a data acquisition request sent by the data requester; if the security identity authentication is passed, the corresponding medical privacy data and the hash algorithm corresponding to the desensitization processing are sent to the data requester.

[0061] For the device embodiment, since it basically corresponds to the method embodiment, the relevant parts can refer to the partial description of the method embodiment. The device embodiment described above is only schematic, wherein the modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this specification. A person of ordinary skill in the art can understand and implement it without paying creative labor.

[0062] In a typical configuration, a computer device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0063] Memory may include non-permanent storage in a computer-readable medium, in the form of random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0064] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0065] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0066] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementations described in the following exemplary embodiments do not represent all implementations consistent with this specification. Instead, they are merely examples of devices and methods consistent with some aspects of this specification as detailed in the appended claims.

[0067] The terms used in this specification are for the purpose of describing specific embodiments only and are not intended to limit this specification. The singular forms "a", "the" and "the" used in this specification and the appended claims are also intended to include plural forms unless the context clearly indicates otherwise. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more associated listed items.

[0068] It should be understood that although the terms first, second, third, etc. may be used in this specification to describe various information, this information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of this specification, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0069] The above description is only a preferred embodiment of this specification and is not intended to limit this specification. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of this specification should be included in the scope of protection of this specification.

Claims

1. A method for storing medical privacy data, characterized in that: Applied to a blockchain node, the method comprises: Receiving a storage request for the medical privacy data sent by a data provider; Initiate corresponding identity authentication for the data provider, the identity authentication is used to determine whether the data provider is a preset user; When it is determined that the data provider is a preset user according to the identity authentication, the medical privacy data provided by the data provider is obtained, and the medical privacy data is locally persistently stored, and the medical privacy data is anonymized and then published to the corresponding blockchain.

2. The method according to claim 1, characterized in that The medical privacy data includes at least one of the following: Patient’s medical history data, patient’s identity data, test result data, and / or private data of diagnosis and treatment applications.

3. The method according to claim 1, characterized in that The desensitizing of the medical privacy data and publishing it to the corresponding blockchain includes: Hash processing is performed on the medical privacy data to obtain corresponding summary data; The summary data is published to the corresponding blockchain.

4. The method according to claim 3, characterized in that The hash algorithm corresponding to the hash processing includes: MD5, SHA-1, SHA-256, SHA-384, SHA-512.

5. The method according to claim 1, characterized in that The desensitizing of the medical privacy data and publishing it to the corresponding blockchain includes: Initiate a medical privacy data storage transaction to the blockchain, so that the blockchain calls the corresponding smart contract to store the desensitized medical privacy data in the blockchain.

6. The method according to claim 1, characterized in that The method further comprises: In response to a data acquisition request sent by a data demander, initiating a security identity authentication to the data demander; When the security identity authentication is passed, the corresponding medical privacy data and the corresponding hash algorithm for desensitization processing are sent to the data requester.

7. A storage device for medical privacy data, characterized in that: Applied to a blockchain node, the device comprises: A receiving unit, configured to receive a storage request for the medical privacy data sent by a data provider; An authentication unit, used to initiate a corresponding identity authentication for the data provider, wherein the identity authentication is used to determine whether the data provider is a preset user; A storage unit is used to obtain the medical privacy data provided by the data provider when it is determined that the data provider is a preset user according to the identity authentication, and to locally store the medical privacy data persistently, and to publish the medical privacy data to the corresponding blockchain after desensitizing it.

8. A computer-readable storage medium having a computer program stored thereon, wherein the program, when executed by a processor, implements the steps of the method according to any one of claims 1 to 6.

9. An electronic device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the method according to any one of claims 1 to 6 when executing the program.

Images