Method, system, electronic device and storage medium for accessing medical data
By employing a multi-chain collaborative architecture and dynamic access control, the risks of centralized storage and rigid access control in medical data management are resolved, enabling trusted cross-chain exchange and efficient data sharing. This approach is particularly suitable for flexible collaborative scenarios such as ad-hoc consultations.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- SHANGHAI UPPER BIO TECH PHARMA
- Filing Date
- 2025-09-25
- Publication Date
- 2026-06-02
AI Technical Summary
Existing medical data management systems suffer from risks such as centralized storage, potential data tampering, rigid access control, poor interoperability across institutions, insufficient privacy protection, and static encryption strategies that cannot support flexible collaboration needs.
It adopts a multi-chain collaborative architecture, including a private chain, a consortium chain, and an IPFS cluster. Through digital signatures, NFT credentials, and dynamic access control, it enables fine-grained authorization and real-time revocation of patient privacy data. Combined with TEE and federated learning for encrypted computation, it ensures data security and compliance.
It enables trusted cross-chain exchange, reduces storage costs, improves the efficiency of permission changes, meets the flexible collaboration needs such as ad-hoc consultations, has high scalability and compliance, and is suitable for data sharing and scientific research collaboration in multiple medical scenarios.
Smart Images

Figure CN121283705B_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the field of medical data processing technology, and in particular to a method, system, electronic device, and storage medium for accessing medical data. Background Technology
[0002] Current medical data management faces two core challenges: the risks of centralized storage and rigid access control. Traditional systems rely on centralized databases, which are prone to single points of failure and data tampering. Furthermore, their access control models (often using RBAC) are ill-suited to dynamic medical scenarios, making it difficult to precisely control the flow of data. While existing blockchain solutions improve tamper resistance, they generally suffer from high storage costs, poor interoperability across institutions, and insufficient privacy protection. Moreover, static encryption strategies cannot support flexible collaborative needs such as ad-hoc consultations. Summary of the Invention
[0003] The technical problem to be solved by this disclosure is to overcome the above-mentioned defects in the prior art and provide a method, system, electronic device, and storage medium for accessing medical data.
[0004] This disclosure solves the above-mentioned technical problems through the following technical solution:
[0005] Firstly, a method for accessing medical data is provided, including:
[0006] In response to a request from an accessing party to access a target patient's medical data, an authorization request is sent to the target patient. This authorization request triggers the target patient to obtain their private key, digitally sign the authorization information using the private key, and submit the signed authorization information to the permission management contract of the consortium blockchain. The authorization information includes at least one of the following: the accessing party's public key, content identifier, operation permissions, and access validity period. The content identifier is generated by storing the medical data in IPFS shards, and the IPFS shards corresponding to the patient's privacy data contained in the medical data are written to the private blockchain, while the IPFS shards corresponding to other data in the medical data besides the patient's privacy data are written to the consortium blockchain. The private blockchain is deployed at the medical institution where the patient receives treatment, and the consortium blockchain's members include multiple medical institutions.
[0007] In response to the validity of the digital signature verification by the access management contract, an NFT credential is generated for the access party;
[0008] Determine the storage location of the medical data and verify the validity of the NFT certificate;
[0009] In response to the successful validity verification of the NFT certificate, the access request is redirected to the data gateway corresponding to the storage location, so as to obtain the IPFS shard corresponding to the patient's privacy data and the IPFS shard corresponding to the other data through a secure channel;
[0010] The IPFS fragment is restored to plaintext and displayed to the accessing party within a security sandbox.
[0011] Optionally, obtaining the IPFS shards corresponding to the patient's privacy data and the IPFS shards corresponding to the other data through a secure channel includes:
[0012] The identity of the accessing party is determined, and an IPFS fragment matching the identity is obtained through the secure channel after format conversion; wherein, the data format of the IPFS fragment is converted to a format matching the identity through a format conversion contract.
[0013] Optionally, the medical data stored in IPFS shards has undergone compliance review; wherein the compliance review of the medical data is based on a smart contract.
[0014] Optionally, the data written to the private blockchain is an IPFS shard containing patient privacy data encrypted using the national cryptographic algorithm SM4.
[0015] And / or, the patient privacy data is encrypted and computed in the TEE or federated learning node.
[0016] Secondly, a medical data access system is provided, including:
[0017] A dynamic access control module is used to respond to an access request from an access party to a target patient's medical data by sending an authorization request to the target patient. The authorization request triggers the target patient to obtain their private key, digitally sign the authorization information using the private key, and submit the signed authorization information to the access management contract of the consortium blockchain. The authorization information includes at least one of the following: the access party's public key, a content identifier, operation permissions, and an access validity period. The content identifier is generated by storing the medical data in IPFS shards, and the IPFS shards corresponding to the patient's privacy data contained in the medical data are written to the private blockchain, while the IPFS shards corresponding to other data in the medical data besides the patient's privacy data are written to the consortium blockchain. The private blockchain is deployed at the medical institution where the patient receives treatment, and the consortium blockchain comprises multiple medical institutions.
[0018] The dynamic access control module is also used to generate an NFT credential for the access party in response to the validity of the digital signature verification by the access management contract.
[0019] The dynamic access control module is also used to determine the storage location of the medical data and verify the validity of the NFT credential;
[0020] The privacy computing gateway module is used to redirect the access request to the data gateway corresponding to the storage location in response to the successful validity verification of the NFT certificate, so as to obtain the IPFS shard corresponding to the patient privacy data and the IPFS shard corresponding to the other data through a secure channel;
[0021] The display module is used to restore the IPFS fragments to plaintext and display them to the accessing party within a security sandbox.
[0022] Optionally, when obtaining the IPFS shards corresponding to the patient's privacy data and the IPFS shards corresponding to the other data through a secure channel, the privacy computing gateway module is used to:
[0023] The identity of the accessing party is determined, and an IPFS fragment matching the identity is obtained through the secure channel after format conversion; wherein, the data format of the IPFS fragment is converted to a format matching the identity through a format conversion contract.
[0024] Optionally, the medical data stored in IPFS shards has undergone compliance review; wherein the compliance review of the medical data is based on a smart contract.
[0025] Optionally, the data written to the private blockchain is an IPFS shard containing patient privacy data encrypted using the national cryptographic algorithm SM4.
[0026] And / or, the patient privacy data is encrypted and computed in the TEE or federated learning node.
[0027] Thirdly, an electronic device is provided, including a memory, a processor, and a computer program stored in the memory and for running on the processor, wherein the processor executes the computer program to implement the method for accessing medical data as described in any of the first aspects.
[0028] Fourthly, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the method for accessing medical data as described in any one of the first aspects.
[0029] Based on common knowledge in the field, the above-mentioned preferred conditions can be combined arbitrarily to obtain various preferred embodiments of this disclosure.
[0030] The positive and progressive effects of this disclosure are as follows: Based on multi-chain collaboration and dynamic permission control, this disclosure enables cross-chain trusted exchange while ensuring data sovereignty. Through dynamic permission control and verifiable credentials, it realizes fine-grained authorization and real-time revocation led by patients, which greatly improves the efficiency of permission change and is particularly suitable for flexible collaboration needs such as ad-hoc consultations. Attached Figure Description
[0031] Figure 1 A flowchart illustrating a method for accessing medical data as provided in an exemplary embodiment of this disclosure;
[0032] Figure 2 A flowchart of another method for accessing medical data provided as an exemplary embodiment of this disclosure;
[0033] Figure 3 A schematic diagram of a medical data access system provided as an exemplary embodiment of this disclosure;
[0034] Figure 4 This is a schematic diagram of the structure of an electronic device provided as an exemplary embodiment of the present disclosure. Detailed Implementation
[0035] The present disclosure is further illustrated below by way of embodiments, but the present disclosure is not limited to the scope of the embodiments described herein.
[0036] The prefixes such as "first" and "second" used in this disclosure are merely for distinguishing different descriptive objects and do not limit the position, order, priority, quantity, or content of the described objects. The use of ordinal numbers and other prefixes used to distinguish descriptive objects in this disclosure does not constitute a limitation on the described objects. The description of the described objects is given in the claims or the context of the embodiments, and should not be construed as an unnecessary limitation. Furthermore, in the description of this embodiment, unless otherwise stated, "multiple" means two or more.
[0037] In this embodiment of the disclosure, the collection, storage, use, processing, transmission, provision, and disclosure of medical data all comply with relevant laws and regulations and do not violate public order and good morals.
[0038] This disclosure provides a method for accessing medical data, which is based on multi-chain collaboration and adopts a hierarchical chain architecture, including:
[0039] (1) Private blockchain: Deployed within various medical institutions to store patient privacy data, i.e., highly sensitive raw data. It can be encrypted using the national cryptographic algorithm SM4 to ensure data sovereignty and local compliance;
[0040] (2) Consortium blockchain: It is jointly maintained by multiple medical institutions, storing metadata such as data hashes, permission policies, and audit logs, and realizing cross-chain communication and atomic exchange through the Interledger protocol;
[0041] (3) IPFS cluster: used for distributed storage of encrypted data shards, deployed by region to meet data localization requirements, and combined with erasure coding technology to improve disaster recovery capabilities;
[0042] (4) This layer achieves physical data isolation and logical unified management through inter-chain collaboration, effectively improving system scalability, availability and compliance.
[0043] Through a multi-chain collaborative storage architecture, we can achieve hierarchical data management, trusted cross-chain exchange, and low-cost disaster recovery, reducing storage costs by more than 90% and shortening cross-organization data synchronization time from several days to minutes.
[0044] See Figure 1 and Figure 2 The access method includes the following steps:
[0045] Step 101: In response to the access party's request to access the target patient's medical data, send an authorization request to the target patient.
[0046] The authorization request is used to trigger the target patient to obtain the target patient's private key, use the private key to digitally sign the authorization information, and submit the signed authorization information to the permission management contract of the consortium blockchain.
[0047] The authorization information includes at least one of the following: the accessing party's public key, content identifier, operation permissions, and access validity period; wherein, the content identifier is generated by storing medical data in IPFS shards, and the IPFS shards corresponding to the patient privacy data contained in the medical data are written to the private chain, and the IPFS shards corresponding to other data in the medical data besides the patient privacy data are written to the consortium chain; the private chain is deployed in the medical institution where the patient seeks medical treatment, and the consortium chain's consortium members include multiple medical institutions.
[0048] In this embodiment, the patient's medical data is stored in a hybrid architecture of private chain, consortium chain, and IPFS through a distributed storage mode, which achieves data tamper-proofing and low-cost disaster recovery, reducing storage costs by 98%.
[0049] It should be noted that the access party can be, but is not limited to, medical institution servers, doctors' terminals, etc. The patient's access party can be, for example, a patient's terminal (such as a mobile phone, tablet, or mini-program). Patient privacy data may include, but is not limited to, patient identification numbers, mobile phone numbers, etc.
[0050] The medical institution where the patient seeks treatment and the medical institution where the visitor (e.g., the doctor) seeks treatment can be the same institution. For example, if the patient seeks treatment at institution A, the doctor at institution A can review the patient's medical records (medical data) when conducting a consultation. Alternatively, the medical institution where the patient seeks treatment and the medical institution where the visitor seeks treatment can be different institutions. For example, if the patient seeks treatment at institution A, the medical records can be shared with a doctor at institution B for a temporary consultation.
[0051] Taking patient Li as an example, a doctor from medical institution B needs to review Li's medical records for a consultation. Li's terminal displays an authorization request. Li uses his private key sk_patient to digitally sign a structured authorization message M (containing the target doctor's public key pk_doctor_B, content identifier CID, access validity period t=24h, and operation permission of viewing only), generating Sig=Sign(sk_patient,M). This signature request is submitted to the permission management contract of the consortium blockchain through the patient's terminal.
[0052] It should be noted that the "view only" permission mentioned above is an example, and the permission can be set according to actual needs. The permission can be proposed by the accessing party and reviewed and confirmed by the target patient, or modified and then confirmed.
[0053] Step 102: In response to the validity of the digital signature verification by the access control contract, generate an NFT credential for the access party.
[0054] After the blockchain verifies the signature validity based on the permission management contract (Verify(pk_patient,M,Sig) == true), it automatically generates a non-transferable NFT (Soulbound Token) conforming to the ERC-1155 standard. The NFT's metadata precisely records the authorization terms and is sent to the designated address of the access party. Using the example of medical institution A and medical institution B, this means it's sent to the address of the designated doctor at medical institution B, enabling real-time dynamic issuance of permissions. This process can be completed within 3 seconds.
[0055] Step 103: Determine the storage location of the medical data and verify the validity of the NFT certificate.
[0056] In step 103, cross-chain request and verification are implemented: A doctor from medical institution B initiates an access request. The system executing the access method parses the chain identifier (Chain ID) of the target medical data for the access request, and determines that the target medical data includes medical record data stored on the private chain of medical institution A. The system synchronously queries the consortium chain (permission policy) and the private chain of medical institution A (latest status) to verify the validity of the NFT certificate and whether it is within the validity period.
[0057] Step 104: In response to the successful verification of the validity of the NFT certificate, the access request is redirected to the data gateway corresponding to the storage location to obtain the IPFS fragments corresponding to the patient's privacy data and the IPFS fragments corresponding to other data through a secure channel.
[0058] After successful validity verification, the access request is redirected to the data gateway of medical institution A. The gateway retrieves the IPFS shards corresponding to the patient's privacy data from its local IPFS cluster and transmits them to the local TEE (Intel SGX) environment of medical institution B via a secure channel (mTLS). At the same time, medical institution B retrieves the IPFS shards corresponding to other data besides the patient's privacy data from the consortium blockchain.
[0059] Step 105: Restore the IPFS fragments to plaintext and display them to the accessing party through a security sandbox.
[0060] Within the SGX environment of medical institution B, IPFS fragments are decrypted, reassembled, and restored to plaintext using a securely loaded key, allowing doctors to browse them within a secure sandbox. Throughout the entire process, the original plaintext data never leaves the storage domain of medical institution A, and there is no persistent storage on the medical institution B side.
[0061] In this embodiment, the key steps of each access operation to medical data (authorization verification, access initiation, and data decryption event) are written as transaction records onto the consortium blockchain's dedicated audit chain, forming immutable audit trails for subsequent compliance review. Smart contracts automatically execute data lifecycle management and compliance review, improving audit efficiency by 80% and fully meeting the requirements of GDPR, HIPAA, and other regulations.
[0062] In this embodiment, medical data privacy computing based on multi-chain collaboration and dynamic permission control can achieve cross-chain trusted exchange while ensuring data sovereignty. Through dynamic permission control and verifiable credentials, it realizes fine-grained authorization and real-time revocation led by patients, improving the efficiency of permission change by more than 40 times, which is particularly suitable for flexible collaboration needs such as ad-hoc consultations.
[0063] In one embodiment, the steps of obtaining IPFS fragments corresponding to patient privacy data and other data through a secure channel include: determining the identity of the accessing party, and obtaining the format-converted IPFS fragments that match the identity through the secure channel; wherein, the data format of the IPFS fragments is converted to a format matching the identity through a format conversion contract. The correspondence between identity and data format can be predefined in the format conversion contract (smart contract).
[0064] For example, if the visitor is a hospital radiologist's terminal, and the radiologist focuses on image data, then the IPFS fragment data format is converted to image format so that the image data can be displayed to the visitor within a security sandbox. If the visitor is an outpatient doctor's terminal, and the outpatient doctor focuses on text data, then the IPFS fragment data format is converted to text format so that the text data can be displayed to the visitor within a security sandbox.
[0065] In this embodiment, the identity of the visitor can be automatically identified, and medical data in a data format that matches the visitor's identity can be provided so that the visitor can access the medical data.
[0066] In one embodiment, IPFS sharding stores compliant medical data; the compliance review of the medical data is based on smart contracts. This ensures that the data usage complies with privacy computing requirements under regulations such as GDPR and HIPAA.
[0067] In one embodiment, the data written to the private blockchain is an IPFS fragment of patient privacy data encrypted using the national cryptographic algorithm SM4. In step 104, after the validity verification is successful, the access request is redirected to the data gateway of medical institution A, which retrieves the SM4-encrypted ciphertext fragment from its local IPFS cluster.
[0068] In one embodiment, patient privacy data is encrypted and computed within the TEE or federated learning node, and the original data remains within the domain and is not decrypted.
[0069] In one embodiment, a three-tiered access control system is introduced:
[0070] (1) Patient-level permissions: Based on digital signatures and verifiable credentials (VC), patients can sign authorization information with their private keys to achieve autonomous and fine-grained data authorization;
[0071] (2) Institutional-level permissions: Access control based on data attributes is implemented through attribute-based encryption (ABE) to ensure that data is only accessed by entities that comply with the policy;
[0072] (3) Regulatory-level permissions: The smart contract automatically executes data lifecycle management strategies, such as automatically deleting expired data and recording all access behaviors, to meet the requirements of regulations such as GDPR;
[0073] (4) The permission representation adopts the NFT (non-fungible token) design, follows the ERC-1155 standard to generate non-transferable permission certificates (Soulbound Token), and embeds constraints such as validity period and number of uses to realize the dynamic issuance and revocation of permissions.
[0074] In one embodiment, a privacy-enhancing gateway is employed. This gateway integrates multiple privacy-enhancing technologies to ensure that data is "usable but not visible" during the computation process:
[0075] (1) Trusted Execution Environment (TEE): such as Intel SGX, used to decrypt data and perform calculations within an enclave, ensuring that the original data is not leaked;
[0076] (2) Federated learning: It supports multiple parties to collaboratively train the model in an encrypted state, and protects gradient information through homomorphic encryption or differential privacy.
[0077] (3) Differential privacy: Inject calibrated noise into the query results (IPFS shards) to meet the requirements of ε-differential privacy and prevent re-identification attacks;
[0078] (4) k-anonymization: generalize the output results to ensure that each record cannot be distinguished from fewer than k-1 other records;
[0079] (5) The gateway also has functions such as computing task scheduling, cross-chain communication coordination, and compliance checks, forming a complete privacy computing closed loop.
[0080] In this embodiment, the privacy computing gateway integrates technologies such as TEE, federated learning, and differential privacy to support efficient collaborative analysis while ensuring data privacy, with a data re-identification risk of less than 0.01%.
[0081] Corresponding to the aforementioned embodiments of medical data access methods, this disclosure also provides embodiments of medical data access systems.
[0082] Figure 3 A schematic diagram of a medical data access system provided for an exemplary embodiment of this disclosure, the system comprising:
[0083] The dynamic permission control module 31 is used to respond to an access request from an access party to a target patient's medical data by sending an authorization request to the target patient. The authorization request triggers the target patient to obtain the patient's private key, digitally sign the authorization information using the private key, and submit the signed authorization information to the permission management contract of the consortium blockchain. The authorization information includes at least one of the following: the access party's public key, content identifier, operation permissions, and access validity period. The content identifier is generated by sharding the medical data using IPFS, and the IPFS shards corresponding to the patient's privacy data contained in the medical data are written to the private blockchain, while the IPFS shards corresponding to other data in the medical data besides the patient's privacy data are written to the consortium blockchain. The private blockchain is deployed at the medical institution where the patient receives treatment, and the consortium blockchain's members include multiple medical institutions.
[0084] The dynamic access control module 31 is also used to generate an NFT credential for the access party in response to the validity of the digital signature verification by the access management contract.
[0085] The dynamic access control module 31 is also used to determine the storage location of the medical data and verify the validity of the NFT certificate;
[0086] Privacy computing gateway module 32 is used to redirect the access request to the data gateway corresponding to the storage location in response to the successful validity verification of the NFT certificate, so as to obtain the IPFS shard corresponding to the patient privacy data and the IPFS shard corresponding to the other data through a secure channel;
[0087] The display module 33 is used to restore the IPFS fragment to plaintext and display it to the accessing party within a security sandbox.
[0088] In this embodiment, medical data privacy computing based on multi-chain collaboration and dynamic access control enables trusted cross-chain exchange while ensuring data sovereignty. Through dynamic access control and verifiable credentials, it achieves patient-led fine-grained authorization and real-time revocation, improving access control efficiency by more than 40 times. This makes it particularly suitable for flexible collaboration needs such as ad-hoc consultations. The system in this embodiment also possesses high scalability, interoperability, and compliance, making it suitable for data sharing and research collaboration in various medical scenarios, and has significant clinical application value and social significance.
[0089] Optionally, when obtaining the IPFS shards corresponding to the patient's privacy data and the IPFS shards corresponding to the other data through a secure channel, the privacy computing gateway module is used to:
[0090] The identity of the accessing party is determined, and an IPFS fragment matching the identity is obtained through the secure channel after format conversion; wherein, the data format of the IPFS fragment is converted to a format matching the identity through a format conversion contract.
[0091] Optionally, the medical data stored in IPFS shards has undergone compliance review; wherein the compliance review of the medical data is based on a smart contract.
[0092] Optionally, the data written to the private blockchain is an IPFS shard containing patient privacy data encrypted using the national cryptographic algorithm SM4.
[0093] And / or, the patient privacy data is encrypted and computed in the TEE or federated learning node.
[0094] For the system embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to in the description of the method embodiments. The system embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this disclosure according to actual needs.
[0095] Figure 4 This is a schematic diagram of the structure of an electronic device according to an example embodiment of the present disclosure. The electronic device includes a memory, a processor, and a computer program stored in the memory and used to run on the processor. When the processor executes the computer program, it implements the medical data access method described in any of the above embodiments. Figure 4 The electronic device 40 shown is merely an example and should not be construed as limiting the functionality and scope of use of the embodiments disclosed herein.
[0096] like Figure 4 As shown, the electronic device 40 can be manifested as a general-purpose computing device, such as a server device. The components of the electronic device 40 may include, but are not limited to: at least one processor 41, at least one memory 42, and a bus 43 connecting different system components (including memory 42 and processor 41).
[0097] Bus 43 includes a data bus, an address bus, and a control bus.
[0098] The memory 42 may include volatile memory, such as random access memory (RAM) 421 and / or cache memory 422, and may further include read-only memory (ROM) 423.
[0099] The memory 42 may also include a program tool 425 (or utility) having a set (at least one) program module 424, such program module 424 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of these examples may include an implementation of a network environment.
[0100] The processor 41 executes various functional applications and data processing by running computer programs stored in the memory 42, such as the medical data access method provided in any of the above embodiments.
[0101] Electronic device 40 can also communicate with one or more external devices 44 (e.g., keyboard, pointing device, etc.). This communication can be performed via input / output (I / O) interface 45. Furthermore, electronic device 40 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public network, such as the Internet) via network adapter 46. As shown, network adapter 46 communicates with other modules of electronic device 40 via bus 43. It should be understood that, although not shown in the figure, other hardware and / or software modules can be used in conjunction with electronic device 40, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID (disk array) systems, tape drives, and data backup storage systems.
[0102] It should be noted that although several units / modules or sub-units / modules of the electronic device have been mentioned in the detailed description above, this division is merely exemplary and not mandatory. In fact, according to embodiments of this disclosure, the features and functions of two or more units / modules described above can be embodied in one unit / module. Conversely, the features and functions of one unit / module described above can be further divided and embodied by multiple units / modules.
[0103] This disclosure also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the medical data access method provided in any of the above embodiments.
[0104] The readable storage medium may be more specifically adopted, including but not limited to: portable disk, hard disk, random access memory, read-only memory, erasable programmable read-only memory, optical storage device, magnetic storage device, or any suitable combination thereof.
[0105] This disclosure also provides a computer program product, including a computer program that, when executed by a processor, implements the medical data access method described in any of the preceding embodiments.
[0106] The program code for executing the computer program product of this disclosure can be written in any combination of one or more programming languages, and the program code can be executed entirely on a user device, partially on a user device, as a stand-alone software package, partially on a user device and partially on a remote device, or entirely on a remote device.
[0107] While specific embodiments of this disclosure have been described above, those skilled in the art should understand that these are merely illustrative examples, and the scope of protection of this disclosure is defined by the appended claims. Those skilled in the art can make various changes or modifications to these embodiments without departing from the principles and essence of this disclosure, but all such changes and modifications fall within the scope of protection of this disclosure.
Claims
1. A method of accessing medical data, characterized by, include: In response to a request from the accessing party to access the target patient's medical data, an authorization request is sent to the target patient. The authorization request is used to trigger the target patient to obtain the target patient's private key, digitally sign the authorization information using the private key, and submit the signed authorization information to the permission management contract of the consortium blockchain. The authorization information includes at least one of the following: the accessing party's public key, content identifier, operation permissions, and access validity period. The content identifier is generated by storing the medical data in IPFS shards, and the IPFS shards corresponding to the patient's privacy data contained in the medical data are written to the private blockchain, while the IPFS shards corresponding to other data in the medical data besides the patient's privacy data are written to the consortium blockchain. The private blockchain is deployed at the medical institution where the patient receives treatment, and the consortium blockchain's members include multiple medical institutions. In response to the validity of the digital signature verification by the access management contract, an NFT credential is generated for the access party; Determine the storage location of the medical data and verify the validity of the NFT certificate; In response to the successful validity verification of the NFT certificate, the access request is redirected to the data gateway corresponding to the storage location, so as to obtain the IPFS shard corresponding to the patient's privacy data and the IPFS shard corresponding to the other data through a secure channel; The IPFS fragment is restored to plaintext and displayed to the accessing party within a security sandbox.
2. The medical data access method according to claim 1, wherein, Obtaining the IPFS shards corresponding to the patient's privacy data and the IPFS shards corresponding to the other data through a secure channel includes: The identity of the accessing party is determined, and an IPFS fragment matching the identity is obtained through the secure channel after format conversion; wherein, the data format of the IPFS fragment is converted to a format matching the identity through a format conversion contract.
3. The method for accessing medical data according to claim 1, characterized in that, The medical data stored in IPFS shards has undergone compliance review; the compliance review of the medical data is based on a smart contract.
4. The method for accessing medical data according to any one of claims 1-3, characterized in that, The data written to the private blockchain is an IPFS fragment of patient privacy data encrypted using the national cryptographic algorithm SM4; And / or, the patient privacy data is encrypted and computed in the TEE or federated learning node.
5. A medical data access system, characterized in that, include: The dynamic access control module is used to send an authorization request to the target patient in response to the access request from the access party to the target patient's medical data; The authorization request is used to trigger the target patient to obtain the target patient's private key, digitally sign the authorization information using the private key, and submit the signed authorization information to the permission management contract of the consortium blockchain. The authorization information includes at least one of the following: the accessing party's public key, content identifier, operation permissions, and access validity period. The content identifier is generated by storing the medical data in IPFS shards, and the IPFS shards corresponding to the patient's privacy data contained in the medical data are written to the private blockchain, while the IPFS shards corresponding to other data in the medical data besides the patient's privacy data are written to the consortium blockchain. The private blockchain is deployed at the medical institution where the patient receives treatment, and the consortium blockchain's members include multiple medical institutions. The dynamic access control module is also used to generate an NFT credential for the access party in response to the validity of the digital signature verification by the access management contract. The dynamic access control module is also used to determine the storage location of the medical data and verify the validity of the NFT credential; The privacy computing gateway module is used to redirect the access request to the data gateway corresponding to the storage location in response to the successful validity verification of the NFT certificate, so as to obtain the IPFS shard corresponding to the patient privacy data and the IPFS shard corresponding to the other data through a secure channel; The display module is used to restore the IPFS fragments to plaintext and display them to the accessing party within a security sandbox.
6. The medical data access system according to claim 5, characterized in that, When obtaining the IPFS shards corresponding to the patient's privacy data and the IPFS shards corresponding to other data through a secure channel, the privacy computing gateway module is used for: The identity of the accessing party is determined, and an IPFS fragment matching the identity is obtained through the secure channel after format conversion; wherein, the data format of the IPFS fragment is converted to a format matching the identity through a format conversion contract.
7. The medical data access system according to claim 5, characterized in that, The medical data stored in IPFS shards has undergone compliance review; the compliance review of the medical data is based on a smart contract.
8. The medical data access system according to any one of claims 5-7, characterized in that, The data written to the private blockchain is an IPFS fragment of patient privacy data encrypted using the national cryptographic algorithm SM4; And / or, the patient privacy data is encrypted and computed in the TEE or federated learning node.
9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and for running on the processor, characterized in that, When the processor executes the computer program, it implements the method for accessing medical data as described in any one of claims 1 to 4.
10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method for accessing medical data as described in any one of claims 1 to 4.