The systems and methods disclosed herein are directed to surgical robotic systems, and more particularly to detecting undesirable forces on one or more robotic arms in a surgical robotic system.
Medical procedures such as endoscopy (e.g., bronchoscopy) may involve the insertion of a medical tool into a patient's luminal network (e.g., airways) for diagnostic and/or therapeutic purposes. Surgical robotic systems may be used to control the insertion and/or manipulation of the steerable instrument tool during a medical procedure. The surgical robotic system may comprise at least one robotic arm including an instrument device manipulator (IDM) assembly which may be used to control the positioning of the steerable instrument during the medical procedure.
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.
In one aspect, there is provided a system comprising: a first robotic arm, comprising: at least two linkages, at least one joint connecting the at least two linkages, at least one torque sensor configured to detect torque between the at least two linkages, and an instrument device manipulator (IDM) connected to a distal end of the first robotic arm; a processor; and a memory storing computer-executable instructions to cause the processor to: measure a first torque value at the at least one joint based on an output of the torque sensor, determine a second torque value at the at least one joint based on a position of the first robotic arm, the second torque value indicative of a gravitational component of the torque between the at least two linkages, determine a first force at the IDM based on a difference between the first and second torque values, and determine whether the first robotic arm has collided with an object based on the first force at the IDM.
In another aspect, there is provided a non-transitory computer readable storage medium having stored thereon instructions that, when executed, cause at least one computing device to: measure a first torque value at a joint of a first robotic arm based on an output of a torque sensor, the first robotic arm comprising: two linkages connected by the joint, a torque sensor configured to detect torque between the two linkages, and an instrument device manipulator (IDM) connected to a distal end of the first robotic arm; determine a second torque value at the joint based on a position of the first robotic arm, the second torque value indicative of a gravitational component of the torque between the two linkages; determine a first force at the IDM based on a difference between the first and second torque values; and determine whether the first robotic arm has collided with an object based on the first force at the IDM.
In yet another aspect, there is provided a method of positioning a first robotic comprising: measuring a first torque value at a joint of a first robotic arm based on an output of a torque sensor, the first robotic arm comprising: two linkages connected by the joint, a torque sensor configured to detect torque between the two linkages, and an instrument device manipulator (IDM) connected to a distal end of the first robotic arm; determining a second torque value at the joint based on a position of the first robotic arm, the second torque value indicative of a gravitational component of the torque between the two linkages; determining a first force at the IDM based on a difference between the first and second torque values; and determining whether the first robotic arm has collided with an object based on the first force at the IDM.
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.
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 endoscopy procedures, the system may be capable of performing bronchoscopy, ureteroscopy, gastroenterology, etc.
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.
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.
The robotically-enabled medical system may be configured in a variety of ways depending on the particular procedure.
With continued reference to
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 independent of each other.
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 may need to 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.
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/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.
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.
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 system that may be deployed through the endoscope 13. These components may also be controlled using the computer system of tower 30. In some embodiments, irrigation and aspiration capabilities may be delivered directly to the endoscope 13 through separate cable(s).
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.
The tower 30 may also include support equipment for the sensors deployed throughout the robotic system 10. For example, the tower 30 may include opto-electronics 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 opto-electronics 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.
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 system 10 are generally designed to provide both robotic controls as well as pre-operative 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 system, as well as provide procedure-specific data, such as navigational and localization information.
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, the support for controls, optics, fluidics, and/or navigation may be provided through a separate cable.
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 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 robotic arms 12 to be angled in a variety of configurations.
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 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.
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.
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 available to the robotic arm. Each of the arms 12 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. Redundant degrees of freedom allow 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.
The cart base 15 balances the weight of the column 14, carriage 17, and 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. For example, the cart base 15 includes rollable wheel-shaped casters 25 that allow for the cart 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.
Positioned at the vertical end of 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 pre-operative and intra-operative data. Potential pre-operative data on the touchscreen 26 may include pre-operative plans, navigation and mapping data derived from pre-operative computerized tomography (CT) scans, and/or notes from pre-operative patient interviews. Intra-operative 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 from the side of the column 14 opposite 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 cart 11.
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 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.
B. Robotic System—Table.
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.
The arms 39 may be mounted on the carriages 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 table 38 (as shown in
The column 37 structurally provides support for the table 38, and a path for vertical translation of the carriages. Internally, the column 37 may be equipped with lead screws for guiding vertical translation of the carriages, and motors to mechanize the translation of said carriages based the lead screws. The column 37 may also convey power and control signals to the carriage 43 and robotic arms 39 mounted thereon.
The table base 46 serves a similar function as the cart base 15 in cart 11 shown in
Continuing with
In some embodiments, a table base may stow and store the robotic arms when not in use.
In a laparoscopic procedure, through small incision(s) in the patient's abdominal wall, minimally invasive instruments (elongated in shape to accommodate the size of the one or more incisions) may be inserted into the patient's anatomy. After inflation of the patient's abdominal cavity, the instruments, often referred to as laparoscopes, may be directed to perform surgical tasks, such as grasping, cutting, ablating, suturing, etc.
To accommodate laparoscopic procedures, the robotically-enabled table system may also tilt the platform to a desired angle.
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 lower 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 procedures, such as laparoscopic prostatectomy.
C. Instrument Driver & Interface.
The end effectors of the system's robotic arms comprise (i) an instrument driver (alternatively referred to as “instrument drive mechanism” or “instrument device manipulator” (IDM)) that incorporate 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.
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 of 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.
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 66 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 comprising a jointed wrist formed from a clevis with an axis of rotation and a surgical tool, 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.
Torque from the instrument driver 75 is transmitted down the elongated shaft 71 using tendons within the 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 within the elongated shaft 71 and anchored at the distal portion of the elongated shaft 71. In laparoscopy, 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 laparoscopy, 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 distal end of the elongated shaft 71, where tension from the tendon cause the grasper to close.
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 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 there between 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 also exhibits 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.
In endoscopy, the elongated shaft 71 houses a number of components to assist with the robotic procedure. The shaft may comprise of a working channel for deploying surgical tools, 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 of 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.
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.
In the example of
Like earlier disclosed embodiments, an instrument 86 may comprise of 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, instrument shaft 88 extends from the center of instrument base 87 with an axis substantially parallel to the axes of the drive inputs 89, rather than orthogonal as in the design of
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.
E. Navigation and Control.
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 pre-operative 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 pre-operative 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.
As shown in
The various input data 91-94 are now described in greater detail. Pre-operative mapping may be accomplished through the use of the collection of low dose CT scans. Pre-operative CT scans generate two-dimensional images, each representing a “slice” 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 preoperative model data 91. The use of center-line geometry is discussed in U.S. patent application Ser. No. 14/523,760, 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.
In some embodiments, the instrument may be equipped with a camera to provide vision data 92. The localization module 95 may process the vision data to enable one or more vision-based location tracking. For example, the preoperative model data 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. Intra-operatively, 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.
Other computer vision-based tracking techniques use feature tracking to determine motion of the camera, and thus the endoscope. Some feature 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.
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. Through the comparison of multiple frames over multiple iterations, movement and location of the camera (and thus the endoscope) may be determined.
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 of 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 intra-operatively “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 pre-operative 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.
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 pre-operative calibration. Intra-operatively, 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.
As
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.
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.
Embodiments of the disclosure relate to systems and techniques for the detection of undesirable forces occurring with respect to one or more robotic arms of a surgical robotic system. The detection of undesirable force events may be an important factor in the overall safety of the surgical robotic system. For example, if a robotic arm collides with an object during a medical procedure, the collision may result in unexpected forces being applied to the robotic arm, which may affect the position and/or force applied to a steerable instrument located in the patient. Thus, it is important to detect robotic arm collisions and appropriately respond to the collisions to prevent harm to the patient.
As used herein, the term “collision” may generally refer to contact between two or more objects. A collision may occur between two robotic arms and/or between a robotic arm and another object in the operating environment (e.g., a platform, a cart, a C-arm, etc.). Another source of unexpected or undesirable force(s) at one or more robotic arms may also be misalignment between two robotic arms. While misalignment may not involve a collision between the two robotic arms, misalignment may result in similar unexpected forces, and thus it may also be important to detect misalignment for the overall safety of the surgical robotic system.
The system may take one or more actions in response to the detection of a collision or misalignment. For example, the system may provide an indication of the detected event (e.g., collision or misalignment) to a user of the system. The indication of the detected event to the user may be provided via one or more output devices, including a display device, a haptic feedback device, an audio device, etc. The system may also discontinue the medical procedure until the collision or misalignment event has been resolved.
A. Example System for Detecting Collision and Misalignment.
Returning to
The robotic arm(s) 110 and 120 may include a first robotic arm 110 and a second robotic arm 120, respectively. However, aspects of this disclosure are also applicable to system having a greater or fewer number of robotic arms. In the embodiment of
Additionally, a given joint 113 may further house a motor (not illustrated) configured to apply a force between the two adjacent linkages 111 to the given joint 113 in order to adjust the positioning of the two adjacent linkages 111. The IDM 115 may be connected to a distal end of the robotic arm 110. By actuating the motor(s) in one or more of the joints 113 of the first robotic arm 110, the motor(s) may be operable to adjust the posture or pose of the first robotic arm 110, and thus the IDM 115 (e.g., by adjusting the position and/or orientation of one or more joints 113 of the first arm) and thereby control a steerable instrument 130 attached to the IDM 115.
Each of the joints 113 may further house a position sensor configured to measure the relative position of the two adjacent linkages 111. Thus, a given joint 113 may further house the position sensor, which may be configured to measure the angle between the two adjacent linkages 111. The system may be able to determine the position of each of the linkages 111 in the first robotic arm 110 based on the output of each of the position sensors. Additionally, as discussed below, the output of the position sensors may be used to determine a force applied to a reference point on the first robotic arm 110. In certain embodiments, a given position sensor may include an encoder. The encoder may be configured to measure the speed and/or position of the motor shaft by reading, for example, coded visual information printed on the motor shaft and may provide feedback to the system representative of the speed and/or position of the motor.
Similar to the first robotic arm 110, the second robotic arm 120 may include a, plurality of linkages 121, a plurality of joints 123 connecting adjacent linkages 121, and an IDM 125. Each of the joints 123 may house a corresponding torque sensor and motor (not illustrated). The IDM 125 may also be attached to the second medical instrument 133 to operate the steerable instrument 130.
In certain embodiments, rather than including separate torque sensors and motors in each of the joints 113 and 123, the motors may also function as torque sensors. For example, when a force is applied to the first robotic arm 110 (e.g., the force of gravity, the force of a collision, a force exerted by a user, etc.), the motor(s) may be configured to apply opposite and opposing force(s) to the joint 113 to maintain the position of the first robotic arm 110. The current required in the motor(s) to maintain the first robotic arm 110 position may correspond to the torque applied to the corresponding joints 113.
The steerable instrument 130 in the
The first and second medical instruments 131 and 133 may be configured to be advanced/inserted into (or retracted from) a patient along a first axis 140. As discussed above, the first axis 140 may be termed a virtual rail. The virtual rail may be defined by the axis of alignment of the IDMs 115 and 125. Movement of the IDMs 115 and 125 along the virtual rail may control the advancing and retracting of the first and second medical instruments 131 and 133 into and out of the patient. As shown in
B. Determination of Force Applied to Robotic Arm(s) and Collision Detection.
One technique for detecting collisions or misalignment of the robotic arm(s) is to analyze the forces experience by the robotic arm(s). For example, while the robotic arm(s) are stationary, the only expected force on the arm(s) is the force due to gravity. Accordingly, any force experienced by the robotic arm(s) that is inconsistent with the expected force due to gravity (e.g., when the difference between the expected force and the measured force is greater than a threshold value) may be indicative of a collision between at least one of the robotic arm(s) and another object.
Certain surgical robotic systems may incorporate a force sensor in each of the robotic arms to measure the force experienced at a reference point on the corresponding robotic arm. For example, a force sensor may be positioned on or near (e.g., within a defined distance of) the IDM 115 of the first robotic arm 110 of
The method 1700 begins at block 1701. At block 1705, the system receives robotic arm torque and position values. The system may receive torque values from each of the torque sensors included in the robotic arm. Further, the system may retrieve position values from position data stored in memory that indicate the position of each of the linkages in the robotic arm. For example, the robotic arms may further include an encoder formed on each of the joints. The encoder may measure the speed and/or position of the motor shaft by reading coded visual information printed on the motor shaft and may provide feedback to the system representative of the speed and/or position of the motor. The system may be configured to determine the position of each of the joints based on the feedback from the encoders. Using the information from each of the encoders positions on the robotic arm, the system can determine to position of each of the linkages and the DM.
At block 1710, the system determines a gravity-compensated torque value for each of the joints based on the torque values and position values. The gravity-compensated torque value for a given joint may represent the component of the torque at the joint that is due to forces other than the force of gravity. In one implementation, the system may measure a first torque value at a joint based on the output of the corresponding torque sensor. The system may then determine a second torque value at the joint based on the position of the robotic arm. The position data of the robotic arm may include data that enables the system to determine the position of the two linkages connected by the joint and the angle formed therebetween. The second torque value may be indicative of a gravitational component of the torque between the two linkages. The system may then be able to determine the gravity-compensated torque value based on the first and second torque values. For example, the difference between the first and second torque values may correspond to the gravity-compensated torque value.
At block 1715, the system may determine the force exerted on the robotic arm based on the gravity-compensated torque values for each of the joints. The determined force may therefore exclude the component of the forces experienced by the robotic arm due to gravity. An example of one technique for determining the gravity-compensated torque value and the force applied at a reference point on the robotic arm will be discussed in connection with
At block 1720, the system may detect a collision based on the determined force. For example, when the force exceeds a threshold value, the system may determine that the robotic arm has collided with another object. In certain implementations, the system may also determine whether the robotic arm is misaligned with another robotic arm based on the determined force. At block 1725, the system may provide an indication of the detected collision to a user of the system. For example, in response to determining that the force exceeds the threshold value, the system may notify the user that a collision has been detected. Further, in response to detecting misalignment, the system may also provide an indication of the detected misalignment to the user. The method 1700 ends at block 1730.
C. Robotic Arm Free-Body Diagram.
Each of the joints 240 and 245 may include a torque sensor configured to output a measured torque value τmeasured. The measured torque value τmeasured at each of the joints 240 and 245 may be determined according to the following equation:
τmeasured=τforce+τgravity (1)
where τmeasured is the measured torque value, τforce is the torque at the joint 240 or 245 due to the force F applied to the robotic arm 210, and τgravity is the torque applied to joint 240 or 245 due to the force of gravity g. In this embodiment, the force F applied to the robotic arm 210 is modelled as being applied to the IDM 250 as a reference point. However, the force may be modelled as being applied to the robotic arm 210 at difference points depending on the embodiment.
The torque due to the force F applied at the reference point and the torque due to gravity g may be determined as follows:
τforce=J(θ)TF (2)
τgravity=G(θ,g) (3)
where J(θ)T is a Jacobian transpose matrix that represents the transmission of the force F to the joint 240 or 245 based on the positions of the joints 240 or 245 in the robotic arm 210 and G(θ, g) represents the transmission of torque to the joints 240 or 245 due to gravity g. Substituting equations (2) and (3) into (1) gives:
τmeasured=J(θ)TF+G(θ,g) (4)
Accordingly, the force F applied to the reference point (e.g., the IDM 250) can be solved based on the measured torques τmeasured the Jacobian transpose matrix J(θ)T, and the transmission of torque due to gravity G (θ, g).
D. Collision and Misalignment Detection.
Once the force(s) at a reference point on one or more robotic arms have been determined, the system may determine whether a collision or misalignment event has occurred based on the force(s). This determination may be based on whether the determined force(s) are consistent with the expected forces at the reference points.
When a robotic arm is stationary, the expected value of a gravity-compensated force (e.g., the determined force in which the component of the force due to gravity has been removed) is zero. That is, under normal circumstances, there is no force expected to be applied to the arm other than the force due to gravity when the robotic arm is stationary. As such, when the robotic arm is stationary, the system may compare the force to a threshold value. If the gravity-compensated force is greater than the threshold value, the system may determine that an object has collided with the robotic arm.
In certain implementations, the system may determine the components of the force in each of the X, Y, and Z-axes. The system may, at a certain frequency, determine the components of the force during a medical procedure. The expected values of the force may depend on the medical procedure being performed. For example, while a medical instrument is being advanced into a patient along the Y-axis (which may correspond to a first axis 140 or axis of insertion, see
Additionally, the X and Z-components of the force may be correlated with the Y-component of the force or changes in the configuration of the medical instrument as the medical instrument is being driven. That is, changes in the X and Z-components of the force may occur when driving of the medical instrument starts or stops (e.g., when the Y-component of the force transitions to or from about 0 N). Further, when the direction of insertion of the distal end of the medical instrument changes, the force transmitted back to the IDM from the medical instrument may also change.
Referring back to
If the first IDM 115 and the second IDM 125 are not properly aligned along the first axis 140, a force may be generated between the first and second IDMs 115 and 125 in the direction of misalignment in the X-Z plane. Accordingly, the first IDM 115 and the second IDM 125 may experience opposite and opposing forces in the X-Z plane due to the misalignment of the first and second IDMs 115 and 125. Further, the forces caused due to misalignment may only be generated while driving one or more of the first and second medical instruments 131 and 133 (e.g., while advancing/inserting the second medical instrument 133 or retracting the first medical instrument 131).
In order to detect a misalignment event, the system may be configured to detect a second force at the second IDM 125 of the second robotic arm 120. The system may determine that at least one of the first force measured at the first IDM 115 and the second force measured at the second IDM 125 is greater than a threshold force. The system may further determine that that the first and second robotic arms 110 and 120 are misaligned in response to determining that both of the first and second forces are greater than the threshold force.
E. Example Collision and Misalignment Detection Technique.
In one example implementation, the surgical robotic system may be configured to detect both collision and misalignment events and provide an indication to a user that an event has been detected.
The method 2000 begins at block 2001. At block 2105 the processor determines forces at IDMs of first and second robotic arms. For example, the processor may determine a first force at a first IDM of the first robotic arm and determine a second force at a second IDM of the second robotic arm. The processor may determine the forces based on: i) output received from torque sensors located at each of the joints of the first and second robotic arms and ii) positions of the first and second robotic arms. The first and second forces may be adjusted to remove the forces experienced by the first and second robotic arms due to gravity.
At block 2010, the processor determines whether at least one of the first and second forces is indicative of a collision. For example, the processor may determine whether the first robotic arm has collided with an object based on the first force at the first IDM. Similarly, the processor may determine whether the second robotic arm has collided with an object based on the second force at the second IDM.
In one implementation, the first and/or second robotic arms may be configured to advance a steerable instrument into a patient by movement of the first and/or second IDMs along a first axis. The processor may determine a first component of the first force applied to the first IDM along a second axis perpendicular to the first axis. The processor may determine that the first component of the first force is greater than a first threshold value. Thus, the processor may determine that the first robotic arm has collided with an object based on determining that the first component of the first force is greater than the first threshold value. Since forces along an axis perpendicular to the axis of insertion (e.g., the first axis) are expected to be less than the threshold value, the processor may interpret components of the first force along the perpendicular axis that are greater than the first threshold value to be indicative of a collision. The processor may perform a similar procedure to determine whether the second robotic arm has collided with an object.
The processor may also compare the component of the force along the first axis of insertion to a second threshold. For example, the processor may determine a second component of the first force applied to the IDM along the first axis and determine that the second component of the first force is greater than a second threshold value. The processor may determine that the first robotic arm has collided with the object based on determining that the second component of the first force is greater than the second threshold value, where the second threshold value greater than an expected force of insertion of the steerable instrument into the patient. In this embodiment, the second threshold may be selected to be greater than the expected force of insertion along the first axis, such that any component of the force measured in the first axis that is greater than the second threshold may be determined to be due to a collision with an object.
In response to determining that the first and second forces are not indicative of a collision, the method 2000 may continue at block 2015, where the processor determines whether the first and second forces are indicative of misalignment. In certain implementations, the processor may determine that both of the first and second forces are greater than a third threshold force and determine that that the first and second robotic arms are misaligned in response to determining that both of the first and second forces are greater than the third threshold force.
The processor may also determine insertion data that indicates that the second medical instrument was being driven (e.g., inserted or retracted) through the first medical instrument at the time that the second force was detected. The insertion data may be stored in the memory and may be determined based on at least one of: the position of the first and second robotic arms and instructions to drive the second medical instrument received from a user. The processor may determine that the first and second robotic arms are misaligned in response to determining that the insertion data indicates that the second medical instrument was being driven (e.g., inserted or retracted) through the first medical instrument. Further, in certain implementations, the processor may determine the forces experienced by the IDMs of the first and second robotic arms are not due to misalignment when the second medical instrument is not being driven through the first medical instrument during measurement of the first and second forces.
In another implementation, the insertion data may indicate that the first medical instrument was being driven at the time that the first and second torque values were measured. The processor may determine that the first force is greater than the threshold value and determine that the first robotic arm is misaligned with a patient introducer in response to determining that the insertion data indicates that the first medical instrument was being driven and determining that the first force is greater than the first threshold value. The patient introducer may be a device configured to guide the first medical instrument into the patient. In certain implementations, the system may be configured to determine a force exerted on the patient introducer. In these implementations, the processor may determine whether the force applied to the patient introducer and the first force are in opposing directions and determine that the first IDM is misaligned with the patient introducer in response to the force applied to the patient introducer and the first force being in opposing directions.
In some embodiments, the processor may be further configured to determine that the first and second forces are in opposing directions. The processor may also determine that a difference between the magnitudes of the first and second forces is less than a threshold difference. The processor may determine that the first and second robotic arms are misaligned in response to determining that the first and second forces are in opposing directions and determining that the difference between the magnitudes of the first and second forces is less than the threshold difference. That the first and second forces having similar magnitudes in opposing directions may be indicative of misalignment since the second medical instrument is coupled to each of the first and second IDMs through the insertion of the second medical instrument into the working channel of the first medical instrument.
In response to determining that one of the first and second robotic arms have collided within an object (in block 2010) or determining that the first and second robotic arm are misaligned, at block 2020, the processor provides an indication of the collision or misalignment. For example, the processor may encode an indication of the collision or misalignment and provide the encoded indication to a display configured to render the encoded data. In certain implementations, the indication may not specify whether the event is a collision or a misalignment. For example, the indication may simply inform the user that a collision/misalignment error has been detected.
In other embodiments, the processor may encode information indicative of the type of event into the indication. For example, the indication may specify at least one of: whether a collision has occurred, which arm(s) are involved in the collision, whether a misalignment has occurred, and which arms are involved in the misalignment.
In response to determining that a collision or misalignment has occurred, the processor may prevent the user from further advancing the steerable instrument into the patient. The indication may further provide instructions to the user to retract the steerable instrument from the patient and reset the system. The processor may also be configured to receive an input from the user indicating that the source of the collision or misalignment has been addressed. In response to receiving an input that the collision or misalignment has been resolved, the processor may allow the user to continue the medical procedure. The method 2000 ends at block 2025.
F. Further Example Collision and Misalignment Technique.
In one example implementation, the surgical robotic system may be configured to detect a collision of a robotic arm.
The method 2100 begins at block 2101. At block 2105, the processor measures a first torque value at a joint of a robotic arm based on an output of a torque sensor. The robotic arm may include: two linkages connected by the joint, a torque sensor configured to detect torque between the two linkages, and an instrument device manipulator (IDM) connected to a distal end of the robotic arm. At block 2110, the processor determines a second torque value at the joint based on a position of the robotic arm. The second torque value may be indicative of a gravitational component of the torque between the two linkages.
At block 2115, the processor determines a force at the IDM based a difference between the first and second torque values. At block 2120, the processor determines whether the robotic arm has collided with an object based on the force at the IDM. In certain implementations, the processor may provide an indication that the robotic arm has collided with an object in response to determining that the robotic arm has collided with the object. The method ends at block 2125.
Implementations disclosed herein provide systems, methods and apparatus for detecting a collision or misalignment of one or more robotic arms of a surgical robotic system. This detection may be based on, in certain embodiments, torque measurements performed at the joints of the robotic arm(s).
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.
The techniques for detection of collision and/or misalignment 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.
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.
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.
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.”
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 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.
Number | Name | Date | Kind |
---|---|---|---|
4644237 | Frushour et al. | Feb 1987 | A |
4748969 | Wardle | Jun 1988 | A |
5408263 | Kikuchi | Apr 1995 | A |
5672877 | Liebig et al. | Sep 1997 | A |
6004016 | Spector | Dec 1999 | A |
6198974 | Webster, Jr. | Mar 2001 | B1 |
6246200 | Blumenkranz et al. | Jun 2001 | B1 |
6459926 | Nowlin | Oct 2002 | B1 |
6837846 | Jaffe | Jan 2005 | B2 |
7197354 | Sobe | Mar 2007 | B2 |
7607440 | Coste-Maniere et al. | Oct 2009 | B2 |
7772541 | Froggatt et al. | Aug 2010 | B2 |
8335557 | Maschke | Dec 2012 | B2 |
8396595 | Dariush | Mar 2013 | B2 |
8442618 | Strommer et al. | May 2013 | B2 |
8506555 | Ruiz Morales | Aug 2013 | B2 |
8554368 | Fielding et al. | Oct 2013 | B2 |
8720448 | Reis et al. | May 2014 | B2 |
8738181 | Greer et al. | May 2014 | B2 |
8827948 | Romo et al. | Sep 2014 | B2 |
8929631 | Pfister et al. | Jan 2015 | B2 |
8945095 | Blumenkranz | Feb 2015 | B2 |
9014851 | Wong et al. | Apr 2015 | B2 |
9129417 | Zheng et al. | Sep 2015 | B2 |
9199372 | Henderson et al. | Dec 2015 | B2 |
9226796 | Bowling | Jan 2016 | B2 |
9256940 | Carelsen et al. | Feb 2016 | B2 |
9289578 | Walker et al. | Mar 2016 | B2 |
9314306 | Yu | Apr 2016 | B2 |
9358682 | Ruiz Morales | Jun 2016 | B2 |
9504604 | Alvarez | Nov 2016 | B2 |
9561083 | Yu et al. | Feb 2017 | B2 |
9622827 | Yu et al. | Apr 2017 | B2 |
9629595 | Walker et al. | Apr 2017 | B2 |
9636184 | Lee et al. | May 2017 | B2 |
9675422 | Hourtash et al. | Jun 2017 | B2 |
9713509 | Schuh et al. | Jul 2017 | B2 |
9727963 | Mintz et al. | Aug 2017 | B2 |
9737371 | Romo et al. | Aug 2017 | B2 |
9737373 | Schuh | Aug 2017 | B2 |
9744335 | Jiang | Aug 2017 | B2 |
9763741 | Alvarez et al. | Sep 2017 | B2 |
9788910 | Schuh | Oct 2017 | B2 |
9789608 | Itkowitz et al. | Oct 2017 | B2 |
9844353 | Walker et al. | Dec 2017 | B2 |
9844412 | Bogusky et al. | Dec 2017 | B2 |
9867635 | Alvarez et al. | Jan 2018 | B2 |
10016900 | Meyer et al. | Jul 2018 | B1 |
10022192 | Ummalaneni | Jul 2018 | B1 |
20030045778 | Ohline | Mar 2003 | A1 |
20030182091 | Kukuk | Sep 2003 | A1 |
20040257021 | Chang et al. | Dec 2004 | A1 |
20050043718 | Madhani | Feb 2005 | A1 |
20050065400 | Banik | Mar 2005 | A1 |
20050256398 | Hastings | Nov 2005 | A1 |
20050261551 | Couvillon | Nov 2005 | A1 |
20060015096 | Hauck et al. | Jan 2006 | A1 |
20060041293 | Mehdizadeh | Feb 2006 | A1 |
20070013336 | Nowlin | Jan 2007 | A1 |
20070043455 | Viswanathan | Feb 2007 | A1 |
20070135886 | Maschke | Jun 2007 | A1 |
20070150155 | Kawai | Jun 2007 | A1 |
20070249911 | Simon | Oct 2007 | A1 |
20070253599 | White et al. | Nov 2007 | A1 |
20070287992 | Diolaiti | Dec 2007 | A1 |
20070299353 | Harlev et al. | Dec 2007 | A1 |
20080123921 | Gielen et al. | May 2008 | A1 |
20080231221 | Ogawa | Sep 2008 | A1 |
20080249640 | Vittor et al. | Oct 2008 | A1 |
20080255505 | Carlson et al. | Oct 2008 | A1 |
20080312771 | Sugiura | Dec 2008 | A1 |
20090076534 | Shelton | Mar 2009 | A1 |
20090184825 | Anderson | Jul 2009 | A1 |
20090198298 | Kaiser et al. | Aug 2009 | A1 |
20090245600 | Hoffman | Oct 2009 | A1 |
20090287354 | Choi | Nov 2009 | A1 |
20100030115 | Fujimoto | Feb 2010 | A1 |
20100076263 | Tanaka | Mar 2010 | A1 |
20100121138 | Goldenberg et al. | May 2010 | A1 |
20100234856 | Stoianovici et al. | Sep 2010 | A1 |
20100256812 | Tsusaka | Oct 2010 | A1 |
20110082462 | Suarez | Apr 2011 | A1 |
20110137122 | Kawai | Jun 2011 | A1 |
20110153252 | Govari | Jun 2011 | A1 |
20110160570 | Kariv | Jun 2011 | A1 |
20110319910 | Roelle et al. | Dec 2011 | A1 |
20120000427 | Nilsson | Jan 2012 | A1 |
20120046522 | Naito | Feb 2012 | A1 |
20120071752 | Sewell | Mar 2012 | A1 |
20120123441 | Au | May 2012 | A1 |
20120209293 | Carlson | Aug 2012 | A1 |
20120215094 | Rahimian et al. | Aug 2012 | A1 |
20120253276 | Govari et al. | Oct 2012 | A1 |
20120328077 | Bouvier | Dec 2012 | A1 |
20130072787 | Wallace et al. | Mar 2013 | A1 |
20130090530 | Ramamurthy | Apr 2013 | A1 |
20130102846 | Sjostrom | Apr 2013 | A1 |
20130131503 | Schneider et al. | May 2013 | A1 |
20130165945 | Roelle | Jun 2013 | A9 |
20130325030 | Hourtash et al. | Dec 2013 | A1 |
20140114180 | Jain | Apr 2014 | A1 |
20140135985 | Coste-Maniere et al. | May 2014 | A1 |
20140142591 | Alvarez et al. | May 2014 | A1 |
20140163664 | Goldsmith | Jun 2014 | A1 |
20140222207 | Bowling | Aug 2014 | A1 |
20140296870 | Stern et al. | Oct 2014 | A1 |
20140309649 | Alvarez et al. | Oct 2014 | A1 |
20140316420 | Ballard et al. | Oct 2014 | A1 |
20140357984 | Wallace et al. | Dec 2014 | A1 |
20140364870 | Alvarez et al. | Dec 2014 | A1 |
20140379000 | Romo et al. | Dec 2014 | A1 |
20150051592 | Kintz | Feb 2015 | A1 |
20150088161 | Hata | Mar 2015 | A1 |
20150101442 | Romo | Apr 2015 | A1 |
20150104284 | Riedel | Apr 2015 | A1 |
20150119628 | Bharat et al. | Apr 2015 | A1 |
20150119638 | Yu et al. | Apr 2015 | A1 |
20150164594 | Romo et al. | Jun 2015 | A1 |
20150164596 | Romo | Jun 2015 | A1 |
20150202015 | Elhawary | Jul 2015 | A1 |
20150223902 | Walker et al. | Aug 2015 | A1 |
20150265359 | Camarillo | Sep 2015 | A1 |
20150297864 | Kokish | Oct 2015 | A1 |
20150335480 | Alvarez et al. | Nov 2015 | A1 |
20150342695 | He | Dec 2015 | A1 |
20150359597 | Gombert | Dec 2015 | A1 |
20150374956 | Bogusky | Dec 2015 | A1 |
20160001038 | Romo et al. | Jan 2016 | A1 |
20160005168 | Merlet | Jan 2016 | A1 |
20160016319 | Remirez | Jan 2016 | A1 |
20160045269 | Elhawary et al. | Feb 2016 | A1 |
20160051221 | Dickhans et al. | Feb 2016 | A1 |
20160066794 | Klinder et al. | Mar 2016 | A1 |
20160081568 | Kolberg | Mar 2016 | A1 |
20160100772 | Ikuma | Apr 2016 | A1 |
20160228032 | Walker et al. | Aug 2016 | A1 |
20160270865 | Landey et al. | Sep 2016 | A1 |
20160278865 | Capote | Sep 2016 | A1 |
20160287111 | Jacobsen | Oct 2016 | A1 |
20160287279 | Bovay et al. | Oct 2016 | A1 |
20160296294 | Moll et al. | Oct 2016 | A1 |
20160331469 | Hall et al. | Nov 2016 | A1 |
20160338787 | Popovic | Nov 2016 | A1 |
20160346924 | Hasegawa | Dec 2016 | A1 |
20160354057 | Hansen et al. | Dec 2016 | A1 |
20160360949 | Hyodo | Dec 2016 | A1 |
20160374541 | Agrawal et al. | Dec 2016 | A1 |
20170007337 | Dan | Jan 2017 | A1 |
20170056215 | Nagesh et al. | Mar 2017 | A1 |
20170065364 | Schuh et al. | Mar 2017 | A1 |
20170065365 | Schuh | Mar 2017 | A1 |
20170068796 | Passerini et al. | Mar 2017 | A1 |
20170100199 | Yu et al. | Apr 2017 | A1 |
20170119411 | Shah | May 2017 | A1 |
20170119412 | Noonan et al. | May 2017 | A1 |
20170119413 | Romo | May 2017 | A1 |
20170119481 | Romo et al. | May 2017 | A1 |
20170151027 | Walker et al. | Jun 2017 | A1 |
20170165011 | Bovay et al. | Jun 2017 | A1 |
20170165503 | Hautvast et al. | Jun 2017 | A1 |
20170172673 | Yu et al. | Jun 2017 | A1 |
20170202627 | Sramek et al. | Jul 2017 | A1 |
20170209073 | Sramek et al. | Jul 2017 | A1 |
20170251988 | Weber et al. | Sep 2017 | A1 |
20170280978 | Yamamoto | Oct 2017 | A1 |
20170281049 | Yamamoto | Oct 2017 | A1 |
20170290631 | Lee et al. | Oct 2017 | A1 |
20170304015 | Tavallaei et al. | Oct 2017 | A1 |
20170325715 | Mehendale et al. | Nov 2017 | A1 |
20170333679 | Jiang | Nov 2017 | A1 |
20170340396 | Romo et al. | Nov 2017 | A1 |
20170365055 | Mintz et al. | Dec 2017 | A1 |
20170367782 | Schuh et al. | Dec 2017 | A1 |
20180025666 | Ho et al. | Jan 2018 | A1 |
20180055583 | Schuh et al. | Mar 2018 | A1 |
20180177383 | Noonan et al. | Jun 2018 | A1 |
20180177556 | Noonan et al. | Jun 2018 | A1 |
20180177561 | Mintz et al. | Jun 2018 | A1 |
Number | Date | Country |
---|---|---|
102013100605 | Jul 2014 | DE |
1 566 150 | Aug 2005 | EP |
2 392 435 | Dec 2011 | EP |
3 025 630 | Jun 2016 | EP |
WO 0156457 | Aug 2001 | WO |
WO 06122061 | Nov 2006 | WO |
WO 09120940 | Oct 2009 | WO |
WO 11132409 | Oct 2011 | WO |
Entry |
---|
Kukuk, Oct. 5, 2001, TBNA-protocols: Guiding TransBronchial Needle Aspirations Without a Computer in the Operating Room, MICCAI 2001, 2208:997-1006. |
Verdaasdonk et al., Jan. 23, 2012, Effect of microsecond pulse length and tip shape on explosive bubble formation of 2.78 μm Er,Cr;YSGG and 2.94 μm Er:YAG laser, Proceedings of SPIE, vol. 8221, 12. |