Patent Grant
11565134
This description relates to a medical device.
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 internet with the medical device. In particular, it is important that a medical device be capable of providing effective treatment and a positive patient experience.
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.
Implementations may include one or more of the following features. For example, the medical device includes a wireless communication module operable to receive the activation code over a wireless communication link. The wireless communication link is a Bluetooth or cellular communication link. The medical device is configured to receive the activation code from an enabling device configured to activate a limited number of medical devices and to not activate more than the limited number of medical devices. The one or more processing devices being configured to receive the activation code includes the one or more processing devices being configured to access the activation code from a removable medium. The activation code includes authorization information indicating a number of treatments authorized using the medical device.
In another general aspect, an enabling device includes: a communication module operable to wirelessly transmit one or more activation codes to a medical device, the one or more activation codes being capable of activating the medical device; one or more data storage devices storing authorization information indicating a number of authorized activations of medical devices that the enabling device is authorized to perform; one or more processing devices configured to: receive user input indicating that a medical device should be activated; determine, based on the authorization information, whether activation of the medical device is authorized; if the determination indicates that the activation of the medical device is authorized: control the wireless communication module to transmit the one or more activation codes, and update the authorization information to decrease the number of authorized activations remaining for the enabling device; if the determination indicates that the treatment is not authorized, control the treatment module such that the one or more activation codes are not transmitted.
Implementations may include one or more of the following features. For example, the enabling device is associated with an inventory of medical devices, and the number of authorized activations of medical devices is based on the associated inventory. The communication module is further configured to receive, over a network, second authorization information altering the number of authorized activations the enabling device is authorized to perform, and the one or more processors are further configured to update the information indicating the number of authorized activations to alter the number of authorized activations by the additional number indicated by the second authorization information. The communication module is further configured to receive, over a network, second authorization information indicating an additional number of authorized activations the enabling device is authorized to perform, and the one or more processors are further configured to update the information indicating the number of authorized activations to increase the number of authorized activations by the additional number indicated by the second authorization information.
In 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; one or more data storage devices; 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.
Implementations may include one or more of the following features. For example, the enabling device is configured to activate the medical device by transmitting an activation code over a wireless communication link between the enabling device and the medical device, and the medical device is configured to allow treatments using the treatment module in response to receiving the activation code.
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.
In another general aspect, a medical device includes: a treatment module operable 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 primary or rechargeable battery configured to supply power to the medical device; a color display configured to display information to a user of the medical device; a wireless communication module; one or more data storage devices; one or more processing devices configured to: disallow treatment using the treatment module until an activation code is received; receive an activation code received by the wireless communication module over a wireless communication link; in response to receiving the activation code, permit treatment to be applied using the treatment module; store on the one or more data storage devices authorization information indicating a number of authorized treatments remaining for the medical device; receive user input indicating a treatment should be initiated; determine whether the treatment is authorized; if the determination indicates that the treatment is authorized, control the treatment module to apply the treatment and update the authorization information to decrease the number of authorized treatments remaining for the medical device; if the determination indicates that the treatment is not authorized, control the treatment module such that the treatment is not applied; record, on the one or more storage devices, compliance information indicating dates during which treatment was performed using the treatment module; cause the wireless communication module to transmit the recorded compliance information over the wireless communication link; and display on the color display a calendar indicating days during which treatment was performed and days during which treatment was not performed.
In another general aspect, a medical device includes: a treatment module operable 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 primary or rechargeable battery configured to supply power to the medical device; a color display configured to display information to a user of the medical device; one or more data storage devices including a removable memory card and a non-removable storage device; one or more processing devices configured to cause the medical device to: access from the removable memory card information indicating a number of authorized treatments for the medical device; based on the accessed information, store authorization information indicating the number of authorized treatments for the medical device on the non-removable storage; receive user input indicating a treatment should be initiated; determine, based on the authorization information, whether the treatment is authorized; if the determination indicates that the treatment is authorized, control the treatment module to apply the treatment and update the authorization information to decrease the number of authorized treatments remaining for the medical device; if the determination indicates that the treatment is not authorized, control the treatment module such that the treatment is not applied; record on the one or more storage devices compliance information indicating dates during which treatment was performed using the treatment module; automatically display on the color display, in response to the medical device being powered on, a calendar indicating days during which treatment was performed and days during which treatment was not performed; access, from a second removable memory card, second authorization information indicating a second number of authorized treatments using the medical device; and based on the second authorization information, increase the number of authorized treatments remaining for the medical device stored on the one or more storage devices.
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 above aspects may include one or more of the following features. For example, the activation code includes the authorization information. The wireless communication link is a Bluetooth or cellular communication link. The one or more storage devices include a removable memory card; and the one or more processing devices configured to: record the compliance information to the removable memory card; and access an activation code stored on the removable memory card or another memory card.
The removable memory card and the second removable memory cards are Secure Digital memory cards. The one or more processing devices being configured to record on the one or more storage devices compliance information indicating dates during which treatment was performed using the treatment module includes the one or more processing devices being configured to record, on the removable memory card and on the non-removable storage, compliance information indicating dates during which treatment was performed using the treatment module. The one or more processing devices being configured to indicate on the display days during which treatment was performed and days in which treatment was not performed 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 performed and days in which treatment was not performed. The one or more processing devices are further configured to receive an authorization code indicating a number of treatments that are authorized for the medical device and update the authorization information such that the number of treatments indicated by authorization code are added. The one or more processing devices are configured to determine whether the treatment is authorized by determining if the authorization information indicates that at least one treatment is authorized for the medical device. The one or more processing devices are further configured to: access an identifier from the one or more storage devices; and cause the compliance information and the accessed identifier to be transmitted to a server system that is configured to receive the compliance information and the identifier.
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 one or more processing devices are further configured to: identify a treatment regimen that identifies a prescribed use of the medical device; compare the information about a recorded use to the prescribed use of the medical device; and generate information indicating the degree that the recorded use matches the prescribed use.
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.
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. For example, the compliance information can indicate days and/or times that a patient has performed treatments using the medical device. The compliance information can also indicate the degree to which a patient has complied with a particular treatment regimen. The compliance information can be collected at a server system, and the information can be accessed by multiple parties. The level of access that a party receives can be limited based on the party's relationship to the patient. The server system can receive, store, and provide access to compliance information from multiple medical devices operated by different patients. The medical device can also record errors in the operation of the medical device, send the errors to a server system, and receive service information to address the errors.
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 identity 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. Compliance information may be collected and sent to a server system. Security measures can be implemented so that insurance companies, physicians, and caretakers can receive access to the compliance information based on their relationship to the patient. The server system may receive information about errors that occur during operation of the medical device, and the server system may send service information to address the errors.
Some implementations of the medical device may provide the following additional advantages. Medical devices can be maintained in a deactivated state until activated in a controlled process, reducing incentive for theft and misuse. The ability of devices to activate medical devices and authorize medical treatments can be controlled. The number of medical device activations that can be performed by a device can be limited to the inventory associated with the device.
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
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 ischemic 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, tendinosis, 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
By executing the instructions stored on the storage device 52, 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/cm2 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.
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.
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
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
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
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
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 61O 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
Referring to
Referring to
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
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
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
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
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
The medical device 10 can record use of the medical device 10, for example, by recording the date, time, and duration that treatment occurs using the medical device 10. The recorded use of the medical device 10 can be collected as compliance information 1010. For example, the medical device 10 can collect information about multiple treatments performed or multiple aspects of treatment.
As described above, in some implementations, the medical device 10 may receive information about the treatment regimen for the patient. 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. The compliance information 1010 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.
To distinguish the medical device 10 from other medical devices 10, the medical device 10 may store a device identifier 1012 that enables the medical device 10 to be identified. For example, the device identifier 1012 may uniquely identify a particular medical device 10.
The medical device 10 can send the compliance information 1010 to the server system 1002. Compliance information 1010 can be sent automatically, for example, after a predefined number of treatments are performed, after a particular amount of time has elapsed, or after a treatment regimen has been completed. The medical device 10 may send the compliance information 1010 over the network 1008. Additionally, or alternatively, medical device 10 may send the compliance information 1010 over a cellular network 1009. The medical device 10 can also send the device identifier 1012 to the server system 1002 with the compliance information 1010, enabling the server system 1002 to associate the compliance information 1010 with the particular device. In addition to a device identifier, or alternatively, the medical device 10 may send a patient identifier with the compliance information 1010.
The server system 1002 can be configured to receive the compliance information 1010 and the device identifier 1012 from the medical device 10. The server system 1002 can determine a patient identifier using the device identifier 1012. For example, the server system 1002 may store records that associate device identifiers 1012 for multiple medical devices 10 with patient identifiers. The server system 1002 can compare the received device identifier 1012 to stored device identifiers to determine a patient identifier and identify the patient that uses the medical device 10. The server system can store the compliance information 1010 in association with the determined patient identifier.
The server system 1002 can be configured to receive compliance information from multiple medical devices 10 operated by different patients. For example, the server system 1002 may include a compliance database of many patients and information about the prescriptions and medical devices 10 that correspond to each patient. The server system 1002 can receive and record compliance information from each or any of patients or medical devices 10 described in the compliance database. The server system 1002 can add information about additional patients and medical devices 10 to the compliance database records.
The server system 1002 can provide access to the stored compliance information 1010 to one or more parties that have a relationship with the patient. For example, an insurance company for the patient may use the compliance information 1010 to determine whether the patient is using the medical device 10 that the insurance company paid for. A physician or a caretaker of the patient may use compliance information 1010 to determine if the patient is complying with a treatment regimen that has been prescribed. To obtain compliance information 1010 for the patient, a third-party system 1004 may submit an inquiry requesting the compliance information 1010 to the server system 1002. For example, the inquiry 1016 may include one or more patient identifiers to identify one or more patients. The server system 1002 can provide access to the compliance information 1010 for one or more users in response to receiving the inquiry from the third-party system 1004.
Because the server system 1002 can store compliance information about multiple patients and multiple medical devices 10, the server system 1002 can provide aggregate information about multiple patients and medical devices 10. For example, the server system 1002 may provide an insurance provider with a summary of the treatments performed for all patients covered by the insurance provider. As another example, a physician may receive compliance information for each of his patients from the server system 1002, without being required to interface with each of the prescribed medical devices 10 individually.
Summaries, reports, graphs, and comparisons can be provided based on compliance data for multiple patients, including, for example, information about a set or subset of patients. For example, the compliance of patients that have a particular health condition can be provided.
Access to the compliance information 1010 can be limited based on the relationship of the third party to the patient. The server system 1002 can store records that associate various third parties with various patients. The third party system 1004 may be required to be authenticated or comply with other security measures before access to compliance information 1010 is provided. Access to compliance information 1010 can also be limited by restricting the quantity or detail of information available. For example, one third party may receive more detailed compliance information 1010 than a different third party may receive for the same patient. For example, an insurance company for the patient may be provided access only to the number of treatments performed with the medical device 10, but the physician of the patient may be provided access to the particular dates and times that treatments occurred in addition to the total number of treatments.
The medical device 10 can also detect and record information about errors of the medical device 10. During treatment or during other operation of the medical device 10, one or more errors may occur. The medical device can store information about the errors as error information 1014, and can send the error information 1014 to the server system 1002 with the device identifier 1012. In one implementation, error information 1014 can be sent soon after the error is detected. Examples of errors that can be detected, and for which information can be recorded and sent, include a gel error indicating that there is insufficient ultrasound conductive gel on a transducer, a battery error that indicates that remaining power of the battery is low, and a connectivity error that indicates that a wire to a transducer is disconnected or broken.
The server system 1002 can be configured to receive the error information 1014 and the device identifier 1012. The server system 1002 can store the received error information 1014 and can associate error information 1014 with the device identifier 1012. The received error information 1014 may quickly and accurately indicate which medical devices 10 and which types of medical devices 10 experience errors and at what frequency errors occur.
The received error information may also enable the server system 1002 to provide information to the medical device 10 to address the errors. For example, the server system 1002 may use error information 1014 to determine a possible cause of an error. The server system 1002 may select service information 1018 that addresses the error. For example, the server system 1002 may select information to store on the medical device 10, which may include information to restore or replace outdated or incorrect information. The server system 1002 may select control instructions to be executed on the medical device 10, for example, control instructions to clear an error or to reinitialize the medical device 10. The server system 1002 can send the selected service information 1018 that addresses one or more errors to the medical device 10. The service information 1018 can include, for example, software or firmware updates, instructions to the user of the medical device 10, instructions to trained service personnel, and/or control instructions to alter the functioning of the medical device 10 and modules coupled to the medical device 10.
The medical device 10 can send information including one or more messages 304 to the medical device 10. The messages 304 may be stored on the medical device 10 and displayed to the patient during treatment. The messages 304 can include updated information or additional information to add to the variety of messages 304 already stored on the medical device 10. In addition, one or more messages 304 can be provided to instruct the patient how to correct an error of the medical device 10, or to inform the patient that an error has been corrected.
Referring to
A driver circuit is controlled to produce ultrasound with therapeutic properties (1102).
Compliance information is collected (1104). Collecting compliance information can include recording information about use of the medical device, for example recording the number of treatments that are performed. Compliance information can include a number of treatments provided by the medical device, a date and time that a treatment was provided by the medical device, and/or a duration that a treatment was provided by the medical device. Information about multiple uses or treatments with the medical device can be collected.
A treatment regimen that identifies a prescribed use of the medical device can be identified. For example, information about a treatment regimen may be entered on the medical device or received from a network, which may include a cellular network. The information about the recorded use of the medical device 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.
A device identifier can be accessed (1106). The device identifier can be stored on the medical device. The compliance information can be sent (1108). The accessed device identifier can be sent with the compliance information. For example, the compliance information can be sent to a server system configured to receive the compliance information. Compliance information can be sent automatically after a predetermined number of treatments have been performed. Compliance information may be sent using a wireless module, and the wireless module can include a cellular transceiver. For example, compliance information may be sent to a server system over a cellular network using the cellular transceiver. The medical device can include a SIM card that associates a particular telephone number with the medical device.
One or more errors of the medical device can be detected. Information about the detected errors can be sent with the accessed device identifier to a server system. Service information to address the detected errors can be received from the server system.
Referring to
Compliance information can be received (1202). For example, compliance information can be received over a network or cellular network from one or more medical devices. Compliance information for multiple medical devices operated by different patients can be received. For example, the server system may be configured to receive compliance information from each of a plurality of patients, and each patient can be associated with at least one of a plurality of medical devices. The compliance information can include a number of treatments provided by a medical device, a date and time that a treatment was provided by the medical device, and/or a duration that a treatment was provided by the medical device. Compliance information can be received for multiple medical devices operated by different patients.
A device identifier can be received (1204). The device identifier can be received with the compliance information. A patient identifier can be determined (1206). For example, the received device identifier can be used to determine the patient identifier. The server system can store records that associate device identifiers with one or more patient identifiers. The recorded device identifiers can be compared to the received device identifier to determine a recorded device identifier that matches the received device identifier.
The compliance information can be stored (1208). The compliance information can be stored in association with the patient identifier that was determined to correspond to the compliance information. For example, the server system may be configured to store compliance information for each of a plurality of patients, and each patient can be associated with at least one of a plurality of medical devices. Compliance information for each patient can be stored in association with one or more device identifiers and/or patient identifiers.
Access to the compliance information can be provided (1210). For example, access may be provided to one or more users of the server system. Users may submit an inquiry to the server system, and the inquiry can be associated with a patient identifier. Users can include, for example, one or more of a representative of an insurance provider of the patient, a physician of the patient, and a caretaker of the patient. Access to the compliance information for a particular patient can be provided to the users in response to receiving the inquiry that is associated with the patient identifier for the particular patient. Access to the compliance information can be limited based on the relationship of the user to the patient.
For example, a physician of the patient may receive access to only a portion of the compliance information, such as only the number of times the medical device was used. A physician, on the other hand, may receive access to more detailed compliance information, such as the date, time, and duration that the medical device was used.
Because compliance information for multiple patients and multiple medical devices can be stored, access to compliance information for multiple patients and multiple medical devices can be provided. For example, compliance information can be provided to a third party for treatment performed by multiple medical devices operated by multiple patients.
Users that can receive access to the compliance information can include, for example, one or more caretakers, physicians, and representatives of insurance providers for any of the multiple patients whose compliance information is stored. Access can be provided to compliance information for each of a plurality of patients, where each patient is associated with at least one of a plurality of medical devices. Access to the compliance information for a particular patient can be provided to the users in response to receiving the inquiry that is associated with the patient identifier for the particular patient.
Information about one or more errors of the medical device can be received. Based on the information about the errors, service information to address the errors can be selected and transmitted to the medical device. One or more messages for the patient can be transmitted to the medical device.
Referring to
Records for the patient and the dispensed medical device can be entered into a database 1314 (1306). For example, the database 1314 may store a patient record 1310 that associates a particular medical device or treatment with a particular patient, in the example, a patient named “John Smith.” The database 1314 may also store a prescription record 1312 that indicates the number of treatments that can be purchased for the patient. The number of treatments indicated in a prescription record 1312 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 1314 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 1318, 1320, a server system 1322, or other systems. For example, the server system 1322 may use the patient record 1310 to match payment to a particular medical device or patient. The records stored in the database 1314 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
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 (
Referring to
As illustrated in
Advantageously, a medical device can be designed for use within only a specific geographical area, for example, a country or region as illustrated in
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
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
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
In use, the patient turns the device 10 on at step 1960, the device performs a self-test of the clock and configuration at step 1962, the patient, for example, scans his or her index finger over the fingerprint sensor 1852, and the device confirms the patient identity at step 1964. If the patient is the authorized user, the geographical location of the device is checked at step 1966. If the patient is not the authorized user, an authorization alarm is delivered at step 1968 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 1970. If the device 10 is not within its authorized geographical location, an authorization alarm is delivered at step 1968 and treatment will not commence.
At steps 1972, 1974 and 1976, the device 10 monitors the time of use, allowing up to 20 minutes of treatment to be delivered before ending treatment.
Referring to
Each medical device 10 can be provided to a distributor or physician in a disabled or deactivated state. For example, the medical device 10 can be provided in a state in which no treatments are authorized. Additionally, the medical device 10 can be provided in a state in which treatments cannot be purchased or authorized, until the medical device 10 is activated and thus made operative by an enabling device. Because the medical devices 10 are shipped and stored in inventory in an inoperative state, the potential for unauthorized use is very low.
The enabling device 2010 includes the capability to activate medical devices 10. For example, the enabling device 2010 can include an activation module including a wireless or wired communication system to transmit activation information. The server 2020, however, can limit the enabling device 2010. For example, the server 2020 can authorize the enabling device 2010 to activate only a limited number of medical devices 10. The total number of medical device activations that the enabling device can be performed can be limited (e.g., no more than 10 activations, until further authorization is received). Additionally, or alternatively, the number of activations that can be performed over a particular period of time can be limited (e.g., no more than 10 activations per month). As described in further detail below, the server 2020 can limit the number of medical device activations that the enabling device 2010 can perform so that, at any given time, the enabling device 2010 is authorized to perform a number of medical device activations no greater than the number of medical devices in a particular inventory 2013 of a particular sales representative 2012. The enabling device 2010 is associated with the sales representative 2012, and a unique identifier for the enabling device 2010 or for the representative 2012 associates the enabling device 2010 with the inventory 2013 of the representative 2012.
The server 2020 tracks the inventories of multiple representatives. The server 2020 can identify changes in inventories using information from reliable sources, for example, information that is verifiable or outside the control of the representatives. For example, the server 2020 receives information from manufacturers or distributors of medical devices about shipments of products to the representatives.
Based on the inventory 2013 for the representative 2012, the server 2020 adjusts the ability of the enabling device 2010 to activate medical devices 10. For example, the server 2020 authorizes the enabling device 2010 to activate as many medical devices 10 as are in the official inventory 2013 for the representative 2012. For example, when the medical devices 10 are shipped to the representative 2012, the server 2020 receives information about the shipment 2014 from the manufacturer or distributor. In response to determining that the inventory 2013 for the representative 2012 has increased, the server 2020 transmits to the representative's enabling device 2010 an authorization code 2022 permitting a number of medical device 10 activations corresponding to the size of the shipment 2014. If twenty medical devices 10 are shipped to the representative 2012, the server 2020 sends an authorization code 2022 permitting the enabling device 2010 to activate up to twenty medical devices 10.
When the medical device 10 is purchased or dispensed to a patient, the sales representative 2012 can activate the medical device 10 using the enabling device 2010. The enabling device 2010 communicates with the medical device 10 over a wired link or a wireless link, such as Bluetooth. For example, the enabling device 2010 supplies an activation code 2024 to the medical device 10 that unlocks the functionality of the medical device 10. The enabling device 2010 can also supply an authorization code 2026 that authorizes a particular number of treatments to be performed with the medical device 10. The activation code 2024 and the authorization code 2026 can be combined in a single message or code. After the medical device 10 receives the activation code 2024, the medical device 10 determines whether the activation code 2024 is valid to activate the medical device 10 and/or one or more of its treatment modules. In response to determining that the activation code 2024 is valid, the medical device 10 may send an activation confirmation message (not shown) to the enabling device 2010 to indicate that activation was successful.
After the enabling device 2010 activates the medical device 10, the enabling device 2010 automatically decreases the number of activations that the enabling device 2010 can provide. For example, the number of activations permitted is decreased by one, from twenty to nineteen. The number of activations can be decreased in response to receiving the activation confirmation message from the medical device 10 so that the number is decreased only after successful activation attempts.
Once the activations allowed by the authorization code 2022 are exhausted, the enabling device 2010 is restricted from activating additional medical devices 10. The representative 2012 is thus restricted from activating medical devices 10 beyond those legitimately in the representative's inventory 2013. When a new shipment of medical devices 10 is sent to the representative 2012, the server 2020 transmits a new authorization code that permits the enabling device 2010 to activate the medical devices 10 in the new shipment.
In some implementations, the server 2020 can also communicate with the enabling device 2010 to reduce the number of activations allowed, for example, if the inventory 2013 of the representative 2012 decreases due to returning unused medical devices to the manufacturer. Accordingly, the number of activations that can be provided by the enabling device 2010 is maintained according to the current inventory 2013 of the representative 2012.
In some implementations, the enabling device 2010 sends a message 2028 to the server 2020 that indicates when an activation of a medical device 10 has occurred, allowing the server 2020 to monitor activations. The remaining number of activations currently allowed by the enabling device 2010 can also be included in the message 2028.
In some implementations, after the medical device 10 expends all of the treatments authorized by the authorization code 2026, a second authorization code can be received to permit additional treatments to be performed. As described above, the second authorization code can be received in response to payment by a patient or a patient's insurance provider. The second authorization code can be received, for example, over the network 2030, from the enabling device 2010, or from a removable medium.
By contrast, in some implementations, the medical device 10 returns to an inoperative, deactivated state after the treatments authorized by the authorization code 2026 are exhausted. Thus the medical device 10 must be activated with an activation code from the enabling device 2010 before further treatments are permitted.
The medical device 10 can be configured to transmit information indicating usage of the medical device 10, including compliance with a treatment regimen, to the enabling device 2010 over the same communication link used to receive the activation code. Thus, as part of the exchange, the medical device 10 receives a new activation code from the enabling device 2010, and the enabling device 2010 receives usage information from the medical device 10. The enabling device 2010 can then transmit the usage information to the server 2020, with identifiers to identify, for example, the patient, prescription, and medical device 10 associated with the usage information.
In some implementations, rather than being enabled by a transmission of an activation code from an enabling device, a medical device can be activated by a code accessed from a removable medium, such as an SD memory card.
Referring to
The enabling device 2010 can be configured to require an authorization code before performing each activation. Each time a medical device is activated, a new authorization code is required. The server 2020 provides authorization codes over the network 2030. The server 2020 can provide an authorization code allowing the activation of a single medical device based on a particular prescription for the medical device. If no prescription is submitted to the server 2020, the server 2020 does not send an authorization code to the enabling device 2010, and the enabling device 2010 is unable to activate medical devices.
For example, after a physician issues a prescription for treatment using the medical device 10, the prescription can be entered on the enabling device 2010, which transmits identifying information 2115 identifying the prescription to the server 2020. For example, the enabling device 2010 transmits a representative identifier and a prescription identifier in the identifying information 2115. The identifying information 2115 may be additionally or alternatively transmitted by the medical device 10, a physician's computer system, an insurance company computer system, or other system. In some implementations, the identifying information 2115 can identify the prescription, the patient receiving the prescription, the doctor or office issuing the prescription, an insurance company for the patient, an insurance policy for the patient, the representative 2012, the medical device 10 to be activated, and/or the enabling device 2010, and the information can be stored by the server 2020.
The server 2020 verifies the prescription information, for example, by comparing the prescription information to other prescription records or by verifying an authentication signature in the received information. The server 2020 can also communicate with another server system 2110, such as a server for an insurance company of the patient, to determine whether payment has been authorized for the prescription.
If the prescription is determined to be valid, and/or if payment has been authorized, the server 2020 transmits an authorization code 2120 to the enabling device 2010. The authorization code 2120 permits the enabling device 2010 to activate a single medical device 10 for the patient and prescription that were verified. The enabling device 2010 transmits an activation code 2124 to the medical device 10. The enabling device 2010 also transmits an authorization code 2126 to the medical device 10, permitting the medical device 10 to apply the number of treatments indicated in the prescription, or the number of treatments for which payment was authorized by the insurance company.
The enabling device 2010 can transmit information to the server 2020 indicating that the activation of the medical device 10 was performed. Based on the initial identifying information 2115 and/or information received subsequent to the activation, the server 2020 can record the transaction identifying, for example, the patient, the prescription, the medical device 10, the representative 2012, the enabling device 2010, and the authorization code 2120 associated with the activation.
When no prescription is submitted to the server 2020, the server 2020 does not send an authorization code to the enabling device 2010, and the enabling device 2010 cannot activate the medical device 10. Similarly, if the prescription information sent to the server 2020 is invalid or is not verifiable, or if payment is refused by an insurance provider, the server 2020 can withhold the authorization code, disallowing the activation of the medical device 10.
In a similar manner, the system 2000 can be used to track and/or evaluate passes for unpaid treatments. In some implementations, the enabling device 2010 can be authorized to provide a limited number of complimentary medical device activations or treatment authorizations for previously activated medical devices 10. Each time a pass is provided, the enabling device 2010 transmits information to the server 2020 identifying, for example, the physician, representative 2012, medical device 10, and insurance provider associated with the pass. The information may also identify the patient and prescription associated with the pass. The server 2020 can thus maintain a database tracking the issuance of complimentary passes for different representatives 2012, physicians, and insurance providers.
In some implementations, the enabling device 2010 can be limited to providing passes when the server 2020 provides authorization for each pass individually. For example, the server 2020 can evaluate the circumstances of a particular patient and a particular prescription to determine whether the patient qualifies for complimentary or reduced cost treatment.
The enabling device 2010 transmits a request to the server 2020 that indicates the circumstances of the desired pass. The request can indicate, for example, the medical condition to be treated, the identity of the patient, an associated prescription, the patient's income or other financial status, whether and to what degree treatment is covered by insurance, and what insurance provider covers the treatment. The request can also identify the physician, representative 2012, enabling device 2010, and medical device 10 associated with the request.
The server 2020 receives and evaluates the request for the pass. For example, the server 2020 uses the information in the request to evaluate the patient's medical needs, economic circumstances, and other circumstances to determine whether to authorize the activation and treatment authorization of a medical device for the patient. If the patient's circumstances meet the criteria for complimentary treatment, the server 2020 sends an authorization code to the enabling device 2010 permitting the enabling device 2010 to provide a pass for the particular patient. If the patient does not qualify for a pass, the server system 2020 withholds the authorization code necessary to activate a medical device or authorize additional treatments for the medical device. The server 2020 can record each request for a pass, each pass granted, and activations and treatments that occur based on the pass.
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.
This application is a continuation of U.S. application Ser. No. 15/482,449, filed on Apr. 7, 2017, which is a continuation of U.S. application Ser. No. 15/357,883, filed on Nov. 21, 2016, now U.S. Pat. No. 10,086,216, issued on Oct. 2, 2018, which is a continuation of U.S. application Ser. No. 13/271,870, filed on Oct. 12, 2011, now U.S. Pat. No. 9,526,920, issued on Dec. 27, 2016, which claims the benefit of U.S. Provisional Application No. 61/392,154, filed Oct. 12, 2010, U.S. Provisional Application No. 61/405,405, filed Oct. 21, 2010, U.S. Provisional Application No. 61/405,757, filed Oct. 22, 2010, and U.S. Provisional Application No. 61/483,445, filed May 6, 2011, each of which is incorporated herein in its entirety for all purposes.
| Number | Name | Date | Kind |
|---|---|---|---|
| 695270 | Beringer | Mar 1902 | A |
| 3194239 | Sullivan et al. | 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 et al. | 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 |
| 5590658 | Chiang et al. | Jan 1997 | 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 |
| 5960403 | Brown | Sep 1999 | A |
| 5989234 | Valerio et al. | Nov 1999 | A |
| 6018289 | Sekura et al. | Jan 2000 | A |
| 6055506 | Frasca et al. | Apr 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 |
| 6336900 | Alleckson et al. | Jan 2002 | B1 |
| 6353445 | Babula et al. | Mar 2002 | B1 |
| 6375614 | Braun et al. | Apr 2002 | B1 |
| 6385622 | Bouve et al. | May 2002 | B2 |
| 6387092 | Burnside et al. | May 2002 | B1 |
| 6406426 | Reuss et al. | Jun 2002 | B1 |
| 6413213 | Essenpreis et al. | Jul 2002 | B1 |
| 6434572 | Derzay et al. | Aug 2002 | B2 |
| 6460041 | Lloyd | Oct 2002 | B2 |
| 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 |
| 6640145 | Hoffberg et al. | Oct 2003 | B2 |
| 6640246 | Gary et al. | Oct 2003 | B1 |
| 6675131 | Hahn | Jan 2004 | B2 |
| 6681003 | Linder et al. | Jan 2004 | B2 |
| 6723046 | Lichtenstein et al. | Apr 2004 | B2 |
| 6738052 | Manke et al. | May 2004 | B1 |
| 6747556 | Medema et al. | Jun 2004 | B2 |
| 6766218 | Rosenblum | Jul 2004 | B2 |
| 6779024 | Delahuerga | Aug 2004 | B2 |
| 6782285 | Birkenbach et al. | Aug 2004 | B2 |
| 6792306 | Henley et al. | Sep 2004 | B2 |
| 6811533 | Lebel et al. | Nov 2004 | B2 |
| 6868528 | Roberts | Mar 2005 | B2 |
| 6871211 | Labounty et al. | Mar 2005 | B2 |
| 6909974 | Yung et al. | Jun 2005 | B2 |
| 6912481 | Breunissen et al. | Jun 2005 | B2 |
| 6961731 | Holbrook | Nov 2005 | B2 |
| 7004915 | Boynton et al. | Feb 2006 | B2 |
| 7022113 | Lockwood et al. | Apr 2006 | B2 |
| 7048687 | Reuss et al. | May 2006 | B1 |
| 7051012 | Cole et al. | May 2006 | B2 |
| 7066883 | Schmidt et al. | Jun 2006 | B2 |
| 7103578 | Beck et al. | Sep 2006 | B2 |
| 7108683 | Zamierowski | Sep 2006 | B2 |
| 7120488 | Nova et al. | Oct 2006 | B2 |
| 7128735 | Weston | Oct 2006 | B2 |
| 7133869 | Bryan et al. | Nov 2006 | B2 |
| 7167858 | Naeymi-Rad et al. | Jan 2007 | B2 |
| 7212829 | Lau et al. | May 2007 | B1 |
| 7264591 | Brown | Sep 2007 | B2 |
| 7273483 | Wiener et al. | Sep 2007 | B2 |
| 7304573 | Postma | Dec 2007 | B2 |
| 7311665 | Hawthorne et al. | Dec 2007 | B2 |
| 7333002 | Bixler et al. | Feb 2008 | B2 |
| D565177 | Locke et al. | Mar 2008 | S |
| 7353179 | Ott et al. | Apr 2008 | B2 |
| 7361184 | Joshi | Apr 2008 | B2 |
| 7364554 | Bolze et al. | Apr 2008 | B2 |
| 7384267 | Franks et al. | Jun 2008 | B1 |
| 7395214 | Shillingburg | Jul 2008 | B2 |
| 7430598 | Raden et al. | Sep 2008 | B2 |
| D581042 | Randolph et al. | Nov 2008 | S |
| D581522 | Randolph et al. | Nov 2008 | S |
| 7448265 | Smyser et al. | Nov 2008 | B2 |
| 7451002 | Choubey | Nov 2008 | B2 |
| 7457804 | Uber et al. | Nov 2008 | B2 |
| 7460872 | Millard et al. | Dec 2008 | B2 |
| 7492278 | Zigmond et al. | Feb 2009 | B2 |
| 7505815 | Lee et al. | Mar 2009 | B2 |
| D590934 | Randolph et al. | Apr 2009 | S |
| 7534240 | Johnson | May 2009 | B1 |
| 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 |
| 7627334 | Cohen et al. | Dec 2009 | B2 |
| 7639120 | Sekura | Dec 2009 | B2 |
| 7649449 | Fenske et al. | Jan 2010 | B2 |
| 7670323 | Hunt et al. | Mar 2010 | B2 |
| 7671733 | McNeal et al. | Mar 2010 | B2 |
| 7684999 | Brown | Mar 2010 | B2 |
| 7699823 | Haggstrom et al. | Apr 2010 | B2 |
| 7723560 | Lockwood et al. | May 2010 | B2 |
| 7734764 | Weiner et al. | Jun 2010 | B2 |
| 7749164 | Davis | Jul 2010 | B2 |
| 7753894 | Blott et al. | Jul 2010 | B2 |
| 7770855 | Locke et al. | Aug 2010 | B2 |
| 7776028 | Miller et al. | Aug 2010 | B2 |
| 7779153 | Van Den Heuvel et al. | Aug 2010 | B2 |
| 7785277 | Babaev et al. | Aug 2010 | B2 |
| 7789828 | Clapp | Sep 2010 | B2 |
| D625801 | Pidgeon et al. | Oct 2010 | S |
| 7827148 | Mori et al. | Nov 2010 | B2 |
| 7846141 | Weston | Dec 2010 | B2 |
| 7857806 | Karpowicz et al. | Dec 2010 | B2 |
| 7865375 | Lancaster et al. | Jan 2011 | B2 |
| 7889069 | Fifolt et al. | Feb 2011 | B2 |
| 7890887 | Linardos et al. | Feb 2011 | B1 |
| 7912823 | Ferrari et al. | Mar 2011 | B2 |
| 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 |
| 7976519 | Bubb et al. | Jul 2011 | B2 |
| 7981098 | Boehringer et al. | Jul 2011 | B2 |
| D644250 | Barber et al. | Aug 2011 | S |
| 7988850 | Roncadi et al. | Aug 2011 | B2 |
| 8007481 | Schuessler et al. | Aug 2011 | B2 |
| 8015443 | Adachi | Sep 2011 | B2 |
| 8015972 | Pirzada | Sep 2011 | B2 |
| 8019618 | Brown | Sep 2011 | B2 |
| 8048046 | Hudspeth et al. | Nov 2011 | B2 |
| 8054950 | Hung et al. | Nov 2011 | B1 |
| 8061360 | Locke et al. | Nov 2011 | B2 |
| 8066243 | Svedman et al. | Nov 2011 | B2 |
| 8094009 | Allen et al. | Jan 2012 | B2 |
| 8096515 | Locke et al. | Jan 2012 | B2 |
| 8100873 | Jaeb et al. | Jan 2012 | B2 |
| 8105295 | Blott et al. | Jan 2012 | B2 |
| 8126735 | Dicks et al. | Feb 2012 | B2 |
| 8130095 | Allen et al. | Mar 2012 | B2 |
| 8131472 | Chow et al. | Mar 2012 | B2 |
| 8180750 | Wilmering et al. | May 2012 | B2 |
| 8190445 | Kuth et al. | May 2012 | B2 |
| 8190448 | Bajars et al. | May 2012 | B2 |
| 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 |
| 8246606 | Stevenson et al. | Aug 2012 | B2 |
| 8246607 | Karpowicz et al. | Aug 2012 | B2 |
| 8249894 | Brown | Aug 2012 | B2 |
| 8255241 | Cafer | Aug 2012 | B2 |
| 8257328 | Augustine et al. | Sep 2012 | B2 |
| 8260630 | Brown | Sep 2012 | B2 |
| 8267918 | Johnson et al. | Sep 2012 | B2 |
| 8280682 | Vock et al. | Oct 2012 | B2 |
| 8284024 | Toleti et al. | Oct 2012 | B2 |
| 8284046 | Allen et al. | Oct 2012 | B2 |
| 8290792 | Sekura | Oct 2012 | B2 |
| 8291337 | Gannin 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 |
| 8317774 | Adahan | Nov 2012 | B2 |
| 8323263 | Wood et al. | Dec 2012 | B2 |
| 8332233 | Ott et al. | Dec 2012 | B2 |
| 8333744 | Hartwell et al. | Dec 2012 | B2 |
| 8334768 | Eaton et al. | Dec 2012 | B2 |
| 8337482 | Wood et al. | Dec 2012 | B2 |
| 8360975 | Schwieterman et al. | Jan 2013 | B1 |
| 8366692 | Weston et al. | 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 |
| 8422377 | Weiner et al. | Apr 2013 | B2 |
| 8424517 | Sutherland et al. | Apr 2013 | B2 |
| 8436871 | Alberte | May 2013 | B2 |
| 8439882 | Kelch | May 2013 | B2 |
| 8444392 | Turner et al. | May 2013 | B2 |
| 8457740 | Osche | Jun 2013 | B2 |
| 8480641 | Jacobs | Jul 2013 | B2 |
| 8494349 | Gordon | Jul 2013 | B2 |
| 8515776 | Schoenberg | Aug 2013 | B2 |
| 8532764 | Duke | Sep 2013 | B2 |
| 8540688 | Eckstein et al. | Sep 2013 | B2 |
| 8545483 | Schwabe et al. | Oct 2013 | B2 |
| 8552880 | Kopp et al. | Oct 2013 | B2 |
| 8554195 | Rao | Oct 2013 | B2 |
| 8558964 | Bedingfield | Oct 2013 | B2 |
| 8560082 | Wei | Oct 2013 | B2 |
| 8577694 | Kanaan | Nov 2013 | B2 |
| 8595553 | Goertler et al. | Nov 2013 | B2 |
| 8604265 | Locke et al. | Dec 2013 | B2 |
| 8617129 | Hartwell | Dec 2013 | B2 |
| 8622981 | Hartwell et al. | Jan 2014 | B2 |
| 8626342 | Williams et al. | Jan 2014 | B2 |
| 8626526 | Lemke et al. | Jan 2014 | B2 |
| 8628258 | Vogt | Jan 2014 | B2 |
| 8632485 | Schlaeper et al. | Jan 2014 | B2 |
| 8641693 | Locke et al. | Feb 2014 | B2 |
| 8652111 | Pratt et al. | Feb 2014 | B2 |
| 8659420 | Salvat et al. | Feb 2014 | B2 |
| 8668677 | Eckstein et al. | Mar 2014 | B2 |
| 8676597 | Buehler et al. | Mar 2014 | B2 |
| 8689008 | Rangadass et al. | Apr 2014 | B2 |
| 8694600 | Gaines et al. | Apr 2014 | B2 |
| 8747376 | Locke et al. | Jun 2014 | B2 |
| 8756078 | Collins et al. | Jun 2014 | B2 |
| 8768441 | De Zwart et al. | Jul 2014 | B2 |
| 8771259 | Karpowicz et al. | Jul 2014 | B2 |
| 8781847 | Simms et al. | Jul 2014 | B2 |
| 8795171 | Adamczyk | Aug 2014 | B2 |
| 8795244 | Randolph et al. | Aug 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 |
| 8862393 | Zhou et al. | Oct 2014 | B2 |
| 8868794 | Masoud et al. | Oct 2014 | B2 |
| 8870812 | Alberti et al. | Oct 2014 | B2 |
| 8874035 | Sherman et al. | Oct 2014 | B2 |
| 8887100 | Cook et al. | Nov 2014 | B1 |
| 8890656 | Pendse | Nov 2014 | B2 |
| 8897198 | Gaines et al. | Nov 2014 | B2 |
| 8902278 | Pinter et al. | Dec 2014 | B2 |
| 8905959 | Basaglia | Dec 2014 | B2 |
| 8905985 | Allen et al. | Dec 2014 | B2 |
| 8909595 | Gandy 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 |
| 8947237 | Margon et al. | Feb 2015 | B2 |
| 8961497 | Ryu et al. | Feb 2015 | B2 |
| 8974429 | Gordon et al. | Mar 2015 | B2 |
| 8978026 | Charlton et al. | Mar 2015 | B2 |
| 8996393 | Sobie | Mar 2015 | B2 |
| 9017286 | Kamen et al. | Apr 2015 | B2 |
| 9019681 | Locke et al. | Apr 2015 | B2 |
| 9023002 | Robinson et al. | May 2015 | B2 |
| 9047648 | Lekutai et al. | Jun 2015 | B1 |
| 9058634 | Buan et al. | Jun 2015 | B2 |
| 9067003 | Buan et al. | Jun 2015 | B2 |
| 9084845 | Adie et al. | Jul 2015 | B2 |
| 9098114 | Potter et al. | Aug 2015 | B2 |
| 9105006 | Williamson | Aug 2015 | B2 |
| 9135398 | Kaib et al. | Sep 2015 | B2 |
| 9215581 | Julian et al. | Dec 2015 | B2 |
| 9268827 | Fernandez | Feb 2016 | B2 |
| 9286443 | Ford et al. | Mar 2016 | B2 |
| 9323893 | Berry et al. | Apr 2016 | B2 |
| 9408954 | Gordon et al. | Aug 2016 | B2 |
| 9436800 | Forrester | Sep 2016 | B2 |
| 9526920 | Tanis et al. | Dec 2016 | B2 |
| 9539373 | Jones et al. | Jan 2017 | B2 |
| 9658066 | Yuen et al. | May 2017 | B2 |
| 9662438 | Kamen et al. | May 2017 | B2 |
| 9741084 | Holmes et al. | Aug 2017 | B2 |
| 9792660 | Cannon et al. | Oct 2017 | B2 |
| 9818164 | Nolte et al. | Nov 2017 | B2 |
| 9878081 | Leiendecker et al. | Jan 2018 | B2 |
| 9990466 | Debusk et al. | Jun 2018 | B2 |
| 10061894 | Sethumadhavan et al. | Aug 2018 | B2 |
| 10173008 | Simpson et al. | Jan 2019 | B2 |
| 10231878 | Hartwell et al. | Mar 2019 | B2 |
| 10639502 | Tanis et al. | May 2020 | 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 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 |
| 20020177757 | Britton | Nov 2002 | A1 |
| 20020184055 | Naghavi et al. | Dec 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 |
| 20030023460 | Ackermann et al. | Jan 2003 | A1 |
| 20030028175 | D'Antonio | Feb 2003 | A1 |
| 20030036683 | Kehr et al. | Feb 2003 | A1 |
| 20030093041 | Risk, Jr. et al. | May 2003 | A1 |
| 20030093181 | Rosenblum | May 2003 | A1 |
| 20030095648 | Kaib et al. | 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 |
| 20030199794 | Sakurai et al. | Oct 2003 | A1 |
| 20030214412 | Ho et al. | Nov 2003 | A1 |
| 20030221687 | Kaigler | Dec 2003 | A1 |
| 20030229518 | Abraham-Fuchs et al. | Dec 2003 | A1 |
| 20030233071 | Gillespie et al. | Dec 2003 | A1 |
| 20030236450 | Kocinski | Dec 2003 | A1 |
| 20040006492 | Watanabe | Jan 2004 | 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 |
| 20040167802 | Takada et al. | Aug 2004 | A1 |
| 20040167804 | Simpson et al. | Aug 2004 | A1 |
| 20040171982 | Danchin | Sep 2004 | A1 |
| 20040172301 | Mihai et al. | Sep 2004 | A1 |
| 20040176983 | Birkett et al. | Sep 2004 | A1 |
| 20040181314 | Zaleski | Sep 2004 | A1 |
| 20040181433 | Blair | Sep 2004 | A1 |
| 20040193449 | Wildman et al. | Sep 2004 | A1 |
| 20040204962 | Howser et al. | Oct 2004 | A1 |
| 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 |
| 20050055225 | Mehl | Mar 2005 | A1 |
| 20050055242 | Bello et al. | Mar 2005 | A1 |
| 20050055244 | Mullan et al. | Mar 2005 | A1 |
| 20050060211 | Xiao et al. | Mar 2005 | A1 |
| 20050065471 | Kuntz | Mar 2005 | A1 |
| 20050065817 | Mihai et al. | Mar 2005 | A1 |
| 20050097200 | Denning et al. | May 2005 | A1 |
| 20050102167 | Kapoor | May 2005 | A1 |
| 20050108046 | Craft | May 2005 | A1 |
| 20050108057 | Cohen et al. | May 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 |
| 20050222873 | Nephin et al. | Oct 2005 | A1 |
| 20050230575 | Zelenski et al. | Oct 2005 | A1 |
| 20050240111 | Chung | Oct 2005 | A1 |
| 20050256447 | Richardson et al. | Nov 2005 | A1 |
| 20050261805 | Mori et al. | Nov 2005 | A1 |
| 20050283382 | Donoghue et al. | Dec 2005 | A1 |
| 20060004604 | White | Jan 2006 | A1 |
| 20060020161 | Mageras et al. | Jan 2006 | A1 |
| 20060029675 | Ginther | Feb 2006 | A1 |
| 20060064323 | Alleckson et al. | Mar 2006 | A1 |
| 20060064491 | Ebert et al. | Mar 2006 | A1 |
| 20060085393 | Modesitt | Apr 2006 | A1 |
| 20060089539 | Miodownik et al. | Apr 2006 | A1 |
| 20060089544 | Williams 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 |
| 20060161460 | Smitherman et al. | Jul 2006 | A1 |
| 20060190130 | Fedor et al. | Aug 2006 | A1 |
| 20060195843 | Hall | Aug 2006 | A1 |
| 20060224051 | Teller et al. | Oct 2006 | A1 |
| 20060229557 | Fathallah et al. | Oct 2006 | A1 |
| 20060246922 | Gasbarro et al. | Nov 2006 | A1 |
| 20060255935 | Scalisi et al. | Nov 2006 | A1 |
| 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 |
| 20070136099 | Neligh et al. | Jun 2007 | A1 |
| 20070138069 | Roncadi et al. | Jun 2007 | A1 |
| 20070156186 | Lee et al. | Jul 2007 | A1 |
| 20070156456 | McGillin et al. | Jul 2007 | A1 |
| 20070173708 | Dobbles et al. | Jul 2007 | A9 |
| 20070179460 | Adahan | Aug 2007 | A1 |
| 20070180904 | Gao | Aug 2007 | A1 |
| 20070197881 | Wolf et al. | Aug 2007 | A1 |
| 20070219480 | Kamen et al. | Sep 2007 | A1 |
| 20070219826 | Brodsky et al. | Sep 2007 | A1 |
| 20070227360 | Atlas et al. | Oct 2007 | A1 |
| 20070227537 | Bemister et al. | Oct 2007 | A1 |
| 20070233022 | Henley et al. | Oct 2007 | A1 |
| 20070250009 | Barak | Oct 2007 | A1 |
| 20070255114 | Ackermann 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 | Al 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 |
| 20080097550 | Dicks et al. | Apr 2008 | A1 |
| 20080119705 | Patel et al. | May 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 |
| 20080177579 | Dehaan | Jul 2008 | A1 |
| 20080180268 | Nissels et al. | Jul 2008 | A1 |
| 20080200868 | Alberti et al. | Aug 2008 | A1 |
| 20080200905 | Heaton et al. | 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 |
| 20080243035 | Crunkilton | 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 |
| 20080312953 | Claus | 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 |
| 20090097623 | Bharadwaj | Apr 2009 | A1 |
| 20090099866 | Newman | Apr 2009 | A1 |
| 20090099867 | Newman | Apr 2009 | A1 |
| 20090101219 | Martini et al. | Apr 2009 | A1 |
| 20090112769 | Dicks 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 |
| 20090136909 | Asukai et al. | May 2009 | A1 |
| 20090144091 | Rago | Jun 2009 | A1 |
| 20090157429 | Lee et al. | Jun 2009 | A1 |
| 20090163774 | Thatha et al. | Jun 2009 | A1 |
| 20090171166 | Amundson et al. | Jul 2009 | A1 |
| 20090171288 | Wheeler | Jul 2009 | A1 |
| 20090171289 | Davis et al. | Jul 2009 | A1 |
| 20090177495 | Abousy et al. | Jul 2009 | A1 |
| 20090182266 | Gordon et al. | Jul 2009 | A1 |
| 20090182594 | Choubey | Jul 2009 | A1 |
| 20090187424 | Grabowski | Jul 2009 | A1 |
| 20090204434 | Breazeale, Jr. | Aug 2009 | A1 |
| 20090204435 | Gale | Aug 2009 | A1 |
| 20090205042 | Zhou et al. | Aug 2009 | A1 |
| 20090206017 | Rohde et al. | Aug 2009 | A1 |
| 20090224889 | Aggarwal et al. | Sep 2009 | A1 |
| 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 |
| 20090281822 | Warner et al. | Nov 2009 | A1 |
| 20090281830 | Mcnames 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 |
| 20100017471 | Brown et al. | Jan 2010 | A1 |
| 20100020021 | Mills et al. | Jan 2010 | A1 |
| 20100022848 | Lee et al. | Jan 2010 | A1 |
| 20100022990 | Karpowicz et al. | Jan 2010 | A1 |
| 20100030302 | Blowers et al. | Feb 2010 | A1 |
| 20100036333 | Schenk, III et al. | Feb 2010 | A1 |
| 20100042021 | Hu et al. | Feb 2010 | A1 |
| 20100042059 | Pratt et al. | Feb 2010 | A1 |
| 20100056875 | Schoenberg et al. | Mar 2010 | A1 |
| 20100069829 | Hutchinson et al. | Mar 2010 | A1 |
| 20100081971 | Allison | Apr 2010 | A1 |
| 20100090004 | Sands et al. | Apr 2010 | A1 |
| 20100106528 | Brackett et al. | Apr 2010 | A1 |
| 20100113908 | Vargas et al. | May 2010 | A1 |
| 20100114026 | Karratt et al. | May 2010 | A1 |
| 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 | Lina 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 | Guenther 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 |
| 20110015593 | 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 |
| 20110040288 | Eckstein et al. | Feb 2011 | A1 |
| 20110046521 | Farrelly | Feb 2011 | A1 |
| 20110054810 | Turner et al. | Mar 2011 | A1 |
| 20110063117 | Turner et al. | 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 |
| 20110073107 | Rodman 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 |
| 20110133948 | Ervin | Jun 2011 | A1 |
| 20110137759 | Wellington et al. | Jun 2011 | A1 |
| 20110145018 | Fotsch et al. | Jun 2011 | A1 |
| 20110152739 | Roncadi et al. | Jun 2011 | A1 |
| 20110173028 | Bond | Jul 2011 | A1 |
| 20110184754 | Park et al. | Jul 2011 | A1 |
| 20110190703 | Pratt et al. | Aug 2011 | A1 |
| 20110196321 | Wudyka | Aug 2011 | A1 |
| 20110225008 | Elkouh et al. | Sep 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 |
| 20110275353 | Liu | Nov 2011 | A1 |
| 20110285244 | Lewis et al. | Nov 2011 | A1 |
| 20110288511 | Locke et al. | Nov 2011 | A1 |
| 20110288878 | Blair | 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 |
| 20120029312 | Beaudry et al. | Feb 2012 | A1 |
| 20120029313 | Burdett et al. | Feb 2012 | A1 |
| 20120032819 | Chae et al. | Feb 2012 | A1 |
| 20120035427 | Friedman et al. | Feb 2012 | A1 |
| 20120035560 | Eddy et al. | Feb 2012 | A1 |
| 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 |
| 20120077605 | Nakagaito et al. | Mar 2012 | A1 |
| 20120081225 | Waugh et al. | Apr 2012 | A1 |
| 20120089369 | Abuzeni et al. | Apr 2012 | A1 |
| 20120123323 | Kagan et al. | May 2012 | A1 |
| 20120123358 | Hall et al. | May 2012 | A1 |
| 20120123796 | Mcfaul | May 2012 | A1 |
| 20120157889 | Tanis et al. | Jun 2012 | A1 |
| 20120157941 | Luckemeyer 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 |
| 20120191475 | Pandey | 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 |
| 20120215136 | Schneider et al. | 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 |
| 20130045764 | Vik et al. | 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 |
| 20130087609 | Nichol et al. | Apr 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 |
| 20130160082 | Miller | 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 |
| 20130204106 | Bennett | Aug 2013 | A1 |
| 20130204210 | Pratt et al. | Aug 2013 | A1 |
| 20130211854 | Wagstaff | Aug 2013 | A1 |
| 20130212168 | Bonasera et al. | Aug 2013 | A1 |
| 20130214925 | Weiss | Aug 2013 | A1 |
| 20130218053 | Kaiser et al. | Aug 2013 | A1 |
| 20130223979 | Locke et al. | Aug 2013 | A1 |
| 20130226607 | Woody et al. | Aug 2013 | A1 |
| 20130227128 | Wagstaff | Aug 2013 | A1 |
| 20130231596 | Hornbach et al. | Sep 2013 | A1 |
| 20130245387 | Patel | Sep 2013 | A1 |
| 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, Jr. | 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 | 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 |
| 20150012290 | Inciardi et al. | Jan 2015 | 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 |
| 20160080365 | Baker et al. | Mar 2016 | A1 |
| 20160110507 | Abbo | Apr 2016 | A1 |
| 20160151015 | Condurso et al. | Jun 2016 | A1 |
| 20160203275 | Benjamin et al. | Jul 2016 | A1 |
| 20170065837 | Tanis et al. | Mar 2017 | A1 |
| 20180158545 | Blomquist | Jun 2018 | A1 |
| 20180233016 | Daniel et al. | Aug 2018 | A1 |
| 20180233221 | Blomquist | Aug 2018 | A1 |
| Number | Date | Country |
|---|---|---|
| 2819475 | Jun 2012 | CA |
| 1797418 | Jul 2006 | CN |
| 201921164 | Aug 2011 | CN |
| 102805894 | Dec 2012 | CN |
| 102961815 | Mar 2013 | CN |
| 104721892 | Jun 2015 | CN |
| 102010036405 | Jan 2012 | DE |
| 202014101752 | Jun 2014 | DE |
| 0403294 | Dec 1990 | EP |
| 0526166 | Feb 1994 | EP |
| 0829228 | Mar 1998 | EP |
| 1034734 | Sep 2000 | EP |
| 1064053 | Jan 2001 | EP |
| 0566381 | Jul 2002 | EP |
| 1231965 | Aug 2002 | EP |
| 0809470 | Oct 2002 | EP |
| 1291802 | Mar 2003 | EP |
| 1309960 | May 2003 | EP |
| 1176909 | Jul 2003 | EP |
| 0904788 | Nov 2003 | EP |
| 0814864 | Dec 2003 | EP |
| 1407624 | Apr 2004 | EP |
| 1011420 | Dec 2004 | EP |
| 1199046 | Jan 2005 | EP |
| 1495713 | Jan 2005 | EP |
| 1524619 | Apr 2005 | EP |
| 1540557 | Jun 2005 | EP |
| 1566201 | Aug 2005 | EP |
| 1566201 | Sep 2005 | EP |
| 1579367 | Sep 2005 | EP |
| 1587017 | Oct 2005 | EP |
| 1633241 | Mar 2006 | EP |
| 1684146 | Jul 2006 | EP |
| 1702649 | Sep 2006 | EP |
| 1788503 | May 2007 | EP |
| 1797918 | Jun 2007 | EP |
| 1839244 | Oct 2007 | EP |
| 1839615 | Oct 2007 | EP |
| 1857950 | Nov 2007 | EP |
| 1870068 | Dec 2007 | EP |
| 1904964 | Apr 2008 | EP |
| 1934852 | Jun 2008 | EP |
| 1975828 | Oct 2008 | EP |
| 1993435 | Nov 2008 | EP |
| 1610861 | Mar 2009 | EP |
| 2038786 | Mar 2009 | EP |
| 2040604 | Apr 2009 | EP |
| 2092470 | Aug 2009 | EP |
| 2146297 | Jan 2010 | EP |
| 2172859 | Apr 2010 | EP |
| 2214552 | Aug 2010 | EP |
| 2218478 | Aug 2010 | EP |
| 2246079 | Nov 2010 | EP |
| 2248545 | Nov 2010 | EP |
| 1668556 | Feb 2011 | EP |
| 2279028 | Feb 2011 | EP |
| 1404213 | Mar 2011 | EP |
| 1247229 | Apr 2011 | EP |
| 1970098 | May 2011 | EP |
| 1406540 | Jun 2011 | EP |
| 1812094 | Aug 2011 | EP |
| 2384472 | Nov 2011 | EP |
| 2226002 | Jan 2012 | EP |
| 1610494 | Mar 2012 | EP |
| 1248660 | Apr 2012 | EP |
| 2023800 | Apr 2012 | EP |
| 2451513 | May 2012 | EP |
| 1248661 | Aug 2012 | EP |
| 2488977 | Aug 2012 | EP |
| 2503478 | Sep 2012 | EP |
| 2505169 | Dec 2012 | EP |
| 2529765 | Dec 2012 | EP |
| 2389961 | Mar 2013 | EP |
| 2619723 | Jul 2013 | EP |
| 1881784 | Oct 2013 | EP |
| 2664194 | Nov 2013 | EP |
| 2674845 | Dec 2013 | EP |
| 2650027 | Jan 2014 | EP |
| 1565219 | Feb 2014 | EP |
| 2745204 | Jun 2014 | EP |
| 2562665 | Jul 2014 | EP |
| 2066365 | Apr 2015 | EP |
| 2563437 | Mar 2017 | EP |
| 2556650 | May 2017 | EP |
| 2632407 | Aug 2017 | EP |
| 2320971 | May 2018 | EP |
| 2335173 | May 2018 | EP |
| 2440112 | Oct 2018 | EP |
| 3219340 | Jan 2019 | EP |
| 3246054 | May 2019 | EP |
| 2235877 | Mar 1991 | GB |
| 2279784 | Jan 1995 | GB |
| 2342584 | Apr 2000 | GB |
| 2409951 | Jul 2005 | GB |
| 2436160 | Sep 2007 | GB |
| 2449400 | Nov 2008 | GB |
| 2456708 | Jul 2009 | GB |
| 2423178 | May 2010 | GB |
| 2475091 | May 2011 | GB |
| 2488904 | Sep 2012 | GB |
| 2446923 | May 2013 | GB |
| 2491946 | Aug 2014 | GB |
| H1085288 | Apr 1998 | JP |
| 2003116796 | Apr 2003 | JP |
| 2005027798 | Feb 2005 | JP |
| 2005071314 | Mar 2005 | JP |
| 2007289481 | Nov 2007 | JP |
| WO-9619335 | Jun 1996 | WO |
| WO-9625112 | Aug 1996 | WO |
| WO-9627163 | Sep 1996 | WO |
| WO-9744745 | Nov 1997 | WO |
| WO-9924927 | May 1999 | WO |
| WO-9935588 | Jul 1999 | WO |
| WO-9947209 | Sep 1999 | WO |
| WO-9963886 | Dec 1999 | WO |
| WO-0032088 | Jun 2000 | WO |
| WO-0060522 | Oct 2000 | WO |
| WO-0061003 | Oct 2000 | WO |
| WO-0114048 | Mar 2001 | WO |
| WO-0133457 | May 2001 | WO |
| WO-0136027 | May 2001 | WO |
| WO-0181829 | Nov 2001 | WO |
| WO-0217075 | Feb 2002 | WO |
| WO-0228477 | Apr 2002 | WO |
| WO-0233577 | Apr 2002 | WO |
| WO-02078594 | Oct 2002 | WO |
| WO-02101713 | Dec 2002 | WO |
| WO-02093301 | May 2003 | WO |
| WO-03054668 | Jul 2003 | WO |
| WO-03055432 | Jul 2003 | WO |
| WO-03060650 | Jul 2003 | WO |
| WO-03101508 | Dec 2003 | WO |
| WO-2004057514 | Jul 2004 | WO |
| WO-03094090 | Sep 2004 | WO |
| WO-2004074457 | Sep 2004 | WO |
| WO-2004093983 | Nov 2004 | WO |
| WO-2004100779 | Nov 2004 | WO |
| WO-2005022349 | Mar 2005 | WO |
| WO-2005031632 | Apr 2005 | WO |
| WO-2005036447 | Apr 2005 | WO |
| WO-2005045461 | May 2005 | WO |
| WO-2005053793 | Jun 2005 | WO |
| WO-2005057466 | Jun 2005 | WO |
| WO-2005083619 | Sep 2005 | WO |
| WO-2005101282 | Oct 2005 | WO |
| WO-2005120097 | Dec 2005 | WO |
| WO-2005109297 | Mar 2006 | WO |
| WO-2006021154 | Mar 2006 | WO |
| WO-2006066583 | Jun 2006 | WO |
| WO-2006066585 | Jun 2006 | WO |
| WO-2006071711 | Jul 2006 | WO |
| WO-2006099120 | Sep 2006 | WO |
| WO-2006108858 | Oct 2006 | WO |
| WO-2006111109 | Oct 2006 | WO |
| WO-2007027490 | Mar 2007 | WO |
| WO-2007035646 | Mar 2007 | WO |
| WO-2007056734 | May 2007 | WO |
| WO-2007127879 | Nov 2007 | WO |
| WO-2007133478 | Nov 2007 | WO |
| WO-2007137869 | Dec 2007 | WO |
| WO-2008010012 | Jan 2008 | WO |
| WO-2008036344 | Mar 2008 | WO |
| WO-2008036360 | Mar 2008 | WO |
| WO-2008039314 | Apr 2008 | WO |
| WO-2008062382 | May 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-2009140669 | Nov 2009 | WO |
| WO-2009151645 | Dec 2009 | WO |
| WO-2010017484 | Feb 2010 | WO |
| WO-2010025166 | Mar 2010 | WO |
| WO-2010025467 | Mar 2010 | WO |
| WO-2010039481 | Apr 2010 | WO |
| WO-2010078558 | Jul 2010 | WO |
| WO-2010085033 | Jul 2010 | WO |
| WO-2010089368 | Aug 2010 | WO |
| WO-2010126668 | Nov 2010 | WO |
| WO-2010132617 | Nov 2010 | WO |
| WO-2010145780 | Dec 2010 | WO |
| WO-2011022330 | Feb 2011 | WO |
| WO-2011023275 | Mar 2011 | WO |
| WO-2011023384 | Mar 2011 | WO |
| WO-2011039676 | Apr 2011 | WO |
| WO-2011046860 | Apr 2011 | WO |
| WO-2011047334 | Apr 2011 | WO |
| WO-2011089270 | Jul 2011 | WO |
| WO-2011107972 | Sep 2011 | WO |
| WO-2011123933 | Oct 2011 | WO |
| WO-2011124388 | Oct 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-2013026999 | Feb 2013 | WO |
| WO-2013029330 | Mar 2013 | WO |
| WO-2013036853 | 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 |
| Entry |
|---|
| Cinterion., “Cinterion PHS8-P 3G HSPA+,” retrieved from http://www.cinterion.com/tl_files/cinterion/downloads/cinterion_datasheet_PHSS_web.pdf, 2012, 2 pages. |
| Decision of Rejection for Japanese Patent Application No. 2015254568, dated Jul. 3, 2017, 4 pages. |
| First Examination Report for Australian Application No. 2011316883, dated Feb. 29, 2016, 3 pages. |
| Hartmann Vivano., “Vivano—Product Application Description,” retrieved from http://www.vivanosystem.info/20809.php, accessed on Feb. 28, 2013, 3 pages. |
| Huntleigh Healthcare, “Negative Pressure Positive Outcomes,” WoundASSIST TNP Console and Canister Brochure, 2007, 6 pages. |
| International Preliminary Report on Patentability Application No. PCT/US2011/057337, dated May 2, 2013, 8 pages. |
| International Preliminary Report on Patentability for Application No. PCT/US2011/055937, dated Apr. 25, 2013, 8 pages. |
| International Preliminary Report on Patentability for Application No. PCT/US2014/026692, dated Sep. 24, 2015, 16 pages. |
| International Search Report and Written Opinion for Application No. PCT/US2011/055937, dated Dec. 23, 2011, 11 pages. |
| International Search Report and Written Opinion for Application No. PCT/US2011/057332, dated Mar. 23, 2012, 8 pages. |
| International Search Report and Written Opinion for Application No. PCT/US2011/057337, dated Feb. 23, 2012, 9 pages. |
| International Search Report and Written Opinion for Application No. PCT/US2014/026692, dated Mar. 2, 2015, 26 pages. |
| Invitation to Pay and Partial International Search Report for Application No. PCT/US2014/026692, dated Sep. 26, 2014, 9 pages. |
| Japanese Office Action, re JP Application No. 2015-254568, dated Feb. 21, 2017, 6 pages. |
| Notice of Opposition for the European Patent No. 2630601, dated May 7, 2020, 37 pages. |
| Notice of Reasons for Rejection for Japanese Patent Application No. 2013533968, dated Jul. 14, 2015, 6 pages. |
| Oddsson L.I.E., et al., “A Robotic Home Telehealth Platform System for Treatment Adherence, Social Assistance and Companionship—an Overview,” 31st Annual international Conference of the IEEE EMBS, Sep. 2009, pp. 6437-6440. |
| Office Action dated Dec. 11, 2017 for Canadian Application No. 2814657, 4 pages. |
| Office Action dated Nov. 14, 2017 for Australian Application No. 2017201192, 3 pages. |
| Office Action dated Jul. 19, 2017 for Canadian Application No. 2815474, 5 pages. |
| Office Action dated Jan. 9, 2015 for Australian Application No. 2011316599, 5 pages. |
| Second Examination Report for Australian Application No. 2011316883, dated Feb. 2, 2017, 5 pages. |
| Brief Communication—Letter from the Opponent, re the Opposition of European Patent No. EP2627277, dated Mar. 16, 2021, 3 pages. |
| Brief Communication—Letter from the Proprietor, re the Opposition of European Patent No. EP2627277, dated Apr. 7, 2021, 13 pages. |
| Brief Communication—Letter from the Opponent, re the Opposition of European Patent No. 2627277, dated Feb. 9, 2022, 4 pages. |
| Brief Communication—Letter from the Opponent, re the Opposition of European Patent No. 2630601, dated Sep. 22, 2021, 5 pages. |
| Brief Communication—Letter from the Opponent, re the Opposition of European Patent No. EP2627277, dated Dec. 10, 2021, 4 pages. |
| Brief Communication—Letter from the Opponent, re the Opposition of European Patent No. EP2630601, dated Jan. 19, 2021, 3 pages. |
| Brief Communication—Letter from the Opponent, re the Opposition of European Patent No. EP3581244, dated Jun. 22, 2022, 5 pages. |
| Brief Communication—Letter from the Proprietor for Opposition proceedings of the European Patent No. 2630601, dated Oct. 16, 2020, 43 pages. |
| Brief Communication—Letter from the Proprietor for Reply to the notice(s) of opposition of European Patent No. 2630601, dated Oct. 29, 2020, 15 pages. |
| Brief Communication—Letter from the Proprietor of the Patent, re the Opposition for Simmons & Simmons for European Patent No. 2630601, dated Sep. 21, 2021, 2 pages. |
| Brief Communication—Letter from the Proprietor of the Patent, re the Opposition of European Patent No. EP3581244, dated May 13, 2022, 47 pages. |
| Brief Communication—Letter from the Proprietor, re the Opposition of European Patent No. EP2627277, dated Dec. 9, 2021, 2 pages. |
| Brief communication in opposition procedure—time limit, letter from the Proprietor for European Patent No. 2630601, dated Oct. 27, 2020, 2 pages. |
| Brief Communication of Letter from the Opponent for Opposition against of the European Patent No. 2630601, dated Nov. 11, 2020, 6 pages. |
| Communication of a Notice of Opposition including Statement of Facts and Arguments for European Patent No. 3581244, dated Dec. 22, 2021, 26 pages. |
| Communication of further notices of opposition pursuant to Rule 79(2) EPC for European Application No. 11776953.9, dated Sep. 1, 2020, 2 pages. |
| Communication to the parties concerning termination of opposition proceedings for European Patent No. 2627277, dated May 25, 2022, 1 page. |
| Discussion between Lesley Fenton and Kevin Cordina regarding Opponent's name, mailed on Dec. 12, 2019, 3 pages. |
| Discussion between Mr. Kevin Cordina and Mr. Nadeem Bridi regarding Opponent's name, mailed on Dec. 11, 2019, 2 pages. |
| Extract from the Register of European Patents No. EP2731564 on Jan. 12, 2021, 4 pages. |
| Grounds for the Decision, the Opposition of European Patent No. 2630601, mailed Feb. 17, 2022, 77 pages. |
| Information about the Result of Oral Proceedings, the Opposition of European Patent No. 2630601, dated Nov. 18, 2021, 4 pages. |
| Letter from the Proprietor for Opposition proceedings of the European Patent No. 2630601, mailed on Dec. 7, 2020, 4 pages. |
| Notice of Communication of amended entries concerning the representative (R. 143(1)(h) EPC) and enclosed letter from the proprietor of the patent dated Jan. 11, 2021 for European Patent No. 2627277, dated Jan. 20, 2021, 21 pages. |
| Notice of Decision to Discontinue the Opposition Proceedings for European Patent No. 2627277, dated Feb. 10, 2022, 3 pages. |
| Notice of Opposition—Statement of Facts and Evidence for the European Patent No. 2731564, mailed on Jan. 22, 2020, 12 pages. |
| Opponent's Statement of Facts and Arguments for the European Patent No. 2627277, mailed on Aug. 20, 2020, 5 pages. |
| Patentee's letter for Opposition proceedings of the European Patent No. 2731564, dated Jun. 16, 2020, 5 pages. |
| Proprietor's Written Submission in Preparation for the Oral Proceedings for the Opposition of European Patent No. 2627277, dated Feb. 3, 2022, 2 pages. |
| State on Oath of Kevin Cronin submitted in the Opposition against European Patent No. 2630601, signed on Nov. 4, 2020, 1 page. |
| State On Oath of Nadeem Bridi submitted in the Opposition against European Patent No. 3246054, signed on Dec. 14, 2020, 1 page. |
| Statement of Grounds of Appeal for the European Patent No. 2630601, mailed on Jun. 8, 2022, 63 pages. |
| Statement of Grounds of Appeal for the European Patent No. 2630601, mailed on Jun. 14, 2022, 4 pages. |
| Summons to Attend Oral Proceedings Pursuant to Rule 115(1) EPC for European Patent No. 2627277, mailed on Apr. 28, 2021, 10 pages. |
| Summons to Attend Oral Proceedings pursuant to rule 115(1) EPC for Patent No. 2630601, mailed on Jan. 18, 2021, 18 pages. |
| Termination of the Opposition Proceedings with Maintenance of European Patent No. 2627277, dated May 20, 2022, 1 page. |
| Forwarding of Submissions to Parties of a Letter of the Opponent for European Patent No. EP2630601, dated Oct. 12, 2022, 17 pages. |
| Forwarding of Submissions to Parties of a Letter of the Patent Proprietor for European Patent No. EP2630601, dated Oct. 14, 2022, 11 pages. |
| Summons to Attend Oral Proceedings Pursuant to Rule 115(1) EPC for European Patent No. 3581244, dated Nov. 29, 2022, 16 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20200324146 A1 | Oct 2020 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61483445 | May 2011 | US | |
| 61405757 | Oct 2010 | US | |
| 61405405 | Oct 2010 | US | |
| 61392154 | Oct 2010 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15482449 | Apr 2017 | US |
| Child | 16863820 | US | |
| Parent | 15357883 | Nov 2016 | US |
| Child | 15482449 | US | |
| Parent | 13271870 | Oct 2011 | US |
| Child | 15357883 | US |
