Patent Grant
11529195
This invention relates generally to robotic surgical systems. For example, in certain embodiments, the invention relates to robotic surgical systems with built-in navigation capability for position tracking during a surgical procedure.
Many surgeries (e.g., spinal and orthopedic surgeries) currently require the use of medical images displayed to the surgeon in real time, to provide visual navigation to support surgical action, gestures, and decision making. Using medical images, a surgeon can be provided with real-time feedback of the position of surgical instruments in reference to patient anatomy (as pictured by medical images).
Current surgical navigation systems are based on the principle of tracking. For example, a navigation system generally contains a tracking device which measures position of the surgical instruments and patient in real time. Different tracking devices operate on different principles. The most popular are optical tracking and electro-magnetic tracking. Optical tracking uses camera systems that measure fiducials (e.g., reflective spheres, LEDs) configured on markers having defined and known anatomy. In this way, the position and orientation of a marker can be determined and, thus, the position and orientation of the element to which they are affixed (e.g., surgical instruments, patient anatomy) can be tracked as well. In electro-magnetic tracking, the camera of an optical tracking system is replaced by a field generator. Markers are sensor units (e.g., coils) which measure spatial changes in the generated field. In this way, the position and orientation of the EM marker can be determined in reference to field generator.
There are commercial navigation systems available on the market, for example, Stealthstation S7 from Medtronic, Curve from Brain lab, electro-magnetic Kick EM from Brainlab and others. A typical workflow for use of these navigation systems follows the steps of: obtaining patient images, fixing a reference on the patient, registering the patient, and tracking instrument and patients to show real-time feedback to the surgeon. Patient images may be generated by CT, MRI, or flat-panel fluoroscopy (e.g., 0-Arm), for example. References fixed to the patient include optical markers with a fiducial mark or electro-magnetic markers. Markers are fixed using, for example, bone screws or bone fixations. Registering the patient requires defining a relationship between the patient images and the fixed marker. Registration may be performed using a point-to-point method, surface matching, or automatic registration based on images taken with fixed markers (e.g., on the patient's anatomy).
Current navigation systems have numerous limitations. These navigation systems are generally difficult to use and require additional surgeon and/or staff training for their operation. The navigation systems take up a lot of space in the operating room. For example, precious real estate in the operating room space may be occupied by a stand-alone navigation station/console with tracking camera, screens used for visual feedback, cords and plugs, power systems, controllers, and the like, creating additional clutter. Also, current optical navigation systems have a line of sight requirement, in that all tracked instruments must remain visible to the camera in order to be tracked. If there are not enough fiducials (e.g., spheres, LEDs) visible marker positions may not be able to be determined. An additional risk is that fiducial position can be misread by the navigation system due to obfuscation (e.g., by a drop of blood or transparent drape). Electro-magnetic navigation systems have problems with metal and ferromagnetic materials placed in field which can influence the field and thus add error to marker position measurement. Moreover, navigation systems are expensive, costing approximately $200k or more. The precision of the measurement is relatively low in commercial stations, for example, on the level of O.3 mm RMS error for position measurement. Additionally, the measurements are noisy. The frequency of measurement is low (i.e., approximately 20 Hz).
The most severe limitation of known navigation systems is that the navigation desynchronizes over time. The surgeon registers the patient initially at the beginning of the surgical procedure, using one or more markers attached to the patient's anatomy. Throughout the surgical procedure, the patient's anatomy shifts due to movement of the patient or as a result of the surgical procedure itself. For example, in surgeries involving elongation steps or realignment steps, the patient's anatomy will have a different position and orientation relative to the fiducial marker(s) after the elongation or realignment. Only the area local to the fiducial marker(s) remains accurate to the physical reality of the patient's anatomy. The error between the reality of the patient's anatomy and the assumed reality based on the initial registration increases with distance from the fiducial marker(s). Thus, in many surgical procedures being performed today using robotic surgical systems with known navigation systems, as the procedure progresses, the navigation system becomes more desynchronized and thus less useful to the surgeon, as it is less reflective of real life. Likewise, the likelihood of complications and serious medical error increases.
There are robotic surgical systems which are combined with a navigation system, for example, Excelsius GPS from Globus, ROSA SPINE from Medtech (currently Zimmer/Biomet), MAKO from Stryker and others. However, these systems use the same navigation system approach as the aforementioned known systems. The use of a robotic arm aids a surgeon in making precise gestures, but the systems inherit the disadvantages of navigation systems especially: training requirements, required space, line of sight, price and low precision of optical navigation over the course of a surgical procedure. The likelihood of complications and serious medical errors due to desynchronization are not reduced in these robotic surgical systems.
Thus, there is a need for robotic surgical systems for instrument guidance and navigation wherein the patient registration can be updated overtime to accurately reflect the instant patient situation.
In certain embodiments, the systems, apparatus, and methods disclosed herein relate to robotic surgical systems with built-in navigation capability for patient position tracking and surgical instrument guidance during a surgical procedure, without the need for a separate navigation system. Robotic based navigation of surgical instruments during surgical procedures allows for easy registration and operative volume identification and tracking. The systems, apparatus, and methods herein allow re-registration, model updates, and operative volumes to be performed intra-operatively with minimal disruption to the surgical workflow. In certain embodiments, navigational assistance can be provided to a surgeon by displaying a surgical instrument's position relative to a patient's anatomy. Additionally, by revising pre-operatively defined data such as operative volumes, patient-robot orientation relationships, and anatomical models of the patient, a higher degree of precision and lower risk of complications and serious medical error can be achieved.
In certain embodiments, described herein is a robotic surgical system comprising a robotic arm that has a directly or indirectly attached force sensor that is used to collect spatial coordinates of a patient's anatomy. A surgeon can maneuver the robotic arm between different points in space and contact the patient at different points on the patient's anatomy with an instrument attached to the robotic arm. In certain embodiments, the instrument comprises the force sensor. Contact is determined based on haptic feedback registered by the force sensor. In certain embodiments, a threshold (e.g., a magnitude of haptic feedback) must be exceeded in order to register the contact as belonging to the patient's anatomy. Furthermore, in this way, the magnitude of haptic feedback can be used to determine the type of tissue being contacted (e.g., because bone is harder than soft tissue). In some embodiments, the instrwnent contacts a specially engineered fiducial marker attached to the patient's anatomy at one or more of a set of orienting contact points (e.g., indents), wherein the fiducial marker has an established spatial relationship with the patient's anatomy (e.g., given its known size and intended attachment at a specific known location on the patient's anatomy). A plurality of spatial coordinates can be recorded and stored electronically using a plurality of contacts of the instrwnent to the patient's anatomy.
A set of spatial coordinates recorded from contact of the instrwnent with the patient's anatomy can be used to perform many navigational and surgical guidance functions such as registration, modeling volume removal, re-registration, defining operational volumes, revising operational volumes after re-registration, converting stored volume models to physical locations, and displaying surgical relative to a patient's anatomy on navigation screens.
By mapping surfaces defined by sets of coordinates obtained by contacting a patient's anatomy to a model of their anatomy (e.g., from medical image data), a coordinate mapping can be recorded that translates between the coordinate systems of the model and physical reality. For example, the model can be represented in a medical image data coordinate system and physical reality in a robot coordinate system. Thus, a robotic surgical system can know the physical location of the patient's anatomy relative to a surgical instrument attached hereto. Using the combination of haptic-feedback-generated sets of spatial coordinates and sets of medical image data coordinates that model the surface of a patient's anatomy, the aforementioned navigational and surgical guidance functions can be performed quickly and with high precision pre- and/or intra-operatively.
A set of spatial coordinates can be used to register the patient's anatomy with a model of the patient's anatomy derived from medical image data. Medical image data may be used from any relevant technique. Examples include, but are not limited to, x-ray data, tomographic data (e.g., CT data), magnetic resonance imaging (MM) data, and flat-panel fluoroscopy (e.g., 0-Arm) data. In some embodiments, such medical image data is taken intra-operatively. In this way, the physical position and orientation of a patient's anatomy can be mapped to the model of the patient's anatomy and the robotic surgical system can know where it is in relation to the anatomy at all times.
A set of spatial coordinates can be used to update a model of a patient's anatomy after volume removal by determining the volume removed using additional contacts between the instrument and the patient's anatomy. Contacts determined to be made on the new surface of the anatomy that correspond to coordinates inside the volume of the model can be used to update the surface of the model to reflect the patient's new anatomy.
A set of spatial coordinates collected intra-operatively can be used to re-register the patient's anatomy. In this way, changes that have occurred in the anatomy, such as re-orientation or re-positioning of all of or a part of the anatomy, can be used to update the mapping between the robot coordinate system and the medical image data coordinate system as well as the model of the patient's anatomy.
A set of spatial coordinates can be used to define an operational volume, wherein the movement of a surgical instrument is constrained to be within the operational volume during a part of a procedure. For example, this can be used to limit the volume of bone removed by a surgeon. The operational volume may be defined by contacting points on the patient's anatomy and using those as vertices of a surface or by mapping a model of the anatomical volume to the set of spatial coordinates and then defining the operational volume as the mapped anatomical model expressed in the robotic surgical system's coordinate system. The operational volume can be updated after a re-registration to accurately reflect the patient's current anatomy and/or anatomical position and orientation. Likewise, a stored model (e.g., a model generated from medical image data) can be used to define a physical location of a portion (or entirety) of that model by using a coordinate mapping.
A rendering of the patient's anatomy and a surgical instrument's position relative to the anatomy can be displayed on a navigation screen for use and/or reference by a surgeon using the methods and systems described herein. By using a coordinate mapping, the location of a terminal point of a surgical instrument can be displayed along with a rendering of the patient's anatomy such that a surgeon can observe an accurate representation of the space or distances between the terminal point and the patient's anatomy. This can be used to visualize trajectories, positions, and orientations of the surgical instrument relative to the patient's anatomy. A surgeon may use this to monitor the progress of a surgical procedure, avoid a serious medical error, and/or improve patient outcome by revising the planned surgical procedure. For example, the surgeon can use the navigational display in deciding to alter the volume planned for removal or the planned orientation or trajectory of the surgical tool when removing the volume. This can be done intra-operatively.
In another aspect, the disclosed technology includes a robot-based navigation system for real-time, dynamic re-registration of a patient position (e.g., position of vertebrae of a patient) during a procedure (e.g., surgical procedure, e.g., a spinal surgery) (e.g., a combined navigation/robotic system), the system including: (a) a robotic arm (e.g., having 3, 4, 5, 6, or 7 degrees of freedom) including: an end effector [e.g., said end effector including a surgical instrument holder for insertion or attachment of a surgical instrument therein/thereto, e.g., said robotic arm designed to allow direct manipulation of said surgical instrument by an operator (e.g., by a surgeon) when the surgical instrument is inserted in/attached to the surgical instrument holder of the end effector, said manipulation subject to haptic constraints based on the position of the end effector (and/or the surgical instrument) in relation to the patient, e.g., said surgical instrument having known geometry and fixed position in relation to the surgical instrument holder]; (ii) a position sensor for dynamically tracking a position of the end effector [e.g., during a surgical procedure) (and/or for dynamically tracking one or more points of the surgical instrument, e.g., in 30 space, e.g., during a surgical procedure) (e.g., at a rate of at least 100 Hz, e.g., 250 Hz or greater, e.g., 500 Hz or greater, e.g., 1000 Hz or greater (position determinations per second)]; and (iii) a force feedback subsystem (e.g., including sensor(s), actuator(s), controller(s), servo(s), and/or other mechanisms) for delivering a haptic force to a user manipulating the end effector (e.g., manipulating a surgical instrument inserted in the instrument holder of the end effector) (e.g., wherein the force feedback subsystem includes one or more sensors for performing one or more of (I) to (IV) as follows: (I) detecting a resistive force caused by the surgical instrument contacting, moving against, penetrating, and/or moving within a tissue of the patient, (II) distinguishing between contacted tissue types (e.g., determining when contacted tissue meets or exceeds a threshold resistance, e.g., when the tissue is bone), (III) detecting a force delivered by the operator (e.g., the surgeon, e.g., delivered by direct manipulation of the surgical instrument inserted in the surgical instrument holder of the end effector) (e.g., to cause movement of the surgical instrument and, therefore, the end effector), and (IV) distinguishing between the force delivered by the operator and the resistive force caused by movement of the surgical instrument in relation to the tissue of the patient; (b) a display [e.g., attached to, embedded within, or otherwise positioned in relation to the robotic arm being directly manipulated by the operator (e.g., surgeon) to allow for unimpeded visual feedback to the operator during the procedure, e.g., wherein the display is positioned beneath a transparent or semitransparent sterile drape, e.g., wherein the display has touch sensors for control of the display during use]; and (c) a processor of a computing device programmed to execute a set of instructions to: (i) access (e.g., and graphically render on the display) an initial registration of the patient position (e.g., position of the vertebrae of the patient) (e.g., via medical images of the patient, e.g., MRI, CT, X-rays, SPECT, ultrasound, or the like, e.g., said medical images obtained pre-operatively)(e.g., for storing and/or rendering a 3D representation, e.g., a 3D graphical representation and/or a 3D haptic representation, of an initial patient situation, e.g., wherein the 3D graphical representation is the same as or different from the 3D haptic representation, e.g., for use in displaying a real-time graphical representation of the patient situation (e.g., a target anatomy) on the display and/or for use in dynamically determining a force feedback delivered to the operator, e.g., during a surgical procedure, via the force feedback subsystem); (ii) dynamically determine a position of the end effector (e.g., dynamically determine a 3D position of one or more points of a surgical instrument positioned in relation to the end effector, e.g., within an instrument holder of the end effector); (iii) dynamically determine a force received by the end effector and/or a force to be delivered to the end effector [e.g., a force received by and/or a force to be delivered to the end effector via the surgical instrument, e.g., dynamically perform one or more of (I) to (IV) as follows: (I) determine a resistive force caused by the surgical instrwnent contacting, moving against, penetrating, and/or moving within a tissue of the patient, (II) distinguish between contacted tissue types (e.g., determining when contacted tissue meets or exceeds a threshold resistance, e.g., when the tissue is bone), (III) detect a force delivered by the operator (e.g., the surgeon, e.g., delivered by direct manipulation of the surgical instrument inserted in the surgical instrument holder of the end effector) (e.g., to cause movement of the surgical instrwnent and, therefore, the end effector), and (IV) distinguish between the force delivered by the operator and the resistive force caused by movement of the surgical instrument in relation to the tissue of the patient, (e.g., using the force feedback subsystem, e.g., the force to be dynamically determined at a rate of at least 100 Hz, e.g., 250 Hz or greater, e.g., 500 Hz or greater, e.g., 1000 Hz or greater)]; (iv) dynamically determine a position of the position sensor of the robotic arm for dynamically tracking the end effector (e.g., determine a position of the position sensor of the robotic arm upon contact of the surgical instrument with bone tissue of the patient, or other target tissue of the patient) (e.g., dynamically update the recorded position of the position sensor at a rate of at least 100 Hz, e.g., 250 Hz or greater, e.g., 500 Hz or greater, e.g., 1000 Hz or greater); (v) dynamically re-register the patient position based at least in part on an updated position of the end effector determined by the position sensor [(e.g., during a surgical procedure) (e.g., update the 30 representation of the patient situation, e.g., the 30 graphical representation and/or the 30 haptic representation, based at least in part on the updated position of the end effector when it is determined (e.g., via the force feedback subsystem) that the surgical instrument is in contact with a target anatomy, e.g., in contact with bone of the patient) (e.g., using a surface matching algorithm keyed to the initial (or previous) registration) (e.g., dynamically re-register the patient position upon detected contact of the end effector, or the surgical instrument, or a portion or component of the surgical instrument or end effector, with a pre-planned fiducial (e.g., a mechanical marker, e.g., a marker fixed to the patient, e.g., attached to target anatomy, e.g., attached to a vertebra)) (e.g., dynamically re-register the patient position upon detected proximity of the end effector, or the surgical instrument, or a portion or component of the surgical instrument or end effector, with a pre-planned fiducial (e.g., a mechanical marker, e.g., a marker fixed to the patient, e.g., attached to target anatomy, e.g., attached to a vertebra)) (e.g., dynamically re-register the patient position based upon the updated position of the end effector determined upon operator command, e.g., surgeon pressing a button or otherwise activating a graphical or tactile user interface when a re-registered representation is desired)]; (vi) graphically render the re-registered patient position for viewing on the display (e.g., graphically render the updated 3D graphical representation); and (vii) dynamically determine a force feedback to deliver via the force feedback subsystem (e.g., to an operator of the robotic arm during the surgical procedure) based at least in part on the re-registered patient position [(e.g., based at least on the updated 3D representation of the patient situation and a current position of the end effector (and/or the surgical instrument) (e.g., subject to predetermined go/no-go zones) (e.g., thereby permitting, facilitating, directing (e.g., imposing a haptic detent or well), inhibiting (e.g., imposing a speed constraint), and/or disallowing movement of the surgical instrument in go/no-go zones, e.g., by direct manipulation of the surgical instrument by the operator, e.g., surgeon)].
In another aspect, the disclosed technology includes a method of registering a patient's anatomy with an instrument attached to an end-effector of a robotic arm of a robotic surgical system, the method including the steps of: receiving, by a processor of a computing device, haptic feedback, from a force sensor attached directly or indirectly to the robotic arm, prompted by movement of the end-effector (e.g., towards a patient); determining, by the processor, that the haptic feedback corresponds to contact of the instrument with a material (e.g., having a certain density or certain mechanical properties) (e.g., based at least on a magnitude of the haptic feedback exceeding a threshold) (e.g., additionally based on the location of at least one point on the instrument) (e.g., wherein the material is bone); determining, by the processor, a set of spatial coordinates, wherein the set of spatial coordinates includes a spatial coordinate for each contact of the instrument with the material, expressed using a robot coordinate system, (e.g., relative to the position of the end-effector), wherein each spatial coordinate corresponds to a point on the surface of an anatomical volume (e.g., a point on a surface of a bone); receiving, by the processor, a set of medical image data coordinates expressed using a medical image data coordinate system that correspond to a patient anatomy surface (e.g., determined from tomographic patient data (e.g., CT data, Mill data)); mapping, by the processor, (e.g., using surface matching) the surface corresponding to the set of spatial coordinates to the patient anatomy surface corresponding to the set of medical image data coordinates (e.g., by generating a transformation array or transformation matrix); generating, by the processor, a coordinate mapping between the robot coordinate system and the medical image data coordinate system based on the mapping between the surface corresponding to the set of spatial coordinates and the surface corresponding to the set of medical image data coordinates; and storing, by the processor, the coordinate mapping, thereby registering the patient's anatomy (e.g., for navigational use by a surgeon during a surgical procedure).
In certain embodiments, the method includes the step of: outputting, by the processor rendering data for display (e.g., on a display of the robotic surgical system; e.g., on a display on the robotic arm), wherein the rendering data corresponds to a representation of a position of a member and at least a portion of the medical image data based on the coordinate mapping, wherein the member is selected from the group consisting of: the end-effector, the instrument, and a surgical instrument.
In certain embodiments, the method includes the steps of: generating, by the processor, new rendering data by modifying the rendering data based on a change in the end-effector's position; and outputting, by the processor, the new rendering data for display.
In certain embodiments, a fiducial marker includes the material (e.g., the end-effector contacts a fiducial marker with known size and shape such that the spatial coordinate is determined using a spatial relationship between the fiducial marker and the patient's anatomy).
In certain embodiments, the robotic arm is active and non-back drivable.
In certain embodiments, the robotic surgical system includes the processor.
In certain embodiments, the method includes storing, by the processor, a patient anatomy model wherein the patient anatomy model is defined by the patient anatomy surface expressed in the robot coordinate system.
In one aspect, the disclosed technology includes a robotic surgical system for registering a patient's anatomy with an instrument attached to an end-effector of a robotic arm of the robotic surgical system, the system including: a robotic arm with amend-effector having an instrument attached thereto; a force sensor attached directly or indirectly to the robotic arm (e.g., the force sensor located between the instrument and the robotic arm); and a processor and a memory having instructions stored thereon, wherein the instructions, when executed by the processor, cause the processor to: receive haptic feedback, from the force sensor, prompted by movement of the end-effector (e.g., towards a patient); determine that the haptic feedback corresponds to contact of the instrument with a material (e.g., having a certain density or certain mechanical properties) (e.g., based at least on a magnitude of the haptic feedback exceeding a threshold) (e.g., additionally based on the location of at least one point on the instrument) (e.g., wherein the material is bone); determine a set of spatial coordinates, wherein the set of spatial coordinates includes a spatial coordinate for each contact of the instrument with the material, expressed using a robot coordinate system, (e.g., relative to the position of the end-effector), wherein each spatial coordinate corresponds to a point on the surface of an anatomical volume (e.g., a point on a surface of a bone); determine a set of medical image data coordinates expressed using a medical image data coordinate system that correspond to a patient anatomy surface (e.g., determined from tomographic patient data (e.g., CT data, Mill data)); map (e.g., using surface matching) the surface corresponding to the set of spatial coordinates to the patient anatomy surface corresponding to the set of medical image data coordinates (e.g., by generating a transformation array or transformation matrix); generate a coordinate mapping between the robot coordinate system and the medical image data coordinate system based on the mapping between the surface corresponding to the set of spatial coordinates and the surface corresponding to the set of medical image data coordinates; and store the coordinate mapping, thereby registering the patient's anatomy (e.g., for navigational use by a surgeon during a surgical procedure).
In certain embodiments, the instructions, when executed by the processor, cause the processor to: output rendering data for display (e.g., on a display of the robotic surgical system; e.g., on a display on the robotic arm), wherein the rendering data corresponds to a representation of a position of a member and at least a portion of the medical image data based on the coordinate mapping, wherein the member is selected from the group consisting of: the end-effector, the instrument, and a surgical instrument.
In certain embodiments, the instructions, when executed by the processor, cause the processor to: generate new rendering data by modifying the rendering data based on a change in the end-effector's position; and output the new rendering data for display.
In certain embodiments, a fiducial marker includes the material (e.g., the end-effector contacts a fiducial marker with known size and shape such that the spatial coordinate is determined using a spatial relationship between the fiducial marker and the patient's anatomy).
In certain embodiments, the robotic arm is active and non-back drivable.
In certain embodiments, the robotic surgical system includes the processor.
In certain embodiments, the instructions, when executed by the processor, cause the processor to: store a patient anatomy model wherein the patient anatomy model is defined by the patient anatomy surface expressed in the robot coordinate system.
In one aspect, the disclosed technology includes a method of updating a model of a patient's anatomy after volume removal with an instrument attached to an end-effector of a robotic arm of a robotic surgical system, the method including the steps of: receiving, by a processor of a computing device, haptic feedback, from a force sensor attached directly or indirectly to therobotic arm, prompted by movement of the end-effector (e.g., towards a patient); determining, by the processor, that the haptic feedback corresponds to contact of the instrument with a material (e.g., having a certain density or certain mechanical properties) (e.g., based at least on a magnitude of the haptic feedback exceeding a threshold) (e.g., additionally based on the location of at least one point on the instrument) (e.g., wherein the material is bone); determining, by the processor, a set of spatial coordinates, wherein the set of spatial coordinates includes a spatial coordinate for each contact of the instrument with the material, expressed using a robot coordinate system (e.g., relative to the position of the end-effector), wherein each spatial coordinate corresponds to a point on the surface of an anatomical volume (e.g., a point on a surface of a bone); receiving, by the processor, a set of medical image data coordinates that correspond to the surface of a volume of the patient's anatomy, wherein each medical image data coordinate in the set of medical image data coordinates is expressed using a medical image data coordinate system; receiving, by the processor, a coordinate mapping between the robot coordinate system and the medical image data coordinate system (e.g., a transformation array or transformation matrix); determining, by the processor, one or more interior spatial coordinates in the set of spatial coordinates that correspond to points inside the surface of the volume of the patient's anatomy based on the set of medical image data coordinates and the coordinate mapping; generating, by the processor, a set of interior medical image data coordinates, wherein the set of interior medical image data coordinates includes an interior medical image data coordinate for each of the one or more interior spatial coordinates using the coordinate mapping; modifying, by the processor, the set of medical image data coordinates that define the surface of the volume of the patient's anatomy with the set of interior medical image data coordinates such that a first volume defined by the set of medical image data coordinates is larger than a second volume defined by the modified set of medical image data coordinates; and storing, by the processor, the modified set of medical image data coordinates (e.g., for displaying to a surgeon), thereby updating the model of the patient's anatomy.
In one aspect, the disclosed technology includes a system for updating a model of a patient's anatomy after volume removal with an instrument attached to an end-effector of a robotic arm of a robotic surgical system, the system including: a robotic arm with an end-effector having an instrument attached thereto; a force sensor attached directly or indirectly to the robotic arm (e.g., the force sensor located between the instrument and the robotic arm); and a processor and a memory having instructions stored thereon, wherein the instructions, when executed by the processor, cause the processor to: receive haptic feedback, from the force sensor, prompted by movement of the end-effector (e.g., towards a patient); determine that the haptic feedback corresponds to contact of the instrument with a material (e.g., having a certain density or certain mechanical properties) (e.g., based at least on a magnitude of the haptic feedback exceeding a threshold) (e.g., additionally based on the location of at least one point on the instrument) (e.g., wherein the material is bone); determine a set of spatial coordinates, wherein the set of spatial coordinates includes a spatial coordinate for each contact of the instrument with the material, expressed using a robot coordinate system (e.g., relative to the position of the end-effector), wherein each spatial coordinate corresponds to a point on the surface of an anatomical volume (e.g., a point on a surface of a bone); receive a set of medical image data coordinates that correspond to the surface of a volume of the patient's anatomy, wherein each medical image data coordinate in the set of medical image data coordinates is expressed using a medical image data coordinate system; receive a coordinate mapping between the robot coordinate system and the medical image data coordinate system (e.g., a transformation array or transformation matrix);determine one or more interior spatial coordinates in the set of spatial coordinates that correspond to points inside the surface of the volume of the patient's anatomy based on the set of medical image data coordinates and the coordinate mapping; determine a portion of the volume of the patient's anatomy that has been removed using the one or more interior spatial coordinates; generate a set of interior medical image data coordinates, wherein the set of interior medical image data coordinates includes an interior medical image data coordinate for each of the one or more interior spatial coordinates using the coordinate mapping; modify the set of medical image data coordinates that define the surface of the volante of the patient's anatomy with the set of interior medical image data coordinates such that a first volume defined by the set of medical image data coordinates is larger than a second volume defined by the modified set of medical image data coordinates; and store the modified set of medical image data coordinates (e.g., for displaying to a surgeon), thereby updating the model of the patient's anatomy.
In one aspect, the disclosed technology includes a method of re-registration patient's anatomy during a surgical procedure with an instrument attached to an end-effector of a robotic arm of a robotic surgical system, the method including the steps of: receiving, by a processor of a computing device, haptic feedback, from a force sensor attached directly or indirectly to the robotic arm, prompted by movement of the end-effector (e.g., towards a patient); determining, by the processor, that the haptic feedback corresponds to contact of the instrument with a material (e.g., having a certain density or certain mechanical properties) (e.g., based at least on a magnitude of the haptic feedback exceeding a threshold) (e.g., additionally based on the location of at least one point on the instrument) (e.g., wherein the material is bone); determining, by the processor, a set of spatial coordinates, wherein the set of spatial coordinates includes a spatial coordinate for each contact of the instrument with the material, expressed using the robot coordinate system (e.g., relative to the position of the end-effector), wherein each spatial coordinate corresponds to a point on the surface of an anatomical volume (e.g., a point on a surface of a bone); receiving, by the processor, a coordinate mapping between a robot coordinate system and a medical image data coordinate system (e.g., a transformation array or transformation matrix), wherein the robot coordinate system corresponds to a physical coordinate system of the end-effector; updating, by the processor, the coordinate mapping based on a mapping of the surface corresponding to the set of spatial coordinates; and storing, by the processor, the updated coordinate mapping (e.g., to provide an accurate navigational model for use by a surgeon during a surgical procedure), thereby re-registering the patient's anatomy, the mapping is generated using surface matching.
In certain embodiments, the updating step includes: determining, by the processor, a set of modeling coordinates, by converting, using the coordinate mapping, a set of medical image modeling coordinates defining the surface of a volume of a patient anatomy, wherein the set of modeling coordinates are expressed in the robot coordinate system and define an anticipated location of the surface of the volume, and the set of medical image modeling coordinates have been generated from medical imaging data; and mapping, by the processor, (e.g., using surface matching,) the surface corresponding to the set of spatial coordinates to the patient anatomy surface corresponding to the set of modeling coordinates (e.g., by generating a transformation array or transformation matrix); and updating, by the processor, the coordinate mapping based on the mapping of the surface corresponding to the set of spatial coordinates to the set of modeling coordinates.
In certain embodiments, the updating step includes: receiving, by the processor, a set of modeling coordinates, wherein the set of modeling coordinates are expressed in the robot coordinate system and define the surface of a volume of a patient anatomy; mapping, by the processor, (e.g., using surface matching,) the surface corresponding to the set of spatial coordinates to the patient anatomy surface corresponding to the set of modeling coordinates (e.g., by generating a transformation array or transformation matrix); and updating, by the processor, the coordinate mapping based on the mapping of the surface corresponding to the set of spatial coordinates to the set of modeling coordinates.
In one aspect, the disclosed technology includes a system for re-registering a patient's anatomy during a surgical procedure with an instrument attached to an end-effector of a robotic arm of a robotic surgical system, the system including: a robotic arm with an end-effector having an instrument attached thereto; a force sensor attached directly or indirectly to the robotic arm (e.g., the force sensor located between the instrument and the robotic arm); and a processor and a memory having instructions stored thereon, wherein the instructions, when executed by the processor, cause the processor to: receive haptic feedback, from the force sensor, prompted by movement of the end-effector (e.g., towards a patient); determine that the haptic feedback corresponds to contact of the instrument with a material (e.g., having a certain density or certain mechanical properties) (e.g., based at least on a magnitude of the haptic feedback exceeding a threshold) (e.g., additionally based on the location of at least one point on the instrument) (e.g., wherein the material is bone); determine a set of spatial coordinates, wherein the set of spatial coordinates includes a spatial coordinate for each contact of the instrument with the material, expressed using the robot coordinate system (e.g., relative to the position of the end-effector), wherein each spatial coordinate corresponds to a point on the surface of an anatomical volume (e.g., a point on a surface of a bone); receive a coordinate mapping between a robot coordinate system and a medical image data coordinate system (e.g., a transformation array or transformation matrix), wherein the robot coordinate system corresponds to a physical coordinate system of the end-effector; update the coordinate mapping based on a mapping of the surface corresponding to the set of spatial coordinates; and store the updated coordinate mapping (e.g., to provide an accurate navigational model for use by a surgeon during a surgical procedure), thereby re-registering the patient's anatomy.
In certain embodiments, the mapping is generated using surface matching.
In certain embodiments, the updating step includes instructions that, when executed by the processor, cause the processor to: determine a set of modeling coordinates, by converting, using the coordinate mapping, a set of medical image modeling coordinates defining the surface of a volume of a patient anatomy, wherein: the set of modeling coordinates are expressed in the robot coordinate system and define an anticipated location of the surface of the volume, and the set of medical image modeling coordinates have been generated from medical imaging data; and map (e.g., using surface matching,) the surface corresponding to the set of spatial coordinates to the patient anatomy surface corresponding to the set of modeling coordinates (e.g., by generating a transformation array or transformation matrix); and update the coordinate mapping based on the mapping of the surface corresponding to the set of spatial coordinates to the set of modeling coordinates.
In certain embodiments, the updating step includes instructions that, when executed by the processor, cause the processor to: receive a set of modeling coordinates, wherein the set of modeling coordinates are expressed in the robot coordinate system and define the surface of a volume of a patient anatomy; map (e.g., using surface matching,) the surface corresponding to the set of spatial coordinates to the patient anatomy surface corresponding to the set of modeling coordinates (e.g., by generating a transformation array or transformation matrix); and update the coordinate mapping based on the mapping of the surface corresponding to the set of spatial coordinates to the set of modeling coordinates.
In one aspect, the disclosed technology includes a method of defining an operational volume in which a surgical instrument attached to an end-effector of a robotic arm of a robotic surgical system can be maneuvered, the method including the steps of: receiving, by a processor of a computing device, haptic feedback, from a force sensor attached directly or indirectly to the robotic arm, prompted by movement of the end-effector (e.g., towards a patient); determining, by the processor, that the haptic feedback corresponds to contact of the instrument with a material (e.g., having a certain density or certain mechanical properties) (e.g., based at least on a magnitude of the haptic feedback exceeding a threshold) (e.g., additionally based on the location of at least one point on the instrument) (e.g., wherein the material is bone); determining, by the processor, a set of spatial coordinates, wherein the set of spatial coordinates includes a spatial coordinate for each contact of the instrument with the material, expressed using a robot coordinate system (e.g., relative to the position of the end-effector), wherein each spatial coordinate corresponds to a point on the surface of a volume (e.g., a point on a surface of a bone); receiving, by the processor, a model volume selected by a user (e.g., a model of a portion of bone to be removed), wherein the model volume is expressed in a robot coordinate system; mapping, by the processor, the surface of the model volume to the set of spatial coordinates; generating, by the processor, an updated model volume, wherein coordinates of the updated model volume are generated by converting coordinates of the model volume using the mapping of the surface of the model volume to the set of spatial coordinates; and storing, by the processor, the updated model volume.
In certain embodiments, the updated model volume is a constrained operational volume, wherein a terminal point of the surgical instrument is temporarily constrained to within the constrained operational volume.
In certain embodiments, the model volume is generated from medical image data using a coordinate mapping.
In certain embodiments, the method includes receiving, by the processor, the updated model volume (e.g., a model of a portion of bone to be removed), wherein the stored model volume is expressed in a first robot coordinate system; receiving, by the processor, an updated coordinate mapping expressed in a second robot coordinate system; mapping, by the processor, the first robot coordinate system to the second robot coordinate system; generating, by the processor, a second updated model volume by converting coordinates of the updated model volume to updated coordinates expressed in the second robot coordinate system using the mapping between the first robot coordinate system and the second robot coordinate system; and storing, by the processor, the second updated model volume.
In one aspect, the disclosed technology includes a system for defining an operational volume in which a surgical instrument attached to an end-effector of a robotic arm of a robotic surgical system can be maneuvered, the system including: a robotic arm with an end-effector having an instrument attached thereto; a force sensor attached directly or indirectly to the robotic arm (e.g., the force sensor located between the instrument and the robotic arm); and a processor and a memory having instructions stored thereon, wherein the instructions, when executed by the processor, cause the processor to: receive haptic feedback, from the force sensor, prompted by movement of the end-effector (e.g., towards a patient); determine that the haptic feedback corresponds to contact of the instrument with a material (e.g., having a certain density or certain mechanical properties) (e.g., based at least on a magnitude of the haptic feedback exceeding a threshold) (e.g., additionally based on the location of at least one point on the instrument) (e.g., wherein the material is bone); determine a set of spatial coordinates, wherein the set of spatial coordinates includes a spatial coordinate for each contact of the instrument with the material, expressed using a robot coordinate system (e.g., relative to the position of the end-effector), wherein each spatial coordinate corresponds to a point on the surface of a volume (e.g., a point on a surface of a bone); receive a model volume selected by a user (e.g., a model of a portion of bone to be removed), wherein the model volume is expressed in a robot coordinate system; map the surface of the model volume to the set of spatial coordinates; generate an updated model volume, wherein coordinates of the updated model volume are generated by converting coordinates of the model volume using the mapping of the surface of the model volume to the set of spatial coordinates; and store the updated model volume.
In certain embodiments, the updated model volume is a constrained operational volume, wherein a terminal point of the surgical instrument is temporarily constrained to within the constrained operational volume.
In certain embodiments, the model volume is generated from medical image data using a coordinate mapping.
In certain embodiments, the instructions, when executed by the processor, cause the processor to: receive the updated model volume (e.g., a model of a portion of bone to be removed), wherein the stored model volume is expressed in a first robot coordinate system; receive an updated coordinate mapping expressed in a second robot coordinate system; map the first robot coordinate system to the second robot coordinate system; generate a second updated model volume by converting coordinates of the updated model volume to updated coordinates expressed in the second robot coordinate system using the mapping between the first robot coordinate system and the second robot coordinate system; and store the second updated model volume.
In one aspect, the disclosed technology includes a method of displaying a position of a surgical instrument attached to a robotic arm relative to a patient anatomy for navigation during a robotically-assisted surgical procedure, the method including: receiving, by a processor of a computing device, a location of a terminal point of the surgical tool (e.g., wherein the location of the terminal point is determined, by the processor, using a known (e.g., stored) distance between a location of the robotic arm and the terminal point), wherein the location is expressed in a robot coordinate system; receiving, by the processor, a coordinate mapping between the robot coordinate system and a medical image data coordinate system (e.g., a transformation array or transformation matrix); converting, by the processor, using the coordinate mapping, the location of the terminal point, such that the converted location of the terminal point is expressed in a medical image data coordinate system; generating, by the processor, rendering data including the converted location of the terminal point; and outputting, by the processor, the rendering data, wherein a display of the rendering data includes a representation of the patient anatomy and a representation of the location of the terminal point, wherein a simulated distance between a point on the representation of the patient anatomy and the representation of the terminal point is proportional to a spatial distance between the terminal point and the corresponding point on the patient's anatomy.
In certain embodiments, the rendering data corresponding to the representation of the patient anatomy is generated from medical image data coordinates generated from medical imaging data, wherein the medical image data coordinates are expressed in the medical image data coordinate system.
In one aspect, the disclosed technology includes a system of displaying a position of a surgical instrument attached to a robotic arm relative to a patient anatomy for navigation during a robotically-assisted surgical procedure, the system including: a robotic arm with an end-effector having an instrument attached thereto; a force sensor attached directly or indirectly to the robotic arm (e.g., the force sensor located between the instrument and the robotic arm); and a processor and a memory having instructions stored thereon, wherein the instructions, when executed by the processor, cause the processor to: receive a location of a terminal point of the surgical tool (e.g., wherein the location of the terminal point is determined, by the processor, using a known (e.g., stored) distance between a location of the robotic arm and the terminal point), wherein the location is expressed in a robot coordinate system; receive a coordinate mapping between the robot coordinate system and a medical image data coordinate system (e.g., a transformation array or transformation matrix); convert, using the coordinate mapping, the location of the terminal point, such that the converted location of the terminal point is expressed in a medical image data coordinate system; generate rendering data including the converted location of the terminal point; output the rendering data, wherein a display of the rendering data includes a representation of the patient anatomy and a representation of the location of the terminal point, wherein a simulated distance between a point on the representation of the patient anatomy and the representation of the terminal point is proportional to a spatial distance between the terminal point and the corresponding point on the patient's anatomy.
In certain embodiments, the rendering data corresponding to the representation of the patient anatomy is generated from medical image data coordinates generated from medical imaging data, wherein the medical image data coordinates are expressed in the medical image data coordinate system.
In one aspect, the disclosed technology includes a method of performing volume removal surgery with one or more instruments, wherein the one or more instruments used by attaching to an end-effector of a robotic arm of a robotic surgical system, the method including the steps of: registering a patient's anatomy to express a model of the patient's anatomy in a robot coordinate system; contacting, following removal of a first volume of the patient's anatomy, an instrument attached to the end-effector to the patient's anatomy in a plurality of locations, wherein contact is determined by haptic feedback from a force sensor attached directly or indirectly to the robotic arm, wherein the haptic feedback is prompted by movement of the end-effector (e.g., towards a patient); updating the model of the patient's anatomy by determining a portion of the model that corresponds to the first volume of the patient's anatomy that has been removed using spatial coordinates corresponding to the plurality of locations contacted; optionally, re-registering the patient's anatomy by contacting a plurality of re-registration locations with the instrument, wherein contact is determined by haptic feedback from a force sensor attached directly or indirectly to the robotic arm, wherein the haptic feedback is prompted by movement of the end-effector (e.g., towards a patient), and coordinates in the model of the patient's anatomy are converted such that they are expressed in a new robot coordinate system based on the re-registration; defining an operational volume, wherein the operational volume is expressed in either the robot coordinate system or the new robot coordinate system (e.g., if the re-registration step is performed); and maneuvering the robotic arm such that a pre-defined terminal point on a surgical instrument is constrained to within the operational volume for a period of time during a second volume removal.
In certain embodiments, the registering step includes: receiving, by a processor of a computing device, haptic feedback, from a force sensor attached directly or indirectly to the robotic arm, prompted by movement of the end-effector (e.g., towards a patient); determining, by the processor, that the haptic feedback corresponds to contact of the instrument with a material (e.g., having a certain density or certain mechanical properties) (e.g., based at least on a magnitude of the haptic feedback exceeding a threshold) (e.g., additionally based on the location of at least one point on the instrument) (e.g., wherein the material is bone); determining, by the processor, a set of spatial coordinates, wherein the set of spatial coordinates includes a spatial coordinate for each contact of the instrument with the material, expressed using the robot coordinate system, (e.g., relative to the position of the end-effector), wherein each spatial coordinate corresponds to a point on the surface of an anatomical volume (e.g., a point on a surface of a bone); receiving, by the processor, a set of medical image data coordinates expressed using a medical image data coordinate system that correspond to a patient anatomy surface (e.g., determined from tomographic patient data (e.g., CT data, MM data)); mapping, by the processor, (e.g., using surface matching,) the surface corresponding to the set of spatial coordinates to the patient anatomy surface corresponding to the set of medical image data coordinates (e.g., by generating a transformation array or transformation matrix); generating, by the processor, a coordinate mapping between the robot coordinate system and the medical image data coordinate system based on the mapping between the surface corresponding to the set of spatial coordinates and the surface corresponding to the set of medical image data coordinates; and storing, by the processor, the coordinate mapping (e.g., for navigational use by a surgeon during a surgical procedure).
In certain embodiments, the method including the step of: outputting, b y the processor, rendering data for display, wherein the rendering data corresponds to a representation of a member's position and at least a portion of the medical image data based on the coordinate mapping, wherein the member is selected from the group consisting of: the end-effector, the instrument, and a surgical instrument. In certain embodiments, the method including the steps of: generating, by the processor, new rendering data by modifying the rendering data based on a change in the end-effector's position; and outputting, by the processor, the new rendering data for display.
In certain embodiments, a fiducial marker includes the material (e.g., the end-effector contacts a fiducial marker with known size and shape such that the spatial coordinate is determined using a spatial relationship between the fiducial marker and the patient's anatomy).
In certain embodiments, the robotic arm is active and non-back drivable.
In certain embodiments, therobotic surgical system includes the processor.
In certain embodiments, the method includes storing, by the processor, a patient anatomy model wherein the patient anatomy model is defined by the patient anatomy surface expressed in the robot coordinate system.
In certain embodiments, the updating step includes: determining, by the processor, a set of spatial coordinates, wherein the set of spatial coordinates includes a spatial coordinate for each contact of the instrument with the material, expressed using a robot coordinate system (e.g., relative to the position of the end-effector), wherein each spatial coordinate corresponds to a point on the surface of an anatomical volume (e.g., a point on a surface of a bone); receiving, by the processor, a set of medical image data coordinates that correspond to the surface of a volume of the patient's anatomy, wherein each medical image data coordinate in the set of medical image data coordinates is expressed using a medical image data coordinate system; receiving, by the processor, a coordinate mapping between the robot coordinate system and the medical image data coordinate system (e.g., a transformation array or transformation matrix); determining, by the processor, one or more interior spatial coordinates in the set of spatial coordinates that correspond to points inside the surface of the volume of the patient's anatomy based on the set of medical image data coordinates and the coordinate mapping; determining, by the processor, a portion of the volume of the patient's anatomy that has been removed using the one or more interior spatial coordinates; generating, by the processor, a set of interior medical image data coordinates, wherein the set of interior medical image data coordinates includes an interior medical image data coordinate for each of the one or more interior spatial coordinates using the coordinate mapping; modifying, by the processor, the set of medical image data coordinates that define the surface of the volume of the patient's anatomy with the set of interior medical image data coordinates such that first volume defined by the set of medical image data coordinates is larger than second volume defined by the modified set of medical image data coordinates; and storing, by the processor, the modified set of medical image data coordinates (e.g., for displaying to a surgeon).
In certain embodiments, the defining step includes: receiving, by a processor of a computing device, haptic feedback, from a force sensor attached directly or indirectly to the robotic arm, prompted by movement of the end-effector (e.g., towards a patient); determining, by the processor, that the haptic feedback corresponds to contact of the instrument with a material (e.g., having a certain density or certain mechanical properties) (e.g., based at least on a magnitude of the haptic feedback exceeding a threshold) (e.g., additionally based on the location of at least one point on the instrwnent) (e.g., wherein the material is bone); determining, by the processor, a set of spatial coordinates, wherein the set of spatial coordinates includes a spatial coordinate for each contact of the instrwnent with the material, expressed using a robot coordinate system (e.g., relative to the position of the end-effector), wherein each spatial coordinate corresponds to a point on the surface of a volume (e.g., a point on a surface of a bone); receiving, by the processor, a model volume selected by a user (e.g., a model of a portion of bone to be removed), wherein the model volume is expressed in a robot coordinate system; mapping, by the processor, the surface of the model volume to the set of spatial coordinates; generating, by the processor, an updated model volume, wherein coordinates of the updated model volume are generated by converting coordinates of the model volume using the mapping of the surface of the model volume to the set of spatial coordinates; and storing, by the processor, the updated model volume.
In certain embodiments, the updated model volume is a constrained operational volume, wherein a terminal point of the surgical instrument is temporarily constrained to within the constrained operational volume.
In certain embodiments, the model volume is generated from medical image data using a coordinate mapping.
In certain embodiments, the method includes receiving, by the processor, the updated model volume (e.g., a model of a portion of bone to be removed), wherein the stored model volume is expressed in a first robot coordinate system; receiving, by the processor, an updated coordinate mapping expressed in a second robot coordinate system; mapping, by the processor, the first robot coordinate system to the second robot coordinate system; generating, by the processor, a second updated model volume by converting coordinates of the updated model volume to updated coordinates expressed in the second robot coordinate system using the mapping between the first robot coordinate system and the second robot coordinate system; and storing, by the processor, the second updated model volume.
In certain embodiments, the re-registering step includes: receiving, by a processor of a computing device, haptic feedback, from a force sensor attached directly or indirectly to the robotic arm, prompted by movement of the end-effector (e.g., towards a patient); determining, by the processor, that the haptic feedback corresponds to contact of the instrument with a material (e.g., having a certain density or certain mechanical properties) (e.g., based at least on a magnitude of the haptic feedback exceeding a threshold) (e.g., additionally based on the location of at least one point on the instrument) (e.g., wherein the material is bone); determining, by the processor, a set of spatial coordinates, wherein the set of spatial coordinates includes a spatial coordinate for each contact of the instrument with the material, expressed using the robot coordinate system (e.g., relative to the position of the end-effector), wherein each spatial coordinate corresponds to a point on the surface of an anatomical volume (e.g., a point on a surface of a bone); receiving, by the processor, a coordinate mapping between a robot coordinate system and a medical image data coordinate system (e.g., a transformation array or transformation matrix), wherein the robot coordinate system corresponds to a physical coordinate system of the end-effector; updating, by the processor, the coordinate mapping based on a mapping of the surface corresponding to the set of spatial coordinates; and storing, by the processor, the updated coordinate mapping (e.g., to provide an accurate navigational model for use by a surgeon during a surgical procedure).
In certain embodiments, the mapping is generated using surface matching.
In certain embodiments, the updating step includes: determining, by the processor, a set of modeling coordinates, by converting, using the coordinate mapping, a set of medical image modeling coordinates defining the surface of a volume of a patient anatomy, wherein the set of modeling coordinates are expressed in the robot coordinate system and define an anticipated location of the surface of the volume, and the set of medical image modeling coordinates have been generated from medical imaging data; and mapping, by the processor, (e.g., using surface matching,) the surface corresponding to the set of spatial coordinates to the patient anatomy surface corresponding to the set of modeling coordinates (e.g., by generating a transformation array or transformation matrix); and updating, by the processor, the coordinate mapping based on the mapping of the surface corresponding to the set of spatial coordinates to the set of modeling coordinates.
In certain embodiments, the updating step includes: receiving, by the processor, a set of modeling coordinates, wherein the set of modeling coordinates are expressed in the robot coordinate system and define the surface of a volume of a patient anatomy; mapping, by the processor, (e.g., using surface matching,) the surface corresponding to the set of spatial coordinates to the patient anatomy surface corresponding to the set of modeling coordinates (e.g., by generating a transformation array or transformation matrix); and updating, by the processor, the coordinate mapping based on the mapping of the surface corresponding to the set of spatial coordinates to the set of modeling coordinates.
In another aspect, the disclosed technology includes a method of updating an operational volume in which a surgical instrument attached to an end-effector of a robotic arm of a robotic surgical system can be maneuvered, the method including the steps of: receiving, by the processor, a stored model volume including coordinates (e.g., a model of a portion of bone to be removed), wherein the stored model volume is expressed in a first robot coordinate system; receiving, by the processor, an updated coordinate mapping expressed in a second robot coordinate system; converting, by the processor, each coordinate of the stored model volume to be expressed in the second robot coordinate system using the updated coordinate mapping; and storing, by the processor, an updated model volume including the converted coordinates.
In order for the present disclosure to be more readily understood, certain terms used herein are defined below. Additional definitions for the following terms and other terms may be set forth throughout the specification.
In this application, the use of “or” means “and/or” unless stated otherwise. As used in this application, the term “comprise” and variations of the term, such as “comprising” and “comprises,” are not intended to exclude other additives, components, integers or steps. As used in this application, the terms “about” and “approximately” are used as equivalents. Any numerals used in this application with or without about/approximately are meant to cover any normal fluctuations appreciated by one of ordinary skill in the relevant art. In certain embodiments, the term “approximately” or “about” refers to a range of values that fall within 25%, 20%, 19%, 18%, 17%, 16%, 15%, 14%, I3o/o, 12%, 11%, 10%,9%,8%, 7%,6%,5%,4%, 3%, 2%, 1%, or less in either direction (greater than or less than) of the stated reference value unless otherwise stated or otherwise evident from the context (except where such number would exceed 100% of a possible value).
Mapping: As used herein, “mapping” refers to establishing a function between two sets of coordinates or data corresponding to two sets of coordinates. The function between the two sets may be discrete or continuous. A mapping allows coordinates recorded and/or stored in one coordinate system to be converted to coordinates in another coordinate system and vice versa. Two sets of coordinates expressed in the same coordinate system may be mapped with each other as well. A map or mapping may be stored on a computer readable medium as an array or matrix of data. In certain embodiments, a map or mapping is a linear transform stored as an array on a computer readable medium. In certain embodiments, the map or mapping is used to convert between coordinate systems. In certain embodiments, the coordinate systems are Cartesian. In some embodiments, at least one of the coordinate systems is non-Cartesian. A mapping may be an optimized function, wherein the mapping represents the function of minimal error or error below a threshold according to the mapping method (e.g., surface matching). In certain embodiments, mapping comprises surface matching. Herein, “a map” and “a mapping” are used interchangeably.
Drawings are presented herein for illustration purposes, not for limitation. The foregoing and other objects, aspects, features, and advantages of the invention will become more apparent and may be better understood by referring to the following description taken in conjunction with the accompanying drawings, in which:
It is contemplated that systems, devices, methods, and processes of the claimed invention encompass variations and adaptations developed using information from the embodiments described herein. Adaptation and/or modification of the systems, devices, methods, and processes described herein may be performed by those of ordinary skill in the relevant art.
Throughout the description, where articles, devices, and systems are described as having, including, or comprising specific components, or where processes and methods are described as having, including, or comprising specific steps, it is contemplated that, additionally, there are articles, devices, and systems of the present invention that consist essentially of, or consist of, the recited components, and that there are processes and methods according to the present invention that consist essentially of, or consist of, the recited processing steps.
It should be understood that the order of steps or order for performing certain action is immaterial so long as the invention remains operable. Moreover, two or more steps or actions may be conducted simultaneously.
The mention herein of any publication, for example, in the Background section, is not an admission that the publication serves as prior art with respect to any of the claims presented herein. The Background section is presented for purposes of clarity and is not meant as a description of prior art with respect to any claim. Headers are provided for the convenience of the reader and are not intended to be limiting with respect to the claimed subject matter.
In some embodiments, the operation may be spinal surgery, such as a discectomy, a for aminotomy, a laminectomy, or a spinal fusion. In some implementations, the surgical robotic system includes a surgical robot 102 on a mobile cart. The surgical robot 102 may be positioned in proximity to an operating table 112 without being attached to the operating table, thereby providing maximum operating area and mobility to surgeons around the operating table and reducing clutter on the operating table. In alternative embodiments, the surgical robot (or cart) is securable to the operating table. In certain embodiments, both the operating table and the cart are secured to a common base to prevent any movement of the cart or table in relation to each other, even in the event of an earth tremor.
The mobile cart may permit a user (operator) 106a, such as a technician, nurse, surgeon, or any other medical personnel in the operating room, to move the surgical robot 102 to different locations before, during, and/or after a surgical procedure. The mobile cart enables the surgical robot 102 to be easily transported into and out of the operating room 100. For example, a user I06a may move the surgical robot into the operating room from a storage location. In some implementations, the mobile cart may include wheels, a track system, such as a continuous track propulsion system, or other similar mobility systems for translocation of the cart. The mobile cart may include an attached or embedded handle for locomotion of the mobile cart by an operator.
For safety reasons, the mobile cart may be provided with a stabilization system that may be used during a surgical procedure performed with a surgical robot. The stabilization system increases the global stiffness of the mobile cart relative to the floor in order to ensure the accuracy of the surgical procedure. In some implementations, the wheels include a locking system that prevents the cart from moving. The stabilizing, braking, and/or locking system may be activated when the machine is turned on. In some implementations, the mobile cart includes multiple stabilizing, braking, and/or locking systems. In some implementations, the stabilizing system is electro-mechanical with electronic activation. The stabilizing, braking, and/or locking system(s) may be entirely mechanical. The stabilizing, braking, and/or locking system(s) may be electronically activated and deactivated.
In some implementations, the surgical robot 102 includes a robotic arm mounted on a mobile cart. An actuator may move the robotic arm. The robotic arm may include a force control end-effector configured to hold a surgical tool. The robot may be configured to control and/or allow positioning and/or movement of the end-effector with at least four degrees of freedom (e.g., six degrees of freedom, three translations and three rotations).
In some implementations, the robotic arm is configured to releasably hold a surgical tool, allowing the surgical tool to be removed and replaced with a second surgical tool. The system may allow the surgical tools to be swapped without re-registration, or with automatic or semi-automatic re-registration of the position of the end-effector.
In some implementations, the surgical system includes a surgical robot 102, a tracking detector 108 that captures the position of the patient and different components of the surgical robot I 02, and a display screen 110 that displays, for example, real time patient data and/or real time surgical robot trajectories.
In some implementations, a tracking detector 108 monitors the location of patient 104 and the surgical robot 102. The tracking detector may be a camera, a video camera, an infrared detector, field generator and sensors for electro-magnetic tracking or any other motion detecting apparatus. In some implementation, based on the patient and robot position, the display screen displays a projected trajectory and/or a proposed trajectory for the robotic arm of robot 102 from its current location to a patient operation site. By continuously monitoring the patient and robotic arm positions, using tracking detector I08, the surgical system can calculate updated trajectories and visually display these trajectories on display screen 110 to inform and guide surgeons and/or technicians in the operating room using the surgical robot. In addition, in certain embodiments, the surgical robot 102 may also change its position and automatically position itself based on trajectories calculated from the real time patient and robotic arm positions captured using the tracking detector 108. For instance, the trajectory of the end-effector can be automatically adjusted in real time to account for movement of the vertebrae or other part of the patient during the surgical procedure. The disclosed technology includes a robot-based navigation system for real-time, dynamic re-registration of a patient position (e.g., position of vertebrae of a patient) during a procedure (e.g., surgical procedure, e.g., a spinal surgery). An example robotic surgical system is shown in
In certain embodiments, the robotic arm 3802 includes a position sensor 3806 for dynamically tracking a position of the end effector 3804 and/or surgical instrument during a surgical procedure. Additionally, one or more points of the surgical instrument can be dynamically tracked, for example, at a rate of at least 100 Hz, 250 Hz or greater, 500 Hz or greater, or 1000 Hz or greater (e.g., position determination per second).
In certain embodiments, the system 3800 includes a force feedback subsystem 3808. The force feedback subsystem 3808 can include sensor(s), actuator(s), controller(s), servo(s), and/or other mechanisms for delivering a haptic force to a user manipulating the end effector or a surgical instrument inserted in the instrument holder of the end effector. The force feedback subsystem 3808 can detect the resistive force caused by the surgical instrument contacting, moving against, penetrating, and/or moving within a tissue of the patient. Furthermore, the force feedback subsystem 3808 can distinguish between contacted tissue types (e.g., determining when contacted tissue meets or exceeds a threshold resistance, e.g., when the tissue is bone).
The force feedback subsystem 3808 can also detect a force delivered by the operator. For example, it can detect forces delivered by direct manipulation of the surgical instrument inserted in the surgical instrument holder of the end effector to cause movement of the surgical instrument and, therefore, the end effector. The force feedback subsystem 3808 can further distinguish between the force delivered by the operator and the resistive force caused by movement of the surgical instrument in relation to the tissue of the patient. This allows the operator to both apply forces to the system as well as feel resistance (e.g., via haptic feedback) as a surgical instrument contacts tissue in the patient. [0108] In certain embodiments, the robotic surgical system 3800 includes a display 3810 that is attached to, embedded within, or otherwise positioned in relation to the robotic arm being directly manipulated by the operator (e.g., surgeon) to allow for unimpeded visual feedback to the operator during the procedure.
When an operator uses the system, the system initially accesses (e.g., and graphically renders on the display) an initial registration of a target volume, such as a vertebra of the patient. This can be accomplished using medical images of the patient, including MRI, CT, X-rays, SPECT, ultrasound, or the like. These images can be obtained preoperatively or intraoperatively.
As the operative moves the position of the end effector, the position of the end effector is dynamically determined (e.g., by processor 3812). Specifically, in some implementations, the system dynamically determines a 3D position of one or more points of a surgical instrument.
Forces received by the surgical instrument are dynamically determined when the surgical instrument contacts, moves against, penetrates, and/or moves within the patient. The system can measure these forces and distinguish between contacted tissue types. This can be accomplished, for example, by determining when contacted tissue meets or exceeds a threshold resistance, such as when the tissue is bone). The system can further detect forces applied to the surgical instrument by the operator and distinguish between forces delivered by the operator and the resistive force caused by movement of the surgical instrument in relation to the tissue of the patient.
In certain embodiments, the system can dynamically re-register the patient position based at least in part on an updated position of the end effector determined by the position sensor. This can be used to update the 3D representation of the patient situation based at least in part on the updated position of the end effector when it is determined (e.g., via the force feedback subsystem) that the surgical instrument is in contact with a target anatomy. This can be accomplished using a surface matching algorithm keyed to the initial (or previous) registration.
For example, the system can dynamically re-register the patient position upon detected contact or proximity of the end effector, or the surgical instrument, or a portion or component of the surgical instrument or end effector, with a pre-planned fiducial, such as a mechanical marker, a marker fixed to the patient. Alternatively, the system can dynamically re-register the patient position based upon the updated position of the end effector determined upon operator command, such as the operator pressing a button or otherwise activating a graphical or tactile user interface when a re-registered representation is desired.
A surgical instrument holder can be connected to the end effector for insertion or attachment of a surgical instrument therein/thereto. The instrument holder can be removable. In such instances, attachment of the instrument holder to the end effector is precise and predictable such that it is always connected in the same position.
The robotic arm is designed to allow direct manipulation of a surgical instrument by an operator (e.g., by a surgeon) when the surgical instrument is inserted in/attached to the surgical instrument holder of the end effector. The manipulation of the instrument can be subject to haptic constraints based on the position of the end effector (and/or the surgical instrument) in relation to the patient. The surgical instrument has a known geometry and position in relation to the surgical instrument holder such that the location of the instrument (e.g., the tip of the instrument) is known by the robotic surgical system. For example, when a surgical instrument is fully inserted into the instrument holder, the position of the instrument is known to the robotic surgical system because the position of the end effector is known as well as information about the surgical instrument and the instrument holder.
In certain embodiments, a tool center point (TCP) facilitates precise positioning and trajectory planning for surgical instrument guides and surgical instruments inserted through or attached to the surgical instrument holder. Surgical instruments can be engineered such that when inserted into the surgical instrument holder, there is a defined tool center point with known coordinates relative to robotic arm. The origin of a coordinate system used to define the tool center point may be located at a flange of a robotic arm. It may additionally be located at any convenient to define point such as an interface, joint, or terminal aspect of a component of a robotic surgical system.
In certain embodiments, because the TCP is in a constant position relative to the robotic arm, regardless of whether a surgical guide or surgical instrument is being used with the surgical instrument holder, a surgeon can be provided visualization of the orientation, trajectory, and position of an instrument or instrument guide used with the surgical instrument holder. The use of engineered surgical instrument systems eliminates the need for navigation markers to be attached to the end of surgical guides or tools in order to precisely determine the position, orientation, and trajectory of a surgical instrument guide relative to a patient's anatomy.
Additionally, a navigation marker attached to surgical instrument holder can be used to track the position and orientation of the universal surgical instrument guide to update the position, orientation, and current trajectory based on manipulation of robotic arm by a surgeon. Additional information provided by patient imaging (e.g., CT data, radio imaging data, or similar) taken pre- or intra-operatively as well as navigation markers attached to a patient's body may be combined with data from a navigation marker attached to a universal surgical instrument guide and displayed on a screen viewable by the surgeon such that the surgeon can see the location of necessary features of the patient's anatomy and the position, trajectory, and orientation of a surgical instrument or surgical instrument guide relative to said anatomy.
As shown in
Additionally, in some implementations the force sensor is integrated directly in the surgical instrument. For example, the force sensor may be integrated directly in the surgical drill bit as illustrated in
In the example configuration shown in
An electric or pneumatic motor 608 rotates the drill bit 602 shaft. In some implementations, a sensor 612 (e.g., an encoder) measures position of the shaft. The sensor 612 measures the position of the shaft in order to correlate forces measured by the force sensor to the relative position of the shaft. For example, if the force sensor is located in a drill bit, the measurement of the direction of the force will vary as the drill bit rotates. Specifically, the force sensor measures force and the direction of the force periodically (e.g., every millisecond, every microsecond, or somewhere therebetween). The drill bit rotates as the surgeon pushes it into bone. When the drill contacts the bone, the force sensor will indicate some force (F1) in a direction (D1). One period later (e.g., one millisecond), the drill bit will rotate slightly so the force sensor will indicate force of the same value (F1) (assuming a constant force is applied) in a different direction (D2). The direction of the force will continue to change relative to a single perspective as the drill bit rotates even if surgeon pushes into the bone with a constant force. A constantly changing force direction is not acceptable. In order to correlate the directions (e.g., D1, D2) with the global direction of the force (D) coming from the bone (seen by the surgeon, robotic system etc.) the position of the drill in the global space must be calculated as the drill bit rotates. The sensor 612 is used to measure the position of the shaft and thus determine the global direction of the force (D). The sensor 612 may be located on the back of the motor 608 as shown in
The force sensor 604 in this example may be a miniaturized industrial sensor (e.g., the multi-axis force/torque sensor from ATI Industrial Automation, Inc. of Apex, N.C.) that measures, for example, all six components of force and torque using a transducer. Alternatively, the force sensor 604 may be an optical sensor. Alternatively, the force sensor 604 may comprise a strain gauge 706 integrated directly into the shaft of the drill bit 602 as shown in
As shown in
A goal of the robot-based navigation is to assist a surgeon during a surgical procedure that results in a change to patient's target anatomy. The implants and surgical instruments are used for this purpose and the robotic system assists the surgeon to improve the accuracy with which these instruments are used during the surgical procedure.
The interaction of a surgeon and components of a surgical system is further outlined in
The process of determining target anatomy position takes as an input target anatomy. The target anatomy may be modeled using medical images, wherein medical images are taken using a medical imaging technique or scanning-based technique. As a result, determining the target anatomy position provides the exact anatomy position of the target anatomy at any moment in time. The process of rendering feedback provides information to the surgeon based on medical images, anatomy position and instrument(s) position. The rendering is visually displayed to the surgeon. The tracking instruments process takes surgical instruments and as a result calculates their position. At the same time the instrument is guided which means that their spatial position is constrained in some way by the robotic system (i.e., using an operational volume). The robotic system implements all these four processes and the surgeon participates in the two of them: guidance and rendering feedback.
Different options for the imaging process are shown in
There are other ways of obtaining information about the target anatomy. For example, information about the target anatomy can be collected by surface scanning using a haptic device and force feedback. Using such a device mounted on the robot allows user to measure forces that can provide spatial information about surface and rigidity of tissues.
Alternatively known techniques of surface scanning, such as a laser scanner, can be used. Additionally, visual, direct exploration can be used to explore the patient's anatomy. The outcome of these techniques, if used, is stored as medical image data, which is used to model the patient's anatomy.
The initial registration data can be used along with a stability module to manage the location of the end-effector relative to the target anatomy. The stability module can run all the time in the background (e.g., automatically), in certain embodiments, without surgeon taking any special actions.
Examples of such a stability module, includes surface matching methods which take a set of points (e.g. measured points) and finds the best match between the set of points and another set of points (e.g., from the surface of the vertebra on medical images). Example algorithm for surface matching is Iterative Closet Point method described in Section 4.5.3 of “A Robotic System for Cervical Spine Surgery”, Szymon Kostrzewski, Warsaw University of Technology (2011).
In certain embodiments, other algorithms are used for a stability module. Re-registration can be accomplished using other methods as well. For example, in certain embodiments, re-registration can be accomplished by periodically re-validating using fiducials. In certain embodiments, when necessary, the surgeon can touch pre-placed fiducials and re-register with an instrument attached to a robotic arm.
In certain embodiments, a specially designed marker can be fixed to the patient as shown in
Various ways of rendering feedback are shown in
A robotic surgical system with instrument attached can be used to contact a patient's anatomy at a plurality of contact points determined using haptic feedback from a force sensor attached directly or indirectly to the robotic an of the robotic surgical system. The coordinates of the plurality of contacts define a set of spatial coordinates. The value of a spatial coordinate is determined by storing the position of a portion of the robotic surgical system (e.g., a terminal point of an instrument or surgical instrument or the robotic arm) in the robot's coordinate system when contact is determined.
A set of spatial coordinates recorded from contact of the instrument with the patient's anatomy can be used to perform many navigational and surgical guidance functions such as registration, modeling volume removal, re-registration, defining operational volumes, revising operational volumes after re-registration, converting stored volume models to physical locations, and displaying surgical instruments relative to a patient's anatomy on navigation screens. A processor that is either a part of the robotic surgical system or part of a remote computing device (e.g., on a server) can be used to correlate the coordinates of surgical instruments, instruments, and/or a patient's anatomy by generating and using appropriate coordinate mappings in combination with sets of spatial coordinates. In some embodiments, a set of spatial coordinates may be provided for further use, wherein the set of spatial coordinates are generated using a technique other than haptic-feedback-based contacting of the patient's anatomy with an instrument attached to a robotic arm. For example, the set of spatial coordinates may be provided as a result of a known registration technique.
A patient's anatomy can be registered with a robotic surgical system without the use of a separate navigation system by contacting an instrument to the patient's anatomy to generate a set of spatial coordinates that can be correlated with a model of the patient generated using medical imaging data. In certain embodiments, a surgeon uses a surgical instrument to contact the patient, including during registration. In some embodiments, one or more navigation markers are used for reference during registration. Once the processor has determined a set of spatial coordinates, wherein each spatial coordinate corresponds to a point on the surface of an anatomical volume (e.g., a patient's vertebrae), the set of spatial coordinates can be mapped with a model of the patient's anatomy. The patient's anatomy may be modeled using medical imaging data. In certain embodiments, CT, MRI, or x-ray data is used to pre-operatively generate a 3D model of the patient's anatomy. In some embodiments, medical images used to generate patient anatomy models are taken intra-operatively.
A set of spatial coordinates is mapped to a model of a patient's anatomy by determining a function for converting points in the model to coordinates in the robot coordinate system (i.e., physical reality) and vice versa. In certain embodiments, mappings are made using surface matching of a surface defined by a set of spatial coordinates and the surface of the anatomical model. Points on the surface of the patient's anatomy or the anatomical model of the patient's anatomy may be extrapolated from known points (i.e., points measured by contacting the patient's anatomy with an instrwnent or data points collected during medical imaging). The extrapolated points may be used to generate the mapping. An example of a surface matching method is Iterative Closest Point (ICP) described in Section 4.5.3 of “A Robotic System for Cervical Spine Surgery,” Szymon Kostrzewski, Warsaw University of Technology (2011). The contents of Section 4.5.3 are hereby incorporated by reference herein in their entirety. In general, any algorithm or method that generates a function that can be used to transform points from one coordinate system to another (i.e., bilinear transform) is appropriate for use. A threshold may be specified that defines an error measure that the mapping must stay under in order to be used. This threshold can be set to a value that is sufficient for high precision mapping (e.g., registration), but such that mappings can be generated with high frequency (i.e., the speed of the generation of the mapping does not rate limit a surgical procedure).
Prior to registration, there is no defined relationship between the coordinate system that defines the anatomical model of the patient in the medical imaging data and the coordinate system that defines the location of a surgical instrument attached to the robotic arm of the robotic surgical system. By generating a coordinate mapping from the robot coordinate system to the medical image data coordinate system and storing the coordinate mapping, a processor can determine a physical location for each point of the patient's anatomy represented in the anatomical model. In this way, the patient is registered with the robotic surgical system.
Once a patient is registered, for each point in space, the robotic surgical system knows whether that point is on the surface of the patient's anatomy, in the patient's anatomy, or outside of the patient's anatomy. This information can be used for further processing to assist in surgical guidance and navigation. For example, this information can be used to define “no go” zones for a surgical instrument if the patient's anatomy is to be avoided entirely or only a portion of the patient's anatomy is to be accessible to the surgical instrument. Additionally, a surgical instrument could trace a line, plane, or curve that falls on the surface of the patient's anatomy.
In order to accurately register a patient using haptic-feedback-based contacting, as described above, only a small set of points need to be contacted. For example, in certain embodiments, no more than 30 points are needed to register a patient's anatomy to a robotic surgical system with sufficient precision to proceed with surgery. In certain embodiments, only 5-10 contacts are needed. The number of contacts necessary varies with the particular surgical procedure being performed. In general, surgeries requiring more precise surgical instrument positioning require more contacts to be made in order to generate a larger set of spatial coordinates. Given the simplicity of using a robotic surgical system to contact the patient's anatomy, a sufficient number of contacts for registration may be made in a short period of time, thus expediting the overall surgical procedure.
In certain embodiments, the coordinate mapping is used to generate navigational renderings on a display, for example, where a terminal point of a surgical instrument is shown in correct relation to the patient's anatomy. This rendering can be live updated as the position of the surgical tool shifts. This is done without the need for navigational markers because the location of the surgical tool is known from registration. In certain embodiments, the set of spatial coordinates is collected by contacting a fiducial marker with a plurality of orienting points (e.g., indents) on the marker (e.g., distributed on faces of the marker}, wherein the orienting points are in a known location relative to the patient's anatomy due to the marker being engineered to attach in a specific location on the patient's anatomy (see
In some embodiments of methods and systems described herein, registration is performed using a technique known in the art.
During certain surgical procedures, a portion of a patient's anatomy (i.e., a first volume) originally included in a model of the patient's anatomy is removed during an operation prior to the removal of an additional volume, for example, to gain access to the additional volume. The removal of the first volume may not require high precision during removal. The removal of the first volume may be done manually. The model of the patient's anatomy can be updated to reflect this removal. The model update may be necessary to maintain accurate patient records (i.e., medical history). The model update may be necessary for intra-operative planning of additional volume removal.
A set of spatial coordinates can be used to update the model of a patient's anatomy after volume removal. In certain embodiments, the set of spatial coordinates are generated using haptic-feedback-hazed contacting of the patient's anatomy with an instrument attached to a robotic arm.
Using a set of spatial coordinates and a model of the patient's anatomy, points on the patient's anatomy that were formerly inside the surface of the anatomy can be determined, if a coordinate mapping between the model's coordinate system and the coordinate system of the spatial coordinates (i.e., a robot's coordinate system) has been generated. The coordinate mapping may be generated, for example, during registration. The set of spatial coordinates can be converted to be expressed in the coordinate system of the model using the coordinate mapping. Then, coordinates determined to be located on the interior of the model's surface can be used to define a new surface for the model. For example, if half of a rectangular solid is removed, an instrument attached to a robotic surgical system can contact points that were previously on the inside of the rectangular solid, thus, the coordinates of the points when converted to the model's coordinate system will be located inside the model. These points can be used to determine a new surface for the model. Thus, the volume of the model will shrink by excluding all points in the removed volume from the model. The updated model will have a smaller volume than the original model that accurately reflects the change in size that occurred due to volume removal. A coordinate may be included in a set of coordinates that is not determined to be an internal coordinate in the model (i.e., the model before updating). This coordinate would not be used to define a new surface as it would be part of an existing surface. This coordinate is thus not used to update the model.
The revised set of coordinates that define the new surface of the patient's anatomy after volume removal can be stored as an updated model for future reference. This updated model may be stored in addition to or overwrite the original model. When patient data is augmented to comprise both the original model before volume removal and the updated model after volume removal, a comparison can be displayed. This comparison includes displaying the original model, the updated model, and the portion that was removed. An exemplary original model is shown in
Because typical registration procedures are lengthy and require unobstructed line-of-sight (either visually or electromagnetically unobstructed line-of-sight), a navigation system and/or robotic surgical system are typically only registered once during a surgical procedure, at the beginning. However, a patient's orientation and/or position relative to these systems may shift during the procedure. Additionally, depending on the type of procedure, the patient's anatomy may undergo physical changes that should be reflected in the registration. Serious medical error can result during a surgical procedure due to any desynchronization that occurs between physical reality and the initial registration. In general, more complex procedures involving many steps are more prone to desynchronization and with greater magnitude. Serious medical error is more likely in surgical procedures on or near sensitive anatomical features (e.g., nerves or arteries) due to desynchronization. Thus, easy and fast re-registration that may be performed intra-operatively is of great benefit.
Re-registration acts to reset any desynchronization that may have happened and, unlike traditional registration methods, haptic-feedback-based contacting with robotic surgical systems are easy to integrate methods for re-registration. In certain embodiments, a re-registration can be processed in 1-2 seconds after re-registration contacts are made. In certain embodiments, re-registration can be processed in under 5 seconds. Re-registration may be performed with such a system or using such a method by contacting the patient's anatomy at any plurality of points. There is no need to contact the patient's anatomy at specific points, for example, the points contacted during initial registration.
After an initial registration is performed that defines a coordinate map between a robot's coordinate system and the coordinate system of a model of the patient's anatomy, re-registration may be performed. Each coordinate of the patient's anatomy is known to the robotic surgical system after registration by expressing coordinates of the patient's anatomical model in the robot's coordinate system using a coordinate mapping. By collecting a set of spatial coordinates, the surface of the patient's anatomy expressed in the robot's coordinate system can be mapped to the surface defamed by the set of spatial coordinates. The mapping can be used to update the coordinate mapping.
An updated coordinate mapping may reflect changes in the patient's anatomy, orientation, or position. For example, if a patient is rotated about an axis, the patient's physical anatomy will be tilted relative to what the patient's anatomical model reflects when expressed in a robot's coordinate system. An instrument can contact the patient's anatomy after the rotation at a set of points on the patient's anatomy (for example, 5-10 points). A re-registration map between the current patient's anatomical model expressed in the robot's coordinate system and the surface defamed by the set of points is generated. The coordinate map can be modified using the registration map to produce an updated coordinate map. For example, if both the coordinate map and re-registration map are linear transforms stored as arrays, the updated coordinate map is the product of the two arrays. Likewise, a change in position will be reflected as a translation during re-registration and a change in the patient's anatomy may be reflected as a scaling transform. For example, the spacing of a patient's vertebrae may change after volume removal, prompting a surgeon to perform re-registration.
In certain embodiments, the model of the patient's anatomy is updated simultaneously during re-registration if one or more of the set of spatial coordinates is determined to be an interior coordinate of the model (i.e., the model as it existed pre-re-registration). For example, in certain embodiments, re-registration may be performed after a volume removal whereby re-registration and model updating are processed in one simultaneous method. Re-registration is useful after volume removal because given the likelihood of anatomical shifting during such a significant surgical step is high.
In certain surgical procedures, the use of a surgical instrument should be constrained to only a specific operational volume corresponding to the surgical site of the patient's anatomy. Operational volumes are physical volumes, wherein the physical volume is defined using the robot's coordinate system. It is clear that the physical volume in which the surgical instrument should be constrained is relative to the patient's anatomy. In certain embodiments, a robotic surgical system provides haptic feedback when a surgeon attempts to move the surgical instrument outside of the operational volume. In this way, the surgeon feels resistance when the surgical instrument is at the boundary of the operational volume and can redirect the surgical tool away from the boundary. This is useful, for example, during bone removal, where a surgeon does not want to remove bone from locations outside of the intended volume. Operational volumes are stored on a non-transitory computer readable medium for use in providing haptic feedback to surgeons during surgical procedures.
Using a coordinate mapping, a physical operational volume occupied by a volume of and/or around a patient's anatomy can be precisely defined using the patient's anatomical model. The intended operational volume can be defined intra-operatively. A surgeon can contact a set of points on the patient's anatomy to generate a set of spatial coordinates that define a boundary of the operational volume. In many surgical procedures, the operational volume corresponds to an anatomical feature of the patient's anatomy. For example, a particular bone or segment of a bone. Thus, in certain embodiments, the surgeon selects the anatomical feature from a model of the patient's anatomy. The model of the patient's anatomical feature can be mapped to the set of spatial coordinates corresponding to the surgeon's desired operational volume boundary. In certain embodiments, each coordinate in the model of the patient's anatomical feature can expressed using the robot's coordinate system based on the mapping.
Then, the operational volume can be defined and expressed in the robot's coordinate system using the mapping of the model of the patient's anatomical feature to the set of spatial coordinates. In some embodiments, each coordinate of the surface of the model of the patient's anatomical feature is used to define the surface of the operational volume.
In certain embodiments, the operational volume is the volume defined by the surface defined by the set of spatial coordinates. Thus, these methods for producing operational volumes do not require medical imaging data or a pre-constructed model of the patient's anatomy. For example, a surgeon may contact 10 points on a patient that are determined as a set of spatial coordinates. The set of spatial coordinates can be used as a set of vertices (i.e., surface points) that define a volume. This may be used as an operational volume wherein movement of a surgical instrument attached to the robotic arm of the robotic surgical system is constrained to that operational volume. This can be done with or without any registration.
An operational volume may be defined by a surgeon selecting a volume of a patient's anatomical model without generating a set of spatial coordinates (i.e., without contacting the patient's anatomy). The surgeon may select the volume using software that allows viewing of the patient's anatomical model. Once the volume is selected, a coordinate mapping that maps the anatomical model to the robot's coordinate system may be used to generate a set of coordinates that define the operational volume. Thus, the operational volume is defined using a coordinate mapping generated during, for example, registration or re-registration, and does not require a surgeon to separately generate a set of spatial coordinates for use in defining the operational volume by contacting the patient's anatomy.
Stored operational volumes may be updated when a coordinate mapping is updated or at some later time using the updated coordinate mapping. The coordinate mapping is updated during re-registration, for example, to reflect a shift in the position, orientation, or change in the patient's anatomy. The coordinates of the stored operational volume may be converted to the new robot coordinate system by mapping the new robot coordinate system to the robot coordinate system the stored operational volume is expressed in and using the mapping (i.e., by converting each coordinate of the operational volume to the new coordinate system and storing the converted coordinates as the updated operational volume).
Similarly, any stored model volume that is expressed in a medical image data coordinate system can be converted to a spatial volume by expressing the coordinates of the model volume in the robot's coordinate system using a coordinate mapping. This allows a robotic surgical system to trace, enter, maneuver only within or maneuver only outside a physical volume corresponding to the model volume.
A surgeon benefits from visualizing the position of a surgical instrument relative to a patient's anatomy to assist in navigation and decision making during a surgical procedure. When the terminal point of a surgical instrument has a pre-defined position relative to the origin of a robot's coordinate system, the terminal point can be converted to a position in a medical image data coordinate system with a coordinate mapping between the robot's coordinate system and the medical image data coordinate system using the position of the robotic arm. In certain embodiments, the terminal point is used to represent the position of the robotic arm. In certain embodiments, all surgical instruments have the same terminal point when attached to a robotic arm. After converting the terminal point to be expressed in a medical image data coordinate system, the terminal point can be plotted relative to a model of the patient's anatomy that precisely reflects the distance between the terminal point and the patient's anatomy in physical space. Using this, rendering data can be generated that, when displayed, shows a representation of the terminal point (and, optionally, the surgical instrument) and the model of the patient's anatomy. Thus, visualization of the surgical instrument and its position relative to the patient's anatomy can be made without the use of a navigational marker attached to the surgical instrument and without using image recognition techniques.
The rendering data may be displayed on a screen that is part of the robotic surgical system or that is viewable from inside and/or outside an operating room. The screen may be mounted on the robotic arm. The rendering data may be updated to refresh the display in real-time or substantially real-time (i.e., acting as a video feed of the patient). The representation of the terminal point and/or surgical instrument may be overlaid over a representation of the model of the patient's anatomy or over medical images taken pre- or intra-operatively. The position of the terminal point on a display will update as the position of the robotic arm is adjusted.
The following is a description of an exemplary surgical method for performing a laminectomy, but it is understood that the method can easily be adapted to other types of volume removal surgery. Additionally, many of the steps discussed in this exemplary method are applicable to surgical procedures that do not involve volume removal or involve surgical outcomes other than volume removal. Aspects of the surgical method are shown in
It is understood that surgical methods described herein are exemplary. Many surgical procedures require well-defined spatial relationships between a patient's anatomy and surgical instruments as well as operative volumes that constrain the movement of the surgical instruments. Other orthopedic and non-orthopedic methods are easily adapted to integrate the methods described herein. Other surgeries contemplated for use with robotic-based navigation systems and methods include, but are not limited to, orthopedic procedures, ENT procedures, and neurosurgical procedures. It is readily understood by one of ordinary skill in the art that such procedures may be performed using an open, percutaneous, or minimally invasive surgical (MIS) approach. It is also understood that any of the methods for determining coordinates and/or volumes using relevant coordinate systems described herein above can be used in any surgical method described herein.
The cloud computing environment 3600 may include a resource manager 3606. The resource manager 3606 may be connected to the resource providers 3602 and the computing devices 3604 over the computer network 3608. In some implementations, the resource manager 3606 may facilitate the provision of computing resources by one or more resource providers 3602 to one or more computing devices 3604. The resource manager 3606 may receive a request for a computing resource from a particular computing device 3604. The resource manager 3606 may identify one or more resource providers 3602 capable of providing the computing resource requested by the computing device 3604. The resource manager 3606 may select a resource provider 3602 to provide the computing resource. The resource manager 3606 may facilitate a connection between the resource provider 3602 and a particular computing device 3604. In some implementations, the resource manager 3606 may establish a connection between a particular resource provider 3602 and a particular computing device 3604. In some implementations, the resource manager 3606 may redirect a particular computing device 3604 to a particular resource provider 3602 with the requested computing resource.
The computing device 3700 includes a processor 3702, a memory 3704, a storage device 3706, a high-speed interface 3708 connecting to the memory 3704 and multiple high-speed expansion ports 3710, and a low-speed interface 3712 connecting to a low-speed expansion port 3714 and the storage device 3706. Each of the processor 3702, the memory 3704, the storage device 3706, the high-speed interface 3708, the high-speed expansion ports 3710, and the low-speed interface 3712, are interconnected using various busses, and may be mounted on a common motherboard or in other manners as appropriate. The processor 3702 can process instructions for execution within the computing device 3700, including instructions stored in the memory 3704 or on the storage device 3706 to display graphical information for a GUI on an external input/output device, such as a display 3716 coupled to the high-speed interface 3708. In other implementations, multiple processors and/or multiple buses may be used, as appropriate, along with multiple memories and types of memory. Also, multiple computing devices may be connected, with each device providing portions of the necessary operations (e.g., as a server bank, a group of blade servers, or a multi-processor system).
The memory 3704 stores information within the computing device 3700. In some implementations, the memory 3704 is a volatile memory unit or units. In some implementations, the memory 3704 is a non-volatile memory unit or units. The memory 3704 may also be another form of computer-readable medium, such as a magnetic or optical disk.
The storage device 3706 is capable of providing mass storage for the computing device 3700. In some implementations, the storage device 3706 may be or contain a computer-readable medium, such as a floppy disk device, a hard disk device, an optical disk device, or a tape device, a flash memory or other similar solid state memory device, or an array of devices, including devices in a storage area network or other configurations. Instructions can be stored in an information carrier. The instructions, when executed by one or more processing devices (for example, processor 3702), perform one or more methods, such as those described above. The instructions can also be stored by one or more storage devices such as computer- or machine-readable mediums (for example, the memory 3704, the storage device 3706, or memory on the processor 3702).
The high-speed interface 3708 manages bandwidth-intensive operations for the computing device 3700, while the low-speed interface 3712 manages lower bandwidth-intensive operations. Such allocation of functions is an example only. In some implementations, the high-speed interface 3708 is coupled to the memory 3704, the display 3716 (e.g., through a graphics processor or accelerator), and to the high-speed expansion ports 3710, which may accept various expansion cards (not shown). In the implementation, the low-speed interface 3712 is coupled to the storage device 3706 and the low-speed expansion port 3714. The low-speed expansion port 3714, which may include various communication ports (e.g., USB, Bluetooth®, Ethernet, wireless Ethernet) may be coupled to one or more input/output devices, such as a keyboard, a pointing device, a scanner, or a networking device such as a switch or router, e.g., through a network adapter.
The computing device 3700 may be implemented in a number of different forms, as shown in the figure. For example, it may be implemented as a standard server 3720, or multiple times in a group of such servers. In addition, it may be implemented in a personal computer such as a laptop computer 3722. It may also be implemented as part of a rack server system 3724. Alternatively, components from the computing device 3700 may be combined with other components in a mobile device (not shown), such as a mobile computing device 3750. Each of such devices may contain one or more of the computing device 3700 and the mobile computing device 3750, and an entire system may be made up of multiple computing devices communicating with each other.
The mobile computing device 3750 includes a processor 3752, a memory 3764, an input/output device such as a display 3754, a communication interface 3766, and a transceiver 3768, among other components. The mobile computing device 3750 may also be provided with a storage device, such as a micro-drive or other device, to provide additional storage. Each of the processor 3752, the memory 3764, the display 3754, the communication interface 3766, and the transceiver 3768, are interconnected using various buses, and several of the components may be mounted on a common motherboard or in other manners as appropriate.
The processor 3752 can execute instructions within the mobile computing device 3750, including instructions stored in the memory 3764. The processor 3752 may be implemented as a chipset of chips that include separate and multiple analog and digital processors. The processor 3752 may provide, for example, for coordination of the other components of the mobile computing device 3750, such as control of user interfaces, applications run by the mobile computing device 3750, and wireless communication by the mobile computing device 3750.
The processor 3752 may communicate with a user through a control interface 3758 and a display interface 3756 coupled to the display 3754. The display 3754 may be, for example, a TFT (Thin-Film-Transistor Liquid Crystal Display) display or an OLED (Organic Light Emitting Diode) display, or other appropriate display technology. The display interface 3756 may comprise appropriate circuitry for driving the display 3754 to present graphical and other information to a user. The control interface 3758 may receive commands from a user and convert them for submission to the processor 3752. In addition, an external interface 3762 may provide communication with the processor 3752, so as to enable near area communication of the mobile computing device 3750 with other devices. The external interface 3762 may provide, for example, for wired communication in some implementations, or for wireless communication in other implementations, and multiple interfaces may also be used.
The memory 3764 stores information within the mobile computing device 3750. The memory 3764 can be implemented as one or more of a computer-readable medium or media, a volatile memory unit or units, or a non-volatile memory unit or units. An expansion memory 3774 may also be provided and connected to the mobile computing device 3750 through an expansion interface 3772, which may include, for example, a SIMM (Single in Line Memory Module) card interface. The expansion memory 3774 may provide extra storage space for the mobile computing device 3750, or may also store applications or other information for the mobile computing device 3750. Specifically, the expansion memory 3774 may include instructions to carry out or supplement the processes described above, and may include secure information also. Thus, for example, the expansion memory 3774 may be provided as a security module for the mobile computing device 3750, and may be programmed with instructions that permit secure use of the mobile computing device 3750. In addition, secure applications may be provided via the SIMM cards, along with additional information, such as placing identifying information on the SIMM card in a non-hackable manner.
The memory may include, for example, flash memory and/or NVRAM memory (non-volatile random access memory), as discussed below. In some implementations, instructions are stored in an information carrier and, when executed by one or more processing devices (for example, processor 3752), perform one or more methods, such as those described above. The instructions can also be stored by one or more storage devices, such as one or more computer- or machine-readable mediums (for example, the memory 3764, the expansion memory 3774, or memory on the processor 3752). In some implementations, the instructions can be received in a propagated signal, for example, over the transceiver 3768 or the external interface 3762.
The mobile computing device 3750 may communicate wirelessly through the communication interface 3766, which may include digital signal processing circuitry where necessary. The communication interface 3766 may provide for communications under various modes or protocols, such as GSM voice calls (Global System for Mobile communications), SMS (Short Message Service), EMS (Enhanced Messaging Service), or MIMS messaging (Multimedia Messaging Service), CDMA (code division multiple access), TOMA (time division multiple access), PDC (Personal Digital Cellular), WCDMA (Wideband Code Division Multiple Access), CDMA2000, or GPRS (General Packet Radio Service), among others. Such communication may occur, for example, through the transceiver 3768 using a radio-frequency. In addition, short-range communication may occur, such as using a Bluetooth®, Wi-Fi™, or other such transceiver (not shown). In addition, a GPS (Global Positioning System) receiver module 3770 may provide additional navigation- and location-related wireless data to the mobile computing device 3750, which may be used as appropriate by applications running on the mobile computing device 3750.
The mobile computing device 3750 may also communicate audibly using an audio codec 3760, which may receive spoken information from a user and convert it to usable digital information. The audio codec 3760 may likewise generate audible sound for a user, such as through a speaker, e.g., in a handset of the mobile computing device 3750. Such sound may include sound from voice telephone calls, may include recorded sound (e.g., voice messages, music files, etc.) and may also include sound generated by applications operating on the mobile computing device 3750.
The mobile computing device 3750 may be implemented in a number of different forms, as shown in the figure. For example, it may be implemented as a cellular telephone 3780. It may also be implemented as part of a smart-phone 3782, personal digital assistant, or other similar mobile device.
Various implementations of the systems and techniques described here can be realized in digital electronic circuitry, integrated circuitry, specially designed ASICs (application specific integrated circuits), computer hardware, firmware, software, and/or combinations thereof. These various implementations can include implementation in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, coupled to receive data and instructions from, and to transmit data and instructions to, a storage system, at least one input device, and at least one output device.
These computer programs (also known as programs, software, software applications or code) include machine instructions for a programmable processor, and can be implemented in a high-level procedural and/or object-oriented programming language, and/or in assembly/machine language. As used herein, the terms machine-readable medium and computer-readable medium refer to any computer program product, apparatus and/or device (e.g., magnetic discs, optical disks, memory, Programmable Logic Devices (PLDs)) used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term machine-readable signal refers to any signal used to provide machine instructions and/or data to a programmable processor.
To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user and a keyboard and a pointing device (e.g., a mouse or a trackball) by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form, including acoustic, speech or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a back end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front end component (e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back end, middleware, or front end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network (LAN), a wide area network (WAN), and the Internet.
The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
Certain embodiments of the present invention were described above. It is, however, expressly noted that the present invention is not limited to those embodiments, but rather the intention is that additions and modifications to what was expressly described herein are also included within the scope of the invention. Moreover, it is to be understood that the features of the various embodiments described herein were not mutually exclusive and can exist in various combinations and permutations, even if such combinations or permutations were not made express herein, without departing from the spirit and scope of the invention. In fact, variations, modifications, and other implementations of what was described herein will occur to those of ordinary skill in the art without departing from the spirit and the scope of the invention. As such, the invention is not to be defined only by the preceding illustrative description.
Having described certain implementations of methods and apparatus for robotic navigation of robotic surgical systems, it will now become apparent to one of skill in the art that other implementations incorporating the concepts of the disclosure may be used. Therefore, the disclosure should not be limited to certain implementations, but rather should be limited only by the spirit and scope of the following claims.
This application is a non-provisional application, which is a continuation of U.S. patent application Ser. No. 15/874,695 filed on Jan. 18, 2018, which claims priority to provisional application Ser. No. 62/447,884 filed on Jan. 17, 2017, which is incorporated in its entirety herein.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4150293 | Franke | Apr 1979 | A |
| 5246010 | Gazzara et al. | Sep 1993 | A |
| 5354314 | Hardy et al. | Oct 1994 | A |
| 5397323 | Taylor et al. | Mar 1995 | A |
| 5598453 | Baba et al. | Jan 1997 | A |
| 5772594 | Barrick | Jun 1998 | A |
| 5791908 | Gillio | Aug 1998 | A |
| 5820559 | Ng et al. | Oct 1998 | A |
| 5825982 | Wright et al. | Oct 1998 | A |
| 5887121 | Funda et al. | Mar 1999 | A |
| 5911449 | Daniele et al. | Jun 1999 | A |
| 5951475 | Gueziec et al. | Sep 1999 | A |
| 5987960 | Messner et al. | Nov 1999 | A |
| 6012216 | Esteves et al. | Jan 2000 | A |
| 6031888 | Ivan et al. | Feb 2000 | A |
| 6033415 | Mittelstadt et al. | Mar 2000 | A |
| 6080181 | Jensen et al. | Jun 2000 | A |
| 6106511 | Jensen | Aug 2000 | A |
| 6122541 | Cosman et al. | Sep 2000 | A |
| 6144875 | Schweikard et al. | Nov 2000 | A |
| 6157853 | Blume et al. | Dec 2000 | A |
| 6167145 | Foley et al. | Dec 2000 | A |
| 6167292 | Badano et al. | Dec 2000 | A |
| 6201984 | Funda et al. | Mar 2001 | B1 |
| 6203196 | Meyer et al. | Mar 2001 | B1 |
| 6205411 | DiGioia, III et al. | Mar 2001 | B1 |
| 6212419 | Blume et al. | Apr 2001 | B1 |
| 6231565 | Tovey et al. | May 2001 | B1 |
| 6236875 | Bucholz et al. | May 2001 | B1 |
| 6246900 | Cosman et al. | Jun 2001 | B1 |
| 6301495 | Gueziec et al. | Oct 2001 | B1 |
| 6306126 | Montezuma | Oct 2001 | B1 |
| 6312435 | Wallace et al. | Nov 2001 | B1 |
| 6314311 | Williams et al. | Nov 2001 | B1 |
| 6320929 | Von Der Haar | Nov 2001 | B1 |
| 6322567 | Mittelstadt et al. | Nov 2001 | B1 |
| 6325808 | Bernard et al. | Dec 2001 | B1 |
| 6340363 | Bolger et al. | Jan 2002 | B1 |
| 6377011 | Ben-Ur | Apr 2002 | B1 |
| 6379302 | Kessman et al. | Apr 2002 | B1 |
| 6402762 | Hunter et al. | Jun 2002 | B2 |
| 6424885 | Niemeyer et al. | Jul 2002 | B1 |
| 6447503 | Wynne et al. | Sep 2002 | B1 |
| 6451027 | Cooper et al. | Sep 2002 | B1 |
| 6477400 | Barrick | Nov 2002 | B1 |
| 6484049 | Seeley et al. | Nov 2002 | B1 |
| 6487267 | Wolter | Nov 2002 | B1 |
| 6490467 | Bucholz et al. | Dec 2002 | B1 |
| 6490475 | Seeley et al. | Dec 2002 | B1 |
| 6499488 | Hunter et al. | Dec 2002 | B1 |
| 6501981 | Schweikard et al. | Dec 2002 | B1 |
| 6507751 | Blume et al. | Jan 2003 | B2 |
| 6535756 | Simon et al. | Mar 2003 | B1 |
| 6560354 | Maurer, Jr. et al. | May 2003 | B1 |
| 6565554 | Niemeyer | May 2003 | B1 |
| 6587750 | Gerbi et al. | Jul 2003 | B2 |
| 6614453 | Suri et al. | Sep 2003 | B1 |
| 6614871 | Kobiki et al. | Sep 2003 | B1 |
| 6619840 | Rasche et al. | Sep 2003 | B2 |
| 6636757 | Jascob et al. | Oct 2003 | B1 |
| 6645196 | Nixon et al. | Nov 2003 | B1 |
| 6666579 | Jensen | Dec 2003 | B2 |
| 6669635 | Kessman et al. | Dec 2003 | B2 |
| 6701173 | Nowinski et al. | Mar 2004 | B2 |
| 6757068 | Foxlin | Jun 2004 | B2 |
| 6782287 | Grzeszczuk et al. | Aug 2004 | B2 |
| 6783524 | Anderson et al. | Aug 2004 | B2 |
| 6786896 | Madhani et al. | Sep 2004 | B1 |
| 6788018 | Blumenkranz | Sep 2004 | B1 |
| 6804581 | Wang et al. | Oct 2004 | B2 |
| 6823207 | Jensen et al. | Nov 2004 | B1 |
| 6827351 | Graziani et al. | Dec 2004 | B2 |
| 6837892 | Shoham | Jan 2005 | B2 |
| 6839612 | Sanchez et al. | Jan 2005 | B2 |
| 6856826 | Seeley et al. | Feb 2005 | B2 |
| 6856827 | Seeley et al. | Feb 2005 | B2 |
| 6879880 | Nowlin et al. | Apr 2005 | B2 |
| 6892090 | Verard et al. | May 2005 | B2 |
| 6920347 | Simon et al. | Jul 2005 | B2 |
| 6922632 | Foxlin | Jul 2005 | B2 |
| 6968224 | Kessman et al. | Nov 2005 | B2 |
| 6978166 | Foley et al. | Dec 2005 | B2 |
| 6988009 | Grimm et al. | Jan 2006 | B2 |
| 6991627 | Madhani et al. | Jan 2006 | B2 |
| 6996487 | Jutras et al. | Feb 2006 | B2 |
| 6999852 | Green | Feb 2006 | B2 |
| 7007699 | Martinelli et al. | Mar 2006 | B2 |
| 7016457 | Senzig et al. | Mar 2006 | B1 |
| 7043961 | Pandey et al. | May 2006 | B2 |
| 7062006 | Pelc et al. | Jun 2006 | B1 |
| 7063705 | Young et al. | Jun 2006 | B2 |
| 7072707 | Galloway, Jr. et al. | Jul 2006 | B2 |
| 7083615 | Peterson et al. | Aug 2006 | B2 |
| 7097640 | Wang et al. | Aug 2006 | B2 |
| 7099428 | Clinthorne et al. | Aug 2006 | B2 |
| 7108421 | Gregerson et al. | Sep 2006 | B2 |
| 7130676 | Barrick | Oct 2006 | B2 |
| 7139418 | Abovitz et al. | Nov 2006 | B2 |
| 7139601 | Bucholz et al. | Nov 2006 | B2 |
| 7155316 | Sutherland et al. | Dec 2006 | B2 |
| 7164968 | Treat et al. | Jan 2007 | B2 |
| 7167738 | Schweikard et al. | Jan 2007 | B2 |
| 7169141 | Brock et al. | Jan 2007 | B2 |
| 7172627 | Fiere et al. | Feb 2007 | B2 |
| 7194120 | Wicker et al. | Mar 2007 | B2 |
| 7197107 | Arai et al. | Mar 2007 | B2 |
| 7231014 | Levy | Jun 2007 | B2 |
| 7231063 | Naimark et al. | Jun 2007 | B2 |
| 7239940 | Wang et al. | Jul 2007 | B2 |
| 7248914 | Hastings et al. | Jul 2007 | B2 |
| 7301648 | Foxlin | Nov 2007 | B2 |
| 7302288 | Schellenberg | Nov 2007 | B1 |
| 7313430 | Urquhart et al. | Dec 2007 | B2 |
| 7318805 | Schweikard et al. | Jan 2008 | B2 |
| 7318827 | Leitner et al. | Jan 2008 | B2 |
| 7319897 | Leitner et al. | Jan 2008 | B2 |
| 7324623 | Heuscher et al. | Jan 2008 | B2 |
| 7327865 | Fu et al. | Feb 2008 | B2 |
| 7331967 | Lee et al. | Feb 2008 | B2 |
| 7333642 | Green | Feb 2008 | B2 |
| 7339341 | Oleynikov et al. | Mar 2008 | B2 |
| 7366562 | Dukesherer et al. | Apr 2008 | B2 |
| 7379790 | Toth et al. | May 2008 | B2 |
| 7386365 | Nixon | Jun 2008 | B2 |
| 7422592 | Morley et al. | Sep 2008 | B2 |
| 7435216 | Kwon et al. | Oct 2008 | B2 |
| 7440793 | Chauhan et al. | Oct 2008 | B2 |
| 7460637 | Clinthorne et al. | Dec 2008 | B2 |
| 7466303 | Yi et al. | Dec 2008 | B2 |
| 7493153 | Ahmed et al. | Feb 2009 | B2 |
| 7505617 | Fu et al. | Mar 2009 | B2 |
| 7533892 | Schena et al. | May 2009 | B2 |
| 7542791 | Mire et al. | Jun 2009 | B2 |
| 7555331 | Viswanathan | Jun 2009 | B2 |
| 7567834 | Clayton et al. | Jul 2009 | B2 |
| 7594912 | Cooper et al. | Sep 2009 | B2 |
| 7606613 | Simon et al. | Oct 2009 | B2 |
| 7607440 | Coste-Maniere et al. | Oct 2009 | B2 |
| 7623902 | Pacheco | Nov 2009 | B2 |
| 7630752 | Viswanathan | Dec 2009 | B2 |
| 7630753 | Simon et al. | Dec 2009 | B2 |
| 7643862 | Schoenefeld | Jan 2010 | B2 |
| 7660623 | Hunter et al. | Feb 2010 | B2 |
| 7661881 | Gregerson et al. | Feb 2010 | B2 |
| 7683331 | Chang | Mar 2010 | B2 |
| 7683332 | Chang | Mar 2010 | B2 |
| 7689320 | Prisco et al. | Mar 2010 | B2 |
| 7691098 | Wallace et al. | Apr 2010 | B2 |
| 7702379 | Avinash et al. | Apr 2010 | B2 |
| 7702477 | Tuemmler et al. | Apr 2010 | B2 |
| 7711083 | Heigl et al. | May 2010 | B2 |
| 7711406 | Kuhn et al. | May 2010 | B2 |
| 7720523 | Omernick et al. | May 2010 | B2 |
| 7725253 | Foxlin | May 2010 | B2 |
| 7726171 | Langlotz et al. | Jun 2010 | B2 |
| 7742801 | Neubauer et al. | Jun 2010 | B2 |
| 7751865 | Jascob et al. | Jul 2010 | B2 |
| 7760849 | Zhang | Jul 2010 | B2 |
| 7762825 | Burbank et al. | Jul 2010 | B2 |
| 7763015 | Cooper et al. | Jul 2010 | B2 |
| 7787699 | Mahesh et al. | Aug 2010 | B2 |
| 7796728 | Bergfjord | Sep 2010 | B2 |
| 7813838 | Sommer | Oct 2010 | B2 |
| 7818044 | Dukesherer et al. | Oct 2010 | B2 |
| 7819859 | Prisco et al. | Oct 2010 | B2 |
| 7824401 | Manzo et al. | Nov 2010 | B2 |
| 7831294 | Viswanathan | Nov 2010 | B2 |
| 7834484 | Sartor | Nov 2010 | B2 |
| 7835557 | Kendrick et al. | Nov 2010 | B2 |
| 7835778 | Foley et al. | Nov 2010 | B2 |
| 7835784 | Mire et al. | Nov 2010 | B2 |
| 7840253 | Tremblay et al. | Nov 2010 | B2 |
| 7840256 | Lakin et al. | Nov 2010 | B2 |
| 7843158 | Prisco | Nov 2010 | B2 |
| 7844320 | Shahidi | Nov 2010 | B2 |
| 7853305 | Simon et al. | Dec 2010 | B2 |
| 7853313 | Thompson | Dec 2010 | B2 |
| 7865269 | Prisco et al. | Jan 2011 | B2 |
| D631966 | Perloff et al. | Feb 2011 | S |
| 7879045 | Gielen et al. | Feb 2011 | B2 |
| 7881767 | Strommer et al. | Feb 2011 | B2 |
| 7881770 | Melkent et al. | Feb 2011 | B2 |
| 7886743 | Cooper et al. | Feb 2011 | B2 |
| RE42194 | Foley et al. | Mar 2011 | E |
| RE42226 | Foley et al. | Mar 2011 | E |
| 7900524 | Calloway et al. | Mar 2011 | B2 |
| 7907166 | Lamprecht et al. | Mar 2011 | B2 |
| 7909122 | Schena et al. | Mar 2011 | B2 |
| 7925653 | Saptharishi | Apr 2011 | B2 |
| 7930065 | Larkin et al. | Apr 2011 | B2 |
| 7935130 | Willliams | May 2011 | B2 |
| 7940999 | Liao et al. | May 2011 | B2 |
| 7945012 | Ye et al. | May 2011 | B2 |
| 7945021 | Shapiro et al. | May 2011 | B2 |
| 7953470 | Vetter et al. | May 2011 | B2 |
| 7954397 | Choi et al. | Jun 2011 | B2 |
| 7971341 | Dukesherer et al. | Jul 2011 | B2 |
| 7974674 | Hauck et al. | Jul 2011 | B2 |
| 7974677 | Mire et al. | Jul 2011 | B2 |
| 7974681 | Wallace et al. | Jul 2011 | B2 |
| 7979157 | Anvari | Jul 2011 | B2 |
| 7983733 | Viswanathan | Jul 2011 | B2 |
| 3004121 | Sartor | Aug 2011 | A1 |
| 7988215 | Seibold | Aug 2011 | B2 |
| 7996110 | Lipow et al. | Aug 2011 | B2 |
| 8004229 | Nowlin et al. | Aug 2011 | B2 |
| 8010177 | Csavoy et al. | Aug 2011 | B2 |
| 8019045 | Kato | Sep 2011 | B2 |
| 8021310 | Sanborn et al. | Sep 2011 | B2 |
| 3046057 | Clarke | Oct 2011 | A1 |
| 8035685 | Jensen | Oct 2011 | B2 |
| 8046054 | Kim et al. | Oct 2011 | B2 |
| 8052688 | Wolf, II | Nov 2011 | B2 |
| 8054184 | Cline et al. | Nov 2011 | B2 |
| 8054752 | Druke et al. | Nov 2011 | B2 |
| 8057397 | Li et al. | Nov 2011 | B2 |
| 8057407 | Martinelli et al. | Nov 2011 | B2 |
| 8062288 | Cooper et al. | Nov 2011 | B2 |
| 8062375 | Glerum et al. | Nov 2011 | B2 |
| 8066524 | Burbank et al. | Nov 2011 | B2 |
| 8073335 | Labonville et al. | Dec 2011 | B2 |
| 8079950 | Stern et al. | Dec 2011 | B2 |
| 8086299 | Adler et al. | Dec 2011 | B2 |
| 8092370 | Roberts et al. | Jan 2012 | B2 |
| 8098914 | Liao et al. | Jan 2012 | B2 |
| 8100950 | St. Clair et al. | Jan 2012 | B2 |
| 8105320 | Manzo | Jan 2012 | B2 |
| 8108025 | Csavoy et al. | Jan 2012 | B2 |
| 8109877 | Moctezuma de la Barrera et al. | Feb 2012 | B2 |
| 8112292 | Simon | Feb 2012 | B2 |
| 8116430 | Shapiro et al. | Feb 2012 | B1 |
| 8120301 | Goldberg et al. | Feb 2012 | B2 |
| 8121249 | Wang et al. | Feb 2012 | B2 |
| 8123675 | Funda et al. | Feb 2012 | B2 |
| 8133229 | Bonutti | Mar 2012 | B1 |
| 8142420 | Schena | Mar 2012 | B2 |
| 8147494 | Leitner et al. | Apr 2012 | B2 |
| 8150494 | Simon et al. | Apr 2012 | B2 |
| 8150497 | Gielen et al. | Apr 2012 | B2 |
| 8150498 | Gielen et al. | Apr 2012 | B2 |
| 8165658 | Waynik et al. | Apr 2012 | B2 |
| 8170313 | Kendrick et al. | May 2012 | B2 |
| 8179073 | Farritor et al. | May 2012 | B2 |
| 8182476 | Julian et al. | May 2012 | B2 |
| 8184880 | Zhao et al. | May 2012 | B2 |
| 8202278 | Orban, III et al. | Jun 2012 | B2 |
| 8208708 | Homan et al. | Jun 2012 | B2 |
| 8208988 | Jensen | Jun 2012 | B2 |
| 8219177 | Smith et al. | Jul 2012 | B2 |
| 8219178 | Smith et al. | Jul 2012 | B2 |
| 8220468 | Cooper et al. | Jul 2012 | B2 |
| 8224024 | Foxlin et al. | Jul 2012 | B2 |
| 8224484 | Swarup et al. | Jul 2012 | B2 |
| 8225798 | Baldwin et al. | Jul 2012 | B2 |
| 8228368 | Zhao et al. | Jul 2012 | B2 |
| 8231610 | Jo et al. | Jul 2012 | B2 |
| 8263933 | Hartmann et al. | Jul 2012 | B2 |
| 8239001 | Verard et al. | Aug 2012 | B2 |
| 8241271 | Millman et al. | Aug 2012 | B2 |
| 8248413 | Gattani et al. | Aug 2012 | B2 |
| 8256319 | Cooper et al. | Sep 2012 | B2 |
| 8271069 | Jascob et al. | Sep 2012 | B2 |
| 8271130 | Hourtash | Sep 2012 | B2 |
| 8281670 | Larkin et al. | Oct 2012 | B2 |
| 8282653 | Nelson et al. | Oct 2012 | B2 |
| 8301226 | Csavoy et al. | Oct 2012 | B2 |
| 8311611 | Csavoy et al. | Nov 2012 | B2 |
| 8320991 | Jascob et al. | Nov 2012 | B2 |
| 8332012 | Kienzle, III | Dec 2012 | B2 |
| 8333755 | Cooper et al. | Dec 2012 | B2 |
| 8335552 | Stiles | Dec 2012 | B2 |
| 8335557 | Maschke | Dec 2012 | B2 |
| 8348931 | Cooper et al. | Jan 2013 | B2 |
| 8353963 | Glerum | Jan 2013 | B2 |
| 8358818 | Miga et al. | Jan 2013 | B2 |
| 8359730 | Burg et al. | Jan 2013 | B2 |
| 8374673 | Adcox et al. | Feb 2013 | B2 |
| 8374723 | Zhao et al. | Feb 2013 | B2 |
| 8379791 | Forthmann et al. | Feb 2013 | B2 |
| 8386019 | Camus et al. | Feb 2013 | B2 |
| 8392022 | Ortmaier et al. | Mar 2013 | B2 |
| 8394099 | Patwardhan | Mar 2013 | B2 |
| 8395342 | Prisco | Mar 2013 | B2 |
| 8398634 | Manzo et al. | Mar 2013 | B2 |
| 8400094 | Schena | Mar 2013 | B2 |
| 8414957 | Enzerink et al. | Apr 2013 | B2 |
| 8418073 | Mohr et al. | Apr 2013 | B2 |
| 8450694 | Baviera et al. | May 2013 | B2 |
| 8452447 | Nixon | May 2013 | B2 |
| RE44305 | Foley et al. | Jun 2013 | E |
| 8462911 | Vesel et al. | Jun 2013 | B2 |
| 8465476 | Rogers et al. | Jun 2013 | B2 |
| 8465771 | Wan et al. | Jun 2013 | B2 |
| 8467851 | Mire et al. | Jun 2013 | B2 |
| 8467852 | Csavoy et al. | Jun 2013 | B2 |
| 8469947 | Devengenzo et al. | Jun 2013 | B2 |
| RE44392 | Hynes | Jul 2013 | E |
| 8483434 | Buehner et al. | Jul 2013 | B2 |
| 8483800 | Jensen et al. | Jul 2013 | B2 |
| 8486532 | Enzerink et al. | Jul 2013 | B2 |
| 8489235 | Moll et al. | Jul 2013 | B2 |
| 8500722 | Cooper | Aug 2013 | B2 |
| 8500728 | Newton et al. | Aug 2013 | B2 |
| 8504201 | Moll et al. | Aug 2013 | B2 |
| 8506555 | Ruiz Morales | Aug 2013 | B2 |
| 8506556 | Schena | Aug 2013 | B2 |
| 8508173 | Goldberg et al. | Aug 2013 | B2 |
| 8512318 | Tovey et al. | Aug 2013 | B2 |
| 8515576 | Lipow et al. | Aug 2013 | B2 |
| 8518120 | Glerum et al. | Aug 2013 | B2 |
| 8521331 | Itkowitz | Aug 2013 | B2 |
| 8526688 | Groszmann et al. | Sep 2013 | B2 |
| 8526700 | Isaacs | Sep 2013 | B2 |
| 8527094 | Kumar et al. | Sep 2013 | B2 |
| 8528440 | Morley et al. | Sep 2013 | B2 |
| 8532741 | Heruth et al. | Sep 2013 | B2 |
| 8541970 | Nowlin et al. | Sep 2013 | B2 |
| 8548563 | Simon et al. | Oct 2013 | B2 |
| 8549732 | Burg et al. | Oct 2013 | B2 |
| 8551114 | Ramos de la Pena | Oct 2013 | B2 |
| 8551116 | Julian et al. | Oct 2013 | B2 |
| 8556807 | Scott et al. | Oct 2013 | B2 |
| 8556979 | Glerum et al. | Oct 2013 | B2 |
| 8560118 | Green et al. | Oct 2013 | B2 |
| 8561473 | Blumenkranz | Oct 2013 | B2 |
| 8562594 | Cooper et al. | Oct 2013 | B2 |
| 8571638 | Shoham | Oct 2013 | B2 |
| 8571710 | Coste-Maniere et al. | Oct 2013 | B2 |
| 8573465 | Shelton, IV | Nov 2013 | B2 |
| 8574303 | Sharkey et al. | Nov 2013 | B2 |
| 8585420 | Burbank et al. | Nov 2013 | B2 |
| 8594841 | Zhao et al. | Nov 2013 | B2 |
| 8597198 | Sanborn et al. | Dec 2013 | B2 |
| 8600478 | Verard et al. | Dec 2013 | B2 |
| 8603077 | Cooper et al. | Dec 2013 | B2 |
| 8611985 | Lavallee et al. | Dec 2013 | B2 |
| 8613230 | Blumenkranz et al. | Dec 2013 | B2 |
| 8621939 | Blumenkranz et al. | Jan 2014 | B2 |
| 8624537 | Nowlin et al. | Jan 2014 | B2 |
| 8630389 | Kato | Jan 2014 | B2 |
| 8634897 | Simon et al. | Jan 2014 | B2 |
| 8634957 | Toth et al. | Jan 2014 | B2 |
| 8638056 | Goldberg et al. | Jan 2014 | B2 |
| 8638057 | Goldberg et al. | Jan 2014 | B2 |
| 8639000 | Zhao et al. | Jan 2014 | B2 |
| 8641726 | Bonutti | Feb 2014 | B2 |
| 8644907 | Hartmann et al. | Feb 2014 | B2 |
| 8657809 | Schoepp | Feb 2014 | B2 |
| 8660635 | Simon et al. | Feb 2014 | B2 |
| 8666544 | Moll et al. | Mar 2014 | B2 |
| 8675939 | Moctezuma de la Barrera | Mar 2014 | B2 |
| 8678647 | Gregerson et al. | Mar 2014 | B2 |
| 8679125 | Smith et al. | Mar 2014 | B2 |
| 8679183 | Glerum et al. | Mar 2014 | B2 |
| 8682413 | Lloyd | Mar 2014 | B2 |
| 8684253 | Giordano et al. | Apr 2014 | B2 |
| 8685098 | Glerum et al. | Apr 2014 | B2 |
| 8693730 | Umasuthan et al. | Apr 2014 | B2 |
| 8694075 | Groszmann et al. | Apr 2014 | B2 |
| 8696458 | Foxlin et al. | Apr 2014 | B2 |
| 8700123 | Okamura et al. | Apr 2014 | B2 |
| 8706086 | Glerum | Apr 2014 | B2 |
| 8706185 | Foley et al. | Apr 2014 | B2 |
| 8706301 | Zhao et al. | Apr 2014 | B2 |
| 8717430 | Simon et al. | May 2014 | B2 |
| 8727618 | Maschke et al. | May 2014 | B2 |
| 8734432 | Tuma et al. | May 2014 | B2 |
| 8738115 | Amberg et al. | May 2014 | B2 |
| 8738181 | Greer et al. | May 2014 | B2 |
| 8740882 | Jun et al. | Jun 2014 | B2 |
| 8746252 | McGrogan et al. | Jun 2014 | B2 |
| 8749189 | Nowlin et al. | Jun 2014 | B2 |
| 8749190 | Nowlin et al. | Jun 2014 | B2 |
| 8761930 | Nixon | Jun 2014 | B2 |
| 8764448 | Yang et al. | Jul 2014 | B2 |
| 8771170 | Mesallum et al. | Jul 2014 | B2 |
| 8781186 | Clements et al. | Jul 2014 | B2 |
| 8781630 | Banks et al. | Jul 2014 | B2 |
| 8784385 | Boyden et al. | Jul 2014 | B2 |
| 8786241 | Nowlin et al. | Jul 2014 | B2 |
| 8787520 | Baba | Jul 2014 | B2 |
| 8792704 | Isaacs | Jul 2014 | B2 |
| 8798231 | Notohara et al. | Aug 2014 | B2 |
| 8800838 | Shelton, IV | Aug 2014 | B2 |
| 8808164 | Hoffman et al. | Aug 2014 | B2 |
| 8812077 | Dempsey | Aug 2014 | B2 |
| 8814793 | Brabrand | Aug 2014 | B2 |
| 8816628 | Nowlin et al. | Aug 2014 | B2 |
| 8818105 | Myronenko et al. | Aug 2014 | B2 |
| 8820605 | Shelton, IV | Sep 2014 | B2 |
| 8821511 | von Jako et al. | Sep 2014 | B2 |
| 8823308 | Nowlin et al. | Sep 2014 | B2 |
| 8827996 | Scott et al. | Sep 2014 | B2 |
| 8828024 | Farritor et al. | Sep 2014 | B2 |
| 8830224 | Zhao et al. | Sep 2014 | B2 |
| 8834489 | Cooper et al. | Sep 2014 | B2 |
| 8834490 | Bonutti | Sep 2014 | B2 |
| 8838270 | Druke et al. | Sep 2014 | B2 |
| 8844789 | Shelton, IV et al. | Sep 2014 | B2 |
| 8855822 | Bartol et al. | Oct 2014 | B2 |
| 8858598 | Seifert et al. | Oct 2014 | B2 |
| 8860753 | Bhandarkar et al. | Oct 2014 | B2 |
| 8864751 | Prisco et al. | Oct 2014 | B2 |
| 8864798 | Weiman et al. | Oct 2014 | B2 |
| 8864833 | Glerum et al. | Oct 2014 | B2 |
| 8867703 | Shapiro et al. | Oct 2014 | B2 |
| 8870880 | Himmelberger et al. | Oct 2014 | B2 |
| 8876866 | Zappacosta et al. | Nov 2014 | B2 |
| 8880223 | Raj et al. | Nov 2014 | B2 |
| 8882803 | Iott et al. | Nov 2014 | B2 |
| 8883210 | Truncale et al. | Nov 2014 | B1 |
| 8888821 | Rezach et al. | Nov 2014 | B2 |
| 8888853 | Glerum et al. | Nov 2014 | B2 |
| 8888854 | Glerum et al. | Nov 2014 | B2 |
| 8894652 | Seifert et al. | Nov 2014 | B2 |
| 8894688 | Suh | Nov 2014 | B2 |
| 8894691 | Iott et al. | Nov 2014 | B2 |
| 8906069 | Hansell et al. | Dec 2014 | B2 |
| 8964934 | Ein-Gal | Feb 2015 | B2 |
| 8992580 | Bar et al. | Mar 2015 | B2 |
| 8996169 | Lightcap et al. | Mar 2015 | B2 |
| 9001963 | Sowards-Emmerd et al. | Apr 2015 | B2 |
| 9002076 | Khadem et al. | Apr 2015 | B2 |
| 9044190 | Rubner et al. | Jun 2015 | B2 |
| 9107683 | Hourtash et al. | Aug 2015 | B2 |
| 9125556 | Zehavi et al. | Sep 2015 | B2 |
| 9131986 | Greer et al. | Sep 2015 | B2 |
| 9215968 | Schostek et al. | Dec 2015 | B2 |
| 9308050 | Kostrzewski et al. | Apr 2016 | B2 |
| 9380984 | Li et al. | Jul 2016 | B2 |
| 9393039 | Lechner et al. | Jul 2016 | B2 |
| 9398886 | Gregerson et al. | Jul 2016 | B2 |
| 9398890 | Dong et al. | Jul 2016 | B2 |
| 9414859 | Ballard et al. | Aug 2016 | B2 |
| 9420975 | Gutfleisch et al. | Aug 2016 | B2 |
| 9492235 | Hourtash et al. | Nov 2016 | B2 |
| 9592096 | Maillet et al. | Mar 2017 | B2 |
| 9750465 | Engel et al. | Sep 2017 | B2 |
| 9757203 | Hourtash et al. | Sep 2017 | B2 |
| 9795354 | Menegaz et al. | Oct 2017 | B2 |
| 9814535 | Bar et al. | Nov 2017 | B2 |
| 9820783 | Donner et al. | Nov 2017 | B2 |
| 9833265 | Donner et al. | Nov 2017 | B2 |
| 9848922 | Tohmeh et al. | Dec 2017 | B2 |
| 9925011 | Gombert et al. | Mar 2018 | B2 |
| 9931025 | Graetzel et al. | Apr 2018 | B1 |
| 10034717 | Miller et al. | Jul 2018 | B2 |
| 20010025183 | Shadidi | Sep 2001 | A1 |
| 20010036302 | Miller | Nov 2001 | A1 |
| 20020035321 | Bucholz et al. | Mar 2002 | A1 |
| 20040068172 | Nowinski et al. | Apr 2004 | A1 |
| 20040076259 | Jensen et al. | Apr 2004 | A1 |
| 20040106916 | Quaid | Jun 2004 | A1 |
| 20050096502 | Khalili | May 2005 | A1 |
| 20050143651 | Verard et al. | Jun 2005 | A1 |
| 20050171558 | Abovitz et al. | Aug 2005 | A1 |
| 20060100610 | Wallace et al. | May 2006 | A1 |
| 20060142657 | Quaid | Jun 2006 | A1 |
| 20060173329 | Marquart et al. | Aug 2006 | A1 |
| 20060184396 | Dennis et al. | Aug 2006 | A1 |
| 20060241416 | Marquart et al. | Oct 2006 | A1 |
| 20060291612 | Nishide et al. | Dec 2006 | A1 |
| 20070015987 | Benlloch Baviera et al. | Jan 2007 | A1 |
| 20070021738 | Hasser et al. | Jan 2007 | A1 |
| 20070038059 | Sheffer et al. | Feb 2007 | A1 |
| 20070073133 | Schoenefeld | Mar 2007 | A1 |
| 20070156121 | Millman et al. | Jul 2007 | A1 |
| 20070156157 | Nahum et al. | Jul 2007 | A1 |
| 20070167712 | Keglovich et al. | Jul 2007 | A1 |
| 20070233238 | Huynh et al. | Oct 2007 | A1 |
| 20080004523 | Jensen | Jan 2008 | A1 |
| 20080013809 | Zhu et al. | Jan 2008 | A1 |
| 20080033283 | Dellaca et al. | Feb 2008 | A1 |
| 20080046122 | Manzo et al. | Feb 2008 | A1 |
| 20080077158 | Haider et al. | Mar 2008 | A1 |
| 20080082109 | Moll et al. | Apr 2008 | A1 |
| 20080108912 | Node-Langlois | May 2008 | A1 |
| 20080108991 | von Jako | May 2008 | A1 |
| 20080109012 | Falco et al. | May 2008 | A1 |
| 20080144906 | Mired et al. | Jun 2008 | A1 |
| 20080161680 | von Jako et al. | Jul 2008 | A1 |
| 20080161682 | Kendrick et al. | Jul 2008 | A1 |
| 20080177203 | von Jako | Jul 2008 | A1 |
| 20080214922 | Hartmann et al. | Sep 2008 | A1 |
| 20080218770 | Moll | Sep 2008 | A1 |
| 20080228068 | Viswanathan et al. | Sep 2008 | A1 |
| 20080228196 | Wang et al. | Sep 2008 | A1 |
| 20080235052 | Node-Langlois et al. | Sep 2008 | A1 |
| 20080269596 | Revie et al. | Oct 2008 | A1 |
| 20080287771 | Anderson | Nov 2008 | A1 |
| 20080287781 | Revie et al. | Nov 2008 | A1 |
| 20080300477 | Lloyd et al. | Dec 2008 | A1 |
| 20080300478 | Zuhars et al. | Dec 2008 | A1 |
| 20080302950 | Park et al. | Dec 2008 | A1 |
| 20080306490 | Lakin et al. | Dec 2008 | A1 |
| 20080319311 | Hamadeh | Dec 2008 | A1 |
| 20090012509 | Csavoy et al. | Jan 2009 | A1 |
| 20090030428 | Omori et al. | Jan 2009 | A1 |
| 20090080737 | Battle et al. | Mar 2009 | A1 |
| 20090185655 | Koken et al. | Jul 2009 | A1 |
| 20090198121 | Hoheisel | Aug 2009 | A1 |
| 20090216113 | Meier et al. | Aug 2009 | A1 |
| 20090228019 | Gross et al. | Sep 2009 | A1 |
| 20090259123 | Navab et al. | Oct 2009 | A1 |
| 20090259230 | Khadem et al. | Oct 2009 | A1 |
| 20090264899 | Appenrodt et al. | Oct 2009 | A1 |
| 20090281417 | Hartmann et al. | Nov 2009 | A1 |
| 20100022874 | Wang et al. | Jan 2010 | A1 |
| 20100039506 | Sarvestani et al. | Feb 2010 | A1 |
| 20100063387 | Timinger | Mar 2010 | A1 |
| 20100076455 | Birkenbach et al. | Mar 2010 | A1 |
| 20100125286 | Wang et al. | May 2010 | A1 |
| 20100130986 | Mailloux et al. | May 2010 | A1 |
| 20100168723 | Suarez | Jul 2010 | A1 |
| 20100228117 | Hartmann | Sep 2010 | A1 |
| 20100228265 | Prisco | Sep 2010 | A1 |
| 20100234724 | Jacobsen | Sep 2010 | A1 |
| 20100249571 | Jensen et al. | Sep 2010 | A1 |
| 20100274120 | Heuscher | Oct 2010 | A1 |
| 20100280363 | Skarda et al. | Nov 2010 | A1 |
| 20100331858 | Simaan et al. | Dec 2010 | A1 |
| 20110022229 | Jang et al. | Jan 2011 | A1 |
| 20110077504 | Fischer et al. | Mar 2011 | A1 |
| 20110098553 | Robbins et al. | Apr 2011 | A1 |
| 20110137152 | Li | Jun 2011 | A1 |
| 20110160569 | Cohen | Jun 2011 | A1 |
| 20110213384 | Jeong | Sep 2011 | A1 |
| 20110224684 | Larkin et al. | Sep 2011 | A1 |
| 20110224685 | Larkin et al. | Sep 2011 | A1 |
| 20110224686 | Larkin et al. | Sep 2011 | A1 |
| 20110224687 | Larkin et al. | Sep 2011 | A1 |
| 20110224688 | Larkin et al. | Sep 2011 | A1 |
| 20110224689 | Larkin et al. | Sep 2011 | A1 |
| 20110224825 | Larkin et al. | Sep 2011 | A1 |
| 20110230967 | O'Halloran et al. | Sep 2011 | A1 |
| 20110238080 | Ranjit et al. | Sep 2011 | A1 |
| 20110276058 | Choi et al. | Nov 2011 | A1 |
| 20110282189 | Graumann | Nov 2011 | A1 |
| 20110286573 | Schretter et al. | Nov 2011 | A1 |
| 20110295062 | Solsona et al. | Dec 2011 | A1 |
| 20110295370 | Suh et al. | Dec 2011 | A1 |
| 20110306986 | Lee et al. | Dec 2011 | A1 |
| 20120035507 | George et al. | Feb 2012 | A1 |
| 20120046668 | Gantes | Feb 2012 | A1 |
| 20120051498 | Koishi | Mar 2012 | A1 |
| 20120053597 | Anvari et al. | Mar 2012 | A1 |
| 20120059248 | Holsing et al. | Mar 2012 | A1 |
| 20120071753 | Hunter et al. | Mar 2012 | A1 |
| 20120108954 | Schulhauser et al. | May 2012 | A1 |
| 20120109152 | Quaid | May 2012 | A1 |
| 20120136372 | Amat Girbau et al. | May 2012 | A1 |
| 20120143084 | Shoham | Jun 2012 | A1 |
| 20120184839 | Woerlein | Jul 2012 | A1 |
| 20120185099 | Bosscher | Jul 2012 | A1 |
| 20120190981 | Harris | Jul 2012 | A1 |
| 20120197182 | Millman et al. | Aug 2012 | A1 |
| 20120209117 | Mozes et al. | Aug 2012 | A1 |
| 20120226145 | Chang | Sep 2012 | A1 |
| 20120235909 | Birkenbach et al. | Sep 2012 | A1 |
| 20120245596 | Meenink | Sep 2012 | A1 |
| 20120253332 | Moll | Oct 2012 | A1 |
| 20120253360 | White et al. | Oct 2012 | A1 |
| 20120256092 | Zingerman | Oct 2012 | A1 |
| 20120294498 | Popovic | Nov 2012 | A1 |
| 20120296203 | Hartmann et al. | Nov 2012 | A1 |
| 20130006267 | Odermatt et al. | Jan 2013 | A1 |
| 20130010081 | Tenney | Jan 2013 | A1 |
| 20130016889 | Myronenko et al. | Jan 2013 | A1 |
| 20130030571 | Ruiz Morales et al. | Jan 2013 | A1 |
| 20130035583 | Park et al. | Feb 2013 | A1 |
| 20130060146 | Yang et al. | Mar 2013 | A1 |
| 20130060337 | Petersheim et al. | Mar 2013 | A1 |
| 20130094742 | Feilkas | Apr 2013 | A1 |
| 20130096573 | Kang | Apr 2013 | A1 |
| 20130096574 | Kang et al. | Apr 2013 | A1 |
| 20130113791 | Isaacs et al. | May 2013 | A1 |
| 20130116706 | Lee et al. | May 2013 | A1 |
| 20130131695 | Scarfogliero et al. | May 2013 | A1 |
| 20130144307 | Jeong et al. | Jun 2013 | A1 |
| 20130158542 | Manzo et al. | Jun 2013 | A1 |
| 20130165937 | Patwardhan | Jun 2013 | A1 |
| 20130178867 | Farritor et al. | Jul 2013 | A1 |
| 20130178868 | Roh | Jul 2013 | A1 |
| 20130178870 | Schena | Jul 2013 | A1 |
| 20130204271 | Brisson et al. | Aug 2013 | A1 |
| 20130211419 | Jensen | Aug 2013 | A1 |
| 20130211420 | Jensen | Aug 2013 | A1 |
| 20130218142 | Tuma et al. | Aug 2013 | A1 |
| 20130223702 | Holsing et al. | Aug 2013 | A1 |
| 20130225942 | Holsing et al. | Aug 2013 | A1 |
| 20130225943 | Holsing et al. | Aug 2013 | A1 |
| 20130231556 | Holsing et al. | Sep 2013 | A1 |
| 20130237995 | Lee et al. | Sep 2013 | A1 |
| 20130245375 | DiMaio et al. | Sep 2013 | A1 |
| 20130261640 | Kim et al. | Oct 2013 | A1 |
| 20130272488 | Bailey et al. | Oct 2013 | A1 |
| 20130272489 | Dickman et al. | Oct 2013 | A1 |
| 20130274761 | Devengenzo et al. | Oct 2013 | A1 |
| 20130281821 | Liu et al. | Oct 2013 | A1 |
| 20130296884 | Taylor et al. | Nov 2013 | A1 |
| 20130303887 | Holsing et al. | Nov 2013 | A1 |
| 20130307955 | Deitz et al. | Nov 2013 | A1 |
| 20130317521 | Choi et al. | Nov 2013 | A1 |
| 20130325033 | Schena et al. | Dec 2013 | A1 |
| 20130325035 | Hauck et al. | Dec 2013 | A1 |
| 20130331686 | Freysinger et al. | Dec 2013 | A1 |
| 20130331858 | Devengenzo et al. | Dec 2013 | A1 |
| 20130331861 | Yoon | Dec 2013 | A1 |
| 20130342578 | Isaacs | Dec 2013 | A1 |
| 20130345717 | Markvicka et al. | Dec 2013 | A1 |
| 20130345757 | Stad | Dec 2013 | A1 |
| 20140001235 | Shelton, IV | Jan 2014 | A1 |
| 20140012131 | Heruth et al. | Jan 2014 | A1 |
| 20140031664 | Kang et al. | Jan 2014 | A1 |
| 20140046128 | Lee et al. | Feb 2014 | A1 |
| 20140046132 | Hoeg et al. | Feb 2014 | A1 |
| 20140046340 | Wilson et al. | Feb 2014 | A1 |
| 20140049629 | Siewerdsen et al. | Feb 2014 | A1 |
| 20140058406 | Tsekos | Feb 2014 | A1 |
| 20140073914 | Lavallee et al. | Mar 2014 | A1 |
| 20140080086 | Chen | Mar 2014 | A1 |
| 20140081128 | Verard et al. | Mar 2014 | A1 |
| 20140088612 | Bartol et al. | Mar 2014 | A1 |
| 20140094694 | Moctezuma de la Barrera | Apr 2014 | A1 |
| 20140094851 | Gordon | Apr 2014 | A1 |
| 20140096369 | Matsumoto et al. | Apr 2014 | A1 |
| 20140100587 | Farritor et al. | Apr 2014 | A1 |
| 20140121676 | Kostrzewski et al. | May 2014 | A1 |
| 20140128882 | Kwak et al. | May 2014 | A1 |
| 20140135796 | Simon et al. | May 2014 | A1 |
| 20140142591 | Alvarez et al. | May 2014 | A1 |
| 20140142592 | Moon et al. | May 2014 | A1 |
| 20140148692 | Hartmann et al. | May 2014 | A1 |
| 20140163581 | Devengenzo et al. | Jun 2014 | A1 |
| 20140171781 | Stiles | Jun 2014 | A1 |
| 20140171900 | Stiles | Jun 2014 | A1 |
| 20140171965 | Loh et al. | Jun 2014 | A1 |
| 20140180308 | von Grunberg | Jun 2014 | A1 |
| 20140180309 | Seeber et al. | Jun 2014 | A1 |
| 20140187915 | Yaroshenko et al. | Jul 2014 | A1 |
| 20140188132 | Kang | Jul 2014 | A1 |
| 20140194699 | Roh et al. | Jul 2014 | A1 |
| 20140130810 | Azizian et al. | Aug 2014 | A1 |
| 20140221819 | Sarment | Aug 2014 | A1 |
| 20140222023 | Kim et al. | Aug 2014 | A1 |
| 20140228631 | Kwak et al. | Aug 2014 | A1 |
| 20140228860 | Steines | Aug 2014 | A1 |
| 20140234804 | Huang et al. | Aug 2014 | A1 |
| 20140257328 | Kim et al. | Sep 2014 | A1 |
| 20140257329 | Jang et al. | Sep 2014 | A1 |
| 20140257330 | Choi et al. | Sep 2014 | A1 |
| 20140275760 | Lee et al. | Sep 2014 | A1 |
| 20140275985 | Walker et al. | Sep 2014 | A1 |
| 20140276931 | Parihar et al. | Sep 2014 | A1 |
| 20140276940 | Seo | Sep 2014 | A1 |
| 20140276944 | Farritor et al. | Sep 2014 | A1 |
| 20140288413 | Hwang et al. | Sep 2014 | A1 |
| 20140299648 | Shelton, IV et al. | Oct 2014 | A1 |
| 20140303434 | Farritor et al. | Oct 2014 | A1 |
| 20140303643 | Ha et al. | Oct 2014 | A1 |
| 20140305995 | Shelton, IV et al. | Oct 2014 | A1 |
| 20140309659 | Roh et al. | Oct 2014 | A1 |
| 20140316436 | Bar et al. | Oct 2014 | A1 |
| 20140323803 | Hoffman et al. | Oct 2014 | A1 |
| 20140324070 | Min et al. | Oct 2014 | A1 |
| 20140330288 | Date et al. | Nov 2014 | A1 |
| 20140364720 | Darrow et al. | Dec 2014 | A1 |
| 20140371577 | Maillet et al. | Dec 2014 | A1 |
| 20150039034 | Frankel et al. | Feb 2015 | A1 |
| 20150085970 | Bouhnik et al. | Mar 2015 | A1 |
| 20150100066 | Kostrzewski | Apr 2015 | A1 |
| 20150146847 | Liu | May 2015 | A1 |
| 20150150524 | Yorkston et al. | Jun 2015 | A1 |
| 20150196261 | Funk | Jul 2015 | A1 |
| 20150213633 | Chang et al. | Jul 2015 | A1 |
| 20150335480 | Alvarez | Nov 2015 | A1 |
| 20150342647 | Frankel et al. | Dec 2015 | A1 |
| 20150347682 | Chen | Dec 2015 | A1 |
| 20160005194 | Schretter et al. | Jan 2016 | A1 |
| 20160151120 | Kostrzewski et al. | Jun 2016 | A1 |
| 20160166329 | Langan et al. | Jun 2016 | A1 |
| 20160213415 | Carter | Jul 2016 | A1 |
| 20160235480 | Scholl et al. | Aug 2016 | A1 |
| 20160249990 | Glozman et al. | Sep 2016 | A1 |
| 20160302871 | Gregerson et al. | Oct 2016 | A1 |
| 20160320322 | Suzuki | Nov 2016 | A1 |
| 20160331335 | Gregerson et al. | Nov 2016 | A1 |
| 20170135770 | Scholl et al. | May 2017 | A1 |
| 20170143284 | Sehnert et al. | May 2017 | A1 |
| 20170143426 | Isaacs et al. | May 2017 | A1 |
| 20170156816 | Ibrahim | Jun 2017 | A1 |
| 20170202629 | Maillet et al. | Jul 2017 | A1 |
| 20170212723 | Atarot et al. | Jul 2017 | A1 |
| 20170215825 | Johnson et al. | Aug 2017 | A1 |
| 20170215826 | Johnson et al. | Aug 2017 | A1 |
| 20170215827 | Johnson et al. | Aug 2017 | A1 |
| 20170231710 | Scholl et al. | Aug 2017 | A1 |
| 20170258426 | Risher-Kelly et al. | Sep 2017 | A1 |
| 20170273748 | Hourtash et al. | Sep 2017 | A1 |
| 20170296277 | Hourtash et al. | Oct 2017 | A1 |
| 20170340389 | Otto | Nov 2017 | A1 |
| 20170360493 | Zucher et al. | Dec 2017 | A1 |
| 20180199995 | Odermatt | Jul 2018 | A1 |
| 20180199996 | Hogan | Jul 2018 | A1 |
| 20190015167 | Draelos | Jan 2019 | A1 |
| 20190015168 | Verner | Jan 2019 | A1 |
| 20200030040 | Kostrzewski | Jan 2020 | A1 |
| 20210244485 | Coiseur | Aug 2021 | A1 |
| Number | Date | Country |
|---|---|---|
| 3360502 | Aug 2018 | EP |
| 2005537583 | Dec 2005 | JP |
| 2008237784 | Oct 2008 | JP |
| 2008538184 | Oct 2008 | JP |
| 2010519635 | Jun 2010 | JP |
| 2016087539 | Jun 2016 | WO |
| Entry |
|---|
| US 8,231,638 B2, 07/2012, Swarup et al. (withdrawn) |
| Jon T. Lea, Dane Watkins, Aaron Mills, Michael A. Peshkin, Thomas C. Kienzle, and S. David Stulberg , “Registration and Immobilization in Robot-Assisted Surgery”, Journal of Image Guided Surgery, 1995, 80-87. |
| Number | Date | Country | |
|---|---|---|---|
| 20200030040 A1 | Jan 2020 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62447884 | Jan 2017 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15874695 | Jan 2018 | US |
| Child | 16535166 | US |
