US 12,575,901 B2Grant
Systems and methods for collision detection and avoidance
Issue Date:2026-03-17
•20 Claims
•29 Drawing Sheets
Abstract
In examples, a robotic medical system comprises a link of a robotic arm and a processor configured to control movement of the link based on a received input; determine a distance between the link and another object during the movement; and, responsive to the distance being within a threshold, adjust the movement of the link to avoid a collision between the link and the another object.
Metadata
Assignee
- Auris Health, Inc.
Inventors
- Yanan Huang
- Benjamin Robert Fredrickson
- Ryan J. Murphy
- Ying Mao
Application Information
Application Number:US 18/320,825
Filing Date:2023-05-19
Priority Date:2019-09-26
Art Unit:3656
Classifications
IPC:
A61B34/30A61B34/00B25J9/04B25J9/10B25J9/16
Field of Search:
A61B 34/30A61B 34/76A61B 2034/301B25J 9/04B25J 9/1666B25J 9/106
Patent Drawings (29 sheets)
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application is a continuation of U.S. application Ser. No. 17/162,498, filed Jan. 29, 2021, issued as U.S. Pat. No. 11,701,187 on Jul. 18, 2023, which is a continuation of U.S. application Ser. No. 17/025,718, filed Sep. 18, 2020, issued as U.S. Pat. No. 10,959,792 on Mar. 30, 2021, which claims the benefit of U.S. Provisional Application No. 62/906,612, filed Sep. 26, 2019, each of which is hereby incorporated by reference in its entirety.
TECHNICAL FIELD
[0002] The systems and methods disclosed herein are directed to surgical robotics, and more particularly to avoiding robotic arm collisions.
BACKGROUND
[0003] Medical procedures, such as laparoscopy, may involve accessing and visualizing an internal region of a patient. In a laparoscopic procedure, a medical tool can be inserted into the internal region through a laparoscopic cannula.
[0004] In certain procedures, a robotically-enabled medical system may be used to control the insertion and/or manipulation of one or more medical tool(s). The robotically-enabled medical system may have a plurality of robotic arms which control the medical tool(s). In positioning the medical tool(s), portion(s) of a given one of the robotic arms may move towards another robotic arm or other object in the environment, which can lead to collisions.
SUMMARY
[0005] The systems, methods and devices of this disclosure each have several innovative aspects, no single one of which is solely responsible for the desirable attributes disclosed herein.
[0006] In one aspect, there is provided a robotic medical system, comprising: a first set of links; a second set of links; a console configured to receive input commanding motion of the first set of links and the second set of links; a processor; and at least one computer-readable memory in communication with the processor and having stored thereon a model of the first set of links and the second set of links and computer-executable instructions to cause the processor to: access the model of the first set of links and the second set of links, control movement of the first set of links and the second set of links based on the input received by the console, determine a distance between the first set of links and the second set of links based on the model, and prevent a collision between the first set of links and the second set of links based on the determined distance.
[0007] In another aspect, there is provided a robotic medical system, comprising: a first set of links; a second set of links; a console configured to receive input commanding motion of the first set of links and the second set of links; a processor; and at least one computer-readable memory in communication with the processor and having stored thereon a model of the first set of links and the second set of links and computer-executable instructions to cause the processor to: control movement of the first set of links and the second set of links based on the input received by the console, determine a distance between the first set of links and the second set of links based on the model, determine that the distance between the first set of links and the second set of links is less than a cutoff distance, and prevent a collision in response to determining that the distance between the first set of links and the second set of links is less than the cutoff distance.
[0008] In yet another aspect, there is provided a method, comprising: accessing a model of a first set of links and a second set of links of a robotic medical system; controlling movement of the first set of links and the second set of links based on the input received by a console of the robotic medical system; determining a distance between the first set of links and the second set of links based on the model; and detecting and avoiding a collision between the first set of links and the second set of links based on the determined distance.
[0009] In still yet another aspect, there is provided a method, comprising: accessing a model of a first set of links and a second set of links of a robotic medical system; controlling movement of the first set of links and the second set of links based on an input received by a console of the robotic medical system; determining a distance between the first set of links and the second set of links based on the model; determining that the distance between the first set of links and the second set of links is less than a cutoff distance; and performing an action to prevent a collision in response to determining that the distance between the first set of links and the second set of links is less than the cutoff distance.
BRIEF DESCRIPTION OF THE DRAWINGS
[0010] The disclosed aspects will hereinafter be described in conjunction with the appended drawings, provided to illustrate and not to limit the disclosed aspects, wherein like designations denote like elements.
[0011] FIG. 1 illustrates an embodiment of a cart-based robotic system arranged for diagnostic and/or therapeutic bronchoscopy.
[0012] FIG. 2 depicts further aspects of the robotic system of FIG. 1 .
[0013] FIG. 3 illustrates an embodiment of the robotic system of FIG. 1 arranged for ureteroscopy.
[0014] FIG. 4 illustrates an embodiment of the robotic system of FIG. 1 arranged for a vascular procedure.
[0015] FIG. 5 illustrates an embodiment of a table-based robotic system arranged for a bronchoscopic procedure.
[0016] FIG. 6 provides an alternative view of the robotic system of FIG. 5 .
[0017] FIG. 7 illustrates an example system configured to stow robotic arm(s).
[0018] FIG. 8 illustrates an embodiment of a table-based robotic system configured for a ureteroscopic procedure.
[0019] FIG. 9 illustrates an embodiment of a table-based robotic system configured for a laparoscopic procedure.
[0020] FIG. 10 illustrates an embodiment of the table-based robotic system of FIGS. 5-9 with pitch or tilt adjustment.
[0021] FIG. 11 provides a detailed illustration of the interface between the table and the column of the table-based robotic system of FIGS. 5-10 .
[0022] FIG. 12 illustrates an alternative embodiment of a table-based robotic system.
[0023] FIG. 13 illustrates an end view of the table-based robotic system of FIG. 12 .
[0024] FIG. 14 illustrates an end view of a table-based robotic system with robotic arms attached thereto.
[0025] FIG. 15 illustrates an exemplary instrument driver.
[0026] FIG. 16 illustrates an exemplary medical instrument with a paired instrument driver.
[0027] FIG. 17 illustrates an alternative design for an instrument driver and instrument where the axes of the drive units are parallel to the axis of the elongated shaft of the instrument.
[0028] FIG. 18 illustrates an instrument having an instrument-based insertion architecture.
[0029] FIG. 19 illustrates an exemplary controller.
[0030] FIG. 20 depicts a block diagram illustrating a localization system that estimates a location of one or more elements of the robotic systems of FIGS. 1-10 , such as the location of the instrument of FIGS. 16-18 , in accordance to an example embodiment.
[0031] FIG. 21 illustrates an example view of a model of a robotic system in accordance with aspects of this disclosure.
[0032] FIG. 22 illustrates a model of a robotic system approximated using a geometric form in accordance with aspects of this disclosure.
[0033] FIG. 23 illustrates an example of an unavoidable collision which can be detected using a model of a robotic system in accordance with aspects of this disclosure.
[0034] FIG. 24 illustrates an example of an avoidable collision which can be detected using a model of a robotic system in accordance with aspects of this disclosure.
[0035] FIG. 25 is a flowchart illustrating an example method operable by a robotic system, or component(s) thereof, for detecting and avoiding collisions in accordance with aspects of this disclosure.
[0036] FIGS. 26A and 26B illustrate an example sequence of actions when a trigger distance is reached in accordance with aspects of this disclosure.
[0037] FIG. 27 illustrates the cutoff and trigger distances for a modeled link in accordance with aspects of this disclosure.
[0038] FIG. 28 is a flowchart illustrating an example method operable by a robotic system, or component(s) thereof, for detecting and avoiding collisions using a cutoff distance in accordance with aspects of this disclosure.
DETAILED DESCRIPTION
1. Overview
[0039] Aspects of the present disclosure may be integrated into a robotically-enabled medical system capable of performing a variety of medical procedures, including both minimally invasive, such as laparoscopy, and non-invasive, such as endoscopy, procedures. Among endoscopic procedures, the system may be capable of performing bronchoscopy, ureteroscopy, gastroscopy, etc.
[0040] In addition to performing the breadth of procedures, the system may provide additional benefits, such as enhanced imaging and guidance to assist the physician. Additionally, the system may provide the physician with the ability to perform the procedure from an ergonomic position without the need for awkward arm motions and positions. Still further, the system may provide the physician with the ability to perform the procedure with improved ease of use such that one or more of the instruments of the system can be controlled by a single user.
[0041] Various embodiments will be described below in conjunction with the drawings for purposes of illustration. It should be appreciated that many other implementations of the disclosed concepts are possible, and various advantages can be achieved with the disclosed implementations. Headings are included herein for reference and to aid in locating various sections. These headings are not intended to limit the scope of the concepts described with respect thereto. Such concepts may have applicability throughout the entire specification.
A. Robotic System—Cart.
[0042] The robotically-enabled medical system may be configured in a variety of ways depending on the particular procedure. FIG. 1 illustrates an embodiment of a cart-based robotically-enabled system 10 arranged for a diagnostic and/or therapeutic bronchoscopy. During a bronchoscopy, the system 10 may comprise a cart 11 having one or more robotic arms 12 to deliver a medical instrument, such as a steerable endoscope 13, which may be a procedure-specific bronchoscope for bronchoscopy, to a natural orifice access point (i.e., the mouth of the patient positioned on a table in the present example) to deliver diagnostic and/or therapeutic tools. As shown, the cart 11 may be positioned proximate to the patient's upper torso in order to provide access to the access point. Similarly, the robotic arms 12 may be actuated to position the bronchoscope relative to the access point. The arrangement in FIG. 1 may also be utilized when performing a gastro-intestinal (GI) procedure with a gastroscope, a specialized endoscope for GI procedures. FIG. 2 depicts an example embodiment of the cart in greater detail.
[0043] With continued reference to FIG. 1 , once the cart 11 is properly positioned, the robotic arms 12 may insert the steerable endoscope 13 into the patient robotically, manually, or a combination thereof. As shown, the steerable endoscope 13 may comprise at least two telescoping parts, such as an inner leader portion and an outer sheath portion, each portion coupled to a separate instrument driver from the set of instrument drivers 28, each instrument driver coupled to the distal end of an individual robotic arm. This linear arrangement of the instrument drivers 28, which facilitates coaxially aligning the leader portion with the sheath portion, creates a “virtual rail” 29 that may be repositioned in space by manipulating the one or more robotic arms 12 into different angles and/or positions. The virtual rails described herein are depicted in the Figures using dashed lines, and accordingly the dashed lines do not depict any physical structure of the system. Translation of the instrument drivers 28 along the virtual rail 29 telescopes the inner leader portion relative to the outer sheath portion or advances or retracts the endoscope 13 from the patient. The angle of the virtual rail 29 may be adjusted, translated, and pivoted based on clinical application or physician preference. For example, in bronchoscopy, the angle and position of the virtual rail 29 as shown represents a compromise between providing physician access to the endoscope 13 while minimizing friction that results from bending the endoscope 13 into the patient's mouth.
[0044] The endoscope 13 may be directed down the patient's trachea and lungs after insertion using precise commands from the robotic system until reaching the target destination or operative site. In order to enhance navigation through the patient's lung network and/or reach the desired target, the endoscope 13 may be manipulated to telescopically extend the inner leader portion from the outer sheath portion to obtain enhanced articulation and greater bend radius. The use of separate instrument drivers 28 also allows the leader portion and sheath portion to be driven independently of each other.
[0045] For example, the endoscope 13 may be directed to deliver a biopsy needle to a target, such as, for example, a lesion or nodule within the lungs of a patient. The needle may be deployed down a working channel that runs the length of the endoscope to obtain a tissue sample to be analyzed by a pathologist. Depending on the pathology results, additional tools may be deployed down the working channel of the endoscope for additional biopsies. After identifying a nodule to be malignant, the endoscope 13 may endoscopically deliver tools to resect the potentially cancerous tissue. In some instances, diagnostic and therapeutic treatments can be delivered in separate procedures. In those circumstances, the endoscope 13 may also be used to deliver a fiducial to “mark” the location of the target nodule as well. In other instances, diagnostic and therapeutic treatments may be delivered during the same procedure.
[0046] The system 10 may also include a movable tower 30, which may be connected via support cables to the cart 11 to provide support for controls, electronics, fluidics, optics, sensors, and/or power to the cart 11. Placing such functionality in the tower 30 allows for a smaller form factor cart 11 that may be more easily adjusted and/or re-positioned by an operating physician and his/her staff. Additionally, the division of functionality between the cart I table and the support tower 30 reduces operating room clutter and facilitates improving clinical workflow. While the cart 11 may be positioned close to the patient, the tower 30 may be stowed in a remote location to stay out of the way during a procedure.
[0047] In support of the robotic systems described above, the tower 30 may include component(s) of a computer-based control system that stores computer program instructions, for example, within a non-transitory computer-readable storage medium such as a persistent magnetic storage drive, solid state drive, etc. The execution of those instructions, whether the execution occurs in the tower 30 or the cart 11, may control the entire system or sub-system(s) thereof. For example, when executed by a processor of the computer system, the instructions may cause the components of the robotics system to actuate the relevant carriages and arm mounts, actuate the robotics arms, and control the medical instruments. For example, in response to receiving the control signal, the motors in the joints of the robotics arms may position the arms into a certain posture.
[0048] The tower 30 may also include a pump, flow meter, valve control, and/or fluid access in order to provide controlled irrigation and aspiration capabilities to the system that may be deployed through the endoscope 13. These components may also be controlled using the computer system of the tower 30. In some embodiments, irrigation and aspiration capabilities may be delivered directly to the endoscope 13 through separate cable(s).
[0049] The tower 30 may include a voltage and surge protector designed to provide filtered and protected electrical power to the cart 11, thereby avoiding placement of a power transformer and other auxiliary power components in the cart 11, resulting in a smaller, more moveable cart 11.
[0050] The tower 30 may also include support equipment for the sensors deployed throughout the robotic system 10. For example, the tower 30 may include optoelectronics equipment for detecting, receiving, and processing data received from the optical sensors or cameras throughout the robotic system 10. In combination with the control system, such optoelectronics equipment may be used to generate real-time images for display in any number of consoles deployed throughout the system, including in the tower 30. Similarly, the tower 30 may also include an electronic subsystem for receiving and processing signals received from deployed electromagnetic (EM) sensors. The tower 30 may also be used to house and position an EM field generator for detection by EM sensors in or on the medical instrument.
[0051] The tower 30 may also include a console 31 in addition to other consoles available in the rest of the system, e.g., console mounted on top of the cart. The console 31 may include a user interface and a display screen, such as a touchscreen, for the physician operator. Consoles in the system 10 are generally designed to provide both robotic controls as well as preoperative and real-time information of the procedure, such as navigational and localization information of the endoscope 13. When the console 31 is not the only console available to the physician, it may be used by a second operator, such as a nurse, to monitor the health or vitals of the patient and the operation of the system 10, as well as to provide procedure-specific data, such as navigational and localization information. In other embodiments, the console 30 is housed in a body that is separate from the tower 30.
[0052] The tower 30 may be coupled to the cart 11 and endoscope 13 through one or more cables or connections (not shown). In some embodiments, the support functionality from the tower 30 may be provided through a single cable to the cart 11, simplifying and de-cluttering the operating room. In other embodiments, specific functionality may be coupled in separate cabling and connections. For example, while power may be provided through a single power cable to the cart 11, the support for controls, optics, fluidics, and/or navigation may be provided through a separate cable.
[0053] FIG. 2 provides a detailed illustration of an embodiment of the cart 11 from the cart-based robotically-enabled system shown in FIG. 1 . The cart 11 generally includes an elongated support structure 14 (often referred to as a “column”), a cart base 15, and a console 16 at the top of the column 14. The column 14 may include one or more carriages, such as a carriage 17 (alternatively “arm support”) for supporting the deployment of one or more robotic arms 12 (three shown in FIG. 2 ). The carriage 17 may include individually configurable arm mounts that rotate along a perpendicular axis to adjust the base of the robotic arms 12 for better positioning relative to the patient. The carriage 17 also includes a carriage interface 19 that allows the carriage 17 to vertically translate along the column 14.
[0054] The carriage interface 19 is connected to the column 14 through slots, such as slot 20, that are positioned on opposite sides of the column 14 to guide the vertical translation of the carriage 17. The slot 20 contains a vertical translation interface to position and hold the carriage 17 at various vertical heights relative to the cart base 15. Vertical translation of the carriage 17 allows the cart 11 to adjust the reach of the robotic arms 12 to meet a variety of table heights, patient sizes, and physician preferences. Similarly, the individually configurable arm mounts on the carriage 17 allow the robotic arm base 21 of the robotic arms 12 to be angled in a variety of configurations.
[0055] In some embodiments, the slot 20 may be supplemented with slot covers that are flush and parallel to the slot surface to prevent dirt and fluid ingress into the internal chambers of the column 14 and the vertical translation interface as the carriage 17 vertically translates. The slot covers may be deployed through pairs of spring spools positioned near the vertical top and bottom of the slot 20. The covers are coiled within the spools until deployed to extend and retract from their coiled state as the carriage 17 vertically translates up and down. The spring-loading of the spools provides force to retract the cover into a spool when the carriage 17 translates towards the spool, while also maintaining a tight seal when the carriage 17 translates away from the spool. The covers may be connected to the carriage 17 using, for example, brackets in the carriage interface 19 to ensure proper extension and retraction of the cover as the carriage 17 translates.
[0056] The column 14 may internally comprise mechanisms, such as gears and motors, that are designed to use a vertically aligned lead screw to translate the carriage 17 in a mechanized fashion in response to control signals generated in response to user inputs, e.g., inputs from the console 16.
[0057] The robotic arms 12 may generally comprise robotic arm bases 21 and end effectors 22, separated by a series of linkages 23 that are connected by a series of joints 24, each joint comprising an independent actuator, each actuator comprising an independently controllable motor. Each independently controllable joint represents an independent degree-of-freedom (DoF) available to the robotic arm 12. Each of the robotic arms 12 may have seven joints, and thus provide seven degrees of freedom. A multitude of joints result in a multitude of degrees of freedom, allowing for “redundant” degrees of freedom. Having redundant degrees of freedom allows the robotic arms 12 to position their respective end effectors 22 at a specific position, orientation, and trajectory in space using different linkage positions and joint angles. This allows for the system to position and direct a medical instrument from a desired point in space while allowing the physician to move the arm joints into a clinically advantageous position away from the patient to create greater access, while avoiding arm collisions.
[0058] The cart base 15 balances the weight of the column 14, carriage 17, and robotic arms 12 over the floor. Accordingly, the cart base 15 houses heavier components, such as electronics, motors, power supply, as well as components that either enable movement and/or immobilize the cart I1. For example, the cart base 15 includes rollable wheel-shaped casters 25 that allow for the cart 11 to easily move around the room prior to a procedure. After reaching the appropriate position, the casters 25 may be immobilized using wheel locks to hold the cart 11 in place during the procedure.
[0059] Positioned at the vertical end of the column 14, the console 16 allows for both a user interface for receiving user input and a display screen (or a dual-purpose device such as, for example, a touchscreen 26) to provide the physician user with both preoperative and intraoperative data. Potential preoperative data on the touchscreen 26 may include preoperative plans, navigation and mapping data derived from preoperative computerized tomography (CT) scans, and/or notes from preoperative patient interviews. Intraoperative data on display may include optical information provided from the tool, sensor and coordinate information from sensors, as well as vital patient statistics, such as respiration, heart rate, and/or pulse. The console 16 may be positioned and tilted to allow a physician to access the console 16 from the side of the column 14 opposite the carriage 17. From this position, the physician may view the console 16, robotic arms 12, and patient while operating the console 16 from behind the cart 11. As shown, the console 16 also includes a handle 27 to assist with maneuvering and stabilizing the cart 11.
[0060] FIG. 3 illustrates an embodiment of a robotically-enabled system 10 arranged for ureteroscopy. In a ureteroscopic procedure, the cart 11 may be positioned to deliver a ureteroscope 32, a procedure-specific endoscope designed to traverse a patient's urethra and ureter, to the lower abdominal area of the patient. In a ureteroscopy, it may be desirable for the ureteroscope 32 to be directly aligned with the patient's urethra to reduce friction and forces on the sensitive anatomy in the area. As shown, the cart 11 may be aligned at the foot of the table to allow the robotic arms 12 to position the ureteroscope 32 for direct linear access to the patient's urethra. From the foot of the table, the robotic arms 12 may insert the ureteroscope 32 along the virtual rail 33 directly into the patient's lower abdomen through the urethra.
[0061] After insertion into the urethra, using similar control techniques as in bronchoscopy, the ureteroscope 32 may be navigated into the bladder, ureters, and/or kidneys for diagnostic and/or therapeutic applications. For example, the ureteroscope 32 may be directed into the ureter and kidneys to break up kidney stone build up using a laser or ultrasonic lithotripsy device deployed down the working channel of the ureteroscope 32. After lithotripsy is complete, the resulting stone fragments may be removed using baskets deployed down the ureteroscope 32.
[0062] FIG. 4 illustrates an embodiment of a robotically-enabled system 10 similarly arranged for a vascular procedure. In a vascular procedure, the system 10 may be configured such that the cart 11 may deliver a medical instrument 34, such as a steerable catheter, to an access point in the femoral artery in the patient's leg. The femoral artery presents both a larger diameter for navigation as well as a relatively less circuitous and tortuous path to the patient's heart, which simplifies navigation. As in a ureteroscopic procedure, the cart 11 may be positioned towards the patient's legs and lower abdomen to allow the robotic arms 12 to provide a virtual rail 35 with direct linear access to the femoral artery access point in the patient's thigh/hip region. After insertion into the artery, the medical instrument 34 may be directed and inserted by translating the instrument drivers 28. Alternatively, the cart may be positioned around the patient's upper abdomen in order to reach alternative vascular access points, such as, for example, the carotid and brachia! arteries near the shoulder and wrist.
B. Robotic System—Table.
[0063] Embodiments of the robotically-enabled medical system may also incorporate the patient's table. Incorporation of the table reduces the amount of capital equipment within the operating room by removing the cart, which allows greater access to the patient. FIG. 5 illustrates an embodiment of such a robotically-enabled system arranged for a bronchoscopic procedure. System 36 includes a support structure or column 37 for supporting platform 38 (shown as a “table” or “bed”) over the floor. Much like in the cart-based systems, the end effectors of the robotic arms 39 of the system 36 comprise instrument drivers 42 that are designed to manipulate an elongated medical instrument, such as a bronchoscope 40 in FIG. 5 , through or along a virtual rail 41 formed from the linear alignment of the instrument drivers 42. In practice, a C-arm for providing fluoroscopic imaging may be positioned over the patient's upper abdominal area by placing the emitter and detector around the table 38.
[0064] FIG. 6 provides an alternative view of the system 36 without the patient and medical instrument for discussion purposes. As shown, the column 37 may include one or more carriages 43 shown as ring-shaped in the system 36, from which the one or more robotic arms 39 may be based. The carriages 43 may translate along a vertical column interface 44 that runs the length of the column 37 to provide different vantage points from which the robotic arms 39 may be positioned to reach the patient. The carriage(s) 43 may rotate around the column 37 using a mechanical motor positioned within the column 37 to allow the robotic arms 39 to have access to multiples sides of the table 38, such as, for example, both sides of the patient. In embodiments with multiple carriages, the carriages may be individually positioned on the column and may translate and/or rotate independently of the other carriages. While the carriages 43 need not surround the column 37 or even be circular, the ring-shape as shown facilitates rotation of the carriages 43 around the column 37 while maintaining structural balance. Rotation and translation of the carriages 43 allows the system 36 to align the medical instruments, such as endoscopes and laparoscopes, into different access points on the patient. In other embodiments (not shown), the system 36 can include a patient table or bed with adjustable arm supports in the form of bars or rails extending alongside it. One or more robotic arms 39 (e.g., via a shoulder with an elbow joint) can be attached to the adjustable arm supports, which can be vertically adjusted. By providing vertical adjustment, the robotic arms 39 are advantageously capable of being stowed compactly beneath the patient table or bed, and subsequently raised during a procedure.
[0065] The robotic arms 39 may be mounted on the carriages 43 through a set of arm mounts 45 comprising a series of joints that may individually rotate and/or telescopically extend to provide additional configurability to the robotic arms 39. Additionally, the arm mounts 45 may be positioned on the carriages 43 such that, when the carriages 43 are appropriately rotated, the arm mounts 45 may be positioned on either the same side of the table 38 (as shown in FIG. 6 ), on opposite sides of the table 38 (as shown in FIG. 9 ), or on adjacent sides of the table 38 (not shown).
[0066] The column 37 structurally provides support for the table 38, and a path for vertical translation of the carriages 43. Internally, the column 37 may be equipped with lead screws for guiding vertical translation of the carriages, and motors to mechanize the translation of the carriages 43 based the lead screws. The column 37 may also convey power and control signals to the carriages 43 and the robotic arms 39 mounted thereon.
[0067] The table base 46 serves a similar function as the cart base 15 in the cart 11 shown in FIG. 2 , housing heavier components to balance the table/bed 38, the column 37, the carriages 43, and the robotic arms 39. The table base 46 may also incorporate rigid casters to provide stability during procedures. Deployed from the bottom of the table base 46, the casters may extend in opposite directions on both sides of the base 46 and retract when the system 36 needs to be moved.
[0068] With continued reference to FIG. 6 , the system 36 may also include a tower (not shown) that divides the functionality of the system 36 between the table and the tower to reduce the form factor and bulk of the table. As in earlier disclosed embodiments, the tower may provide a variety of support functionalities to the table, such as processing, computing, and control capabilities, power, fluidics, and/or optical and sensor processing. The tower may also be movable to be positioned away from the patient to improve physician access and de-clutter the operating room. Additionally, placing components in the tower allows for more storage space in the table base 46 for potential stowage of the robotic arms 39. The tower may also include a master controller or console that provides both a user interface for user input, such as keyboard and/or pendant, as well as a display screen (or touchscreen) for preoperative and intraoperative information, such as real-time imaging, navigation, and tracking information. In some embodiments, the tower may also contain holders for gas tanks to be used for insufflation.
[0069] In some embodiments, a table base may stow and store the robotic arms when not in use. FIG. 7 illustrates a system 47 that stows robotic arms in an embodiment of the table-based system. In the system 47, carriages 48 may be vertically translated into base 49 to stow robotic arms 50, arm mounts 51, and the carriages 48 within the base 49. Base covers 52 may be translated and retracted open to deploy the carriages 48, arm mounts 51, and robotic arms 50 around column 53, and closed to stow to protect them when not in use. The base covers 52 may be sealed with a membrane 54 along the edges of its opening to prevent dirt and fluid ingress when closed.
[0070] FIG. 8 illustrates an embodiment of a robotically-enabled table-based system configured for a ureteroscopic procedure. In a ureteroscopy, the table 38 may include a swivel portion 55 for positioning a patient off-angle from the column 37 and table base 46. The swivel portion 55 may rotate or pivot around a pivot point (e.g., located below the patient's head) in order to position the bottom portion of the swivel portion 55 away from the column 37. For example, the pivoting of the swivel portion 55 allows a C-arm (not shown) to be positioned over the patient's lower abdomen without competing for space with the column (not shown) below table 38. By rotating the carriage 35 (not shown) around the column 37, the robotic arms 39 may directly insert a ureteroscope 56 along a virtual rail 57 into the patient's groin area to reach the urethra. In a ureteroscopy, stirrups 58 may also be fixed to the swivel portion 55 of the table 38 to support the position of the patient's legs during the procedure and allow clear access to the patient's groin area.
[0071] In a laparoscopic procedure, through small incision(s) in the patient's abdominal wall, minimally invasive instruments may be inserted into the patient's anatomy. In some embodiments, the minimally invasive instruments comprise an elongated rigid member, such as a shaft, which is used to access anatomy within the patient. After inflation of the patient's abdominal cavity, the instruments may be directed to perform surgical or medical tasks, such as grasping, cutting, ablating, suturing, etc. In some embodiments, the instruments can comprise a scope, such as a laparoscope. FIG. 9 illustrates an embodiment of a robotically-enabled table-based system configured for a laparoscopic procedure. As shown in FIG. 9 , the carriages 43 of the system 36 may be rotated and vertically adjusted to position pairs of the robotic arms 39 on opposite sides of the table 38, such that instrument 59 may be positioned using the arm mounts 45 to be passed through minimal incisions on both sides of the patient to reach his/her abdominal cavity.
[0072] To accommodate laparoscopic procedures, the robotically-enabled table system may also tilt the platform to a desired angle. FIG. 10 illustrates an embodiment of the robotically-enabled medical system with pitch or tilt adjustment. As shown in FIG. 10 , the system 36 may accommodate tilt of the table 38 to position one portion of the table at a greater distance from the floor than the other. Additionally, the arm mounts 45 may rotate to match the tilt such that the robotic arms 39 maintain the same planar relationship with the table 38. To accommodate steeper angles, the column 37 may also include telescoping portions 60 that allow vertical extension of the column 37 to keep the table 38 from touching the floor or colliding with the table base 46.
[0073] FIG. 11 provides a detailed illustration of the interface between the table 38 and the column 37. Pitch rotation mechanism 61 may be configured to alter the pitch angle of the table 38 relative to the column 37 in multiple degrees of freedom. The pitch rotation mechanism 61 may be enabled by the positioning of orthogonal axes 1, 2 at the column-table interface, each axis actuated by a separate motor 3, 4 responsive to an electrical pitch angle command. Rotation along one screw 5 would enable tilt adjustments in one axis 1, while rotation along the other screw 6 would enable tilt adjustments along the other axis 2. In some embodiments, a ball joint can be used to alter the pitch angle of the table 38 relative to the column 37 in multiple degrees of freedom.
[0074] For example, pitch adjustments are particularly useful when trying to position the table in a Trendelenburg position, i.e., position the patient's lower abdomen at a higher position from the floor than the patient's upper abdomen, for lower abdominal surgery. The Trendelenburg position causes the patient's internal organs to slide towards his/her upper abdomen through the force of gravity, clearing out the abdominal cavity for minimally invasive tools to enter and perform lower abdominal surgical or medical procedures, such as laparoscopic prostatectomy.
[0075] FIGS. 12 and 13 illustrate isometric and end views of an alternative embodiment of a table-based surgical robotics system 100. The surgical robotics system 100 includes one or more adjustable arm supports 105 that can be configured to support one or more robotic arms (see, for example, FIG. 14 ) relative to a table 101. In the illustrated embodiment, a single adjustable arm support 105 is shown, though an additional arm support can be provided on an opposite side of the table 101. The adjustable arm support 105 can be configured so that it can move relative to the table IOI to adjust and/or vary the position of the adjustable arm support 105 and/or any robotic arms mounted thereto relative to the table 101. For example, the adjustable arm support 105 may be adjusted one or more degrees of freedom relative to the table 101. The adjustable arm support 105 provides high versatility to the system 100, including the ability to easily stow the one or more adjustable arm supports 105 and any robotics arms attached thereto beneath the table 101. The adjustable arm support 105 can be elevated from the stowed position to a position below an upper surface of the table IO1. In other embodiments, the adjustable arm support 105 can be elevated from the stowed position to a position above an upper surface of the table IO1.
[0076] The adjustable arm support 105 can provide several degrees of freedom, including lift, lateral translation, tilt, etc. In the illustrated embodiment of FIGS. 12 and 13 , the arm support 105 is configured with four degrees of freedom, which are illustrated with arrows in FIG. 12 . A first degree of freedom allows for adjustment of the adjustable arm support 105 in the z-direction (“Z-lift”). For example, the adjustable arm support 105 can include a carriage 109 configured to move up or down along or relative to a column 102 supporting the table 101. A second degree of freedom can allow the adjustable arm support 105 to tilt. For example, the adjustable arm support 105 can include a rotary joint, which can allow the adjustable arm support 105 to be aligned with the bed in a Trendelenburg position. A third degree of freedom can allow the adjustable arm support 105 to “pivot up,” which can be used to adjust a distance between a side of the table 101 and the adjustable arm support 105. A fourth degree of freedom can permit translation of the adjustable arm support 105 along a longitudinal length of the table.
[0077] The surgical robotics system 100 in FIGS. 12 and 13 can comprise a table supported by a column 102 that is mounted to a base 103. The base 103 and the column 102 support the table 10 I relative to a support surface. A floor axis 131 and a support axis 133 are shown in FIG. 13 .
[0078] The adjustable arm support 105 can be mounted to the column 102. In other embodiments, the arm support 105 can be mounted to the table 101 or base 103. The adjustable arm support 105 can include a carriage 109, a bar or rail connector 111 and a bar or rail 107. In some embodiments, one or more robotic arms mounted to the rail 107 can translate and move relative to one another.
[0079] The carriage 109 can be attached to the column 102 by a first joint 113, which allows the carriage 109 to move relative to the column 102 (e.g., such as up and down a first or vertical axis 123). The first joint 113 can provide the first degree of freedom (“Z-lift”) to the adjustable arm support 105. The adjustable arm support 105 can include a second joint 115, which provides the second degree of freedom (tilt) for the adjustable arm support 105. The adjustable arm support 105 can include a third joint 117, which can provide the third degree of freedom (“pivot up”) for the adjustable arm support 105. An additional joint 119 (shown in FIG. 13 ) can be provided that mechanically constrains the third joint 117 to maintain an orientation of the rail 107 as the rail connector 111 is rotated about a third axis 127. The adjustable arm support 105 can include a fourth joint 121, which can provide a fourth degree of freedom (translation) for the adjustable arm support 105 along a fourth axis 129.
[0080] FIG. 14 illustrates an end view of the surgical robotics system 140A with two adjustable arm supports 105A, 105B mounted on opposite sides of a table 101. A first robotic arm 142A is attached to the bar or rail 107A of the first adjustable arm support 105B. The first robotic arm 142A includes a base 144A attached to the rail 107A. The distal end of the first robotic arm 142A includes an instrument drive mechanism 146A that can attach to one or more robotic medical instruments or tools. Similarly, the second robotic arm 142B includes a base 144B attached to the rail 107B. The distal end of the second robotic arm 142B includes an instrument drive mechanism 146B. The instrument drive mechanism 146B can be configured to attach to one or more robotic medical instruments or tools.
[0081] In some embodiments, one or more of the robotic arms 142A, 142B comprises an arm with seven or more degrees of freedom. In some embodiments, one or more of the robotic arms 142A, 142B can include eight degrees of freedom, including an insertion axis (1-degree of freedom including insertion), a wrist (3-degrees of freedom including wrist pitch, yaw and roll), an elbow (1-degree of freedom including elbow pitch), a shoulder (2-degrees of freedom including shoulder pitch and yaw), and base 144A, 144B (1-degree of freedom including translation). In some embodiments, the insertion degree of freedom can be provided by the robotic arm 142A, 142B, while in other embodiments, the instrument itself provides insertion via an instrument-based insertion architecture.
C. Instrument Driver & Interface.
[0082] The end effectors of the system's robotic arms may comprise (i) an instrument driver (alternatively referred to as “instrument drive mechanism” or “instrument device manipulator”) that incorporates electro-mechanical means for actuating the medical instrument and (ii) a removable or detachable medical instrument, which may be devoid of any electro-mechanical components, such as motors. This dichotomy may be driven by the need to sterilize medical instruments used in medical procedures, and the inability to adequately sterilize expensive capital equipment due to their intricate mechanical assemblies and sensitive electronics. Accordingly, the medical instruments may be designed to be detached, removed, and interchanged from the instrument driver (and thus the system) for individual sterilization or disposal by the physician or the physician's staff. In contrast, the instrument drivers need not be changed or sterilized, and may be draped for protection.
[0083] FIG. 15 illustrates an example instrument driver. Positioned at the distal end of a robotic arm, instrument driver 62 comprises one or more drive units 63 arranged with parallel axes to provide controlled torque to a medical instrument via drive shafts 64. Each drive unit 63 comprises an individual drive shaft 64 for interacting with the instrument, a gear head 65 for converting the motor shaft rotation to a desired torque, a motor 66 for generating the drive torque, an encoder 67 to measure the speed of the motor shaft and provide feedback to the control circuitry, and control circuitry 68 for receiving control signals and actuating the drive unit. Each drive unit 63 being independently controlled and motorized, the instrument driver 62 may provide multiple (e.g., four as shown in FIG. 15 ) independent drive outputs to the medical instrument. In operation, the control circuitry 68 would receive a control signal, transmit a motor signal to the motor 66, compare the resulting motor speed as measured by the encoder 67 with the desired speed, and modulate the motor signal to generate the desired torque.
[0084] For procedures that require a sterile environment, the robotic system may incorporate a drive interface, such as a sterile adapter connected to a sterile drape, that sits between the instrument driver and the medical instrument. The chief purpose of the sterile adapter is to transfer angular motion from the drive shafts of the instrument driver to the drive inputs of the instrument while maintaining physical separation, and thus sterility, between the drive shafts and drive inputs. Accordingly, an example sterile adapter may comprise a series of rotational inputs and outputs intended to be mated with the drive shafts of the instrument driver and drive inputs on the instrument. Connected to the sterile adapter, the sterile drape, comprised of a thin, flexible material such as transparent or translucent plastic, is designed to cover the capital equipment, such as the instrument driver, robotic arm, and cart (in a cart-based system) or table (in a table-based system). Use of the drape would allow the capital equipment to be positioned proximate to the patient while still being located in an area not requiring sterilization (i.e., non-sterile field). On the other side of the sterile drape, the medical instrument may interface with the patient in an area requiring sterilization (i.e., sterile field).
D. Medical Instrument.
[0085] FIG. 16 illustrates an example medical instrument with a paired instrument driver. Like other instruments designed for use with a robotic system, medical instrument 70 comprises an elongated shaft 71 (or elongate body) and an instrument base 72. The instrument base 72, also referred to as an “instrument handle” due to its intended design for manual interaction by the physician, may generally comprise rotatable drive inputs 73, e.g., receptacles, pulleys or spools, that are designed to be mated with drive outputs 74 that extend through a drive interface on instrument driver 75 at the distal end of robotic arm 76. When physically connected, latched, and/or coupled, the mated drive inputs 73 of the instrument base 72 may share axes of rotation with the drive outputs 74 in the instrument driver 75 to allow the transfer of torque from the drive outputs 74 to the drive inputs 73. In some embodiments, the drive outputs 74 may comprise splines that are designed to mate with receptacles on the drive inputs 73.
[0086] The elongated shaft 71 is designed to be delivered through either an anatomical opening or lumen, e.g., as in endoscopy, or a minimally invasive incision, e.g., as in laparoscopy. The elongated shaft 71 may be either flexible (e.g., having properties similar to an endoscope) or rigid (e.g., having properties similar to a laparoscope) or contain a customized combination of both flexible and rigid portions. When designed for laparoscopy, the distal end of a rigid elongated shaft may be connected to an end effector extending from a jointed wrist formed from a clevis with at least one degree of freedom and a surgical tool or medical instrument, such as, for example, a grasper or scissors, that may be actuated based on force from the tendons as the drive inputs rotate in response to torque received from the drive outputs 74 of the instrument driver 75. When designed for endoscopy, the distal end of a flexible elongated shaft may include a steerable or controllable bending section that may be articulated and bent based on torque received from the drive outputs 74 of the instrument driver 75.
[0087] Torque from the instrument driver 75 is transmitted down the elongated shaft 71 using tendons along the elongated shaft 71. These individual tendons, such as pull wires, may be individually anchored to individual drive inputs 73 within the instrument handle 72. From the handle 72, the tendons are directed down one or more pull lumens along the elongated shaft 71 and anchored at the distal portion of the elongated shaft 71, or in the wrist at the distal portion of the elongated shaft. During a surgical procedure, such as a laparoscopic, endoscopic or hybrid procedure, these tendons may be coupled to a distally mounted end effector, such as a wrist, grasper, or scissor. Under such an arrangement, torque exerted on drive inputs 73 would transfer tension to the tendon, thereby causing the end effector to actuate in some way. In some embodiments, during a surgical procedure, the tendon may cause a joint to rotate about an axis, thereby causing the end effector to move in one direction or another. Alternatively, the tendon may be connected to one or more jaws of a grasper at the distal end of the elongated shaft 71, where tension from the tendon causes the grasper to close.
[0088] In endoscopy, the tendons may be coupled to a bending or articulating section positioned along the elongated shaft 71 (e.g., at the distal end) via adhesive, control ring, or other mechanical fixation. When fixedly attached to the distal end of a bending section, torque exerted on the drive inputs 73 would be transmitted down the tendons, causing the softer, bending section (sometimes referred to as the articulable section or region) to bend or articulate. Along the non-bending sections, it may be advantageous to spiral or helix the individual pull lumens that direct the individual tendons along (or inside) the walls of the endoscope shaft to balance the radial forces that result from tension in the pull wires. The angle of the spiraling and/or spacing therebetween may be altered or engineered for specific purposes, wherein tighter spiraling exhibits lesser shaft compression under load forces, while lower amounts of spiraling results in greater shaft compression under load forces, but limits bending. On the other end of the spectrum, the pull lumens may be directed parallel to the longitudinal axis of the elongated shaft 71 to allow for controlled articulation in the desired bending or articulable sections.
[0089] In endoscopy, the elongated shaft 71 houses a number of components to assist with the robotic procedure. The shaft 71 may comprise a working channel for deploying surgical tools (or medical instruments), irrigation, and/or aspiration to the operative region at the distal end of the shaft 71. The shaft 71 may also accommodate wires and/or optical fibers to transfer signals to/from an optical assembly at the distal tip, which may include an optical camera. The shaft 71 may also accommodate optical fibers to carry light from proximally-located light sources, such as light emitting diodes, to the distal end of the shaft 71.
[0090] At the distal end of the instrument 70, the distal tip may also comprise the opening of a working channel for delivering tools for diagnostic and/or therapy, irrigation, and aspiration to an operative site. The distal tip may also include a port for a camera, such as a fiberscope or a digital camera, to capture images of an internal anatomical space. Relatedly, the distal tip may also include ports for light sources for illuminating the anatomical space when using the camera.
[0091] In the example of FIG. 16 , the drive shaft axes, and thus the drive input axes, are orthogonal to the axis of the elongated shaft 71. This arrangement, however, complicates roll capabilities for the elongated shaft 71. Rolling the elongated shaft 71 along its axis while keeping the drive inputs 73 static results in undesirable tangling of the tendons as they extend off the drive inputs 73 and enter pull lumens within the elongated shaft 71. The resulting entanglement of such tendons may disrupt any control algorithms intended to predict movement of the flexible elongated shaft 71 during an endoscopic procedure.
[0092] FIG. 17 illustrates an alternative design for an instrument driver and instrument where the axes of the drive units are parallel to the axis of the elongated shaft of the instrument. As shown, a circular instrument driver 80 comprises four drive units with their drive outputs 81 aligned in parallel at the end of a robotic arm 82. The drive units, and their respective drive outputs 81, are housed in a rotational assembly 83 of the instrument driver 80 that is driven by one of the drive units within the assembly 83. In response to torque provided by the rotational drive unit, the rotational assembly 83 rotates along a circular bearing that connects the rotational assembly 83 to the non-rotational portion 84 of the instrument driver 80. Power and controls signals may be communicated from the non-rotational portion 84 of the instrument driver 80 to the rotational assembly 83 through electrical contacts that may be maintained through rotation by a brushed slip ring connection (not shown). In other embodiments, the rotational assembly 83 may be responsive to a separate drive unit that is integrated into the non-rotatable portion 84, and thus not in parallel to the other drive units. The rotational mechanism 83 allows the instrument driver 80 to rotate the drive units, and their respective drive outputs 81, as a single unit around an instrument driver axis 85.
[0093] Like earlier disclosed embodiments, an instrument 86 may comprise an elongated shaft portion 88 and an instrument base 87 (shown with a transparent external skin for discussion purposes) comprising a plurality of drive inputs 89 (such as receptacles, pulleys, and spools) that are configured to receive the drive outputs 81 in the instrument driver 80. Unlike prior disclosed embodiments, the instrument shaft 88 extends from the center of the instrument base 87 with an axis substantially parallel to the axes of the drive inputs 89, rather than orthogonal as in the design of FIG. 16 .
[0094] When coupled to the rotational assembly 83 of the instrument driver 80, the medical instrument 86, comprising instrument base 87 and instrument shaft 88, rotates in combination with the rotational assembly 83 about the instrument driver axis 85. Since the instrument shaft 88 is positioned at the center of instrument base 87, the instrument shaft 88 is coaxial with instrument driver axis 85 when attached. Thus, rotation of the rotational assembly 83 causes the instrument shaft 88 to rotate about its own longitudinal axis. Moreover, as the instrument base 87 rotates with the instrument shaft 88, any tendons connected to the drive inputs 89 in the instrument base 87 are not tangled during rotation. Accordingly, the parallelism of the axes of the drive outputs 81, drive inputs 89, and instrument shaft 88 allows for the shaft rotation without tangling any control tendons.
[0095] FIG. 18 illustrates an instrument having an instrument based insertion architecture in accordance with some embodiments. The instrument 150 can be coupled to any of the instrument drivers discussed above. The instrument 150 comprises an elongated shaft 152, an end effector 162 connected to the shaft 152, and a handle 170 coupled to the shaft 152. The elongated shaft 152 comprises a tubular member having a proximal portion 154 and a distal portion 156. The elongated shaft 152 comprises one or more channels or grooves 158 along its outer surface. The grooves 158 are configured to receive one or more wires or cables 180 therethrough. One or more cables 180 thus run along an outer surface of the elongated shaft 152. In other embodiments, cables 180 can also run through the elongated shaft 152. Manipulation of the one or more cables 180 (e.g., via an instrument driver) results in actuation of the end effector 162.
[0096] The instrument handle 170, which may also be referred to as an instrument base, may generally comprise an attachment interface 172 having one or more mechanical inputs 174, e.g., receptacles, pulleys or spools, that are designed to be reciprocally mated with one or more torque couplers on an attachment surface of an instrument driver.
[0097] In some embodiments, the instrument 150 comprises a series of pulleys or cables that enable the elongated shaft 152 to translate relative to the handle 170. In other words, the instrument 150 itself comprises an instrument-based insertion architecture that accommodates insertion of the instrument, thereby minimizing the reliance on a robot arm to provide insertion of the instrument 150. In other embodiments, a robotic arm can be largely responsible for instrument insertion.
E. Controller.
[0098] Any of the robotic systems described herein can include an input device or controller for manipulating an instrument attached to a robotic arm. In some embodiments, the controller can be coupled (e.g., communicatively, electronically, electrically, wirelessly and/or mechanically) with an instrument such that manipulation of the controller causes a corresponding manipulation of the instrument e.g., via master slave control.
[0099] FIG. 19 is a perspective view of an embodiment of a controller 182. In the present embodiment, the controller 182 comprises a hybrid controller that can have both impedance and admittance control. In other embodiments, the controller 182 can utilize just impedance or passive control. In other embodiments, the controller 182 can utilize just admittance control. By being a hybrid controller, the controller 182 advantageously can have a lower perceived inertia while in use.
[0100] In the illustrated embodiment, the controller 182 is configured to allow manipulation of two medical instruments, and includes two handles 184. Each of the handles 184 is connected to a gimbal 186. Each gimbal 186 is connected to a positioning platform 188.
[0101] As shown in FIG. 19 , each positioning platform 188 includes a SCARA arm (selective compliance assembly robot arm) 198 coupled to a column 194 by a prismatic joint 196. The prismatic joints 196 are configured to translate along the column 194 (e.g., along rails 197) to allow each of the handles 184 to be translated in the z-direction, providing a first degree of freedom. The SCARA arm 198 is configured to allow motion of the handle 184 in an x-y plane, providing two additional degrees of freedom.
[0102] In some embodiments, one or more load cells are positioned in the controller. For example, in some embodiments, a load cell (not shown) is positioned in the body of each of the gimbals 186. By providing a load cell, portions of the controller 182 are capable of operating under admittance control, thereby advantageously reducing the perceived inertia of the controller while in use. In some embodiments, the positioning platform 188 is configured for admittance control, while the gimbal 186 is configured for impedance control. In other embodiments, the gimbal 186 is configured for admittance control, while the positioning platform 188 is configured for impedance control. Accordingly, for some embodiments, the translational or positional degrees of freedom of the positioning platform 188 can rely on admittance control, while the rotational degrees of freedom of the gimbal 186 rely on impedance control.
F. Navigation and Control.
[0103] Traditional endoscopy may involve the use of fluoroscopy (e.g., as may be delivered through a C-arm) and other forms of radiation-based imaging modalities to provide endoluminal guidance to an operator physician. In contrast, the robotic systems contemplated by this disclosure can provide for non-radiation-based navigational and localization means to reduce physician exposure to radiation and reduce the amount of equipment within the operating room. As used herein, the term “localization” may refer to determining and/or monitoring the position of objects in a reference coordinate system. Technologies such as preoperative mapping, computer vision, real-time EM tracking, and robot command data may be used individually or in combination to achieve a radiation-free operating environment. In other cases, where radiation-based imaging modalities are still used, the preoperative mapping, computer vision, real-time EM tracking, and robot command data may be used individually or in combination to improve upon the information obtained solely through radiation-based imaging modalities.
[0104] FIG. 20 1s a block diagram illustrating a localization system 90 that estimates a location of one or more elements of the robotic system, such as the location of the instrument, in accordance to an example embodiment. The localization system 90 may be a set of one or more computer devices configured to execute one or more instructions. The computer devices may be embodied by a processor (or processors) and computer-readable memory in one or more components discussed above. By way of example and not limitation, the computer devices may be in the tower 30 shown in FIG. 1 , the cart 11 shown in FIGS. 1-4 , the beds shown in FIGS. 5-14 , etc.
[0105] As shown in FIG. 20 , the localization system 90 may include a localization module 95 that processes input data 91-94 to generate location data 96 for the distal tip of a medical instrument. The location data 96 may be data or logic that represents a location and/or orientation of the distal end of the instrument relative to a frame of reference. The frame of reference can be a frame of reference relative to the anatomy of the patient or to a known object, such as an EM field generator (see discussion below for the EM field generator).
[0106] The various input data 91-94 are now described in greater detail. Preoperative mapping may be accomplished through the use of the collection of low dose CT scans. Preoperative CT scans are reconstructed into three-dimensional images, which are visualized, e.g. as “slices” of a cutaway view of the patient's internal anatomy. When analyzed in the aggregate, image-based models for anatomical cavities, spaces and structures of the patient's anatomy, such as a patient lung network, may be generated. Techniques such as center-line geometry may be determined and approximated from the CT images to develop a three-dimensional volume of the patient's anatomy, referred to as model data 91 (also referred to as “preoperative model data” when generated using only preoperative CT scans). The use of center-line geometry is discussed in U.S. patent application Ser. No. 14/523,760, issued as U.S. Pat. No. 9,763,741 on Sep. 19, 2017, the contents of which are herein incorporated in its entirety. Network topological models may also be derived from the CT-images, and are particularly appropriate for bronchoscopy.
[0107] In some embodiments, the instrument may be equipped with a camera to provide vision data (or image data) 92. The localization module 95 may process the vision data 92 to enable one or more vision-based (or image-based) location tracking modules or features. For example, the preoperative model data 91 may be used in conjunction with the vision data 92 to enable computer vision-based tracking of the medical instrument (e.g., an endoscope or an instrument advance through a working channel of the endoscope). For example, using the preoperative model data 91, the robotic system may generate a library of expected endoscopic images from the model based on the expected path of travel of the endoscope, each image linked to a location within the model. Intraoperatively, this library may be referenced by the robotic system in order to compare real-time images captured at the camera (e.g., a camera at a distal end of the endoscope) to those in the image library to assist localization.
[0108] Other computer vision-based tracking techniques use feature tracking to determine motion of the camera, and thus the endoscope. Some features of the localization module 95 may identify circular geometries in the preoperative model data 91 that correspond to anatomical lumens and track the change of those geometries to determine which anatomical lumen was selected, as well as the relative rotational and/or translational motion of the camera. Use of a topological map may further enhance vision-based algorithms or techniques.
[0109] Optical flow, another computer vision-based technique, may analyze the displacement and translation of image pixels in a video sequence in the vision data 92 to infer camera movement. Examples of optical flow techniques may include motion detection, object segmentation calculations, luminance, motion compensated encoding, stereo disparity measurement, etc. Through the comparison of multiple frames over multiple iterations, movement and location of the camera (and thus the endoscope) may be determined.
[0110] The localization module 95 may use real-time EM tracking to generate a real-time location of the endoscope in a global coordinate system that may be registered to the patient's anatomy, represented by the preoperative model. In EM tracking, an EM sensor (or tracker) comprising one or more sensor coils embedded in one or more locations and orientations in a medical instrument (e.g., an endoscopic tool) measures the variation in the EM field created by one or more static EM field generators positioned at a known location. The location information detected by the EM sensors is stored as EM data 93. The EM field generator (or transmitter), may be placed close to the patient to create a low intensity magnetic field that the embedded sensor may detect. The magnetic field induces small currents in the sensor coils of the EM sensor, which may be analyzed to determine the distance and angle between the EM sensor and the EM field generator. These distances and orientations may be intraoperatively “registered” to the patient anatomy (e.g., the preoperative model) in order to determine the geometric transformation that aligns a single location in the coordinate system with a position in the preoperative model of the patient's anatomy. Once registered, an embedded EM tracker in one or more positions of the medical instrument (e.g., the distal tip of an endoscope) may provide real-time indications of the progression of the medical instrument through the patient's anatomy.
[0111] Robotic command and kinematics data 94 may also be used by the localization module 95 to provide localization data 96 for the robotic system. Device pitch and yaw resulting from articulation commands may be determined during preoperative calibration. Intraoperatively, these calibration measurements may be used in combination with known insertion depth information to estimate the position of the instrument. Alternatively, these calculations may be analyzed in combination with EM, vision, and/or topological modeling to estimate the position of the medical instrument within the network.
[0112] As FIG. 20 shows, a number of other input data can be used by the localization module 95. For example, although not shown in FIG. 20 , an instrument utilizing shape-sensing fiber can provide shape data that the localization module 95 can use to determine the location and shape of the instrument.
[0113] The localization module 95 may use the input data 91-94 in combination(s). In some cases, such a combination may use a probabilistic approach where the localization module 95 assigns a confidence weight to the location determined from each of the input data 91-94. Thus, where the EM data may not be reliable (as may be the case where there is EM interference) the confidence of the location determined by the EM data 93 can be decrease and the localization module 95 may rely more heavily on the vision data 92 and/or the robotic command and kinematics data 94.
[0114] As discussed above, the robotic systems discussed herein may be designed to incorporate a combination of one or more of the technologies above. The robotic system's computer-based control system, based in the tower, bed and/or cart, may store computer program instructions, for example, within a non-transitory computer-readable storage medium such as a persistent magnetic storage drive, solid state drive, or the like, that, upon execution, cause the system to receive and analyze sensor data and user commands, generate control signals throughout the system, and display the navigational and localization data, such as the position of the instrument within the global coordinate system, anatomical map, etc.
2. Introduction to Systems and Methods for Collision Avoidance
[0115] The present disclosure relates to systems and techniques for collision avoidance. Robotic arms may be used to achieve a desired pose (i.e., position and orientation) of an end effector of a medical tool. In some implementations, the medical tool may include a medical instrument or a camera. In manipulating a robotic arm to achieve the desired end effector pose, there may be a risk that some portion of the robotic arm is moved into a pose that would collide with another nearby object (e.g., another robotic arm, the patient, a platform supporting the patient, medical accessories attached to the platform, etc.).
[0116] One way to avoid robotic arm collisions is to position the robotic arms and access points during a pre-procedure set up, e.g., prior to performing a medical procedure, in such a way that the robotic arms are unlikely to be placed into a pose that would result in a collision with other object(s). However, pre-procedure placement or positioning may limit the options for robotic arm placement and/or access point placement. For example, in some instances robotic arms and access points may be spaced apart by minimum distances in order to reduce the likelihood of collisions therebetween. However, such spacing of the robotic arms and/or access points may reduce the ability of the user to position medical tool(s) in desired pose(s). For example, certain procedures for patients of certain sizes (e.g., smaller patients) may involve close spacing of ports to form access points into the patient's anatomy. In these cases, it may not be possible to place the robotic arms and/or access points in locations that reduce the likelihood of robotic arm collisions.
[0117] During certain medical procedures, it can be beneficial to have multiple robotic arms in very close proximity, for example, when access points are placed in close proximity. It can also be beneficial to provide clinicians with the ability to change the anatomical quadrant they are working in while also providing as much room as possible to operate. In controlling the robotic arms in accordance with one or more of the above constraints, collisions between the robotic arms may be more likely to occur, which can interrupt workflow. Thus, it can be desirable to mitigate the likelihood of collisions between the robotic arms, reducing the likelihood of workflow interruptions.
[0118] There may be challenges for clinicians to manually mitigate collisions between robotic arms and/or with other objects. Clinicians may operate the system with their head down in a viewer, which may prevent the clinician from seeing the robotic arms outside of the patient's body. Furthermore, each robotic arm may have a plurality of possible positions that achieve the same end effector pose due to the inclusion of redundant DoFs in the robotic arm(s). Thus, it may not be immediately apparent to the clinician what robotic arm motions outside of the body will result from the commanded end effector motions inside of the body. The result is that robotic arms may collide with another object without the clinician being able to predict the collision, and it may require time and mental effort for the clinician to determine possible movements of the end effectors that will position the robotic arms back into good working location(s). If the clinician is unable to reposition the robotic arms back into good working location(s), the clinician may pause the medical procedure in order to relocate the robotic arms into positions and port placements that will not result in robotic arm collisions.
[0119] For some robotic systems that include robotic arms that are heavy and bulky, certain collisions may be allowed. However, for robotic systems that have robotic arms that are of a sleek and elegant design, such as the robotic arms 142A, 142B of FIG. 14 , it is desirable to detect and avoid collisions before they occur to prevent premature wear and/or damage to the robotic arms.
A. System Modelling for Collision Detection and Avoidance
[0120] Aspects of this disclosure relate to systems and methods for collision detection and avoidance. Specifically, implementations of the robotic systems described herein can be configured to model the robotic system for use in collision detection and avoidance. While certain aspect of the modeling of the robotic system relate to the modelling of robotic arms as an example, aspects of this disclosure can also be used to model other objects of the having measurable dimensions, such as the platform supporting the patient, the adjustable arm support, the rail, the column, etc.
[0121] In certain implementations, the system may form a model of the robotic system by breaking down the robotic system into a set of rigid sections called links that are connected by motors, which in kinematics are referred to as connection joints. At each of these joints, the system can include an encoder configured to generate a signal that is indicative of the relationship between two adjacent links. There are many different types of encoders that can be used, including rotational, linear, magnetic, resistance-based, and/or optical encoders. The system can build a model of the robotic system by connecting alternating links and joints, starting from the fixed base of the robotic system out to each tool tip location or pose of platform. Thus, the system can build a full model of what the robotic system looks like at any given time during a medical procedure using the physical shape/size of each link and the signals received from each of the encoders.
[0122] FIG. 21 illustrates an example view of a model of a robotic system in accordance with aspects of this disclosure. The model 200 includes a plurality of links that model a platform 205, adjustable arm support(s) 210, and a plurality of robotic arms 215. The model 200 may include additional links that model other components of a robotic system which are not illustrated in detail, such as one or more medical instruments, a base, etc. In some implementations, the model 200 is formed based on a series of rigid transformations (e.g., based on the relative size of each link) for each of the links 205-215 and the distance or angle between each of the links 205-215 (e.g., the joint angle(s) read from the encoders). The illustration of the model 200 in FIG. 21 is a human-viewable representation of the model 200 which can be generated using, for example, a CAD model drawn for each link with software used to rotate the links so that the links line up with the corresponding joint angles. The computer generated image of the model 200 may look very much like the actual hardware of the robotic system at a given point in time. In some implementations, the model 200 maintained by the robotic system may not be stored in a human-viewable format.
[0123] In some implementations, the system may generate a human-viewable model and provide the model to be viewed by a clinician (e.g., in the viewer of the clinician console or the clinician assistant console). In other implementations, the model is not viewable by a clinician, but can be running behind the scenes in the system. The clinician may be capable of pulling up a view of the model when the model is hidden from view.
[0124] Using the model of the robotic system, the system may be able to perform certain actions based on the current configuration of the robotic system. Advantageously, one action that the system can perform is detecting when two pieces of hardware are about to collide and prevent the pieces of hardware from colliding. In certain implementations, the model may also include modeled representations of objects which are not a part of the robotic system (e.g., medical accessories, the patient, etc.) in order to prevent collisions between the robotic arms and the modeled objects.
[0125] One aspect of providing for collision detection and avoidance using a model may involve the system determining how close each link is to colliding with every other link in the system. There are a number of different techniques that can be used to determine how close each link is to each other link. In one implementation, the system can use the CAD model directly to determine these distances. In another implementation, the system can generate an approximation of the model based on the CAD model which can be used to speed up computation of the distances between links. One technique for approximating the CAD model involves generating an approximation for each link using a geometric form approximation for each link. In one implementation, the links may be approximated as “capsules.” In other implementations, geometric form(s) used in the approximation can include using cylinders, rectangles, cuboids, etc. The system can efficiently determine a minimal distance between each capsule in the approximated model using the geometric approximations.
[0126] FIG. 22 illustrates a model of a robotic system approximated using a geometric form in accordance with aspects of this disclosure. In the model 300 of FIG. 22 , each link is approximated using one or more capsules to simplify the calculation of the distances between the links. For example, two of the links forming a robotic arm 305 can be modelled using two capsules 310 and 315. The capsules 310 and 315 overlap and can be moved longitudinally with respect to each other in accordance with a change in the distance between the corresponding links, which is measured using an encoder arranged between the links. Similarly, the platform 320 can be modelled using a plurality of capsules 325, which can overlap and may be able to move with respect to each other to model movement of the platform 320.
[0127] FIG. 23 illustrates an example of an unavoidable collision which can be detected using a model of a robotic system in accordance with aspects of this disclosure. An unavoidable collision generally refers to a collision for which there is no action that the system can take to achieve the commanded movement without a collision occurring. In general, there may be two points defined that cannot be changed during active surgery. The first point is the remote center of motion (RCM) which can be defined when a robotic arm is docked to an access point (e.g., a cannula). The RCM may be the point where the cannula passes through the body wall and the system does not normally allow for movement of the RCM since this may cause trauma to the patient (unless under explicit user command).
[0128] The second point is the medical tool end effector tip location and orientation which can be defined based on commands received from the user driving the system. With these two points defined the system controls movement of the ADM to in order meet both of these points. In order to meet all possible end effector positions, the system can move the ADM through a hemi-sphere centered upon the port location. Typically, ports are placed such that two or more of these hemi-spheres will intersect one another, leading to the possibility of unavoidable collisions for certain commanded end effector poses.
[0129] In the example unavoidable collision 400 illustrated in FIG. 23 , a first set of modeled links 405 form a first robotic arm and a second set of model links 410 for a second robotic arm. A first subset 406 of the first links 405 have collided with a second subset 411 of the second links 410 at a number of collision points 415. The collision 400 illustrated FIG. 23 is an unavoidable collision since there are no other poses for the first and second robotic arms which would achieve the same end effector poses without a collision between some portion of the first links 405 and the second links 410.
[0130] FIG. 24 illustrates an example of an avoidable collision which can be detected using a model of a robotic system in accordance with aspects of this disclosure. While there may be only one AMD position that defines each medical instrument end effector position, there are often many robot arm positions for each ADM position. The robot arm(s) can include at least six joints to achieve any spatial and rotational pose commanded by the user. In certain implementations, the robotic arm(s) each have at least seven joints, with the additional joints over six being termed redundant joint(s) since the movement provided by the redundant joints can be accomplished by a combination of motions of the other joints. The redundant joint(s) can be used with the other joints in combination to cancel out any motion on the redundant joint. For example, the system can use both ADM roll and linear bar motion together we can swing the elbow of the robotic arm without the end effector of the medical instrument moving. This repositioning of the robotic arm without medical instrument end effector motion is called a null space motion. The system can control null space motion while also fully controlling the medical instrument end effector and thus actively while the user is driving to advantageously reposition the robotic arm, which can be used to avoid collisions.
[0131] In the avoidable collision 500 of FIG. 24 , a first set of modeled links 505 form a first robotic arm and a second set of model links 510 for a second robotic arm. A first subset 506 of the first links 505 have collided with a second subset 511 of the second links 510 at a collision point. The collision 500 illustrated FIG. 24 is an avoidable collision since the first links 505 and/or the second links 510 can be moved into a different pose while maintaining the same end effector poses. Thus, in certain implementations, the system can detect that an avoidable collision, such as the collision 500, is imminent and move one or more of the first links 505 and the second links 510 to avoid the collision. Examples of systems and methods for avoiding such a collision are described in detail below.
[0132] FIG. 25 is a flowchart illustrating an example method operable by a robotic system, or component(s) thereof, for detecting and avoiding collisions in accordance with aspects of this disclosure. For example, certain steps of method 600 illustrated in FIG. 25 may be performed by processor(s) and/or other component(s) of a medical robotic system (e.g., robotically-enabled system 10) or associated system(s). For convenience, the method 600 is described as performed by the “system” in connection with the description of the method 600.
[0133] The method 600 begins at block 601. At block 605, the system accesses a model of a first set of links and a second set of links of a robotic medical system. For example, the model may be similar to the model 200 of FIG. 21 or may be a geometric approximated model such as the model 300 of FIG. 22 . In some implementations, the first set of links include a first robotic arm and the second set of links include a second robotic arm. However, in other implementations, the first and/or second set of links may include a moveable patient platform, an adjustable arm support, etc.
[0134] At block 610, the system controls movement of the first set of links and the second set of links based on input received by a console of the robotic medical system. In certain implementations, the console may include a controller such as controller 182 of FIG. 19 . At block 615, the system determines a distance between the first set of links and the second set of links based on the model. The determined distance may be the minimum distance between the first set of links and the second set of links. In some implementations, the system may determine the minimum distance between each pair of links in the first set of links and the second set of links.
[0135] At block 620, the system detects and avoids a collision between the first set of links and the second set of links based on the determined distance. For example, the system may avoid the collision by performing an action the prevent the collision, which may include the system prevent further movement of the first set of links and the second set of links. The action can also involve actively avoiding the collision via null space movement of the first set of links and/or the second set of links. The method 600 ends at block 625.
[0136] In some circumstances, a robotic system can be configured to move one or more links of the robotic arm within a “null space” to avoid collisions with nearby objects (e.g., other robotic arms) while the ADM of the robotic arm and/or the RCM are maintained in their respective poses/positions. The null space can be viewed as the space in which a robotic arm can move that does not result in movement of the ADM and/or the RCM, thereby maintaining the position and/or the orientation of the medical tool. In some implementations, a robotic arm can have multiple positions and/or configurations available for each pose of the ADM, allowing for null space movement of the robotic arm without affecting end effector pose. For example, when no medical instrument is coupled to an ADM, the robotic arm can maintain the ADS pose/position while moving the robotic arm in null space. As another example, when a medical instrument is coupled to the ADM, the robotic arm can maintain both the ADM and RCM while moving the robotic arm in null space.
B. Collision Detection and Avoidance—Cutoff Distance
[0137] In certain implementations, the system can prevent the collision of two links of the robotic system by comparing the distance between the two links to a threshold distance and prevent the two links from moving towards each other when the distance between the links is less than the threshold distance. For example, each link in the system can have a minimum distance called the cutoff distance define such that if two links move within the cutoff distance, the system will command the hardware associated with the two links (e.g., the motors controlling movement of the links) to stop motion. An example of the cutoff distance 825 is illustrated in FIG. 27 , which is described in detail below.
[0138] In some implementations, the system can detect when a commanded movement of either one of the robotic arms would put the robotic arms within the cutoff distance and prevent the commanded movement from occurring. The system can continuously update the model based on the signals received from the joint encoders, and thus, the system can continuously measure changes in the distances between the modeled links. Thus, depending on the implementation, the system can detect changes in the distances between the modeled links without measuring the actual movement (e.g., changes in velocity) of the links. By detecting a commanded movement that would have resulted in two links being within the cutoff distance, the system can advantageously prevent the links from touching and place the system in a faulted state. When an input that includes a commanded movement to move away from the collision, the system can allow the user to command further movements of the links with normal moving hardware.
[0139] After the system has determined that two links are within the cutoff distance or will be moved within the cutoff distance based on a commanded movement, the system can provide feedback to the user via a clinician console. In some implementations, the feedback can include haptic feedback which, for example, can be provided via a controller such as the controller 182 of FIG. 19 . For example, the system can apply a haptic force to the user's hand via the controller that will discourage the user from moving further into the collision. The system can also display a warning on a viewer of the clinician console that a collision is imminent or has occurred. By providing feedback via the viewer, the system can advantageously provide an indication of the collision to the user without the user having to remove his/her head from the clinician console viewer. In some implementations, the visual feedback can also indicate one or more action(s) that the user can implement to correct or avoid the collision. By providing the haptic and/or visual feedback to the user, the system can provide feedback that can advantageously induce the user to instinctively move away from the collision point and back into areas where the user can freely operate the robotic arms. By providing haptic feedback via the controller and/or visual feedback via the viewer, the system can provide information to the user regarding accidental collisions without the user having to disengage from the console. This can enable the user to continue to control the robotic system without a break in concentration and continue with any work that is inside of the workspace.
C. Collision Detection and Avoidance—Trigger Distance
[0140] In addition to determining whether one or more arms have entered into a cutoff distance, the system can also use the modeled robotic system to determine whether one or more links have entered into a trigger distance, which is greater than the cutoff distance. In contrast to preventing movement of the robotic arms the arms are within the cutoff distance, the system can take one or more actions to avoid the collision in response to the arms being separated by less than the trigger distance, thereby mitigating the risk of collision. For example, upon entering a trigger distance, one or more arms may use null-space motion while maintaining the corresponding medical tool's remote center of motion in order to avoid a collision. In other words, upon two robotic arms entering a trigger distance, the system can automatically reposition one or more of the arms such that the commanded motion is still executed and a collision never happens due to the movement in null space. The trigger distance may be the minimal distance between two links before the system takes avoidance action, such as null space movement. An example of the trigger distance 820 is illustrated in FIG. 27 , which is described in detail below.
[0141] FIGS. 26A and 26B illustrate an example sequence of actions when a trigger distance is reached in accordance with aspects of this disclosure. At an initial point in time 700 illustrated in FIG. 26A , the system is moving a first robotic arm 705 and the associated first medical instrument based on a commanded movement in the direction of the arrow. For example, the user may input a commanded movement for the first robotic arm 705 and the first medical instrument with a left gimbal and input a commanded movement for a second robotic arm 710 and the associate second medical instrument with a right gimbal.
[0142] As shown in FIG. 26A , the system may have received a command to move the first robotic arm 705 to perform a particular function, thereby bringing certain points on the first and second robotic arms 705 and 710 within a trigger distance of each other. Once the first and second robotic arms 705 and 710 are within the trigger distance, one or more of the first and second robotic arms 705 and 710 can use null space movements (e.g., via its redundant joints) for collision avoidance as shown in the image of the subsequent point in time 701 in FIG. 26B . As shown in FIG. 26B , the base joint of the second robotic arm 710 is slid along an adjustable arm support 715, thereby providing collision avoidance via null space movement (e.g., without moving the end effector of the medical instrument associated with the second robotic arm 710). As shown in FIG. 26B , that the end effector of the second medical instrument associated with the second robotic arm 710 has not moved—only the proximal joints for null space motion and collision avoidance have moved.
[0143] Accordingly, by detecting that two links have moved within a trigger distance of each other, the system can avoid certain types of collisions by taking certain actions (such as null space movement) without needing to inform the user of the potential collision.
[0144] The trigger distance can be set to be larger than the cutoff distance to ensure that avoidance can be triggered before stopping further movement of the robotic links. The system can use to model to determine not only with the minimum distance between two links which may lead to a collision, but also the points at which the two links will collide. Using the distance and the point of collision, the system can determine whether null space motion will increase the distance between the two links at the collision point. If such a null space motion exists, the system can execute the null space motion before the two links enter the cutoff distance, avoiding the collision entirely.
[0145] FIG. 27 illustrates the cutoff and trigger distances for a modeled link in accordance with aspects of this disclosure. In particular, FIG. 27 illustrates the cross-sections of a first link 805 and a second link 810 which are separated by a current (minimum) distance 815. A trigger distance 820 and a cutoff distance 825 are shown surrounding the first link 805. Although not illustrated, the second link 810 may also have a trigger distance and a cutoff distance, which may or may not have the same values as the trigger distance 820 and the cutoff distance 825 associated with the first link 805. As described herein, when another link (such as the second link 810) penetrates the trigger distance 820 of the first link 805, the system may take an action to avoid collision with the other link. Similarly, when the other link penetrates the cutoff distance 825, the system may take an action to prevent the collision with the other link, for example, by preventing further movement towards the collision. For example, the system can determine that a commanded input received by the console would result in a decrease in the distance between the links, and prevent further movement in response to the determination. In contrast, when the system determines that the commanded input received by the console would result in an increase in the distance between the links, the system can control movement of the links based on the received input and the determination, thereby allowing the links to move away from the collision.
[0146] In some implementations, the cutoff distance (e.g., when the robotic arms will stop) can be, for example, up to 10 mm, up to 15 mm, up to 20 mm, or greater. In some embodiments, the trigger distance (e.g., when null-space motion can occur for collision avoidance) can be, for example, up to 5 mm, up to 10 mm, up to 15 mm, or greater. In certain implementations, when the current cutoff distance is 15 mm, the trigger distance can be 20 mm, such that a 5 mm gap is established between the cutoff distance and the trigger distance. The 5 mm gap can be enough room to move the links/robotic arms away from each other faster than a typical command to move the links/arms together. However, if the system receives a command to move the robotic arm together faster than null space movement can move the robotic arms apart, the robotic arms may breach the cutoff distance causing the robotic arms to briefly stop following input commands. However, the system will continue collision avoidance via null space movement even while the robotic arms are within the cutoff distance resulting in moving the arms apart. Once the robotic arms have been moved to be separated by more than the cutoff distance, the robotic arms would resume following the user command to move together. The user may experience this stop and start of movement as the console arms feeling heavy and having slowed motions. If the system detects that an arm has two opposing collisions, then the system may not be able to avoid the collision with null space motion and the system will stop motion once the cutoff distance has been hit. When the system prevents further motion due to a cutoff distance breach, the system can provide haptic force feedback to the user to inform the user of the need to move one of the tools in the opposite direction to allow the other to move away from the collision.
[0147] In some implementations, the system can be pre-programmed with the cutoff distance and/or trigger distance. In other implementations, a user can manually program a cutoff distance and/or trigger distance. Depending on the implementation, the cutoff distance and/or trigger distance may be the same for each link, or may be set on a link-by-link basis.
[0148] FIG. 28 is a flowchart illustrating an example method operable by a robotic system, or component(s) thereof, for detecting and avoiding collisions using a cutoff distance in accordance with aspects of this disclosure. For example, certain steps of method 900 illustrated in FIG. 29 may be performed by processor(s) and/or other component(s) of a medical robotic system (e.g., robotically-enabled system 10) or associated system(s). For convenience, the method 900 is described as performed by the “system” in connection with the description of the method 900.
[0149] The method 900 begins at block 901. At block 905, the system controls movement of the first set of links and the second set of links based on the input received by a console. The system may include the first set of links, the second set of links, and the console, which is configured to receive input commanding motion of the first set of links and the second set of links.
[0150] At block 910, the system determines a distance between the first set of links and the second set of links based on the model. The model may be stored in memory and may model the first set of links and the second set of links.
[0151] At block 915, the system determines that the distance between the first set of links and the second set of links is less than a cutoff distance. At block 920, the system prevents a collision in response to determining that the distance between the first set of links and the second set of links is less than the cutoff distance. The method 900 ends at block 925.
[0152] There are a number of advantages that can be achieved according to various implementations of this disclosure. For example, by using the cutoff distance and the trigger distance as defined herein, the system can control the robotic arms to take no unnecessary motions when outside of the trigger distance, thereby minimizing the amount of robotic arm motion when collision(s) are not imminent. Inside of the trigger distance, yet outside the cutoff distance, the system can use null space motions to attempt to move the links away from the collision, without increasing the cognitive load of the user. By setting the trigger distance to be sufficiently small, the robotic arm motions commanded by the system will be instinctive and staff within the operating room will be able to visualize the cause of the actions (e.g., the potential collision). The user will tend to be unaware that these null space motions are happening to avoid a collision. When the cutoff distance is reached the system can stop further motion of the robotic arms towards the collision, inform the user informed visually, and provide a haptic effect to guide the user toward a resolution of the collision with minimal distraction to the user's workflow. For example, the system can determine that a commanded input received by the console would result in a decrease in the distance between the links, and provide the haptic feedback in response to the determination.
D. Collision Detection and Avoidance—Global Optimization
[0153] In other implementations, the system can detect and avoid collisions without the use of a cutoff distance and a trigger distance as described herein. In particular, the system may implement a global optimization algorithm. The global optimization may involve adding all the links and joints into a single kinematic model and applying a metric to the kinematic model that keeps all links in an optimal configuration. In one implementation, the metric can be defined to maintain all of the links as far away from all collisions as possible. For example, the metric can include a configuration in which the first set of links and the second set of links are at a maximum distance. Depending on the implementation, the optimal configuration algorithm may also take into consideration other optimization goals, such as ensuring that the pose of the robotic arms has sufficient stability. Thus, the global optimization algorithm may try to find an optimal configuration that optimized a plurality of different metrics, including maintaining the links as far away from each other as possible.
[0154] In other implementations, the metric can be defined by adding virtual fixtures onto the modeled links that are theoretical points that system should work to avoid. In some implementations, the system can also use either a determined velocity or energy and distance of the links to determine that two or more links are moving towards a collision and avoid the collision. If the system is unable to use the global optimization algorithm to converge on a solution that does avoid all collisions, the system may stop motion of links of the system, thereby preventing the collision(s).
[0155] Implementations which solve such a global optimization algorithm may involve the use of additional computational complexity compared to the cutoff and/or trigger distance-based implementations. The global optimization solution may also involve addition null space movements even when relatively far away from a collision, making it difficult to minimize robotic arm motion when the arms are not near a collision. It can be desirable to have substantially stationary robotic arms where possible, for example, such that the motion of the robotic arms is predictable to people in the operating room.
3. Implementing Systems and Terminology
[0156] Implementations disclosed herein provide systems, methods and apparatus for collision detection and avoidance.
[0157] It should be noted that the terms “couple,” “coupling,” “coupled” or other variations of the word couple as used herein may indicate either an indirect connection or a direct connection. For example, if a first component is “coupled” to a second component, the first component may be either indirectly connected to the second component via another component or directly connected to the second component.
[0158] The functions for collision detection and avoidance described herein may be stored as one or more instructions on a processor-readable or computer-readable medium. The term “computer-readable medium” refers to any available medium that can be accessed by a computer or processor. By way of example, and not limitation, such a medium may comprise random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory, compact disc read-only memory (CD-ROM) or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer. It should be noted that a computer-readable medium may be tangible and non-transitory. As used herein, the term “code” may refer to software, instructions, code or data that is/are executable by a computing device or processor.
[0159] The methods disclosed herein comprise one or more steps or actions for achieving the described method. The method steps and/or actions may be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order of steps or actions is required for proper operation of the method that is being described, the order and/or use of specific steps and/or actions may be modified without departing from the scope of the claims.
[0160] As used herein, the term “plurality” denotes two or more. For example, a plurality of components indicates two or more components. The term “determining” encompasses a wide variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database or another data structure), ascertaining and the like. Also, “determining” can include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory) and the like. Also, “determining” can include resolving, selecting, choosing, establishing and the like.
[0161] The phrase “based on” does not mean “based only on,” unless expressly specified otherwise. In other words, the phrase “based on” describes both “based only on” and “based at least on.”
[0162] The previous description of the disclosed implementations is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these implementations will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other implementations without departing from the scope of the invention. For example, it will be appreciated that one of ordinary skill in the art will be able to employ a number of corresponding alternative and equivalent structural details, such as equivalent ways of fastening, mounting, coupling, or engaging tool components, equivalent mechanisms for producing particular actuation motions, and equivalent mechanisms for delivering electrical energy. Thus, the present invention is not intended to be limited to the implementations shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims
What is claimed is:
1. A robotic medical system, comprising:
a link of a robotic arm; and
a processor configured to:
control movement of the link based on a received input;
determine a distance between the link and an object during the movement; and
responsive to the distance being within a threshold, reposition the link to avoid a collision between the link and the object.
2. The robotic medical system of claim 1, wherein the processor is configured to determine the distance between the link and the other object using a model of the link.
3. The robotic medical system of claim 1, wherein the model is a model of the robotic arm.
4. The robotic medical system of claim 1, wherein the threshold is a cutoff distance, and wherein the processor is configured to cease movement of the link to avoid the collision responsive to the distance being less than the cutoff distance.
5. The robotic medical system of claim 1, wherein the threshold is a trigger distance, and wherein the processor is configured to reposition the link to avoid the collision responsive to the distance being less than the trigger distance.
6. The robotic medical system of claim 1, wherein the processor is configured to reposition the link by preventing movement of the link.
7. The robotic medical system of claim 1, wherein the other object is another robotic arm or another link.
8. A robotic medical system, comprising:
a link of a robotic arm; and
a processor configured to:
control movement of the link based on a received input;
determine a distance between the link and another object during the movement; and
responsive to the distance being within a threshold, reposition the link in null space to avoid a collision between the link and the object.
9. The robotic medical system of claim 8, wherein the processor is configured to determine the distance between the link and the other object using a model of the robotic arm.
10. The robotic medical system of claim 8, wherein the processor is configured to reposition the link in null space responsive to the distance being less than a trigger distance.
11. The robotic medical system of claim 8, wherein the processor is configured to predict whether the link and the object will collide if the link is moved according to the received input, and wherein the processor is configured to adjust movement of the link responsive to the prediction.
12. The robotic medical system of claim 8, wherein the processor is configured to stop movement of the link responsive to the distance being less than a cutoff distance.
13. The robotic medical system of claim 8, wherein the object is another link.
14. A robotic medical system, comprising:
a link of a robotic arm; and
a processor configured to:
receive an input commanding motion of the link;
predict whether moving the link according to the received input commanding motion would place the link within a threshold distance of another object; and
reposition the link based on the prediction to avoid placing the link within a threshold distance of the other object.
15. The robotic medical system of claim 14, wherein the processor is configured to reposition the link by moving the link in null space.
16. The robotic medical system of claim 14, wherein the processor is configured to reposition the link by preventing movement of the link in accordance with the input commanding motion.
17. The robotic medical system of claim 14, wherein the processor is configured to use a model of the link to perform the prediction.
18. The robotic medical system of claim 14, wherein the processor is configured to predict whether the link will collide with the object if the processor repositions the link based on the input commanding motion.
19. The robotic medical system of claim 18, wherein the processor is configured to determine whether a specific movement of the link would increase a distance between the link and the object at a point where the link is predicted to collide with the object.
20. The robotic medical system of claim 19, wherein the processor is configured to reposition the link according to the specific movement based on a determination that the specific movement of the link would increase the distance between the link and the another-object.
Patent Citations (625)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US3763860(A) | 1973-10-01 | Clarke | Applicant |
| US4040413(A) | 1977-08-01 | Ohshiro | Applicant |
| US4198960(A) | 1980-04-01 | Utsugi | Applicant |
| US4470407(A) | 1984-09-01 | Hussein | Applicant |
| US4532935(A) | 1985-08-01 | Wang et al. | Applicant |
| US4685458(A) | 1987-08-01 | Leckrone | Applicant |
| US4747405(A) | 1988-05-01 | Leckrone | Applicant |
| US4854301(A) | 1989-08-01 | Nakajima | Applicant |
| US4898574(A) | 1990-02-01 | Uchiyama | Applicant |
| US4975856(A) | 1990-12-01 | Vold et al. | Applicant |
| US4983165(A) | 1991-01-01 | Loiterman | Applicant |
| US5029574(A) | 1991-07-01 | Shimamura et al. | Applicant |
| US5085659(A) | 1992-02-01 | Rydell | Applicant |
| US5150452(A) | 1992-09-01 | Pollack et al. | Applicant |
| US5196023(A) | 1993-03-01 | Martin | Applicant |
| US5199417(A) | 1993-04-01 | Muller et al. | Applicant |
| US5217465(A) | 1993-06-01 | Steppe | Applicant |
| US5308323(A) | 1994-05-01 | Sogawa et al. | Applicant |
| US5318589(A) | 1994-06-01 | Lichtman | Applicant |
| US5325848(A) | 1994-07-01 | Adams et al. | Applicant |
| US5342381(A) | 1994-08-01 | Tidemand | Applicant |
| US5344395(A) | 1994-09-01 | Whalen et al. | Applicant |
| US5353783(A) | 1994-10-01 | Nakao et al. | Applicant |
| US5370609(A) | 1994-12-01 | Drasler et al. | Applicant |
| US5372124(A) | 1994-12-01 | Takayama et al. | Applicant |
| US5411016(A) | 1995-05-01 | Kume et al. | Applicant |
| US5431649(A) | 1995-07-01 | Muller et al. | Applicant |
| US5441485(A) | 1995-08-01 | Peters | Applicant |
| US5449356(A) | 1995-09-01 | Walbrink et al. | Applicant |
| US5450843(A) | 1995-09-01 | Moll et al. | Applicant |
| US5472426(A) | 1995-12-01 | Bonati et al. | Applicant |
| US5496267(A) | 1996-03-01 | Drasler | Applicant |
| US5501667(A) | 1996-03-01 | Verduin, Jr. | Applicant |
| US5520684(A) | 1996-05-01 | Imran | Applicant |
| US5545170(A) | 1996-08-01 | Hart | Applicant |
| US5562239(A) | 1996-10-01 | Boiarski et al. | Applicant |
| US5562648(A) | 1996-10-01 | Peterson | Applicant |
| US5562678(A) | 1996-10-01 | Booker | Applicant |
| US5572999(A) | 1996-11-01 | Funda et al. | Applicant |
| US5573535(A) | 1996-11-01 | Viklund | Applicant |
| US5613973(A) | 1997-03-01 | Jackson et al. | Applicant |
| US5645083(A) | 1997-07-01 | Essig et al. | Applicant |
| US5653374(A) | 1997-08-01 | Young et al. | Applicant |
| US5658311(A) | 1997-08-01 | Baden | Applicant |
| US5695500(A) | 1997-12-01 | Taylor et al. | Applicant |
| US5697949(A) | 1997-12-01 | Giurtino et al. | Applicant |
| US5710870(A) | 1998-01-01 | Ohm | Applicant |
| US5716325(A) | 1998-02-01 | Bonutti | Applicant |
| US5737500(A) | 1998-04-01 | Seraji et al. | Applicant |
| US5788667(A) | 1998-08-01 | Stoller | Applicant |
| US5792165(A) | 1998-08-01 | Klieman | Applicant |
| US5797900(A) | 1998-08-01 | Madhani | Applicant |
| US5798627(A) | 1998-08-01 | Gilliland | Applicant |
| US5810770(A) | 1998-09-01 | Chin et al. | Applicant |
| US5876325(A) | 1999-03-01 | Mizuno et al. | Applicant |
| US5893869(A) | 1999-04-01 | Barnhart | Applicant |
| US5897491(A) | 1999-04-01 | Kastenbauer et al. | Applicant |
| US5924175(A) | 1999-07-01 | Lippitt | Applicant |
| US5943056(A) | 1999-08-01 | Sato | Applicant |
| US5989230(A) | 1999-11-01 | Frassica | Applicant |
| US6071281(A) | 2000-06-01 | Burnside et al. | Applicant |
| US6093157(A) | 2000-07-01 | Chandrasekaran | Applicant |
| US6110171(A) | 2000-08-01 | Rydell | Applicant |
| US6120476(A) | 2000-09-01 | Fung et al. | Applicant |
| US6120498(A) | 2000-09-01 | Jani et al. | Applicant |
| US6156030(A) | 2000-12-01 | Neev | Applicant |
| US6174318(B1) | 2001-01-01 | Bates et al. | Applicant |
| US6183435(B1) | 2001-02-01 | Bumbalough et al. | Applicant |
| US6206903(B1) | 2001-03-01 | Ramans | Applicant |
| US6236906(B1) | 2001-05-01 | Muller | Applicant |
| US6322557(B1) | 2001-11-01 | Nikolaevich | Applicant |
| US6375635(B1) | 2002-04-01 | Moutafis | Applicant |
| US6394998(B1) | 2002-05-01 | Wallace et al. | Applicant |
| US6405078(B1) | 2002-06-01 | Moaddeb et al. | Applicant |
| US6440061(B1) | 2002-08-01 | Wenner et al. | Applicant |
| US6508823(B1) | 2003-01-01 | Gonon | Applicant |
| US6522906(B1) | 2003-02-01 | Salisbury et al. | Applicant |
| US6577891(B1) | 2003-06-01 | Jaross et al. | Applicant |
| US6676668(B2) | 2004-01-01 | Mercereau et al. | Applicant |
| US6685698(B2) | 2004-02-01 | Morley et al. | Applicant |
| US6706050(B1) | 2004-03-01 | Giannadakis | Applicant |
| US7002585(B1) | 2006-02-01 | Watanabe et al. | Applicant |
| US7282055(B2) | 2007-10-01 | Tsuruta | Applicant |
| US7559934(B2) | 2009-07-01 | Teague et al. | Applicant |
| US7736356(B2) | 2010-06-01 | Cooper et al. | Applicant |
| US7963911(B2) | 2011-06-01 | Turliuc | Applicant |
| US7987046(B1) | 2011-07-01 | Peterman | Applicant |
| US8002713(B2) | 2011-08-01 | Heske | Applicant |
| US8004229(B2) | 2011-08-01 | Nowlin et al. | Applicant |
| US8021326(B2) | 2011-09-01 | Moll et al. | Applicant |
| US8038598(B2) | 2011-10-01 | Khachi | Applicant |
| US8092397(B2) | 2012-01-01 | Wallace et al. | Applicant |
| US8187173(B2) | 2012-05-01 | Miyoshi | Applicant |
| US8257303(B2) | 2012-09-01 | Moll et al. | Applicant |
| US8480595(B2) | 2013-07-01 | Speeg | Applicant |
| US8506555(B2) | 2013-08-01 | Morales | Applicant |
| US8523762(B2) | 2013-09-01 | Miyamoto et al. | Applicant |
| US8540748(B2) | 2013-09-01 | Murphy et al. | Applicant |
| US8541970(B2) | 2013-09-01 | Nowlin | Applicant |
| US8652030(B2) | 2014-02-01 | Matsuura et al. | Applicant |
| US8749190(B2) | 2014-06-01 | Nowlin et al. | Applicant |
| US8786241(B2) | 2014-07-01 | Nowlin et al. | Applicant |
| US8820603(B2) | 2014-09-01 | Shelton et al. | Applicant |
| US8821480(B2) | 2014-09-01 | Burbank | Applicant |
| US8882660(B2) | 2014-11-01 | Phee et al. | Applicant |
| US8945163(B2) | 2015-02-01 | Voegele et al. | Applicant |
| US8956280(B2) | 2015-02-01 | Eversull et al. | Applicant |
| US9179979(B2) | 2015-11-01 | Jinno | Applicant |
| US9259282(B2) | 2016-02-01 | Azizian | Applicant |
| US9296104(B2) | 2016-03-01 | Swarup et al. | Applicant |
| US9345456(B2) | 2016-05-01 | Tsonton et al. | Applicant |
| US9345544(B2) | 2016-05-01 | Hourtash et al. | Applicant |
| US9375284(B2) | 2016-06-01 | Hourtash | Applicant |
| US9415510(B2) | 2016-08-01 | Hourtash et al. | Applicant |
| US9460536(B2) | 2016-10-01 | Hasegawa et al. | Applicant |
| US9480534(B2) | 2016-11-01 | Bowling | Applicant |
| US9504604(B2) | 2016-11-01 | Alvarez | Applicant |
| US9510911(B2) | 2016-12-01 | Hourtash | Applicant |
| US9517106(B2) | 2016-12-01 | Hourtash et al. | Applicant |
| US9561083(B2) | 2017-02-01 | Yu et al. | Applicant |
| US9566125(B2) | 2017-02-01 | Bowling | Applicant |
| US9592042(B2) | 2017-03-01 | Titus | Applicant |
| US9597152(B2) | 2017-03-01 | Schaeffer | Applicant |
| US9622827(B2) | 2017-04-01 | Yu et al. | Applicant |
| US9636184(B2) | 2017-05-01 | Lee et al. | Applicant |
| US9668768(B2) | 2017-06-01 | Piron et al. | Applicant |
| US9675422(B2) | 2017-06-01 | Hourtash et al. | Applicant |
| US9687310(B2) | 2017-06-01 | Nowlin et al. | Applicant |
| US9713509(B2) | 2017-07-01 | Schuh et al. | Applicant |
| US9717563(B2) | 2017-08-01 | Tognaccini | Applicant |
| US9727963(B2) | 2017-08-01 | Mintz et al. | Applicant |
| US9730757(B2) | 2017-08-01 | Brudniok | Applicant |
| US9737371(B2) | 2017-08-01 | Romo et al. | Applicant |
| US9737373(B2) | 2017-08-01 | Schuh | Applicant |
| US9744335(B2) | 2017-08-01 | Jiang | Applicant |
| US9763741(B2) | 2017-09-01 | Alvarez et al. | Applicant |
| US9782229(B2) | 2017-10-01 | Crawford | Applicant |
| US9788910(B2) | 2017-10-01 | Schuh | Applicant |
| US9789608(B2) | 2017-10-01 | Itkowitz | Examiner |
| US9844412(B2) | 2017-12-01 | Bogusky et al. | Applicant |
| US9867635(B2) | 2018-01-01 | Alvarez et al. | Applicant |
| US9918681(B2) | 2018-03-01 | Wallace et al. | Applicant |
| US9931025(B1) | 2018-04-01 | Graetzel et al. | Applicant |
| US9943962(B2) | 2018-04-01 | Sattler et al. | Applicant |
| US9949749(B2) | 2018-04-01 | Noonan et al. | Applicant |
| US9955986(B2) | 2018-05-01 | Shah | Applicant |
| US9962228(B2) | 2018-05-01 | Schuh et al. | Applicant |
| US9980785(B2) | 2018-05-01 | Schuh | Applicant |
| US9993313(B2) | 2018-06-01 | Schuh et al. | Applicant |
| US10016900(B1) | 2018-07-01 | Meyer et al. | Applicant |
| US10022192(B1) | 2018-07-01 | Ummalaneni | Applicant |
| US10029367(B2) | 2018-07-01 | Hourtash | Applicant |
| US10071479(B2) | 2018-09-01 | Swarup et al. | Applicant |
| US10080576(B2) | 2018-09-01 | Romo et al. | Applicant |
| US10117713(B2) | 2018-11-01 | Moctezuma de la Barrera | Applicant |
| US10130429(B1) | 2018-11-01 | Weir | Applicant |
| US10136949(B2) | 2018-11-01 | Felder et al. | Applicant |
| US10136959(B2) | 2018-11-01 | Mintz et al. | Applicant |
| US10145747(B1) | 2018-12-01 | Lin et al. | Applicant |
| US10149720(B2) | 2018-12-01 | Romo | Applicant |
| US10154822(B2) | 2018-12-01 | Henderson | Applicant |
| US10159532(B1) | 2018-12-01 | Ummalaneni et al. | Applicant |
| US10159533(B2) | 2018-12-01 | Moll et al. | Applicant |
| US10169875(B2) | 2019-01-01 | Mintz et al. | Applicant |
| US10219868(B2) | 2019-03-01 | Weir | Applicant |
| US10219874(B2) | 2019-03-01 | Yu et al. | Applicant |
| US10231793(B2) | 2019-03-01 | Romo | Applicant |
| US10231867(B2) | 2019-03-01 | Alvarez et al. | Applicant |
| US10244926(B2) | 2019-04-01 | Noonan et al. | Applicant |
| US10285574(B2) | 2019-05-01 | Landey et al. | Applicant |
| US10299870(B2) | 2019-05-01 | Connolly et al. | Applicant |
| US10314463(B2) | 2019-06-01 | Agrawal et al. | Applicant |
| US10314661(B2) | 2019-06-01 | Bowling | Applicant |
| US10327855(B2) | 2019-06-01 | Hourtash et al. | Applicant |
| US10350017(B2) | 2019-07-01 | Bowling | Applicant |
| US10350390(B2) | 2019-07-01 | Moll et al. | Applicant |
| US10383765(B2) | 2019-08-01 | Alvarez et al. | Applicant |
| US10398518(B2) | 2019-09-01 | Yu et al. | Applicant |
| US10405939(B2) | 2019-09-01 | Romo et al. | Applicant |
| US10405940(B2) | 2019-09-01 | Romo | Applicant |
| US10426559(B2) | 2019-10-01 | Graetzel et al. | Applicant |
| US10426661(B2) | 2019-10-01 | Kintz | Applicant |
| US10434660(B2) | 2019-10-01 | Meyer et al. | Applicant |
| US10463440(B2) | 2019-11-01 | Bowling | Applicant |
| US10464209(B2) | 2019-11-01 | Ho et al. | Applicant |
| US10470830(B2) | 2019-11-01 | Hill | Applicant |
| US10482599(B2) | 2019-11-01 | Mintz et al. | Applicant |
| US10493241(B2) | 2019-12-01 | Jiang | Applicant |
| US10500001(B2) | 2019-12-01 | Yu et al. | Applicant |
| US10517692(B2) | 2019-12-01 | Eyre et al. | Applicant |
| US10524866(B2) | 2020-01-01 | Srinivasan | Applicant |
| US10539478(B2) | 2020-01-01 | Lin | Applicant |
| US10543048(B2) | 2020-01-01 | Noonan et al. | Applicant |
| US10555778(B2) | 2020-02-01 | Ummalaneni et al. | Applicant |
| US10631949(B2) | 2020-04-01 | Schuh et al. | Applicant |
| US10639108(B2) | 2020-05-01 | Romo et al. | Applicant |
| US10639109(B2) | 2020-05-01 | Bovay et al. | Applicant |
| US10639114(B2) | 2020-05-01 | Schuh | Applicant |
| US10646291(B2) | 2020-05-01 | Turner | Applicant |
| US10667871(B2) | 2020-06-01 | Romo et al. | Applicant |
| US10667875(B2) | 2020-06-01 | DeFonzo | Applicant |
| US10682189(B2) | 2020-06-01 | Schuh et al. | Applicant |
| US10702348(B2) | 2020-07-01 | Moll et al. | Applicant |
| US10716461(B2) | 2020-07-01 | Jenkins | Applicant |
| US10743751(B2) | 2020-08-01 | Landey et al. | Applicant |
| US10744035(B2) | 2020-08-01 | Alvarez et al. | Applicant |
| US10744981(B2) | 2020-08-01 | Auer | Applicant |
| US10751140(B2) | 2020-08-01 | Wallace et al. | Applicant |
| US10765303(B2) | 2020-09-01 | Graetzel et al. | Applicant |
| US10765487(B2) | 2020-09-01 | Ho | Applicant |
| US10779898(B2) | 2020-09-01 | Hill | Applicant |
| US10786329(B2) | 2020-09-01 | Schuh et al. | Applicant |
| US10786432(B2) | 2020-09-01 | Jornitz et al. | Applicant |
| US10792464(B2) | 2020-10-01 | Romo et al. | Applicant |
| US10792466(B2) | 2020-10-01 | Landey et al. | Applicant |
| US10813539(B2) | 2020-10-01 | Graetzel et al. | Applicant |
| US10814101(B2) | 2020-10-01 | Jiang | Applicant |
| US10820947(B2) | 2020-11-01 | Julian | Applicant |
| US10820954(B2) | 2020-11-01 | Marsot et al. | Applicant |
| US10827913(B2) | 2020-11-01 | Ummalaneni et al. | Applicant |
| US10828118(B2) | 2020-11-01 | Schuh et al. | Applicant |
| US10835153(B2) | 2020-11-01 | Rafii-Tari et al. | Applicant |
| US10850013(B2) | 2020-12-01 | Hsu | Applicant |
| US10959792(B1) | 2021-03-01 | Huang et al. | Applicant |
| US11547468(B2) | 2023-01-01 | Shelton, IV et al. | Applicant |
| US11638999(B2) | 2023-05-01 | Itkowitz | Examiner |
| US11701187(B2) | 2023-07-01 | Huang et al. | Applicant |
| US2002/0019644(A1) | 2002-02-01 | Hastings | Applicant |
| US2002/0082612(A1) | 2002-06-01 | Moll et al. | Applicant |
| US2002/0111608(A1) | 2002-08-01 | Baerveldt | Applicant |
| US2002/0111621(A1) | 2002-08-01 | Wallace et al. | Applicant |
| US2003/0004455(A1) | 2003-01-01 | Kadziauskas | Applicant |
| US2003/0040681(A1) | 2003-02-01 | Ng et al. | Applicant |
| US2003/0065358(A1) | 2003-04-01 | Frecker | Applicant |
| US2003/0100892(A1) | 2003-05-01 | Morley et al. | Applicant |
| US2003/0109780(A1) | 2003-06-01 | Coste-Maniere | Applicant |
| US2003/0109877(A1) | 2003-06-01 | Morley | Applicant |
| US2003/0109889(A1) | 2003-06-01 | Mercereau | Applicant |
| US2003/0158545(A1) | 2003-08-01 | Hovda et al. | Applicant |
| US2003/0181809(A1) | 2003-09-01 | Hall et al. | Applicant |
| US2003/0208189(A1) | 2003-11-01 | Payman | Applicant |
| US2004/0143253(A1) | 2004-07-01 | Vanney | Applicant |
| US2004/0153093(A1) | 2004-08-01 | Donovan | Applicant |
| US2004/0158261(A1) | 2004-08-01 | Vu | Applicant |
| US2004/0176751(A1) | 2004-09-01 | Weitzner et al. | Applicant |
| US2004/0186349(A1) | 2004-09-01 | Ewers | Applicant |
| US2004/0193146(A1) | 2004-09-01 | Lee et al. | Applicant |
| US2004/0210116(A1) | 2004-10-01 | Nakao | Applicant |
| US2004/0253079(A1) | 2004-12-01 | Sanchez | Applicant |
| US2005/0033270(A1) | 2005-02-01 | Ramans et al. | Applicant |
| US2005/0054900(A1) | 2005-03-01 | Mawn | Applicant |
| US2005/0159645(A1) | 2005-07-01 | Bertolero | Applicant |
| US2005/0177143(A1) | 2005-08-01 | Bullington et al. | Applicant |
| US2005/0240178(A1) | 2005-10-01 | Morley et al. | Applicant |
| US2005/0261705(A1) | 2005-11-01 | Gist | Applicant |
| US2006/0015133(A1) | 2006-01-01 | Grayzel | Applicant |
| US2006/0058617(A1) | 2006-03-01 | Sano et al. | Applicant |
| US2006/0058813(A1) | 2006-03-01 | Teague | Applicant |
| US2006/0116693(A1) | 2006-06-01 | Weisenburgh | Applicant |
| US2006/0135963(A1) | 2006-06-01 | Kick | Applicant |
| US2006/0156875(A1) | 2006-07-01 | McRury et al. | Applicant |
| US2006/0161137(A1) | 2006-07-01 | Orban et al. | Applicant |
| US2006/0178556(A1) | 2006-08-01 | Hasser et al. | Applicant |
| US2006/0189891(A1) | 2006-08-01 | Waxman et al. | Applicant |
| US2007/0016164(A1) | 2007-01-01 | Dudney et al. | Applicant |
| US2007/0027443(A1) | 2007-02-01 | Rose | Applicant |
| US2007/0027534(A1) | 2007-02-01 | Bergheim | Applicant |
| US2007/0032906(A1) | 2007-02-01 | Sutherland et al. | Applicant |
| US2007/0083098(A1) | 2007-04-01 | Stern et al. | Applicant |
| US2007/0106304(A1) | 2007-05-01 | Hammack | Applicant |
| US2007/0123855(A1) | 2007-05-01 | Morley et al. | Applicant |
| US2007/0135803(A1) | 2007-06-01 | Belson | Applicant |
| US2007/0208375(A1) | 2007-09-01 | Nishizawa | Applicant |
| US2007/0213668(A1) | 2007-09-01 | Spitz | Applicant |
| US2007/0239178(A1) | 2007-10-01 | Weitzner et al. | Applicant |
| US2007/0250111(A1) | 2007-10-01 | Lu | Applicant |
| US2007/0276539(A1) | 2007-11-01 | Habibi et al. | Applicant |
| US2007/0299427(A1) | 2007-12-01 | Yeung et al. | Applicant |
| US2008/0015566(A1) | 2008-01-01 | Livneh | Applicant |
| US2008/0021440(A1) | 2008-01-01 | Solomon | Applicant |
| US2008/0033467(A1) | 2008-02-01 | Miyamoto et al. | Applicant |
| US2008/0045981(A1) | 2008-02-01 | Margolin et al. | Applicant |
| US2008/0046122(A1) | 2008-02-01 | Manzo et al. | Applicant |
| US2008/0065111(A1) | 2008-03-01 | Blumenkranz et al. | Applicant |
| US2008/0065112(A1) | 2008-03-01 | Tovey et al. | Applicant |
| US2008/0125698(A1) | 2008-05-01 | Gerg et al. | Applicant |
| US2008/0147089(A1) | 2008-06-01 | Loh | Applicant |
| US2008/0187101(A1) | 2008-08-01 | Gertner | Applicant |
| US2008/0196533(A1) | 2008-08-01 | Bergamasco | Applicant |
| US2008/0228104(A1) | 2008-09-01 | Uber et al. | Applicant |
| US2009/0005768(A1) | 2009-01-01 | Sharareh | Applicant |
| US2009/0012507(A1) | 2009-01-01 | Culbertson et al. | Applicant |
| US2009/0030446(A1) | 2009-01-01 | Measamer | Applicant |
| US2009/0036900(A1) | 2009-02-01 | Moll | Applicant |
| US2009/0043305(A1) | 2009-02-01 | Brodbeck | Applicant |
| US2009/0048611(A1) | 2009-02-01 | Funda | Applicant |
| US2009/0082634(A1) | 2009-03-01 | Kathrani et al. | Applicant |
| US2009/0088774(A1) | 2009-04-01 | Swarup et al. | Applicant |
| US2009/0105723(A1) | 2009-04-01 | Dillinger | Applicant |
| US2009/0131885(A1) | 2009-05-01 | Akahoshi | Applicant |
| US2009/0161827(A1) | 2009-06-01 | Gertner et al. | Applicant |
| US2009/0192524(A1) | 2009-07-01 | Itkowitz | Examiner |
| US2009/0227998(A1) | 2009-09-01 | Aljuri | Applicant |
| US2009/0248041(A1) | 2009-10-01 | Williams et al. | Applicant |
| US2009/0248043(A1) | 2009-10-01 | Tierney et al. | Applicant |
| US2009/0264878(A1) | 2009-10-01 | Carmel et al. | Applicant |
| US2009/0270760(A1) | 2009-10-01 | Leimbach et al. | Applicant |
| US2009/0287188(A1) | 2009-11-01 | Golden et al. | Applicant |
| US2009/0299352(A1) | 2009-12-01 | Zerfas | Applicant |
| US2009/0312773(A1) | 2009-12-01 | Cabrera et al. | Applicant |
| US2009/0326318(A1) | 2009-12-01 | Tognaccini | Applicant |
| US2010/0004642(A1) | 2010-01-01 | Lumpkin | Applicant |
| US2010/0010504(A1) | 2010-01-01 | Simaan et al. | Applicant |
| US2010/0011900(A1) | 2010-01-01 | Burbank | Applicant |
| US2010/0011901(A1) | 2010-01-01 | Burbank | Applicant |
| US2010/0016852(A1) | 2010-01-01 | Manzo et al. | Applicant |
| US2010/0016853(A1) | 2010-01-01 | Burbank | Applicant |
| US2010/0081965(A1) | 2010-04-01 | Mugan et al. | Applicant |
| US2010/0082017(A1) | 2010-04-01 | Zickler | Applicant |
| US2010/0100045(A1) | 2010-04-01 | Pravongviengkham et al. | Applicant |
| US2010/0179632(A1) | 2010-07-01 | Bruszewski et al. | Applicant |
| US2010/0204605(A1) | 2010-08-01 | Blakley | Applicant |
| US2010/0204646(A1) | 2010-08-01 | Plicchi et al. | Applicant |
| US2010/0217235(A1) | 2010-08-01 | Thorstenson | Applicant |
| US2010/0225209(A1) | 2010-09-01 | Goldberg | Applicant |
| US2010/0228249(A1) | 2010-09-01 | Mohr | Applicant |
| US2010/0234857(A1) | 2010-09-01 | Itkowitz | Applicant |
| US2010/0268211(A1) | 2010-10-01 | Manwaring et al. | Applicant |
| US2010/0286712(A1) | 2010-11-01 | Won et al. | Applicant |
| US2010/0312141(A1) | 2010-12-01 | Keast et al. | Applicant |
| US2010/0331858(A1) | 2010-12-01 | Simaan et al. | Applicant |
| US2011/0015483(A1) | 2011-01-01 | Barbagli | Applicant |
| US2011/0028790(A1) | 2011-02-01 | Farr et al. | Applicant |
| US2011/0071541(A1) | 2011-03-01 | Prisco et al. | Applicant |
| US2011/0071543(A1) | 2011-03-01 | Prisco et al. | Applicant |
| US2011/0106146(A1) | 2011-05-01 | Jeong | Applicant |
| US2011/0125165(A1) | 2011-05-01 | Simaan et al. | Applicant |
| US2011/0152880(A1) | 2011-06-01 | Alvarez et al. | Applicant |
| US2011/0160713(A1) | 2011-06-01 | Neuberger | Applicant |
| US2011/0160745(A1) | 2011-06-01 | Fielding | Applicant |
| US2011/0167611(A1) | 2011-07-01 | Williams | Applicant |
| US2011/0184558(A1) | 2011-07-01 | Jacob | Applicant |
| US2011/0208211(A1) | 2011-08-01 | Whitfield et al. | Applicant |
| US2011/0213362(A1) | 2011-09-01 | Cunningham et al. | Applicant |
| US2011/0224660(A1) | 2011-09-01 | Neuberger et al. | Applicant |
| US2011/0238064(A1) | 2011-09-01 | Williams | Applicant |
| US2011/0257641(A1) | 2011-10-01 | Hastings et al. | Applicant |
| US2011/0264112(A1) | 2011-10-01 | Nowlin et al. | Applicant |
| US2011/0276085(A1) | 2011-11-01 | Krzyzanowski | Applicant |
| US2011/0277775(A1) | 2011-11-01 | Holop et al. | Applicant |
| US2011/0313343(A1) | 2011-12-01 | Milutinovic et al. | Applicant |
| US2012/0048759(A1) | 2012-03-01 | Disch et al. | Applicant |
| US2012/0069167(A1) | 2012-03-01 | Liu et al. | Applicant |
| US2012/0138586(A1) | 2012-06-01 | Webster et al. | Applicant |
| US2012/0138660(A1) | 2012-06-01 | Shelton, IV et al. | Applicant |
| US2012/0209069(A1) | 2012-08-01 | Popovic et al. | Applicant |
| US2012/0209315(A1) | 2012-08-01 | Amat | Applicant |
| US2012/0232342(A1) | 2012-09-01 | Reydel | Applicant |
| US2012/0253277(A1) | 2012-10-01 | Tah et al. | Applicant |
| US2012/0253332(A1) | 2012-10-01 | Moll | Applicant |
| US2012/0259320(A1) | 2012-10-01 | Loesel et al. | Applicant |
| US2012/0283747(A1) | 2012-11-01 | Popovic | Applicant |
| US2012/0296318(A1) | 2012-11-01 | Wellhofer et al. | Applicant |
| US2012/0302869(A1) | 2012-11-01 | Koyrakh | Applicant |
| US2013/0006144(A1) | 2013-01-01 | Clancy | Applicant |
| US2013/0035537(A1) | 2013-02-01 | Wallace et al. | Applicant |
| US2013/0053877(A1) | 2013-02-01 | BenMaamer | Applicant |
| US2013/0066136(A1) | 2013-03-01 | Palese et al. | Applicant |
| US2013/0085442(A1) | 2013-04-01 | Shtul et al. | Applicant |
| US2013/0085486(A1) | 2013-04-01 | Boutoussov et al. | Applicant |
| US2013/0096422(A1) | 2013-04-01 | Boctor | Applicant |
| US2013/0096574(A1) | 2013-04-01 | Kang et al. | Applicant |
| US2013/0110042(A1) | 2013-05-01 | Humphreys | Applicant |
| US2013/0110107(A1) | 2013-05-01 | Smith et al. | Applicant |
| US2013/0116716(A1) | 2013-05-01 | Bahls et al. | Applicant |
| US2013/0144274(A1) | 2013-06-01 | Stefanchik et al. | Applicant |
| US2013/0144395(A1) | 2013-06-01 | Stefanchik | Applicant |
| US2013/0190796(A1) | 2013-07-01 | Tilson et al. | Applicant |
| US2013/0225997(A1) | 2013-08-01 | Dillard et al. | Applicant |
| US2013/0226161(A1) | 2013-08-01 | Hickenbotham | Applicant |
| US2013/0233908(A1) | 2013-09-01 | Knodel | Applicant |
| US2013/0253267(A1) | 2013-09-01 | Collins | Applicant |
| US2013/0303876(A1) | 2013-11-01 | Gelfand et al. | Applicant |
| US2013/0310819(A1) | 2013-11-01 | Neuberger et al. | Applicant |
| US2013/0317519(A1) | 2013-11-01 | Romo et al. | Applicant |
| US2013/0334281(A1) | 2013-12-01 | Williams | Applicant |
| US2013/0345686(A1) | 2013-12-01 | Brown | Applicant |
| US2014/0005681(A1) | 2014-01-01 | Gee et al. | Applicant |
| US2014/0022353(A1) | 2014-01-01 | Hamersma et al. | Applicant |
| US2014/0039517(A1) | 2014-02-01 | Bowling | Applicant |
| US2014/0039681(A1) | 2014-02-01 | Bowling | Applicant |
| US2014/0046308(A1) | 2014-02-01 | Bischoff | Applicant |
| US2014/0051049(A1) | 2014-02-01 | Jarc | Applicant |
| US2014/0051985(A1) | 2014-02-01 | Fan et al. | Applicant |
| US2014/0058365(A1) | 2014-02-01 | Bille | Applicant |
| US2014/0058404(A1) | 2014-02-01 | Hammack | Applicant |
| US2014/0058428(A1) | 2014-02-01 | Christopher | Applicant |
| US2014/0100445(A1) | 2014-04-01 | Stenzel | Applicant |
| US2014/0142591(A1) | 2014-05-01 | Alvarez et al. | Applicant |
| US2014/0163318(A1) | 2014-06-01 | Swanstrom | Applicant |
| US2014/0163736(A1) | 2014-06-01 | Azizian | Applicant |
| US2014/0194859(A1) | 2014-07-01 | Ianchulev | Applicant |
| US2014/0194905(A1) | 2014-07-01 | Kappel | Applicant |
| US2014/0222207(A1) | 2014-08-01 | Bowling | Applicant |
| US2014/0243801(A1) | 2014-08-01 | Fanelli et al. | Applicant |
| US2014/0243849(A1) | 2014-08-01 | Saglam et al. | Applicant |
| US2014/0246473(A1) | 2014-09-01 | Auld | Applicant |
| US2014/0257333(A1) | 2014-09-01 | Blumenkranz | Applicant |
| US2014/0275956(A1) | 2014-09-01 | Fan | Applicant |
| US2014/0276723(A1) | 2014-09-01 | Parihar | Applicant |
| US2014/0276956(A1) | 2014-09-01 | Crainich | Applicant |
| US2014/0309655(A1) | 2014-10-01 | Gal et al. | Applicant |
| US2014/0316203(A1) | 2014-10-01 | Carroux et al. | Applicant |
| US2014/0357984(A1) | 2014-12-01 | Wallace et al. | Applicant |
| US2015/0025549(A1) | 2015-01-01 | Kilroy et al. | Applicant |
| US2015/0045675(A1) | 2015-02-01 | Chernomorsky | Applicant |
| US2015/0073439(A1) | 2015-03-01 | Dannaher | Applicant |
| US2015/0080879(A1) | 2015-03-01 | Trees | Applicant |
| US2015/0088161(A1) | 2015-03-01 | Hata | Applicant |
| US2015/0127045(A1) | 2015-05-01 | Prestel | Applicant |
| US2015/0133960(A1) | 2015-05-01 | Lohmeier | Applicant |
| US2015/0150635(A1) | 2015-06-01 | Kilroy et al. | Applicant |
| US2015/0164522(A1) | 2015-06-01 | Budiman | Applicant |
| US2015/0190204(A1) | 2015-07-01 | Popovi | Applicant |
| US2015/0201917(A1) | 2015-07-01 | Snow | Applicant |
| US2015/0202085(A1) | 2015-07-01 | Lemonis | Applicant |
| US2015/0223832(A1) | 2015-08-01 | Swaney | Applicant |
| US2015/0297299(A1) | 2015-10-01 | Yeung | Applicant |
| US2015/0305650(A1) | 2015-10-01 | Hunter | Applicant |
| US2015/0314110(A1) | 2015-11-01 | Park | Applicant |
| US2015/0366629(A1) | 2015-12-01 | Bowling | Applicant |
| US2015/0374446(A1) | 2015-12-01 | Malackowski | Applicant |
| US2016/0022289(A1) | 2016-01-01 | Wan | Applicant |
| US2016/0022466(A1) | 2016-01-01 | Pedtke | Applicant |
| US2016/0030073(A1) | 2016-02-01 | Lsakov | Applicant |
| US2016/0045208(A1) | 2016-02-01 | Ciulla | Applicant |
| US2016/0051318(A1) | 2016-02-01 | Manzo et al. | Applicant |
| US2016/0066935(A1) | 2016-03-01 | Nguyen et al. | Applicant |
| US2016/0158490(A1) | 2016-06-01 | Leeflang | Applicant |
| US2016/0183841(A1) | 2016-06-01 | Duindarn et al. | Applicant |
| US2016/0199984(A1) | 2016-07-01 | Lohmeier et al. | Applicant |
| US2016/0235495(A1) | 2016-08-01 | Wallace et al. | Applicant |
| US2016/0242858(A1) | 2016-08-01 | Moctezuma de la Barrera | Applicant |
| US2016/0249932(A1) | 2016-09-01 | Rogers et al. | Applicant |
| US2016/0270865(A1) | 2016-09-01 | Landey et al. | Applicant |
| US2016/0287279(A1) | 2016-10-01 | Bovay et al. | Applicant |
| US2016/0302871(A1) | 2016-10-01 | Gregerson et al. | Applicant |
| US2016/0303743(A1) | 2016-10-01 | Rockrohr | Applicant |
| US2016/0310146(A1) | 2016-10-01 | Levy et al. | Applicant |
| US2016/0314710(A1) | 2016-10-01 | Jarc et al. | Applicant |
| US2016/0331358(A1) | 2016-11-01 | Gordon | Applicant |
| US2016/0367324(A1) | 2016-12-01 | Sato et al. | Applicant |
| US2017/0000577(A1) | 2017-01-01 | Bowling | Applicant |
| US2017/0007337(A1) | 2017-01-01 | Dan | Applicant |
| US2017/0010620(A1) | 2017-01-01 | Watabe | Applicant |
| US2017/0020615(A1) | 2017-01-01 | Koenig et al. | Applicant |
| US2017/0049471(A1) | 2017-02-01 | Gaffney et al. | Applicant |
| US2017/0055995(A1) | 2017-03-01 | Weier | Applicant |
| US2017/0056117(A1) | 2017-03-01 | Hourtash et al. | Applicant |
| US2017/0065227(A1) | 2017-03-01 | Marrs | Applicant |
| US2017/0071456(A1) | 2017-03-01 | Ratnakar | Applicant |
| US2017/0071584(A1) | 2017-03-01 | Suigetsu et al. | Applicant |
| US2017/0086934(A1) | 2017-03-01 | Devengenzo et al. | Applicant |
| US2017/0095234(A1) | 2017-04-01 | Prisco et al. | Applicant |
| US2017/0095295(A1) | 2017-04-01 | Overmyer | Applicant |
| US2017/0095299(A1) | 2017-04-01 | Hendrick | Applicant |
| US2017/0135706(A1) | 2017-05-01 | Frey | Applicant |
| US2017/0135710(A1) | 2017-05-01 | Hasegawa et al. | Applicant |
| US2017/0135833(A1) | 2017-05-01 | Syed | Applicant |
| US2017/0143442(A1) | 2017-05-01 | Tesar | Applicant |
| US2017/0151416(A1) | 2017-06-01 | Kutikov | Applicant |
| US2017/0165009(A1) | 2017-06-01 | Chaplin et al. | Applicant |
| US2017/0172553(A1) | 2017-06-01 | Chaplin | Applicant |
| US2017/0172680(A1) | 2017-06-01 | Bowling | Applicant |
| US2017/0189118(A1) | 2017-07-01 | Chopra et al. | Applicant |
| US2017/0189131(A1) | 2017-07-01 | Weir | Applicant |
| US2017/0202627(A1) | 2017-07-01 | Sramek et al. | Applicant |
| US2017/0209073(A1) | 2017-07-01 | Sramek et al. | Applicant |
| US2017/0252096(A1) | 2017-09-01 | Felder | Applicant |
| US2017/0258534(A1) | 2017-09-01 | Hourtash et al. | Applicant |
| US2017/0265923(A1) | 2017-09-01 | Privitera | Applicant |
| US2017/0265954(A1) | 2017-09-01 | Burbank | Applicant |
| US2017/0281145(A1) | 2017-10-01 | Crawford et al. | Applicant |
| US2017/0290631(A1) | 2017-10-01 | Lee et al. | Applicant |
| US2017/0296277(A1) | 2017-10-01 | Hourtash et al. | Applicant |
| US2017/0319289(A1) | 2017-11-01 | Neff et al. | Applicant |
| US2017/0333145(A1) | 2017-11-01 | Griffiths | Applicant |
| US2017/0333147(A1) | 2017-11-01 | Bernstein | Applicant |
| US2018/0000563(A1) | 2018-01-01 | Shanjani et al. | Applicant |
| US2018/0025666(A1) | 2018-01-01 | Ho et al. | Applicant |
| US2018/0036884(A1) | 2018-02-01 | Chen et al. | Applicant |
| US2018/0049824(A1) | 2018-02-01 | Harris | Applicant |
| US2018/0078439(A1) | 2018-03-01 | Cagle et al. | Applicant |
| US2018/0079090(A1) | 2018-03-01 | Koenig | Applicant |
| US2018/0080841(A1) | 2018-03-01 | Cordoba | Applicant |
| US2018/0098817(A1) | 2018-04-01 | Nichogi et al. | Applicant |
| US2018/0140371(A1) | 2018-05-01 | Hares et al. | Applicant |
| US2018/0193049(A1) | 2018-07-01 | Heck et al. | Applicant |
| US2018/0206931(A1) | 2018-07-01 | Scheib | Applicant |
| US2018/0221038(A1) | 2018-08-01 | Noonan et al. | Applicant |
| US2018/0221039(A1) | 2018-08-01 | Shah | Applicant |
| US2018/0250085(A1) | 2018-09-01 | Simi | Applicant |
| US2018/0263714(A1) | 2018-09-01 | Kostrzewski | Applicant |
| US2018/0279852(A1) | 2018-10-01 | Rafii-Tari et al. | Applicant |
| US2018/0289431(A1) | 2018-10-01 | Draper et al. | Applicant |
| US2018/0296285(A1) | 2018-10-01 | Simi et al. | Applicant |
| US2018/0325499(A1) | 2018-11-01 | Landey et al. | Applicant |
| US2018/0338799(A1) | 2018-11-01 | Hladio et al. | Applicant |
| US2018/0360435(A1) | 2018-12-01 | Romo | Applicant |
| US2018/0368920(A1) | 2018-12-01 | Ummalaneni | Applicant |
| US2019/0000559(A1) | 2019-01-01 | Berman et al. | Applicant |
| US2019/0000560(A1) | 2019-01-01 | Berman et al. | Applicant |
| US2019/0000576(A1) | 2019-01-01 | Mintz et al. | Applicant |
| US2019/0015166(A1) | 2019-01-01 | Mahoney | Applicant |
| US2019/0047154(A1) | 2019-02-01 | Itkowitz et al. | Applicant |
| US2019/0054620(A1) | 2019-02-01 | Griffiths et al. | Applicant |
| US2019/0069962(A1) | 2019-03-01 | Tabandeh et al. | Applicant |
| US2019/0099231(A1) | 2019-04-01 | Bruehwiler | Applicant |
| US2019/0099232(A1) | 2019-04-01 | Soto et al. | Applicant |
| US2019/0110839(A1) | 2019-04-01 | Rafii-Tari et al. | Applicant |
| US2019/0117320(A1) | 2019-04-01 | Shoham et al. | Applicant |
| US2019/0117324(A1) | 2019-04-01 | Hibner | Applicant |
| US2019/0133689(A1) | 2019-05-01 | Johnson et al. | Applicant |
| US2019/0151148(A1) | 2019-05-01 | Alvarez et al. | Applicant |
| US2019/0159848(A1) | 2019-05-01 | Quaid et al. | Applicant |
| US2019/0167366(A1) | 2019-06-01 | Ummalaneni | Applicant |
| US2019/0175009(A1) | 2019-06-01 | Mintz | Applicant |
| US2019/0183585(A1) | 2019-06-01 | Rafii-Tari et al. | Applicant |
| US2019/0183587(A1) | 2019-06-01 | Rafii-Tari et al. | Applicant |
| US2019/0192249(A1) | 2019-06-01 | Bowling | Applicant |
| US2019/0216548(A1) | 2019-07-01 | Ummalaneni | Applicant |
| US2019/0216550(A1) | 2019-07-01 | Eyre | Applicant |
| US2019/0216576(A1) | 2019-07-01 | Eyre | Applicant |
| US2019/0223974(A1) | 2019-07-01 | Romo | Applicant |
| US2019/0231460(A1) | 2019-08-01 | DiMaio | Applicant |
| US2019/0239890(A1) | 2019-08-01 | Stokes | Applicant |
| US2019/0262084(A1) | 2019-08-01 | Roh et al. | Applicant |
| US2019/0262086(A1) | 2019-08-01 | Connolly et al. | Applicant |
| US2019/0269468(A1) | 2019-09-01 | Hsu et al. | Applicant |
| US2019/0274764(A1) | 2019-09-01 | Romo | Applicant |
| US2019/0290109(A1) | 2019-09-01 | Aarawal et al. | Applicant |
| US2019/0298460(A1) | 2019-10-01 | Al-Jadda | Applicant |
| US2019/0298464(A1) | 2019-10-01 | Abbott | Applicant |
| US2019/0298465(A1) | 2019-10-01 | Chin | Applicant |
| US2019/0298469(A1) | 2019-10-01 | Ramstad et al. | Applicant |
| US2019/0314616(A1) | 2019-10-01 | Moll et al. | Applicant |
| US2019/0336238(A1) | 2019-11-01 | Yu | Applicant |
| US2019/0365201(A1) | 2019-12-01 | Noonan et al. | Applicant |
| US2019/0365209(A1) | 2019-12-01 | Ye et al. | Applicant |
| US2019/0365479(A1) | 2019-12-01 | Rafii-Tari | Applicant |
| US2019/0365486(A1) | 2019-12-01 | Srinivasan et al. | Applicant |
| US2019/0375383(A1) | 2019-12-01 | Alvarez | Applicant |
| US2019/0380787(A1) | 2019-12-01 | Ye | Applicant |
| US2019/0380797(A1) | 2019-12-01 | Yu | Applicant |
| US2020/0000533(A1) | 2020-01-01 | Schuh | Applicant |
| US2020/0030046(A1) | 2020-01-01 | Bowling | Applicant |
| US2020/0038123(A1) | 2020-02-01 | Graetzel | Applicant |
| US2020/0039086(A1) | 2020-02-01 | Meyer | Applicant |
| US2020/0046434(A1) | 2020-02-01 | Graetzel | Applicant |
| US2020/0060516(A1) | 2020-02-01 | Baez | Applicant |
| US2020/0085516(A1) | 2020-03-01 | DeFonzo | Applicant |
| US2020/0093549(A1) | 2020-03-01 | Chin et al. | Applicant |
| US2020/0093554(A1) | 2020-03-01 | Schuh | Applicant |
| US2020/0100855(A1) | 2020-04-01 | Leparmentier | Applicant |
| US2020/0107894(A1) | 2020-04-01 | Wallace | Applicant |
| US2020/0121502(A1) | 2020-04-01 | Kintz | Applicant |
| US2020/0138531(A1) | 2020-05-01 | Chaplin | Applicant |
| US2020/0146769(A1) | 2020-05-01 | Eyre | Applicant |
| US2020/0163726(A1) | 2020-05-01 | Tanner | Applicant |
| US2020/0170720(A1) | 2020-06-01 | Ummalaneni | Applicant |
| US2020/0171660(A1) | 2020-06-01 | Ho | Applicant |
| US2020/0188043(A1) | 2020-06-01 | Yu | Applicant |
| US2020/0197109(A1) | 2020-06-01 | Chaplin | Applicant |
| US2020/0197112(A1) | 2020-06-01 | Chin | Applicant |
| US2020/0206472(A1) | 2020-07-01 | Ma | Applicant |
| US2020/0217733(A1) | 2020-07-01 | Lin | Applicant |
| US2020/0222134(A1) | 2020-07-01 | Schuh | Applicant |
| US2020/0237458(A1) | 2020-07-01 | DeFonzo | Applicant |
| US2020/0261172(A1) | 2020-08-01 | Romo | Applicant |
| US2020/0268459(A1) | 2020-08-01 | Noonan et al. | Applicant |
| US2020/0268460(A1) | 2020-08-01 | Tse | Applicant |
| US2020/0281787(A1) | 2020-09-01 | Ruiz | Applicant |
| US2020/0297437(A1) | 2020-09-01 | Schuh | Applicant |
| US2020/0297444(A1) | 2020-09-01 | Camarillo | Applicant |
| US2020/0305983(A1) | 2020-10-01 | Yampolsky | Applicant |
| US2020/0305989(A1) | 2020-10-01 | Schuh | Applicant |
| US2020/0305992(A1) | 2020-10-01 | Schuh | Applicant |
| US2020/0315717(A1) | 2020-10-01 | Bovay | Applicant |
| US2020/0315723(A1) | 2020-10-01 | Hassan | Applicant |
| US2020/0323596(A1) | 2020-10-01 | Moll | Applicant |
| US2020/0330167(A1) | 2020-10-01 | Romo | Applicant |
| US2020/0335207(A1) | 2020-10-01 | Kara et al. | Applicant |
| US2020/0345216(A1) | 2020-11-01 | Jenkins | Applicant |
| US2020/0352420(A1) | 2020-11-01 | Graetzel | Applicant |
| US2020/0360183(A1) | 2020-11-01 | Alvarez | Applicant |
| US2020/0367726(A1) | 2020-11-01 | Landey et al. | Applicant |
| US2020/0367981(A1) | 2020-11-01 | Ho et al. | Applicant |
| US2020/0375678(A1) | 2020-12-01 | Wallace | Applicant |
| US2020/0405375(A1) | 2020-12-01 | Shelton, IV et al. | Applicant |
| US2020/0405403(A1) | 2020-12-01 | Shelton, IV et al. | Applicant |
| US2020/0405406(A1) | 2020-12-01 | Harris et al. | Applicant |
| US2020/0405414(A1) | 2020-12-01 | Shelton, IV et al. | Applicant |
| US2021/0068908(A1) | 2021-03-01 | Thienphrapa et al. | Applicant |
| US2021/0093407(A1) | 2021-04-01 | Fredrickson et al. | Applicant |
| US2021/0275275(A1) | 2021-09-01 | Toporek | Applicant |
| US2022/0022984(A1) | 2022-01-01 | Peine et al. | Applicant |
| CN101443069 | 2009-05-01 | Applicant | |
| CN100515347 | 2009-07-01 | Applicant | |
| CN103298414 | 2013-09-01 | Applicant | |
| CN104619281 | 2015-05-01 | Applicant | |
| CN205729413 | 2016-11-01 | Applicant | |
| EP347098 | 1996-02-01 | Applicant | |
| EP1321106 | 2003-06-01 | Applicant | |
| EP1849423 | 2007-10-01 | Applicant | |
| JP2005270464 | 2005-10-01 | Applicant | |
| WO-06/124390 | 2006-11-01 | Applicant | |
| WO-11/161218 | 2011-12-01 | Applicant | |
| WO-13/107468 | 2013-07-01 | Applicant | |
| WO-15/153174 | 2015-10-01 | Applicant | |
| WO-16/137612 | 2016-09-01 | Applicant | |
| WO-17/048194 | 2017-03-01 | Applicant | |
| WO-17/114855 | 2017-07-01 | Applicant | |
| WO-18/069679 | 2018-04-01 | Applicant | |
| WO-18/189722 | 2018-10-01 | Applicant | |
| WO2019/136039(A1) | 2019-07-01 | Applicant |
Non-Patent Literature (13)
- Aghakhani et al., May 6, 2013, Task control with remote center of motion constraint for minimally invasive robotic surgery, 2013 IEEE International Conference on Robotics and Automation, pp. 5807-5812.Applicant
- Darwiche, 2015, Operative technique and early experience for robotic assisted laparoscopic nephroueterectomy (RALNU) using da Vinci XI, SpingerPlus, 4:298.Applicant
- Hernansanz et al., A multi-robot cooperation strategy for dexterous task oriented teleoperation, 2015, Elsevier, Robotics and Autonomous Systems 68 (205), 156-172 (Year: 2015).Applicant
- Ramezanifard et al, A Novel Modeling Approach for Collision Avoidance in Robotic Surgery, 2007 Science Publications, American Journal of Applied Sciences 4 (9): 693-699 (Year: 2007).Applicant
- Sasaki, 2017, Laparoscopic hemicolectomy for a patient with situs inversus totalis: a case report, Int. J. Surg. Case Rep. 41;93-96.Applicant
- International Preliminary Report on Patentability dated Apr. 7, 2022, issued in International Application No. PCT/IB2020/058715, 14 pages.Applicant
- European Examination Report dated Dec. 18, 2024, for Application No. 20786049.5, 9 pages.Applicant
- International Search Report and Written Opinion dated Dec. 22, 2020 for Application No. PCT/IB2020/058717, 20 pgs.Applicant
- International Preliminary Report on Patentability dated Apr. 7, 2022, for International Application No. PCT/IB2020/058717, 17 pages.Applicant
- U.S. Appl. No. 62/906,612, entitled “Systems and Methods for Collision Detection and Avoidance,” filed Sep. 26, 2019.Applicant
- U.S. Appl. No. 62/906,613, entitled “Systems and Methods for Collision Avoidance Using Object Models,” filed Sep. 26, 2019.Applicant
- European Communication dated Dec. 11, 2024, for Application No. 20781088.8, 12 pages.Applicant
- International Search Report and Written Opinion dated Dec. 18, 2020, for International Application No. PCT/IB2020/058715, 17 pages.Applicant