Cross-reference is made to U.S. Utility patent application Ser. No. 12/415,225 entitled “DEVICE AND METHOD FOR DISPLAYING JOINT FORCE DATA” by Jason Sherman, which was filed on Mar. 31, 2009 and issued as U.S. Pat. No. 8,556,830 on Oct. 15, 2013; to U.S. Utility patent application Ser. No. 12/415,290 entitled “METHOD FOR PERFORMING AN ORTHOPAEDIC SURGICAL PROCEDURE” by Mick Rock, which was filed on Mar. 31, 2009; to U.S. Utility patent application Ser. No. 12/415,350 entitled “DEVICE AND METHOD FOR DETERMINING FORCES OF A PATIENT'S JOINT” by Jason Sherman, which was filed on Mar. 31, 2009; and to U.S. Utility patent application Ser. No. 12/415,172 entitled “DEVICE AND METHOD FOR DETERMINING FORCE OF A KNEE JOINT” by Jason Sherman, which was filed on Mar. 31, 2009 and issued as U.S. Pat. No. 8,551,023 on Oct. 8, 2013;the entirety of each of which is incorporated herein by reference.
The present disclosure relates generally to orthopaedic surgical instruments and, more particularly, to systems, devices, and methods for determining and displaying joint force data.
Orthopaedic prostheses are implanted in patients by orthopaedic surgeons to, for example, correct or otherwise alleviate bone and/or soft tissue loss, trauma damage, and/or deformation of the bone(s) of the patients. Orthopaedic prostheses may replace a portion or the complete joint of a patient. For example, the orthopaedic prosthesis may replace the patient's knee, hip, shoulder, ankle, or other joint. In the case of a knee replacement, the orthopaedic knee prosthesis may include a tibial tray, a femoral component, and a polymer insert or bearing positioned between the tibial tray and the femoral component. In some cases, the knee prosthesis may also include a prosthetic patella component, which is secured to a posterior side of the patient's surgically-prepared patella.
During the orthopaedic surgical procedure, a surgeon initially prepares the patient's bone(s) to receive the orthopaedic prosthesis. For example, in the case of a knee replacement orthopaedic surgical procedure, the surgeon may resect a portion of the patient's proximal tibia to which the tibia tray will be attached, a portion of patient's distal femur to which the femoral component will be attached, and/or a portion of the patient's patella to which the patella component will be attached. During such procedures, the surgeon may attempt to balance or otherwise distribute the joint forces of the patient's joint in order to produce joint motion that is similar to the motion of a natural joint. To do so, the surgeon may use surgical experience and manually “feel” for the appropriate joint force balance. Additionally or alternatively, the orthopaedic surgeon may use surgical instruments, such as a ligament balancer in the case of a knee replacement procedure, to assist in the balancing or distributing of joint forces.
In addition, in some surgical procedures such as minimally invasive orthopaedic procedures, surgeons may rely on computer assisted orthopaedic surgery (CAOS) systems to improve the surgeon's ability to see the operative area such as in minimally invasive orthopaedic procedures, to improve alignment of bone cut planes, and to improve the reproducibility of such cut planes. Computer assisted orthopaedic surgery systems assist surgeons in the performance of orthopaedic surgical procedures by, for example, displaying images illustrating surgical steps of the surgical procedure being performed and rendered images of the relevant bones of the patient. Additionally, computer assisted orthopaedic surgery (CAOS) systems provide surgical navigation for the surgeon by tracking and displaying the position of the patient's bones, implants, and/or surgical tools.
According to one aspect, a computer assisted orthopaedic system may include a sensor module, a display, and a computer coupled to the display. The sensor module may be configured to transmit joint force data indicative of the joint force of a patient's knee joint. The computer may be configured to determine position data indicative of a position of a patient's femur and a patient's tibia and display an image of the patient's femur and the patient's tibia based on the position data. For example, the computer may be configured to determine the position data based on signals received from sensors coupled to the patient's femur and the patient's tibia. The computer may also be configured to determine a medial force value indicative of a medial component of the joint force based on the joint force data, determine a lateral force value indicative of a lateral component of the joint force based on the joint force data, and display the medial force value and the lateral force value on the display.
In some embodiments, the computer may also be configured to determine an average force value based on the medial force value and the lateral force value and display the average force value on the display. Additionally, the computer may be configured to determine an angle of flexion between the patient's femur and the patient's tibia based on the position data, determine a medial force value indicative of the medial component of the joint force at the angle of flexion, and determine a lateral force value indicative of the lateral component of the joint force at the angle of flexion. In such embodiments, the computer may be configured to display the angle of flexion and the associated medial force value and the associated lateral force value on the display. The computer may also be configured to store the angle of flexion, the medial force value, and the lateral force value in association with each other. Additionally, the computer may be configured to display a an image, such as a graph, indicative of flexion angle versus medial force value and lateral force value on the display.
In some embodiments, the computer may be configured to determine a varus/valgus angle of between the patient's femur and the patient's tibia based on the position data and display the varus/valgus angle on the display in association with the greater of the medial force value and the lateral force value. Additionally, the computer may be configured to determine a condyle of the patient's femur that corresponds to the greater of the medial force value and the lateral force value at the varus/valgus angle and identify the condyle on the display.
Additionally, in some embodiments, the computer may be configured to store the medial force value and the lateral force value in association with other orthopaedic surgical data related to an orthopaedic surgical procedure. For example, the computer may be configured to store the medial force value and the lateral force value in association with identification data that identifies the patient and implant data that identifies an implant used in the orthopaedic surgical procedure.
According to another aspect, the computer assisted orthopaedic system may a sensor module, a display, and a computer coupled to the display. The sensor module may include a sensor array. The sensor array may include a plurality of medially located pressure sensors configured to generate medial sensor signals indicative of a medial joint force between a patient's tibia and a medial condyle of the patient's femur and a plurality of laterally located pressure sensors configured to generate lateral sensor signals indicative of a lateral joint force between the patient's tibia and a lateral condyle of the patient's femur. Additionally, the sensor module may be configured to wirelessly transmit medial force data indicative of the medial joint force and lateral force data indicative of the lateral force. The computer may include a receiver circuit configured to receive the medial and lateral force data. The computer may be configured to determine position data indicative of a position of a patient's femur and a patient's tibia and display an image of the patient's femur and the patient's tibia based on the position data. Additionally, the computer may be configured to determine a medial force value based on the medial joint data, determine a lateral force value based on the lateral joint data, and display the medial force value and the lateral force value on the display.
In some embodiments, the computer may also be configured to determine an average force value based on the medial force value and the lateral force value and display the average force value on the display. Additionally, the computer may be configured to determine an angle of flexion between the patient's femur and the patient's tibia based on the position data, determine a medial force value indicative of the medial joint force at the angle of flexion, and determine a lateral force value indicative of the lateral joint force at the angle of flexion. The computer may also be configured to display the angle of flexion and the associated medial force value and the associated lateral force value on the display. Additionally, the computer may be configured to display a graph of flexion angle versus medial force value and lateral force value on the display.
Additionally, in some embodiments, the computer may be configured determine a varus/valgus angle of between the patient's femur and the patient's tibia based on the position data. The computer may also be configured to display the varus/valgus angle on the display in association with the greater of the medial force value and the lateral force value. Further, the computer may be configured to a condyle of the patient's femur that corresponds to the greater of the medial force value and the lateral force value at the varus/valgus angle and identify the condyle on the display.
According to a further aspect, a method for operating a computer assisted orthopaedic surgery system, may include determining position data indicative of a position of a patient's femur and a patient's tibia and displaying an image of the patient's femur and the patient's tibia based on the position data. The method may also include determining a medial force value indicative of a medial component of the joint force based on the joint force data, determining a lateral force value indicative of a lateral component of the joint force based on the joint force data, and displaying the medial force value and the lateral force value on the display. The method may also include determining an average force value based on the medial force value and the lateral force value and displaying the average force value on the display.
The detailed description particularly refers to the following figures, in which:
While the concepts of the present disclosure are susceptible to various modifications and alternative forms, specific exemplary embodiments thereof have been shown by way of example in the drawings and will herein be described in detail. It should be understood, however, that there is no intent to limit the concepts of the present disclosure to the particular forms disclosed, but on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the invention as defined by the appended claims.
Terms representing anatomical references, such as anterior, posterior, medial, lateral, superior, inferior, etcetera, may be used throughout this disclosure in reference to both the orthopaedic implants described herein and a patient's natural anatomy. Such terms have well-understood meanings in both the study of anatomy and the field of orthopaedics. Use of such anatomical reference terms in the specification and claims is intended to be consistent with their well-understood meanings unless noted otherwise.
Referring now to
Referring now to
In use, the tibial paddle 34 is configured to be positioned on a proximal plateau of a patient's resected tibia (see, e.g.,
As such, it should be appreciated that sensor module 12 may be used on the patient's left or right knee using a medial or lateral surgical approach. For clarity of description, the sensor module 12 and the system 10 are described below with reference to an orthopaedic surgical procedure using a medial surgical approach (i.e., using a medial capsular incision to access the patient's joint). However, it should be appreciated that such description is equally applicable to lateral surgical approach procedures. As such, some structures are described using particular anatomical references (e.g., lateral and medial) with the understanding that such references would be flipped or switched when the module 12 is used in a lateral surgical approach procedure. For example, a “medial side” of the tibial paddle 34 becomes a “lateral side” of the tibial paddle 34 when used in a lateral surgical approach procedure.
The tibial paddle 34 is substantially planar and has a shape generally corresponding to the shape of the orthopaedic prosthesis to be implanted in the patient. For example, in the illustrative embodiment, the tibial paddle 34 has a shape generally corresponding to a knee prosthesis of a particular size. However, in other embodiments as discussed in more detail below, the paddle 34 (or sensor housing 30) may have a shape generally corresponding to other types of orthopedic prostheses such as a hip prosthesis, a shoulder prosthesis, an ankle prosthesis, a spine prosthesis, or a patella prosthesis.
The illustrative tibial paddle 34 includes a curved anterior side 36, a curved lateral side 38, a curved medial side 40, and a curved posterior side 42, each shaped to approximate the shape a tibial bearing of an orthopaedic knee prosthesis. Again, as discussed above, the lateral side 38 and the medial side 40 are lateral and medial sides, respectively, in those embodiments wherein the sensor module 12 is used in a lateral surgical approach procedure. The posterior side 42 includes a posterior notch 44 to allow the tibial paddle 34 to be positioned around the soft tissue of the patient's joint such as the posterior cruciate ligament. Additionally, in some embodiments, the posterior notch 44 may also provide a mount for other surgical devices such as a trail post for rotating mobile bearing trails. Further, in some embodiments, the posterior notch 44 may be extended or otherwise have other configurations so as to provide a mount for other orthopaedic surgical devices such as fixed and/or mobile tibial trials or the like.
The overall size of the tibial paddle 34 may be selected based on the particular anatomical structure of the patient. For example, in some embodiments, the tibial paddle 34 may be provided in various sizes to accommodate patients of varying sizes. It should be appreciated that the general shape and size of the paddle 34 (and sensor housing 30) is designed and selected such that the paddle 34 or housing 30 does not significantly overhang with respect to the associated bony anatomy of the patient such that the paddle 34 or housing 30 nor adversely impinge the surrounding soft tissue.
The handle 32 includes a pair of displays 50, 52 coupled to a first end 54 of the handle 32. A second end 56 of the handle 32 opposite the first end 54 is coupled to the tibial paddle 34. In the illustrative embodiment of
As illustrated in
Depending on the particular surgical approach to be used by the orthopedic surgeon, the surgeon may flip the sensor module 12 to the proper orientation such that the tibial paddle 34 is inserted into the patient's knee joint through the associated capsular incision. In either orientation, the handle 32 extends out of the capsular incision and at least one of the displays 50, 52 is visible to the orthopaedic surgeon. For example, if the orthopaedic surgeon is using a medial surgical approach on a patient's left knee, the orthopaedic surgeon may position the sensor module 12 in the orientation illustrated in
As discussed above, the sensor module 12 is configured to assist a surgeon during the performance of an orthopaedic surgical procedure. As such, the sensor module 12 includes an outer housing 58 formed from a bio-compatible material. For example, the outer housing 58 may be formed from a bio-compatible plastic or polymer. In one particular embodiment, the sensor module 12 is configured for single-usage and, as such, is provided in a sterile form. For example, the sensor module 12 may be provided in a sterile packaging. However, in those embodiments wherein the tibial paddle 34 is removably coupled to the handle 32, the tibial paddle 34 may be designed for single-usage and the handle 32 may be configured to be reusable via an autoclaving procedure or the like.
As illustrated in
The display 50 is coupled to the end 54 of the upper housing 60 and the display 52 is coupled to the 54 of the lower housing 62. As illustrated in
As discussed in more detail below, the light emitting diodes 80,82, 84, 86, 88 may be illuminated according to a predetermined display protocol to provide a visual indication to the surgeon of the relative medial-lateral joint force balance. By activating or illuminating one or more of the light emitting diodes 80, 82, 84, 86, 88, an orthopaedic surgeon may visual determine which side of the patient's joint is exerting a greater amount of force and the general magnitude of such force relative to the opposite side of the patient's joint. For example, one illustrative display protocol is presented in graph 170 in
The sensor module 12 includes a sensor array 90 positioned in the tibial paddle 34 and communicatively coupled to a control circuit 92 positioned in the handle 32. The sensor array 90 is “sandwiched” between the upper housing piece 60 and the lower housing piece 62. However, the upper housing piece 60 and the lower housing piece 62 are spaced apart to allow the sensor array 90 to be compressed by the joint force applied to the tibial paddle 34. For example, as illustrated in
The sensor array 90 includes a plurality of pressure sensors or sensor elements 100 configured to generate sensor signals indicative of the joint force applied to the sensor array 90. In the illustrative embodiment, the pressure sensors 100 are embodied as capacitive pressure sensors, but may be embodied as other types of sensors in other embodiments. In the illustrative embodiment, the pressure sensors 100 of the sensor array 90 are arranged in a particular configuration. For example, in one embodiment as illustrated in
The pressure sensors 102, 104, 108, 106, 120, 124 form a medial set of pressure sensors that generate sensor signals indicative of a medial joint force component of the joint force of a patient's knee (again, assuming a medial surgical approach). Similarly, the pressure sensors 112, 114, 118, 116, 122, 125 form a lateral set of pressure sensors that generate sensor signals indicative of a lateral joint force component of the joint force of a patient's knee. Additionally, pressure sensors 102, 104, 120 form an anterior-medial set of pressure sensors that generate sensor signals indicative of an anterior-medial joint force component of the joint force of a patient's knee. Similarly, the pressure sensors 112, 114, 122 form an anterior-lateral set of pressure sensors that generate sensor signals indicative of an anterior-lateral joint force component of the joint force of a patient's knee. The pressure sensors 106, 108, 124 form a posterior-medial set of pressure sensors that generate sensor signals indicative of a posterior-medial joint force component of the joint force of a patient's knee. Similarly, the pressure sensors 116, 118, 126 form a posterior-lateral set of pressure sensors that generate sensor signals indicative of a posterior-lateral joint force component of the joint force of a patient's knee.
In other embodiments, the sensor array 90 may include more or fewer pressure sensors. In one particular embodiment, the sensor array 90 may include additional medial and lateral pressure sensors for each condyle of the patient's femur. For example, as illustrated in
Referring now to
The processor 130 is communicatively coupled to the memory device 132 via signal paths 134. The signal paths 134 may be embodied as any type of signal paths capable of facilitating communication between the processor 130 and the memory device 132. For example, the signal paths 134 may be embodied as any number of wires, printed circuit board traces, via, bus, intervening devices, and/or the like. The processor 130 is also communicatively coupled to the sensor array 90 via signal paths 136. Similar to signal paths 134, the signal paths 136 may be embodied as any type of signal paths capable of facilitating communication between the processor 130 and the sensor array 90 including, for example any number of wires, printed circuit board traces, via, bus, intervening devices, and/or the like. Additionally, the signal path 136 may include a connector 138 (see
The control circuit 92 also includes a power source 142 and associated power control circuitry 144. The power source 142 may be embodied as a number of batteries sized to fit in the sensor module 12. The power source 142 is electrically coupled to the power control circuitry 144 via signal paths 146 and the power control circuitry 144 is electrically coupled to the processor 130 and other devices of the control circuit 92 via signal paths 148. The signal paths 146, 148 may be embodied as any type of signal paths including, for example any number of wires, printed circuit board traces, via, bus, intervening devices, and/or the like. The power circuitry 144 may include power control, distribution, and filtering circuitry and is configured to provide or distribute power from the power source 142 to the processor 130 and other devices or components of the control circuit 92.
The control circuit 92 also includes user controls 150 communicatively coupled to the processor 130 via signal paths 152. The user controls 150 are embodied as power buttons 154 (see
The signal paths 152 are similar to the signal paths 134 and may be embodied as any type of signal paths capable of facilitating communication between the user controls 150 and the processor 130 including, for example any number of wires, printed circuit board traces, via, bus, intervening devices, and/or the like.
The control circuit 92 also includes display circuitry 156 for driving and/or controlling the displays 50, 52. The display circuitry 156 is communicatively coupled to the processor 130 via signal paths 158 and to the displays 50, 52 via signal paths 160. Similar to the signal paths 134 discussed above, the signal paths 158, 160 may be embodied as any type of signal paths capable of facilitating communication between the processor 130 and display circuitry 156 and the display circuit 156 and displays 50, 52, respectively. For example, the signal paths 158, 160 may be embodied as any number of wires, printed circuit board traces, via, bus, intervening devices, and/or the like. As discussed above, in the illustrative embodiment, the displays 50, 52 are embodied as an arrangement of light emitting diodes 80, 82, 84, 86, 88.
In some embodiments, the sensor module 12 is configured to transmit force data to the display module 14 and/or computer assisted orthopaedic surgery (CAOS) system 18. In such embodiments, the control circuit includes transmitter circuitry 162 and an antenna 164. The transmitter circuitry 162 is communicatively coupled to the processor 130 via signal paths 166 and to the antenna 164 via signal paths 168. The signal paths 166, 168 may be embodied as any type of signal paths capable of facilitating communication between the transmitter circuitry 162 and the processor 130 and antenna 164, respectively. For example, similar to the signal paths 134, the signal paths 166, 168 may be embodied as any number of wires, printed circuit board traces, via, bus, intervening devices, and/or the like. The transmitter circuitry 162 may be configured to use any type of wireless communication protocol, standard, or technologies to transmit the joint force data to the display module 14 and/or computer assisted orthopaedic surgery (CAOS) system 18. For example, the transmitter circuitry 162 may be configured to use a wireless networking protocol, a cellular communication protocol such as a code division multiple access (CDMA) protocol, a Bluetooth® protocol, or other wireless communication protocol, standard, or technology.
Referring now to
In block 206, the control circuit 92 receives the sensor signals or data from the sensor array 90. As discussed above, the sensor array 90 generates sensor signals indicative of a joint force applied to the tibial paddle 34 when the paddle 34 is positioned in the knee joint of a patient. In block 208, the processor 130 of the control circuit 92 determines joint force data based on the sensor signals received from the sensor array 90. The joint force data is indicative of the joint force of the patient's knee. In some embodiments, the joint force data may be embodied as specific joint force values such as a medial joint force value, a lateral joint force value, an anterior joint force value, and/or a posterior joint force value, each force being determined in Newtons or similar force measurement unit. In such embodiments, the medial joint force may be determined based on the sensor signals from the pressure sensors 102, 104, 106, 108, 120, 124. The lateral joint force may be determined based on the sensor signals from the pressure sensors 112, 114, 116, 118, 122, 126. The anterior joint force may be based on the pressure sensor anterior-medial pressure sensors 102, 104, 120 and/or the anterior-lateral pressure sensors 112, 114, 122. Additionally, the posterior joint force may be based on the sensor signals from the posterior-medial pressure sensors 106, 108, 124 and/or the posterior-lateral sensors 116, 118, 126. Subsequently, in block 210 the control circuit 92 controls or otherwise activates the displays 50, 52 to display the joint force data determined in block 208. For example, in embodiments wherein one or more specific joint forces are determined, the processor 130 may display the determine joint forces or indicia thereof on the displays 50, 52.
Additionally or alternatively, the control circuit 92 may be configured to determine the relative medial-lateral joint force balance and display indicia of such medial-lateral balance on the displays 50, 52 in blocks 208, 210. For example, as illustrated in
In block 226, the control circuit 92 determines the relative medial-lateral balance of the joint force of the patient's joint. To do so, the control circuit 92 compares the medial force data and the lateral force data. For example, in one embodiment, the control circuit 92 is configured to determine a total force value by summing the medial force data and the lateral force data. The control circuit 92 subsequently determines a medial percentage value by dividing the medial force data by the total force value and a lateral percentage value by dividing the lateral force data by the total force value. As such, if the medial and lateral forces of a patient's joint are balanced, the medial percentage value would be determined to be about 50% and the lateral percentage value would be determined to be about 50%. Of course, in some embodiments, the control circuit 92 may be configured to determine only one of the medial and lateral percentage values, the remaining one being known or determined by simple subtraction from 100%.
In block 228, the control circuit 92 activates or controls the displays 50, 52 to provide a visual indication of the relative medial-lateral balance of the joint forces of the patient's joint. For example, in embodiments wherein the displays 50, 52 are embodied as light emitting diodes, the control circuit 92 is configured to activate or illuminate one or more of the light emitting diodes to provide a visual indication of the medial-lateral balance of joint forces. The control circuit 92 may use any display protocol or pattern of illumination of the light emitting diodes that provides an appropriate indication to the orthopaedic surgeon of such joint forces.
For example, in one particular embodiment, the control circuit 92 is configured to control the displays 50, 52 according to the display protocol 170 illustrated in and discussed above in regard to
In this way, sensor module 12 provides a visual indication to the orthopaedic surgeon of the relative medial and lateral forces of the patient's joint. As discussed in more detail below, the orthopaedic surgeon can perform balancing procedures on the patient's knee joint while monitoring the current balance of the medial and lateral forces via the displays 50, 52 to achieve the desired balance for the particular patient. Additionally, because the sensor module 12 includes a display 50, 52 on either side, the orthopaedic surgeon is provide the visual indication of the joint forces whether the surgeon is operating on the patient's left or right knee.
Referring back to
Referring now to
Referring now to
In some embodiments, the sensor housing 252 may be detached from the handle 254, but communicatively coupled therewith, to improve the ease of use of the sensor module 250 with particular joints. For example, as illustrated in
In another embodiment as illustrated in
Additionally, in some embodiments as illustrated in
Referring now to
Referring now to
As discussed above, the hand-held display module 14 is configured to be used with the sensor module 12 to receive joint force data form the module 12 and display indicia on the display 302 indicative of the joint forces of the patient's joint. Similar to the sensor module 12, the display module 14 may be configured to determine the relative medial-lateral and/or anterior-posterior balance of the patient's joint forces and display indicia of such balances on the display 302. Additionally, the display module 14 may be configured to determine the anterior-posterior balance of the patient's joint forces and display indicia of such balances on the display 302. Further, as discussed in more detail below, the display module 14 may be configured to determine the specific joint force values (e.g., the medial and lateral joint forces) and display such force values on the display 302. That is, in addition to an indication of the joint forces relative to each other, the hand-held display module 14 may calculate or otherwise determine the magnitude of the joint force values as measured in a suitable unit of force such as Newtons. Additionally, the display module 14 may also be configured to perform other functions such as store screenshots and data of the patient's joint forces as displayed on the display 302 and download such data to other devices.
As illustrated in
The processor 322 is communicatively coupled to the memory device 324 via signal paths 326. The signal paths 326 may be embodied as any type of signal paths capable of facilitating communication between the processor 322 and the memory device 324. For example, the signal paths 326 may be embodied as any number of wires, printed circuit board traces, via, bus, intervening devices, and/or the like.
The processor 322 is also communicatively coupled to the user input buttons 306, 308, 310 via signal paths 328 and to the power indicator 314 via signal paths 344. Similar to signal paths 326, the signal paths 328, 344 may be embodied as any type of signal paths capable of facilitating communication between the processor 322 and the user input buttons 306, 308, 310 and the power indicator 314, respectively. For example, the signal paths 328, 344 may include any number of wires, printed circuit board traces, via, bus, intervening devices, and/or the like. The user input buttons 306, 308, 310 are software or “soft” buttons, the functionality of each of which may be determined based on the particular screen displayed on the display 302.
The control circuit 320 also includes an external power input circuitry 330, a rechargeable power source 332 such as a rechargeable battery or the like, and power circuitry 334. The external power input circuitry 330 is configured to receive a plug of a charger such as a “wall charger” and is communicatively coupled to the rechargeable power source 332 via signal paths 336. The rechargeable power source 332 is communicatively coupled to the power circuitry 334 via signal paths 338. The power circuitry 334 is communicatively coupled to the processor 332 via signal paths 340 and to the power button 312 via signal paths 342. The signal paths 336, 338, 340, 342 may be embodied as any type of signal paths including, for example any number of wires, printed circuit board traces, via, bus, intervening devices, and/or the like. The power circuitry 334 may include power control, distribution, and filtering circuitry and is configured to provide or distribute power the rechargeable power source 332 to the processor 322 and other devices or components of the control circuit 320.
The control circuit 320 also includes display circuitry 346 for driving and/or controlling the display 392. The display circuitry 346 is communicatively coupled to the processor 322 via signal paths 348 and to the display 302 via signal paths 350. The signal paths 348, 350 may be embodied as any type of signal paths capable of facilitating communication between the processor 322 and display circuitry 346 and the display circuit 346 and display 302, respectively. For example, the signal paths 348, 350 may be embodied as any number of wires, printed circuit board traces, via, bus, intervening devices, and/or the like.
As discussed above, the hand-held display module 14 is configured to receive joint force data from the sensor module 12. As such the control circuit 320 includes receiver circuitry 352 and an antenna 354. The receiver circuitry 352 is communicatively coupled to the processor 322 via signal paths 356 and to the antenna 354 via signal paths 358. The signal paths 356, 358 may be embodied as any type of signal paths capable of facilitating communication between the receiver circuitry 352 and the processor 322 and the antenna 354, respectively. For example, the signal paths 356, 358 may be embodied as any number of wires, printed circuit board traces, via, bus, intervening devices, and/or the like. The receiver circuitry 352 may be configured to use any type of wireless communication protocol, standard, or technologies to receive the joint force data from the sensor module 12. For example, as discussed above in regard to the sensor module 12, the display module 14 may be configured to a wireless networking protocol, a cellular communication protocol such as a code division multiple access (CDMA) protocol, a Bluetooth® protocol, or other wireless communication protocol, standard, or technology to communicate with the sensor module 12.
The control circuit 320 also includes a universal serial bus (USB) interface 360. The USB interface 360 is communicatively coupled to the processor 322 via signal paths 362, which may be embodied as any type of signal paths capable of facilitating communication between the USB interface 360 and the processor 322. For example, the signal paths 362 may be embodied as any number of wires, printed circuit board traces, via, bus, intervening devices, and/or the like. The USB interface 360 may be used to download data, such as joint force data or screenshot data, from the display module 14 to another device such as a computer. Additionally, the USB interface 360 may be used to update the software or firmware of the control circuit 320.
Referring now to
In block 406, the control circuit 320 receives the joint force data from the sensor module 12. As discussed above, the joint force data is indicative of the joint force of the patient's knee as indicated by the sensor signals generated by the sensor array 90 of the sensor module 12. In block 408, the control circuit 320 determines a medial joint force value and a lateral joint force value based on the joint force data received in block 406. The medial joint force value is based on the sensor signals received from the pressure sensors 102, 104, 106, 108, 120, 124 and the lateral joint force value is based on the sensor signals received from the pressure sensors 112, 114, 116, 118, 122, 126. In block 410, the control circuit 320 determines an average medial/lateral force value based on the medial joint force value and the lateral joint force value determined in block 408. The medial joint force value, the lateral joint force value, and the average joint force value are subsequently displayed on the display 302 in block 412. For example, as illustrated in the screenshots 450, 452, 454 in
In blocks 414, 416, the control circuit 320 determines which mode the orthopaedic surgeon has selected. In the illustrative embodiment, the orthopaedic surgeon may select a first mode in which indicia of only the medial-lateral balance of the patient's joint forces is displayed on the display 302 or a second mode in which may indicia of the medial-lateral and the anterior-posterior balance of the patient's joint forces is displayed in the display 302. The user may switch between the two modes by selecting the appropriate user input buttons 306, 308, 310.
If the orthopaedic surgeon has selected the medial-lateral only mode, the method 400 advances to block 418 in which indicia of the medial-lateral balance of the joint forces of the patient's knee are displayed on the display 302. To do so, as illustrated in
If, however, the orthopaedic surgeon has selected the medial-lateral and anterior-posterior mode, the method 400 advances to block 420 in which indicia of the medial-lateral and anterior-posterior balance of the joint forces of the patient's knee are displayed on the display 302. To do so, as illustrated in
In the illustrative screen display 452 of
Referring now back to
When a screenshot is stored, an icon 484 appears in the upper right corner of the display 302. The icon 484 displays the average force value that was measured on the respective stored screenshot. Any number of icons 484 may be displayed on the display 302 to indicate corresponding stored screenshots. Additionally, although only a select number of icons 484 may be displayed on the display 302, the control circuit 320 may be configured to store any number of screenshots. In addition to the icon 484, when a screenshot is stored, a corresponding vertical balance line 486 is displayed on the display 302. The balance line 486 provides a visual indication of the medial-lateral balance of the joint forces displayed in the associated stored screenshot. Further, if the orthopaedic surgeon has selected the medial-lateral and anterior-posterior mode, an anterior-posterior balance line 488 is displayed on the display 302. The balance line 488 provides a visual indication of the anterior-posterior balance of the medial and lateral forces of the patient's knee joint displayed in the associated stored screenshot.
Referring now to
As illustrated in
As illustrated in
In use, the sensor module 12 is positioned in the cradle 500 and secured in place via the locking mechanism 510. Depending on which knee of the patient will be operated on, the distractor components 502, 504 may be positioned such that the tibial paddles 538, 542 contact the tibial paddle 34 of the sensor module 12 as illustrated in
In the illustrative embodiment of
Referring now to
The display 602 may be embodied as any type of device such as a liquid crystal display monitor, a cathode ray tube (CRT) display monitor, or the like. Additionally, in some embodiments, the display 602 may be embodied as a “heads-up” display. In such embodiments, the signal path 606 may be embodied as a wired or wireless signal path. The camera unit 604 includes two or more cameras 610, which are positioned such that reflective arrays 620 coupled to the relevant bones of a patient 612 are in the field of view 614 of the cameras 610.
The computer 600 includes a processor 622, a memory device 624, and a receiver or receiver circuitry 626. The processor 622 may be embodied as any type of processor configurable to perform the functions described herein. For example, the processor 622 may be embodied as a separate integrated circuit or as a collection of electronic devices. Additionally, the processor may be a single or multi-core processors. Although only a single processor 622 is illustrated in
The receiver circuitry 626 may be configured to use any type of wireless communication protocol, standard, or technologies to receive the joint force data from the sensor module 12. For example, as discussed above in regard to the sensor module 12, the computer 600 may be configured to communicate using a wireless networking protocol, a cellular communication protocol such as a code division multiple access (CDMA) protocol, a Bluetooth® protocol, or other wireless communication protocol, standard, or technology to communicate with the sensor module 12.
In use, the computer assisted orthopaedic surgery (CAOS) system 18 is configured to provide surgical navigation by tracking and displaying the position of the patient's relevant bony anatomy (e.g., the patient's tibia and femur) to which the reflective arrays 620 are coupled and provide an amount of surgical procedure walk-through. Additionally, the computer assisted orthopaedic surgery (CAOS) system 18 is configured to receive the joint force data from the sensor module 12 and display the joint force data or other indicia of the joint forces of the patient's joint on the display 602.
To do so, the computer 600 may execute a method 700 for performing an orthopaedic surgical procedure as illustrated in
In block 704, the selections and preferences of the orthopaedic surgical procedure are chosen by the surgeon. Such selections may include the type of orthopaedic surgical procedure that is to be performed (e.g., a total knee arthroplasty), the type of orthopaedic implant that will be used (e.g., make, model, size, fixation type, etc.), the sequence of operation (e.g., the tibia or the femur first), and the like. Once the orthopaedic surgical procedure has been set up in block 704, the bones of the patient are registered in block 706. To do so, the reflective arrays 620 are coupled with the relevant bones of the patient (e.g., the tibia and femur of the patient). Additionally, the contours of such bones are registered using an appropriate registration tool. To do so, a pointer end of such tool is touched to various areas of the bones to be registered. In response to the registration, the computer 600 displays rendered images of the bones wherein the location and orientation of the bones are determined based on the reflective arrays coupled therewith and the contours of the bones are determined based on the registered points. Additionally, one or more surgical tools may be registered with the computer assisted orthopaedic surgery (CAOS) system in block 706.
Once the pertinent bones have been registered in block 706, the computer 600, in cooperation with the camera unit 604, displays the images of the surgical steps of the orthopaedic surgical procedure and associated navigation data (e.g., location of surgical tools) in block 708. To do so, the process step 708 may include any number of sub-steps in which each surgical procedure step is displayed to the orthopaedic surgeon in sequential order along with the associated navigational data. Additionally, in block 710 the computer 600 receives joint force data from the sensor module 12. As discussed above, the joint force data is indicative of the joint force of the patient's knee as indicated by the sensor signals generated by the sensor array 90 of the sensor module 12.
In block 712, the computer 600 displays the joint force data or other data derived therefrom that is indicative of the joint forces of the patient's joint on the display 602. The computer 600 may be configured to determine any one or more joint force values based on the joint force data in block 712. For example, similar to the hand-held display module 14, the computer 600 may be configured to determine a medial joint force value and a lateral joint force value based on the joint force data received in block 710. Again, such medial joint force value is based on the sensor signals received from the pressure sensors 102, 104, 106, 108, 120, 124 and the lateral joint force value is based on the sensor signals received from the pressure sensors 112, 114, 116, 118, 122, 126. The computer 600 may also determine an average medial/lateral force value based on the medial joint force value and the lateral joint force value. In such embodiments, the medial joint force value, the lateral joint force value, and the average joint force value are subsequently displayed on the display 602 in block 712. In addition, the computer 600 may be configured to determine the medial-lateral and/or anterior-posterior balance of the joint forces based on the joint force data and display indicia of joint force balance on the display 602 in a manner similar to the hand-held display module 14. For example, the computer 600 may present displays similar to the displays 450, 452, 454 illustrated in and described above in regard to
In some embodiments, the computer assisted orthopaedic surgery (CAOS) system 18 may be configured to determine and display joint force data on the display 602 in association with the navigation data. For example, the computer 600 may execute a method 720 for displaying joint force data in association with navigation data as illustrated in
Contemporaneously with the determination of the joint force values in block 722, the computer 600 determines the location and orientation of the patient's relevant bones, such as the patient's femur and tibia in those embodiments wherein the patient's knee is undergoing an orthopaedic surgical procedure, in block 724. Subsequently, in block 728, the computer 600 displays the joint force values determined in block 722 and the image of the knee joint in block 728. As such, the computer 600 may be used to display, for example, the flexion and extension gaps of the medial and lateral condyles of the patient's knee and contemporaneously display the associated medial, lateral, and/or average joint force values of the patient's knee. By monitoring the flexion and extension gaps and the associated joint force values, the orthopaedic surgeon may determine the appropriate amount of gap or joint force for a particular orthopaedic procedure.
Additionally, in some embodiments, the computer 600 may also be configured to determine other anatomical data based on the orientation and position of the patients bones determined in block 726 and display such anatomical data along with the associated joint force values. For example, in one embodiment, the computer 600 is configured to determine the varus/valgus angle of the patient's knee and display the associated medial and lateral force values. Additionally, the computer 600 may be configured to determine the loaded condyle based on the medial and lateral force values and identify the loaded condyle to the orthopaedic surgeon on the display 602. Further, in some embodiments, the computer 600 may be configured to store the anatomical data, the joint force values, and/or other surgical data such as the implant type size, patient identification data, and/or the like in association with each other in the memory device 624 or other storage device.
The computer 600 may also be configured to determine and display a graph of flexion angle and associated joint force values in some embodiments. To do so, the computer 600 executes a method 730 as illustrated in
Contemporaneously with the determination of the joint force values in block 732, the computer 600 determines the flexion angle of the patient's knee in block 736. To do so, the computer 600 determines the relative location of the patient's tibia and femur and determines the flexion angle defined therebetween based on these locations. In block 738, the computer 600 stores the joint force data determined in block 734 and the flexion angle data determined in block 738. The method repeats through blocks 732, 734, 736 to collect data and each, or every predetermined, flexion angle within a desired range of flexion. After such data has been collected, the method 730 advances to block 740 in which the computer 600 displays a graph of joint force values versus flexion angle. Such graph may include medial and lateral joint force values or may include an average joint force values depending on the preference of the orthopaedic surgeon.
Referring now to
In block 806, the patient's knee is placed in extension. Subsequently, in block 808, the patient's knee is distracted while in extension and the joint forces are balanced. To do so, the orthopaedic surgeon may place the tibial paddle 34 of the sensor module 12 in the patient's knee joint. In particular, the tibial paddle 34 is placed on the resected plateau 850 of the patient's proximal tibia as illustrated in
Once a generally rectangular joint gap is established, the orthopaedic surgeon may balance the medial and lateral joint forces. To do so, the orthopaedic surgeon may perform a ligament release or balancing procedure to reduce the medial or lateral force of the patient's knee. While so doing, the orthopaedic surgeon may monitor the display 50, 52 of the sensor module 12 and/or the hand-held display module 14 to determine which side to release and when the medial and lateral forces are approximately equal (e.g., when the middle light emitting diode 84 is illuminated). Of course, the orthopaedic surgeon may decide that an alternative joint force balance, such as a 45%/55% medial-lateral joint force balance, is desirable for the particular patient based on such criteria as, for example, the age of the patient, the gender of the patient, the extent of soft tissue damage of the patient's joint, the extent of pre-operative deformity of the patient's joint, etc. Additionally, in some embodiments, such as those embodiments wherein the computer assisted orthopaedic surgery (CAOS) system 18 is used, the distal end of the patient's femur 902 may be resected in block 810.
After the orthopaedic surgeon has properly balanced the medial-lateral joint forces of the patient's joint in extension, the patient's joint is placed in flexion in block 812. Subsequently, in block 814, the patient's knee is distracted while in flexion to the desired balance of joint forces. To do so, the orthopaedic surgeon may again place the tibial paddle 34 of the sensor module 12 on the resected plateau 850 of the patient's proximal tibia 900. The tibial paddle 34 may be placed in contact with the patient's tibia or may be placed on a membrane or other intervening member. The orthopaedic surgeon may distract the patient's knee using, for example, the distractor 16, 560, or other distractor to distract each condyle of the patient's femur differing amounts until the medial and lateral joint forces are approximately equal. By, equalizing the medial and lateral joint forces, the rotation of the femur is established.
After the patient's joint has been distracted to achieve the desired medial-lateral joint balance in block 814, a number of additional resectioning cuts are performed on the patient's distal femur 902 in block 816. To do so, as illustrated in
Alternatively, in some embodiments, the rotation of the femur in flexion is predetermined based on anatomical references such as the posterior condyles, Whiteside's line, and/or the transepicondylar axis. The anterior femoral cut, a posterior femoral cut, and/or chamfer cuts are performed on the patient's distal femur 902 based on the predetermined rotation of the femur. As illustrated in
After the final resectioning of the patient's distal femur is complete, the joint force balance of the patient's knee joint is verified in block 818. To do so, the orthopaedic surgeon may place the tibial paddle 34 of the sensor module 12 on the resected plateau 850 of the patient's proximal tibia 900 as illustrated in
The system 10 has been described above in regard to the measuring, determining, and displaying of joint forces. Such joint forces generally correspond to the joint pressure of the patient's joint over a defined area. As such, it should be appreciated that in other embodiments the sensor module 12, the hand-held display module 14, and the computer assisted surgery system 18 may be configured to measure, determine, and display the pressure of the patient's relative joint in addition to or alternatively to the patient's joint force. For example, in one embodiment, the pressure of the patient's joint may be determined based on the known area of each sensor of the pressure sensors or sensor elements 100 of the sensor array 90.
While the disclosure has been illustrated and described in detail in the drawings and foregoing description, such an illustration and description is to be considered as illustrative and not restrictive in character, it being understood that only illustrative embodiments have been shown and described and that all changes and modifications that come within the spirit of the disclosure are desired to be protected.
There are a plurality of advantages of the present disclosure arising from the various features of the devices, systems, and methods described herein. It will be noted that alternative embodiments of the devices, systems, and methods of the present disclosure may not include all of the features described yet still benefit from at least some of the advantages of such features. Those of ordinary skill in the art may readily devise their own implementations of the devices, systems, and methods that incorporate one or more of the features of the present invention and fall within the spirit and scope of the present disclosure as defined by the appended claims.
Number | Name | Date | Kind |
---|---|---|---|
4501266 | McDaniel | Feb 1985 | A |
4566448 | Rohr, Jr. | Jan 1986 | A |
4795473 | Grimes | Jan 1989 | A |
4796610 | Cromartie | Jan 1989 | A |
4804000 | Lamb | Feb 1989 | A |
4808186 | Smith | Feb 1989 | A |
4822362 | Walker | Apr 1989 | A |
4825857 | Kenna | May 1989 | A |
4828562 | Kenna | May 1989 | A |
4834057 | McLeod | May 1989 | A |
4856993 | Maness et al. | Aug 1989 | A |
4888021 | Forte | Dec 1989 | A |
4892093 | Zarnowski | Jan 1990 | A |
4892546 | Kotz | Jan 1990 | A |
4899761 | Brown et al. | Feb 1990 | A |
4907578 | Petersen | Mar 1990 | A |
4926847 | Luckman | May 1990 | A |
4932974 | Pappas | Jun 1990 | A |
4935023 | Whiteside | Jun 1990 | A |
4936853 | Fabian et al. | Jun 1990 | A |
4938762 | Wehrli | Jul 1990 | A |
4944756 | Kenna | Jul 1990 | A |
4959071 | Brown | Sep 1990 | A |
4963153 | Noesberger | Oct 1990 | A |
4973331 | Pursley et al. | Nov 1990 | A |
4979949 | Matsen et al. | Dec 1990 | A |
4986281 | Preves et al. | Jan 1991 | A |
5002547 | Poggie et al. | Mar 1991 | A |
5018514 | Grood et al. | May 1991 | A |
5020797 | Burns | Jun 1991 | A |
5032132 | Matsen | Jul 1991 | A |
5033291 | Podoloff et al. | Jul 1991 | A |
5037423 | Kenna | Aug 1991 | A |
5056530 | Butler et al. | Oct 1991 | A |
5080675 | Lawes et al. | Jan 1992 | A |
5082003 | Lamb et al. | Jan 1992 | A |
5098436 | Ferrante et al. | Mar 1992 | A |
5122144 | Bert | Jun 1992 | A |
5125408 | Basser | Jun 1992 | A |
5129909 | Sutherland | Jul 1992 | A |
5197488 | Kovacevic | Mar 1993 | A |
5207711 | Caspari et al. | May 1993 | A |
5213112 | Niwa | May 1993 | A |
5228459 | Caspari et al. | Jul 1993 | A |
5234433 | Bert | Aug 1993 | A |
5234434 | Goble | Aug 1993 | A |
5234435 | Seagrave | Aug 1993 | A |
5236432 | Matsen et al. | Aug 1993 | A |
5250050 | Poggie et al. | Oct 1993 | A |
5257996 | McGuire | Nov 1993 | A |
5312411 | Steele et al. | May 1994 | A |
5326363 | Aikins | Jul 1994 | A |
5329933 | Graf | Jul 1994 | A |
5342367 | Ferrante et al. | Aug 1994 | A |
5358527 | Forte | Oct 1994 | A |
5360016 | Kovacevic | Nov 1994 | A |
5364401 | Ferrante | Nov 1994 | A |
5364402 | Mumme | Nov 1994 | A |
5395401 | Bahler | Mar 1995 | A |
5403319 | Matsen et al. | Apr 1995 | A |
5417694 | Marik et al. | May 1995 | A |
5425775 | Kovacevic | Jun 1995 | A |
5431652 | Shimamoto et al. | Jul 1995 | A |
5431653 | Callaway | Jul 1995 | A |
5443518 | Insall | Aug 1995 | A |
5456724 | Yen et al. | Oct 1995 | A |
5470354 | Hershberger et al. | Nov 1995 | A |
5489311 | Cipolletti | Feb 1996 | A |
5496352 | Renger | Mar 1996 | A |
5514144 | Bolton | May 1996 | A |
5514183 | Epstein | May 1996 | A |
5520695 | Luckman | May 1996 | A |
5540696 | Booth et al. | Jul 1996 | A |
5562674 | Stalcup et al. | Oct 1996 | A |
5569261 | Marik et al. | Oct 1996 | A |
5571110 | Matsen et al. | Nov 1996 | A |
5571197 | Insall | Nov 1996 | A |
5597379 | Haines | Jan 1997 | A |
5611774 | Postelmans | Mar 1997 | A |
5613971 | Lower | Mar 1997 | A |
5630820 | Todd | May 1997 | A |
5643272 | Haines | Jul 1997 | A |
5649929 | Callaway | Jul 1997 | A |
5656785 | Trainor et al. | Aug 1997 | A |
5658293 | Vanlaningham | Aug 1997 | A |
5669914 | Eckhoff | Sep 1997 | A |
5671695 | Schroeder | Sep 1997 | A |
5682886 | Delp et al. | Nov 1997 | A |
5683397 | Vendrely et al. | Nov 1997 | A |
5688280 | Booth, Jr. et al. | Nov 1997 | A |
5688282 | Baron et al. | Nov 1997 | A |
5690635 | Matsen et al. | Nov 1997 | A |
5702422 | Stone | Dec 1997 | A |
5702463 | Pothier et al. | Dec 1997 | A |
5733292 | Gustilo et al. | Mar 1998 | A |
5735904 | Pappas | Apr 1998 | A |
5743909 | Collette | Apr 1998 | A |
5769894 | Ferragamo | Jun 1998 | A |
5782925 | Collazo et al. | Jul 1998 | A |
5800438 | Tuke | Sep 1998 | A |
5800552 | Forte | Sep 1998 | A |
5810827 | Haines | Sep 1998 | A |
5824104 | Tuke | Oct 1998 | A |
5840047 | Stedham | Nov 1998 | A |
5860980 | Axelson et al. | Jan 1999 | A |
5871018 | Delp et al. | Feb 1999 | A |
5879389 | Koshino | Mar 1999 | A |
5880976 | DiGioia, III et al. | Mar 1999 | A |
5891150 | Chan | Apr 1999 | A |
5911723 | Ashby | Jun 1999 | A |
5931777 | Sava | Aug 1999 | A |
5935086 | Beacon et al. | Aug 1999 | A |
6013103 | Kaufman et al. | Jan 2000 | A |
6019767 | Howell | Feb 2000 | A |
6022377 | Nuelle et al. | Feb 2000 | A |
6034296 | Elvin et al. | Mar 2000 | A |
6056752 | Roger | May 2000 | A |
6056754 | Haines | May 2000 | A |
6056756 | Eng et al. | May 2000 | A |
6080154 | Reay-Young et al. | Jun 2000 | A |
6086592 | Rosenberg | Jul 2000 | A |
6096043 | Techiera et al. | Aug 2000 | A |
6102952 | Koshino | Aug 2000 | A |
6113604 | Whittaker et al. | Sep 2000 | A |
6126692 | Robie et al. | Oct 2000 | A |
6165142 | Bar | Dec 2000 | A |
6174294 | Crabb et al. | Jan 2001 | B1 |
6447448 | Ishikawa et al. | Sep 2002 | B1 |
6488711 | Grafinger | Dec 2002 | B1 |
6540787 | Biegun et al. | Apr 2003 | B2 |
6553681 | Ekholm, Jr. et al. | Apr 2003 | B2 |
6575980 | Robie et al. | Jun 2003 | B1 |
6589283 | Metzger | Jul 2003 | B1 |
6610096 | MacDonald | Aug 2003 | B2 |
6632225 | Sanford et al. | Oct 2003 | B2 |
6648896 | Overes | Nov 2003 | B2 |
6702821 | Bonutti | Mar 2004 | B2 |
6706005 | Roy et al. | Mar 2004 | B2 |
6758850 | Smith et al. | Jul 2004 | B2 |
6770078 | Bonutti | Aug 2004 | B2 |
6821299 | Kirking et al. | Nov 2004 | B2 |
6827723 | Carson | Dec 2004 | B2 |
6856834 | Treppo et al. | Feb 2005 | B2 |
6905513 | Metzger | Jun 2005 | B1 |
6923817 | Carson | Aug 2005 | B2 |
6972039 | Metzger et al. | Dec 2005 | B2 |
6984249 | Keller | Jan 2006 | B2 |
7104996 | Bonutti | Sep 2006 | B2 |
7153281 | Holmes | Dec 2006 | B2 |
7232416 | Czernicki | Jun 2007 | B2 |
7275218 | Petrella et al. | Sep 2007 | B2 |
7412897 | Crottet et al. | Aug 2008 | B2 |
7559931 | Stone | Jul 2009 | B2 |
7575602 | Amirouche et al. | Aug 2009 | B2 |
7615055 | DiSilvestro | Nov 2009 | B2 |
7794499 | Navarro et al. | Sep 2010 | B2 |
7849751 | Clark et al. | Dec 2010 | B2 |
7892236 | Bonutti | Feb 2011 | B1 |
8118815 | van der Walt | Feb 2012 | B2 |
20010021877 | Biegun et al. | Sep 2001 | A1 |
20020029045 | Bonutti | Mar 2002 | A1 |
20020052606 | Bonutti | May 2002 | A1 |
20020133175 | Carson | Sep 2002 | A1 |
20020147455 | Carson | Oct 2002 | A1 |
20020156480 | Overes et al. | Oct 2002 | A1 |
20030028196 | Bonutti | Feb 2003 | A1 |
20030069591 | Carson et al. | Apr 2003 | A1 |
20030069644 | Kovacevic et al. | Apr 2003 | A1 |
20030130665 | Pinczewski et al. | Jul 2003 | A1 |
20030144669 | Robinson | Jul 2003 | A1 |
20030153978 | Whiteside | Aug 2003 | A1 |
20030187452 | Smith et al. | Oct 2003 | A1 |
20030236472 | Van Hoeck et al. | Dec 2003 | A1 |
20040019382 | Amirouche et al. | Jan 2004 | A1 |
20040064073 | Heldreth | Apr 2004 | A1 |
20040064191 | Wasielewski | Apr 2004 | A1 |
20040097951 | Steffensmeier | May 2004 | A1 |
20040122441 | Muratsu | Jun 2004 | A1 |
20040243148 | Wasielewski | Dec 2004 | A1 |
20050010302 | Dietz et al. | Jan 2005 | A1 |
20050021044 | Stone et al. | Jan 2005 | A1 |
20050038442 | Freeman | Feb 2005 | A1 |
20050085920 | Williamson | Apr 2005 | A1 |
20050113846 | Carson | May 2005 | A1 |
20050149041 | McGinley et al. | Jul 2005 | A1 |
20050177169 | Fisher et al. | Aug 2005 | A1 |
20050177170 | Fisher et al. | Aug 2005 | A1 |
20050177173 | Aebi et al. | Aug 2005 | A1 |
20050234332 | Murphy | Oct 2005 | A1 |
20050234448 | McCarthy | Oct 2005 | A1 |
20050234465 | McCombs et al. | Oct 2005 | A1 |
20050234466 | Stallings | Oct 2005 | A1 |
20050234468 | Carson | Oct 2005 | A1 |
20050251026 | Stone | Nov 2005 | A1 |
20050267485 | Cordes et al. | Dec 2005 | A1 |
20060012736 | Nishino et al. | Jan 2006 | A1 |
20060081063 | Neubauer et al. | Apr 2006 | A1 |
20060149277 | Cinquin et al. | Jul 2006 | A1 |
20060161051 | Terrill-Grisoni et al. | Jul 2006 | A1 |
20060224088 | Roche | Oct 2006 | A1 |
20060241569 | DiSilvestro | Oct 2006 | A1 |
20060271056 | Terrill-Grisoni et al. | Nov 2006 | A1 |
20070162142 | Stone | Jul 2007 | A1 |
20070219561 | Lavallee et al. | Sep 2007 | A1 |
20070233144 | Lavallee | Oct 2007 | A1 |
20070239165 | Amirouche | Oct 2007 | A1 |
20070244488 | Metzger et al. | Oct 2007 | A1 |
20080051892 | Malandain | Feb 2008 | A1 |
20080133022 | Caylor | Jun 2008 | A1 |
20080306413 | Crottet et al. | Dec 2008 | A1 |
20090005708 | Johanson et al. | Jan 2009 | A1 |
20090018544 | Heavener | Jan 2009 | A1 |
20090099570 | Paradis et al. | Apr 2009 | A1 |
20090138019 | Wasielewski | May 2009 | A1 |
20090138021 | Colquhoun | May 2009 | A1 |
20090270869 | Colquhoun et al. | Oct 2009 | A1 |
20090318836 | Stone et al. | Dec 2009 | A1 |
20090318930 | Stone et al. | Dec 2009 | A1 |
20090318931 | Stone et al. | Dec 2009 | A1 |
20090326544 | Chessar et al. | Dec 2009 | A1 |
20100016705 | Stone | Jan 2010 | A1 |
20100063508 | Borja et al. | Mar 2010 | A1 |
20100063509 | Borja et al. | Mar 2010 | A1 |
20100064216 | Borja et al. | Mar 2010 | A1 |
20100069911 | Borja et al. | Mar 2010 | A1 |
20100076505 | Borja | Mar 2010 | A1 |
20100137869 | Borja et al. | Jun 2010 | A1 |
20100137871 | Borja | Jun 2010 | A1 |
20100198275 | Chana et al. | Aug 2010 | A1 |
20100250571 | Pierce et al. | Sep 2010 | A1 |
20110251694 | Wasielewski | Oct 2011 | A1 |
Number | Date | Country |
---|---|---|
10335410 | Feb 2005 | DE |
0720834 | Jun 1999 | EP |
0979636 | Feb 2000 | EP |
1129676 | Sep 2001 | EP |
1245193 | Oct 2002 | EP |
1348382 | Oct 2003 | EP |
1402857 | Mar 2004 | EP |
1645229 | Apr 2006 | EP |
1707159 | Oct 2006 | EP |
1800616 | Jun 2007 | EP |
1915951 | Apr 2008 | EP |
1707159 | Nov 2008 | EP |
1402857 | Aug 2010 | EP |
1915951 | Jun 2011 | EP |
7900739 | Oct 1979 | WO |
9617552 | Jun 1996 | WO |
9617552 | Jun 1996 | WO |
9935972 | Jul 1999 | WO |
02071924 | Sep 2002 | WO |
03065949 | Aug 2003 | WO |
03084412 | Oct 2003 | WO |
2004008988 | Jan 2004 | WO |
2005023120 | Mar 2005 | WO |
2005089681 | Sep 2005 | WO |
2007036694 | Apr 2007 | WO |
2007036699 | Apr 2007 | WO |
2007036694 | Apr 2007 | WO |
2007036699 | Apr 2007 | WO |
2007036699 | Apr 2007 | WO |
2010011978 | Jan 2010 | WO |
2010022272 | Feb 2010 | WO |
2010022272 | Feb 2010 | WO |
2010030809 | Mar 2010 | WO |
Entry |
---|
European Search Report for European Patent Application No. 10156105.8-2319, Jun. 15, 2010, 8 pgs. |
European Search Report, dated Jul. 14, 2006. |
European Search Report, European Patent Application No. 10156120.7-2201, Jul. 7, 2010, 6 pages. |
European Communication pursuant to Article 94(3) EPC, European Patent Application No. 10156105.8-2319, Aug. 1, 2012, 5 pages. |
European Search Report, European Patent Application No. 10156132.7-2201, Jul. 12, 2010, 6 pages. |
European Search Report, European Patent Application No. 10156128.0-1526/2237014, Dec. 13, 2012, 6 pages. |
Jian Wu et al., A Method for Widening the Range of Force Measurement and Gap Adjustment in the Total Knee Replacement, International Conference on BioMedical Engineering and Informatics, 2008, 4 pages. |
Number | Date | Country | |
---|---|---|---|
20100249660 A1 | Sep 2010 | US |