Intelligent information management method and device for implantable left ventricular assist device

Abstract

A communication module is disclosed. The communication module is connected to a patient controller of an implantable left ventricular assist device and a cloud device. The implantable left ventricular assist device further includes a blood pump connected to the patient controller. The communication module receives the current operating data of the blood pump transmitted by the patient controller. The communication module further periodically publishes the current operating data to the cloud device. An implantable left ventricular assist system is also disclosed. The system includes an implantable left ventricular assist device, a cloud device, a mobile device, and the communication module. An intelligent information management method for the implantable left ventricular assist device applied to the communication module is also disclosed.

Description

[Technical Field]

[0001] (CROSS-REFERENCE TO RELATED ART APPLICATIONS) This application claims priority to a Chinese patent application bearing application number 202410016946.0, filed with the State Intellectual Property Office of the People's Republic of China on January 5, 2024, the entire contents of which are incorporated herein by reference.

[0002] The present disclosure relates to the technical field of medical devices, and in particular to a communication module, an implantable left ventricular assist system, and an intelligent information management method for an implantable left ventricular assist device. [Background technology]

[0003] With the development of medical device technology, implantable left ventricular assist devices have emerged to provide hemodynamic support to patients. An implantable left ventricular assist device includes a blood pump implanted in the human body, a patient controller, a power supply, and a medical monitor. The patient controller is connected to the blood pump, and the medical monitor communicates with the patient controller via a serial port. Medical personnel monitor the real-time status of the blood pump on the medical monitor, thereby monitoring the real-time status of the patient.

[0004] After the patient is discharged from the hospital, medical monitors are no longer able to monitor the implantable left ventricular assist device in a timely manner, and current implantable left ventricular assist devices have the problem of low safety in the case of remote real-time monitoring. Summary of the Invention [Problem to be solved by the invention]

[0005] In view of the above technical problems, there is a need to provide a communication module, an implantable left ventricular assist system, and an intelligent information management method for an implantable left ventricular assist device that improves safety. [Means for solving the problem]

[0006] In a first aspect, the present disclosure provides a communication module configured to connect to a patient controller of an implantable left ventricular assist device and a cloud device, the implantable left ventricular assist device further comprising a blood pump connected to the patient controller, the communication module configured to receive current operating data of the blood pump transmitted by the patient controller, and the communication module configured to periodically publish the current operating data to the cloud device.

[0007] In one embodiment, the communication module is configured to receive current power data of the implantable left ventricular assist device transmitted by the patient controller, and the communication module is configured to periodically publish the current power data to the cloud device.

[0008] In one embodiment, the communication module is configured to receive device alarm messages of the implantable left ventricular assist device transmitted by the patient controller, and the communication module is configured to periodically publish the device alarm messages to the cloud device.

[0009] In one embodiment, the communication module includes a communication unit configured to be connected to the patient controller, a power source of the implantable left ventricular assist device, and the cloud device, respectively; a display unit; and a step-down unit configured to be connected to the patient controller and the power source, respectively, and further connected to the communication unit and the display unit, respectively.

[0010] In one embodiment, the communication module includes a power interface connected to the power source and a plurality of cables connected between the patient controller and the power interface, the cables including a monitor communication cable, a battery communication cable, a power cable, and a ground cable, the step-down unit is connected to the power cable and the ground cable, and the communication unit is connected to the monitor communication cable.

[0011] In a second aspect, the present disclosure provides an implantable left ventricular assist system comprising: a communications module; an implantable left ventricular assist device including a patient controller and a blood pump connected to the patient controller, the patient controller connected to the communications module and configured to acquire current operating data of the blood pump and transmit the acquired current operating data to the communications module; a cloud device connected to the communications module; and a mobile device connected to the cloud device, the communications module configured to periodically publish the acquired current operating data to the cloud device, the cloud device configured to store the acquired current operating data and provide data access to the mobile device.

[0012] In one embodiment, the patient controller is configured to obtain current power data of the implantable left ventricular assist device and transmit the current power data to the communication module. The communication module is configured to receive the current power data and periodically publish the current power data to the cloud device. The cloud device is configured to transmit the current power data to the mobile device in response to receiving the current power data. The mobile device is configured to output a corresponding prompting message in response to receiving the current power data.

[0013] In one embodiment, the communications module is configured to receive device alarm messages of the implantable left ventricular assist device transmitted by the patient controller and periodically publish the device alarm messages to the cloud device, which is configured to transmit the device alarm messages to the mobile device in response to receiving the device alarm messages, and which is configured to output corresponding prompting messages in response to receiving the device alarm messages.

[0014] In one embodiment, the communication module includes a communication unit connected to the patient controller and the cloud device, respectively, and further connected to a power source of the implantable left ventricular assist device; a display unit; and a step-down unit connected to the patient controller, the communication unit, and the display unit, respectively, and further connected to the power source.

[0015] In one embodiment, the communication module includes a power interface connected to the power source and a plurality of cables connected between the patient controller and the power interface, the cables including a monitor communication cable, a battery communication cable, a power cable, and a ground cable, the step-down unit is connected to the power cable and the ground cable, and the communication unit is connected to the monitor communication cable.

[0016] In a third aspect, the present disclosure provides an intelligent information management method for an implantable left ventricular assist device, the method being applied to the communication module described above. The method includes the step of receiving current device data transmitted by the patient controller by the communication module, the current device data including at least one of the current operating data of the blood pump, the current power data of the implantable left ventricular assist device, and the device alarm messages of the implantable left ventricular assist device by the communication module. The method also includes the step of periodically publishing the current device data to the cloud device by the communication module.

[0017] In one embodiment, the current operating data includes blood pump current start / stop status data and current pump speed data.

[0018] In one embodiment, the communication module's periodically publishing the current device data to the cloud device includes: in response to the communication module being connected to an access point, the communication module establishing an MQTT connection to the cloud device; if the MQTT connection is successfully established, the communication module sending a subscription request including an MQTT subscription topic to the cloud device; and if the MQTT subscription topic is successfully subscribed to and no MQTT subscription information is received from the cloud device, the communication module periodically publishing the current device data to the cloud device.

[0019] In one embodiment, the method further includes, when the MQTT subscription topic is successfully subscribed to and the MQTT subscription information from the cloud device is received, the communication module executes a corresponding request based on the MQTT subscription information.

[0020] In one embodiment, the method further includes the steps of: if the MQTT subscription information includes a data export request, the communication module publishing historical device data to the cloud device; and after the historical device data is published, the communication module reporting an export result to the cloud device.

[0021] The details of one or more embodiments of the disclosure are set forth in the accompanying drawings and the description below. Other features, objects, and advantages of the disclosure will become apparent from the description, the accompanying drawings, and the claims.

[0022] In order to more clearly explain the technical aspects of the embodiments of the present disclosure or related technologies, the following will briefly introduce the accompanying drawings that need to be used in the description of the embodiments or related technologies. However, the accompanying drawings in the following description are only some embodiments of the present disclosure, and it is clear that those skilled in the art can obtain other accompanying drawings based on these drawings without any creative effort. [Brief explanation of the drawings]

[0023] [Figure 1] FIG. 1 is a block diagram illustrating the configuration of an implantable left ventricular assist device according to some embodiments.

[0024] [Figure 2] FIG. 2 is a block diagram illustrating a configuration of a communication module according to some embodiments.

[0025] [Figure 3] FIG. 3 is a block diagram illustrating a configuration of a communication module according to some other embodiments.

[0026] [Figure 4] FIG. 4 is a block diagram illustrating a configuration of a communication module according to further some embodiments.

[0027] [Figure 5]FIG. 5 is a block diagram illustrating the configuration of an implantable left ventricular assist system according to some embodiments.

[0028] [Figure 6] FIG. 6 is a flowchart illustrating a process of intelligent information management of a cloud device according to some embodiments.

[0029] [Figure 7] FIG. 7 is a flowchart illustrating a process of intelligent information management of a cloud device according to some other embodiments.

[0030] [Figure 8] FIG. 8 is a schematic diagram illustrating the internal configuration of a cloud device according to some embodiments.

[0031] [Figure 9] FIG. 9 is a schematic diagram illustrating the internal configuration of a mobile device according to some embodiments.

[0032] [Figure 10] FIG. 10 is a flowchart of a method for intelligent information management of an implantable left ventricular assist device according to some embodiments.

[0033] [Figure 11] FIG. 11 is a flowchart of steps for intelligent information management of an implantable left ventricular assist device according to some embodiments.

[0034] [Figure 12] FIG. 12 is a flowchart of a method for intelligent information management of an implantable left ventricular assist device according to some other embodiments.

[0035] [Figure 13] FIG. 13 is a flow chart illustrating a process of intelligent information management of a communication module according to some embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0036] In order to make the above-mentioned objects, features, and advantages of the present disclosure clearer and easier to understand, specific embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. In the following description, many specific details are set forth in order to fully understand the present disclosure. However, the present disclosure can be implemented in many other ways different from those described herein, and those skilled in the art can make similar improvements without departing from the spirit of the present disclosure. Therefore, the present disclosure is not limited by the specific examples disclosed below.

[0037] In describing the present disclosure, orientations or positional relationships indicated by terms such as "center," "longitudinal," "lateral," "length," "width," "thickness," "upper," "lower," "front," "rear," "left side," "right side," "longitudinal," "lateral," "top," "bottom," "inner," "outer," "clockwise," "counterclockwise," "axial," "radial," "circumferential," and the like, are based on the orientations or positional relationships shown in the accompanying drawings, are intended merely to facilitate and simplify the description of the present disclosure, and do not expressly or imply that the devices or elements shown must have a particular orientation or be configured or operated in a particular orientation, and therefore should not be construed as limiting the present disclosure.

[0038] An implantable left ventricular assist device can provide hemodynamic support to a patient with heart failure. As shown in FIG. 1 , the implantable left ventricular assist device includes a blood pump implanted in the human body, a patient controller, a power source such as an external battery or adapter, and a medical monitor. The patient controller is connected to the blood pump via a percutaneous cable and to a power source to power the entire implantable left ventricular assist device. In a hospital, the medical monitor can communicate with the patient controller via a serial port. The patient controller is a patient controller that can display information on the status of the blood pump and the power source in real time. Medical personnel can monitor and control the implantable left ventricular assist device using the medical monitor.

[0039] In the above-mentioned aspects, there is still a gap in remote monitoring of the patient's real-time condition after discharge. If an abnormality occurs in the operation of the implantable left ventricular assist device, medical personnel cannot receive immediate notification, and the patient must provide emergency treatment themselves. If a special abnormality occurs that the patient cannot resolve, it will naturally pose an unexpected risk to the patient. Meanwhile, the increasing number of patients will naturally pose a great challenge to clinical support and after-sales management. From the perspective of patient risk control and after-sales tracking, the operational safety of conventional implantable left ventricular assist devices still has room for improvement.

[0040] In one embodiment, as shown in Figure 2, a communications module 110 is provided. The communications module 110 is connected to a patient controller 130 of the implantable left ventricular assist device 10. The implantable left ventricular assist device 10 further comprises a blood pump 120 connected to the patient controller 130. The communications module 110 is further connected to a cloud device 20. The communications module 110 receives current operating data of the blood pump 120 transmitted by the patient controller 130. The communications module 110 periodically publishes the current operating data to the cloud device 20.

[0041] Specifically, the blood pump 120 can be implanted in the left ventricle of the heart, and the patient controller 130 is installed outside the patient's body and connected to the blood pump 120. The patient controller 130 can acquire current operating data of the blood pump 120 in real time, thereby monitoring the real-time status of the blood pump 120. The operating data of the blood pump 120 includes data such as the pump speed, flow rate, and power consumption of the blood pump 120. The communication module 110 is connected to the patient controller 130 and receives the current operating data of the blood pump 120 transmitted by the patient controller 130. As shown in FIG. 2(a), the communication module 110 can be integrated into the implantable left ventricular assist device 10, for example, integrated inside the patient controller 130. As shown in FIG. 2(b), the communication module 110 is independent of the implantable left ventricular assist device 10 and can wirelessly exchange data with the patient controller 130. The communication module 110 can wirelessly communicate with the cloud device 20. When the communication module 110 receives current operation data of the blood pump 120 transmitted by the patient controller 130, the communication module 110 can periodically publish the current operation data to the cloud device 20, thereby realizing synchronization of the current operation data between the cloud device 20 and the patient controller 130.

[0042] As some examples, the patient controller 130 can be connected to the blood pump 120 via a percutaneous cable. The patient controller 130 can be connected to a monitoring device, allowing a medical professional to monitor and control the implantable left ventricular assist device 10 through the monitoring device. For example, the monitoring device can monitor the real-time status of the blood pump 120 and control the start / stop, pump speed, HCT value (hematocrit value), low flow threshold, and high power consumption threshold of the blood pump 120. The cloud device 20 can be connected to one or more mobile devices and synchronize current operating data with the corresponding mobile devices, thereby realizing remote monitoring of the implantable left ventricular assist device 10.

[0043] An embodiment of the present disclosure provides a communication module 110. The communication module 110 is connected to a patient controller 130 of the implantable left ventricular assist device 10. The implantable left ventricular assist device 10 further includes a blood pump 120 connected to the patient controller 130. The communication module 110 is connected to a cloud device 20. The communication module 110 receives current operation data of the blood pump 120 transmitted by the patient controller 130. The communication module 110 periodically publishes the current operation data to the cloud device 20. The above-described communication module enables remote monitoring of the operation status of the blood pump 120. After the patient is discharged from the hospital, if an abnormality occurs in the operation of the implantable left ventricular assist device 10, medical personnel can receive a corresponding notification from the cloud device in a timely manner. As a result, the safety of the implantable left ventricular assist device 10 is improved.

[0044] In one embodiment, the current operating data includes current start / stop status data of the blood pump 120 and current pump speed data.

[0045] Specifically, the current start / stop status data of the blood pump 120 can be used to indicate whether the blood pump 120 is currently in a start or stop state. The current pump speed data of the blood pump 120 can be used to indicate the real-time pump speed and the target pump speed of the blood pump 120.

[0046] In one embodiment, the communications module 110 receives current power data of the implantable left ventricular assist device 10 transmitted by the patient controller 130 .

[0047] The communication module 110 periodically publishes current power data to the cloud device 20 .

[0048] Specifically, the implantable left ventricular assist device 10 can be connected to a power source for normal operation. The power source may be an external power source or an internal power source, and the external power source may include an external battery or an external adapter. The communication module 110 can wirelessly communicate with the cloud device 20. When the communication module 110 receives current power data of the blood pump 120 transmitted by the patient controller 130, the communication module 110 can periodically publish the current power data to the cloud device 20, thereby achieving synchronization of the current power data between the cloud device 20 and the patient controller 130. The current power data of the implantable left ventricular assist device 10 may be information related to the currently used power source, including the voltage, current, battery capacity, etc. of the power source. The current power data can be used to monitor the power status of the implantable left ventricular assist device 10 to ensure normal operation of the implantable left ventricular assist device 10.

[0049] As some examples, the communication module 110 can be installed between the patient controller 130 and the power source. The communication module 110 is connected to the patient controller 130 and the power source, respectively. The communication module 110 can be integrated inside the power source that is installed outside the body.

[0050] In one embodiment, the communication module 110 receives device alarm messages for the implantable left ventricular assist device 10 sent by the patient controller 130. The communication module 110 periodically publishes the device alarm messages to the cloud device 20.

[0051] Specifically, the communication module 110 can wirelessly communicate with the cloud device 20. When the communication module 110 receives a device alarm message of the implantable left ventricular assist device 10 transmitted by the patient controller 130, the communication module 110 can periodically publish the device alarm message to the cloud device 20, thereby achieving synchronization of the device alarm messages between the cloud device 20 and the patient controller 130. The device alarm message of the implantable left ventricular assist device 10 may be information related to an abnormal condition or malfunction detected during operation of the implantable left ventricular assist device 10 and notified to a user or medical professional via an alarm. The device alarm message can be used to notify a user or medical professional of an abnormal condition of the implantable left ventricular assist device 10 so that the user or medical professional can take appropriate action.

[0052] In one embodiment, the communication module 110 includes a communication unit 112, a display unit 114, and a step-down unit 116. The communication unit 112 is connected to the patient controller 130 and a power source of the implantable left ventricular assist device 10, respectively. The communication unit 112 is further connected to the cloud device 20. The step-down unit 116 is connected to the patient controller 130 and a power source, respectively. The step-down unit 116 is also connected to the communication unit 112 and the display unit 114, respectively.

[0053] Specifically, as shown in FIG. 3 , the communication module 110 is integrated into the implantable left ventricular assist device 10. The communication unit 112 is connected to the patient controller 130 to obtain current operation data of the blood pump 120, current power data of the implantable left ventricular assist device 10, and / or device alarm messages transmitted by the patient controller 130. The step-down unit 116 is connected to the patient controller 130, the communication unit 112, and the display unit 114. The step-down unit 116 can also be connected to an external power source to enable step-down power supply to the patient controller 130, the communication unit 112, and the display unit 114. The communication unit 112 is connected to the cloud device 20 and can wirelessly communicate with the cloud device 20. When the communication unit 112 receives current operation data of the blood pump 120 transmitted by the patient controller 130, the communication unit 112 can periodically publish the current operation data to the cloud device 20, thereby achieving synchronization of the current operation data between the cloud device 20 and the patient controller 130. When the communication unit 112 receives current power data of the blood pump 120 transmitted by the patient controller 130, the communication unit 112 can periodically publish the current power data to the cloud device 20, thereby realizing synchronization of the current power data between the cloud device 20 and the patient controller 130. When the communication unit 112 receives a device alarm message of the implantable left ventricular assist device 10 transmitted by the patient controller 130, the communication unit 112 can periodically publish the device alarm message to the cloud device 20, thereby realizing synchronization of the device alarm message between the cloud device 20 and the patient controller 130. The display unit 114 can display current operating data, current power data and / or device alarm messages of the implantable left ventricular assist device 10. The current operating data includes current start / stop status data and current pump speed data of the blood pump 120.

[0054] In one embodiment, as shown in Figure 4, the communications module 110 includes a power interface that connects to a power source. The communications module 110 further includes a plurality of cables that connect between the patient controller 130 and the power interface. The cables include a monitor communications cable 410, a battery communications cable 420, a power cable 430, and a ground cable 440. The step-down unit 116 is connected to the power cable 430 and the ground cable 440, respectively. The communications unit 112 is connected to the monitor communications cable 410.

[0055] Specifically, the communication module 110 is connected in series between the patient controller 130 and an external power source such as a battery or an adapter. The multiple cables of the communication module 110 can all be hardwired between the patient controller 130 and the external power source. The step-down unit 116 is connected to the power cable 430 and the ground cable 440. The step-down unit 116 converts the external power source to DC-DC (direct current-direct current) and then supplies power to the connected communication unit 112 and display unit 114. Furthermore, if a failure occurs in the communication module 110, the patient controller 130 and the external power source connected to the communication module 110 will not be damaged, thereby improving the safety and reliability of the communication module 110.

[0056] As some examples, the communication module 110 can be connected in series between the power cable connector of the patient controller 130 and an external power source. The monitor communication cable 410 includes a data transmission line and a data reception line. The battery communication cable 420 includes a clock line and a data line. The communication unit 112 can support at least one of Wi-Fi (wireless network communication technology) communication, 4G (fourth generation mobile communication technology) communication, and 5G (fifth generation mobile communication technology) communication. The display unit 114 includes a button and an LED (light emitting diode) display.

[0057] In one embodiment, an implantable left ventricular assist system is provided, as shown in Figure 5. The implantable left ventricular assist system includes an implantable left ventricular assist device 10, a cloud device 20, a mobile device 30, and a communication module 110.

[0058] The implantable left ventricular assist device 10 includes a patient controller 130 and a blood pump 120 connected to the patient controller 130. The patient controller 130 is connected to a communication module 110, and acquires current operating data of the blood pump 120 and transmits the current operating data to the communication module 110. The communication module 110 is connected to a cloud device 20, and the communication module 110 periodically publishes the current operating data to the cloud device 20. The cloud device 20 is connected to a mobile device 30, and stores the acquired current operating data and provides data access to the mobile device 30.

[0059] Specifically, the communication module 110 of the implantable left ventricular assist device 10 is a central point for acquiring and uploading current operating data to the cloud device 20, and can function as a medical monitor for monitoring the operating status of the blood pump 120. In the cloud device 20, the communication module 110 corresponds to an MQTT client. In the implantable left ventricular assist system, the implantable left ventricular assist device 10 is on the device side, the cloud device 20 is on the cloud side, and the mobile device 30 is on the mobile side. The cloud device 20 is a server or server cluster that can be shared between the device side and the mobile side and can be accessed through a specific public IP address. The cloud device 20 can provide services such as an MQTT broker server, a database server, a network time protocol server (NTP server), and a web server. The cloud device 20 acts as an MQTT broker server, mediating data subscription and publication between the device side and the mobile side, and protects data security and integrity through encryption and authentication based on SSL (Secure Sockets Layer) / TSL (Transport Layer Security). The cloud device 20 acts as a database server, providing reliable data storage and access services, such as storage and access services for current work data, historical work data, and mobile side historical operation data. The cloud device 20 acts as a network time protocol server, providing timing synchronization services. The cloud device 20 acts as a web server, providing service front-end interaction services, such as web interaction services and Web Sockets, to the mobile side. The mobile side includes one or more mobile devices 30. The mobile devices 30 are mobile, multi-platform devices capable of communicating with the cloud side, and are capable of providing healthcare services, clinical services, and after-sales services.The mobile side can support remote export of historical work data from the cloud device 20, for example, by sending a data export request to the cloud device 20. The mobile side can provide remote monitoring of the patient's real-time condition.

[0060] The above-described system enables remote monitoring of the operating status of the blood pump 120. Even if an abnormality occurs in the operation of the implantable left ventricular assist device 10 after the patient is discharged from the hospital, medical personnel can receive appropriate notifications in a timely manner from the mobile device 30, thereby improving the safety of the implantable left ventricular assist device 10.

[0061] As some examples, the cloud device 20 can be connected to one or more mobile devices 30 and one or more implantable left ventricular assist devices 10. The mobile devices 30 include at least one of a mobile phone, a tablet, and a personal computer. As shown in FIG. 6 , after the cloud device 20 is started, the cloud device 20 can start the MQTT service, the database service, and the web service in order, and keep all the services in a listening state. It is determined whether the cloud device 20 needs to be shut down. If the result is YES, the cloud device 20 ends its operation. If the result is NO, the process returns to the step of keeping all the services in a listening state.

[0062] As some examples, as shown in FIG. 7, in the listening process of the MQTT service, the cloud device 20 detects whether a new device is connected. If the result is YES, it searches the database to confirm whether the new device is registered. If the new device is not registered, it creates a new table for the new device and inserts it into the database. If the new device is already registered, the cloud device 20 detects whether a new message has arrived. If the cloud device 20 detects the arrived new message, it determines whether a topic corresponding to the arrived message has been defined. If the topic of the arrived message has already been defined, the cloud device 20 determines whether the arrived message needs to be published to other devices. The cloud device 20 can publish the arrived message to other devices that have subscribed to the topic of the arrived message. The cloud device 20 can further determine whether the arrived message is system operation time information. If the arrived message is system operation time information, the cloud device 20 analyzes whether there is a potential risk in the system operation time information. If there is a risk, the cloud device 20 distributes the system operation time information to medical personnel. If there is no potential risk, the cloud device 20 inserts the system operation time information into the system operation time information table. If the cloud device 20 determines that the received message is not system operation time information, it can determine whether the received message is a history log. If the received message is a history log, the cloud device 20 can store the history log in memory. If the history log is completely stored, the cloud device 20 inserts the history log into the history log table.

[0063] For example, if the client located on the mobile device 30 is an APP, the mobile device 30 can subscribe to a corresponding push application function program through the APP program interface to receive device alarm messages and provide corresponding suggested action information to medical professionals when an abnormality occurs in the implantable left ventricular assist device 10. If the client located on the mobile device 30 is a web page, the mobile device 30 can use the web page to check which implantable left ventricular assist devices 10 are currently online and monitor the real-time status of each implantable left ventricular assist device 10. The mobile device 30 can use the web page to generate a data export request and realize remote export of historical operation data. The mobile device 30 can use the web page to perform analysis based on the mobile user's big data, thereby providing the user with early warnings to minimize risk occurrence.

[0064] In one embodiment, the patient controller 130 obtains current power data of the implantable left ventricular assist device 10 and transmits the current power data to the communication module 110. The communication module 110 receives the current power data and periodically publishes the current power data to the cloud device 20. In response to receiving the current power data, the cloud device 20 transmits the current power data to the mobile device 30. In response to receiving the current power data, the mobile device 30 outputs a corresponding prompting message.

[0065] Specifically, the communication module 110 of the implantable left ventricular assist device 10 is a central point for uploading current power data to the cloud device 20 and periodically publishing the current power data to the cloud device 20, thereby fulfilling the role of remote monitoring of the power status of the implantable left ventricular assist device 10. For example, the cloud device 20 transmits the received current power data to the mobile device 30, allowing a user to remotely monitor the power status of the implantable left ventricular assist device 10 through the mobile device 30. The cloud device 20 can function as a database server and provide reliable data storage and access services, such as storage and access services for current power data and historical power data. The mobile side can support remote export of historical power data stored in the cloud device 20, for example, by sending a data export request to the cloud device 20.

[0066] In one embodiment, the communication module 110 receives device alarm messages for the implantable left ventricular assist device 10 sent by the patient controller 130 and periodically publishes the device alarm messages to the cloud device 20. In response to receiving the device alarm messages, the cloud device 20 transmits the device alarm messages to the mobile device 30. In response to receiving the device alarm messages, the mobile device 30 outputs corresponding prompting messages.

[0067] Specifically, when the cloud device 20 receives a device alarm message from the implantable left ventricular assist device 10, it can transmit the device alarm message to the mobile device 30. In response to receiving the device alarm message, the mobile device 30 outputs a corresponding prompting message to prompt the medical staff to perform a corresponding process on the implantable left ventricular assist device 10, thereby realizing remote monitoring of the patient's real-time condition.

[0068] Specifically, the communication module 110 of the implantable left ventricular assist device 10 is the hub for uploading device alarm messages to the cloud device 20. The communication module 110 can periodically publish device alarm messages to the cloud device 20, thereby fulfilling the role of remote monitoring of the implantable left ventricular assist device 10. For example, the cloud device 20 can transmit the received device alarm messages to the mobile device 30, allowing a user to remotely monitor the implantable left ventricular assist device 10 via the mobile device 30. When an abnormality occurs in the implantable left ventricular assist device 10, the mobile device 30 can timely obtain the device alarm message and provide corresponding suggested treatment information to a medical professional.

[0069] In one embodiment, the communication module 110 includes a communication unit 112, a display unit 114, and a step-down unit 116. The communication unit 112 is connected to the patient controller 130 and the cloud device 20, respectively, and is further connected to a power source of the implantable left ventricular assist device 10. The step-down unit 116 is connected to the patient controller 130, the communication unit 112, and the display unit 114, respectively. The step-down unit 116 is further connected to a power source.

[0070] Specifically, the communication unit 112 is connected to the patient controller 130 to obtain current operation data of the blood pump 120, current power data of the implantable left ventricular assist device 10, and / or device alarm messages transmitted by the patient controller 130. The step-down unit 116 is connected to the patient controller 130, the communication unit 112, and the display unit 114. The step-down unit 116 is connected to an external power source to realize step-down power supply for the patient controller 130, the communication unit 112, and the display unit 114. The communication unit 112 is connected to the cloud device 20 and can wirelessly communicate with the cloud device 20. When the communication unit 112 receives current operation data of the blood pump 120 transmitted by the patient controller 130, the communication unit 112 can periodically publish the current operation data to the cloud device 20, thereby achieving synchronization of the current operation data between the cloud device 20 and the patient controller 130. When the communication unit 112 receives current power data of the blood pump 120 transmitted by the patient controller 130, the communication unit 112 can periodically publish the current power data to the cloud device 20, thereby realizing synchronization of the current power data between the cloud device 20 and the patient controller 130. When the communication unit 112 receives a device alarm message of the implantable left ventricular assist device 10 transmitted by the patient controller 130, the communication unit 112 can periodically publish the device alarm message to the cloud device 20, thereby realizing synchronization of the device alarm message between the cloud device 20 and the patient controller 130. The display unit 114 can display current operating data, current power data and / or device alarm messages of the implantable left ventricular assist device 10. The current operating data includes current start / stop status data and current pump speed data of the blood pump 120.

[0071] In one embodiment, the communications module 110 includes a power interface that connects to a power source. The communications module 110 further includes a plurality of cables connected between the patient controller 130 and the power interface. The cables include a monitor communications cable 410, a battery communications cable 420, a power cable 430, and a ground cable 440. The step-down units are connected to the power cable 430 and the ground cable 440, respectively. The communications unit is connected to the monitor communications cable 410.

[0072] Specifically, the communication module 110 can be connected in series between the patient controller 130 and an external power source such as a battery or an adapter. The multiple cables of the communication module 110 can all be hardwired between the patient controller 130 and the external power source. The step-down unit 116 is connected to the power cable 430 and the ground cable 440. The step-down unit 116 converts the external power source to DC-DC (direct current-direct current) and then supplies power to the connected communication unit 112 and display unit 114. Furthermore, if a failure occurs in the communication module 110, the patient controller 130 and the external power source connected to the communication module 110 will not be damaged, thereby improving the safety and reliability of the communication module 110.

[0073] As some examples, the communication module 110 can be connected in series between the power cable connector of the patient controller 130 and an external power source. The monitor communication cable 410 includes a data transmission line and a data reception line. The battery communication cable 420 includes a clock line and a data line. The communication unit 112 can support at least one of Wi-Fi (wireless network communication technology) communication, 4G (fourth generation mobile communication technology) communication, and 5G (fifth generation mobile communication technology) communication. The display unit 114 includes a button and an LED (light emitting diode) display.

[0074] In an exemplary embodiment, a cloud device 20 is provided as a server, the internal configuration of which is shown in FIG. 8 . The cloud device 20 includes a processor, a memory, an input / output (I / O) interface, and a communication interface. The processor, memory, and I / O interface are connected by a system bus, and the communication interface is connected to the system bus via the I / O interface. The processor of the cloud device 20 is used to provide computing and control functions. The memory of the cloud device 20 includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for executing the operating system and computer programs stored in the non-volatile storage medium. The database of the cloud device 20 is used to store current device data, historical device data, and mobile-side historical operation data. The I / O interface of the cloud device 20 is used to exchange information between the processor and external devices. The communication interface of the cloud device 20 is used to communicate with external terminals via a network connection.

[0075] In an exemplary embodiment, a mobile device 30 serving as a terminal is provided, the internal configuration of which is shown in FIG. 9 . The mobile device 30 includes a processor, a memory, an input / output interface, a communication interface, a display unit, and an input device. The processor, memory, and input / output interface are connected via a system bus, and the communication interface, display unit, and input device are connected to the system bus by the input / output interface. The processor of the mobile device 30 is used to provide computing and control functions. The memory of the mobile device 30 includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and computer programs. The internal memory provides an environment for executing the operating system and computer programs stored in the non-volatile storage medium. The input / output interface of the mobile device 30 is used to exchange information between the processor and external devices. The communication interface of the mobile device 30 is used for communicating with the outside world in a wired or wireless manner, and the wireless manner can be realized by Wi-Fi, a mobile cellular network, NFC (Near Field Communication), or other technologies. The display unit of the mobile device 30 is used to form a visually visible image and may be a display, a projection device, or a virtual reality imaging device. The display may be an LCD (Liquid Crystal Display) or an e-ink display, and the input device of the mobile device 30 may be a touch layer covered by the display, or may be a button, trackball, or touchpad provided on the housing of the mobile device 30, or may be an external keyboard, touchpad, or mouse.

[0076] For those skilled in the art, the structures shown in Figures 8 and 9 are merely block diagrams illustrating the configuration of parts related to embodiments of the present disclosure and are not intended to limit the computer devices to which embodiments of the present disclosure can be applied; a specific computer device may include more or fewer components than those shown, may combine some of the components, or may have a different arrangement of the components.

[0077] In one embodiment, an intelligent information management method for an implantable left ventricular assist device 10 is provided, which is applied to the above-mentioned communication module 110, as shown in Figure 10. The method includes the following steps.

[0078] In step 1010, current device data transmitted by the patient controller 130 is received. The current device data includes at least one of current operating data of the blood pump 120, current power data of the implantable left ventricular assist device 10, and device alarm messages of the implantable left ventricular assist device 10.

[0079] In step 1020, current device data is periodically published to the cloud device 20.

[0080] Specifically, the communication module 110 is capable of wirelessly communicating with the cloud device 20. When the communication module 110 receives current device data of the implantable left ventricular assist device 10 transmitted by the patient controller 130, the communication module 110 can periodically publish the current device data to the cloud device 20, thereby achieving synchronization of the current device data between the cloud device 20 and the patient controller 130. The current device data includes at least one of current operating data of the blood pump 120, current power data of the implantable left ventricular assist device 10, and device alarm messages of the implantable left ventricular assist device 10.

[0081] In one embodiment, the current operating data includes current start / stop status data of the blood pump 120 and current pump speed data.

[0082] Specifically, the current start / stop status data of the blood pump 120 is used to indicate whether the blood pump 120 is currently in a start or stop state. The current pump speed data of the blood pump 120 is used to indicate the real-time pump speed and the target pump speed of the blood pump 120.

[0083] In one embodiment, as shown in FIG. 11, periodically publishing current device data to cloud device 20 includes the following steps.

[0084] In step 1110, in response to the communication module 110 being connected to the access point, an MQTT connection is established to the cloud device 20.

[0085] In step 1120, if the MQTT connection is successfully established, send a subscription request including the MQTT subscription topic to the cloud device 20.

[0086] In step 1130, if the MQTT subscription topic is successfully subscribed to and no MQTT subscription information is received from the cloud device 20, the current device data is periodically published to the cloud device 20.

[0087] MQTT (Message Queuing Telemetry Transport) is a lightweight messaging protocol commonly used for communication between Internet of Things (IoT) devices. Specifically, the communication module 110 is initialized after power-on and can connect to an access point (AP). The access point can provide wireless network access to devices such as the communication module 110. When the communication module 110 is successfully connected to the access point, it can establish an MQTT connection to the cloud device 20. The cloud device 20 provides the functionality of an MQTT broker server, receiving messages from MQTT clients (e.g., the communication module 110) and distributing them to clients that have subscribed to the corresponding topics. When the MQTT connection to the cloud device 20 is successfully established, the communication module 110 sends a subscription request to the cloud device 20. The subscription request includes an MQTT subscription topic, which is a string for identifying the topic or main content of the MQTT subscription information. If the communication module 110 successfully subscribes to the MQTT subscription topic and the MQTT subscription information of the cloud device 20 is not received, the communication module 110 can periodically publish current device data to the cloud device 20.

[0088] As some examples, the MQTT subscription topic may include SYS_INFO (system information). The SYS_INFO topic may be used to periodically and proactively publish current device data of the implantable left ventricular assist device 10, including the current start / stop status data and current pump speed data of the blood pump 120, as well as the current power data and device alarm messages of the implantable left ventricular assist device 10. By subscribing to the SYS_INFO topic, it is possible to receive the above-mentioned current device data. The MQTT subscription topic may further include RESP_DATETIME (response date and time). The RESP_DATETIME topic may be used by the communication module 110 to report the setting result after completing the system time setting of the patient controller 130. For example, the RESP_DATETIME topic may report the client ID and the corresponding setting result as a data structure for reporting the setting result. By subscribing to the RESP_DATETIME topic, it is possible to receive information related to device response times, such as the time when the device responds to a request and an execution timestamp.

[0089] In one embodiment, the method further includes, when the MQTT subscription topic is successfully subscribed to and the MQTT subscription information from the cloud device 20 is received, executing a corresponding request based on the MQTT subscription information.

[0090] Specifically, when the communication module 110 successfully subscribes to the MQTT subscription topic and receives the MQTT subscription information of the cloud device 20, it can execute a corresponding request based on the MQTT subscription information. The MQTT subscription information is information sent by the cloud device 20 to the communication module 110 based on a corresponding request from a connected mobile device. After the communication module 110 executes the corresponding request, the cloud device 20 can accept the execution result fed back from the communication module 110 and feed back the execution result to the mobile device connected to the cloud device 20.

[0091] In one embodiment, as shown in FIG. 12, the method further includes the following steps:

[0092] In step 1210, if the MQTT subscription information includes a data export request, publish the historical device data to the cloud device 20.

[0093] In step 1220, after the historical device data is published, the export result is reported to the cloud device 20.

[0094] Specifically, the cloud device 20 can send MQTT subscription information to the communication module 110. The MQTT subscription information can include, for example, a data export request, which is sent by a mobile device connected to the cloud device 20 to export historical device data. If the MQTT subscription information received by the communication module 110 includes a data export request, the communication module 110 can publish the historical device data to the cloud device 20. The historical device data can include historical start / stop status data and historical pump speed data of the blood pump 120, and historical power data and device historical alarm messages of the implantable left ventricular assist device 10. After the historical device data is published, the communication module 110 can report the export result to the cloud device 20.

[0095] As some examples, MQTT subscription topics include SYS_LOG (system log) and RESP_LOG (response log). The SYS_LOG topic is used to conditionally publish historical device data of the implantable left ventricular assist device 10. For example, the communication module 110 can publish historical device data only upon a data export request. Each time the communication module 110 publishes historical device data, it can export the data in the form of a 512-byte block at a time. The data structure includes a 2-byte block address and 512 bytes of historical device data. Other devices can receive the above-mentioned historical device data by subscribing to the SYS_LOG topic. The RESP_LOG topic can be used to report the export result to the cloud device 20 after the communication module 110 completes exporting the historical device data. For example, the communication module 110 reports the client ID and the corresponding export result as a data structure.

[0096] As some examples, as shown in FIG. 13 , after power-on, the communication module 110 is initialized. After completing initialization, the communication module 110 attempts to connect to an access point until a connection is successful. If the communication module 110 successfully connects to the access point, it can establish an MQTT connection to the cloud device 20. When the communication module 110 successfully establishes the MQTT connection to the cloud device 20, it can send a subscription request for an MQTT subscription topic to the cloud device 20. If the communication module 110 cannot establish an MQTT connection to the cloud device 20, it can determine whether the connection with the access point has been lost. If the connection with the access point has been lost, the communication module 110 can reconnect to the access point. If the communication module 110 remains connected to the access point, it can re-establish the MQTT connection to the cloud device 20. After sending the subscription request for the MQTT subscription topic to the cloud device 20, the communication module 110 re-determines whether the connection with the access point has been lost. The communication module 110 can reconnect to an access point if the connection with the access point is lost. When the communication module 110 remains connected to the access point, it can determine whether the MQTT connection with the cloud device 20 is lost. When the MQTT connection with the cloud device 20 is lost, the communication module 110 can re-determine whether the connection with the access point is lost. When the MQTT connection to the cloud device 20 remains established, the communication module 110 can determine whether MQTT subscription information is received. If the MQTT subscription information is received, the communication module 110 can publish historical device data in response to a specific request based on the MQTT subscription information, such as a data export request. If the communication module 110 does not receive MQTT subscription information, it can periodically publish current device data.

[0097] Although the steps in the flowcharts relating to the above-described embodiments are indicated by arrows, it is understood that these steps are not necessarily performed sequentially in the order indicated by the arrows. Unless otherwise specified herein, there are no strict restrictions on the order in which these steps are performed, and these steps may be performed in other orders. Furthermore, at least some of the steps in the flowcharts relating to the above-described embodiments may include multiple steps or multiple stages, and these steps or stages may not necessarily be completed at the same time but may be performed at different times. The order in which these steps or stages are performed is also not necessarily sequential, and they may be performed in order or alternately with other steps or at least some of the steps or stages in other steps.

[0098] In one embodiment, there is provided a computer readable storage medium having stored thereon a computer program which, when executed by a processor, causes the processor to perform the steps of the method described above.

[0099] In one embodiment, a computer program product is provided that includes a computer program that, when executed by a processor, causes the processor to perform the steps of the method described above.

[0100] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by instructing associated hardware via a computer program. The computer program is stored in a non-volatile computer-readable storage medium, and when executed, can execute the steps of each of the above-described method embodiments. References to memory, databases, or other media used in the embodiments provided in this disclosure may include at least one of non-volatile memory and volatile memory. Non-volatile memory includes read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory includes random access memory (RAM) or external cache memory, etc. As a non-limiting example, the RAM may be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database for the embodiments provided herein includes at least one of a relational database or a non-relational database. The non-relational database includes, but is not limited to, a blockchain-based distributed database. The processor for the embodiments provided herein includes, but is not limited to, a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logician, a quantum computing-based data processing logician, etc.

[0101] The technical features of the above-described embodiments may be combined in any desired manner, and for the sake of brevity, not all possible combinations of the technical features of the above-described embodiments are described. However, as long as there is no contradiction in the combination of these technical features, it should be considered that the combination falls within the scope recorded in this specification.

[0102] The above examples merely represent some embodiments of the present disclosure in more specific and detailed form, and should not be construed as limiting the scope of the present patent application. It should be noted that a person skilled in the art may make some modifications and improvements without departing from the spirit of the present disclosure, and all of these also fall within the scope of protection of the present disclosure. Therefore, the scope of protection of the present patent application shall be governed by the appended claims.

Claims

1. a communication module configured to connect to a patient controller of an implantable left ventricular assist device and to a cloud device, the implantable left ventricular assist device further comprising a blood pump connected to the patient controller; the communication module is configured to receive current operating data of the blood pump transmitted by the patient controller; The communication module is configured to periodically publish the current work data to the cloud device.

2. the communications module is configured to receive current power data of the implantable left ventricular assist device transmitted by the patient controller; The communication module of claim 1 , wherein the communication module is configured to periodically publish the current power data to the cloud device.

3. the communications module is configured to receive a device alarm message of the implantable left ventricular assist device transmitted by the patient controller; The communication module of claim 1 , wherein the communication module is configured to periodically publish the device alarm message to the cloud device.

4. The communication module includes: a communication unit configured to be connected to the patient controller, a power source of the implantable left ventricular assist device, and the cloud device, respectively; A display unit; The communication module of claim 2 , comprising: a step-down unit configured to be connected to the patient controller and the power source, respectively, and further to be connected to the communication unit and the display unit, respectively.

5. The communication module includes: a power interface connected to the power source; a plurality of cables connected between the patient controller and the power interface; the cables include a monitoring device communication cable, a battery communication cable, a power cable, and a ground cable; the step-down unit is connected to the power cable and the ground cable, The communication module of claim 4 , wherein the communication unit is connected to the monitoring device communication cable.

6. 1. An implantable left ventricular assist system comprising: a communication module; an implantable left ventricular assist device comprising: a patient controller and a blood pump connected to the patient controller, the patient controller connected to the communications module and configured to acquire current operating data of the blood pump and transmit the acquired current operating data to the communications module; a cloud device connected to the communication module; a mobile device connected to the cloud device; The communication module is configured to periodically publish the acquired current work data to the cloud device; The cloud device is configured to store the obtained current operating data and provide data access to the mobile device.

7. the patient controller is configured to obtain current power data of the implantable left ventricular assist device and to transmit the current power data to the communications module; the communication module is configured to receive the current power data and periodically publish the current power data to the cloud device; the cloud device is configured to, in response to receiving the current power data, transmit the current power data to the mobile device; The system of claim 6 , wherein the mobile device is configured to output a corresponding prompting message in response to receiving the current power data.

8. the communications module is configured to receive device alarm messages of the implantable left ventricular assist device transmitted by the patient controller and to periodically publish the device alarm messages to the cloud device; the cloud device is configured to transmit the device alarm message to the mobile device in response to receiving the device alarm message; The system of claim 6 , wherein the mobile device is configured to output a corresponding prompting message in response to receiving the device alarm message.

9. The communication module includes: a communication unit connected to the patient controller and the cloud device, respectively, and further connected to a power source of the implantable left ventricular assist device; A display unit; The system of claim 6 , further comprising a step-down unit connected to the patient controller, the communication unit, and the display unit, respectively, and further connected to the power source.

10. The communication module includes: a power interface connected to the power source; a plurality of cables connected between the patient controller and the power interface; the cables include a monitoring device communication cable, a battery communication cable, a power cable, and a ground cable; the step-down unit is connected to the power cable and the ground cable, The system of claim 9 , wherein the communication unit is connected to the monitoring device communication cable.

11. A method for intelligent information management of an implantable left ventricular assist device, applied to the communication module according to any one of claims 1 to 5, said method comprising: receiving, by the communications module, current device data transmitted by the patient controller, the current device data including at least one of the current operating data of the blood pump, the current power data of the implantable left ventricular assist device, and the device alarm messages of the implantable left ventricular assist device; the communication module periodically publishing the current device data to the cloud device.

12. The method of claim 11 , wherein the current operating data includes current start-stop status data of the blood pump and current pump speed data.

13. The communication module periodically publishing the current device data to the cloud device may further include: In response to the communication module connecting to an access point, the communication module establishing an MQTT connection to the cloud device; If the MQTT connection is successfully established, the communication module sends a subscription request to the cloud device, the subscription request including an MQTT subscription topic; and if the MQTT subscription topic is successfully subscribed to and no MQTT subscription information is received from the cloud device, the communications module periodically publishes the current device data to the cloud device.

14. 14. The method of claim 13, further comprising: if the MQTT subscription topic is successfully subscribed to and the MQTT subscription information from the cloud device is received, the communication module executes a corresponding request based on the MQTT subscription information.

15. If the MQTT subscription information includes a data export request, the communications module publishes historical device data to the cloud device; The method of claim 14 , further comprising: after the historical device data is published, the communication module reporting an export result to the cloud device.

Images