Systems and methods for delivering prescribed wound therapy

Information

  • Patent Grant
  • 12268806
  • Patent Number
    12,268,806
  • Date Filed
    Monday, October 23, 2023
    a year ago
  • Date Issued
    Tuesday, April 8, 2025
    26 days ago
Abstract
Embodiments of delivering reduced pressure wound therapy are disclosed. In some embodiments, a system includes a reduced pressure wound therapy device and a remote computer. The device can be configured to apply reduced pressure to a wound of a patient according to a default reduced pressure therapy prescription. The device can be configured to monitor usage data and transmit the usage data to the remove computer for determining compliance with a reduced therapy prescription. In some cases, non-compliance can be determined due to change of the prescription from the default prescription to a prescription more suitable for treating the wound. A non-compliance notification can be transmitted to the device. The device settings can be updated to the current prescription.
Description
TECHNICAL FIELD

Embodiments of the present disclosure relate to systems, devices, and methods for monitoring and/or treating a wound with, for example with reduced pressure therapy or topical negative pressure (TNP) therapy. In particular, but without limitation, embodiments disclosed herein relate to the delivery of prescribed reduced pressure therapy.


DESCRIPTION OF THE RELATED ART

Many different types of wound dressings are known for aiding in the healing process of a human or animal. These different types of wound dressings include many different types of materials and layers, for example, gauze, pads, foam pads or multi-layer wound dressings. Topical negative pressure (TNP) therapy, sometimes referred to as vacuum assisted closure, negative pressure wound therapy, or reduced pressure wound therapy, is widely recognized as a beneficial mechanism for improving the healing rate of a wound. Such therapy is applicable to a broad range of wounds such as incisional wounds, open wounds, and abdominal wounds or the like. TNP therapy assists in the closure and healing of wounds by reducing tissue edema, encouraging blood flow, stimulating the formation of granulation tissue, removing excess exudates and may reduce bacterial load. Thus, reducing infection to the wound. Furthermore, TNP therapy permits less outside disturbance of the wound and promotes more rapid healing.


SUMMARY

In some cases, a negative pressure wound therapy device includes a negative pressure source configured to be fluidically connected to a dressing positioned over a wound, the negative pressure source further configured to provide negative pressure therapy to the wound, a user interface configured to receive input from a user and provide feedback to the user, and a controller configured to: receive from the user interface a request to provide negative pressure therapy in accordance with a default therapy prescription, in response to receipt of the request, cause the negative pressure source to provide negative pressure therapy to the wound in accordance with the default therapy prescription, transmit or cause transmission of usage data associated with provision of negative pressure therapy over a time duration to a remote computer and cause the remote computer to monitor compliance with an updated therapy prescription over at least a portion of the time duration, the updated therapy prescription being different than the default therapy prescription, receive an indication from the remote computer that provision of negative therapy over at least the portion of the time duration was non-compliant with the updated therapy prescription, in response to receipt of the indication, provide a non-compliant therapy alert to a user via the user interface and cause receipt from the user interface of an authorization to switch therapy prescription, and in response to receipt of the authorization to switch therapy prescription, cause the negative pressure source to provide negative pressure therapy to the wound in accordance with the updated therapy prescription.


The device of any preceding paragraphs and/or any of the devices disclosed herein can include one or more of the following features. The device can further include a primary power source configured to supply power to at least the negative pressure source and the controller and a secondary power source configured to supply power to at least the user interface and the controller, wherein the controller is configured to provide the non-compliant therapy alert to the user via the user interface when the primary power source is disconnected from the controller or depleted. The secondary power source can be configured to not provide power to the negative pressure source. The controller can be configured to receive the updated therapy prescription from the remote computer and not cause the negative pressure source to provide negative pressure therapy to the wound in accordance with the updated prescription until receipt of the authorization to switch therapy prescription. In response to receipt of the updated therapy prescription, the controller can be further configured to provide an updated therapy prescription alert to the user via the user interface until receipt of the authorization to switch therapy prescription.


The device of any preceding paragraphs and/or any of the devices disclosed herein can include one or more of the following features. Default therapy prescription and updated therapy prescription can specify at least one of therapy duration, therapy intensity, or therapy mode. Usage data can include at least one of therapy duration, therapy intensity, or therapy mode over the time duration. The updated therapy prescription can specify at least one of longer therapy duration, higher therapy intensity, or different therapy mode than the default therapy prescription. The device can include a housing enclosing the negative pressure source and the controller, wherein the user interface is positioned at least partially on an exterior of the housing.


In some cases, a method of operating a negative pressure wound therapy device can include, by at least one processor of the device, receiving, via a user interface of the device, a request to provide negative pressure therapy in accordance with a default therapy prescription, in response to receiving the request, causing a negative pressure source of the device to provide negative pressure therapy in accordance with the default therapy prescription, transmitting or causing transmission of a usage data associated with provision of the negative pressure therapy over a time duration to a remote computer, receiving, from the remote computer, an indication that provision of negative pressure therapy over at least the portion of the time duration was non-compliant with an updated therapy prescription that is different from the default therapy prescription, in response to the receipt of the indication, generating a non-compliance alert via a user interface of the device, obtaining an authorization to switch therapy (such as, the therapy prescription) to the updated therapy prescription, and in response to obtaining the authorization, causing the negative pressure source to provide negative pressure therapy in accordance with the updated therapy prescription.


The method of any preceding paragraphs and/or any of the methods disclosed herein can include one or more of the following features. The default therapy prescription can specify at least one of therapy duration, therapy intensity, or therapy mode. The usage data can include at least one of therapy duration, therapy intensity, or therapy mode over the time duration. The updated therapy prescription can specify at least one of a longer therapy duration, higher therapy intensity, or different therapy mode than the default therapy prescription. The method can include configuring the user interface to enable a user to authorize to switch therapy prescription. The method can include receiving from the remote computer the updated therapy prescription.


In some cases, a system for applying therapy (such as, negative pressure wound therapy) includes a medical device configured to apply or provide treatment according to a default therapy prescription and a remote computing system connected to the medical device via a network, the remote computing system including at least one processor configured to obtain an updated therapy prescription different than the default therapy prescription, receive, from the medical device, usage data associated with provision of the default therapy prescription over a period of time, compare the usage data to an expected usage data associated with the updated therapy prescription, based on the comparison, determine that the usage data is not compliant with the updated therapy prescription, transmit a non-compliance indication to the medical device, receive an authorization to switch (for example, switch treatment) to the updated therapy prescription, and transmit the updated therapy prescription to the medical device.


The system of any preceding paragraphs and/or any of the systems disclosed herein can include one or more of the following features. The default therapy prescription can specify at least one of therapy duration, therapy intensity, or therapy mode. The usage data can include at least one of therapy duration, therapy intensity, or therapy mode over the time duration. The updated therapy prescription can specify at least one of longer therapy duration, higher therapy intensity, or different therapy mode than the default therapy prescription. The at least one processor can be further configured to cause the medical device to apply or provide treatment according to the updated therapy prescription. The medical device can include at least one processor configured to receive an authorization to switch (for example, switch treatment) to the updated therapy prescription from the remote computing device. The medical device can be a negative pressure wound therapy device.


In some cases, a method of operating a medical device includes, by at least one processor, obtaining an updated therapy prescription different than a default therapy prescription according to which treatment is being provided by a medical device. The method can include receiving, from the medical device, usage data associated with provision of the default therapy prescription over a period of time. The method can include comparing the usage data to an expected usage data associated with the updated therapy prescription. The method can include, based on the comparison, determining that the usage data is not compliant with the updated therapy prescription. The method can include transmitting a non-compliance indication to the medical device. The method can include receiving an authorization to switch treatment to the updated therapy prescription. The method can include transmitting the updated therapy prescription to the medical device, thereby causing the medical device to switch treatment to the updated therapy prescription.


The method of any preceding paragraphs and/or any of the methods disclosed herein can include one or more of the following features. Default therapy prescription can specify at least one of therapy duration, therapy intensity, or therapy mode. Usage data can include at least one of therapy duration, therapy intensity, or therapy mode over the time duration. Updated therapy prescription can specify at least one of longer therapy duration, higher therapy intensity, or different therapy mode than the default therapy prescription. Medical device can include a negative pressure wound therapy device.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 illustrates a reduced pressure wound therapy system.



FIG. 2 illustrate a pump assembly and canister.



FIG. 3 illustrates a schematic of a reduced pressure wound therapy system.



FIG. 4 illustrates a schematic of a reduced pressure wound therapy system connected over a network.



FIG. 5 illustrates a process of operating a negative pressure wound therapy system.



FIG. 6 illustrates a process of updating a therapy prescription.





DETAILED DESCRIPTION

Embodiments disclosed herein relate to systems and methods of monitoring and/or treating a wound. It will be appreciated that throughout this specification reference is made to a wound. It is to be understood that the term wound is to be broadly construed and encompasses open and closed wounds in which skin is torn, cut or punctured or where trauma causes a contusion, or any other superficial or other conditions or imperfections on the skin of a patient or otherwise that benefit from reduced pressure treatment. A wound is thus broadly defined as any damaged region of tissue where fluid may or may not be produced. Examples of such wounds include, but are not limited to, abdominal wounds or other large or incisional wounds, either as a result of surgery, trauma, sternotomies, fasciotomies, or other conditions, dehisced wounds, acute wounds, chronic wounds, subacute and dehisced wounds, traumatic wounds, flaps and skin grafts, lacerations, abrasions, contusions, burns, diabetic ulcers, pressure ulcers, stoma, surgical wounds, trauma and venous ulcers or the like.


Embodiments of systems and methods disclosed herein can be used with topical negative pressure (“TNP”) or reduced pressure therapy systems. Briefly, negative pressure wound therapy assists in the closure and healing of many forms of “hard to heal” wounds by reducing tissue oedema, encouraging blood flow and granular tissue formation, and/or removing excess exudate and can reduce bacterial load (and thus infection risk). In addition, the therapy allows for less disturbance of a wound leading to more rapid healing. TNP therapy systems can also assist in the healing of surgically closed wounds by removing fluid. In some cases, TNP therapy helps to stabilize the tissue in the apposed position of closure. A further beneficial use of TNP therapy can be found in grafts and flaps where removal of excess fluid is important and close proximity of the graft to tissue is required in order to ensure tissue viability.


As is used herein, reduced or negative pressure levels, such as −X mmHg, represent pressure levels relative to normal ambient atmospheric pressure, which can correspond to 760 mmHg (or 1 atm, 29.93 inHg, 101.325 kPa, 14.696 psi, etc.). Accordingly, a negative pressure value of −X mmHg reflects pressure that is X mmHg below 760 mmHg or, in other words, a pressure of (760−X) mmHg. In addition, negative pressure that is “less” or “smaller” than X mmHg corresponds to pressure that is closer to atmospheric pressure (for example, −40 mmHg is less than −60 mmHg). Negative pressure that is “more” or “greater” than −X mmHg corresponds to pressure that is further from atmospheric pressure (for example, −80 mmHg is more than −60 mmHg). In some cases, local ambient atmospheric pressure is used as a reference point, and such local atmospheric pressure may not necessarily be, for example, 760 mmHg.


Systems and methods disclosed herein can be used with other types of treatment in addition to or instead of reduced pressure therapy, such as irrigation, ultrasound, heat and/or cold, neuro stimulation, or the like. In some cases, disclosed systems and methods can be used for wound monitoring without application of additional therapy. Systems and methods disclosed herein can be used in conjunction with a dressing, including with compression dressing, reduced pressure dressing, or the like.


A healthcare provider, such as a clinician, nurse, or the like, can provide a TNP prescription specifying, for example, the pressure level and/or time of application. However, the healing process is different for each patient and the prescription may affect the healing process in a way the clinician or healthcare provider did not expect at the time of devising the prescription. A healthcare provider may try to adjust the prescription as the wound heals (or does not heal), but such process may require various appointments that can be time consuming and repetitive. Embodiments disclosed herein provide systems, devices, and/or methods of efficiently adjusting TNP prescriptions and delivering effective TNP therapy.


Negative Pressure System


FIG. 1 illustrates a negative or reduced pressure wound treatment (or TNP) system 100 comprising a wound filler 130 placed inside a wound cavity 110, the wound cavity sealed by a wound cover 120. The wound filler 130 in combination with the wound cover 120 can be referred to as wound dressing. A single or multi lumen tube or conduit 140 is connected the wound cover 120 with a pump assembly 150 configured to supply reduced pressure. The wound cover 120 can be in fluidic communication with the wound cavity 110. In any of the system embodiments disclosed herein, as in the embodiment illustrated in FIG. 1, a negative pressure wound therapy device (sometimes as a whole or partially referred to as a “pump assembly”) can be a canisterless (meaning that exudate is collected in the wound dressing or is transferred via tube 140 for collection to another location). However, any of the pump assembly embodiments disclosed herein can be configured to include or support a canister. Additionally, in any of the system embodiments disclosed herein, any of the pump assembly embodiments can be mounted to or supported by the dressing, or adjacent to the dressing. The wound filler 130 can be any suitable type, such as hydrophilic or hydrophobic foam, gauze, inflatable bag, and so on. The wound filler 130 can be conformable to the wound cavity 110 such that it substantially fills the cavity. The wound cover 120 can provide a substantially fluid impermeable seal over the wound cavity 110. In some cases, the wound cover 120 has a top side and a bottom side, and the bottom side adhesively (or in any other suitable manner) seals with wound cavity 110. The conduit 140 or any other conduit disclosed herein can be formed from polyurethane, PVC, nylon, polyethylene, silicone, or any other suitable material.


The wound cover 120 can have a port (not shown) configured to receive an end of the conduit 140. The conduit 140 can otherwise pass through and/or under the wound cover 120 to supply reduced pressure to the wound cavity 110 so as to maintain a desired level of reduced pressure in the wound cavity. The conduit 140 can be any suitable article configured to provide at least a substantially sealed fluid flow pathway or path between the pump assembly 150 and the wound cover 120, so as to supply the reduced pressure provided by the pump assembly 150 to wound cavity 110.


The wound cover 120 and the wound filler 130 can be provided as a single article or an integrated single unit. In some cases, no wound filler is provided and the wound cover by itself may be considered the wound dressing. The wound dressing may then be connected, via the conduit 140, to a source of negative pressure, such as the pump assembly 150. In some cases, though not required, the pump assembly 150 can be miniaturized and portable, although larger conventional pumps such can also be used.


The wound cover 120 can be located over a wound site to be treated. The wound cover 120 can form a substantially sealed cavity or enclosure over the wound site. In some cases, the wound cover 120 can be configured to have a film having a high water vapour permeability to enable the evaporation of surplus fluid, and can have a superabsorbing material contained therein to safely absorb wound exudate. It will be appreciated that throughout this specification reference is made to a wound. In this sense it is to be understood that the term wound is to be broadly construed and encompasses open and closed wounds in which skin is torn, cut or punctured or where trauma causes a contusion, or any other surficial or other conditions or imperfections on the skin of a patient or otherwise that benefit from reduced pressure treatment. A wound is thus broadly defined as any damaged region of tissue where fluid may or may not be produced. Examples of such wounds include, but are not limited to, acute wounds, chronic wounds, surgical incisions and other incisions, subacute and dehisced wounds, traumatic wounds, flaps and skin grafts, lacerations, abrasions, contusions, burns, diabetic ulcers, pressure ulcers, stoma, surgical wounds, trauma and venous ulcers or the like. In some cases, the components of the TNP system described herein can be particularly suited for incisional wounds that exude a small amount of wound exudate.


The system can be designed to operate without the use of an exudate canister. The system can be configured to support an exudate canister. In some cases, configuring the pump assembly 150 and tubing 140 so that the tubing 140 can be quickly and easily removed from the pump assembly 150 can facilitate or improve the process of dressing or pump changes, if necessary. Any of the pump embodiments disclosed herein can be configured to have any suitable connection between the tubing and the pump.


In some cases, the pump assembly 150 can be configured to deliver negative pressure of approximately −80 mmHg, or between about −20 mmHg and −200 mmHg. Note that these pressures are relative to normal ambient atmospheric pressure thus, −200 mmHg would be about 560 mmHg in practical terms. In some cases, the pressure range can be between about −40 mmHg and −150 mmHg. Alternatively, a pressure range of up to −75 mmHg, up to −80 mmHg or over −80 mmHg can be used. Also, in other cases a pressure range of below −75 mmHg can be used. Alternatively, a pressure range of over approximately −100 mmHg, or even 150 mmHg, can be supplied by the pump assembly 150.


In some cases, the pump assembly 150 is configured to provide continuous or intermittent negative pressure therapy. Continuous therapy can be delivered at above −25 mmHg, −25 mmHg, −40 mmHg, −50 mmHg, −60 mmHg, −70 mmHg, −80 mmHg, −90 mmHg, −100 mmHg, −120 mmHg, −140 mmHg, −160 mmHg, −180 mmHg, −200 mmHg, or below 200 mmHg. Intermittent therapy can be delivered between low and high negative pressure set points. Low set point can be set at above 0 mmHg, 0 mmHg, −25 mmHg, −40 mmHg, −50 mmHg, 60 mmHg, −70 mmHg, −80 mmHg, −90 mmHg, −100 mmHg, −120 mmHg, −140 mmHg, −160 mmHg, −180 mmHg, or below −180 mmHg. High set point can be set at above 25 mmHg, 40 mmHg, 50 mmHg, 60 mmHg, 70 mmHg, 80 mmHg, 90 mmHg, 100 mmHg, 120 mmHg, 140 mmHg, 160 mmHg, 180 mmHg, 200 mmHg, or below −200 mmHg. During intermittent therapy, negative pressure at low set point can be delivered for a first time duration, and upon expiration of the first time duration, negative pressure at high set point can be delivered for a second time duration. Upon expiration of the second time duration, negative pressure at low set point can be delivered. The first and second time durations can be same or different values. The first and second time durations can be selected from the following range: less than 2 minutes, 2 minutes, 3 minutes, 4 minutes, 6 minutes, 8 minutes, 10 minutes, or greater than 10 minutes. In some cases, switching between low and high set points and vice versa can be performed according to a step waveform, square waveform, sinusoidal waveform, and the like.


In operation, the wound filler 130 is inserted into the wound cavity 110 and wound cover 120 is placed so as to seal the wound cavity 110. The pump assembly 150 provides a source of a negative pressure to the wound cover 120, which is transmitted to the wound cavity 110 via the wound filler 130. Fluid (such as, wound exudate) is drawn through the conduit 140, and can be stored in a canister. In some cases, fluid is absorbed by the wound filler 130 or one or more absorbent layers (not shown).


Wound dressings that may be utilized with the pump assembly and other embodiments of the present application include Renasys-F, Renasys-G, Renasys AB, and Pico Dressings available from Smith & Nephew. Further description of such wound dressings and other components of a negative pressure wound therapy system that may be used with the pump assembly and other embodiments of the present application are found in U.S. Patent Publication Nos. 2012/0116334, 2011/0213287, 2011/0282309, 2012/0136325 and U.S. Pat. No. 9,084,845, each of which is incorporated by reference in its entirety. In other embodiments, other suitable wound dressings can be utilized.


Pump Assembly and Canister


FIG. 2 illustrates a negative pressure wound therapy device 200 including a pump assembly 230 and canister 220. As is illustrated, the pump assembly 230 and the canister are connected, thereby forming the device 200. The pump assembly 230 comprises one or more indicators, such as visual indicator 202 configured to indicate alarms and visual indicator 204 configured to indicate status of the TNP system. The indicators 202 and 204 can be configured to alert a user to a variety of operating and/or failure conditions of the system, including alerting the user to normal or proper operating conditions, pump failure, power supplied to the pump or power failure, detection of a leak within the wound cover or flow pathway, suction blockage, or any other similar or suitable conditions or combinations thereof. In some cases, any one or more of the indicators 202 and 204 can be configured to alert a user that the current operation is compliant or non-compliant with a therapy prescription, which can be stored in a remote computing device (sometimes referred to a “remote computing system” or “remote computer”). The remote computing device can be any one or more computing devices with at least one processor and/or database, such as one or more cloud servers (sometimes referred to as “the cloud”). In some cases, the pump assembly 230 can comprise additional indicators. In some cases, a single indicator is used. In some cases, multiple indicators are used. Any one or more suitable indicators can be used such as visual, audio, tactile indicator, and so on. The indicator 202 can be configured to signal alarm conditions, such as canister full, power low, conduit 140 disconnected, seal broken in the wound seal 120, and so on. The indicator 202 can be configured to display red flashing light to draw user's attention. The indicator 204 can be configured to signal status of the TNP system, such as therapy delivery is ok, leak detected, and so on. The indicator 204 can be configured to display one or more different colors of light, such as green, yellow, etc. For example, green light can be emitted when the TNP system is operating properly and yellow light can be emitted to indicate a warning.


The pump assembly 230 comprises a display or screen 206 mounted in a recess formed in a case of the pump assembly. In some cases, the display 206 can be a touch screen display. In some cases, the display 206 can support playback of audiovisual (AV) content, such as instructional videos. As explained below, the display 206 can be configured to render a number of screens or graphical user interfaces (GUIs) for configuring, controlling, and monitoring the operation of the TNP system. The pump assembly 230 comprises a gripping portion formed in the case of the pump assembly. The gripping portion can be configured to assist the user to hold the pump assembly 230, such as during removal of the canister 220. The pump assembly 230 includes one or more strap mounts 226 for connecting a carry strap to the pump assembly 230 or for attaching a cradle. In some cases, the canister 220 can be replaced with another canister, such as when the canister 220 has been filled with fluid.


The pump assembly 230 comprises one or more keys or buttons 212 configured to allow the user to operate and monitor the operation of the TNP system. As is illustrated, in some cases, there can be a plurality of buttons. One button can be configured as a power button to turn on/off the pump assembly 230. Another button can be configured as a play/pause button for the delivery of negative pressure therapy. For example, pressing the button can cause therapy to start, and pressing the button afterward can cause therapy to pause or end. A button can be configured to lock the display 206 and/or the buttons 212. For instance, a button can be pressed so that the user does not unintentionally alter the delivery of the therapy. In some cases, multiple key presses and/or sequences of key presses can be used to operate the pump assembly 230.


The canister 220 is configured to hold fluid (such as, exudate) removed from the wound cavity 110. The canister 220 includes one or more latches for attaching the canister to the pump assembly 230. The exterior of the canister 220 can be formed from frosted plastic so that the canister is substantially opaque and the contents of the canister and substantially hidden from plain view. The canister 220 includes a substantially transparent window, which can also include graduations of volume. For example, the illustrated 300 mL canister 220 includes graduations of 50 mL, 100 mL, 150 mL, 200 mL, 250 mL, and 300 mL. Other embodiments of the canister can hold different volume of fluid and can include different graduation scale. The canister 220 comprises a tubing channel for connecting to the conduit 140.


In some cases, the pump assembly 230 comprises a power jack for charging and recharging a primary power source, such as an internal battery, of the pump assembly. In some cases, the power jack is a direct current (DC) jack. In some cases, the pump assembly can comprise a disposable primary power source, such as batteries, so that no power jack is needed. In some cases, the pump assembly 230 comprises two or more power sources or supplies. In some cases, one of the power supplies (for example, primary) can deliver power to operate and control the pump. In some cases, a secondary power source can deliver power to one or more of the user interface, alert system, and/or communication system for uploading usage data to the cloud.


Control System


FIG. 3 illustrates a schematic of a control system 300 which can be employed in any of the embodiments of wound monitoring and/or treatment systems described herein. Electrical components can operate to accept user input, provide output to the user, operate the negative pressure source of a TNP system, provide network connectivity, and so on. It may be advantageous to utilize multiple processors in order to allocate or assign various tasks to different processors. In some cases, a first processor can be responsible for user activity and a second processor can be responsible for controlling another device, such as a pump 390. This way, the activity of controlling the other device, such as the pump 390, which may necessitate a higher level of responsiveness (corresponding to higher risk level), can be offloaded to a dedicated processor and, thereby, will not be interrupted by user interface tasks, which may take longer to complete because of interactions with the user.


Input and output to the other device, such as a pump 390, one or more sensors (for example, one or more pressure sensors configured to monitor pressure in one or more locations of the fluid flow path), or the like, can be controlled by an input/output (I/O) module 320. For example, the I/O module can receive data from one or more sensors through one or more ports, such as serial (for example, I2C), parallel, hybrid ports, and the like. The processor 310 also receives data from and provides data to one or more expansion modules 360, such as one or more USB ports, SD ports, Compact Disc (CD) drives, DVD drives, FireWire ports, Thunderbolt ports, PCI Express ports, and the like. The processor 310, along with other controllers or processors, stores data in one or more memory modules 350, which can be internal and/or external to the processor 310. Any suitable type of memory can be used, including volatile and/or non-volatile memory, such as RAM, ROM, magnetic memory, solid-state memory, Magnetoresistive random-access memory (MRAM), and the like.


In some cases, the processor 310 can be a general purpose controller, such as a low-power processor. In other cases, the processor 310 can be an application specific processor. In some cases, the processor 310 can be configured as a “central” processor in the electronic architecture of the system 300, and the processor 310 can coordinate the activity of other processors, such as a pump control processor 370, communications processor 330, and one or more additional processors 380. The processor 310 can run a suitable operating system, such as a Linux, Windows CE, VxWorks, etc.


The pump control processor 370 (if present) can be configured to control the operation of a negative pressure pump 390. The pump 390 can be a suitable pump, such as a diaphragm pump, peristaltic pump, rotary pump, rotary vane pump, scroll pump, screw pump, liquid ring pump, diaphragm pump operated by a piezoelectric transducer, voice coil pump, and the like. In some cases, the pump control processor 370 can measure pressure in a fluid flow path, using data received from one or more pressure sensors, calculate the rate of fluid flow, and control the pump. In some cases, the pump control processor 370 controls the pump motor so that a desired level of negative pressure in achieved in the wound cavity 110. The desired level of negative pressure can be pressure set or selected by the user. The pump control processor 370 can control the pump (for example, pump motor) using pulse-width modulation (PWM). A control signal for driving the pump can be a 0-100% duty cycle PWM signal. The pump control processor 370 can perform flow rate calculations and detect alarms. The pump control processor 370 can communicate information to the processor 310. The pump control processor 370 can include internal memory and/or can utilize memory 350. The pump control processor 370 can be a low-power processor.


A communications processor 330 can be configured to provide wired and/or wireless connectivity. The communications processor 330 can utilize one or more antennas or transceivers 340 for sending and receiving data. In some cases, the communications processor 330 can provide one or more of the following types of connections: Global Positioning System (GPS) technology, cellular connectivity (for example, 2G, 3G, LTE, 4G, 5G, or the like), WiFi connectivity, Internet connectivity, and the like. Connectivity can be used for various activities, such as pump assembly location tracking, asset tracking, compliance monitoring, remote selection, uploading of logs, alarms, and other operational data, and adjustment of therapy settings, upgrading of software and/or firmware, and the like. In some cases, the communications processor 330 can provide dual GPS/cellular functionality. Cellular functionality can, for example, be 3G functionality. In such cases, if the GPS module is not be able to establish satellite connection due to various factors including atmospheric conditions, building or terrain interference, satellite geometry, and so on, the device location can be determined using the 3G network connection, such as by using cell identification, triangulation, forward link timing, and the like. In some cases, the system 300 can include a SIM card, and SIM-based positional information can be obtained. The communications processor 330 can communicate information to the processor 310. The communications processor 330 can include internal memory and/or can utilize memory 350. The communications processor 330 can be a low-power processor.


In some cases, the system 300 can store data illustrated in Table 1. This data can be stored, for example, in memory 350. This data can include patient data collected by one or more sensors. In various cases, different or additional data can be stored by system 300. In some cases, location information can be acquired by GPS or any other suitable method, such as cellular triangulation, cell identification forward link timing, and the like.









TABLE 1







Example Data Stored










Category
Item
Type
Source





GPS
Location
Latitude,
Acquired from




Longitude,
GPS




Altitude




Timestamp Location
Timestamp




Acquired




Therapy
Total time therapy ON
Minutes
Calculated on



since device activation

device based on



Total time therapy ON
Minutes
user control



since last maintenance





reset





Device Placement;
Minutes




accumulated daily hours





starting from first Therapy





ON after last maintenance





reset, stopping at last





Therapy OFF before





returning for Maintenance





and maintenance reset.





(Includes both THERAPY





ON and THERAPY OFF





hours)




Device
Serial Number
Alphanumeric
Set by Pump





Utility



Controller Firmware
Alphanumeric
Unique version



Version

identifier, hard





coded in





firmware


Events
Device Event Log (See
List of Events
Generated in



Table 3 for example)
(See Table 2)
response to





various user





actions and





detected events









The system 300 can track and log therapy and other operational data. Such data can be stored, for example, in the memory 350. In some cases, the system 300 can store log data illustrated in Table 2. Table 3 illustrates an example event log. One or more such event logs can be stored by the system 300. As is illustrated, the event log can include time stamps indicating the time of occurrence. In some cases, additional and/or alternative data can be logged.









TABLE 2







Example Data Tracked











Category
ID
Type
Data Content
Notes














Device
0
Startup (Created

First time, out-




DB)

of-the-box.



1
Startup

Subsequent




(Resumed DB)

power-ups.



2
Startup (Corrupt

Corrupt




DB, Recreated)

configuration






was detected.






The database






was deleted and






recreated, and






next run was in






out-of-the-box






mode.



3
Shutdown

Normal




(Signaled)

shutdown,






handled/






registered






by software.



4
Shutdown

Unexpected




(Inferred)

shutdown; on






next power-up,






last active time






registered as






shutdown event.


Therapy
5
Start Delivery
modes,
Modes are Y-




(Continuous)
setpoints
connect status,






and intensity.



6
Start Delivery
modes,
Modes are Y-




(Intermittent)
setpoints
connect status,






and intensity.



7
Stop Delivery





8
Set Therapy
mmHg
This and other




Pressure Setpoint

therapy






adjustment






events are only






recorded while






therapy is being






delivered.



9
Set Standby
mmHg





Pressure Setpoint





10
Set Intermittent
setting (30 s,





Therapy Duration
60 s, etc)




11
Set Intermittent
setting (30 s,





Standby Duration
60 s, etc)




12
SetMode
cont/Intermittent




13
Set Intensity
low/med/high




14
Set Y Connect
yes/no



Alarm
15
Over Vacuum
high mmHg




16
High Vacuum
high deviation






mmHg




17
Blocked Full
low airflow lpm





Canister





18
High Flow Leak
high airflow lpm




19
Low Vacuum
low mmHg




20
Battery Failure





21
Critical Battery





22
Low Battery





23
Inactivity




Maintenance
24
Maintenance






Reset





25
Reset to Defaults





26
Software/Device
Warning code
Any detected,




Warning

minor






unexpected






software






behavior will






be logged as






an event



27
Software/Device
Fault code
Any detected,




Fault

severe






unexpected






software






behavior will






be logged as






an event
















TABLE 3







Example Event Log











Type




Timestamp
ID
Type Description
Data













1:23:45 Apr. 2, 2012 (UTC-12)
0
Startup (Created





DB)



1:29:23 Apr. 2, 2012 (UTC-12)
15
Set Intensity
medium


1:29:43 Apr. 2, 2012 (UTC-12)
10
Set Therapy
120 mmHg




Pressure Setpoint



1:31:02 Apr. 2, 2012 (UTC-12)
7
Start Delivery
120 mmHg




(Continuous)
continuous,





medium





intensity, no





Y connect


1:44:20 Apr. 2, 2012 (UTC-12)
20
High Flow Leak
4 lpm


1:44:24 Apr. 2, 2012 (UTC-12)
9
Stop Delivery









In some cases, using the connectivity provided by the communications processor 330, the system 300 can upload any of the data stored, maintained, and/or tracked by the system 300 to a remote computing device. In some cases, the following information can be uploaded to the remote computing device: activity log(s), which includes therapy delivery information, such as therapy duration, alarm log(s), which includes alarm type and time of occurrence; error log, which includes internal error information, transmission errors, and the like; therapy duration information, which can be computed hourly, daily, and the like; total therapy time, which includes therapy duration from first applying a particular therapy program or programs; lifetime therapy information; device information, such as the serial number, software version, battery level, etc.; device location information; patient information; and so on. The system 300 can also download various operational data, such as therapy selection and parameters, firmware and software patches and upgrades, and the like. The system 300 can provide Internet browsing functionality using one or more browser programs, mail programs, application software (for example, apps), etc. Additional processors 380, such as processor for controlling one or more user interfaces (such as, one or more displays), can be utilized. In some cases, any of the illustrated and/or described components of the system 300 can be omitted depending on an embodiment of a wound monitoring and/or treatment system in which the system 300 is used.



FIG. 4 illustrates a schematic of a reduced pressure wound therapy system 400. A pump assembly 420 includes a user interface processor firmware and/or software 422, which can be executed by the user interface processor 310, pump control processor firmware and/or software, which can be executed by the pump control processor 370, communications processor firmware and/or software 426, which can be executed by the communications processor 330, and additional processor(s) firmware and/or software, which can be executed by one or more additional processors 380. The pump assembly 420 can be connected to one or more remote computing device 410, 411, 440 via a network 430. In some cases, the pump assembly 420 can be directly connected to one or more devices 410, 411, 440, which can be a laptop, desktop, tablet, smartphone, server, and the like. A wired or wireless connection can be utilized to connect the one or more devices 410, 411, 440 to the pump assembly 420. The connection between the one or more devices 410, 411, 440 and the pump assembly 420 can be used for various activities, such as pump assembly location tracking, asset tracking, compliance monitoring, selection, uploading of logs, alarms, and other operational data, and adjustment of therapy settings, upgrading of software and/or firmware, and the like. The pump assembly 420 and one or more devices 410, 411 can communicate with device 440, which can be a server, via the network 430. The server 440 can include a data storage module 442 and a web interface 444 for accessing the server.


The connection between the one or more devices 410, 411, 440 and the pump assembly 420 can be utilized to perform one or more of the following: initialization and programming of the pump assembly 420, firmware and/or software upgrades, maintenance and troubleshooting, selecting and adjusting therapy parameters, and the like. In some cases, the one or more devices 410, 411, 440 can execute an application program for communicating with the pump assembly 420.


The pump assembly 420 can upload various data to the server 440 via the network 430. In some cases, the pump assembly 420 can upload data to one or more remote computing devices, such as one or more servers. As explained above, upload data can include activity log(s), alarm log(s), usage data, therapy duration information, total therapy time, lifetime therapy information, device information, device location information, patient information, etc. In addition, the pump assembly 420 can receive and process commands received from the network 430


Further description of a negative pressure wound therapy system and its operation that may be used with any of the embodiments of the present application is found in U.S. Pat. No. 9,737,649, which is incorporated by reference in its entirety.


Adjusting the Therapy Prescription

In some cases, a reduced pressure device can be configured to collect information from the patient, such as:

    • How painful is the wound (scale 1-10)
    • Has the exudate colour changed?
    • Is there any smell?
    • Is there anything wrong?


      The data can be collected periodically, for example, daily, several times a day, every other day, or the like. The data can be collected via the user interface. For example, the data can be collected via a daily pop up screen. The data could alternatively or additionally be inputted via a stand-alone application on a computing device, such as a smart phone, tablet, laptop computer, or the like. The data can be transmitted to a remote computing system, which can make the data available to a healthcare provider. The healthcare provider may use the information to prescribe a new or updated therapy prescription. For example, if there is pain, negative pressure may be reduced. As another example, if there is odour, infection may be present.


In some cases, the therapy prescription can be updated as the healing progresses. For example, a healthcare provider can apply a default prescription when prescribing the device but update the prescription with more complex adjustments as he or she assesses the healing of the wound. When a reduced pressure therapy device is prescribed to a patient, a default therapy prescription can be set. A default therapy prescription can be automatically loaded onto the reduced pressure therapy device. The default prescription may be the only therapy accessible on the device for the particular healthcare provider without inserting or entering an access code. The default therapy prescription may be factory set or set by a senior clinical administrator. The default therapy prescription may only be a basic safe operating therapy. For example, the default therapy prescription may not include therapy duration, and the healthcare provider may be required to set the duration on the device or remotely. Capability to apply the default therapy prescription may allow a junior clinician or nurse to apply the device and start a safe protocol therapy without delay in determining more tailored therapy parameters.


A healthcare provider, such as the clinician or nurse, can select the default therapy prescription via a user interface. After the default therapy is prescribed, the reduced pressure therapy device transmits compliance or usage data to a remote computer. The reduced pressure therapy device can record and/or transmit usage data to a remote computer for a period of time, such as 1 hour, 3 hours, half a day, 1 day, or the like. In some cases, the period of time can be defined via the reduced pressure therapy device. In some cases, the period of time can be defined via the remote computing device.


Usage data can be indicative of how the device is being used for delivering therapy. For example, usage data can include one or more of the number of treatments that have been performed, the date and time that each treatment is performed, duration of each treatment, and/or the like. As another example, usage data can comprise amount of time the device was turned on, applied therapy over time, amount of aspirated exudate, and/or the like. As yet another example, usage data can comprise biometric information, such as tissue impedance, temperature, wound image information, and/or the like.


The remote computing device can receive usage data from the reduced pressure therapy device and monitor the usage data to generate compliance information. Compliance information can be indicative of the usage of the device complying with a therapy prescription, such as the current therapy prescription. The usage data can indicate the manner in which treatments were performed using the device, from which a patient's compliance with a particular treatment prescription can be determined.


In some cases, a patient's compliance with prescribed therapy is determined with respect to an updated therapy prescription. A user, such as a senior clinician or doctor, can enter updated therapy prescription information via the remote computing device. The user can determine an updated therapy prescription based on the received usage data from the reduced pressure therapy device. The updated therapy prescription can include a different applied pressure setting and/or durational setting. The updated therapy prescription can specify a different therapy intensity or therapy mode. Some embodiments disclosed herein allow the user to propose an updated therapy prescription after the patient has received at least some therapy and after at least some information regarding the healing progress is available.


Further description of determining compliance that may be used with any of the embodiments of the present application is found in U.S. Pat. No. 9,526,920, which is incorporated by reference in its entirety.


In some cases, if the remote computing device detects that the received usage data is non-compliant with the updated therapy prescription, the remote computing device can generate an indication or alert indicative of non-compliance. The alert can be transmitted to the reduced pressure therapy device. The alert can be displayed on the user interface of the reduced pressure therapy device. In some cases, before switching therapy to the updated prescription, the updated prescription should first be verified by a healthcare provider. This can be performed manually at the reduced pressure therapy device (such as, via the user interface) or remotely. For example, upon receipt of the alert, the user interface of the reduced pressure therapy device can prompt the user, such as a clinician, nurse, or user, to authorize a switch to the updated therapy prescription. Authorization can be performed manually, such as at the user Interface of the device, or remotely, such as via the remote computing device. In response to the authorization and/or as part of transmitting the non-compliance alert, the remote computing system can transmit the updated therapy prescription to the reduced pressure therapy device, which then can apply the updated therapy prescription once authorization has been received. The remote computing system can transmit the updated therapy prescription before the reduced pressure therapy device has received authorization for the prescription switch. In some cases, the updated therapy prescription is stored on the reduced pressure therapy device but is applied when the user inputs authorization.


In some cases, an indication or alert that an updated prescription has been sent to the reduced pressure therapy device can be transmitted from the remote computing device and/or generated by the reduced pressure therapy device. This updated therapy prescription alert can be separate from the non-compliance alert. This alert can be provided to the user as described herein, such as via the user interface, to facilitate authorization of the updated prescription.


Further description of authorization that may be used with any of the embodiments of the present application is found in International Patent Application No. PCT/EP2019/081248, which is incorporated by reference in its entirety.


In some cases, a default therapy prescription may be applied to override the factory default. This can be applied by a local clinician or engineer. In some cases, the prescription may be stored in the remote computing device and may be assigned to one or a number of devices registered with the remote computing device. Each device may have a unique identification code that may be stored in the device and the remote computing device, making it possible to account for each device.


In some instances, a tailored therapy prescription may already be set by and/or on the remote computing device. On power up (or at another time), the reduced pressure wound therapy device may check the remote computing device for the most current therapy setting and provide an alert that a new prescription is awaiting acceptance as described herein.


In some cases, the alerts for non-compliance and/or updated therapy prescription can be received by the reduced pressure therapy system and/or provided to the user even when the pump assembly is powered off and/or when a primary power source is depleted. When the pump assembly is turned off, the primary power source can be disconnected from at least some of the electric components, such as from the negative pressure source. The primary power source could be depleted so that it cannot supply sufficient power to operate the at least some of the electric components, such as the negative pressure source and/or one or more processors. The secondary power source can serve as a back-up power source that provides sufficient power to allow provision of at least one of the non-compliant therapy or the updated therapy prescription alert when the primary power source is disconnected and/or depleted. In some cases, the user interface can be powered by a secondary power source. In some cases, usage data is transmitted even when the pump assembly is powered off and/or the primary power source is depleted. In such cases, the communication system can be powered by a secondary power source. The secondary power source can include one or more supercapacitors.


At least some embodiments disclosed herein advantageously allow for therapy to be applied quicker and more effectively than with traditional systems. A healthcare provider can setup the reduced pressure therapy device to apply therapy to the patient according to a default therapy prescription, as described herein, without having to determine optimal therapy prescription and/or receive extensive training on how to operate the device. Such default therapy prescription can be pre-loaded on the device, making it easier to cause provision of therapy to the patient according to the default therapy prescription. While the patient receives therapy according to the default therapy prescription, the same healthcare provider (or a more experienced or knowledgeable healthcare provider, such as a senior clinician) can update the therapy prescription to be more tailored to the patient's needs. This can be performed remotely based on the data received from the device, as described herein. Non-compliance with the updated therapy prescription can be determined as described herein, which can cause generation and display of the alert, leading to a switch in the therapy prescription and application of therapy to the patient according to the updated therapy prescription. Accordingly, therapy time and effectiveness can be maximized.


For example, a reduced pressure therapy device can be first applied by a healthcare provider to a patient according to instructions for use and local medical protocols. The device may on power up be configured to access a default safe and efficacious therapy prescription settings (for instance, from non-volatile memory), and on selection of start therapy, the default therapy prescription to the patient. The default therapy settings may include a compliant therapy use threshold, such as to exceed 22 hours of use in any 24 hours. Initialization of therapy may allow for any troubleshooting to occur. The application of therapy may cause the default therapy setting to be sent to a remote computing device along with an indication of a new application of therapy and/or any other information, such as location, clinician name, patient ID, and/or the like. Once the data message is received, alerts may be sent to administrators and/or healthcare providers via any transmission means, such as email, SMS, etc. indicating a new application of therapy according to the default therapy prescription has occurred. A response to confirm acceptance or to change the settings may be required. Acceptance (for example, via SMS message, reply email, or via log-on to the remote computing device through an application) can confirm monitoring against the default therapy setting identified in the acceptance message. Alternatively, the therapy prescription may be changed according to the individual requirements of the patient. Changing the prescription results in the prescription being sent to the device and logged in the remote computing system. On receipt of the new prescription at the device, an alert can be indicated on the device that a new prescription is waiting to be accepted. Acceptance of the prescription may only be carried out by input of an authorization password or a biometric check (for example, a finger print check being completed by the clinician at the device and acceptance of the new settings displayed).


The device may send telemetry/status data updates to the remote computing device periodically and/or in real time. The remote computing device can generate alerts for non-compliant application of the prescription stored in the remote computing device. For example, usage time may be below the threshold, application of pressure(s) may be outside a threshold range, and/or any suitable deviation from the prescription that may mean therapy is not being delivered at a therapeutic level. Non-compliance alerts may be sent remotely to the device and/or to the healthcare providers registered with the remote computing device via any of the messaging techniques described herein.



FIG. 5 illustrates a process of operating a reduced pressure wound therapy device. The illustrated process can be implemented by any of the reduced pressure wound therapy devices disclosed herein, and in particular by at least one processor of the reduced pressure wound therapy device. The process can start in block 500 when the reduced pressure therapy device provides therapy to a wound of a patient according to a default therapy prescription. In some cases, the default therapy prescription specifies a minimum pressure applied to the wound. In some cases, the default therapy prescription specifies time intervals in which the minimum pressure is applied. In some cases, the default therapy prescription specifies control rules that adjust the applied pressure. In block 502, the process can transmit usage data to a remote computing device. Such transmission can be performed periodically as described herein. The usage data can comprise applied pressure over time, amount of exudate aspirated from the wound, the amount of time the therapy has been applied, and/or the like. In some cases, the usage data additionally or alternatively comprises biometric information as described herein. At block 504, the process determines whether the device has received an alert that the currently administered therapy is non-compliant. The process can receive the updated therapy prescription as described herein, such as in block 504. In some cases, block 504 is executed periodically at time intervals. In some cases, block 504 is executed continuously.


If the process does not receive the non-compliance alert and/or the updated therapy prescription, the process can return to block 502 and continue to monitor and/or transmit usage data to the remote computing device. If the process receives the alert and/or the updated therapy prescription, the process can proceed to block 505. In block 505, the process can communicate one or more of the non-compliant or updated therapy prescription alerts to the user via the user interface. In block 506, the process can determine whether to authorize a switch to the updated therapy prescription as set at or by the remote computing device. In some cases, the decision to or not to authorize the update can be made via the user interface, such as via one or more buttons, a touch screen, fingerprint reader, or the like. In some cases, the decision to authorize can be made on the remote computing device. If the update is not authorized, the process can return to block 502 and continue to transmit usage data to the remote computing device. The process can continue to provide one or more of the non-compliance or updated prescription alerts to the user. If the update is authorized, the process can cause application of therapy according to the updated therapy prescription in block 508.



FIG. 6 illustrates a process of updating a therapy prescription. The illustrated process can be performed by any of the remote computing devices described herein, and in particular by at least one processor of the remote computing device. The process can start in block 600 when the remote computing device receives usage data from the reduced wound therapy device. In some cases, the usage data can include applied pressure over time, amount of exudate in the canister, the amount of time the therapy was applied, and/or the like as described herein. In some cases, the usage data comprises biometric information as described herein. In block 602, the process can verify the received usage data for compliance with an updated therapy prescription. In some cases, the updated therapy prescription has been stored in the remote computing device and has not yet been transmitted to reduced pressure therapy device. In some cases, blocks 600 and 602 can be combined into a single block.


In block 604, the process can determine if the usage data complies with the updated therapy prescription. For example, the process can verify if the usage data matches or exceeds expected usage data associated with the updated therapy prescription (such as, verify if the therapy time matches or exceeds the expected therapy time, verify that applied pressure is within a threshold range, and/or the like). In some cases, the block 604 is executed periodically, such as at regular intervals. In some cases, the block 604 is executed continuously.


If the process determines that the usage data complies with the updated therapy prescription, the process can return to block 602. If the process determines that the usage data does not comply with the updated therapy prescription, the process can proceed to block 606. In block 606, the process can transmit a non-compliance alert to the reduced pressure therapy device. In some cases, the alert can include non-compliance information indicating which one or more parameters of the therapy failed to be compliant. In block 608, the process can determine whether authorization to switch to the updated therapy prescription has been received (for example, from a healthcare provider as described herein). If authorization has not been received, the process can return to block 602. In some cases, the process can alternatively terminate.


If the authorization has been received, the process can transition to block 610 and transmit the updated therapy prescription to the reduced pressure therapy device. In some cases, one or more of the blocks 608 and 610 may not be implemented. For example, the updated therapy prescription can be transmitted in block 606 (or in another block) as described herein.


Other Variations

Although some embodiments describe negative pressure wound therapy, the systems, devices, and/or methods disclosed herein can be applied to other types of therapies usable standalone or in addition to TNP therapy. Systems, devices, and/or methods disclosed herein can be extended to any medical device, and in particular any wound treatment device. For example, systems, devices, and/or methods disclosed herein can be used with devices that provide one or more of ultrasound therapy, oxygen therapy, neurostimulation, microwave therapy, active agents, antibiotics, antimicrobials, or the like. Such devices can, in addition, provide TNP therapy.


Any of transmission of data described herein can be performed securely. For example, one or more of encryption, https protocol, secure VPN connection, error checking, confirmation of deliver can be utilized.


Any value of a threshold, limit, duration, etc. provided herein is not intended to be absolute and, thereby, can be approximate. In addition, any threshold, limit, duration, etc. provided herein can be fixed or varied either automatically or by a user. Furthermore, as is used herein relative terminology such as exceeds, greater than, less than, etc. in relation to a reference value is intended to also encompass being equal to the reference value. For example, exceeding a reference value that is positive can encompass being equal to or greater than the reference value. In addition, as is used herein relative terminology such as exceeds, greater than, less than, etc. in relation to a reference value is intended to also encompass an inverse of the disclosed relationship, such as below, less than, greater than, etc. in relations to the reference value.


Features, materials, characteristics, or groups described in conjunction with a particular aspect, embodiment, or example are to be understood to be applicable to any other aspect, embodiment or example described herein unless incompatible therewith. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and/or all of the steps of any method or process so disclosed, may be combined in any combination, except combinations where at least some of such features and/or steps are mutually exclusive. The protection is not restricted to the details of any foregoing embodiments. The protection extends to any novel one, or any novel combination, of the features disclosed in this specification (including any accompanying claims, abstract and drawings), or to any novel one, or any novel combination, of the steps of any method or process so disclosed.


While certain embodiments have been described, these embodiments have been presented by way of example only, and are not intended to limit the scope of protection. Indeed, the novel methods and systems described herein may be embodied in a variety of other forms. Furthermore, various omissions, substitutions and changes in the form of the methods and systems described herein may be made. Those skilled in the art will appreciate that in some embodiments, the actual steps taken in the processes illustrated and/or disclosed may differ from those shown in the figures. Depending on the embodiment, certain of the steps described above may be removed, others may be added. For example, the actual steps and/or order of steps taken in the disclosed processes may differ from those shown in the figure. Depending on the embodiment, certain of the steps described above may be removed, others may be added. For instance, the various components illustrated in the figures may be implemented as software and/or firmware on a processor, controller, ASIC, FPGA, and/or dedicated hardware. Furthermore, the features and attributes of the specific embodiments disclosed above may be combined in different ways to form additional embodiments, all of which fall within the scope of the present disclosure.


User interface screens illustrated and described herein can include additional and/or alternative components. These components can include menus, lists, buttons, text boxes, labels, radio buttons, scroll bars, sliders, checkboxes, combo boxes, status bars, dialog boxes, windows, and the like. User interface screens can include additional and/or alternative information. Components can be arranged, grouped, displayed in any suitable order.


Conditional language used herein, such as, among others, “can,” “could” “might,” “may,” “e.g.,” and the like, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or states. Thus, such conditional language is not generally intended to imply that features, elements and/or states are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without author input or prompting, whether these features, elements and/or states are included or are to be performed in any particular embodiment. The terms “comprising,” “including,” “having,” and the like are synonymous and are used inclusively, in an open-ended fashion, and do not exclude additional elements, features, acts, operations, and so forth. Also, the term “or” is used in its inclusive sense (and not in its exclusive sense) so that when used, for example, to connect a list of elements, the term “or” means one, some, or all of the elements in the list. Further, the term “each,” as used herein, in addition to having its ordinary meaning, can mean any subset of a set of elements to which the term “each” is applied. Additionally, the words “herein,” “above,” “below,” and words of similar import, when used in this application, refer to this application as a whole and not to any particular portions of this application.


Conjunctive language such as the phrase “at least one of X, Y and Z,” unless specifically stated otherwise, is to be understood with the context as used in general to convey that an item, term, etc. may be either X, Y, or Z, or a combination thereof. Thus, such conjunctive language is not generally intended to imply that certain embodiments require at least one of X, at least one of Y and at least one of Z to each be present.


Language of degree used herein, such as the terms “approximately,” “about,” “generally,” and “substantially” as used herein represent a value, amount, or characteristic close to the stated value, amount, or characteristic that still performs a desired function or achieves a desired result. For example, the terms “approximately” “about” “generally,” and “substantially” may refer to an amount that is within less than 10% of, within less than 5% of, within less than 1% of, within less than 0.1% of, and within less than 0.01% of the stated amount. As another example, in certain embodiments, the terms “generally parallel” and “substantially parallel” refer to a value, amount, or characteristic that departs from exactly parallel by less than or equal to 15 degrees, 10 degrees, 5 degrees, 3 degrees, 1 degree, or 0.1 degree.


Unless otherwise explicitly stated, articles such as “a” or “an” should generally be interpreted to include one or more described items. Accordingly, phrases such as “a device configured to” are intended to include one or more recited devices. Such one or more recited devices can also be collectively configured to carry out the stated recitations.


Although the present disclosure includes certain embodiments, examples and applications, it will be understood by those skilled in the art that the present disclosure extends beyond the specifically disclosed embodiments to other alternative embodiments and/or uses and obvious modifications and equivalents thereof, including embodiments which do not provide all of the features and advantages set forth herein. Accordingly, the scope of the present disclosure is not intended to be limited by the specific disclosures of preferred embodiments herein, and may be defined by claims as presented herein or as presented in the future.

Claims
  • 1. A negative pressure wound therapy device comprising: a negative pressure source configured to be fluidically connected to a dressing positioned over a wound, the negative pressure source further configured to provide a negative pressure therapy to the wound; anda controller configured to: operate the negative pressure source to provide the negative pressure therapy to the wound in accordance with a default therapy prescription;prior to switching a therapy prescription for the negative pressure therapy from the default therapy prescription to an updated therapy prescription different from the default therapy prescription, cause a remote computer to determine, based on a usage data associated with provision of the negative pressure therapy over a time duration, compliance of the provision of the negative pressure therapy over at least a portion of the time duration with the updated therapy prescription;receive an indication from the remote computer that the provision of the negative pressure therapy over at least the portion of the time duration was noncompliant with the updated therapy prescription;in response to receipt of the indication, receive an authorization to switch the therapy prescription from the default therapy prescription to the updated therapy prescription; andin response to receipt of the authorization, operate the negative pressure source to provide the negative pressure therapy in accordance with the updated therapy prescription.
  • 2. The device of claim 1, further comprising a user interface, the controller further configured to: receive from the user interface a selection of the default therapy prescription.
  • 3. The device of claim 1, further comprising a user interface, the controller further configured to: provide a noncompliant therapy alert via the user interface.
  • 4. The device of claim 1, wherein the default therapy prescription specifies at least one of a first therapy duration, a first therapy intensity, or a first therapy mode, and wherein the updated therapy prescription specifies at least one of a second therapy duration, a second therapy intensity, or a second therapy mode.
  • 5. The device of claim 1, wherein the usage data indicates at least one of a therapy duration, a therapy intensity, or a therapy mode.
  • 6. The device of claim 1, wherein the controller is further configured to: receive the updated therapy prescription from the remote computer.
  • 7. The device of claim 1, wherein the controller is further configured to: receive the updated therapy prescription from the remote computer and not cause the negative pressure source to provide the negative pressure therapy in accordance with the updated therapy prescription until the receipt of the authorization.
  • 8. The device of claim 1, wherein: the negative pressure therapy is provided to the wound of a patient; andthe authorization is received from a clinician responsive to provision of a password or a biometric check verifying identity of the clinician.
  • 9. The device of claim 1, the controller is further configured to: cause the remote computer to determine the compliance prior to receiving the updated therapy prescription at the negative pressure wound therapy device.
  • 10. The device of claim 1, the controller is further configured to: provide the usage data to the remote computer.
  • 11. A method comprising: operating a negative pressure source to provide a negative pressure therapy to a wound in accordance with a default therapy prescription;prior to switching a therapy prescription for the negative pressure therapy from the default therapy prescription to an updated therapy prescription different from the default therapy prescription, causing a remote computer to determine, based on a usage data associated with provision of the negative pressure therapy over a time duration, compliance of the provision of the negative pressure therapy over at least a portion of the time duration with the updated therapy prescription;receiving an indication from the remote computer that the provision of the negative pressure therapy over at least the portion of the time duration was noncompliant with the updated therapy prescription;in response to receipt of the indication, receiving an authorization to switch the therapy prescription from the default therapy prescription to the updated therapy prescription; andin response to receipt of the authorization, operating the negative pressure source to provide the negative pressure therapy in accordance with the updated therapy prescription.
  • 12. The method of claim 11, further comprising: receiving from a user interface a selection of the default therapy prescription.
  • 13. The method of claim 11, further comprising: providing a noncompliant therapy alert via a user interface.
  • 14. The method of claim 11, wherein the default therapy prescription specifies at least one of a first therapy duration, a first therapy intensity, or a first therapy mode, and wherein the updated therapy prescription specifies at least one of a second therapy duration, a second therapy intensity, or a second therapy mode.
  • 15. The method of claim 11, wherein the usage data indicates at least one of a therapy duration, a therapy intensity, or a therapy mode.
  • 16. The method of claim 11, further comprising: receiving the updated therapy prescription from the remote computer.
  • 17. The method of claim 11, further comprising: receiving the updated therapy prescription from the remote computer and not causing the negative pressure source to provide the negative pressure therapy in accordance with the updated therapy prescription until the receipt of the authorization.
  • 18. The method of claim 11, wherein: the negative pressure therapy is provided to the wound of a patient; andthe authorization is received from a clinician responsive to provision of a password or a biometric check verifying identity of the clinician.
  • 19. The method of claim 11, further comprising: causing the remote computer to determine the compliance prior to receiving the updated therapy prescription.
  • 20. The method of claim 11, further comprising: providing the usage data to the remote computer.
Priority Claims (1)
Number Date Country Kind
1820668 Dec 2018 GB national
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 17/416,385, filed Jun. 18, 2021, which is a U.S. national stage application of International Patent Application No. PCT/EP2019/084611, filed Dec. 11, 2019, which claims priority to U.K. Provisional Application No. 1820668.0, filed on Dec. 19, 2018; the disclosure of each of which is hereby incorporated by reference in its entirety.

US Referenced Citations (594)
Number Name Date Kind
695270 Beringer Mar 1902 A
3194239 Sullivan et al. Jul 1965 A
4832299 Gorton et al. May 1989 A
5219428 Stern Jun 1993 A
5473536 Wimmer Dec 1995 A
5960403 Brown Sep 1999 A
6055506 Frasca et al. Apr 2000 A
6336900 Alleckson et al. Jan 2002 B1
6353445 Babula et al. Mar 2002 B1
6375614 Braun et al. Apr 2002 B1
6385622 Bouve et al. May 2002 B2
6406426 Reuss et al. Jun 2002 B1
6434572 Derzay et al. Aug 2002 B2
6460041 Lloyd Oct 2002 B2
6574518 Lounsberry et al. Jun 2003 B1
6640145 Hoffberg et al. Oct 2003 B2
6640246 Gary et al. Oct 2003 B1
6675131 Hahn Jan 2004 B2
6681003 Linder et al. Jan 2004 B2
6723046 Lichtenstein et al. Apr 2004 B2
6730024 Freyre et al. May 2004 B2
6747556 Medema et al. Jun 2004 B2
6779024 DeLaHuerga Aug 2004 B2
6782285 Birkenbach et al. Aug 2004 B2
6856825 Hahn Feb 2005 B2
6868528 Roberts Mar 2005 B2
6871211 Labounty et al. Mar 2005 B2
6909974 Yung et al. Jun 2005 B2
6912481 Breunissen et al. Jun 2005 B2
6961731 Holbrook Nov 2005 B2
7004915 Boynton et al. Feb 2006 B2
7022113 Lockwood et al. Apr 2006 B2
7051012 Cole et al. May 2006 B2
7062251 Birkett et al. Jun 2006 B2
7066883 Schmidt et al. Jun 2006 B2
7103578 Beck et al. Sep 2006 B2
7108683 Zamierowski Sep 2006 B2
7120488 Nova et al. Oct 2006 B2
7133869 Bryan et al. Nov 2006 B2
7167858 Naeymi-Rad et al. Jan 2007 B2
7212829 Lau et al. May 2007 B1
7264591 Brown Sep 2007 B2
7300418 Zaleski Nov 2007 B2
7304573 Postma Dec 2007 B2
7311665 Hawthorne et al. Dec 2007 B2
7333002 Bixler et al. Feb 2008 B2
7353179 Ott et al. Apr 2008 B2
7384267 Franks et al. Jun 2008 B1
7430598 Raden et al. Sep 2008 B2
7430608 Noonan et al. Sep 2008 B2
7438705 Karpowicz et al. Oct 2008 B2
7451002 Choubey Nov 2008 B2
7457804 Uber et al. Nov 2008 B2
7460872 Millard et al. Dec 2008 B2
7534240 Johnson May 2009 B1
7598855 Scalisi et al. Oct 2009 B2
7608066 Vogel Oct 2009 B2
7627334 Cohen et al. Dec 2009 B2
7649449 Fenske et al. Jan 2010 B2
7671733 McNeal et al. Mar 2010 B2
7684999 Brown Mar 2010 B2
7698156 Martucci et al. Apr 2010 B2
7734764 Weiner et al. Jun 2010 B2
7749164 Davis Jul 2010 B2
7758555 Kelch et al. Jul 2010 B2
7779153 Van den Heuvel et al. Aug 2010 B2
7789828 Clapp Sep 2010 B2
7794438 Henley et al. Sep 2010 B2
7827148 Mori et al. Nov 2010 B2
7865375 Lancaster et al. Jan 2011 B2
7889069 Fifolt et al. Feb 2011 B2
7890887 Linardos et al. Feb 2011 B1
7912823 Ferrari et al. Mar 2011 B2
7925603 Laidig et al. Apr 2011 B1
7933817 Radl et al. Apr 2011 B2
7976519 Bubb et al. Jul 2011 B2
7981098 Boehringer et al. Jul 2011 B2
7988850 Roncadi et al. Aug 2011 B2
8015443 Adachi Sep 2011 B2
8015972 Pirzada Sep 2011 B2
8019618 Brown Sep 2011 B2
8036925 Choubey Oct 2011 B2
8054950 Hung et al. Nov 2011 B1
8069057 Choubey et al. Nov 2011 B2
8094009 Allen et al. Jan 2012 B2
8126735 Dicks et al. Feb 2012 B2
8130095 Allen et al. Mar 2012 B2
8131472 Chow et al. Mar 2012 B2
8180750 Wilmering et al. May 2012 B2
8190445 Kuth et al. May 2012 B2
8190448 Bajars et al. May 2012 B2
8228188 Key et al. Jul 2012 B2
8246606 Stevenson et al. Aug 2012 B2
8249894 Brown Aug 2012 B2
8255241 Cafer Aug 2012 B2
8260630 Brown Sep 2012 B2
8280682 Vock et al. Oct 2012 B2
8284046 Allen et al. Oct 2012 B2
8290792 Sekura Oct 2012 B2
8291337 Gannin et al. Oct 2012 B2
8332233 Ott et al. Dec 2012 B2
8332236 Yurko et al. Dec 2012 B2
8334768 Eaton et al. Dec 2012 B2
8360975 Schwieterman et al. Jan 2013 B1
8361056 Wood, Jr. Jan 2013 B2
8400295 Khaira Mar 2013 B1
8422377 Weiner et al. Apr 2013 B2
8424517 Sutherland et al. Apr 2013 B2
8436871 Alberte May 2013 B2
8439882 Kelch May 2013 B2
8457740 Osche Jun 2013 B2
8480641 Jacobs Jul 2013 B2
8515776 Schoenberg Aug 2013 B2
8532764 Duke Sep 2013 B2
8540688 Eckstein et al. Sep 2013 B2
8545483 Schwabe et al. Oct 2013 B2
8554195 Rao Oct 2013 B2
8554902 Ebert et al. Oct 2013 B2
8558964 Bedingfield Oct 2013 B2
8560082 Wei Oct 2013 B2
8577694 Kanaan Nov 2013 B2
8595553 Goertler et al. Nov 2013 B2
8600777 Schoenberg et al. Dec 2013 B2
8626342 Williams et al. Jan 2014 B2
8626526 Lemke et al. Jan 2014 B2
8630660 Ray et al. Jan 2014 B2
8632485 Schlaeper et al. Jan 2014 B2
8641693 Locke et al. Feb 2014 B2
8659420 Salvat et al. Feb 2014 B2
8676597 Buehler et al. Mar 2014 B2
8689008 Rangadass et al. Apr 2014 B2
8694600 Gaines et al. Apr 2014 B2
8706537 Young et al. Apr 2014 B1
8725528 Locke et al. May 2014 B2
8756078 Collins, Jr. et al. Jun 2014 B2
8757485 Drees et al. Jun 2014 B2
8758315 Chen et al. Jun 2014 B2
8768441 De Zwart et al. Jul 2014 B2
8769625 Wang et al. Jul 2014 B2
8781847 Simms et al. Jul 2014 B2
8795171 Adamczyk Aug 2014 B2
8795244 Randolph et al. Aug 2014 B2
8838136 Carnes et al. Sep 2014 B2
8862393 Zhou et al. Oct 2014 B2
8868794 Masoud et al. Oct 2014 B2
8874035 Sherman et al. Oct 2014 B2
8887100 Cook et al. Nov 2014 B1
8890656 Pendse Nov 2014 B2
8897198 Gaines et al. Nov 2014 B2
8902278 Pinter et al. Dec 2014 B2
8905959 Basaglia Dec 2014 B2
8909595 Gandy et al. Dec 2014 B2
8912897 Carnes Dec 2014 B2
8922377 Carnes Dec 2014 B2
8945073 Croizat et al. Feb 2015 B2
8947237 Margon et al. Feb 2015 B2
8978026 Charlton et al. Mar 2015 B2
8996393 Sobie Mar 2015 B2
9047648 Lekutai et al. Jun 2015 B1
9058634 Buan et al. Jun 2015 B2
9081885 Bangera et al. Jul 2015 B2
9087141 Huang et al. Jul 2015 B2
9092705 Zhuang Jul 2015 B2
9098114 Potter et al. Aug 2015 B2
9105006 Williamson Aug 2015 B2
9114054 Bennett Aug 2015 B2
9117012 Basaglia Aug 2015 B2
9135398 Kaib et al. Sep 2015 B2
9141270 Stuart et al. Sep 2015 B1
9159148 Boyer et al. Oct 2015 B2
9215075 Poltorak Dec 2015 B1
9215516 Carnes et al. Dec 2015 B2
9215581 Julian et al. Dec 2015 B2
9230420 Lee et al. Jan 2016 B2
9268827 Fernandez Feb 2016 B2
9286443 Ford et al. Mar 2016 B2
9323893 Berry et al. Apr 2016 B2
9332363 Jain et al. May 2016 B2
9338819 Meng et al. May 2016 B2
9427159 Chang Aug 2016 B2
9436645 Al-Ali et al. Sep 2016 B2
9436800 Forrester Sep 2016 B2
9439584 De Vries et al. Sep 2016 B1
9460431 Curry Oct 2016 B2
9474679 Locke et al. Oct 2016 B2
9483614 Ash et al. Nov 2016 B2
9539373 Jones et al. Jan 2017 B2
9545466 Locke et al. Jan 2017 B2
9558331 Orona et al. Jan 2017 B2
9585565 Carnes Mar 2017 B2
9589247 Bolene et al. Mar 2017 B2
9602952 Kang et al. Mar 2017 B2
9629986 Patel et al. Apr 2017 B2
9658066 Yuen et al. May 2017 B2
9662438 Kamen et al. May 2017 B2
9687618 Steinhauer et al. Jun 2017 B2
9693691 Johnson Jul 2017 B2
9700462 DeBusk et al. Jul 2017 B2
9716757 Fernandes Jul 2017 B2
9740825 Sansale et al. Aug 2017 B2
9741084 Holmes et al. Aug 2017 B2
9787842 Brooksby et al. Oct 2017 B1
9792660 Cannon et al. Oct 2017 B2
9817948 Swank Nov 2017 B2
9818164 Nolte et al. Nov 2017 B2
9838645 Hyde et al. Dec 2017 B2
9878081 Leiendecker et al. Jan 2018 B2
9905123 Lawhorn Feb 2018 B2
9928478 Ragusky et al. Mar 2018 B2
9974492 Dicks et al. May 2018 B1
9990466 DeBusk et al. Jun 2018 B2
9996681 Suarez et al. Jun 2018 B2
10049346 Jensen et al. Aug 2018 B2
10061894 Sethumadhavan et al. Aug 2018 B2
10095649 Joshua et al. Oct 2018 B2
10127357 Whiting et al. Nov 2018 B2
10152575 Sexton et al. Dec 2018 B2
10173008 Simpson et al. Jan 2019 B2
10185834 Adam et al. Jan 2019 B2
10207031 Toth Feb 2019 B2
10328188 Deutsch et al. Jun 2019 B2
20020087360 Pettit Jul 2002 A1
20020128804 Geva Sep 2002 A1
20020128869 Kuth Sep 2002 A1
20020135336 Zhou et al. Sep 2002 A1
20020161317 Risk et al. Oct 2002 A1
20020177757 Britton Nov 2002 A1
20020184055 Naghavi et al. Dec 2002 A1
20030009244 Engleson et al. Jan 2003 A1
20030018736 Christ et al. Jan 2003 A1
20030105649 Sheiner et al. Jun 2003 A1
20030182158 Son Sep 2003 A1
20030221687 Kaigler Dec 2003 A1
20030229518 Abraham-Fuchs et al. Dec 2003 A1
20040006319 Lina et al. Jan 2004 A1
20040006492 Watanabe Jan 2004 A1
20040054775 Poliac et al. Mar 2004 A1
20040078223 Sacco et al. Apr 2004 A1
20040127774 Moore et al. Jul 2004 A1
20040143458 Pulkkinen et al. Jul 2004 A1
20040167802 Takada et al. Aug 2004 A1
20040167804 Simpson et al. Aug 2004 A1
20040172301 Mihai et al. Sep 2004 A1
20040181433 Blair Sep 2004 A1
20040187871 Kimmel et al. Sep 2004 A1
20040193449 Wildman et al. Sep 2004 A1
20040204962 Howser et al. Oct 2004 A1
20050033124 Kelly et al. Feb 2005 A1
20050055225 Mehl Mar 2005 A1
20050055242 Bello et al. Mar 2005 A1
20050055244 Mullan et al. Mar 2005 A1
20050060211 Xiao et al. Mar 2005 A1
20050065817 Mihai et al. Mar 2005 A1
20050097200 Denning, Jr. et al. May 2005 A1
20050102167 Kapoor May 2005 A1
20050108046 Craft May 2005 A1
20050108057 Cohen et al. May 2005 A1
20050114176 Dominick et al. May 2005 A1
20050119914 Batch Jun 2005 A1
20050222873 Nephin et al. Oct 2005 A1
20050240111 Chung Oct 2005 A1
20050283382 Donoghue et al. Dec 2005 A1
20060004604 White Jan 2006 A1
20060064323 Alleckson et al. Mar 2006 A1
20060085393 Modesitt Apr 2006 A1
20060089539 Miodownik et al. Apr 2006 A1
20060095853 Amyot et al. May 2006 A1
20060155584 Aggarwal Jul 2006 A1
20060161460 Smitherman et al. Jul 2006 A1
20060190130 Fedor et al. Aug 2006 A1
20060195843 Hall Aug 2006 A1
20060224051 Teller et al. Oct 2006 A1
20060246922 Gasbarro et al. Nov 2006 A1
20070136099 Neligh et al. Jun 2007 A1
20070156456 McGillin et al. Jul 2007 A1
20070197881 Wolf et al. Aug 2007 A1
20070219826 Brodsky et al. Sep 2007 A1
20070255116 Mehta et al. Nov 2007 A1
20070271298 Juang et al. Nov 2007 A1
20080009681 Al Hussiny Jan 2008 A1
20080086357 Choubey et al. Apr 2008 A1
20080091659 McFaul Apr 2008 A1
20080119705 Patel et al. May 2008 A1
20080126126 Ballai May 2008 A1
20080140160 Goetz et al. Jun 2008 A1
20080167534 Young et al. Jul 2008 A1
20080177579 Dehaan Jul 2008 A1
20080221396 Garces et al. Sep 2008 A1
20080242945 Gugliotti et al. Oct 2008 A1
20080312953 Claus Dec 2008 A1
20090033482 Hayter et al. Feb 2009 A1
20090037220 Chambers et al. Feb 2009 A1
20090048492 Rantala et al. Feb 2009 A1
20090048865 Breazeale, Jr. Feb 2009 A1
20090082641 Giftakis et al. Mar 2009 A1
20090097623 Bharadwaj Apr 2009 A1
20090099866 Newman Apr 2009 A1
20090099867 Newman Apr 2009 A1
20090115663 Brown et al. May 2009 A1
20090118591 Kim et al. May 2009 A1
20090125331 Pamsgaard et al. May 2009 A1
20090136909 Asukai et al. May 2009 A1
20090144091 Rago Jun 2009 A1
20090157429 Lee et al. Jun 2009 A1
20090163774 Thatha et al. Jun 2009 A1
20090171166 Amundson et al. Jul 2009 A1
20090177495 Abousy et al. Jul 2009 A1
20090187424 Grabowski Jul 2009 A1
20090204434 Breazeale, Jr. Aug 2009 A1
20090204435 Gale Aug 2009 A1
20090205042 Zhou et al. Aug 2009 A1
20090224889 Aggarwal et al. Sep 2009 A1
20090270833 DeBelser et al. Oct 2009 A1
20090281822 Warner et al. Nov 2009 A1
20090281830 McNames et al. Nov 2009 A1
20090281867 Sievenpiper et al. Nov 2009 A1
20090299306 Buan Dec 2009 A1
20090326339 Horvitz Dec 2009 A1
20090327102 Maniar et al. Dec 2009 A1
20100001838 Miodownik et al. Jan 2010 A1
20100017471 Brown et al. Jan 2010 A1
20100022848 Lee et al. Jan 2010 A1
20100022990 Karpowicz et al. Jan 2010 A1
20100030302 Blowers et al. Feb 2010 A1
20100036333 Schenk, III et al. Feb 2010 A1
20100042059 Pratt et al. Feb 2010 A1
20100042074 Weston et al. Feb 2010 A1
20100090004 Sands et al. Apr 2010 A1
20100106528 Brackett et al. Apr 2010 A1
20100113908 Vargas et al. May 2010 A1
20100145161 Niyato et al. Jun 2010 A1
20100150991 Bernstein Jun 2010 A1
20100207768 Pidgeon et al. Aug 2010 A1
20100222645 Nadler et al. Sep 2010 A1
20100222845 Goetz Sep 2010 A1
20100234708 Buck et al. Sep 2010 A1
20100255876 Jordan et al. Oct 2010 A1
20110004188 Shekalim Jan 2011 A1
20110063117 Turner et al. Mar 2011 A1
20110066110 Fathallah et al. Mar 2011 A1
20110071844 Cannon et al. Mar 2011 A1
20110073107 Rodman et al. Mar 2011 A1
20110077605 Karpowicz et al. Mar 2011 A1
20110092958 Jacobs Apr 2011 A1
20110106561 Eaton, Jr. et al. May 2011 A1
20110130730 Hartwell et al. Jun 2011 A1
20110137759 Wellington et al. Jun 2011 A1
20110145018 Fotsch et al. Jun 2011 A1
20110173028 Bond Jul 2011 A1
20110184754 Park et al. Jul 2011 A1
20110225008 Elkouh et al. Sep 2011 A1
20110246219 Smith et al. Oct 2011 A1
20110275353 Liu Nov 2011 A1
20110288878 Blair Nov 2011 A1
20120029312 Beaudry et al. Feb 2012 A1
20120029313 Burdett et al. Feb 2012 A1
20120032819 Chae et al. Feb 2012 A1
20120035427 Friedman et al. Feb 2012 A1
20120035560 Eddy et al. Feb 2012 A1
20120077605 Nakagaito et al. Mar 2012 A1
20120081225 Waugh et al. Apr 2012 A1
20120089369 Abuzeni et al. Apr 2012 A1
20120123323 Kagan et al. May 2012 A1
20120123796 McFaul May 2012 A1
20120136325 Allen et al. May 2012 A1
20120157889 Tanis et al. Jun 2012 A1
20120181405 Zlatic et al. Jul 2012 A1
20120182143 Gaines et al. Jul 2012 A1
20120185267 Kamen et al. Jul 2012 A1
20120191475 Pandey Jul 2012 A1
20120212455 Kloeffel Aug 2012 A1
20120215455 Patil et al. Aug 2012 A1
20120259651 Mallon et al. Oct 2012 A1
20120271256 Locke et al. Oct 2012 A1
20120290217 Shoval et al. Nov 2012 A1
20120295566 Collins et al. Nov 2012 A1
20120302975 Buan et al. Nov 2012 A1
20120310205 Lee et al. Dec 2012 A1
20130018355 Brand et al. Jan 2013 A1
20130023820 Solomon et al. Jan 2013 A1
20130035615 Hsieh Feb 2013 A1
20130045764 Vik et al. Feb 2013 A1
20130073303 Hsu Mar 2013 A1
20130076528 Boettner et al. Mar 2013 A1
20130087609 Nichol et al. Apr 2013 A1
20130090949 Tibebu Apr 2013 A1
20130103419 Beaudry Apr 2013 A1
20130124227 Ellis May 2013 A1
20130132855 Manicka et al. May 2013 A1
20130150686 Fronterhouse et al. Jun 2013 A1
20130150698 Hsu et al. Jun 2013 A1
20130150813 Gordon et al. Jun 2013 A1
20130151274 Bage et al. Jun 2013 A1
20130157571 Wondka et al. Jun 2013 A1
20130159456 Daoud et al. Jun 2013 A1
20130160082 Miller Jun 2013 A1
20130186405 Krzyzanowski et al. Jul 2013 A1
20130190903 Balakrishnan et al. Jul 2013 A1
20130191513 Kamen et al. Jul 2013 A1
20130196703 Masoud et al. Aug 2013 A1
20130204106 Bennett Aug 2013 A1
20130211206 Sands et al. Aug 2013 A1
20130211854 Wagstaff Aug 2013 A1
20130212168 Bonasera et al. Aug 2013 A1
20130214925 Weiss Aug 2013 A1
20130218053 Kaiser et al. Aug 2013 A1
20130226607 Woody et al. Aug 2013 A1
20130227128 Wagstaff Aug 2013 A1
20130231596 Hornbach et al. Sep 2013 A1
20130245387 Patel Sep 2013 A1
20130253952 Burke et al. Sep 2013 A1
20130255681 Batch et al. Oct 2013 A1
20130267919 Caso et al. Oct 2013 A1
20130268283 Vann et al. Oct 2013 A1
20130271556 Ross et al. Oct 2013 A1
20130282395 Rustgi et al. Oct 2013 A1
20130285837 Uchida Oct 2013 A1
20130297350 Gross et al. Nov 2013 A1
20130304489 Miller Nov 2013 A1
20130310726 Miller et al. Nov 2013 A1
20130317753 Kamen et al. Nov 2013 A1
20130325508 Johnson et al. Dec 2013 A1
20130331748 Wright et al. Dec 2013 A1
20130332197 Hinkel Dec 2013 A1
20130335233 Kamar et al. Dec 2013 A1
20130339049 Blumberg, Jr. et al. Dec 2013 A1
20130345524 Meyer et al. Dec 2013 A1
20140002234 Alwan Jan 2014 A1
20140018637 Bennett et al. Jan 2014 A1
20140028464 Garibaldi Jan 2014 A1
20140031884 Elghazzawi Jan 2014 A1
20140032231 Semen et al. Jan 2014 A1
20140039914 Dansereau et al. Feb 2014 A1
20140058714 Boyer Feb 2014 A1
20140087762 Galvin et al. Mar 2014 A1
20140108033 Akbay et al. Apr 2014 A1
20140108034 Akbay et al. Apr 2014 A1
20140108035 Akbay et al. Apr 2014 A1
20140129250 Daniel et al. May 2014 A1
20140148138 Chou May 2014 A1
20140171753 Montejo et al. Jun 2014 A1
20140187888 Hatziantoniou Jul 2014 A1
20140207090 Jian Jul 2014 A1
20140221788 Teller et al. Aug 2014 A1
20140222446 Ash et al. Aug 2014 A1
20140235975 Carnes Aug 2014 A1
20140244285 Hinkle et al. Aug 2014 A1
20140244301 Lee et al. Aug 2014 A1
20140244307 Shutko et al. Aug 2014 A1
20140266713 Sehgal et al. Sep 2014 A1
20140275876 Hansen et al. Sep 2014 A1
20140278502 Laskin Sep 2014 A1
20140280882 Lacerte et al. Sep 2014 A1
20140297299 Lester, IV Oct 2014 A1
20140316819 Dunsirn et al. Oct 2014 A1
20140350966 Khatana et al. Nov 2014 A1
20140366878 Baron Dec 2014 A1
20140371816 Matos Dec 2014 A1
20140372147 White Dec 2014 A1
20140372522 Orona et al. Dec 2014 A1
20140375470 Malveaux Dec 2014 A1
20140378895 Barack Dec 2014 A1
20150012290 Inciardi et al. Jan 2015 A1
20150019237 Doyle et al. Jan 2015 A1
20150019257 Doyle et al. Jan 2015 A1
20150025482 Begin et al. Jan 2015 A1
20150025486 Hu et al. Jan 2015 A1
20150046137 Zeilinger Feb 2015 A1
20150066531 Jacobson et al. Mar 2015 A1
20150072613 Swanson Mar 2015 A1
20150094830 Lipoma et al. Apr 2015 A1
20150095056 Ryan et al. Apr 2015 A1
20150095059 Yegge et al. Apr 2015 A1
20150095066 Ryan et al. Apr 2015 A1
20150100340 Folsom et al. Apr 2015 A1
20150112707 Manice et al. Apr 2015 A1
20150118662 Ellison et al. Apr 2015 A1
20150119652 Hyde et al. Apr 2015 A1
20150120318 Toyama Apr 2015 A1
20150143300 Zhang et al. May 2015 A1
20150164323 Holtzclaw Jun 2015 A1
20150164376 Huang Jun 2015 A1
20150186615 Armor et al. Jul 2015 A1
20150189001 Lee et al. Jul 2015 A1
20150227716 Ryan et al. Aug 2015 A1
20150227717 Ryan et al. Aug 2015 A1
20150228043 Ryan et al. Aug 2015 A1
20150234557 Dorn Aug 2015 A1
20150234995 Casady et al. Aug 2015 A1
20150242578 Siemon Aug 2015 A1
20150242583 Edson Aug 2015 A1
20150254403 Laperna Sep 2015 A1
20150257643 Watson et al. Sep 2015 A1
20150261920 Blick Sep 2015 A1
20150269323 Ginsburg Sep 2015 A1
20150286970 Dickerson et al. Oct 2015 A1
20150304478 Kim et al. Oct 2015 A1
20150310182 Henze et al. Oct 2015 A1
20150324943 Han et al. Nov 2015 A1
20150339445 Gruby et al. Nov 2015 A1
20150363058 Chung et al. Dec 2015 A1
20150370984 Russell et al. Dec 2015 A1
20150370997 Krongrad et al. Dec 2015 A1
20150379441 Syed et al. Dec 2015 A1
20160004824 Stanton et al. Jan 2016 A1
20160018963 Robbins et al. Jan 2016 A1
20160042154 Goldberg et al. Feb 2016 A1
20160044141 Pfutzenreuter et al. Feb 2016 A1
20160055310 Bentley et al. Feb 2016 A1
20160058286 Joshua et al. Mar 2016 A1
20160063210 Bardi et al. Mar 2016 A1
20160066864 Frieder et al. Mar 2016 A1
20160080365 Baker et al. Mar 2016 A1
20160085415 Humphrys et al. Mar 2016 A1
20160098524 Himmelstein Apr 2016 A1
20160110507 Abbo Apr 2016 A1
20160128571 Adler May 2016 A1
20160129186 Douglas et al. May 2016 A1
20160135752 Beaumont May 2016 A1
20160142443 Ting et al. May 2016 A1
20160151015 Condurso et al. Jun 2016 A1
20160154936 Kalathil Jun 2016 A1
20160154943 Cho et al. Jun 2016 A1
20160171866 Dupasquier et al. Jun 2016 A1
20160180031 Slater Jun 2016 A1
20160184497 Phillips et al. Jun 2016 A1
20160196399 Bonhomme Jul 2016 A1
20160203275 Benjamin et al. Jul 2016 A1
20160203283 Baruah et al. Jul 2016 A1
20160209837 Kim Jul 2016 A1
20160212577 Dor et al. Jul 2016 A1
20160217433 Walton et al. Jul 2016 A1
20160235901 Miller et al. Aug 2016 A1
20160246943 Lake et al. Aug 2016 A1
20160260035 Crooks et al. Sep 2016 A1
20160287189 Modai et al. Oct 2016 A1
20160308969 Aihara et al. Oct 2016 A1
20160321404 Ginsburg Nov 2016 A1
20160321422 Albright Nov 2016 A1
20160337362 Cameron Nov 2016 A1
20170007494 Rock et al. Jan 2017 A1
20170014028 Clear, Jr. Jan 2017 A1
20170017765 Yegge et al. Jan 2017 A1
20170032648 McClain et al. Feb 2017 A1
20170046503 Cho et al. Feb 2017 A1
20170053073 Allen et al. Feb 2017 A1
20170055205 Morris et al. Feb 2017 A1
20170068781 Zasowski et al. Mar 2017 A1
20170074717 Pilkington et al. Mar 2017 A1
20170078396 Haas et al. Mar 2017 A1
20170116373 Ginsburg et al. Apr 2017 A1
20170140120 Thrower May 2017 A1
20170150939 Shah Jun 2017 A1
20170165405 Muser et al. Jun 2017 A1
20170193181 Carter et al. Jul 2017 A1
20170212995 Ingmanson Jul 2017 A1
20170220755 Fowler et al. Aug 2017 A1
20170257682 Shtalryd Sep 2017 A1
20170270533 Barton et al. Sep 2017 A1
20170273116 Elghazzawi Sep 2017 A1
20170312161 Johnson et al. Nov 2017 A1
20170327371 Bai et al. Nov 2017 A1
20170372010 Doherty et al. Dec 2017 A1
20180004908 Barrus et al. Jan 2018 A1
20180052454 Magno et al. Feb 2018 A1
20180121629 Dyer et al. May 2018 A1
20180139572 Hansen May 2018 A1
20180144817 Lofgren et al. May 2018 A1
20180158545 Blomquist Jun 2018 A1
20180160907 Verma Jun 2018 A1
20180181714 Pillarisetty et al. Jun 2018 A1
20180224559 Park et al. Aug 2018 A1
20180233016 Daniel et al. Aug 2018 A1
20180233221 Blomquist Aug 2018 A1
20180234499 Borges et al. Aug 2018 A1
20180250452 Locke et al. Sep 2018 A1
20180279880 Bacchi Oct 2018 A1
20180280202 Pratt et al. Oct 2018 A1
20180286502 Lane et al. Oct 2018 A1
20180308569 Luellen Oct 2018 A1
20180308573 Hochrein et al. Oct 2018 A1
20180315492 Bishop et al. Nov 2018 A1
20180322944 Valdizan Nov 2018 A1
20190151156 Kieswetter et al. May 2019 A1
20190267127 Pemberton et al. Aug 2019 A1
20190295718 Lawhorn Sep 2019 A1
20190307957 Worden et al. Oct 2019 A1
20190355454 Deshpande Nov 2019 A1
20200078224 Carroll et al. Mar 2020 A1
20210030939 Heide et al. Feb 2021 A1
20210038775 Locke et al. Feb 2021 A1
20210060217 Locke et al. Mar 2021 A1
20220068453 Simpson Mar 2022 A1
20220257180 Armitstead Aug 2022 A1
Foreign Referenced Citations (242)
Number Date Country
102961815 Mar 2013 CN
104721892 Jun 2015 CN
102010036405 Jan 2012 DE
0980227 Feb 2000 EP
0566381 Jul 2002 EP
1231965 Aug 2002 EP
1291802 Mar 2003 EP
1309960 May 2003 EP
0814864 Dec 2003 EP
1407624 Apr 2004 EP
1011420 Dec 2004 EP
1495713 Jan 2005 EP
1524619 Apr 2005 EP
1540557 Jun 2005 EP
1579367 Sep 2005 EP
1587017 Oct 2005 EP
1788503 May 2007 EP
1839244 Oct 2007 EP
1839615 Oct 2007 EP
1857950 Nov 2007 EP
1870068 Dec 2007 EP
1904964 Apr 2008 EP
1934852 Jun 2008 EP
1975828 Oct 2008 EP
1993435 Nov 2008 EP
2038786 Mar 2009 EP
2040604 Apr 2009 EP
2092470 Aug 2009 EP
2146297 Jan 2010 EP
2172859 Apr 2010 EP
2214552 Aug 2010 EP
2218478 Aug 2010 EP
1404213 Mar 2011 EP
1247229 Apr 2011 EP
1406540 Jun 2011 EP
1812094 Aug 2011 EP
2384472 Nov 2011 EP
2226002 Jan 2012 EP
1610494 Mar 2012 EP
1248660 Apr 2012 EP
2023800 Apr 2012 EP
2451513 May 2012 EP
1248661 Aug 2012 EP
2488977 Aug 2012 EP
2562665 Feb 2013 EP
2619723 Jul 2013 EP
1881784 Oct 2013 EP
2664194 Nov 2013 EP
2743850 Jun 2014 EP
2745204 Jun 2014 EP
1684146 Jul 2014 EP
2841895 Mar 2015 EP
2850771 Mar 2015 EP
2876567 May 2015 EP
2891999 Jul 2015 EP
2894581 Jul 2015 EP
2906101 Aug 2015 EP
2945084 Nov 2015 EP
2962266 Jan 2016 EP
2968829 Jan 2016 EP
2973089 Jan 2016 EP
3000082 Mar 2016 EP
3010398 Apr 2016 EP
3054389 Aug 2016 EP
3070628 Sep 2016 EP
3078010 Oct 2016 EP
3096113 Nov 2016 EP
2563437 Mar 2017 EP
2773393 Mar 2017 EP
3134854 Mar 2017 EP
3027242 Apr 2017 EP
2556650 May 2017 EP
3174569 Jun 2017 EP
2632407 Aug 2017 EP
3209358 Aug 2017 EP
3041571 Sep 2017 EP
2856767 Nov 2017 EP
3252635 Dec 2017 EP
2320971 May 2018 EP
2335173 May 2018 EP
3100188 Jun 2018 EP
3330973 Jun 2018 EP
3352174 Jul 2018 EP
2440112 Oct 2018 EP
3400549 Nov 2018 EP
2992500 Dec 2018 EP
2597584 Jan 2019 EP
3219340 Jan 2019 EP
2890456 Feb 2019 EP
3377130 Apr 2019 EP
2881875 May 2019 EP
2866851 Sep 2019 EP
3899979 Oct 2021 EP
2409951 Jul 2005 GB
2436160 Sep 2007 GB
2449400 Nov 2008 GB
2456708 Jul 2009 GB
2423178 May 2010 GB
2475091 May 2011 GB
2488904 Sep 2012 GB
2446923 May 2013 GB
2499986 Sep 2013 GB
2491946 Aug 2014 GB
2499873 May 2016 GB
2533910 Jul 2016 GB
2541286 Feb 2017 GB
2550576 Jun 2018 GB
WO-9627163 Sep 1996 WO
WO-9744745 Nov 1997 WO
WO-9924927 May 1999 WO
WO-9963886 Dec 1999 WO
WO-0032088 Jun 2000 WO
WO-0060522 Oct 2000 WO
WO-0133457 May 2001 WO
WO-0181829 Nov 2001 WO
WO-0217075 Feb 2002 WO
WO-0233577 Apr 2002 WO
WO-02078594 Oct 2002 WO
WO-02101713 Dec 2002 WO
WO-03054668 Jul 2003 WO
WO-2004057514 Jul 2004 WO
WO-2004074457 Sep 2004 WO
WO-2005022349 Mar 2005 WO
WO-2005031632 Apr 2005 WO
WO-2005036447 Apr 2005 WO
WO-2005045461 May 2005 WO
WO-2005053793 Jun 2005 WO
WO-2005057466 Jun 2005 WO
WO-2005083619 Sep 2005 WO
WO-2005101282 Oct 2005 WO
WO-2005109297 Nov 2005 WO
WO-2005120097 Dec 2005 WO
WO-2006021154 Mar 2006 WO
WO-2006066583 Jun 2006 WO
WO-2006066585 Jun 2006 WO
WO-2006071711 Jul 2006 WO
WO-2006099120 Sep 2006 WO
WO-2006108304 Oct 2006 WO
WO-2006108858 Oct 2006 WO
WO-2006111109 Oct 2006 WO
WO-2007027490 Mar 2007 WO
WO-2007035646 Mar 2007 WO
WO-2007127879 Nov 2007 WO
WO-2007133478 Nov 2007 WO
WO-2007137869 Dec 2007 WO
WO-2008010012 Jan 2008 WO
WO-2008036344 Mar 2008 WO
WO-2008062382 May 2008 WO
WO-2008116295 Oct 2008 WO
WO-2008150633 Dec 2008 WO
WO-2009140669 Nov 2009 WO
WO-2010017484 Feb 2010 WO
WO-2010025166 Mar 2010 WO
WO-2010025467 Mar 2010 WO
WO-2010078558 Jul 2010 WO
WO-2010085033 Jul 2010 WO
WO-2010132617 Nov 2010 WO
WO-2010145780 Dec 2010 WO
WO-2011005633 Jan 2011 WO
WO-2011023384 Mar 2011 WO
WO-2011039676 Apr 2011 WO
WO-2011046860 Apr 2011 WO
WO-2011047334 Apr 2011 WO
WO-2011123933 Oct 2011 WO
WO-2011137230 Nov 2011 WO
WO-2012127281 Sep 2012 WO
WO-2013026999 Feb 2013 WO
WO-2013036853 Mar 2013 WO
WO-2013061887 May 2013 WO
WO-2013102855 Jul 2013 WO
WO-2013109517 Jul 2013 WO
WO-2013138182 Sep 2013 WO
WO-2013141870 Sep 2013 WO
WO-2013155193 Oct 2013 WO
WO-2013175076 Nov 2013 WO
WO-2014015215 Jan 2014 WO
WO-2014018786 Jan 2014 WO
WO-2014075494 May 2014 WO
WO-2014089086 Jun 2014 WO
WO-2014100036 Jun 2014 WO
WO-2014106056 Jul 2014 WO
WO-2014123846 Aug 2014 WO
WO-2014133822 Sep 2014 WO
WO-2014141221 Sep 2014 WO
WO-2014145496 Sep 2014 WO
WO-2014150255 Sep 2014 WO
WO-2014152963 Sep 2014 WO
WO-2014189070 Nov 2014 WO
WO-2014009876 Dec 2014 WO
WO-2015019273 Feb 2015 WO
WO-2015025482 Feb 2015 WO
WO-2015026387 Feb 2015 WO
WO-2015050816 Apr 2015 WO
WO-2015078112 Jun 2015 WO
WO-2015085249 Jun 2015 WO
WO-2015091070 Jun 2015 WO
WO-2015124670 Aug 2015 WO
WO-2015132528 Sep 2015 WO
WO-2015140801 Sep 2015 WO
WO-2015143099 Sep 2015 WO
WO-2015145455 Oct 2015 WO
WO-2015156143 Oct 2015 WO
WO-2015164787 Oct 2015 WO
WO-2015179915 Dec 2015 WO
WO-2015179916 Dec 2015 WO
WO-2015179917 Dec 2015 WO
WO-2015181836 Dec 2015 WO
WO-2015187480 Dec 2015 WO
WO-2016001088 Jan 2016 WO
WO-2016006536 Jan 2016 WO
WO-2016075656 May 2016 WO
WO-2016108163 Jul 2016 WO
WO-2016118318 Jul 2016 WO
WO-2016120820 Aug 2016 WO
WO-2016136694 Sep 2016 WO
WO-2016141799 Sep 2016 WO
WO-2016151364 Sep 2016 WO
WO-2016160849 Oct 2016 WO
WO-2016175649 Nov 2016 WO
WO-2016178936 Nov 2016 WO
WO-2016190978 Dec 2016 WO
WO-2017001848 Jan 2017 WO
WO-2017004423 Jan 2017 WO
WO-2017027729 Feb 2017 WO
WO-2017035024 Mar 2017 WO
WO-2017053384 Mar 2017 WO
WO-2017062042 Apr 2017 WO
WO-2017142100 Aug 2017 WO
WO-2017165895 Sep 2017 WO
WO-2017192673 Nov 2017 WO
WO-2018007100 Jan 2018 WO
WO-2018013666 Jan 2018 WO
WO-2018033819 Feb 2018 WO
WO-2018044894 Mar 2018 WO
WO-2018064234 Apr 2018 WO
WO-2018067593 Apr 2018 WO
WO-2018082813 May 2018 WO
WO-2018091492 May 2018 WO
WO-2018096390 May 2018 WO
WO-2018108724 Jun 2018 WO
WO-2018145880 Aug 2018 WO
WO-2020051273 Mar 2020 WO
Non-Patent Literature Citations (6)
Entry
Cinterion., “Cinterion PHS8-P 3G HSPA+,” retrieved from http://www.cinterion.com/tl_files/cinterion/downloads/cinterion_datasheet_PHSS_web.pdf, 2012, 2 pages.
International Preliminary Report on Patentability for Application No. PCT/EP2019/084611, mailed on Jul. 1, 2021, 9 pages.
International Preliminary Report on Patentability for Application No. PCT/US2014/026692, mailed on Sep. 24, 2015, 16 pages.
International Search Report and Written Opinion for Application No. PCT/EP2019/084611, mailed on Mar. 17, 2020, 10 pages.
International Search Report and Written Opinion for Application No. PCT/US2014/026692, mailed on Mar. 2, 2015, 26 pages.
Invitation to Pay and Partial International Search Report for Application No. PCT/US2014/026692, mailed on Sep. 26, 2014, 9 pages.
Related Publications (2)
Number Date Country
20240131248 A1 Apr 2024 US
20240226414 A9 Jul 2024 US
Continuations (1)
Number Date Country
Parent 17416385 US
Child 18382877 US