Medical privacy data sharing method and system, terminal and storage medium

Abstract

The invention provides a medical privacy data sharing method and system, a terminal and a storage medium, and belongs to the technical field of medical data processing. A medical processing terminal obtains a medical encryption key from a medical institution data platform; the medical processing terminal encrypts the medical privacy data set based on the medical encryption key to obtain a medical privacy ciphertext; the medical processing terminal calculates an encryption identification code of the medical privacy ciphertext, and encrypts the encryption identification code of the medical privacy ciphertext to obtain medical privacy signature data; and the medical processing terminal sends the medical privacy ciphertext and the medical privacy signature data to the medical institution data platform. According to the method, the medical processing terminal is encrypted based on the encryption private key of the medical processing terminal to obtain the medical privacy signature data, the medical institution data platform can confirm the authenticity and integrity of the data by verifying the signature data, and the problem that the data may be tampered in the sharing process is avoided.

Description

Technical Field

[0001] This invention belongs to the field of medical data processing technology, and in particular relates to a method, system, terminal and storage medium for sharing medical privacy data. Background Technology

[0002] In the course of medical services, medical privacy data involves patient privacy and personal information. This data is generated during medical activities and includes personal information, mental health status, physiological data, lifestyle information, and health status information, such as disease diagnosis, symptoms, and medical history.

[0003] Existing medical data sharing systems often employ global encryption, failing to differentiate between critical privacy information (such as patient IDs and medical history) and routine information (such as statistical indicators). This leads to inefficient processing and over-encryption issues. When using these systems, multiple terminals typically access the data platform, which relies solely on one-way hash verification, lacking a two-layer verification mechanism combining digital signatures and encrypted identifiers. Data may be tampered with during sharing, making it difficult for recipients to verify the authenticity and integrity of the data. Furthermore, medical encryption uses static key allocation, failing to dynamically bind keys to data processing rules, thus posing a risk of key leakage. Summary of the Invention

[0004] This invention provides a method for sharing medical privacy data. The method encrypts medical processing terminal private key to obtain medical privacy signature data. Medical institution data platforms can verify the authenticity and integrity of the data by verifying the signature data, thus avoiding the problem of data tampering during the sharing process.

[0005] The methods include: S101, the medical processing terminal obtains the medical encryption key from the medical institution's data platform; S102, the medical processing terminal encrypts the medical privacy dataset based on the medical encryption key to obtain medical privacy ciphertext; S103, the medical processing terminal calculates the encryption identifier code of the medical privacy ciphertext, and encrypts the encryption identifier code of the medical privacy ciphertext based on the encryption private key of the medical processing terminal to obtain medical privacy signature data; S104, the medical processing terminal sends the medical privacy encrypted data and medical privacy signature data to the medical institution's data platform.

[0006] Preferably, step S102 further includes: The medical processing terminal extracts key medical information and routine medical information defined in the privacy data processing rules from the medical privacy dataset based on the privacy data processing rules. The medical processing terminal uses the encryption method defined in the privacy data processing rules to encrypt the medical critical information and the corresponding routine medical information to obtain the encryption result. The medical processing terminal generates encrypted medical files containing medical privacy data based on key medical information and corresponding encryption results, and then provides them to the medical institution's data platform.

[0007] Preferably, the medical institution's data platform verifies the encrypted medical files based on privacy data processing rules, and saves the encrypted medical files according to the verification results; The verification method for encrypted medical files includes verifying key medical information within the encrypted medical files and obtaining the verification results corresponding to the key medical information.

[0008] Preferably, in the method, the medical processing terminal configures the medical information hash value of the medical key information value based on a preset encryption algorithm; The medical processing terminal uses the timestamp of the medical information generated for this medical privacy dataset as a symmetric key to encrypt the hash value of the medical information, thus obtaining the encrypted hash value. The medical processing terminal uses the platform's public key for encryption to obtain the encryption key; The medical processing terminal provides the encrypted hash value and encryption key to the medical institution's data platform.

[0009] Preferably, the medical institution's data platform decrypts the encryption key based on the platform's private encryption key to obtain a symmetric key; The medical institution's data platform uses a symmetric key to decrypt the encrypted hash value, thus obtaining the hash value of the medical information. The medical institution's data platform encrypts the hash value of medical information based on the encryption key defined with the data recipient, and saves the encrypted hash value of medical information.

[0010] Preferably, the method further includes the following steps before step S101: The medical processing terminal obtains the data transmission request sent by the user and determines the medical privacy dataset associated with the medical privacy data transmission request; The medical processing terminal sends a medical data transmission request to the medical institution's data platform; The medical processing terminal receives a transmission policy associated with medical privacy data sent by the medical institution's data platform. The transmission policy is used to configure security verification information. The medical privacy dataset, which is associated with the transmission policy and the medical privacy data transmission request, is sent to the medical institution's data platform.

[0011] Preferably, the method further includes: the medical institution's data platform receiving a medical data transmission request sent by a medical processing terminal; Medical institution data platforms determine transmission strategies for data related to medical privacy. The received information is returned to the medical processing terminal based on the transmission strategy.

[0012] This application also provides a medical privacy data sharing system, which includes: a medical processing terminal and a medical institution data platform; The medical processing terminal obtains the medical encryption key from the medical institution's data platform and uses the medical encryption key to encrypt the medical privacy dataset; The medical processing terminal encrypts the medical privacy dataset based on the medical encryption key to obtain the medical privacy ciphertext; The medical processing terminal calculates the encryption identifier code of the medical privacy ciphertext, and encrypts the encryption identifier code of the medical privacy ciphertext based on the encryption private key of the medical processing terminal to obtain medical privacy signature data; The medical processing terminal sends encrypted medical privacy data and medical privacy signature data to the medical institution's data platform.

[0013] According to another embodiment of this application, an electronic device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the steps of a method for sharing medical privacy data.

[0014] According to another embodiment of this application, a storage medium is also provided, on which a computer program is stored, wherein the computer program, when executed by a processor, implements the steps of a method for sharing medical privacy data.

[0015] As can be seen from the above technical solutions, the present invention has the following advantages: The medical privacy data sharing method provided in this application encrypts the medical privacy dataset using a medical encryption key to generate medical privacy ciphertext, protecting the confidentiality of medical data during transmission and storage, and solving the problem of potential data theft or illegal acquisition. Considering that data may be tampered with during sharing, and that the recipient may have difficulty verifying the authenticity and integrity of the data, this application configures an encryption identifier code for the medical privacy ciphertext and encrypts it based on the encryption private key of the medical processing terminal to obtain medical privacy signed data. The medical institution's data platform can verify the authenticity and integrity of the data by verifying the signed data, avoiding the problem of data tampering going undetected.

[0016] In this application, the medical processing terminal extracts key and routine information from medical privacy data according to clearly defined privacy data processing rules, and encrypts it accordingly. The medical institution's data platform also verifies the encrypted files according to the same rules, ensuring the standardization of data processing and avoiding data security and compliance risks caused by inconsistent or non-standard processing methods. From the medical processing terminal extracting and encrypting information according to privacy data processing rules, to the medical institution's data platform verifying and storing it according to the same rules, this application ensures the standardization and consistency of data throughout the entire process from generation to storage, avoiding data processing chaos caused by differences in rules at different stages. Attached Figure Description

[0017] To more clearly illustrate the technical solution of the present invention, the accompanying drawings used in the description will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 Flowchart of methods for sharing medical privacy data; Figure 2 Flowchart of an embodiment of a method for sharing medical privacy data; Figure 3 Flowchart of another embodiment of a method for sharing medical privacy data; Figure 4 This is a schematic diagram of an electronic device. Detailed Implementation

[0019] The following details the execution process of the medical privacy data sharing method. Specific details, such as particular system architectures and technologies, are presented for illustrative purposes rather than limiting, to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application can also be implemented in other embodiments without these specific details.

[0020] To facilitate a clear description of the technical solutions of this application, the terms "first" and "second" are used to distinguish identical or similar items with essentially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and that the terms "first" and "second" do not necessarily imply that they are different.

[0021] The terms "one embodiment" or "some embodiments" used in this application mean that one or more embodiments of this application include the specific features, structures, or characteristics described in that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this application do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized.

[0022] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0023] Please see Figure 1 The diagram shows a flowchart of a medical privacy data sharing method in a specific embodiment. The method includes: S101, the medical processing terminal obtains the medical encryption key from the medical institution's data platform.

[0024] In this embodiment, a secure communication channel is established between the medical processing terminal and the medical institution's data platform. Through this secure communication channel, the medical institution's data platform sends a medical encryption key to the medical processing terminal.

[0025] In this embodiment, the medical processing terminal encrypts the medical user's identity information based on its private encryption key to obtain encrypted medical user identity information; and sends a synchronization key request, including the medical user's identity information and the encrypted medical user's identity information, to the medical institution's data platform.

[0026] The medical institution's data platform can receive synchronization key requests sent by medical processing terminals. These requests include the medical user's identity information and encrypted medical user identity information, obtained by encrypting the medical user's identity information using the medical processing terminal's private key. The platform then parses the synchronization key request to obtain the medical user's identity information and the encrypted medical user identity information. It then searches for the locally stored encryption public key of the medical processing terminal corresponding to the medical user's identity information. Based on this public key, it decrypts the encrypted medical user's identity information to obtain the decrypted medical user's identity information. Next, it searches for the corresponding medical encryption key. Finally, it encrypts the medical encryption key using the medical processing terminal's public key and returns the encrypted medical encryption key to the medical processing terminal.

[0027] The medical processing terminal receives the encrypted medical encryption key returned by the medical institution's data platform; it then decrypts the encrypted medical encryption key using the medical processing terminal's private key to obtain the medical encryption key.

[0028] In this embodiment, the medical processing terminal can send an access request to the medical institution's data platform. After receiving the access request from the medical processing terminal, the medical institution's data platform configures an account for the medical processing terminal and sets the address of the medical processing terminal.

[0029] For example, a medical institution's data platform can use an asymmetric encryption system to securely distribute symmetric keys. The medical institution's data platform generates a public-private key pair (PK, SK), and the medical processing terminals pre-register and obtain the public key PK.

[0030] The medical institution's data platform generates a symmetric key K (such as an AES-256 key), which is then encrypted using the terminal's public key. .

[0031] The medical processing terminal receives E through a secure channel K And decrypt it using your own private key: Asymmetric encryption is used to avoid the risk of key leakage. Only entities with the correct decryption key can access the medical privacy dataset, thus achieving access control.

[0032] S102, the medical processing terminal encrypts the medical privacy dataset based on the medical encryption key to obtain the medical privacy ciphertext.

[0033] In this embodiment, the medical processing terminal encrypts each data block of the medical privacy dataset sequentially using a medical encryption key, according to a selected encryption algorithm, such as the one described above. After all data blocks are encrypted, these encrypted blocks are combined to form a complete medical privacy ciphertext.

[0034] In practice, suppose we have a medical privacy dataset: ,in It is the first i Each medical privacy data block. The medical processing terminal processes each block through a cyclical operation. Execute based on the following formula: Finally, the ciphertext was obtained. .

[0035] This encryption of the entire medical privacy dataset further ensures data confidentiality. The entire dataset exists in encrypted form during transmission and storage, reducing the risk of data leakage. Furthermore, the encryption process typically preserves the data's length and structure, allowing for accurate reconstruction of the original data after decryption, thus guaranteeing data integrity.

[0036] S103, the medical processing terminal calculates the encryption identifier code of the medical privacy ciphertext, and encrypts the encryption identifier code of the medical privacy ciphertext based on the encryption private key of the medical processing terminal to obtain medical privacy signature data.

[0037] The private key for the medical processing terminal is configured based on a pre-set encryption algorithm on the medical institution's data platform. The public key for the medical processing terminal corresponds to its private key, and the public key for the platform corresponds to its private key.

[0038] Optionally, the medical processing terminal and the medical institution's data platform negotiate and preset an encryption algorithm, each generating a public key and a private key pair, and sending the public key to the medical processing terminal. Specifically, after the medical institution's data platform presets the encryption algorithm, the medical processing terminal generates its own encryption public key and private key, while the medical institution's data platform generates its own encryption public key and private key.

[0039] In this embodiment, the encrypted identifier can be obtained by performing a specific hash operation on the medical privacy ciphertext. A hash function can map data of any length to a fixed-length hash value, which can serve as a unique identifier for the data. The calculated encrypted identifier is then encrypted using the medical processing terminal's encryption private key to generate medical privacy signature data.

[0040] This embodiment can use an asymmetric encryption algorithm. Assume the medical processing terminal's private key is d, the public key is e, and the modulus is n. The medical privacy signature data is... This means encrypting the encrypted identifier H using the private key d. When verifying the signature, the recipient can decrypt it using the corresponding public key e. and the decrypted result The hash value is compared with the recalculated ciphertext hash. In this way, by encrypting the encrypted identifier using the medical processing terminal's private key, the medical institution's data platform can use the corresponding public key to verify the signature, thereby confirming that the data originates from the medical processing terminal and preventing data forgery.

[0041] S104, the medical processing terminal sends the medical privacy encrypted data and medical privacy signature data to the medical institution's data platform.

[0042] In this embodiment, after receiving the medical privacy ciphertext and medical privacy signature data, the medical institution data platform can decrypt the medical privacy signature data based on the encryption public key of the medical processing terminal. If the decrypted encryption identifier code is consistent with the encryption identifier code of the recalculated medical privacy ciphertext, the signature verification is successful. Then, the medical privacy ciphertext is decrypted based on the medical encryption key to obtain the medical privacy dataset.

[0043] As can be seen, in the medical data sharing method involved in this application, data may be damaged or lost due to network transmission problems, storage failures, or other reasons during the medical data sharing process. In this embodiment, the medical processing terminal and the medical institution's data platform use the same algorithm to recalculate the encryption identifier code based on the received medical privacy ciphertext, and then compare it with the received encryption identifier code. If they match, it indicates that the data has not been tampered with or damaged during transmission, ensuring data integrity; if they do not match, it indicates that the data may have problems and needs to be re-acquired or further checked. This ensures the accuracy and integrity of medical data.

[0044] Medical privacy data involves multiple stakeholders, including medical institutions, medical processing terminals, and medical users. It is crucial to ensure that only authorized devices or users can access and use the data. In a data sharing system, each medical processing terminal or user is assigned a unique encrypted identifier, which is then bound to their corresponding identity information and authorization permissions. When a medical processing terminal sends encrypted medical privacy data along with the encrypted identifier, the medical institution's data platform can verify the sender's identity and access rights by confirming the encrypted identifier. Only requests with verified identity and matching permissions are allowed to access and use the data. This effectively prevents unauthorized access and data leakage, protects patient privacy and the security of medical data, and maintains the order and stability of the medical data sharing system.

[0045] In this embodiment, when generating the medical encryption key, the encryption identifier can be combined with other factors to increase the key's complexity and security. During decryption, the encryption identifier is also verified to ensure the correct decryption key is used, thereby correctly decrypting the medical privacy ciphertext. Furthermore, the encryption identifier can also be used for version management of encryption algorithms and keys. When the encryption algorithm or key is updated, the encryption identifier is updated to ensure that data encryption and decryption operations can be performed correctly. This enhances the security of medical data encryption and decryption, protecting the confidentiality of medical privacy data.

[0046] Based on the above embodiments, in order to further improve the reliability of the medical privacy data sharing method provided in the above embodiments, the following is an implementable method combining the above approach, such as... Figure 2 As shown, one embodiment includes the following steps: S201, Medical processing terminal obtains platform encryption public key.

[0047] In this embodiment, the medical processing terminal acquires and stores the platform's encrypted public key. After the medical processing terminal and the medical institution's data platform negotiate a preset encryption algorithm, the medical institution's data platform can generate corresponding asymmetric public and private keys. The medical institution's data platform stores its own asymmetric private key locally, while sending the platform's encrypted public key to the medical processing terminal.

[0048] After receiving the platform's encryption public key, the medical processing terminal can store the platform's encryption public key locally. When the platform's encryption public key is needed, it can be retrieved locally.

[0049] S202, the medical processing terminal encrypts the medical encryption key based on the platform's encryption public key to obtain the key ciphertext.

[0050] S203, the medical processing terminal sends the encrypted key to the medical institution's data platform.

[0051] The medical processing terminal simultaneously sends medical privacy ciphertext, medical privacy signature data, and key ciphertext to the medical institution's data platform. The medical institution's data platform can obtain the medical encryption key by: receiving the key ciphertext sent by the medical processing terminal (which is obtained by encrypting a randomly generated medical encryption key using the platform's public encryption key); and decrypting the key ciphertext using the platform's private encryption key.

[0052] Furthermore, as a refinement and extension of the specific implementation methods of the above embodiments, in order to fully illustrate the specific implementation process in this embodiment, as follows: Figure 3 As shown, the method for sharing medical privacy data also includes the following steps: S510: The medical processing terminal obtains the data transmission request sent by the user and determines the medical privacy dataset associated with the medical privacy data transmission request.

[0053] In this embodiment, when the medical processing terminal receives a user-triggered medical privacy data transmission request, it confirms the type of medical privacy data to be transmitted. Medical privacy data types include: text-based medical privacy data, audio-based medical privacy data, video-based medical privacy data, or image-based medical privacy data. The terminal obtains the medical communication identification policy associated with the medical privacy data type. If the medical privacy dataset associated with the medical privacy data transmission request conforms to the medical communication identification policy, it determines the medical privacy data associated with the medical privacy data transmission request. Medical privacy data refers to a unique identifier assigned to a medical privacy data transmission request for a specific medical privacy data type. During data transmission, the medical privacy data identifier can be used to monitor the status of data transmission and identify the source of the data.

[0054] As can be seen, when a user has a data transmission need, they will trigger a corresponding operation on the terminal, such as selecting the "send data" button to submit a data transmission command. After receiving these user-triggered operation signals, the medical processing terminal parses them into data transmission requests. Upon receiving the request, the medical processing terminal first needs to determine the type of medical privacy data to be transmitted. Text-based medical privacy data may include medical records, diagnostic reports, etc.; audio-based medical privacy data may include patients' voice descriptions of symptoms, auscultation audio, etc.; video-based medical privacy data may include surgical videos, patient rehabilitation training videos, etc.; image-based medical privacy data may include X-ray films, CT images, etc. The specific data type is confirmed by parsing the request content or based on the user's selection during the operation. Each type of medical privacy data has its unique security requirements and transmission characteristics, thus corresponding to different medical communication identification strategies. These strategies are pre-defined and stored by the medical institution's data platform, and the medical processing terminal can retrieve them through the interface established with the medical institution's data platform. For example, for image-based medical privacy data, it may be required that the image be compressed and encrypted in a specific format before transmission, and that the image's metadata be attached as an identifier; while for audio-based medical privacy data, more emphasis may be placed on the audio encoding format and the real-time nature of transmission, and the communication identification policy will specify the corresponding audio encoding method and the rules for adding timestamps.

[0055] S520: The medical processing terminal sends a medical data transmission request to the medical institution's data platform.

[0056] It should be noted that after determining the medical privacy data to be transmitted, the medical processing terminal encapsulates this data and related metadata to form a complete medical data transmission request. The medical processing terminal then sends out the encapsulated medical data transmission request through a pre-established network connection with the medical institution's data platform.

[0057] Step S530: The medical processing terminal receives a transmission policy associated with medical privacy data sent by the medical institution's data platform, wherein the transmission policy is used to configure security verification information.

[0058] After receiving a medical data transmission request from a medical processing terminal, the medical institution's data platform retrieves and generates a corresponding transmission strategy based on the type of medical privacy data in the request or the address information of the medical processing terminal. This transmission strategy is then sent back to the medical processing terminal via the previously established network connection. The medical processing terminal continuously listens to the network port, and upon receiving the transmission strategy from the medical institution's data platform, it receives and parses it.

[0059] Step S540: Send the medical privacy dataset associated with the transmission policy and the medical privacy data transmission request to the medical institution's data platform.

[0060] The transmission policy is used to securely verify medical privacy data transmitted from medical processing terminals. The transmission policy includes data transmission permissions, data format, encryption algorithms, etc., and verifies the legitimacy of requests to send medical privacy data. Medical institution data platforms and medical processing terminals can send data via HTTP requests.

[0061] As can be seen, after receiving the transmission policy, the medical processing terminal integrates it with the medical privacy dataset associated with the previously prepared medical privacy data transmission request. This means applying the security verification information in the transmission policy to the medical privacy data, such as encrypting the medical privacy data according to the policy requirements and adding authentication information. After integration, the medical processing terminal sends the data packet containing the transmission policy and the medical privacy data back to the medical institution's data platform via the network. In this process, because security configuration has been performed according to the transmission policy, the security of the data is guaranteed during transmission.

[0062] As one implementation of this application, the following steps are also involved: Step S621: The medical institution's data platform receives a medical data transmission request sent by the medical processing terminal.

[0063] Step S622: The medical institution's data platform determines the transmission strategy for medical privacy data.

[0064] Step S623: Return the received information to the medical processing terminal based on the transmission strategy.

[0065] The healthcare institution's data platform receives requests for the transmission of medical privacy data from healthcare processing terminals. These requests contain medical privacy data, which is a unique identifier assigned to each request for this specific data type, thus determining the type of medical privacy data being transmitted. The healthcare institution's data platform parses the medical privacy data based on the data transmission permissions, data format, and encryption algorithm specified in the transmission policy, and then determines whether the transmission and storage requirements are met.

[0066] Step S624: The medical processing terminal receives the reception information sent by the medical institution's data platform.

[0067] As an execution process different from the above methods, the method may include the following steps: S201, Medical processing terminal acquires medical privacy data and privacy data processing rules.

[0068] The privacy data processing rules maintained by the medical processing terminal can be obtained through the following steps: The medical institution's data platform obtains a pre-signed cooperation agreement between the medical processing terminal and the data recipient, which at least defines the content of the medical privacy dataset. Based on the content of the medical privacy dataset, the medical institution's data platform generates privacy data processing rules, determines the results of multi-dimensional compliance checks on the privacy data processing rules, and, if the compliance checks are passed, distributes the privacy data processing rules to the medical processing terminal.

[0069] It should be noted that the privacy data processing rules configure multiple key medical information items and their respective encryption methods.

[0070] S202, the medical processing terminal extracts key medical information and routine medical information defined in the privacy data processing rules from medical privacy data.

[0071] In this embodiment, if multiple non-critical information are defined in the privacy data processing rules, routine medical information of each non-critical information can be extracted from the medical privacy data.

[0072] In this embodiment, the medical processing terminal filters out relevant data items from the collected medical privacy data based on the key medical information defined in the privacy data processing rules. For example, if the key medical information defined in the rules is the patient's ID number and gene sequence, the terminal will extract the key medical information from the medical privacy data.

[0073] Optionally, the medical processing terminal uses a data filtering algorithm to extract the required key and routine information from the medical privacy data based on the information names and data formats defined in the rules. SQL queries can be used for data filtering, and the specific filtering method is not limited.

[0074] S203, the medical processing terminal encrypts the medical key information according to the encryption method defined in the privacy data processing rules, and obtains the encryption result.

[0075] The medical processing terminal determines the appropriate encryption method for each piece of critical medical information based on privacy data processing rules. For example, AES symmetric encryption might be used for a patient's ID number, while RSA asymmetric encryption might be used for a gene sequence.

[0076] S204, the medical processing terminal generates a medical encrypted file of medical privacy data based on key medical information and their corresponding encryption results, and provides it to the medical institution's data platform.

[0077] In this embodiment, when the privacy data processing rules also define multiple non-critical information, the medical privacy data can be formed into a medical encrypted file based on the medical critical information and their corresponding encryption results, as well as the non-critical information and their respective routine medical information.

[0078] In this embodiment, the medical processing terminal integrates encrypted critical medical information with unencrypted routine medical information to form an encrypted medical file containing medical privacy data. This information can be organized according to a specific format (such as JSON, XML, etc.). The encrypted medical file can then be sent to the medical institution's data platform via a secure network channel.

[0079] Specifically, a data serialization tool can be used to convert the encrypted key information and general information into strings of a specified format, forming a medical encrypted file. This encrypted medical file is then sent to the medical institution's data platform via the HTTPS protocol.

[0080] S205, the medical institution's data platform verifies encrypted medical files based on its maintained privacy data processing rules, and saves the encrypted medical files for use by the data recipient based on the verification results.

[0081] It should be noted that the medical institution's data platform conducts a comprehensive verification of encrypted medical files according to its maintained privacy data processing rules. The verification includes checking the integrity of the data and whether critical medical information is encrypted using the methods specified in the rules. Based on the verification results, if the encrypted medical file passes verification, the medical institution's data platform saves the relevant data to its database for the data recipient's use; if the verification fails, the medical institution's data platform will refuse to receive the data and notify the medical processing terminal to reprocess it.

[0082] In S206, verifying a medical encrypted file may include sequentially verifying the key medical information in the medical encrypted file to obtain the verification results corresponding to each key medical information.

[0083] In this embodiment, the medical institution data platform verifies each piece of critical medical information in the encrypted medical file individually according to privacy data processing rules. The verification process includes checking whether the encryption method is correct, whether the decrypted data format meets the requirements, and whether the data content is compliant. For each piece of critical medical information, the verification result is recorded. If the verification results for all critical medical information are passed, the entire encrypted medical file is considered to have passed verification; if any single piece of critical medical information fails verification, the entire encrypted medical file is considered to have failed verification.

[0084] The specific implementation uses a loop to iterate through each piece of critical medical information in the encrypted medical file, performing decryption and verification operations according to the encryption method specified in the rules. The verification result for each piece of critical medical information is stored in a result list, and finally, the encrypted medical file is judged based on the results in the list to determine whether it has passed verification. This verification method can pinpoint problems in the data, facilitating targeted modifications and adjustments at the medical processing terminal. This improves the accuracy and reliability of data verification, ensuring the quality and security of critical medical information.

[0085] The method may also include the following steps: S401: The medical processing terminal is configured with the hash value of the medical information key information based on a preset encryption algorithm. The preset encryption algorithm here can be either SHA256 or a hash algorithm.

[0086] S402: The medical processing terminal uses the timestamp of the medical information generated for this medical privacy dataset as a symmetric key to encrypt the hash value of the medical information, thus obtaining the encrypted hash value.

[0087] S403: The medical processing terminal encrypts the data based on the platform's public key to obtain the encryption key.

[0088] S404: The medical processing terminal provides the encrypted hash value and encryption key to the medical institution's data platform.

[0089] S405: The medical institution's data platform decrypts the encryption key based on the platform's encrypted private key to obtain the symmetric key.

[0090] S406: The medical institution's data platform uses a symmetric key to decrypt the encrypted hash value to obtain the medical information hash value.

[0091] S407: The medical institution's data platform encrypts the hash value of medical information based on the encryption key defined with the data recipient, and saves the encrypted hash value of medical information.

[0092] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0093] The following are embodiments of the medical privacy data sharing system provided in this disclosure. This system and the medical privacy data sharing methods in the above embodiments belong to the same inventive concept. For details not described in detail in the embodiments of the medical privacy data sharing system, please refer to the embodiments of the above medical privacy data sharing methods.

[0094] The system includes: medical processing terminals and medical institution data platforms.

[0095] The medical processing terminal obtains the medical encryption key from the medical institution's data platform.

[0096] The medical processing terminal encrypts the medical privacy dataset based on the medical encryption key to obtain the medical privacy ciphertext.

[0097] The medical processing terminal calculates the encryption identifier of the medical privacy ciphertext and encrypts the encryption identifier of the medical privacy ciphertext based on the encryption private key of the medical processing terminal to obtain medical privacy signature data.

[0098] The medical processing terminal sends encrypted medical privacy data and medical privacy signature data to the medical institution's data platform.

[0099] like Figure 4 As shown, this application also provides an electronic device, including a display module 103, a memory 102, a processor 101, and a computer program stored in the memory and executable on the processor 101. When the processor 101 executes the program, it implements the steps of a medical privacy data sharing method.

[0100] In embodiments of the present invention, electronic devices include, but are not limited to, laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. Electronic devices may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the embodiments described and / or claimed herein.

[0101] In this embodiment, processor 101 may be implemented using at least one of an Application-Specific Integrated Circuit (ASIC), a Programmable Logic Device (PLD), a Field-Programmable Gate Array (FPGA), a processor, a controller, a microcontroller, a microprocessor, or an electronic unit designed to perform the functions described herein. In some cases, such implementations may be implemented within a controller. For software implementations, implementations such as processes or functions may be implemented with separate software modules that allow the performance of at least one function or operation. The software code may be implemented by a software application (or program) written in any suitable programming language, and the software code may be stored in memory and executed by the controller.

[0102] The display module 103 is used to display information input by the user or information provided to the user. The display module 103 may include a display panel, which may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.

[0103] The memory 102 can be used to store software programs and various data. The memory 102 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0104] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.

[0105] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of devices, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram and / or flowchart, and combinations of blocks in block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0106] In the embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the couplings or direct couplings or communication connections shown or discussed may be indirect couplings or communication connections through some interfaces, apparatuses, or units, or they may be electrical, mechanical, or other forms of connection.

[0107] This application also provides a storage medium storing a computer program thereon, wherein the computer program, when executed by a processor, implements the steps of a method for sharing medical privacy data.

[0108] The storage medium may be any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example,, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of readable storage media include: electrical connections having one or more wires, portable disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0109] The above description of the disclosed embodiments enables those skilled in the art to make or use the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the invention is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for sharing medical privacy data, characterized in that the method... include: S101, the medical processing terminal obtains the medical encryption key from the medical institution's data platform; S102, the medical processing terminal encrypts the medical privacy dataset based on the medical encryption key to obtain medical privacy ciphertext; S103, the medical processing terminal calculates the encryption identifier code of the medical privacy ciphertext, and encrypts the encryption identifier code of the medical privacy ciphertext based on the encryption private key of the medical processing terminal to obtain medical privacy signature data; S104, the medical processing terminal sends the medical privacy encrypted data and medical privacy signature data to the medical institution's data platform.

2. The method for sharing medical privacy data according to claim 1, characterized in that, Step S102 also includes: The medical processing terminal extracts key medical information and routine medical information defined in the privacy data processing rules from the medical privacy dataset based on the privacy data processing rules. The medical processing terminal uses the encryption method defined in the privacy data processing rules to encrypt the medical critical information and the corresponding routine medical information to obtain the encryption result. The medical processing terminal generates encrypted medical files containing medical privacy data based on key medical information and corresponding encryption results, and then provides them to the medical institution's data platform.

3. The method for sharing medical privacy data according to claim 2, characterized in that, The medical institution's data platform verifies encrypted medical files based on privacy data processing rules and saves the encrypted medical files according to the verification results. The verification method for encrypted medical files includes verifying key medical information within the encrypted medical files and obtaining the verification results corresponding to the key medical information.

4. The method for sharing medical privacy data according to claim 1 or 2, characterized in that, In this method, the medical processing terminal is configured with the medical information hash value of the medical key information value based on a preset encryption algorithm. The medical processing terminal uses the timestamp of the medical information generated for this medical privacy dataset as a symmetric key to encrypt the hash value of the medical information, thus obtaining the encrypted hash value. The medical processing terminal uses the platform's public key for encryption to obtain the encryption key; The medical processing terminal provides the encrypted hash value and encryption key to the medical institution's data platform.

5. The method for sharing medical privacy data according to claim 4, characterized in that, The medical institution's data platform uses the platform's encrypted private key to decrypt the encrypted key and obtain the symmetric key. The medical institution's data platform uses a symmetric key to decrypt the encrypted hash value, thus obtaining the hash value of the medical information. The medical institution's data platform encrypts the hash value of medical information based on the encryption key defined with the data recipient, and saves the encrypted hash value of medical information.

6. The method for sharing medical privacy data according to claim 1 or 2, characterized in that, The steps preceding step S101 also include: The medical processing terminal obtains the data transmission request sent by the user and determines the medical privacy dataset associated with the medical privacy data transmission request; The medical processing terminal sends a medical data transmission request to the medical institution's data platform; The medical processing terminal receives a transmission policy associated with medical privacy data sent by the medical institution's data platform. The transmission policy is used to configure security verification information. The medical privacy dataset, which is associated with the transmission policy and the medical privacy data transmission request, is sent to the medical institution's data platform.

7. The method for sharing medical privacy data according to claim 6, characterized in that, The method also includes: The medical institution's data platform receives medical data transmission requests from medical processing terminals; Medical institution data platforms determine transmission strategies for data related to medical privacy. The received information is returned to the medical processing terminal based on the transmission strategy.

8. A medical privacy data sharing system, characterized in that, The system is used to implement the medical privacy data sharing method as described in any one of claims 1 to 7; The system includes: medical processing terminals and a medical institution data platform; The medical processing terminal obtains the medical encryption key from the medical institution's data platform; The medical processing terminal encrypts the medical privacy dataset based on the medical encryption key to obtain the medical privacy ciphertext; The medical processing terminal calculates the encryption identifier code of the medical privacy ciphertext, and encrypts the encryption identifier code of the medical privacy ciphertext based on the encryption private key of the medical processing terminal to obtain medical privacy signature data; The medical processing terminal sends encrypted medical privacy data and medical privacy signature data to the medical institution's data platform.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the steps of any one of the medical privacy data sharing methods as claimed in claims 1 to 7.

10. A storage medium having a computer program stored thereon, characterized in that, When a computer program is executed by a processor, it implements the steps of any one of the medical privacy data sharing methods as claimed in claims 1 to 7.

Images