Patient monitoring apparatus and method for orthosis and other devices

Information

  • Patent Grant
  • 9763581
  • Patent Number
    9,763,581
  • Date Filed
    Friday, March 15, 2013
    11 years ago
  • Date Issued
    Tuesday, September 19, 2017
    7 years ago
Abstract
A drug delivery system is provided. The drug delivery apparatus including at least one sensor configured to detect at least one of a drug delivery parameter and patient data and a portable communication device communicatively coupled to the drug delivery apparatus. The portable communication device includes an input device configured to receive data from the drug delivery apparatus, wherein the data includes at least one of a drug delivery parameter and patient data and an output device coupled to the input device and configured to display the received data.
Description
BACKGROUND OF THE INVENTION

Field of the Invention


The present invention relates to a patient monitoring system and method that can be used, for example, with an orthosis for physical therapy.


Description of Related Art


In the field of medicine, rehabilitation after surgery or other major medical procedures has been an important issue for researchers. As shown in U.S. Pat. Nos. 5,395,303; 5,285,773; 5,213,094; 5,167,612; 6,502,577; 6,113,562 and 5,848,979, continuous passive motion has been used to treat conditions such as the glenohumeral joint adhesive capsulitis. These patents teach using stretching principles in order to treat one of the major problems patients are referred to physical therapists for: lack of a full range of motion in their joints. The orthosis devices of these patents simulate manual therapy techniques used in clinical settings, combining the principles of stress relaxation and progressive stretch to achieve permanent elongation of soft tissue.


Once a patient has been prescribed treatment with one of the rehabilitation orthosis devices, a major concern is patient education and compliance. To maximize improvement in range of motion the patient must comply with the prescribed protocol and the patient improvement must be tracked. The exercise protocol for these orthosis devices is well established, and should be followed closely to ensure the best treatment possible. First, the patient fits the orthosis as specified by the device specific instructions. Then the patient rotates the knob of the orthosis device until a slight stretch is felt. This stretch should not be painful. Now the patient holds this position for a predetermined time period (e.g., five minutes), and then this procedure is repeated for a predetermined number of stretches (e.g., 6 stretches). During the first week of the patient's treatment, typically one session a day is performed. During the second week, typically two sessions per day are performed. During the third and following weeks, typically three sessions per day are performed.


The above described orthosis devices allow the patient to do these sessions outside of the confines of the doctor's or physical therapist's office. Due to the fact that there are no medically trained personnel to oversee this treatment the opportunity to stray from the protocol is introduced. In addition, the patient is responsible for the tracking of his or her own progress until reporting back to the physical therapist or doctor. Both of these conditions have the possibility of introducing a high margin of error. Most recently, physicians have expressed an interest in keeping better records of an individual patient's progress during the rehabilitation process. Unfortunately, in many cases, since the rehabilitation process occurs mostly within the confines of the patient's home, it is difficult for a physician to keep an accurate record of the patient's progress.


There are other areas in which patient education and compliance outside the immediate supervision of a health care professional remain problematic. For example, electrical stimulation of bone growth for treatment of fractures requires a regime of therapy that demands patient adherence in order to optimize the stimulatory effects.


Thus, there exists a need for an improved patient monitoring system and method.


SUMMARY OF THE INVENTION

In one embodiment of the disclosure, a drug delivery system is provided. The drug delivery system includes a drug delivery apparatus including at least one sensor configured to detect at least one of a drug delivery parameter and patient data and a portable communication device communicatively coupled to the drug delivery apparatus. The portable communication device includes an input device configured to receive data from the drug delivery apparatus, wherein the data includes at least one of a drug delivery parameter and patient data and an output device coupled to the input device and configured to display the received data.


In another embodiment of the disclosure, one or more non-transitory computer-readable storage media having computer-executable instructions embodied thereon is provided. When executed by a processor, the computer-executable instructions cause the processor to receive, by an input device, data from at least one sensor of a drug delivery apparatus, wherein the data includes at least one of a drug delivery parameter and patient data, display, on an output device, the received data from at least one sensor, and transmit a delivery protocol to the drug delivery apparatus.


In another embodiment of the disclosure, a portable communication device configured to monitor a patient therapy system is provided. The mobile communication device includes an input device configured to receive data from at least one sensor of a patient therapy system, wherein the data includes at least one of therapy data and patient data and an output device coupled to the processor and configured to display the received data.


In another embodiment of the disclosure, a drug delivery system is provided. The drug delivery system includes a drug delivery apparatus including at least one sensor configured to detect at least one of a drug delivery parameter and patient data, a portable communication device communicatively coupled to the drug delivery apparatus, and a communications component. The portable communication device includes an input device configured to receive data from the drug delivery apparatus, wherein the data includes at least one of a drug delivery parameter and patient data and an output device coupled to the input device and configured to display the received data. The communications component is configured to transmit, to an external source, an indication that a change be made to the delivery protocol based on the received data.


Consistent with the title of this section, the above summary is not intended to be an exhaustive discussion of all the features or embodiments of the present invention. A more complete, although not necessarily exhaustive, description of the features and embodiments of the invention are found in the section entitled “Detailed Description Of The Invention”.





BRIEF DESCRIPTION OF THE DRAWINGS

A more complete appreciation of the present invention and many of the attendant advantages thereof will be readily obtained as the same becomes better understood by reference to the following detailed description when considered in connection with the accompanying drawings, wherein:



FIG. 1 is a view of an illustrative orthosis device used with the monitor in accordance with the present invention.



FIG. 2 is an enlarged sectional view of tower of FIG. 1 including the drive mechanism.



FIG. 3 is a block diagram of the monitoring system in accordance with the present invention.



FIG. 4 is a block diagram of the hardware used in the monitor of the present invention when in the treatment mode of operation.



FIG. 5 is a block diagram of the hardware used in the monitor of the present invention when in the data transfer mode of operation.



FIG. 6 is a schematic diagram of the position sensor used in the present invention.



FIG. 7 is a flow chart of the firmware embedded in the monitor of the present invention.



FIG. 8 is a detailed schematic of the hardware used in the monitor of the present invention.



FIG. 9 is a schematic of the circuitry for the sensors used in the monitor of the present invention.



FIG. 10 shows circuit diagram of an alternative embodiment of the monitor which includes a device type sensor in accordance with another aspect of the present invention.





DETAILED DESCRIPTION OF THE INVENTION

Referring to FIGS. 1 and 2, there is illustrated one of many possible prior art orthosis devices, generally indicated by the reference number 10, which may be used with the patient monitor of the present invention. More specifically, this particular illustrative orthosis device 10 is described in U.S. Pat. Nos. 5,395,303; 5,285,303; 5,285,773; 5,213,094; and 5,167,612 to Bonutti, et al., which are incorporated herein.


In FIG. 1 the orthosis device 10 is illustrated as attached to a human arm, for moving the elbow joint which is between the upper arm and the forearm. The orthosis 10 includes a first cuff 12 for attachment to a first body portion 14 such as the forearm, and a second cuff 16 for attachment to a second body portion 18 such as the upper arm. The term “cuff” as used herein means any suitable structure for transmitting the force of the orthosis to the limb portion it engages. The first body portion 14 is joined to the second body portion 18 at the elbow joint designated A. Each of the first and second cuffs 12 and 16 includes a plurality of loop connectors 20 for receiving straps extending around the body portions 14 and 18 to clamp the cuffs 12 and 16 to the body portions 14 and 18. The first cuff 12 is mounted for sliding movement on a first cuff arm 22. The term “cuff arm” as used herein means any suitable structure for transmitting the force of the orthosis to the cuff and thence to the limb portion. The first cuff arm 22 is pivotally mounted by a pin 24 to a tower 26. The first cuff arm 22 includes a support 28. A first lever arm 30 extends from the tower 26 and is pivotally connected to the support 28 by a pin 32. The first lever arm 30 is pivotally connected to a cuff actuator block 34. The cuff actuator block 34 is fixed to the first cuff 12 and is slidable along the first cuff arm 22 in a manner as described below. The second cuff 16 is mounted for sliding movement on a second cuff arm 40. The second cuff arm 40 is pivotally mounted by a pin 42 to the tower 26. The second cuff arm 40 includes a support 44. A second lever arm 46 extends from the tower 26 and is pivotally connected to the support 44 by a pin 48. The second lever arm 46 is pivotally connected to a cuff actuator block 50. The cuff actuator block 50 is fixed to the second cuff 16 and is slidable along the second cuff arm 40 in a manner as described below.


As shown in FIGS. 1 and 2, the tower 26 is a box-like structure including a lower housing 66 and an upper housing 70 joined by a front plate (removed) and a back plate 53. A drive mechanism for the orthosis device 10 is disposed substantially within the tower 26. The drive mechanism includes a manually actuatable knob 52 (FIG. 1) which is fixed to a shaft 54. The shaft 54 extends into the tower 26 and a gear 56 (FIG. 2) is fixed to the shaft. The gear 56 engages external gear teeth 58 on a gear 60. Rotation of the gear 56 about its axis causes rotation of the gear 60 about its axis. The gear 60 is fixed to an externally threaded lead screw 62. One end of the lead screw 62 is journalled for rotation in a bushing 64 mounted in a lower housing 66 of the tower 26. The opposite end of the lead screw 62 is journalled for rotation in a bushing 68 mounted in an upper housing 70 of the tower 26. An arm actuator block or base link 72 has an internally threaded opening 74 though which the lead screw 62 extends in threaded engagement. As the lead screw 62 rotates, the actuator block 72 moves axially along the lead screw 62 within the tower 26. This mechanism provides the “rotating means” for rotating the first cuff arm 22 relative to the second cuff arm 40 and thereby expanding or reducing the angular relationship there between.


In operation, the orthosis device 10 of the prior art may provide for distraction of the joint through an entire range of motion. Movement of the cuff arms to extend the joint results in distractive forces being applied to the joint. These distractive forces are limited and controlled by having the cuffs 12 and 16 slidable on the cuff arms 22 and 40, respectively. The cuffs 12 and 16 are selectively moved along the cuff arms 22 and 40, during relative movement of the cuff arms 22 and 40, to provide the proper amount of distractive forces to the joint and to limit compressive forces on the joint. Thus, the orthosis device 10 illustrates one of many orthosis devices that are well suited for stretching therapy.


It should be understood that the orthosis device 10 can be used to extend or flex other joints in the body, such as a knee joint or a wrist joint or ankle joint, with the construction of the orthosis 10 in such case being varied to fit the particular application. A few more illustrative examples are shown in U.S. Pat. No. 6,502,577 for finger joints orthosis, U.S. Pat. No. 6,113,562 for a shoulder orthosis, and U.S. Pat. No. 5,848,979 for a hand orthosis. Moreover, it is contemplated that the monitoring unit of the present invention may also be used for other types of devices, including, but not limited to, rehabilitative devices implementing isometric exercises and those in the continuous passive motion (CPM) area.


To generalize the description of the one class of orthosis devices that may be used with the present invention, such as orthosis devices including (but are not limited to) the stretching orthosis device 10 of FIGS. 1 and 2, isometric orthosis devices, and CPM orthosis devices, the following generic terminology is used in the appended claims. The orthosis devices used with the monitoring system in accordance with the present invention generally are for moving a first portion and a second body portion of a patient connected by a joint. These orthosis devices typically include a first carriage member for receiving the first body portion and a second carriage member for receiving the second body portion. Each carriage member has proximal and distal ends. The second carriage member and the second carriage member are movably connected about their proximal ends so that the first carriage member pivots relative to the second carriage member about an axis intermediate to the first and second carriage members. Hence, the carriage members may move from a first position to a second position and in so doing change the angle defined by the two carriage members.


In the illustrative embodiment of the stretching orthosis shown in FIGS. 1 and 2, the first and second carriage members each include the cuff arm 22 or 40 and a cuff 12 or 16 for connecting cuff arm 22 or 40 to one of said body portions 14, with the cuff 12 or 16 slidably mounted on the cuff arm 22 or 40. In other orthosis devices not directed toward stretching exercises, such those directed toward isometric exercises, the first carriage member and the second carriage member are merely pivotally connected at their proximal ends (frequently adjustably locked in fixed relationship). An example of a simplified orthosis device is shown in U.S. Pat. No. 5,116,296 to Watkins et al. and is incorporated herein by reference thereto. Another example is described in U.S. Pat. No. 5,052,375 to Stark et al. (also incorporated herein by reference thereto), wherein the two carriage members are interconnected by an adjustable hinge and the angle between the respective distal end sections can be adjusted relative to one another. The angular position between the first carriage member and the second carriage member is one of the parameters that is measured by the monitoring system in accordance to be present invention, but as will be discussed hereinafter, the monitoring system includes other sensors for measuring other parameters, such the identification of the orthosis device to eliminate the need for external unit configuration and temperature as an indication the orthosis device is actually being used.


In the case of using the temperature and device identification sensors, the monitoring system of the present invention may be used with any number of different types of orthosis devices. More specifically, any orthosis device needing assurances that the user is actually wearing the orthosis device during his/her exercise period using the orthosis, and not falsifying usage, may make use of the monitoring system of the present invention for temperature measurements which provides evidence that the orthosis is being properly used. Likewise, with monitors using different parameters or firmware for different orthosis devices, the family of orthosis devices may make use of the device type identification sensor, which will allow the monitor to access the connect parameters and/or firmware appropriate for a particular orthosis device without the need for parameters and/or firmware to be downloaded to the monitor.


Referring to the block diagram of FIG. 3, a patient monitoring system 100 for use with a device such as a physical therapy orthosis, like the orthosis device of FIGS. 1 and 2, is shown. The patient monitoring system 100 includes a standalone monitor 102 which can be incorporated into the orthosis device of FIGS. 1 and 2. More specifically, the monitor 102 has a data acquisition unit 104 mounted on the outside of the tower 26 (shown by a dashed line), such tower 26 being described with respect to FIGS. 1 and 2. Additionally, the monitor 102 includes a plurality of sensors 105, three of which are shown in FIG. 3 as a position sensor 106, a temperature sensor 108, and an optional device type sensor 110. As shown by the dashed line, the temperature sensor 102 and the device sensor are mounted on one of the cuff arms 22 and/or 40 shown in FIGS. 1 and 2.


As an overview of the monitoring system 100 when applied to a stretching orthosis such as that shown in FIGS. 1 and 2, a patient is prescribed treatment by a physician or physical therapist, with the prescribed treatment using a given orthosis device having a monitor 102. In a first mode of operation (data transfer or administrative mode), the appropriate orthosis device is modified to fit a patient's specific requirements by the physician or physical therapist down loading the required parameters to the monitor 102. This data transfer mode of operation is used only by the physical therapist or doctor.


In a second mode of operation (treatment mode), the user connects the sensors 105 to the data acquisition unit 104. The monitor 102 controls each exercise session with the patient by stepping the patient through his or her treatment following the previously described stretching protocol. During the critical sections of this treatment in a first mode of operation, the monitor 102 monitors the operation by taking measurements from the sensors 105 and storing them in memory. These retrieval and storage operations are accomplished via a micro-controller and an EEPROM, which will be described in detail hereinafter. Preferably, the unit 104 is able to store approximately two months worth of sessions. Alternatively, the data can be transmitted to another data storage unit. This transmission can occur instantaneously or at set intervals.


At the time of the follow-up appointment with a physician or physical therapist, the user disconnects the unit 104 from the orthosis device and disconnects the sensors 105. Then the user brings the unit 104 to the physician or physical therapist. At this point, the unit 104 again uses the data transfer mode of operation. The information is transferred from the unit 104 to a computer 112 at the office of physician or physical therapist. The memory containing such data in the unit 104 is then erased. This computer 112 uses data analysis software to further manipulate the data and present it for display by the computer 112.


Overviews of the hardware of the data acquisition unit 104, as configured in the above-described modes of operation, are provided in FIGS. 4 and 5. The data acquisition unit 104 includes a microprocessor 120 (PIC16F877) and an external memory 122. In both FIGS. 4 and 5, the microprocessor 120 (PIC16F877) uses the external memory 122 and is electrically coupled to a display device 124, in the form of a parallel LCD. FIG. 4 shows the hardware configured for the treatment mode, wherein the microcontroller 120 is electrically coupled to the sensors 105 via buses 126 and 128. FIG. 5 shows the hardware configured in the data transfer mode to be in communication with the computer 112 via a cable 130 coupled to an RS-232 port 132 on the microprocessor 120. The MAX 233, shown by reference numeral 133, is a Maxim MAX233a device which is used to convert the serial communication voltages used on the microprocessor 120 to the RS-232 levels required by the computer 112.


With reference to FIGS. 3, 4 and 5, the two modes of operation of the monitor 102 will be described in detail, with the mode of operation being set by the computer 112 via the cable 114. The data transfer mode is entered when the monitor 102 is turned on with the monitor-to-PC cable 114 being inserted into the data acquisition unit interface provided by the port 116 of the monitor 102. As described above, this mode is used for the configuration of the monitor 112 as well as the retrieval of the acquired data after the monitor is returned by the patient. Through device configuration by the computer 112 various options may be set allowing the monitor 102 not only to be used with the illustrative orthosis device of FIGS. 1 and 2, but also to be used with the entire family of rehabilitation devices without modifying the hardware or firmware of the data acquisition unit 104. The device configuration options are stored on various orthosis devices in the memory 122. The communications protocol for configuring the monitor 102 is provided below in TABLE I:












TABLE I







Expected



Command
Name
Arguments
Description







0x00
Send data
none
Sends the patient data to the





PC via the RS-232 port.


0x11
Set reps
number of reps
Set the number of stretches




(ASCII)
the patient performs per





session.


0x22
Set mins
number of
Set the number of minutes




minutes (ASCII)
the patient will hold each





stretch.


0x33
Set secs
number of
Set the 10's position of the




seconds (ASCII)
number of seconds to hold





each stretch.


0x44
Set ID
device id
Sets the device ID. The first





time monitor is restarted &





connected to orthosis device





after setting the device ID,





the user will be prompted





to configure the device.


0x55
Set clock
minutes (BCD)
Sets and configures the




hours (BCD)
real time clock with the given




date (BCD)
arguments.




month (BCD)


0x66
Set mask
comparison mask
Sets the mask used to





compare measurements for





position sensor. This is used





to compensate for noisy





sensors.


0xFF
Delete
none
Marks all data as deleted





from the EEPROM storage.









It should be noted, that with the above protocol, the device id (identification) is set by the computer 112. In this embodiment, the device type sensor 110 shown in FIG. 3 is not used. Optionally, the device type sensor 110 may be used, in which case the “id” command is not needed. The alternative embodiment using the device type sensor 110 is described hereinafter.


The treatment mode is used when connected to the sensor 105 through the data acquisition unit interface 132. The sensor hardware unit contains all the necessary circuitry for the operation of the current sensors 105 as well as power and ground for the expansion ports. Referring back to FIGS. 1, 2 and 3, the temperature sensor 108 is embedded into one of the cutis 22 or 40 of the orthosis device 10. The temperature sensor 108 is not necessarily intended for an accurate measurement of the patient's body temperature while using the orthosis device 10, but is a way to ensure that the patient is actually wearing the orthosis device 10 during the treatment session.


Modifications to the tower 26 shown in FIG. 2 to include the position sensor 106 of FIG. 3 are shown in the schematic diagram of FIG. 6. Referencing to FIG. 6, the overall structure remains the same as shown by the lead screw 62, lower housing 66, actuator block 74, and upper housing 70. What is added is a spring 130 which extends from the lower housing 66 to the upper housing 70 and is disposed in parallel relationship with the lead screw 62. The spring 130 passes through an aperture 132 in the actuator block 74. An electrical contact 134 is embedded in the upper housing 70 and is in electrical contact with an upper end of the spring 130. A second electrical contact 136 is embedded in the actuator block 74 and is in electrical engagement with the spring as it slidingly passes through the aperture 132 when the actuator block 74 is moved along the lead screw 62, such movement being caused by the rotation of the lead screw, as discussed with respect to FIGS. 1 and 2. More specifically, referring back to FIGS. 1 and 2, in addition to FIG. 6, the rotation of the lead screw 62 is used to drive the device cuffs 22 and 40. As the knob 52 on the exterior of the tower 26 is turned, the actuator driver 72 moves up and down accordingly, thus moving the cuffs 22 and 40. By placing the contact 136 on the actuator driver 72 and one at the top of the spring, a variable resistor is created. This variable resistor is then used in a voltage divider circuit (shown hereinafter) to create a center-tapped potentiometer to monitor the angle formed by the arms 22 and 40 during the treatment.


Referring to FIGS. 3-5, the first time that the hardware sensors 105 are attached after the device identification number has been set during the above described data transfer mode, the user will be prompted to extend the orthosis device 10 to the maximum and then the minimum position to calibrate the device 10. These measurements are then stored in the memory 122 for use during the remainder of the treatment sessions to calculate the angle between the arms of the device 10.


Referring to FIG. 7, both the treatment mode of operation and the data transfer mode of operation for the monitor 102 are described in a flow chart of a firmware program 140, which is embedded in the data acquisition unit 104. At step 142, the firmware program 140 waits until a button is pushed by the physician or physical therapist specifying the selected mode of operation. At step 142, the mode is checked, and if the user selected the treatment mode, the program 140 branches to the “Treatment” branch. If the user selects the data transfer mode of operation, then the program 140 branches to the “Data Transfer” branch.


After the patient/user begins his or her treatment session, the monitor 102 has already been set for the treatment mode of operation. First, a splash screen is displayed with the name and version of the firmware included in the data acquisition unit 104. The session runs according to the following flow chart shown in FIG. 7, as shown on the left side. At step 146, the user is prompted to turn the knob 52 (see FIG. 1) until a gentle stretch is felt. At step 146, the program checks to see if there is power on the sensor bus. If yes, the program goes to step 150 and if no, the program branches to step 152. The micro-controller 120 at step 150 begins taking measurements of the position sensor 106 in the tower 26 (see FIG. 3) to see if the patient has stopped stretching. The micro-controller 120 (see FIG. 3) continues in a loop 154 until the current position measurement of the position sensor 106 matches the last one, which indicates that the patient has stopped stretching. More specifically, the user definable mask, set via the RS-232 port in data transfer mode, is used to compensate for noisy sensors 106, and the natural variation in analog to digital conversion. When the two position measurements of the position sensor 106 match, it is assumed that the user of the orthosis device 10 has stopped turning the knob 52 and is ready to hold the stretch. The position sensor 106 of FIG. 6, in combination with execution of this firmware routine, provides the “position sensor means” for detecting when there is a stop in movement of the first arm cuff 22 relative to the second arm cuff 40 when a patient starts to hold a stretch.


Upon the program determining that the patient has started to hold a stretch, the program proceeds to step 156, where the power is turned off on the sensor bus and the program waits a preset amount of time, e.g., 5 minutes. As specified in the previously described stretching protocol, the user is to hold the stretch for 5 minutes and the time is displayed on the LCD 124 (see FIG. 3). As shown in Table I above, the time to hold a stretch is also configured in the data transfer mode, which allows for easy modifications of this protocol if needed. This firmware routine provides “timing means” for generating a patient detectable signal aster the expiration of the predetermined time period, with in this illustrative example, is 5 minutes.


Upon completion of the hold for the stretch, the program 140 proceeds to step 158, where power is turned on to the sensor bus, all measurements of the sensors are recorded and a sound buzzer is triggered to indicate the end of the period for holding the stretch. More specifically, all of the analog conversions of the sensor 106 are repeated and stored into the memory 122. When all the measurements are saved, a 16 bit address pointer for the memory 122 is updated in the micro-controller. If the user interrupts a stretch before it is completed, then that session will automatically be overwritten by the next session without the need for more complicated error checking. At step 152, if the number of stretches is less then the amount defined by the treatment protocol, the stretch loop is repeated via loop 160. If the number of stretches completed is equal to the amount defined by the treatment protocol at step 152, then a session complete prompt is displayed on the LCD 124 and the program 140 proceeds to step 162, where the power is turned off and then the program goes to sleep at step 164.


Referring to the right side of the flow chart in FIG. 7, the data transfer mode of operation is shown. As previously described with respect to FIG. 5, the data acquisition unit 104 is in communications with the computer 112. First, the physician or physical therapist would have selected this mode of operation and the program would recognizes the same at step 144 and taken the “Data transfer” branch to step 170. If there is a timeout, the program 140 proceeds to a sleep state at step 172. If there is no timeout, then the program proceeds to step 174, where the micro-controller of 120 (FIG. 5) fetches an instruction from the computer 112. The instructions from the computer 112 include, but are not limited to, the commands listed in TABLE I above. The micro-controller 120 interprets the instruction at step 176. Depending upon the instruction, the program takes the “transfer” branch or the “delete” branch.


When the program 140 takes the “transfer” branch, at step 178, the program sends the product ID to the computer 112. Then at step 180, all the sensor data is transferred from the memory 122 to the computer 112. When the program 140 takes the “delete branch”, at step 182, the program 140 obtains from the computer 122 the product ID (see TABLE I above), then sets the product ID at step 184 and erases the existing sensor data by setting all sensor data to 0xFF (see TABLE I above). Then the program 140 proceeds to its sleep state at step 188. With this embodiment, it should be clear that the device sensor 110 is not included, because the computer 112 sets the device ID.


In FIG. 8 a detailed schematic 190 of the hardware for the data acquisition unit 104 of FIG. 3 is shown, with such hardware having been generally described on a higher level in FIGS. 4 and 5. Referring to FIG. 8, the micro-controller 120 preferably comprises a Microchip PIC16F877 micro-controller. This PIC16F877 micro-controller is a 40 pin, 8 bit CMOS Flash microcontroller configured using the following pin assignments in TABLE II below:













TABLE II








Direction/




Name
Mode
Port



















1
Temp
Analog
RA0


2
Position
Analog
RA1


3
Expand 1
Analog
RA2


4
Expand 2
Analog
RA3


5
Expand 3
Analog
RA4


6
LCD RS
Out
RB0


7
LCD R/W
Out
RB1


8
LCD E
Out
RB2


10
Mode 1
In
RB4


11
Mode 2
In
RB5


14
Buzzer
Out
RC0


16
SCL
I2C
RC3


17
SDA
I2C
RC4


18
Serial Tx
USART
RC6


19
Serial Rx
USART
RC7


20
LCD DB0
Out
RD0


21
LCD DB1
Out
RD1


22
LCD DB2
Out
RD2


23
LCD DB3
Out
RD3


24
LCD DB4
Out
RD4


25
LCD DB5
Out
RD5


26
LCD DB6
Out
RD6


27
LCD DB7
Out
RD7









The external memory 122 is a Microchip 24AA64 I2C EEPROM. The memory 122 is connected to the controller 120 via the I2C serial communications bus 192. The memory 122 has 64K bits of EEPROM and is used for the storage of the patient data. The operation of this device is limited to the low speed bus operation due to the use of a 4 MHz crystal. The LED 124 is a Hitachi 44780 compatible LCD operating in 8 bit parallel mode. The Hitachi LCD is an industry standard, and was chosen because any 14×2 LCD could then easily be substituted. A Dallas Semiconductor DS 1307 I2C real time clock 194 is provided, which is connected to the I2C bus 192 along with the EEPROM memory 122. This clock 194 is used to record, to the nearest hour, when the actual stretch sessions were performed. This allows the PC software for the computer 112 (see FIG. 3) to group the stretches into sessions.


This micro-controller 120 has an onboard poll capable of 8-channel analog to digital conversion at 10-bit resolution making it a powerful tool in data acquisition. The controller 120 also supports both SCI and I2C serial communication. The SCI module of the controller 120 is used to communicate with the computer 112 through standard RS-232 port of a RS-232 communications interface 196. This communications, for example, allows for further analysis of the data by the physical therapist or doctor. The I2C protocol will used to interface with the memory 122 and the real time clock 194. The use of external memory 122 will be needed as the 128 bytes of EEPROM storage for the internal memory of the controller 120 is insufficient to store the data acquired from the sensors. The controller 120 is electrically coupled to a Piezo buzzer (not shown) via the pin RCO being connected to the terminal 199.


In FIG. 8, there is also shown the header 198 (including insulated terminals or leads) for connecting the LCD 124 of FIGS. 4 and 5. Also, there is shown a header 200 for connecting with the sensors (terminals J3-J6) and the computer 112 (for selecting the mode of operation via terminals J8 and J9). The sensor hardware schematic 210, including the header 200, is shown in FIG. 9 in more detail. Referring to FIG. 9, the terminals J1-J12 of header 200 are electrically coupled to the ports of the controller 120 as specified in TABLE 11. A first variable resistor RV1 comprises the resistance of the position sensor 106 (FIG. 3) and a second variable resistor RV2 is used to match the resistance to create a voltage divider as previously described, to form a potentiometer, used with the position sensor 106 (FIG. 3).


In an alternative embodiment of the sensor hardware of FIG. 9, it is contemplated that the expansion terminals J5-J7 may be used for additional sensors, including blood pressure, heart rate, and stress indicators. To accomplish this, the sensor bus is modified to use both 3.3 and 5.0 volt supply lines to allow for the plug-in of multiple expansion sensors. With a selectable supply voltage, a universal connector is provided for both patient data acquisition in the treatment mode and for data transmission to the doctor's office in the data transmission mode selected by cable.


Referring to FIG. 3, the temperature sensor 108 is a Dallas Semiconductor LM34DZ temperature sensor. This temperature sensor was not used to measure the patient's actual temperature but was used to confirm that the patient was actually using the device.


With reference to FIG. 3, the patient monitoring system software running on the computer 112 briefly will be described. The software application provides a therapist a way of obtaining the data stored on the data acquisition unit 104 and presents it in a meaningful way. One function of the Patient Monitoring System software is the ability to view patient records. The system checks to ensure that all fields are entered and informs the user if one or more of the fields are blank. In addition, the system checks the patient name entered against the array of current patient names. If the entered name is invalid, the system reports no patient found. Otherwise, the system uses the “Patient ID” field from the array to access the data file for that particular patient. This file contains all of the information obtained from the data acquisition unit (FIG. 3) from previous visits. The system then displays the contents of the file in the grid at the bottom of the form. The grid is another built-in control of Visual Basic 6.0 called the “Microsoft FlexGrid Control 6.0”. In addition, the system displays other patient information such as the name of that patient's physician and the date that patient received their orthosis device.


Another function provided by the system software is the form for actually acquiring data from the data acquisition unit 104 (FIG. 3). The screen layout is very similar to that of the form for viewing patient records that are already stored in the system. This form also uses a grid to display the data once it has been obtained from the Data Acquisition Unit. In order to facilitate reading from a communications port, Visual Basic has a control entitled “Microsoft Comm Control 6.0”. This control allows communication between the personal computer 112 (FIG. 3) and any device attached to a designated communications port. The user also has the option to change what communications port the system will look for the data acquisition unit on in case other communications ports are already in use by that individual's computer. By default, this is set to COM1.


When the user clicks on the “Acquire” command button, as in other forms, the system checks to see first if all proper text fields have been filled in, and then if the patient name entered is valid. Also, it informs the user to make sure that the data acquisition unit is securely connected to the selected communication port. Next, the system sends out a zero byte on the communication port, which informs the data acquisition unit to begin sending data. The patient monitoring system software then reads in the raw data from the unit, one byte at a time, and stores it into a temporary file called “output.dat”. After the data acquisition unit has completed sending all of its data, the system software sends out a byte equal to 0xFF in hexadecimal to inform the data acquisition unit to wipe out its memory and the serial communication is complete.


The next major task that the software application does involves manipulating data. This includes converting the raw data obtained from the data acquisition unit into meaningful values, saving them in the proper patient's file, and displaying them in the grid for the user to examine. First, the system goes through and converts all of the data received from the data acquisition unit into actual integers, instead of the binary form that they are initially sent in. The first major changing of any data occurs with the data representing the time and the date. Actually, the date is composed of a byte representing the month, and one representing the day. The data acquisition unit transmits all three of these values: month, day, and hour, in BCD form (see TABLE I). To do this, the system subtracts a factor of six from the data based on the value of its upper four bits. For example, the BCD value of thirty-one is stored in binary as 0011 0001. The system will subtract eighteen (six times the value of the upper four bits, three) from the integer value of the number, forty-nine, to produce the correct result of thirty-one.


The next major conversion occurs with the “Position” readings taken by the position sensor 106 (FIG. 3) and transmitted from the data acquisition unit 104. The data acquisition unit transmits values called Stretch_Min and Stretch_Max during its serial communication with the patient monitoring software. The difference between these two numbers is computed and adjusted to fit a scale of based on the particular device. For example, a one orthosis device allows a range of motion from one hundred thirty-eight to negative ten degrees. Next, each “Position” value is then adjusted accordingly to fit within these two values. In reality, this conversion may not be exactly linear, but since the position sensor need not be as highly accurate as other more expensive models, assuming linearity in this case is acceptable.


The final conversion that the system makes involves the readings from the temperature sensor 108 (see FIG. 3). Based on the specifications of the temperature sensor itself, the voltage increases ten millivolts per degree. The system then fits the binary data into the range of acceptable values. For the most part, the temperature data should be relatively constant. Its primary purpose is to ensure that the patient is actually wearing the device while using it, instead of simply turning it on to take false readings. As a result, the therapist would be able to tell if a reading was false by seeing if any of the temperature values were conspicuously above or below any realistic, expected values. This helps to ensure proper adherence to the stretching protocol.


In FIG. 10 an alternative embodiment of the monitoring system 100 shown in FIG. 3 is shown. In this alternative embodiment, the device type sensor 110 shown in FIG. 3 is used. Although shown in FIG. 3, the sensor 110 was not used in the first embodiment, in that the device ID was downloaded by the application software operating on the computer 112 to the data acquisition unit 104. But in this alternative embodiment, the device ID is obtained via the sensor 110. Referring to FIG. 10, each orthosis device is given its own unique resistor R2. Typically, this resistor is mounted on orthosis separate from the data acquisition unit 104, so that the data acquisition unit 104 is not device specific. In the case of the orthosis 10, the resistor R2 enclosed in a protective casing and the casing is mounted to one of the arms 22 or 40. The resistor R2 is electrically coupled on one side to a lead 210 extending from the casing and is electrically coupled at its other side to ground. The lead 210 is connected to the first expansion terminal J5 shown in FIG. 9. The device sensor 110 includes additional circuitry located within the data acquisition unit 104. This additional circuitry includes a node 212, a capacitor C (having a value of 0.1 uF) electrically coupled between the node 212 and electrical ground, a resistor R1 electrically coupled between the node 212 and a voltage source Vcc and a 10 bit Analog-to-digital converter (ADC) 214 connected to node 212.


When the node 212 is electrically coupled to the lead 210 of the resistor R2, the resistor R2 and Care in parallel. The voltage VADC applied to the ADC 214 is as follows:






VADC
=


(


R





2



R





2

+

R





1



)



(
Vcc
)







In this case the following conditions apply: no cable resistance, so that when R2=infinity, VADC=Vcc; for the PC link cable, when resistor R2=0, then VADC=0 and that there is a valid orthosis device with an embedded resister R2. In this case, the resolution of this device sensor 110 at Vcc=5V would be 210=1024, so that 5/1024=5 mV. The following TABLE III provides illustrative values used to identify different orthosis devices (R2 is provided in kilo ohms, VADC and Range are provided in volts, and R1=10 kilo ohms):











TABLE III





Device - R2
VADC
Range

















440
4.89
4.85-4.91


150
4.76
 4.7-4.82


100
4.54
4.45-4.65


50
4.17
4.09-4.35


32
3.8
3.61-4.06


18
3.21
2.96-3.54


10
2.5
2.23-2.95


5.8
1.83
1.59-2.2 


3.3
1.24
1.05-1.55


1.8
0.96
0.63-1.0 


1.0
0.45
0.37-0.6 


0.5
0.238
0.195-0.55 


0.28
0.136
0.110-0.18 









As discussed above, this alternative embodiment is utilizable where it is desirable to identify a given orthosis device out of a plurality of possible orthosis devices so as to eliminate the need for downloading parameters, commands and/or firmware for that specific orthosis device. In other words, like the use of the temperature sensor, the orthosis devices making use of this embodiment of the monitor 100 do not need to be directed toward those implementing stretching exercises.


An additional feature that may be added to the Patient Monitoring System software is a “non-programmers” interface wherein a Microsoft® Windows based graphical user interface (GUI) is provided with a plurality of predetermined unit configurations for the monitor system 100 of FIG. 3 are provided in a first window. The user is able to select one of these unit configurations by clicking on the same and dragging the same to a selection window. This feature allows for unit configuration by a therapist or family configuration by an Original Equipment Manufacturer (OEM) without the need for factory assistance. Additionally, a third window may be provided wherein the user may select other system or user variables, by once again dragging the same from the third window to the selection window.


Referring to FIG. 3, aspects of the monitor system 100, such as the device type detector 110 (FIG. 3), may be used with devices other than the stretching orthosis shown by the illustrative embodiment of FIG. 6. Other possible applications for these aspects would be to other types of orthosis devices, such as isometric orthosis devices. Via software, the monitor system 100 may be configured to work with any rehabilitation device having position measurements. The monitor also has the ability to accept other sensor inputs not accounted for previously. The firmware and hardware of the monitor system 100 already provides for the possibility of up to 5 sensor inputs, thus only minor changes in the PC software are necessary in order to view data output from other sensor inputs, such as mentioned with respect to FIG. 9.


After thorough testing of the data transfer capabilities of the monitor 102, it has been concluded that a higher crystal frequency may be more suitable for transmitting the required data over the RS-232 port. Operating the micro-controller at 20 MHz would significantly decrease the data transfer time and would not add much to the cost of the product, but allow the I2C bus to operate in high speed mode as well as allow a higher baud rate for the RS-232 communications.


Having a spring measure the amount of extension/flexion may be a very cost-effective solution for the position sensor 106 of FIG. 6; however, those skilled in the art will recognize that more accurate position sensors may be used.


While various values, scalar and otherwise, may be disclosed herein, it is to be understood that these are not exact values, but rather to be interpreted as “about” such values. Further, the use of a modifier such as “about” or “approximately” in this specification with respect to any value is not to imply that the absence of such a modifier with respect to another value indicated the latter to be exact.


Changes and modifications can be made by those skilled in the art to the embodiments as disclosed herein and such examples, illustrations, and theories are for explanatory purposes and are not intended to limit the scope of the claims. For example, one embodiment of the invention has been described as utilizing cables to transfer data. In this regard, the data transfer can be implemented using fiber optics, a phone line, a cellular phone link, an RF link, and/or other communications channels. Thus, the present invention also envisions the use of wireless means for data transfer. Such wireless means could use technology like the CENTRINO mobile technology and personal digital assistants (PDA's).


Furthermore, the invention has been described as being used by patients and health care professionals. However, limited access to the system and/or data by others could be allowed if authorized by the patient and/or health care professional. On such scenario in which limited access could be granted would be for proof of assurance to an insurance company for a worker's compensation carrier. Others may also have a need to have some assurance that a patient is indeed following through with a compliance protocol.


Although the monitoring system and method have been described primarily in the context of an orthosis device, other applications are contemplated by the present invention. These include other aspects of physical therapy; electrostimulation; bone growth stimulation; drug delivery systems; cardiac rehabilitation; generalized rehabilitation, including compliance; implantable pumps, such as insulin pumps for diabetics; intravenous or implantable pump medication; and implantable or wearable chemical sensors to monitor various physiological parameters such as blood coagulation, blood profile, and blood enzyme content.


For example, in known pharmaceutical delivery systems, a rotatable wheel has a number of compartments, each containing an incremental dose of medications. As programmed, a door opens at a prescribed time and the pill either by weight or by size would be opened up for patient access.


With the present invention, we can externally monitor these dmg deliveries systems or internally monitor them. The delivery systems could be used with an implantable pump or implantable blood chemistry sensor. A wireless readout from the pump or sensor could attach, for example, to a wrist watch which would monitor the compliance through a digital readout. A patient could monitor their own blood chemistries or response to particular medications and then these results would be broadcast to physician, extended care, nurse practitioner, nurse, insurance carrier, etc. This would then monitor the changes to a specific drug and then monitor the serum chemistries, for example, blood sugar, etc. These are monitored and then the patient can be monitored through a wireless format to see how they respond to certain medications and have an instant readout through this chemistry monitor without actually having the patient in the office or in the hospital. If the response is not as desired, the delivery protocol can be remotely changed based on the measurements.


In light of the foregoing, it should be understood that while various descriptions of the present invention are described above, the various features could be used singly or in any combination thereof. Therefore, this invention is not to be limited to only the specifically preferred embodiments depicted herein.


Further, it should be understood that variations and modifications within the spirit and scope of the invention might occur to those skilled in the art to which the invention pertains. Accordingly, all expedient modifications readily attainable by one versed in the art from the disclosure set forth herein that are within the scope and spirit of the present invention are to be included as further embodiments of the present invention. The scope of the present invention is accordingly defined as set forth in the appended claims.

Claims
  • 1. A drug delivery system comprising: a drug delivery apparatus including at least one sensor configured to detect at least one of a drug delivery parameter and patient data; anda portable communication device communicatively coupled to the drug delivery apparatus, the portable communication device comprising: an input device configured to receive data from the drug delivery apparatus, wherein the data includes at least one of the detected drug delivery parameter and patient data; andan output device coupled to the input device and configured to display the received data.
  • 2. A drug delivery system in accordance with claim 1, wherein the portable communication device further comprises a communications component configured to transmit a delivery protocol to the drug delivery apparatus.
  • 3. A drug delivery system in accordance with claim 2, wherein the communications component is further configured to transmit, to an external source, an indication that a change be made to the delivery protocol based on the received data.
  • 4. A drug delivery system in accordance with claim 2, wherein the communications component is configured to transmit the received data to an external source.
  • 5. A drug delivery system in accordance with claim 1, wherein the drug delivery apparatus is configured to change the drug delivery protocol based on data received from an external source.
  • 6. A drug delivery system in accordance with claim 1, wherein the drug delivery apparatus is at least one of implanted in a patient and an insulin pump.
  • 7. A drug delivery system in accordance with claim 1, wherein the portable communication device is at least one of a laptop, smartphone, cellular telephone, and personal digital assistant (PDA).
  • 8. One or more non-transitory computer-readable storage media having computer-executable instructions embodied thereon, wherein when executed by a processor, the computer-executable instructions cause the processor to: receive, by an input device, data from at least one sensor of a drug delivery apparatus, wherein the data includes at least one of a drug delivery parameter and patient data;display, on an output device, the received data from the at least one sensor; andtransmit a delivery protocol to the drug delivery apparatus.
  • 9. One or more non-transitory computer-readable storage media according to claim 8, wherein the computer-executable instructions cause the processor to receive data from at least one sensor via a wireless connection.
  • 10. One or more non-transitory computer-readable storage media according to claim 8, wherein the computer-executable instructions cause the processor to transmit the received data to an external source.
  • 11. One or more non-transitory computer-readable storage media according to claim 8, wherein the computer-executable instructions cause the processor to receive a delivery protocol for the drug delivery system.
  • 12. A portable communication device configured to monitor a patient therapy system, the mobile communication device comprising: an input device configured to receive data from at least one sensor of a patient therapy system, wherein the data includes at least one of therapy data and patient data; andan output device coupled to the processor and configured to display the received data.
  • 13. A portable communication device in accordance with claim 12, wherein the input device is further configured to receive data from at least one sensor via a wireless connection.
  • 14. A portable communication device in accordance with claim 12, wherein the input device is further configured to receive data from at least one sensor via a wired connection.
  • 15. A portable communication device in accordance with claim 12, wherein the therapy data includes at least one of an amount of drug delivered to a patient, an amount of electrostimulation delivered to a patient, and an amount of bone growth stimulation delivered to a patient.
  • 16. A portable communication device in accordance with claim 12, wherein the patient data includes at least one of a blood chemistry, blood coagulation, a blood profile, a blood sugar concentration, and blood enzyme content.
  • 17. A portable communication device in accordance with claim 12, further comprising a communications component configured to transmit the received data to an external source.
  • 18. A portable communication device in accordance with claim 17, wherein the communications component is further configured to wirelessly transmit the received data to an external source.
  • 19. A portable communication device in accordance with claim 17, wherein the communications component is configured to transmit a delivery protocol to the patient therapy system.
  • 20. A portable communication device in accordance with claim 19, wherein the input device is configured to receive a delivery protocol for the patient therapy system.
  • 21. A portable communication device in accordance with claim 12, wherein the portable communication device is at least one of a laptop, smartphone, cellular telephone, and personal digital assistant (PDA).
CROSS REFERENCE TO RELATED APPLICATIONS

The present application is a continuation application of U.S. patent application Ser. No. 11/625,879 filed on Jan. 23, 2007, which is a continuation of U.S. patent application Ser. No. 10/421,965, now issued as U.S. Pat. No. 7,182,738. The contents of each of the above-identified applications are herein incorporated by reference in their entirety.

US Referenced Citations (720)
Number Name Date Kind
3608641 Cottrell Sep 1971 A
3870034 James Mar 1975 A
4031365 Raggiotti Jun 1977 A
4052979 Scherr Oct 1977 A
4129125 Lester Dec 1978 A
4148304 Mull Apr 1979 A
4151831 Lester May 1979 A
4192000 Lipsey Mar 1980 A
4312358 Barney Jan 1982 A
4364398 Sassi Dec 1982 A
4367752 Jimenez et al. Jan 1983 A
4377171 Wada Mar 1983 A
4407295 Steuer Oct 1983 A
4488558 Simbruner Dec 1984 A
4509531 Ward Apr 1985 A
4531527 Reinhold Jul 1985 A
4539994 Baumbach Sep 1985 A
4557273 Stoller Dec 1985 A
4601468 Bond et al. Jul 1986 A
4608987 Mills Sep 1986 A
4622979 Katchis Nov 1986 A
4627738 Kao Dec 1986 A
4672977 Kroll Jun 1987 A
4676254 Frohn Jun 1987 A
4711450 McArthur Dec 1987 A
4757453 Nasiff Jul 1988 A
RE32758 Zartman Oct 1988 E
4784162 Ricks Nov 1988 A
4788627 Ehlert Nov 1988 A
4803625 Fu Feb 1989 A
4807601 Wright Feb 1989 A
4817940 Shaw et al. Apr 1989 A
4819860 Hargrove Apr 1989 A
4827943 Bornn May 1989 A
4828257 Dyer May 1989 A
4883063 Bernard Nov 1989 A
4891756 Williams, III Jan 1990 A
4917108 Mault Apr 1990 A
4934694 McIntosh Jun 1990 A
4951197 Mellinger Aug 1990 A
4958645 Cadell Sep 1990 A
4966154 Cooper Oct 1990 A
4981139 Pfohl Jan 1991 A
4986261 Iams Jan 1991 A
5007427 Suzuki Apr 1991 A
5012411 Policastro Apr 1991 A
5012819 Marras May 1991 A
5013007 Whiteside May 1991 A
5019673 Juskey May 1991 A
5020795 Airy Jun 1991 A
5027824 Dougherty Jul 1991 A
5038792 Mault Aug 1991 A
5040541 Poppendiek Aug 1991 A
5050612 Matsumura Sep 1991 A
5052375 Stark Oct 1991 A
5072458 Suzuki Dec 1991 A
5100403 Hotchkiss et al. Mar 1992 A
5135311 Alpert Aug 1992 A
5143088 Marras Sep 1992 A
5148002 Kuo Sep 1992 A
5167612 Bonutti Dec 1992 A
5178155 Mault Jan 1993 A
5179958 Mault Jan 1993 A
5201772 Maxwell Apr 1993 A
5209223 McGorry et al. May 1993 A
5213094 Bonutti May 1993 A
5216599 Uebe Jun 1993 A
5224479 Sekine Jul 1993 A
5246643 Inaba Sep 1993 A
5252102 Singer Oct 1993 A
5255188 Telepko Oct 1993 A
5263491 Thornton Nov 1993 A
5285398 Janik Feb 1994 A
5285773 Bonutti Feb 1994 A
5297540 Kaiser Mar 1994 A
5305244 Newman Apr 1994 A
5320641 Riddle et al. Jun 1994 A
5331851 Parviainen et al. Jul 1994 A
5335664 Nagashima Aug 1994 A
5353793 Bornn Oct 1994 A
5365947 Bonutti Nov 1994 A
5387170 Rawls et al. Feb 1995 A
5395303 Bonutti Mar 1995 A
5410471 Alyfuku Apr 1995 A
5426130 Thurber Jun 1995 A
5435315 McPhee Jul 1995 A
5445149 Rotolo Aug 1995 A
5452205 Telepko Sep 1995 A
5453075 Bonutti Sep 1995 A
5454773 Blanchard Oct 1995 A
5456262 Birnbaum Oct 1995 A
5456268 Bonutti Oct 1995 A
5458123 Unger Oct 1995 A
5466213 Hogan Nov 1995 A
5469861 Piscopo Nov 1995 A
5474090 Begun Dec 1995 A
5474552 Palti Dec 1995 A
5476103 Nahsner Dec 1995 A
5484389 Stark Jan 1996 A
5491474 Suni Feb 1996 A
5491651 Janik Feb 1996 A
5503619 Bonutti Apr 1996 A
5507288 Bocker Apr 1996 A
5511553 Segalowitz Apr 1996 A
5515858 Myllymaki May 1996 A
5515865 Scanlon May 1996 A
5523730 Van Zeeland Jun 1996 A
5524618 Pottgen Jun 1996 A
5535274 Braitberg Jul 1996 A
5538486 France Jul 1996 A
5539706 Takenaka Jul 1996 A
5555490 Carroll Sep 1996 A
5559497 Hong Sep 1996 A
5564429 Bornn Oct 1996 A
5566679 Herriott Oct 1996 A
5581238 Chang Dec 1996 A
5581492 Janik Dec 1996 A
5583758 McIlroy Dec 1996 A
5594638 Iliff Jan 1997 A
5611085 Rasmussen Mar 1997 A
5611764 Bonutti Mar 1997 A
5617477 Boyden Apr 1997 A
5622180 Tammi Apr 1997 A
5626537 Danyo May 1997 A
5645068 Mezack Jul 1997 A
5652570 Lepkofker Jul 1997 A
5655997 Greenberg et al. Aug 1997 A
5660176 Iliff Aug 1997 A
5663703 Pearlman Sep 1997 A
5666096 Van Zeeland Sep 1997 A
5670944 Myllymaki Sep 1997 A
5673691 Abrams Oct 1997 A
5673692 Schulze Oct 1997 A
5682327 Telepko Oct 1997 A
5685830 Bonutti Nov 1997 A
5686516 Tzur Nov 1997 A
5687734 Dempsey Nov 1997 A
5692501 Minturn Dec 1997 A
5697791 Nashner Dec 1997 A
5701894 Cherry Dec 1997 A
5704350 Williams, III Jan 1998 A
5706822 Khavari Jan 1998 A
5719743 Jenkins Feb 1998 A
5724025 Tavori Mar 1998 A
5724968 Iliff Mar 1998 A
5726631 Lin Mar 1998 A
5729203 Oka Mar 1998 A
5729479 Golan Mar 1998 A
5730140 Fitch Mar 1998 A
5738104 Lo Apr 1998 A
5741217 Gero Apr 1998 A
5746704 Schenck et al. May 1998 A
5752976 Duffin May 1998 A
5771001 Cobb Jun 1998 A
5778882 Raymond Jul 1998 A
5798907 Janik Aug 1998 A
5803915 Kremenchugsky Sep 1998 A
5813766 Chen Sep 1998 A
5813994 Pottgen Sep 1998 A
5823975 Stark Oct 1998 A
5827180 Goodman Oct 1998 A
5828943 Brown Oct 1998 A
5830160 Reinkensmeyer Nov 1998 A
5832296 Wang Nov 1998 A
5832448 Brown Nov 1998 A
5836300 Mault Nov 1998 A
5839901 Karkanen Nov 1998 A
5848979 Bonutti Dec 1998 A
5853005 Scanlon Dec 1998 A
5855550 Lai Jan 1999 A
5857939 Kaufman Jan 1999 A
5857967 Frid Jan 1999 A
5860957 Jacobsen et al. Jan 1999 A
5862803 Besson Jan 1999 A
5865733 Malinouskas Feb 1999 A
5868669 Iliff Feb 1999 A
5868671 Mahoney Feb 1999 A
5871451 Unger Feb 1999 A
5876350 Lo Mar 1999 A
5879163 Brown Mar 1999 A
5879309 Johnson Mar 1999 A
5884198 Kese Mar 1999 A
5888172 Andrus Mar 1999 A
5890997 Roth Apr 1999 A
5897493 Brown Apr 1999 A
5899855 Brown May 1999 A
5902250 Verrier May 1999 A
5908396 Hayakawa Jun 1999 A
5910107 Iliff Jun 1999 A
5912865 Ortega Jun 1999 A
5913310 Brown Jun 1999 A
5919141 Money Jul 1999 A
5924979 Swedlow Jul 1999 A
5929782 Stark Jul 1999 A
5931763 Alessandri Aug 1999 A
5931791 Saltzstein Aug 1999 A
5933136 Brown Aug 1999 A
5935060 Iliff Aug 1999 A
5941837 Amano Aug 1999 A
5951300 Brown Sep 1999 A
5954510 Merrill Sep 1999 A
5956501 Brown Sep 1999 A
5957854 Besson Sep 1999 A
5959529 Kail Sep 1999 A
5959611 Smailagic Sep 1999 A
5960380 Flentov Sep 1999 A
5960403 Brown Sep 1999 A
5974262 Fuller Oct 1999 A
5976083 Richardson Nov 1999 A
5980429 Nashner Nov 1999 A
5980435 Joutras Nov 1999 A
5989157 Walton Nov 1999 A
5990772 Van Zeeland Nov 1999 A
6022315 Iliff Feb 2000 A
6030342 Amano Feb 2000 A
6032119 Brown Feb 2000 A
6047203 Sackner Apr 2000 A
6050940 Braun Apr 2000 A
6053872 Mohler Apr 2000 A
6059576 Brann May 2000 A
6059692 Hickman May 2000 A
6066075 Poulton May 2000 A
6067468 Korenman May 2000 A
6069552 Van Zeeland May 2000 A
6071236 Iliff Jun 2000 A
6080106 Lloyd Jun 2000 A
6091973 Colla Jul 2000 A
6095949 Arai Aug 2000 A
6101407 Groezinger Aug 2000 A
6101478 Brown Aug 2000 A
6113540 Iliff Sep 2000 A
6113562 Bonutti Sep 2000 A
6126595 Amano Oct 2000 A
6135107 Mault Oct 2000 A
6135951 Richardson Oct 2000 A
6138079 Putnam Oct 2000 A
6139494 Cairnes Oct 2000 A
6154668 Pedersen Nov 2000 A
6156461 Grenon Dec 2000 A
6168563 Brown Jan 2001 B1
6175608 Pyles Jan 2001 B1
6184797 Stark Feb 2001 B1
6190314 Ark Feb 2001 B1
6198394 Jacobsen Mar 2001 B1
6206829 Iliff Mar 2001 B1
6208900 Ecker Mar 2001 B1
D439981 Kasabach Apr 2001 S
6221011 Bardy Apr 2001 B1
6225901 Kail May 2001 B1
6225980 Weiss May 2001 B1
6228000 Jones May 2001 B1
6234964 Iliff May 2001 B1
6240323 Calenzo May 2001 B1
6246900 Cosman Jun 2001 B1
6247647 Courtney Jun 2001 B1
6248065 Brown Jun 2001 B1
6251048 Kaufman Jun 2001 B1
6254536 deVito Jul 2001 B1
6254815 Cheperak Jul 2001 B1
6265978 Atlas Jul 2001 B1
6266623 Vock Jul 2001 B1
6267735 Blanchard et al. Jul 2001 B1
6270455 Brown Aug 2001 B1
6270456 Iliff Aug 2001 B1
6285897 Kilcoyne Sep 2001 B1
6287252 Lugo Sep 2001 B1
6290646 Cosentino Sep 2001 B1
6290650 Butterfield Sep 2001 B1
6292698 Duffin Sep 2001 B1
6296595 Stark Oct 2001 B1
6298218 Lowe Oct 2001 B1
6302844 Walker Oct 2001 B1
6305071 Van Zeeland Oct 2001 B1
6306088 Krausman Oct 2001 B1
6312363 Watterson Nov 2001 B1
6315719 Rode Nov 2001 B1
D451604 Kasabach Dec 2001 S
6327495 Iwabuchi Dec 2001 B1
6334848 Wong Jan 2002 B1
6336900 Alleckson Jan 2002 B1
6339720 Anzellini Jan 2002 B1
6341229 Akiva Jan 2002 B1
6341295 Stotler Jan 2002 B1
6356940 Short Mar 2002 B1
6364834 Reuss Apr 2002 B1
6366871 Geva Apr 2002 B1
6368287 Hadas Apr 2002 B1
6371123 Stark Apr 2002 B1
6377162 Delestienne Apr 2002 B1
6377178 Detoro Apr 2002 B1
6384755 Hayden May 2002 B1
6385473 Haines May 2002 B1
6386041 Yang May 2002 B1
6392515 Van Zeeland May 2002 B1
6402689 Scarantino et al. Jun 2002 B1
6411567 Niemiec et al. Jun 2002 B1
D460971 Sica Jul 2002 S
6416471 Kumar Jul 2002 B1
6418181 Nissila Jul 2002 B1
6420959 Lizzi Jul 2002 B1
6434212 Pyles Aug 2002 B2
6436058 Krahner Aug 2002 B1
6438407 Ousdigian et al. Aug 2002 B1
6450922 Henderson Sep 2002 B1
6450953 Place Sep 2002 B1
6453195 Thompson Sep 2002 B1
6454707 Casscells Sep 2002 B1
6454708 Ferguson Sep 2002 B1
6464687 Ishikawa et al. Oct 2002 B1
6466232 Newell Oct 2002 B1
6468210 Iliff Oct 2002 B1
6468222 Mault Oct 2002 B1
6473483 Pyles Oct 2002 B2
6475143 Iliff Nov 2002 B2
6478735 Pope Nov 2002 B1
6478736 Mault Nov 2002 B1
6482156 Iliff Nov 2002 B2
6486801 Jones Nov 2002 B1
6494829 New Dec 2002 B1
6502577 Bonutti Jan 2003 B1
6509659 Carroll Jan 2003 B1
6513532 Mault Feb 2003 B2
6514200 Khouri Feb 2003 B1
6516289 David Feb 2003 B2
6524241 Iliff Feb 2003 B2
6527711 Stivoric Mar 2003 B1
6527713 Iliff Mar 2003 B2
6532381 Bayer Mar 2003 B2
6533731 Pottgen Mar 2003 B2
6539336 Vock Mar 2003 B1
6547745 Rubinstein Apr 2003 B1
6551251 Zuckerwar Apr 2003 B2
6551252 Sackner Apr 2003 B2
6553251 Lahdesmaki Apr 2003 B1
6558320 Causey May 2003 B1
6558352 Hogan May 2003 B1
6569093 Iliff May 2003 B2
6569094 Suzuki May 2003 B2
6571200 Mault May 2003 B1
6579231 Phipps Jun 2003 B1
6584344 Hannula Jun 2003 B2
6589229 Connelly Jul 2003 B1
6595901 Reinbold et al. Jul 2003 B2
6595929 Stivoric Jul 2003 B2
6597944 Hadas Jul 2003 B1
6601016 Brown et al. Jul 2003 B1
6602191 Quy Aug 2003 B2
6605038 Teller Aug 2003 B1
6605044 Bimbaum Aug 2003 B2
6607484 Suzuki Aug 2003 B2
6610012 Mault Aug 2003 B2
6611206 Milanski Aug 2003 B2
6611783 Kelly Aug 2003 B2
6613000 Reinkensmeyer et al. Sep 2003 B1
6616613 Goodman Sep 2003 B1
6626800 Casler Sep 2003 B1
6635015 Sagel Oct 2003 B2
6641532 Iliff Nov 2003 B2
6656125 Misczynski Dec 2003 B2
6659918 Schiessl Dec 2003 B2
6662032 Gavish et al. Dec 2003 B1
6665174 Derr Dec 2003 B1
6665559 Rowlandson Dec 2003 B2
6669600 Warner Dec 2003 B2
6690959 Thompson Feb 2004 B2
6694182 Yamazaki Feb 2004 B1
6702719 Brown et al. Mar 2004 B1
6712615 Martin Mar 2004 B2
6714859 Jones Mar 2004 B2
6730027 Iliff May 2004 B2
6734802 Halleck May 2004 B2
6736759 Stubbs et al. May 2004 B1
6746371 Brown et al. Jun 2004 B1
6746399 Iliff Jun 2004 B2
6755795 Marmaropoulos Jun 2004 B2
6764447 Iliff Jul 2004 B2
6767325 Iliff Jul 2004 B2
6773344 Gabai Aug 2004 B1
6786847 Morgan et al. Sep 2004 B1
6790178 Mault Sep 2004 B1
6808473 Hisano Oct 2004 B2
6817980 Iliff Nov 2004 B2
6834436 Townsend Dec 2004 B2
6842877 RObarts Jan 2005 B2
6849045 Iliff Feb 2005 B2
6852085 Rubinstein Feb 2005 B2
6872187 Stark et al. Mar 2005 B1
6874127 Newell Mar 2005 B2
6890285 Rahman May 2005 B2
6890312 Priester et al. May 2005 B1
6904359 Jones Jun 2005 B2
6920348 Vasin Jul 2005 B2
6921351 Hickman et al. Jul 2005 B1
6923324 Kanai Aug 2005 B2
6942615 Suzuki Sep 2005 B2
6949081 Chance Sep 2005 B1
6952645 Jones Oct 2005 B1
6959259 Vock Oct 2005 B2
6968375 Brown Nov 2005 B1
6969365 Scorvo Nov 2005 B2
6984886 Ahn Jan 2006 B2
7020508 Stivoric Mar 2006 B2
7024245 Lebel et al. Apr 2006 B2
7030781 Jones Apr 2006 B2
7056297 Dohno Jun 2006 B2
7060216 Schuumans Jun 2006 B2
7073129 Robarts Jul 2006 B1
7092846 Vock Aug 2006 B2
7101752 Park Sep 2006 B2
7144151 Saaski Dec 2006 B2
7153262 Stivoric Dec 2006 B2
7171331 Vock Jan 2007 B2
7182738 Bonutti Feb 2007 B2
7196972 Pitocco Mar 2007 B2
7204814 Peles Apr 2007 B2
7210240 Townsend May 2007 B2
7218232 DiSilvestro May 2007 B2
7222054 Geva May 2007 B2
7242981 Ginggen Jul 2007 B2
7254448 Almendinger et al. Aug 2007 B2
7261690 Teller Aug 2007 B2
7276802 Hall Oct 2007 B2
7285090 Stivoric Oct 2007 B2
7297111 Iliff Nov 2007 B2
7300402 Iliff Nov 2007 B2
7306560 Iliff Dec 2007 B2
7306567 Loree Dec 2007 B2
7336187 Hubbard Feb 2008 B2
7343260 Kahn Mar 2008 B1
7344496 Iliff Mar 2008 B2
7347874 DiSilvestro Mar 2008 B2
7364445 Ni Apr 2008 B1
7400970 Jones Jul 2008 B2
7416537 Stark Aug 2008 B1
7429255 Thompson Sep 2008 B2
7454002 Gardner Nov 2008 B1
7457719 Kahn Nov 2008 B1
7485095 Shusterman Feb 2009 B2
7502643 Farringdon Mar 2009 B2
7526335 Ferek-Petric Apr 2009 B2
7610099 Almendinger et al. Oct 2009 B2
7647195 Kahn Jan 2010 B1
7647196 Kahn Jan 2010 B2
7653508 Kahn Jan 2010 B1
7662065 Kahn Feb 2010 B1
7672726 Ginggen Mar 2010 B2
7676384 Baker Mar 2010 B2
7689437 Teller Mar 2010 B1
7690556 Kahn Apr 2010 B1
7698830 Townsend Apr 2010 B2
7704282 Disilvestro Apr 2010 B2
7705723 Kahn Apr 2010 B2
7713229 Veit et al. May 2010 B2
7720696 Berger May 2010 B1
7723162 Anderson May 2010 B2
7733224 Tran Jun 2010 B2
7747735 Kahn Jun 2010 B1
7751907 Blomquist Jul 2010 B2
7753861 Kahn Jul 2010 B1
7766794 Oliver Aug 2010 B2
7769187 Farrar Aug 2010 B1
7769600 Iliff Aug 2010 B2
7788059 Kahn Aug 2010 B1
7800044 Kahn Sep 2010 B1
7825815 Shears Nov 2010 B2
7839279 Kahn Nov 2010 B2
7841967 Kahn Nov 2010 B1
7849184 Kahn Dec 2010 B1
D631552 Kasabach Jan 2011 S
D632396 Kasabach Feb 2011 S
7881902 Kahn Feb 2011 B1
7895053 Holland et al. Feb 2011 B2
7907901 Kahn Mar 2011 B1
7917768 Kahn Mar 2011 B2
7931613 Haueter Apr 2011 B2
7959567 Stivoric Jun 2011 B2
7970586 Kahn Jun 2011 B1
7981067 Bonutti Jul 2011 B2
7982770 Kahn Jul 2011 B1
7987009 Liebchen Jul 2011 B2
7987070 Kahn Jul 2011 B2
7993276 Nazarian Aug 2011 B2
7993291 Karkanias Aug 2011 B2
D645968 Kasabach Sep 2011 S
8015138 Iliff Sep 2011 B2
8019582 Iliff Sep 2011 B2
8040382 Kahn Oct 2011 B2
8047966 Dorogusker Nov 2011 B2
8049614 Kahn Nov 2011 B2
8060378 Iliff Nov 2011 B2
8064759 Kahn Nov 2011 B1
8073707 Teller Dec 2011 B2
8083643 Ng Dec 2011 B2
8083741 Morgan Dec 2011 B2
8096960 Loree Jan 2012 B2
8099305 Kuo Jan 2012 B2
RE43433 Iliff May 2012 E
8190451 Lloyd May 2012 B2
RE43548 Iliff Jul 2012 E
8241231 Bausewein Aug 2012 B2
8271415 Iliff Sep 2012 B2
8301467 Iliff Oct 2012 B2
8337409 Iliff Dec 2012 B2
8357091 Say et al. Jan 2013 B2
8545483 Schwabe et al. Oct 2013 B2
8551039 Veit et al. Oct 2013 B2
8579853 Reggiardo Nov 2013 B2
20010004234 Petelenz Jun 2001 A1
20010027150 Duke Oct 2001 A1
20010029340 Mault Oct 2001 A1
20010032059 Kelly Oct 2001 A1
20010036883 Suzuki Nov 2001 A1
20010037179 Vock Nov 2001 A1
20010044581 Mault Nov 2001 A1
20010044588 Mault Nov 2001 A1
20010047209 Solomon Nov 2001 A1
20010049470 Mault Dec 2001 A1
20010056229 Cosentino Dec 2001 A1
20020013516 Freyre et al. Jan 2002 A1
20020019296 Freeman Feb 2002 A1
20020019584 Schulze Feb 2002 A1
20020019585 Dickinson Feb 2002 A1
20020019586 Teller Feb 2002 A1
20020027164 Mault Mar 2002 A1
20020028995 Mault Mar 2002 A1
20020029784 Stark Mar 2002 A1
20020032386 Sackner Mar 2002 A1
20020035340 Fraden Mar 2002 A1
20020055857 Mault May 2002 A1
20020062069 Mault May 2002 A1
20020063799 Ortiz et al. May 2002 A1
20020068857 Iliff Jun 2002 A1
20020068873 Nissila Jun 2002 A1
20020074877 Lee Jun 2002 A1
20020091796 Higginson et al. Jul 2002 A1
20020107450 Ogura Aug 2002 A1
20020109600 Mault Aug 2002 A1
20020111539 Cosentino Aug 2002 A1
20020128804 Geva Sep 2002 A1
20020133378 Mault Sep 2002 A1
20020138304 Fontanesi Sep 2002 A1
20020143491 Scherzinger Oct 2002 A1
20020169634 Nishi Nov 2002 A1
20020170193 Townsend Nov 2002 A1
20020183646 Stivoric Dec 2002 A1
20020183655 Zhang Dec 2002 A1
20030013072 Thomas Jan 2003 A1
20030036685 Goodman Feb 2003 A1
20030046228 Berney Mar 2003 A1
20030049596 Uda Mar 2003 A1
20030055460 Owen Mar 2003 A1
20030069510 Semler Apr 2003 A1
20030071734 Vodin Apr 2003 A1
20030083559 Thompson May 2003 A1
20030107487 Korman Jun 2003 A1
20030114836 Estes Jun 2003 A1
20030120183 Simmons Jun 2003 A1
20030130595 Mault Jul 2003 A1
20030149597 Zaleski Aug 2003 A1
20030152607 Mault Aug 2003 A1
20030171188 Neil Sep 2003 A1
20030176797 Anzellini Sep 2003 A1
20030177031 Malek Sep 2003 A1
20030208113 Mault Nov 2003 A1
20030236474 Singh Dec 2003 A1
20040018915 Reyes et al. Jan 2004 A1
20040034289 Teller Feb 2004 A1
20040039605 Bardy Feb 2004 A1
20040102931 Ellis May 2004 A1
20040122702 Sabol Jun 2004 A1
20040127821 Ou et al. Jul 2004 A1
20040133081 Teller Jul 2004 A1
20040147818 Levy Jul 2004 A1
20040152956 Korman Aug 2004 A1
20040152957 Stivoric Aug 2004 A1
20040167409 Lo Aug 2004 A1
20040172290 Leven Sep 2004 A1
20040188518 McDonald Sep 2004 A1
20040210458 Evans Oct 2004 A1
20040229685 Smith Nov 2004 A1
20040230549 Freer Nov 2004 A1
20040249778 Iliff Dec 2004 A1
20040254771 Riener Dec 2004 A1
20050010444 Iliff Jan 2005 A1
20050028136 Woodley Feb 2005 A1
20050049022 Mullen Mar 2005 A1
20050070778 Lackey Mar 2005 A1
20050113650 Pacione May 2005 A1
20050140005 Huang Jun 2005 A1
20050182389 Laporte Aug 2005 A1
20050226310 Nakazawa Oct 2005 A1
20050245839 Stivoric Nov 2005 A1
20060030813 Chance Feb 2006 A1
20060031102 Teller Feb 2006 A1
20060065645 Nakasu Mar 2006 A1
20060074279 Brover Apr 2006 A1
20060079740 Silver Apr 2006 A1
20060116557 Moore Jun 2006 A1
20060122474 Teller Jun 2006 A1
20060132477 Kerr Jun 2006 A1
20060135859 Iliff Jun 2006 A1
20060224051 Teller Oct 2006 A1
20060237252 Mobley Oct 2006 A1
20060264730 Stivoric Nov 2006 A1
20070027370 Brauker Feb 2007 A1
20070038161 Bonutti Feb 2007 A1
20070072156 Kaufman Mar 2007 A1
20070105404 Lee May 2007 A1
20070173705 Teller Jul 2007 A1
20070185391 Morgan Aug 2007 A1
20070186429 Bonnet Aug 2007 A1
20070197878 Shklarski Aug 2007 A1
20070253602 Amano Nov 2007 A1
20070254137 Koppe Nov 2007 A1
20070296571 Kolen Dec 2007 A1
20080004904 Tran Jan 2008 A1
20080015891 Lee Jan 2008 A1
20080032119 Feldhahn Feb 2008 A1
20080040615 Carper Feb 2008 A1
20080051638 Iliff Feb 2008 A1
20080051640 Iliff Feb 2008 A1
20080052119 Iliff Feb 2008 A1
20080052120 Iliff Feb 2008 A1
20080052317 Francis Feb 2008 A1
20080055074 Gao Mar 2008 A1
20080059247 Iliff Mar 2008 A1
20080091089 Guillory Apr 2008 A1
20080103824 Francis May 2008 A1
20080147041 Kristensen Jun 2008 A1
20080154098 Morris Jun 2008 A1
20080167535 Stivoric Jul 2008 A1
20080167536 Teller Jul 2008 A1
20080171919 Stivoric Jul 2008 A1
20080176655 James Jul 2008 A1
20080183052 Teller Jul 2008 A1
20080183388 Goodrich Jul 2008 A1
20080194928 Bandic Aug 2008 A1
20080208015 Morris Aug 2008 A1
20080216171 Sano Sep 2008 A1
20080255979 Slutzky Oct 2008 A1
20080275309 Stivoric Nov 2008 A1
20080294294 Blomquist Nov 2008 A1
20080318678 Stivoric Dec 2008 A1
20080319787 Stivoric Dec 2008 A1
20080320029 Stivoric Dec 2008 A1
20090006458 Stivoric Jan 2009 A1
20090007924 Iliff Jan 2009 A1
20090019374 Logan Jan 2009 A1
20090034771 Gleissner Feb 2009 A1
20090043291 Thompson Feb 2009 A1
20090072955 Cary Mar 2009 A1
20090076343 James Mar 2009 A1
20090077849 Glass, Jr. Mar 2009 A1
20090099505 Hendrixson Apr 2009 A1
20090112626 Talbot Apr 2009 A1
20090118100 Oliver May 2009 A1
20090118592 Klitgaard May 2009 A1
20090131759 Sims May 2009 A1
20090146947 Ng Jun 2009 A1
20090150178 Sutton Jun 2009 A1
20090163774 Thatha Jun 2009 A1
20090192362 Sweeney Jul 2009 A1
20090208756 Kimura Aug 2009 A1
20090218725 Thelemann Sep 2009 A1
20090227877 Tran Sep 2009 A1
20090247931 Damgaard-Sorensen Oct 2009 A1
20090264714 Chou Oct 2009 A1
20090265183 Pollard Oct 2009 A1
20090292180 Mirow Nov 2009 A1
20090318779 Tran Dec 2009 A1
20090319221 Kahn Dec 2009 A1
20090319347 Albrecht Dec 2009 A1
20100004947 Nadeau Jan 2010 A1
20100030578 Siddique Feb 2010 A1
20100041772 Liversage Feb 2010 A1
20100056878 Partin Mar 2010 A1
20100070867 Lemmers Mar 2010 A1
20100119461 Bicard-Benhamou May 2010 A1
20100137106 Oshima Jun 2010 A1
20100156007 Huang Jun 2010 A1
20100204616 Shears Aug 2010 A1
20100217099 LeBoeuf Aug 2010 A1
20100221188 Clark Sep 2010 A1
20100240962 Contant Sep 2010 A1
20100241465 Amigo Sep 2010 A1
20100268056 Picard Oct 2010 A1
20100279554 Steijner Nov 2010 A1
20100284552 Lasarov Nov 2010 A1
20100305642 Dong Dec 2010 A1
20100315225 Teague Dec 2010 A1
20100331146 Kil Dec 2010 A1
20100331682 Stein Dec 2010 A1
20110004072 Fletcher Jan 2011 A1
20110010188 Yoshikawa Jan 2011 A1
20110046519 Raheman Feb 2011 A1
20110054359 Sazonov Mar 2011 A1
20110066064 Jangle Mar 2011 A1
20110071003 Watterson Mar 2011 A1
20110087115 Sackner Apr 2011 A1
20110095916 Kass Apr 2011 A1
20110106627 Le Boeuf May 2011 A1
20110125063 Shalon May 2011 A1
20110137213 Caulfield Jun 2011 A1
20110160544 Hayter Jun 2011 A1
20110184247 Contant Jul 2011 A1
20110213278 Horak et al. Sep 2011 A1
20110213625 Joao Sep 2011 A1
20110230732 Edman Sep 2011 A1
20110245633 Goldberg Oct 2011 A1
20110270214 Jorgensen Nov 2011 A1
20110313395 Krulevitch Dec 2011 A1
20120039809 Levinson Feb 2012 A1
20120065548 Morgan Mar 2012 A1
20120179004 Roesicke et al. Jul 2012 A1
20120220528 Van Antwerp Aug 2012 A1
20120302821 Burnett Nov 2012 A1
20120310971 Tran Dec 2012 A1
20120313773 Loree, IV Dec 2012 A1
20130066426 Martinson Mar 2013 A1
20130252216 Clavin Sep 2013 A1
Foreign Referenced Citations (90)
Number Date Country
P0001075-8 Nov 2001 BR
2413220 Nov 2001 CA
2441962 Oct 2002 CA
2454655 Feb 2003 CA
2496579 Mar 2004 CA
2560323 Oct 2005 CA
2413148 Aug 2010 CA
579798 Sep 1976 CH
19832361 Feb 2000 DE
19911766 Sep 2000 DE
0670064 Nov 1993 EP
0707825 Apr 1996 EP
880936 Feb 1998 EP
1534126 Mar 2004 EP
1639939 Mar 2006 EP
1702560 Sep 2006 EP
2126828 Aug 2008 EP
1743571 May 2009 EP
2322952 May 1997 GB
2203250 Oct 1998 GB
153516 Jun 2001 IL
58067 Mar 2002 IL
160079 Jan 2004 IL
167045 Feb 2005 IL
153478 Aug 2009 IL
4341243 Mar 1997 JP
10118052 Nov 1998 JP
10305016 Nov 1998 JP
10305072 Nov 1998 JP
2000083935 Mar 2000 JP
2002095637 Apr 2002 JP
2004500949 Jan 2004 JP
2005536260 Feb 2005 JP
4125132 Jul 2008 JP
4283672 Jun 2009 JP
200244874 Nov 2001 KR
20030011103 Feb 2003 KR
20030015281 Feb 2003 KR
20030086337 Nov 2003 KR
1020040019380 Mar 2004 KR
1020050032119 Apr 2005 KR
100821945 Apr 2008 KR
100831036 May 2008 KR
100885030 Feb 2009 KR
100956791 May 2010 KR
PA05002024 Mar 2005 MX
9301574 Jan 1993 WO
9425841 Nov 1994 WO
9525946 Sep 1995 WO
9706499 Feb 1997 WO
9747239 Dec 1997 WO
9850873 Nov 1998 WO
9859227 Dec 1998 WO
9927483 Jun 1999 WO
9944494 Sep 1999 WO
0011578 Mar 2000 WO
0052604 Mar 2000 WO
0026882 May 2000 WO
0032098 Jun 2000 WO
0047108 Aug 2000 WO
0051543 Sep 2000 WO
0101093 Jan 2001 WO
0152718 Jan 2001 WO
0108554 Feb 2001 WO
0156454 Feb 2001 WO
0126535 Apr 2001 WO
0126547 Apr 2001 WO
0128416 Apr 2001 WO
0128495 Apr 2001 WO
0182783 Apr 2001 WO
0139089 May 2001 WO
0182789 May 2001 WO
0189365 May 2001 WO
0189368 May 2001 WO
0141645 Jun 2001 WO
0196986 Dec 2001 WO
0200111 Jan 2002 WO
02051308 Jul 2002 WO
02069798 Sep 2002 WO
02078538 Oct 2002 WO
02093272 Nov 2002 WO
03015005 Feb 2003 WO
2004019172 Mar 2004 WO
2005016124 Feb 2005 WO
2005046433 May 2005 WO
2005092177 Oct 2005 WO
2008101248 Aug 2008 WO
2010064162 Jun 2010 WO
2010065067 Jun 2010 WO
2011046657 Apr 2011 WO
Non-Patent Literature Citations (27)
Entry
Non-Final Officce Action dated Jul. 14, 2016 relating to U.S. Appl. No. 14/017,765, 11 pages.
Office Action dated Jan. 14, 2015 regarding U.S. Appl. No. 11/625,879, 18 pages.
Final Office Action dated May 20, 2015 relating to U.S. Appl. No. 14/017,765, 14 pages.
Office action from U.S. Appl. No. 14/017,765 dated Oct. 8, 2014, 12 pages.
Final Office Action dated Aug. 1, 2006 relating to U.S. Appl. No. 10/421,965, 10 pages.
Non-Final Office Action dated Mar. 2, 2006 relating to U.S. Appl. No. 10/421,965, 15 pages.
Non-Final Office Action for U.S. Appl. No. 14/807,465 dated Jun. 8, 2016, 30 pages.
Non-Final Office Action for U.S. Appl. No. 14/625,879 dated Jun. 28, 2016, 26 pages.
U.S. Office action for U.S. Appl. No. 14/017,765, dated Dec. 21, 2015, 11 pages.
Final Office Action dated Oct. 2, 2015 relating to U.S. Appl. No. 11/625,879, 114 pages.
Non-Final Office Action dated Sep. 8, 2015 relating to U.S. Appl. No. 14/017,765, 9 pgs.
International Search Report and Written Opinion of International Application No. PCT/US14/21652; Jul. 1, 2014, 10 pages.
Non-Final Office Action dated Jan. 14, 2015 relating to U.S. Appl. No. 11/625,879, 17 pages.
Final Office Action dated May 7, 2014 relating to U.S. Appl. No. 11/625,879, 16 pages.
Non-Final Office Action dated Dec. 19, 2013, relating to U.S. Appl. No. 11/625,879, 10 pages.
Final Office Action dated Mar. 7, 2012 relating to U.S. Appl. No. 11/625,879, 11 pages.
Non-Final Office Action dated Sep. 9, 2011 relating to U.S. Appl. No. 11/625,879, 11 pages.
Final Office Action dated Jun. 14, 2011 relating to U.S. Appl. No. 11/625,879, 7 pages.
Non-Final Office Action dated Feb. 18, 2011 relating to U.S. Appl. No. 11/625,879, 7 pages.
Final Office Action dated Jun. 1, 2010 relating to U.S. Appl. No. 11/625,879, 6 pages.
Non-Final Office Action dated Mar. 23, 2009 relating to U.S. Appl. No. 11/625,879, 7 pages.
Final Office action from U.S. Appl. No. 14/017,765, Mar. 29, 2017, 14 pages.
Non-Final Office action from U.S. Appl. No. 11/625,879, Mar. 30, 2017, 28 pages.
Fischer, et al. Handheld Computing in Medicine, Journal of the American Medical Informatics Association 10.2, 2003, pp. 139-149.
Freedman, Computer Desktop Encyclopedia, 9th ED., Osborne/McGraw-Hill, 2001, p. 745.
PDA. (2003). In B. Pfaffenberger, Webster's New World & Trade, Computer Dictionary, Boston MA; Houghton Mifflin Harcourt, retrieved from <http://search.credoreference.com/content/entry/webstercom/pda/0> on Dec. 7, 2016.
Roth, Intel Centrino Mobile Technology, Windows it Pro website, Sep. 22, 2003, retrieved from <http://windowsitpro.com/hardware/intel-centrino-mobile-technology> on Dec. 7, 2016.
Related Publications (1)
Number Date Country
20130274653 A1 Oct 2013 US
Continuations (1)
Number Date Country
Parent 11625879 Jan 2007 US
Child 13832317 US