Medical data file sharing method and device, electronic equipment and program product

Abstract

The invention provides a medical data file sharing method and device, electronic equipment and a program product. The method comprises the following steps: receiving a viewing request for a medical data encryption file of a target patient sent by a first terminal device, wherein the medical data encryption file is obtained by encrypting medical data of the target patient by adopting identity information of the target patient; if the first terminal device and the second terminal device generating the medical data do not belong to the same institution, sending an authorization request to a third terminal device of the target patient; if the authorization result returned by the third terminal device indicates that the first terminal device is agreed to view the medical data, obtaining a decryption key of the encrypted file of the medical data according to the identity information of the target patient; and decrypting the medical data encrypted file according to the decryption key to obtain medical data, and returning the medical data to the first terminal device. The method is used for enhancing the security and privacy protection of the medical data file and improving the interoperability and cooperation efficiency of the medical information.

Description

Technical Field

[0001] The present application relates to the technical field of medical data sharing, and in particular to a medical data file sharing method, device, electronic device and program product. Background Art

[0002] In the modern medical industry, the dispersion and privacy sensitivity of medical data are the main obstacles to achieving cross-institutional, cross-regional and cross-hospital data sharing. The demand for sharing document-based medical data such as electronic medical records and electronic reports is growing, but the traditional data open sharing method cannot meet the requirements of privacy protection and data security. Therefore, how to achieve secure sharing of medical data while protecting patient privacy has become an important research direction in the field of medical information technology.

[0003] Current solutions usually involve generating a public-private key pair for each patient, encrypting medical data with the public key, and controlling data access rights through smart contracts. When medical institutions need to access data, they apply for authorization from the patient. After the patient agrees, the private key is used to decrypt the data for use by the medical institution. At the same time, in order to ensure the integrity and immutability of the data, the hash value of medical data such as electronic reports is stored on IPFS (InterPlanetary File System).

[0004] However, in practical applications, existing methods have the problem of poor medical data file sharing effect. Summary of the invention

[0005] The present application provides a medical data file sharing method, device, electronic device and program product to solve the problem that the existing method has poor medical data file sharing effect, thereby enhancing the security and privacy protection of medical data files and improving the interoperability and collaboration efficiency of medical information.

[0006] In a first aspect, an embodiment of the present application provides a medical data file sharing method, comprising:

[0007] receiving a request for viewing a medical data encryption file of a target patient sent by a first terminal device, where the medical data encryption file is obtained by encrypting the medical data of the target patient using the identity information of the target patient;

[0008] If the first terminal device and the second terminal device generating the medical data do not belong to the same institution, sending an authorization request to a third terminal device of the target patient;

[0009] If the authorization result returned by the third terminal device indicates that the first terminal device is allowed to view the medical data, a decryption key for the encrypted medical data file is obtained based on the identity information of the target patient;

[0010] The medical data encrypted file is decrypted according to the decryption key to obtain the medical data, and the medical data is returned to the first terminal device.

[0011] In a possible implementation, the method further includes:

[0012] If the first terminal device and the second terminal device generating the medical data belong to the same institution, obtaining a decryption key for the encrypted file of the medical data according to the identity information of the target patient;

[0013] The medical data encrypted file is decrypted according to the decryption key to obtain the medical data, and the medical data is returned to the first terminal device.

[0014] In a possible implementation, before receiving the request for viewing the encrypted medical data file of the target patient sent by the first terminal device, the method further includes:

[0015] When it is detected that the second terminal device generates medical data, obtaining the identity information of the target patient;

[0016] The identity information is hashed to obtain the encryption key for encrypting the medical data;

[0017] Based on the preset symmetric encryption algorithm and encryption key, the medical data is encrypted to obtain an encrypted medical data file.

[0018] In a possible implementation, obtaining a decryption key for a medical data encryption file according to the identity information of a target patient includes:

[0019] Hash the identity information of the target patient to obtain the hash value corresponding to the identity information;

[0020] Generate the decryption key of the medical data encrypted file according to the preset symmetric encryption algorithm requirements and hash value.

[0021] In a possible implementation, the method further includes:

[0022] Encrypt medical data files for storage;

[0023] and / or,

[0024] Sending the encrypted medical data file to a third terminal device;

[0025] and / or,

[0026] The encrypted medical data file is sent to the storage device corresponding to the second terminal device for storage.

[0027] In a possible implementation, the method further includes:

[0028] Obtaining a file identifier of the medical data encryption file, a file storage address, and an identifier of the institution where the second terminal device is located;

[0029] The file identifier, file storage address of the medical data encryption file and the identifier of the institution where the second terminal device is located are stored on the chain.

[0030] In a possible implementation, the method further includes:

[0031] Obtaining the identification of the institution where the first terminal device is located, as well as the viewing purpose, viewing time, and file identification of the encrypted medical data file;

[0032] The identification of the institution where the first terminal device is located, as well as the viewing purpose, viewing time and file identification of the medical data encrypted file are stored on the chain.

[0033] In a second aspect, an embodiment of the present application provides a medical data file sharing device, comprising:

[0034] A receiving module, configured to receive a request for viewing a medical data encryption file of a target patient sent by a first terminal device, where the medical data encryption file is obtained by encrypting the medical data of the target patient using the identity information of the target patient;

[0035] a sending module, configured to send an authorization request to a third terminal device of the target patient if the first terminal device and the second terminal device generating the medical data do not belong to the same institution;

[0036] An acquisition module, configured to acquire a decryption key for the encrypted medical data file according to the identity information of the target patient if the authorization result returned by the third terminal device indicates that the first terminal device is allowed to view the medical data;

[0037] The processing module is used to decrypt the medical data encrypted file according to the decryption key, obtain the medical data, and return the medical data to the first terminal device.

[0038] In a third aspect, an embodiment of the present application provides an electronic device, including: a memory, a processor;

[0039] Memory stores computer-executable instructions;

[0040] The processor executes the computer-executable instructions stored in the memory to implement the above first aspect and / or various possible implementations of the first aspect.

[0041] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed, they are used to implement the first aspect above and / or various possible implementation methods of the first aspect.

[0042] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program, which, when executed, implements the above first aspect and / or various possible implementation methods of the first aspect.

[0043] The medical data file sharing method, device, electronic device and program product provided by the present application receive a viewing request for a target patient's encrypted medical data file sent by a first terminal device, where the encrypted medical data file is obtained by encrypting the target patient's medical data using the target patient's identity information; if the first terminal device and the second terminal device that generates the medical data do not belong to the same institution, an authorization request is sent to a third terminal device of the target patient; if the authorization result returned by the third terminal device indicates that the first terminal device is allowed to view the medical data, a decryption key for the encrypted medical data file is obtained based on the target patient's identity information; the encrypted medical data file is decrypted based on the decryption key to obtain the medical data, and the medical data is returned to the first terminal device, wherein the patient controls the file access of the third terminal device to ensure that the device can view the file only after being authorized, thereby reducing the risk of data leakage and enhancing the patient's control over personal data; combined with encryption technology and authorization mechanism, cross-institutional medical data file sharing is realized, the security and privacy protection of medical data files are enhanced, thereby improving the interoperability and collaboration efficiency of medical information. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0045] Figure 1 A schematic diagram of a scenario of a medical data file sharing method provided in this application;

[0046] Figure 2 A flowchart of a medical data file sharing method provided for this application;

[0047] Figure 3 A schematic diagram of a medical data file encryption method provided in this application;

[0048] Figure 4 A specific flow chart of a medical data file encryption method provided in this application;

[0049] Figure 5 A flowchart of a medical data file decryption method provided in this application;

[0050] Figure 6 A specific flow chart of a medical data file decryption method provided in this application;

[0051] Figure 7 A specific flow chart of another medical data file decryption method provided by this application;

[0052] Figure 8 A schematic diagram of the structure of the medical data file sharing device provided in this application;

[0053] Fig. 9 A schematic diagram of the structure of the electronic device provided in this application.

[0054] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0055] 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, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0056] It should be noted that the identity information (including but not limited to the patient's name, ID number, other identity information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the patient or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards, and provide corresponding operation entrances for patients to choose to authorize or refuse.

[0057] In the prior art, current solutions usually involve generating a public-private key pair for each patient, using the public key to encrypt medical data, and controlling data access rights through smart contracts. When a medical institution needs to access data, it applies to the patient for authorization. After the patient agrees, the private key is used to decrypt the data for use by the medical institution. At the same time, in order to ensure the integrity and immutability of the data, the hash value of medical data such as electronic reports is stored on IPFS. However, the storage of data in IPFS is decentralized, and multiple nodes may store the same data blocks to improve the availability and reliability of the data. A large amount of encrypted and stored data will result in a large amount of redundant data wasting server resources according to the characteristics of blockchain node synchronization. At the same time, the use of public-private key pairs for encryption and decryption will require patients or data owners to specially save private keys. There are problems such as complex and difficult to remember private keys, and the password is easily exposed when stored on mobile phones or computers, which makes the sharing of medical data files ineffective.

[0058] In order to solve the above problems, the present application provides a medical data file sharing method, device, electronic device and program product, which uses the identity information of the target patient to encrypt its medical data to ensure the security of the data during transmission and storage. When it is necessary to share data across institutions, an authorization request is sent to the patient's third terminal device to ensure that the patient has ultimate control over the access to the data file. Only when the patient explicitly authorizes, a decryption key is generated based on the patient's identity information, the medical data file is decrypted and provided to the requesting party. This not only ensures the security and privacy protection of the data, but also enhances the patient's control over personal data files through a dynamic authorization mechanism, realizes safe and controlled medical data sharing, and promotes the interoperability and collaboration efficiency of medical information.

[0059] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0060] Figure 1 A scenario diagram of a medical data file sharing method provided in this application, such as Figure 1 As shown, the specific application scenario of this application can be a medical data file sharing system. The medical data file sharing system includes a data layer, a support layer, a functional layer, and an application layer, wherein the data layer is used to store medical-related information, such as patient medical records, various examination reports, films and other data information; the support layer is used to provide the system with operating capabilities, including blockchain management and blockchain services, such as building a medical service chain to supervise the blockchain life cycle; the functional layer is used to display functions provided to users, such as user management, file generation, application report, authorization report, download report and other functions; the application layer includes application scenarios such as inspection and testing reports between medical institutions, such as encrypted sharing of data files such as radiology reports, ultrasound examination results, blood test results, electrocardiogram reports, and CT (Computed Tomography) reports.

[0061] In one example, the functional layers of the system can be divided into the medical institution side (exe client installed in the medical institution), the patient side (the original App (Application) / Mini Program / Official Account of the medical institution, etc.) and the patient service side, which provides authorization, downloading, sharing of encrypted electronic reports, and traceability of usage records API (Application ProgrammingInterface, application programming interface). Among them, the account information of the medical client records the information of the medical institution, which requires real-name authentication, such as the name of the institution, address, registration number, contact information, etc. This information is used to identify and manage different medical institutions in the system. The medical client includes a monitoring function. When the original medical system generates an electronic report, the doctor / medical user clicks "encrypted report" to trigger the smart contract to encrypt the electronic report and finally generate an encrypted electronic report and push it to the patient (the original medical system push path); when the patient shares the electronic report (encrypted) to the medical institution, the medical institution user clicks "report decryption" to trigger the smart contract to decrypt the encrypted electronic report for medical personnel to view and use. The patient end provides an API standardized interface based on the original medical institution patients to realize data authorization, download, and share encrypted electronic reports. The patient end logs in through the corresponding patient's account authentication information. At the same time, the use purpose, use organization, and use time of the electronic report are recorded on the medical service chain. For example, when the medical institution personnel open the encrypted electronic report, the blockchain monitors and records the use organization and other information.

[0062] In another example, the system includes a client and a medical service blockchain. The client uses a lightweight C / S architecture exe program that is directly installed on the original medical client. When using it, you only need to open it. For example, the doctor does not need to do any additional operations. The exe program automatically captures and reads patient information such as medical insurance cards / visit cards / ID cards, uses smart contracts to encrypt and decrypt data, and records operations on the chain. It automatically goes dormant when the system is not in use. Among them, client users can include patients, medical institution personnel, and regulatory units such as health commission personnel. Patients can authorize, view, and download electronic reports through the system; medical institution personnel can apply for and view electronic reports through the system; and regulatory unit personnel can use the system to monitor data usage records and monitor whether there is data abuse.

[0063] This embodiment does not impose any special restrictions on the selection type of the medical data file sharing system, as long as it can receive a request for viewing the medical data encryption file of the target patient sent by the first terminal device, and the medical data encryption file is obtained by encrypting the medical data of the target patient using the identity information of the target patient; if the first terminal device and the second terminal device that generates the medical data do not belong to the same organization, an authorization request is sent to the third terminal device of the target patient; if the authorization result returned by the third terminal device indicates that the first terminal device is allowed to view the medical data, a decryption key for the medical data encryption file is obtained based on the identity information of the target patient; the medical data encryption file is decrypted based on the decryption key to obtain the medical data, and the medical data is returned to the first terminal device.

[0064] Figure 2 A flowchart of a medical data file sharing method provided in this application. Figure 2 As shown, the method may include:

[0065] S201. Receive a request for viewing a medical data encryption file of a target patient sent by a first terminal device, where the medical data encryption file is obtained by encrypting the medical data of the target patient using the identity information of the target patient.

[0066] The first terminal device may refer to a device that initiates a viewing request, such as a doctor's computer, a nurse's tablet computer, or a medical researcher's workstation.

[0067] Target patients can refer to individuals with medical data, such as patients in a hospital or patients receiving telemedicine services, which can include online medical services and offline services across medical institutions.

[0068] Medical data encryption files may refer to encrypted patient medical data files, such as medical records, test results, imaging materials, and other document-type medical data.

[0069] The identity information may be patient-specific information used for encryption, such as the patient's ID number, medical card number, or biometric data. The identity information may be obtained through the information entry system of the institution corresponding to the first terminal device. For example, when a patient visits a doctor offline, the patient's identity identification medium is read through an information entry device (such as a card reader) to obtain the patient's identity information. The identity identification medium includes at least one of the patient's medical insurance card, ID card, and medical card. When a patient visits a doctor online, the patient's identity information is obtained through a unique identifier such as the ID card number, medical number, medical insurance card number, and mobile phone number input by the patient.

[0070] In one instance, a doctor requests to view a patient's encrypted medical records on his computer through the hospital system; or a researcher requests access to a patient's medical data files in a laboratory.

[0071] S202: If the first terminal device and the second terminal device that generates the medical data do not belong to the same institution, an authorization request is sent to a third terminal device of the target patient.

[0072] In this step, the second terminal device may refer to a medical institution that generates and stores patient medical data, such as a server or diagnostic equipment in a hospital.

[0073] The third terminal device may refer to the patient end used to receive the authorization request, such as the original App / mini program / public account of the medical institution in the patient's smartphone, tablet computer or personal computer.

[0074] An authorization request may refer to an operation requesting the patient to agree to data access, such as sending a request to the patient's mini program through a medical data file sharing system. The patient can then enter the mini program to perform the authorization operation.

[0075] Among them, whether the first terminal device and the second terminal device belong to the same medical institution can be determined by comparing the institution identifier, checking the institution IP address range, device registration information, etc. For example, when receiving a viewing request, the system can compare the institution identifiers of the first terminal device and the second terminal device to determine whether they are the same; or determine whether the devices belong to the same institution through the account information of the medical client of the device.

[0076] S203: If the authorization result returned by the third terminal device indicates that the first terminal device is allowed to view the medical data, a decryption key for the encrypted medical data file is obtained based on the identity information of the target patient.

[0077] The authorization result represents the patient's response to the authorization request, which may be approval or rejection. For example, when the patient makes a request for confirmation on the medical institution's patient service applet corresponding to the third terminal device, the authorization result obtained by the system is approval. When the patient makes a request for cancellation, the authorization result obtained by the system is rejection.

[0078] S204. Decrypt the medical data encrypted file according to the decryption key to obtain the medical data, and return the medical data to the first terminal device.

[0079] Decrypting the encrypted medical data file according to the decryption key may be performed by extracting or converting the decryption key using a symmetric encryption algorithm to obtain a decryption password, and then decrypting the encrypted medical data file according to the decryption password. After obtaining the medical data, the system will display it in the first terminal device so that the doctor or medical staff can view the medical data of the target patient.

[0080] The medical data file sharing method provided in the embodiment of the present application realizes secure data sharing across institutions by combining encryption technology and dynamic authorization mechanism, significantly enhancing data security and privacy protection. Patients control data access through third-party terminal devices to ensure that data is decrypted and shared only with explicit authorization, thereby reducing the risk of data leakage. This not only improves the interoperability and collaboration efficiency of medical information, but also enhances patients' control over personal data, improves trust in the system and satisfaction with medical services.

[0081] Based on the above embodiment, the medical data file sharing method also includes: if the first terminal device and the second terminal device that generates the medical data belong to the same organization, then obtaining the decryption key of the medical data encryption file according to the identity information of the target patient; decrypting the medical data encryption file according to the decryption key to obtain the medical data, and returning the medical data to the first terminal device.

[0082] It is understandable that when the first terminal device (the device requesting to view data) and the second terminal device (the device generating and storing data) belong to the same institution, there is no need to send an authorization request to the patient's third terminal device; the system can directly obtain the decryption key based on the identity information of the target patient; use the decryption key to decrypt the medical data encrypted file to obtain the medical data; and then return the decrypted medical data to the first terminal device. It should be noted that in the case of offline consultations, the patient and the doctor are usually in the same physical environment, and the patient's physical presence can be regarded as an implicit authorization. In addition, offline consultations usually require quick access to medical data to support immediate diagnosis and treatment decisions. Direct decryption of reports can improve efficiency and reduce unnecessary delays. Online remote consultations may involve the transmission of sensitive medical data over the Internet, which increases the risk of data being intercepted or leaked during transmission. Therefore, optionally, when a patient has an online remote consultation and the first terminal device and the second terminal device belong to the same institution, the patient authorization step can be retained before decrypting the report. After the patient agrees, the doctor can view previous medical records or reports to ensure that only doctors with explicit authorization can access and decrypt the report, thereby enhancing data security and privacy protection.

[0083] This method simplifies the medical data access process within the same institution, improves the efficiency of data sharing and user experience, omits unnecessary authorization steps, speeds up data access, reduces the operational burden on patients, and enhances collaboration and information sharing within the institution. At the same time, by reducing the system processing burden and communication overhead, system resources are used more effectively, thereby improving the response speed and overall efficiency of medical services.

[0084] Based on the above embodiment, the medical data file sharing method before S201 also includes: when it is detected that the second terminal device generates medical data, obtaining the identity information of the target patient; hashing the identity information to obtain an encryption key for encrypting the medical data; encrypting the medical data based on a preset symmetric encryption algorithm and encryption key to obtain a medical data encrypted file.

[0085] Among them, when the second terminal device generates new medical data, the system can automatically detect and trigger the report encryption task by monitoring the report generation event, or the report encryption task can be triggered by the doctor or medical staff performing operations related to report encryption in the second terminal device.

[0086] Furthermore, the system can set an event listener on the second terminal device to monitor medical data generation events. When new medical data (such as diagnostic reports and test results) are generated, the system starts the smart contract to execute the predefined report encryption task. This method has a high degree of automation, does not require human intervention, reduces human errors, is real-time, and can encrypt data at the moment of generation to ensure data security. An option can also be provided in the user interface of the second terminal device to allow doctors or medical personnel to manually trigger encryption tasks. For example, when generating a report, medical personnel can select the "Encrypt and Save" option. These two methods can be used in combination to meet the needs of different scenarios. The automatic monitoring mechanism is suitable for routine operations to ensure that data is encrypted immediately when it is generated, while the manual triggering mechanism provides flexibility for medical personnel and is suitable for situations that require special processing.

[0087] In this step, when the encryption task is triggered, the system extracts the target patient's identity information from the patient's record, which may include the patient's ID number, medical card number or other preset unique identifier; then the obtained identity information is hashed to generate a unique hash value to ensure the confidentiality of the identity information and as the basis for generating an encryption key; the hashed identity information is used to generate the encryption key required for the symmetric encryption algorithm; based on the preset symmetric encryption algorithm, the generated encryption key is used to encrypt the medical data to generate a medical data encrypted file. Among them, the preset symmetric encryption algorithm can be AES (Advanced Encryption Standard), DES (Data Encryption Standard), 3DES (Triple DES), SM4 (symmetric encryption standard corresponding to the password management bureau), etc.

[0088] In one example, based on a preset symmetric encryption algorithm, medical data is encrypted using a generated encryption key to generate a medical data encrypted file, including: according to a preset SM4 encryption algorithm, the medical data is divided into blocks to obtain data blocks of a fixed size; according to the encryption key and the SM4 encryption algorithm, each data block is encrypted; all encrypted data blocks are combined to obtain the final medical data encrypted file.

[0089] This method significantly enhances data security and privacy protection by encrypting medical data when it is generated. The encryption key is generated using patient identity information to ensure that only the party with the patient's identity information can decrypt and access the data. At the same time, the identity information is protected from direct exposure through hashing. The symmetric encryption algorithm not only ensures the confidentiality of the data, but also ensures data integrity and prevents tampering through its characteristics. In addition, the automated key generation and management process reduces manual intervention. Patients and doctors do not know what the key is, which prevents the key from being lost, forgotten, or leaked, and improves the accuracy and efficiency of operations. Therefore, this method optimizes system performance and operation processes while ensuring data security.

[0090] On the basis of the above-mentioned embodiment, the method described in S203 for obtaining the decryption key of the medical data encrypted file according to the identity information of the target patient includes: hashing the identity information of the target patient to obtain the hash value corresponding to the identity information; generating the decryption key of the medical data encrypted file according to the preset symmetric encryption algorithm requirements and the hash value. In this step, the system first hashes the identity information of the target patient, the identity information may be the patient's ID number, medical card number or other preset unique identifier, and converts the identity information into a hash value of a fixed length. Since this process is irreversible, the security of the identity information can be ensured; using the generated hash value as a basis, according to the requirements of the preset symmetric encryption algorithm (such as SM4), a decryption key is generated, and the decryption key is the same as the key used for encryption, ensuring that the medical data encrypted file can be correctly decrypted. Among them, the requirements of the preset symmetric encryption algorithm (such as SM4) may be the specific requirements and format of the algorithm for the key, such as requiring the key length to be 128 bits.

[0091] Therefore, by hashing the patient's identity information to generate a decryption key, data security and privacy protection can be enhanced, ensuring that the identity information is not directly exposed and preventing sensitive information from being leaked. At the same time, the decryption key generated based on the hash value matches the encryption key, ensuring the integrity and consistency of the data, so that only devices and personnel with the patient's identity information can access and decrypt the data.

[0092] Based on the above embodiment, the medical data file sharing method also includes: storing the encrypted medical data file; and / or sending the encrypted medical data file to a third terminal device; and / or sending the encrypted medical data file to a storage device corresponding to the second terminal device for storage.

[0093] In one example, the medical data file sharing method further includes: storing the medical data encrypted file.

[0094] In another example, the medical data file sharing method further includes: sending the encrypted medical data file to a third terminal device.

[0095] In another example, the medical data file sharing method further includes: sending the encrypted medical data file to a storage device corresponding to the second terminal device for storage.

[0096] In another example, the medical data file sharing method further includes: storing the encrypted medical data file, and sending the encrypted medical data file to a third terminal device.

[0097] Optionally, the medical data file sharing method further includes: storing the encrypted medical data file, sending the encrypted medical data file to a storage device corresponding to the second terminal device for storage, and sending the encrypted medical data file to a third terminal device.

[0098] Storing the encrypted medical data file may refer to storing the encrypted medical data file in the local storage system of the second terminal device, thereby ensuring that the data is securely stored immediately after generation, facilitating subsequent access and processing. It may also refer to sending the encrypted file to a remote storage device (such as cloud storage or data center) corresponding to the second terminal device for storage, so as to provide higher storage capacity and data backup capabilities. The medical data file sharing system can quickly search for the corresponding file from the original local storage system or remote storage device of the medical institution through the storage information of the corresponding file.

[0099] Sending the encrypted medical data file to a third terminal device may mean sending the encrypted file to the third terminal device or a cache device of the medical institution corresponding to the third terminal device when sharing or backup is required, so as to realize data sharing across medical institutions.

[0100] Sending the encrypted medical data file to the storage device corresponding to the second terminal device for storage may mean that after the medical data is encrypted, the encrypted medical data file is sent to the patient end where the corresponding patient is located or the storage device corresponding to the patient end, so that the patient can store, authorize, download, forward, and other further processes the file.

[0101] By storing and transmitting encrypted medical data files, this method further enhances the security and accessibility of data. Storing encrypted files ensures that data is protected immediately after generation to prevent data loss or unauthorized access. Sending encrypted files to third-party terminal devices or other storage devices supports flexible data sharing and backup strategies to meet data management needs in different scenarios. This not only improves data security and reliability, but also enhances the flexibility and scalability of the system, supporting a wider range of medical data applications and collaboration.

[0102] On the basis of the above-mentioned embodiment, the medical data file sharing method further includes: obtaining the file identification, file storage address and identification of the institution where the second terminal device is located of the medical data encryption file; storing the file identification, file storage address and identification of the institution where the second terminal device is located of the medical data encryption file on the chain. Among them, the file identification can identify a specific medical data encryption file, such as the hash value or other unique identifier of the file; the file storage address is used to record the storage location of the medical data encryption file, such as a local path, a remote storage URL or a cloud storage address; and using blockchain technology to store the data record (file identification, file storage address, identification of the institution where the file is generated).

[0103] By storing the relevant information of encrypted medical data files on the chain, the immutability of the blockchain can be used to ensure that the records of file identification, storage address, and the identification of the institution where the second terminal device is located cannot be modified or deleted without authorization, thereby enhancing the integrity and credibility of the data. In addition, on-chain storage provides a traceable history that facilitates auditing and verifying the source and storage location of the data. It not only improves the security of data sharing and management, but also supports cross-institutional data collaboration and supervision, and promotes the trusted circulation and use of medical data.

[0104] On the basis of the above embodiment, the medical data file sharing method further includes: obtaining the identification of the institution where the first terminal device is located, as well as the viewing purpose, viewing time and file identification of the medical data encrypted file; storing the identification of the institution where the first terminal device is located, as well as the viewing purpose, viewing time and file identification of the medical data encrypted file on the chain. Among them, the identification of the institution where the first terminal device is located may refer to the unique identifier of the institution to which the terminal device requesting access to the medical data encrypted file belongs; the viewing purpose may refer to recording the purpose or use of accessing the medical data encrypted file, such as for diagnosis, research or supervision; the viewing time may refer to recording the specific time and date of the access request for tracking or supervision; using blockchain technology to store the access record of the data file (the identification of the institution where the first terminal device is located, as well as the viewing purpose, viewing time and file identification of the file) on the blockchain.

[0105] By storing the access records of encrypted medical data files on-chain, the transparency and security of data access are enhanced. At the same time, medical (original or encrypted) data is not stored on the chain, only data records and access records are recorded, making the system more portable.

[0106] Next, taking the example of a patient seeing a doctor in a medical institution based on the original medical data file, it is explained how to use the medical data file sharing method provided in the embodiment of the present application to ensure the security of the electronic report file through encryption and decryption while achieving the purpose of file sharing. Figure 3 A schematic diagram of a medical data file encryption method provided in this application, such as Figure 3 As shown, the medical data file encryption method includes:

[0107] S301, read the identity information such as medical insurance card / medical card, etc.

[0108] Among them, the system reads the information in medical insurance cards / medical cards and other documents through the medical institution's own card reader or other equipment. The system can monitor the information read by the medical institution's own card reader or other equipment in real time. When the patient's electronic report / data and other files are generated, the system triggers the smart contract to obtain the corresponding information, such as ID number, name and other key information used to identify the target patient.

[0109] S302, hashing the patient's identity information to generate a key.

[0110] In this step, the smart contract hashes the read patient information and generates an encryption key that meets the SM4 encryption requirements.

[0111] S303, SM4 generates an encryption password.

[0112] Among them, the encryption password of the patient can be generated based on the encryption key of S302 and SM4.

[0113] S304. Encrypt electronic reports / data.

[0114] Furthermore, the smart contract uses the encryption password of S303 to encrypt the patient's electronic report / data and other files; and sends the encrypted files to the corresponding patient, such as the patient end such as the mini program.

[0115] Figure 4 A specific flow chart of a medical data file encryption method provided in this application is as follows: Figure 4As shown, when a patient swipes a card (medical insurance card or ID card or medical card, etc.) to see a doctor, checks various indicators, takes a CT scan, and finally generates an examination report, the smart contract in the medical service blockchain reads the patient's personal information and generates a key based on hashing and SM4 algorithm; an encryption password is generated based on the key and the examination report is encrypted to generate an encrypted report; optionally, the encrypted report is displayed on the patient side.

[0116] Figure 5 A flowchart of a medical data file decryption method provided in this application is shown in FIG. Figure 5 As shown, the medical data file decryption method includes:

[0117] S501, read the identity information such as medical insurance card / medical card.

[0118] S502: Hash the patient's identity information to generate a key.

[0119] In this step, the smart contract uses SM4 to calculate the read patient identity information and generate a decryption key, where the decryption key for each patient is the same as the encryption key.

[0120] S503, SM4 generates a decryption password.

[0121] S504. Decrypt electronic report / data.

[0122] Furthermore, the smart contract uses the decryption password of S503 to decrypt the electronic report / data and other files encrypted by the patient; the medical staff can then read the decrypted files.

[0123] Figure 6 A specific flow chart of a medical data file decryption method provided in this application, such as Figure 6 As shown, the patient goes to the medical institution offline to swipe the card for medical treatment, and the doctor retrieves the report from the system; after retrieving the report, the smart contract in the medical service blockchain reads the patient's personal information and generates a key based on hashing and SM4 algorithm; a decryption password is generated based on the key and the report is decrypted to obtain a decrypted electronic report; the doctor reads the decrypted electronic report through the client of the hospital institution and the medical platform and performs diagnosis.

[0124] Optionally, doctors can retrieve reports from the system in two situations: retrieval of reports from the doctor's medical institution and retrieval of reports from other medical institutions. When doctors retrieve reports from other medical institutions, they need to obtain patient authorization results before the smart contract decrypts the report. Decryption can only be performed when the patient agrees that the doctor retrieves reports from other medical institutions. At the same time, patients can also perform selective file authorization on the patient side. For example, patients only authorize access requests to files related to this diagnosis or within a certain time period. Then, when doctors view the decrypted files, they can only see files authorized by the patient.

[0125] When patients see a doctor online and the remote doctor / medical institution needs to retrieve the patient's past medical records, CT scans and other documents, all shared medical data files must be authorized by the patient before they can be used, considering the security of the patient's privacy data. Figure 7 A specific flow chart of another medical data file decryption method provided by this application, such as Figure 7 As shown, when the doctor retrieves the report from the system, he initiates an authorization access request to the patient and stores the record on the chain; after the patient authorizes (the patient's authorization record is stored on the chain), the smart contract in the medical service blockchain reads the patient's personal information (determined by the patient's account authentication information), generates a decryption key and decrypts the electronic report, so that the doctor can read the decrypted electronic report through the client of the medical institution and perform diagnosis and processing. In one example, the doctor / medical institution clicks to open the encrypted electronic report (obtained through the patient's sharing) or clicks the "decrypt report" button in the client, which is regarded as applying for access.

[0126] The use of blockchain smart contract technology can not only control data permissions, but also use the SM4 national encryption algorithm to decrypt electronic reports and other medical records data files based on patient information, and share them with medical institutions for remote diagnosis. The use process and purpose of medical data will leave traces on the chain.

[0127] The medical data file sharing method provided in the embodiment of the present application completes the encryption and decryption of medical data without the "perception" of users such as doctors and patients, and is easy to use; the blockchain smart contract is only used to encrypt and decrypt electronic reports but not to store reports, which greatly facilitates service resources and human resource development; the entire process of medical data file generation and access records is recorded on the chain, which is convenient for subsequent accountability and prevents the abuse of medical data; patients do not need to specially save and record keys, which also prevents the problem of key loss and data leakage; for the safe sharing of medical data, the patient's privacy data is returned to the patient himself, and the medical institution is not the only subject of data sharing to reduce the leakage and abuse of medical privacy data.

[0128] Figure 8 A schematic diagram of the structure of the medical data file sharing device provided in this application, such as Figure 8As shown, the medical data file sharing device 80 provided in this embodiment includes:

[0129] The receiving module 801 is used to receive a request for viewing a medical data encryption file of a target patient sent by a first terminal device, where the medical data encryption file is obtained by encrypting the medical data of the target patient using the identity information of the target patient;

[0130] A sending module 802, configured to send an authorization request to a third terminal device of the target patient if the first terminal device and the second terminal device generating the medical data do not belong to the same institution;

[0131] The acquisition module 803 is used to acquire a decryption key of the medical data encryption file according to the identity information of the target patient if the authorization result returned by the third terminal device indicates that the first terminal device is allowed to view the medical data;

[0132] The processing module 804 is used to decrypt the medical data encrypted file according to the decryption key, obtain the medical data, and return the medical data to the first terminal device.

[0133] In a possible implementation, the acquisition module 803 may also be used to:

[0134] If the first terminal device and the second terminal device generating the medical data belong to the same institution, obtaining a decryption key for the encrypted file of the medical data according to the identity information of the target patient;

[0135] The medical data encrypted file is decrypted according to the decryption key to obtain the medical data, and the medical data is returned to the first terminal device.

[0136] In a possible implementation, the acquisition module 803 may also be used to:

[0137] Hash the identity information of the target patient to obtain the hash value corresponding to the identity information;

[0138] Generate the decryption key of the medical data encrypted file according to the preset symmetric encryption algorithm requirements and hash value.

[0139] In a possible implementation, the processing module 804 may also be used to:

[0140] When it is detected that the second terminal device generates medical data, obtaining the identity information of the target patient;

[0141] The identity information is hashed to obtain the encryption key for encrypting the medical data;

[0142] Based on the preset symmetric encryption algorithm and encryption key, the medical data is encrypted to obtain an encrypted medical data file.

[0143] In a possible implementation, the processing module 804 may also be used to:

[0144] Encrypt medical data files for storage;

[0145] and / or,

[0146] Sending the encrypted medical data file to a third terminal device;

[0147] and / or,

[0148] The encrypted medical data file is sent to the storage device corresponding to the second terminal device for storage.

[0149] In a possible implementation, the processing module 804 may also be used to:

[0150] Obtaining a file identifier of the medical data encryption file, a file storage address, and an identifier of the institution where the second terminal device is located;

[0151] The file identifier, file storage address of the medical data encryption file and the identifier of the institution where the second terminal device is located are stored on the chain.

[0152] In a possible implementation, the processing module 804 may also be used to:

[0153] Obtaining the identification of the institution where the first terminal device is located, as well as the viewing purpose, viewing time, and file identification of the encrypted medical data file;

[0154] The identification of the institution where the first terminal device is located, as well as the viewing purpose, viewing time and file identification of the medical data encrypted file are stored on the chain.

[0155] The medical data file sharing device provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and this embodiment will not be described in detail here.

[0156] Fig. 9 This is a schematic diagram of the structure of the electronic device provided in this application. Fig. 9 As shown, the electronic device 90 provided in this embodiment includes: at least one processor 901 and a memory 902. Optionally, the device 90 further includes a communication component 903. The processor 901, the memory 902 and the communication component 903 are connected via a bus 904.

[0157] In a specific implementation process, at least one processor 901 executes the computer execution instructions stored in the memory 902, so that at least one processor 901 executes the above method.

[0158] The specific implementation process of the processor 901 can be found in the above method embodiment, and its implementation principle and technical effect are similar, so this embodiment will not be repeated here.

[0159] In the above embodiments, it should be understood that the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), etc. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in the invention may be directly implemented as being executed by a hardware processor, or may be executed by a combination of hardware and software modules in the processor.

[0160] The memory may include a high-speed memory (Random Access Memory, RAM), and may also include a non-volatile memory (Non-volatile Memory, NVM), such as at least one disk memory.

[0161] The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, the bus in the drawings of the present application is not limited to only one bus or one type of bus.

[0162] The present application also provides a computer program product, including a computer program, which implements the above method when executed by a processor.

[0163] The present application also provides a computer-readable storage medium, in which computer-executable instructions are stored. When a processor executes the computer-executable instructions, the above method is implemented.

[0164] The above-mentioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The readable storage medium can be any available medium that can be accessed by a general or special-purpose computer.

[0165] An exemplary readable storage medium is coupled to a processor so that the processor can read information from the readable storage medium and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can be located in an application specific integrated circuit (Application Specific Integrated Circuits, referred to as: ASIC). Of course, the processor and the readable storage medium can also exist in the device as discrete components.

[0166] The division of units is only a logical function division, and there may be other divisions in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interface, device or unit, which can be electrical, mechanical or other forms.

[0167] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0168] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0169] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods of each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, etc. Various media that can store program codes.

[0170] Those skilled in the art can understand that all or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, disk or optical disk and other media that can store program codes.

[0171] Finally, it should be noted that those skilled in the art will readily conceive of other embodiments of the present invention after considering the specification and practicing the invention disclosed herein. The present invention is intended to cover any variations, uses or adaptations of the present invention, which follow the general principles of the present invention and include common knowledge or customary technical means in the art not disclosed by the present invention, are not limited to the precise structure described above and shown in the drawings, and may be modified and changed in various ways without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.

Claims

1. A medical data file sharing method, characterized in that: include: receiving a request for viewing a medical data encryption file of a target patient sent by a first terminal device, wherein the medical data encryption file is obtained by encrypting the medical data of the target patient using the identity information of the target patient; If the first terminal device and the second terminal device that generates the medical data do not belong to the same institution, sending an authorization request to a third terminal device of the target patient; If the authorization result returned by the third terminal device indicates that the first terminal device is allowed to view the medical data, then obtaining a decryption key for the medical data encryption file according to the identity information of the target patient; The medical data encrypted file is decrypted according to the decryption key to obtain the medical data, and the medical data is returned to the first terminal device.

2. The method according to claim 1, characterized in that The method further comprises: If the first terminal device and the second terminal device that generates the medical data belong to the same organization, obtaining a decryption key for the encrypted file of the medical data according to the identity information of the target patient; The medical data encrypted file is decrypted according to the decryption key to obtain the medical data, and the medical data is returned to the first terminal device.

3. The method according to claim 1 or 2, characterized in that: Before receiving the request for viewing the encrypted medical data file of the target patient sent by the first terminal device, the method further includes: When detecting that the second terminal device generates the medical data, acquiring the identity information of the target patient; Hash processing is performed on the identity information to obtain an encryption key for encrypting the medical data; Based on a preset symmetric encryption algorithm and the encryption key, the medical data is encrypted to obtain the medical data encrypted file.

4. The method according to claim 1 or 2, characterized in that: The step of obtaining the decryption key of the medical data encrypted file according to the identity information of the target patient includes: Performing hashing on the identity information of the target patient to obtain a hash value corresponding to the identity information; A decryption key for the medical data encrypted file is generated according to the preset symmetric encryption algorithm requirements and the hash value.

5. The method according to claim 3, characterized in that: The method further comprises: Storing the encrypted medical data file; and / or, Sending the encrypted medical data file to the third terminal device; and / or, The encrypted medical data file is sent to the storage device corresponding to the second terminal device for storage.

6. The method according to claim 3, characterized in that The method further comprises: Obtaining a file identifier and a file storage address of the medical data encryption file and an identifier of an institution where the second terminal device is located; The file identifier, file storage address of the medical data encryption file and the identifier of the institution where the second terminal device is located are stored on the chain.

7. The method according to claim 1 or 2, characterized in that: The method further comprises: Obtaining the identification of the institution where the first terminal device is located, as well as the viewing purpose, viewing time and file identification of the encrypted medical data file; The identification of the institution where the first terminal device is located, as well as the viewing purpose, viewing time and file identification of the medical data encrypted file are stored on the chain.

8. A medical data file sharing device, characterized in that: include: A receiving module, configured to receive a request for viewing a medical data encryption file of a target patient sent by a first terminal device, wherein the medical data encryption file is obtained by encrypting the medical data of the target patient using the identity information of the target patient; a sending module, configured to send an authorization request to a third terminal device of the target patient if the first terminal device and the second terminal device generating the medical data do not belong to the same institution; an acquisition module, configured to acquire a decryption key for the encrypted medical data file according to the identity information of the target patient if the authorization result returned by the third terminal device indicates that the first terminal device is allowed to view the medical data; The processing module is used to decrypt the medical data encrypted file according to the decryption key, obtain the medical data, and return the medical data to the first terminal device.

9. An electronic device, characterized in that: include: Memory, processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 7 when executed.

11. A computer program product, comprising a computer program, wherein when the computer program is executed, the method according to any one of claims 1 to 7 is implemented.

Images