Patent Grant
10769244
The present disclosure relates generally to implantable medical devices and more specifically to managing and analyzing data generated by implantable medical devices.
Physiological data may offer medical experts an understanding of a person's wellbeing far beyond what may be gleaned by observation. For example, measuring a patient's temperature, pulse, pulse strength, respiratory rate, blood oxygen levels, tidal volume, blood pressure and various other physiological parameters may provide medical professionals a better understanding of the current state of a patient's body, vital organs and systems. Physiological data may further include measurements of biomarkers.
Physiological data also may provide early detection of a medical condition. As is the case with many medical conditions, early detection may be the difference between life and death. In the field of cancer, periodic monitoring of a patient's wellbeing may improve survival and decrease mortality by detecting cancer at an early stage when treatment is more effective. Similarly, early detection of heart disease allows the patient to change or eliminate habits that worsen their condition.
Even after a medical condition is detected, physiological data remains extremely valuable. By monitoring and analyzing a patient's symptoms and physiological measurements over an appropriate period of time, a better understanding of a patient's wellbeing or medical condition may be achieved. Monitoring a patient's symptoms and physiological measurements over a period of time will allow physicians and medical professionals to better understand the progression of the patient's medical condition and detect additional related and potentially unrelated conditions. Having a record of a patient's symptoms and physiological measurements provides an archive from which the significance and relevance of future changes may be determined.
Though physiological data may be gathered during hospital stays and office visits, the data gathered represents only glimpse into the patient's physiological wellbeing at that given period of time while the patient is in the hospital or doctor's office. With so few data points, it is difficult to truly understand how these physiological measurements are changing over time and how they relate to events and routines of a patient. Furthermore, the physiological measurements taken during a hospital stay or doctor's office visit are typically limited to non-invasive measurement mechanisms limited to the exterior of one's body. These types of measurements are often incapable of measuring interior parameters used as biomarkers such as temperature, pressure and other fluid parameters within a body cavity. Non-invasive measurements limited to the exterior of one's body typically do not serve as reliable biomarkers for conditions within the body.
Several devices have been produced that are directed to gathering specific physiological data outside of a hospital or doctor's office setting. Heart rate monitors are an example of a specific physiological measurement device used outside of the hospital setting. Heart rate monitors are typically worn by patients who have been diagnosed with a heart condition or have recently had a heart attack. Additionally, athletes are known to wear heart rate monitors for fitness purposes. Typically, heart rate monitors measure the heart rate from the exterior of the patient's body in a non-invasive manner. Some heart rate monitors are also capable of communicating to a mobile device allowing the user to view the data at a later time in a reader friendly way.
Similar in purpose is Medtronic's Reveal LINQ Insertable Cardiac Monitor device which continuously monitors a patient's heart and automatically detects and records abnormal heart rhythms. The system is implanted under the skin in the user's chest and continuously monitors a patient's heart activity in the form of an electrocardiogram (ECG). When a medical event occurs, an extracorporeal recording device is placed in close proximity to the implantable device to record the heart's rhythm during the medical episode.
Another device designed to gather specific physiological data outside of a hospital or doctor's office setting is Medtronic's Continuous Glucose Monitoring (CGM) system which measures glucose levels in real time and sends alerts to a remote monitor. The alerts include the direction glucose levels are going, early notification of oncoming lows and highs, alerts for lows or highs, and insights into how food, physical activity, medication, and illness impact glucose levels. The system consists of a glucose sensor inserted under the skin that measures glucose levels, a transmitter that sends the glucose information from the sensor to a monitor via wireless radio frequency, and a small external monitor that displays glucose levels on a screen and notifies the user if it detects that glucose is reaching a high or low limit.
While devices for measuring specific physiological parameters outside of the hospital or doctor's office setting have been developed and commercialized, these devices are only directed to measuring physiological parameters specific to the medical condition being treated or the part of the anatomy in question. Typically these devices are limited to one sensor, only measuring heart rate or glucose levels, for example. For this reason, any analysis of the data generated is often narrow in scope and directed to the medical condition being treated. While the limited data generated is helpful for better understanding that particular medical condition, it offers little to no insight into the body's overall wellbeing and how other parts of the body or systems within the body relate to the medical condition or part of the anatomy in question and therefore is often insufficient to serve as a biomarker.
Another drawback of these devices is that the monitoring or recording elements of the device are typically physically coupled to the sensing device or required to be in very close proximity to the sensing device. Where the sensing device is physically connected to the monitoring or recording element, this often requires a cable running transcutaneously from an implanted sensor to an external monitoring or recording device. The transcutaneous cable is not only painful but also could lead to infection. Additionally, the transcutaneous cable may restrict movement and hinder the user's daily activities.
In U.S. Pat. No. 9,039,652 to Degen, entitled apparatus and methods for treating intracorporeal fluid accumulation, incorporated by reference herein in its entirety, an implantable medical sensing device is configured to generate data and a charging device is configured to download the data. The implantable device disclosed in the Degen patent includes a mechanical gear pump that is configured to be coupled to the bladder and another cavity such as the peritoneal cavity. The implantable device in Degen further describes a plurality of sensors to continually monitor pressure, temperature, humidity, charge status, pump status, patient movement and other environmental and system related parameters. The plurality of sensors may communicate wirelessly with the charging device only when in close proximity. The charging device may then relay this information to a physician's computer.
Devices generally require that the monitoring or recording device be in close proximity to an implantable device. Considering that the implantable device will frequently be out of range of the monitoring and recording device, data may not be uploaded to the monitoring or recording device continuously. Accordingly, the implantable sensing device is required to include complex circuitry and memory for storing data between uploads.
Yet another drawback of these devices is that they often do not generate operational parameters to track the performance of the implanted machinery, such as an insulin pump. For example, while a Continuous Glucose Monitoring system may generate data regarding the patient's glucose levels, such systems do not measure insulin pump parameters, leaving the performance of the pump in question. Such data, if available, could be compared to the performance of the insulin pump to better optimize and understand the pump's effect on the body.
In view of the above-noted drawbacks of previously-known systems, it would be desirable to provide methods and systems for managing and analyzing physiological and operational data generated by an implantable device using a number of other computing devices not necessarily located in close proximity to the implantable device.
The present disclosure overcomes the drawbacks of the previously-known systems having an implantable medical device by providing systems and methods for managing, reviewing and analyzing data generated by an implantable device configured to communicate wirelessly with a variety of communication devices including a remote data analyst device.
In accordance with the principles of the present invention, an exemplary system may include an implantable device to be implanted into a patient, a charging device for charging and/or communicating with the implantable device, a remote server configured to communicate with the implantable device and/or the charging device, a monitoring and control device and optionally, a mobile device, each of which may be in communication with the implantable device, the charging device, and/or the remote server, as well as each other. The system may further include a data analyst device in communication with at least the remote server.
The implantable device may have a microprocessor, a communication unit, and a plurality of sensors. The implantable device may generate operational data and physiological data and extract biomarkers based on information sensed by one or more sensors of the plurality of sensors. The operational data and physiological data may be processed using the microprocessor and communicated to other devices within the system using the communication unit. The implantable device may communicate with other devices in the system through communications with the charging device. In this manner, the implantable device may communicate operational data and/or physiological data to the charging device and the charging device may then send the data to other devices in the system. In this same way, other devices in the system may send operational parameters and/or instructions to the implantable device by relaying that information through the charging device. The communication unit of the implantable device may communicate with the charging device using any number of well-known wireless communication technologies. The other devices within the system may communicate with the charging device using any number of well-known wireless or wired communication technologies.
Alternatively, the implantable device may communicate directly to other devices within the system, without relaying communications through the charging device, by communicating wirelessly with these other devices. For example, the monitoring and control device and/or a mobile device may receive physiological and/or operational data from the implantable device. Wireless communication may be enabled by any number of well-known wireless communication technologies. In this manner, the implantable device may communicate operational data and/or physiological data to the other devices within the system and similarly the other devices within the system may wirelessly communicate operational parameters and/or instructions to the implantable device.
Whether the charging device is used as a relay or the implantable device communicates directly with the other devices in the system using wireless technology, the remote server may receive physiological and/or operational data. The data analyst device may access and download operational data and/or physiological data including biomarker data from the remote server. The data analyst device may be configured to analyze operational and/or physiological data and generate analyst data. The analyst data may include trends in the data and may compare the operational and/or physiological data to past data received from that individual's implantable device and/or to data from other implantable devices. The data also may be compared to predetermined or calculated thresholds. The analyst data may be communicated to the remote server and saved on the remote server for retrieval by the charging device, the monitoring and control device and/or the mobile device. The data analyst device also may generate a warning message containing a medical diagnosis or indication of a high risk of a medical condition, for example, and communicate the warning message to the charging device, the monitoring and control device, and/or the mobile device.
The implantable device also or alternatively may be programmed to analyze the operational and/or physiological data including biomarker data. For example, the implantable device may compare operational and/or physiological data to predetermined thresholds programmed into the implantable device. If the operational and/or physiological data exceeds or is otherwise inconsistent with the predetermined threshold, the implantable device may communicate a warning message to one or more of the other devices in the system.
The system of the present disclosure includes systems and methods for monitoring and analyzing physiological and/or operational data generated by an implantable medical device. In addition to an implantable device, an exemplary system constructed in accordance with the principles of the present invention may include a charging device, a patient's mobile communication device, a physician's monitoring and control device, and one or more remote servers. The one or more remote servers further may be in communication with one or more data analyst devices for accessing the operational and/or physiological data from the remote server and analyzing the operational and/or physiological data. The system may be configured to alert the physician and/or the patient of a medical condition or operational anomaly based on analysis of the physiological and/or operational data.
Data generated by implantable medical devices may be analyzed to achieve several different objectives, depending on the user group or business model. One goal may be to improve outcomes for patients with chronic diseases by delivering actionable insights to patients thereby influencing their behavior. Another goal may be to reduce healthcare cost and improve quality of life by enabling home care through provision of safe technical solutions for self-administration and remote monitoring. Another objective may be to improve outcomes, and potentially life expectancy, by delivering actionable insights to physicians based on personalized trend recognition and prediction, enabling early interventions or preventive therapeutical measures. Data generated by implantable devices may also deliver actionable insights to pharmaceutical companies based on biomarkers.
Data generated by implantable medical devices further ensures authenticity as an implantable device with a unique identifier cannot easily be removed from a patient. The data can be trusted to originate from that specific patient unlike wearable sensors which can easily be swapped between patients. Authenticity may be an important factor for new business models evolving around medical data.
Referring to
Implantable device 15 is implanted subcutaneously into the body of a patient and is configured to generate various physiological and/or operational data and communicate physiological and/or operational data to other devices within system 10. As shown in
Implantable device 15 further may include hardware for treating a medical condition subcutaneously such as a pump. Implantable device 15 may include inlet port 17 coupled to inlet catheter 18 and outlet port 19 coupled to outlet catheter 20. The pump may be an electromechanical pump designed to move fluid from one body cavity to another body cavity, e.g. a first body cavity to a second body cavity. For example, the electromechanical pump may be used for treating ascites by positioning inlet catheter 18 in a patient's peritoneal cavity and outlet catheter 20 through the wall of a patient's bladder. In this manner, the electromechanical pump may move fluid from the peritoneal cavity to the patient's bladder as disclosed in the Degen patent discussed above. It is understood that implantable device 15 alternatively or additionally may be include other hardware within the biocompatible housing.
Referring now to
Microprocessor 22 may include firmware having instructions stored on non-transitory computer readable medium configured to cause transmission of operational data and/or physiological data to any or all of charging device 40, monitoring and control device 60, mobile device 80 and/or remote server 95. Instructions also may cause implantable device 15 to receive operational instructions. Microprocessor 22 may be electrically coupled to battery 25, inductive circuit 26, radio transceiver 27, electric motor 28, infrared LED 38 and a plurality of sensors, including for example, one or more humidity sensors 29, one or more temperature sensors 30, one or more accelerometers 31, one or more pressure sensors 32, one or more respiratory rate sensors 33 and one or more heart rate sensors 34. Other sensors additionally could be included in device 15, such as flow rate sensors, ECG sensors, pH sensors, and capacity sensors for measuring the amount of a liquid in a given cavity.
Operational data is indicative of the operation of implantable device 15 and/or hardware incorporated into implantable device 15 and may be generated by sensors incorporated into implantable device 15. Physiological data is indicative of the physiological state of the patient and also may be generated by sensors incorporated into system 10. For example, one or more humidity sensors 29 may be used to measure the humidity within the implantable device housing; one or more temperature sensors 30 may be used for measuring the temperature in one or more body cavities (e.g., peritoneal cavity, pleural cavity, pericardial cavity, and/or bladder) or region of the body (e.g., abdomen) and/or for measuring the temperature within implantable device 15 housing and/or the temperature of an implantable device component such as battery 25, one or more accelerometers 31 may be used for determining whether the patient is at rest and/or for sensing the position of a patient, e.g., vertical, horizontal; one or more pressure sensors 32 may be incorporated in implantable device 15 to measure blood pressure and/or the pressure within one or more body cavities (e.g., peritoneal cavity, pleural cavity, pericardial cavity, and/or bladder); one or more respiratory rate sensors 33 may be used to sense the number of breaths taken in a given period of time; and one or more heart rate sensors 34 may be used to sense the rate at which the heart is beating over a given period of time or the heart rate variation. Other sensors such as flow rate sensors, pH sensors and capacity sensors may be used for measuring the flow rate of the pump inlet and the pump outlet from which fluid viscosity may also be derived if the flow measurement is combined with pressure sensor measurements, the acidity of fluids within the body, and the degree to which a cavity is filled with fluid, respectively.
Examples of physiological data may include sensed data associated with the physiology of the patient such as temperature data associated with the one or more body cavities, accelerometer data associated with, for example, heart rate, respiratory rate and/or, pressure data associated with blood pressure and/or the one or more body cavities, respiratory rate data, and heart rate data, flow rate data associated with the one or more body cavities, pH data associated with bodily fluid pumped by the implantable device, and capacity data associated with the one or more body cavities. Physiological data may include biomarker data—measurable data indicative of a biological state or condition. For example, the viscosity of ascites in patients with liver disease may act as a biomarker indicative of an infection. Data gathered from multiple sensors within the patient may be combined to result in an effective biomarker. For example, temperature data in combination with ascites viscosity data may be combined to result an even more reliable indicator of an existing or developing infection. Examples of operational data may include data associated with the implantable device such as humidity data associated with the implantable device, temperature data associated with the implantable device, pressure data associated with the implantable device, flow rate data associated with the implantable device and may also include data related to the pump such as RPM data, efficiency data, run-time data, etc. In some cases, operational parameters may even serve as an indirect measurement of physiological parameters. For example, measurement of the motor torque of a pump can be used, in combination with other measured parameters, to determine fluid viscosity based on flow resistance.
Inductive circuit 26 may be electrically coupled to coil 35 to receive energy transmitted from charging device 40. Transceiver 27 may incorporate wireless communication unit 37 and may be coupled to antenna 36. Wireless communication unit 37 may be communication circuitry, such as a chipset, conforming to one or more wireless telephony/cellular standards such as GSM, LTE, CDMA, and/or other communication standards such as BLUETOOTH™, Bluetooth low energy, ZigBee, IEEE802.15, NFC, any IEEE 802.11 wireless standard such as Wi-Fi or Wi-Fi Direct or any other wireless standard comprising optical, acoustical or conductive intracorporal principles. All of the components depicted in
As shown in
Referring now to
Microprocessor 41 also may execute firmware stored in nonvolatile memory 42 that controls communications and/or charging of the implantable device. Microprocessor 41 is configured to transfer and store data, such as physiological data, operational data, and/or event logs, uploaded to charging device 40 from implantable device 15. Microprocessor 41 may include firmware having instructions stored on non-transitory computer readable medium configured for receiving command inputs from monitoring control device 60 and/or mobile device 80 and for transmitting those command inputs to implantable device 15. Microprocessor 41 also may include firmware having instructions stored on non-transitory computer readable medium configured for transmitting command inputs to implantable device 15 using input device 52 incorporated into charging device 40. Microprocessor 41 also may include firmware having instructions stored on non-transitory computer readable medium configured to cause transmission of operational data and/or physiological data to remote server 95. The instructions also may cause communication unit 50 of charging device 40 to communicate with remote server 95 over the internet and/or over via a wireless telephony regime. Furthermore, the instructions may cause the communications between remote server 95 and charging device 40 to be encrypted. Microprocessor 41 may also control and monitor various power operations of charging device 40, including operation of inductive circuit 45 during recharging of the implantable device and displaying the state of the charge, e.g. the charge rate or percentage charged.
Inductive circuit 45 is coupled to coil 53, and is configured to inductively couple with coil 35 of implantable device 15 to recharge battery 25 of implantable device 15. Energy transfer is accomplished via electromagnetic coupling of coil 53 with coil 35 in the implantable device. As will be appreciated by one of ordinary skill, an alternating current may be delivered through coil 53, which causes an electromagnetic field to be established around coil 53, which induces an alternating current in coil 35 when coil 53 and 35 are held in close proximity.
Monitoring and control device 60, shown in
Referring now to
As shown in
Referring now to
Remote server 95, as shown in
Data analyst device 100, also shown in
Data analyst device 100 may be any computing device (e.g., personal computer, laptop, tablet, smartphones, etc.) of the data analyst configured to retrieve physiological and/or operational data and analyze the data for trends and anomalies. The instructions also may cause data analyst device to generate analyst data or aid the data analyst in the generation of analyst data which may include a diagnosis a medical condition and/or an indication a heightened risk of a medical condition. The instructions run on the non-transitory computer readable medium may cause data analyst device 100 to generate a warning message when the operational data and/or physiological data exceeds preprogrammed thresholds and also may cause data analyst device 100 to communicate the warning message to the patient mobile communication device 80 and/or monitoring and control device 60. Data analyst device 100 may include components generally found on a conventional personal computing device, such as a processor, volatile and/or non-volatile memory, a user interface such as digital display, a transceiver, a battery and input and output components such as a keyboard, a mouse and a USB port.
There are at least two ways in which implantable device 15 may communicate with system 10. First, implantable device 15 may be in direct wireless communication with charging device 40 using one or more of any well-known wireless standards such as GSM, LTE, CDMA, BLUETOOTH™, Bluetooth low energy, ZigBee, NFC, or any IEEE 802.11 wireless standard such as Wi-Fi or Wi-Fi Direct or any other wireless standard comprising optical, acoustical or conductive intracorporal principles. In this first configuration, implantable device 15 may communicate with other devices in system 10 by relaying communication through charging device 40. Charging device 40 may be in either wired or wireless communication with one or more of the devices in system 10 using one or more well-known communication standards including but not limited to GSM, LTE, CDMA, BLUETOOTH™, Bluetooth low energy, ZigBee and any IEEE 802.11 wireless standard such as Wi-Fi or Wi-Fi Direct. For example, charging device 40 may connect with implantable device 15 using Wi-Fi Direct and also may make a connection with a local Wi-Fi router and connect to the internet. Through the Internet, charging device 40 may be in communication with monitoring and control device 60, mobile device 80, and/or remote server 95.
Charging device 40, monitoring and control device 60 and mobile device 80 may each be configured to run instructions stored on a non-transitory computer readable medium programmed with messaging protocols that allows each device to communicate to one another over the internet. Commands may be communicated to microprocessor 41 of charging device 40 from monitoring and control device 60 and/or mobile device 80 which may subsequently be relayed from charging device 40 to implantable device 15. In this manner, communicating with charging device 40 through the monitoring and control device 60, a clinician may communicate with implantable device 15 to set or adjust the operational parameters of implantable device 15. Upon receiving the command to set or adjust the operational parameters, implantable device 15 will set or adjust the operational parameters according to the instructions from charging device 40. Alternatively, charging device 40 may communicate with other devices within system 10 using different communication standards discussed above.
Where charging device 40 is used as a relay point between implantable device 15 and other devices of system 10, information such as physiological and/or operational data may be communicated from implantable device 15 to charging device 40 and then from charging device 40 to remote server 95 for storage on remote server 95. For example, implantable device 15 may transmit physiological and/or operational data to charging device 40. Charging device 40 may store the physiological and/or operational data and may run a programmed routine configured to transmit the stored physiological and/or operational data to remote server 95 for remote storage. The programmed routine may include instructions that permit the charging device to communicate with remote server over the internet or via a wireless telephony regime. The instructions also may cause communications from charging device 40 to be encrypted such that transmission of physiological and/or operational data is encrypted. Alternatively, charging device 40 may transmit the physiological and/or operational data to monitoring and control device 60 and/or mobile device 80 to be stored on the respective devices. In this configuration, monitoring and control device 60 and/or mobile device 80 may run a programmed routine configured to transmit the stored physiological and/or operational data to remote server 95 for remote storage. The programmed routine further may cause monitoring and control device 60 and mobile device 80 to transmit operational parameters and instructions or commands to charging device 40 to be relayed to implantable device 15.
The second way in which implantable device 15 may communicate with system 10, is by directly communicating with one or more devices in system 10 without the use of a relay device. In this configuration, communication with other devices within system 10 may be established using any of the communication standards discussed above including close range standards, such as BLUETOOTH™, Bluetooth low energy, ZigBee and Wi-Fi, and long range standards such as GSM, LTE, CDMA. It is further understood that implantable device 15 may communicate with different devices within system 10 using different communication standards as implantable device 15 may be configured to communicate using more than one communication standard. Like in the first arrangement, where charging device 40 was used as a relay, clinician may communicate with implantable device 15 to set or adjust the operational parameters of implantable device 15. Upon receiving the command to set or adjust the operational parameters, implantable device 15 will set or adjust the operational parameters according to the instructions from charging device 40.
For example, implantable device 15 may be in direct wireless communication with monitoring and control device 60 using BLUETOOTH™ or Bluetooth low energy connectivity. Monitoring and control device 60 may include non-transitory computer readable medium programmed with instructions that, when run on monitoring and control device 60 allows monitoring and control device 60 to directly communicate with implantable device 15. In this example, during patient visits, a clinician using monitoring and control device 60 may wirelessly connect to implantable device 15 to download for review, data generated by and stored on implantable device 15. Further, monitoring and control device 60 may transmit operational parameters to implantable device 15 to adjust or set operational parameters of implantable device 15 without using charging device 40 as a relay point. Where implantable device 15 includes a pump, a clinician may adjust operational parameters in the pump such as timing intervals for running the pump. Upon receiving the operational parameters, implantable device 15, e.g. the one or more processors, may adjust operation according to the received operational parameters. While in communication with implantable device 15, the clinician using monitoring and control device 60 also may download operational and/or physiological data stored on implantable device 15. In yet another example, implantable device 15 may support Wi-Fi connectivity and the clinician using monitoring and control device 60 may directly connect to implantable device 15 even when the clinician and patient are not in the same location.
Implantable device 15 also may be configured to communicate directly with mobile device 80 and/or remote server 95. Mobile device 80 and remote server 95 may each similarly include a non-transitory computer readable medium programmed with instructions that, when run on mobile device 80 and/or remote server 95 allow mobile device 80 and/or remote server 95, respectively, to directly communicate with implantable device 15. In this configuration, implantable device 15 may transmit data generated from the sensors incorporated in implantable device 15 to remote server 95 so that the sensor data is accessible for review by the data analyst device 100. Mobile device 80 and/or remote server 95 may communicate with implantable device 15 using any of the well-known methods discussed above. For example mobile device 80 and remote server 95 may have Wi-Fi compatibility and communicate with implantable device 20 via the internet. Alternatively, or in addition to, implantable device 20 may be configured to have wireless telephony capabilities and establish a connection to mobile device 80, for example, using LTE.
Whether implantable device 15 uses charging device 40 to communicate with system 10 or is in direct communication with other devices within system 10, monitoring and control device 60 and/or mobile device 80 may each have non-transitory computer readable medium and may each run instructions on the non-transitory computer readable medium to cause the monitoring and control device 60 and/or mobile device 80 to communicate with the remote server and receive from the remote server operational and/or physiological data. Specifically, monitoring and control device 60 and/or mobile device 80 may interrogate remote server 95 for new data uploaded onto remote server 95, including data generated by implantable device 15 and data generated by data analyst device 100, discussed in more detail below. For example, monitoring and control device 60 and/or mobile device 80 may be configured to manually interrogate remote server 95 to determine if analyst data has been uploaded to remote server 95.
Alternatively, monitoring and control device 60 and/or mobile device 80 may each include a non-transitory computer readable medium programmed with instructions that, when run on monitoring and control device 60 and/or mobile device 80, cause monitoring and control device 60 or mobile device 80, respectively, to automatically periodically interrogate remote server 95 for new analyst data uploaded to remote server 95 to determine, for example, whether uploaded analyst data includes a diagnosis of a medical condition and/or an indication of a high risk of a medical condition. Monitoring and control device 60 may be configured to transmit an alert to mobile device 80 upon confirmation that the analyst data includes a diagnosis of a medical condition and/or an indication of high risk of a medical condition. Data analyst device 100 and implantable device 15 also may be configured to automatically generate and transmit an alert to monitoring and control device 60 and/or mobile device 80 indicating that data has been transmitted to the server. Preferably communication between implantable device 15, charging device 40, monitoring and control device 60, mobile device 80, remote server 95 and/or data analyst device 100 is encrypted.
Referring now to
Mobile graphic user interface 85 also may output parameter status 84. Parameter status 84 may indicate the status of the measured parameter, e.g., whether the measured parameter is LOW, HIGH or OK (normal) for a given patient. For example, parameter status 84 may indicate to the patient how the measured parameter compares to pre-programmed thresholds. If the pressure reading exceeds a pre-programmed threshold, the parameter status will read “HIGH”. Similarly, if the pressure reading is below a pre-programmed threshold, the parameter status will read “LOW”. The other parameter statuses in
The data displayed on mobile graphic user interface 85 may be received from remote server 95 when mobile device 80 has established a connection with remote server 95. Alternatively, when mobile device 80 has established a direct connection with implantable device 15, the data displayed on graphic user interface 85 may be transmitted directly from implantable device 15. In yet another example, the data displayed on graphic user interface 85 may be transmitted from charging device 60. The status parameters illustrated in
Referring now to
Referring now to
Warning graphic user interface 86 may show actionable insight related to the measured physiological and/or operational data and may show a warning message related to the physiological and/or operational data. Warning graphic user interface 86 may indicate that an anomaly has been detected or may even display the measured parameter compared to the predetermined threshold. For example, analysis from implantable device 15 may detect an irregular heartbeat and upon detection, warning graphic user interface 86 may alert the patient to this anomaly. Warning graphic user interface 86 may further include a direct link to the patient's physician, either by text, email or phone. If it is possible to alleviate the condition by adjusting operational parameters, warning graphic user interface 86 may seek permission from the patient to adjust the operational parameters. Where the warning is issued by data analyst device 100 the warning message also may indicate the type of medical condition that has been detected and/or other actionable insight generated. Warning graphic user interface 86 may further include a link to the data related to the warning and/or analysis of the data. Emergency responders may simultaneously be contacted and informed of the patient's location and condition upon generation of the warning message.
Where the warning is generated by implantable device 15, mobile device 80 and/or data analyst device 100, a physician or clinician using monitoring and control device 60 may also receive an alert on monitoring and control device 60 regarding the same information displayed on warning graphic user interface 86. The alert may further include data related to the warning, actionable insight and/or a link to access the data, similar to the warning shown in
If it is possible to alleviate the condition by adjusting operational parameters, a request may be sent to the physician or clinician to adjust operational parameters of implantable device 15, and upon receiving permission, command implantable device 15 to adjust operation, either by communicating the command directly from monitoring and control device 60 to the implantable device or relaying the command through the charging device. Upon receiving the command, implantable device 15 may adjust the operational parameter or parameters. For example, the command may direct the processor of implantable device 15 to pump more or less fluid from one body cavity, e.g. peritoneal, pleural, pericardial, to another body cavity, e.g., bladder, peritoneal cavity, and/or to adjust time intervals between pumping sessions. Implantable device 15 may send a similar alert to any number of devices within the system including data analyst device 100. An alert sent to data analyst device 100 from implantable device 15 may further include the most recent data measured by the implantable device relating to the warning being transmitted, allowing the remote analyst to immediately access and analyze the relevant data.
Referring now to
Clinician graphic user interface 71 shown in
Similarly, operational data box 74 may display operational data such as operational measurements 77 which may include displacement, temperature, duration and voltage measurements or any other measurements related to performance of the implantable pump 15 or performance of hardware incorporated into the implantable pump. Operational data box 74, like physiological data box 73, may show current operational measurements of implantable device 15 or measurements archived by implantable device 15, remote server 95, charging device 40 and/or monitoring and control device 60. For example, operational data box 74 may show operational parameters such as the current measurements for the hardware in implantable device 15, e.g., current displacement of an incorporated pump, current temperature of a battery, current flow speed, current voltage measurements, or any other current measurement sensed by implantable device 15 indicative of the operation of implantable device 15 or hardware incorporated in implantable device 15.
Operational box 74 also or alternatively may show operational parameters such as average displacement or a previously recorded displacement measurements, average temperature or a previously recorded temperature measurements, average flow speed or a previously recorded flow speed measurements, average voltage or a previously recorded voltage measurements or any other average or previously recorded measurement sensed by implantable device 15 indicative of the operation of implantable device 15 or hardware incorporated in implantable device 15. Operational data box 74 may further include operational data measurements such as battery and/or pump temperature, pump RPMs, humidity within the housing of implantable device 15, or any other measurements related to the performance or operation of implantable device 15 or hardware incorporated into implantable device 15.
Clinician graphic user interface 71 may also show other parameters and data amounting to actionable insight. For example, clinician graphic user interface 71 may include parameters calculated from measured physiological and/or operational parameters such as viscosity of a fluid within a body cavity or burn rate of calories. Actionable insight garnered from measured physiological and/or operational parameters may be generated using algorithms programmed into implantable device 15, monitoring and control device 60, mobile device 80, or data analyst device 100. Alternatively, or in addition to, a data analyst may analyze measured physiological and/or operational parameters on data analyst device 100 and generate actionable insight by comparing data to known trends or correlations.
Using clinician graphic user interface 71, a clinician or physician may adjust the performance of implantable device 15 by altering operational settings which may also appear in operational data box 74. For example, a clinician may change the desired displacement of the pump to 0.05. This change may be immediately communicated to implantable device 15 either through direct communication between implantable device 15 and monitoring and control device 60 or by using charging device 40 as a relay. Other examples of settings that a clinician or physician may adjust include the timing of pump activation, duration of pumping, or any other setting that may control the operation of implantable device 15 or hardware incorporated into implantable device 15.
Physician graphic user interface 71 may be customizable such that the physician may decide which data to display. The physician may choose to display any combination of archived data and current data. For example, the physician may customize the graphic user interface to display pressure averages over a period of time, e.g., the last six months, or may choose to display pressure highs and lows instead. Alternatively, a physician may customize the graphic user interface to only show select physiological and/or operational data but not others, e.g., the pressure, temperature and heart rate, but not the respiratory rate.
Clinician graphic user interface 71 also may generate one or more graphic representations of the data generated by implantable device 15. Graphic representation 78 may be generated by the physician to analyze a given parameter over a certain period of time. Graphic presentation 78 may include a flow chart(s), a pie chart(s), a bar graph(s), etc., representing measured physiological and/or operational data. The physician may choose to compare the patient's respiratory rate against the patient's heart rate for a given period of time to better understand the patient's oxygen saturation levels. As is discussed in more detail below, graphical analysis also may be generated by a dedicated analyst remotely and may be viewed by the clinician on graphic user interface 71. Similarly, tables and various other well-known data comparison methods may be generated remotely by dedicated analysts at data analyst devices and accessed by the clinician using graphic user interface 71. Clinician graphic user interface 71 may display additional information such as that shown in U.S. Pat. No. 9,039,652 to Degen, the entire contents of which are incorporated herein by reference.
Clinician graphic user interface 71 also may communicate various messages such as warnings 79 to the physician. Warnings or alerts may be generated by implantable device 15, mobile device 80 and/or data analyst device 100. For example, where implantable device 15 has a pump, clinician graphic user interface 71 may display a warning that the pump experienced a malfunction such as a clog and may even suggest methods for fixing the problem such as reversing flow direction. In another example, monitoring and control device 60 may run instructions stored on a non-transitory computer readable medium programmed to automatically compare physiological parameters and/or operational parameters against predetermined thresholds and to automatically generate a warning when an anomaly is discovered, e.g. when the measured parameters are above or below predetermined thresholds and/or are outside of a predetermined threshold range(s), much like the process shown in steps 152 to 155 in
Clinician graphic user interface 71 may support a messaging protocol established on monitoring and control device 60 and/or mobile device 80. The messaging protocol may permit a physician or clinician to communicate a message and/or a warning to the patient by transmitting the message and/or warning to mobile device 80. For example, a physician may notice an unusual physiological and/or operational parameter or trend and may send a message to mobile device 80 to, for example, ask the patient how he or she feels or if he or she is experiencing certain symptoms or discomfort. Using the messaging protocol, the patient may inform the physician of his current condition using mobile device 80. If the physician instead notices from the physiological data that the patient is currently experiencing a medical event or is about to experience a medical event, the physician may immediately message the patient with instructions on what to do next. For example, the message may direct the patient to immediately cease all physical activity. Alternatively or additionally, the physician may message emergency services using clinician graphic user interface 71 and inform emergency services of the patient's location and condition.
Referring now to
Data analyst device 100 also may establish a connection with other devices within the system and retrieve physiological and/or operational data for the other devices. For example, a remote analyst using data analyst device 100 may retrieve physiological data from implantable device 15, analyze the received physiological data, and transmit data analysis to a remote server 95 for download by other devices in the system. As another example, a remote analyst using data analyst device 100 may retrieve operational data from implantable device 15, analyze the received operational data, and transmit data analysis to a remote server 95 for download by other devices in the system. As explained above, the data analysis may include actionable insight that may provide a patient, caretaker, physician or clinician enough information to determine how to act or what measures to take to address a problem or concern.
Referring now to
Using analyst graphic user interface 101, data analyst may review and analyze data, e.g., operational and/or physiological data generated by implantable device 15. Analyst also may use both current data and archived data to observe trends, predict trends, identify a medical condition and/or risk of a medical condition and produce actionable insight. Data from multiple patients may be anonymously or non-anonymously compared against each other. For example, data generated from a son's implantable device may be compared to data generated by a father's implantable device to better understand the effects of a hereditary condition where both patients have the same diagnosis. Alternatively, data from multiple patients known to have developed the same condition may be collectively analyzed to search for a trend among the data. Such a trend may help prevent or diagnose the medical condition in others who share the same trend.
In an exemplary embodiment, a data analyst may detect early warning signs of a heart attack by analyzing data generated by respiratory rate sensors, heart rate sensors, ECG sensors, blood pressure sensors, and/or temperature sensors. The data generated from these sensors may be compared to trends of individuals who have had heart attacks to determine whether a heart attack is imminent or likely. Similarly, using sensors including respiratory rate sensors, heart rate sensors, blood pressure sensors and/or temperature sensors, a data analyst may detect early signs of heart failure.
Specifically, from the respiratory rate sensor, shortness of breath may be detected in addition to chronic coughing or wheezing; from the blood pressure sensor, high blood pressure may be detected; from the temperature sensor, abnormalities in the patient's temperature may be detected; and from the heart rate sensor, an increased heart rate may be detected. Additionally, a third heart sound known as ventricular gallop or a protodiastolic gallop may also be detected which is an additional indicator of heart failure. Data analyst device 100 may run instructions stored on a non-transitory computer readable medium programmed to automatically compare data generated by implantable device 15 to various trends to determine the risk of a given condition or medical event. If a risk of a medical condition or event is determined to be high, the instructions may also generate a warning of the risk and automatically store the warning on remote server 95 for retrieval by mobile device 80 and/or monitoring and control device 60 and/or may automatically transmit the warning to mobile device 80 and/or monitoring and control device 60.
Analyst graphic user interface 101 shown in
Analyst also may wish to compare certain data to archived data by generating a table. One or more tables may display one or more measured parameters from implantable device 15 over time including select measurements such as highs or lows over a time period. For example, table 107 illustrates the highest pressure measurement and the highest heart rate measurement for each month. In the snapshot shown, for the month of April, the highest pressure measured is 1.25 mmHg and the highest heart rate measured is 113 beats per minute. Analyst graphic user interface 101, arranged in the manner shown, allows the analyst to compare table 107 to graphic representations 104, 105 and 106. It is understood that an analyst may use any number of analytic tools that are well known in the art for analyzing the data generated by the implantable device.
The data analysis generated by data analyst device 100 may be formatted in any number of well-known ways and transmitted to and stored on remote server 95. For example, the results may be in the form of a report or a spreadsheet. Alternatively, the analyst may simply save the graphical representations or tables generated on data analyst device 100 to remote server 95. As explained above, in addition to transmitting the data analysis to remote server 95, a data analyst using analyst device 100 may transmit the results directly to mobile device 80 and monitoring and control device 60 and may generate an alert and communicate the alert to monitoring and control device 60 and/or mobile device 80 when data has been uploaded to remote server 95.
As discussed above and in accordance with the present disclosure, communication between devices in system 10 may be facilitated by a number of well-known techniques. While all devices within system 10 may be in communication with one another, it is understood that some devices may be in communication with less than the number of total devices in the system. For example, some devices of system 10 may be connected to the internet and others may make one-to-one connections to other devices that are connected to the internet using one or more of the well-known methods.
While various illustrative embodiments of the invention are described above, it will be apparent to one skilled in the art that various changes and modifications may be made therein without departing from the invention. For example, system 10 shown in
This application claims the benefit of the filing date of U.S. Provisional Patent Application No. 62/380,284 filed on Aug. 26, 2016, the disclosure of which is incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3540451 | Zenman | Nov 1970 | A |
| 3575158 | Summers | Apr 1971 | A |
| 3654932 | Newkirk et al. | Apr 1972 | A |
| 3810259 | Summers | May 1974 | A |
| 3910283 | Leveen | Oct 1975 | A |
| 4014346 | Brownlee et al. | Mar 1977 | A |
| 4083786 | Tsuda et al. | Apr 1978 | A |
| 4240434 | Newkirk | Dec 1980 | A |
| 4261341 | Hakim et al. | Apr 1981 | A |
| 4354933 | Lester | Oct 1982 | A |
| 4416657 | Berglund | Nov 1983 | A |
| 4419094 | Patel | Dec 1983 | A |
| 4475898 | Brodner et al. | Oct 1984 | A |
| 4475899 | Muller | Oct 1984 | A |
| 4490137 | Moukheibir | Dec 1984 | A |
| 4553956 | Muller | Nov 1985 | A |
| 4610625 | Bunn | Sep 1986 | A |
| 4610658 | Buchwald et al. | Sep 1986 | A |
| 4615691 | Hakim et al. | Oct 1986 | A |
| 4618343 | Polaschegg | Oct 1986 | A |
| 4632435 | Polyak | Dec 1986 | A |
| 4657530 | Buchwald et al. | Apr 1987 | A |
| 4687471 | Twardowski et al. | Aug 1987 | A |
| 4725207 | Buchwald et al. | Feb 1988 | A |
| 4772257 | Hakim et al. | Sep 1988 | A |
| 4779614 | Moise | Oct 1988 | A |
| 4784638 | Ghajar et al. | Nov 1988 | A |
| 4850955 | Newkirk et al. | Jul 1989 | A |
| 4880414 | Whipple | Nov 1989 | A |
| 4904236 | Redmont et al. | Feb 1990 | A |
| 4963129 | Rusch | Oct 1990 | A |
| 4963133 | Whipple | Oct 1990 | A |
| 5011472 | Aebischer et al. | Apr 1991 | A |
| 5021048 | Buckholtz | Jun 1991 | A |
| 5037385 | O'Byrne | Aug 1991 | A |
| 5057075 | Moncrief et al. | Oct 1991 | A |
| 5071408 | Ahmed et al. | Dec 1991 | A |
| 5078688 | Lobodzinski et al. | Jan 1992 | A |
| 5147281 | Thornton et al. | Sep 1992 | A |
| 5167615 | East et al. | Dec 1992 | A |
| 5180387 | Ghajar et al. | Jan 1993 | A |
| 5254084 | Geary | Oct 1993 | A |
| 5356386 | Goldberg et al. | Oct 1994 | A |
| 5385541 | Kirsch et al. | Jan 1995 | A |
| 5387188 | Watson | Feb 1995 | A |
| 5387192 | Glantz et al. | Feb 1995 | A |
| 5391143 | Kensey | Feb 1995 | A |
| 5395350 | Summers | Mar 1995 | A |
| 5397354 | Wilk et al. | Mar 1995 | A |
| 5472323 | Hirabayashi et al. | Dec 1995 | A |
| 5474683 | Bryant et al. | Dec 1995 | A |
| 5575770 | Melsky et al. | Nov 1996 | A |
| 5589197 | Shockley et al. | Dec 1996 | A |
| 5629025 | Shockley et al. | May 1997 | A |
| 5631025 | Shockley et al. | May 1997 | A |
| 5637083 | Bertrand et al. | Jun 1997 | A |
| 5725506 | Freeman et al. | Mar 1998 | A |
| 5830172 | Leveen et al. | Nov 1998 | A |
| 5902336 | Mishkin | May 1999 | A |
| 5944684 | Roberts et al. | Aug 1999 | A |
| 5947911 | Wong et al. | Sep 1999 | A |
| 5980478 | Gorsuch et al. | Nov 1999 | A |
| 5989207 | Hughes | Nov 1999 | A |
| 6007511 | Prywes | Dec 1999 | A |
| 6017355 | Hessel et al. | Jan 2000 | A |
| D420738 | Carter et al. | Feb 2000 | S |
| 6022333 | Kensey | Feb 2000 | A |
| 6132405 | Nilsson et al. | Oct 2000 | A |
| 6132415 | Finch et al. | Oct 2000 | A |
| 6162238 | Kaplan et al. | Dec 2000 | A |
| 6162487 | Darouiche | Dec 2000 | A |
| 6193684 | Burbank et al. | Feb 2001 | B1 |
| 6214802 | Nakamura et al. | Apr 2001 | B1 |
| 6245039 | Brugger et al. | Jun 2001 | B1 |
| 6248726 | Alsop et al. | Jun 2001 | B1 |
| 6254567 | Treu et al. | Jul 2001 | B1 |
| 6264601 | Jassawalla et al. | Jul 2001 | B1 |
| 6264625 | Rubenstein et al. | Jul 2001 | B1 |
| 6417750 | Sohn | Jul 2002 | B1 |
| 6436087 | Lewis et al. | Aug 2002 | B1 |
| 6533733 | Ericson et al. | Mar 2003 | B1 |
| 6554822 | Holschneider et al. | Apr 2003 | B1 |
| 6585681 | Brugger et al. | Jul 2003 | B2 |
| 6613095 | Levin | Sep 2003 | B1 |
| 6656227 | Levin | Dec 2003 | B2 |
| 6689085 | Rubenstein et al. | Feb 2004 | B1 |
| 6814547 | Childers et al. | Nov 2004 | B2 |
| 6827682 | Bugge et al. | Dec 2004 | B2 |
| 6845267 | Harrison et al. | Jan 2005 | B2 |
| 6846168 | Davis et al. | Jan 2005 | B2 |
| 6854467 | Boekstegers | Feb 2005 | B2 |
| 6875192 | Saul et al. | Apr 2005 | B1 |
| 6887214 | Levin et al. | May 2005 | B1 |
| 6894456 | Tsukamoto | May 2005 | B2 |
| 6905474 | Borgesen | Jun 2005 | B2 |
| 6911014 | Wentling et al. | Jun 2005 | B2 |
| 6921378 | O'Keefe et al. | Jul 2005 | B2 |
| 6926691 | Miethke | Aug 2005 | B2 |
| 6939111 | Huitt et al. | Sep 2005 | B2 |
| 6945949 | Wilk | Sep 2005 | B2 |
| 6949080 | Wolf et al. | Sep 2005 | B2 |
| 6953481 | Phelps et al. | Oct 2005 | B2 |
| 6955655 | Burbank et al. | Oct 2005 | B2 |
| 6960179 | Gura | Nov 2005 | B2 |
| 6964652 | Guiles et al. | Nov 2005 | B2 |
| 6974445 | Stergiopulos | Dec 2005 | B2 |
| 6976973 | Ruddell et al. | Dec 2005 | B1 |
| 6979351 | Forsell et al. | Dec 2005 | B2 |
| 6981964 | Rioux et al. | Jan 2006 | B2 |
| 6994700 | Elkins et al. | Feb 2006 | B2 |
| 7011095 | Wolf et al. | Mar 2006 | B2 |
| 7017340 | Chicky | Mar 2006 | B2 |
| 7025739 | Saul | Apr 2006 | B2 |
| 7025742 | Rubenstein et al. | Apr 2006 | B2 |
| 7063679 | Maguire et al. | Jun 2006 | B2 |
| 7169303 | Sullivan et al. | Jan 2007 | B2 |
| 7195608 | Burnett | Mar 2007 | B2 |
| 7311690 | Burnett | Dec 2007 | B2 |
| 7335179 | Burnett | Feb 2008 | B2 |
| 7621886 | Burnett | Nov 2009 | B2 |
| 7670332 | O'Keefe et al. | Mar 2010 | B2 |
| 7909790 | Burnett | Mar 2011 | B2 |
| 8012118 | Curtin et al. | Sep 2011 | B2 |
| 8202248 | Burnett et al. | Jun 2012 | B2 |
| 8241239 | Solomon et al. | Aug 2012 | B2 |
| 8394048 | Burnett | Mar 2013 | B2 |
| 8398577 | Burnett | Mar 2013 | B2 |
| 8517973 | Burnett | Aug 2013 | B2 |
| 8585635 | Degen et al. | Nov 2013 | B2 |
| 8641659 | Soykan | Feb 2014 | B2 |
| 8771221 | Burnett | Jul 2014 | B2 |
| 8882699 | Burnett | Nov 2014 | B2 |
| 8961448 | Forsell | Feb 2015 | B2 |
| 8992456 | Powell | Mar 2015 | B1 |
| 9039652 | Degen | May 2015 | B2 |
| 9138523 | Burnett et al. | Sep 2015 | B2 |
| 9144660 | Degen | Sep 2015 | B2 |
| 9149613 | Degen et al. | Oct 2015 | B2 |
| D743542 | Degen | Nov 2015 | S |
| D743543 | Degen | Nov 2015 | S |
| 9339636 | Khan et al. | May 2016 | B1 |
| 9381301 | Lattanzio et al. | Jul 2016 | B2 |
| 9421347 | Burnett | Aug 2016 | B2 |
| 9577459 | Degen et al. | Feb 2017 | B2 |
| 9675327 | Johnson et al. | Jun 2017 | B2 |
| 9913968 | Burnett | Mar 2018 | B2 |
| 9956336 | Degen et al. | May 2018 | B2 |
| 20020013545 | Soltanpour et al. | Jan 2002 | A1 |
| 20020022793 | Bertrand et al. | Feb 2002 | A1 |
| 20020123715 | Sorenson et al. | Sep 2002 | A1 |
| 20030114787 | Gura | Jun 2003 | A1 |
| 20030114898 | Von Arx | Jun 2003 | A1 |
| 20030163079 | Burnett | Aug 2003 | A1 |
| 20030171710 | Bassuk | Sep 2003 | A1 |
| 20030217962 | Childers et al. | Nov 2003 | A1 |
| 20030220606 | Busby et al. | Nov 2003 | A1 |
| 20040018228 | Fischell et al. | Jan 2004 | A1 |
| 20040049288 | Levin | Mar 2004 | A1 |
| 20040098113 | Forsell | May 2004 | A1 |
| 20040126775 | Altieri et al. | Jul 2004 | A1 |
| 20040147871 | Burnett | Jul 2004 | A1 |
| 20050131340 | Sorenson et al. | Jun 2005 | A1 |
| 20050273034 | Burnett | Dec 2005 | A1 |
| 20060010014 | Brown | Jan 2006 | A1 |
| 20060024200 | Nishikiori et al. | Feb 2006 | A1 |
| 20060036208 | Burnett | Feb 2006 | A1 |
| 20060058731 | Burnett et al. | Mar 2006 | A1 |
| 20060094984 | Wood et al. | May 2006 | A1 |
| 20070055197 | Shakir | Mar 2007 | A1 |
| 20070106205 | Connell et al. | May 2007 | A1 |
| 20070228071 | Kamen | Oct 2007 | A1 |
| 20070255345 | Krause | Nov 2007 | A1 |
| 20070299317 | Hoyme et al. | Dec 2007 | A1 |
| 20080024294 | Mazar | Jan 2008 | A1 |
| 20080108935 | Nyhart, Jr. | May 2008 | A1 |
| 20080154173 | Burnett | Jun 2008 | A1 |
| 20080214983 | Mauge et al. | Sep 2008 | A1 |
| 20080230450 | Burbank et al. | Sep 2008 | A1 |
| 20090069642 | Gao et al. | Mar 2009 | A1 |
| 20090171241 | Garcia et al. | Jul 2009 | A1 |
| 20090198174 | Childers et al. | Aug 2009 | A1 |
| 20090222065 | Dlugos, Jr. | Sep 2009 | A1 |
| 20090275805 | Lane | Nov 2009 | A1 |
| 20090275924 | Lattanzio et al. | Nov 2009 | A1 |
| 20090318844 | Burnett | Dec 2009 | A1 |
| 20100010832 | Boute et al. | Jan 2010 | A1 |
| 20100022902 | Lee | Jan 2010 | A1 |
| 20100114012 | Sandford et al. | May 2010 | A1 |
| 20100185225 | Albrecht | Jul 2010 | A1 |
| 20100215375 | Reams | Aug 2010 | A1 |
| 20100222846 | Goetz | Sep 2010 | A1 |
| 20100234793 | Dacey, Jr. et al. | Sep 2010 | A1 |
| 20100249692 | Dacey, Jr. | Sep 2010 | A1 |
| 20100312163 | Forsell | Dec 2010 | A1 |
| 20100312164 | Forsell | Dec 2010 | A1 |
| 20110025261 | Bersenev | Feb 2011 | A1 |
| 20110034986 | Chou et al. | Feb 2011 | A1 |
| 20110172545 | Grudic | Jul 2011 | A1 |
| 20110184339 | Tan | Jul 2011 | A1 |
| 20110184340 | Tan et al. | Jul 2011 | A1 |
| 20110202041 | Forsell | Aug 2011 | A1 |
| 20110291613 | Rosik et al. | Dec 2011 | A1 |
| 20120035255 | Schatz et al. | Feb 2012 | A1 |
| 20120041279 | Freeman | Feb 2012 | A1 |
| 20120209085 | Degen | Aug 2012 | A1 |
| 20120209165 | Degen | Aug 2012 | A1 |
| 20120235503 | Kesler | Sep 2012 | A1 |
| 20120235634 | Hall | Sep 2012 | A1 |
| 20130199998 | Kelly et al. | Aug 2013 | A1 |
| 20130211322 | Degen | Aug 2013 | A1 |
| 20130289334 | Badstibner | Oct 2013 | A1 |
| 20130303971 | Budgett et al. | Nov 2013 | A1 |
| 20140005743 | Giuffrida | Jan 2014 | A1 |
| 20140012180 | Levin et al. | Jan 2014 | A1 |
| 20140066841 | Degen | Mar 2014 | A1 |
| 20140074180 | Heldman | Mar 2014 | A1 |
| 20140098627 | Mochizuki | Apr 2014 | A1 |
| 20140200481 | Johnson | Jul 2014 | A1 |
| 20140266022 | Degen | Sep 2014 | A1 |
| 20140275727 | Bonde | Sep 2014 | A1 |
| 20140275827 | Gill | Sep 2014 | A1 |
| 20150088090 | Macy, Jr. | Mar 2015 | A1 |
| 20160000984 | Burnett et al. | Jan 2016 | A1 |
| 20160022971 | Degen et al. | Jan 2016 | A1 |
| 20160087687 | Kesler | Mar 2016 | A1 |
| 20160151553 | Bonde | Jun 2016 | A1 |
| 20160183819 | Burnett | Jun 2016 | A1 |
| 20160303313 | Burke | Oct 2016 | A1 |
| 20160331947 | Burnett | Nov 2016 | A1 |
| 20170079760 | Newman | Mar 2017 | A1 |
| 20170128654 | Feld | May 2017 | A1 |
| 20170136221 | Budgett et al. | May 2017 | A1 |
| 20170173262 | Veltz | Jun 2017 | A1 |
| 20170281848 | Axelsson et al. | Oct 2017 | A1 |
| 20180056050 | Degen et al. | Mar 2018 | A1 |
| 20180060520 | Degen et al. | Mar 2018 | A1 |
| 20180344917 | Inhaber | Dec 2018 | A1 |
| Number | Date | Country |
|---|---|---|
| 101485683 | Jul 2009 | CN |
| 201930383 | Aug 2011 | CN |
| 0 366 389 | May 1990 | EP |
| 0 980 685 | Feb 2000 | EP |
| 1 362 605 | Nov 2003 | EP |
| 1 517 718 | Mar 2005 | EP |
| 1 539 294 | Jun 2005 | EP |
| 2 244 667 | Nov 2010 | EP |
| 2 676 638 | Dec 2013 | EP |
| 2 350 794 | Dec 2000 | GB |
| H04-327857 | Nov 1992 | JP |
| 2000-072658 | Mar 2000 | JP |
| A2004-513681 | May 2004 | JP |
| A2005-171892 | Jun 2005 | JP |
| WO-9741799 | Nov 1997 | WO |
| WO-9816171 | Apr 1998 | WO |
| WO-9934116 | Jul 1999 | WO |
| WO-0207596 | Jan 2001 | WO |
| WO-03072166 | Sep 2003 | WO |
| WO-2004012806 | Feb 2004 | WO |
| WO-2004105730 | Dec 2004 | WO |
| WO-2005018708 | Mar 2005 | WO |
| WO-2006023589 | Mar 2006 | WO |
| WO-2008055248 | May 2008 | WO |
| WO-2009091267 | Jul 2009 | WO |
| WO-2009096854 | Aug 2009 | WO |
| WO-2010077851 | Jul 2010 | WO |
| WO-2012112664 | Aug 2012 | WO |
| WO-2013122580 | Aug 2013 | WO |
| WO-2013166038 | Nov 2013 | WO |
| WO-2014140277 | Sep 2014 | WO |
| WO-2015108782 | Jul 2015 | WO |
| WO-2018037359 | Mar 2018 | WO |
| Entry |
|---|
| “Pump implant for cancer patients ‘is a game-changer’ for thousands”, The Times, Health News, p. 11, Jan. 18, 2013. |
| Bellot, Pablo, et al., Automated low flow pump system for the treatment of refractory ascites: A multi-center safety and efficacy study, Journal of Hepatology, 58(5):922-927 (2013). |
| Fukuda, et al., Survivin, a cancer target with an emerging role in normal adult tissues, Mol. Cancer Ther., 5(5):1087-1098 (2006). |
| International Search Report and Written Opinion dated Apr. 16, 2015 in Int'l PCT Patent Appl. No. PCT/US2015/010840. |
| Medtronic Reveal Ling™ LNQ11, Insertable Cardiac Monitor, Clinician Manual, 98 pages (2015). |
| Rosenblit et al., “Peritoneal-urinary drainage for treatment of refractory ascites: a pilot study,” J. Vascular & Interv. Radiology, 9(6):998-1005 (Nov./Dec. 1998). |
| www.medtronic.com/us-en/patients/treatments-therapies/fainting-heart-monitor/reveal-linq-icm.html (May 2017) (Accessed Nov. 27, 2017). |
| Costanzo et al., “Early Ultrafiltration in Patients with Decompensated Heart Failure and Diuretic Resistance,” J. Am. Coll. Cardiol., 46(11):2047-2051 (2005). |
| Doty, et al., Effect of Increased Renal Venous Pressure on Renal Function, J. Trauma., 47(6):1000-3 (1999). |
| Francois, et al., Peritoneal Dialysis for Chronic Congestive Heart Failure, Blood Purif., 40(1):45-52 (2015). |
| Hecking, et al., Sodium Setpoint and Sodium Gradient: Influence on Plasma Sodium Change and Weight Gain, Am J. Nephrol, 33(1):39-48 (2011). |
| Houlberg et al., “Terminal Right Heart Failure Due to Complex Congenital Cardiac Disease Successfully Managed by Home Peritoneal Drainage,” Cardiol. Young, 13(6):568-70 (2003). |
| International Search Report & Written Opinion dated Jan. 4, 2018 in Int'l PCT Patent Appl. Serial No. PCT/IB2017/055092. |
| International Search Report & Written Opinion dated Mar. 18, 2013 in Int'l PCT Patent Appl. Serial No. PCT/US2012/025188. |
| Kenny, Intra-Abdominal Pressure and Renal Function: The Venous Side of the Road, PulmCCM, Critical Carer, GI and Nutrition, Jul. 14, 2016, accessed on line on Mar. 27, 2017 at http://pulmccm.org/main/2016/critical-care-review/intra-abdominal-pressure-renal-function/. |
| McCausland, et al., Dialysate Sodium, Serum Sodium and Mortality in Maintenance Hemodialysis, 27(4):1613-1618 (2012). |
| Munoz Mendoza, et al., Dialysate sodium and sodium gradient in maintenance hemodialysis: a neglected sodium restriction approach? Nephrol Dial Transplant, 26(4):1281-1287 (2011). |
| Nakayama, et al., Clinical Effect of Low Na Concentration Dialysate (120mEq/L) for CAPD Patients, Abstracts of the XIII Annual CAPD Conference, Peritoneal Dialysis International, vol. 13, Supplement 1, 1993. |
| Ortiz et al., “Long-Term Automated Peritoneal Dialysis in Patients with Refractory Congestive Heart Failure,” Advances in Peritoneal Dialysis, 19:77-80 (2003). |
| International Search Report dated Sep. 16, 2008 in Int'l PCT Patent Appl. Serial No. PCT/US2005/029305. |
| Puttagunta, et al., Peritoneal Dialysis for Heart Failure, Peritoneal Dialysis International, 35(6):645-649 (2015). |
| Rosenblit et al., “Peritoneal-Urinary Drainage for Treatment of Refractory Ascites: A Pilot Study,” J. of Vascular & Interventional Radiology, 9(6):998-1005 (1998). |
| Ruhi, et al., Use of Peritoneal Ultrafiltration in the Elderly Refractory Congestive Heart Failure Patients, Int. Urol. and Nephrol., 44(3):963-969 (2012). |
| Zepeda-Orozco, et al., Dialysis Disequilibrium Syndrome, Pediatr. Nephrol, 27:2205-2211 (2012). |
| Communication Relating to the Results of the Partial International Search dated Dec. 8, 2017 in Int'l PCT Patent Appl. No. PCT/IB17/55093. |
| Extended European Search Report dated Sep. 18, 2019 in EP Patent Appl. Serial No. 19172235.4. |
| Number | Date | Country | |
|---|---|---|---|
| 20180060520 A1 | Mar 2018 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62380284 | Aug 2016 | US |
