Reduced pressure therapy device operation and authorization monitoring

Information

  • Patent Grant
  • 11783943
  • Patent Number
    11,783,943
  • Date Filed
    Thursday, March 24, 2022
    2 years ago
  • Date Issued
    Tuesday, October 10, 2023
    8 months ago
Abstract
Embodiments of a negative pressure wound therapy systems and methods for operating the systems are disclosed. In some embodiments, a system includes a pump assembly, canister, and a wound dressing configured to be positioned over a wound. The pump assembly, canister, and the wound dressing can be fluidically connected to facilitate delivery of negative pressure to a wound. The pump assembly can be configured to communicate data to a remote computer. The data can include location information, usage information, therapy information, and the like. Remote management and tracking of the pump assembly can be performed.
Description
BACKGROUND
Field

Embodiments of the present disclosure relate to methods and apparatuses for dressing and treating a wound with reduced pressure therapy or topical negative pressure (TNP) therapy. In particular, but without limitation, embodiments disclosed herein relate to negative pressure therapy devices, methods for controlling the operation of TNP systems, and methods of using TNP systems.


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 oedema, encouraging blood flow, stimulating the formation of granulation tissue, removing excess exudates and may reduce bacterial load and, thus, infection to the wound. Furthermore, TNP therapy permits less outside disturbance of the wound and promotes more rapid healing.


SUMMARY

In some embodiments, an apparatus for processing registration and usage information for a plurality of negative pressure wound therapy devices includes a memory and a computer system including computer hardware. The memory is configured to store account information for a plurality of negative wound pressure therapy devices. The computer system is in communication with the memory. The computer system is configured to: receive a registration request to register a negative wound pressure therapy device of the plurality of negative wound pressure therapy devices to an account in the account information, the account associated with a user; determine, based at least on the registration request, whether the negative wound pressure therapy device is authorized to be registered to the account; in response to determining that the negative wound pressure therapy device is not authorized to be registered to the account, perform a first exception action; in response to determining that the negative wound pressure therapy device is authorized to be registered to the account, register the negative wound pressure therapy device to the account so that data gathered by the computer system about operations of the negative wound pressure therapy device is accessible via the account; receive a usage notification for the negative wound pressure therapy device, the usage notification indicating a location of the negative wound pressure therapy device and an operation performed by the negative wound pressure therapy device; determine, based at least on the usage notification, whether the negative wound pressure therapy device is being operated at an authorized location and whether the operation performed by the negative wound pressure therapy device is an authorized operation; in response to determining that the negative wound pressure therapy device is not operated in the authorized location or that the operation performed by the negative wound pressure therapy device is not the authorized operation, perform a second exception action; and in response to determining that the negative wound pressure therapy device is operated in the authorized location and the operation performed by the negative wound pressure therapy device is the authorized operation, store in the memory an indication of performance of the operation by the negative wound pressure therapy device to the account.


In some embodiments, the apparatus of the preceding paragraph can include one or more of the following features. The computer system can be configured to receive the registration request from a user system via a computer network, and the registration request can include a first account identifier corresponding to the account and a first device identifier corresponding to the negative wound pressure therapy device. The computer system can be configured to use a look-up table comprising account identifiers and device identifiers to determine whether the negative wound pressure therapy device is authorized to be registered to the account, and the account identifiers can include the first account identifier and the device identifiers can include the first device identifier. The first exception action can include generation and transmission of a notification communication to an owner of the account or an administrator of a group that includes the account, and the notification communication can indicate that the negative wound pressure therapy device was attempted to be registered to the account and that the negative wound pressure therapy device is unauthorized to be registered to the account. The first exception action can include generation and transmission of a command message to the negative wound pressure therapy device, and the command message can instruct the negative wound pressure therapy device not to perform one or more operations. The computer system can be configured to receive the usage indication from the negative wound pressure therapy device via a computer network, and the usage notification can provide the location as a Global Positioning System (GPS) location. The computer system can be configured to use a look-up table comprising device identifiers and location identifiers to determine whether the negative wound pressure therapy device is operated at the authorized location, and the device identifiers can include a first device identifier corresponding to the negative wound pressure therapy device and the location identifiers can include a first location identifier corresponding to the authorized location. The computer system can be configured to use a look-up table comprising device identifiers and operation identifiers to determine whether the operation performed by the negative wound pressure therapy device is the authorized operation, and the device identifiers can include a first device identifier corresponding to the negative wound pressure therapy device and the operation identifiers can include a first operation identifier corresponding to the authorized operation. The second exception action can include generation and transmission of a notification communication to an owner of the account or an administrator of a group that includes the account, and the notification communication can indicate that the negative wound pressure therapy device is operated outside of the authorized location. The second exception action can include generation and transmission of a notification communication to an owner of the account or an administrator of a group that includes the account, and the notification communication can indicate that the negative wound pressure therapy device performed an unauthorized operation. The first exception action can include generation and transmission of a command message to the negative wound pressure therapy device, and the command message can instruct the negative wound pressure therapy device not to perform one or more operations. The first exception action can be the same as the second exception action.


In some embodiments, a method of operating the apparatus of any of the preceding two paragraphs is disclosed.


In some embodiments, an apparatus for applying negative pressure therapy to a wound is disclosed. The apparatus includes a source of negative pressure and a controller. The source of negative pressure is configured to be fluidically connected to a dressing configured to be placed over a wound. The source of negative pressure is configured to deliver negative pressure wound therapy to the wound. The controller is configured to: control operations of the source of negative pressure; record operation data indicative of the operations performed by the source of negative pressure; record location data corresponding to geographical locations of the source of negative pressure over time; transmit to a remote computer over a communication interface via a computer network at least some of the operation data and at least some of the location data; and vary, based at least on one or more conditions, a timing of at least one of (i) when the controller records the operation data or the location data or (ii) when the controller transmits the at least some of the operation data and the at least some of the location data.


In some embodiments, the apparatus of the preceding paragraph can include one or more of the following features. The one or more conditions can include one or more of: (i) the controller transitioning from a first mode of operation for the source of negative pressure to a second mode of operation for the source of negative pressure different from the first mode of operation, (ii) the controller connecting to a communications network, (iii) the source of negative pressure or the controller being powered by a mains power source rather than by a battery, (iv) the controller operating in a high power mode rather than a low power mode, (v) a communications network connection being enabled for the controller, (vi) the source of negative pressure or the controller being powered on or powered off, and (vii) data being gathered to the controller as a result of provision of therapy rather than being loaded to the controller from an external connection port of a housing comprising the source of negative pressure and the controller.


In some embodiments, a method of operating the apparatus of any of the preceding two paragraphs is disclosed.





BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the present disclosure will now be described hereinafter, by way of example only, with reference to the accompanying drawings in which:



FIG. 1 illustrates a reduced pressure wound therapy system according to some embodiments.



FIGS. 2A-2C illustrate a pump assembly and canister according to some embodiments.



FIG. 3 illustrates an electrical component schematic of a pump assembly according to some embodiments.



FIG. 4 illustrates a system schematic according to some embodiments.



FIGS. 5A-5C illustrate graphical user interface screens according to some embodiments.



FIG. 6 illustrates a process for validating the registration and usage of a pump assembly with a remote server according to some embodiments.





DETAILED DESCRIPTION OF SOME EMBODIMENTS
Overview

Embodiments disclosed herein relate to systems and methods of treating a wound with reduced pressure. 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 absolute pressure that is X mmHg below 760 mmHg or, in other words, an absolute 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 (e.g., −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 (e.g., −80 mmHg is more than −60 mmHg). In some embodiments, local ambient atmospheric pressure is used as a reference point, and such local atmospheric pressure may not necessarily be, for example, 760 mmHg.


Embodiments of the present disclosure are generally applicable to use in 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 embodiments, 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.


Negative Pressure System


FIG. 1 illustrates an embodiment of 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, the pump assembly can be a canisterless pump assembly (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. The wound cover 120 can have 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 lumen or any other conduit or lumen disclosed herein can be formed from polyurethane, PVC, nylon, polyethylene, silicone, or any other suitable material.


Some embodiments of the wound cover 120 can have a port (not shown) configured to receive an end of the conduit 140. In other embodiments, 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 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 embodiments, 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. The pump assembly 150 can be miniaturized and portable, although larger conventional pumps 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 embodiments, 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. The components of the TNP system described herein can be particularly suited for incisional wounds that exude a small amount of wound exudate.


Some embodiments of the system are designed to operate without the use of an exudate canister. Some embodiments can be configured to support an exudate canister. In some embodiments, configuring the pump assembly 150 and conduit 140 so that the conduit 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 embodiments, 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. 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 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 embodiments, 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 setpoints. Low setpoint 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 setpoint 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 setpoint can be delivered for a first time duration, and upon expiration of the first time duration, negative pressure at high setpoint can be delivered for a second time duration. Upon expiration of the second time duration, negative pressure at low setpoint can be delivered. The first and second time durations can be same or different values. The first and second 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 embodiments, switching between low and high setpoints 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 (e.g., wound exudate) is drawn through the conduit 140, and can be stored in a canister. In some embodiments, 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. 2011/0213287, 2011/0282309, 2012/0116334, 2012/0136325, and 2013/0110058, which are incorporated by reference in their entirety. In other embodiments, other suitable wound dressings can be utilized.


Pump Assembly and Canister


FIG. 2A illustrates a front view 200A of a pump assembly 230, such as the pump assembly 150, and canister 220 according to some embodiments. As is illustrated, the pump assembly 230 and the canister 220 are connected, thereby forming a device. 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, such as patient or medical care provider, 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. The pump assembly 230 can comprise additional indicators. The pump assembly can use a single indicator or multiple indicators. Any suitable indicator 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 a 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 208 formed in a case of the pump assembly. The display 206 can be a touchscreen display. 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 210 formed in the case of the pump assembly. The gripping portion 210 can be configured to assist the user to hold the pump assembly 230, such as during removal of the canister 220. 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, there buttons 212a, 212b, and 212c are included. Button 212a can be configured as a power button to turn on/off the pump assembly 230. Button 212b can be configured as a play/pause button for the delivery of negative pressure therapy. For example, pressing the button 212b can cause therapy to start, and pressing the button 212b afterward can cause therapy to pause or end. Button 212c can be configured to lock the display 206 and/or the buttons 212. For instance, button 212c can be pressed so that the user does not unintentionally alter the delivery of the therapy. Button 212c can be depressed to unlock the controls. In other embodiments, additional buttons can be used or one or more of the illustrated buttons 212a, 212b, or 212c can be omitted. Multiple key presses and/or sequences of key presses can be used to operate the pump assembly 230.


The pump assembly 230 includes one or more latch recesses 222 formed in the cover. In the illustrated embodiment, two latch recesses 222 can be formed on the sides of the pump assembly 230. The latch recesses 222 can be configured to allow attachment and detachment of the canister 220 using one or more canister latches 221. The pump assembly 230 comprises an air outlet 224 for allowing air removed from the wound cavity 110 to escape. Air entering the pump assembly 230 can be passed through one or more suitable filters, such as antibacterial filters. This can maintain reusability of the pump assembly 230. 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 the illustrated embodiment, two strap mounts 226 can be formed on the sides of the pump assembly 230. In some embodiments, various of these features are omitted and/or various additional features are added to the pump assembly 230.


The canister 220 is configured to hold fluid (e.g., exudate) removed from the wound cavity 110. The canister 220 includes one or more latches 221 for attaching the canister to the pump assembly 230. In the illustrated embodiment, the canister 220 comprises two latches 221 on the sides of the canister. The exterior of the canister 220 can 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 comprises a gripping portion 214 formed in a case of the canister. The gripping portion 214 can be configured to allow the user to hold the pump assembly 220, such as during removal of the canister from the apparatus 230. The canister 220 includes a substantially transparent window 216, 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. For example, the canister can be an 800 mL canister. The canister 220 comprises a tubing channel 218 for connecting to the conduit 140. In some embodiments, various of these features, such as the gripping portion 214, are omitted and/or various additional features are added to the canister 220. Any of the disclosed canisters may include or may omit a solidifier.



FIG. 2B illustrates a rear view 200B of the pump assembly 230 and canister 220 according to some embodiments. The pump assembly 230 comprises a speaker port 232 for producing sound. The pump assembly 230 includes a filter access door 234 for accessing and replacing one or more filters, such as antibacterial filters. The pump assembly 230 comprises a gripping portion 236 formed in the case of the pump assembly 230. The gripping portion 236 can be configured to allow the user to hold the pump assembly 230, such as during removal of the canister 220. The pump assembly 230 includes one or more covers 238 configured to as screw covers and/or feet or protectors for placing the pump assembly 230 on a surface. The covers 230 can be formed out of rubber, silicone, or any other suitable material. The pump assembly 230 comprises a power jack 239 for charging and recharging an internal battery of the pump assembly. The power jack 239 can be a direct current (DC) jack. In some embodiments, the pump assembly 230 can comprise a disposable power source, such as batteries, so that no power jack is needed.


The canister 220 includes one or more feet 244 for placing the canister on a surface. The feet 244 can be formed out of rubber, silicone, or any other suitable material and can be angled at a suitable angle so that the canister 220 remains stable when placed on the surface. The canister 220 comprises a tube mount relief 246 configured to allow one or more tubes to exit to the front of the device. The canister 220 includes a stand or kickstand 248 for supporting the canister when it is placed on a surface. As explained below, the kickstand 248 can pivot between an opened and closed position. In closed position, the kickstand 248 can be latched to the canister 220. In some embodiments, the kickstand 248 can be made out of opaque material, such as plastic. In other embodiments, the kickstand 248 can be made out of transparent material. The kickstand 248 includes a gripping portion 242 formed in the kickstand. The gripping portion 242 can be configured to allow the user to place the kickstand 248 in the closed position. The kickstand 248 comprises a hole 249 to allow the user to place the kickstand in the open position. The hole 249 can be sized to allow the user to extend the kickstand using a finger.



FIG. 2C illustrates a view 200C of the pump assembly 230 separated from the canister 220 according to some embodiments. The pump assembly 230 includes a vacuum attachment, connector, or inlet 252 through which a vacuum pump communicates negative pressure to the canister 220. The pump assembly aspirates fluid, such as gas, from the wound via the inlet 252. The pump assembly 230 comprises a USB access door 256 configured to allow access to one or more USB ports. In some embodiments, the USB access door is omitted and USB ports are accessed through the door 234. The pump assembly 230 can include additional access doors configured to allow access to additional serial, parallel, and/or hybrid data transfer interfaces, such as SD, Compact Disc (CD), DVD, FireWire, Thunderbolt, PCI Express, and the like. In other embodiments, one or more of these additional ports are accessed through the door 234.


Additional description of the pump assembly 230 is disclosed in U.S. patent application Ser. No. 14/210,062, filed on Mar. 13, 2014 and titled “SYSTEMS AND METHODS FOR APPLYING REDUCED PRESSURE THERAPY,” which is incorporated by reference in its entirety.


Electronics and Software


FIG. 3 illustrates an electrical component schematic 300 of a pump assembly, such as the pump assembly 150, according to some embodiments. Electrical components can operate to accept user input, provide output to the user, operate the pump assembly and the TNP system, provide network connectivity, and so on. Electrical components can be mounted on one or more printed circuit boards (PCBs). As is illustrated, the pump assembly can include multiple processors. It may be advantageous to utilize multiple processors in order to allocate or assign various tasks to different processors. A first processor can be responsible for user activity and a second processor can be responsible for controlling the pump. This way, the activity of controlling the pump, 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.


The pump assembly can comprise a user interface processor or controller 310 configured to operate one or more components for accepting user input and providing output to the user, such as the display 206, buttons 212, etc. Input to the pump assembly and output from the pump assembly can controlled by an input/output (I/O) module 320. For example, the I/O module can receive data from one or more ports, such as serial, 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 embodiments, the processor 310 can be a general purpose controller, such as a low-power processor. In other embodiments, the processor 310 can be an application specific processor. The processor 310 can be configured as a “central” processor in the electronic architecture of the pump assembly, 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 (e.g., processor for controlling the display 206, processor for controlling the buttons 212, etc.). The processor 310 can run a suitable operating system, such as a Linux, Windows CE, VxWorks, etc.


The pump control processor 370 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. The pump can include one or more valves, such as inlet and outlet (or exhaust) valves. The valves can be configured to open and close to enable the pump to aspirate fluid from the wound cavity 110. 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. The pump control processor 370 can control a pump motor so that a desired level of negative pressure is achieved in the wound cavity 110. The desired level of negative pressure can be pressure set or selected by the user. In various embodiments, the pump control processor 370 controls the pump (e.g., 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 various conditions in a flow path. 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. In some embodiments, processor 310 is configured to control the pump 390, and pump control processor 370 is not used.


A communications processor 330 can be configured to provide wired and/or wireless connectivity. The communications processor 330 can utilize one or more antennas 340 for sending and receiving data. The communications processor 330 can provide one or more of the following types of connections: Global Positioning System (GPS) technology, cellular connectivity (e.g., 2G, 3G, LTE, 4G), 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. 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 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. The pump assembly 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 embodiments, the pump assembly can track and store various data, such as one or more of positioning data, therapy parameters, logs, device data, and so on. The pump assembly can track and log therapy and other operational data. Data can be stored, for example, in the memory 350. The frequency or triggering of tracking or storing the various data can moreover vary depending on one or more conditions. For example, the various data (e.g., positioning data for a pump assembly) can be tracked or stored periodically, such as once per day, hour, or minute, or with more or less frequency. As another example, the various data (e.g., positioning data for a pump assembly) can be tracked or stored when the pump assembly changes its mode of operation (e.g., initiates or stops providing therapy), connects to a communications network (e.g., 3G or WiFi network) using the communications processor 330, and the like. Such frequency or triggering control can, in certain embodiments, advantageously enable protection of the privacy of users of the pump assembly such that limited information about the use or possession of the pump assembly are tracked or stored.


In some embodiments, using the connectivity provided by the communications processor 330, the device can upload any of the data stored, maintained, and/or tracked by the pump assembly. For example, the following information can be uploaded to a remote computer or server: 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 device can also download various operational data, such as therapy selection and parameters, firmware and software patches and upgrades, and the like. The pump assembly can provide Internet browsing functionality using one or more browser programs, mail programs, application software (e.g., apps), etc.


In some embodiments, the communications processor 330 can use the antenna 340 to communicate a location of the pump assembly, such as a location of a housing of the pump assembly, to other devices in the proximity (for example, within 10, 20, or 50 meters and the like) of the pump assembly. The communications processor 330 can perform one-way or two-way communication with the other devices depending on the implementation. The communications transmitted by the communications processor 330 can include identifying information to uniquely identify the pump assembly relative to one or more other pump assemblies also in the proximity of the pump assembly. For example, identifying information can include a serial number or a value derived from the serial number. The signal strength of the transmitted communications by the communications processor 330 can be controlled (for example, maintained at a constant or substantially constant level) to enable another device to determine a distance to the pump assembly, such as a distance between the device and the pump assembly.


In some embodiments, the communications processor 330 can communicate with other devices in the proximity of the pump assembly so that the communications processor 330 can itself determine a distance from the pump assembly to the other devices. The communications processor 330, in such embodiments, can track and store the distance from the pump assembly to the other devices or indications of change in the distance over time, and the communications processor 330 can later provide this information to the other devices. For instance, the communications processor 330 can determine a duration of time during which the pump assembly has been removed from a coverage area of a device and subsequently report this time to the device upon being returned to the coverage area.



FIG. 4 illustrates a system schematic 400 according to some embodiments. A pump assembly 420, such as the pump assembly 150, 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 424, 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 428, which can be executed by one or more additional processors 380. The pump assembly 420 can be connected to a user computer 410, which can be a laptop, desktop, tablet, smartphone, and the like. A wired or wireless connection can be utilized to connect the computer 410 to the pump assembly 420. For example, a USB connection can be used. The connection between the computer 410 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 computer 410 can communicate with a remote computer or server 440 via the cloud 430. As is used herein, the term “cloud” and the like, in addition to having its ordinary meaning, can refer to the Internet. The remote computer 440 can include a data storage module 442 and a web interface 444 for accessing the remote computer 440. The remote computer 440 includes a processor 446, such as one or more CPUs. In some embodiments, the remote computer 440 includes multiple computers.


The connection between the computer 410 and 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 embodiments, the computer 410 can execute an application program for communicating the pump assembly 420.


The pump assembly 420 can upload various data to the remote computer (or multiple remote computers) 440 via the cloud 430. As explained above, upload data can include activity log(s), alarm log(s), 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 cloud 430.


In some embodiments, the frequency or triggering of uploading various data by the pump assembly can moreover vary depending on one or more conditions. In one example, the various data can be uploaded with a frequency that depends on whether an external power source is connected to the pump assembly (e.g., the various data can be uploaded more frequently when connected to line or mains power than when not connected to mains power) and/or certain power settings for the pump assembly (e.g., the various data can be uploaded less frequently when power settings indicate a lower power mode of operation for the pump assembly). For instance, the pump assembly can upload positioning data (i) once per hour when the pump assembly is connected to mains power and when a backlight of the touchscreen is on indicating a higher power mode of operation for the pump assembly and (ii) once per two hours when the pump assembly is not connected to mains power (e.g., pump assembly is running off battery power) or when the backlight of the touchscreen is off indicating a lower power mode of operation for the pump assembly. In another example, the various data may be uploaded when a communications network connection is enabled for the pump assembly or when the pump assembly is connected to a communications network, but not when communications network connection is disabled or when the pump assembly is not connected to the communications network. In yet another example, the powering on or off of the pump assembly can trigger the transmission of the various data, potentially with a delay in some implementations (e.g., data transmission can be triggered ten minutes after power on of a pump assembly if more than one hour has elapsed since a last power off of the pump assembly). In a further example, when data is loaded to the pump assembly (e.g., via the I/O module 320, expansion module 360, etc.) rather than collected by the pump assembly (e.g., as a result of the provision of therapy by the pump assembly), the transmission of the various data, such as the data loaded to the pump assembly, can be triggered.


In some embodiments, the computer 410 can be used to create an account with the remote computer 440 and register one or more pump assemblies to the account. The computer 410 can then, for example, be used to login to the account to access saved therapy data for the one or more registered pump assemblies, access operation instructions for the one or more registered pump assemblies, enable or control certain functionality of the one or more registered pump assemblies, and the like. The registration process can additionally enable possession or usage of the one or more registered pump assemblies to be attributed to an account owner so that any restrictions on use (e.g., use limited to specific entities, within geographic areas, or under certain contractual terms) for the one or more pump assemblies may be tracked or enforced.


Operation of the Pump Assembly

In some embodiments, the pump assembly 230 can be operated using a touchscreen interface displayed on the screen 206. Various graphical user interface (GUI) screens present information on systems settings and operations, among other things. The touchscreen interface can be actuated or operated by a finger (or a stylus or another suitable device). Tapping a touchscreen cam result in making a selection. To scroll, a user can touchscreen and hold and drag to view the selections. Additional or alternative ways to operate the touchscreen interface can be implemented, such as multiple finger swipes for scrolling, multiple finger pinch for zooming, and the like.



FIGS. 5A-5C illustrate graphical user interface screens according to some embodiments. The GUI screens can be displayed on the screen 206, which can be configured as a touchscreen interface. Information displayed on the screens can be generated based on input received from the user. The GUI screens can be utilized for initializing the device, selecting and adjusting therapy settings, monitoring device operation, uploading data to the network (e.g., cloud), and the like. The illustrated GUI screens can be generated directly by an operating system running on the processor 310 and/or by a graphical user interface layer or component running on the operating system. For instance, the screens can be developed using Qt framework available from Digia.



FIG. 5A illustrates a therapy settings screen 500A according to some embodiments. The therapy settings screen 500A can be displayed after the pump assembly has been initialized (e.g., screen 500A can function as a home screen). The therapy settings screen 500A includes a status bar 502 that comprises icons indicating operational parameters of the device. Animated icon 503 is a therapy delivery indicator. When therapy is not being delivered, icon 503 can be static and displayed in a color, such as gray. When therapy is being delivered, icon 503 can turn a different color, such as orange, and becomes animated, such as, rotates, pulsates, become filled with color, etc. Other status bar icons include a volume indicator and a battery indicator, and may include additional icons, such as wireless connectivity. The therapy settings screen 500A includes date/time and information. The therapy settings screen 500A includes a menu 510 that comprises menu items 512 for accessing device settings, 514 for accessing logs, 516 for accessing help, and 518 for returning to the therapy settings screen (or home screen) from other screens. The pump assembly can be configured so that after a period of inactivity, such as not receiving input from the user, therapy settings screen 500A (or home screen) is displayed. Additional or alternative controls, indicators, messages, icons, and the like can be used.


The therapy settings screen 500A includes negative pressure up and down controls 522 and 524. Up and down controls 522 and 524 can be configured to adjust the negative pressure setpoint by a suitable step size, such as ±5 mmHg. As is indicated by label 526, the current therapy selection is −80 mmHg (or 80 mmHg below atmospheric pressure). The therapy settings screen 500A includes continuous/intermittent therapy selection 530. Continuous therapy selection screen can be accessed via control 532 and intermittent therapy selection screen can be accessed via control 534. As is illustrated, the current therapy setting is to continuously deliver negative pressure at −80 mmHg. As is indicated by message 528, therapy delivery can be initiated by pressing a button, such as button 212b on the pump assembly 230. The therapy settings screen 500A includes Y-connector selection 535 for treating multiple wounds, such as two, three, etc. wounds, with one pump assembly 230. Control 536 selects treatment of a single wound, and control 538 selects treatment of more than one wound by the pump assembly. As is indicated by the label “Y-CONNECT OFF,” the current selection is to treat a single wound. Additional or alternative controls, indicators, messages, icons, and the like can be used.



FIG. 5B illustrates settings screen 500B according to some embodiments. The settings screen 500B can be accessed by selecting menu item 512 (e.g., from screen 500A). As is illustrated, settings screen 500B includes a menu 560 for adjusting various operational parameters of the pump assembly 230, including alarm volume setting, compression setting 562, user mode setting (e.g., clinician or patient), language setting, time zone setting, flow meter 564, restore presets (e.g., factory presets), and device information. Attempting to set the user mode as clinician mode may prompt the user to enter a password or satisfy any other suitable security check. Operating the pump assembly in clinician mode can provide unrestricted access to all features and settings, whereas operating the pump assembly in patient mode can prevent inadvertent changes to therapy settings by preventing access to one or more features and settings, such as therapy settings, compression settings, and the like. Alternative or additional menu items can be displayed. The illustrated menu 560 is an expanded version of the menu showing all menu items. In use, menu 560 may only partially fit on the screen, and the menu items can be accessed via the scroll bar 561 or via any other suitable alternative or additional controls. Additional or alternative controls, indicators, messages, icons, and the like can be used.



FIG. 5C illustrates alarms and troubleshooting screen 500C according to some embodiments. The screen 500C can be accessed by selecting the menu item 516 for accessing help (see FIG. 5B) and selecting alarms menu item from the help screen (not shown). As is illustrated, screen 500C includes a menu 588 with menu items for various alarm and troubleshooting categories, including over vacuum, high vacuum, blockage, canister flow, high flow/leak, and low or insufficient vacuum (as explained below) as well as technical failure (e.g., unrecoverable error), battery (e.g., low battery, critical low battery, battery failed), and inactivity (e.g., pump assembly is powered on an has been left without user interaction for longer than a certain period of time, such as 15 minutes). Alternative or additional menu items can be displayed. Accessing a particular menu item can bring up a screen with step-by-step instructions to assist in resolving the corresponding alarm. The instructions can include a combination of text, audio, video, etc. The illustrated menu 588 is an expanded version of the menu showing all menu items. In use, menu 588 may only partially fit on the screen, and menu items can be accessed via the scroll bar 587 or via any other suitable alternative or additional controls. Additional or alternative controls, indicators, messages, icons, and the like can be used.


Pump Assembly Registration and Usage Validation


FIG. 6 illustrates a process 600 for validating the registration and usage of a pump assembly, such as the pump assembly 150, with a remote server according to some embodiments. The process 600 can be executed, for example, by the remote computer 440. Advantageously, the process 600 can, in certain embodiments, enable the remote computer 440 to determine or track unauthorized registration and uses of a pump assembly and take appropriate actions (e.g., automatically generating a notification message or adjusting operation of the pump assembly). Although the process 600 is described as being performed for one pump assembly for convenience, the process 600 can be performed for tens, hundreds, thousands, or more pump assemblies.


The process 600 begins at block 602 when a registration request is received for a pump assembly, such as the pump assembly 150, to register the pump assembly to an account. The registration request can be received from a computer, such as the computer 410 or the pump assembly, such as the pump assembly 420, via a communications network, such as the cloud 430. The registration request can indicate to register the pump assembly with an account so that the pump assembly becomes associated with the account in the future. The account can be a user account or entity account in account information managed by the remote computer 440 and through which a patient, caregiver, or another individual or entity can access information gathered by the remote computer 440 related to the registered pump assembly (e.g., activity log(s), alarm log(s), therapy duration information, total therapy time, or lifetime therapy information for the registered pump assembly). One account can be registered with one or more different pump assemblies (e.g., a fleet), and one pump assembly can be registered to one or more different accounts.


At block 604, the process 600 can determine whether the pump assembly is authorized to be registered to the account. In one example, the process 600 can use a data structure (e.g., a look-up table) including account identifiers and device identifiers to determine whether an account identifier for the account and a device identifier for the pump assembly indicate that the pump assembly is authorized to be registered to the account. Other approaches for determining whether the pump assembly is authorized to be registered to the account can be used in other implementations. Pump assembly may not be authorized to be registered when it is determined that the user or entity associated with the account is not permitted to administer or be associated with the pump assembly. In response to determining that the pump assembly is unauthorized to be registered to the account, the process 600 moves to block 606.


At block 606, the process 600 performs an exception action for the pump assembly or account. The exception action can, in one example, include generating and sending a notification communication (e.g., an email, SMS, etc.) to an owner of the account or an administrator of a group (e.g., accounts within a geographic area) that includes the account informing of the exception. The notification communication can inform a receipt about the unauthorized registration attempt and/or provide suggested actions for resolving issues associated with the unauthorized registration (e.g., offering information about what steps may be taken so that the pump assembly may be successfully registered). In another example, the exception action can include preventing registration of the pump assembly to the account and/or enabling the registration to remain in effect for a limited duration (e.g., one week). In yet other examples, the exception action can include one or more of the following: (i) generating and sending a command message to the pump assembly limiting the operation capabilities for the pump assembly (e.g., disabling certain components or features, shortening the useful life, altering modes of operation, or changing data gathering approaches), (ii) generating and sending a command message to the pump assembly causing the pump assembly to provide its location (e.g., GPS location including longitude and latitude coordinates) more frequently to the remote computer 440, (iii) generating and sending a command message to the pump assembly causing the pump assembly to display a notification on the screen that the pump assembly is not properly registered (e.g., the notification may be display periodically or consistently until the pump assembly may be successfully registered), (iv) initiating the installation of revised operating or calibration software on the pump assembly, or (v) generating and sending a command message to the pump assembly causing the power of the pump assembly to cycle off and on. After block 606, the process 600 ends.


On the other hand, in response to determining that the pump assembly is authorized to be registered to the account, the process 600 moves to block 608, and the pump assembly is registered to the account. After registration, the owner of the account may login to the account to access the information gathered by the remote computer 440 related to the pump assembly, such as information communicated (e.g., uploaded) by the pump assembly.


At block 610, the process 600 receives a pump assembly usage notification. The pump assembly usage notification can be a communication (e.g., data upload) indicating that the pump assembly has been turned on or that one or more other operations have been performed by the pump assembly. The pump assembly usage notification can be communicated by the pump assembly or a computer, such as the computer 410, via a communications network, such as the cloud 430. The pump assembly usage notification can include an indication of a location of the pump assembly (e.g., a current location of the pump assembly or a location of the pump assembly when the pump assembly was turned on), as well as how, when, or for what duration the pump assembly is or was used. The indication of the location can include information such as a GPS location of the pump assembly.


At block 612, the process 600 determines whether the pump assembly is in an authorized location. The process 600 can, for instance, compare the indication of the location from the pump assembly usage notification with a permitted zone of usage for the pump assembly, such as a zone defined by terms associated with administration of the pump assembly and stored in a memory (e.g., a memory of the remote computer 440). This can be performed using a data structure (e.g., a look-up table) including device identifiers and location identifiers to determine whether a device identifier for the pump assembly and a location identifier for the location indicate that the pump assembly is or was in an authorized location. Other approaches for determining whether the pump assembly is in an authorized location can be used in other implementations.


In response to determining that the pump assembly is in an unauthorized location, the process 600 moves to block 606 and performs an exception action, such as described herein, for the pump assembly or account. For example, the exception action can include generating and sending a notification communication (e.g., an email, SMS, etc.) to an owner of an account or an administrator of a group (e.g., accounts within a geographic area) to which the pump assembly is registered or associated. The notification communication can inform a receipt about the unauthorized location for the pump assembly and/or provide suggested actions for resolving issues associated with the unauthorized location (e.g., offering information about where the pump assembly is authorized to be used or what steps may be taken so that the location in which the pump assembly may be used can be adjusted or expanded to cover the unauthorized location).


On the other hand, in response to determining that the pump assembly is in an authorized location, the process 600 moves to block 614. At block 614, the process 600 determines whether a usage of the pump assembly is authorized. The process 600, for instance, can compare the indication of how, when, or for what duration the pump assembly is or was used with an authorized usage for the pump assembly, such as a usage defined by the terms associated with usage of the pump assembly and stored in a memory (e.g., a memory of the remote computer 440). This can be performed using a data structure (e.g., a look-up table) including device identifiers and operation identifiers to determine whether a device identifier for the pump assembly and an operation identifier for an operation performed by the pump assembly indicate that the pump assembly is or was used in a permitted manner. Other approaches for determining whether the usage of the pump assembly is authorized can be utilized in other implementations.


In response to determining that the usage of the pump assembly is unauthorized, the process 600 moves to block 606 and performs an exception action, such as described herein, for the pump assembly or account. For example, the exception action can include generating and sending a notification communication (e.g., an email, SMS, etc.) to an owner of an account or an administrator of a group (e.g., accounts within a geographic area) to which the pump assembly is registered or associated. The notification communication can inform a receipt about the unauthorized usage for the pump assembly and/or provide suggested actions for resolving issues associated with the unauthorized usage (e.g., offering information about how the pump assembly may be properly used or what steps may be taken so that the pump assembly usage abilities for the pump assembly may be adjusted or expanded to cover the unauthorized usage). On the other hand, in response to determining that the usage of the pump assembly is authorized, the process 600 moves to block 616.


At block 616, the process 600 stores an indication of the authorized usage of the assembly to the account to which the pump assembly is registered. The process 600 can, for example, store to a memory (e.g., a memory of the remote computer 440) the indication of a duration of the authorized usage of the pump assembly in association with the account so that the duration of the authorized usage is later available for access via the account.


In some embodiments, the process 600 can be used or modified to track arrival of one or more pump assemblies at one or more particular locations, such as one or more hospitals, care facilities, and the like. For example, at block 610, the indication of the location for a pump assembly can be received and, based at least on the indication of the location, arrival of the pump assembly can be tracked. In various embodiments, the process 600 can be used or modified to track misplaced or lost pump assemblies. For example, the indication of the location for a pump assembly received at block 610 can be used to determine the location of a misplaced pump assembly.


Other Variations

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. Hardware components, such as processors, ASICs, FPGAs, and the like, can include logic circuitry. 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.


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 method for processing registration and usage information for a plurality of negative pressure wound therapy devices, the method comprising: storing, in a memory device, account information for a plurality of negative pressure wound therapy devices; andby a computer system comprising computer hardware: receiving a registration request to register a negative pressure wound therapy device of the plurality of negative pressure wound therapy devices to an account in the account information, the account associated with a user;determining, based at least on the registration request, that the negative pressure wound therapy device is authorized to be registered to the account;in response to determining that the negative pressure wound therapy device is authorized to be registered to the account, registering the negative pressure wound therapy device to the account so that data gathered by the computer system about operations of the negative pressure wound therapy device is accessible via the account;receiving a first usage notification for the negative pressure wound therapy device, the first usage notification indicating a first location of the negative pressure wound therapy device and a first operation performed by the negative pressure wound therapy device;determining, based at least on a comparison of the first location to a first location identifier corresponding to an authorized location and a comparison of the first operation performed by the negative pressure wound therapy device to a first operation identifier corresponding to an authorized operation, that the negative pressure wound therapy device is being operated in a different location from the authorized location or that the first operation performed by the negative pressure wound therapy device is not the authorized operation;in response to determining that the negative pressure wound therapy device is being operated in the different location from the authorized location or that the first operation performed by the negative pressure wound therapy device is not the authorized operation, performing an exception action;receiving a second usage notification for the negative pressure wound therapy device, the second usage notification indicating a second location of the negative pressure wound therapy device and a second operation performed by the negative pressure wound therapy device;determining, based at least on a comparison of the second location to the first location identifier corresponding to the authorized location and a comparison of the second operation performed by the negative pressure wound therapy device to the first operation identifier corresponding to the authorized operation, that the negative pressure wound therapy device is being operated in the authorized location and that the second operation performed by the negative pressure wound therapy device is the authorized operation; andin response to determining that being operated in the authorized location and that the second operation performed by the negative pressure wound therapy device is the authorized operation, storing in the memory device an indication of performance of the second operation by the negative pressure wound therapy device to the account.
  • 2. The method of claim 1, wherein the registration request is received by the computer system from a user system via a computer network, and the registration request comprises a first account identifier corresponding to the account and a first device identifier corresponding to the negative pressure wound therapy device.
  • 3. The method of claim 2, wherein said determining that the negative pressure wound therapy device is authorized to be registered to the account comprises using a look-up table comprising account identifiers and device identifiers to determine that the negative pressure wound therapy device is authorized to be registered to the account, the account identifiers comprising the first account identifier and the device identifiers comprising the first device identifier.
  • 4. The method of claim 1, wherein the first usage notification and the second usage notification are received from the negative pressure wound therapy device via a computer network, and the first usage notification provides the first location as a first Global Positioning System (GPS) location and the second usage notification provides the second location as a second GPS location.
  • 5. The method of claim 1, wherein said determining that the negative pressure wound therapy device is being operated in the authorized location and that the second operation performed by the negative pressure wound therapy device is the authorized operation comprises using a look-up table comprising device identifiers and location identifiers to determine that the negative pressure wound therapy device is being operated in the authorized location, the device identifiers comprising a first device identifier corresponding to the negative pressure wound therapy device and the location identifiers comprising the first location identifier.
  • 6. The method of claim 1, wherein said determining that the negative pressure wound therapy device is being operated in the authorized location and that the second operation performed by the negative pressure wound therapy device is the authorized operation comprises using a look-up table comprising device identifiers and operation identifiers to determine that the second operation performed by the negative pressure wound therapy device is the authorized operation, the device identifiers comprising a first device identifier corresponding to the negative pressure wound therapy device and the operation identifiers comprising the first operation identifier.
  • 7. The method of claim 1, wherein said performing the exception action comprises generating and transmitting a notification communication to an owner of the account or an administrator of a group that includes the account, the notification communication indicating that the negative pressure wound therapy device is operated outside of the authorized location.
  • 8. The method of claim 1, wherein said performing the exception action comprises generating and transmitting a notification communication to an owner of the account or an administrator of a group that includes the account, the notification communication indicating that the negative pressure wound therapy device performed an unauthorized operation.
  • 9. The method of claim 1, wherein said performing the exception action comprises generating and transmitting a command message to the negative pressure wound therapy device, the command message instructing the negative pressure wound therapy device not to perform one or more operations.
  • 10. The method of claim 1, wherein said performing the exception action comprises generating and transmitting a command message to the negative pressure wound therapy device, the command message instructing the negative pressure wound therapy device to disable one or more features.
  • 11. The method of claim 1, wherein said performing the exception action comprises generating and transmitting a command message to the negative pressure wound therapy device, the command message instructing the negative pressure wound therapy device to increase a frequency of transmitting a location of the negative pressure wound therapy device.
  • 12. The method of claim 1, wherein said performing the exception action comprises generating and transmitting a command message to the negative pressure wound therapy device, the command message instructing the negative pressure wound therapy device to update software of the negative pressure wound therapy device.
  • 13. The method of claim 1, wherein said performing the exception action comprises generating and transmitting a command message to the negative pressure wound therapy device, the command message instructing the negative pressure wound therapy device to cycle power of the negative pressure wound therapy device.
  • 14. The method of claim 1, wherein said performing the exception action comprises generating and transmitting a notification communication to an owner of the account or an administrator of a group that includes the account, the notification communication indicating that the negative pressure wound therapy device was attempted to be registered to the account and that the negative pressure wound therapy device is unauthorized to be registered to the account.
  • 15. The method of claim 1, wherein performing the exception action comprises: performing a first exception action in response to determining that the negative pressure wound therapy device is being operated in the different location from the authorized location and performing a second exception action in response to determining that the first operation performed by the negative pressure wound therapy device is not the authorized operation.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a divisional application of U.S. application Ser. No. 15/766,213, filed Apr. 5, 2018, which is a U.S. national stage application of International Patent Application No. PCT/US2015/057211, filed Oct. 23, 2015, which claims priority to U.S. Provisional Application No. 62/238,501, filed Oct. 7, 2015, titled “SYSTEMS AND METHODS FOR APPLYING REDUCED PRESSURE THERAPY,” the entirety of which is hereby incorporated by reference.

US Referenced Citations (629)
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
5622429 Heinze Apr 1997 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
6747556 Medema et al. Jun 2004 B2
6779024 DeLAHUERGA Aug 2004 B2
6782285 Birkenbach et al. Aug 2004 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
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
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
7670323 Hunt et al. Mar 2010 B2
7671733 McNeal et al. Mar 2010 B2
7684999 Brown Mar 2010 B2
7723560 Lockwood et al. May 2010 B2
7734764 Weiner et al. Jun 2010 B2
7749164 Davis 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
7846141 Weston Dec 2010 B2
7862339 Mulligan Jan 2011 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
8054950 Hung et al. Nov 2011 B1
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
8323263 Wood et al. Dec 2012 B2
8332233 Ott et al. Dec 2012 B2
8334768 Eaton et al. Dec 2012 B2
8337482 Wood et al. Dec 2012 B2
8360975 Schwieterman et al. Jan 2013 B1
8400295 Khaira Mar 2013 B1
8409160 Locke et al. Apr 2013 B2
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
8535296 Blott et al. Sep 2013 B2
8540688 Eckstein et al. Sep 2013 B2
8545483 Schwabe et al. Oct 2013 B2
8554195 Rao 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
8626342 Williams et al. Jan 2014 B2
8626526 Lemke 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
8668677 Eckstein et al. Mar 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 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
8781847 Simms et al. Jul 2014 B2
8791316 Greener 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
8943168 Wiesner et al. Jan 2015 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 Jun 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
9135398 Kaib et al. Sep 2015 B2
9141270 Stuart et al. Sep 2015 B1
9159148 Boyer et al. Oct 2015 B2
9215516 Carnes et al. Dec 2015 B2
9215581 Julian et al. Dec 2015 B2
9220822 Hartwell 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
9424020 Borges et al. Aug 2016 B2
9427159 Chang Aug 2016 B2
9436645 Al-Ali et al. Sep 2016 B2
9436800 Forrester Sep 2016 B2
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
9602952 Kang et al. Mar 2017 B2
9628460 Leong et al. Apr 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
9716757 Fernandes Jul 2017 B2
9740825 Sansale et al. Aug 2017 B2
9741084 Holmes et al. Aug 2017 B2
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
9864066 Park et al. Jan 2018 B2
9871866 Borges et al. Jan 2018 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
10127357 Whiting et al. Nov 2018 B2
10173008 Simpson et al. Jan 2019 B2
10185834 Adam et al. Jan 2019 B2
10207031 Toth Feb 2019 B2
10328188 Deutsch Jun 2019 B2
10537657 Phillips et al. Jan 2020 B2
11147459 Sobol Oct 2021 B2
11315681 Armstrong Apr 2022 B2
11426506 Moore Aug 2022 B2
20010013822 Nazarian et al. Aug 2001 A1
20010031944 Peterson et al. Oct 2001 A1
20020013516 Freyre et al. Jan 2002 A1
20020013545 Soltanpour et al. Jan 2002 A1
20020049562 Hahn Apr 2002 A1
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
20020193679 Malave et al. Dec 2002 A1
20030009244 Engleson et al. Jan 2003 A1
20030018736 Christ et al. Jan 2003 A1
20030105389 Noonan et al. Jun 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
20040006492 Watanabe Jan 2004 A1
20040019464 Martucci et al. Jan 2004 A1
20040039255 Simonsen et al. Feb 2004 A1
20040054775 Poliac et al. Mar 2004 A1
20040064132 Boehringer et al. Apr 2004 A1
20040068224 Couvillon, Jr. et al. Apr 2004 A1
20040078223 Sacco et al. Apr 2004 A1
20040143458 Pulkkinen et al. Jul 2004 A1
20040167802 Takada et al. Aug 2004 A1
20040167804 Simpson et al. Aug 2004 A1
20040171982 Danchin Sep 2004 A1
20040172301 Mihai et al. Sep 2004 A1
20040181314 Zaleski Sep 2004 A1
20040181433 Blair 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
20050065471 Kuntz 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
20050256447 Richardson et al. Nov 2005 A1
20050261805 Mori et al. Nov 2005 A1
20050283382 Donoghue et al. Dec 2005 A1
20060004604 White Jan 2006 A1
20060064323 Alleckson et al. Mar 2006 A1
20060064491 Ebert 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
20060229557 Fathallah et al. Oct 2006 A1
20060246922 Gasbarro et al. Nov 2006 A1
20060255935 Scalisi 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
20070219480 Kamen et al. Sep 2007 A1
20070219826 Brodsky et al. Sep 2007 A1
20070255116 Mehta et al. Nov 2007 A1
20070271298 Juang et al. Nov 2007 A1
20080005000 Radl et al. Jan 2008 A1
20080009681 Al Hussiny Jan 2008 A1
20080041401 Casola et al. Feb 2008 A1
20080071209 Moubayed et al. Mar 2008 A1
20080071234 Kelch et al. Mar 2008 A1
20080086357 Choubey et al. Apr 2008 A1
20080091175 Frikart 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
20080241396 Dresser Oct 2008 A1
20080242945 Gugliotti et al. Oct 2008 A1
20080312953 Claus Dec 2008 A1
20090037216 Bluemler et al. Feb 2009 A1
20090037220 Chambers et al. Feb 2009 A1
20090043268 Eddy et al. Feb 2009 A1
20090048492 Rantala et al. Feb 2009 A1
20090048865 Breazeale, Jr. Feb 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
20090182594 Choubey 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
20090206017 Rohde et al. Aug 2009 A1
20090224889 Aggarwal et al. Sep 2009 A1
20090254362 Choubey et al. Oct 2009 A1
20090270833 DeBelser et al. Oct 2009 A1
20090281464 Cioanta et al. Nov 2009 A1
20090281822 Warner et al. Nov 2009 A1
20090281830 Mcnames et al. Nov 2009 A1
20090281867 Sievenpiper et al. Nov 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 Feb 2010 A1
20100056875 Schoenberg et al. Mar 2010 A1
20100090004 Sands et al. Apr 2010 A1
20100106528 Brackett et al. Apr 2010 A1
20100113908 Vargas et al. May 2010 A1
20100114026 Karratt et al. May 2010 A1
20100145161 Niyato et al. Jun 2010 A1
20100222645 Nadler et al. Sep 2010 A1
20100234708 Buck et al. Sep 2010 A1
20100255876 Jordan et al. Oct 2010 A1
20110003610 Key et al. Jan 2011 A1
20110004188 Shekalim Jan 2011 A1
20110009824 Yodfat et al. Jan 2011 A1
20110028881 Basaglia Feb 2011 A1
20110028882 Basaglia Feb 2011 A1
20110034861 Schaefer Feb 2011 A1
20110040288 Eckstein et al. Feb 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
20110112857 Yurko et al. May 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
20120157889 Tanis et al. Jun 2012 A1
20120181405 Zlatic et al. Jul 2012 A1
20120182143 Gaines et al. Jul 2012 A1
20120191475 Pandey Jul 2012 A1
20120197196 Halbert et al. Aug 2012 A1
20120212455 Kloeffel Aug 2012 A1
20120215455 Patil et al. Aug 2012 A1
20120226768 Gaines et al. Sep 2012 A1
20120259651 Mallon et al. Oct 2012 A1
20120271256 Locke et al. Oct 2012 A1
20120290217 Shoval et al. Nov 2012 A1
20120293322 Ray et al. Nov 2012 A1
20120295566 Collins et al. Nov 2012 A1
20120302978 Buan Nov 2012 A1
20120310205 Lee et al. Dec 2012 A1
20130018355 Brand et al. Jan 2013 A1
20130023719 Bennett Jan 2013 A1
20130035615 Hsieh Feb 2013 A1
20130045764 Vik et al. Feb 2013 A1
20130062265 Balschat et al. Mar 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
20130133036 Wang et al. May 2013 A1
20130150686 Fronterhouse et al. Jun 2013 A1
20130150698 Hsu 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
20130165821 Freedman et al. 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
20130291060 Moore 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 Jan 2014 A1
20140028464 Garibaldi Jan 2014 A1
20140031884 Elghazzawi Jan 2014 A1
20140032231 Semen et al. Jan 2014 A1
20140055588 Bangera et al. Feb 2014 A1
20140058344 Toth 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
20140136218 Bolene 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
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
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
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
20150095068 Ryan et al. Apr 2015 A1
20150100340 Folsom et al. Apr 2015 A1
20150112707 Manice et al. Apr 2015 A1
20150112725 Ryan Apr 2015 A1
20150118662 Ellison et al. Apr 2015 A1
20150119652 Hyde et al. Apr 2015 A1
20150120318 Toyama Apr 2015 A1
20150120328 Ryan et al. Apr 2015 A1
20150133829 DeBusk May 2015 A1
20150143300 Zhang et al. May 2015 A1
20150159066 Hartwell et al. Jun 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
20150227712 Ryan et al. Aug 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
20160004820 Moore Jan 2016 A1
20160004824 Stanton et al. Jan 2016 A1
20160018963 Robbins et al. Jan 2016 A1
20160042154 Goldberg et al. Feb 2016 A1
20160044141 Pfützenreuter 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
20160110985 Lee et al. Apr 2016 A1
20160128571 Adler May 2016 A1
20160129186 Douglas et al. May 2016 A1
20160135752 Beaumont May 2016 A1
20160136339 Begin 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
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
20170004106 Joshua et al. Jan 2017 A1
20170004271 Ash et al. Jan 2017 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
20170150939 Shah Jun 2017 A1
20170173262 Veltz Jun 2017 A1
20170212995 Ingmanson Jul 2017 A1
20170220755 Fowler Aug 2017 A1
20170270533 Barton et al. Sep 2017 A1
20170273116 Elghazzawi Sep 2017 A1
20170327371 Bai et al. Nov 2017 A1
20180004908 Barrus et al. Jan 2018 A1
20180052454 Magno et al. Feb 2018 A1
20180089387 Swank Mar 2018 A1
20180092774 Mehta Apr 2018 A1
20180096292 DeBusk Apr 2018 A1
20180139572 Hansen May 2018 A1
20180144817 Lofgren et al. May 2018 A1
20180158545 Blomquist Jun 2018 A1
20180160907 Verma 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
20180247713 Rothman Aug 2018 A1
20180308578 Armstrong Oct 2018 A1
20180375849 Koskimies Dec 2018 A1
20190057189 Frederickson Feb 2019 A1
20190083353 Khurana Mar 2019 A1
20190147721 Avitan May 2019 A1
20190209022 Sobol Jul 2019 A1
20190213352 Rios Jul 2019 A1
20190328943 Deutsch Oct 2019 A1
20200078499 Gadde Mar 2020 A1
20200222599 Gregory Jul 2020 A1
20200306422 Moore Oct 2020 A1
20210174448 Kotarinos Jun 2021 A1
20210196869 Hartwell Jul 2021 A1
20210379272 Hartwell Dec 2021 A1
20210401358 Quintanar Dec 2021 A1
20220189620 Quintanar Jun 2022 A1
20220215946 Armstrong Jul 2022 A1
20220249293 Lin Aug 2022 A1
20220362454 Moore Nov 2022 A1
Foreign Referenced Citations (234)
Number Date Country
2819475 Jun 2012 CA
201921164 Aug 2011 CN
102805894 Dec 2012 CN
102961815 Mar 2013 CN
104721892 Jun 2015 CN
102010036405 Jan 2012 DE
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
1684146 Jul 2006 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
2366721 Sep 2011 EP
2384472 Nov 2011 EP
2226002 Jan 2012 EP
1610494 Mar 2012 EP
1248660 Apr 2012 EP
2023800 Apr 2012 EP
2441409 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
2795492 Oct 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
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
2320971 May 2018 EP
2335173 May 2018 EP
3100188 Jun 2018 EP
2440112 Oct 2018 EP
2992500 Dec 2018 EP
2597584 Jan 2019 EP
3219340 Jan 2019 EP
2890456 Feb 2019 EP
2881875 May 2019 EP
2836269 Aug 2019 EP
2866851 Sep 2019 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
WO-9627163 Sep 1996 WO
WO-9744745 Nov 1997 WO
WO-9924927 May 1999 WO
WO-9963886 Dec 1999 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-03094090 Nov 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-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-2008039314 Apr 2008 WO
WO-2008062382 May 2008 WO
WO-2008116295 Oct 2008 WO
WO-2008150633 Dec 2008 WO
WO-2009140669 Nov 2009 WO
WO-2009151645 Dec 2009 WO
WO-2010017484 Feb 2010 WO
WO-2010025166 Mar 2010 WO
WO-2010025467 Mar 2010 WO
WO-2010039481 Apr 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-2012027342 Mar 2012 WO
WO-2012027914 Mar 2012 WO
WO-2012027915 Mar 2012 WO
WO-2012051278 Apr 2012 WO
WO-2012100624 Aug 2012 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-2014100687 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-2014151930 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
Non-Patent Literature Citations (7)
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/US2014/026692, dated Sep. 24, 2015, 16 pages.
International Preliminary Report on Patentability for Application No. PCT/US2015/057211, dated Apr. 19, 2018, 14 pages.
International Search Report and Written Opinion for Application No. PCT/US2014/026692, dated Mar. 2, 2015, 26 pages.
International Search Report and Written Opinion for Application No. PCT/US2015/057211, dated Sep. 8, 2016, 20 pages.
Invitation to Pay Additional Fees and Partial Search Report for Application No. PCT/US2015/057211, dated Jun. 8, 2016, 7 pages.
Invitation to Pay and Partial International Search Report for Application No. PCT/US2014/026692, dated Sep. 26, 2014, 9 pages.
Related Publications (1)
Number Date Country
20220215946 A1 Jul 2022 US
Provisional Applications (1)
Number Date Country
62238501 Oct 2015 US
Divisions (1)
Number Date Country
Parent 15766213 US
Child 17703145 US