Robotic systems providing co-registration using natural fiducials and related methods

Information

  • Patent Grant
  • 11399900
  • Patent Number
    11,399,900
  • Date Filed
    Thursday, June 7, 2018
    6 years ago
  • Date Issued
    Tuesday, August 2, 2022
    2 years ago
Abstract
A method may be provided to operate a medical system. First data may be provided for a first 3-dimensional (3D) image scan of an anatomical volume, with the first data identifying a blood vessel node in a first coordinate system for the first 3D image scan. Second data may be provided for a second 3D image scan of the anatomical volume, with the second data identifying the blood vessel node in a second coordinate system for the second 3D image scan. The first and second coordinate systems for the first and second 3D image scans of the anatomical volume may be co-registered using the blood vessel node identified in the first data and in the second data as a fiducial.
Description
FIELD

The present disclosure relates to medical devices, and more particularly, robotic systems and related methods and devices.


BACKGROUND

When performing cranial/brain surgery, the soft tissues of the brain can easily shift. Such shifting may occur, for example, after the surgeon penetrates the skull and intracranial pressure changes. Tracking structures internal to the brain using markers attached external to the skull and/or based on registration from a preoperative scan may thus be inaccurate if such shifting occurs. Stated in other words, during surgery, brain structures may shift/distort relative to a pre-operative image scan, thereby reducing accuracy of planned trajectories determined based on the pre-operative image scan.


SUMMARY

According to some embodiments of inventive concepts, a robotic system may include a robotic actuator configured to position a surgical end-effector with respect to an anatomical volume of a patient, and a controller coupled with the robotic actuator. The controller may be configured to provide first data for a first 3-dimensional (3D) image scan of the anatomical volume, with the first data identifying a blood vessel node in a first coordinate system for the first 3D image scan. The controller may also be configured to provide second data for a second 3D image scan of the anatomical volume, with the second data identifying the blood vessel node in a second coordinate system for the second 3D image scan. The controller may be further configured to co-register the first and second coordinate systems for the first and second 3D image scans of the anatomical volume using the blood vessel node identified in the first data and in the second data as a fiducial. In addition, the controller may be configured to control the robotic actuator to move the end-effector to a target trajectory relative to the anatomical volume based on co-registering the first and second coordinate systems for the first and second 3D image scans using the blood vessel node.


According to some other embodiments of inventive concepts, a method may be provided to operate a medical system. First data may be provided for a first 3-dimensional (3D) image scan of an anatomical volume, with the first data identifying a blood vessel node in a first coordinate system for the first 3D image scan. Second data may be provided for a second 3D image scan of the anatomical volume, with the second data identifying the blood vessel node in a second coordinate system for the second 3D image scan. The first and second coordinate systems for the first and second 3D image scans of the anatomical volume may be co-registered using the blood vessel node identified in the first data and in the second data as a fiducial.


Other methods and related systems, and corresponding methods and computer program products according to embodiments of the inventive subject matter will be or become apparent to one with skill in the art upon review of the following drawings and detailed description. It is intended that all such systems, and corresponding methods and computer program products be included within this description, be within the scope of the present inventive subject matter, and be protected by the accompanying claims. Moreover, it is intended that all embodiments disclosed herein can be implemented separately or combined in any way and/or combination.





DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in a constitute a part of this application, illustrate certain non-limiting embodiments of inventive concepts. In the drawings:



FIG. 1 is an overhead view of a potential arrangement for locations of the robotic system, patient, surgeon, and other medical personnel during a surgical procedure;



FIG. 2 illustrates the robotic system including positioning of the surgical robot and the camera relative to the patient according to one embodiment;



FIG. 3 illustrates a surgical robotic system in accordance with an exemplary embodiment;



FIG. 4 illustrates a portion of a surgical robot in accordance with an exemplary embodiment;



FIG. 5 illustrates a block diagram of a surgical robot in accordance with an exemplary embodiment;



FIG. 6 illustrates a surgical robot in accordance with an exemplary embodiment;



FIGS. 7A-7C illustrate an end-effector in accordance with an exemplary embodiment;



FIG. 8 illustrates a surgical instrument and the end-effector, before and after, inserting the surgical instrument into the guide tube of the end-effector according to one embodiment;



FIGS. 9A-9C illustrate portions of an end-effector and robot arm in accordance with an exemplary embodiment;



FIG. 10 illustrates a dynamic reference array, an imaging array, and other components in accordance with an exemplary embodiment;



FIG. 11 illustrates a method of registration in accordance with an exemplary embodiment;



FIG. 12A-12B illustrate embodiments of imaging devices according to exemplary embodiments;



FIG. 13A illustrates a portion of a robot including the robot arm and an end-effector in accordance with an exemplary embodiment;



FIG. 13B is a close-up view of the end-effector, with a plurality of tracking markers rigidly affixed thereon, shown in FIG. 13A;



FIG. 13C is a tool or instrument with a plurality of tracking markers rigidly affixed thereon according to one embodiment;



FIG. 14A is an alternative version of an end-effector with moveable tracking markers in a first configuration;



FIG. 14B is the end-effector shown in FIG. 14A with the moveable tracking markers in a second configuration;



FIG. 14C shows the template of tracking markers in the first configuration from FIG. 14A;



FIG. 14D shows the template of tracking markers in the second configuration from FIG. 14B;



FIG. 15A shows an alternative version of the end-effector having only a single tracking marker affixed thereto;



FIG. 15B shows the end-effector of FIG. 15A with an instrument disposed through the guide tube;



FIG. 15C shows the end-effector of FIG. 15A with the instrument in two different positions, and the resulting logic to determine if the instrument is positioned within the guide tube or outside of the guide tube;



FIG. 15D shows the end-effector of FIG. 15A with the instrument in the guide tube at two different frames and its relative distance to the single tracking marker on the guide tube;



FIG. 15E shows the end-effector of FIG. 15A relative to a coordinate system;



FIG. 16 is a block diagram of a method for navigating and moving the end-effector of the robot to a desired target trajectory;



FIGS. 17A-17B depict an instrument for inserting an expandable implant having fixed and moveable tracking markers in contracted and expanded positions, respectively;



FIGS. 18A-18B depict an instrument for inserting an articulating implant having fixed and moveable tracking markers in insertion and angled positions, respectively;



FIG. 19A depicts an embodiment of a robot with interchangeable or alternative end-effectors;



FIG. 19B depicts an embodiment of a robot with an instrument style end-effector coupled thereto;



FIG. 20 is a block diagram illustrating a robotic controller according to some embodiments of inventive concepts;



FIG. 21 is a 3-dimensional (3D) reconstruction of a CT image with contrast showing blood vessels in the brain according to some embodiments;



FIG. 22 is an example of a tree structure mapping used to record/identify natural fiducials using blood vessel nodes in the brain according to some embodiments; and



FIG. 23 is a flow chart illustrating operations of robotic systems according to some embodiments.





DETAILED DESCRIPTION

It is to be understood that the present disclosure is not limited in its application to the details of construction and the arrangement of components set forth in the description herein or illustrated in the drawings. The teachings of the present disclosure may be used and practiced in other embodiments and practiced or carried out in various ways. Also, it is to be understood that the phraseology and terminology used herein is for the purpose of description and should not be regarded as limiting. The use of “including,” “comprising,” or “having” and variations thereof herein is meant to encompass the items listed thereafter and equivalents thereof as well as additional items. Unless specified or limited otherwise, the terms “mounted,” “connected,” “supported,” and “coupled” and variations thereof are used broadly and encompass both direct and indirect mountings, connections, supports, and couplings. Further, “connected” and “coupled” are not restricted to physical or mechanical connections or couplings.


The following discussion is presented to enable a person skilled in the art to make and use embodiments of the present disclosure. Various modifications to the illustrated embodiments will be readily apparent to those skilled in the art, and the principles herein can be applied to other embodiments and applications without departing from embodiments of the present disclosure. Thus, the embodiments are not intended to be limited to embodiments shown, but are to be accorded the widest scope consistent with the principles and features disclosed herein. The following detailed description is to be read with reference to the figures, in which like elements in different figures have like reference numerals. The figures, which are not necessarily to scale, depict selected embodiments and are not intended to limit the scope of the embodiments. Skilled artisans will recognize the examples provided herein have many useful alternatives and fall within the scope of the embodiments.


Turning now to the drawing, FIGS. 1 and 2 illustrate a surgical robot system 100 in accordance with an exemplary embodiment. Surgical robot system 100 may include, for example, a surgical robot 102, one or more robot arms 104, a base 106, a display 110, an end-effector 112, for example, including a guide tube 114, and one or more tracking markers 118. The surgical robot system 100 may include a patient tracking device 116 also including one or more tracking markers 118, which is adapted to be secured directly to the patient 210 (e.g., to a bone of the patient 210). The surgical robot system 100 may also use a camera 200, for example, positioned on a camera stand 202. The camera stand 202 can have any suitable configuration to move, orient, and support the camera 200 in a desired position. The camera 200 may include any suitable camera or cameras, such as one or more infrared cameras (e.g., bifocal or stereophotogrammetric cameras), able to identify, for example, active and passive tracking markers 118 (shown as part of patient tracking device 116 in FIG. 2 and shown by enlarged view in FIGS. 13A-13B) in a given measurement volume viewable from the perspective of the camera 200. The camera 200 may scan the given measurement volume and detect the light that comes from the markers 118 in order to identify and determine the position of the markers 118 in three-dimensions. For example, active markers 118 may include infrared-emitting markers that are activated by an electrical signal (e.g., infrared light emitting diodes (LEDs)), and/or passive markers 118 may include retro-reflective markers that reflect infrared light (e.g., they reflect incoming IR radiation into the direction of the incoming light), for example, emitted by illuminators on the camera 200 or other suitable device.



FIGS. 1 and 2 illustrate a potential configuration for the placement of the surgical robot system 100 in an operating room environment. For example, the robot 102 may be positioned near or next to patient 210. Although depicted near the head of the patient 210, it will be appreciated that the robot 102 can be positioned at any suitable location near the patient 210 depending on the area of the patient 210 undergoing the operation. The camera 200 may be separated from the robot system 100 and positioned at the foot of patient 210. This location allows the camera 200 to have a direct visual line of sight to the surgical field 208. Again, it is contemplated that the camera 200 may be located at any suitable position having line of sight to the surgical field 208. In the configuration shown, the surgeon 120 may be positioned across from the robot 102, but is still able to manipulate the end-effector 112 and the display 110. A surgical assistant 126 may be positioned across from the surgeon 120 again with access to both the end-effector 112 and the display 110. If desired, the locations of the surgeon 120 and the assistant 126 may be reversed. The traditional areas for the anesthesiologist 122 and the nurse or scrub tech 124 may remain unimpeded by the locations of the robot 102 and camera 200.


With respect to the other components of the robot 102, the display 110 can be attached to the surgical robot 102 and in other exemplary embodiments, display 110 can be detached from surgical robot 102, either within a surgical room with the surgical robot 102, or in a remote location. End-effector 112 may be coupled to the robot arm 104 and controlled by at least one motor. In exemplary embodiments, end-effector 112 can comprise a guide tube 114, which is able to receive and orient a surgical instrument 608 (described further herein) used to perform surgery on the patient 210. As used herein, the term “end-effector” is used interchangeably with the terms “end-effectuator” and “effectuator element.” Although generally shown with a guide tube 114, it will be appreciated that the end-effector 112 may be replaced with any suitable instrumentation suitable for use in surgery. In some embodiments, end-effector 112 can comprise any known structure for effecting the movement of the surgical instrument 608 in a desired manner.


The surgical robot 102 is able to control the translation and orientation of the end-effector 112. The robot 102 is able to move end-effector 112 along x-, y-, and z-axes, for example. The end-effector 112 can be configured for selective rotation about one or more of the x-, y-, and z-axis, and a Z Frame axis (such that one or more of the Euler Angles (e.g., roll, pitch, and/or yaw) associated with end-effector 112 can be selectively controlled). In some exemplary embodiments, selective control of the translation and orientation of end-effector 112 can permit performance of medical procedures with significantly improved accuracy compared to conventional robots that use, for example, a six degree of freedom robot arm comprising only rotational axes. For example, the surgical robot system 100 may be used to operate on patient 210, and robot arm 104 can be positioned above the body of patient 210, with end-effector 112 selectively angled relative to the z-axis toward the body of patient 210.


In some exemplary embodiments, the position of the surgical instrument 608 can be dynamically updated so that surgical robot 102 can be aware of the location of the surgical instrument 608 at all times during the procedure. Consequently, in some exemplary embodiments, surgical robot 102 can move the surgical instrument 608 to the desired position quickly without any further assistance from a physician (unless the physician so desires). In some further embodiments, surgical robot 102 can be configured to correct the path of the surgical instrument 608 if the surgical instrument 608 strays from the selected, preplanned trajectory. In some exemplary embodiments, surgical robot 102 can be configured to permit stoppage, modification, and/or manual control of the movement of end-effector 112 and/or the surgical instrument 608. Thus, in use, in exemplary embodiments, a physician or other user can operate the system 100, and has the option to stop, modify, or manually control the autonomous movement of end-effector 112 and/or the surgical instrument 608. Further details of surgical robot system 100 including the control and movement of a surgical instrument 608 by surgical robot 102 can be found in co-pending U.S. Pat. No. 9,782,229, the disclosure of which is hereby incorporated herein by reference in its entirety.


The robotic surgical system 100 can comprise one or more tracking markers 118 configured to track the movement of robot arm 104, end-effector 112, patient 210, and/or the surgical instrument 608 in three dimensions. In exemplary embodiments, a plurality of tracking markers 118 can be mounted (or otherwise secured) thereon to an outer surface of the robot 102, such as, for example and without limitation, on base 106 of robot 102, on robot arm 104, and/or on the end-effector 112. In exemplary embodiments, at least one tracking marker 118 of the plurality of tracking markers 118 can be mounted or otherwise secured to the end-effector 112. One or more tracking markers 118 can further be mounted (or otherwise secured) to the patient 210. In exemplary embodiments, the plurality of tracking markers 118 can be positioned on the patient 210 spaced apart from the surgical field 208 to reduce the likelihood of being obscured by the surgeon, surgical tools, or other parts of the robot 102. Further, one or more tracking markers 118 can be further mounted (or otherwise secured) to the surgical tools 608 (e.g., a screw driver, dilator, implant inserter, or the like). Thus, the tracking markers 118 enable each of the marked objects (e.g., the end-effector 112, the patient 210, and the surgical tools 608) to be tracked by the robot 102. In exemplary embodiments, system 100 can use tracking information collected from each of the marked objects to calculate the orientation and location, for example, of the end-effector 112, the surgical instrument 608 (e.g., positioned in the tube 114 of the end-effector 112), and the relative position of the patient 210.


The markers 118 may include radiopaque or optical markers. The markers 118 may be suitably shaped include spherical, spheroid, cylindrical, cube, cuboid, or the like. In exemplary embodiments, one or more of markers 118 may be optical markers. In some embodiments, the positioning of one or more tracking markers 118 on end-effector 112 may increase/maximize accuracy of positional measurements by serving to check or verify a position of end-effector 112. Further details of surgical robot system 100 including the control, movement and tracking of surgical robot 102 and of a surgical instrument 608 can be found in U.S. patent publication No. 2016/0242849, the disclosure of which is incorporated herein by reference in its entirety.


Exemplary embodiments include one or more markers 118 coupled to the surgical instrument 608. In exemplary embodiments, these markers 118, for example, coupled to the patient 210 and surgical instruments 608, as well as markers 118 coupled to the end-effector 112 of the robot 102 can comprise conventional infrared light-emitting diodes (LEDs) or an Optotrak® diode capable of being tracked using a commercially available infrared optical tracking system such as Optotrak®. Optotrak® is a registered trademark of Northern Digital Inc., Waterloo, Ontario, Canada. In other embodiments, markers 118 can comprise conventional reflective spheres capable of being tracked using a commercially available optical tracking system such as Polaris Spectra. Polaris Spectra is also a registered trademark of Northern Digital, Inc. In an exemplary embodiment, the markers 118 coupled to the end-effector 112 are active markers which comprise infrared light-emitting diodes which may be turned on and off, and the markers 118 coupled to the patient 210 and the surgical instruments 608 comprise passive reflective spheres.


In exemplary embodiments, light emitted from and/or reflected by markers 118 can be detected by camera 200 and can be used to monitor the location and movement of the marked objects. In alternative embodiments, markers 118 can comprise a radio-frequency and/or electromagnetic reflector or transceiver and the camera 200 can include or be replaced by a radio-frequency and/or electromagnetic transceiver.


Similar to surgical robot system 100, FIG. 3 illustrates a surgical robot system 300 and camera stand 302, in a docked configuration, consistent with an exemplary embodiment of the present disclosure. Surgical robot system 300 may comprise a robot 301 including a display 304, upper arm 306, lower arm 308, end-effector 310, vertical column 312, casters 314, cabinet 316, tablet drawer 318, connector panel 320, control panel 322, and ring of information 324. Camera stand 302 may comprise camera 326. These components are described in greater with respect to FIG. 5. FIG. 3 illustrates the surgical robot system 300 in a docked configuration where the camera stand 302 is nested with the robot 301, for example, when not in use. It will be appreciated by those skilled in the art that the camera 326 and robot 301 may be separated from one another and positioned at any appropriate location during the surgical procedure, for example, as shown in FIGS. 1 and 2.



FIG. 4 illustrates a base 400 consistent with an exemplary embodiment of the present disclosure. Base 400 may be a portion of surgical robot system 300 and comprise cabinet 316. Cabinet 316 may house certain components of surgical robot system 300 including but not limited to a battery 402, a power distribution module 404, a platform interface board module 406, a computer 408, a handle 412, and a tablet drawer 414. The connections and relationship between these components is described in greater detail with respect to FIG. 5.



FIG. 5 illustrates a block diagram of certain components of an exemplary embodiment of surgical robot system 300. Surgical robot system 300 may comprise platform subsystem 502, computer subsystem 504, motion control subsystem 506, and tracking subsystem 532. Platform subsystem 502 may further comprise battery 402, power distribution module 404, platform interface board module 406, and tablet charging station 534. Computer subsystem 504 may further comprise computer 408, display 304, and speaker 536. Motion control subsystem 506 may further comprise driver circuit 508, motors 510, 512, 514, 516, 518, stabilizers 520, 522, 524, 526, end-effector 310, and controller 538. Tracking subsystem 532 may further comprise position sensor 540 and camera converter 542. System 300 may also comprise a foot pedal 544 and tablet 546.


Input power is supplied to system 300 via a power source 548 which may be provided to power distribution module 404. Power distribution module 404 receives input power and is configured to generate different power supply voltages that are provided to other modules, components, and subsystems of system 300. Power distribution module 404 may be configured to provide different voltage supplies to platform interface module 406, which may be provided to other components such as computer 408, display 304, speaker 536, driver 508 to, for example, power motors 512, 514, 516, 518 and end-effector 310, motor 510, ring 324, camera converter 542, and other components for system 300 for example, fans for cooling the electrical components within cabinet 316.


Power distribution module 404 may also provide power to other components such as tablet charging station 534 that may be located within tablet drawer 318. Tablet charging station 534 may be in wireless or wired communication with tablet 546 for charging table 546. Tablet 546 may be used by a surgeon consistent with the present disclosure and described herein.


Power distribution module 404 may also be connected to battery 402, which serves as temporary power source in the event that power distribution module 404 does not receive power from input power 548. At other times, power distribution module 404 may serve to charge battery 402 if necessary.


Other components of platform subsystem 502 may also include connector panel 320, control panel 322, and ring 324. Connector panel 320 may serve to connect different devices and components to system 300 and/or associated components and modules. Connector panel 320 may contain one or more ports that receive lines or connections from different components. For example, connector panel 320 may have a ground terminal port that may ground system 300 to other equipment, a port to connect foot pedal 544 to system 300, a port to connect to tracking subsystem 532, which may comprise position sensor 540, camera converter 542, and cameras 326 associated with camera stand 302. Connector panel 320 may also include other ports to allow USB, Ethernet, HDMI communications to other components, such as computer 408.


Control panel 322 may provide various buttons or indicators that control operation of system 300 and/or provide information regarding system 300. For example, control panel 322 may include buttons to power on or off system 300, lift or lower vertical column 312, and lift or lower stabilizers 520-526 that may be designed to engage casters 314 to lock system 300 from physically moving. Other buttons may stop system 300 in the event of an emergency, which may remove all motor power and apply mechanical brakes to stop all motion from occurring. Control panel 322 may also have indicators notifying the user of certain system conditions such as a line power indicator or status of charge for battery 402.


Ring 324 may be a visual indicator to notify the user of system 300 of different modes that system 300 is operating under and certain warnings to the user.


Computer subsystem 504 includes computer 408, display 304, and speaker 536. Computer 504 includes an operating system and software to operate system 300. Computer 504 may receive and process information from other components (for example, tracking subsystem 532, platform subsystem 502, and/or motion control subsystem 506) in order to display information to the user. Further, computer subsystem 504 may also include speaker 536 to provide audio to the user.


Tracking subsystem 532 may include position sensor 504 and converter 542. Tracking subsystem 532 may correspond to camera stand 302 including camera 326 as described with respect to FIG. 3. Position sensor 504 may be camera 326. Tracking subsystem may track the location of certain markers that are located on the different components of system 300 and/or instruments used by a user during a surgical procedure. This tracking may be conducted in a manner consistent with the present disclosure including the use of infrared technology that tracks the location of active or passive elements, such as LEDs or reflective markers, respectively. The location, orientation, and position of structures having these types of markers may be provided to computer 408 which may be shown to a user on display 304. For example, a surgical instrument 608 having these types of markers and tracked in this manner (which may be referred to as a navigational space) may be shown to a user in relation to a three dimensional image of a patient's anatomical structure.


Motion control subsystem 506 may be configured to physically move vertical column 312, upper arm 306, lower arm 308, or rotate end-effector 310. The physical movement may be conducted through the use of one or more motors 510-518. For example, motor 510 may be configured to vertically lift or lower vertical column 312. Motor 512 may be configured to laterally move upper arm 308 around a point of engagement with vertical column 312 as shown in FIG. 3. Motor 514 may be configured to laterally move lower arm 308 around a point of engagement with upper arm 308 as shown in FIG. 3. Motors 516 and 518 may be configured to move end-effector 310 in a manner such that one may control the roll and one may control the tilt, thereby providing multiple angles that end-effector 310 may be moved. These movements may be achieved by controller 538 which may control these movements through load cells disposed on end-effector 310 and activated by a user engaging these load cells to move system 300 in a desired manner.


Moreover, system 300 may provide for automatic movement of vertical column 312, upper arm 306, and lower arm 308 through a user indicating on display 304 (which may be a touchscreen input device) the location of a surgical instrument or component on a three dimensional image of the patient's anatomy on display 304. The user may initiate this automatic movement by stepping on foot pedal 544 or some other input means.



FIG. 6 illustrates a surgical robot system 600 consistent with an exemplary embodiment. Surgical robot system 600 may comprise end-effector 602, robot arm 604, guide tube 606, instrument 608, and robot base 610. Instrument tool 608 may be attached to a tracking array 612 including one or more tracking markers (such as markers 118) and have an associated trajectory 614. Trajectory 614 may represent a path of movement that instrument tool 608 is configured to travel once it is positioned through or secured in guide tube 606, for example, a path of insertion of instrument tool 608 into a patient. In an exemplary operation, robot base 610 may be configured to be in electronic communication with robot arm 604 and end-effector 602 so that surgical robot system 600 may assist a user (for example, a surgeon) in operating on the patient 210. Surgical robot system 600 may be consistent with previously described surgical robot system 100 and 300.


A tracking array 612 may be mounted on instrument 608 to monitor the location and orientation of instrument tool 608. The tracking array 612 may be attached to an instrument 608 and may comprise tracking markers 804. As best seen in FIG. 8, tracking markers 804 may be, for example, light emitting diodes and/or other types of reflective markers (e.g., markers 118 as described elsewhere herein). The tracking devices may be one or more line of sight devices associated with the surgical robot system. As an example, the tracking devices may be one or more cameras 200, 326 associated with the surgical robot system 100, 300 and may also track tracking array 612 for a defined domain or relative orientations of the instrument 608 in relation to the robot arm 604, the robot base 610, end-effector 602, and/or the patient 210. The tracking devices may be consistent with those structures described in connection with camera stand 302 and tracking subsystem 532.



FIGS. 7A, 7B, and 7C illustrate a top view, front view, and side view, respectively, of end-effector 602 consistent with an exemplary embodiment. End-effector 602 may comprise one or more tracking markers 702. Tracking markers 702 may be light emitting diodes or other types of active and passive markers, such as tracking markers 118 that have been previously described. In an exemplary embodiment, the tracking markers 702 are active infrared-emitting markers that are activated by an electrical signal (e.g., infrared light emitting diodes (LEDs)). Thus, tracking markers 702 may be activated such that the infrared markers 702 are visible to the camera 200, 326 or may be deactivated such that the infrared markers 702 are not visible to the camera 200, 326. Thus, when the markers 702 are active, the end-effector 602 may be controlled by the system 100, 300, 600, and when the markers 702 are deactivated, the end-effector 602 may be locked in position and unable to be moved by the system 100, 300, 600.


Markers 702 may be disposed on or within end-effector 602 in a manner such that the markers 702 are visible by one or more cameras 200, 326 or other tracking devices associated with the surgical robot system 100, 300, 600. The camera 200, 326 or other tracking devices may track end-effector 602 as it moves to different positions and viewing angles by following the movement of tracking markers 702. The location of markers 702 and/or end-effector 602 may be shown on a display 110, 304 associated with the surgical robot system 100, 300, 600, for example, display 110 as shown in FIG. 2 and/or display 304 shown in FIG. 3. This display 110, 304 may allow a user to ensure that end-effector 602 is in a desirable position in relation to robot arm 604, robot base 610, the patient 210, and/or the user.


For example, as shown in FIG. 7A, markers 702 may be placed around the surface of end-effector 602 so that a tracking device placed away from the surgical field 208 and facing toward the robot 102, 301 and the camera 200, 326 is able to view at least 3 of the markers 702 through a range of common orientations of the end-effector 602 relative to the tracking device. For example, distribution of markers 702 in this way allows end-effector 602 to be monitored by the tracking devices when end-effector 602 is translated and rotated in the surgical field 208.


In addition, in exemplary embodiments, end-effector 602 may be equipped with infrared (IR) receivers that can detect when an external camera 200, 326 is getting ready to read markers 702. Upon this detection, end-effector 602 may then illuminate markers 702. The detection by the IR receivers that the external camera 200, 326 is ready to read markers 702 may signal the need to synchronize a duty cycle of markers 702, which may be light emitting diodes, to an external camera 200, 326. This may also allow for lower power consumption by the robotic system as a whole, whereby markers 702 would only be illuminated at the appropriate time instead of being illuminated continuously. Further, in exemplary embodiments, markers 702 may be powered off to prevent interference with other navigation tools, such as different types of surgical instruments 608.



FIG. 8 depicts one type of surgical instrument 608 including a tracking array 612 and tracking markers 804. Tracking markers 804 may be of any type described herein including but not limited to light emitting diodes or reflective spheres. Markers 804 are monitored by tracking devices associated with the surgical robot system 100, 300, 600 and may be one or more of the line of sight cameras 200, 326. The cameras 200, 326 may track the location of instrument 608 based on the position and orientation of tracking array 612 and markers 804. A user, such as a surgeon 120, may orient instrument 608 in a manner so that tracking array 612 and markers 804 are sufficiently recognized by the tracking device or camera 200, 326 to display instrument 608 and markers 804 on, for example, display 110 of the exemplary surgical robot system.


The manner in which a surgeon 120 may place instrument 608 into guide tube 606 of the end-effector 602 and adjust the instrument 608 is evident in FIG. 8. The hollow tube or guide tube 114, 606 of the end-effector 112, 310, 602 is sized and configured to receive at least a portion of the surgical instrument 608. The guide tube 114, 606 is configured to be oriented by the robot arm 104 such that insertion and trajectory for the surgical instrument 608 is able to reach a desired anatomical target within or upon the body of the patient 210. The surgical instrument 608 may include at least a portion of a generally cylindrical instrument. Although a screw driver is exemplified as the surgical tool 608, it will be appreciated that any suitable surgical tool 608 may be positioned by the end-effector 602. By way of example, the surgical instrument 608 may include one or more of a guide wire, cannula, a retractor, a drill, a reamer, a screw driver, an insertion tool, a removal tool, or the like. Although the hollow tube 114, 606 is generally shown as having a cylindrical configuration, it will be appreciated by those of skill in the art that the guide tube 114, 606 may have any suitable shape, size and configuration desired to accommodate the surgical instrument 608 and access the surgical site.



FIGS. 9A-9C illustrate end-effector 602 and a portion of robot arm 604 consistent with an exemplary embodiment. End-effector 602 may further comprise body 1202 and clamp 1204. Clamp 1204 may comprise handle 1206, balls 1208, spring 1210, and lip 1212. Robot arm 604 may further comprise depressions 1214, mounting plate 1216, lip 1218, and magnets 1220.


End-effector 602 may mechanically interface and/or engage with the surgical robot system and robot arm 604 through one or more couplings. For example, end-effector 602 may engage with robot arm 604 through a locating coupling and/or a reinforcing coupling. Through these couplings, end-effector 602 may fasten with robot arm 604 outside a flexible and sterile barrier. In an exemplary embodiment, the locating coupling may be a magnetically kinematic mount and the reinforcing coupling may be a five bar over center clamping linkage.


With respect to the locating coupling, robot arm 604 may comprise mounting plate 1216, which may be non-magnetic material, one or more depressions 1214, lip 1218, and magnets 1220. Magnet 1220 is mounted below each of depressions 1214. Portions of clamp 1204 may comprise magnetic material and be attracted by one or more magnets 1220. Through the magnetic attraction of clamp 1204 and robot arm 604, balls 1208 become seated into respective depressions 1214. For example, balls 1208 as shown in FIG. 9B would be seated in depressions 1214 as shown in FIG. 9A. This seating may be considered a magnetically-assisted kinematic coupling. Magnets 1220 may be configured to be strong enough to support the entire weight of end-effector 602 regardless of the orientation of end-effector 602. The locating coupling may be any style of kinematic mount that uniquely restrains six degrees of freedom.


With respect to the reinforcing coupling, portions of clamp 1204 may be configured to be a fixed ground link and as such clamp 1204 may serve as a five bar linkage. Closing clamp handle 1206 may fasten end-effector 602 to robot arm 604 as lip 1212 and lip 1218 engage clamp 1204 in a manner to secure end-effector 602 and robot arm 604. When clamp handle 1206 is closed, spring 1210 may be stretched or stressed while clamp 1204 is in a locked position. The locked position may be a position that provides for linkage past center. Because of a closed position that is past center, the linkage will not open absent a force applied to clamp handle 1206 to release clamp 1204. Thus, in a locked position, end-effector 602 may be robustly secured to robot arm 604.


Spring 1210 may be a curved beam in tension. Spring 1210 may be comprised of a material that exhibits high stiffness and high yield strain such as virgin PEEK (poly-ether-ether-ketone). The linkage between end-effector 602 and robot arm 604 may provide for a sterile barrier between end-effector 602 and robot arm 604 without impeding fastening of the two couplings.


The reinforcing coupling may be a linkage with multiple spring members. The reinforcing coupling may latch with a cam or friction based mechanism. The reinforcing coupling may also be a sufficiently powerful electromagnet that will support fastening end-effector 102 to robot arm 604. The reinforcing coupling may be a multi-piece collar completely separate from either end-effector 602 and/or robot arm 604 that slips over an interface between end-effector 602 and robot arm 604 and tightens with a screw mechanism, an over center linkage, or a cam mechanism.


Referring to FIGS. 10 and 11, prior to or during a surgical procedure, certain registration procedures may be conducted to track objects and a target anatomical structure of the patient 210 both in a navigation space and an image space. To conduct such registration, a registration system 1400 may be used as illustrated in FIG. 10.


To track the position of the patient 210, a patient tracking device 116 may include a patient fixation instrument 1402 to be secured to a rigid anatomical structure of the patient 210 and a dynamic reference base (DRB) 1404 may be securely attached to the patient fixation instrument 1402. For example, patient fixation instrument 1402 may be inserted into opening 1406 of dynamic reference base 1404. Dynamic reference base 1404 may contain markers 1408 that are visible to tracking devices, such as tracking subsystem 532. These markers 1408 may be optical markers or reflective spheres, such as tracking markers 118, as previously discussed herein.


Patient fixation instrument 1402 is attached to a rigid anatomy of the patient 210 and may remain attached throughout the surgical procedure. In an exemplary embodiment, patient fixation instrument 1402 is attached to a rigid area of the patient 210, for example, a bone that is located away from the targeted anatomical structure subject to the surgical procedure. In order to track the targeted anatomical structure, dynamic reference base 1404 is associated with the targeted anatomical structure through the use of a registration fixture that is temporarily placed on or near the targeted anatomical structure in order to register the dynamic reference base 1404 with the location of the targeted anatomical structure.


A registration fixture 1410 is attached to patient fixation instrument 1402 through the use of a pivot arm 1412. Pivot arm 1412 is attached to patient fixation instrument 1402 by inserting patient fixation instrument 1402 through an opening 1414 of registration fixture 1410. Pivot arm 1412 is attached to registration fixture 1410 by, for example, inserting a knob 1416 through an opening 1418 of pivot arm 1412.


Using pivot arm 1412, registration fixture 1410 may be placed over the targeted anatomical structure and its location may be determined in an image space and navigation space using tracking markers 1420 and/or fiducials 1422 on registration fixture 1410. Registration fixture 1410 may contain a collection of markers 1420 that are visible in a navigational space (for example, markers 1420 may be detectable by tracking subsystem 532). Tracking markers 1420 may be optical markers visible in infrared light as previously described herein. Registration fixture 1410 may also contain a collection of fiducials 1422, for example, such as bearing balls, that are visible in an imaging space (for example, a three dimension CT image). As described in greater detail with respect to FIG. 11, using registration fixture 1410, the targeted anatomical structure may be associated with dynamic reference base 1404 thereby allowing depictions of objects in the navigational space to be overlaid on images of the anatomical structure. Dynamic reference base 1404, located at a position away from the targeted anatomical structure, may become a reference point thereby allowing removal of registration fixture 1410 and/or pivot arm 1412 from the surgical area.



FIG. 11 provides an exemplary method 1500 for registration consistent with the present disclosure. Method 1500 begins at step 1502 wherein a graphical representation (or image(s)) of the targeted anatomical structure may be imported into system 100, 300600, for example computer 408. The graphical representation may be three dimensional CT or a fluoroscope scan of the targeted anatomical structure of the patient 210 which includes registration fixture 1410 and a detectable imaging pattern of fiducials 1420.


At step 1504, an imaging pattern of fiducials 1420 is detected and registered in the imaging space and stored in computer 408. Optionally, at this time at step 1506, a graphical representation of the registration fixture 1410 may be overlaid on the images of the targeted anatomical structure.


At step 1508, a navigational pattern of registration fixture 1410 is detected and registered by recognizing markers 1420. Markers 1420 may be optical markers that are recognized in the navigation space through infrared light by tracking subsystem 532 via position sensor 540. Thus, the location, orientation, and other information of the targeted anatomical structure is registered in the navigation space. Therefore, registration fixture 1410 may be recognized in both the image space through the use of fiducials 1422 and the navigation space through the use of markers 1420. At step 1510, the registration of registration fixture 1410 in the image space is transferred to the navigation space. This transferal is done, for example, by using the relative position of the imaging pattern of fiducials 1422 compared to the position of the navigation pattern of markers 1420.


At step 1512, registration of the navigation space of registration fixture 1410 (having been registered with the image space) is further transferred to the navigation space of dynamic registration array 1404 attached to patient fixture instrument 1402. Thus, registration fixture 1410 may be removed and dynamic reference base 1404 may be used to track the targeted anatomical structure in both the navigation and image space because the navigation space is associated with the image space.


At steps 1514 and 1516, the navigation space may be overlaid on the image space and objects with markers visible in the navigation space (for example, surgical instruments 608 with optical markers 804). The objects may be tracked through graphical representations of the surgical instrument 608 on the images of the targeted anatomical structure.



FIGS. 12A-12B illustrate imaging devices 1304 that may be used in conjunction with robot systems 100, 300, 600 to acquire pre-operative, intra-operative, post-operative, and/or real-time image data of patient 210. Any appropriate subject matter may be imaged for any appropriate procedure using the imaging system 1304. The imaging system 1304 may be any imaging device such as imaging device 1306 and/or a C-arm 1308 device. It may be desirable to take x-rays of patient 210 from a number of different positions, without the need for frequent manual repositioning of patient 210 which may be required in an x-ray system. As illustrated in FIG. 12A, the imaging system 1304 may be in the form of a C-arm 1308 that includes an elongated C-shaped member terminating in opposing distal ends 1312 of the “C” shape. C-shaped member 1130 may further comprise an x-ray source 1314 and an image receptor 1316. The space within C-arm 1308 of the arm may provide room for the physician to attend to the patient substantially free of interference from x-ray support structure 1318. As illustrated in FIG. 12B, the imaging system may include imaging device 1306 having a gantry housing 1324 attached to a support structure imaging device support structure 1328, such as a wheeled mobile cart 1330 with wheels 1332, which may enclose an image capturing portion, not illustrated. The image capturing portion may include an x-ray source and/or emission portion and an x-ray receiving and/or image receiving portion, which may be disposed about one hundred and eighty degrees from each other and mounted on a rotor (not illustrated) relative to a track of the image capturing portion. The image capturing portion may be operable to rotate three hundred and sixty degrees during image acquisition. The image capturing portion may rotate around a central point and/or axis, allowing image data of patient 210 to be acquired from multiple directions or in multiple planes. Although certain imaging systems 1304 are exemplified herein, it will be appreciated that any suitable imaging system may be selected by one of ordinary skill in the art.


Turning now to FIGS. 13A-13C, the surgical robot system 100, 300, 600 relies on accurate positioning of the end-effector 112, 602, surgical instruments 608, and/or the patient 210 (e.g., patient tracking device 116) relative to the desired surgical area. In the embodiments shown in FIGS. 13A-13C, the tracking markers 118, 804 are rigidly attached to a portion of the instrument 608 and/or end-effector 112.



FIG. 13A depicts part of the surgical robot system 100 with the robot 102 including base 106, robot arm 104, and end-effector 112. The other elements, not illustrated, such as the display, cameras, etc. may also be present as described herein. FIG. 13B depicts a close-up view of the end-effector 112 with guide tube 114 and a plurality of tracking markers 118 rigidly affixed to the end-effector 112. In this embodiment, the plurality of tracking markers 118 are attached to the guide tube 112. FIG. 13C depicts an instrument 608 (in this case, a probe 608A) with a plurality of tracking markers 804 rigidly affixed to the instrument 608. As described elsewhere herein, the instrument 608 could include any suitable surgical instrument, such as, but not limited to, guide wire, cannula, a retractor, a drill, a reamer, a screw driver, an insertion tool, a removal tool, or the like.


When tracking an instrument 608, end-effector 112, or other object to be tracked in 3D, an array of tracking markers 118, 804 may be rigidly attached to a portion of the tool 608 or end-effector 112. Preferably, the tracking markers 118, 804 are attached such that the markers 118, 804 are out of the way (e.g., not impeding the surgical operation, visibility, etc.). The markers 118, 804 may be affixed to the instrument 608, end-effector 112, or other object to be tracked, for example, with an array 612. Usually three or four markers 118, 804 are used with an array 612. The array 612 may include a linear section, a cross piece, and may be asymmetric such that the markers 118, 804 are at different relative positions and locations with respect to one another. For example, as shown in FIG. 13C, a probe 608A with a 4-marker tracking array 612 is shown, and FIG. 13B depicts the end-effector 112 with a different 4-marker tracking array 612.


In FIG. 13C, the tracking array 612 functions as the handle 620 of the probe 608A. Thus, the four markers 804 are attached to the handle 620 of the probe 608A, which is out of the way of the shaft 622 and tip 624. Stereophotogrammetric tracking of these four markers 804 allows the instrument 608 to be tracked as a rigid body and for the tracking system 100, 300, 600 to precisely determine the position of the tip 624 and the orientation of the shaft 622 while the probe 608A is moved around in front of tracking cameras 200, 326.


To enable automatic tracking of one or more tools 608, end-effector 112, or other object to be tracked in 3D (e.g., multiple rigid bodies), the markers 118, 804 on each tool 608, end-effector 112, or the like, are arranged asymmetrically with a known inter-marker spacing. The reason for asymmetric alignment is so that it is unambiguous which marker 118, 804 corresponds to a particular location on the rigid body and whether markers 118, 804 are being viewed from the front or back, i.e., mirrored. For example, if the markers 118, 804 were arranged in a square on the tool 608 or end-effector 112, it would be unclear to the system 100, 300, 600 which marker 118, 804 corresponded to which corner of the square. For example, for the probe 608A, it would be unclear which marker 804 was closest to the shaft 622. Thus, it would be unknown which way the shaft 622 was extending from the array 612. Accordingly, each array 612 and thus each tool 608, end-effector 112, or other object to be tracked should have a unique marker pattern to allow it to be distinguished from other tools 608 or other objects being tracked. Asymmetry and unique marker patterns allow the system 100, 300, 600 to detect individual markers 118, 804 then to check the marker spacing against a stored template to determine which tool 608, end effector 112, or other object they represent. Detected markers 118, 804 can then be sorted automatically and assigned to each tracked object in the correct order. Without this information, rigid body calculations could not then be performed to extract key geometric information, for example, such as tool tip 624 and alignment of the shaft 622, unless the user manually specified which detected marker 118, 804 corresponded to which position on each rigid body. These concepts are commonly known to those skilled in the methods of 3D optical tracking.


Turning now to FIGS. 14A-14D, an alternative version of an end-effector 912 with moveable tracking markers 918A-918D is shown. In FIG. 14A, an array with moveable tracking markers 918A-918D are shown in a first configuration, and in FIG. 14B the moveable tracking markers 918A-918D are shown in a second configuration, which is angled relative to the first configuration. FIG. 14C shows the template of the tracking markers 918A-918D, for example, as seen by the cameras 200, 326 in the first configuration of FIG. 14A; and FIG. 14D shows the template of tracking markers 918A-918D, for example, as seen by the cameras 200, 326 in the second configuration of FIG. 14B.


In this embodiment, 4-marker array tracking is contemplated wherein the markers 918A-918D are not all in fixed position relative to the rigid body and instead, one or more of the array markers 918A-918D can be adjusted, for example, during testing, to give updated information about the rigid body that is being tracked without disrupting the process for automatic detection and sorting of the tracked markers 918A-918D.


When tracking any tool, such as a guide tube 914 connected to the end effector 912 of a robot system 100, 300, 600, the tracking array's primary purpose is to update the position of the end effector 912 in the camera coordinate system. When using the rigid system, for example, as shown in FIG. 13B, the array 612 of reflective markers 118 rigidly extend from the guide tube 114. Because the tracking markers 118 are rigidly connected, knowledge of the marker locations in the camera coordinate system also provides exact location of the centerline, tip, and tail of the guide tube 114 in the camera coordinate system. Typically, information about the position of the end effector 112 from such an array 612 and information about the location of a target trajectory from another tracked source are used to calculate the required moves that must be input for each axis of the robot 102 that will move the guide tube 114 into alignment with the trajectory and move the tip to a particular location along the trajectory vector.


Sometimes, the desired trajectory is in an awkward or unreachable location, but if the guide tube 114 could be swiveled, it could be reached. For example, a very steep trajectory pointing away from the base 106 of the robot 102 might be reachable if the guide tube 114 could be swiveled upward beyond the limit of the pitch (wrist up-down angle) axis, but might not be reachable if the guide tube 114 is attached parallel to the plate connecting it to the end of the wrist. To reach such a trajectory, the base 106 of the robot 102 might be moved or a different end effector 112 with a different guide tube attachment might be exchanged with the working end effector. Both of these solutions may be time consuming and cumbersome.


As best seen in FIGS. 14A and 14B, if the array 908 is configured such that one or more of the markers 918A-918D are not in a fixed position and instead, one or more of the markers 918A-918D can be adjusted, swiveled, pivoted, or moved, the robot 102 can provide updated information about the object being tracked without disrupting the detection and tracking process. For example, one of the markers 918A-918D may be fixed in position and the other markers 918A-918D may be moveable; two of the markers 918A-918D may be fixed in position and the other markers 918A-918D may be moveable; three of the markers 918A-918D may be fixed in position and the other marker 918A-918D may be moveable; or all of the markers 918A-918D may be moveable.


In the embodiment shown in FIGS. 14A and 14B, markers 918A, 918B are rigidly connected directly to a base 906 of the end-effector 912, and markers 918C, 918D are rigidly connected to the tube 914. Similar to array 612, array 908 may be provided to attach the markers 918A-918D to the end-effector 912, instrument 608, or other object to be tracked. In this case, however, the array 908 is comprised of a plurality of separate components. For example, markers 918A, 918B may be connected to the base 906 with a first array 908A, and markers 918C, 918D may be connected to the guide tube 914 with a second array 908B. Marker 918A may be affixed to a first end of the first array 908A and marker 918B may be separated a linear distance and affixed to a second end of the first array 908A. While first array 908 is substantially linear, second array 908B has a bent or V-shaped configuration, with respective root ends, connected to the guide tube 914, and diverging therefrom to distal ends in a V-shape with marker 918C at one distal end and marker 918D at the other distal end. Although specific configurations are exemplified herein, it will be appreciated that other asymmetric designs including different numbers and types of arrays 908A, 908B and different arrangements, numbers, and types of markers 918A-918D are contemplated.


The guide tube 914 may be moveable, swivelable, or pivotable relative to the base 906, for example, across a hinge 920 or other connector to the base 906. Thus, markers 918C, 918D are moveable such that when the guide tube 914 pivots, swivels, or moves, markers 918C, 918D also pivot, swivel, or move. As best seen in FIG. 14A, guide tube 914 has a longitudinal axis 916 which is aligned in a substantially normal or vertical orientation such that markers 918A-918D have a first configuration. Turning now to FIG. 14B, the guide tube 914 is pivoted, swiveled, or moved such that the longitudinal axis 916 is now angled relative to the vertical orientation such that markers 918A-918D have a second configuration, different from the first configuration.


In contrast to the embodiment described for FIGS. 14A-14D, if a swivel existed between the guide tube 914 and the arm 104 (e.g., the wrist attachment) with all four markers 918A-918D remaining attached rigidly to the guide tube 914 and this swivel was adjusted by the user, the robotic system 100, 300, 600 would not be able to automatically detect that the guide tube 914 orientation had changed. The robotic system 100, 300, 600 would track the positions of the marker array 908 and would calculate incorrect robot axis moves assuming the guide tube 914 was attached to the wrist (the robot arm 104) in the previous orientation. By keeping one or more markers 918A-918D (e.g., two markers 918C, 918D) rigidly on the tube 914 and one or more markers 918A-918D (e.g., two markers 918A, 918B) across the swivel, automatic detection of the new position becomes possible and correct robot moves are calculated based on the detection of a new tool or end-effector 112, 912 on the end of the robot arm 104.


One or more of the markers 918A-918D are configured to be moved, pivoted, swiveled, or the like according to any suitable means. For example, the markers 918A-918D may be moved by a hinge 920, such as a clamp, spring, lever, slide, toggle, or the like, or any other suitable mechanism for moving the markers 918A-918D individually or in combination, moving the arrays 908A, 908B individually or in combination, moving any portion of the end-effector 912 relative to another portion, or moving any portion of the tool 608 relative to another portion.


As shown in FIGS. 14A and 14B, the array 908 and guide tube 914 may become reconfigurable by simply loosening the clamp or hinge 920, moving part of the array 908A, 908B relative to the other part 908A, 908B, and retightening the hinge 920 such that the guide tube 914 is oriented in a different position. For example, two markers 918C, 918D may be rigidly interconnected with the tube 914 and two markers 918A, 918B may be rigidly interconnected across the hinge 920 to the base 906 of the end-effector 912 that attaches to the robot arm 104. The hinge 920 may be in the form of a clamp, such as a wing nut or the like, which can be loosened and retightened to allow the user to quickly switch between the first configuration (FIG. 14A) and the second configuration (FIG. 14B).


The cameras 200, 326 detect the markers 918A-918D, for example, in one of the templates identified in FIGS. 14C and 14D. If the array 908 is in the first configuration (FIG. 14A) and tracking cameras 200, 326 detect the markers 918A-918D, then the tracked markers match Array Template 1 as shown in FIG. 14C. If the array 908 is the second configuration (FIG. 14B) and tracking cameras 200, 326 detect the same markers 918A-918D, then the tracked markers match Array Template 2 as shown in FIG. 14D. Array Template 1 and Array Template 2 are recognized by the system 100, 300, 600 as two distinct tools, each with its own uniquely defined spatial relationship between guide tube 914, markers 918A-918D, and robot attachment. The user could therefore adjust the position of the end-effector 912 between the first and second configurations without notifying the system 100, 300, 600 of the change and the system 100, 300, 600 would appropriately adjust the movements of the robot 102 to stay on trajectory.


In this embodiment, there are two assembly positions in which the marker array matches unique templates that allow the system 100, 300, 600 to recognize the assembly as two different tools or two different end effectors. In any position of the swivel between or outside of these two positions (namely, Array Template 1 and Array Template 2 shown in FIGS. 14C and 14D, respectively), the markers 918A-918D would not match any template and the system 100, 300, 600 would not detect any array present despite individual markers 918A-918D being detected by cameras 200, 326, with the result being the same as if the markers 918A-918D were temporarily blocked from view of the cameras 200, 326. It will be appreciated that other array templates may exist for other configurations, for example, identifying different instruments 608 or other end-effectors 112, 912, etc.


In the embodiment described, two discrete assembly positions are shown in FIGS. 14A and 14B. It will be appreciated, however, that there could be multiple discrete positions on a swivel joint, linear joint, combination of swivel and linear joints, pegboard, or other assembly where unique marker templates may be created by adjusting the position of one or more markers 918A-918D of the array relative to the others, with each discrete position matching a particular template and defining a unique tool 608 or end-effector 112, 912 with different known attributes. In addition, although exemplified for end effector 912, it will be appreciated that moveable and fixed markers 918A-918D may be used with any suitable instrument 608 or other object to be tracked.


When using an external 3D tracking system 100, 300, 600 to track a full rigid body array of three or more markers attached to a robot's end effector 112 (for example, as depicted in FIGS. 13A and 13B), it is possible to directly track or to calculate the 3D position of every section of the robot 102 in the coordinate system of the cameras 200, 326. The geometric orientations of joints relative to the tracker are known by design, and the linear or angular positions of joints are known from encoders for each motor of the robot 102, fully defining the 3D positions of all of the moving parts from the end effector 112 to the base 116. Similarly, if a tracker were mounted on the base 106 of the robot 102 (not shown), it is likewise possible to track or calculate the 3D position of every section of the robot 102 from base 106 to end effector 112 based on known joint geometry and joint positions from each motor's encoder.


In some situations, it may be desirable to track the positions of all segments of the robot 102 from fewer than three markers 118 rigidly attached to the end effector 112. Specifically, if a tool 608 is introduced into the guide tube 114, it may be desirable to track full rigid body motion of the robot 902 with only one additional marker 118 being tracked.


Turning now to FIGS. 15A-15E, an alternative version of an end-effector 1012 having only a single tracking marker 1018 is shown. End-effector 1012 may be similar to the other end-effectors described herein, and may include a guide tube 1014 extending along a longitudinal axis 1016. A single tracking marker 1018, similar to the other tracking markers described herein, may be rigidly affixed to the guide tube 1014. This single marker 1018 can serve the purpose of adding missing degrees of freedom to allow full rigid body tracking and/or can serve the purpose of acting as a surveillance marker to ensure that assumptions about robot and camera positioning are valid.


The single tracking marker 1018 may be attached to the robotic end effector 1012 as a rigid extension to the end effector 1012 that protrudes in any convenient direction and does not obstruct the surgeon's view. The tracking marker 1018 may be affixed to the guide tube 1014 or any other suitable location of on the end-effector 1012. When affixed to the guide tube 1014, the tracking marker 1018 may be positioned at a location between first and second ends of the guide tube 1014. For example, in FIG. 15A, the single tracking marker 1018 is shown as a reflective sphere mounted on the end of a narrow shaft 1017 that extends forward from the guide tube 1014 and is positioned longitudinally above a mid-point of the guide tube 1014 and below the entry of the guide tube 1014. This position allows the marker 1018 to be generally visible by cameras 200, 326 but also would not obstruct vision of the surgeon 120 or collide with other tools or objects in the vicinity of surgery. In addition, the guide tube 1014 with the marker 1018 in this position is designed for the marker array on any tool 608 introduced into the guide tube 1014 to be visible at the same time as the single marker 1018 on the guide tube 1014 is visible.


As shown in FIG. 15B, when a snugly fitting tool or instrument 608 is placed within the guide tube 1014, the instrument 608 becomes mechanically constrained in 4 of 6 degrees of freedom. That is, the instrument 608 cannot be rotated in any direction except about the longitudinal axis 1016 of the guide tube 1014 and the instrument 608 cannot be translated in any direction except along the longitudinal axis 1016 of the guide tube 1014. In other words, the instrument 608 can only be translated along and rotated about the centerline of the guide tube 1014. If two more parameters are known, such as (1) an angle of rotation about the longitudinal axis 1016 of the guide tube 1014; and (2) a position along the guide tube 1014, then the position of the end effector 1012 in the camera coordinate system becomes fully defined.


Referring now to FIG. 15C, the system 100, 300, 600 should be able to know when a tool 608 is actually positioned inside of the guide tube 1014 and is not instead outside of the guide tube 1014 and just somewhere in view of the cameras 200, 326. The tool 608 has a longitudinal axis or centerline 616 and an array 612 with a plurality of tracked markers 804. The rigid body calculations may be used to determine where the centerline 616 of the tool 608 is located in the camera coordinate system based on the tracked position of the array 612 on the tool 608.


The fixed normal (perpendicular) distance DF from the single marker 1018 to the centerline or longitudinal axis 1016 of the guide tube 1014 is fixed and is known geometrically, and the position of the single marker 1018 can be tracked. Therefore, when a detected distance DD from tool centerline 616 to single marker 1018 matches the known fixed distance DF from the guide tube centerline 1016 to the single marker 1018, it can be determined that the tool 608 is either within the guide tube 1014 (centerlines 616, 1016 of tool 608 and guide tube 1014 coincident) or happens to be at some point in the locus of possible positions where this distance DD matches the fixed distance Dr. For example, in FIG. 15C, the normal detected distance DD from tool centerline 616 to the single marker 1018 matches the fixed distance DF from guide tube centerline 1016 to the single marker 1018 in both frames of data (tracked marker coordinates) represented by the transparent tool 608 in two positions, and thus, additional considerations may be needed to determine when the tool 608 is located in the guide tube 1014.


Turning now to FIG. 15D, programmed logic can be used to look for frames of tracking data in which the detected distance DD from tool centerline 616 to single marker 1018 remains fixed at the correct length despite the tool 608 moving in space by more than some minimum distance relative to the single sphere 1018 to satisfy the condition that the tool 608 is moving within the guide tube 1014. For example, a first frame F1 may be detected with the tool 608 in a first position and a second frame F2 may be detected with the tool 608 in a second position (namely, moved linearly with respect to the first position). The markers 804 on the tool array 612 may move by more than a given amount (e.g., more than 5 mm total) from the first frame F1 to the second frame F2. Even with this movement, the detected distance DD from the tool centerline vector C′ to the single marker 1018 is substantially identical in both the first frame F1 and the second frame F2.


Logistically, the surgeon 120 or user could place the tool 608 within the guide tube 1014 and slightly rotate it or slide it down into the guide tube 1014 and the system 100, 300, 600 would be able to detect that the tool 608 is within the guide tube 1014 from tracking of the five markers (four markers 804 on tool 608 plus single marker 1018 on guide tube 1014). Knowing that the tool 608 is within the guide tube 1014, all 6 degrees of freedom may be calculated that define the position and orientation of the robotic end effector 1012 in space. Without the single marker 1018, even if it is known with certainty that the tool 608 is within the guide tube 1014, it is unknown where the guide tube 1014 is located along the tool's centerline vector C′ and how the guide tube 1014 is rotated relative to the centerline vector C′.


With emphasis on FIG. 15E, the presence of the single marker 1018 being tracked as well as the four markers 804 on the tool 608, it is possible to construct the centerline vector C′ of the guide tube 1014 and tool 608 and the normal vector through the single marker 1018 and through the centerline vector C′. This normal vector has an orientation that is in a known orientation relative to the forearm of the robot distal to the wrist (in this example, oriented parallel to that segment) and intersects the centerline vector C′ at a specific fixed position. For convenience, three mutually orthogonal vectors k′, j′, i′ can be constructed, as shown in FIG. 15E, defining rigid body position and orientation of the guide tube 1014. One of the three mutually orthogonal vectors k′ is constructed from the centerline vector C′, the second vector j′ is constructed from the normal vector through the single marker 1018, and the third vector i′ is the vector cross product of the first and second vectors k′, j′. The robot's joint positions relative to these vectors k′, j′, i′ are known and fixed when all joints are at zero, and therefore rigid body calculations can be used to determine the location of any section of the robot relative to these vectors k′, j′, i′ when the robot is at a home position. During robot movement, if the positions of the tool markers 804 (while the tool 608 is in the guide tube 1014) and the position of the single marker 1018 are detected from the tracking system, and angles/linear positions of each joint are known from encoders, then position and orientation of any section of the robot can be determined.


In some embodiments, it may be useful to fix the orientation of the tool 608 relative to the guide tube 1014. For example, the end effector guide tube 1014 may be oriented in a particular position about its axis 1016 to allow machining or implant positioning. Although the orientation of anything attached to the tool 608 inserted into the guide tube 1014 is known from the tracked markers 804 on the tool 608, the rotational orientation of the guide tube 1014 itself in the camera coordinate system is unknown without the additional tracking marker 1018 (or multiple tracking markers in other embodiments) on the guide tube 1014. This marker 1018 provides essentially a “clock position” from −180° to +180° based on the orientation of the marker 1018 relative to the centerline vector C′. Thus, the single marker 1018 can provide additional degrees of freedom to allow full rigid body tracking and/or can act as a surveillance marker to ensure that assumptions about the robot and camera positioning are valid.



FIG. 16 is a block diagram of a method 1100 for navigating and moving the end-effector 1012 (or any other end-effector described herein) of the robot 102 to a desired target trajectory. Another use of the single marker 1018 on the robotic end effector 1012 or guide tube 1014 is as part of the method 1100 enabling the automated safe movement of the robot 102 without a full tracking array attached to the robot 102. This method 1100 functions when the tracking cameras 200, 326 do not move relative to the robot 102 (i.e., they are in a fixed position), the tracking system's coordinate system and robot's coordinate system are co-registered, and the robot 102 is calibrated such that the position and orientation of the guide tube 1014 can be accurately determined in the robot's Cartesian coordinate system based only on the encoded positions of each robotic axis.


For this method 1100, the coordinate systems of the tracker and the robot must be co-registered, meaning that the coordinate transformation from the tracking system's Cartesian coordinate system to the robot's Cartesian coordinate system is needed. For convenience, this coordinate transformation can be a 4×4 matrix of translations and rotations that is well known in the field of robotics. This transformation will be termed Tcr to refer to “transformation—camera to robot”. Once this transformation is known, any new frame of tracking data, which is received as x,y,z coordinates in vector form for each tracked marker, can be multiplied by the 4×4 matrix and the resulting x,y,z coordinates will be in the robot's coordinate system. To obtain Tcr, a full tracking array on the robot is tracked while it is rigidly attached to the robot at a location that is known in the robot's coordinate system, then known rigid body methods are used to calculate the transformation of coordinates. It should be evident that any tool 608 inserted into the guide tube 1014 of the robot 102 can provide the same rigid body information as a rigidly attached array when the additional marker 1018 is also read. That is, the tool 608 need only be inserted to any position within the guide tube 1014 and at any rotation within the guide tube 1014, not to a fixed position and orientation. Thus, it is possible to determine Tcr by inserting any tool 608 with a tracking array 612 into the guide tube 1014 and reading the tool's array 612 plus the single marker 1018 of the guide tube 1014 while at the same time determining from the encoders on each axis the current location of the guide tube 1014 in the robot's coordinate system.


Logic for navigating and moving the robot 102 to a target trajectory is provided in the method 1100 of FIG. 16. Before entering the loop 1102, it is assumed that the transformation Tcr was previously stored. Thus, before entering loop 1102, in step 1104, after the robot base 106 is secured, greater than or equal to one frame of tracking data of a tool inserted in the guide tube while the robot is static is stored; and in step 1106, the transformation of robot guide tube position from camera coordinates to robot coordinates Tcr is calculated from this static data and previous calibration data. Tcr should remain valid as long as the cameras 200, 326 do not move relative to the robot 102. If the cameras 200, 326 move relative to the robot 102, and Tcr needs to be re-obtained, the system 100, 300, 600 can be made to prompt the user to insert a tool 608 into the guide tube 1014 and then automatically perform the necessary calculations.


In the flowchart of method 1100, each frame of data collected consists of the tracked position of the DRB 1404 on the patient 210, the tracked position of the single marker 1018 on the end effector 1014, and a snapshot of the positions of each robotic axis. From the positions of the robot's axes, the location of the single marker 1018 on the end effector 1012 is calculated. This calculated position is compared to the actual position of the marker 1018 as recorded from the tracking system. If the values agree, it can be assured that the robot 102 is in a known location. The transformation Tcr is applied to the tracked position of the DRB 1404 so that the target for the robot 102 can be provided in terms of the robot's coordinate system. The robot 102 can then be commanded to move to reach the target.


After steps 1104, 1106, loop 1102 includes step 1108 receiving rigid body information for DRB 1404 from the tracking system; step 1110 transforming target tip and trajectory from image coordinates to tracking system coordinates; and step 1112 transforming target tip and trajectory from camera coordinates to robot coordinates (apply Tcr). Loop 1102 further includes step 1114 receiving a single stray marker position for robot from tracking system; and step 1116 transforming the single stray marker from tracking system coordinates to robot coordinates (apply stored Tcr). Loop 1102 also includes step 1118 determining current location of the single robot marker 1018 in the robot coordinate system from forward kinematics. The information from steps 1116 and 1118 is used to determine step 1120 whether the stray marker coordinates from transformed tracked position agree with the calculated coordinates being less than a given tolerance. If yes, proceed to step 1122, calculate and apply robot move to target x, y, z and trajectory. If no, proceed to step 1124, halt and require full array insertion into guide tube 1014 before proceeding; step 1126 after array is inserted, recalculate Tcr; and then proceed to repeat steps 1108, 1114, and 1118.


This method 1100 has advantages over a method in which the continuous monitoring of the single marker 1018 to verify the location is omitted. Without the single marker 1018, it would still be possible to determine the position of the end effector 1012 using Tcr and to send the end-effector 1012 to a target location but it would not be possible to verify that the robot 102 was actually in the expected location. For example, if the cameras 200, 326 had been bumped and Tcr was no longer valid, the robot 102 would move to an erroneous location. For this reason, the single marker 1018 provides value with regard to safety.


For a given fixed position of the robot 102, it is theoretically possible to move the tracking cameras 200, 326 to a new location in which the single tracked marker 1018 remains unmoved since it is a single point, not an array. In such a case, the system 100, 300, 600 would not detect any error since there would be agreement in the calculated and tracked locations of the single marker 1018. However, once the robot's axes caused the guide tube 1012 to move to a new location, the calculated and tracked positions would disagree and the safety check would be effective.


The term “surveillance marker” may be used, for example, in reference to a single marker that is in a fixed location relative to the DRB 1404. In this instance, if the DRB 1404 is bumped or otherwise dislodged, the relative location of the surveillance marker changes and the surgeon 120 can be alerted that there may be a problem with navigation. Similarly, in the embodiments described herein, with a single marker 1018 on the robot's guide tube 1014, the system 100, 300, 600 can continuously check whether the cameras 200, 326 have moved relative to the robot 102. If registration of the tracking system's coordinate system to the robot's coordinate system is lost, such as by cameras 200, 326 being bumped or malfunctioning or by the robot malfunctioning, the system 100, 300, 600 can alert the user and corrections can be made. Thus, this single marker 1018 can also be thought of as a surveillance marker for the robot 102.


It should be clear that with a full array permanently mounted on the robot 102 (e.g., the plurality of tracking markers 702 on end-effector 602 shown in FIGS. 7A-7C) such functionality of a single marker 1018 as a robot surveillance marker is not needed because it is not required that the cameras 200, 326 be in a fixed position relative to the robot 102, and Tcr is updated at each frame based on the tracked position of the robot 102. Reasons to use a single marker 1018 instead of a full array are that the full array is more bulky and obtrusive, thereby blocking the surgeon's view and access to the surgical field 208 more than a single marker 1018, and line of sight to a full array is more easily blocked than line of sight to a single marker 1018.


Turning now to FIGS. 17A-17B and 18A-18B, instruments 608, such as implant holders 608B, 608C, are depicted which include both fixed and moveable tracking markers 804, 806. The implant holders 608B, 608C may have a handle 620 and an outer shaft 622 extending from the handle 620. The shaft 622 may be positioned substantially perpendicular to the handle 620, as shown, or in any other suitable orientation. An inner shaft 626 may extend through the outer shaft 622 with a knob 628 at one end. Implant 10, 12 connects to the shaft 622, at the other end, at tip 624 of the implant holder 608B, 608C using typical connection mechanisms known to those of skill in the art. The knob 628 may be rotated, for example, to expand or articulate the implant 10, 12. U.S. Pat. Nos. 8,709,086 and 8,491,659, the disclosures of which are incorporated by reference herein, describe expandable fusion devices and methods of installation.


When tracking the tool 608, such as implant holder 608B, 608C, the tracking array 612 may contain a combination of fixed markers 804 and one or more moveable markers 806 which make up the array 612 or is otherwise attached to the implant holder 608B, 608C. The navigation array 612 may include at least one or more (e.g., at least two) fixed position markers 804, which are positioned with a known location relative to the implant holder instrument 608B, 608C. These fixed markers 804 would not be able to move in any orientation relative to the instrument geometry and would be useful in defining where the instrument 608 is in space. In addition, at least one marker 806 is present which can be attached to the array 612 or the instrument itself which is capable of moving within a pre-determined boundary (e.g., sliding, rotating, etc.) relative to the fixed markers 804. The system 100, 300, 600 (e.g., the software) correlates the position of the moveable marker 806 to a particular position, orientation, or other attribute of the implant 10 (such as height of an expandable interbody spacer shown in FIGS. 17A-17B or angle of an articulating interbody spacer shown in FIGS. 18A-18B). Thus, the system and/or the user can determine the height or angle of the implant 10, 12 based on the location of the moveable marker 806.


In the embodiment shown in FIGS. 17A-17B, four fixed markers 804 are used to define the implant holder 608B and a fifth moveable marker 806 is able to slide within a pre-determined path to provide feedback on the implant height (e.g., a contracted position or an expanded position). FIG. 17A shows the expandable spacer 10 at its initial height, and FIG. 17B shows the spacer 10 in the expanded state with the moveable marker 806 translated to a different position. In this case, the moveable marker 806 moves closer to the fixed markers 804 when the implant 10 is expanded, although it is contemplated that this movement may be reversed or otherwise different. The amount of linear translation of the marker 806 would correspond to the height of the implant 10. Although only two positions are shown, it would be possible to have this as a continuous function whereby any given expansion height could be correlated to a specific position of the moveable marker 806.


Turning now to FIGS. 18A-18B, four fixed markers 804 are used to define the implant holder 608C and a fifth, moveable marker 806 is configured to slide within a pre-determined path to provide feedback on the implant articulation angle. FIG. 18A shows the articulating spacer 12 at its initial linear state, and FIG. 18B shows the spacer 12 in an articulated state at some offset angle with the moveable marker 806 translated to a different position. The amount of linear translation of the marker 806 would correspond to the articulation angle of the implant 12. Although only two positions are shown, it would be possible to have this as a continuous function whereby any given articulation angle could be correlated to a specific position of the moveable marker 806.


In these embodiments, the moveable marker 806 slides continuously to provide feedback about an attribute of the implant 10, 12 based on position. It is also contemplated that there may be discreet positions that the moveable marker 806 must be in which would also be able to provide further information about an implant attribute. In this case, each discreet configuration of all markers 804, 806 correlates to a specific geometry of the implant holder 608B, 608C and the implant 10, 12 in a specific orientation or at a specific height. In addition, any motion of the moveable marker 806 could be used for other variable attributes of any other type of navigated implant.


Although depicted and described with respect to linear movement of the moveable marker 806, the moveable marker 806 should not be limited to just sliding as there may be applications where rotation of the marker 806 or other movements could be useful to provide information about the implant 10, 12. Any relative change in position between the set of fixed markers 804 and the moveable marker 806 could be relevant information for the implant 10, 12 or other device. In addition, although expandable and articulating implants 10, 12 are exemplified, the instrument 608 could work with other medical devices and materials, such as spacers, cages, plates, fasteners, nails, screws, rods, pins, wire structures, sutures, anchor clips, staples, stents, bone grafts, biologics, cements, or the like.


Turning now to FIG. 19A, it is envisioned that the robot end-effector 112 is interchangeable with other types of end-effectors 112. Moreover, it is contemplated that each end-effector 112 may be able to perform one or more functions based on a desired surgical procedure. For example, the end-effector 112 having a guide tube 114 may be used for guiding an instrument 608 as described herein. In addition, end-effector 112 may be replaced with a different or alternative end-effector 112 that controls a surgical device, instrument, or implant, for example.


The alternative end-effector 112 may include one or more devices or instruments coupled to and controllable by the robot. By way of non-limiting example, the end-effector 112, as depicted in FIG. 19A, may comprise a retractor (for example, one or more retractors disclosed in U.S. Pat. Nos. 8,992,425 and 8,968,363) or one or more mechanisms for inserting or installing surgical devices such as expandable intervertebral fusion devices (such as expandable implants exemplified in U.S. Pat. Nos. 8,845,734; 9,510,954; and 9,456,903), stand-alone intervertebral fusion devices (such as implants exemplified in U.S. Pat. Nos. 9,364,343 and 9,480,579), expandable corpectomy devices (such as corpectomy implants exemplified in U.S. Pat. Nos. 9,393,128 and 9,173,747), articulating spacers (such as implants exemplified in U.S. Pat. No. 9,259,327), facet prostheses (such as devices exemplified in U.S. Pat. No. 9,539,031), laminoplasty devices (such as devices exemplified in U.S. Pat. No. 9,486,253), spinous process spacers (such as implants exemplified in U.S. Pat. No. 9,592,082), inflatables, fasteners including polyaxial screws, uniplanar screws, pedicle screws, posted screws, and the like, bone fixation plates, rod constructs and revision devices (such as devices exemplified in U.S. Pat. No. 8,882,803), artificial and natural discs, motion preserving devices and implants, spinal cord stimulators (such as devices exemplified in U.S. Pat. No. 9,440,076), and other surgical devices. The end-effector 112 may include one or instruments directly or indirectly coupled to the robot for providing bone cement, bone grafts, living cells, pharmaceuticals, or other deliverable to a surgical target. The end-effector 112 may also include one or more instruments designed for performing a discectomy, kyphoplasty, vertebrostenting, dilation, or other surgical procedure.


The end-effector itself and/or the implant, device, or instrument may include one or more markers 118 such that the location and position of the markers 118 may be identified in three-dimensions. It is contemplated that the markers 118 may include active or passive markers 118, as described herein, that may be directly or indirectly visible to the cameras 200. Thus, one or more markers 118 located on an implant 10, for example, may provide for tracking of the implant 10 before, during, and after implantation.


As shown in FIG. 19B, the end-effector 112 may include an instrument 608 or portion thereof that is coupled to the robot arm 104 (for example, the instrument 608 may be coupled to the robot arm 104 by the coupling mechanism shown in FIGS. 9A-9C) and is controllable by the robot system 100. Thus, in the embodiment shown in FIG. 19B, the robot system 100 is able to insert implant 10 into a patient and expand or contract the expandable implant 10. Accordingly, the robot system 100 may be configured to assist a surgeon or to operate partially or completely independently thereof. Thus, it is envisioned that the robot system 100 may be capable of controlling each alternative end-effector 112 for its specified function or surgical procedure.


Although the robot and associated systems described above are generally described with reference to spine applications, it is also contemplated that the robot system is configured for use in other surgical applications, including but not limited to, surgeries in trauma or other orthopedic applications (such as the placement of intramedullary nails, plates, and the like), cranial, neuro, cardiothoracic, vascular, colorectal, oncological, dental, and other surgical operations and procedures. According to some embodiments discussed below, robot systems may be used for brain surgery applications.



FIG. 20 is a block diagram illustrating elements of a robotic system controller (e.g., implemented within computer 408). As shown, the controller may include processor circuit 2007 (also referred to as a processor) coupled with input interface circuit 2001 (also referred to as an input interface), output interface circuit 2003 (also referred to as an output interface), control interface circuit 2005 (also referred to as a control interface), and memory circuit 2009 (also referred to as a memory). The memory circuit 2009 may include computer readable program code that when executed by the processor circuit 2007 causes the processor circuit to perform operations according to embodiments disclosed herein. According to other embodiments, processor circuit 2007 may be defined to include memory so that a separate memory circuit is not required.


As discussed herein, operations of controlling a robotic system according to some embodiments of the present disclosure may be performed by controller 2000 including processor 2007, input interface 2001, output interface 2003, and/or control interface 2005. For example, processor 2007 may receive user input through input interface 2001, and such user input may include user input received through foot pedal 544, tablet 546, a touch sensitive interface of display 110/304, etc. Processor 2007 may also receive position sensor input from tracking subsystem 532 and/or cameras 200 through input interface 2001. Processor 2007 may provide output through output interface 2003, and such out may include information to render graphic/visual information on display 110/304 and/or audio output to be provided through speaker 536. Processor 2007 may provide robotic control information through control interface 2005 to motion control subsystem 506, and the robotic control information may be used to control operation of a robotic actuator (such as robot arm 104/306-308/604, also referred to as a robotic arm), and/or end-effector 112/602.


A fiducial (also referred to as a fiducial point or a fiducial object) is a point on an object (in 3-dimensional 3D space) that can be localized in the 3D coordinate system of the image scan (e.g., a preoperative MRI scan and an intraoperative CT scan). It is often possible to detect the same fiducial within two or more different image scans. If at least three fiducials are located in two different coordinate systems, the two coordinate systems can be co-registered using the three or more fiducials. Once two coordinate systems for respective 3D image scans have been co-registered, a known point or object (e.g., a location of a tumor) in one of the image scans can be identified/located in the other image scan. If a tumor is located/identified in a preoperative MRI scan, for example, a coordinate system of the preoperative MRI scan can be co-registered with a coordinate system of an intraoperative CT scan to allow localization of the tumor in the intraoperative CT scan. In a surgical robotic system, it may be easier and more accurate to register the tracking camera's coordinate system to an intraoperative CT scan volume (e.g., using the registration method of FIGS. 10 and 11 and associated text) than to register to an MRI scan volume. After co-registration of CT and MRI coordinate systems, a trajectory for a surgical robot may be planned using the preoperative MRI scan and the trajectory transformed into the coordinate system of the CT, which is in turn transformed to the coordinate system of the cameras through the camera-CT registration process. In other words, co-registration of CT and MRI scans allows control of the robot according to trajectories in the MRI scan.


An artificial fiducial may be provided using an artificial object that is placed or adhered to/near the anatomical object of interest, and the artificial fiducial may be a sphere, a donut, or a divot that has features allowing it to be accurately and repeatably identified. For example, an artificial fiducial could be a metallic bb that is adhered to an object to be tracked. The metallic bb can be detected by processor 2007 using image processing techniques within a 3D scan to provide its 3D position in the coordinate system of the scan, and/or the metallic bb can be detected by touching the surface of the sphere with a tracked probe to provide its 3D position in a coordinate system of a robotic system (e.g., using optical tracking cameras 200/326).


According to some embodiments of inventive concepts, when performing cranial surgery, distinctive anatomical features on/in the brain may serve as natural fiducials. Particularly, the brain's naturally occurring blood vessels may serve as natural fiducial points rather than (or in addition to) inserting or placing an artificial fiducial object(s) in/on the brain/head/skull. Since blood vessels traverse and branch in unique patterns, the vessels in their entirety can serve as fiducial objects. However, with swelling, shrinking and shifting of the brain, it may be more difficult to keep track of the distortion of entire vessels than to follow displacement of any node (also referred to as a point) where a blood vessel (e.g., an artery or a vein) branches. These nodes (points) may be detected by processor 2007 using image processing in a preoperative scan/scans (e.g., a Magnetic Resonance Imaging MRI scan or a Computed Tomography CT scan), an intraoperative scan/scans (e.g., an MRI scan or CT scan), x-rays, and/or ultrasound. Branch nodes (points) of blood vessels (also referred to as blood vessel nodes) may provide unique natural fiducials because such blood vessel nodes provide good coverage permeating most/all regions of the brain. When used as a group, branch nodes of blood vessels may thus be used by processor 2007 to accurately monitor shifting/distortion of different regions of the brain and/or the whole brain. Moreover, various ones of the blood vessel nodes may be distinct in shape, direction, and distance from adjacent branch nodes, allowing such branch nodes to be automatically detected/identified and sorted in different 3D scans of the brain.



FIG. 21 illustrates a 3D reconstruction of a CT image with contrast showing blood vessels in the brain. When using x-ray images or CT scans, a liquid contrast agent may be injected into the patient's bloodstream so that the blood vessels in the brain may be more easily visualized in the resulting image scans. Without a contrast agent, the blood vessels may not show up visually due to similarity of intensity between blood vessels and brain tissue. When studied on an MRI scan, the appropriate MRI sequence type may be selected to show the blood vessels most clearly while contrasting with surrounding tissues.


In order for processor 2007 to co-register two or more different coordinate systems, it may be useful/necessary to locate a plurality of (e.g., at least three) natural and/or artificial fiducials in the image scans for which coordinate systems are to be co-registered, and automatic identification of the locations of the fiducials in the scans may be preferred to manual identification of the locations. When using 3D image volumes (e.g., MRI or CT scans), automated image processing algorithms may be used by processor 2007 to auto-detect branch points on blood vessels using different components for detection/identification of blood vessel nodes.


One component of such automated image processing algorithms may include processor 2007 determining a direction in which the branch is occurring. When looking at blood vessel branches extending in different directions, the trunk blood vessel and the branch blood vessels for the node may be determined to identify a direction of the branch. For example, processor 2007 may use image processing to follow a blood vessel until it reaches a node (also referred to as a branch or branch point) where it meets with two or more other blood vessels. At the node, sizes (e.g., diameters and/or cross-sections) of the blood vessels may be assessed by processor 2007. The blood vessel at the node with the largest size (e.g., diameter and/or cross-section) can be identified as the trunk blood vessel for the node, and the other blood vessels at the node (with smaller sizes) can be identified as branch blood vessels for the node. This information may be useful for processor 2007 to categorize, identify, and/or locate the blood vessel nodes, and to identify/locate the same blood vessel nodes as natural fiducials in different scans of the same anatomical volume.


Another component of such automated image processing algorithms may include processor 2007 determining distances between blood vessel nodes/branches. When following a blood vessel along its course, distances from one node/branch to the next are not likely to be identical. The distances between consecutive nodes/branches (along a path of blood vessels) can thus be measured and used to identify particular blood vessels and/or nodes/branches thereof. The different distances between nodes/branches can thus be used to identify particular blood vessels and nodes/branches that those blood vessels pass through, and this information can be used by processor 2007 to identify/locate the same nodes/branches in a different scan of the same anatomical volume. This information, for example, can be used to generate a map of internode distances along blood vessel pathways through the brain, and the map of internode distances can be used to identify the same blood vessel nodes as natural fiducials in different scans of the same anatomical volume.


According to some embodiments of inventive concepts, processor 2007 may thus detect blood vessel nodes in a CT scan (with contrast) and/or in an MRI scan. Processor 2007 may find a candidate blood vessel by identifying a structure appearing as a high-contrast thin snaking line through lower intensity surrounding tissues. The blood vessel may be followed in one direction until a node with two (or more) new branches is encountered. Based on comparing sizes (e.g., cross-sections and/or diameters) of blood vessels at the node, processor 2007 may determine whether the blood vessel being followed is being followed up or down the tree structure. If being followed down (to smaller sized branches), the direction may be reversed, and the blood vessel may be followed in the opposite direction up its tree structure. Once processor 2007 detects the node representing the first branch point of the trunk blood vessel, the trunk blood vessel may be followed down to the next blood vessel node where two or more smaller blood vessels branch from the trunk blood vessel. In this manner, processor 2007 can map and identify blood vessel nodes throughout the brain.



FIG. 22 is a diagram illustrating a tree structure of blood vessels and blood vessel nodes and examples of mappings, where the blood vessel nodes (AB, AC, AE, BD, BG, CF, and DH) may be used by processor 2007 as fiducials. As shown in FIG. 22, the trunk blood vessel is the largest blood vessel of the tree structure, and each node may have two or more branches. Moreover, a branch at one node may be a trunk for a next node down the tree structure. For example, branch C may be a branch blood vessel for node AC and a trunk blood vessel for node CF. Processor 2007 may follow the trunk blood vessel down the tree structure to the first branch point at node AB where branch blood vessels A and B split off from the trunk blood vessel. Branch blood vessel A may then be followed through nodes AC, AE, etc., and as each node is reached along branch A, processor 2007 may record a respective length of the branch between adjacent nodes.


In the example of FIG. 2, processor 2007 may follow branch A through each of nodes AB, AC, and AE, and processor 2007 may record lengths of branch A between nodes AB and AC and between nodes AC and AE. In addition, processor 2007 may record x-, y-, and z-coordinates for each node according to the name of that node (e.g., node AB, node AC, and node AE). This information about nodes and inter-node distances on each branch may be used when detecting branches on a new scan to facilitate identification of the same nodes as fiducials in different 3D image scans (for example, assuming that differences in inter-node distances for different 3D image scans of the same patient will be significantly less than distances between adjacent branches). Processor 2007 may similarly map nodes BD and BG along branch B, node CF along branch C, and node DH along branch D.


When mapping blood vessel branches defining nodes to be used as natural fiducials, processor 2007 may use other factors to uniquely define/identify the blood vessel branches and/or nodes. According to some embodiments, a shape of a trunk and/or branch blood vessel of a node may be used to identify the node. For example, a blood vessel may define a squiggly line or a blood vessel may turn sharply in one direction and then turn sharply in another direction after a short distance. These shape features may be useful for processor 2007 to identify/verify a particular trunk/branch blood vessel that is being followed and/or node associated with the trunk/branch blood vessel. Such information may be especially useful if inter-node distances are ambiguous in distinguishing between blood vessels. According to some other embodiments, inter-branch angles between two smaller branches at a node may be used to define/identify a node. For example, an angle between branches A and B at node AB may be used to identify/define node AB.


Operations discussed above with respect to FIG. 22 may be performed by processor 2007 using a 3D image scan such as a CT scan or an MRI scan. Detection using x-rays may be more difficult than using CT or MRI scans. Using x-rays, two x-ray shots may be captured taken from different positions at least 60 degrees apart and with a tracked registration object affixed to the fluoroscopic imaging machine in a method similar to that used for fluoroscopic robotic guidance. The tracked registration object allows the angle and distance between x-ray shots to be known and the 3D coordinate system viewed on the two x-ray shots to be evaluated accurately. By registering multiple fluoroscopic x-ray shots, processor 2007 may use image processing to detect branch points/nodes in 3D, and detected branch points/nodes may be marked for comparison with later fluoroscopic shots or other 3D scans (e.g., CT or MRI scans). With fluoroscopic imaging, multiple blood vessels may overlay each other and may be difficult to distinguish. If a node cannot be clearly viewed in both shots of a fluoroscopic pair, its 3D coordinates may be difficult to determine accurately. In a 3D imaging volume (e.g., generated using CT or MRI), it may be possible to inspect and follow discrete slices and to more clearly discern blood vessel nodes.


Operations discussed above may be used by processor 2007 to co-register coordinate systems of two medical 3D image scans. To control robotic operations based on information from such 3D image scans, registration to a tracking coordinate system used by the robot may also be performed. Such a tracking coordinate system may be based on optical information received by processor 2007 from cameras 200/326 through input interface 2001. For such registration, external markers may be attached to the patient. For example, an external ICT (intraoperative CT) frame may contain metal fiducials 1422 and optical tracking markers 1420 in fixed positions relative to each other. By capturing the metal fiducials in the same scan as the natural fiducials and their respective locations determined by processor 2007 using image processing, relative positions of the metal fiducials, optical tracking markers, and blood vessel nodes may be determined and used to provide co-registration of the coordinate system of the robot with the coordinate system of intraoperative CT scan. Processor 2007 can then control the robotic actuator (e.g., robot arm 104/604) to manipulate tracked tools in relation to the anatomy of the intraoperative CT scan and/or another scan (e.g., preoperative MRI scan) with a coordinate system that has been co-registered with respect to the ICT scan.


The ICT scan may not be captured within a preoperative scan on which surgical planning is performed (e.g., a high-resolution MRI scan). In the preoperative scan, natural fiducials (e.g., blood vessel nodes) may be detected and their positions recorded, and the preoperative scan may be provided to processor 2007 with information regarding a planned trajectory for an end-effector 112/602 of the robotic actuator. The ICT fiducials (artificial fiducials) may be attached to the patient and captured in the ICT scan (e.g., a CT scan using dye contrast), and tracking registration would be established by processor 2007 relative to the ICT fiducials and new natural fiducials. By detecting and relating the new natural fiducials in the ICT scan to the original natural fiducials in the preoperative MRI scan, all plans of trajectories into the brain that were made relative to the preoperative MRI scan may be automatically related to the intraoperative CT scan and to the optical tracking system. Such co-registration may compensate for shifting/distortion of the brain (or portions thereof) that may occur during surgery after planning trajectories using a preoperative image scan. This registration using blood vessel nodes as fiducials may be more accurate than registration of CT to MRI based on skull structures because the brain may shift relative to such skull structures in the preoperative and intraoperative scans.


In addition, the brain may shrink or swell during surgery and/or from the time of the preoperative scan to the intraoperative scan. When matching blood vessel nodes in the preoperative and intraoperative scans, processor 2007 may perform an affine transformation for a best fit of blood vessel nodes to account for non-rigid-body movement of the blood vessel nodes that would be expected as the brain expands or shrinks. Processor 2007 may analyze parameters used by the affine transformation to achieve a fit to provide an estimate of an amount by which different regions of the brain swell or shrink during surgery. Such information may be useful in research to track outcomes of brain surgery.


According to some other embodiments, ultrasound may be used to generate an image scan used to detect blood vessel nodes to be used as fiducials and relate the blood vessel nodes to the tracking coordinate system of the robot. Using ultrasound with a tracked probe (i.e., a probe that is tracked by the optical tracking system of the robot), locations of blood vessel nodes may be triangulated through different probe poses or by simultaneously tracking the same node with two probes at different angles. According to some embodiments using ultrasound, the Doppler effect may be used to guide the probe to find blood vessels and to determine which way the blood is flowing since blood flowing through blood vessels creates a different signal on ultrasound than static tissues due to the Doppler effect.


By using natural fiducials such as blood vessel nodes within the brain itself, tracking may be more accurate than if only external fiducials are used to co-register the different coordinate systems. Moreover, use of blood vessel nodes may provide detection of and/or accommodation for swelling, shrinking, and/or other non-uniform shifting/distortion from a preoperative scan to an intraoperative scan. In addition, comparison of blood vessel nodes may be used to provide real time monitoring of brain shifts, swelling, shrinking, and/or distortion.


Operations of a robotic system (including a robotic actuator configured to position an end-effector with respect to an anatomical location of a patient) will now be discussed with reference to the flow chart of FIG. 23 according to some embodiments of inventive concepts. For example, modules may be stored in memory 2009 of FIG. 20, and these modules may provide instructions so that when the instructions of a module are executed by processor 2007, processor 2007 performs respective operations of the flow chart of FIG. 23.


At block 2301, processor 2007 may provide first data for a first 3-dimensional (3D) image scan of an anatomical volume (e.g., the patient's head, including the brain), and the first data may identify first, second, and third blood vessel nodes (to be used as natural fiducials) in a first coordinate system for the first 3D image scan. The first 3D image scan, for example, may be a preoperative MRI scan, and a planned trajectory for a robotic actuator may be provided with the first 3D image scan. The planned trajectory, for example, may define a target location in the anatomical volume and a direction to the target location. The identification of the first, second, and third blood vessel nodes may be provided to processor 2007 with the first 3D image scan, or processor 2007 may use image processing to identify the first, second, and third blood vessel nodes from the first 3D image scan.


At block 2303, processor 2007 may provide second data for a second 3D image scan of the anatomical volume, and the second data may identify the first, second, and third blood vessel nodes in a second coordinate system for the second 3D image scan. The second 3D image scan, for example, may be an intraoperative CT scan, and the second data for the second 3D image scan may also identify an artificial fiducial outside the anatomical volume that can be separately tracked using cameras 200/326. Processor 2007, for example, may identify the first, second, and third blood vessel nodes in the first and/or second 3D image scans as discussed above with respect to FIGS. 21 and 22. By identifying at least the first, second, and third blood vessel nodes in both image scans, processor 2007 can identify the same three points in both image scans to facilitate co-registration.


At block 2305, processor 2007 may co-register the first and second coordinate systems for the first and second 3D image scans of the anatomical volume using the first, second, and third blood vessel nodes identified in the first data and in the second data as first, second, and third natural fiducials. Because the blood vessel nodes move with the brain, the use of blood vessel nodes may provide increased accuracy for co-registration even if shifting, shrinking, swelling, and/or deformation occur between image scans. By co-registering the first and second coordinate systems, processor 2007 may be able to translate additional information, e.g., the target location and/or planned trajectory for the robotic actuator, from the first 3D image scan to the second 3D image scan.


At block 2307, processor may co-register the second coordinate system for the second 3D image scan and a third coordinate system for the robotic actuator using the artificial fiducial from the second 3D image scan. Because the artificial fiducial can be tracked using cameras 200/326 and/or tracking system 532, co-registering the second and third coordinate systems may be performed using optical information from tracking cameras 200/326 to locate the artificial fiducial in the third coordinate system for the robotic actuator.


At block 2309, processor 2007 may provide the target location in one of the second and third coordinate systems using a transformation based on the first, second, and third blood vessel nodes in the first and second coordinate systems. The transformation, for example, may include an affine transformation. Such a transformation may provide a more accurate location of the target location for the robotic actuator to accommodate for shifting, shrinking, swelling, and/or other deformation of the brain between the first and second 3D image scans.


At block 2311, processor 2007 may control the robotic actuator (e.g., robotic arm 104/306-308/604) to move the end-effector 112/302/602 to a target trajectory relative to the anatomical volume and target location therein. Processor 2007, for example, may control the robotic actuator based on one or more of: the first data identifying the target location; co-registering the first and second coordinate systems; based on co-registering the second and third coordinate systems; and/or providing the target location in one of the second and third coordinate systems using the transformation.


According to some embodiments of FIG. 23, each blood vessel node may be defined at a branch of one trunk blood vessel into at least first and second branch blood vessels, with a size (e.g., a cross-section and/or diameter) of the trunk blood vessel being greater than a size of the first branch blood vessel and a size of the second branch blood vessel. Unique characteristics may be used to identify the same blood vessel node in each 3D scan. Such characteristics may include one or more of: a number of branch blood vessels of the blood vessel node; a length of a trunk blood vessel of the blood vessel node between the blood vessel node and a previous blood vessel node; an angle between branch blood vessels of the blood vessel node; and/or a shape of one of the trunk/branch blood vessels of the node.


In the above-description of various embodiments of present inventive concepts, it is to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of present inventive concepts. Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which present inventive concepts belong. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.


When an element is referred to as being “connected”, “coupled”, “responsive”, or variants thereof to another element, it can be directly connected, coupled, or responsive to the other element or intervening elements may be present. In contrast, when an element is referred to as being “directly connected”, “directly coupled”, “directly responsive”, or variants thereof to another element, there are no intervening elements present. Like numbers refer to like elements throughout. Furthermore, “coupled”, “connected”, “responsive”, or variants thereof as used herein may include wirelessly coupled, connected, or responsive. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. Well-known functions or constructions may not be described in detail for brevity and/or clarity. The term “and/or” includes any and all combinations of one or more of the associated listed items.


It will be understood that although the terms first, second, third, etc. may be used herein to describe various elements/operations, these elements/operations should not be limited by these terms. These terms are only used to distinguish one element/operation from another element/operation. Thus, a first element/operation in some embodiments could be termed a second element/operation in other embodiments without departing from the teachings of present inventive concepts. The same reference numerals or the same reference designators denote the same or similar elements throughout the specification.


As used herein, the terms “comprise”, “comprising”, “comprises”, “include”, “including”, “includes”, “have”, “has”, “having”, or variants thereof are open-ended, and include one or more stated features, integers, elements, steps, components or functions but does not preclude the presence or addition of one or more other features, integers, elements, steps, components, functions or groups thereof. Furthermore, as used herein, the common abbreviation “e.g.”, which derives from the Latin phrase “exempli gratia,” may be used to introduce or specify a general example or examples of a previously mentioned item, and is not intended to be limiting of such item. The common abbreviation “i.e.”, which derives from the Latin phrase “id est,” may be used to specify a particular item from a more general recitation.


Example embodiments are described herein with reference to block diagrams and/or flowchart illustrations of computer-implemented methods, apparatus (systems and/or devices) and/or computer program products. It is understood that a block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by computer program instructions that are performed by one or more computer circuits. These computer program instructions may be provided to a processor circuit of a general purpose computer circuit, special purpose computer circuit, and/or other programmable data processing circuit to produce a machine, such that the instructions, which execute via the processor of the computer and/or other programmable data processing apparatus, transform and control transistors, values stored in memory locations, and other hardware components within such circuitry to implement the functions/acts specified in the block diagrams and/or flowchart block or blocks, and thereby create means (functionality) and/or structure for implementing the functions/acts specified in the block diagrams and/or flowchart block(s).


These computer program instructions may also be stored in a tangible computer-readable medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable medium produce an article of manufacture including instructions which implement the functions/acts specified in the block diagrams and/or flowchart block or blocks. Accordingly, embodiments of present inventive concepts may be embodied in hardware and/or in software (including firmware, resident software, micro-code, etc.) that runs on a processor such as a digital signal processor, which may collectively be referred to as “circuitry,” “a module” or variants thereof.


It should also be noted that in some alternate implementations, the functions/acts noted in the blocks may occur out of the order noted in the flowcharts. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Moreover, the functionality of a given block of the flowcharts and/or block diagrams may be separated into multiple blocks and/or the functionality of two or more blocks of the flowcharts and/or block diagrams may be at least partially integrated. Finally, other blocks may be added/inserted between the blocks that are illustrated, and/or blocks/operations may be omitted without departing from the scope of inventive concepts. Moreover, although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.


Although several embodiments of inventive concepts have been disclosed in the foregoing specification, it is understood that many modifications and other embodiments of inventive concepts will come to mind to which inventive concepts pertain, having the benefit of teachings presented in the foregoing description and associated drawings. It is thus understood that inventive concepts are not limited to the specific embodiments disclosed hereinabove, and that many modifications and other embodiments are intended to be included within the scope of the appended claims. It is further envisioned that features from one embodiment may be combined or used with the features from a different embodiment(s) described herein. Moreover, although specific terms are employed herein, as well as in the claims which follow, they are used only in a generic and descriptive sense, and not for the purposes of limiting the described inventive concepts, nor the claims which follow. The entire disclosure of each patent and patent publication cited herein is incorporated by reference herein in its entirety, as if each such patent or publication were individually incorporated by reference herein. Various features and/or potential advantages of inventive concepts are set forth in the following claims.

Claims
  • 1. A robotic system comprising: a robotic actuator configured to position a surgical end-effector with respect to an anatomical volume of a patient; anda controller coupled with the robotic actuator, wherein the controller is configured to, provide first data for a first 3-dimensional (3D) image scan of the anatomical volume, wherein the first data identifies a blood vessel node in a first coordinate system for the first 3D image scan,provide second data for a second 3D image scan of the anatomical volume, wherein the second data identifies the blood vessel node in a second coordinate system for the second 3D image scan, wherein the controller derives the second data by processing the second 3D image scan, which includes traversing a blood vessel in an upstream direction to find the largest blood vessel and then mapping each downstream blood vessel node by its 3D location,co-register the first and second coordinate systems for the first and second 3D image scans of the anatomical volume using the blood vessel node identified in the first data and in the second data as a fiducial,co-register the second coordinate system for the second 3D image scan and a third coordinate system for the robotic actuator using an artificial fiducial from the second 3D image scan, andcontrol the robotic actuator to move the end-effector to a target trajectory relative to the anatomical volume based on co-registering the first and second coordinate systems for the first and second 3D image scans using the blood vessel node and based on co-registration of the second coordinate system for the second 3D image scan and the third coordinate system for the robotic actuator.
  • 2. The robotic system of claim 1, wherein the blood vessel node is a first blood vessel node,wherein the first data identifies the first blood vessel node, a second blood vessel node, and a third blood vessel node in the first coordinate system,wherein the second data identifies the first blood vessel node, the second blood vessel node, and the third blood vessel node in the second coordinate system, andwherein co-registering comprises co-registering the first and second coordinate systems for the first and second 3D image scans of the anatomical volume using the first, second, and third blood vessel nodes identified in the first data and in the second data as first, second, and third fiducials.
  • 3. The robotic system of claim 1, wherein the first data identifies a target location in the anatomical volume, wherein the second data identifies the artificial fiducial outside the anatomical volume, wherein controlling the robotic actuator comprises controlling the robotic actuator to move the end-effector to the target trajectory based on the first data identifying the target location and based on co-registering the second and third coordinate systems.
  • 4. The robotic system of claim 3, wherein the blood vessel node is a first blood vessel node, wherein the first data identifies the first blood vessel node, a second blood vessel node, and a third blood vessel node in the first coordinate system, wherein the second data identifies the first blood vessel node, the second blood vessel node, and the third blood vessel node in the second coordinate system, and wherein co-registering comprises co-registering the first and second coordinate systems for the first and second 3D image scans of the anatomical volume using the first, second, and third blood vessel nodes identified in the first data and in the second data as first, second, and third fiducials, wherein the controller is further configured to, provide the target location in at least one of the second and third coordinate systems using a transformation based on the first, second, and third blood vessel nodes in the first and second coordinate systems;wherein controlling the robotic actuator further comprises controlling the robotic actuator to move the end-effector to the target trajectory based on providing the target location in one of the second and third coordinate systems using the transformation.
  • 5. The robotic system of claim 4, wherein the transformation comprises an affine transformation.
  • 6. The robotic system of claim 3, wherein co-registering the second and third coordinate systems comprises co-registering the second and third coordinate systems using optical information from tracking cameras to locate the artificial fiducial in the third coordinate system for the robotic actuator.
  • 7. The robotic system of claim 1, wherein the blood vessel node comprises a branch of one trunk blood vessel into at least first and second branch blood vessels, wherein a size of the trunk blood vessel is greater than a size of the first branch blood vessel and a size of the second branch blood vessel.
  • 8. The robotic system of claim 7, wherein the first data for the first 3D image scan identifies a number of the at least first and second branch blood vessels of the blood vessel node, and wherein providing the second data comprises identifying the blood vessel node in the second 3D image scan based on the number of the at least first and second branch blood vessels of the blood vessel node.
  • 9. The robotic system of claim 7, wherein the first data for the first 3D image scan identifies a length of the trunk blood vessel between the blood vessel node and a previous blood vessel node, and wherein providing the second data comprises identifying the blood vessel node in the second 3D image scan based on the length of the trunk blood vessel between the blood vessel node and the previous blood vessel node.
  • 10. The robotic system of claim 7, wherein the first data for the first 3D image scan identifies an angle between the first and second branch blood vessels, and wherein providing the second data comprises identifying the blood vessel node in the second 3D image scan based on the angle between the first and second branch blood vessels.
  • 11. The robotic system of claim 7, wherein the first data for the first 3D image scan identifies a shape of at least one of the trunk blood vessel, the first branch blood vessel, and/or the second branch blood vessel, and wherein providing the second data comprises identifying the blood vessel node in the second 3D image scan based on the shape of the at least one of the trunk blood vessel, the first branch blood vessel, and/or the second branch blood vessel.
CROSS REFERENCE TO RELATED APPLICATIONS

The present application is a non-provisional patent application that claims priority to provisional application 62/634,245 filed on Feb. 23, 2018. This present application is also a continuation-in-part application of U.S. patent application Ser. No. 15/609,334 filed on May 31, 2017, which is continuation-in-part of U.S. patent application Ser. No. 15/157,444, filed May 18, 2016, which is a continuation-in-part of U.S. patent application Ser. No. 15/095,883, filed Apr. 11, 2016, which is a continuation-in-part of U.S. patent application Ser. No. 14/062,707, filed on Oct. 24, 2013, which is a continuation-in-part application of U.S. patent application Ser. No. 13/924,505, filed on Jun. 21, 2013, which claims priority to provisional application No. 61/662,702 filed on Jun. 21, 2012 and claims priority to provisional application No. 61/800,527 filed on Mar. 15, 2013, all of which are incorporated by reference herein in their entireties for all purposes.

US Referenced Citations (802)
Number Name Date Kind
4150293 Franke Apr 1979 A
5020933 Salvestro et al. Jun 1991 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
7207995 Vandewalle Apr 2007 B1
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
7988215 Seibold Aug 2011 B2
7996110 Lipow et al. Aug 2011 B2
8004121 Sartor 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
8035685 Jensen Oct 2011 B2
8046054 Kim et al. Oct 2011 B2
8046057 Clarke 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
8313430 Pimenta Nov 2012 B1
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 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
9280823 Popovic Mar 2016 B2
9308050 Kostrzewski et al. Apr 2016 B2
9351709 Hague May 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
9463073 Gill et al. Oct 2016 B2
9492235 Hourtash et al. Nov 2016 B2
9554117 Lee Jan 2017 B2
9592096 Maillet et al. Mar 2017 B2
9615886 Popovic Apr 2017 B2
9750465 Engel et al. Sep 2017 B2
9757203 Hourtash et al. Sep 2017 B2
9782229 Crawford Oct 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 Meh 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
10182704 Popovic Jan 2019 B2
10357184 Crawford Jul 2019 B2
10575906 Wu Mar 2020 B2
10893912 Crawford Jan 2021 B2
11020202 Wada Jun 2021 B2
11109843 Li Sep 2021 B2
20010036302 Miller Nov 2001 A1
20020035321 Bucholz et al. Mar 2002 A1
20030125622 Schweikard et al. Jul 2003 A1
20030161442 Zeiss Aug 2003 A1
20040019263 Jutras et al. Jan 2004 A1
20040024311 Quaid Feb 2004 A1
20040034302 Abovitz et al. Feb 2004 A1
20040068172 Nowinski et al. Apr 2004 A1
20040076259 Jensen et al. Apr 2004 A1
20040157188 Luth et al. Aug 2004 A1
20050085714 Foley et al. Apr 2005 A1
20050096502 Khalili May 2005 A1
20050107679 Geiger et al. May 2005 A1
20050119639 McCombs et al. Jun 2005 A1
20050143651 Verard et al. Jun 2005 A1
20050149045 Elliott Jul 2005 A1
20050171558 Abovitz et al. Aug 2005 A1
20050215888 Grimm et al. Sep 2005 A1
20060036264 Selover et al. Feb 2006 A1
20060100610 Wallace et al. May 2006 A1
20060142657 Quaid et al. Jun 2006 A1
20060173329 Marquart et al. Aug 2006 A1
20060178559 Kumar et al. Aug 2006 A1
20060184396 Dennis et al. Aug 2006 A1
20060241416 Marquart et al. Oct 2006 A1
20060264963 Reed et al. Nov 2006 A1
20060291612 Nishide et al. Dec 2006 A1
20070001879 Kaftan et al. Jan 2007 A1
20070015987 Benlloch Baviera et al. Jan 2007 A1
20070016009 Lakin et al. Jan 2007 A1
20070021738 Hasser et al. Jan 2007 A1
20070038059 Sheffer et al. Feb 2007 A1
20070073133 Schoenefeld Mar 2007 A1
20070122020 Claus et al. May 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
20070238985 Smith et al. Oct 2007 A1
20080004523 Jensen Jan 2008 A1
20080010706 Moses et al. Jan 2008 A1
20080013809 Zhu et al. Jan 2008 A1
20080033283 Dellaca et al. Feb 2008 A1
20080046122 Manzo et al. Feb 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
20080119725 Lloyd May 2008 A1
20080144906 Allred et al. Jun 2008 A1
20080154389 Smith 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
20080188934 Moser et al. Aug 2008 A1
20080200794 Teichman et al. Aug 2008 A1
20080214922 Hartmann et al. Sep 2008 A1
20080228068 Viswanathan et al. Sep 2008 A1
20080228195 von Jako 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
20090099445 Burger Apr 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
20090234217 Mire et al. Sep 2009 A1
20090240141 Neubauer et al. Sep 2009 A1
20090254326 Isaacs Oct 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
20090306480 Protopsaltis Dec 2009 A1
20090306499 Van Vorhis et al. Dec 2009 A1
20100022874 Wang et al. Jan 2010 A1
20100039506 Sarvestani et al. Feb 2010 A1
20100046718 Weiser et al. Feb 2010 A1
20100076305 Maier-Hein et al. Mar 2010 A1
20100114288 Haller et al. May 2010 A1
20100125286 Wang et al. May 2010 A1
20100130986 Mailloux et al. May 2010 A1
20100174410 Greer et al. Jul 2010 A1
20100228117 Hartmann Sep 2010 A1
20100228265 Prisco Sep 2010 A1
20100228340 Erbel et al. 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
20110019884 Blau Jan 2011 A1
20110020084 Brett et al. Jan 2011 A1
20110022229 Jang et al. Jan 2011 A1
20110040305 Gomez et al. Feb 2011 A1
20110071347 Rogers et al. Mar 2011 A1
20110077504 Fischer et al. Mar 2011 A1
20110082468 Hagag et al. Apr 2011 A1
20110098553 Robbins et al. Apr 2011 A1
20110137152 Li Jun 2011 A1
20110184245 Xia et al. Jul 2011 A1
20110190588 McKay Aug 2011 A1
20110213379 Blau et al. Sep 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
20110257653 Hughes et al. Oct 2011 A1
20110276058 Choi et al. Nov 2011 A1
20110282189 Graumann Nov 2011 A1
20110286573 Schretter et al. Nov 2011 A1
20110295062 Gratacos 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
20120136372 Amat Girbau et al. May 2012 A1
20120143084 Shoham Jun 2012 A1
20120184839 Woerlein Jul 2012 A1
20120197182 Millman et al. Aug 2012 A1
20120226145 Chang et al. 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
20120289820 Rohling Nov 2012 A1
20120294498 Popovic Nov 2012 A1
20120296203 Hartmann et al. Nov 2012 A1
20130006267 Odermatt et al. 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
20130051647 Miao et al. Feb 2013 A1
20130053679 Owen Feb 2013 A1
20130060146 Yang et al. Mar 2013 A1
20130060337 Petersheim et al. Mar 2013 A1
20130064427 Picard et al. Mar 2013 A1
20130094742 Feilkas 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
20130165948 Popovic Jun 2013 A1
20130178867 Farritor et al. Jul 2013 A1
20130178868 Roh Jul 2013 A1
20130178870 Schena Jul 2013 A1
20130184873 Namiki 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
20130268007 Rezach 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
20130279784 Gill 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 Koon Dec 2013 A1
20130342578 Isaacs Dec 2013 A1
20130345717 Markvicka et al. Dec 2013 A1
20130345718 Crawford 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
20140052150 Taylor 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
20140088410 Wu 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
20140135744 Stein 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
20140200587 Pompee et al. Jul 2014 A1
20140130810 Azizian et al. Aug 2014 A1
20140221819 Sarment Aug 2014 A1
20140221822 Ehlers et al. Aug 2014 A1
20140222023 Kim et al. Aug 2014 A1
20140228631 Kwak et al. 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
20140275955 Crawford et al. Sep 2014 A1
20140275985 Walker et al. Sep 2014 A1
20140276931 Parihar et al. Sep 2014 A1
20140276940 Seo Sep 2014 A1
20140276943 Bowling et al. 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
20140316420 Ballard 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
20140336669 Park Nov 2014 A1
20140343416 Panescu et al. Nov 2014 A1
20140347353 Popovic Nov 2014 A1
20140357989 Hendriks et al. Dec 2014 A1
20140364720 Darrow et al. Dec 2014 A1
20140371577 Maillet et al. Dec 2014 A1
20150032164 Crawford et al. Jan 2015 A1
20150039034 Frankel et al. Feb 2015 A1
20150049174 Lee Feb 2015 A1
20150085970 Bouhnik et al. Mar 2015 A1
20150100066 Kostrzewski et al. Apr 2015 A1
20150146847 Liu May 2015 A1
20150150524 Yorkston et al. Jun 2015 A1
20150157416 Andersson Jun 2015 A1
20150157468 Wakayama et al. Jun 2015 A1
20150173810 Biedermann et al. Jun 2015 A1
20150196261 Funk Jul 2015 A1
20150196365 Kostrzewski et al. Jul 2015 A1
20150209056 Shoham et al. Jul 2015 A1
20150213633 Chang et al. Jul 2015 A1
20150335480 Alvarez et al. Nov 2015 A1
20150342647 Frankel et al. Dec 2015 A1
20160005194 Schretter et al. Jan 2016 A1
20160063707 Masumoto Mar 2016 A1
20160166329 Langan et al. Jun 2016 A1
20160220320 Crawford et al. Aug 2016 A1
20160235480 Scholl et al. Aug 2016 A1
20160235492 Morard et al. Aug 2016 A1
20160235493 Leboeuf, II et al. Aug 2016 A1
20160249990 Glozman et al. Sep 2016 A1
20160256225 Crawford et al. Sep 2016 A1
20160296266 Chandanson et al. Oct 2016 A1
20160302871 Gregerson et al. Oct 2016 A1
20160320322 Suzuki Nov 2016 A1
20160331335 Gregerson et al. Nov 2016 A1
20170000562 Frank et al. Jan 2017 A1
20170007327 Haider et al. Jan 2017 A1
20170020609 Wentorf et al. Jan 2017 A1
20170079727 Crawford et al. Mar 2017 A1
20170112552 Sinnott et al. Apr 2017 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
20170189126 Weir Jul 2017 A1
20170202629 Maillet et al. Jul 2017 A1
20170209222 Gassner 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
20170245946 Tabandeh et al. Aug 2017 A1
20170245951 Crawford et al. Aug 2017 A1
20170258426 Risher-Kelly et al. Sep 2017 A1
20170258526 Lang Sep 2017 A1
20170258535 Crawford et al. Sep 2017 A1
20170265952 Donhowe et al. Sep 2017 A1
20170273748 Hourtash et al. Sep 2017 A1
20170296277 Hourtash et al. Oct 2017 A1
20170312032 Amanatullah et al. Nov 2017 A1
20170333137 Roessler Nov 2017 A1
20170348061 Joshi et al. Dec 2017 A1
20170360493 Zucher et al. Dec 2017 A1
20180008355 Mozes et al. Jan 2018 A1
20180042464 Arai et al. Feb 2018 A1
20180049825 Kwon et al. Feb 2018 A1
20180064496 Hladio et al. Mar 2018 A1
20180064497 Hussain et al. Mar 2018 A1
20180066794 Okuda et al. Mar 2018 A1
20180158201 Thompson Jun 2018 A1
20180200016 Chappuis Jul 2018 A1
20180249981 Johnson et al. Sep 2018 A1
20180325610 Cameron et al. Nov 2018 A1
20190274765 Crawford Sep 2019 A1
20210244494 Wada Aug 2021 A1
Foreign Referenced Citations (93)
Number Date Country
1536975 Oct 2004 CN
1714742 Jan 2006 CN
202027725 Nov 2011 CN
102596062 Jul 2012 CN
102612350 Jul 2012 CN
102933163 Feb 2013 CN
104334110 Feb 2015 CN
104994805 Oct 2015 CN
105101903 Nov 2015 CN
106163446 Nov 2016 CN
106691600 May 2017 CN
106999245 Aug 2017 CN
209153975 Jul 2019 CN
107847275 Oct 2020 CN
102014221469 Apr 2016 DE
1103223 May 2001 EP
1346687 Sep 2003 EP
1523950 Apr 2005 EP
2468207 Jun 2012 EP
2471483 Jul 2012 EP
3181085 Jun 2017 EP
3517069 Jul 2019 EP
107545585 Jan 2018 GN
3-118053 May 1991 JP
11-313837 Nov 1999 JP
2001135734 May 2001 JP
2002253574 Sep 2002 JP
2004518475 Jun 2004 JP
2005-533579 Nov 2005 JP
2007-044488 Feb 2007 JP
2007-531543 Nov 2007 JP
2007534351 Nov 2007 JP
2007537835 Dec 2007 JP
2008-507361 Mar 2008 JP
2008188417 Aug 2008 JP
2008-538184 Oct 2008 JP
2009537229 Oct 2009 JP
2011-120782 Jun 2011 JP
2011-517594 Jun 2011 JP
2012075507 Apr 2012 JP
2013-541365 Nov 2013 JP
2014036700 Feb 2014 JP
2014097220 May 2014 JP
2015-504721 Feb 2015 JP
201536161 Feb 2015 JP
2015100677 Jun 2015 JP
2015119968 Jul 2015 JP
2015521084 Jul 2015 JP
2015528713 Oct 2015 JP
2015-534480 Dec 2015 JP
2016043211 Apr 2016 JP
2016185225 Oct 2016 JP
2016-193222 Nov 2016 JP
2016193222 Nov 2016 JP
2016539681 Dec 2016 JP
2017087313 May 2017 JP
2017176848 Oct 2017 JP
2017530842 Oct 2017 JP
2017223657 Dec 2017 JP
2018011938 Jan 2018 JP
2018-027288 Feb 2018 JP
2018516107 Jun 2018 JP
2018-114283 Jul 2018 JP
2018523516 Aug 2018 JP
2018-202156 Dec 2018 JP
03007198 Jan 2003 WO
2005039417 May 2005 WO
2009092164 Jul 2009 WO
20090126953 Oct 2009 WO
2011128766 Oct 2011 WO
2012050634 Apr 2012 WO
2013114823 Aug 2013 WO
2013118047 Aug 2013 WO
2013192598 Dec 2013 WO
2014010760 Jan 2014 WO
2014139023 Sep 2014 WO
2015023665 Feb 2015 WO
2015052718 Apr 2015 WO
2015061638 Apr 2015 WO
2015079775 Jun 2015 WO
2015142762 Sep 2015 WO
201613049 Jan 2016 WO
2016087539 Jun 2016 WO
2016114834 Jul 2016 WO
2016152255 Sep 2016 WO
2016154557 Sep 2016 WO
2016170372 Oct 2016 WO
2017221257 Feb 2017 WO
2017127202 Jul 2017 WO
2017147596 Aug 2017 WO
2017186799 Nov 2017 WO
2017204832 Nov 2017 WO
2018183461 Oct 2018 WO
Non-Patent Literature Citations (7)
Entry
US 8,231,638 B2, 07/2012, Swarup et al. (withdrawn)
Markelj et al.: “A review of 3D/2D registration methods for image-guided interventions”, Medical Image Analysis, Oxford University Press, Oxford, GB, vol. 16, No. 3,pp. 642-661, Apr. 1, 2012.
Gong Ren Hui et al.: “Interactive initialization of 2D/3D rigid registration”, Medical Physics, AIP, Melville, NY, US, vol. 40, No. 12, 14 pages, Dec. 2013.
Dumenil A et al.: “A versatile intensity-based 3D/2D rigid registration compatible with mobile C-arm for endovascular treatment of abdominal aortic aneurysm”, International Journal of Computer Assisted Radiology and Surgery, Springer, DE, vol. 11, No. 9, pp. 1713-1729, May 26, 2016.
Alk et al., “Smart Device Assisted Method for Rod Length and Rod Radius Measurement in Percutaneious Pedicle Screw Surgery”, Prizeglad Elektrotechniczny, vol. 3, Mar. 5, 2016, pp. 30-33.
Marintschev et al.: “Navigation of vertebra-pelvic fixations based on CT-fluoro macthing”, European Spine Journal, Springer, Berlin, DE, vol. 19, No. 11, pp. 1921-1927, Jun. 16, 2010.
Andreas Alk et a.: “Smart Device Assisted Method for Rod Length and Rod Radius Measurement in Percutaneous Pedicle Screw Surgery”, Przeglad Elektrotechniczny, vol. 3, Mar. 5, 2016 (Mar. 5, 2016), pp. 30-33, XP055668769, PO ISSN: 0033-2097, DOI: 10.15199/48.2016.03.07.
Related Publications (1)
Number Date Country
20180296283 A1 Oct 2018 US
Provisional Applications (3)
Number Date Country
61800527 Mar 2013 US
61662702 Jun 2012 US
62634245 Feb 2018 US
Continuation in Parts (5)
Number Date Country
Parent 15609334 May 2017 US
Child 16002047 US
Parent 15157444 May 2016 US
Child 15609334 US
Parent 15095883 Apr 2016 US
Child 15157444 US
Parent 14062707 Oct 2013 US
Child 15095883 US
Parent 13924505 Jun 2013 US
Child 14062707 US