US 9,008,757 B2Grant
Navigation system including optical and non-optical sensors
Issue Date:2015-04-14
•31 Claims
•10 Drawing Sheets
Abstract
Systems and methods that utilize optical sensors and non-optical sensors to determine the position and/or orientation of objects. A navigation system includes an optical sensor for receiving optical signals from markers and a non-optical sensor, such as a gyroscope, for generating non-optical data. A navigation computer determines positions and/or orientations of objects based on optical and non-optical data.
Metadata
Assignee
- Stryker Corporation
Inventor
- Chunwu Wu
Application Information
Application Number:US 14/035,207
Filing Date:2013-09-24
Priority Date:2012-09-26
Art Unit:3737
Classifications
IPC:
A61B5/05A61B5/06A61B19/00
Patent Drawings (10 sheets)
Description
RELATED APPLICATIONS
[0001] This application claims priority to and the benefit of U.S. Provisional Patent Application No. 61/705,804, filed on Sep. 26, 2012, the entire contents of which are hereby incorporated by reference.
FIELD OF THE INVENTION
[0002] The present invention relates generally to a navigation system that tracks objects in space by determining changes in the position and/or orientation of such objects over time. More specifically, the present invention relates to navigation systems that utilize optical sensors and non-optical sensors to determine the position and/or orientation of objects.
BACKGROUND OF THE INVENTION
[0003] Navigation systems assist users in precisely locating objects. For instance, navigation systems are used in industrial, aerospace, defense, and medical applications. In the medical field, navigation systems assist surgeons in precisely placing surgical instruments relative to a patient's anatomy.
[0004] Surgeries in which navigation systems are used include neurosurgery and orthopedic surgery. Often the instrument and the anatomy are tracked together with their relative movement shown on a display. The navigation system may display the instrument moving in conjunction with a preoperative image or an intraoperative image of the anatomy. Preoperative images are typically prepared by MRI or CT scans, while intraoperative images may be prepared using a fluoroscope, low level x-ray or any similar device. Alternatively, some systems are image-less in which the patient's anatomy is “painted” by a navigation probe and mathematically fitted to an anatomical model for display.
[0005] Navigation systems may employ light signals, sound waves, magnetic fields, RF signals, etc. in order to track the position and/or orientation of the instrument and anatomy. Optical navigation systems are widely used due to the accuracy of such systems.
[0006] Prior art optical navigation systems typically include one or more camera units that house one or more optical sensors (such as charge coupled devices or CCDs). The optical sensors detect light emitted from trackers attached to the instrument and the anatomy. Each tracker has a plurality of optical emitters such as light emitting diodes (LEDs) that periodically transmit light to the sensors to determine the position of the LEDs.
[0007] The positions of the LEDs on the instrument tracker correlate to the coordinates of a working end of the instrument relative to a camera coordinate system. The positions of the LEDs on the anatomy tracker(s) correlate to the coordinates of a target area of the anatomy in three-dimensional space relative to the camera coordinate system. Thus, the position and/or orientation of the working end of the instrument relative to the target area of the anatomy can be tracked and displayed.
[0008] Navigation systems can be used in a closed loop manner to control movement of surgical instruments. In these navigation systems both the instrument and the anatomy being treated are outfitted with trackers such that the navigation system can track their position and orientation. Information from the navigation system is then fed to a control system to control or guide movement of the instrument. In some cases, the instrument is held by a robot and the information is sent from the navigation system to a control system of the robot.
[0009] In order for the control system to quickly account for relative motion between the instrument and the anatomy being treated, the accuracy and speed of the navigation system must meet the desired tolerances of the procedure. For instance, tolerances associated with cementless knee implants may be very small to ensure adequate fit and function of the implant. Accordingly, the accuracy and speed of the navigation system may need to be greater than in more rough cutting procedures.
[0010] One of the limitations on accuracy and speed of optical navigation systems is that the system relies on the line-of-sight between the LEDs and the optical sensors of the camera unit. When the line-of-sight is broken, the system may not accurately determine the position and/or orientation of the instrument and anatomy being tracked. As a result, surgeries can encounter many starts and stops. For instance, during control of robotically assisted cutting, when the line-of-sight is broken, the cutting tool must be disabled until the line-of-sight is regained. This can cause significant delays and added cost to the procedure.
[0011] Another limitation on accuracy occurs when using active LEDs on the trackers. In such systems, the LEDs are often fired in sequence. In this case only the position of the actively fired LED is measured and known by the system, while the positions of the remaining, unmeasured LEDs are unknown. In these systems, the positions of the remaining, unmeasured LEDs are approximated. Approximations are usually based on linear velocity data extrapolated from the last known measured positions of the currently unmeasured LEDs. However, because the LEDs are fired in sequence, there can be a considerable lag between measurements of any one LED. This lag is increased with each additional tracker used in the system. Furthermore, this approximation does not take into account rotations of the trackers, resulting in further possible errors in position data for the trackers.
[0012] As a result, there is a need in the art for an optical navigation system that utilizes additional non-optically based data to improve tracking and provide a level of accuracy and speed with which to determine position and/or orientations of objects for precise surgical procedures such as robotically assisted surgical cutting.
SUMMARY OF THE INVENTION
[0013] The present invention relates to systems and methods that utilize optical sensors and non-optical sensors to determine the position and/or orientation of objects.
[0014] In one version of the invention a navigation system is provided for tracking an object. The navigation system includes an optical sensor that receives optical signals from one or more markers on a tracker. The tracker also includes a non-optical sensor that generates non-optical signals. A computing system determines a position of one of the markers at a first time based on a first optical signal. The computing system also determines a position of one or more of the other markers at the first time based on the first optical signal and a non-optical signal from the non-optical sensor. The determined positions are then correlated to the object to track a position of the object.
[0015] In another version of the invention a navigation system is provided for tracking an object. The navigation system includes an optical sensor that receives optical signals sequentially from three markers on a tracker. The tracker also includes a non-optical sensor that generates non-optical signals. A computing system determines a position of a first of the markers at a first time based on a first optical signal from the first marker. The computing system also determines a position of a second and third of the markers at the first time based on the first optical signal and a non-optical signal from the non-optical sensor. The determined positions are then correlated to the object to track a position of the object.
[0016] In yet another version of the invention, a robotic surgical cutting system is provided. The system includes a robotic manipulator and a cutting tool. A robotic control system controls or constrains movement of the cutting tool in at least 5 degrees of freedom. A navigation system communicates with the robotic control system. The navigation system includes at least one optical sensor and a tracker mounted to the robotic manipulator. A tracker is also provided for mounting to a patient's anatomy. This anatomy tracker includes three markers and a non-optical sensor. The optical sensor receives optical signals from the markers and the non-optical sensor generates non-optical signals. The navigation system communicates position data indicative of a position of the anatomy to the robotic control system to control cutting of the anatomy such that the cutting occurs within a predefined boundary.
[0017] In another version of the invention a navigation system is provided that includes a localizer having at least one optical sensor. A tracker communicates with the optical sensor. The tracker includes three markers and a non-optical sensor. A computing system determines a position of each of the three markers in a localizer coordinate system based on optical signals and non-optical signals. The computing system performs a matching algorithm to match the determined positions of one or more of the markers in the localizer coordinate system with positions of the one or more of said markers in a model of the tracker established relative to a tracker coordinate system to obtain a transformation matrix to transform the tracker coordinate system to the localizer coordinate system.
[0018] In another version of the invention, a system is provided for tracking an object. The system comprises at least two optical sensors and a tracker for mounting to the object. The tracker has three markers and a non-optical sensor. The at least two optical sensors receives optical signals from the markers at an optical-sensing frequency of at least 100 Hz. The non-optical sensor generates non-optical signals at a non-optical sensing frequency of at least 100 Hz.
[0019] A method for tracking an object is also provided. The method includes receiving optical signals sequentially from markers and generating non-optical signals. A position of a first of the markers at a first time is determined based on a first optical signal from the first marker. A position of a second and third of the markers at the first time is determined based on the first optical signal and a non-optical signal from the non-optical sensor. The determined positions of the first, second, and third markers are correlated to the object to track a position of the object during the surgical procedure.
[0020] Another method for tracking an object during a surgical procedure is provided. In this method three markers are positioned in the field of view of the optical sensor so that the optical sensor receives optical signals sequentially from the markers. A computing system is then operated to determine a position of a first of the markers at a first time based on a first optical signal from the first marker and determine a position of a second and third of the markers at the first time based on the first optical signal and a non-optical signal from a non-optical sensor. The positions are then correlated to the object to track a position of the object during the surgical procedure.
BRIEF DESCRIPTION OF THE DRAWINGS
[0021] Advantages of the present invention will be readily appreciated as the same becomes better understood by reference to the following detailed description when considered in connection with the accompanying drawings wherein:
[0022] FIG. 1 is a perspective view of a navigation system of the present invention being used in conjunction with a robotic manipulator;
[0023] FIG. 2 is a schematic view of the navigation system;
[0024] FIG. 3 is schematic view of coordinate systems used with the navigation system;
[0025] FIG. 4 is a flow diagram of steps carried out by a localization engine of the navigation system;
[0026] FIG. 4A is a schematic illustration of matching measured LEDs with a tracker model to obtain a transformation matrix;
[0027] FIG. 5 is a flow diagram of steps carried out by the localization engine in a first alternative embodiment;
[0028] FIG. 5A is an illustration of a tracker model including real and virtual LEDs;
[0029] FIG. 6 is a flow diagram of steps carried out by the localization engine in a second alternative embodiment; and
[0030] FIG. 7 is a flow diagram of steps carried out by the localization engine when one or more LEDs are blocked from measurement.
DETAILED DESCRIPTION
I. Overview
[0031] Referring to FIG. 1 a surgical navigation system 20 is illustrated. System 20 is shown in a surgical setting such as an operating room of a medical facility. The navigation system 20 is set up to track movement of various objects in the operating room. Such objects include, for example, a surgical instrument 22, a femur F of a patient, and a tibia T of the patient. The navigation system 20 tracks these objects for purposes of displaying their relative positions and orientations to the surgeon and, in some cases, for purposes of controlling or constraining movement of the surgical instrument 22 relative to a predefined path or anatomical boundary.
[0032] The surgical navigation system 20 includes a computer cart assembly 24 that houses a navigation computer 26. A navigation interface is in operative communication with the navigation computer 26. The navigation interface includes a display 28 adapted to be situated outside of the sterile field and a display 29 adapted to be situated inside the sterile field. The displays 28, 29 are adjustably mounted to the computer cart assembly 24. Input devices 30, 32 such as a mouse and keyboard can be used to input information into the navigation computer 26 or otherwise select/control certain aspects of the navigation computer 26. Other input devices are contemplated including a touch screen (not shown) on displays 28, 29 or voice-activation.
[0033] A localizer 34 communicates with the navigation computer 26. In the embodiment shown, the localizer 34 is an optical localizer and includes a camera unit 36. The camera unit 36 has an outer casing 38 that houses one or more optical sensors 40. In some embodiments at least two optical sensors 40 are employed, preferably three. The optical sensors 40 may be three separate high resolution charge-coupled devices (CCD). In one embodiment three, one-dimensional CCDs are employed. It should be appreciated that in other embodiments, separate camera units, each with a separate CCD, or two or more CCDs, could also be arranged around the operating room. The CCDs detect infrared (IR) signals.
[0034] Camera unit 36 is mounted on an adjustable arm to position the optical sensors 40 above the zone in which the procedure is to take place to provide the camera unit 36 with a field of view of the below discussed trackers that, ideally, is free from obstructions.
[0035] The camera unit 36 includes a camera controller 42 in communication with the optical sensors 40 to receive signals from the optical sensors 40. The camera controller 42 communicates with the navigation computer 26 through either a wired or wireless connection (not shown). One such connection may be an IEEE 1394 interface, which is a serial bus interface standard for high-speed communications and isochronous real-time data transfer. Connection could also use a company specific protocol. In other embodiments, the optical sensors 40 communicate directly with the navigation computer 26.
[0036] Position and orientation signals and/or data are transmitted to the navigation computer 26 for purposes of tracking the objects. The computer cart assembly 24, display 28, and camera unit 36 may be like those described in U.S. Pat. No. 7,725,162 to Malackowski, et al. issued on May 25, 2010, entitled “Surgery System”, hereby incorporated by reference.
[0037] The navigation computer 26 can be a personal computer or laptop computer. Navigation computer 26 has the display 28, central processing unit (CPU) and/or other processors, memory (not shown), and storage (not shown). The navigation computer 26 is loaded with software as described below. The software converts the signals received from the camera unit 36 into data representative of the position and orientation of the objects being tracked.
[0038] Navigation system 20 includes a plurality of tracking devices 44, 46, 48, also referred to herein as trackers. In the illustrated embodiment, one tracker 44 is firmly affixed to the femur F of the patient and another tracker 46 is firmly affixed to the tibia T of the patient. Trackers 44, 46 are firmly affixed to sections of bone. Trackers 44, 46 may be attached to the femur F in the manner shown in U.S. Pat. No. 7,725,162, hereby incorporated by reference. In further embodiments, an additional tracker (not shown) is attached to the patella to track a position and orientation of the patella. In further embodiments, the trackers 44, 46 could be mounted to other tissue types or parts of the anatomy.
[0039] An instrument tracker 48 is firmly attached to the surgical instrument 22. The instrument tracker 48 may be integrated into the surgical instrument 22 during manufacture or may be separately mounted to the surgical instrument 22 in preparation for the surgical procedures. The working end of the surgical instrument 22, which is being tracked, may be a rotating bur, electrical ablation device, or the like. In the embodiment shown, the surgical instrument 22 is an end effector of a surgical manipulator. Such an arrangement is shown in U.S. Provisional Patent Application No. 61/679,258, entitled, “Surgical Manipulator Capable of Controlling a Surgical Instrument in either a Semi-Autonomous Mode or a Manual, Boundary Constrained Mode”, the disclosure of which is hereby incorporated by reference, and also in U.S. patent application Ser. No. 13/958,834, entitled, “Navigation System for use with a Surgical Manipulator Operable in Manual or Semi-Autonomous Mode”, the disclosure of which is hereby incorporated by reference.
[0040] The trackers 44, 46, 48 can be battery powered with an internal battery or may have leads to receive power through the navigation computer 26, which, like the camera unit 36, preferably receives external power.
[0041] In other embodiments, the surgical instrument 22 may be manually positioned by only the hand of the user, without the aid of any cutting guide, jib, or other constraining mechanism such as a manipulator or robot. Such a surgical instrument is described in U.S. Provisional Patent Application No. 61/662,070, entitled, “Surgical Instrument Including Housing, a Cutting Accessory that Extends from the Housing and Actuators that Establish the Position of the Cutting Accessory Relative to the Housing”, hereby incorporated by reference, and also in U.S. patent application Ser. No. 13/600,888, entitled “Surgical Instrument Including Housing, a Cutting Accessory that Extends from the Housing and Actuators that Establish the Position of the Cutting Accessory Relative to the Housing”, hereby incorporated by reference.
[0042] The optical sensors 40 of the localizer 34 receive light signals from the trackers 44, 46, 48. In the illustrated embodiment, the trackers 44, 46, 48 are active trackers. In this embodiment, each tracker 44, 46, 48 has at least three active markers 50 for transmitting light signals to the optical sensors 40. The active markers 50 can be light emitting diodes or LEDs 50. The optical sensors 40 preferably have sampling rates of 100 Hz or more, more preferably 300 Hz or more, and most preferably 500 Hz or more. In some embodiments, the optical sensors 40 have sampling rates of 1000 Hz. The sampling rate is the rate at which the optical sensors 40 receive light signals from sequentially fired LEDs 50. In some embodiments, the light signals from the LEDs 50 are fired at different rates for each tracker 44, 46, 48.
[0043] Referring to FIG. 2 , each of the LEDs 50 are connected to a tracker controller 62 located in a housing (not shown) of the associated tracker 44, 46, 48 that transmits/receives data to/from the navigation computer 26. In one embodiment, the tracker controllers 62 transmit data on the order of several Megabytes/second through wired connections with the navigation computer 26. In other embodiments, a wireless connection may be used. In these embodiments, the navigation computer 26 has a transceiver (not shown) to receive the data from the tracker controller 62.
[0044] In other embodiments, the trackers 44, 46, 48 may have passive markers (not shown), such as reflectors that reflect light emitted from the camera unit 36. The reflected light is then received by the optical sensors 40. Active and passive arrangements are well known in the art.
[0045] Each of the trackers 44, 46, 48 also includes a 3-dimensional gyroscope sensor 60 that measures angular velocities of the trackers 44, 46, 48. As is well known to those skilled in the art, the gyroscope sensors 60 output readings indicative of the angular velocities relative to x-, y-, and z-axes of a gyroscope coordinate system. These readings are multiplied by a conversion constant defined by the manufacturer to obtain measurements in degrees/second with respect to each of the x-, y-, and z-axes of the gyroscope coordinate system. These measurements can then be converted to an angular velocity vector {right arrow over (ω)} defined in radians/second.
[0046] The angular velocities measured by the gyroscope sensors 60 provide additional non-optically based kinematic data for the navigation system 20 with which to track the trackers 44, 46, 48. The gyroscope sensors 60 may be oriented along the axis of each coordinate system of the trackers 44, 46, 48. In other embodiments, each gyroscope coordinate system is transformed to its tracker coordinate system such that the gyroscope data reflects the angular velocities with respect to the x-, y-, and z-axes of the coordinate systems of the trackers 44, 46, 48.
[0047] Each of the gyroscope sensors 60 communicate with the tracker controller 62 located within the housing of the associated tracker that transmits/receives data to/from the navigation computer 26. The navigation computer 26 has one or more transceivers (not shown) to receive the data from the gyroscope sensors 60. The data can be received either through a wired or wireless connection.
[0048] The gyroscope sensors 60 preferably have sampling rates of 100 Hz or more, more preferably 300 Hz or more, and most preferably 500 Hz or more. In some embodiments, the gyroscope sensors 60 have sampling rates of 1000 Hz. The sampling rate of the gyroscope sensors 60 is the rate at which signals are sent out from the gyroscope sensors 60 to be converted into angular velocity data.
[0049] The sampling rates of the gyroscope sensors 60 and the optical sensors 40 are established or timed so that for each optical measurement of position there is a corresponding non-optical measurement of angular velocity.
[0050] Each of the trackers 44, 46, 48 also includes a 3-axis accelerometer 70 that measures acceleration along each of x-, y-, and z-axes of an accelerometer coordinate system. The accelerometers 70 provide additional non-optically based data for the navigation system 20 with which to track the trackers 44, 46, 48.
[0051] Each of the accelerometers 70 communicate with the tracker controller 62 located in the housing of the associated tracker that transmits/receives data to/from the navigation computer 26. One or more of the transceivers (not shown) of the navigation computer receives the data from the accelerometers 70.
[0052] The accelerometers 70 may be oriented along the axis of each coordinate system of the trackers 44, 46, 48. In other embodiments, each accelerometer coordinate system is transformed to its tracker coordinate system such that the accelerometer data reflects the accelerations with respect to the x-, y-, and z-axes of the coordinate systems of the trackers 44, 46, 48.
[0053] The navigation computer 26 includes a navigation processor 52. The camera unit 36 receives optical signals from the LEDs 50 of the trackers 44, 46, 48 and outputs to the processor 52 signals relating to the position of the LEDs 50 of the trackers 44, 46, 48 relative to the localizer 34. The gyroscope sensors 60 transmit non-optical signals to the processor 52 relating to the 3-dimensional angular velocities measured by the gyroscope sensors 60. Based on the received optical and non-optical signals, navigation processor 52 generates data indicating the relative positions and orientations of the trackers 44, 46, 48 relative to the localizer 34.
[0054] It should be understood that the navigation processor 52 could include one or more processors to control operation of the navigation computer 26. The processors can be any type of microprocessor or multi-processor system. The term processor is not intended to limit the scope of the invention to a single processor.
[0055] Prior to the start of the surgical procedure, additional data are loaded into the navigation processor 52. Based on the position and orientation of the trackers 44, 46, and the previously loaded data, navigation processor 52 determines the position of the working end of the surgical instrument 22 and the orientation of the surgical instrument 22 relative to the tissue against which the working end is to be applied. In some embodiments, navigation processor 52 forwards these data to a manipulator controller 54. The manipulator controller 54 can then use the data to control a robotic manipulator 56 as described in U.S. Provisional Patent Application No. 61/679,258, entitled, “Surgical Manipulator Capable of Controlling a Surgical Instrument in either a Semi-Autonomous Mode or a Manual, Boundary Constrained Mode, the disclosure of which is hereby incorporated by reference, and also in U.S. patent application Ser. No. 13/958,834, entitled, “Navigation System for use with a Surgical Manipulator Operable in Manual or Semi-Autonomous Mode”, the disclosure of which is hereby incorporated by reference.
[0056] The navigation processor 52 also generates image signals that indicate the relative position of the surgical instrument working end to the surgical site. These image signals are applied to the displays 28, 29. Displays 28, 29, based on these signals, generate images that allow the surgeon and staff to view the relative position of the surgical instrument working end to the surgical site. The displays, 28, 29, as discussed above, may include a touch screen or other input/output device that allows entry of commands.
II. Coordinate Systems and Transformation
[0057] Referring to FIG. 3 , tracking of objects is generally conducted with reference to a localizer coordinate system LCLZ. The localizer coordinate system has an origin and an orientation (a set of x-, y-, and z-axes). During the procedure one goal is to keep the localizer coordinate system LCLZ stationary. As will be described further below, an accelerometer mounted to the camera unit 36 may be used to track sudden or unexpected movement of the localizer coordinate system LCLZ, as may occur when the camera unit 36 is inadvertently bumped by surgical personnel.
[0058] Each tracker 44, 46, 48 and object being tracked also has its own coordinate system separate from localizer coordinate system LCLZ. Components of the navigation system that have their own coordinate systems are the bone trackers 44, 46 and the instrument tracker 48. These coordinate systems are represented as, respectively, bone tracker coordinate systems BTRK1, BTRK2, and instrument tracker coordinate system TLTR.
[0059] Navigation system 20 monitors the positions of the femur F and tibia T of the patient by monitoring the position of bone trackers 44, 46 firmly attached to bone. Femur coordinate system is FBONE and tibia coordinate system is TBONE, which are the coordinate systems of the bones to which the bone trackers 44, 46 are firmly attached.
[0060] Prior to the start of the procedure, pre-operative images of the femur F and tibia T are generated (or of other tissues in other embodiments). These images may be based on MRI scans, radiological scans or computed tomography (CT) scans of the patient's anatomy. These images are mapped to the femur coordinate system FBONE and tibia coordinate system TBONE using well known methods in the art. In one embodiment, a pointer instrument P, such as disclosed in U.S. Pat. No. 7,725,162 to Malackowski, et al., hereby incorporated by reference, having its own tracker PT (see FIG. 2 ), may be used to map the femur coordinate system FBONE and tibia coordinate system TBONE to the pre-operative images. These images are fixed in the femur coordinate system FBONE and tibia coordinate system TBONE.
[0061] During the initial phase of the procedure, the bone trackers 44, 46 are firmly affixed to the bones of the patient. The pose (position and orientation) of coordinate systems FBONE and TBONE are mapped to coordinate systems BTRK1 and BTRK2, respectively. Given the fixed relationship between the bones and their bone trackers 44, 46, the pose of coordinate systems FBONE and TBONE remain fixed relative to coordinate systems BTRK1 and BTRK2, respectively, throughout the procedure. The pose-describing data are stored in memory integral with both manipulator controller 54 and navigation processor 52.
[0062] The working end of the surgical instrument 22 (also referred to as energy applicator distal end) has its own coordinate system EAPP. The origin of the coordinate system EAPP may represent a centroid of a surgical cutting bur, for example. The pose of coordinate system EAPP is fixed to the pose of instrument tracker coordinate system TLTR before the procedure begins. Accordingly, the poses of these coordinate systems EAPP, TLTR relative to each other are determined. The pose-describing data are stored in memory integral with both manipulator controller 54 and navigation processor 52.
III. Software
[0063] Referring to FIG. 2 , a localization engine 100 is a software module that can be considered part of the navigation system 20. Components of the localization engine 100 run on navigation processor 52. In some versions of the invention, the localization engine 100 may run on the manipulator controller 54.
[0064] Localization engine 100 receives as inputs the optically-based signals from the camera controller 42 and the non-optically based signals from the tracker controller 62. Based on these signals, localization engine 100 determines the pose (position and orientation) of the bone tracker coordinate systems BTRK1 and BTRK2 in the localizer coordinate system LCLZ. Based on the same signals received for the instrument tracker 48, the localization engine 100 determines the pose of the instrument tracker coordinate system TLTR in the localizer coordinate system LCLZ.
[0065] The localization engine 100 forwards the signals representative of the poses of trackers 44, 46, 48 to a coordinate transformer 102. Coordinate transformer 102 is a navigation system software module that runs on navigation processor 52. Coordinate transformer 102 references the data that defines the relationship between the pre-operative images of the patient and the patient trackers 44, 46. Coordinate transformer 102 also stores the data indicating the pose of the working end of the surgical instrument relative to the instrument tracker 48.
[0066] During the procedure, the coordinate transformer 102 receives the data indicating the relative poses of the trackers 44, 46, 48 to the localizer 34. Based on these data and the previously loaded data, the coordinate transformer 102 generates data indicating the relative position and orientation of both the coordinate system EAPP, and the bone coordinate systems, FBONE and TBONE to the localizer coordinate system LCLZ.
[0067] As a result, coordinate transformer 102 generates data indicating the position and orientation of the working end of the surgical instrument 22 relative to the tissue (e.g., bone) against which the instrument working end is applied. Image signals representative of these data are forwarded to displays 28, 29 enabling the surgeon and staff to view this information. In certain embodiments, other signals representative of these data can be forwarded to the manipulator controller 54 to control the manipulator 56 and corresponding movement of the surgical instrument 22.
[0068] Steps for determining the pose of each of the tracker coordinate systems BTRK1, BTRK2, TLTR in the localizer coordinate system LCLZ are the same, so only one will be described in detail. The steps shown in FIG. 4 are based on only one tracker being active, tracker 44. In the following description, the LEDs of tracker 44 shall be represented by numerals 50a, 50b, 50c which identify first 50a, second 50b, and third 50c LEDs.
[0069] The steps set forth in FIG. 4 illustrate the use of optically-based sensor data and non-optically based sensor data to determine the positions of the LEDs 50a, 50b, 50c of tracker 44. From these positions, the navigation processor 52 can determine the position and orientation of the tracker 44, and thus, the position and orientation of the femur F to which it is attached. Optically-based sensor data derived from the signals received by the optical sensors 40 provide line-of-sight based data that relies on the line-of-sight between the LEDs 50a, 50b, 50c and the optical sensors 40. However, the gyroscope sensor 60, which provides non-optically based signals for generating non-optically based sensor data do not rely on line-of-sight and thus can be integrated into the navigation system 20 to better approximate positions of the LEDs 50a, 50b, 50c when two of the LEDs 50a, 50b, 50c are not being measured (since only one LED measured at a time), or when one or more of the LEDs 50a, 50b, 50c are not visible to the optical sensors 40 during a procedure.
[0070] In a first initialization step 200, the system 20 measures the position of the LEDs 50a, 50b, 50c for the tracker 44 in the localizer coordinate system LCLZ to establish initial position data. These measurements are taken by sequentially firing the LEDs 50a, 50b, 50c, which transmits light signals to the optical sensors 40. Once the light signals are received by the optical sensors 40, corresponding signals are generated by the optical sensors 40 and transmitted to the camera controller 42. The frequency between firings of the LEDs 50a, 50b, 50c is 100 Hz or greater, preferably 300 Hz or greater, and more preferably 500 Hz or greater. In some cases, the frequency between firings is 1000 Hz or 1 millisecond between firings.
[0071] In some embodiments, only one LED can be read by the optical sensors 40 at a time. The camera controller 42, through one or more infrared or RF transceivers (on camera unit 36 and tracker 44) may control the firing of the LEDs 50a, 50b, 50c, as described in U.S. Pat. No. 7,725,162 to Malackowski, et al., hereby incorporated by reference. Alternatively, the tracker 44 may be activated locally (such as by a switch on tracker 44) which then fires its LEDs 50a, 50b, 50c sequentially once activated, without instruction from the camera controller 42.
[0072] Based on the inputs from the optical sensors 40, the camera controller 42 generates raw position signals that are then sent to the localization engine 100 to determine the position of each of the corresponding three LEDs 50a, 50b, 50c in the localizer coordinate system LCLZ.
[0073] During the initialization step 200, in order to establish the initial position data, movement of the tracker 44 must be less than a predetermined threshold. A value of the predetermined threshold is stored in the navigation computer 26. The initial position data established in step 200 essentially provides a static snapshot of position of the three LEDs 50a, 50b, 50c at an initial time t0, from which to base the remaining steps of the process. During initialization, velocities of the LEDs 50a, 50b, 50c are calculated by the localization engine 100 between cycles (i.e., each set of three LED measurements) and once the velocities are low enough, i.e., less than the predetermined threshold showing little movement occurred, then the initial position data or static snapshot is established. In some embodiments, the predetermined threshold (also referred to as the static velocity limit) is 200 mm/s or less, preferably 100 mm/s or less, and more preferably 10 mm/s or less along any axis. When the predetermined threshold is 100 mm/s, then the calculated velocities must be less than 100 mm/s to establish the static snapshot.
[0074] Referring to FIGS. 4 and 4A , once the static snapshot is taken, the positions of the measured LEDs 50a, 50b, 50c are compared to a model of the tracker 44 in step 202. The model is data stored in the navigation computer 26. The model data indicates the positions of the LEDs on the tracker 44 in the tracker coordinate system BTRK1. The system 20 has stored the number and position of the LEDs 50 of each tracker 44, 46, 48 in each tracker's coordinate system. For trackers 44, 46, 48 the origin of their coordinate systems is set at the centroid of all LED positions of the tracker 44.
[0075] The localization engine 100 utilizes a rigid body matching algorithm or point matching algorithm to match the measured LEDs 50a, 50b, 50c in the localizer coordinate system LCLZ to the LEDs in the stored model. Once the best-fit is determined, the localization engine 100 evaluates the deviation of the fit to determine if the measured LEDs 50a, 50b, 50c fit within a stored predefined tolerance of the model. The tolerance may be based on a distance between the corresponding LEDs such that if the fit results in too great of a distance, the initialization step has to be repeated. In some embodiments, the positions of the LEDs must not deviate from the model by more than 2.0 mm, preferably not more than 0.5 mm, and more preferably not more than 0.1 mm.
[0076] If the fit is within the predefined tolerance, a transformation matrix is generated to transform any other unmeasured LEDs in the model from the bone tracker coordinate system BTRK1 into the localizer coordinate system LCLZ in step 204. This step is utilized if more than three LEDs are used or if virtual LEDs are used as explained further below. In some embodiments, trackers 44, 46, 48 may have four or more LEDs. Once all positions in the localizer coordinate system LCLZ are established, an LED cloud is created. The LED cloud is an arrangement of all LEDs 50a, 50b, 50c on the tracker 44 in the localizer coordinate system LCLZ based on the x-, y-, and z-axis positions of all the LEDs 50a, 50b, 50c in the localizer coordinate system LCLZ.
[0077] Once the LED cloud is initially established, the navigation system 20 can proceed with tracking the tracker 44 during a surgical procedure. As previously discussed, this includes firing the next LED in the sequence. For illustration, LED 50a is now fired. Thus, LED 50a transmits light signals to the optical sensors 40. Once the light signals are received by the optical sensors 40, corresponding signals are generated by the optical sensors 40 and transmitted to the camera controller 42.
[0078] Based on the inputs from the optical sensors 40, the camera controller 42 generates a raw position signal that is then sent to the localization engine 100 to determine at time t1 the new position of LED 50a relative to the x-, y-, and z-axes of the localizer coordinate system LCLZ. This is shown in step 206 as a new LED measurement.
[0079] It should be appreciated that the designation of time such as t0, t1 . . . tn is used for illustrative purposes to indicate different times or different ranges of time or time periods and does not limit this invention to specific or definitive times.
[0080] With the new position of LED 50a determined, a linear velocity vector of LED 50a can be calculated by the localization engine 100 in step 208.
[0081] The tracker 44 is treated as a rigid body. Accordingly, the linear velocity vector of LED 50a is a vector quantity, equal to the time rate of change of its linear position. The velocity, even the acceleration of each LED, in localizer coordinate system LCLZ, can be calculated from the previously and currently measured positions and time of that LED in localizer coordinate system LCLZ. The previously and currently measured positions and time of a LED define the position history of that LED. The velocity calculation of LED 50a can take the simplest form of:
[0082]
Where {right arrow over (x)}p=(x,y,z)p and is the previously measured position of LED 50a at time tp; and {right arrow over (x)}q=(x,y,z)n and is the currently measured position of LED 50a at time tn. One can also obtain the velocity and/or acceleration of each LED by data fitting the LED position history of that LED as is well known to those skilled in the art.
Where {right arrow over (x)}p=(x,y,z)p and is the previously measured position of LED 50a at time tp; and {right arrow over (x)}q=(x,y,z)n and is the currently measured position of LED 50a at time tn. One can also obtain the velocity and/or acceleration of each LED by data fitting the LED position history of that LED as is well known to those skilled in the art.
[0083] At time t1, in step 210, the gyroscope sensor 60 is also measuring an angular velocity of the tracker 44. Gyroscope sensor 60 transmits signals to the tracker controller 62 related to this angular velocity.
[0084] The tracker controller 62 then transmits a corresponding signal to the localization engine 100 so that the localization engine 100 can calculate an angular velocity vector {right arrow over (ω)} from these signals. In step 210, the gyroscope coordinate system is also transformed to the bone tracker coordinate system BTRK1 so that the angular velocity vector {right arrow over (ω)} calculated by the localization engine 100 is expressed in the bone tracker coordinate system BTRK1.
[0085] In step 212, a relative velocity vector {right arrow over (v)}R is calculated for the origin of the bone tracker coordinate system BTRK1 with respect to position vector {right arrow over (x)}(LED50a to ORIGIN). This position vector {right arrow over (x)}(LED50a to ORIGIN) is also stored in memory in the navigation computer 26 for access by the localization engine 100 for the following calculation. This calculation determines the relative velocity of the origin {right arrow over (v)}R(ORIGIN) of the bone tracker coordinate system BTRK1 by calculating the cross product of the angular velocity vector {right arrow over (ω)} derived from the gyroscope signal and the position vector from LED 50a to the origin.
{right arrow over (v)}R(ORIGIN)={right arrow over (ω)}×{right arrow over (x)}(LED50a to ORIGIN)
{right arrow over (v)}R(ORIGIN)={right arrow over (ω)}×{right arrow over (x)}(LED50a to ORIGIN)
[0086] The localization engine 100 then calculates relative velocity vectors {right arrow over (v)}R for the remaining, unmeasured LEDs 50b, 50c (unmeasured because these LEDs have not been fired and thus their positions are not being measured). These velocity vectors can be calculated with respect to the origin of bone tracker coordinate system BTRK1.
[0087] The calculation performed by the localization engine 100 to determine the relative velocity vector {right arrow over (v)}R for each unmeasured LED 50b, 50c at time t1 is based on the cross product of the angular velocity vector {right arrow over (ω)} at time t1 and the position vectors {right arrow over (x)}(ORIGIN to LED50b) and {right arrow over (x)}(ORIGIN to LED50c), which are taken from the origin of bone tracker coordinate system BTRK1 to each of the unmeasured LEDs 50b, 50c. These position vectors {right arrow over (x)}(ORIGIN to LED50b) and {right arrow over (x)}(ORIGIN to LED50c) are stored in memory in the navigation computer 26 for access by the localization engine 100 for the following calculations:
{right arrow over (v)}R(LED50b)={right arrow over (ω)}×{right arrow over (x)}(ORIGIN to LED50b)
{right arrow over (v)}R(LED50c)={right arrow over (ω)}×{right arrow over (x)}(ORIGIN to LED50c)
{right arrow over (v)}R(LED50b)={right arrow over (ω)}×{right arrow over (x)}(ORIGIN to LED50b)
{right arrow over (v)}R(LED50c)={right arrow over (ω)}×{right arrow over (x)}(ORIGIN to LED50c)
[0088] Also in step 212, these relative velocities, which are calculated in the bone tracker coordinate system BTRK1, are transferred into the localizer coordinate system LCLZ using the transformation matrix determined in step 202. The relative velocities in the localizer coordinate system LCLZ are used in calculations in step 214.
[0089] In step 214 the velocity vector of the origin of the bone tracker coordinate system BTRK1 in the localizer coordinate system LCLZ at time t1 is first calculated by the localization engine 100 based on the measured velocity vector {right arrow over (v)}(LED50a) of LED 50a at time t1. The velocity vector {right arrow over (v)}(ORIGIN) is calculated by adding the velocity vector {right arrow over (v)}(LED50a) of LED 50a at time t1 and the relative velocity vector {right arrow over (v)}R(OR/G/N) of the origin at time t1 expressed relative to the position vector of LED 50a to the origin. Thus, the velocity vector of the origin at time t1 is calculated as follows:
{right arrow over (v)}(ORIGIN)={right arrow over (v)}(LED50a)+{right arrow over (v)}R(ORIGIN)
{right arrow over (v)}(ORIGIN)={right arrow over (v)}(LED50a)+{right arrow over (v)}R(ORIGIN)
[0090] Velocity vectors of the remaining, unmeasured LEDs in the localizer coordinate system LCLZ at time t1 can now be calculated by the localization engine 100 based on the velocity vector {right arrow over (v)}(ORIGIN) of the origin of the bone tracker coordinate system BTRK1 in the localizer coordinate system LCLZ at time t1 and their respective relative velocity vectors at time t1 expressed relative to their position vectors with the origin of the bone tracker coordinate system BTRK1. These velocity vectors at time t1 are calculated as follows:
{right arrow over (v)}(LED50b)={right arrow over (v)}(ORIGIN)+{right arrow over (v)}R(LED50b)
{right arrow over (v)}(LED50c)={right arrow over (v)}(ORIGIN)+{right arrow over (v)}R(LED50c)
{right arrow over (v)}(LED50b)={right arrow over (v)}(ORIGIN)+{right arrow over (v)}R(LED50b)
{right arrow over (v)}(LED50c)={right arrow over (v)}(ORIGIN)+{right arrow over (v)}R(LED50c)
[0091] In step 216, the localization engine 100 calculates the movements, i.e., the change in position Δx (in Cartesian coordinates), of each of the unmeasured LEDs 50b, 50c from time t0 to time t1 based on the calculated velocity vectors of LEDs 50b, 50c and the change in time. In some embodiments the change in time Δt for each LED measurement is two milliseconds or less, and in some embodiments one millisecond or less.
Δx(LED50b)={right arrow over (v)}(LED50b)×Δt
Δx(LED50c)={right arrow over (v)}(LED50c)×Δt
Δx(LED50b)={right arrow over (v)}(LED50b)×Δt
Δx(LED50c)={right arrow over (v)}(LED50c)×Δt
[0092] These calculated changes in position (x, y, z) can then be added to the previously determined positions of each of LEDs 50b, 50c in the localizer coordinate system LCLZ. Thus, in step 218, changes in position can be added to the previous positions of the LEDs 50b, 50c at time t0, which were determined during the static snapshot. This is expressed as follows:
x(LED50b)t1=x(LED50b)t0+Δx(LED50b)
x(LED50b)t1=x(LED50b)t0+Δx(LED50b)
[0093] In step 220, these calculated positions for each of LEDs 50b, 50c at time t1 are combined with the determined position of LED 50a at time t1. The newly determined positions of LEDs 50a, 50b, 50c are then matched to the model of tracker 44 to obtain a best fit using the point matching algorithm or rigid body matching algorithm. The result of this best fit calculation, if within the defined tolerance of the system 20, is that a new transformation matrix is created by the navigation processor 52 to link the bone tracker coordinate system BTRK1 to the localizer coordinate system LCLZ.
[0094] With the new transformation matrix the newly calculated positions of the unmeasured LEDs 50b, 50c are adjusted to the model in step 222 to provide adjusted positions. The measured position of LED 50a can also be adjusted due to the matching algorithm such that it is also recalculated. These adjustments are considered an update to the LED cloud. In some embodiments, the measured position of LED 50a is fixed to the model's position of LED 50a during the matching step.
[0095] With the best fit transformation complete, the measured (and possibly adjusted) position of LED 50a and the calculated (and adjusted) positions of LEDs 50b, 50c in the localizer coordinate system LCLZ enable the coordinate transformer 102 to determine a new position and orientation of the femur F based on the previously described relationships between the femur coordinate system FBONE, the bone tracker coordinate system BTRK1, and the localizer coordinate system LCLZ.
[0096] Steps 206 through 222 are then repeated at a next time t2 and start with the measurement in the localizer coordinate system LCLZ of LED 50b, with LEDs 50a, 50c being the unmeasured LEDs. As a result of this loop at each time t1, t2 . . . tn positions of each LED 50a, 50b, 50c are either measured (one LED being fired at each time) or calculated with the calculated positions being very accurately approximated based on measurements by the optical sensor 40 and the gyroscope sensor 60. This loop of steps 206 through 222 to determine the new positions of the LEDs 50 can be carried out by the localization engine 100 at a frequency of at least 100 Hz, more preferably at least 300 Hz, and most preferably at least 500 Hz.
[0097] Referring to FIG. 5 , the LED cloud may also include virtual LEDs, which are predetermined points identified on the model, but that do not actually correspond to physical LEDs on the tracker 44. The positions of these points may also be calculated at times t1, t2 . . . tn. These virtual LEDs can be calculated in the same fashion as the unmeasured LEDs with reference to FIG. 4 . The only difference is that the virtual LEDs are never fired or included in the sequence of optical measurements, since they do not correspond to any light source, but are merely virtual in nature. Steps 300-322 show the steps used for tracking the trackers 44, 46, using real and virtual LEDS. Steps 300-322 generally correspond to steps 200-222 except for the addition of the virtual LEDs, which are treated like unmeasured LEDs using the same equations described above.
[0098] One purpose of using virtual LEDs in addition to the LEDs 50a, 50b, 50c, for example, is to reduce the effect of errors in the velocity calculations described above. These errors may have little consequence on the calculated positions of the LEDs 50a, 50b, 50c, but can be amplified the further away from the LEDs 50a, 50b, 50c a point of interest is located. For instance, when tracking the femur F with tracker 44, the LEDs 50a, 50b, 50c incorporated in the tracker 44 may experience slight errors in their calculated positions of about 0.2 millimeters. However, consider the surface of the femur F that may be located over 10 centimeters away from the LEDs 50a, 50b, 50c. The slight error of 0.2 millimeters at the LEDs 50a, 50b, 50c can result in 0.4 to 2 millimeters of error on the surface of the femur F. The further away the femur F is located from the LEDs 50a, 50b, 50c the more the error increases. The use of virtual LEDs in the steps of FIG. 5 can reduce the potential amplification of such errors as described below.
[0099] Referring to FIG. 5A , one virtual LED 50d can be positioned on the surface of the femur F. Other virtual LEDs 50e, 50f, 50g, 50h, 50i, 50j, 50k can be positioned at random locations in the bone tracker coordinate system BTRK1 such as along each of the x-, y-, and z-axes, and on both sides of the origin along these axes to yield 6 virtual LEDs. These virtual LEDs are included as part of the model of the tracker 44 shown in FIG. 5A and used in steps 302 and 320. In some embodiments, only the virtual LEDs 50e-50k are used. In other embodiments, virtual LEDs may be positioned at locations along each of the x-, y-, and z-axes, but at different distances from the origin of the bone tracker coordinate system BTRK1. In still further embodiments, some or all of the virtual LEDs may be located off of the axes x-, y-, and z-.
[0100] Now in the model are real LEDs 50a, 50b, 50c and virtual LEDs 50d-50k. At each time t1, t2 . . . tn this extended model is matched in step 320 with the measured/calculated positions of real LEDs 50a, 50b, 50c and with the calculated positions of virtual LEDs 50d-50k to obtain the transformation matrix that links the bone tracker coordinate system BTRK1 with the localizer coordinate system LCLZ. Now, with the virtual LEDs 50d-50k included in the model, which are located at positions outlying the real LEDs 50a, 50b, 50c, the error in the rotation matrix can be reduced. In essence, the rigid body matching algorithm or point matching algorithm has additional points used for matching and some of these additional points are located radially outwardly from the points defining the real LEDs 50a, 50b, 50c, thus rotationally stabilizing the match.
[0101] In another variation of the process of FIG. 5 , the locations of the virtual LEDs 50e-50k can be changed dynamically during use depending on movement of the tracker 44. The calculated positions of the unmeasured real LEDs 50b, 50c and the virtual LEDs 50e-50k at time t1 are more accurate the slower the tracker 44 moves. Thus, the locations of virtual LEDs 50e-50k along the x-, y-, and z-axes relative to the origin of the bone tracker coordinate system BTRK1 can be adjusted based on speed of the tracker 44. Thus, if the locations of the virtual LEDs 50e-50k are denoted (s,0,0), (−s,0,0), (0,s,0), (0,−s,0), (0,0,s), (0,0,−s), respectively, then s would increase when the tracker 44 moves slowly and s would decrease to a smaller value when the tracker 44 moves faster. This could be handled by an empirical formula for s or s can be adjusted based on an estimate in the error in velocity and calculated positions.
[0102] Determining new positions of the LEDs 50 (real and virtual) can be carried out at a frequency of at least 100 Hz, more preferably at least 300 Hz, and most preferably at least 500 Hz.
[0103] Data from the accelerometers 70 can be used in situations where optical measurement of an LED 50 is impeded due to interference with the line-of-sight. When an LED to be measured is blocked, the localization engine 100 assumes a constant velocity of the origin to estimate positions. However, the constant velocity assumption in this situation may be inaccurate and result in errors. The accelerometers 70 essentially monitor if the constant velocity assumption in the time period is accurate. The steps shown in FIGS. 6 and 7 illustrate how this assumption is checked.
[0104] Continuing to use tracker 44 as an example, steps 400-422 of FIG. 6 generally correspond to steps 300-322 from FIG. 5 . However, in step 424, the system 20 determines whether, in the last cycle of measurements, less than 3 LEDs were measured—meaning that one or more of the LEDs in the cycle could not be measured. This could be caused by line-of-sight issues, etc. A cycle for tracker 44 is the last three attempted measurements. If during last the three measurements, each of the LEDs 50a, 50b, 50c were visible and could be measured, then the system 20 proceeds to step 408 and continues as previously described with respect to FIG. 5 .
[0105] If the system 20 determines that one or more of the LEDs 50a, 50b, 50c could not be measured during the cycle, i.e., were blocked from measurement, then the algorithm still moves to step 408, but if the new LED to be measured in step 406 was the one that could not be measured, the system makes some velocity assumptions as described below.
[0106] When a LED, such as LED 50a, is not seen by the optical sensor 40 at its measurement time to in step 406, the previously calculated velocity vector {right arrow over (v)}(OR/G/N) of the origin of the tracker 44 in the localizer coordinate system LCLZ at the previous time t(n−1) is assumed to remain constant. Accordingly, velocity vectors of LEDs 50a, 50b, 50c in the localizer coordinate system LCLZ can be calculated based on the previously calculated velocity vector {right arrow over (v)}(OR/G/N) in the localizer coordinate system LCLZ and the relative velocity vectors of LEDs 50a, 50b, 50c, which are derived from a newly measured angular velocity vector from the gyroscope 60. The equations described in steps 316-322 can then be used to determine new positions of the LEDs 50a, 50b, 50c.
[0107] To start, when LED 50a is to be measured at step 406, but is obstructed, the velocity vector of the origin is assumed to be the same as the previous calculation. Accordingly, the velocity of the new LED is not calculated at step 408:
{right arrow over (v)}(ORIGIN)=previous calculation
{right arrow over (v)}(ORIGIN)=previous calculation
[0108] Step 410 proceeds the same as step 310.
[0109] The relative velocity vectors {right arrow over (v)}R of LEDs 50a, 50b, 50c calculated in step 412 are then based on the previous velocity vector {right arrow over (v)}(ORIGIN) and the newly measured angular velocity vector from the gyroscope 60 in the bone tracker coordinate system BTRK1:
{right arrow over (v)}R(LED50a)={right arrow over (ω)}(current)×{right arrow over (x)}(ORIGIN to LED50a)
{right arrow over (v)}R(LED50b)={right arrow over (ω)}(current)×{right arrow over (x)}(ORIGIN to LED50b)
{right arrow over (v)}R(LED50c)={right arrow over (ω)}(current)×{right arrow over (x)}(ORIGIN to LED50c)
{right arrow over (v)}R(LED50a)={right arrow over (ω)}(current)×{right arrow over (x)}(ORIGIN to LED50a)
{right arrow over (v)}R(LED50b)={right arrow over (ω)}(current)×{right arrow over (x)}(ORIGIN to LED50b)
{right arrow over (v)}R(LED50c)={right arrow over (ω)}(current)×{right arrow over (x)}(ORIGIN to LED50c)
[0110] In step 414, velocity vectors in the localizer coordinate system LCLZ can the be calculated using the origin velocity vector {right arrow over (v)}(ORIGIN) and the relative velocity vectors {right arrow over (v)}R of LEDs 50a, 50b, 50c:
{right arrow over (v)}(LED50a)=(ORIGIN)+{right arrow over (v)}R(LED50a)
{right arrow over (v)}(LED50b)=(ORIGIN)+{right arrow over (v)}R(LED50b)
{right arrow over (v)}(LED50c)=(ORIGIN)+{right arrow over (v)}R(LED50c)
{right arrow over (v)}(LED50a)=(ORIGIN)+{right arrow over (v)}R(LED50a)
{right arrow over (v)}(LED50b)=(ORIGIN)+{right arrow over (v)}R(LED50b)
{right arrow over (v)}(LED50c)=(ORIGIN)+{right arrow over (v)}R(LED50c)
[0111] Steps 416 through 422 proceed the same as steps 316-322.
[0112] If the system 20 determines at step 424 that one or more of the LEDs 50a, 50b, 50c could not be measured during the cycle, i.e., were blocked from measurement, another algorithm is carried out simultaneously at steps 500-506 shown in FIG. 7 until a complete cycle of measurements is made where all of the LEDs 50a, 50b, 50c in the cycle were visible to the optical sensor 40. Thus, the system 20 is considered to be in a “blocked” condition until the complete cycle with all visible measurements is made.
[0113] Steps 500-506 are carried out continuously while the system 20 is in the blocked condition.
[0114] In step 500 the navigation processor 52 starts a clock that tracks how long the system 20 is in the blocked condition. The time in the blocked condition is referred to below as t(blocked).
[0115] In step 502, the accelerometer 70 measures accelerations along the x-, y-, and z-axes of the bone tracker coordinate system BTRK1 to track errors in the constant velocity assumption. Accelerometer readings, like gyroscope readings are transformed from the accelerometer coordinate system to the bone tracker coordinate system BTRK1.
[0116] If the accelerometer 70 detects acceleration(s) that exceed predefined acceleration tolerance(s), the navigation computer 26 will put the system 20 into an error condition. The acceleration tolerances could be defined differently along each x-, y-, and z-axis, or could be the same along each axis. If a measured acceleration exceeds a tolerance then the constant velocity assumption is unreliable and cannot be used for that particular application of surgical navigation. Different tolerances may be employed for different applications. For instance, during robotic cutting, the tolerance may be very low, but for visual navigation only, i.e., not feedback for cutting control loop, the tolerance may be set higher.
[0117] In step 504, velocity errors associated with the positions of the LEDs 50 relative to the optical sensor 40 are taken into account and monitored during the blocked condition. For each of the LEDs 50, the velocity error verror multiplied by the time in the blocked condition tblocked condition must be less than a position error tolerance γ and thus must satisfy the following equation to prevent the system 20 from being put into an error condition:
verror×tblocked condition<γ
verror×tblocked condition<γ
[0118] In this equation, the velocity error verror is calculated for each of the LEDs 50a, 50b, 50c as follows:
[0119]
[0120] Position errors xerror(t) and Xerror(t-1) are predefined position errors in the system 20 that are based on location relative to the optical sensors 40 at times t and t−1. In essence, the further away the LEDs 50a, 50b, 50c are located from the optical sensors 40, the higher the potential position errors. These positions errors are derived either experimentally or theoretically and placed in a look-up table or formula so that at each position of the LEDs 50a, 50b, 50c in Cartesian coordinates (x, y, z) an associated position error is provided.
[0121] In step 504, the localization engine 100 accesses this look-up table or calculates this formula to determine the position errors for each of LEDs 50a, 50b, 50c at the current time t and at the previous time t−1. The position errors are thus based on the positions in Cartesian coordinates in the localizer coordinate system LCLZ calculated by the system 20 in step 422 for the current time t and at the previous time t−1. The time variable Δt represents the time it takes for subsequent position calculations, so the difference between t and t−1, which for illustrative purposes may be 1 millisecond.
[0122] The position error tolerance γ is predefined in the navigation computer 26 for access by the localization engine 100. The position error tolerance γ could be expressed in millimeters. The position error tolerance γ can range from 0.001 to 1 millimeters and in some embodiments is specifically set at 0.5 millimeters. Thus, if the position error tolerance γ is set to 0.5 millimeters, the following equation must be satisfied:
verror×tblocked condition<0.5 millimeters
verror×tblocked condition<0.5 millimeters
[0123] As can be seen, the longer the system 20 is in the blocked condition, the larger the effect that the time variable has in this equation and thus the smaller the velocity errors that will be tolerated. In some embodiments, this equation is calculated by the localization engine 100 in step 504 separately for each of the LEDs 50a, 50b, 50c. In other embodiments, because of how closely arranged the LEDs 50a, 50b, 50c are on the tracker 44, the velocity error of only one of the LEDs 50a, 50b, 50c is used in this calculation to determine compliance.
[0124] In step 506, when the error(s) exceeds the position error tolerance γ, the system 20 is placed in an error condition. In such a condition, for example, any control or movement of cutting or ablation tools is ceased and the tools are shut down.
IV. Other Embodiments
[0125] In one embodiment, when each of the trackers 44, 46, 48 are being actively tracked, the firing of the LEDs occurs such that one LED from tracker 44 is fired, then one LED from tracker 46, then one LED from tracker 48, then a second LED from tracker 44, then a second LED from tracker 46, and so on until all LEDs have been fired and then the sequence repeats. This order of firing may occur through instruction signals sent from the transceivers (not shown) on the camera unit 36 to transceivers (not shown) on the trackers 44, 46, 48.
[0126] The navigation system 20 can be used in a closed loop manner to control surgical procedures carried out by surgical cutting instruments. Both the instrument 22 and the anatomy being cut are outfitted with trackers 50 such that the navigation system 20 can track the position and orientation of the instrument 22 and the anatomy being cut, such as bone.
[0127] In one embodiment, the navigation system is part of a robotic surgical system for treating tissue. In some versions, the robotic surgical system is a robotic surgical cutting system for cutting away material from a patient's anatomy, such as bone or soft tissue. The cutting system could be used to prepare bone for surgical implants such as hip and knee implants, including unicompartmental, bicompartmental, or total knee implants. Some of these types of implants are shown in U.S. patent application Ser. No. 13/530,927, entitled, “Prosthetic Implant and Method of Implantation”, the disclosure of which is hereby incorporated by reference.
[0128] The robotic surgical cutting system includes a manipulator (see, for instance, FIG. 1 ). The manipulator has a plurality of arms and a cutting tool carried by at least one of said plurality of arms. A robotic control system controls or constrains movement of the cutting tool in at least 5 degrees of freedom. An example of such a manipulator and control system are shown in U.S. Provisional Patent Application No. 61/679,258, entitled, “Surgical Manipulator Capable of Controlling a Surgical Instrument in either a Semi-Autonomous Mode or a Manual, Boundary Constrained Mode”, hereby incorporated by reference, and also in U.S. patent application Ser. No. 13/958,834, entitled, “Navigation System for use with a Surgical Manipulator Operable in Manual or Semi-Autonomous Mode”, the disclosure of which is hereby incorporated by reference.
[0129] In this embodiment, the navigation system 20 communicates with the robotic control system (which can include the manipulator controller 54). The navigation system 20 communicates position and/or orientation data to said robotic control system. The position and/or orientation data is indicative of a position and/or orientation of instrument 22 relative to the anatomy. This communication provides closed loop control to control cutting of the anatomy such that the cutting occurs within a predefined boundary.
[0130] In this embodiment, manipulator movement may coincide with LED measurements such that for each LED measurement taken, there is a corresponding movement of the instrument 22 by the manipulator 56. However, this may not always be the case. For instance, there may be such a lag between the last LED measurement and movement by the manipulator 56 that the position and/or orientation data sent from the navigation computer 26 to the manipulator 56 for purposes of control loop movement becomes unreliable. In such a case, the navigation computer 26 can be configured to also transmit to the manipulator controller 54 kinematic data. Such kinematic data includes the previously determined linear and angular velocities for the trackers 44, 46, 48. Since the velocities are already known, positions can calculated based on the lag of time. The manipulator controller 54 could then calculate, for purposes of controlling movement of the manipulator 56, the positions and orientations of the trackers 44, 46, 48 and thus, the relative positions and orientations of the instrument 22 (or instrument tip) to the femur F and/or tibia T.
[0131] In this embodiment, the instrument 22 is held by the manipulator shown in FIG. 1 or other robot that provides some form of mechanical constraint to movement. This constraint limits the movement of the instrument 22 to within a predefined boundary. If the instrument 22 strays beyond the predefined boundary, a control is sent to the instrument 22 to stop cutting.
[0132] When tracking both the instrument 22 and the anatomy being cut in real time in these systems, the need to rigidly fix anatomy in position can be eliminated. Since both the instrument 22 and anatomy are tracked, control of the instrument 22 can be adjusted based on relative position and/or orientation of the instrument 22 to the anatomy. Also, representations of the instrument 22 and anatomy on the display can move relative to one another—to emulate their real world motion.
[0133] In one embodiment, each of the femur F and tibia T has a target volume of material that is to be removed by the working end of the surgical instrument 22. The target volumes are defined by one or more boundaries. The boundaries define the surfaces of the bone that should remain after the procedure. In some embodiments, system 20 tracks and controls the surgical instrument 22 to ensure that working end, e.g., bur, only removes the target volume of material and does not extend beyond the boundary, as disclosed in Provisional Patent Application No. 61/679,258, entitled, “Surgical Manipulator Capable of Controlling a Surgical Instrument in either a Semi-Autonomous Mode or a Manual, Boundary Constrained Mode”, hereby incorporated by reference.
[0134] In the described embodiment, control of the instrument 22 is accomplished by utilizing the data generated by the coordinate transformer 102 that indicates the position and orientation of the bur or other cutting tool relative to the target volume. By knowing these relative positions, the surgical instrument 22 or the manipulator to which it is mounted, can be controlled so that only desired material is removed.
[0135] In other systems, the instrument 22 has a cutting tool that is movable in three degrees of freedom relative to a handheld housing and is manually positioned by the hand of the surgeon, without the aid of cutting jig, guide arm or other constraining mechanism. Such systems are shown in U.S. Provisional Patent Application No. 61/662,070, entitled, “Surgical Instrument Including Housing, a Cutting Accessory that Extends from the Housing and Actuators that Establish the Position of the Cutting Accessory Relative to the Housing”, the disclosure of which is hereby incorporated by reference.
[0136] In these embodiments, the system includes a hand held surgical cutting instrument having a cutting tool. A control system controls movement of the cutting tool in at least 3 degrees of freedom using internal actuators/motors, as shown in U.S. Provisional Patent Application No. 61/662,070, entitled, “Surgical Instrument Including Housing, a Cutting Accessory that Extends from the Housing and Actuators that Establish the Position of the Cutting Accessory Relative to the Housing”, the disclosure of which is hereby incorporated by reference. The navigation system 20 communicates with the control system. One tracker (such as tracker 48) is mounted to the instrument. Other trackers (such as trackers 44, 46) are mounted to a patient's anatomy.
[0137] In this embodiment, the navigation system 20 communicates with the control system of the hand held surgical cutting instrument. The navigation system 20 communicates position and/or orientation data to the control system. The position and/or orientation data is indicative of a position and/or orientation of the instrument 22 relative to the anatomy. This communication provides closed loop control to control cutting of the anatomy such that the cutting occurs within a predefined boundary (the term predefined boundary is understood to include predefined trajectory, volume, line, other shapes or geometric forms, and the like).
[0138] Features of the invention may be used to track sudden or unexpected movements of the localizer coordinate system LCLZ, as may occur when the camera unit 36 is bumped by surgical personnel. An accelerometer (not shown) mounted to camera unit 36 monitors bumps and stops system 20 if a bump is detected. In this embodiment, the accelerometer communicates with the camera controller 42 and if the measured acceleration along any of the x, y, or z axes exceeds a predetermined value, then the camera controller 42 sends a corresponding signal to the navigation computer 26 to disable the system 20 and await the camera unit 36 to stabilize and resume measurements. In some cases, the initialization step 200, 300, 400 would have to be repeated before resuming navigation.
[0139] In some embodiments, a virtual LED is positioned at the working tip of the instrument 22. In this embodiment, the virtual LED is located at the location of the working tip in the model of the instrument tracker 48 so that the working tip location is continuously calculated.
[0140] It is an object of the intended claims to cover all such modifications and variations that come within the true spirit and scope of this invention. Furthermore, the embodiments described above are related to medical applications, but the inventions described herein are also applicable to other applications such as industrial, aerospace, defense, and the like.
Claims
What is claimed is:
1. A navigation system for tracking an object, said navigation system comprising:
a plurality of optical sensors;
a tracker for mounting to the object, said tracker including three markers and a non-optical sensor, wherein said plurality of optical sensors are configured to receive optical signals sequentially from said markers and said non-optical sensor is configured to generate non-optical signals; and
a computing system including at least one processor configured to:
determine a position of a first of said markers at a first time based on a first optical signal from said first marker;
determine positions of a second and third of said markers at said first time based on said first optical signal and a non-optical signal from said non-optical sensor; and
correlate said determined positions of said first, second, and third markers to the object to track a position of the object.
2. A navigation system as set forth in claim 1 wherein said non-optical sensor is disposed in a known position relative to each of said markers.
3. A navigation system as set forth in claim 1 wherein said markers are passive reflectors.
4. A navigation system as set forth in claim 1 wherein said markers are active emitters configured to sequentially emit optical signals such that said first marker emits said first optical signal at said first time and prior to said second and third markers emitting optical signals.
5. A navigation system as set forth in claim 4 wherein said active emitters are light emitting diodes.
6. A navigation system as set forth in claim 1 wherein said plurality of optical sensors are housed in a camera unit.
7. A navigation system as set forth in claim 6 wherein said plurality of optical sensors are further defined as first, second, and third optical sensors.
8. A navigation system as set forth in claim 7 wherein said first, second, and third optical sensors are one-dimensional charge coupled devices.
9. A navigation system as set forth in claim 1 including a second tracker having three markers and a second non-optical sensor.
10. A navigation system as set forth in claim 9 wherein said first and second trackers are configured for mounting to bone.
11. A navigation system as set forth in claim 1 wherein said at least one processor is configured to calculate said positions of said second and third markers by calculating a first velocity of said first marker based on said first optical signal and by calculating velocities of said second and third markers based on said first velocity and said non-optical signal in said first time.
12. A navigation system as set forth in claim 1 wherein said at least one processor is configured to correlate said determined positions of said first, second, and third markers to the object to track a position and orientation of the object.
13. A navigation system as set forth in claim 12 including a probe adapted to select landmarks on a patient's anatomy, said probe having a plurality of markers for transmitting signals to said plurality of optical sensors during selection of the landmarks.
14. A navigation system as set forth in claim 1 wherein said at least one processor is configured to measure initial positions of said first, second, and third markers at an initial time to establish initial position data.
15. A navigation system as set forth in claim 14 wherein said at least one processor is configured to measure said initial positions of said first, second, and third markers to establish said initial position data by sequentially firing said first, second, and third markers to transmit light signals to said plurality of optical sensors.
16. A navigation system as set forth in claim 14 wherein said at least one processor is configured to calculate velocities of said first, second, and third markers while establishing said initial position data and is configured to compare said calculated velocities to a predetermined threshold.
17. A navigation system as set forth in claim 14 wherein said at least one processor is configured to compare said measured initial positions of said first, second, and third markers at said initial time to a model of said first, second, and third markers stored in said computing system.
18. A navigation system as set forth in claim 17 wherein said at least one processor is configured to match said first, second, and third markers to said model and provide a best-fit to said model.
19. A navigation system as set forth in claim 18 wherein said at least one processor is configured to match one or more virtual markers to said model to provide said best-fit to said model.
20. A navigation system as set forth in claim 17 wherein said at least one processor is configured to generate a transformation matrix from a tracker coordinate system to a localizer coordinate system.
21. A navigation system as set forth in claim 1 wherein said at least one processor is configured to calculate a linear velocity vector of said first marker.
22. A navigation system as set forth in claim 21 wherein said at least one processor is configured to measure an angular velocity of said tracker at said first time.
23. A navigation system as set forth in claim 22 wherein said at least one processor is configured to calculate a relative velocity vector of an origin of a tracker coordinate system based on said measured angular velocity.
24. A navigation system as set forth in claim 23 wherein said at least one processor is configured to calculate relative velocity vectors for said second and third markers based on said measured angular velocity.
25. A navigation system as set forth in claim 24 wherein said at least one processor is configured to calculate a velocity vector of an origin of said tracker coordinate system based on said calculated linear velocity vector of said first marker and said calculated relative velocity vector of said origin.
26. A navigation system as set forth in claim 25 wherein said at least one processor is configured to calculate velocity vectors of said second and third markers at said first time based on said calculated velocity vector of said origin and said calculated relative velocity vectors of said second and third markers.
27. A navigation system as set forth in claim 26 wherein said at least one processor is configured to calculate said positions of said second and third markers at said first time based on said calculated velocity vectors of said second and third markers at said first time.
28. A navigation system as set forth in claim 27 wherein said at least one processor is configured to calculate relative velocity vectors for one or more virtual markers.
29. A navigation system as set forth in claim 28 wherein said at least one processor is configured to calculate velocity vectors of said one or more virtual markers at said first time based on said calculated velocity vector of said origin and said calculated relative velocity vectors of said one or more virtual markers.
30. A navigation system as set forth in claim 29 wherein said at least one processor is configured to calculate a position of said one or more virtual markers at said first time based on said calculated velocity vectors of said one or more virtual markers at said first time.
31. A navigation system as set forth in claim 1 wherein said first time includes a first period of time.
Patent Citations (209)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US5086401(A) | 1992-02-01 | Glassman et al. | Applicant |
| US5279309(A) | 1994-01-01 | Taylor et al. | Applicant |
| US5408409(A) | 1995-04-01 | Glassman et al. | Applicant |
| US5494034(A) | 1996-02-01 | Schlondörff et al. | Applicant |
| US5497061(A) | 1996-03-01 | Nonaka et al. | Applicant |
| US5506682(A) | 1996-04-01 | Pryor | Applicant |
| US5569578(A) | 1996-10-01 | Mushabac | Applicant |
| US5577502(A) | 1996-11-01 | Darrow et al. | Applicant |
| US5592401(A) | 1997-01-01 | Kramer | Applicant |
| US5630431(A) | 1997-05-01 | Taylor | Applicant |
| US5638819(A) | 1997-06-01 | Manwaring et al. | Applicant |
| US5662111(A) | 1997-09-01 | Cosman | Applicant |
| US5676673(A) | 1997-10-01 | Ferre et al. | Applicant |
| US5682886(A) | 1997-11-01 | Delp et al. | Applicant |
| US5704897(A) | 1998-01-01 | Truppe | Applicant |
| US5729475(A) | 1998-03-01 | Romanik, Jr. | Applicant |
| US5730129(A) | 1998-03-01 | Darrow et al. | Applicant |
| US5765561(A) | 1998-06-01 | Chen et al. | Applicant |
| US5800352(A) | 1998-09-01 | Ferre et al. | Applicant |
| US5803089(A) | 1998-09-01 | Ferre et al. | Applicant |
| US5828770(A) | 1998-10-01 | Leis et al. | Applicant |
| US5829444(A) | 1998-11-01 | Ferre et al. | Applicant |
| US5848967(A) | 1998-12-01 | Cosman | Applicant |
| US5923417(A) | 1999-07-01 | Leis | Applicant |
| US5930741(A) | 1999-07-01 | Kramer | Applicant |
| US5953683(A) | 1999-09-01 | Hansen et al. | Applicant |
| US5967980(A) | 1999-10-01 | Ferre et al. | Applicant |
| US5976156(A) | 1999-11-01 | Taylor et al. | Applicant |
| US6006126(A) | 1999-12-01 | Cosman | Applicant |
| US6026315(A) | 2000-02-01 | Lenz et al. | Applicant |
| US6061644(A) | 2000-05-01 | Leis | Applicant |
| US6106464(A) | 2000-08-01 | Bass et al. | Applicant |
| US6115128(A) | 2000-09-01 | Vann | Applicant |
| US6122538(A) | 2000-09-01 | Sliwa, Jr. et al. | Applicant |
| US6161033(A) | 2000-12-01 | Kuhn | Applicant |
| US6167295(A) | 2000-12-01 | Cosman | Applicant |
| US6175756(B1) | 2001-01-01 | Ferre et al. | Applicant |
| US6226548(B1) | 2001-05-01 | Foley et al. | Applicant |
| US6228089(B1) | 2001-05-01 | Wahrburg | Applicant |
| US6234983(B1) | 2001-05-01 | Storey et al. | Applicant |
| US6235038(B1) | 2001-05-01 | Hunter et al. | Applicant |
| US6236875(B1) | 2001-05-01 | Bucholz et al. | Applicant |
| US6246898(B1) | 2001-06-01 | Vesely et al. | Applicant |
| US6266142(B1) | 2001-07-01 | Junkins et al. | Applicant |
| US6273896(B1) | 2001-08-01 | Franck et al. | Applicant |
| US6275725(B1) | 2001-08-01 | Cosman | Applicant |
| US6285902(B1) | 2001-09-01 | Kienzle, III et al. | Applicant |
| US6288785(B1) | 2001-09-01 | Frantz et al. | Applicant |
| US6314312(B1) | 2001-11-01 | Wessels et al. | Applicant |
| US6322567(B1) | 2001-11-01 | Mittelstadt et al. | Applicant |
| US6341231(B1) | 2002-01-01 | Ferre et al. | Applicant |
| US6351659(B1) | 2002-02-01 | Vilsmeier | Applicant |
| US6351661(B1) | 2002-02-01 | Cosman | Applicant |
| US6400460(B1) | 2002-06-01 | Chen | Applicant |
| US6409687(B1) | 2002-06-01 | Foxlin | Applicant |
| US6442416(B1) | 2002-08-01 | Schultz | Applicant |
| US6442417(B1) | 2002-08-01 | Shahidi et al. | Applicant |
| US6445943(B1) | 2002-09-01 | Ferre et al. | Applicant |
| US6450978(B1) | 2002-09-01 | Brosseau et al. | Applicant |
| US6456868(B2) | 2002-09-01 | Saito et al. | Applicant |
| US6466815(B1) | 2002-10-01 | Saito et al. | Applicant |
| US6473635(B1) | 2002-10-01 | Rasche | Applicant |
| US6490467(B1) | 2002-12-01 | Bucholz et al. | Applicant |
| US6491702(B2) | 2002-12-01 | Heilbrun et al. | Applicant |
| US6527443(B1) | 2003-03-01 | Vilsmeier et al. | Applicant |
| US6581000(B2) | 2003-06-01 | Hills et al. | Applicant |
| US6584339(B2) | 2003-06-01 | Galloway, Jr. et al. | Applicant |
| US6584378(B1) | 2003-06-01 | Anfindsen | Applicant |
| US6585651(B2) | 2003-07-01 | Nolte et al. | Applicant |
| US6611141(B1) | 2003-08-01 | Schulz et al. | Applicant |
| US6665079(B1) | 2003-12-01 | Tocci et al. | Applicant |
| US6675032(B2) | 2004-01-01 | Chen et al. | Applicant |
| US6675040(B1) | 2004-01-01 | Cosman | Applicant |
| US6675122(B1) | 2004-01-01 | Markendorf et al. | Applicant |
| US6691074(B1) | 2004-02-01 | Moriya et al. | Applicant |
| US6694167(B1) | 2004-02-01 | Ferre et al. | Applicant |
| US6711431(B2) | 2004-03-01 | Sarin et al. | Applicant |
| US6757582(B2) | 2004-06-01 | Brisson et al. | Applicant |
| US6848304(B2) | 2005-02-01 | Geen | Applicant |
| US6876926(B2) | 2005-04-01 | Kirkland et al. | Applicant |
| US6926709(B2) | 2005-08-01 | Bieger et al. | Applicant |
| US6963409(B2) | 2005-11-01 | Benner et al. | Applicant |
| US7072704(B2) | 2006-07-01 | Bucholz | Applicant |
| US7104996(B2) | 2006-09-01 | Bonutti | Applicant |
| US7139601(B2) | 2006-11-01 | Bucholz et al. | Applicant |
| US7166114(B2) | 2007-01-01 | Moctezuma de la Barrera et al. | Applicant |
| US7206627(B2) | 2007-04-01 | Abovitz et al. | Applicant |
| US7209028(B2) | 2007-04-01 | Boronkay et al. | Applicant |
| US7217276(B2) | 2007-05-01 | Henderson et al. | Applicant |
| US7283892(B1) | 2007-10-01 | Boillot et al. | Applicant |
| US7289227(B2) | 2007-10-01 | Smetak et al. | Applicant |
| US7295891(B2) | 2007-11-01 | Hüttenhofer et al. | Applicant |
| US7395181(B2) | 2008-07-01 | Foxlin | Applicant |
| US7421343(B2) | 2008-09-01 | Hawkinson | Applicant |
| US7535411(B2) | 2009-05-01 | Falco | Applicant |
| US7542791(B2) | 2009-06-01 | Mire et al. | Applicant |
| US7556428(B2) | 2009-07-01 | Sukovic et al. | Applicant |
| US7640106(B1) | 2009-12-01 | Stokar et al. | Applicant |
| US7689321(B2) | 2010-03-01 | Karlsson | Applicant |
| US7702379(B2) | 2010-04-01 | Avinash et al. | Applicant |
| US7725162(B2) | 2010-05-01 | Malackowski et al. | Applicant |
| US7725279(B2) | 2010-05-01 | Luinge et al. | Applicant |
| US7728868(B2) | 2010-06-01 | Razzaque et al. | Applicant |
| US7747312(B2) | 2010-06-01 | Barrick et al. | Applicant |
| US7862570(B2) | 2011-01-01 | Russell et al. | Applicant |
| US7868610(B2) | 2011-01-01 | Velinsky et al. | Applicant |
| US7895761(B2) | 2011-03-01 | Pettersson | Applicant |
| US8010180(B2) | 2011-08-01 | Quaid et al. | Applicant |
| US8028580(B2) | 2011-10-01 | Millet | Applicant |
| US8047075(B2) | 2011-11-01 | Nasiri et al. | Applicant |
| US8057407(B2) | 2011-11-01 | Martinelli et al. | Applicant |
| US8057479(B2) | 2011-11-01 | Stone | Applicant |
| US8057482(B2) | 2011-11-01 | Stone et al. | Applicant |
| US8072614(B2) | 2011-12-01 | Deliwala | Applicant |
| US8082064(B2) | 2011-12-01 | Kay | Applicant |
| US8096163(B2) | 2012-01-01 | Goldbach | Applicant |
| US8100769(B2) | 2012-01-01 | Rabin | Applicant |
| US8103472(B2) | 2012-01-01 | Braun et al. | Applicant |
| US8109890(B2) | 2012-02-01 | Kamiar et al. | Applicant |
| US8111407(B2) | 2012-02-01 | Takimasa et al. | Applicant |
| US8112292(B2) | 2012-02-01 | Simon | Applicant |
| US8126535(B2) | 2012-02-01 | Maier et al. | Applicant |
| US8131344(B2) | 2012-03-01 | Strommer et al. | Applicant |
| US8141424(B2) | 2012-03-01 | Seeger et al. | Applicant |
| US8165844(B2) | 2012-04-01 | Luinge et al. | Applicant |
| US2001/0011175(A1) | 2001-08-01 | Hunter et al. | Applicant |
| US2001/0037064(A1) | 2001-11-01 | Shahidi | Applicant |
| US2002/0052546(A1) | 2002-05-01 | Frantz et al. | Applicant |
| US2002/0120192(A1) | 2002-08-01 | Nolte et al. | Applicant |
| US2002/0198448(A1) | 2002-12-01 | Zuk et al. | Applicant |
| US2003/0031349(A1) | 2003-02-01 | Giorgi et al. | Applicant |
| US2003/0163142(A1) | 2003-08-01 | Paltieli et al. | Applicant |
| US2004/0024309(A1) | 2004-02-01 | Ferre et al. | Applicant |
| US2004/0027587(A1) | 2004-02-01 | Morimoto | Applicant |
| US2004/0068178(A1) | 2004-04-01 | Govari | Applicant |
| US2004/0138556(A1) | 2004-07-01 | Cosman | Applicant |
| US2004/0149036(A1) | 2004-08-01 | Foxlin et al. | Applicant |
| US2004/0150560(A1) | 2004-08-01 | Feng et al. | Applicant |
| US2004/0167688(A1) | 2004-08-01 | Karlsson et al. | Applicant |
| US2004/0172164(A1) | 2004-09-01 | Habibi et al. | Applicant |
| US2004/0204646(A1) | 2004-10-01 | Nagler et al. | Applicant |
| US2004/0243148(A1) | 2004-12-01 | Wasielewski | Applicant |
| US2005/0049485(A1) | 2005-03-01 | Harmon et al. | Applicant |
| US2005/0085717(A1) | 2005-04-01 | Shahidi | Applicant |
| US2005/0085718(A1) | 2005-04-01 | Shahidi | Applicant |
| US2005/0154295(A1) | 2005-07-01 | Quistgaard et al. | Applicant |
| US2005/0245820(A1) | 2005-11-01 | Sarin | Applicant |
| US2005/0267353(A1) | 2005-12-01 | Marquart et al. | Applicant |
| US2006/0178775(A1) | 2006-08-01 | Zhang et al. | Applicant |
| US2006/0190012(A1) | 2006-08-01 | Freitag | Applicant |
| US2006/0258938(A1) | 2006-11-01 | Hoffman et al. | Applicant |
| US2006/0282873(A1) | 2006-12-01 | Zalewski et al. | Applicant |
| US2007/0225731(A1) | 2007-09-01 | Couture et al. | Applicant |
| US2007/0270686(A1) | 2007-11-01 | Ritter et al. | Applicant |
| US2007/0270690(A1) | 2007-11-01 | Woerlein | Applicant |
| US2007/0287911(A1) | 2007-12-01 | Haid et al. | Applicant |
| US2008/0018912(A1) | 2008-01-01 | Schreiber | Applicant |
| US2008/0039868(A1) | 2008-02-01 | Tuemmler et al. | Applicant |
| US2008/0119726(A1) | 2008-05-01 | Immerz et al. | Applicant |
| US2008/0154125(A1) | 2008-06-01 | Maier et al. | Applicant |
| US2008/0161682(A1) | 2008-07-01 | Kendrick et al. | Applicant |
| US2008/0192263(A1) | 2008-08-01 | Wienand et al. | Applicant |
| US2009/0030608(A1) | 2009-01-01 | Soehren et al. | Applicant |
| US2009/0048779(A1) | 2009-02-01 | Zeng et al. | Applicant |
| US2009/0088629(A1) | 2009-04-01 | Groszmann et al. | Applicant |
| US2009/0143670(A1) | 2009-06-01 | Daigneault | Applicant |
| US2009/0149740(A1) | 2009-06-01 | Hoheisel | Applicant |
| US2009/0248044(A1) | 2009-10-01 | Amiot et al. | Applicant |
| US2009/0281417(A1) | 2009-11-01 | Hartmann et al. | Applicant |
| US2009/0312629(A1) | 2009-12-01 | Razzaque et al. | Applicant |
| US2009/0318836(A1) | 2009-12-01 | Stone et al. | Applicant |
| US2010/0030063(A1) | 2010-02-01 | Lee et al. | Applicant |
| US2010/0130853(A1) | 2010-05-01 | Chandonnet et al. | Applicant |
| US2010/0154540(A1) | 2010-06-01 | Uemura | Applicant |
| US2010/0160771(A1) | 2010-06-01 | Gielen et al. | Applicant |
| US2010/0234770(A1) | 2010-09-01 | Colombet et al. | Applicant |
| US2010/0261999(A1) | 2010-10-01 | Soubelet et al. | Applicant |
| US2010/0318223(A1) | 2010-12-01 | Motoyoshi et al. | Applicant |
| US2011/0045736(A1) | 2011-02-01 | Wooten | Applicant |
| US2011/0054304(A1) | 2011-03-01 | Markowitz et al. | Applicant |
| US2011/0087092(A1) | 2011-04-01 | Kienzle, III | Applicant |
| US2011/0105895(A1) | 2011-05-01 | Kornblau et al. | Applicant |
| US2011/0178394(A1) | 2011-07-01 | Fitzpatrick | Applicant |
| US2011/0190790(A1) | 2011-08-01 | Summerer et al. | Applicant |
| US2011/0218458(A1) | 2011-09-01 | Valin et al. | Applicant |
| US2011/0257909(A1) | 2011-10-01 | Allen et al. | Applicant |
| US2011/0275957(A1) | 2011-11-01 | Bhandari | Applicant |
| US2011/0320153(A1) | 2011-12-01 | Lightcap et al. | Applicant |
| US2012/0029389(A1) | 2012-02-01 | Amiot et al. | Applicant |
| US2012/0089014(A1) | 2012-04-01 | Sabczynski et al. | Applicant |
| US2012/0095330(A1) | 2012-04-01 | Shechter et al. | Applicant |
| US2012/0108954(A1) | 2012-05-01 | Schulhauser et al. | Applicant |
| US2012/0108955(A1) | 2012-05-01 | Razzaque et al. | Applicant |
| US2013/0064427(A1) | 2013-03-01 | Picard et al. | Applicant |
| DE102004047905(A1) | 2006-04-01 | Applicant | |
| DE102004061764(A1) | 2006-07-01 | Applicant | |
| WO9611624(A2) | 1996-04-01 | Applicant | |
| WO200131(A1) | 2002-03-01 | Applicant | |
| WO2010086374(A1) | 2010-05-01 | Applicant | |
| WO2010077008(A2) | 2010-08-01 | Applicant | |
| WO2010150148(A1) | 2010-12-01 | Applicant | |
| WO2011025708(A2) | 2011-03-01 | Applicant | |
| WO2011026077(A2) | 2011-03-01 | Applicant | |
| WO2011059383(A1) | 2011-05-01 | Applicant | |
| WO2011089606(A1) | 2011-07-01 | Applicant | |
| WO2011106861(A1) | 2011-09-01 | Applicant | |
| WO2011128766(A2) | 2011-10-01 | Applicant | |
| WO2011128766(A3) | 2011-10-01 | Applicant | |
| WO2012052070(A1) | 2012-04-01 | Applicant |
Non-Patent Literature (69)
- International Search Report of the International Searching Authority for Application No. PCT/US2013/061642 dated Jan. 20, 2014; 7 pages.Applicant
- Written Opinion of the International Searching Authority for Application No. PCT/US2013/061642 dated Jan. 20, 2014; 7 pages.Applicant
- A Literature Review: Robots in Medicine, Hsia, T.C.; Mittelstadt, B., Jun. 1991, vol. 10, Issue 2, pp. 13-22, 10 pages.Applicant
- A Novel Approach to Computer Assisted Spine Surgery, Lutz P. Nolte, Lucia J. Zamorano, Zhaowel Jlang, Qinghai Wang, Frank Langlotz, Erich Arm, Heiko Visarius, Proceedings of the First International Symposium on Medical Robotics and Computer Assisted Surgery, vol. 2, Workshop [Part I & II] Session VI, Sep. 1994, pp. 323-328, 7 pages.Applicant
- A review of robotics in surgery, B. Davies, Proceedings of the Institution of Mechanical Engineers, Part H: Journal of Engineering in Medicine, 2000, pp. 129-140, 13 pages.Applicant
- A Robotized Surgeon Assistant, T. Wang, M. Fadda, M. Marcacci, S. Martelli, P. Dario and A. Visani, Intelligent Robots and Systems '94. ‘Advanced Robotic Systems and the Real World’, IROS '94. Proceedings of the IEEE/RSJ/GI International Conference on (vol. 2) pp. 852-868, 1994, 8 pages.Applicant
- A Safe Robot System for Craniofacial Surgery, D. Engel, J. Raczkowsky, H. Worn, May 21-26, 2001, Proceedings of the 2001 IEEE, International Conference on Robotics and Automation, pp. 2020-2024, 5 pages.Applicant
- A Steady-Hand Robotic System for Microsurgical Augmentation, Russell Taylor, Pat Jensen, Louis Whitcomb, Aaron Barnes, Rajest Kumar, Dan Stoianovici, Puneet Gupta, Zhengxian Wange, Eugen Dejuan and Louis Kavoussi, The International Journal of Robotics Research, 1999, vol. 18, pp. 1201-1210, 11 pages.Applicant
- A Stereotactic/Robotic System for Pedicle Screw Placement, Julio J. Santos-Munné, Michael A. Peshkin, Srdjan Mirkovic, S. David Stulberg, Thomas C. Kienzle III, 1995, Interactive Technology and the New Paradigm for Hardware, pp. 326-333, 8 pages.Applicant
- A Surgical Robot for Total Hip Replacement Surgery, Proceedings of the 1992 IEEE, International Conference on Robotics and Automation, May, 1992, pp. 606-611, 6 pages.Applicant
- Accuracy Study on the Registration of the Tibia by Means of an Intramedullary Rod in Robot-Assisted Total Knee Arthroplasty, G. Van Ham, J. Bellemans, K. Denis, L. Labey, J. Vander Sloten, R. Van Audekercke, G. Van Der Perre, J. De Schutter, 46th Annual Meeting, Orthopaedic Research Society, Mar. 2000, pp. 450, 1 page.Applicant
- Accuracy Validation in Image-Guided Orthopaedic Surgery, David Simon, R.V. O'Toole, Mike Blackwell, F. Morgan, Anthony M. Digioia, and Takeo Kanade, Proceedings of the Second International Symposium on Medical Robotics and Computer Assisted Surgery, 1995, pp. 185-192, 8 pages.Applicant
- Acrobot—Using Robots and Surgeons Synergistically in Knee Surgery, BL Davies, KL Fan, RD Hibberd, M. Jakopec and SJ Harris, Mechatronics in Medicine, Jul. 1997, pp. 173-178, 6 pages.Applicant
- Active compliance in robotic surgery—the use of force control as a dynamic constraint, B.L. Davies, S. J. Harris, W. J. Lin, R. D. Hibberd, R. Middleton and J.C. Cobb, Proceedings of the Institution of Mechanical Engineers, Part H: Journal of Engineering in Medicine, 1997 vol. 211, pp. 285-292; 9 pages.Applicant
- An Image-directed Robotic System for Hip Replacement Surgery, Russell H. Taylor, Howard A. Paul, Brent D. Mittelstadt, William Hanson, Peter Kazanzides, Joel Zuhars, Edward Glassman, Bela L. Musits, Bill Williamson, William L. Bargar, Oct. 1990, pp. 111-118, 7 pages.Applicant
- An Integrated CAD-Robotics System for Total Knee Replacement Surgery, Kienzle, T.C., III, 1993, IEEE, pp. 889-894, 6 pages.Applicant
- Architecture of a Surgical Robot, P. Kazanzides, J. Zuhars, B. Mittelstadt, B. Williams, P. Cain, F. Smith, L. Rose, B. Musits, 1992 IEEE, pp. 1624-1629, 6 pages.Applicant
- Clinical Introduction of the Caspar System Problems and Initial Results, C.O.R. Grueneis, R.H. Richter, F.F. Hennig, Abstracts from CAOS, 1999, pp. 160, 1 page.Applicant
- Comparative Tracking Error Analysis of Five Different Optical Tracking Systems, R Khadem, C C Yeh, M Sadeghi-Tehrani, M R Bax, J A Johnson, J N Welch, E P Wilkinson, R Shahidi, Computer Aided Surgery vol. 5, 2000, pp. 98-107.Applicant
- Comparison of Relative Accuracy Between a Mechanical and an Optical Position Tracker for Image-Guided Neurosurgery, Rohling R, Munger P, Hollerbach JM, Peter T., J Image Guid Surg., 1995;1(1), pp. 30-34, 4 pages.Applicant
- Computer Assisted Knee Replacement, Scott L. Delp, Ph.D., S. David Stulberg, MD, Brian Davies, Ph.D. Frederic Picard, MD and Francois Leitner, Ph.D., Clinical Orthopaedics, Sep. 1998, vol. 354, pp. 49-56; 8 pages.Applicant
- Computer Assisted Orthopaedic Surgery Image Guided and Robotic Assistive Technologies, Anthony M. Digioia, Branislav Jaramaz, and B. Colgan, Clinical Orthopaedics and Related Research, No. 354, Sep. 1998, pp. 8-16, 9 pages.Applicant
- Computer Assisted Planning for Total Knee Arthroplasty, CVRMed-MRCAS'97, M. Fadda, D. Bertelli, S. Martelli, M. Marcacci, P. Dario, C. Paggetti, D. Caramella, D. Trippi, 1997, pp. 619-628, 10 pages.Applicant
- Computer Assisted Spine Surgery: a technique for accurate transpedicular screw fixation, S Lavallée, Proceedings of the First International Symposium on Medical Robotics and Computer Assisted Surgery, vol. 2, Workshop [Part I & II] Session VI, Sep. 1994, pp. 315-322, 9 pages.Applicant
- Computer-assisted and robotics surgery, Brian Davies, International Congress and Symposium Series 223, 1997, pp. 71-82; 12 pages.Applicant
- Computer-Assisted Knee Arthroplasty at Rizzoli Institutes, M. Fadda, Proceedings of the First International Symposium on Medical Robotics and Computer Assisted Surgery, Sep. 1994, pp. 26-30, 6 pages.Applicant
- Concepts and methods of registration for computer-integrated surgery, E. Bainville, I. Bricault, P. Cinquin, and S. Lavallée, Computer Assisted Orthopedic Surgery (“CAOS”), L.-P. Nolte and R. Ganz, Eds., pp. 15-34, Hogrefe & Huber, Seattle, Wash, USA, 1999; 22 pages.Applicant
- Crigos A Compact Robot for Image-Guided Orthopedic Surgery, Guido Brandt, Andreas Zimolong, Lional Carrat, Philippe Merloz, Hans-Walter Staudte, Stephane Lavallee, Klaus Rademacher and Gunter Rau, Dec. 1999, IEEE Transactions on Information Technology in Biomedicine, vol. 3, No. 4, pp. 252-260, 9 pages.Applicant
- Design Optically Tracked Instruments for Image Guided Surgery, Jay B. West and Calvin R. Maurer, Jr., Member, IEEE Transactions on Medical Imaging, vol. 23, No. 5, May 2004, 13 pages.Applicant
- Digital surgery the future of medicine and human-robot symbiotic interaction, Rony A. Abovitz, Industrial Robot: An International Journal, vol. 28, No. 5, 2001, pp. 401-405, 5 pages.Applicant
- EasyGuide Neuro, ein neues System zur bildgefuhrten Planung, Simulation und Navigation in der Neurochirurgie, TH. Schmidt und W. Hentschel, 1995, Biomedizinische Technik, Band 40, Erganzungsband 1, pp. 233-234; 2 pages.Applicant
- Ein Robotersystem für craniomaxillofaciale chirurgische Eingriffe, J. Raczkowsky, J. Münchenberg, I. Bertovic, C. Burghart, Informatik Forsch. Entw., 1999, pp. 24-35, 12 pages.Applicant
- Experiences with Robotic Systems for Knee Surgery, S. J. Harris, W. J. Lin, K. L. Fan, R. D. Hibberd, J. Cobb, R. Middleton, B. L. Davies, CVRMed-MRCAS'97, Lecture Notes in Computer Science vol. 1205, 1997, pp. 757-766; 10 pages.Applicant
- Force Control for Robotic Surgery, S.C. Ho, R.D. Hibberd, J. Cobb and B.L. Davies, ICAR, 1995, pp. 21-32, 12 pages.Applicant
- Frameless Neuronavigation in Modern Neurosurgery, Spetzger U, Laborde G, Gilsbach JM, Minim. Invas, Neurosurg., 1995, vol. 38, pp. 163-166, 4 pages.Applicant
- Haptic information displays for computer-assisted surgery, A.E. Quaid and Rony A. Abovitz, Robotics and Automation, 2002 Proceedings ICRA '02. IEEE International Conference on Robotics and Automation, 2092, vol. 2, pp. 2092-2097, 6 pages.Applicant
- High-Bandwidth Low-Latency Tracking Using Optical and Inertial Sensors, Gontje C. Claasen and Philippe Martin, Centre Automatique et Systemes, and Frederic Picard, Department of Ofthopaedics, Golden Jubilee National Hospital, Proceedings of the 5th International Conference on Automation, Robotics and Applications, Dec. 6-8, 2011, Wellington, New Zealand, 6 pages.Applicant
- Human-Interactive Medical Robotics, Rony A. Abovitz, M.S., Computer Assisted Orthopedic Surgery (“CAOS”), 2000, pp. 71-72, 2 pages.Applicant
- Image-Guided Manipulator Compliant Surgical Planning Methodology for Robotic Skull-Base Surgery, Wan Sing NG; Ming Yeong Teo; Yong-Chong Loh; Tseng Tsai Yeo, Medical Imaging and Augmented Reality, 2001 IEEE, pp. 26-29, 4 pages.Applicant
- Inertial and Magnetic Sensing of Human Motion, Daniel Roetenberg, May 24, 2006, 128 pages.Applicant
- Intra-operative Application of a Robotic Knee Surgery System, S. J. Harris, M. Jakopec, J. Cobb, B. L. Davies, Medical Image Computing and Computer-Assisted Intervention—MICCAI'99, Lecture Notes in Computer Science vol. 1679, 1999, pp. 1116-1124; 9 pages.Applicant
- Intraoperative Navigation Techniques Accuracy Tests and Clinical Report, S. Hassfeld, C. Burghart, I. Bertovic, J. Raczkowsky, U. Rembod, H. Worn and J. Muling, 1998, pp. 670-675, 6 pages.Applicant
- Machining and Accuracy Studies for a Tibial Knee Implant Using a Force-Controlled Robot, Computer Aided Surgery, 1998, pp. 123-133, 11 pages.Applicant
- Minimally Invasive Total Knee Arthroplasty Surgery Through Navigated Freehand Bone Cutting, Hani Haider, PhD, O. Andres Barrera, MSC, and Kevin L. Garvin, MD, The Journal of Arthroplasty, vol. 22, No. 4, 2007, 8 pages.Applicant
- Precision Freehand Sculpting of Bone, Gabriel Brisson, Takeo Kanade, Anthony Digioia, Branislav Jaramaz, MICCAI 2004, LNCS 3217, pp. 105-112, 2004, 8 pages.Applicant
- PrecisioN Knee Navigation Operative Technique, Stryker Software Manual, Knute Buehler, M.D., Chief of Arthritis and Joint Reconstruction the Center—Orthopedic and Neurosurgery Care and Research Bend, Oregon 40 pages.Applicant
- Premiers Pas Vers La Dissectomie et la Realisation de Protheses du Genou a L'Aide de Robots, M. Fadda, S. Martelli, P. Dario, M. Marcacci, S. Zaffagnini, A. Visani, Innov. Tech. Biol. Med., vol. 13, No. 4, 1992, pp. 394-409, 16 pages.Applicant
- Primary and Revision Total Hip Replacement Using the Robodoc System, William L. Bargar, MD, Andre Bauer, MD and Martin Börner, MD, Clinical Orthopaedics and Related Research, 1998, No. 354, pp. 82-91, 10 pages.Applicant
- Registration and immobilization in robot-assisted surgery, Jon T. Lea, Dane Watkins, Aaron Mills, Michael A. Peshkin, Thomas C. Kienzle III and S. David Stulberg, Journal of Image Guided Surgery, 1995, vol. 1, No. 2, pp. 80-87, 11 pages.Applicant
- Registration Graphs a Language for Modeling and Analyzing Registration in Image-Guided Surgery, Jon Thomas Lea, Dec. 1998, 1-49, 49 pages.Applicant
- Robot assisted craniofacial surgery: first clinical evaluation, C. Burghart, R. Krempien, T. Redlich, A. Pernozzoli, H. Grabowski, J. Muenchenberg, J. Albers, S. Haβfeld, C. Vahl, U. Rembold and H. Woern, 1999, 7 pages.Applicant
- Robot Assisted Knee Surgery, 4527 IEEE, Engineering in Medicine & Biology 14, May/Jun. 1995, No. 3, pp. 292-300, 9 pages.Applicant
- Robot Controlled Osteotomy in Craniofacial Surgery, Catherina Burghart, Jochen Keitel, Stefan Hassfeld, Ulrich Rembold and Heinz Woern, Haptic Devices in Medical Applications, Jun. 23, 1999; pp. 12-22, 13 pages.Applicant
- Robotergestützte Osteotomie in der craniofacialen Chirurgie, Catherina R. Burghart, GCA-Verlag, 2000, and partial English translation, 250 pages.Applicant
- Robotic Assistance in Orthopaedic Surgery a Proof of Principle Using Distal Femoral Arthroplasty, Clinical Orthopaedics and Related Research, 1993, No. 296, pp. 178-186, 9 pages.Applicant
- Robotic Execution of a Surgical Plan, Howard A. Paul, DVM, William L. Bargar, MD, Brent Mittlestadt, Peter Kazanzides, Ph.D., Bela Musites, Joel Suhars, Phillip W. Cain, Bill Williamson, Fred G. Smith, 1992 IEEE, 99. 1621-1623, 3 pages.Applicant
- Robotics in Minimally Invasive Surgery, Brian Davies, Mechatronics in Medicine Lab, IEE, 1996 The Institution of Electrical Engineers, pp. 1-2, 2 pages.Applicant
- Robotics in surgery a new generation of surgical tools incorporate computer technology and mechanical actuation to give surgeons much finer control than previously possible during some operations, Rob Buckingham, IEE Review, Sep. 1994, pp. 193-196, 4 pages.Applicant
- Robust Multi Sensor Pose Estimation for Medical Applications, Andreas Tobergte, Mihai Pomarlan and Gerd Hirzinger, 8 pages.Applicant
- Safe Active Robotic Devices for Surgery, RO Buckingham, Oct. 1993, vol. 5, pp. 355-358, 4 pages.Applicant
- Section 4 Robotic Systems and Task-Level Programming, a Model-Based Optimal Planning and Execution System with Active Sensing and Passive Manipulation for Augmentation of Human Precision in Computer-Integrated Surgery, Russell H. Taylor, Yong-Yil Kim, Alan D. Kalvin, David Larose, Betsy Haddad, Deljou Khoramabadi, Marilyn Noz, Robert Olyha, Nils Brunn and Dieter Grimm, Experimental Robotics II Lecture Notes in Control and Information Sciences, vol. 190, 1993, pp. 177-195, 19 pages.Applicant
- Semi-Active Guiding Systems in Surgery. A Two-DOF Prototype of the Passive Arm with Dynamic Constraints (PADyC), Jocelyne Troccaz, Yves Delnondedieu, Mechatronics vol. 6, No. 4, pp. 399-421, 1996, 23 pages.Applicant
- Surgical Robotics An Introduction, Ulrich Rembold and Catherina R. Burghart, Journal of Intelligent and Robotic Systems, vol. 30, Institute of Process Control and Robotics, 2001, pp. 1-28, 28 pages.Applicant
- Technique and first clinical results of robot-assisted total knee replacement, Werner Siebert, Sabine Mai, Rudolf Kober and Peter F. Heeckt, The Knee, vol. 9, 2002, pp. 173-130, 8 pages.Applicant
- The ROBODOC Clinical Trial a Robotic Assistant for Total Hip Arthroplasty, Evelyn Harkins Spencer, Orthopaedic Nursing, Jan./Feb. 1996, vol. 15, No. 1, pp. 9-14, 6 pages.Applicant
- Three-Dimensional Digitizer (Neuronavigator); New Equipment for Computed Tomography-Guided Stereotaxic Surgery, Watanabe E, Watanabe T, Manaka S, Mayanagi Y, Takakura K., Surg Neurol., Jun. 1987, Issue 6, pp. 543-547, 5 pages.Applicant
- Three-Dimensional Ultrasound Imaging Using Multiple Magnetic Tracking Systems and Miniature Sensors, Daniel F. Leotta, Paul R. Detmer, ODD Helge Gilja, Jing-Ming Jong, Roy W. Martin, Jean F. Primozich, Kirk W. Beach and D. Eugene Strandness, Bioengineering, Surgery, Anesthesiology, University of Washington, Seattle, WA, 1995 IEEE Ultrasonics Symposium, 4 pages.Applicant
- Total Knee Replacement Computer-assisted surgical system uses a calibrated robot, May/Jun. 1995, IEEE Engineering in Medicine and Biology; A Computer-Assisted Total Knee Replacement Surgical System Using a Calibrated Robot, Thomas C. Kienzle III, S. David Stulberg, Michael Peshkin, Arthur Quaid, Jon Lea, Ambarish Goswami, Chi-hau Engineering in Medicine and Biology vol. 14, Issue 3, May 1995, pp. 301-306, 35 pages.Applicant
- G.C. Claasen, P. Martin, F. Picard, Tracking and Control for Handheld Surgery Tools, Biomedical Circuits and Systems Conference (BioCAS), 2011 IEEE, pp. 428-431, IEEE, San Diego, CA, USA; 4 pages.Applicant