The disclosure herein is directed to systems and methods for the alignment and docking of robotic arm, and more particularly to computer assisted alignment and/or docking of a robotic arm with a target.
Before performing a surgical procedure, robotic arm(s) that support surgical instrument(s) may be “docked” to corresponding target(s) placed on a patient. The target may include a port such as a cannula or an access point such as a natural orifice. When the target is a port, the docking of a robotic arm to the port may include coupling or otherwise latching the robotic arm to the port. The docking process can occur before the start of any surgical procedure, or mid-procedure (e.g., occasionally, a surgeon may need to use different cannulas and re-dock one or more robotic arms). The docking process is typically performed manually and may involve a surgeon or clinician moving a robotic arm into alignment with a port to dock the robotic arm to the port. Once the docking process is completed, a surgical instrument can be inserted coaxially to the port and to gain access to an internal region of the patient.
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 robotic arm; a sensor configured to generate information indicative of a location of the robotic arm; a processor; and at least one computer-readable memory in communication with the processor and having stored thereon computer-executable instructions to cause the processor to: receive the information from the sensor, determine that the robotic arm is located at a first position in which a first axis associated with the robotic arm is not in alignment with a second axis associated with a port installed in a patient, and provide a command to move the robotic arm to a second position in which the first axis associated with the robotic arm is in alignment with the second axis.
In another aspect, there is provided a method of preparing a robotic system for surgery, comprising: moving a robotic arm from a first position to a second position based on information generated by a sensor, the information indicative of a location of the robotic arm, wherein in the first position a first axis associated with the robotic arm is not in alignment with a second axis of a port placed in a patient, and wherein in the second position the first axis associated with the robotic arm is in alignment with the second axis.
In yet 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: receive information from a sensor configured to generate information indicative of a location of a port, determine that a robotic arm is located at a first position in which a tool path axis associated with the robotic arm is not in alignment with an insertion axis of the port installed in a patient; and provide a command to move the robotic arm to a second position in which the tool path axis associated with the robotic arm is in alignment with the insertion axis.
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 endoscopic procedures, the system may be capable of performing bronchoscopy, ureteroscopy, gastroscopy, 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 independently 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 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.
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 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).
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 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.
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.
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.
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.
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.
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 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.
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 11. 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.
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.
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.
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 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
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.
The table base 46 serves a similar function as the cart base 15 in the cart 11 shown in
With continued reference to
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 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.
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 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.
The adjustable arm support 105 can provide several degrees of freedom, including lift, lateral translation, tilt, etc. In the illustrated embodiment of
The surgical robotics system 100 in
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.
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
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
The end effectors of the system's robotic arms may comprise (i) an instrument driver (alternatively referred to as “instrument drive mechanism,” “instrument device manipulator,” or “advanced device manipulator (ADM)”) 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.
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
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.
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.
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.
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.
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 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
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.
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.
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
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.
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.
As shown in
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
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.
As shown in
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, 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 (or image data) 92. The localization module 95 may process the vision data 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.
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.
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.
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.
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.
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 computer assisted alignment and/or docking of robotic arm(s) to a target of a patient. As previously discussed, prior to introducing a surgical instrument into a patient, a robotic arm may be aligned and/or docked with a target (e.g., a port which is installed or otherwise placed in the patient). After docking, the robotic arm and/or system may be configured to control the movement of a distal end of an instrument while maintaining a remote center of motion.
The robotic arm and/or surgical system can establish and maintain the position of the remote center of motion 120 for the instrument 130. Depending on the embodiment, the remote center of motion 120 can be maintained either mechanically or by software execute on one or more processors of the system. During a surgical procedure, the instrument 130 may be inserted through the patient's body wall to gain access to an internal region of the patient. The remote center of motion 120 may be defined at the intersection between the body wall and the instrument in order to prevent and/or reduce movement of the body wall during the procedure, thereby enabling the surgical procedure to safely take place. For example, if the location of the intersection between the instrument is not held substantially stationary during the procedure, the instrument may apply unnecessary force to the body wall, potentially tearing the body wall. Thus, it is desirable to maintain the remote center of motion 120 to prevent unnecessary forces from being applied to the body wall.
There may be a number of challenges associated with docking an ADM to a port installed or placed in the patient. For example, the surgical environment may include a plurality of other robotic arms, sterile drapes, and other surgical equipment, which may obscure the view of the robotic arm and/or port and limit the range of motion available for the docking procedure. Thus, manual docking of the robotic arm and/or ADM to or with the port may be a time-consuming and difficult procedure. The docking procedure can therefore be time-consuming and can require numerous adjustments and interaction with the robotic arm in a confined space. Due to the time-consuming nature of the docking procedure, surgeons may choose sub-optimal port locations that will accommodate larger workspaces to reduce the chance that a port location will need to be moved during the surgical procedure and require undocking and re-docking of the robotic arm.
Aspects of this disclosure relate to methods and systems that may automate at least a portion of the docking process. Certain aspects may provide advantages including automating at least a portion of the docking process and reducing the reliance on health care providers to manually dock robotic arms to ports.
A. Alignment and Docking Techniques
Aspects of this disclosure involve the use of one or more sensors to assist in alignment and docking of a robotic arm with a target of a patient. The docking procedure may involve moving the robotic arm to align a first axis associated with the robotic arm into alignment with a second axis associated with the target.
The steps of method 200 illustrated in
As is described in detail below, the sensor can be used to detect and identify a fiducial that is associated with the port or access point. As used herein, a fiducial may refer to a marking or object that can be detected by the sensor and used by the system to determine the relative spatial position between the fiducial and the sensor. For example, when the sensor is embodied as an image sensor, the fiducial may include a marking or other visual pattern detectable by the image sensor. In the EM sensor embodiments, the fiducial may include an EM emitter and/or reflector that radiates an EM signal detectable by the EM sensor. The processor may be configured to determine the orientation and position of the fiducial relative to the sensor based on a signal produced by the sensor. In certain embodiments, the fiducial can be positioned on the patient in a defined relative position with an access point in which the port is located.
Referring back to
At block 204, the processor determines that the robotic arm is located at a first position in which a first axis associated with the robotic arm is not in alignment with a second axis associated with a port installed in a patient. Here, the first axis may comprise a tool path axis along which a tool is configured to be inserted/retracted by the robotic arm, and the second axis may comprise an insertion axis of the port through which the tool can be inserted. At block 206, the processor provides a command to move the robotic arm to a second position in which the tool path axis associated with the robotic arm is in alignment with the insertion axis. Accordingly, the processor may be able to determine the motion of the robotic arm which will bring the robotic arm into alignment with the port. In certain embodiments, the system may include a user input (e.g., a button or switch) configured to control the alignment/docking process. For example, the system may receive a command from the user to automatically align and/or dock the robotic arm to the port by moving the robotic arm from the first position in which the tool path axis of the robotic arm is not in alignment with the insertion axis of the port to the second position in which the tool path axis is aligned with the insertion axis.
With the tool path axis aligned with the insertion axis, the processor may move the robotic arm towards the port along the insertion axis. The processor may bring a portion of the robotic arm (e.g., an ADM formed at the distal end of the robotic arm) within a threshold distance of the port to allow the ADM to be docked to the port. In certain embodiments, the final docking (e.g., coupling or latching) of the ADM to the port may be performed manually. In other embodiments, docking may be performed automatically under control of the processor and/or may involve automatically placing the ADM in close spatial proximity to the port without physically coupling the ADM to the port. The method ends at block 208.
With reference to
During set-up of the surgical environment, the robotic arm and the ADM 265 may be located at a defined distance from the port 235, and the ADM 265 may not be in alignment with the port 235. As an initial step of the alignment method, the user may manually position the ADM 265 into the first position such that the fiducial 240 is within the field of view 230 of the image sensor 225. In another embodiment, the movement of the ADM 265 into the first position may be performed automatically by the robotic system 209. Once the fiducial 240 is within the field of view 230 of the image sensor 225, the system 209 may be able to use the images received from the image sensor 225 to determine the relative position between the ADM 265 and the port 235.
Using the images received from the image sensor 225 as an input, a processor and/or controller of the robotic system 209′ may provide instructions to the robotic arm to move the ADM 265 from the first position to the second position illustrated in
After the tool path axis 220 is aligned with the insertion axis at the second position of
In certain embodiments, the processor may command the robotic arm to bring the ADM 265 within a threshold distance of the port 235 to allow the ADM 265 to be docked to the port 235. Once the ADM 265 is within a threshold distance of the port 235, the ADM 265 may be secured to the port 235 in an automated mode by the robotic system and/or manually by the user (or another person helping the user). In some embodiments, the distance between the ADM 265 and the port 235 may be determined based on the distance between the remote center of motion 220 and the intersection point 250. In related aspects, docking (e.g., coupling or latching) of the ADM 265 to the port 235 may, e.g., be performed manually. In addition, or in the alternative, the docking may be performed automatically under control of the processor and/or may involve placing the ADM 265 in close spatial proximity to (i.e., within a defined distance or area of) the port 235 without physically coupling the ADM 265 to the port 235. Once the ADM 265 is docked to the port 235, an instrument can inserted through the ADM 265 and the port 235 to gain access to an internal region of the patient.
In certain implementations, the ADM 265 may be part of an instrument-based insertion architecture, and may be connected to an instrument, such as, e.g., the instrument 150 illustrated in
The method described above in connection with
The method described in connection with
B. ADM and Image Sensor
For certain procedures, a sterile drape (not illustrated) may be coupled to the ADM 305 to provide a barrier between the ADM 305 and the patient. The sterile drape may cover at least a portion of the ADM including the image sensor 325. Since in some instances, the sterile drape may be opaque, the sterile drape may include a transparent region that overlaps with the image sensor 325 such that the image sensor 325 can view the port via the transparent region. Thus, the transparent region may be configured so that the field of view 330 is substantially unobstructed by the sterile drape.
C. Cannula and Fiducial
In certain implementations, the port can be embodied as a cannula or similar instrument placed into a body wall of the patient.
In some embodiments, the fiducial can be a mark or pattern that is formed on a portion of the cannula 535 or 635.
In view of the above, the processor can determine the angle between the tool path axis and the insertion axis based on the shape of the fiducial 1040 within a field of view of the image sensor. Similarly, the processor can also determine the distance between the image sensor and the fiducial based on the length of the major axis of the fiducial within the field of view of the image sensor. Thus, when the fiducial has the form of a circle or ring, the processor may be able to more easily determine the relative distance and orientation between the image sensor (and thus the ADM) and the port. However, the fiducial need not be in the form of a circle or ring, and can be any shape that is detectable by the image sensor.
D. Ports and Surgical Procedures
The alignment and docking procedures described herein may be applied to a variety of different surgical procedures, some of which may use different types of ports or may involve aligning the ADM to a natural orifice of the patient without the use of a port. In one embodiment, the port may include a patient introducer or sheath placed into a natural orifice of the patient. For example, the patient introducer may be configured to be installed in a mouth or nose of the patient, for example, for use during a bronchoscopy procedure. In another embodiment, a sheath can be configured to be secured to a ureteroscope coupled with the robotic arm. In yet another embodiment, the port can be configured to be placed in the patient's sinus for an otolaryngology (ENT) procedure. In other embodiments, the ADM may be aligned to the patient's sinus for an ENT procedure without the use of a port.
The alignment and docking procedure may also be applied to procedure using a feed roller configured to receive a scope, e.g., for a ureteroscopic procedure.
Implementations disclosed herein provide systems, methods and apparatus for alignment and docking of a robotic arm are provided.
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 alignment and docking functions 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.
This application is a continuation application of U.S. patent application Ser. No. 16/584,624, entitled “SYSTEMS AND METHODS FOR ROBOTIC ARM ALIGNMENT AND DOCKING,” filed Sep. 26, 2019, which claims the benefit of U.S. Provisional Application No. 62/783,089, entitled “SYSTEMS AND METHODS FOR ROBOTIC ARM ALIGNMENT AND DOCKING,” filed Dec. 20, 2018, both of which are incorporated by reference herein in their entireties.
Number | Name | Date | Kind |
---|---|---|---|
5199417 | Muller et al. | Apr 1993 | A |
5876325 | Mizuno et al. | Mar 1999 | A |
8021326 | Moll et al. | Sep 2011 | B2 |
8652030 | Matsuura et al. | Feb 2014 | B2 |
9108318 | Diolaiti | Aug 2015 | B2 |
9504604 | Alvarez | Nov 2016 | B2 |
9561083 | Yu et al. | Feb 2017 | B2 |
9622827 | Yu et al. | Apr 2017 | B2 |
9636184 | Lee et al. | May 2017 | B2 |
9668768 | Piron et al. | Jun 2017 | B2 |
9713509 | Schuh et al. | Jul 2017 | B2 |
9717563 | Tognaccini | Aug 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 |
9782229 | Crawford | Oct 2017 | B2 |
9788910 | Schuh | Oct 2017 | B2 |
9827054 | Richmond | Nov 2017 | B2 |
9844412 | Bogusky et al. | Dec 2017 | B2 |
9867635 | Alvarez et al. | Jan 2018 | B2 |
9872737 | Nixon | Jan 2018 | B2 |
9918681 | Wallace et al. | Mar 2018 | B2 |
9931025 | Graetzel et al. | Apr 2018 | B1 |
9949749 | Noonan et al. | Apr 2018 | B2 |
9949799 | Hingwe | Apr 2018 | B2 |
9955986 | Shah | May 2018 | B2 |
9962228 | Schuh et al. | May 2018 | B2 |
9980785 | Schuh | May 2018 | B2 |
9993313 | Schuh et al. | Jun 2018 | B2 |
10016900 | Meyer et al. | Jul 2018 | B1 |
10022192 | Ummalaneni | Jul 2018 | B1 |
10080576 | Romo et al. | Sep 2018 | B2 |
10136959 | Mintz et al. | Nov 2018 | B2 |
10145747 | Lin et al. | Dec 2018 | B1 |
10149720 | Romo | Dec 2018 | B2 |
10154822 | Henderson | Dec 2018 | B2 |
10159532 | Ummalaneni et al. | Dec 2018 | B1 |
10159533 | Moll et al. | Dec 2018 | B2 |
10169875 | Mintz et al. | Jan 2019 | B2 |
10172687 | Garbus | Jan 2019 | B2 |
10219874 | Yu et al. | Mar 2019 | B2 |
10231793 | Romo | Mar 2019 | B2 |
10231867 | Alvarez et al. | Mar 2019 | B2 |
10244926 | Noonan et al. | Apr 2019 | B2 |
10285574 | Landey et al. | May 2019 | B2 |
10299870 | Connolly et al. | May 2019 | B2 |
10314463 | Agrawal et al. | Jun 2019 | B2 |
10383765 | Alvarez et al. | Aug 2019 | B2 |
10398518 | Yu et al. | Sep 2019 | B2 |
10405939 | Romo et al. | Sep 2019 | B2 |
10405940 | Romo | Sep 2019 | B2 |
10426559 | Graetzel et al. | Oct 2019 | B2 |
10426661 | Kintz | Oct 2019 | B2 |
10434660 | Meyer | Oct 2019 | B2 |
10464209 | Ho et al. | Nov 2019 | B2 |
10470830 | Hill | Nov 2019 | B2 |
10482599 | Mintz et al. | Nov 2019 | B2 |
10493241 | Jiang | Dec 2019 | B2 |
10500001 | Yu et al. | Dec 2019 | B2 |
10517692 | Eyre et al. | Dec 2019 | B2 |
10524866 | Srinivasan | Jan 2020 | B2 |
10539478 | Lin | Jan 2020 | B2 |
10543048 | Noonan et al. | Jan 2020 | B2 |
10555778 | Ummalaneni et al. | Feb 2020 | B2 |
10639114 | Schuh | May 2020 | B2 |
10646291 | Turner | May 2020 | B2 |
10765487 | Ho | Sep 2020 | B2 |
11052930 | Schaller | Jul 2021 | B2 |
11254009 | Fredrickson | Feb 2022 | B2 |
11324558 | Graetzel | May 2022 | B2 |
20020082612 | Moll et al. | Jun 2002 | A1 |
20030181809 | Hall et al. | Sep 2003 | A1 |
20040176751 | Weitzner et al. | Sep 2004 | A1 |
20060058617 | Sano et al. | Mar 2006 | A1 |
20060178556 | Hasser et al. | Aug 2006 | A1 |
20080147089 | Loh | Jun 2008 | A1 |
20090005768 | Sharareh | Jan 2009 | A1 |
20090048611 | Funda | Feb 2009 | A1 |
20090088774 | Swarup | Apr 2009 | A1 |
20090326318 | Tognaccini | Dec 2009 | A1 |
20100100045 | Pravongviengkham et al. | Apr 2010 | A1 |
20100234857 | Itkowitz | Sep 2010 | A1 |
20110277775 | Holop et al. | Nov 2011 | A1 |
20120283747 | Popovic | Nov 2012 | A1 |
20120302869 | Koyrakh | Nov 2012 | A1 |
20140051049 | Jarc | Feb 2014 | A1 |
20140142591 | Alvarez et al. | May 2014 | A1 |
20140243801 | Fanelli et al. | Aug 2014 | A1 |
20140357984 | Wallace et al. | Dec 2014 | A1 |
20140364870 | Alvarez et al. | Dec 2014 | A1 |
20150025549 | Kilroy et al. | Jan 2015 | A1 |
20150045675 | Chemomorsky | Feb 2015 | A1 |
20150088161 | Hata | Mar 2015 | A1 |
20150223832 | Swaney | Aug 2015 | A1 |
20150297299 | Yeung | Oct 2015 | A1 |
20150305650 | Hunter | Oct 2015 | A1 |
20160001038 | Romo et al. | Jan 2016 | A1 |
20160270865 | Landey et al. | Sep 2016 | A1 |
20160287279 | Bovay et al. | Oct 2016 | A1 |
20170007337 | Dan | Jan 2017 | A1 |
20170071456 | Ratnakar | Mar 2017 | A1 |
20170095299 | Hendrick | Apr 2017 | A1 |
20170119481 | Romo et al. | May 2017 | A1 |
20170135710 | Hasegawa et al. | May 2017 | A1 |
20170135833 | Syed | May 2017 | A1 |
20170143442 | Tesar | May 2017 | A1 |
20170165011 | Bovay et al. | Jun 2017 | A1 |
20170172674 | Hanuschik | Jun 2017 | A1 |
20170189118 | Chopra | Jul 2017 | A1 |
20170189131 | Weir | Jul 2017 | A1 |
20170202627 | Sramek et al. | Jul 2017 | A1 |
20170209073 | Sramek et al. | Jul 2017 | A1 |
20170290631 | Lee et al. | Oct 2017 | A1 |
20170340396 | Romo et al. | Nov 2017 | A1 |
20170367782 | Schuh et al. | Dec 2017 | A1 |
20180025666 | Ho et al. | Jan 2018 | A1 |
20180098817 | Nichogi et al. | Apr 2018 | A1 |
20180214011 | Graetzel et al. | Aug 2018 | A1 |
20180221038 | Noonan et al. | Aug 2018 | A1 |
20180221039 | Shah | Aug 2018 | A1 |
20180228559 | Brierton | Aug 2018 | A1 |
20180250083 | Schuh et al. | Sep 2018 | A1 |
20180271616 | Schuh et al. | Sep 2018 | A1 |
20180279852 | Rafii-Tani et al. | Oct 2018 | A1 |
20180280660 | Landey et al. | Oct 2018 | A1 |
20180289431 | Draper et al. | Oct 2018 | A1 |
20180325499 | Landey et al. | Nov 2018 | A1 |
20180333044 | Jenkins | Nov 2018 | A1 |
20180338799 | Hladio et al. | Nov 2018 | A1 |
20180360435 | Romo | Dec 2018 | A1 |
20180368920 | Ummalaneni | Dec 2018 | A1 |
20190000559 | Berman et al. | Jan 2019 | A1 |
20190000560 | Berman et al. | Jan 2019 | A1 |
20190000576 | Mintz et al. | Jan 2019 | A1 |
20190083183 | Moll et al. | Mar 2019 | A1 |
20190110839 | Rafii-Tari et al. | Apr 2019 | A1 |
20190110843 | Ummalaneni et al. | Apr 2019 | A1 |
20190151148 | Alvarez et al. | Apr 2019 | A1 |
20190167366 | Ummalaneni | Jun 2019 | A1 |
20190175009 | Mintz | Jun 2019 | A1 |
20190175062 | Rafii-Tani et al. | Jun 2019 | A1 |
20190175799 | Hsu | Jun 2019 | A1 |
20190183585 | Rafii-Tari et al. | Jun 2019 | A1 |
20190183587 | Rafii-Tani et al. | Jun 2019 | A1 |
20190200981 | Harris | Jul 2019 | A1 |
20190201111 | Shelton, IV | Jul 2019 | A1 |
20190201136 | Shelton, IV | Jul 2019 | A1 |
20190206565 | Shelton, IV | Jul 2019 | A1 |
20190216548 | Ummalaneni | Jul 2019 | A1 |
20190216576 | Eyre | Jul 2019 | A1 |
20190223974 | Romo | Jul 2019 | A1 |
20190228525 | Mintz et al. | Jul 2019 | A1 |
20190246882 | Graetzel et al. | Aug 2019 | A1 |
20190262086 | Connolly et al. | Aug 2019 | A1 |
20190269468 | Hsu et al. | Sep 2019 | A1 |
20190274764 | Romo | Sep 2019 | A1 |
20190290109 | Agrawal et al. | Sep 2019 | A1 |
20190298160 | Ummalaneni et al. | Oct 2019 | A1 |
20190298460 | Al-Jadda | Oct 2019 | A1 |
20190298465 | Chin | Oct 2019 | A1 |
20190328213 | Landey et al. | Oct 2019 | A1 |
20190336238 | Yu | Nov 2019 | A1 |
20190365201 | Noonan et al. | Dec 2019 | A1 |
20190365209 | Ye et al. | Dec 2019 | A1 |
20190365479 | Rafii-Tari | Dec 2019 | A1 |
20190365486 | Srinivasan et al. | Dec 2019 | A1 |
20190374297 | Wallace et al. | Dec 2019 | A1 |
20190375383 | Alvarez | Dec 2019 | A1 |
20190380787 | Ye | Dec 2019 | A1 |
20190380797 | Yu | Dec 2019 | A1 |
20200000530 | DeFonzo | Jan 2020 | A1 |
20200000533 | Schuh | Jan 2020 | A1 |
20200022767 | Hill | Jan 2020 | A1 |
20200038123 | Graetzel | Feb 2020 | A1 |
20200039086 | Meyer | Feb 2020 | A1 |
20200046434 | Graetzel | Feb 2020 | A1 |
20200054408 | Schuh et al. | Feb 2020 | A1 |
20200060516 | Baez | Feb 2020 | A1 |
20200085516 | DeFonzo | Mar 2020 | A1 |
20200093549 | Chin | Mar 2020 | A1 |
20200093554 | Schuh | Mar 2020 | A1 |
20200100845 | Julian | Apr 2020 | A1 |
20200100855 | Leparmentier | Apr 2020 | A1 |
20200101264 | Jiang | Apr 2020 | A1 |
20200107894 | Wallace | Apr 2020 | A1 |
20200121502 | Kintz | Apr 2020 | A1 |
20200146769 | Eyre | May 2020 | A1 |
20200170720 | Ummalaneni | Jun 2020 | A1 |
20200171660 | Ho | Jun 2020 | A1 |
20200188043 | Yu | Jun 2020 | A1 |
20200197112 | Chin | Jun 2020 | A1 |
20200198147 | Fredrickson | Jun 2020 | A1 |
20200206472 | Ma | Jul 2020 | A1 |
20200217733 | Lin | Jul 2020 | A1 |
20200222134 | Schuh | Jul 2020 | A1 |
20200237458 | DeFonzo | Jul 2020 | A1 |
20200261172 | Romo | Aug 2020 | A1 |
20200268459 | Noonan et al. | Aug 2020 | A1 |
20200268460 | Tse | Aug 2020 | A1 |
20200281787 | Ruiz | Sep 2020 | A1 |
20200289205 | Scheib | Sep 2020 | A1 |
20200289220 | Denlinger | Sep 2020 | A1 |
20200289221 | Denlinger | Sep 2020 | A1 |
20200405419 | Mao | Dec 2020 | A1 |
20210030501 | Eyre | Feb 2021 | A1 |
20210212776 | Schmitt | Jul 2021 | A1 |
Number | Date | Country |
---|---|---|
0 347 098 | Feb 1996 | EP |
WO 2015142933 | Sep 2015 | WO |
WO 17048194 | Mar 2017 | WO |
WO 2018187069 | Oct 2018 | WO |
Entry |
---|
Ishak et al., Design and Implementation of Robot Assisted Surgery Based on Internet of Things (IoT), 2017, IEEE, p. 65-70 (Year: 2017). |
Kruse et al., A sensor-based dual-arm tele-robotic manipulation platform, 2013, IEEE, p. 350-355 (Year: 2013). |
Jhang et al., Multi-sensor based glove control of an industrial mobile robot arm, 2017, IEEE, p. 1-6 (Year: 2017). |
Kofman et al., Teleoperation of a robot manipulator using a vision-based human-robot interface, 2005, IEEE, p. 1206-1219 (Year: 2005). |
Rahimi et al., An Industrial Robotics Application with Cloud Computing and High-Speed Networking, 2017, IEEE, p. 44-51 (Year: 2017). |
Zhang et al., A teleoperation system fora humanoid robot with multiple information feedback and operational modes, 2005, IEEE, pg. (Year: 2005). |
Zhang et al., A two-arm situated artificial communicator for human-robot cooperative assembly, 2003, IEEE, p. 651-658 (Year: 2003). |
Carignan, Controlling robots on-orbit, 2001, IEEE, p. 314-319 (Year: 2001). |
Darwiche, 2015, Operative technique and early experience for robotic assisted laparoscopic nephroureterectomy (RALNU) using da Vinci XI, SpringerPlus, 4:298. |
Sasaki, 2017, Laparoscopic hemicolectomy for a patient with situs inversus totalis: a case report, Int. J. Surg. Case Rep. 41:93-96. |
International search report and written opinion dated Dec. 13, 2019 for PCT/US2019/53122. |
Number | Date | Country | |
---|---|---|---|
20220241981 A1 | Aug 2022 | US |
Number | Date | Country | |
---|---|---|---|
62783089 | Dec 2018 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16584624 | Sep 2019 | US |
Child | 17676117 | US |