Electrocardio medical data transmission method, device, equipment, medium and program product

Abstract

The invention relates to an electrocardio medical data transmission method and device, computer equipment, a storage medium and a computer program product. The method comprises the steps that device online data and a first random code sent by an electrocardio device are received, the device online data comprise a user identifier, and the first random code is generated by the electrocardio device based on a secret key and a random number sent by a first platform; when it is determined that the electrocardiogram equipment is registered on the first platform based on the user identification, a secret key and a random number corresponding to the equipment identification are acquired locally, and a second random code is generated based on the secret key and the random number; when the first random code is matched with the second random code, feeding back response data of identity verification passing corresponding to the equipment online data to the electrocardio equipment; receiving electrocardio medical data sent by the electrocardio equipment passing the identity verification, and checking whether the format of the electrocardio medical data accords with a user-defined communication protocol; and if so, processing the electrocardiogram medical data. By adopting the method, the data transmission security can be improved.

Description

Technical Field

[0001] The present application relates to the technical field of medical data transmission, and in particular to a method, apparatus, computer equipment, storage medium and computer program product for electrocardiogram medical data transmission. Background Art

[0002] The traditional ECG monitoring equipment in hospitals generally collects data through three-electrode contact collection and electrode patch plus lead wire. As the name implies, three-electrode contact collection collects data by fitting the electrode patch to the human skin, while the electrode patch plus lead wire method collects data by connecting the lead wire to the device. Then, common network transmission protocols such as WB (Wire Bond, abbreviated as WB), MQTT (Message Queuing Telemetry Transport, abbreviated as MQTT), HTTP (Hyper Text Transfer Protocol, abbreviated as HTTP), etc. are used to transmit the data to the server. However, these open source protocols are easily exploited by criminals during the data transmission process, thereby increasing the risk of data leakage. Summary of the invention

[0003] Based on this, it is necessary to provide an electrocardiogram medical data transmission method, apparatus, computer equipment, computer-readable storage medium and computer program product that can improve the security of data transmission in response to the above-mentioned technical problems.

[0004] A method for transmitting electrocardiographic medical data, the method comprising:

[0005] Receiving device online data and a first random code sent by an electrocardiogram device, wherein the device online data includes a user identifier, and the first random code is generated by the electrocardiogram device based on a key and a random number sent by a first platform;

[0006] When it is determined based on the user identifier that the electrocardiogram device has been registered on the first platform, a key and a random number corresponding to the device identifier are locally acquired, and a second random code is generated based on the key and the random number;

[0007] When the first random code matches the second random code, feedback is given to the electrocardiograph device, indicating that the identity authentication is passed and the identity authentication response data corresponding to the online data of the device is passed;

[0008] Receiving electrocardiographic medical data sent by the electrocardiographic device that has passed identity authentication, and verifying whether the format of the electrocardiographic medical data complies with the custom communication protocol;

[0009] When the format of the electrocardiographic medical data conforms to the custom communication protocol, the electrocardiographic medical data is processed.

[0010] In one embodiment, before receiving the device online data and the first random code sent by the electrocardiogram device, the process includes:

[0011] Receiving connection code acquisition data sent by the electrocardiograph device, wherein the connection code acquisition data includes a user identifier;

[0012] When it is determined based on the user identifier that the electrocardiograph device has been registered on the first platform, obtaining a key and a random number corresponding to the user identifier, where the random number is generated in advance or in real time;

[0013] Based on the key and the random number, connection code feedback data corresponding to the connection code acquisition data is generated, and the connection code feedback data is sent to the electrocardiograph device. The key and the random number in the connection code feedback data are used for identity verification of the electrocardiograph device.

[0014] In one embodiment, the device online data also includes survival time; the method further includes:

[0015] Saving the survival time, and generating a time threshold based on the survival time;

[0016] When the heartbeat reporting data sent by the electrocardiograph device is not received within the time threshold, determining that the electrocardiograph device is offline;

[0017] When the heartbeat reporting data sent by the electrocardiograph device is received within the time threshold, the heartbeat feedback data corresponding to the heartbeat reporting data is sent to the electrocardiograph device, and the heartbeat feedback data is used to instruct the electrocardiograph device to determine whether the first platform is abnormal. If the first platform is abnormal, the information that the first platform is abnormal is output.

[0018] In one embodiment, after processing the electrocardiogram medical data, the following steps are performed:

[0019] Receiving device offline data sent by the electrocardiograph device;

[0020] The status of the electrocardiograph device is updated to offline based on the device offline data.

[0021] In one of the embodiments, the ECG medical data includes at least one of patient alarm data, technical alarm data, device location data, device power data, and real-time ECG data.

[0022] In one of the embodiments, the data transmission between the ECG device and the first platform is generated based on a custom communication protocol, and the custom communication protocol removes the interaction rules in the general protocol that are not related to the ECG medical data.

[0023] In one embodiment, after receiving the electrocardiographic medical data sent by the electrocardiographic device that has passed identity authentication, the method further includes:

[0024] When the current data packet corresponding to the ECG medical data sent by the ECG device is received successfully, confirmation data of the successful reception of the current data packet is asynchronously sent to the ECG device, and the confirmation data is used to instruct the ECG device to cache the data packets without confirmation data, and before the ECG device sends the device offline data to the first platform, the cached data packets without the confirmation data are sent to the first platform.

[0025] In one embodiment, the processing of the electrocardiographic medical data includes:

[0026] Obtain a target mapping relationship between a user ID and a doctor ID;

[0027] Based on the target mapping relationship, obtaining a doctor identifier corresponding to the user identifier of the electrocardiographic medical data;

[0028] The electrocardiogram medical data is sent to a terminal corresponding to the doctor identification.

[0029] In one embodiment, the step of obtaining a target mapping relationship between a user identifier and a doctor identifier includes:

[0030] Obtain the static mapping relationship between user ID and doctor ID;

[0031] When an online notification or offline notification of a terminal corresponding to the doctor identifier is monitored, the static mapping relationship is dynamically updated to obtain a target mapping relationship.

[0032] In one embodiment, the processing of the electrocardiographic medical data includes:

[0033] Acquire pre-configured routing information, the routing information including a routing address of the second platform;

[0034] The electrocardiogram medical data is sent to a second platform corresponding to the routing address.

[0035] In one embodiment, before obtaining the pre-configured routing information, the process further includes:

[0036] receiving a routing information configuration request, the routing information configuration request carrying a routing address and a data transmission direction, the data transmission direction being used to characterize a direction of data transmission and / or data reception between the first platform and a second platform corresponding to the routing address;

[0037] The routing address is stored, and the data transmission direction corresponding to the routing address is set.

[0038] In one embodiment, sending the electrocardiogram medical data to the second platform corresponding to the routing address includes:

[0039] When the electrocardiographic medical data is medical data of a single user, sending the electrocardiographic medical data of the single user to the second platform corresponding to the routing address;

[0040] When the ECG medical data is medical data of batch users, a request for obtaining the ECG medical data from the second platform is received, and based on the request for obtaining the ECG medical data, whether the second platform is online is determined; when the second platform is online, the ECG medical data of the batch users is sent to the second platform.

[0041] In one embodiment, before receiving the ECG medical data acquisition request from the second platform, the method further includes:

[0042] receiving a routing information configuration instruction of a second platform corresponding to the first platform, and configuring routing information of the second platform corresponding to the first platform based on the configuration instruction;

[0043] The routing information is sent to the second platform, and the configuration information is used to instruct the second platform to update the local routing information, and after the update is completed, feedback the update completion information to the first platform.

[0044] In one embodiment, the method further comprises:

[0045] Receiving electrocardiographic medical data sent by the second platform, wherein the electrocardiographic medical data carries a routing address;

[0046] When the routing address is stored in the local routing address whitelist, storing the electrocardiographic medical data;

[0047] When the routing address is stored in a local routing address blacklist, shielding the electrocardiographic medical data;

[0048] When the routing address is not stored in the local routing address whitelist and the local routing address blacklist, and the number of times the second platform corresponding to the routing address continues to send electrocardiographic medical data is greater than a preset value, the routing address corresponding to the second platform is stored in the local routing address blacklist.

[0049] In one embodiment, the method further comprises:

[0050] Dynamically manage the resources of the first platform based on K8S technology.

[0051] In a second aspect, the present application further provides an electrocardiogram medical data transmission device, the device comprising:

[0052] A data receiving module, used for receiving device online data and a first random code sent by an ECG device, wherein the device online data includes a user identifier, and the first random code is generated by the ECG device based on a key and a random number sent by a first platform; and receiving ECG medical data sent by the ECG device after identity verification;

[0053] The permission verification module is used to obtain the key and random number corresponding to the device identification when it is determined based on the user identification that the electrocardiograph device has been registered on the first platform, and generate a second random code based on the key and random number; when the first random code and the second random code match, feedback the response data of identity authentication corresponding to the device online data to the electrocardiograph device; and verify whether the format of the electrocardiograph medical data conforms to the custom communication protocol;

[0054] The routing module is used to process the electrocardiographic medical data when the format of the electrocardiographic medical data conforms to the custom communication protocol.

[0055] In a third aspect, the present application further provides a computer device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the method in any one of the above-mentioned embodiments when executing the computer program.

[0056] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of the method in any one of the above-mentioned embodiments.

[0057] In a fifth aspect, the present application also provides a computer program product, including a computer program, which implements the steps of the method in any one of the above-mentioned embodiments when executed by a processor.

[0058] The above-mentioned ECG medical data transmission method, apparatus, computer equipment, storage medium and computer program product first perform identity authentication before ECG medical data transmission, including receiving device online data and a first random code sent by the ECG device, the device online data including a user identification, the first random code being generated by the ECG device based on a key and a random number sent by a first platform; when it is determined based on the user identification that the ECG device has been registered on the first platform, obtaining the key and random number corresponding to the device identification, and generating a second random code based on the key and the random number; when the first random code and the second random code match, feeding back to the ECG device response data corresponding to the device online data indicating that the identity authentication has passed; when transmitting ECG medical data, a custom communication protocol is used, and after receiving the ECG medical data, first checking whether the format of the ECG medical data complies with the custom communication protocol, and only if the format of the ECG medical data complies with the custom communication protocol will the ECG medical data be processed, thereby improving the security of the ECG medical data by means of verification and custom communication protocols. BRIEF DESCRIPTION OF THE DRAWINGS

[0059] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related technologies, the drawings required for use in the embodiments or the related technical descriptions are briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0060] Figure 1 A diagram showing an application environment of a method for transmitting electrocardiogram medical data in an embodiment;

[0061] Figure 2 is a block diagram of a first platform in one embodiment;

[0062] Figure 3 A schematic diagram of a flow chart of a method for transmitting electrocardiogram medical data in one embodiment;

[0063] Figure 4 A flowchart of an electrocardiogram device authentication step in one embodiment;

[0064] Figure 5 A flowchart of the steps of transmitting ECG medical data in one embodiment;

[0065] Figure 6 A flowchart of a connection code acquisition step in one embodiment;

[0066] Figure 7 A flowchart of the device offline steps in one embodiment;

[0067] Figure 8is a timing diagram of a method for transmitting electrocardiographic medical data in one embodiment;

[0068] Fig. 9 A schematic diagram of routing and forwarding of different platforms in one embodiment;

[0069] Fig.10 is a structural block diagram of an electrocardiogram medical data transmission device in one embodiment;

[0070] Fig.11 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0071] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0072] The electrocardiogram medical data transmission method provided in the embodiment of the present application can be applied to Figure 1 In the application environment shown, the ECG device 102 communicates through the network gateway device 106, and the gateway device 106 communicates with the first platform 104. The data storage system can store data that the first platform 104 needs to process. The data storage system can be integrated on the first platform 104, or it can be placed on the cloud or other network servers.

[0073] The data transmission between the ECG device 102 and the gateway device 106 may be transmitted via the Bluetooth protocol, while the data transmission between the gateway device 106 and the first platform 104 may be performed via a custom communication protocol.

[0074] The ECG device 102 collects ECG medical data and transmits it to the gateway device 106. The gateway device 106 transmits the ECG medical data to the first platform 104. The server 104 can send the ECG medical data to the target screen for display, or store the ECG medical data, which is not specifically limited here.

[0075] In order to ensure data transmission between the gateway device 106 and the first platform 104, strong authentication and a custom communication protocol are used to improve data transmission between the two. Specifically, the first platform 104 receives device online data and a first random code sent by the ECG device 102 through the gateway device 106. The device online data includes a user identifier, and the first random code is generated by the ECG device based on a key and a random number sent by the first platform. When it is determined based on the user identifier that the ECG device 102 has been registered on the first platform, the key and random number corresponding to the device identifier are obtained locally, and a second random code is generated based on the key and the random number. When the first random code and the second random code match, response data of identity authentication corresponding to the device online data is fed back to the ECG device 102. ECG medical data sent by the ECG device 102 that has passed the identity authentication is received, and the format of the ECG medical data complies with the custom communication protocol. When the format of the ECG medical data complies with the custom communication protocol, the first platform 104 processes the ECG medical data.

[0076] The ECG device 102 may be any ECG monitoring device. The first platform 104 may be implemented by an independent server or a server cluster composed of multiple servers. The gateway device 106 may also be any gateway device, which is not specifically limited here.

[0077] Among them, combined Figure 2 As shown, Figure 2 It is a block diagram of the first platform in an embodiment. In this embodiment, the first platform 104 includes a data receiving and forwarding module, a routing management module, a device management module, a permission verification module, a reporting module, a platform system, a data persistence module, a container management module and basic tools. In this embodiment, the data receiving and forwarding module, the routing management module, the device management module and the permission verification module are mainly introduced. The data receiving and forwarding module is used to receive the ECG medical data sent by the ECG device 102 and forward the ECG medical data. The permission verification module is used to verify whether the ECG device 102 is legal. The device management module stores the corresponding user identification of the ECG device registered on the first platform, which can be used to verify whether the ECG device 102 is legal. The routing module is used to save the legal routing relationship to transfer the ECG medical data to the corresponding location.

[0078] In an exemplary embodiment, Figure 3 As shown, a method for transmitting electrocardiographic medical data is provided. Figure 1 The server 104 in the example is used as an example to illustrate, including the following steps 302 to 310. Among them:

[0079] S302: receiving device online data and a first random code sent by the ECG device, where the device online data includes a user identifier, and the first random code is generated by the ECG device based on a key and a random number sent by the first platform.

[0080] The device online data is sent by the ECG device to the first platform, which complies with the custom communication protocol and is used to inform the first platform that the ECG device has been online. The device online data can be a specific data packet of the custom communication protocol, wherein the data packet includes a data type and a data body, and the data body includes at least an online and offline flag and a user identifier. The user identifier may include a user name, and in other embodiments, the user identifier includes a user name and a user identity code to uniquely characterize the user.

[0081] The first random code is generated by the ECG device. Specifically, the ECG device generates the first random code based on the key and random number sent by the first platform. The key and random number are sent to the ECG device by the first platform, wherein the key is allocated by the first platform to each ECG device, and the key corresponding to each ECG data is different. The random number can be generated in real time after the first platform receives the connection code of the ECG data to obtain data, or it can be generated in advance, which is not specifically limited here.

[0082] S304: When it is determined based on the user identifier that the ECG device has been registered on the first platform, a key and a random number corresponding to the device identifier are locally acquired, and a second random code is generated based on the key and the random number.

[0083] The key is a key assigned by the first platform to each ECG device registered on the platform, that is, when the ECG device is registered on the first platform, a key is assigned to the ECG device. The random number can be generated in advance or in real time, which is not specifically limited here. The second random code is generated by the first platform based on the key and random number corresponding to the ECG device stored locally.

[0084] Among them, the first platform can query whether the local device management module includes the user identifier to determine whether the ECG device has been registered on the first platform. If the ECG device has been registered on the first platform, the ECG device will continue to be verified through the authority verification module, and the authority verification module verifies the ECG device based on the key and random number.

[0085] S306: When the first random code and the second random code match, response data indicating that the identity authentication has passed and corresponding to the device online data is fed back to the electrocardiograph device.

[0086] The response data is generated after the ECG device is subjected to the permission check. The response data complies with the custom communication protocol and is used to inform the ECG device whether the permission check has passed. The response data at least includes the data type and the result of the permission check.

[0087] The first platform matches the first random code sent by the ECG device with the second random code generated locally, and if the match is successful, the first platform feeds back corresponding identity verification passed response data to the ECG device. If the match fails, the first platform feeds back corresponding identity verification failed response data to the ECG device.

[0088] Specifically, combined Figure 4 As shown, Figure 4 The present invention is a flowchart of the ECG device authentication steps in an embodiment. In this embodiment, the ECG device generates device online data through a custom communication protocol and sends it to a data receiving module of a first platform, wherein the data receiving module sends the device online data to a device management module, and the device management module checks whether the ECG device is registered on the first platform. If it is not registered, the authority check fails. If it is registered, the authority check module checks whether the first random code is consistent with the second random code generated by the platform. If they are consistent, the check passes. Otherwise, the authority check fails. Response data is obtained based on the result of the data check, and the first platform feeds back the response data of the authority check to the ECG device through the data receiving module.

[0089] S308: Receive ECG medical data sent by the ECG device that has passed identity authentication, and verify whether the format of the ECG medical data complies with the custom communication protocol.

[0090] S310: When the format of the electrocardiographic medical data complies with the custom communication protocol, the electrocardiographic medical data is processed.

[0091] The data transmission between the ECG device and the first platform is generated based on a custom communication protocol, and the custom communication protocol is to remove the interaction rules in the general protocol that are not related to the ECG medical data. The data transmission includes the transmission of ECG medical data, and also includes device online data, device offline data, connection code acquisition data, connection code feedback data, heartbeat reporting data, heartbeat feedback data, etc. In one optional embodiment, the ECG medical data includes at least one of patient alarm data, technical alarm data, device location data, device power data, and real-time ECG data.

[0092] Specifically, combined Figure 5 , Figure 5The flowchart is a step of transmitting ECG medical data in an embodiment. In this embodiment, when the ECG device passes the authority check, the ECG device can transmit ECG medical data with the first platform, wherein the ECG device uploads the ECG medical data to the first platform. After the first platform receives the ECG medical data, it can process the ECG medical data, including forwarding the ECG medical data to the corresponding doctor's terminal; and / or forwarding the ECG medical data to other platforms based on the configuration of the routing module, wherein other platforms can continue to forward the ECG medical data to other platforms based on the configuration of their own routing modules, or forward the ECG medical data to the corresponding doctor's terminal, which is not specifically limited here. After the first platform receives the ECG medical data, it also asynchronously feeds back to the ECG device confirmation data indicating that the data packet corresponding to the ECG medical data has been successfully received.

[0093] The above-mentioned ECG medical data method first performs identity authentication before ECG medical data transmission, including receiving device online data and a first random code sent by the ECG device, the device online data including a user identification, and the first random code is generated by the ECG device based on a key and a random number sent by the first platform; when it is determined based on the user identification that the ECG device has been registered on the first platform, the key and random number corresponding to the device identification are obtained, and a second random code is generated based on the key and the random number; when the first random code and the second random code match, response data of identity authentication corresponding to the device online data is fed back to the ECG device; when ECG medical data is transmitted, a custom communication protocol is adopted, and after receiving the ECG medical data, the format of the ECG medical data is first verified to be in accordance with the custom communication protocol, and the ECG medical data will only be processed if the format of the ECG medical data is in accordance with the custom communication protocol, thereby improving the security of the ECG medical data by means of verification and custom communication protocols.

[0094] In one of the embodiments, before receiving the device online data and the first random code sent by the ECG device, it includes: receiving the connection code acquisition data sent by the ECG device, the connection code acquisition data including the user identification; when it is determined based on the user identification that the ECG device has been registered on the first platform, obtaining the key and random number corresponding to the user identification, the random number is pre-generated or generated in real time; generating connection code feedback data corresponding to the connection code acquisition data based on the key and the random number, sending the connection code feedback data to the ECG device, and the key and random number in the connection code feedback data are used for identity verification of the ECG device.

[0095] The connection code acquisition data is used to be sent to the first platform before the ECG device goes online, so as to obtain the key and random number from the first platform, wherein the connection code acquisition data follows the custom communication protocol and includes at least the data type and user identification. The connection code feedback data corresponds to the connection code acquisition data, follows the custom communication protocol and includes at least the data type, key and random number.

[0096] Among them, combined Figure 6 As shown, Figure 6 The present invention is a flowchart of a connection code acquisition step in an embodiment. In this embodiment, before the ECG device goes online, a connection code is first acquired from the first platform to facilitate the subsequent identity authentication of the ECG device. Specifically, the ECG device sends a connection code acquisition data to the first platform. The data receiving module of the first platform receives the connection code acquisition data, and queries the device management module whether the device corresponding to the user identifier is registered on the first platform. If it is not registered, a verification failure message is fed back. If it is registered, a key corresponding to the user identifier is acquired through the authority verification module, and a random code is generated and stored in association with the key. Connection code feedback data is generated based on the key and the random code, and the connection code feedback data is sent to the ECG device, for example, fed back to the ECG device through a gateway device.

[0097] In the above embodiment, the key and the random number are transmitted before the identity authentication to ensure the security of the identity authentication.

[0098] In one of the embodiments, the device online data also includes survival time; the method also includes: saving the survival time, and generating a time threshold based on the survival time; when the heartbeat reporting data sent by the ECG device is not received after the time threshold, determining that the ECG device is offline; when the heartbeat reporting data sent by the ECG device is received within the time threshold, sending heartbeat feedback data corresponding to the heartbeat reporting data to the ECG device, the heartbeat feedback data is used to instruct the ECG device to determine whether the first platform is abnormal, and if the first platform is abnormal, outputting information about the abnormality of the first platform.

[0099] The survival time is the heartbeat survival time, and the time threshold may be generated based on the survival time, for example, 1.5 times of the survival time, and may be other values ​​in other embodiments.

[0100] The heartbeat reporting data and the heartbeat feedback data are used to ensure that the ECG device and the first platform are online and both comply with a custom communication protocol, wherein the heartbeat reporting data includes at least a data type, a user identifier and a timestamp, and the heartbeat feedback data also includes at least a data type and a timestamp.

[0101] The device online data includes the survival time. After the first platform receives the device online data, it caches the survival time, and the device starts to send heartbeat reporting data to the first platform. The first platform sends heartbeat feedback data corresponding to the heartbeat reporting data to the ECG device, and caches the time when the ECG device reports the heartbeat reporting data. The first platform determines whether the current device is offline. When the device fails to report heartbeat reporting data for more than 1.5 times the survival time, the first platform will take the ECG device offline. For example, if the connection is abnormal, if the ECG device reports the heartbeat but does not receive the heartbeat feedback data from the platform within the survival time, the first platform will be considered abnormal, and will take the initiative to go offline and prompt the patient.

[0102] In one of the embodiments, after receiving the ECG medical data sent by the ECG device that has passed the identity authentication, it also includes: when the current data packet corresponding to the ECG medical data sent by the ECG device is received successfully, asynchronously sending confirmation data of the successful reception of the current data packet to the ECG device, the confirmation data is used to instruct the ECG device to cache the data packets without confirmation data, and before the ECG device sends the device offline data to the first platform, the cached data packets without confirmation data are sent to the first platform.

[0103] In this embodiment, in order to avoid packet loss, each data packet will be confirmed, that is, one packet one confirmation. When the first platform successfully receives the data packet, it asynchronously returns the corresponding confirmation data to the ECG device. The ECG device caches the data packets without confirmation data, and before the device goes offline, the cached data packets without confirmation data are sent to the first platform. In this way, all data packets are sent to the first platform, and packet loss will not occur.

[0104] In one of the embodiments, after the ECG medical data is processed, the method includes: receiving device offline data sent by the ECG device; and updating the state of the ECG device to offline based on the device offline data.

[0105] The device offline data is sent by the ECG device to the first platform, and is used to inform the first platform that the ECG device is offline. It also complies with a custom communication protocol and includes at least a data type and a user identifier.

[0106] Specifically, combined Figure 7 As shown, Figure 7 The present invention is a flowchart of the device offline steps in an embodiment. In this embodiment, before sending the device offline data, the ECG device first sends the cached ECG medical data without confirmation data to the first platform, and after the sending is completed, sends the device offline data to the first platform. After the first platform receives the device offline data, it updates the status of the ECG device to offline based on the device offline data, and subsequently generates a monitoring report record based on the transmitted ECG medical data.

[0107] In order to facilitate the understanding of those skilled in the art, Figure 8 As shown, Figure 8 This is a timing diagram of an ECG medical data transmission method in an embodiment. In this embodiment, data is transmitted between the ECG device and the gateway device via the Bluetooth protocol, and data is transmitted between the gateway device and the first platform via a custom communication protocol, wherein the custom communication protocol is a lightweight data communication protocol combined with medical industry scenarios, which removes interaction rules in the general protocol that are not related to ECG medical data.

[0108] Each data packet in the communication protocol includes a data type and a data body, where the type includes 1 byte, as shown in the following table:

[0109]

[0110]

[0111] The monitoring notification MonitorNotify, which is the device online data in the above text, is as follows:

[0112]

[0113] The server responds to the device online MonitorNotifyBack, which is the example of the response data above:

[0114]

[0115] The example of PatientAlarm is as follows:

[0116]

[0117]

[0118] An example of a technical alarm is

[0119]

[0120] The example of device position BtPosition

[0121]

[0122]

[0123] The example of device power BtPower is as follows:

[0124]

[0125] The example of real-time data is:

[0126]

[0127] The device heartbeat Ping is an example of the heartbeat reporting data mentioned above:

[0128]

[0129] Among them, the server heartbeat response PingBack, that is, an example of heartbeat feedback data:

[0130]

[0131] The AccessCode is obtained for this connection, which is the example of obtaining data using the connection code above:

[0132]

[0133] The server sends the connection key AccessCodeBack, which is the example of the device offline data in the above text:

[0134]

[0135] In this embodiment, in order to ensure the security of data transmission, a key is assigned to each ECG device on the first platform. When the ECG device establishes a connection with the first platform, the ECG device sends the current device number to the first platform. If the ECG device has been registered on the first platform, the first platform will respond with a key and a random number to the ECG device. The ECG device generates a first random code based on the key, random number and the device's own password, and reports it together with the MonitorNotify type data. After receiving it, the first platform will generate a random code in the same way to match it with the one uploaded by the ECG device. If they are consistent, the response is successful, otherwise it fails. After verification, the first platform will respond with a MonitorNotifyBack to the corresponding ECG device. After receiving the response, the ECG device can start sending various real-time data to the first platform. Real-time data transmission is the gateway device sending various real-time data to the platform, including ECG data and various alarm data. The real-time transmission of ECG data to the first platform needs to ensure the stability and reliability of data transmission, but there may be packet loss when the network jitters. In order to minimize the impact of network status on data transmission, this embodiment uses a sending confirmation mechanism to ensure that data must be delivered, that is, when the device sends RealtimeData data, the first platform will confirm it once for each packet sent. In order to ensure efficient and real-time transmission of data, sending and confirmation are asynchronous, and the ECG device will cache data that has not been confirmed by the platform. When the data arrives at the first platform, the first platform will first receive the data and verify whether the real-time data format complies with the custom communication rules. After the verification is passed, the ECG device will be informed that the verification is passed. After the data enters the first platform, the first platform will forward the data to different doctor-side displays through the doctor-patient relationship configured in the forwarding module. When the first platform receives the data, the routing module will query whether the routing mapping is configured in the current routing table. If it exists, the message will be routed to the corresponding second platform. Specifically, after the first platform receives the data, it can be transferred to the display for display. Data that has not been confirmed by the first platform will be sent to the first platform before the end of monitoring. At the end of monitoring, the device sends MonitorNotify type data to inform the platform that it is offline. After receiving the data, the first platform will update the device status to offline.

[0136] Among them, the device online data includes the survival time. After the first platform receives the device online data, it caches the survival time, and the device starts to send heartbeat reporting data to the first platform. The first platform sends heartbeat feedback data corresponding to the heartbeat reporting data to the ECG device, and caches the time when the ECG device reports the heartbeat reporting data. Among them, the first platform determines whether the current device is offline. When the device fails to report heartbeat reporting data for more than 1.5 times the survival time, the first platform will take the ECG device offline. For example, if it is abnormally disconnected, if the ECG device does not receive the platform's heartbeat feedback data within the survival time after reporting the heartbeat, it will be considered that there is an abnormality in the first platform, and it will take the initiative to go offline and prompt the patient.

[0137] In the above embodiment, the security of electrocardiographic medical data is improved by verifying and customizing the communication protocol.

[0138] The processing of ECG medical data by the first platform includes at least one of the following: forwarding the ECG medical data to the corresponding doctor's terminal to display the ECG medical data on the doctor's terminal; forwarding the ECG medical data to the second platform according to a pre-configured routing relationship to achieve cross-platform data sharing.

[0139] In one of the embodiments, processing electrocardiogram medical data includes: obtaining a target mapping relationship between a user identifier and a doctor identifier; based on the target mapping relationship, obtaining a doctor identifier corresponding to the user identifier of the electrocardiogram medical data; and sending the electrocardiogram medical data to a terminal corresponding to the doctor identifier.

[0140] In one of the optional embodiments, obtaining a target mapping relationship between a user identifier and a doctor identifier includes: obtaining a static mapping relationship between a user identifier and a doctor identifier; when an online notification or an offline notification of a terminal corresponding to the doctor identifier is monitored, dynamically updating the static mapping relationship to obtain a target mapping relationship.

[0141] In this embodiment, when the ECG device reports ECG medical data, it will carry the user name corresponding to the current ECG device. When the first platform receives the ECG medical data, it will perform relationship mapping based on the user name and transfer the data to the corresponding doctor's terminal. The static relationship mapping between the user name and the doctor is pre-maintained on the first platform. Optionally, when it is detected that the doctor is online, the current static relationship will be dynamically updated to avoid forwarding data to doctors who are not online, resulting in unreasonable use of traffic. Such a mechanism can effectively ensure point-to-point transmission of data and interactive actions such as doctors reminding their subordinates to take medicine.

[0142] In one of the embodiments, processing the ECG medical data includes: obtaining pre-configured routing information, the routing information including a routing address of the second platform; and sending the ECG medical data to the second platform corresponding to the routing address.

[0143] In this embodiment, the routing information is the pre-configured data forwarding relationship between the first platform and the second platform. Since many hospitals adopt intranet deployment, they cannot be accessed from the outside. When joint diagnosis is required or the main hospital wants to view the data of each branch hospital, other architectures need to be replaced to achieve it. In order to solve this problem, a temporary routing transfer function is added to the platform. Specifically, two platforms deployed in the intranet configure each other's routing address and expose the corresponding port to the public network, thereby realizing cross-network forwarding. Specifically, combined with Fig. 9 As shown, Fig. 9It is a schematic diagram of routing forwarding of different platforms in one embodiment, so that ECG medical data is sent to the second platform based on the routing address of the second platform in the pre-configured routing address.

[0144] In one of the embodiments, the above method also includes: receiving ECG medical data sent by the second platform, the ECG medical data carrying a routing address; when the routing address is stored in the local routing address whitelist, storing the ECG medical data; when the routing address is stored in the local routing address blacklist, shielding the ECG medical data; when the routing address is not stored in the local routing address whitelist and the local routing address blacklist, and the number of times the second platform corresponding to the routing address continues to send ECG medical data is greater than a preset value, storing the routing address corresponding to the second platform in the local routing address blacklist.

[0145] In this embodiment, exposing the port to the public network will bring certain risks, so a mechanism is introduced to ensure the security of data transmission between platforms. Therefore, a black and white list function is added. Here, the routing address of the other party needs to be added to the white list. Since the forwarded message within the platform needs to carry its own source address, when it is found that the source address does not match the white list, the message will be discarded. If the message from the wrong source is sent ten times in a row, the platform will automatically set the source to the black list and block the source data.

[0146] In one of the embodiments, before obtaining the pre-configured routing information, it also includes: receiving a routing information configuration request, the routing information configuration request carries a routing address and a data transmission direction, the data transmission direction is used to characterize the direction of data sending and / or data receiving between the first platform and the second platform corresponding to the routing address; storing the routing address, and setting the data transmission direction corresponding to the routing address.

[0147] In this embodiment, when adding routing information, you can also select the direction of data transmission, such as one-way transmission or two-way transmission, that is, receiving data and sending data. If you choose one-way sending, it means that the other party can only passively receive the data of the first platform, and the first platform will block the other party's data. If you choose to receive, it means that you can receive the other party's data. If both are selected, it means that the data is two-way, and both parties can operate each other's data.

[0148] In one of the embodiments, sending the ECG medical data to the second platform corresponding to the routing address includes: when the ECG medical data is the medical data of a single user, sending the ECG medical data of the single user to the second platform corresponding to the routing address; when the ECG medical data is the medical data of batch users, receiving an ECG medical data acquisition request from the second platform, and judging whether the second platform is online based on the ECG medical data acquisition request, and when the second platform is online, sending the ECG medical data of batch users to the second platform.

[0149] In one of the embodiments, before receiving the ECG medical data acquisition request from the second platform, it also includes: receiving the routing information configuration instruction of the second platform corresponding to the first platform, and configuring the routing information of the second platform corresponding to the first platform based on the configuration instruction; sending the routing information to the second platform, the configuration information is used to instruct the second platform to update the local routing information, and after the update is completed, feedback the update completion information to the first platform.

[0150] When data flows to other second platforms that are open to the first platform, doctors on the second platform may only want to see one or several patients on the first platform. Therefore, there are two dimensions of sharing between individual patients and all patients on the first platform, namely, individuals and the entire hospital. For the scenario where branches of the same level participate in joint diagnosis, the first platform only needs to share a single patient with the other party. For the scenario where the main hospital needs to view the patients of each branch, the first branch is viewed as a whole by the main hospital:

[0151] The first is to share a single patient. When a patient is shared with one or more hospitals, when the corresponding device data is reported to the first platform, the first platform will route it to the other platform based on the sharing relationship and then the other platform will transfer the data. The routed data will have a separate routing mark and source address. When the other platform finds that the data has a routing address, it will verify whether the source address is legal. If it is legal, it will continue to flow, otherwise it will be discarded directly.

[0152] When the hospital is shared as a whole, it is necessary to establish a hierarchical relationship of hospitals on the first platform, that is, set the general hospital to which the current hospital belongs. After the setting is completed, the first platform will send a hierarchical relationship data to the general hospital platform. When the general hospital platform receives the data, it will dynamically update its own local hierarchical relationship. After the update is successful, it will send a successful response message to the first platform. When the general hospital platform selects the branch to be viewed, it will notify the branch. After the first platform receives the notification, when the device reports data to the first platform, the first platform will first check whether the corresponding general hospital platform is online at this time (that is, routing forwarding will only be established when the general hospital views the current branch). If it is online, the data will be forwarded to the corresponding general hospital platform.

[0153] In one of the embodiments, the above method also includes: dynamically managing the resources of the first platform based on K8S technology.

[0154] In the case of limited server resources in hospitals, how to maximize the use of resources is a problem. Considering hardware and labor costs, hospitals generally do not hire relevant technical personnel to maintain the system. In addition, not all hospitals can open their intranets to the public. Therefore, a mechanism is needed to achieve self-monitoring of the system and to dynamically expand and contract the platform when resources are insufficient or too many resources are not needed, so as to ensure that the system can still run smoothly and efficiently when hardware and labor resources are insufficient. For this reason, K8S technology is introduced in this embodiment (it is a container orchestration engine open sourced by Google, which supports automated deployment, large-scale scalability, and application containerized management). By applying containerization, cluster deployment can be achieved on a single physical machine, and K8S's built-in HPA (Horizontal Pod Autoscaler), that is, container horizontal automatic elastic expansion technology, can be used to monitor the CPU usage of the currently running container and perform corresponding operation processes according to pre-configured policies. For example, the upper threshold is configured to be 85% of CPU usage, lasting for 2 minutes, and the lower threshold is 40% of CPU usage, lasting for 2 minutes. Once the container continues to run above the set CPU threshold for more than 2 minutes, K8S will automatically create a new container in the cluster to share the pressure. Similarly, when the container continues to run at a low CPU for more than 2 minutes, K8S will automatically delete excess containers to release occupied hardware resources. This ensures the stable operation of the platform. When too many monitoring devices are connected, there will be no data delay or data loss due to the performance bottleneck of a single node, which greatly reduces the hospital's investment in hardware resources and human resources, and reduces operation and maintenance costs.

[0155] In the above embodiment, K8S container management technology is used to effectively support 1 million device connections at a lower hardware cost; the distributed cluster effectively improves the data flow performance and platform reliability; a single node supports real-time reception, processing and distribution of millions of ECG messages per second. Millisecond-level message flow. It has strong scalability for the ECG medical industry.

[0156] It should be understood that, although the steps in the flowcharts involved in the above embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above embodiments may include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0157] Based on the same inventive concept, the embodiment of the present application also provides an electrocardiographic medical data transmission device for implementing the electrocardiographic medical data transmission method involved above. The implementation solution provided by the device to solve the problem is similar to the implementation solution recorded in the above method, so the specific limitations in one or more embodiments of the electrocardiographic medical data transmission device provided below can refer to the limitations of the electrocardiographic medical data transmission method above, and will not be repeated here.

[0158] In an exemplary embodiment, Fig.10 As shown, a device for transmitting electrocardiogram medical data is provided, including: a data receiving module 1001, an authority checking module 1002 and a routing module 1003, wherein:

[0159] The data receiving module 1001 is used to receive the device online data and the first random code sent by the ECG device, the device online data includes the user identification, and the first random code is generated by the ECG device based on the key and random number sent by the first platform; and receive the ECG medical data sent by the ECG device that has passed the identity authentication;

[0160] The permission verification module 1002 is used to obtain the key and random number corresponding to the device identification when it is determined based on the user identification that the ECG device has been registered on the first platform, and generate a second random code based on the key and the random number; when the first random code and the second random code match, feedback the response data of identity authentication corresponding to the device online data to the ECG device; and verify whether the format of the ECG medical data complies with the custom communication protocol;

[0161] The routing module 1003 is used to process the ECG medical data when the format of the ECG medical data conforms to the custom communication protocol.

[0162] In one embodiment, the data receiving module 1001 is further used to receive connection code acquisition data sent by the electrocardiograph device, and the connection code acquisition data includes a user identifier.

[0163] The above-mentioned authority verification module 1002 is also used to obtain the key and random number corresponding to the user identification when it is determined based on the user identification that the ECG device has been registered on the first platform, and the random number is generated in advance or in real time; based on the key and random number, generate connection code feedback data corresponding to the connection code acquisition data, and send the connection code feedback data to the ECG device. The key and random number in the connection code feedback data are used for identity verification of the ECG device.

[0164] In one of the embodiments, the device online data also includes the survival time; the above-mentioned data receiving module 1001 is also used to save the survival time and generate a time threshold based on the survival time; when the heartbeat reporting data sent by the ECG device is not received after the time threshold, the ECG device is determined to be offline; when the heartbeat reporting data sent by the ECG device is received within the time threshold, heartbeat feedback data corresponding to the heartbeat reporting data is sent to the ECG device, and the heartbeat feedback data is used to instruct the ECG device to determine whether the first platform is abnormal. If the first platform is abnormal, the information that the first platform is abnormal is output.

[0165] In one of the embodiments, the data receiving module 1001 is further used to receive device offline data sent by the ECG device; and update the status of the ECG device to offline based on the device offline data.

[0166] In one embodiment, the ECG medical data includes at least one of patient alarm data, technical alarm data, device location data, device power data, and real-time ECG data.

[0167] In one of the embodiments, data transmission between the ECG device and the first platform is generated based on a custom communication protocol, where the custom communication protocol removes interaction rules in the general protocol that are not related to ECG medical data.

[0168] In one of the embodiments, the data receiving module 1001 is also used to asynchronously send confirmation data of successful reception of the current data packet to the ECG device when the current data packet corresponding to the ECG medical data sent by the ECG device is successfully received. The confirmation data is used to instruct the ECG device to cache the data packets without confirmation data, and send the cached data packets without confirmation data to the first platform before the ECG device sends the device offline data to the first platform.

[0169] In one of the embodiments, the data receiving module 1001 is also used to obtain a target mapping relationship between a user identifier and a doctor identifier; based on the target mapping relationship, obtain a doctor identifier corresponding to the user identifier of the electrocardiographic medical data; and send the electrocardiographic medical data to a terminal corresponding to the doctor identifier.

[0170] In one of the embodiments, the data receiving module 1001 is also used to obtain a static mapping relationship between a user identifier and a doctor identifier; when an online notification or offline notification of a terminal corresponding to the doctor identifier is monitored, the static mapping relationship is dynamically updated to obtain a target mapping relationship.

[0171] In one of the embodiments, the routing module 1003 is further used to obtain pre-configured routing information, the routing information including the routing address of the second platform; and send the ECG medical data to the second platform corresponding to the routing address.

[0172] In one embodiment, the routing module 1003 is also used to receive a routing information configuration request, which carries a routing address and a data transmission direction, where the data transmission direction is used to characterize the direction of data sending and / or data receiving between a first platform and a second platform corresponding to the routing address; store the routing address, and set the data transmission direction corresponding to the routing address.

[0173] In one of the embodiments, the routing module 1003 is also used to send the ECG medical data of a single user to the second platform corresponding to the routing address when the ECG medical data is the medical data of a single user; when the ECG medical data is the medical data of batch users, receive the ECG medical data acquisition request of the second platform, and determine whether the second platform is online based on the ECG medical data acquisition request, and when the second platform is online, send the ECG medical data of batch users to the second platform.

[0174] In one of the embodiments, the routing module 1003 is also used to receive routing information configuration instructions of the second platform corresponding to the first platform, and configure the routing information of the second platform corresponding to the first platform based on the configuration instructions; send the routing information to the second platform, and the configuration information is used to instruct the second platform to update the local routing information, and after the update is completed, feedback the update completion information to the first platform.

[0175] In one of the embodiments, the routing module 1003 is also used to receive ECG medical data sent by the second platform, the ECG medical data carrying a routing address; when the routing address is stored in the local routing address whitelist, the ECG medical data is stored; when the routing address is stored in the local routing address blacklist, the ECG medical data is shielded; when the routing address is not stored in the local routing address whitelist and the local routing address blacklist, and the number of times the second platform corresponding to the routing address continues to send ECG medical data is greater than a preset value, the routing address corresponding to the second platform is stored in the local routing address blacklist.

[0176] In one of the embodiments, the above-mentioned device also includes: a container management module, which is used to dynamically manage the resources of the first platform based on K8S technology.

[0177] Each module in the above-mentioned electrocardiogram medical data transmission device can be implemented in whole or in part by software, hardware or a combination thereof. Each of the above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory in the computer device in the form of software, so that the processor can call and execute the corresponding operations of each of the above modules.

[0178] In an exemplary embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as shown in FIG. Fig.11 As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store electrocardiographic medical data. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a method for transmitting electrocardiographic medical data is implemented.

[0179] Those skilled in the art will understand that Fig.11 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0180] In one embodiment, a computer device is further provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above method embodiments when executing the computer program.

[0181] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0182] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0183] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0184] Those of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited thereto. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited thereto.

[0185] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0186] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A method for transmitting electrocardiographic medical data, It is characterized in that The method comprises: Receiving device online data and a first random code sent by an electrocardiogram device, wherein the device online data includes a user identifier, and the first random code is generated by the electrocardiogram device based on a key and a random number sent by a first platform; When it is determined based on the user identifier that the electrocardiogram device has been registered on the first platform, a key and a random number corresponding to the device identifier are locally acquired, and a second random code is generated based on the key and the random number; When the first random code matches the second random code, feedback is given to the electrocardiograph device, indicating that the identity authentication is passed and the identity authentication response data corresponding to the online data of the device is passed; Receiving electrocardiographic medical data sent by the electrocardiographic device that has passed identity authentication, and verifying whether the format of the electrocardiographic medical data complies with the custom communication protocol; When the format of the electrocardiographic medical data conforms to the custom communication protocol, the electrocardiographic medical data is processed.

2. The method according to claim 1, It is characterized in that Before receiving the device online data and the first random code sent by the electrocardiogram device, the method includes: Receiving connection code acquisition data sent by the electrocardiograph device, wherein the connection code acquisition data includes a user identifier; When it is determined based on the user identifier that the electrocardiograph device has been registered on the first platform, obtaining a key and a random number corresponding to the user identifier, where the random number is generated in advance or in real time; Based on the key and the random number, connection code feedback data corresponding to the connection code acquisition data is generated, and the connection code feedback data is sent to the electrocardiograph device. The key and the random number in the connection code feedback data are used for identity verification of the electrocardiograph device.

3. The method according to claim 1, It is characterized in that The device online data also includes survival time; the method also includes: Saving the survival time, and generating a time threshold based on the survival time; When the heartbeat reporting data sent by the electrocardiograph device is not received within the time threshold, determining that the electrocardiograph device is offline; When the heartbeat reporting data sent by the electrocardiograph device is received within the time threshold, the heartbeat feedback data corresponding to the heartbeat reporting data is sent to the electrocardiograph device, and the heartbeat feedback data is used to instruct the electrocardiograph device to determine whether the first platform is abnormal. If the first platform is abnormal, the information that the first platform is abnormal is output.

4. The method according to claim 1, It is characterized in that After the electrocardiogram medical data is processed, the method further comprises: Receiving device offline data sent by the electrocardiograph device; The status of the electrocardiograph device is updated to offline based on the device offline data.

5. The method according to claim 1, It is characterized in that The ECG medical data includes at least one of patient alarm data, technical alarm data, device location data, device power data, and real-time ECG data.

6. The method according to any one of claims 1 to 5, It is characterized in that The data transmission between the ECG device and the first platform is generated based on a custom communication protocol, and the custom communication protocol is obtained by removing interaction rules in a general protocol that are irrelevant to the ECG medical data.

7. The method according to claim 1, It is characterized in that After receiving the electrocardiographic medical data sent by the electrocardiographic device that has passed the identity authentication, the method further includes: When the current data packet corresponding to the ECG medical data sent by the ECG device is received successfully, confirmation data of the successful reception of the current data packet is asynchronously sent to the ECG device, and the confirmation data is used to instruct the ECG device to cache the data packets without confirmation data, and before the ECG device sends the device offline data to the first platform, the cached data packets without the confirmation data are sent to the first platform.

8. The method according to claim 1, It is characterized in that The processing of the electrocardiographic medical data includes: Obtain a target mapping relationship between a user ID and a doctor ID; Based on the target mapping relationship, obtaining a doctor identifier corresponding to the user identifier of the electrocardiographic medical data; The electrocardiogram medical data is sent to a terminal corresponding to the doctor identification.

9. The method according to claim 8, It is characterized in that The step of obtaining a target mapping relationship between a user identifier and a doctor identifier includes: Obtain the static mapping relationship between user ID and doctor ID; When an online notification or offline notification of a terminal corresponding to the doctor identifier is monitored, the static mapping relationship is dynamically updated to obtain a target mapping relationship.

10. The method according to claim 1, It is characterized in that The processing of the electrocardiographic medical data includes: Acquire pre-configured routing information, the routing information including a routing address of the second platform; The electrocardiogram medical data is sent to a second platform corresponding to the routing address.

11. The method according to claim 10, It is characterized in that Before obtaining the pre-configured routing information, the method further includes: receiving a routing information configuration request, the routing information configuration request carrying a routing address and a data transmission direction, the data transmission direction being used to characterize a direction of data transmission and / or data reception between the first platform and a second platform corresponding to the routing address; The routing address is stored, and the data transmission direction corresponding to the routing address is set.

12. The method according to claim 10, It is characterized in that The sending the electrocardiogram medical data to the second platform corresponding to the routing address includes: When the electrocardiographic medical data is medical data of a single user, sending the electrocardiographic medical data of the single user to the second platform corresponding to the routing address; When the ECG medical data is medical data of batch users, a request for obtaining the ECG medical data from the second platform is received, and based on the request for obtaining the ECG medical data, whether the second platform is online is determined; when the second platform is online, the ECG medical data of the batch users is sent to the second platform.

13. The method according to claim 12, It is characterized in that Before receiving the electrocardiogram medical data acquisition request from the second platform, the method further includes: receiving a routing information configuration instruction of a second platform corresponding to the first platform, and configuring routing information of the second platform corresponding to the first platform based on the configuration instruction; The routing information is sent to the second platform, and the configuration information is used to instruct the second platform to update the local routing information, and after the update is completed, feedback the update completion information to the first platform.

14. The method according to claim 1, It is characterized in that The method further comprises: Receiving electrocardiographic medical data sent by the second platform, wherein the electrocardiographic medical data carries a routing address; When the routing address is stored in the local routing address whitelist, storing the electrocardiographic medical data; When the routing address is stored in a local routing address blacklist, shielding the electrocardiographic medical data; When the routing address is not stored in the local routing address whitelist and the local routing address blacklist, and the number of times the second platform corresponding to the routing address continues to send electrocardiographic medical data is greater than a preset value, the routing address corresponding to the second platform is stored in the local routing address blacklist.

15. The method according to claim 1, It is characterized in that The method further comprises: Dynamically manage the resources of the first platform based on K8S technology.

16. An electrocardiogram medical data transmission device, It is characterized in that The device comprises: A data receiving module, used for receiving device online data and a first random code sent by an ECG device, wherein the device online data includes a user identifier, and the first random code is generated by the ECG device based on a key and a random number sent by a first platform; and receiving ECG medical data sent by the ECG device after identity verification; The permission verification module is used to obtain the key and random number corresponding to the device identification when it is determined based on the user identification that the electrocardiograph device has been registered on the first platform, and generate a second random code based on the key and random number; when the first random code and the second random code match, feedback the response data of identity authentication corresponding to the device online data to the electrocardiograph device; and verify whether the format of the electrocardiograph medical data conforms to the custom communication protocol; The routing module is used to process the electrocardiographic medical data when the format of the electrocardiographic medical data conforms to the custom communication protocol.

17. A computer device comprising a memory and a processor, wherein the memory stores a computer program. It is characterized in that When the processor executes the computer program, the steps of the method according to any one of claims 1 to 15 are implemented.

18. A computer-readable storage medium having a computer program stored thereon, It is characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 15 are implemented.

19. A computer program product comprising a computer program, It is characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 15 are implemented.

Images