A defibrillator monitor data transmission method, system and storage medium

Abstract

This invention discloses a data transmission method, system, and storage medium for a defibrillator monitor, relating to the field of smart healthcare. The method includes: acquiring vital sign data; encapsulating the vital sign data in HL7 format to obtain first encapsulated data; encapsulating the first encapsulated data using the MQTT protocol to obtain second encapsulated data; and sending the second encapsulated data to an MQTT broker server, so that the MQTT broker server pushes the second encapsulated data of a corresponding topic to the subscriber based on the subscriber's subscription request, wherein the corresponding topic is automatically created by the MQTT broker server upon receiving the second encapsulated data. These methods ensure that data can be effectively pushed and managed according to the subscriber's needs, and by further encapsulating the data using the MQTT protocol, stability and security during data transmission are guaranteed, providing a secure and reliable data transmission foundation for building smart healthcare.

Description

Technical Field

[0001] This invention relates to the field of smart healthcare, and in particular to a data transmission method, system, and storage medium for a defibrillator monitor. Background Technology

[0002] In today's era of rapid development in medical technology, the rise of smart healthcare has provided unprecedented opportunities to improve the level of medical services. Through the integration and innovation of information technology, interconnectivity between medical devices has been achieved, injecting new digital and intelligent momentum into the healthcare industry. However, with the widespread application of medical devices, especially the prevalence of monitoring equipment, the stability of data transmission has become one of the main challenges facing smart healthcare.

[0003] Therefore, providing a stable data transmission method is an urgent problem to be solved in the field of smart healthcare. Summary of the Invention

[0004] Based on this, embodiments of the present invention provide a defibrillator monitoring data transmission method, system, and storage medium to solve the problem of unstable data transmission between traditional medical devices.

[0005] A data transmission method for a defibrillator monitor, applied to a defibrillator monitor, the method comprising:

[0006] Obtain vital signs data;

[0007] The vital signs data are encapsulated in HL7 format to obtain the first encapsulated data;

[0008] The first encapsulated data is encapsulated using the MQTT protocol to obtain the second encapsulated data;

[0009] The second encapsulated data is sent to the MQTT broker server, so that the MQTT broker server pushes the second encapsulated data of the corresponding topic to the subscriber based on the subscriber's subscription request, wherein the corresponding topic is automatically created by the MQTT broker server when it receives the second encapsulated data.

[0010] In one embodiment, before sending the second encapsulated data to the MQTT broker server, the following steps are included:

[0011] Generate a request packet based on the port and IP / MAC address information configured by the user;

[0012] The request packet is sent to the MQTT broker server, and after receiving the confirmation instruction returned by the MQTT broker server, the second encapsulated data is sent to the MQTT broker server.

[0013] In one embodiment, after sending the second encapsulated data to the MQTT broker server, the process includes:

[0014] Receive heartbeat packets periodically sent by the MQTT broker server, and determine whether to maintain a connection with the MQTT broker server based on the heartbeat packets;

[0015] When the connection to the MQTT broker server is lost, a reconnection is performed.

[0016] In one embodiment, the vital signs data includes physiological parameters, and the process of acquiring the vital signs data includes:

[0017] Determine whether physiological parameters exceed preset thresholds;

[0018] If the physiological parameters exceed a preset threshold, a warning message will be pushed to the subscribers through the MQTT broker server.

[0019] A defibrillator monitoring data transmission method, applied to an MQTT broker server, the method further includes:

[0020] The system receives second encapsulated data sent by the defibrillator and stores the second encapsulated data in a message queue. The second encapsulated data is obtained by encapsulating the first encapsulated data using the MQTT protocol, and the first encapsulated data is obtained by encapsulating the vital signs data acquired by the defibrillator using the HL7 format.

[0021] The second encapsulated data of the corresponding topic is pushed to the subscriber based on the subscriber's subscription request, wherein the corresponding topic is automatically created after receiving the second encapsulated data sent by the defibrillator monitor.

[0022] In one embodiment, pushing the second encapsulated data corresponding to the topic to the subscriber based on the subscriber's subscription request includes:

[0023] Receive a subscription request sent by the subscriber, wherein the subscription request includes a subscription topic;

[0024] Based on the correspondence between the subscribed topic and the corresponding topic, the second encapsulated data is pushed to the subscriber through the message queue.

[0025] A defibrillator monitoring data transmission system includes a defibrillator monitoring device and an MQTT proxy server;

[0026] The defibrillator monitor is used to acquire vital sign data; the vital sign data is encapsulated in HL7 format to obtain first encapsulated data; the first encapsulated data is encapsulated using the MQTT protocol to obtain second encapsulated data;

[0027] The defibrillator monitor is also used to send the second encapsulated data to an MQTT broker server. The MQTT broker server pushes the second encapsulated data of the corresponding topic to the subscriber based on the subscriber's subscription request. The corresponding topic is automatically created by the MQTT broker server when it receives the second encapsulated data.

[0028] In one embodiment, it includes:

[0029] The MQTT broker server is used to receive the second encapsulated data sent by the defibrillator and store the second encapsulated data in the message queue;

[0030] The MQTT broker server is also used to receive subscription requests sent by the subscriber, wherein the subscription request includes a subscription topic, and pushes the second encapsulated data to the subscriber through the message queue according to the correspondence between the subscription topic and the corresponding topic.

[0031] In one embodiment, it includes:

[0032] The defibrillator monitor is used to generate request packets based on the user-configured port and IP / MAC address information;

[0033] The defibrillator monitor is also used to send the request packet to the MQTT broker server, and after receiving the confirmation instruction returned by the MQTT broker server, send the second encapsulated data to the MQTT broker server.

[0034] A computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described defibrillator monitoring data transmission method.

[0035] The aforementioned defibrillator monitor data transmission method, system, computer equipment, and storage medium acquire vital sign data and encapsulate it into HL7 format first encapsulated data. This second encapsulated data is then further encapsulated using the MQTT protocol to obtain second encapsulated data. Subsequently, the second encapsulated data is sent to an MQTT broker server. The MQTT broker server then pushes the corresponding second encapsulated data to subscribers based on their subscription requests. This method ensures that data is effectively pushed and managed according to subscribers' needs. Furthermore, the use of the MQTT protocol for further data encapsulation guarantees stability and security during data transmission, providing a secure and reliable data transmission foundation for building smart healthcare. Attached Figure Description

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

[0037] Figure 1 This is a flowchart of a defibrillator monitoring data transmission method according to an embodiment of the present invention;

[0038] Figure 2 This is another flowchart of a defibrillator monitoring data transmission method in one embodiment of the present invention;

[0039] Figure 3 This is another flowchart of a defibrillator monitoring data transmission method in one embodiment of the present invention;

[0040] Figure 4 This is another flowchart of a defibrillator monitoring data transmission method in one embodiment of the present invention;

[0041] Figure 5 This is a flowchart of a defibrillator monitoring data transmission system according to an embodiment of the present invention. Detailed Implementation

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

[0043] In one embodiment, a defibrillator monitor data transmission system is provided, including a defibrillator monitor and an MQTT proxy server;

[0044] The system acquires vital sign data from a defibrillator monitor, including heart rate, blood pressure, and oxygen saturation. This data is encapsulated using the monitor's built-in formatting module to obtain first-encapsulated data. Then, the monitor's built-in 4G module further encapsulates this first-encapsulated data via the MQTT protocol to obtain second-encapsulated data. The defibrillator then sends this second-encapsulated data to an MQTT broker server. Upon receiving the second-encapsulated data, the MQTT broker server automatically generates a corresponding topic, such as the patient's ID. When a subscriber (e.g., medical personnel) sends a subscription request via a client, the MQTT broker server pushes the corresponding second-encapsulated data to the subscriber. This enables real-time transmission and monitoring of vital sign data. Furthermore, medical personnel can subscribe to specific topics related to a particular patient's monitoring data (e.g., heart rate) to obtain real-time monitoring data, leading to more timely and accurate medical decisions. This facilitates remote patient monitoring and improves the efficiency and quality of medical services.

[0045] In one embodiment, the MQTT broker server receives the second encapsulated data sent by the defibrillator and stores the second encapsulated data in a message queue. When the MQTT broker server receives a subscription request from a subscriber, it pushes the second encapsulated data to the subscriber through the message queue according to the correspondence between the subscription topic and the corresponding topic. The subscription request includes a subscription topic. By storing the vital signs data monitored by the defibrillator when the MQTT broker server receives the data, it ensures that subscribers who subsequently subscribe to the corresponding topic can receive the data monitored by the defibrillator. This prevents the MQTT broker server from deleting the data directly when it detects that there is no subscriber.

[0046] In this embodiment, the MQTT broker server acts as the central data processing center, receiving and storing the second-encapsulated data sent by the defibrillator monitor. Through the ingenious application of message queues, it achieves ordered data storage and flexible data push. On one hand, the MQTT broker server handles subscription requests from subscribers, including subscription topics. By understanding the relationship between subscription topics and corresponding topics, it retrieves the second-encapsulated data for the corresponding topic from the message queue and dynamically pushes it to the subscribers, ensuring data real-time performance and timely response to subscribers' needs. On the other hand, even if no subscribers exist when data is sent, the MQTT broker server can store the data in the message queue, providing an opportunity for subscribers who may initiate subscription requests at any time, thus ensuring data integrity and availability.

[0047] In one embodiment, the defibrillator monitor is further configured to generate a request packet based on the user-configured port and IP / MAC address information, send the request packet to the MQTT proxy server, and, upon receiving a confirmation instruction from the MQTT proxy server, send the second encapsulated data to the MQTT proxy server. This method ensures secure access for the new defibrillator monitor while also guaranteeing the stability and reliability of data transmission.

[0048] In one embodiment, the defibrillator monitor is also used to receive heartbeat packets periodically sent by the MQTT proxy server and determine whether to maintain a connection with the MQTT proxy server based on the heartbeat packets; when the connection with the MQTT proxy server is lost, the defibrillator monitor is controlled to reconnect. This method ensures communication reliability; even in situations of network instability or disconnection, the defibrillator monitor can proactively attempt to re-establish a connection, ensuring timely data transmission. This self-monitoring and automatic reconnection mechanism effectively improves the stability and availability of data transmission.

[0049] In one embodiment, the defibrillator monitor is also used to determine whether physiological parameter data in the monitored vital signs data exceeds a preset threshold. When the determined physiological parameter value exceeds the preset threshold, the defibrillator monitor is controlled to issue an alarm and generate corresponding alarm information. Simultaneously, the alarm information is pushed to subscribers via an MQTT broker server for early warning. Throughout this process, the defibrillator monitor is not only a data transmission tool but also an intelligent and proactive device. By monitoring and analyzing the patient's physiological parameters in real time, it can take timely measures, issue alarms, and push relevant information when abnormalities are detected, providing crucial decision support for medical personnel and effectively enhancing the value and practicality of the defibrillator monitor.

[0050] In this embodiment, the defibrillator monitoring data transmission system described above is merely an illustrative example and is not intended to limit the scope of the invention.

[0051] In one embodiment, such as Figure 1 and Figure 2 As shown, a data transmission method for a defibrillator monitor is provided, which is applied to a defibrillator monitor and includes the following steps:

[0052] S10. Obtain vital signs data.

[0053] In one embodiment, vital sign data is acquired by using a defibrillator to obtain the patient's physical condition information, including waveform data and physiological parameter data, such as heart rate, respiratory rate, body temperature, blood pressure, and other vital sign parameters, as well as waveform data such as electrocardiograms. This process is to monitor the patient's physical condition in real time, providing medical personnel with timely and objective vital sign data, thereby better understanding the patient's physiological state, developing treatment plans, and preventing diseases.

[0054] By acquiring vital sign data, medical staff can achieve comprehensive and precise monitoring of patients. For example, electrocardiogram (ECG) monitoring can help doctors detect signs of heart disease, blood pressure monitoring helps control hypertension, body temperature monitoring can track fever symptoms, and respiratory rate monitoring can be used to assess respiratory function. The collection and analysis of this data helps to detect changes in a patient's condition early, allowing for timely intervention, reducing medical risks, and improving treatment outcomes.

[0055] It should be noted that the above is just an example, and the specific invention is not limited.

[0056] S20. The vital signs data are encapsulated in HL7 format to obtain the first encapsulated data.

[0057] In one embodiment, encapsulating vital sign data in HL7 format refers to using the Health Level Seven (HL7) standard to structurally process and encode patient vital sign data acquired from defibrillator monitors, enabling better transmission and exchange within medical information systems. HL7 is an international medical information exchange standard that defines the organization, transmission protocols, and interaction specifications of data in smart healthcare systems. Encapsulating vital sign data according to the HL7 standard yields the first encapsulated data. The encapsulation process may involve encoding and organizing the values, units, timestamps, and other information of various physiological parameters according to HL7 specifications to ensure data consistency and readability. Through this standardized encapsulation, vital sign data can be stored and transmitted in a structured form, improving the interoperability of smart healthcare systems and better supporting the management, analysis, and application of medical data. This also lays the foundation for subsequent data processing and transmission, providing technical support for building more robust and scalable smart healthcare systems.

[0058] In addition, the application of the HL7 format helps to protect the privacy and security of medical information. The HL7 standard ensures the secure transmission and storage of patient vital signs data through standardized authentication, access control and encryption mechanisms.

[0059] For example, the encapsulated vital signs data includes not only the patient's physiological parameters but also their identity information and medical records. This process ensures data integrity and reliability while facilitating subsequent data processing and analysis. The use of the HL7 format enables efficient exchange of this data between different medical devices and information systems.

[0060] The packaged HL7 data can be:

[0061] PID|1|123456|7890123|Doe^John||19700101|M|||street^city

[0062] ^12345^CN||(555)555-1234|(555)555-1235|||||0||0|||000000000

[0063] OBX|1|NM|HR^Heart Rate|1|120|bpm|60-100||R|||20211226095000

[0064] This includes the patient's identity information (PID segment) and heart rate data (OBX segment).

[0065] For example, PID: Segment identifier, representing the patient identity information segment. 1: Sequence number, indicating the first PID segment in the message; 123456: Patient ID; 7890123: Appointment number; Doe^John: Patient name, in the format of last name^first name; 19700101: Date of birth; M: Gender, here male; Street^City^12345^CN: Address information, including street, city, postal code and country; (555)

[0066] 555-1234: Contact number; (555)555-1235: Backup contact number.

[0067] OBX: Segment identifier, representing the observation segment; 1: Sequence number, indicating the first OBX segment in the message; NM: Data type, represented as a number; HR^Heart Rate: Name of the observation, here it is heart rate; 1: Identifier of the observation; 120: Observed heart rate value; bpm: Unit, indicating that the unit of measurement for heart rate is pulses per minute; 60-100: Normal range; R: Result status, indicating normal; 20231226095000: Observation timestamp, here it is December 26, 2023, 09:50:00.

[0068] The above format ensures data consistency and can be accurately interpreted in other systems or terminal devices. It should be noted that the above is merely an example, and the specific implementation of this invention is not limited.

[0069] S30. Encapsulate the first encapsulated data using the MQTT protocol to obtain the second encapsulated data.

[0070] In one embodiment, after obtaining the first encapsulated data, the MQTT (Message Queuing Telemetry Transport) protocol is used to generate the second encapsulated data. The characteristics of the MQTT protocol make it a lightweight and efficient messaging protocol suitable for scenarios such as IoT devices. In this process, the first encapsulated data is converted into a message format conforming to the MQTT protocol specification. The MQTT encapsulation may include metadata such as the message subject and quality services, as well as the actual vital sign data. Thus, the second encapsulated data can be easily transmitted over the network via the MQTT protocol. By encapsulating the vital sign data using HL7 format and the MQTT protocol, the resulting second encapsulated data possesses characteristics suitable for complex medical information systems and network environments, achieving efficient data transmission and decoupling. This encapsulation method helps ensure stable data transmission to the MQTT broker server, facilitating subsequent data processing and subscription services. Simultaneously, the MQTT protocol supports TLS / SSL encryption, ensuring the security of data transmission.

[0071] S40. The second encapsulated data is sent to the MQTT broker server, so that the MQTT broker server pushes the second encapsulated data of the corresponding topic to the subscriber based on the subscriber's subscription request, wherein the corresponding topic is automatically created by the MQTT broker server when it receives the second encapsulated data.

[0072] In one embodiment, the defibrillator monitor then sends the second encapsulated data to an MQTT broker server, which acts as an intermediary, responsible for receiving, processing, and distributing all vital sign data from the defibrillator monitor. Upon receiving the second encapsulated data, the MQTT broker server dynamically creates a corresponding topic, typically named after the patient ID and vital sign type. For example, the topic might be / patient / 123456 / vital_signs, where "123456" represents the patient ID.

[0073] "vital_signs" represents vital sign data. Subscribers express their subscription to specific vital sign data by sending subscription requests to the MQTT broker server. These subscription requests include subscription topic information, ensuring that subscribers only receive the data they have subscribed to. Once the MQTT broker server receives the subscription request, it pushes the second encapsulated data for the corresponding topic to the subscriber. This method achieves efficient and real-time transmission of vital sign data, ensuring that only subscribers receive the relevant information, providing a flexible and reliable data interaction mechanism for the construction of smart healthcare.

[0074] In summary, this invention acquires vital sign data and encapsulates it into first-encapsulated data in HL7 format. Then, it encapsulates the data again using the MQTT protocol to obtain second-encapsulated data. This second-encapsulated data is then sent to an MQTT broker server, which pushes the corresponding second-encapsulated data to subscribers based on their subscription requests. These methods ensure that data is effectively pushed and managed according to subscribers' needs. Furthermore, the use of the MQTT protocol for further encapsulation guarantees the stability and security of data transmission, providing a secure and reliable data transmission foundation for building smart healthcare.

[0075] For example, taking patient John Doe as an example, the patient's vital signs data, including heart rate, blood pressure, and blood oxygen saturation, are obtained through the patient ID "123456". First, this obtained vital signs data is encapsulated in HL7 format to form the first layer of encapsulated data, ensuring data standardization and normalization. For example, heart rate is encapsulated as "OBX|1|NM|HR^HeartRate|1|120|bpm|60-100||R|||20231226095000". Next, to transmit this vital signs data more efficiently, a second layer of encapsulation is performed using the MQTT protocol, and it is sent to the MQTT broker server. Through the MQTT broker server's topic publish / subscribe mechanism, the topic " / patient / 123456 / vital_signs" is dynamically created, combining the patient ID and vital sign type. For example, John Doe's heart rate, blood pressure, and blood oxygen saturation data are encapsulated as follows using an HL7 formatted MQTT message:

[0076] Topic: / patient / 123456 / vital_signs

[0077] Message:

[0078] {

[0079] "patient_id":"123456",

[0080] "heart_rate":120,

[0081] "blood pressure":"120 / 80",

[0082] "oxygen_saturation":98,

[0083] "timestamp":"2023-12-26 09:50:00"

[0084] }

[0085] At this point, after receiving the data, the MQTT broker server dynamically creates a corresponding subtopic based on the subscriber's subscription request, such as " / patient / 123456 / vital_signs / heart_rate". If Doctor A is interested in heart rate, they send a subscription request, and the MQTT broker server will push the heart rate data to Doctor A. This achieves precise data delivery and subscription mechanisms, greatly improving the real-time performance and effectiveness of the data, allowing medical staff to obtain patients' vital sign information more effectively.

[0086] In one embodiment, prior to step S10, i.e., before sending the second encapsulated data to the MQTT broker server, the following steps are included:

[0087] S50. Generate a request packet based on the port and IP / MAC address information configured by the user.

[0088] In one embodiment, a request packet is generated based on the user-configured port and IP / MAC address information. This generated request packet is used for communication between the defibrillator monitor and the MQTT broker server, enabling the monitor to function properly and send data. The request packet will contain the monitor's IP / MAC address information and the required port information to ensure connection and communication between the defibrillator monitor and the MQTT broker server.

[0089] For example, suppose a user is using a defibrillator monitor and wants to send the monitored vital signs data to an MQTT proxy server for further processing. The user has configured the MQTT proxy server's IP address as "192.168.1.100", port number as "8080", and the device's MAC address as "00:1A:2B:3C:4D:5E" through the monitor's settings interface. The defibrillator monitor will then integrate this configuration information into a single request packet. The structure of this request packet might be as follows:

[0090] {

[0091] "source_device":"Defibrillator-123",

[0092] "target_server":{

[0093] IP address: 192.168.1.100

[0094] "port":8080

[0095] },

[0096] "device_mac":"00:1A:2B:3C:4D:5E",

[0097] "request_type":"connect"

[0098] }

[0099] It should be noted that the above example is only an illustrative example, and the specific configuration information is not limited in this invention.

[0100] S60. Send the request packet to the MQTT broker server, and after receiving the confirmation instruction returned by the MQTT broker server, send the second encapsulated data to the MQTT broker server.

[0101] In one embodiment, the defibrillator monitor sends a generated request packet to an MQTT proxy server. The MQTT proxy server listens for request packets from the defibrillator monitor on a designated port. When the MQTT proxy server receives a request packet from the defibrillator monitor, it verifies whether the information in the request packet matches the configuration information of the MQTT proxy server. If the MQTT proxy server confirms the legitimacy of the request packet sent by the defibrillator monitor (i.e., the MAC address matches the configured defibrillator monitor and the port information is correct), the MQTT proxy server sends an confirmation command to the defibrillator monitor. This confirmation command serves as an identifier of a successful connection, informing the defibrillator monitor that it has successfully joined the MQTT proxy server. Upon receiving the confirmation command, a secure connection is established between the defibrillator monitor and the MQTT proxy server, enabling bidirectional data transmission. The defibrillator monitor can then send the second encapsulated data to the MQTT proxy server. This verification process not only ensures the secure access of the new defibrillator monitor but also ensures the stability and reliability of data transmission throughout the entire medical system, providing a solid foundation for the security and stability of data transmission.

[0102] In one embodiment, after step S40, i.e. after sending the second encapsulated data to the MQTT broker server, the following steps are included:

[0103] S70. Receive heartbeat packets periodically sent by the MQTT broker server, and determine whether to maintain a connection with the MQTT broker server based on the heartbeat packets.

[0104] S80. When the connection with the MQTT broker server is lost, reconnect.

[0105] In one embodiment, after a connection is established between the defibrillator and the MQTT broker server, the defibrillator periodically receives heartbeat packets from the MQTT broker server to maintain communication stability. This heartbeat packet is a timed signal used to indicate that the connection is functioning correctly.

[0106] By periodically receiving heartbeat packets, the defibrillator monitor can determine whether the connection with the MQTT broker server is maintained normally. If no heartbeat packet is received within a predetermined time, the defibrillator monitor will determine that the connection with the MQTT broker server has been lost. In this case, the defibrillator monitor will actively initiate a reconnection process to ensure that communication with the MQTT broker server can be restored in a timely manner. This heartbeat packet mechanism helps to detect the real-time status of the connection, promptly identify connection anomalies, and take appropriate reconnection measures. By continuously maintaining a valid connection, the defibrillator monitor can ensure the real-time transmission of vital signs data, improve the reliability and stability of the entire defibrillator monitor data transmission system, ensure that remedial measures can be taken in a timely manner in the event of any connection anomaly, and guarantee continuous communication between the defibrillator monitor and the MQTT broker server.

[0107] In one embodiment, that is, after step S10, i.e., when the vital signs data includes physiological parameters, the process of acquiring the vital signs data includes the following:

[0108] S90. Determine whether the physiological parameters exceed the preset threshold.

[0109] S100. If the physiological parameter exceeds the preset threshold, the warning information will be pushed to the subscriber through the MQTT proxy server.

[0110] In one embodiment, the defibrillator monitor can not only monitor and forward vital sign data, but also perform real-time analysis and judgment on physiological parameters (such as heart rate, blood pressure, oxygen saturation, etc.) within the monitored vital sign data. When the monitored physiological parameters exceed a preset threshold range, i.e., reach or exceed a pre-set danger value, the patient is determined to have an abnormal condition. Once a physiological parameter is detected to exceed the preset threshold, the defibrillator monitor will trigger an early warning mechanism. At this time, the defibrillator monitor data transmission system will also generate corresponding early warning information, including patient ID, abnormal physiological parameters, specific values, and early warning time. This early warning information will be pushed through an MQTT broker server to achieve real-time message delivery. Leveraging the characteristics of the MQTT protocol, the defibrillator monitor data transmission system pushes early warning information to subscribers who have pre-subscribed to the relevant topic; these subscribers may include doctors, nurses, or other medical personnel. The pushed early warning information can be quickly conveyed to relevant personnel, enabling them to respond rapidly. The above methods not only provide real-time monitoring of the patient's condition, but also provide timely warnings when the patient's physiological parameters are abnormal, providing strong support for medical staff so that they can take necessary rescue measures in a timely manner. This physiological parameter monitoring and early warning mechanism effectively improves the sensitivity to the patient's condition and ensures the patient's safety.

[0111] For example, taking heart rate as an example, suppose the normal heart rate range is 60 to 100 beats per minute. When a patient's heart rate reaches 110 beats per minute, the defibrillator monitor will detect this abnormality and trigger an alert, sending a notification to subscribers via the MQTT broker server so that timely action can be taken.

[0112] It should be noted that early warning information can also be sent via SMS, email, system pop-ups, and other means to ensure that medical staff or nurses can be informed of changes in the patient's condition as soon as possible. Furthermore, the defibrillator monitor can also provide subscribers with detailed patient physiological parameter trend charts, historical records, and other auxiliary information through an MQTT broker server to help medical staff gain a more comprehensive understanding of the patient's condition.

[0113] In one embodiment, such as Figure 3 As shown, a data transmission method for a defibrillator monitor is provided, applied to an MQTT broker server, including the following steps:

[0114] S110. Receive the second encapsulated data sent by the defibrillator and store the second encapsulated data in a message queue. The second encapsulated data is obtained by encapsulating the first encapsulated data using the MQTT protocol, and the first encapsulated data is obtained by encapsulating the vital signs data acquired by the defibrillator using the HL7 format.

[0115] S120. Based on the subscriber's subscription request, push the second encapsulated data of the corresponding topic to the subscriber, wherein the corresponding topic is automatically created after receiving the second encapsulated data sent by the defibrillator monitor.

[0116] In one embodiment, after the MQTT broker receives the second encapsulated data sent by the defibrillator, it stores it in an orderly manner in a message queue. The process of storing the second encapsulated data in the message queue is essentially a middleware caching mechanism. The message queue queues the data, storing it in order of priority, which helps handle high-concurrency data transmission scenarios. Even when the MQTT broker is under heavy load, the message queue can effectively alleviate pressure and ensure data orderliness and stability. Through the message queue, the MQTT broker achieves asynchronous data transmission, real-time storage, and sorting. This not only helps improve the stability and reliability of data transmission but also better copes with network fluctuations or surges in MQTT broker load. Even if the MQTT broker experiences a brief failure at some point, the data already sent to the message queue can still be retained, waiting for the MQTT broker to recover before processing, ensuring data reliability.

[0117] In summary, when the MQTT broker receives the second encapsulated data sent by the defibrillator, it stores the second encapsulated data in the message queue. The second encapsulated data is obtained by encapsulating the first encapsulated data using the MQTT protocol. The first encapsulated data is obtained by encapsulating the vital signs data acquired by the defibrillator using the HL7 format. Then, based on the subscriber's subscription request, the MQTT broker pushes the second encapsulated data to the subscriber with the corresponding topic. The corresponding topic is automatically created by the MQTT broker after receiving the second encapsulated data from the defibrillator. This method ensures that data can be effectively pushed and managed according to the subscriber's needs, and by further encapsulating the data using the MQTT protocol, it guarantees the stability and security of data transmission, providing a secure and reliable data transmission foundation for building smart healthcare.

[0118] In one embodiment, such as Figure 4 As shown, in step S120, which involves pushing the second encapsulated data of the corresponding topic to the subscriber based on the subscriber's subscription request, the steps include:

[0119] S121. Receive a subscription request sent by the subscriber, wherein the subscription request includes a subscription topic.

[0120] In one embodiment, subscribers establish a valid communication connection with the MQTT broker server by sending a subscription request, ensuring the smooth transmission of medical data and allowing medical personnel to obtain patients' vital signs data in an efficient and timely manner. The subscription request includes a subscription topic, which is typically related to the patient ID or other specific information. Through a specific subscription topic, subscribers can instantly obtain the information they want. They can also customize the information they need without receiving large amounts of irrelevant data. This refined information delivery mechanism allows medical personnel to focus more intently on specific patients or monitoring programs, improving the efficiency and accuracy of information processing.

[0121] It should be noted that the subscription request is not limited to the transmission of patient vital sign data, but can also include system notifications, alarm information, etc. For example, a subscriber may want to receive all alarm information related to a specific patient so that they can respond quickly in case of an emergency, providing a more flexible and personalized service for medical monitoring.

[0122] S122. Based on the correspondence between the subscribed topic and the corresponding topic, the second encapsulated data is pushed to the subscriber through the message queue.

[0123] In this embodiment, the MQTT broker server establishes a mapping relationship between subscription topics and corresponding topics based on the medical record number and vital sign parameters monitored by the defibrillator monitor. This mapping relationship can be a key table recording the topics corresponding to each patient and each vital sign parameter. For example, if a patient with medical record number "P001" is subscribed to both heart rate and blood pressure parameters, the MQTT broker server will create two topics for this patient: "P001_HeartRate" and "P001_BloodPressure". After collecting the patient's vital sign data, the defibrillator monitor encapsulates the data into MQTT messages and sends them to the MQTT broker server. Upon receiving the data, the MQTT broker server searches for the corresponding subscriber based on the data's topic. Through the previously established mapping relationship, the MQTT broker server knows that the "P001_HeartRate" topic corresponds to medical staff A, and the "P001_BloodPressure" topic corresponds to medical staff B. After successfully locating the corresponding subscriber, the MQTT broker server pushes the data to the corresponding subscriber. Medical staff A will receive patient P001's heart rate data, while medical staff B will receive the corresponding blood pressure data. This push notification process associates the subscribed topic with the corresponding topic, ensuring that vital sign data is distributed to the designated medical staff on demand.

[0124] It should be noted that the above is just an example and the specific invention is not limited thereto.

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

[0126] In one embodiment, this application also provides a defibrillator monitor data transmission system 1000, such as... Figure 5 As shown, the defibrillator monitoring data transmission system 1000 may specifically include: a defibrillator monitoring system 1001 and an MQTT proxy server 1002.

[0127] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When executed by a processor, the computer program implements the defibrillator monitor data transmission method described in the above embodiment, such as steps S10-S130, which will not be repeated here to avoid repetition. The computer-readable storage medium can be non-volatile or volatile.

[0128] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. This computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and RAMbus dynamic RAM (RDRAM), etc.

[0129] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is used as an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above.

[0130] The above-described embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be included within the protection scope of the present invention.

Claims

1. A data transmission method for a defibrillator monitor, characterized in that, Applied to a defibrillator monitor, the method includes: Obtain vital signs data; The vital signs data are encapsulated in HL7 format to obtain the first encapsulated data; The first encapsulated data is encapsulated using the MQTT protocol to obtain the second encapsulated data; The second encapsulated data is sent to the MQTT broker server, so that the MQTT broker server pushes the second encapsulated data of the corresponding topic to the subscriber based on the subscriber's subscription request, wherein the corresponding topic is automatically created by the MQTT broker server when it receives the second encapsulated data.

2. The defibrillator data transmission method as described in claim 1, characterized in that, Before sending the second encapsulated data to the MQTT broker server, the following steps are included: Generate a request packet based on the port and IP / MAC address information configured by the user; The request packet is sent to the MQTT broker server, and after receiving the confirmation instruction returned by the MQTT broker server, the second encapsulated data is sent to the MQTT broker server.

3. The defibrillator monitoring data transmission method as described in claim 1, characterized in that, After sending the second encapsulated data to the MQTT broker server, the process includes: Receive heartbeat packets periodically sent by the MQTT broker server, and determine whether to maintain a connection with the MQTT broker server based on the heartbeat packets; When the connection to the MQTT broker server is lost, a reconnection is performed.

4. The defibrillator monitoring data transmission method as described in claim 1, characterized in that, The vital signs data include physiological parameters, and the acquisition of vital signs data includes: Determine whether physiological parameters exceed preset thresholds; If the physiological parameters exceed a preset threshold, a warning message will be pushed to the subscribers through the MQTT broker server.

5. A data transmission method for a defibrillator monitor, characterized in that, Applied to an MQTT broker server, the method includes: The system receives second encapsulated data sent by the defibrillator and stores the second encapsulated data in a message queue. The second encapsulated data is obtained by encapsulating the first encapsulated data using the MQTT protocol, and the first encapsulated data is obtained by encapsulating the vital signs data acquired by the defibrillator using the HL7 format. The second encapsulated data of the corresponding topic is pushed to the subscriber based on the subscriber's subscription request, wherein the corresponding topic is automatically created after receiving the second encapsulated data sent by the defibrillator monitor.

6. The defibrillator monitoring data transmission method as described in claim 5, characterized in that, The step of pushing the second encapsulated data of the corresponding topic to the subscriber based on the subscriber's subscription request includes: Receive a subscription request sent by the subscriber, wherein the subscription request includes a subscription topic; Based on the correspondence between the subscribed topic and the corresponding topic, the second encapsulated data is pushed to the subscriber through the message queue.

7. A defibrillator monitoring data transmission system, characterized in that, This includes defibrillator monitors and MQTT broker servers; The defibrillator monitor is used to acquire vital sign data; the vital sign data is encapsulated in HL7 format to obtain first encapsulated data; the first encapsulated data is encapsulated using the MQTT protocol to obtain second encapsulated data; The defibrillator monitor is also used to send the second encapsulated data to an MQTT broker server. The MQTT broker server pushes the second encapsulated data of the corresponding topic to the subscriber based on the subscriber's subscription request. The corresponding topic is automatically created by the MQTT broker server when it receives the second encapsulated data.

8. The defibrillator monitoring data transmission system as described in claim 7, characterized in that, include: The MQTT broker server is used to receive the second encapsulated data sent by the defibrillator and store the second encapsulated data in the message queue; The MQTT broker server is also used to receive subscription requests sent by the subscriber, wherein the subscription request includes a subscription topic, and pushes the second encapsulated data to the subscriber through the message queue according to the correspondence between the subscription topic and the corresponding topic.

9. The defibrillator monitoring data transmission system as described in claim 8, characterized in that, include: The defibrillator monitor is used to generate request packets based on the user-configured port and IP / MAC address information; The defibrillator monitor is also used to send the request packet to the MQTT broker server, and after receiving the confirmation instruction returned by the MQTT broker server, send the second encapsulated data to the MQTT broker server.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements the defibrillator data transmission method as described in any one of claims 1 to 6.

Images