Data transmission method, system, electronic device and storage medium

Abstract

A data transmission method, system, electronic device and storage medium, relating to the field of data security. In this method, a public-private key pair is generated using a first encryption algorithm, and a temporary access token is generated for the data to be transmitted on the hospital side according to a preset authorization mechanism; a session key is generated based on the public key, and the data to be transmitted is encrypted using a second encryption algorithm and the session key, and a target transmission channel is established using a virtual private network technology, and the encrypted data, metadata and temporary access token are pushed to the first front-end server on the health commission side through the target transmission channel; when the temporary access token is checked, the session key is decrypted using a private key to obtain decrypted data, and when the first hash value obtained by calculating the decrypted data using a hash function is the same as the second hash value in the metadata, a unique patient master index is generated for each patient in the decrypted data. The implementation of the technical solution provided by this application improves the security of data transmission.

Description

Technical Field

[0001] The present application relates to the technical field of data security, and in particular to a data transmission method, system, electronic device and storage medium. Background Art

[0002] In the process of medical and health information construction, information intercommunication between hospitals has become increasingly important, especially in the efficient and secure transmission of key data such as test reports. This development trend not only improves the efficiency of medical services, but also greatly improves the patient's medical experience.

[0003] In order to ensure the secure transmission of medical and patient information, existing technical means mainly rely on various encryption technologies and authentication mechanisms. For example, some medical institutions use encryption methods based on static passwords to ensure the security of data transmission; others try to reduce the risk of data leakage through physical isolation, that is, setting up a dedicated data exchange area for data transmission. Although the above methods can improve data security to a certain extent, it is difficult to fully meet the needs of modern medical systems for data integrity and patient privacy protection in practical applications. Especially for scenarios with large dynamic changes (such as data sharing during emergencies), traditional encryption methods often seem to be inadequate and cannot effectively prevent unauthorized access or tampering.

[0004] Therefore, how to design a data transmission solution that can both ensure a high level of security and flexibly adapt to the needs of various application scenarios has become a technical challenge that urgently needs to be overcome. Summary of the invention

[0005] The present application provides a data transmission method, system, electronic device and storage medium, which provide technical support for the mutual recognition of test and inspection data between the hospital and the health commission by ensuring the security, integrity and efficiency of data transmission, which helps to reduce duplicate tests and inspections, improve the utilization efficiency of medical resources, and reduce the economic burden on patients.

[0006] In a first aspect of the present application, a data transmission method is provided, which is applied to a mutual recognition platform for testing and inspection, wherein the mutual recognition platform for testing and inspection includes a hospital side and a health commission side, and the method includes:

[0007] Generate a public-private key pair using a first encryption algorithm, and generate a temporary access token for the data to be transmitted at the hospital end according to a preset authorization mechanism, wherein the public-private key pair includes a public key and a private key, and the access token includes a sender, a receiver, access rights, and validity period data;

[0008] Generate a session key according to the public key, use a second encryption algorithm and the session key to encrypt the data to be transmitted, use a virtual private network technology to establish a target transmission channel, and push the encrypted data, metadata and the temporary access token to the first front-end server of the Health Commission through the target transmission channel;

[0009] Checking the validity of the temporary access token in the first front-end server, and when the check passes, decrypting the session key using the private key to obtain decrypted data, and calculating a first hash value of the decrypted data using a hash function;

[0010] The first hash value is compared with the second hash value in the metadata. When the comparison is passed, a unique patient primary index is generated for each patient in the decrypted data, and the patient primary index is associated with the corresponding data in the decrypted data and stored on the Health Commission end.

[0011] Optionally, generating a temporary access token for the data to be transmitted at the hospital end according to a preset authorization mechanism includes:

[0012] Preset multiple access rights levels based on data sensitivity, and define the scope and restrictions of each access right level;

[0013] Classifying and evaluating the data to be transmitted at the hospital end to determine the target sensitivity;

[0014] A target access permission level is matched according to the target sensitivity, and the target access permission level is encoded into the temporary access token.

[0015] Optionally, the use of a virtual private network technology to establish a target transmission channel includes:

[0016] Configure the IPSec protocol between the hospital and the health commission and define VPN tunnel parameters, and determine the transmission method according to the target access permission level of the data to be transmitted;

[0017] According to the IPSec protocol, the VPN tunnel parameters and the selected transmission method, a target transmission channel is established between the hospital end and the Health Commission end. The target transmission channel includes a dedicated VPN tunnel and a shared VPN tunnel. The dedicated VPN tunnel is used to transmit data with the highest access permission level.

[0018] Optionally, the using the second encryption algorithm and the session key to encrypt the data to be transmitted includes:

[0019] Generate a first-round subkey according to the session key and a first preset round constant, determine a next-round subkey according to a previous-round subkey and a second preset round constant, and generate a subkey list according to the subkey;

[0020] The data to be transmitted is divided into multiple data blocks as initial input, and each round is encrypted using the subkey of the corresponding round in the subkey list to obtain output, and the output of the previous round is used as the input of the next round, until the preset round is reached and the output of the preset round is used as the encrypted data.

[0021] Optionally, generating a unique patient master index for each patient in the decrypted data further includes:

[0022] Extracting the patient's identity information from the decrypted data, and performing hash processing on the extracted identity information to generate a third hash value, wherein the identity information includes name, ID number, and date of birth;

[0023] Check whether the third Hash value already exists in the patient database of the health commission. If so, associate the condition data in the decrypted data with the third Hash value in the patient database.

[0024] Optionally, the data transmission method further includes:

[0025] When receiving a data request sent by the hospital to the health commission, the health commission analyzes the data request to extract the patient master index, determines the target data by the patient master index, and sends the target data along with the data request to the second front-end server of the hospital;

[0026] The data request is analyzed by the second front-end server to extract the target doctor, the usage habits of the target doctor are determined by a preset data model, and the target data is processed according to the usage habits.

[0027] Optionally, determining the usage habits of the target doctor by using a preset data model, and processing the target data according to the usage habits includes:

[0028] Define medical resource entities according to the HL7 FHIR standard and establish associations between medical resource entities, wherein the medical resource entities include basic patient information, diagnosis information, examination results, and treatment plans;

[0029] The display method and transmission method of the target data are determined according to the usage habits and the association relationship.

[0030] In a second aspect of the present application, a data transmission system is provided, including a generation module, a transmission module, a checking module and a storage module, wherein:

[0031] A generating module configured to generate a public-private key pair using a first encryption algorithm, and to generate a temporary access token for the data to be transmitted at the hospital end according to a preset authorization mechanism, wherein the public-private key pair includes a public key and a private key, and the access token includes a sender, a receiver, access rights, and validity period data;

[0032] A transmission module, configured to generate a session key according to the public key, encrypt the data to be transmitted using a second encryption algorithm and the session key, establish a target transmission channel using a virtual private network technology, and push the encrypted data, metadata and the temporary access token to the first front-end server of the Health Commission through the target transmission channel;

[0033] A checking module configured to check the validity of the temporary access token in the first front-end server, and when the check passes, decrypt the session key using the private key to obtain decrypted data, and calculate a first hash value of the decrypted data using a hash function;

[0034] A storage module is configured to compare the first hash value with the second hash value in the metadata. When the comparison is passed, a unique patient master index is generated for each patient in the decrypted data, and the patient master index is associated with the corresponding data in the decrypted data and stored in the Health Commission end.

[0035] In the third aspect of the present application, an electronic device is provided, including a processor, a memory, a user interface and a network interface, the memory is used to store instructions, the user interface and the network interface are both used to communicate with other devices, and the processor is used to execute the instructions stored in the memory so that the electronic device executes any one of the methods described above.

[0036] In a fourth aspect of the present application, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores instructions, and when the instructions are executed, any of the methods described above is executed.

[0037] In summary, one or more technical solutions provided in the embodiments of the present application have at least the following technical effects or advantages:

[0038] 1. Use the first encryption algorithm to generate a public-private key pair, and generate a temporary access token for the data to be transmitted through a preset authorization mechanism. This step ensures identity authentication and access control before data transmission to prevent unauthorized access. Use the second encryption algorithm and session key to encrypt the data to be transmitted, further enhancing the security of the data during transmission and preventing the data from being stolen or tampered with.

[0039] 2. In the first front-end server of the Health Commission, by comparing the first hash value of the decrypted data with the second hash value in the metadata, it can be verified whether the data remains intact during transmission, that is, whether it has been tampered with. This step ensures that the received data is completely consistent with the data when it was sent;

[0040] 3. Use virtual private network technology to establish the target transmission channel to ensure the stability and efficiency of data transmission. Virtual private network technology can provide a secure network connection and avoid security risks when data is transmitted on the public network;

[0041] 4. Generate a unique patient master index for each patient in the decrypted data, and store the patient master index in association with the corresponding data in the decrypted data. This step simplifies the management and use of data, allowing the health and medical commission to easily query and use the patient's test and examination data;

[0042] 5. By ensuring the security, integrity and efficiency of data transmission, it provides technical support for the mutual recognition of test and inspection data between the hospital and the Health Commission. This helps reduce duplicate tests and inspections, improve the efficiency of medical resource utilization, and reduce the economic burden on patients. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] Figure 1 It is a flowchart of the data transmission method disclosed in the embodiment of the present application;

[0044] Figure 2 It is a schematic diagram of the principle of the inspection and examination mutual recognition platform disclosed in the embodiment of the present application;

[0045] Figure 3 It is a schematic diagram of the architecture of the inspection and examination mutual recognition platform disclosed in the embodiment of the present application;

[0046] Figure 4 It is a module schematic diagram of the data transmission system disclosed in the embodiment of the present application;

[0047] Figure 5 It is a structural schematic diagram of an electronic device disclosed in an embodiment of the present application.

[0048] Explanation of the reference numerals: 401, generation module; 402, transmission module; 403, inspection module; 404, storage module; 501, processor; 502, communication bus; 503, user interface; 504, network interface; 505, memory. DETAILED DESCRIPTION

[0049] In order to enable technicians in this field to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below in conjunction with the drawings in the embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this application, not all of the embodiments.

[0050] In the description of the embodiments of the present application, words such as "for example" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described as "for example" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "for example" or "for example" is intended to present related concepts in a specific way.

[0051] In the description of the embodiments of the present application, the meaning of the term "multiple" refers to two or more. For example, multiple systems refer to two or more systems, and multiple screen terminals refer to two or more screen terminals. In addition, the terms "first" and "second" are used for descriptive purposes only and cannot be understood as indicating or implying relative importance or implicitly indicating the indicated technical features. Thus, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features. The terms "include", "comprise", "have" and their variations all mean "including but not limited to", unless otherwise specifically emphasized.

[0052] This embodiment discloses a data transmission method, which is applied to the inspection and examination mutual recognition platform. Figure 1 is a flow chart of the data transmission method disclosed in the embodiment of the present application, such as Figure 1 As shown, the method comprises the following steps:

[0053] S110, using a first encryption algorithm to generate a public-private key pair, and generating a temporary access token for the data to be transmitted at the hospital end according to a preset authorization mechanism, wherein the public-private key pair includes a public key and a private key, and the access token includes a sender, a receiver, access rights, and validity period data;

[0054] Figure 2 Schematic diagram of the principle of the inspection and examination mutual recognition platform disclosed in the embodiment of the present application, such as Figure 2As shown in the figure, the mutual recognition platform for testing and inspection is a platform system for sharing and mutual recognition of patient testing and inspection data built within the scope of provinces, cities, medical alliances, and medical communities. It is mainly composed of two parts: the testing and inspection data resource center and the mutual recognition sharing subsystem. The testing and inspection data resource center gathers the mutual recognition data of testing and inspection of various medical institutions in the region, and realizes the safe storage of data through security methods such as encryption and de-identification. At the same time, based on the platform master index, unified management of patient testing and inspection data is realized. It supports the analysis and utilization of big data and flexibly expands data analysis and mining services based on data warehouses. The mutual recognition sharing subsystem is the business management platform of the mutual recognition system. Based on multi-level role authorization, it meets the access of users at different levels and with different permissions. It realizes the integration of the whole process of business from patients to testing and inspection data, quality control management, business supervision, etc., covers a variety of front-end display technologies, and realizes interactive use based on business scenarios.

[0055] Figure 3 is a schematic diagram of the architecture of the inspection and examination mutual recognition platform disclosed in the embodiment of the present application, such as Figure 3 As shown in the figure, the mutual recognition platform for inspections and tests uses in-hospital front-end technology to effectively simplify the data collection process and reduce the cost of interface development for each manufacturer, while ensuring the conceptual integrity of the software system and regulating the quality of data based on standardized interfaces and dictionaries from the source of data collection. For big image data, the unified use of the DICOM3.0 standard can reduce the complexity of data transmission and subsequent sharing and retrieval.

[0056] Combination Figure 2 and Figure 3 The embodiments of the present application are described.

[0057] The first encryption algorithm refers to the widely used public key encryption algorithms such as RSA and ECC (elliptic curve encryption). These algorithms can generate a pair of keys: public key and private key. The public key is used to encrypt data or verify signatures, while the private key is used to decrypt data or generate signatures. Public key: This is public information that can be obtained by any receiver who needs to communicate securely with the sender. The public key is used to encrypt data sent to the sender or verify the authenticity of the sender's signature. Private key: This is information that must be kept strictly confidential and is only known by the sender. The private key is used to decrypt the received encrypted data or generate a key for data signing. In the scenario of medical data transmission, in order to ensure secure access and compliance of data, an authorization mechanism is usually used to generate and manage access tokens. Preset authorization mechanism: This is a mechanism designed according to business needs and security policies to define who can access which data, the level of access permissions, and the validity period of access. This mechanism may include multiple strategies such as role-based access control (RBAC) and attribute-based access control (ABAC). Temporary access token: This is a dynamically generated access credential with a limited validity period. It contains the following key information: Sender: the provider or sender of the data, usually a hospital or a department within a hospital; Receiver: the recipient or requester of the data, which may be the National Health Commission, another hospital, a doctor, a patient or other legitimate user; Access rights: defines the operations that the receiver can perform on the data, such as reading, writing, modifying, etc.; Validity period data: specifies the validity period of the token. After this period, the token will become invalid and can no longer be used to access the data.

[0058] Optionally, generating a temporary access token for the data to be transmitted at the hospital end according to a preset authorization mechanism includes:

[0059] Preset multiple access rights levels based on data sensitivity, and define the scope and restrictions of each access right level;

[0060] Classifying and evaluating the data to be transmitted at the hospital end to determine the target sensitivity;

[0061] A target access permission level is matched according to the target sensitivity, and the target access permission level is encoded into the temporary access token.

[0062] Multiple access rights levels are preset based on the sensitivity of the data and business needs. For example, data can be classified into different levels such as "public", "internal", "sensitive" and "highly sensitive". Each level defines the corresponding scope of permissions and restrictions. For example, data at the "public" level can be accessed by anyone, data at the "internal" level is only accessible to hospital personnel, data at the "sensitive" level requires specific permissions to access, and data at the "highly sensitive" level may be subject to stricter access control and audit requirements. On the hospital side, the data to be transmitted is classified and evaluated. This usually involves a comprehensive consideration of factors such as the content, source, purpose and potential risks of the data. Through this process, the target sensitivity of each data item is determined, that is, which preset access right level it belongs to. According to the target sensitivity of the data, the corresponding target access right level is matched. This target access right level is encoded into the temporary access token. This is usually achieved by including a field representing the permission level in the token, and the value of the field corresponds to one of the preset access right levels.

[0063] By presetting multiple access rights levels and classifying and evaluating them according to the sensitivity of the data, hospitals can achieve refined permission management for different data resources. Each access right level defines clear permission scope and restrictions, which helps ensure that only users with corresponding permissions can access specific data resources. The use of temporary access tokens increases the flexibility and security of data access. The token contains access rights and validity period data. When the validity period expires or the permission is revoked, the token will become invalid. This mechanism helps prevent unauthorized access and data leakage, and improves the security of hospital data. By encoding the target access right level into the temporary access token, hospitals can simplify the access control process. Users do not need to go through cumbersome permission verification and approval processes every time they access data, but only need to hold a valid temporary access token. The preset authorization mechanism and the use of temporary access tokens help hospitals comply with relevant data protection and privacy regulations. By clarifying the scope of permissions and restrictions, hospitals can ensure that data access and use meet regulatory requirements and reduce compliance risks. Hospitals can monitor and audit data access behavior by centrally managing temporary access tokens. This helps hospitals detect abnormal access behavior in a timely manner and take corresponding measures, improving the efficiency and accuracy of data management.

[0064] S120, generating a session key according to the public key, using a second encryption algorithm and the session key to encrypt the data to be transmitted, using a virtual private network technology to establish a target transmission channel, and pushing the encrypted data, metadata and the temporary access token to the first front-end server of the Health Commission through the target transmission channel;

[0065] A session key is a temporary key used to establish a secure session between two communicating parties. The hospital uses the public key to generate a session key through a key exchange algorithm (such as Diffie-Hellman key exchange) or a key derivation function (such as password-based key derivation function PBKDF2). This session key is shared by both parties and is used to encrypt and decrypt data in communication. The second encryption algorithm refers to the encryption algorithm used to encrypt the data to be transmitted. Common encryption algorithms include symmetric encryption algorithms (such as AES) and asymmetric encryption algorithms (such as RSA). In this scenario, since the session key is symmetric, it is more likely to use a symmetric encryption algorithm for data encryption. The hospital uses the generated session key to encrypt the data to be transmitted through the second encryption algorithm. The encrypted data becomes unreadable and can only be decrypted by the entity holding the corresponding private key or session key. Virtual private network technology (VPN) is a technology that establishes an encrypted channel on a public network to achieve a secure connection between remote users or branches and a central network. In this scenario, VPN is used to establish a secure transmission channel between the hospital and the Health Commission. The hospital uses VPN technology to configure the corresponding network parameters (such as IP address, port number, encryption protocol, etc.) to establish a target transmission channel with the Health Commission. This channel is encrypted to ensure the security of data during transmission. The encrypted data is sensitive information that the hospital needs to transmit to the Health Commission. Metadata is descriptive information about the data, such as data format, size, generation time, etc. The temporary access token is the access permission credential generated by the hospital for the Health Commission, which is used to control the Health Commission's access to the data. The hospital pushes the encrypted data, metadata, and temporary access token to the first front-end server of the Health Commission through the established target transmission channel. The first front-end server is the server used by the Health Commission to receive and process data from the hospital.

[0066] Optionally, the use of a virtual private network technology to establish a target transmission channel includes:

[0067] Configure the IPSec protocol between the hospital and the health commission and define VPN tunnel parameters, and determine the transmission method according to the target access permission level of the data to be transmitted;

[0068] According to the IPSec protocol, the VPN tunnel parameters and the selected transmission method, a target transmission channel is established between the hospital end and the Health Commission end. The target transmission channel includes a dedicated VPN tunnel and a shared VPN tunnel. The dedicated VPN tunnel is used to transmit data with the highest access permission level.

[0069] IPSec (Internet Protocol Security) is a network security protocol that provides authentication, integrity, and encryption services for IP data packets. Configuring the IPSec protocol between the hospital and the Health Commission can ensure the security of data during transmission. VPN tunnel parameters include the IP addresses, port numbers, encryption algorithms, and authentication methods at both ends of the tunnel. These parameters are used to define the specific configuration of the VPN tunnel to ensure that the hospital and the Health Commission can correctly establish a connection. According to the target access permission level of the data to be transmitted, the hospital and the Health Commission can determine which transmission method to use. The transmission method may include direct transmission, encrypted transmission, and transmission through a specific route. In this scenario, the choice of transmission method is closely related to the sensitivity of the data and the access permission level. A dedicated VPN tunnel is an independent VPN connection dedicated to transmitting specific data. A shared VPN tunnel is a VPN connection shared by multiple users or systems. In this scenario, a dedicated VPN tunnel is used to transmit data with the highest access permission level to ensure the security and confidentiality of the data. According to the IPSec protocol, VPN tunnel parameters, and the selected transmission method, the hospital and the Health Commission begin to establish the target transmission channel. During the establishment process, both parties will perform authentication and key exchange to ensure the security and reliability of the connection. Once the connection is established successfully, the hospital can push the encrypted data, metadata and temporary access token to the first front-end server of the Health Commission through the target transmission channel.

[0070] By configuring the IPSec protocol and defining the VPN tunnel parameters, the data transmission between the hospital and the Health Commission is strongly encrypted. The IPSec protocol is a widely used network security protocol that provides security services such as data integrity, authentication, and data encryption. The setting of dedicated VPN tunnels and shared VPN tunnels further enhances the security of data transmission. Dedicated VPN tunnels are used to transmit data with the highest access level. Such tunnels usually have higher security configurations and stricter access control, thereby ensuring the safe transmission of highly sensitive data. The transmission method is determined according to the access level of the data to be transmitted, so that the hospital can select the appropriate transmission channel according to the sensitivity of the data. This classified transmission method helps to avoid confusion between sensitive data and non-sensitive data, and improves the efficiency and accuracy of data transmission. At the same time, by setting different transmission channels for data of different levels, the hospital can better manage the access rights of the data to ensure that only users with corresponding permissions can access the corresponding data. The setting of dedicated VPN tunnels and shared VPN tunnels makes the data transmission between the hospital and the Health Commission more flexible. For highly sensitive data, a dedicated VPN tunnel can be selected for transmission to ensure the security and integrity of the data; for non-sensitive data, a shared VPN tunnel can be selected for transmission to reduce costs and improve transmission efficiency. In addition, by configuring different VPN tunnel parameters and transmission methods, the hospital can also adjust the bandwidth, latency and other performance indicators of data transmission according to actual needs to meet different business needs. By setting up dedicated VPN tunnels and shared VPN tunnels, the hospital and the Health Commission can use network resources more reasonably. Dedicated VPN tunnels usually have higher security configurations and stricter access control, but they also require more network resources to support. Therefore, for highly sensitive data, you can choose to use a dedicated VPN tunnel for transmission; for non-sensitive data, you can choose to use a shared VPN tunnel to reduce costs and improve the utilization of network resources.

[0071] Optionally, the using the second encryption algorithm and the session key to encrypt the data to be transmitted includes:

[0072] Generate a first-round subkey according to the session key and a first preset round constant, determine a next-round subkey according to a previous-round subkey and a second preset round constant, and generate a subkey list according to the subkey;

[0073] The data to be transmitted is divided into multiple data blocks as initial input, and each round is encrypted using the subkey of the corresponding round in the subkey list to obtain output, and the output of the previous round is used as the input of the next round, until the preset round is reached and the output of the preset round is used as the encrypted data.

[0074] Based on the session key and the first preset round constant, a key expansion algorithm or key derivation function is used to generate the first round of subkeys. Based on the previous round of subkeys and the second preset round constant (these constants may change with the increase of rounds, or may remain unchanged), the same key expansion algorithm or key derivation function is used again to generate the next round of subkeys. This process will continue until all required subkeys are generated to form a subkey list. Divide the data to be transmitted into multiple fixed-size data blocks. These data blocks will be used as the initial input of the encryption algorithm. If the length of the data is not an integer multiple of the data block size, padding (such as PKCS#7 padding) may be required to ensure that the size of each data block is consistent. Initial round: Use the first subkey in the subkey list (i.e., the first round subkey) to encrypt the first data block to obtain the output of the first round. Subsequent rounds: Use the output of the previous round as the input of the next round and encrypt it using the subkey of the corresponding round in the subkey list. This process will be repeated until the preset round (also known as the number of encryption rounds or iterations) is reached. Final output: The output of the preset round is the encrypted data. This encrypted data is one or more encrypted data blocks, which together constitute the encrypted version of the data to be transmitted.

[0075] By generating the first round of subkeys according to the session key and the first preset round constant, and determining the next round of subkeys according to the previous round of subkeys and the second preset round constant, a complex subkey list can be generated. This process increases the complexity of the key, making it difficult for an attacker to obtain the correct key by brute force or analyzing the key structure. Using multiple rounds of subkeys for encryption, each round uses a different subkey, which further enhances the strength and security of the encryption. The data to be transmitted is divided into multiple data blocks as the initial input, and each round is encrypted using the subkey of the corresponding round in the subkey list. This block encryption method can ensure that each data block is fully encrypted, thereby preventing the data from being tampered with or damaged during transmission. By using the output of the previous round as the input of the next round until the preset round is reached, the coherence and consistency of the entire encryption process can be ensured. This round-by-round encryption method helps maintain the integrity of the data, so that the decrypted data is consistent with the original data. Although multiple rounds of encryption increase the complexity of encryption, the encryption process can be optimized and the encryption efficiency can be improved by using a pre-generated subkey list and round-by-round encryption. The pre-generated subkey list reduces the overhead of key generation during the encryption process, while the round-by-round encryption method allows the encryption process to be pipelined, thereby increasing the encryption speed. The encryption process can flexibly adjust the preset round constants and subkey generation methods to adapt to different security requirements and application scenarios. By increasing or decreasing the number of rounds, changing the round constants or the subkey generation algorithm, the strength and security of the encryption can be adjusted to meet specific security requirements. Since the encryption process divides the data into multiple data blocks for encryption, it can support input of multiple data formats and sizes. This flexibility makes the encryption process widely applicable to various data transmission and storage scenarios.

[0076] S130, checking the validity of the temporary access token in the first front-end server, and when the check passes, decrypting the session key using the private key to obtain decrypted data, and calculating a first hash value of the decrypted data using a hash function;

[0077] A temporary access token is a credential used to control data access rights. In this scenario, when the hospital sends data to the Health Commission, it will be accompanied by a temporary access token to prove that the sender of the data is legitimate and has the corresponding data access rights. When the data arrives at the first front-end server of the Health Commission, the server will first check the validity of the temporary access token. This process may include verifying the signature of the token, checking the validity period of the token, confirming the permissions associated with the token, etc. If the temporary access token passes the check, it means that the sender of the data is legitimate and has the permission to access the target data. At this time, the server will continue to process the data; if the check fails, the server may refuse to receive the data or trigger a corresponding security alarm. The private key is the key corresponding to the public key and is used to decrypt data encrypted by the public key. In this scenario, the private key is held by the Health Commission and is used to decrypt the encrypted data sent by the hospital. After confirming the validity of the temporary access token, the first front-end server will use the private key to decrypt the session key. This process is the inverse process of public key encryption. The original session key can be restored through the private key and encryption algorithm. The decrypted session key will be used in the subsequent data decryption process. A hash function is an algorithm that converts data of arbitrary length into a fixed-length hash value. Hash values ​​are often used in scenarios such as data integrity verification and quick search. After decrypting the session key and using it to decrypt the original data, the first front-end server uses the hash function to calculate the first hash value of the decrypted data. This process takes the decrypted data as input and calculates a fixed-length hash value through the hash function. The hash value can be used for subsequent data integrity verification. For example, the Health Commission can receive and store this hash value, and then recalculate the hash value of the decrypted data when needed and compare it with the stored hash value to verify the integrity of the data.

[0078] S140. Compare the first hash value with the second hash value in the metadata. When the comparison is successful, generate a unique patient master index for each patient in the decrypted data, and associate the patient master index with the corresponding data in the decrypted data and store it on the Health Commission end.

[0079] In this scenario, hash values ​​are used as a tool to verify data integrity. By calculating the hash value of the data, a fixed-length unique identifier can be generated, which can uniquely represent the original data (if the data has not changed). In the first front-end server, after the first hash value of the decrypted data is calculated, the server compares it with the second hash value in the metadata. The metadata here may contain the previously calculated and stored hash value corresponding to the current decrypted data. The purpose of the comparison is to verify whether the decrypted data maintains integrity during transmission. If the first hash value is exactly the same as the second hash value, it means that the decrypted data has not changed during transmission, and the data integrity is guaranteed. The Patient Master Index (PMI) is an identifier used to uniquely identify a patient. On the Health Commission side, each patient should have a unique master index to facilitate data tracking, management, and analysis. When the hash value comparison passes, it means that the decrypted data is complete and valid. At this time, the first front-end server or other system components on the Health Commission side will generate a unique patient master index for each patient in the decrypted data. The generation of the patient's primary index may be based on some basic information of the patient (such as name, date of birth, ID number, etc.), or a more complex algorithm may be used to ensure the uniqueness and security of the index. After the patient's primary index is generated, the server will associate the patient's primary index with the corresponding data in the decrypted data (such as the patient's personal information, medical records, etc.). This means that in the database of the Health Commission, each patient's primary index will correspond to a complete set of decrypted patient data. This associative storage method helps the Health Commission to quickly and accurately find and access relevant patient data, and also facilitates further analysis and utilization of the data.

[0080] Optionally, generating a unique patient master index for each patient in the decrypted data further includes:

[0081] Extracting the patient's identity information from the decrypted data, and performing hash processing on the extracted identity information to generate a third hash value, wherein the identity information includes name, ID number, and date of birth;

[0082] Check whether the third Hash value already exists in the patient database of the health commission. If so, associate the condition data in the decrypted data with the third Hash value in the patient database.

[0083] Before generating a unique patient master index for each patient in the decrypted data, the patient's identity information must first be extracted from the decrypted data. This identity information usually includes key information such as the patient's name, ID number, and date of birth, which is the basis for ensuring the uniqueness of the patient's identity. After extracting the identity information, the information needs to be hashed. Hashing is an algorithm that converts data of any length into a fixed-length hash value. Through hashing, a hash value that uniquely represents the patient's identity information (here called the third hash value) can be generated. The reason for using hashing is that it not only protects the patient's privacy (because the original identity information is converted into a hash value that cannot be reversed), but also improves the efficiency of data retrieval (because the hash value is usually much shorter than the original data and is easy to compare). After generating the third hash value, the next step is to check whether the hash value already exists in the patient database on the Health Commission side. The purpose of this step is to ensure the uniqueness of the patient's master index. If the same hash value already exists in the database, it means that a patient record with the same identity information already exists in the database, and there is no need to generate a new patient master index for the patient. If there is no record matching the third hash value in the database, it means that this is a new patient, and a new patient master index needs to be generated for it, and the index is associated with the condition data (and other related information) in the decrypted data for storage. If the hash value already exists in the database, the condition data in the decrypted data is directly associated with the corresponding hash value in the database (that is, the existing patient record), without generating a new patient master index.

[0084] By extracting the patient's identity information (such as name, ID number, date of birth) from the decrypted data and performing hashing, a unique third hash value can be generated. This hash value is used as a substitute for the patient's identity information in the subsequent data processing process, thereby avoiding the direct storage and transmission of the patient's sensitive identity information and enhancing the security of the data. Detecting whether the generated third hash value already exists in the patient database on the Health Commission side can ensure that duplicate patient master indexes and condition data records are not created for the same patient. This deduplication mechanism helps maintain the consistency and accuracy of patient data and avoids data redundancy and confusion. If a matching third hash value is found in the patient database on the Health Commission side, it means that the patient in the decrypted data already exists in the database. At this point, the condition data in the decrypted data can be associated with the patient record in the database (identified by the third hash value). This association method enables all relevant condition data of a specific patient to be quickly located in the subsequent data query and analysis process, improving the efficiency and accuracy of data processing. By using hash values ​​to identify patients and sharing these hash values ​​between different systems or institutions (rather than directly sharing the patient's sensitive identity information), cross-system and cross-institutional data sharing and exchange can be achieved. This approach not only protects the privacy of patients, but also promotes the interconnection and effective use of medical data. Using hash values ​​as the unique identifier of the patient's identity allows the Health Commission to flexibly adjust and optimize data management strategies as needed. For example, the storage structure and indexing method of the database can be dynamically adjusted according to the distribution and number of hash values ​​to improve the performance of data query and processing. In addition, with the continuous growth of medical data and the emergence of new technologies, this hash-based data management method is also easier to adapt to future data management and analysis needs.

[0085] Optionally, the data transmission method further includes:

[0086] When receiving a data request sent by the hospital to the health commission, the health commission analyzes the data request to extract the patient master index, determines the target data by the patient master index, and sends the target data along with the data request to the second front-end server of the hospital;

[0087] The data request is analyzed by the second front-end server to extract the target doctor, the usage habits of the target doctor are determined by a preset data model, and the target data is processed according to the usage habits.

[0088] When the Health Commission receives a data request from the hospital, it first analyzes the data request. The purpose of the analysis is to extract key information from the data request, such as the patient primary index. The patient primary index is an identifier that uniquely identifies the patient, which can help the Health Commission quickly locate the patient data related to the request. After extracting the patient primary index, the Health Commission uses this index to query and determine the target data. The target data refers to the medical data or information related to the patient specified in the data request. Through the patient primary index, the Health Commission can accurately find and extract this data. After determining the target data, the Health Commission will attach this data to the original data request and then send it to the second front-end server on the hospital side. The second front-end server is a component on the hospital side for receiving and processing data requests from the Health Commission. When the second front-end server receives the data request and target data from the Health Commission, it analyzes the data request to extract the information of the target doctor. The target doctor refers to the doctor who is responsible for processing or viewing the requested data. After extracting the target doctor, the second front-end server uses a preset data model to determine the doctor's usage habits. Usage habits may include doctors' preferences for data formats, presentation methods, processing procedures, etc. These data models may be built based on doctors' historical behaviors, feedback, or survey data. According to the target doctors' usage habits, the second front-end server will process the target data accordingly. Processing may include data formatting, filtering, sorting, encryption, and other operations to ensure that the data is presented and transmitted in the way the doctor expects.

[0089] When the hospital sends a data request to the Health Commission, the Health Commission first analyzes the data request and extracts the patient's primary index. This step ensures the pertinence of data transmission, that is, only the patient data specified in the request is transmitted, avoiding unnecessary data transmission and storage. After determining the target data through the patient's primary index, the Health Commission sends the target data with the data request to the second front-end server on the hospital side. This method of directly transmitting the target data reduces the intermediate links of data transmission and improves the efficiency of data transmission. After receiving the data request, the second front-end server further analyzes to extract the target doctor. This step provides a clear object for subsequent data processing, that is, processing according to the needs of specific doctors. The target doctor's usage habits are determined by the preset data model, and the target data is processed according to these habits. This personalized data processing method helps doctors obtain the required information faster, reduces the time for data screening and analysis, and thus improves the doctor's work efficiency. During the entire data transmission and processing process, the patient's primary index is used as the unique identifier of the data, avoiding the direct transmission of the patient's sensitive identity information and enhancing the security of the data. At the same time, the target data is processed by the preset data model instead of directly transmitting the original data, which further protects the patient's privacy. This method realizes the sharing and utilization of medical data through the data request and processing process between the hospital and the Health Commission. This helps medical institutions to better collaborate and jointly improve the quality and efficiency of medical services. By processing and analyzing the target data, it can provide strong support for doctors' medical decision-making. At the same time, these data can also be used for scientific research analysis, providing an important basis for research and development in the medical field.

[0090] Optionally, determining the usage habits of the target doctor by using a preset data model, and processing the target data according to the usage habits includes:

[0091] Define medical resource entities according to the HL7 FHIR standard and establish associations between medical resource entities, wherein the medical resource entities include basic patient information, diagnosis information, examination results, and treatment plans;

[0092] The display method and transmission method of the target data are determined according to the usage habits and the association relationship.

[0093] HL7 (Health Level Seven) is an international medical information exchange standards organization. FHIR (Fast Healthcare Interoperability Resources) is a modern, RESTful API-based medical data exchange standard launched by HL7. The FHIR standard aims to simplify the exchange and integration of medical data and achieve data interoperability between different systems by defining a series of standardized medical resource entities (Resources). According to the HL7 FHIR standard, medical resource entities refer to various data objects involved in medical information systems, such as patient basic information, diagnosis information, examination results, treatment plans, etc. These resource entities have standardized data structures and attributes, so that data between different systems can be mutually understood and exchanged. After defining the medical resource entities, it is necessary to establish associations between these entities. For example, the patient basic information entity can be associated with the diagnosis information entity, the examination result entity, the treatment plan entity, etc. to form a complete medical data chain. These associations help doctors understand the patient's medical condition more comprehensively and make more accurate medical decisions. The target doctor's usage habits may include their preferred data display methods (such as tables, charts, reports, etc.), data sorting methods, data filtering conditions, etc. These habits can be acquired through observation and data analysis of doctors' daily work. Determine the display method of the target data based on the target doctor's usage habits. For example, if the doctor prefers to display the examination results in the form of charts, then the examination results part of the target data can be displayed in the form of charts. Determine the transmission method of the target data based on the association relationship and usage habits. For example, if the target doctor needs to view the patient's examination results in real time, then the examination results part of the target data can be transmitted to the doctor's terminal device in real time through real-time data transmission methods (such as WebSocket, MQTT, etc.). If the target doctor only needs to view the patient's medical data at a specific time, then the target data can be regularly transmitted to the doctor's system or device through periodic data transmission methods (such as FTP, SFTP, etc.).

[0094] Medical resource entities, such as basic patient information, diagnostic information, test results, and treatment plans, are defined according to the HL7 FHIR standard to ensure data consistency and accuracy. By establishing associations between medical resource entities, a more comprehensive understanding of the patient's health status and treatment process can be achieved, providing doctors with more complete information support. Data display and transmission methods are determined according to the target doctor's usage habits, so that doctors can more conveniently obtain the required information and improve the personalization of data processing. Through precise data processing and display, doctors can make medical decisions faster and reduce unnecessary waste of medical resources. Customizing data transmission methods according to doctors' usage habits, such as real-time transmission, scheduled transmission, or on-demand transmission, can more effectively utilize network resources and improve the efficiency and reliability of data transmission. Personalized data processing and display methods help doctors understand patients' health status more quickly, thereby providing more accurate diagnosis and treatment recommendations. By optimizing data transmission methods, data transmission delays and errors are reduced, and the overall efficiency of medical services is improved. Using the HL7 FHIR standard to define medical resource entities and associations helps to achieve standardization and normalization of medical data, thereby improving the security and privacy protection of data. By customizing data transmission methods according to doctors' usage habits, data access rights and transmission scope can be further controlled, reducing the risk of data leakage. Through standardized data definition and processing methods, it is easier to share and exchange medical data, which promotes the interconnection of medical information. At the same time, this technical effect also provides a foundation for the development of medical intelligence. By analyzing and mining medical data, potential medical laws and patterns can be discovered, providing strong support for medical decision-making and scientific research.

[0095] This embodiment also discloses a data transmission system. Figure 4 is a schematic diagram of a module of a data transmission system disclosed in an embodiment of the present application, such as Figure 4 As shown, the system includes a generation module 401, a transmission module 402, a check module 403 and a storage module 404, wherein:

[0096] A generating module 401 is configured to generate a public-private key pair using a first encryption algorithm, and generate a temporary access token for the data to be transmitted at the hospital end according to a preset authorization mechanism, wherein the public-private key pair includes a public key and a private key, and the access token includes a sender, a receiver, access rights, and validity period data;

[0097] The transmission module 402 is configured to generate a session key according to the public key, encrypt the data to be transmitted using a second encryption algorithm and the session key, establish a target transmission channel using a virtual private network technology, and push the encrypted data, metadata and the temporary access token to the first front-end server of the Health Commission through the target transmission channel;

[0098] A checking module 403 is configured to check the validity of the temporary access token in the first front-end server, and when the check passes, use the private key to decrypt the session key to obtain decrypted data, and use a hash function to calculate a first hash value of the decrypted data;

[0099] The storage module 404 is configured to compare the first hash value with the second hash value in the metadata. When the comparison is passed, a unique patient master index is generated for each patient in the decrypted data, and the patient master index is associated with the corresponding data in the decrypted data and stored on the Health Commission end.

[0100] Optionally, the generating module 401 is configured to:

[0101] Preset multiple access rights levels based on data sensitivity, and define the scope and restrictions of each access right level;

[0102] Classifying and evaluating the data to be transmitted at the hospital end to determine the target sensitivity;

[0103] A target access permission level is matched according to the target sensitivity, and the target access permission level is encoded into the temporary access token.

[0104] Optionally, the transmission module 402 is configured to:

[0105] Configure the IPSec protocol between the hospital and the health commission and define VPN tunnel parameters, and determine the transmission method according to the target access permission level of the data to be transmitted;

[0106] According to the IPSec protocol, the VPN tunnel parameters and the selected transmission method, a target transmission channel is established between the hospital end and the Health Commission end. The target transmission channel includes a dedicated VPN tunnel and a shared VPN tunnel. The dedicated VPN tunnel is used to transmit data with the highest access permission level.

[0107] Optionally, the transmission module 402 is configured to:

[0108] Generate a first-round subkey according to the session key and a first preset round constant, determine a next-round subkey according to a previous-round subkey and a second preset round constant, and generate a subkey list according to the subkey;

[0109] The data to be transmitted is divided into multiple data blocks as initial input, and each round is encrypted using the subkey of the corresponding round in the subkey list to obtain output, and the output of the previous round is used as the input of the next round, until the preset round is reached and the output of the preset round is used as the encrypted data.

[0110] Optionally, the storage module 404 is configured to:

[0111] Extracting the patient's identity information from the decrypted data, and performing hash processing on the extracted identity information to generate a third hash value, wherein the identity information includes name, ID number, and date of birth;

[0112] Check whether the third Hash value already exists in the patient database of the health commission. If so, associate the condition data in the decrypted data with the third Hash value in the patient database.

[0113] Optionally, the data transmission system further includes an analysis module, wherein the analysis module is configured to:

[0114] When receiving a data request sent by the hospital to the health commission, the health commission analyzes the data request to extract the patient master index, determines the target data by the patient master index, and sends the target data along with the data request to the second front-end server of the hospital;

[0115] The data request is analyzed by the second front-end server to extract the target doctor, the usage habits of the target doctor are determined by a preset data model, and the target data is processed according to the usage habits.

[0116] Optionally, the analysis module is configured to:

[0117] Define medical resource entities according to the HL7 FHIR standard and establish associations between medical resource entities, wherein the medical resource entities include basic patient information, diagnosis information, examination results, and treatment plans;

[0118] The display method and transmission method of the target data are determined according to the usage habits and the association relationship.

[0119] It should be noted that: when the device provided in the above embodiment realizes its function, only the division of the above functional modules is used as an example. In actual application, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the device and method embodiments provided in the above embodiment belong to the same concept, and the specific implementation process is detailed in the method embodiment, which will not be repeated here.

[0120] This embodiment also discloses an electronic device, referring to Figure 5 The electronic device may include: at least one processor 501 , at least one communication bus 502 , a user interface 503 , a network interface 504 , and at least one memory 505 .

[0121] The communication bus 502 is used to realize the connection and communication between these components.

[0122] The user interface 503 may include a display screen (Display) and a camera (Camera). Optionally, the user interface 503 may also include a standard wired interface and a wireless interface.

[0123] The network interface 504 may optionally include a standard wired interface or a wireless interface (such as a WI-FI interface).

[0124] Among them, the processor 501 may include one or more processing cores. The processor 501 uses various interfaces and lines to connect various parts in the entire server, and executes various functions of the server and processes data by running or executing instructions, programs, code sets or instruction sets stored in the memory 505, and calling data stored in the memory 505. Optionally, the processor 501 can be implemented in at least one hardware form of digital signal processing (Digital Signal Processing, DSP), field programmable gate array (Field-Programmable Gate Array, FPGA), and programmable logic array (Programmable Logic Array, PLA). The processor 501 can integrate one or a combination of a central processing unit (Central Processing Unit, CPU), a graphics processing unit (Graphics Processing Unit, GPU) and a modem. Among them, the CPU mainly processes the operating system, user interface and application programs; the GPU is responsible for rendering and drawing the content to be displayed on the display screen; the modem is used to process wireless communications. It can be understood that the above-mentioned modem may not be integrated into the processor 501, and it can be implemented separately through a chip.

[0125] Among them, the memory 505 may include a random access memory (Random Access Memory, RAM) and may also include a read-only memory (Read-Only Memory). Optionally, the memory 505 includes a non-transitory computer-readable storage medium. The memory 505 can be used to store instructions, programs, codes, code sets or instruction sets. The memory 505 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the above-mentioned various method embodiments, etc.; the data storage area may store data involved in the above-mentioned various method embodiments, etc. The memory 505 may also be optionally at least one storage device located away from the aforementioned processor 501. As Figure 5 As shown, the memory 505 as a computer storage medium may include an operating system, a network communication module, a user interface module, and an application program of a data transmission method.

[0126] exist Figure 5 In the electronic device shown, the user interface 503 is mainly used to provide an input interface for the user and obtain data input by the user; and the processor 501 can be used to call the application program storing the data transmission method in the memory 505. When executed by one or more processors 501, the electronic device executes one or more methods in the above-mentioned embodiments.

[0127] It should be noted that, for the aforementioned method embodiments, for the sake of simplicity, they are all described as a series of action combinations, but those skilled in the art should be aware that the present application is not limited by the order of the actions described, because according to the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required for the present application.

[0128] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0129] In the several embodiments provided in this application, it should be understood that the disclosed devices can be implemented in other ways. For example, the device embodiments described above are only schematic, such as the division of units, which is only a logical function division. There may be other division methods 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 through some service interfaces, and the indirect coupling or communication connection of devices or units can be electrical or other forms.

[0130] 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.

[0131] In addition, each functional unit in each embodiment of the present application 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. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0132] If the integrated unit 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 memory. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a memory 505, including a number of 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 various embodiments of the present application. The aforementioned memory 505 includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a magnetic disk or an optical disk.

[0133] The above is only an exemplary embodiment of the present disclosure and cannot be used to limit the scope of the present disclosure. That is, any equivalent changes and modifications made according to the teachings of the present disclosure are still within the scope of the present disclosure. After considering the disclosure of the specification, those skilled in the art will easily think of other embodiments of the present disclosure. This application is intended to cover any modification, use or adaptation of the present disclosure, which follows the general principles of the present disclosure and includes common knowledge or customary technical means in the technical field that are not recorded in the present disclosure. The description and examples are only regarded as exemplary, and the scope and spirit of the present disclosure are defined by the claims.

Claims

1. A data transmission method, characterized in that: Applied to a mutual recognition platform for testing and examination, the mutual recognition platform for testing and examination includes a hospital side and a health commission side, and the method includes: Generate a public-private key pair using a first encryption algorithm, and generate a temporary access token for the data to be transmitted at the hospital end according to a preset authorization mechanism, wherein the public-private key pair includes a public key and a private key, and the access token includes a sender, a receiver, access rights, and validity period data; Generate a session key according to the public key, use a second encryption algorithm and the session key to encrypt the data to be transmitted, use a virtual private network technology to establish a target transmission channel, and push the encrypted data, metadata and the temporary access token to the first front-end server of the Health Commission through the target transmission channel; Checking the validity of the temporary access token in the first front-end server, and when the check passes, decrypting the session key using the private key to obtain decrypted data, and calculating a first hash value of the decrypted data using a hash function; The first hash value is compared with the second hash value in the metadata. When the comparison is successful, a unique patient master index is generated for each patient in the decrypted data, and the patient master index is associated with the corresponding data in the decrypted data and stored in the health commission terminal. The generating of a temporary access token for the data to be transmitted at the hospital end according to the preset authorization mechanism includes: Preset multiple access rights levels based on data sensitivity, and define the scope and restrictions of each access right level; Classifying and evaluating the data to be transmitted at the hospital end to determine the target sensitivity; matching a target access permission level according to the target sensitivity, encoding the target access permission level into the temporary access token, The use of virtual private network technology to establish a target transmission channel includes: Configure the IPSec protocol between the hospital and the health commission and define VPN tunnel parameters, and determine the transmission method according to the target access permission level of the data to be transmitted; According to the IPSec protocol, the VPN tunnel parameters and the selected transmission method, a target transmission channel is established between the hospital end and the Health Commission end. The target transmission channel includes a dedicated VPN tunnel and a shared VPN tunnel. The dedicated VPN tunnel is used to transmit data with the highest access permission level.

2. The data transmission method according to claim 1, characterized in that: The using the second encryption algorithm and the session key to encrypt the data to be transmitted comprises: Generate a first-round subkey according to the session key and a first preset round constant, determine a next-round subkey according to a previous-round subkey and a second preset round constant, and generate a subkey list according to the subkey; The data to be transmitted is divided into multiple data blocks as initial input, and each round is encrypted using the subkey of the corresponding round in the subkey list to obtain output, and the output of the previous round is used as the input of the next round, until the preset round is reached and the output of the preset round is used as the encrypted data.

3. The data transmission method according to claim 1, characterized in that: Generating a unique patient master index for each patient in the decrypted data further comprises: Extracting the patient's identity information from the decrypted data, and performing hash processing on the extracted identity information to generate a third hash value, wherein the identity information includes name, ID number, and date of birth; Check whether the third Hash value already exists in the patient database of the health commission. If so, associate the condition data in the decrypted data with the third Hash value in the patient database.

4. The data transmission method according to claim 1, characterized in that: The data transmission method further comprises: When receiving a data request sent by the hospital to the health commission, the health commission analyzes the data request to extract the patient master index, determines the target data by the patient master index, and sends the target data along with the data request to the second front-end server of the hospital; The data request is analyzed by the second front-end server to extract the target doctor, the usage habits of the target doctor are determined by a preset data model, and the target data is processed according to the usage habits.

5. The data transmission method according to claim 4, characterized in that: Determining the usage habits of the target doctor by using a preset data model, and processing the target data according to the usage habits includes: Define medical resource entities according to the HL7 FHIR standard and establish associations between medical resource entities, wherein the medical resource entities include basic patient information, diagnosis information, examination results, and treatment plans; The display method and transmission method of the target data are determined according to the usage habits and the association relationship.

6. A data transmission system, characterized in that: It includes a generation module, a transmission module, a check module and a storage module, wherein: A generating module configured to generate a public-private key pair using a first encryption algorithm, and to generate a temporary access token for the data to be transmitted at the hospital end according to a preset authorization mechanism, wherein the public-private key pair includes a public key and a private key, and the access token includes a sender, a receiver, access rights, and validity period data; A transmission module, configured to generate a session key according to the public key, encrypt the data to be transmitted using a second encryption algorithm and the session key, establish a target transmission channel using a virtual private network technology, and push the encrypted data, metadata and the temporary access token to the first front-end server of the Health Commission through the target transmission channel; A checking module configured to check the validity of the temporary access token in the first front-end server, and when the check passes, decrypt the session key using the private key to obtain decrypted data, and calculate a first hash value of the decrypted data using a hash function; A storage module is configured to compare the first hash value with the second hash value in the metadata, and when the comparison is passed, generate a unique patient master index for each patient in the decrypted data, and associate the patient master index with the corresponding data in the decrypted data and store it on the health commission end, The generating of a temporary access token for the data to be transmitted at the hospital end according to the preset authorization mechanism includes: Preset multiple access rights levels based on data sensitivity, and define the scope and restrictions of each access right level; Classifying and evaluating the data to be transmitted at the hospital end to determine the target sensitivity; matching a target access permission level according to the target sensitivity, encoding the target access permission level into the temporary access token, The use of virtual private network technology to establish a target transmission channel includes: Configure the IPSec protocol between the hospital and the health commission and define VPN tunnel parameters, and determine the transmission method according to the target access permission level of the data to be transmitted; According to the IPSec protocol, the VPN tunnel parameters and the selected transmission method, a target transmission channel is established between the hospital end and the Health Commission end. The target transmission channel includes a dedicated VPN tunnel and a shared VPN tunnel. The dedicated VPN tunnel is used to transmit data with the highest access permission level.

7. An electronic device, characterized in that: It includes a processor, a memory, a user interface and a network interface, the memory is used to store instructions, the user interface and the network interface are both used to communicate with other devices, and the processor is used to execute the instructions stored in the memory so that the electronic device executes the method as described in any one of claims 1-5.

8. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores instructions, and when the instructions are executed, the method according to any one of claims 1 to 5 is performed.

Images