Medical device

Description

FIELD

This description relates to a medical device.

BACKGROUND

Medical devices can provide treatment for a variety of health conditions. In some instances, a patient has a degree of control over treatment with a medical device. For example, a patient may be able to initiate treatment with a medical device. The capabilities of a medical device determine to a large degree the way that the patient and others interact with the medical device. In particular, it is important that a medical device be capable of providing effective treatment and a positive patient experience.

SUMMARY

In one aspect, a medical device includes: a treatment module configured to apply a treatment to a patient; one or more processing devices configured to: disallow treatment using the treatment module until treatment authorization occurs; determine that treatment authorization occurs; and in response to determining that treatment authorization occurs, permit treatment to be applied using the treatment module.

Implementations may include one or more of the following features. For example, treatment authorization occurs via payment. Treatment authorization occurs via patient identification. Treatment authorization is linked to geographic location. Treatment authorization occurs via authorization data stored on a removable medium.

In another general aspect, a medical device includes: at least one treatment module configured to apply a treatment to a patient; an interface configured to operatively connect to a removable storage device storing authorization data that identifies a level of treatment authorization; and at least one processing device configured to perform the following in response to receiving user input indicating a treatment should be initiated: determine whether the removable storage device is valid for use with the medical device; if the removable storage device is determined to be valid, access the authorization data; determine whether the treatment is authorized based on the accessed authorization data; if the treatment is determined to be authorized, control the treatment module to apply the treatment; and if the treatment is determined to not be authorized, control the treatment module such that the treatment is not applied.

Implementations of any of the aspects may include one or more of the following features. For example, to determine whether the removable storage device is valid for use with the medical device, the at least one processing device is configured to: access a serial number of the removable medium; and determine that the removable medium is valid if the serial number is within a predetermined range of values. The at least one processing device is configured to record compliance data for the treatment on the removable storage device if the treatment is applied. The compliance data indicates a time, date, and duration of the treatment. The treatment module includes at least one ultrasound transducer and at least one driver circuit coupled to the ultrasound transducer. To control the treatment module to apply the treatment, the processing device is configured to control the driver circuit such that the driver circuit causes the ultrasound transducer to produce ultrasound with therapeutic properties. To control the treatment module such that the treatment is not applied, the processing device is configured to control the driver circuit such that ultrasound with therapeutic properties is not produced. The driver circuitry includes a signal generator and an ultrasound transducer driver.

The authorization data indicates a number of authorized treatments, and the at least one processing device is configured to decrease the number of authorized treatments indicated by the authorization data after a treatment is applied. The authorization data indicates an authorized amount of treatment time, and the at least one processing device is configured to decrease the amount of authorized treatment time indicated by the authorization data after a treatment is applied. The medical device includes a communication module. The at least one processing device is configured to: receive authorization data that indicates a level of treatment authorization through the communication module; store the received authorization data on the removable storage device or a second storage device of the medical device; and in response to receiving the user input indicating a treatment should be initiated, determine whether the treatment is authorized based on the received authorization data. The communication module is a wireless communication module. The wireless communication module is a cellular communication module.

The authorization data is received from a server system configured to: determine that payment has been made for a number of treatments; determine that the payment is associated with the medical device; generate the authorization data; and transmit the authorization data to the medical device. The processing device is further configured to provide, if the treatment is determined to not be authorized, an indication to the patient that more treatments need to be purchased. The processing device is configured to receive new authorization data after providing the indication to the patient that more treatments need to be purchased, the new authorization data identifying a number of additional treatments for which payment has been received. The authorization data is encrypted, and the processing device is further configured to decrypt the authorization data. The medical device includes a second storage device. The second storage device stores a device identifier that uniquely identifies the medical device, the authorization data is encrypted, the at least one processing device is further configured to decrypt the authorization data; and the device identifier is used to decrypt the authorization data. The medical device includes a payment module configured to receive payment for a number of treatments. The payment module is configured to receive payment through a code, a credit card, or a SIM card. The at least one processing device is configured to: record on the removable storage device or an internal storage device information indicating occurrences of treatment applied by the medical device; and indicate, on a display of the medical device, days during which treatment was applied and days during which treatment was not applied. The medical device stores information about a treatment regimen for use of the medical device; and the at least one processing device is configured to indicate compliance with the treatment regimen by displaying a calendar that indicates the days during which treatment was applied and the days during which treatment was not applied.

In another general aspect, a medical device includes: a treatment module configured to apply a treatment to a patient, the treatment module including at least one ultrasound transducer and at least one driver circuit coupled to the ultrasound transducer, a display, one or more data storage devices, and one or more processing devices. The one or more processing devices are configured to: receive user input that a treatment should be initiated using the treatment module; in response to receiving the user input, apply a treatment using the treatment module; record on the one or more data storage devices information indicating occurrences of treatment using the treatment module; and indicate on the display days during which treatment was applied and days during which treatment was not applied.

Implementations of any of the aspects may include one or more of the following features. For example, the days during which treatment was applied and days during which treatment was not applied are indicated on a calendar. Days of the calendar during which one or more treatments are applied are marked with a check mark and days of the calendar during which one or more treatments were not applied are unchecked. The one or more storage devices store information about a treatment regimen for use of the medical device, and the one or more processing devices are configured to indicate compliance with the treatment regimen on the calendar. The one or more processing devices being configured to indicate on the display days during which treatment was applied and days in which treatment was not applied includes the one or more processing devices being configured to automatically indicate on the display, in response to the medical device being powered on, days during which treatment was applied and days during which treatment was not applied.

The medical device includes means for determining the geographic location of the medical device, and treatment is not allowed to commence if the determined geographic location is outside an authorized geographic location. The medical device includes means for determining user identity, and treatment is not allowed to commence if the determined user identity does not match an authorized identity. The treatment module is configured to produce a pulsed ultrasound signal having a frequency in the range of 1 MHz to 2 MHz, consisting of pulses generated at a rate in the range of 100 Hz to 10 KHz with each pulse having a duration in the range of 10 microseconds to 2,000 microseconds. The pulsed ultrasound signal has a power intensity of 100 milliwatts per square centimeter or less. The medical device is a hand-held device configured to accelerate bone healing.

In another general aspect a computer-implemented method includes: receiving user input through a user interface of a medical device, the user input indicating a treatment should be administered by the medical device, and the medical device includes a treatment module configured to apply a treatment to a patient; determining whether a removable storage device coupled to the medical device is valid for use with the medical device; in response to determining that the removable storage device is valid for use with the medical device, accessing authorization data stored on the removable storage device; determining that the treatment is authorized based on the accessed authorization data; and controlling the treatment module to apply the treatment in response to determining that the treatment is authorized based on the accessed authorization data.

Implementations of any of the aspects may include one or more of the following features. For example, determining whether the removable storage device coupled to the medical device is valid for use with the medical device includes accessing a serial number of the removable medium and determining that the removable medium is valid if the serial number is within a predetermined range of values. Recording compliance data for the treatment on the removable storage device if the treatment is applied. The treatment module includes at least one ultrasound transducer and at least one driver circuit. Controlling the treatment module to apply the treatment includes controlling the driver circuit such that the driver circuit causes an ultrasound transducer to produce ultrasound with therapeutic properties. Controlling the treatment module such that the treatment is not applied includes controlling the driver circuit such that ultrasound with therapeutic properties is not produced. Receiving the authorization data, and storing the received authorization data on the removable device.

Receiving the authorization data includes receiving the authorization data with a wireless communication module. The wireless communication module is a cellular communication module. The authorization data indicates a number of authorized treatments, and the computer-implemented method further includes decreasing the number of authorized treatments indicated by the authorization data after a treatment is applied. The authorization data indicates an authorized amount of treatment time, and the computer-implemented method further includes decreasing the amount of authorized treatment time indicated by the authorization data after a treatment is applied. Storing a device identifier that uniquely identifies a medical device. The authorization data is encrypted, accessing the authorization code includes decrypting the authorization data, and the device identifier is used to decrypt the authorization data. Recording on the removable storage device or an internal storage device information indicating occurrences of treatment applied by the medical device. Indicating, on a display of the medical device, days during which treatment was applied and days during which treatment was not applied. Indicating compliance with a treatment regimen by displaying a calendar that indicates the days during which treatment was applied and the days during which treatment was not applied. Receiving payment for a number of treatments. Receiving payment for a number of treatments includes receiving payment at the medical device for a number of treatments, the payment being entered with a code, a credit card, or a SIM card.

In another general aspect, a computer-implemented method includes: receiving user input that a treatment should be initiated using a treatment module of a medical device; in response to receiving the user input, controlling the treatment module to apply a treatment; recording on one or more data storage devices information indicating occurrences of treatment using the treatment module; and indicating, on a display of the medical device, days during which treatment was applied and days during which treatment was not applied.

Implementations of any of the aspects may include one or more of the following features. For example, indicating days during which treatment was applied and days during which treatment was not applied includes indicating the days during which treatment was applied and the days during which treatment was not applied on a calendar. Indicating the days during which treatment was applied and the days during which treatment was not applied on a calendar includes marking days of the calendar during which treatment was applied with a check mark and displaying days of the calendar during which one or more treatments were not applied as unchecked. Storing information about a treatment regimen for use of the medical device, and indicating compliance with the treatment regimen on the calendar. Indicating the days during which treatment was applied and the days during which treatment was not applied occurs in response to the medical device being powered on. Determining the geographic location of the medical device, and disallowing commencement of treatment using the treatment module if the determined geographic location is outside an authorized geographic location. Determining user identity, and disallowing commencement of treatment using the treatment module if the determined user identity does not match an authorized identity. Controlling the treatment module to apply a treatment includes controlling the treatment module to produce a pulsed ultrasound signal having a frequency in the range of 1 MHz to 2 MHz, consisting of pulses generated at a rate in the range of 100 Hz to 10 KHz with each pulse having a duration in the range of 10 microseconds to 2,000 microseconds. The pulsed ultrasound signal has a power intensity of 100 milliwatts per square centimeter or less.

According to another general aspect, a computer-readable storage medium storing instructions that, when executed by one or more processing devices, cause the one or more processing devices to perform the operations of the computer-implemented methods.

According to another general aspect, a medical device includes: at least one treatment module configured to apply a treatment to a patient, the treatment module including at least one ultrasound transducer and at least one driver circuit coupled to the ultrasound transducer; an interface configured to operatively connect to a removable storage device storing authorization data that identifies a level of treatment authorization; and at least one processing device. The at least one processing device is configured to perform the following in response to receiving user input indicating a treatment should be initiated: determine whether the removable storage device is valid for use with the medical device; if the removable storage device is determined to be valid, access the authorization data; determine whether the treatment is authorized based on the accessed authorization data; if the treatment is determined to be authorized, control the treatment module to apply the treatment by producing ultrasound with therapeutic properties; and if the treatment is determined to not be authorized, control the treatment module such that the treatment is not applied.

The details of one or more implementations are set forth in the accompanying drawings and the description below. Other features and advantages will become apparent from the description, the drawings, and the claims.

DESCRIPTION OF DRAWINGS

FIG. 1 is a perspective view of a medical device.

FIG. 2 is a block diagram of the medical device.

FIG. 3 is a diagram of the medical device configured to display information.

FIG. 4 is a chart illustrating examples of information that may be displayed.

FIG. 5 is a flow diagram illustrating a process for displaying information.

FIGS. 6A to 6C are diagrams illustrating user interfaces for the medical device.

FIG. 7 is a diagram illustrating a medium for authorizing treatment using the medical device.

FIG. 8 is a diagram of a system for authorizing medical treatments.

FIGS. 9A and 9B are flow diagrams of a process for authorizing medical treatments.

FIG. 10 is a diagram of a process for storing patient information.

FIG. 11 is a diagram of the medical device.

FIG. 12 is a diagram of a main operating unit of the medical device.

FIG. 13 shows authorized geographic areas.

FIG. 14 is a block diagram of geo-locking components of the medical device.

FIG. 15 is a block diagram of device authorization components of the medical device.

FIG. 16 is a flowchart depicted use of the medical device.

DETAILED DESCRIPTION

In some implementations, a medical device can control its operation to apply treatments that have been purchased and to not apply treatments that have not been purchased. For instance, the medical device can be authorized to provide a particular number of treatments purchased for a patient. When the purchased treatments are exhausted, the medical device can be authorized to perform additional treatments based on additional payment. For example, a user can purchase a card or other removable medium that authorizes a number of additional, prepaid treatments with the medical device. The medical device can access authorization data stored on the removable medium, determine that treatment is authorized, and perform the appropriate treatment.

In addition, or as an alternative, to the above-mentioned features, the medical device can also store information and provide information to a patient. For example, the medical device may provide instructions for using the medical device or information about a particular health condition. The medical device can select the information to provide based a particular health condition of the patient or other information about the patient.

In addition, or as an alternative, to the above-mentioned features, the medical device can record compliance information that indicates occurrences of treatments using the medical device. Days and/or times that a patient has performed treatments using the medical device can be recorded. The compliance information can also indicate the degree to which a patient has complied with a particular treatment regimen.

In addition, or as an alternative, to the above-mentioned features, the medical device can display information to a patient that indicates the recorded compliance information. The medical device can display a calendar indicating days on which treatment was performed and days on which treatment was not performed. The calendar can also indicate whether or not the treatments that were performed occurred according to the scheduled treatments indicated by a particular treatment regimen for the patient.

In addition, or as an alternative, to the above-mentioned features, the medical device can limit restrict unauthorized use based on an identity of a user or the geographical location of the medical device. The medical device can determine the geographic location of the medical device and not allow treatment to commence if the determined geographic location is outside an authorized geographic region. The medical device can also determine the identify of a user and not allow treatment if the determined identity is not any authorized identity.

Some implementations of the medical device may provide the following advantages. For example, rather than incur a large initial expense by purchasing a medical device with unlimited treatments, in some instances, a patient or third-party payer may pay for only the treatments that are prescribed to the patient. By purchasing treatments as needed, patients and third-party payers may also spread expenses over time. Also, when treatments can be authorized after an initial set of treatments is exhausted, the additional use of the medical device can be easily added. Additional treatments can generally be authorized without service, repair, or reconditioning of the medical device. In some instances, the patient may enter payment directly at the medical device and receive treatment with minimal delay after payment is complete. In addition, by providing only treatments that have been purchased, excessive treatment and misuse of the medical device can be deterred.

Some implementations of the medical device may provide the following additional advantages. Information can be displayed to the patient during treatment, including, for example, information about a health condition of the patient, instructions for using the medical device, and information about the patient's compliance with a treatment regimen. Messages may, for example, encourage, motivate, inform, entertain, and instruct the patient.

Some implementations of the medical device may provide the following additional advantages. Information indicating a patient's usage of a medical device over time and compliance with a treatment regimen can be displayed. The patient's compliance with a treatment regimen can be easily discernable from a calendar display indicating days on which treatment occurred.

Some implementations of the medical device can limit use by unauthorized users. Some implementations of the medical device can also limit use outside an authorized geographical area.

Referring to FIG. 1, a patient is shown using a medical device 10 that includes a treatment module for applying a treatment to the patient. In the example illustrated, the medical device 10 is a portable ultrasonic treatment device. The treatment module may include, for example, one or more ultrasound transducers 16 and at least one driver circuit coupled to the ultrasound transducers 16.

The medical device 10 can include a control unit 12 that controls the operation of the transducers 16. The control unit 12 can include the transducer driver circuit. The medical device 10 can also include cables 18 that can carry power, data, and control signals between the control unit 12 and the transducers 16.

The medical device 10 can include a placement module 14 that couples the transducers at a location of the patient's body where treatment is needed, for example, over a fractured bone or next to damaged connective tissue. The placement module 14 can include a band, sleeve, applicator, or other connector to fasten the one or more transducers to a treatment site. An ultrasound conducting gel 20 can be applied to the skin of the patient to enable the ultrasound to propagate effectively to the patient's tissue.

The medical device 10 can use low intensity, high-frequency acoustic energy (ultrasound) to treat injuries, defects, or pathologies. For instance, the ultrasonic treatment device can be designed to treat injuries, defects, or pathologies of bones or connective tissue, and, in some instances, can increase cellular level activity that leads to healing of ischaemic or grafted tissue. The medical device 10 may be used as an adjunct to surgical repair, in order to speed healing, or in some cases can be used alone to heal tissue injuries without surgery (e.g., for degenerative diseases such as osteoarthritis, tendonosis, and tendonitis). The medical device 10 can be suitable for use in treatment of bone fractures and/or connective tissues associated with joints, such as those in the hand, foot, wrist, ankle, knee, elbow, hip, shoulder, back, and neck.

For example, following surgery, the medical device 10 can be applied non-invasively to the outside of the body (e.g., coupled to the skin with coupling media, such as a gel) in the region of the repaired tissue. The medical device 10 can be operated to transmit ultrasound (for example, in the form of pulses) into the tissue in need of treatment, or at the interface with the uninjured tissues. Exposure to the ultrasound can stimulate a faster, better quality repair of the tissue. At a bone interface, the ultrasound can also stimulate bone repair and bone ingrowth into repair or graft tissue. This can give rise to a faster, stronger repair and improved integration of the interface between, for example, tendon, ligament, and bone. The ultrasonic treatment device may also be used to non-invasively treat pathologies of connective tissues, such as osteoarthritis, ligament and tendon conditions, without the need for a surgical procedure.

Referring to FIG. 2, the control unit 12 of the medical device 10 can include a processing device 50 that executes instructions stored on a storage device 52. The processing device 50 can include one or more processing devices. The storage device 52 can include one or more storage devices, one or more of which may be removable. The control unit 12 can also include a driver circuit 54, a user interface module 60, a payment module 62, a communication module 64, and a power supply 68.

By executing the instructions, the processing device 50 can, for example, determine whether a treatment is authorized. If treatment is authorized, the processing device 50 can control the treatment module (for example, driver circuit 54 and transducers 16) to apply the treatment. Applying the treatment can include controlling the driver circuit 54 to produce ultrasound with therapeutic properties. Controlling the driver circuit 54 to produce ultrasound can include activating the driver circuit 54, for example, supplying power to the driver circuit 54, sending control signals to the driver circuit 54, or causing the driver circuit 54 to produce a particular output. If the treatment is not authorized, the processing device 50 can control the treatment module such that the treatment is not applied. For example, the processing device 50 can control the driver circuit 54 such that ultrasound with therapeutic properties is not produced. Controlling the driver circuit to not apply treatment can include not activating the driver circuit 54, deactivating the driver circuit 54, setting the output of the driver circuit 54 (for example, setting the amplitude to zero), and/or otherwise limiting or preventing treatment. The processing device 50 can also be configured to control other components described below, for example through instructions stored on the storage device 52.

The processing device 50 can determine whether a treatment is authorized by, for example, accessing authorization data. If, for example, accessed authorization data is invalid, is for a different medical device 10, has expired or all treatments associated with the code have been expended, or if no authorization data can be accessed, the processing device 50 can determine that treatment is not authorized. On the other hand, if valid authorization data can be accessed, the processing device 50 determines whether at least one treatment using the medical device 10 is authorized. The authorization data may or may not include an authorization code that indicates that payment for treatments has occurred. The authorization data can be stored in the storage device 52, for example, or, as described further below, in a removable medium.

The storage device 52 can store a device identifier, such as a serial number, that identifies the particular medical device 10. The device identifier can uniquely identify the medical device 10 and distinguish it from all other ultrasonic treatment devices, even those of the same type or model. The storage device 52 can also store information about the treatments that are authorized for the medical device 10, for example, a number of treatments that are authorized or an authorization code that authorizes treatments.

The driver circuit 54 can be configured to send drive signals that cause the transducers 16 to generate ultrasound with therapeutic properties. The driver circuit 54 can include a signal generator 56 that generates a signal and a transducer driver 58 that drives the transducers 16 according to the generated signal. In an implementation, the ultrasound generated by the transducers 16 can include low intensity ultrasound (for example, 100 mW/cm²or less) having a frequency ranging between about 1 and 2 MHz, more particularly about 1.5 MHz. The ultrasound can be pulsed, with a pulse width ranging from about 10 to 2,000 microseconds, more particularly about 200 microseconds, with a repetition frequency ranging from about 100 Hz to about 10 KHz, more particularly about 1 KHz.

The user interface module 60 can provide information to the patient and enable treatment to be initiated. The user interface module 60 may include one or more input devices or controls, for example, buttons, a keypad, or a touch-sensitive screen. The user interface module 60 may be used by a patient or other person, for example, to enter user input that indicates that a treatment should be administered by the medical device. When the processing device 50 determines that treatment is not authorized, the processing device 50 can provide an indication to the patient on the user interface module 60 that more treatments need to be purchased.

The user interface module 60 may also include one or more output devices, for example a screen, a liquid crystal display, or lights. For example, the interface module 60 can include a screen 72, for example, a liquid crystal display (LCD), a thin-film transistor (TFT) display, a field sequential display, or an organic light-emitting diode (OLED) display. The interface module 60 can also include light-emitting diodes (LEDs) and other indicators. The interface module 60 may include a speaker or other device that can produce sound (not shown), or other output devices. The user interface module 60 may also include input capabilities or input devices (not shown), for example, buttons, one or more keypads, and other controls. The screen 72 may be touch-sensitive to receive input from a user. The user interface module 60 can also include an interface to access a removable storage medium, such as a subscriber identity module (SIM) card, a Secure Digital (SD) card, or other types of removable storage media.

The payment module 62 can enable a patient to enter payment at the control unit 12, or to receive information indicating prior payment. Payment can be enabled through one or more methods. The payment module 62 can include a credit card reader that reads a card and charges treatment to a credit card, debit card, or similar card that is swiped at the control unit 12. The payment module can include a SIM card reader, and a patient may purchase a SIM card that includes information that represents one or more payments made for treatment with the ultrasonic treatment device. The payment module can include a reader for reading other types of removable media, for example, a SD card or other flash memory device. The control unit 12 can be configured to receive payment in the form of a code or other user input that may be entered on the interface module 60. Some implementations may exclude the payment module 62. For instance, in some implementations, provisions may be made to allow payment remotely from the device 10, for example, at a computer connected to a network.

In some implementations, the processing device 50 is configured to receive an authorization code or other authorization data through the communication module 64 and to store the received authorization code in the storage device 52. The communication module 64 can enable communication with a server system, client system, or other computer system over a wired or wireless connection. The communication module 64 may enable a communication link that is wired or wireless. The communication module may enable communication over, for example, Ethernet, Universal Serial Bus, 502.11, Bluetooth, Zigbee, cellular networks, and other communication links. In one implementation, the communication module 64 can include a cellular transceiver 66 to receive and/or transmit information over a cellular network. The communication module 64 may also enable communication through multiple communication links.

The communication module 64 can be configured to send payment information to a remote system and/or receive authorization information that authorizes additional treatments using the medical device 10. The processing device 50 can be configured to receive an authorization code through the communication module 64 and to store the received authorization code in the storage device 52.

A power supply 68 can provide power to the components of the medical device 10, including the driver circuit 54, the processing device 50, the storage device 52, the payment module 62, the communication module 64, and the user interface module 60. The power supply 68 can include a battery that is integrated into the control unit 12 or is removable. The battery can be primary battery or a rechargeable battery, and the power supply 68 can include a detachable power adapter that can charge a rechargeable battery.

When a user performs treatment using the medical device 10, the medical device 10 can collect and store compliance information. Collecting compliance information can include recording information about use of the medical device 10, for example recording the number of treatments that are performed. Compliance information can include a number of treatments provided by the medical device 10, a date and time that a treatment was provided by the medical device 10, and/or a duration that a treatment was provided by the medical device 10. Information about multiple uses or treatments with the medical device 10 can be collected.

A treatment regimen that identifies a prescribed use of the medical device 10 can be identified. For example, the treatment regimen may be entered on the device after the health condition has been diagnosed or after the medical device 10 has been prescribed to the patient. Information about a treatment regimen may be entered on the medical device 10 or received from a network, which may include a cellular network. The information about the recorded use of the medical device 10 can be compared to the information about the prescribed use of the medical. Information indicating the degree that the recorded use matches the prescribed use can be generated.

Compliance information can be stored on the storage device 52, on a removable medium, or both the storage device 52 and a separate removable medium. The compliance information may, but is not required to, include one or more results of a comparison between the recorded use of the medical device 10 and the treatment regimen of the patient.

Referring to FIG. 3, the medical device 10 can display information to the patient. For example, the medical device 10 can display information that relates to the particular patient using the medical device 10, for example, information about a health condition of the patient, a treatment regimen of the patient, or a physician of the patient. The information displayed on the medical device 10 can thus be personalized to the particular patient that receives the medical device 10 and a particular health condition of the patient. In some instances, the information displayed may be selected to instruct, encourage, or entertain the patient. In addition, the information can provide advertisements and personalize treatment using the name or brand of, for example a particular physician, hospital, or insurance company.

The information displayed on the medical device 10 may be organized into a plurality of messages 304. Messages 304 can include a variety of media, including text, images, video, and sound. Messages 304 can be stored on the storage device 52 of the control unit 12. Some messages 304 may be entered onto medical device 10 during manufacturing. For example, an initial set of predetermined messages 304 may be loaded onto a storage device 52 before it is shipped. Messages 304 may also be entered at other times to supplement the initially loaded messages 304, including before a medical device 10 is dispensed to a patient and after a patient begins use of the medical device 10. Messages 304 may be received with, for example, the communication module 64 and may be stored on the storage device 52.

Messages 304 can include information related to specific health conditions. For example, some messages 304 may relate to treatment of broken bones of the foot, and others may relate to treatment of broken bones of the arm. The medical device 10 can store messages 304 that relate to a wide variety of health conditions. To ensure that the messages 304 displayed to the patient are useful, the processing device 50 can access information that identifies a health condition of the patient, which can be stored on the storage device 52. Based on the identified health condition, the processing device 50 can select one or more messages out of the set of messages 304 that are stored on the storage device 52. For example, if the processing device 50 determines that the patient has a broken foot, the processing device 50 can select one or more messages 304 related to broken bones of the foot and treatment of a broken foot. The selected messages 304 can be displayed to the patient on the screen 72. In some implementations, the screen 72 may be part of the interface module 60, while in others the 72 screen may be integrated into the control unit 12.

Selected messages 304 can be displayed to the patient during treatment. For example, while a treatment is applied, the medical device 304 can display information to instruct the patient about proper use of the medical device 10. In many instances, a patient receives only minimal instruction about the proper use of the medical device 10 when the medical device 10 is dispensed to the patient. A patient may forget the proper use of medical device and the details of a treatment regimen, especially when the medical device 10 is new. By providing messages 304 that instruct the patient how to use the medical device 10, the patient may be more likely to perform treatment correctly. The instructive messages 304 can be selected based on the health condition of the patient and the associated treatment regimen for the health condition.

The medical device 10 can select and display a variety of other messages 304 during treatment. For example, messages 304 can also provide general health information, such as, “smoking inhibits bone healing” or “tell your doctor if you use blood thinners.”

Messages 304 can also be selected based on a patient's compliance to a treatment regimen. The medical device 10 can store information that indicates when the patient should receive treatment. The medical device 10 can also record information indicating when treatment is actually performed. The medical device 10 can compare the planned or prescribed use of the medical device with the actual use of the device and determine how well the patient has complied with the prescribed treatment regimen. The medical device 10 can display messages 304 to the patient that directly or indirectly provide compliance information. For example, messages can provide direct feedback about a patient's compliance. Messages 304 can also be displayed that motivate, encourage, and remind the patient to follow a consistent treatment schedule. Messages 304 can also describe the benefits of continuing treatment or provide information about how the medical device 10 operates.

Messages 304 can also provide physicians and others an opportunity to provide a personalized message. For example, one or more messages 304 may include the name of a patient's physician, the name of the patient's insurance company, or the logo for a hospital. Customized messages 304 can enable physicians and organizations to reinforce their brands and enhance the patient's experience during treatment. Messages 304 can also include contact information, for example, the phone number for the patient's primary physician. Messages 304 can include advertisements and paid content.

Messages 304 can also be provided to entertain a patient during treatment and thus encourage the patient to complete the treatment. In some implementations, the medical device may enable the patient to acquire or input additional content to display on the medical device.

Referring to FIG. 4, a diagram illustrates the selection and display of messages 304 on a screen 72 of the medical device 10.

The processing device 50 of the medical device 10 can access information identifying a health condition of a patient. As illustrated, a health condition record 401 indicates that the health condition of the patient is a broken clavicle. Based on the identified health condition, the processing device 50 can select one or more messages from a plurality of messages 304. The plurality of messages 304 may include a set 402 of predetermined messages 304. Each message 304 in the set 402 may be associated with an identifier, as represented by the numbers from one to ten. From the set 402, a subset 403 of messages 304 may be selected. The selected messages 304 can include messages 304 that relate to the particular health condition of the patient. The selected messages 304 can be ordered into a sequence 404 for display on the medical device 10.

The sequence 404 of messages 304 may be displayed on the screen 72 of the medical device 10. In one implementation, the sequence 404 of messages 304 may begin to be displayed when treatment begins, and the sequence 404 may end roughly when treatment ends. In addition to the messages 304, other information can be included, for example, information that describes the treatment being performed. For example, notifications 406 that indicate the time remaining until treatment is completed may be interspersed between other messages 304.

The messages 304 selected and the sequence 404 of the selected messages 304 can vary according to the needs of the patient and to limit unnecessary repetition. For example, instructions about how to use the medical device 10 may be selected and displayed for an initial set of treatments using the medical device 10, but instructions may be omitted after many treatments have successfully been performed.

Referring to FIG. 5, an example of a process 500 for providing information is illustrated. The processing device 50 of the medical device 10 can be configured to perform the process 500, for example, by executing instructions stored on the storage device 52.

A plurality of messages is stored on the medical device (502). For example, the storage device may store the plurality of messages. Messages may be entered on the storage device by a manufacturer of the medical device before the medical device is sold. Messages can also be entered on the storage device by sales representatives, physicians, and others at other times.

The medical device receives information about a health condition of a patient (504). For example, after a patient is diagnosed with a particular health condition, the health condition can be entered on the medical device. A physician, assistant, sales representative, or other person may enter information that indicates the health condition of the patient on the medical device. In addition, or alternately, the medical device may receive information about a health condition of the patient through the communication module. For example, the medical device may receive information about a prescription or diagnosis automatically over a network, without requiring any manual input. The medical device can store the information about the patient's health condition for later access. The health condition can be, for example, a health condition that is treatable by the medical device.

The medical device selects messages for the patient (506). For example, the messages can be selected from the stored messages stored on the storage device. One or more messages can be selected based on the identified health condition of the patient. For example, if the patient has a broken ankle, messages can be selected that describe treatment of a broken ankle. The selected messages can include messages related to multiple health conditions. The selected messages can include instructions for using the medical device. The selected messages can include one or more messages that include information about a doctor that treated the patient or a medical office where the patient was treated. The selected messages can include one or more messages about the medical device or information about the provider of the medical device. The selected messages can include advertisements. The selected messages can include image data or video data.

In some implementations, the medical device can store records indicating use of the medical device. For example, the medical device can record the number of treatments that have been performed using the medical device, the date and time that each treatment is performed, and/or the duration of each treatment. The information in these records, referred to generally as compliance information, indicates the manner in which treatments were performed using the device, from which a patient's compliance with a particular treatment regimen can be determined.

Compliance information can be stored on the one or more storage devices 52. For example, the compliance information can be stored on internal memory of the medical device 10 and can also be stored on a removable medium, such as an SD memory card. Recording the compliance information on internal memory and the removable medium provides a backup in case one of the storage devices should fail. Additionally, the removable medium may be removed and used to transfer compliance information to other systems.

The medical device can also identify a treatment regimen that corresponds to the health condition. For example, the medical device may receive the information from a prescription, a treatment regimen that is entered directly on the medical device, or the medical device may store a number of treatment regimens on the storage device. The medical device can access the records indicating use of the device. The medical device can compare the records indicating use of the medical device to the treatment regimen identified for the health condition of the patient.

The medical device can provide an indication of compliance with the treatment regimen. For example, the medical device may provide an indication of compliance in one or more messages that are selected to be later displayed to the patient. The selected messages can also encourage compliance to a treatment regimen, for example, by praising the patient for past compliance or assuring the patient that continued treatment will bring good results. The selection of messages, including the selection of messages about compliance to the treatment regimen, can be based on the number of uses of the medical device indicated in the records that indicate use of the medical device.

The medical device can also identify the language of the patient and select one or more messages in the language of the patient. The plurality of messages stored on the medical device can include messages in at least two languages. For example, some or all of the stored messages can be included in multiple languages. The medical device can identify the language of the user, for example, based on user input, messages input on the medical device, information received by the communication module, or other information.

The medical device can begin treatment (508). For example, a patient may enter input indicating that treatment should begin, and the medical device may control a driver circuit to drive an ultrasound transducer so that the ultrasound transducer produces ultrasound with therapeutic properties. The medical device can store and update records indicating use of the medical device.

The medical device can display the selected messages (510). The selected messages can be displayed during treatment, for example, while the ultrasound with therapeutic properties is applied to the patient. The messages can be displayed on a liquid crystal display or other screen.

Referring to FIG. 6A, the medical device 10 can display information about a patient's compliance with a treatment regimen on a user interface 600a. The user interface 600a can be displayed on the screen 72 of the user interface module 60. The user interface 600a includes a calendar view 602 that indicates whether treatment was performed each day of, for example, the current month, or the current month and previous months. In the calendar space corresponding to each day that treatment was performed, a compliance indicator 604 can be displayed, for example, a colored square, a check mark, or other image or icon. In the space corresponding to each day in which treatment was not performed, a noncompliance indicator 606 can be displayed, for example, a different image or icon, such as a blank square or a red “X.” Thus the user interface 600a can visually distinguish the days during which treatment was performed from days during which treatment was not performed, providing an easily-understandable indication of recent compliance with the treatment regimen.

In some implementations, information about the particular treatment regimen prescribed for the user of the medical device 10 is stored on the medical device 10, and the compliance indicator 604 is displayed to indicate that a treatment performed on a particular day complies with the particular treatment regimen prescribed. In other words, rather than assuming that the treatment regimen requires one treatment each day, the medical device 10 compares times that treatments were performed to times that treatments were scheduled to be performed, as dictated by a treatment regimen. If a treatment regimen involves treatment every other day, for example, a neutral indicator can be displayed to represent days in which treatment was not scheduled and was not performed. The neutral indicator may be, for example, the day of the month that the day occurs. The noncompliance indicator 606 may be displayed, for example, only when treatment was scheduled to be performed on a day and treatment did not occur on that day. If treatment was performed on a day that treatment was not scheduled, an improper treatment indicator different from the noncompliance indicator 606 may be displayed for that day, distinguishing noncompliance by omitted treatment from noncompliance by performance of an unscheduled treatment. As a result, compliance relative to a treatment regimen can be accurately indicated when scheduled treatments are not scheduled every day.

Similarly, compliance can be indicated for treatment regimens that dictate treatment multiple times in a day. For example, multiple compliance indicators 604 or multiple noncompliance indicators 606 can be displayed to indicate each treatment that was completed or missed that day.

In other implementations, the medical device 10 displays the compliance indicator 604 for days that treatment was performed and displays the noncompliance indicator 606 for days that treatments were not performed, without regard to times that treatments were dictated by a prescribed treatment regimen. Thus even when the medical device 10 does not have access to information indicating a treatment regimen, the calendar view 602 indicates when treatments were performed, permitting the user or others to determine compliance with an appropriate treatment regimen.

The user interface 600a may display patient compliance for time period longer or shorter than a month, and for previous periods of time rather than, for example, the most recent weeks or months.

The medical device 10 can automatically display the calendar view 602 as the medical device 10 is powered on or at other times. For example, each time the medical device 10 is powered on, while the medical device 10 is initializing and for a period of time afterward, the calendar view 602 showing compliance can be displayed. The calendar view 602 can also be displayed to physicians, caretakers, and others. The calendar view 602 can be displayed automatically after particular functions of the medical device 10 are accessed, or in response to a request that the calendar view 602 be displayed.

The medical device 10 can automatically display a total compliance to-date indication. For example, if ten days have elapsed since the start of a daily treatment regimen and the patient only used the device for eight out of the ten days, then the total compliance indicator can display 8/10 or 80% to indicate the overall level of compliance.

The user interface 600a can also display notification icons 610. The notification icons 610 can vary in appearance according to the current status of the medical device 10. The notification icons 610 can indicate, for example, the status and availability of communication links such as wireless connections, whether service is needed, that error or notification messages are available, the types or quality of connections with various modules, the remaining battery charge of the medical device, and other notifications.

Referring to FIG. 6B, after the calendar view 602 is displayed, or after receiving user input, the medical device 10 can display a treatment timer 612 on a user interface 600b. The treatment timer 612 can indicate the time remaining before a treatment is completed. For example, for a twenty-minute treatment, the treatment timer 612 can initially indicate the duration of treatment, twenty minutes. While a treatment is in progress, the treatment timer 612 can count down toward zero, reaching zero when the treatment ends. The notification icons 610 can also be displayed.

Referring to FIG. 6C, an alternative user interface 620 includes a calendar view 622 indicating daily compliance with the treatment regimen and a treatment timer 624. Days for which treatment was performed as indicated in the treatment regimen are indicated with a first marking 626, while days for which planned treatment failed to be performed are indicated with a different marking 628. Days in the future can be marked with their corresponding calendar numbers.

Referring to FIG. 7, a removable medium 710, for example, an SD card, USB device, or other removable memory device, can be used to authorize use of the medical device 10. The removable medium 710 can store authorization data 720 that indicates a level of treatment authorization, for example, a number of treatments authorized or an amount of treatment time authorized using the medical device 10.

The medical device 10 can include an interface 712 that operatively connects to the removable medium 710, permitting the processing device 50 to access the authorization data 720. The interface 712 can include a slot that receives the removable medium 710 within the medical device 10. The slot can be accessible to a user, permitting the user to replace the removable medium 710 with a different removable medium. The control unit 12 of the medical device 10 can define the slot and can include a cover that covers the slot.

To obtain treatment authorization, the patient can obtain the removable medium 710, which can be a prepaid medium that represents that payment has been made by or for the user. Removable media can store differing levels of treatment authorization. Different removable media may be sold with authorization data 720 that permits, for example, 50, 25, or 10 treatments. Treatment authorization may additionally or alternatively be indicated as an amount of time, for example, 1000, 500, or 100 minutes of treatment. In some implementations, the removable medium 710 can be purchased from a retail store or a physician's office. The fact that the patient obtained the removable medium 710 indicates that payment was made, and no additional verification of payment may be necessary to use the medical device 10.

The removable medium 710 may be a secure mode of communicating that a particular number of treatments are authorized. The removable medium can include a copy-protection or anti-counterfeiting feature that can be used to determine whether the removable medium is genuine. For example, the removable medium can store an encoded value in a manner that the value is not easily duplicated or copied from one removable medium to another. The encoded value can be hardware-encoded or factory-set with a physical setting such that similar removable media cannot be altered to mimic the encoded value. In some implementations, the encoded value is a serial number that is embedded in non-writable storage of the removable medium. Each valid removable medium can have a unique serial number. Only removable media that have a serial number within a predetermined range of values can be considered genuine.

In use, a user interacts with the medical device 10 to indicate that treatment should be initiated, for example, by pressing a button or entering other input. In response, the processing device 50 determines whether a removable medium is present. If no removable medium is present, the processing device 50 disallows treatment.

If a removable medium such as the removable medium 710 is present, the processing device 50 determines whether the removable medium 710 is valid for use with the medical device 10. For example, the processing device 50 determines whether a serial number or other value encoded in the removable medium meets predetermined criteria. In some implementations, the processing device 50 determines whether the value is within a predetermined set or range of values. The serial number can be a value that is not modifiable by a user, for example, a value that is fixed in the hardware configuration of the removable medium and cannot be copied onto a similar removable medium. Thus the processing device 50 can verify that the physical medium is valid. If a removable medium is not genuine, or is not compatible with or intended for the medical device 10, the processing device 50 disallows treatment.

If the removable medium 710 is genuine, the processing device 50 accesses authentication data 720 stored on the removable medium 710. The authentication data 720 can indicate a number of treatments authorized or a number of treatment minutes that treatment is authorized. For example, when each treatment has a duration of twenty minutes, the authorization data 720 may indicate that ten treatments are authorized, or may indicate that two hundred minutes of treatments are authorized. If the authorization data 720 indicates that at least one treatment is authorized, or that one or more treatment minutes are authorized, the processing device 50 controls the treatment module to provide ultrasound with therapeutic properties. If the authorization data 720 indicates that no treatments are authorized, the processing device 50 disallows treatment.

After the medical device 10 applies a treatment, the processing device 50 alters the authorization data 720 to indicate an updated level of authorization. For example, the medical device 10 can decrease the number of authorized treatments or decrease the number of authorized treatment minutes remaining Modified authorization data that indicates an updated level of authorization can be stored on the removable medium 710, for example, by overwriting the authorization data 720 that was stored before treatment began.

The medical device 10 can also store compliance data 730 on the removable medium 710. When the medical device 10 applies a treatment, the processing device 50 can store information about the treatment performed. For example, the compliance data 730 can indicate the time, date, and duration of the treatment applied, along with other treatment information. The removable medium 710 can thus include a compliance log that indicates use of the medical device 10 over time. The compliance data 730 can also indicate, for example, the degree that the use of the medical device 10 corresponds to planned or prescribed use of the medical device 10. For example, the compliance data 730 can indicate days or times at which treatment was scheduled and whether treatment occurred at those days or times. Compliance data 730 can additionally or alternatively be stored on an internal storage device of the medical device, such as the storage device 52.

In some implementations, the authentication data 720 is encrypted, which can discourage tampering. In such implementations, the processing device 50 decrypts the authentication data 720 before determining whether treatment is authorized. Also, after modifying the authentication data to indicate a decreased level of authorization, the processing device 50 encrypts the modified data and stores the encrypted data on the removable medium 710.

When additional treatments are desired, for example, after the treatment authorization of the authorization data 720 is depleted, a user can obtain a different removable medium that includes authorization data for additional treatments.

In some implementations, the authorization data 720 directly authorizes the treatments, without the medical device 10 needing additional information or confirmation from another system. In some implementations, as described below, the medical device 10 verifies the authenticity of authorization data 720 by communicating with a server system or other device.

Referring to FIG. 8, a system 800 for authorizing medical treatments includes the medical device 10 connected to a server system 802 via a network 806. The system 800 can also include a third-party server system 804 and a cellular network 808. After payment is made by or for a patient, authorization data can be entered at or received by the medical device 10. The authorization data indicates a level of treatment authorization, and can include an authorization code.

A patient may desire to authorize medical treatments using the ultrasonic treatment device 10. For example, the patient may receive the ultrasonic treatment device 10 in a condition in which treatments have not yet been authorized. As another example, the patient may have used treatments authorized for the ultrasonic treatment device 10 so that an insufficient number of treatments are currently authorized to complete treatment.

To purchase additional treatments of the medical device 10, the patient may provide payment information 810 at the medical device 10. Payment information 810 includes payment entered or authorized at the medical device 10 and also information that indicates that payment has been made in another manner. For example, the patient may enter a credit card, a debit card, or another payment device into an appropriate reader of the medical device 10 and authorize a charge to an account owned by the patient. The patient may also enter an account number on the user interface module 60 of the medical device 10 to authorize payment. The patient may also purchase a prepaid medium, for example, a SIM card, a Secure Digital (SD) card, or a prepaid card with a magnetic strip, an optical code, or a printed code, from a store or physician's office. In one implementation, the prepaid medium may be a secure mode of communicating an amount of payment that has been paid. The patient may enter the prepaid medium at the ultrasonic treatment device 10 to indicate that payment has been made. The patient may also purchase treatments in a store or through a web site, may receive a confirmation code for the transaction, and may enter the confirmation code at the ultrasonic treatment device 10. The system 800 can also be used to verify the validity of an authorization code received from a prepaid medium.

The medical device 10 can send the payment information 810 to a server system 802. The payment information 810 can be associated with a device identifier 812 that identifies the medical device 10, which can also be sent to the server system 802. In addition to, or instead of, sending a device identifier 812, the medical device 10 may send a patient identifier that identifies the patient, together with the payment information. As will be described in greater detail below, the server system 802 can send an authorization code to the medical device 10 after receiving the payment information 810 and the device identifier 812.

The medical device 10 may send the payment information 810 and the device identifier 812 to the server system 802 through the network 806. Alternatively, or additionally, the medical device 10 may initiate a communication using the cellular network 808 to send the payment information 810 and the device identifier 812 to the server system 802. Payment information 810 can also be received through a removable medium, token, code or other indication that treatment is authorized.

In one implementation, a prepaid medium can store an authorization code that can directly authorize treatments, so that the ultrasonic treatment device 10 is not required to transmit any information to the server system 802. A prepaid medium can include an authorization code that can enable treatments of the ultrasonic treatment device 10, independent of a server system 802. For example, a patient may purchase a SIM card or other device that stores an authorization code compatible with the ultrasonic treatment device 10. The SIM card containing the authorization code can be entered at the ultrasonic treatment device 10 and the treatments authorized by the authorization code can be enabled on the ultrasonic treatment device 10. Payment is received by the retail store or physician's office where the prepaid medium was obtained. The fact that the patient obtained the prepaid medium proves that payment was made, and no additional verification may be necessary. In some implementations, the ultrasonic treatment device 10 may verify that the authentication code included with the prepaid medium is authentic, and may ensure that the authentication code of the prepaid medium is not used multiple times (for example, by altering the data on the prepaid medium). In another implementation, a mechanical device or key may also be used to indicate authorization of additional treatments of the ultrasonic treatment device 10.

Treatments can also be purchased for a patient by a third-party payer, for example, an insurance company. A third-party server system 804 can transfer payment information 816 to the server system 802 with a patient identifier 818 that identifies the patient. The payment information 816 can include the information that completes the act of payment or indicates that payment has been made. The patient identifier 818 can include a name, prescription number, insurance policy number, or other identifier.

The server system 802 can receive the payment information 810 and the device identifier 812 from the medical device 10, or can receive the payment information 816 and the patient identifier 818 from the third-party server system 804.

The server system 802 can determine that payment has been made for a number of treatments, for example, using the payment information 810, 816. The server system 802 can also determine that patient is associated with the medical device, for example, using the patient identifier 818 or device identifier 812 associated with the payment information 810, 816. The server system 802 can use the received information and stored records to associate the payment with the patient to be treated with the medical device 10. The server system 802 may store records that associate patient identifiers 818 and device identifiers 812 with particular patients and medical devices 10 so that payment can be applied for the correct patient and medical device 10.

The server system 802 can also generate an authorization code 814 that enables the medical device 10 to provide a number of treatments. The number of treatments authorized can be based on the amount of payment received. The server system 802 can send the authorization code 814 to the medical device 10 through the network 806 and/or through the cellular network 808.

The authorization code 814 can be encrypted or encoded so that the authorization code 814 enables treatments only for the particular medical device 10 associated with a particular payment received. In one implementation, the authorization code 814 can be encrypted so that the unique device identifier 812 or another unique decryption key is necessary to decrypt or decode the authorization code 814. For example, the authorization code 814 can be encrypted using a symmetric-key or asymmetric-key encryption scheme.

Using a symmetric-key or shared-key encryption system, a key may be used as both the encryption and decryption key. The key can be stored on both the server system 802 and the medical device 10, for example, by the manufacturer of the medical device 10. To prevent interception, the key may not be transmitted. The medical device 10 can send a patient identifier or a device identifier 812 unrelated to the key to identify the medical device 10. The server system 802 can send the encrypted data to the medical device 10, which can decrypt the data with the stored key.

Using an asymmetric-key cryptography system, for example, a public key private key pair encryption system, the server system 802 can store an encryption key and the medical device 10 can store a corresponding decryption key. The server system 802 may encrypt the authorization code 814 using the encryption key and send the encrypted data to the medical device 10. The medical device 10 can include a stored decryption key that can decrypt the encrypted data. The decryption key can include the device identifier 812 or another key. In an implementation, the encryption key that encrypts messages for a particular medical device 10 may be known only to the server system 802.

Because the server system 802 can store records associating patients, medical devices 10, and corresponding encryption keys, the system 800 may not require that the decryption key be sent to the server system 802. If the device identifier 812 is used to decrypt an authorization code 814, instead of sending the device identifier 812, the medical device 10 can send another identifier, such as a patient identifier or a device identifier unrelated to the encryption scheme. The device identifier 812 can be independent of the encryption scheme so that interception of the device identifier does not compromise the encryption scheme.

The medical device 10 can receive the encrypted authorization code 814 through the network 806 or the cellular network 808 and can decrypt the authorization code 814. The medical device 10 can use the authorization code 814 to authorize a number of treatments of the medical device 10. The authorization code 814 or information determined based on the authorization code 814 can be stored to indicate the number of treatments authorized. When the patient attempts to initiate treatment with the medical device 10, the processing device of the medical device 10 can determine that authorized treatments remain for the medical device 10 and initiate treatment.

The medical device 10 may also use the authorization code 814 to determine a change in treatment. For example, an authorization code 814 may indicate that treatment should be disallowed after a particular period of time has elapsed or if the patient does not apply a treatment for a period of time. The authorization code 814 may indicate that the number of treatments that are available each day should be changed, for example, from one treatment each day to two treatments each day. The authorization code 814 may indicate that the intensity of ultrasound produced by the medical device 10 should be changed, for example, that the intensity should be reduced if the patient is healing well.

Referring to FIG. 9A, a process 900 for authorizing medical treatments can include actions by a medical device, a server system, and/or a third-party system. The medical device can be an ultrasonic treatment device as described above.

As illustrated, the process 900 can include payment for treatment by a patient at the medical device, payment by a third-party at a remote system, or both sources of payment. The actions performed by the medical device can be performed by one or more processing devices of the medical device configured to perform those actions. The server system can include one or more processing devices and one or more storage devices that store instructions that, when executed by the one or more processing devices, cause the processing devices to perform the various functions of the server system described below.

A patient can attempt to initiate treatment with the medical device (902). For example, the medical device can receive user input indicating that a treatment should be administered by the medical device.

The medical device can determine whether treatment is authorized (903). For example, the medical device can determine whether at least one treatment is authorized based on stored information that indicates the number of treatments that are authorized. The medical device can access an authorization code that has been received, for example, and determine whether treatment is authorized based on the accessed authorization code. The determination whether the attempted treatment is authorized can be performed in response to the attempt to initiate treatment in (902).

If the determination indicates that treatment by the medical device is authorized, the medical device can control a treatment module to apply the treatment that the patient attempted. If the determination indicates that treatment is not authorized, the medical device can control the treatment module so that the treatment attempted by the patient is not applied. No treatment may be authorized for a medical device if, for example, all of the previously authorized treatments have already been used or if the medical device has not received an initial authorization code to enable treatments.

When treatment is not authorized for the medical device, the medical device can notify the patient that payment is needed to purchase additional treatments (904). The example illustrated in FIG. 9A shows a scenario in which the medical device is not initially authorized to perform a treatment attempted by a patient, so additional payment and authorization of the medical device is needed.

Payment can be received at the medical device (906). The patient can then enter payment in one or more ways, including entering payment at the medical device using, for example, a credit card or a debit card to purchase additional treatments. The patient may also complete payment at a location other than the medical device, and enter proof of payment at the medical device. The patient may purchase treatments for example, at a store, at a medical office, or over the Internet. The patient may then enter proof of payment at the medical device in the form of, for example, a computer file, a code, or a SIM card.

The medical device can then send payment information for the payment received and an identifier to the server system (908). The identifier may be a device identifier that uniquely identifies the particular medical device used by the patient. In other words, the device identifier can identify not merely a model or type of medical device, but a single, particular medical device. The identifier may be a patient identifier that identifies a particular patient associated with the medical device.

Treatments can also be purchased for a patient by a third-party, for example, an insurance company. The third-party system can receive, for example, a prescription for treatment of the patient using the medical device (910). The third-party system can authorize one or more treatments using the medical device (912). For example, the third-party system can authorize the treatments identified in the received prescription.

The third party system can send payment information and an identifier to the server system (914). The payment information can include information that enables a transaction to occur, for example, an authorization to charge an account or otherwise cause funds to be transferred, and can include information that indicates that payment has been performed. The identifier can identify the patient associated with the prescription that was received in action (910). For example, the identifier can include a name of the patient, an insurance policy number for the patient, a prescription identifier, or other information relating to the patient. The identifier may also identify the medical device for the patient.

The server system can receive payment information and an associated identifier from either the medical device or the third party system (916). The associated identifier can be a device identifier that uniquely identifies the medical device. The server system can match the payment described in the payment information with the patient and the medical device of the patient (918). The server system can store one or more associations between a patient and the medical device configured to apply a medical treatment to the patient. For example, the server system can store records that associate patients with particular medical devices, patient identifiers, and medical device identifiers.

The server system may use one or more received identifiers to determine which patient and device are associated with a payment. Specifically, the server system can determine that payment has been made for the patient for a particular number of treatments by the medical device. The determination can be made based on the received information that payment has been made for the patient. The server system can identify the medical device associated with the patient based on the stored association between the patient and the medical device and, for example, based on a received device identifier that uniquely identifies the medical device. The server system may also record the determination that payment has been made for the user and the identification of the medical device associated with the patient.

The server system can generate an authorization code that can authorize the medical device associated with the patient to perform the purchased treatments (920). The authorization code can enable the number of treatments purchased by the patient or third-party payer. The authorization code can be generated so that the code only enables treatments of the particular medical device associated with the patient for whom payment was received. For example, the authorization code may be encoded or encrypted so that only the particular medical device associated with the payment can decode or decrypt the authorization code. The authorization code may include or be transmitted with a unique device identifier, and a medical device can be configured to enter an authorization code only when a device identifier of the medical device matches the device identifier received with an authorization code.

The server system can transmit the authorization code to the medical device (922). The authorization code may be transmitted, for example, over a cellular communication link to the medical device that the server system identified as being associated with the patient.

The medical device can receive the authorization code (924). The authorization code may be a new authorization code that is received after an initial or prior authorization code that authorized different treatments. The new authorization code can be received after the medical device has provided an indication to the patient that more treatments need to be purchased, and the new authorization code can identify a number of additional treatments for which payment has been received.

Referring to FIG. 9B, the medical device can decrypt or decode the authorization code (926). In one implementation, the medical device may decrypt the authorization code using a unique device identifier or decryption key stored on the medical device. The medical device may determine that an authorization code is authentic or intended for the particular medical device that received it. The medical device may determine, using decrypted or decoded data, what treatments are authorized. For example, the medical device may determine that a particular number of treatments are authorized. The medical device may also determine that treatment using the medical device should be modified in some way, for example, that two treatments are authorized each day instead of one treatment each day, or that the intensity of ultrasound produced should be changed.

The medical device can store authorization information (928). For example, the medical device can store the number of treatments that the authorization code indicates should be authorized. The medical device can also store the authorization code received, the authorization information extracted from the received data, and other authorization information. In some instances, treatments using the medical device can be authorized without any input or action by the patient. For example, when a third-party payer sends payment to the server system, the medical device can be authorized without involvement from the patient.

The medical device can determine whether treatment is authorized (929). For example, the medical device can determine whether treatment is authorized based on the authorization code that was accessed by the medical device. The medical device can determine whether treatment authorized in response to receiving user input that treatment should be provided, in (902) or through later inputs. In the situation that the patient has attempted treatment with the medical device in (902), and subsequently entered payment needed to authorize treatment in (906), the medical device can proceed to apply the treatment after the determination is made that treatment is authorized. For example, the payment and authorization process may occur quickly so that the patient perceives very little delay between entering payment and the initiation of treatment. In one implementation, treatment may begin automatically when the patient has previously attempted to initiate treatment. Treatment may alternatively be delayed until the patient imitates treatment again or confirms that treatment should proceed.

If the determination indicates that treatment is authorized, the medical device can control a driver circuit to apply treatment (930). For example, the medical device may control an ultrasound transducer driver circuit in a manner that causes one or more ultrasound transducers to produce ultrasound with therapeutic properties. For example, the driver circuit can be activated to drive one or more ultrasound transducers. The driver circuit may continue to drive the ultrasound transducers until treatment is complete. Of course, if the determination indicates that treatment is not authorized based on the authorization code (for example, if the authorization code is for a different medical device, or if the treatments authorized by that code have already been expended), the medical device can control the driver circuit so that treatment is not applied, for example, by not activating the driver circuit so that treatment is prevented.

The driver circuit can be deactivated when treatment is finished (932). The medical device can store a record of the treatment applied (934). The medical device can also decrease the number of treatments authorized for the medical device (936). For example, if the medical device had received an authorization code that authorized twenty treatments of the medical device, after one treatment is completed, the medical device may update the number of authorized treatments to reflect that only nineteen treatments are currently authorized for the medical device.

Referring to FIG. 10, a process 1000 for storing patient information can begin with a physician writing a prescription for a patient for treatment using a medical device (1002). To carry out the prescribed treatment, a medical device can be dispensed to the patient (1004). The medical device can be authorized at the time the medical device is dispensed or at a later time.

Records for the patient and the dispensed medical device can be entered into a database 1014 (1006). For example, the database 1014 may store a patient record 1010 that associates a particular medical device or treatment with a particular patient, in the example, a patient named “John Smith.” The database 1014 may also store a prescription record 1012 that indicates the number of treatments that can be purchased for the patient. The number of treatments indicated in a prescription record 1012 may be authorized for application by the medical device after payment has been received for the prescribed treatments. For example, the treatments can be enabled after a third-party payer agrees to pay for the treatments or after the patient enters payment at the medical device. The database 1014 may also store other records including records that identify patient identifiers and medical device identifiers.

The information in the database can be accessed by one or more client devices 1018, 1020, a server system 1022, or other systems. For example, the server system 1022 may use the patient record 1010 to match payment to a particular medical device or patient. The records stored in the database 1014 may also be used to inform a third-party payer or patient the number of treatments that should be purchased to enable a treatment plan to be carried out.

Referring to FIG. 11, the authorized use of the medical device 10 can be limited to a particular patient and/or geographic area. In some instances, it is desirable by an automated method to limit the use of a medical device by an unauthorized person or in an unauthorized geographic area, such as in a country where the device has not received regulatory approval or in which an unauthorized sale of the device circumvents the chain of distribution of the device. Other examples where “geolocking” of a medical device may be desirable is where devices are sold at different price points in different regions and it is desirable to limit the ability of a lower priced device to be sold in a higher priced region, where device have region specific chargers, include specific languages, or are designed for single patient use or multiple patient use such as in some hospitals.

It is also desirable to limit a single patient use device from being shared with other than the intended patient by, for example, resale or shared use with friends or family members, particularly where the device is a prescription device. The desire to limit such use is particularly applicable to medical devices such as the Exogen™ Ultrasound Bone Healing System sold by Smith & Nephew, Inc. that is easily transported.

To limit, and preferably prevent, the use of a medical device 10 (FIG. 11) in an unauthorized geographic area, the medical device 10 includes hardware and software that determine the geographical location of the medical device 10 upon start-up and compare the determined geographical location to an authorized geographical location. The authorized geographical location can be, for example, programmed in the medical device 10 during the manufacturing process. Referring to FIG. 12, the medical device 10 include a GPS receiver 1210 to determine geographical location, and memory 1214 to store authorized operating areas for the medical device 10. Alternatively, the medical device 10 can use cell phone networks or Wi-Fi to determine geographical location.

Referring to FIG. 13, the location of the medical device 10 is compared to an approved area 1318 in which treatment is authorized. If the geographical location 1320 of the device 10 is within the authorized area 1318, treatment begins. If the geographical location 1322 of the device 10 is in an unauthorized area 1324, no treatment is delivered. The device can include two-way communication, such as cellular, internet or wireless communication. To accommodate patient travel, the medical device 10 can be configured to accept over-the-air-updates to the authorized geographical location.

As illustrated in FIG. 14, for “geolocking” purposes, the medical device 10 includes the GPS receiver 1412, an antenna 1430 connected to the GPS receiver 1412 via an amplifier 1432 and a filter 1434, and a crystal 1436, an integrated circuit 1438, and a regulator 1440.

Advantageously, a medical device can be designed for use within only a specific geographical area, for example, a country or region as illustrated in FIG. 13, such that use of the device in unintended markets is limited or prevented.

To limit, and preferably prevent, the use of the medical device 10 by an unauthorized person, the medical device 10 requires proof of patient identity using, for example, a key card or token issued to the user, a password, or physical evidence. For example, referring to FIG. 2, the medical device 10 includes hardware and software and a user interface 70 implemented on the device to identify the patient using a fingerprint, retinal scan, or voice recognition. The identity of the user is compared to the stored patient identity and treatment is only authorized when the user is confirmed to be the patient.

As illustrated in FIG. 15, for device authorization purposes, the medical device 10 includes, for example, a fingerprint sensor 1552, control electronics such as an integrated circuit 1554, and an EPROM 1556.

Advantageously, the use of a fingerprint, retinal scan, or voice recognition ensures that the patient is at least present during the treatment. In situations where the patient is, for example, young or elderly, the identity of a supervising individual can alternatively or additionally be required. The fingerprint, voice or retinal scan of the authorized user is saved into the memory of the device when the device is prescribed and fitted by a responsible party, for example, a doctor, pharmacist or sales representative.

Referring to FIG. 16, a method for limiting unauthorized use of the medical device 10 includes determining the geographic location of the medical device 10 and not allowing treatment to commence if the determined geographic location is outside an authorized geographic location, and/or includes determining user identity and not allowing treatment to commence if the determined user identity does not match an authorized identity. The medical device 10 includes means for determining the geographic location of the medical device 10 and means for determining user identity. Treatment is not allowed to commence if either the determined geographic location is outside an authorized geographic location or the determined user identity does not match an authorized identity.

In use, the patient turns the device 10 on at step 1660, the device performs a self-test of the clock and configuration at step 1662, the patient, for example, scans his or her index finger over the fingerprint sensor 1552, and the device confirms the patient identity at step 1664. If the patient is the authorized user, the geographical location of the device is checked at step 1666. If the patient is not the authorized user, an authorization alarm is delivered at step 1668 and treatment will not commence. If the patient is the authorized user and the device 10 is within its authorized geographical location treatment can be started at step 1670. If the device 10 is not within its authorized geographical location, an authorization alarm is delivered at step 1668 and treatment will not commence.

At steps 1672, 1674 and 1676, the device 10 monitors the time of use, allowing up to 20 minutes of treatment to be delivered before ending treatment.

The techniques described above are not limited to any particular hardware or software configuration. Rather, they may be implemented using hardware, software, or a combination of both. The methods and processes described may be implemented as computer programs that are executed on programmable computers comprising at least one processor and at least one data storage system. The programs may be implemented in a high-level programming language and may also be implemented in assembly or other lower level languages, if desired.

Any such program will typically be stored on a computer-usable storage medium or device (e.g., CD-ROM, RAM, or magnetic disk). When read into the processor of the computer and executed, the instructions of the program cause the programmable computer to carry out the various operations described above.

A number of implementations have been described. Nevertheless, it will be understood that various modifications may be made. For example, the described features of presentation of messages selected for a particular patient, the collection and display of compliance information, and treatment authorization, and medical device locking based on identity or geographical location may be implemented for a single medical device. In addition, any subset of the features described can be implemented. Each of the message presentation, compliance information collection and display, treatment authorization, and medical device locking features may be implemented individually, separate from the other features described, or together in any combination.

Accordingly, other implementations are within the scope of the following claims.

Claims

1. An apparatus for treating a patient, the apparatus comprising: a treatment source configured to apply therapy to damaged tissue to facilitate healing of the damaged tissue;a memory device configured to store authorization data;a communication receiver configured to receive an update to the authorization data; anda processor configured to: prior to receipt of the update with the communication receiver, determine from the authorization data that the treatment source is authorized for use in a first geographic area and unauthorized for use in a second geographic area,determine a first location of the treatment source in response to receipt of a first user input,permit application of therapy by the treatment source in response to determinations that the first location is in the first geographic area and that the treatment source is authorized for use in the first geographic area,determine a second location of the treatment source in response to receipt of a second user input, andprevent application of therapy by the treatment source in response to determinations that the second location is in the second geographic area and that the treatment source is unauthorized for use in the second geographic area, andsubsequent to receipt of the update with the communication receiver, determine from the authorization data and the update that the treatment source is authorized for use in the second geographic area,determine a third location of the treatment source in response to receipt of a third user input, andpermit application of therapy by the treatment source in response to determinations that the third location is in the second geographic area and that the treatment source is authorized for use in the second geographic area.
2. The apparatus of claim 1, wherein the processor is configured to: cause the treatment source to initiate application of therapy in response to determinations that the first location is in the first geographic area and that the treatment source is authorized for use in the first geographic area; andcause the treatment source to initiate application of therapy in response to determinations that the third location is in the second geographic area and that the treatment source is authorized for use in the second geographic area.
3. The apparatus of claim 1, wherein the treatment source comprises a driver circuit configured to control application of therapy to the damaged tissue, andthe processor is configured to permit application of therapy by activation of the driver circuit or by failure to deactivate the driver circuit.
4. The apparatus of claim 1, wherein the treatment source comprises a driver circuit configured to control application of therapy to the damaged tissue, andthe processor is configured to prevent application of therapy by failure to activate the driver circuit or by deactivation of the driver circuit.
5. The apparatus of claim 1, wherein the processor is configured to determine one or more of the first location, the second location, and the third location from location data from a wireless communications network.
6. The apparatus of claim 1, further comprising a GPS receiver configured to determine a geographical location of the treatment source, the processor being configured to determine one or more of the first location, the second location, and the third location using the GPS receiver.
7. The apparatus of claim 1, further comprising a user interface configured to receive one or more of the first user input, the second user input, and the third user input as a selection of at least one element of the user interface.
8. The apparatus of claim 1, wherein the processor is configured to, prior to receipt of the update with the communication receiver, activate an alarm in response to determinations that the second location is in the second geographic area and that the treatment source is unauthorized for use in the second geographic area.
9. The apparatus of claim 1, wherein the communication receiver is configured to receive the update via a wireless communications network.
10. The apparatus of claim 1, further comprising a sensor, the processor being configured to: prior to receipt of the update with the communication receiver, determine from a first authentication input from the sensor that a first patient using the treatment source matches a prescribed patient, andfurther require that the first patient using the treatment source matches the prescribed patient prior to application of therapy by the treatment source being permitted in response to determinations that the first location is in the first geographic area and that the treatment source is authorized for use in the first geographic area, andsubsequent to receipt of the update with the communication receiver, determine from a second authentication input from the sensor that a second patient using the treatment source matches the prescribed patient,further require that the second patient using the treatment source matches the prescribed patient prior to application of therapy by the treatment source being permitted in response to determinations that the third location is in the second geographic area and that the treatment source is authorized for use in the second geographic area.
11. The apparatus of claim 10, wherein the first authentication input comprises a fingerprint image, a retinal image, or a voice recording.
12. The apparatus of claim 1, wherein the memory device is configured to store a device identifier,the authorization data is encrypted, andthe processor is configured to decrypt the authorization data using the device identifier.
13. A method of controlling an apparatus for treating a patient, the method comprising: determining from authorization data stored in a memory device that a treatment source is authorized for use in a first geographic area and unauthorized for use in a second geographic area;receiving a first user input via a user interface;determining a first location of the treatment source in response to receiving the first user input;performing first therapy to damaged tissue with the treatment source to facilitate healing of the damaged tissue in response to determining that the first location is in the first geographic area and that the treatment source is authorized for use in the first geographic area;subsequent to said performing first therapy, receiving an update to the authorization data using a communication receiver;determining from the authorization data and the update that the treatment source is authorized for use in the second geographic area;receiving a second user input via the user interface;determining a second location of the treatment source in response to receiving the second user input; andperforming second therapy to the damaged tissue with the treatment source to facilitate healing of the damaged tissue in response to determining that the second location is in the second geographic area and that the treatment source is authorized for use in the second geographic area.
14. The method of claim 13, wherein said determining the first location comprises determining the first location from location data from a wireless communications network.
15. The method of claim 13, wherein said determining the first location comprises determining the first location using a GPS receiver.
16. The method of claim 13, further comprising, prior to said receiving the update, activating an alarm in response to determining that the second location is in the second geographic area and that the treatment source is unauthorized for use in the second geographic area.
17. The method of claim 13, wherein said receiving the update comprises receiving the update via a wireless communications network using the communication receiver.
18. The method of claim 13, further comprising: receiving an authentication input using a sensor; anddetermining from the authorization data and the authentication input that the treatment source is authorized for use in the first geographic area.
19. The method of claim 18, wherein the authentication input comprises a fingerprint image, a retinal image, or a voice recording.
20. The method of claim 13, further comprising: storing a device identifier in the memory device; anddecrypting the authorization data using the device identifier.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 13/271,870, field on Oct. 12, 2011, and titled “Medical Device,” which claims priority to and the full benefit of U.S. Provisional Application Ser. No. 61/392,154, filed Oct. 12, 2010, and titled “Authorizing Use of Medical Devices,” U.S. Provisional Application Ser. No. 61/405,405, filed 5 Oct. 21, 2010, and titled “Medical Device,” U.S. Provisional Application Ser. No. 61/405,757, filed Oct. 22, 2010, and titled “Medical Device,” and U.S. Provisional Application Ser. No. 61/483,445, filed May 6, 2011, and titled “Medical Device,” the entire contents of which are incorporated herein by reference.

US Referenced Citations (599)

Number	Name	Date	Kind
695270	Beringer	Mar 1902	A
3194239	Sullivan	Jul 1965	A
4642769	Petrofsky	Feb 1987	A
4832299	Gorton et al.	May 1989	A
4899839	Dessertine et al.	Feb 1990	A
5016172	Dessertine	May 1991	A
5158528	Walker et al.	Oct 1992	A
5174533	Pryor et al.	Dec 1992	A
5215523	Williams et al.	Jun 1993	A
5219428	Stern	Jun 1993	A
5419768	Kayser	May 1995	A
5449347	Preen et al.	Sep 1995	A
5466229	Elson	Nov 1995	A
5473536	Wimmer	Dec 1995	A
5556372	Talish et al.	Sep 1996	A
5582601	Wortrich et al.	Dec 1996	A
5584824	Gillette et al.	Dec 1996	A
5599308	Krupa	Feb 1997	A
5622429	Heinze	Apr 1997	A
5634939	Kuster et al.	Jun 1997	A
5656027	Ellingboe	Aug 1997	A
5669892	Keogh et al.	Sep 1997	A
5687717	Halpern et al.	Nov 1997	A
5693013	Geuder	Dec 1997	A
5748103	Flach et al.	May 1998	A
5779207	Danby	Jul 1998	A
D408625	Barker	Apr 1999	S
5933136	Brown	Aug 1999	A
5956023	Lyle et al.	Sep 1999	A
5989234	Valerio et al.	Nov 1999	A
6018289	Sekura et al.	Jan 2000	A
6161095	Brown	Dec 2000	A
6174306	Fleischmann	Jan 2001	B1
6228056	Boehringer et al.	May 2001	B1
6241739	Waldron	Jun 2001	B1
6250482	Want et al.	Jun 2001	B1
6261249	Talish et al.	Jul 2001	B1
6270460	McCartan et al.	Aug 2001	B1
6308089	von der Ruhr et al.	Oct 2001	B1
6387092	Burnside et al.	May 2002	B1
6413213	Essenpreis et al.	Jul 2002	B1
6572530	Araki et al.	Jun 2003	B1
6574518	Lounsberry et al.	Jun 2003	B1
6577893	Besson et al.	Jun 2003	B1
6605032	Benkowski et al.	Aug 2003	B2
6640246	Gary, Jr. et al.	Oct 2003	B1
6681003	Linder et al.	Jan 2004	B2
6738052	Manke et al.	May 2004	B1
6766218	Rosenblum	Jul 2004	B2
6792306	Henley et al.	Sep 2004	B2
6811533	Lebel et al.	Nov 2004	B2
7004915	Boynton et al.	Feb 2006	B2
7022113	Lockwood et al.	Apr 2006	B2
7048687	Reuss et al.	May 2006	B1
7128735	Weston	Oct 2006	B2
7273483	Wiener et al.	Sep 2007	B2
D565177	Locke et al.	Mar 2008	S
7361184	Joshi	Apr 2008	B2
7364554	Bolze et al.	Apr 2008	B2
7395214	Shillingburg	Jul 2008	B2
D581042	Randolph et al.	Nov 2008	S
D581522	Randolph et al.	Nov 2008	S
7448265	Smyser et al.	Nov 2008	B2
7505815	Lee et al.	Mar 2009	B2
D590934	Randolph et al.	Apr 2009	S
7553306	Hunt et al.	Jun 2009	B1
7569742	Haggstrom et al.	Aug 2009	B2
7594901	Hopkins et al.	Sep 2009	B2
D602582	Pidgeon et al.	Oct 2009	S
D602583	Pidgeon et al.	Oct 2009	S
7598855	Scalisi et al.	Oct 2009	B2
7611500	Lina et al.	Nov 2009	B1
7615036	Joshi et al.	Nov 2009	B2
7639120	Sekura	Dec 2009	B2
7670323	Hunt et al.	Mar 2010	B2
7699823	Haggstrom et al.	Apr 2010	B2
7723560	Lockwood et al.	May 2010	B2
7753894	Blott et al.	Jul 2010	B2
7770855	Locke et al.	Aug 2010	B2
7776028	Miller et al.	Aug 2010	B2
7785277	Babaev et al.	Aug 2010	B2
D625801	Pidgeon et al.	Oct 2010	S
7846141	Weston	Dec 2010	B2
7857806	Karpowicz et al.	Dec 2010	B2
7890887	Linardos et al.	Feb 2011	B1
D635588	Sprules	Apr 2011	S
7925603	Laidig et al.	Apr 2011	B1
7927319	Lawhorn	Apr 2011	B2
7933817	Radl et al.	Apr 2011	B2
7945452	Fathallah et al.	May 2011	B2
7955281	Pedersen et al.	Jun 2011	B2
7956727	Loncar	Jun 2011	B2
D644250	Barber et al.	Aug 2011	S
7988850	Roncadi et al.	Aug 2011	B2
8007481	Schuessler et al.	Aug 2011	B2
8048046	Hudspeth et al.	Nov 2011	B2
8061360	Locke et al.	Nov 2011	B2
8066243	Svedman et al.	Nov 2011	B2
8096515	Locke et al.	Jan 2012	B2
8100873	Jaeb et al.	Jan 2012	B2
8105295	Blott et al.	Jan 2012	B2
8216198	Heagle et al.	Jul 2012	B2
8228188	Key et al.	Jul 2012	B2
8235955	Blott et al.	Aug 2012	B2
8240470	Pidgeon et al.	Aug 2012	B2
8246607	Karpowicz et al.	Aug 2012	B2
8257328	Augustine et al.	Sep 2012	B2
8267918	Johnson et al.	Sep 2012	B2
8284024	Toleti et al.	Oct 2012	B2
8294586	Pidgeon et al.	Oct 2012	B2
8298200	Vess et al.	Oct 2012	B2
8308714	Weston et al.	Nov 2012	B2
8317752	Cozmi et al.	Nov 2012	B2
8333744	Hartwell et al.	Dec 2012	B2
8360975	Schwieterman et al.	Jan 2013	B1
8366692	Weston	Feb 2013	B2
8377016	Argenta et al.	Feb 2013	B2
8377018	Bendele et al.	Feb 2013	B2
8400295	Khaira	Mar 2013	B1
8403902	Locke et al.	Mar 2013	B2
8409170	Locke et al.	Apr 2013	B2
8424517	Sutherland et al.	Apr 2013	B2
8439882	Kelch	May 2013	B2
8444392	Turner et al.	May 2013	B2
8480641	Jacobs	Jul 2013	B2
8494349	Gordon	Jul 2013	B2
8540688	Eckstein et al.	Sep 2013	B2
8552880	Kopp et al.	Oct 2013	B2
8558964	Bedingfield	Oct 2013	B2
8604265	Locke et al.	Dec 2013	B2
8617129	Hartwell	Dec 2013	B2
8622981	Hartwell et al.	Jan 2014	B2
8626342	Williams, Jr. et al.	Jan 2014	B2
8628258	Vogt	Jan 2014	B2
8641693	Locke et al.	Feb 2014	B2
8652111	Pratt et al.	Feb 2014	B2
8668677	Eckstein et al.	Mar 2014	B2
8694600	Gaines et al.	Apr 2014	B2
8747376	Locke et al.	Jun 2014	B2
8756078	Collins et al.	Jun 2014	B2
8771259	Karpowicz et al.	Jul 2014	B2
8798284	Cartwright et al.	Aug 2014	B2
8814841	Hartwell	Aug 2014	B2
8814842	Coulthard et al.	Aug 2014	B2
8827983	Braga et al.	Sep 2014	B2
8843327	Vernon-Harcourt et al.	Sep 2014	B2
8845603	Middleton et al.	Sep 2014	B2
8845604	Croizat et al.	Sep 2014	B2
8852149	Weston et al.	Oct 2014	B2
8858517	Pan et al.	Oct 2014	B2
8870812	Alberti et al.	Oct 2014	B2
8897198	Gaines et al.	Nov 2014	B2
8902278	Pinter et al.	Dec 2014	B2
8905959	Basaglia	Dec 2014	B2
8905985	Allen et al.	Dec 2014	B2
8926574	Croizat et al.	Jan 2015	B2
8943168	Wiesner et al.	Jan 2015	B2
8945030	Weston	Feb 2015	B2
8945073	Croizat et al.	Feb 2015	B2
8945074	Buan et al.	Feb 2015	B2
8961497	Ryu et al.	Feb 2015	B2
8974429	Gordon et al.	Mar 2015	B2
9017286	Kamen et al.	Apr 2015	B2
9019681	Locke et al.	Apr 2015	B2
9023002	Robinson et al.	May 2015	B2
9058634	Buan et al.	Jun 2015	B2
9067003	Buan et al.	Jun 2015	B2
9084845	Adie et al.	Jul 2015	B2
9408954	Gordon et al.	Aug 2016	B2
20010013822	Nazarian et al.	Aug 2001	A1
20010031944	Peterson et al.	Oct 2001	A1
20010041831	Starkweather et al.	Nov 2001	A1
20010049609	Girouard et al.	Dec 2001	A1
20020002326	Causey, III et al.	Jan 2002	A1
20020002368	Tomita et al.	Jan 2002	A1
20020013516	Freyre et al.	Jan 2002	A1
20020015034	Malmborg	Feb 2002	A1
20020026160	Takahashi et al.	Feb 2002	A1
20020049562	Hahn	Apr 2002	A1
20020065685	Sasaki et al.	May 2002	A1
20020082568	Yam	Jun 2002	A1
20020087360	Pettit	Jul 2002	A1
20020120467	Buanes	Aug 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
20020193679	Malave et al.	Dec 2002	A1
20020198505	Want et al.	Dec 2002	A1
20030009244	Engleson et al.	Jan 2003	A1
20030018395	Crnkovich et al.	Jan 2003	A1
20030018736	Christ et al.	Jan 2003	A1
20030028175	D'Antonio	Feb 2003	A1
20030040687	Boynton et al.	Feb 2003	A1
20030093041	Risk, Jr. et al.	May 2003	A1
20030093181	Rosenblum	May 2003	A1
20030105389	Noonan et al.	Jun 2003	A1
20030105649	Sheiner et al.	Jun 2003	A1
20030128125	Burbank et al.	Jul 2003	A1
20030130567	Mault et al.	Jul 2003	A1
20030164600	Dunn et al.	Sep 2003	A1
20030176183	Drucker et al.	Sep 2003	A1
20030182158	Son	Sep 2003	A1
20030214412	Ho et al.	Nov 2003	A1
20030221687	Kaigler	Dec 2003	A1
20030229518	Abraham-Fuchs	Dec 2003	A1
20030233071	Gillespie, Jr. et al.	Dec 2003	A1
20040015132	Brown	Jan 2004	A1
20040019464	Martucci et al.	Jan 2004	A1
20040039255	Simonsen et al.	Feb 2004	A1
20040049172	Root et al.	Mar 2004	A1
20040054338	Bybordi et al.	Mar 2004	A1
20040054775	Poliac et al.	Mar 2004	A1
20040059284	Nash et al.	Mar 2004	A1
20040064132	Boehringer et al.	Apr 2004	A1
20040078223	Sacco et al.	Apr 2004	A1
20040102743	Walker	May 2004	A1
20040120825	Bouton et al.	Jun 2004	A1
20040143458	Pulkkinen et al.	Jul 2004	A1
20040158193	Bui et al.	Aug 2004	A1
20040171982	Danchin	Sep 2004	A1
20040176983	Birkett et al.	Sep 2004	A1
20040181314	Zaleski	Sep 2004	A1
20040193449	Wildman et al.	Sep 2004	A1
20040227737	Novak et al.	Nov 2004	A1
20040249673	Smith	Dec 2004	A1
20050011282	Voege et al.	Jan 2005	A1
20050022274	Campbell et al.	Jan 2005	A1
20050027311	Wiener et al.	Feb 2005	A1
20050033124	Kelly et al.	Feb 2005	A1
20050060211	Xiao et al.	Mar 2005	A1
20050065471	Kuntz	Mar 2005	A1
20050108190	Conkel	May 2005	A1
20050114176	Dominick et al.	May 2005	A1
20050116126	Ugent et al.	Jun 2005	A1
20050119914	Batch	Jun 2005	A1
20050124966	Karpowicz et al.	Jun 2005	A1
20050187528	Berg	Aug 2005	A1
20050209560	Boukhny et al.	Sep 2005	A1
20050230575	Zelenski	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
20060020161	Mageras et al.	Jan 2006	A1
20060029675	Ginther	Feb 2006	A1
20060064491	Ebert et al.	Mar 2006	A1
20060089544	Williams, Jr. et al.	Apr 2006	A1
20060095853	Amyot et al.	May 2006	A1
20060132283	Eberhart et al.	Jun 2006	A1
20060144440	Merkle	Jul 2006	A1
20060149171	Vogel et al.	Jul 2006	A1
20060155584	Aggarwal	Jul 2006	A1
20060190130	Fedor et al.	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
20070005029	Hopkins et al.	Jan 2007	A1
20070016152	Karpowicz et al.	Jan 2007	A1
20070032741	Hibner et al.	Feb 2007	A1
20070032762	Vogel	Feb 2007	A1
20070032763	Vogel	Feb 2007	A1
20070038044	Dobbles et al.	Feb 2007	A1
20070052683	Knott et al.	Mar 2007	A1
20070055209	Patel et al.	Mar 2007	A1
20070078444	Larsson	Apr 2007	A1
20070100403	Felice et al.	May 2007	A1
20070118096	Smith et al.	May 2007	A1
20070118397	Williams et al.	May 2007	A1
20070138069	Roncadi et al.	Jun 2007	A1
20070156186	Lee et al.	Jul 2007	A1
20070173708	Dobbles et al.	Jul 2007	A9
20070179460	Adahan	Aug 2007	A1
20070180904	Gao	Aug 2007	A1
20070219480	Kamen et al.	Sep 2007	A1
20070227360	Atlas et al.	Oct 2007	A1
20070227537	Bernister et al.	Oct 2007	A1
20070233022	Henley et al.	Oct 2007	A1
20070250009	Barak	Oct 2007	A1
20070255114	Ackerman et al.	Nov 2007	A1
20070255116	Mehta et al.	Nov 2007	A1
20070260226	Jaeb et al.	Nov 2007	A1
20070271298	Juang et al.	Nov 2007	A1
20070276309	Xu et al.	Nov 2007	A1
20070282249	Quisenberry et al.	Dec 2007	A1
20080004818	Zaleski	Jan 2008	A1
20080005000	Radl et al.	Jan 2008	A1
20080009681	Hussiny	Jan 2008	A1
20080015526	Reiner et al.	Jan 2008	A1
20080039761	Heaton et al.	Feb 2008	A1
20080041401	Casola et al.	Feb 2008	A1
20080051708	Kumar et al.	Feb 2008	A1
20080071209	Moubayed et al.	Mar 2008	A1
20080071216	Locke et al.	Mar 2008	A1
20080071234	Kelch et al.	Mar 2008	A1
20080071235	Locke et al.	Mar 2008	A1
20080077091	Mulligan	Mar 2008	A1
20080082040	Kubler et al.	Apr 2008	A1
20080082077	Williams	Apr 2008	A1
20080086357	Choubey et al.	Apr 2008	A1
20080091175	Frikart et al.	Apr 2008	A1
20080091659	McFaul	Apr 2008	A1
20080125697	Gao	May 2008	A1
20080125698	Gerg et al.	May 2008	A1
20080126126	Ballai	May 2008	A1
20080140160	Goetz et al.	Jun 2008	A1
20080147431	Walneck et al.	Jun 2008	A1
20080167534	Young et al.	Jul 2008	A1
20080177224	Kelly et al.	Jul 2008	A1
20080180268	Nissels et al.	Jul 2008	A1
20080200868	Alberti et al.	Aug 2008	A1
20080200905	Heaton	Aug 2008	A1
20080200906	Sanders et al.	Aug 2008	A1
20080201174	Ramasubramanian et al.	Aug 2008	A1
20080208147	Argenta et al.	Aug 2008	A1
20080209357	Vasta et al.	Aug 2008	A1
20080221396	Garces et al.	Sep 2008	A1
20080228526	Locke et al.	Sep 2008	A1
20080234641	Locke et al.	Sep 2008	A1
20080242945	Gugliotti et al.	Oct 2008	A1
20080243096	Svedman	Oct 2008	A1
20080249377	Molducci et al.	Oct 2008	A1
20080272254	Harr et al.	Nov 2008	A1
20080300572	Rankers et al.	Dec 2008	A1
20080307353	Molducci et al.	Dec 2008	A1
20080319510	Simpson et al.	Dec 2008	A1
20090005746	Nielsen et al.	Jan 2009	A1
20090023432	MacInnis et al.	Jan 2009	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
20090082741	Hu	Mar 2009	A1
20090099866	Newman	Apr 2009	A1
20090099867	Newman	Apr 2009	A1
20090101219	Martini et al.	Apr 2009	A1
20090115663	Brown et al.	May 2009	A1
20090118591	Kim et al.	May 2009	A1
20090118751	Wiener et al.	May 2009	A1
20090125055	Larkin et al.	May 2009	A1
20090125331	Pamsgaard et al.	May 2009	A1
20090125389	Dunko et al.	May 2009	A1
20090144091	Rago	Jun 2009	A1
20090171166	Amundson et al.	Jul 2009	A1
20090171288	Wheeler	Jul 2009	A1
20090171289	Davis et al.	Jul 2009	A1
20090182266	Gordon et al.	Jul 2009	A1
20090182594	Choubey	Jul 2009	A1
20090187424	Grabowski	Jul 2009	A1
20090204434	Breazeale	Aug 2009	A1
20090204435	Gale	Aug 2009	A1
20090206017	Rohde et al.	Aug 2009	A1
20090227910	Pedersen et al.	Sep 2009	A1
20090248448	Zakay et al.	Oct 2009	A1
20090248578	Pollock et al.	Oct 2009	A1
20090254362	Choubey et al.	Oct 2009	A1
20090259220	Appling et al.	Oct 2009	A1
20090270833	DeBelser et al.	Oct 2009	A1
20090276008	Lee et al.	Nov 2009	A1
20090281464	Cioanta et al.	Nov 2009	A1
20090281867	Sievenpiper et al.	Nov 2009	A1
20090282192	Maus et al.	Nov 2009	A1
20090292264	Hudspeth et al.	Nov 2009	A1
20090299306	Buan	Dec 2009	A1
20090326339	Horvitz	Dec 2009	A1
20090327102	Maniar et al.	Dec 2009	A1
20100001838	Miodownik et al.	Jan 2010	A1
20100010646	Drew et al.	Jan 2010	A1
20100020021	Mills et al.	Jan 2010	A1
20100022990	Karpowicz et al.	Jan 2010	A1
20100036333	Schenk, III et al.	Feb 2010	A1
20100042021	Hu et al.	Feb 2010	A1
20100042059	Pratt et al.	Feb 2010	A1
20100056875	Schoenberg et al.	Mar 2010	A1
20100063483	Adahan	Mar 2010	A1
20100069829	Hutchinson et al.	Mar 2010	A1
20100081971	Allison	Apr 2010	A1
20100090004	Sands et al.	Apr 2010	A1
20100114026	Karratt et al.	May 2010	A1
20100121257	King	May 2010	A1
20100126268	Baily et al.	May 2010	A1
20100137775	Hu et al.	Jun 2010	A1
20100145161	Niyato et al.	Jun 2010	A1
20100145289	Line et al.	Jun 2010	A1
20100150991	Bernstein	Jun 2010	A1
20100152624	Tanis et al.	Jun 2010	A1
20100168687	Yu	Jul 2010	A1
20100169111	Brue et al.	Jul 2010	A1
20100169120	Herbst et al.	Jul 2010	A1
20100191178	Ross et al.	Jul 2010	A1
20100191199	Evans et al.	Jul 2010	A1
20100198142	Sloan et al.	Aug 2010	A1
20100200486	Gunther et al.	Aug 2010	A1
20100204663	Wudyka	Aug 2010	A1
20100211030	Turner et al.	Aug 2010	A1
20100222645	Nadler et al.	Sep 2010	A1
20100228205	Hu et al.	Sep 2010	A1
20100234708	Buck et al.	Sep 2010	A1
20100250697	Hansen et al.	Sep 2010	A1
20100251114	Wehba et al.	Sep 2010	A1
20100255876	Jordan et al.	Oct 2010	A1
20100268179	Kelch et al.	Oct 2010	A1
20100274177	Rybski et al.	Oct 2010	A1
20100280435	Raney et al.	Nov 2010	A1
20100280536	Hartwell	Nov 2010	A1
20100282834	Devergne et al.	Nov 2010	A1
20100305490	Coulthard et al.	Dec 2010	A1
20100305523	Vess	Dec 2010	A1
20100313958	Patel et al.	Dec 2010	A1
20100314517	Patzer	Dec 2010	A1
20100317933	Colman et al.	Dec 2010	A1
20100318043	Malhi et al.	Dec 2010	A1
20100318071	Wudyka	Dec 2010	A1
20100331673	Maschke et al.	Dec 2010	A1
20100331741	Cioanta et al.	Dec 2010	A9
20110003610	Key et al.	Jan 2011	A1
20110004188	Shekalim	Jan 2011	A1
20110006876	Moberg et al.	Jan 2011	A1
20110009824	Yodfat et al.	Jan 2011	A1
20110015585	Svedman et al.	Jan 2011	A1
20110015587	Tumey et al.	Jan 2011	A1
20110015590	Svedman et al.	Jan 2011	A1
20110021952	Vallone	Jan 2011	A1
20110028881	Basaglia	Feb 2011	A1
20110028882	Basaglia	Feb 2011	A1
20110028921	Hartwell et al.	Feb 2011	A1
20110034861	Schaefer	Feb 2011	A1
20110038741	Lissner et al.	Feb 2011	A1
20110040268	Eckstein et al.	Feb 2011	A1
20110040288	Eckstein et al.	Feb 2011	A1
20110046521	Farrelly	Feb 2011	A1
20110054810	Turner	Mar 2011	A1
20110063117	Turner	Mar 2011	A1
20110066096	Svedman	Mar 2011	A1
20110066110	Fathallah et al.	Mar 2011	A1
20110066123	Tout et al.	Mar 2011	A1
20110071415	Karwoski et al.	Mar 2011	A1
20110071844	Cannon et al.	Mar 2011	A1
20110073644	Sarkis, Jr. et al.	Mar 2011	A1
20110077605	Karpowicz et al.	Mar 2011	A1
20110092927	Wilkes et al.	Apr 2011	A1
20110092958	Jacobs	Apr 2011	A1
20110106028	Giezendanner et al.	May 2011	A1
20110106561	Eaton, Jr. et al.	May 2011	A1
20110107251	Guaitoli et al.	May 2011	A1
20110112492	Bharti et al.	May 2011	A1
20110112857	Yurko et al.	May 2011	A1
20110130712	Topaz	Jun 2011	A1
20110137759	Wellington et al.	Jun 2011	A1
20110152739	Roncadi et al.	Jun 2011	A1
20110173028	Bond	Jul 2011	A1
20110190703	Pratt et al.	Aug 2011	A1
20110196321	Wudyka	Aug 2011	A1
20110237981	Voss	Sep 2011	A1
20110245682	Robinson et al.	Oct 2011	A1
20110246219	Smith et al.	Oct 2011	A1
20110251569	Turner et al.	Oct 2011	A1
20110257572	Locke et al.	Oct 2011	A1
20110288511	Locke et al.	Nov 2011	A1
20110290979	Henault et al.	Dec 2011	A1
20110313789	Kamen et al.	Dec 2011	A1
20110319813	Kamen et al.	Dec 2011	A1
20120001762	Turner et al.	Jan 2012	A1
20120032819	Chae et al.	Feb 2012	A1
20120035427	Friedman et al.	Feb 2012	A1
20120035560	Eddy et al.	Feb 2012	A1
20120035561	Locke et al.	Feb 2012	A1
20120046624	Locke et al.	Feb 2012	A1
20120046625	Johannison	Feb 2012	A1
20120071845	Hu et al.	Mar 2012	A1
20120081225	Waugh et al.	Apr 2012	A1
20120123323	Kagan et al.	May 2012	A1
20120123358	Hall et al.	May 2012	A1
20120157889	Tanis et al.	Jun 2012	A1
20120157941	Luckemeyer et al.	Jun 2012	A1
20120165620	Tanis et al.	Jun 2012	A1
20120176394	Vik et al.	Jul 2012	A1
20120181405	Zlatic et al.	Jul 2012	A1
20120182143	Gaines et al.	Jul 2012	A1
20120184930	Johannison	Jul 2012	A1
20120184932	Giezendanner et al.	Jul 2012	A1
20120197196	Halbert et al.	Aug 2012	A1
20120197580	Vij et al.	Aug 2012	A1
20120209228	Croizat et al.	Aug 2012	A1
20120212434	Bluemler et al.	Aug 2012	A1
20120212455	Kloeffel	Aug 2012	A1
20120215455	Patil et al.	Aug 2012	A1
20120220960	Ruland	Aug 2012	A1
20120226247	Danei et al.	Sep 2012	A1
20120226768	Gaines et al.	Sep 2012	A1
20120259283	Haase	Oct 2012	A1
20120259651	Mallon et al.	Oct 2012	A1
20120271256	Locke et al.	Oct 2012	A1
20120289895	Tsoukalis	Nov 2012	A1
20120289913	Eckstein et al.	Nov 2012	A1
20120289914	Eckstein et al.	Nov 2012	A1
20120290217	Shoval et al.	Nov 2012	A1
20120293322	Ray et al.	Nov 2012	A1
20120295566	Collins et al.	Nov 2012	A1
20120302976	Locke et al.	Nov 2012	A1
20120310205	Lee et al.	Dec 2012	A1
20130018355	Brand et al.	Jan 2013	A1
20130019744	Hu	Jan 2013	A1
20130023719	Bennett	Jan 2013	A1
20130028788	Gronau et al.	Jan 2013	A1
20130030394	Locke et al.	Jan 2013	A1
20130035615	Hsieh	Feb 2013	A1
20130053692	Barron et al.	Feb 2013	A1
20130062265	Balschat et al.	Mar 2013	A1
20130066285	Locke et al.	Mar 2013	A1
20130066301	Locke et al.	Mar 2013	A1
20130073303	Hsu	Mar 2013	A1
20130076528	Boettner et al.	Mar 2013	A1
20130088452	Glaser-Seidnitzer et al.	Apr 2013	A1
20130090613	Kelch et al.	Apr 2013	A1
20130090949	Tibebu	Apr 2013	A1
20130102836	Millman	Apr 2013	A1
20130103419	Beaudry	Apr 2013	A1
20130123755	Locke et al.	May 2013	A1
20130124227	Ellis	May 2013	A1
20130133036	Wang et al.	May 2013	A1
20130144227	Locke et al.	Jun 2013	A1
20130144230	Wu et al.	Jun 2013	A1
20130150686	Fronterhouse et al.	Jun 2013	A1
20130159456	Daoud et al.	Jun 2013	A1
20130165821	Freedman et al.	Jun 2013	A1
20130165854	Sandhu et al.	Jun 2013	A1
20130165877	Leeson et al.	Jun 2013	A1
20130169432	Ozgul et al.	Jul 2013	A1
20130176230	Georgiev et al.	Jul 2013	A1
20130186405	Krzyzanowski et al.	Jul 2013	A1
20130190717	Dollar et al.	Jul 2013	A1
20130190903	Balakrishnan et al.	Jul 2013	A1
20130196703	Masoud et al.	Aug 2013	A1
20130198685	Bernini et al.	Aug 2013	A1
20130204210	Pratt et al.	Aug 2013	A1
20130212168	Bonasera et al.	Aug 2013	A1
20130214925	Weiss	Aug 2013	A1
20130223979	Locke et al.	Aug 2013	A1
20130226607	Woody et al.	Aug 2013	A1
20130231596	Hornback et al.	Sep 2013	A1
20130245387	Patel	Sep 2013	A1
20130245580	Locke et al.	Sep 2013	A1
20130253952	Burke et al.	Sep 2013	A1
20130254717	Al-Ali et al.	Sep 2013	A1
20130262730	Al-Ali et al.	Oct 2013	A1
20130267917	Pan et al.	Oct 2013	A1
20130267918	Pan 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
20130275145	Moore et al.	Oct 2013	A1
20130285837	Uchida	Oct 2013	A1
20130289536	Croizat et al.	Oct 2013	A1
20130293570	Dolgos et al.	Nov 2013	A1
20130297350	Gross et al.	Nov 2013	A1
20130303975	Gvodas et al.	Nov 2013	A1
20130310631	Lee et al.	Nov 2013	A1
20130310726	Miller et al.	Nov 2013	A1
20130310778	Locke et al.	Nov 2013	A1
20130317420	Wehmeyer	Nov 2013	A1
20130317463	Yao et al.	Nov 2013	A1
20130325508	Johnson et al.	Dec 2013	A1
20130327326	Brennan	Dec 2013	A1
20130331822	Patel et al.	Dec 2013	A1
20130332197	Hinkel	Dec 2013	A1
20130335233	Kamar et al.	Dec 2013	A1
20130345524	Meyer et al.	Dec 2013	A1
20140031884	Elghazzawi	Jan 2014	A1
20140032231	Semen et al.	Jan 2014	A1
20140052202	Daynes	Feb 2014	A1
20140055588	Bangera et al.	Feb 2014	A1
20140058344	Toth	Feb 2014	A1
20140100516	Hunt et al.	Apr 2014	A1
20140108033	Akbay et al.	Apr 2014	A1
20140108034	Akbay et al.	Apr 2014	A1
20140108035	Akbay et al.	Apr 2014	A1
20140114236	Gordon	Apr 2014	A1
20140114237	Gordon	Apr 2014	A1
20140129250	Daniel et al.	May 2014	A1
20140136218	Bolene et al.	May 2014	A1
20140148138	Chou et al.	May 2014	A1
20140163490	Locke et al.	Jun 2014	A1
20140163493	Weston et al.	Jun 2014	A1
20140194835	Ehlert	Jul 2014	A1
20140236106	Locke et al.	Aug 2014	A1
20140303551	Germain et al.	Oct 2014	A1
20140323906	Peatfield et al.	Oct 2014	A1
20150025482	Begin et al.	Jan 2015	A1
20150025486	Hu et al.	Jan 2015	A1
20150051560	Askem	Feb 2015	A1
20150073363	Kelch et al.	Mar 2015	A1
20150094673	Pratt et al.	Apr 2015	A1
20150094674	Pratt et al.	Apr 2015	A1
20150133829	DeBusk et al.	May 2015	A1
20150174304	Askem et al.	Jun 2015	A1
20170209718	Tanis et al.	Jul 2017	A1

Foreign Referenced Citations (133)

Number	Date	Country
2 819 475	Jun 2012	CA
104721892	Jun 2015	CN
10 2010 036405	Jan 2012	DE
20 2014 10752	Jun 2014	DE
0 403 294	Dec 1990	EP
0 526 166	Feb 1994	EP
0 829 228	Mar 1998	EP
1 034 734	Sep 2000	EP
1 064 053	Jan 2001	EP
0 809 470	Oct 2002	EP
1 176 909	Jul 2003	EP
0 904 788	Nov 2003	EP
1 199 046	Jan 2005	EP
1 566 201	Aug 2005	EP
1 566 201	Sep 2005	EP
1 633 241	Mar 2006	EP
1 684 146	Jul 2006	EP
1 702 649	Sep 2006	EP
1 788 503	May 2007	EP
1 797 918	Jun 2007	EP
1 857 950	Nov 2007	EP
1 610 861	Mar 2009	EP
2 172 859	Apr 2010	EP
2 218 478	Aug 2010	EP
2 246 079	Nov 2010	EP
2 248 545	Nov 2010	EP
1 668 556	Feb 2011	EP
2 279 028	Feb 2011	EP
1 970 098	May 2011	EP
1 248 660	Apr 2012	EP
1 248 661	Aug 2012	EP
2 503 478	Sep 2012	EP
2 505 169	Dec 2012	EP
2 529 765	Dec 2012	EP
2 389 961	Mar 2013	EP
2 674 845	Dec 2013	EP
2 650 027	Jan 2014	EP
1 565 219	Feb 2014	EP
2 562 665	Jul 2014	EP
2 066 365	Apr 2015	EP
2235877	Mar 1991	GB
2279784	Jan 1995	GB
2342584	Apr 2000	GB
2409951	Jul 2005	GB
2475091	May 2011	GB
2488904	Sep 2012	GB
H10-085288	Apr 1998	JP
2003-116796	Apr 2003	JP
2005-027798	Feb 2005	JP
2005-71314	Mar 2005	JP
2007-289481	Nov 2007	JP
WO 199619335	Jun 1996	WO
WO 1996025112	Aug 1996	WO
WO 1999035588	Jul 1999	WO
WO 1999047209	Sep 1999	WO
WO 2000061003	Oct 2000	WO
WO 200114048	Mar 2001	WO
WO 2001036027	May 2001	WO
WO 2002028477	Apr 2002	WO
WO 2002093301	May 2003	WO
WO 2003055432	Jul 2003	WO
WO 2003060650	Jul 2003	WO
WO 2003101508	Dec 2003	WO
WO 2003094090	Sep 2004	WO
WO 2004093983	Nov 2004	WO
WO 2004100779	Nov 2004	WO
WO 2005109297	Mar 2006	WO
WO 2007056734	May 2007	WO
WO 2008036344	Mar 2008	WO
WO 2008036360	Mar 2008	WO
WO 2008039314	Apr 2008	WO
WO 2008104609	Sep 2008	WO
WO 2008116295	Oct 2008	WO
WO 2008132215	Nov 2008	WO
WO 2008157017	Dec 2008	WO
WO 2009021523	Feb 2009	WO
WO 2009023432	Apr 2009	WO
WO 2009047524	Apr 2009	WO
WO 2009089390	Jul 2009	WO
WO 2009093116	Jul 2009	WO
WO 2009117549	Sep 2009	WO
WO 2009137699	Nov 2009	WO
WO 2009151645	Dec 2009	WO
WO 2010017484	Feb 2010	WO
WO 2010039481	Apr 2010	WO
WO 2010085033	Jul 2010	WO
WO 2010089368	Aug 2010	WO
WO 2010126668	Nov 2010	WO
WO 2010145780	Dec 2010	WO
WO 2011023275	Mar 2011	WO
WO 2011089270	Jul 2011	WO
WO 2011107972	Sep 2011	WO
WO 2011124388	Oct 2011	WO
WO 2009137699	Nov 2011	WO
WO 2011137230	Nov 2011	WO
WO 2012009869	Jan 2012	WO
WO 2012027342	Mar 2012	WO
WO 2012027912	Mar 2012	WO
WO 2012027913	Mar 2012	WO
WO 2012027914	Mar 2012	WO
WO 2012027915	Mar 2012	WO
WO 2012027916	Mar 2012	WO
WO 2012051278	Apr 2012	WO
WO 2012054863	Apr 2012	WO
WO 2012100624	Aug 2012	WO
WO 2012107430	Aug 2012	WO
WO 2012127281	Sep 2012	WO
WO 2012156655	Nov 2012	WO
WO 2012160164	Nov 2012	WO
WO 2012172818	Dec 2012	WO
WO 2013014278	Jan 2013	WO
WO 2013025815	Feb 2013	WO
WO 2013029330	Mar 2013	WO
WO 2013054217	Apr 2013	WO
WO 2013063848	May 2013	WO
WO 2013066775	May 2013	WO
WO 2013078214	May 2013	WO
WO 2013089712	Jun 2013	WO
WO 2013102855	Jul 2013	WO
WO 2013109517	Jul 2013	WO
WO 2013119978	Aug 2013	WO
WO 2013123022	Aug 2013	WO
WO 2013126049	Aug 2013	WO
WO 2013141870	Sep 2013	WO
WO 2013150025	Oct 2013	WO
WO 2013175076	Nov 2013	WO
WO 2013182218	Dec 2013	WO
WO 2014012802	Jan 2014	WO
WO 2014151930	Sep 2014	WO
WO 2014009876	Dec 2014	WO
WO 2015023515	Feb 2015	WO
WO 2015091070	Jun 2015	WO
WO 2015197462	Dec 2015	WO

Non-Patent Literature Citations (7)

Entry
Cinterion PHS8-P 3G HSPA+ http://www.cinterion.com/tl_files/cinterion/downloads/cinterion_datasheet_PHS8_web.pdf.
Huntleigh Healthcare, “Negative Pressure Positive Outcomes” WoundASSIST TNP Console and Canister Brochure, in 6 pages, 2007.
International Search Report and Written Opinion, re International Application No. PCT/US2011/055937, dated Dec. 23, 2011.
International Preliminary Report on Patentability, re International Application No. PCT/US2011/055937, dated Apr. 25, 2013.
Japanese Office Action (Notice of Rejection), re JP Application No. 2013-533968, dated Jul. 14, 2015.
“Vivano—Product application description,” Hartmann Vivano, http://www.vivanosystem.info/20809.php, accessed Feb. 28, 2013.
Oddsson et al., “A Robotic Home Telehealth Platform System for Treatment Adherence, Social Assistance and Companionship—an Overview”, 31st Annual International Conference of the IEEE Sep. 2009, pp. 6437-6440.

Related Publications (1)

	Number	Date	Country
	20170065837 A1	Mar 2017	US

Provisional Applications (4)

Number	Date	Country
61392154	Oct 2010	US
61405405	Oct 2010	US
61405757	Oct 2010	US
61483445	May 2011	US

Continuations (1)

	Number	Date	Country
Parent	13271870	Oct 2011	US
Child	15357883		US

Medical device

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

US

CPC

International Classifications

Disclaimer

Term Extension

Abstract