Collision Avoidance in Surgical Robots Based on Non-Contact Information

Abstract

The robotic system may be capable of collision detection and collision avoidance. The medical robotic system may include a first kinematic chain and one or more sensors positioned to detect one or more objects detected within a vicinity of the first kinematic chain. The medical robotic system may be configured to cause an adjustment of a configuration of the first kinematic chain from a first configuration to a second configuration based on constraints determined from the one or more objects detected by the one or more sensors within a vicinity of the first kinematic chain.

Description

[Technical Field]

[0001] The systems and methods disclosed herein are directed to medical robotic systems having robotic arms, and more particularly to medical robotic systems that can automatically adjust the robotic arms to avoid collisions. [Background technology]

[0002] During medical procedures using medical robotic systems, robotic arms may come into contact with each other (e.g., arm-to-arm collisions) and the environment (e.g., the patient, bedside staff, and accessories). While collisions between robotic arms can be predicted and avoided based on known arm configurations, predicting and completely avoiding collisions with other objects has been difficult, especially for objects whose positions change over time. Regardless of the type of collision, collisions can be problematic for medical procedures, and therefore, a need exists for a medical robotic system that can reduce or eliminate the occurrence of collisions with robotic arms. Summary of the Invention [Means for solving the problem]

[0003] Disclosed herein is a medical robotic system that uses one or more sensors on a kinematic component (e.g., a robotic arm) to detect forces (e.g., other parameters of a collision). The detected forces or other parameters of the collision are used to adjust the configuration (e.g., position) of the kinematic component, which in turn reduces future occurrences of collisions with the kinematic component.

[0004] According to some embodiments, a medical robotic system includes a first kinematic chain, one or more sensors positioned to detect one or more parameters of contact with one or more portions of the first kinematic chain, one or more processors in communication with the one or more sensors, and a memory storing instructions that, when executed by the one or more processors, cause an adjustment of a configuration of the first kinematic chain from a first configuration to a second configuration based on constraints determined from the one or more parameters of contact with the first kinematic chain detected by the one or more sensors.

[0005] According to some embodiments, a method is performed by an electronic device in communication with a medical robotic system including a first kinematic chain and one or more sensors positioned to detect one or more parameters of contact with the first kinematic chain. The method includes receiving the one or more parameters of contact with the first kinematic chain detected by the one or more sensors, determining a constraint associated with the first kinematic chain based on the one or more parameters of contact with the first kinematic chain, and causing an adjustment of a configuration of the first kinematic chain from a first configuration to a second configuration based on the constraint.

[0006] According to some embodiments, an electronic device includes one or more processors and a memory storing instructions that, when executed by the one or more processors, cause the one or more processors to receive one or more parameters of contact with a first kinematic chain of a medical robotic system detected by one or more sensors; determine a constraint associated with the first kinematic chain based on the one or more parameters of the contact with the first kinematic chain; and adjust a configuration of the first kinematic chain from a first configuration to a second configuration based on the constraint.

[0007] According to some embodiments, a computer-readable storage medium stores instructions for execution by one or more processors of an electronic device, the stored instructions including instructions for receiving one or more parameters of contact with a first kinematic chain of a medical robotic system detected by one or more sensors, determining a constraint associated with the first kinematic chain based on the one or more parameters of the contact with the first kinematic chain, and causing an adjustment of a configuration of the first kinematic chain from a first configuration to a second configuration based on the constraint.

[0008] According to some embodiments, a medical robotic system includes a first robotic arm, one or more sensors positioned to detect the presence of objects adjacent to the first robotic arm, one or more processors in communication with the one or more sensors, and a memory. The memory stores instructions that, when executed by the one or more processors, cause the one or more processors to: receive first sensor information from the one or more sensors corresponding to one or more positional locations of one or more objects within a vicinity of the first robotic arm, generate or update an object map based on the first sensor information, the object map characterizing a spatial relationship of the objects adjacent to the first robotic arm, and adjust a configuration of the first robotic arm from a first configuration to a second configuration based on the object map.

[0009] According to some embodiments, a medical robotic system includes a first robotic arm, one or more sensors positioned to detect the presence of a dynamic object within a vicinity of the first robotic arm, one or more processors in communication with the one or more sensors, and a memory. The memory stores instructions that, when executed by the one or more processors, cause the one or more processors to: receive sensor information from the one or more sensors corresponding to a position of a dynamic object within a vicinity of the first robotic arm, generate or update an object map based on the sensor information, the object map characterizing spatial relationships of objects within a vicinity of the first robotic arm, and adjust a configuration of the first robotic arm from a first configuration to a second configuration based on the object map.

[0010] According to some embodiments, a method is performed by an electronic device in communication with a medical robotic system including a first robotic arm and one or more sensors positioned to detect the presence of objects within a vicinity of the first robotic arm. The method includes receiving sensor information from the one or more sensors corresponding to positions of one or more objects present within a vicinity of the first robotic arm, generating or updating an object map based on the sensor information, the object map characterizing spatial relationships of objects within a vicinity of the first robotic arm, and adjusting a configuration of the first robotic arm from a first configuration to a second configuration based on the object map.

[0011] According to some embodiments, an electronic device includes one or more processors and a memory. The memory stores instructions that, when executed by the one or more processors, cause the one or more processors to receive sensor information from one or more sensors corresponding to positions of one or more objects within a vicinity of a first robotic arm of a medical robotic system, generate or update an object map based on the sensor information, the object map characterizing spatial relationships of objects within a vicinity of the first robotic arm, and adjust a configuration of the first robotic arm from a first configuration to a second configuration based on the object map.

[0012] According to some embodiments, a computer-readable storage medium stores instructions for execution by one or more processors of an electronic device, the stored instructions including instructions for receiving sensor information corresponding to positions of one or more objects adjacent to a first robotic arm of a medical robotic system, generating or updating an object map based on the sensor information, the object map characterizing a spatial relationship of the objects adjacent to the first robotic arm, and causing an adjustment of a configuration of the first robotic arm from a first configuration to a second configuration based on the object map. [Brief explanation of the drawings]

[0013] The disclosed aspects are hereinafter described in connection with the accompanying drawings, which illustrate, but are not limited to, the disclosed aspects, and in which like designations refer to like elements. [Figure 1] 1 illustrates an embodiment of a cart-based robotic system positioned for a diagnostic and / or therapeutic bronchoscopy procedure. [Figure 2] 2 illustrates a further aspect of the robotic system of FIG. 1. [Figure 3] 2 illustrates the embodiment of the robotic system of FIG. 1 positioned for ureteroscopy. [Figure 4] 2 illustrates the embodiment of the robotic system of FIG. 1 positioned for a vascular procedure. [Figure 5] 1 illustrates an embodiment of a table-based robotic system positioned for a bronchoscopy procedure. [Figure 6] 6 provides an alternative view of the robotic system of FIG. 5. [Figure 7] 1 illustrates an exemplary system configured to accommodate a robotic arm. [Figure 8] 1 illustrates an embodiment of a table-based robotic system configured for a ureteroscopy procedure. [Figure 9] 1 illustrates an embodiment of a table-based robotic system configured for laparoscopic procedures. [Figure 10] 10 illustrates an embodiment of the table-based robotic system of FIGS. 5-9 with pitch or tilt adjustment. [Figure 11] 5-10 provide detailed illustrations of the interface between the table and column of the table-based robotic system. [Figure 12] 1 illustrates an alternative embodiment of a table-based robotic system. [Figure 13] FIG. 13 shows an end view of the table-based robotic system of FIG. [Figure 14] FIG. 1 shows an end view of a table-based robotic system with a robotic arm attached. [Figure 15] 1 illustrates an exemplary instrument driver. [Figure 16] 1 illustrates an exemplary medical instrument having a pair of instrument drivers. [Figure 17] 10 shows an alternative design of the instrument driver and instrument, where the axis of the drive unit is parallel to the axis of the elongated shaft of the instrument. [Figure 18] 1 illustrates an instrument having an instrument-based insertion architecture. [Figure 19] 1 illustrates an exemplary controller. [Figure 20]FIG. 10 illustrates a block diagram showing a localization system that estimates the position of one or more elements of the robotic system of FIGS. 1-10, such as the position of the instrument of FIGS. 16-18, according to an exemplary embodiment. [Figure 21] 1 illustrates an exemplary robotic arm according to some embodiments. [Figure 22A] 1 illustrates an exemplary robotic link that can form a portion of a robotic arm, according to some embodiments. [Figure 22B] 1 illustrates an exemplary robotic link that can form a portion of a robotic arm, according to some embodiments. [Figure 23] 1 illustrates an exemplary link including a rigid shell and configured to detect contact with an external object, according to some embodiments. [Figure 24] 24 illustrates an example of a force-sensing sensor that may be used in the link of FIG. 23, according to some embodiments. [Figure 25A] 1 illustrates a diagram of a link in which multiple sensors are included in the link, according to some embodiments. [Figure 25B] 1 illustrates a diagram of a link in which multiple sensors are included in the link, according to some embodiments. [Figure 25C] 1 illustrates a diagram of a link in which multiple sensors are included in the link, according to some embodiments. [Figure 25D] 1 illustrates a diagram of a link in which multiple sensors are included in the link, according to some embodiments. [Figure 26] 1 illustrates an example of a robotic system including an adjustable arm support, according to some embodiments. [Figure 27] 1 illustrates schematically how one or more degrees-of-freedom (DoF) can be shared between a robot arm, an adjustable arm support, and a setup joint. [Figure 28] FIG. 10 is a flow diagram illustrating a method for adjusting one or more kinematic chains based on contact information, according to some embodiments. [Figure 29A]29 illustrates the configuration of the robot arm during the operation shown in the flow diagram of FIG. 28. [Figure 29B] 29 illustrates the configuration of the robot arm during the operation shown in the flow diagram of FIG. 28. [Figure 29C] 29 illustrates the configuration of the robot arm during the operation shown in the flow diagram of FIG. 28. [Figure 29D] 29 illustrates the configuration of the robot arm during the operation shown in the flow diagram of FIG. 28. [Figure 29E] 29 illustrates the configuration of the robot arm during the operation shown in the flow diagram of FIG. 28. [Figure 29F] 29 illustrates the configuration of the robot arm during the operation shown in the flow diagram of FIG. 28. [Figure 30] FIG. 10 is a flow diagram illustrating a method for adjusting the configuration of a kinematic chain based on contact information, according to some embodiments. [Figure 31] 1 illustrates a sensor mounted to detect nearby objects, according to some embodiments. [Figure 32] 1 shows an example of a robotic arm with multiple sensors for gathering information about a dynamic environment. [Figure 33] 1 illustrates an exemplary representation of a human with a corresponding map based on information detected by one or more sensors, according to some embodiments. [Figure 34] FIG. 1 is a flow diagram illustrating a method for adjusting one or more kinematic chains based on detected object information, according to some embodiments. [Figure 35A] 1 illustrates a configuration of a robotic arm and corresponding map, according to some embodiments. [Figure 35B] 1 illustrates a configuration of a robotic arm and corresponding map, according to some embodiments. [Figure 35C] 1 illustrates a configuration of a robotic arm and corresponding map, according to some embodiments. [Figure 35D] 1 illustrates a configuration of a robotic arm and corresponding map, according to some embodiments. [Figure 35E]1 illustrates a configuration of a robotic arm and corresponding map, according to some embodiments. [Figure 35F] 1 illustrates a configuration of a robotic arm and corresponding map, according to some embodiments. [Figure 35G] 1 illustrates a configuration of a robotic arm and corresponding map, according to some embodiments. [Figure 36A] FIG. 1 is a schematic diagram illustrating a buffer zone, according to some embodiments. [Figure 36B] FIG. 1 is a schematic diagram illustrating a buffer zone, according to some embodiments. [Figure 37] FIG. 1 is a flow diagram illustrating a method for adjusting the configuration of a robotic arm based on sensor information, according to some embodiments. [Figure 38] FIG. 1 is a schematic diagram illustrating electronic components of a medical robotic system, according to some embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0014] 1.Overview Aspects of the present disclosure may be integrated into robotic-enabled medical systems capable of performing a variety of medical procedures, including both minimally invasive procedures such as laparoscopic procedures, and non-invasive procedures such as endoscopic procedures, among which the system may perform bronchoscopy, ureteroscopy, gastroscopy, etc.

[0015] In addition to performing a wide range of procedures, the system can provide additional benefits such as enhanced imaging and guidance to assist the physician. Additionally, the system can provide the physician with the ability to perform procedures from an ergonomic position without requiring awkward arm and motor movements. Still further, the system can provide the physician with the ability to perform procedures with improved ease of use, such that one or more of the system's instruments can be controlled by a single user.

[0016] Various embodiments are described below in conjunction with the drawings for purposes of explanation. It should be understood that many other implementations of the disclosed concepts are possible and that various advantages may be achieved in the disclosed implementations. Headings are included herein for reference and to aid in locating the various sections. These headings are not intended to limit the scope of the concepts described therein. Such concepts may have applicability throughout the entire specification.

[0017] A. Robot System - Cart Robot-enabled medical systems can be configured in various ways depending on the particular procedure. FIG. 1 illustrates an embodiment of a cart-based robot-enabled system 10 arranged for a diagnostic and / or therapeutic bronchoscopy procedure. During a bronchoscopy procedure, the system 10 can include a cart 11 with one or more robotic arms 12 for delivering a medical instrument, such as a steerable endoscope 13, which may be a procedural bronchoscope for bronchoscopy, to a natural orifice access point (i.e., the mouth of a patient positioned on a table in this example) for delivering diagnostic and / or therapeutic tools. As shown, the cart 11 can be positioned adjacent to the patient's upper torso to provide access to the access point. Similarly, the robotic arms 12 can be actuated to position a bronchoscope relative to the access point. The arrangement of FIG. 1 can also be utilized when performing gastrointestinal (GI) procedures using a gastroscope, a specialized endoscope for GI procedures. FIG. 2 illustrates an exemplary embodiment of the cart in more detail.

[0018] With continued reference to FIG. 1 , once the cart 11 is properly positioned, the robotic arm 12 can insert the steerable endoscope 13 into the patient robotically, manually, or a combination thereof. As shown, the steerable endoscope 13 may include at least two telescoping components, such as an inner leader section and an outer sheath section, each coupled to a separate instrument driver from a set of instrument drivers 28, with each instrument driver coupled to the distal end of a respective robotic arm. This linear arrangement of the instrument drivers 28, which facilitates coaxial alignment of the leader section with the sheath section, forms a “virtual rail” 29 that can be repositioned in space by manipulating one or more robotic arms 12 to different angles and / or positions. The virtual rails described herein are illustrated in the figures using dashed lines, which therefore do not depict the physical structure of either system. Translation of the instrument driver 28 along the virtual rail 29 either nests the inner leader section relative to the outer sheath section or advances or retracts the endoscope 13 from the patient. The angle of the virtual rail 29 may be adjusted, translated, and pivoted based on clinical application or physician preference. For example, in bronchoscopy, the angle and position of the virtual rail 29 as shown represents a compromise that provides the physician access to the endoscope 13 while minimizing friction from bending the endoscope 13 into the patient's mouth.

[0019] After insertion, the endoscope 13 may be directed downstream of the patient's trachea and lungs using precise commands from the robotic system until the targeted destination or surgical site is reached. To facilitate navigation through the patient's pulmonary network and / or to reach the desired target, the endoscope 13 may be manipulated to telescope the inner leader section from the outer sheath section for enhanced articulation and a larger bend radius. The use of a separate instrument driver 28 also allows the leader and sheath sections to be driven independently of one another.

[0020] For example, the endoscope 13 may be directed to deliver a biopsy needle to a target, such as a lesion or nodule within a patient's lung. The needle may be deployed down a working channel spanning the length of the endoscope to obtain a tissue sample that is analyzed by a pathologist. Depending on the results of the pathology, additional tools may be deployed downstream of the endoscope's working channel for additional biopsies. After identifying the nodule as malignant, the endoscope 13 may endoscopically deliver a tool to remove the potentially cancerous tissue. In some cases, diagnostic and therapeutic treatments can be provided in separate procedures. In these situations, the endoscope 13 may also be used to deliver fiducials to "mark" the location of the target nodule. In other examples, diagnostic and therapeutic treatments may be delivered during the same procedure.

[0021] The system 10 may also include a movable tower 30 that may be connected to the cart 11 via a support cable and provide support for control, electronics, fluidics, optics, sensors, and / or power to the cart 11. Locating such functionality within the tower 30 allows for a smaller form factor cart 11 that can be more easily adjusted and / or repositioned by the operating physician and their staff. Additionally, the division of functionality between the cart / table and the support tower 30 reduces clutter in the operating room and promotes improved clinical workflow. The cart 11 may be positioned in close proximity to the patient, while the tower 30 may be housed in a remote location so as not to get in the way during the procedure.

[0022] To support the robotic system described above, tower 30 may include computer-based control system components that store computer program instructions in a non-transitory computer-readable storage medium, such as a persistent magnetic storage drive, a solid-state drive, or the like. Execution of these instructions, whether execution occurs in tower 30 or cart 11, may control the entire system or subsystems thereof. For example, when executed by a processor in a computer system, the instructions may cause components of the robotic system to actuate associated carriages and arm mounts, operate a robotic arm, and control a medical instrument. For example, in response to receiving control signals, motors in the joints of a robotic arm may position the arm in a particular pose.

[0023] Tower 30 may also include pumps, flow meters, valve controls, and / or fluid access to provide controlled irrigation and aspiration functions to a system that may be deployed through 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 endoscope 13 via separate cables.

[0024] The tower 30 may include voltage and surge protection designed to provide filtered and protected power to the cart 11, thereby avoiding the need to place power transformers and other auxiliary power components within the cart 11, making the cart 11 smaller and more mobile.

[0025] The tower 30 may also include support equipment for sensors deployed throughout the robotic system 10. For example, the tower 30 may include optoelectronic equipment for detecting, receiving, and processing data received from optical sensors or cameras throughout the robotic system 10. In combination with a control system, such optoelectronic equipment may be used to generate real-time images for display in any number of consoles located throughout the system, including within the tower 30. Similarly, the tower 30 may also include electronic subsystems for receiving and processing signals from deployed electromagnetic (EM) sensors. The tower 30 may also be used to house and position EM field generators for detection by EM sensors in or on the medical instrument.

[0026] The tower 30 may also include a console 31 in addition to other consoles available to the rest of the system, such as a console mounted on top of a cart. The console 31 may include a user interface for the physician operator and a display screen, such as a touchscreen. The consoles in the system 10 are generally designed to provide both pre-operative and real-time information for the procedure, such as robotic control and navigation and localization information for the endoscope 13. If the console 31 is not the only console available to the physician, the console 31 may be used by a second operator, such as a nurse, to monitor patient health or vitals and system operation, as well as provide procedure-specific data, such as navigation and localization information. In other embodiments, the console 31 is housed in a separate body from the tower 30.

[0027] The tower 30 may be coupled to the cart 11 and the endoscope 13 via one or more cables or connections (not shown). In some embodiments, support functions from the tower 30 may be provided to the cart 11 through a single cable, thereby simplifying and reducing clutter in the operating room. In other embodiments, certain functions may be coupled with separate wiring and connections. For example, power may be provided to the cart through a single power cable, while support for control, optics, fluidics, and / or navigation may be provided through separate cables.

[0028] FIG. 2 provides a detailed view of an embodiment of a cart from the cart-based, robot-enabled system shown in FIG. 1. The cart 11 generally includes an elongated support structure 14 (often referred to as a "column"), a cart base 15, and a console 16 at the top of the column 14. The column 14 may include one or more carriages, such as a carriage 17 (alternatively, an "arm support"), for supporting the deployment of one or more robotic arms 12 (three are shown in FIG. 2). The carriage 17 may include an individually configurable arm mount that rotates along a vertical axis to adjust the base of the robotic arm 12 for better positioning relative to the patient. The carriage 17 also includes a carriage interface 19 that allows the carriage 17 to translate vertically along the column 14.

[0029] Carriage interface 19 connects to column 14 through slots, such as slots 20 positioned on either side of column 14 to guide the vertical translation of carriage 17. Slots 20 include vertical translation interfaces for positioning and holding the carriage at various vertical heights relative to cart base 15. The vertical translation of carriage 17 allows cart 11 to adjust the reach of robotic arm 12 to meet various table heights, patient sizes, and physician preferences. Similarly, an individually configurable arm mount on carriage 17 allows robotic arm base 21 of robotic arm 12 to be angled in various configurations.

[0030] In some embodiments, slot 20 may be supplemented with a slot cover that is flush and parallel with the slot surface to prevent dirt and fluids from entering the interior chamber of column 14 and the vertical translation interface as carriage 17 translates vertically. The slot cover may be deployed via a pair of spring spools positioned near the vertical top and bottom of slot 20. The cover is coiled within the spools until deployed, extending and retracting from its coiled state as carriage 17 translates vertically up and down. The spring load of the spools provides a force to retract the cover into the spools as carriage 17 translates toward them, while also maintaining a seal when carriage 17 translates away from them. The cover may be connected to carriage 17 using, for example, a bracket within carriage interface 19 to ensure the cover extends and retracts properly as carriage 17 translates.

[0031] Column 14 may include internal mechanisms such as gears and motors designed to use a vertically aligned leadscrew to mechanically translate carriage 17 in response to control signals generated in response to user input, such as input from console 16.

[0032] The robotic arm 12 may generally include a robotic arm base 21 and end effectors 22 separated by a series of links 23 connected by a series of joints 24, each including an independent actuator, each including an independently controllable motor. Each independently controllable joint represents an independent degree of freedom available to the robotic arm. Each of the arms 12 has seven joints, thus providing seven degrees of freedom. A large number of joints results in a large number of degrees of freedom, allowing for "redundant" degrees of freedom. The redundant degrees of freedom allow the robotic arms 12 to position their respective end effectors 22 at specific positions, orientations, and trajectories in space using different joint positions and joint angles. This allows the system to position and orient medical instruments from a desired point in space, while also allowing the physician to move the arm joints to a clinically advantageous position away from the patient to create better access while avoiding arm collisions.

[0033] The cart base 15 balances the weight of the column 14, carriage 17, and arm 12 on the floor. Thus, the cart base 15 houses heavier components such as electronics, motors, power supplies, and components that allow the cart to either move and / or be immobilized. For example, the cart base 15 includes casters 25 in the form of rollable wheels that allow the cart to be easily moved around the room before a procedure. Once in the proper position, the casters 25 may be immobilized using wheel locks to hold the cart 11 in place during a procedure.

[0034] The console 16, positioned at the vertical end of the column 14, provides both a user interface and a display screen (or dual-purpose device, such as a touchscreen 26) for receiving user input to provide both preoperative and intraoperative data to the physician user. Potential preoperative data on the touchscreen 26 may include preoperative planning, navigation and mapping data derived from a preoperative computerized tomography (CT) scan, and / or notes from a preoperative patient interview. Intraoperative data on the display may include optical information provided by tools, sensor and coordinate information from sensors, and 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 the carriage 17. From this position, the physician can view the console 16, the robotic arm 12, and the patient while operating the console 16 from behind the cart 11. As shown, the console 16 also includes a handle 27 to aid in maneuvering and stabilizing the cart 11.

[0035] FIG. 3 illustrates an embodiment of the robotic-enabled system 10 positioned for ureteroscopy. In a ureteroscopy procedure, the cart 11 may be positioned to deliver a ureteroscope 32, a procedure-specific endoscope designed to traverse a patient's urethra and ureters, to the patient's lower abdominal area. During a ureteroscopy, it may be desirable for the ureteroscope 32 to be directly aligned with the patient's urethra to reduce friction and force on sensitive anatomical structures in the area. As shown, the cart 11 may be aligned with the table legs to allow the robotic arm 12 to position the ureteroscope 32 for direct, linear access to the patient's urethra. From the table legs, the robotic arm 12 may insert the ureteroscope 32 along a virtual rail 33 directly through the urethra and into the patient's lower abdomen.

[0036] After insertion into the urethra using control techniques similar to those used in bronchoscopy, the ureteroscope 32 may be navigated to the bladder, ureters, and / or kidneys for diagnostic and / or therapeutic applications. For example, the ureteroscope 32 may be aimed at the ureters and kidneys to fragment formed kidney stones using a laser or ultrasonic lithotripsy device deployed down the working channel of the ureteroscope 32. After the lithotripsy is complete, the resulting stone fragments may be removed using a basket deployed down the ureteroscope 32.

[0037] FIG. 4 shows an embodiment of a similarly configured robotic-enabled system for a vascular procedure. In a vascular procedure, the system 10 may be configured so that the cart 11 can deliver a medical instrument 34, such as a steerable catheter, to an access point in the femoral artery in a patient's leg. The femoral artery presents both a larger diameter for navigation and a less circuitous and tortuous path to the patient's heart, simplifying navigation. As in a ureteroscopy procedure, the cart 11 may be positioned toward the patient's leg and lower abdomen, allowing the robotic arm 12 to provide a virtual rail 35 with direct, linear access to the femoral artery access point in the patient's thigh / hip region. After insertion into the artery, the medical instrument 34 may be oriented and inserted by translating the instrument driver 28. Alternatively, the cart may be positioned around the patient's upper abdomen to reach alternative vascular access points, such as the carotid and brachial arteries near the shoulder and wrist.

[0038] B. Robot System - Table Embodiments of robotic-enabled medical systems may also incorporate a patient table. Incorporation of a table reduces the amount of capital equipment in the operating room by eliminating carts and allows greater access to the patient. FIG. 5 shows one embodiment of such a robotic-enabled system deployed for a bronchoscopy procedure. The system 36 includes a support structure or column 37 for supporting a platform 38 (shown as a “table” or “bed”) above the floor. Similar to cart-based systems, the end effector of the robotic arm 39 of the system 36 includes an instrument driver 42 designed to manipulate an elongated medical instrument, such as the bronchoscope 40 of FIG. 5, through or along a virtual rail 41 formed from the linear alignment of the instrument driver 42. In practice, a C-arm for providing fluoroscopic imaging may be positioned above the patient's upper abdominal area by placing emitters and detectors around the table 38.

[0039] FIG. 6 provides, for discussion purposes, an alternative view of the system 36 without the patient and medical instruments. As shown, the column 37 may include one or more carriages 43, illustrated as ring-shaped within the system 36, which may serve as a base for one or more robotic arms 39. The carriages 43 may translate along a vertical column interface 44 that spans the length of the column 37 to provide different vantage points from which the robotic arms 39 may be positioned to reach the patient. The carriages 43 may rotate about the column 37 using mechanical motors positioned within the column 37, allowing the robotic arms 39 to have access to multiple sides of the table 38, such as both sides of the patient. In embodiments with multiple carriages, the carriages may be individually positioned on the column and may translate and / or rotate independently of the other carriages. While the carriages 43 need not surround the column 37 or even be circular, the ring shape as illustrated facilitates rotation of the carriages 43 about the column 37 while maintaining structural balance. Rotation and translation of carriage 43 allows the system to align medical instruments, such as endoscopes and laparoscopes, with different access points on the patient. In another embodiment (not shown), system 36 can include a patient table or bed with adjustable arm supports in the form of parallel-extending bars or rails. One or more robotic arms 39 can be mounted on adjustable arm supports that can be vertically adjusted (e.g., via shoulders with elbow joints). By providing vertical adjustment, robotic arm 39 can advantageously be stored compactly under a patient table or bed and then raised during a procedure.

[0040] Arm 39 may be attached to the carriage via a set of arm mounts 45 comprising a series of joints that may be independently rotated and / or telescopically extended to provide additional configurability to robotic arm 39. Additionally, arm mounts 45 may be positioned on carriage 43 such that, when carriage 43 is appropriately rotated, arm mounts 45 may be positioned on either the same side of table 38 (as shown in FIG. 6), on opposite sides of table 38 (as shown in FIG. 9), or on adjacent sides of table 38 (not shown).

[0041] The column 37 structurally provides support for the table 38 and a path for vertical translation of the carriage. Internally, the column 37 may be equipped with a lead screw for guiding the vertical translation of the carriage, and a motor for mechanizing the translation of the carriage based on the lead screw. The column 37 may also transmit power and control signals to the carriage 43 and the robotic arm 39 mounted thereon.

[0042] The table base 46 serves a similar function as the cart base 15 of the cart 11 shown in FIG. 2, housing the heavier components for counterbalancing the table / bed 38, column 37, carriage 43, and robotic arm 39. The table base 46 may also incorporate rigid casters to provide stability during the procedure. The casters, which deploy from the bottom of the table base 46, extend in opposite directions on either side of the base 46 and may be retracted when the system 36 needs to be moved.

[0043] Continuing with FIG. 6 , system 36 may also include a tower (not shown) that divides the functionality of system 36 between the table and tower to reduce the form factor and bulk of the table. As in previously disclosed embodiments, the tower may provide various support functions to the table, such as processing, computing, and control capabilities, power, fluidics, and / or optics and sensor processing. The tower may also be movable so that it is positioned away from the patient to improve physician access and reduce clutter in the operating room. Additionally, locating components within the tower allows for more storage space within the table base, potentially for the accommodation of a robotic arm. The tower may also include a master controller or console that provides both a user interface for user input, such as a keyboard and / or pendant, and a display screen (or touchscreen) for pre-operative and intra-operative information, such as real-time imaging, navigation, and tracking information. In some embodiments, the tower may also include a holder for a gas tank used for insufflation.

[0044] In some embodiments, the table base may house and store the robotic arm when not in use. FIG. 7 shows a system 47 for housing the robotic arm in a table-based system embodiment. In system 47, carriage 48 may be vertically translated into base 49 to house robotic arm 50, arm mount 51, and carriage 48 within base 49. Base cover 52 may be translated and retracted to open to position carriage 48, arm mount 51, and arm 50 around column 53 and closed to house and protect them when not in use. Base cover 52 may be sealed with a membrane 54 along the edge of its opening to prevent dirt and fluid ingress when closed.

[0045] FIG. 8 illustrates one embodiment of a robotic-enabled table-based system configured for a ureteroscopy procedure. For ureteroscopy, the table 38 may include a swivel portion 55 for positioning the patient off-angle from the column 37 and table base 46. The swivel portion 55 may rotate or pivot about a pivot point (e.g., located below the patient's head) to position the bottom of the swivel portion 55 away from the column 37. For example, pivoting the swivel portion 55 allows a C-arm (not shown) to be positioned above the patient's lower abdomen without competing for space with the column (not shown) below the table 38. By rotating a carriage (not shown) about the column 37, the robotic arm 39 may insert a ureteroscope 56 directly into the patient's groin area along a virtual rail 57 to reach the urethra. For ureteroscopy, stirrups 58 may also be secured to the swivel portion 55 of the table 38 to support the position of the patient's legs during the procedure and allow clear access to the patient's groin area.

[0046] In laparoscopic procedures, minimally invasive instruments may be inserted into a patient's anatomy through small incisions in the patient's abdominal wall. In some embodiments, the minimally invasive instruments include an elongated, rigid member, such as a shaft, used to access anatomy within the patient. After distension of the patient's abdominal cavity, the instruments may be directed to perform surgical or medical tasks, such as grasping, cutting, ablation, or suturing. In some embodiments, the instruments may include a scope, such as a laparoscope. FIG. 9 illustrates an embodiment of a robotic-enabled, table-based system configured for laparoscopic procedures. As shown in FIG. 9 , the carriage 43 of the system 36 can rotate and adjust vertically, allowing a pair of robotic arms 39 to be positioned on either side of the table 38 so that instruments 59 can be positioned using arm mounts 45 to pass through minimal incisions on either side of the patient and reach the patient's abdominal cavity.

[0047] To accommodate laparoscopic procedures, the robotic table system may also tilt the platform to a desired angle. FIG. 10 illustrates an embodiment of a robotic medical system with pitch or tilt adjustment. As shown in FIG. 10, the system 36 can accommodate the tilt of the table 38 to position one portion of the table further from the floor than the other portion. Additionally, the arm mount 45 may rotate to match the tilt so that the arm 39 maintains the same planar relationship as the table 38. To accommodate steeper angles, the column 37 may also include a telescoping portion 60 that allows the column 37 to extend vertically to prevent the table 38 from contacting the floor or colliding with the base 46.

[0048] FIG. 11 provides a detailed view of the interface between the table 38 and the column 37. A pitch rotation mechanism 61 may be configured to change the pitch angle of the table 38 relative to the column 37 in multiple degrees of freedom. The pitch rotation mechanism 61 may be enabled by the positioning of orthogonal axes 1, 2 at the column-table interface, each actuated by a separate motor 3, 4 in response to an electrical pitch angle command. Rotation along one screw 5 allows for tilt adjustment in one axis 1, and rotation along the other screw 6 allows for tilt adjustment along the other axis 2. In some embodiments, a ball-and-socket joint may be used to change the pitch angle of the table 38 relative to the column 37 in multiple degrees of freedom.

[0049] For example, pitch adjustment is particularly useful when attempting to position the table in the Trendelenburg position, i.e., when attempting to position the patient's lower abdomen higher off the floor than the patient's lower abdomen for lower abdominal surgery. The Trendelenburg position allows gravity to slide the patient's internal organs toward the patient's upper abdomen, emptying the abdominal cavity for entry of minimally invasive tools to perform lower abdominal surgical or medical procedures, such as laparoscopic prostatectomy.

[0050] 12 and 13 show isometric and end views of another embodiment of a table-based surgical robotic system 100. The surgical robotic system 100 includes one or more adjustable arm supports 105 (see, e.g., FIG. 14 ), which can be configured to support one or more robotic arms relative to a table 101. In the illustrated embodiment, a single adjustable arm support 105 is shown, but additional arm supports can be provided on the opposite side of the table 101. The adjustable arm support 105 can be configured to move relative to the table 101 to adjust and / or change the position of the adjustable arm support 105 and / or any robotic arms attached thereto relative to the table 101. For example, the adjustable arm support 105 can be adjusted with one or more degrees of freedom relative to the table 101. The adjustable arm support 105 provides the system 100 with great versatility, including the ability to easily accommodate one or more adjustable arm supports 105 and any robotic arms attached thereto beneath the table 101. The adjustable arm support 105 can be elevated from a stowed position to a position below the top surface of the table 101. In other embodiments, the adjustable arm support 105 can be elevated from a stowed position to a position above the top surface of the table 101.

[0051] The adjustable arm support 105 can provide several degrees of freedom, including lift, lateral translation, tilt, etc. In the illustrated embodiment of FIGS. 12 and 13, the arm support 105 is configured with four degrees of freedom, which are indicated by arrows in FIG. 12. The first degree of freedom allows adjustment of the adjustable arm support 105 in the z-direction (“Z-lift”). For example, the adjustable arm support 105 can include a carriage 109 configured to move up and down along or relative to the column 102 that supports the table 101. The second degree of freedom allows the adjustable arm support 105 to tilt. For example, the adjustable arm support 105 can include a rotational joint, which can allow the adjustable arm support 105 to align with the bed in a Trendelenburg position. The third degree of freedom can allow the adjustable arm support 105 to “pivot up,” which can be used to adjust the distance between the side of the table 101 and the adjustable arm support 105. The fourth degree of freedom allows the adjustable arm support 105 to translate along the longitudinal length of the table.

[0052] The surgical robotic system 100 of Figures 12 and 13 can include a table supported by a column 102 mounted to a base 103. The base 103 and column 102 support the table 101 against a support surface. A bed axis 131 and a support axis 133 are shown in Figure 13.

[0053] 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 the 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 each other.

[0054] The carriage 109 may 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., up and down on a first or vertical axis 123). The first joint 113 may provide a first degree of freedom ("Z-lift") for the adjustable arm support 105. The adjustable arm support 105 may include a second joint 115 that provides a second degree of freedom (tilt) for the adjustable arm support 105. The adjustable arm support 105 may include a third joint 117 that may provide a third degree of freedom ("upward pivot") for the adjustable arm support 105. An additional joint 119 (shown in FIG. 13) may be provided that mechanically constrains the third joint 117 to maintain the orientation of the rail 107 when the rail connector 111 is rotated about a third axis 127. The adjustable arm support 105 may include a fourth joint 121 that may provide a fourth degree of freedom (translation) to the adjustable arm support 105 along a fourth axis 129 .

[0055] FIG. 14 shows an end view of a surgical robotic system 140A having two adjustable arm supports 105A, 105B mounted on opposite sides of a table 101. A first robotic arm 142A is attached to a bar or rail 107A of the first adjustable arm support 105B. The first robotic arm 142A includes a base 144A attached to the rail 107A. The distal end of the first robotic arm 142A includes an instrument drive mechanism 146A that can be attached to one or more robotic medical instruments or tools. Similarly, the second robotic arm 142B includes a base 144B attached to the rail 107B. The distal end of the second robotic arm 142B includes an instrument drive mechanism 146B. The instrument drive mechanism 146B can be configured to attach to one or more robotic medical instruments or tools.

[0056] In some embodiments, one or more of the robotic arms 142A, 142B include arms with seven or more degrees of freedom. In some embodiments, one or more of the robotic arms 142A, 142B include eight degrees of freedom, including an insertion axis (one degree of freedom including insertion), a wrist (three degrees of freedom including wrist pitch, yaw, and roll), an elbow (one degree of freedom including elbow pitch), a shoulder (two degrees of freedom including shoulder pitch and yaw), and a base 144A, 144B (one degree of freedom including translation). In some embodiments, the insertion degree of freedom can be provided by the robotic arms 142A, 142B, while in other embodiments, the instrument itself provides the insertion via an instrument-based insertion architecture.

[0057] C. Instrument Drivers and Interfaces The end effector of the system's robotic arm includes (i) an instrument driver (alternatively referred to as an "instrument drive mechanism" or "instrument device manipulator") that incorporates electromechanical means for actuating the medical instrument, and (ii) a removable or detachable medical instrument, which may lack any electromechanical components such as a motor. This dichotomy can be caused by the need to sterilize medical instruments used in medical procedures and the inability to adequately sterilize expensive capital equipment due to the complex mechanical assembly of medical instruments and the sensitivity of their electronics. Thus, medical instruments can be designed to be detached, removed, and replaced from the instrument driver (and therefore the system) for individual sterilization or disposal by a physician or physician's staff. In contrast, instrument drivers do not need to be replaced or sterilized and can be draped for protection.

[0058] FIG. 15 shows an exemplary instrument driver. The instrument driver 62, positioned at the distal end of the robotic arm, includes one or more drive units 63 arranged with parallel axes to provide a controlled torque to the medical instrument via a drive shaft 64. Each drive unit 63 includes an individual drive shaft 64 for interacting with the instrument, a gearhead 65 for converting motor shaft rotation into a desired torque, a motor 66 for generating the drive torque, an encoder 67 for measuring the motor shaft speed and providing feedback to the control circuitry, and a control circuit 68 for receiving control signals and operating the drive unit. Each drive unit 63 is independently controlled and motorized, allowing the instrument driver 62 to provide multiple (four as shown in FIG. 15) independent drive outputs to the medical instrument. During operation, the control circuit 68 receives the control signals, sends motor signals to the motors 66, compares the resulting motor speed measured by the encoders 67 to a desired speed, and modulates the motor signals to generate the desired torque.

[0059] For procedures requiring a sterile environment, the robotic system may incorporate a drive interface, such as a sterile adapter connected to a sterile drape, located between the instrument driver and the medical instrument. The primary purpose of the sterile adapter is to transfer angular motion from the instrument driver's drive shaft to the instrument's drive input while maintaining physical separation, and therefore sterility, between the drive shaft and the drive input. Thus, an exemplary sterile adapter may consist of a series of rotary inputs and outputs intended to mate with the instrument driver's drive shaft and the drive input for the instrument. The sterile drape connected to the sterile adapter is constructed of a thin, flexible material, such as transparent or translucent plastic, and is designed to cover the instrument driver, robotic arm, and capital equipment, such as a cart (in a cart-based system) or table (in a table-based system). The use of the drape allows the capital equipment to be positioned adjacent to the patient while still located in an area not requiring sterility (i.e., the non-sterile field). On the other side of the sterile drape, the medical instrument may interface with the patient in an area requiring sterility (i.e., the sterile field).

[0060] D. Medical equipment FIG. 16 shows an exemplary medical instrument with a paired instrument driver. Similar to other instruments designed for use with a robotic system, the medical instrument 70 includes an elongated shaft 71 (or elongated body) and an instrument base 72. The instrument base 72, also referred to as an “instrument handle” due to its design intended for manual interaction by a physician, may include a rotatable drive input 73, e.g., a receptacle, pulley, or spool, designed to mate with a drive output 74 extending through a drive interface on an instrument driver 75 at the distal end of a robotic arm 76. When physically connected, latched, and / or coupled, the mated drive input 73 of the instrument base 72 can share a rotational axis with the drive output 74 on the instrument driver 75, allowing for the transfer of torque from the drive output 74 to the drive input 73. In some embodiments, the drive output 74 may include a spline designed to mate with a receptacle on the drive input 73.

[0061] The elongate shaft 71 is designed to be delivered through either an anatomical opening or lumen, as in endoscopy, or a minimally invasive incision, as in laparoscopy. The elongate 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 may include a customized combination of both flexible and rigid portions. When designed for laparoscopy, the distal end of the rigid elongate shaft can be connected to an end effector extending from an articulated wrist formed from a clevis having at least one degree of freedom, and a surgical tool or medical instrument, such as a grasper or scissors, that can be actuated based on force from a tendon when the drive input rotates in response to torque received from the drive output 74 of the instrument driver 75. When designed for endoscopy, the distal end of the flexible elongate shaft may include a steerable or controllable bend that can articulate and bend based on torque received from the drive output 74 of the instrument driver 75.

[0062] Torque from the instrument driver 75 is transmitted downstream of the elongate shaft 71 using tendons along 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 routed down one or more pull lumens along the elongate shaft 71 and anchored to a distal portion of the elongate shaft 71 or to a wrist at the distal portion of the elongate shaft. During a surgical procedure, such as a laparoscopic, endoscopic, or hybrid procedure, these tendons may be coupled to a distally attached end effector, such as a wrist, grasper, or scissors. Under such a configuration, torque exerted on the drive input 73 transmits tension to the tendons, thereby actuating the end effector in some manner. In some embodiments, during a surgical procedure, the tendons can rotate a joint about an axis, thereby moving the end effector 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 elongate shaft 71, with tension from the tendon causing the grasper to close.

[0063] In endoscopy, the tendons may be coupled to a bending or articulating section positioned along the elongate shaft 71 (e.g., at the distal end) via adhesive, control rings, or other mechanical fixation. When fixedly attached to the distal end of the bending section, torque exerted on the drive input 73 is transmitted downstream of the tendon, causing the softer bending section (sometimes referred to as the articulatable section or region) to bend or articulate. Along the non-bending section, it may be advantageous to spiral or convolute the individual pull lumens that direct the individual tendons along (or inward from) the wall of the endoscope shaft to counterbalance the radial forces resulting from tension in the pull wires. The angle of the spiral and / or spacing between them may be varied or designed for specific purposes; a narrower spiral will exhibit less shaft compression under load forces, while a lesser amount of spiraling will result in greater shaft compression under load forces but also exhibit bending limitations. At the other end of the spectrum, the pull lumen may be oriented parallel to the longitudinal axis of the elongate shaft 71 to allow for controlled articulation at a desired bend or articulatable section.

[0064] In endoscopy, the elongated shaft 71 houses several components that assist in robotic procedures. The shaft may comprise a working channel for placement of surgical tools (or medical instruments), irrigation, and / or aspiration to the surgical field at the distal end of the shaft 71. The shaft 71 may also house wires and / or optical fibers for communication of signals to and from an optical assembly at the distal tip, which may include an optical camera. The shaft 71 may also house optical fibers for carrying light from a proximally located light source, such as a light emitting diode, to the distal end of the shaft.

[0065] At the distal end of instrument 70, the distal tip may include a working channel opening for delivering tools to the surgical site for diagnosis and / or treatment, irrigation, and aspiration. The distal tip may also include a port for a camera, such as a fiberscope or digital camera, to capture images of the internal anatomical space. Relatedly, the distal tip may also include a port for a light source to illuminate the anatomical space when a camera is used.

[0066] 16, the drive shaft axis, and therefore the drive input axis, is perpendicular to the axis of the elongate shaft. However, this arrangement complicates the roll ability of the elongate shaft 71. Rolling the elongate shaft 71 along its axis while holding the drive input 73 stationary can result in undesirable entanglement of the tendons as they extend from the drive input 73 and enter the pull lumen within the elongate shaft 71. Such resulting tendon entanglement can interfere with any control algorithm intended to predict the movement of a flexible elongate shaft during an endoscopic procedure.

[0067] FIG. 17 shows an alternative design of an instrument driver and instrument in which the axes of the drive units are parallel to the axis of the elongated shaft of the instrument. As shown, a circular instrument driver 80 includes four drive units with parallel-aligned drive outputs 81 at the end of a robotic arm 82. The drive units and their respective drive outputs 81 are housed within a rotating assembly 83 of the instrument driver 80, which is driven by one of the drive units in assembly 83. In response to torque provided by the rotary drive units, the rotating assembly 83 rotates along a circular bearing connecting the rotating assembly 83 to a non-rotating portion 84 of the instrument driver. Power and control signals may be communicated from the non-rotating portion 84 of the instrument driver 80 to the rotating assembly 83 through electrical contacts and may be maintained through rotation by a brushed slip-ring connection (not shown). In other embodiments, the rotating assembly 83 may be responsive to a separate drive unit that is integrated into the non-rotating portion 84 and is therefore not parallel to the other drive units. Rotation mechanism 83 enables instrument driver 80 to rotate the drive units and their respective drive outputs 81 as a single unit about instrument driver axis 85 .

[0068] Similar to the previously disclosed embodiments, the instrument 86 may include an elongated shaft portion 88 and an instrument base 87 (shown with a transparent exterior skin for purposes of illustration) that includes a plurality of drive inputs 89 (such as receptacles, pulleys, and spools) configured to receive the drive outputs 81 in the instrument driver 80. Unlike the previously disclosed embodiments, the instrument shaft 88 extends from the center of the instrument base 87, with an axis that is substantially parallel to the axis of the drive inputs 89, rather than orthogonal as in the design of FIG.

[0069] When coupled to the rotation assembly 83 of the instrument driver 80, the medical instrument 86, including the instrument base 87 and the instrument shaft 88, rotates with the rotation assembly 83 about the instrument driver axis 85. Because the instrument shaft 88 is positioned in the center of the instrument base 87, the instrument shaft 88 is coaxial with the instrument driver axis 85 when attached. Rotation of the rotation assembly 83 therefore causes the instrument shaft 88 to rotate about its own longitudinal axis. Furthermore, as the instrument base 87 rotates with the instrument shaft 88, any tendons connected to the drive input 89 within the instrument base 87 do not become entangled during rotation. Thus, the parallelism of the axes of the drive output 81, drive input 89, and instrument shaft 88 allows shaft rotation without entangling any of the control tendons.

[0070] FIG. 18 illustrates an instrument having an instrument-based insertion architecture, according to some embodiments. The instrument 150 can be coupled to any of the instrument drivers discussed above. The instrument 150 includes an elongate shaft 152, an end effector 162 connected to the shaft 152, and a handle 170 coupled to the shaft 152. The elongate shaft 152 includes a tubular member having a proximal portion 154 and a distal portion 156. The elongate shaft 152 includes one or more channels or grooves 158 along its outer surface. The grooves 158 are configured to receive one or more wires or cables 180 therethrough. Thus, one or more cables 180 extend along the outer surface of the elongate shaft 152. In other embodiments, the cables 180 can extend through the elongate shaft 152. Manipulation of one or more of the cables 180 (e.g., via the instrument driver) results in actuation of the end effector 162.

[0071] The instrument handle 170, which may also be referred to as an instrument base, may generally include a mounting interface 172 having one or more mechanical inputs 174, such as receptacles, pulleys, or spools, designed to reciprocally mate with one or more torque couplers on the mounting surface of the instrument driver.

[0072] In some embodiments, instrument 150 includes a series of pulleys or cables that allow elongate shaft 152 to translate relative to handle 170. In other words, instrument 150 itself includes an instrument-based insertion architecture that accommodates the insertion of the instrument, thereby minimizing reliance on a robotic arm to provide insertion of instrument 150. In other embodiments, the robotic arm can be significantly involved in the insertion of the instrument.

[0073] E. Controller Any of the robotic systems described herein can include an input device or controller for manipulating an instrument attached to the robotic arm. In some embodiments, the controller can be coupled (e.g., communicatively, electronically, electrically, wirelessly, and / or mechanically) to the instrument, such that manipulation of the controller causes a corresponding manipulation of the instrument, e.g., via master-slave control.

[0074] 19 is a perspective view of an embodiment of controller 182. In this embodiment, controller 182 comprises a hybrid controller that can have both impedance control and admittance control. In other embodiments, controller 182 can utilize only impedance or passive control. In other embodiments, controller 182 can utilize only admittance control. By being a hybrid controller, controller 182 can advantageously have a lower perceived inertia during use.

[0075] In the illustrated embodiment, the controller 182 is configured to enable operation 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.

[0076] 19 , each positioning platform 188 includes a selective compliance assembly robot (SCARA) arm 198 coupled to a column 194 by a prismatic joint 196. The prismatic joint 196 is configured to translate along the column 194 (e.g., along a rail 197) to translate each of the handles 184 in the z-direction, providing a first degree of freedom. The SCARA arm 198 is configured to allow movement of the handles 184 in the x-y plane, providing two additional degrees of freedom.

[0077] In some embodiments, one or more load cells are positioned within the controller. For example, in some embodiments, a load cell (not shown) is positioned within the body of each of the gimbals 186. By providing load cells, a portion of the controller 182 can operate under admittance control, thereby advantageously reducing the perceived inertia of the controller during use. In some embodiments, the positioning platform 188 is configured for admittance control, while the gimbals 186 are configured for impedance control. In other embodiments, the gimbals 186 are configured for admittance control and the positioning platform 188 is configured for impedance control. Thus, in some embodiments, the translational or positional degree of freedom of the positioning platform 188 can rely on admittance control, while the rotational degree of freedom of the gimbals 186 relies on impedance control.

[0078] 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 intraluminal guidance to the operating physician. In contrast, the robotic systems contemplated by the present disclosure may provide non-radiation-based navigation and localization means to reduce physician exposure to radiation and reduce the amount of equipment in the operating room. As used herein, the term "localization" may refer to determining and / or monitoring the position of an object within a reference coordinate system. Techniques 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 surgical environment. In other cases where radiation-based imaging modalities are still used, preoperative mapping, computer vision, real-time EM tracking, and robot command data may be used individually or in combination to improve information obtained solely by radiation-based imaging modalities.

[0079] 20 is a block diagram illustrating a localization system 90 for estimating the position of one or more elements of a robotic system, such as the position of an instrument, according to an exemplary embodiment. The localization system 90 may be a set of one or more computing devices configured to execute one or more instructions. The computing devices may be embodied by a processor (or multiple processors) and computer-readable memory in one or more of the components discussed above. By way of example, and not limitation, the computing devices may be in the tower 30 shown in FIG. 1, in the cart shown in FIGS. 1-4, in the bed shown in FIGS. 5-14, etc.

[0080] 20, the localization system 90 may include a localization module 95 that processes the input data 91-94 to generate position data 96 of the distal tip of the medical instrument. The position data 96 may be data or logic that represents the position and / or orientation of the distal tip of the instrument relative to a frame of reference. The frame of reference may be relative to a known object, such as the patient's anatomy or an EM field generator (see discussion of EM field generators below).

[0081] The various input data 91-94 will now be described in more detail. Preoperative mapping can be achieved using the acquisition of low-dose CT scans. Preoperative CT scans are reconstructed into three-dimensional images visualized, for example, as cutaway "slices" of the patient's internal anatomy. When analyzed as a whole, an image-based model can be generated for the anatomical cavities, spaces, and structures of the patient's anatomy, such as the patient's pulmonary network. Techniques such as center-line geometry can be determined and approximated from the CT images to create 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 No. 14 / 523,760, the contents of which are incorporated herein in their entirety. Network topology models may also be derived from CT images and are particularly suited to bronchoscopy.

[0082] In some embodiments, the instrument may be equipped with a camera to provide visual data 92. The localization module 95 may process the visual data to enable one or more vision-based position tracking. For example, pre-operative model data may be used in conjunction with the visual data 92 to enable computer vision-based tracking of a medical instrument (e.g., an endoscope or an instrument advancing through the working channel of the endoscope). For example, using the pre-operative model data 91, the robotic system can generate a library of predicted endoscopic images from the model based on the expected path of travel of the endoscope, with each image linked to a location in the model. During surgery, this library can be referenced by the robotic system to compare real-time images captured by a camera (e.g., a camera at the distal end of the endoscope) with those in the image library to assist with localization.

[0083] Other computer vision-based tracking techniques use feature tracking to determine the motion of the camera, and therefore the endoscope. Some features of the localization module 95 may identify circular geometric shapes in the preoperative model data 91 that correspond to anatomical lumens and track changes in those geometries to determine which anatomical lumens have been selected, as well as the relative rotational and / or translational motion of the camera. The use of a phase map may further enhance vision-based algorithms or techniques.

[0084] Optical flow, another computer vision-based technique, may analyze the displacement and translation of image pixels in a video sequence in visual data 92 to infer camera movement. Examples of optical flow techniques may include motion detection, object segmentation calculations, luminance, motion compensated coding, stereo disparity measurements, etc. By comparing multiple frames over multiple iterations, the movement and position of the camera (and therefore the endoscope) can be determined.

[0085] The localization module 95 can use real-time EM tracking to generate a real-time position of the endoscope within a global coordinate system that can be registered to the patient's anatomy represented by the preoperative model. In EM tracking, an EM sensor (or tracker), consisting of one or more sensor coils embedded in a medical instrument (e.g., an endoscopic instrument) at one or more locations and orientations, measures variations in an EM field generated by one or more static EM field generators positioned at known locations. The position information detected by the EM sensor is stored as EM data 93. The EM field generator (or transmitter) can be placed in close proximity to the patient to generate a low-intensity magnetic field that can be detected by the embedded sensor. The magnetic field induces small currents in the sensor coils of the EM sensor, which can be analyzed to determine the distance and angle between the EM sensor and the EM field generator. These distances and orientations can be "registered" intraoperatively to the patient's anatomy (e.g., the preoperative model) to determine a geometric transformation that aligns a single position in the coordinate system with a location in the preoperative model of the patient's anatomy. Once aligned, an EM tracker embedded in one or more locations on the medical instrument (e.g., the distal tip of an endoscope) can provide a real-time display of the medical instrument's progression through the patient's anatomy.

[0086] The robot command and kinematic data 94 may also be used by a localization module 95 to provide localization data 96 for the robotic system. Device pitch and yaw resulting from articulation commands can be determined during pre-operative calibration. Intraoperatively, these calibration measurements can 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 phase modeling to estimate the position of the medical instrument within the network.

[0087] As Figure 20 illustrates, several other input data can be used by the localization module 95. For example, although not shown in Figure 20, an instrument that utilizes shape-sensing fibers can provide shape data that the localization module 95 can use to determine the position and shape of the instrument.

[0088] The localization module 95 may use a combination of the input data 91-94. In some cases, such a combination may use a probabilistic approach in which the localization module 95 assigns a confidence weight to the position determined from each of the input data 91-94. Thus, if the EM data may be unreliable (such as in the presence of EM interference), the reliability of the position determined by the EM data 93 may be reduced, and the localization module 95 may rely more heavily on the vision data 92 and / or the robot command and kinematic data 94.

[0089] As discussed above, the robotic systems discussed herein can be designed to incorporate one or a combination of two or more of the above-described techniques. The computer-based control system of a tower-, bed-, and / or cart-based robotic system may store, for example, in a non-transitory computer-readable storage medium such as a persistent magnetic storage drive, solid-state drive, or the like, computer program instructions that, when executed, cause the system to receive and analyze sensor data and user commands, generate system-wide control signals, and display navigation and localization data such as instrument position within a global coordinate system, anatomical maps, and the like.

[0090] 2. Introduction to systems and methods for collision avoidance The present application discloses a medical robotic system that utilizes information about objects within the system's vicinity to avoid or reduce the risk of future collisions. As described herein, the robotic medical system can include multiple robotic arms configured to control the movement of medical tools during a given medical procedure. To achieve a desired pose of the medical tool, the robotic arms can be positioned in poses that may cause the robotic arms to come into contact with external objects, such as, for example, a patient, bedside staff, or inanimate objects (e.g., accessories on a bed). Detecting contact between the robotic arms and external objects sufficiently early (e.g., immediately after contact or at least before the contact generates a force greater than a threshold) can improve the safety of robotic surgery.

[0091] The information about nearby objects can include contact information obtained using contact sensors, such as force sensors, and non-contact information obtained using non-contact sensors. Based on the information about nearby objects of the medical robotic system, the configuration of the kinematic chain (e.g., robotic arm and adjustable arm support) is adjusted, for example, to increase the distance from nearby objects to reduce the likelihood of future collisions.

[0092] A. Robotic Arm and Sensor Architecture for Detecting Contact or Obtaining Control Information The medical robotic system includes multiple sensors for collecting information (e.g., position information) about objects within the vicinity of the medical robotic system, some of which are located on or adjacent to the robotic arm of the medical robotic system.

[0093] FIG. 21 illustrates an exemplary robotic arm 205 according to some embodiments. The robotic arm 205 includes multiple links 132 connected by one or more joints 131 (e.g., 131-1 through 131-3). The proximal end of the robotic arm 205 may be connected to a base 136, and the distal end of the robotic arm 205 may be connected to an advanced device manipulator (ADM) 134 (also referred to as an instrument driver or end effector of the robotic arm). The ADM 134 may be configured to control the positioning and manipulation of a medical tool 135 (also referred to as a medical instrument). Accordingly, the links 132 may be removably coupled to the medical tool 135. The joints 131 provide the robotic arm 205 with multiple degrees of freedom (DoF) that facilitate control of the medical tool 135 via the ADM 134.

[0094] In some embodiments, the robotic arm 205 includes one or more force-based sensors for detecting contact between any portion of the robotic arm 205 and an object 137 other than the robotic arm 205 (e.g., another robotic arm, other medical equipment, a patient, a medical professional, etc.). In some embodiments, such sensors are located within or adjacent to a joint 131. For example, one or more force sensors may be located at joint 131-3. The one or more force sensors located at joint 131-3 may detect interaction forces (e.g., magnitude and / or direction of forces and / or moments) from the proximal end of the robotic arm 205. Additionally or alternatively, one or more force sensors may be located at or adjacent joint 131-1 near the distal end of the robotic arm 205. The one or more force sensors located at or near joint 131-1 may include a six-axis load cell capable of detecting both forces and moments (e.g., torque) about six axes (e.g., forces along the x-, y-, and z-axes, and torque about the x-, y-, and z-axes). Based on the forces detected by the one or more sensors, the one or more processors can determine the location of the contact and one or more portions of the robotic arm 205 involved in the contact (one or more links or joints, the ADM 134, or the medical tool 135).

[0095] Additionally or alternatively, the robotic arm 205 includes one or more contact sensors. Figures 22A and 22B illustrate an exemplary robotic link that may form part of a robotic arm having one or more contact sensors, according to some embodiments.

[0096] Figure 22A shows three views of a distal portion of the robotic arm 205, and Figure 22B shows three views of a portion of the robotic arm 205 proximal to the distal portion of Figure 22A. With reference to Figures 22A and 22B, the robotic arm 205 can include a device manipulator 203, a plurality of links 207, 209, 211, and 233, and a plurality of joints 213, 215, 217, and 219 connecting the device manipulator 203 to the links 207, 209, 211, and 233. In each of the views shown in Figure 22A, an area 221 of the robotic arm 205 that is relatively likely to collide with the patient is highlighted.

[0097] In some embodiments, an arm component (e.g., one of robotic links 205-211 or joints 213-219 in Figures 22A-22B) is coupled with one or more sensors for sensing contact with an external object, such as a patient, bedside staff, or other object.

[0098] In some embodiments, a shell can be suspended around a given link, and relative motion between the shell and an internal component / member of the link can be detected using one or more sensors to detect contact with an external object. FIG. 23 shows an exemplary link 300 including a rigid shell 309 and configured to detect contact with an external object, according to some embodiments. In particular, link 300 includes a structural link 301, a structural cover 303, a first joint 305, a second joint 307, a shell 309, a pair of reaction paddles 311, and a shell cover 313. For example, the internal components of link 300 may include structural link 301 and structural cover 303.

[0099] Structural cover 303 may be attached to structural link 301 to house the components of structural link 301 and form an internal structural connection between first joint 305 and second link 305. Shell 309, along with shell cover 313, is suspended from and surrounds structural link 301. As used herein, shell 309 and shell cover 313 may be collectively referred to simply as "shell" 309, while structural link 301 and structural cover 303 may collectively be referred to simply as structural link 301 or operative link, unless the context clearly indicates otherwise.

[0100] Shell 309 may be connected to structural link 301 via a force sensing connection. Shell 309 surrounds structural link 301 so that when link 300 contacts an external object, the object will come into contact with shell 309. Thus, the force sensing connection can detect contact between shell 309 and the external object by measuring a change in force between shell 309 and structural link 301 caused by link 300 contacting the external object. Shell 309 may also be sufficiently rigid such that upon contact with the external object, shell 309 engages the force sensing connection. Advantageously, by using a rigid shell 309, forces and relative motion between shell 309 and structural link 301 can be sensed in all three directions.

[0101] The force sensing connection can be implemented in a variety of different ways according to some embodiments. For example, the force sensing connection can include one or more of a traditional load cell, a force sensing resistor, and / or any component capable of sensing force (or displacement when combined with a spring).

[0102] Figure 24 shows an example of a force sensing connection that may be used in the link 300 of Figure 23, according to some embodiments. In particular, the force sensing connection may include multiple shell sensors 321 (e.g., 14 shell sensors in the illustrated embodiment) that may be disposed between the structural link 301 and the shell 309.

[0103] In some embodiments, the sensors 321 are distributed throughout the link 301 between the shell 309 and the structural link 300. For example, the shell 309 can be suspended on the structural link 301 via the sensors 321. Depending on the implementation, the link 300 can include one, two, three, four, or more sensors 321 distributed along the robot arm link. FIGS. 25A and 25B show two views of a link 401 in which 14 sensors 321 are included in the link 401, according to some embodiments. In particular, FIGS. 25A and 25B show side and front views, respectively, of one end of the link 401 including seven sensors 321. The link 401 can be substantially symmetrical at both ends of the link 401, thereby including a total of 14 sensors 321 within the link 401.

[0104] 25C and 25D show two views of link 411, in which 12 sensors 321 are included in link 411, according to some embodiments. In some implementations, a robotic arm may include both link 401 and link 411, with link 401 positioned proximal to link 411. In particular, FIGS. 25C and 25D show side and front views, respectively, of link 411 including 12 sensors 321. Link 411 may be substantially symmetrical at both ends of link 411, thereby including a total of 24 sensors 321 within link 401. In some implementations, multiple sensors 321 may be configured to support the rigid shell without being fixed to the rigid shell. In some implementations, link 401 or 411 may further include one or more supports configured to support the rigid shell relative to the structural link. For example, the one or more supports may include springs, flexures, and / or suspensions.

[0105] While FIGS. 25A-25D show links 401 and 411 including multiple sensors 321, in some embodiments, the links may include a single sensor configured to sense force and / or displacement between structural link 301 and shell 309 in multiple directions. Using signals received from sensor 321, the robotic system may be configured to detect the direction of contact between shell 309 and an external object. The robotic system may also measure the magnitude of force resulting from contact between shell 309 and an external object based on signals from sensor 321. Based on the arrangement of multiple sensors 321 within links 401 and 411, the robotic system may also be configured to detect torque applied to the links. For example, when torque is applied to shell 309, a particular sensor 321 on one side of links 401 and 411 may compress. Based on the position and force sensed by the compressed sensor 321, the robotic system may determine the torque being applied to links 401 and 411.

[0106] 21 , the robotic arm 205 can be positioned in various poses while one or more sensors 321 detect contact or collision between any portion of the robotic arm 205 and another object. In some situations, there are additional constraints on the movement of the robotic arm 205. For example, during a medical procedure, it may be desirable to maintain a remote center of movement (RCM) of the ADM 134 of the robotic arm 205 and / or a tool 135 coupled thereto at a static pose / position. The RCM may refer to a point in space where the movement of a cannula or other access port through which the medical tool 135 is inserted is constrained. In some implementations, the medical tool 135 includes an end effector that is inserted through an incision or natural orifice in a patient while maintaining the RCM.

[0107] In some situations, the robotic system may be configured to move one or more links 132 of the robotic arm 205 within a "null space" to avoid collisions with nearby objects (e.g., other robotic arms) while the ADM 134 and / or RCM of the robotic arm 205 are maintained in their respective poses / positions. The null space may be considered the space in which the robotic arm 205 can move without causing movement of the ADM 134 and / or RCM, thereby maintaining the position and / or orientation of the medical tool 135. In some implementations, the robotic arm 205 may have multiple positions and / or configurations available for each pose of the ADM 134.

[0108] To enable the robot arm 205 to move the ADM 134 to a desired pose in space, in certain implementations, the robot arm 205 can have at least six DoFs: three DoFs for translation (e.g., X position, Y position, Z position) and three DoFs for rotation (e.g., yaw, pitch, and roll). In some implementations, each joint 131 can provide the robot arm 205 with a single DoF, and thus the robot arm 205 can have at least six joints to achieve degrees of freedom of movement to position the ADM 134 at any pose in space. To further maintain the ADM 134 and / or remote center or movement of the robot arm 205 at a desired pose, the robot arm 205 may further have at least one additional “redundant joint.” Thus, in certain implementations, a system can include a robot arm 205 with at least seven joints 131, providing the robot arm 205 with at least seven DoFs. However, depending on the implementation, the robot arm 205 may have a greater or lesser number of DoF.

[0109] A robot arm 205 with at least one redundant DoF (also referred to as a "kinematically redundant" robot arm) may refer to a robot arm 205 that has at least one more DoF than the minimum number of DoF required to perform a given task. For example, the robot arm 205 may have at least seven DoF, and one of the joints 131 of the robot arm 205 may be considered a redundant joint to complete a task requiring six DoF. The one or more redundant joints may enable the robot arm 205 to move within the null space to maintain both the attitude of the ADM 134 and the position of the RCM, and to avoid collisions with other arms or objects.

[0110] A robotic system (e.g., system 36 of FIG. 6 or system 140A of FIG. 14) may be configured to perform collision avoidance, for example, to avoid collisions between adjacent robot arms, by utilizing motion (e.g., either individual or coordinated motion) of one or more redundant joints in the null space. For example, when a robot arm collides with or approaches (e.g., within a specified distance) another robot arm, one or more processors of the system may be configured to detect the collision or impending collision (e.g., via kinematics). The system may then control one or both of the robot arms to adjust their respective joints in the null space to avoid the collision or impending collision. In some implementations involving a pair of robot arms, the base and its end effector of one of the robot arms may maintain their pose while the link or joint between them moves in the null space to avoid collision with the adjacent robot arm.

[0111] 26 shows an example of a robotic system 200 including an adjustable arm support 210, according to some embodiments. In FIG. 26, the robotic system 200 includes multiple robotic arms 205, one or more adjustable arm supports 210, one or more set-up joints 215, and a bed column 220. Each of the robotic arms 205 may be supported by one of the adjustable arm supports 210, which may be supported by the set-up joints 215. As described above, each robotic arm 205 can have multiple DoFs. Similarly, the adjustable arm supports 210 and the set-up joints 215 may be movable with one or more DoFs.

[0112] FIG. 27 schematically illustrates how one or more DoFs can be shared between a robot arm, an adjustable arm support, and a setup joint. FIG. 27 illustrates a system in which a setup joint 215 can be coupled to a bed support 223 at its proximal end and to an adjustable arm support 210 at its distal end. Additionally, multiple robot arms 205 can be coupled to adjustable arm supports 210 at their respective proximal ends. In one particular implementation, the adjustable arm support 210 and the setup joint 215 can both have four DoFs. Thus, a robot arm 205 attached to an adjustable arm support 210 can share the four DoFs provided by the setup joint 215 and the adjustable arm support 210.

[0113] Thus, depending on the implementation, a robotic medical system can have many more robotically controlled degrees of freedom beyond just the degrees of freedom in the robotic arms to provide null space motion and collision avoidance. In each of these implementations, the end effectors and / or remote centers associated therewith (e.g., along the tool axis) of one or more robotic arms (and any tools or instruments coupled thereto) can advantageously maintain their orientation and / or position within the patient.

[0114] In some embodiments, the robotic systems described herein utilize shared DoFs between different link members (e.g., of multiple robot arms and / or adjustable arm supports) to achieve null space motion for collision avoidance. In certain implementations, the system can use one or more DoFs associated with a first set of one or more motorized links (e.g., in the form of one or more robot arms, such as the robot arm 205 illustrated in FIG. 26 ) in coordinated and / or synchronized movement with one or more DoFs associated with a second set of one or more motorized links (e.g., in the form of support links that support the robot arm, including one or more setup joint links and one or more arm support links, such as the setup joint 215 and adjustable arm support 210 illustrated in FIG. 26 ) to achieve null space motion for collision avoidance.

[0115] A first set of one or more motorized links (e.g., in the form of one or more robotic arms) can be configured to perform a different function than a second set of one or more motorized links (e.g., in the form of adjustable arm support links or rails). In some implementations, the first set of one or more links is supported by the second set of one or more links.

[0116] Furthermore, in some implementations, a first set of one or more motorized links has a different number of DoFs than a second set of one or more motorized links. For example, as shown in the simplified implementation illustrated in FIG. 27 , a first set of one or more links can form three robot arms 205, each having seven or more DoFs. For example, each of the robot arms 205 can have DoFs including, but not limited to, shoulder yaw, shoulder pitch, elbow pitch, wrist yaw, wrist pitch, roll, and insertion. A second set of one or more motorized links can be combined with an adjustable arm support 210 having four or more DoFs to form a setup joint 215. For example, the setup joint 215 and adjustable arm support 210 can have DoFs including, but not limited to, vertical translation or “Z-lift,” longitudinal translation along the bed, tilt, and upward pivot. The DoFs of the setup joint 215 and adjustable arm support 210 are also shown in FIG. 24 , as discussed above.

[0117] In some other implementations, a first set of one or more motorized links can have the same number of DoFs as a second set of one or more motorized links. Advantageously, sharing DoFs between the first set of one or more links and the second set of one or more links can expand the number of DoFs for null space motion and collision avoidance.

[0118] Aspects of the present disclosure relate to robotic systems having one or more DoFs in addition to the DoFs of the robotic arm capable of null space motion. These additional DoFs (e.g., from setup joints in combination with an adjustable arm support) can affect the motion of the robotic arm coupled to the adjustable arm support and assist in collision avoidance. For example, DoFs from a second set of links including vertical translation, longitudinal translation, and tilt can be particularly useful for null space motion when combined with each of the DoFs of the robotic arm.

[0119] In the above-described implementations, at least one set of link members is associated with the robot arm such that shared DoFs between different sets of link members are utilized for null space motion. In these implementations, the ADM of the robot arm, as well as the RCM of a tool attached to the robot arm, can advantageously maintain its pose / position.

[0120] B. Use of Force Information for Robot Arm and / or Bar Optimization Force information detected by one or more of the sensors described above (e.g., during collision or contact between a robotic arm and an object such as a patient) can be converted into general constraints for optimization of the robotic arm and / or adjustable arm support (also known as a "bar"). In some cases, a medical procedure can start with a standard port configuration, whereby one or more robotic arms are attached to the port locations. When a collision occurs, collision information will be collected via one or more force sensors (e.g., contact sensors including force sensors at one or more joints). Other potential sensors that can detect collisions include sensors for detecting ultrasound or light. Such collision information includes the nature of the collision (e.g., arm-to-arm collision, arm-to-environment collision), the general location of the collision (e.g., whether the collision is on a link, a joint, an advanced device manipulator (ADM), etc.), and the estimated direction of the collision (e.g., a collision vector). This information is used to generate external constraints, e.g., latent fields / collision fields that occur at the location of the collision in the direction of the collision. This potential field can repel and "push" nearby joints and links of the robotic arm and / or adjustable arm support away, thereby advantageously avoiding further collisions. The strength of this "push" can be a function of the distance from nearby components to the location of the collision. With these constraints, in addition to optimizing one or more arms, the adjustable arm support / bar pose can also be optimized relative to the collision distance and the robotic arm end effector workspace. This allows the system to easily recover from the collision and continue the procedure with a lower likelihood of future collisions.

[0121] FIG. 28 is a flow diagram illustrating a method for adjusting one or more kinematic chains (e.g., each kinematic chain includes an assembly of rigid bodies rotatably coupled to one another, such as one or more robotic arms coupled to associated adjustable arm supports / bars) based on contact information, according to some embodiments.

[0122] The workflow shown in FIG. 28 begins with a medical robotic system being used for a medical procedure (operation 281), where the medical robotic system has one or more kinematic chains. While the system is being used for the medical procedure, a collision with the kinematic chains (e.g., contact between the robotic arm and a patient) is detected (operation 282) (e.g., using one or more sensors described with respect to FIGS. 21 , 22A-22B, 24, and 25A-25D). The medical robotic system stops the movement of the kinematic chains (operation 283) and collects contact information. In some cases, the medical robotic system provides the contact information to a specific instruction set (e.g., a software application) or electronic device for optimization of the configuration of one or more kinematic chains. The medical robotic system then determines a new configuration of the kinematic chains (operation 284), for example, by using the specific instruction set or electronic device, and places the kinematic chains in the determined configuration (operation 285), thereby eliminating contact with the kinematic chains. The medical robotic system then resumes the medical procedure (operation 286). With the kinematic chain in an optimized configuration, the likelihood of the kinematic chain contacting the object is reduced. In some cases, the medical robotic system continues the medical procedure (operation 281).

[0123] 29A-29F show the configuration of the robot arm 205 during operation according to the flow diagram of FIG.

[0124] 29A shows the medical robotic system 200 described with respect to FIG. 26 with a patient on a tabletop 225 undergoing a medical procedure. In FIGS. 29A-29F, medical instruments are not shown so as not to obscure other aspects of the operation of the medical robotic system 200.

[0125] Figure 29B shows that the robot arm 205-2 moves downward and a portion of the robot arm 205-2 comes into contact with the patient. Figure 29C shows that the medical robotic system 200 (or one or more processors thereof) receives the contact information (e.g., the location of the contact, the direction of the contact, the force of the contact, etc.) and models the contact in a map (e.g., a three-dimensional map that models objects within the vicinity of the medical robotic system 200). For example, the contact or collision can be modeled as a constraint field or a latent field in the map. In Figure 29C, the contact is modeled as a latent field 227-1. In some implementations, the latent field is directional (e.g., applicable to portions of the kinematic chain located in a particular direction or range of directions from the contact location) or omnidirectional (e.g., applicable to all portions of the kinematic chain regardless of their position relative to the contact location). In some implementations, the influence of the constraint or latent field is based on the distance from the contact location to the respective portion of the kinematic chain. For example, a portion of the kinematic chain located a first distance from the contact location may be moved further away from its original position and / or the contact location than another portion of the kinematic chain located a second distance from the contact location that is greater than the first distance. In FIG. 29C, the distal end of robotic arm 205-2 (e.g., the tip of robotic arm 205-2 configured to hold a medical tool), located near the contact location, may be maintained away from the contact location or moved minimally. Similarly, the proximal end of robotic arm 205-2 (near adjustable arm support 210) and the other robotic arms 205-1 and 205-3 through 205-6 may remain stationary, while intermediate links and joints between the proximal and distal ends of the arms may move.

[0126] In some implementations, the size of the constraint (e.g., the size of the constrained area or volume) or the extent of the latent field is determined based on one or more factors, such as the force detected from the contact, the type of contacting object (e.g., determined based on the contact location, such as a patient whose collision is detected on tabletop 225 and a medical professional whose collision is detected outside tabletop 225), and the probability of detection. For example, FIG. 29D shows a latent field having a wider extent than the latent field shown in FIG. 29C, and the configuration of multiple robotic arms, i.e., robotic arms 205-1 through 205-3, is adjusted (e.g., robotic arms 205-1 and 205-3 and portions of robotic arm 205-2 are moved away from the contact location or latent field).

[0127] FIG. 29E shows that another collision (or contact) between robot arm 205-1 and the patient is detected during downward movement of the distal end of robot arm 205-1. In FIG. 29E, medical robotic system 200 receives information about the contact between robot arm 205-1 and the patient, models the contact as latent field 227-2 in the map, and adjusts the configuration of robot arm 205-1 (or the configuration of two or more of robot arms 205-1 through 205-6, depending on the extent of the latent field). FIGS. 29E and 29F also show that medical robotic system 200 maintains latent field 227-1 in the map (so that robot arm 205-1 may not be in the vicinity of latent field 227-1 during adjustment of the configuration of robot arm 205-1). In some cases, one or more latent fields (or constraints) may expire over time, resulting in the medical robotic system 200 not maintaining the latent field 227-1 by the time a collision between the robotic arm 205-1 and the patient is detected.

[0128] 30 is a flow diagram illustrating a method 330 for adjusting a kinematic chain configuration based on contact information, according to some embodiments. The method 330 is performed by an electronic device (e.g., one or more processors, such as the processor 380 described with respect to FIG. 38) in communication with a medical robotic system including a first kinematic chain and one or more sensors positioned to detect one or more parameters (e.g., force, torque, direction of contact, contact location, etc.) of contact with the first kinematic chain (e.g., the medical robotic system 200 having the robotic arm 205 and one or more sensors described with respect to FIGS. 21, 23, 24, and 25A-25D).

[0129] In some embodiments, the one or more sensors include at least one of a force sensor positioned at the base of the first kinematic chain (e.g., joint 131-3 or base 136), a force sensor positioned adjacent a joint between one or more links of the first kinematic chain and the end effector (e.g., joint 131-1), or one or more contact sensors (e.g., sensor 321) on one or more links (e.g., on shell sensors). In some embodiments, the force sensor positioned adjacent a joint between one or more links and the robot arm end effector includes a six-axis load cell.

[0130] In some embodiments, the first kinematic chain is kinematically redundant. For example, the first kinematic chain has more degrees of freedom than are necessary to complete the medical task (e.g., the first kinematic chain has seven, eight, or more degrees of freedom). In some embodiments, the first robotic arm is kinematically redundant. In some embodiments, the combination of the first robotic arm and adjustable arm support is kinematically redundant.

[0131] The method 330 includes receiving (331) one or more parameters (e.g., from one or more sensors) of contact with the first kinematic chain detected by the one or more sensors.

[0132] In some embodiments, contact with the first kinematic chain includes contact between the first kinematic chain and an object that is not part of the medical robotic system (e.g., a patient, staff, or accessory).

[0133] In some embodiments, the one or more parameters of the contact include one or more selected from the group consisting of contact force information (including force and / or torque), contact position information, and contact direction information (which may be determined from the direction of movement and / or force of the first kinematic chain before and / or during contact between the first kinematic chain and the object) (332).

[0134] In some embodiments, the one or more parameters of the contact include information about whether the contact is with a moving object or a fixed object (which may be determined based on whether the position of the contact changes over time).

[0135] The method 330 also includes determining (333) a constraint associated with the first kinematic chain based on one or more parameters of the contact with the first kinematic chain.

[0136] In some embodiments, the method 330 includes updating the constraints and / or building a constraint map based on one or more parameters of a subsequent contact with the first kinematic chain detected by one or more sensors. For example, the medical robotic system 200 creates a constraint map (e.g., based on initial contact information) or updates a previously built constraint map (e.g., based on subsequent contact information).

[0137] In some embodiments, one or more parameters of the contact form part of a probability map, e.g., the contact information is converted into a probability that a particular object may be present at each location in three-dimensional space (thus the probability values ​​in the probability map represent the likelihood of contact or collision for each location or voxel).

[0138] In some embodiments, the probability map is determined based on the confidence of the contact detection, for example, an object (or contact) that is detected with a high degree of confidence may be assigned a high probability value because the object is more likely to be present at the corresponding location, and an object (or contact) that is detected with a low degree of confidence may be assigned a low probability value because the object is less likely to be present at the corresponding location.

[0139] In some embodiments, the method 330 includes updating the probability map based on the finite duration of the constraints. For example, the medical robotic system 200 may update the probability map at one or more time intervals. In some implementations, updating the probability map based on the finite duration of the constraints includes expiring (or removing) one or more constraints a certain period of time after such constraints were last updated in the probability map. This prevents old constraints from remaining on the probability map and interfering with the determination of an optimal configuration for the first kinematic chain.

[0140] In some embodiments, the method 330 includes updating the probability map based on the changing probability of the constraint. In some implementations, the medical robotic system 200 determines whether the contact was made with a stationary object or a dynamic, moving object (e.g., based on the contact location; e.g., a contact outside the tabletop 225 may be modeled as a contact with a moving object, and a contact on the tabletop 225 may be modeled as a contact with a stationary object). For contact with a dynamic object, the probability is reduced based on the likelihood that the dynamic object will not remain in the same location. For example, the probability map may be updated using a time decay function (or curve), which may be a linear or nonlinear decay function (e.g., an exponential decay function).

[0141] In some embodiments, the constraints are modeled (334) as a latent field (e.g., latent field 227-1) based at least in part on one or more parameters of the contact detected by one or more sensors. For example, the latent field is modeled as one or more locations at which forces are applied to one or more components of the first kinematic chain (and possibly components of other kinematic chains). In some embodiments, the modeled force on each component of the first kinematic chain due to the latent field may have a direction away from the location of the collision based on the distance of the respective component's location from the contact location.

[0142] In some embodiments, the latent field is also based on the probability of detecting a contact by each of the one or more sensors (335). For example, for contact detected by a sensor with high reliability / fidelity of detection (e.g., a sensor with low sensitivity), the modeled force is increased, and for contact detected by a sensor with low reliability / fidelity of detection (e.g., a sensor with high sensitivity), the modeled force is decreased. This increases the space available for the robotic arm and tool to maneuver by reducing the likelihood of contact with objects that are difficult to detect (e.g., due to the object's size or material) while reducing the force on objects that can be reliably and accurately detected. In some embodiments, each of the one or more sensors is assigned a predetermined detection probability (e.g., the medical robotic system 200 stores in memory a table of predetermined detection probability values ​​for each sensor or each sensor type).

[0143] In some embodiments, the constraint is modeled as a no-go zone (e.g., a volume that the components of the first kinematic chain are not allowed to enter). In some embodiments, the no-go zone has one or more boundaries that are defined based on one or more parameters of the contact (e.g., the size of the no-go zone is determined based on force information, and the shape of the no-go zone is determined based on directional and / or positional information).

[0144] The method 330 further includes adjusting the configuration of the first kinematic chain (e.g., by actuating one or more actuators coupled to or included in the first kinematic chain) from a first configuration to a second configuration (e.g., the second configuration is different from the first configuration) based on the constraint (336). The adjustment positions the first kinematic chain in a non-collision position to reduce the risk of a future collision.

[0145] In some embodiments, the first kinematic chain includes a first robotic arm (e.g., robot arm 205-1) and an adjustable arm support (e.g., adjustable arm support 210) on which the first robotic arm is positioned (e.g., the first robotic arm is mechanically coupled, such as rotatably coupled, to the adjustable arm support), and adjusting the configuration of the first kinematic chain includes changing the position of the adjustable arm support (337).

[0146] In some embodiments, the method includes utilizing the null space of the first kinematic chain to adjust (338) a configuration of the first kinematic chain from a first configuration to a second configuration.

[0147] In some embodiments, method 330 includes causing adjustments to the configuration of one or more other kinematic chains that are not in contact with one or more portions of the first kinematic chain based on constraints determined from one or more parameters of contact with the first kinematic chain detected by one or more sensors (e.g., moving robot arms 205-1 and 205-3 even though robot arms 205-1 and 205-3 are not in contact with robot arm 205-2, as shown in FIG. 29D ).

[0148] In some embodiments, the method 330 includes adjusting the configuration of one or more kinematic chains that are not in contact with the object (e.g., moving robotic arms 205-1 and 205-3 that are not in contact with the patient, as shown in FIG. 29D ) based on constraints determined from one or more parameters of contact with the first kinematic chain detected by one or more sensors.

[0149] In some embodiments, the method 330 further comprises performing a medical procedure. In some embodiments, the medical procedure comprises a surgical procedure.

[0150] C. Sensor Architecture for Detecting Objects in the Neighborhood As described above, the medical robotic system 200 may include one or more sensors for detecting contact with the kinematic chain (e.g., the robotic arm). In some embodiments, the medical robotic system 200 includes one or more sensors (e.g., non-contact proximity sensors) for detecting objects within the vicinity of the medical robotic system 200. Such sensors do not require contact and therefore may be used to adjust the configuration (or movement) of the kinematic chain and prevent contact before it occurs. Examples of such sensors include sonar, radar, LIDAR, ultrasonic sensors, light-based sensors, or vision-based sensors.

[0151] FIG. 31 illustrates sensors 314 mounted to detect nearby objects, according to some embodiments. In some embodiments, one or more sensors (e.g., sensors 314-1 through 314-5) are fixed to one or more of the robot links 132. In some embodiments, one or more sensors (e.g., sensors 314-6 and 314-7) are fixed to the exterior of the medical robotic system 200 (e.g., to a wall or ceiling). In some cases, one or more sensors 314 can serve as reference points for gathering information about the dynamic environment. In some embodiments, one or more sensors 314 are located either on a link or a joint between links that has maximum visibility to the object (e.g., a patient). In some embodiments, at least one robotic arm has one sensor. In some embodiments, at least one robotic arm has multiple sensors.

[0152] FIG. 32 shows an example of a robotic arm 205 having multiple sensors 314 for collecting information about a dynamic environment. In FIG. 32, the robotic arm 205 includes at least four sensors (four sensors 314-1 through 314-4 are shown in FIG. 32, although the robotic arm 205 may include additional sensors). Three sensors 314-1 through 314-3 are positioned on the distal link of the robotic arm 205, while one sensor 314-4 is positioned on the proximal link of the robotic arm 205. As shown in FIG. 32, different sensors 314 may be configured to detect different patches or regions of the environment. Sensors 314-1 and 314-2 detect different areas of the patient, sensor 314-3 detects medical staff (e.g., physician assistants, nurses, anesthesiologists, etc.), while sensor 314-4 detects nothing. A map of the environment can be generated from the information detected by the sensors 314.

[0153] FIG. 33 shows an example representation of a human (e.g., a patient) with a map based on information detected by one or more sensors 314 (or a single sensor), according to some embodiments. In FIG. 33, the human is represented as a cloud of points (e.g., a group of points or dots) in three-dimensional space (e.g., each point is associated with a three-dimensional coordinate). In some embodiments, each point has a probability value that indicates the likelihood that the point belongs to a particular object (e.g., a patient). In FIG. 33, the probability value is represented based on the size of the point (e.g., a larger point represents a higher probability that the point belongs to the object).

[0154] D. Using sensed information to generate a map of sensed objects FIG. 34 is a flow diagram illustrating a method for adjusting one or more kinematic chains based on detected object information, according to some embodiments.

[0155] The workflow shown in FIG. 34 begins with map initialization (operation 322). In some implementations, map initialization includes using an empty map. In such cases, the medical robotic system does not assume a priori knowledge of the environment (e.g., the location and size of objects). In some other implementations, map initialization includes selecting an initial patient body map from a pre-defined model of the patient's body model (a spatial model in the form of a grid or point cloud, a statistical model, or a deterministic model). In such cases, the map is initialized with a patient body map (e.g., a default patient body map or a patient body map selected or generated based on user input). For example, the patient body map may be generated based on the patient's body measurements (e.g., height, waist circumference, etc.). In some implementations, the initial patient body map has empty space around the modeled patient body.

[0156] The medical procedure begins, and the medical robotic system monitors the environment (operation 323) and updates the map with information about the detected object (operation 324). For example, as the robotic arm moves, sensors record the distance to the nearest object in its field of view. In some implementations, the medical robotic system determines whether the detected object belongs to the medical robotic system. If the detected object does not belong to the medical robotic system 200 and the object is within the scope of the medical procedure, the initial spatial model / statistical model or deterministic model (or map) is updated. The update can be based on any simultaneous localization and mapping (SLAM) algorithm or sensor fusion algorithm, such as a Kalman filter, a particle filter, and a covariance intersection algorithm. The update operation (operation 324) is repeated periodically. After several iterations, a spatial model of the environment (e.g., including the patient's body) with a high degree of confidence can be achieved.

[0157] The robot processor avoids collisions with the model if the model is sufficiently reliable and accurate, thereby eliminating the possibility of collision with the patient. The model can also be used to modify the bar placement during operation to improve efficiency (e.g., reduce arm-to-arm collisions).

[0158] In some cases, a new configuration of the kinematic chain is determined based on the updated map (operation 325), and the medical robotic system places the kinematic chain in the determined configuration (operation 326). The medical procedure continues while the kinematic chain is in the optimized configuration. As a result, the likelihood of the kinematic chain coming into contact with another object is reduced. This, in turn, improves the efficiency of the medical procedure by reducing collisions (e.g., between robotic arms or between a robotic arm and another object).

[0159] In some implementations, due to the dynamic nature of the environment, each boundary patch may be assigned a probability based on when and how the boundary patch was detected (e.g., the medical robotic system stores information indicating when and how information about a particular point was detected, such as a timestamp of the detection). For example, following a determination that the patch was determined with a high contact force (or with a sensor with high sensitivity), the medical robotic system assigns a high probability to the detected boundary of the object. In addition, the medical robotic system decreases the probability over time to reflect the fact that the object may have moved from its original position, thereby invalidating a boundary detected long ago. On the other hand, if the object continues to be detected in the same or similar position over time, the medical robotic system increases the probability assigned to the detected boundary of the object. In such cases, the location and shape of the object (or its boundary) may be approximated with greater accuracy. In some implementations, additional a priori knowledge may be used. For example, it is known that the patient is relatively fixed to the tabletop, while staff typically move around outside the bed. Thus, separate models may be generated based on the location of the sensor measurements (e.g., a patient model based on sensor measurements in the tabletop area, which may expire or decay over time, and a staff model based on sensor measurements outside the bed).

[0160] 35A-35G show the configuration of a robotic arm and corresponding map, according to some embodiments. In Figures 35A-35G, sensors are not shown so as not to obscure other aspects of the operation of the medical robotic system.

[0161] Figure 35A shows, on the left side of the figure, a medical robotic system with robotic arms 205-1 and 205-2, with patient 240 positioned on tabletop 225. Figure 35A also shows ceiling structure 291 (e.g., lighting fixtures). On the right side of Figure 35A, a graphical representation of an object map corresponding to the setup shown on the left side of Figure 35A is shown. The object map includes a map 241 of the patient (e.g., a point cloud representing the surface boundary of the patient) and also includes maps of one or more portions of tabletop 225 and ceiling structure 291.

[0162] Figure 35B shows, on the left side of the figure, that robotic arm 205-2 has moved (e.g., to a more optimal position or posture) based on patient map 241. Figure 35B also shows, on the left side of the figure, that medical personnel 242 has moved into proximity with robotic arm 205-1. On the right side of Figure 35B, a graphical representation of the updated object map is shown, including map 243 of medical personnel 242.

[0163] FIG. 35C shows, on the left side of the figure, that the robotic arm 205-1 moves based on the updated map, which includes the map 243 of the medical personnel.

[0164] Figure 35D shows, on the left side of the figure, that medical personnel 242 has moved away from robotic arm 205-1. However, on the right side of the figure, Figure 35D shows that medical personnel map 243 remains (at least for a certain period of time).

[0165] 35E shows, on the right side of the figure, that the map 243 of the medical personnel has been removed. In some implementations, the map 243 of the medical personnel (or any moving object) expires after a certain period of time (e.g., the map of the moving object is removed after a preset period of time). In some other implementations, the map 243 of the medical personnel (or any moving object) decays over time (e.g., the probability value of the map of the moving object decreases over time). Meanwhile, the patient 240 continues to be detected at the same location over time. In some implementations, the probability value of the map of the static object (e.g., the patient 240) increases over time.

[0166] Figure 35F shows, on the left side of the figure, that medical personnel 242 has moved into proximity with robotic arm 205-2. On the right side of Figure 35F, a graphical representation of another updated object map is shown, including a map 243 of medical personnel 242 to the right of patient 240.

[0167] FIG. 35G shows, on the left side of the figure, that the robotic arm 205-2 moves based on the updated map, which includes a map 243 of the medical personnel in their new position.

[0168] As shown in Figures 35A-35G, a medical robotic system can detect objects within its vicinity and adjust the configuration of the kinematic chain so that the risk of collision with the kinematic chain is reduced. Figures 35A-35G also show that certain objects are modeled differently in the map. For example, the map of a moving object may stale or decay over time, while the probability value of a static object may increase over time (or when a threshold time is reached).

[0169] In some embodiments, objects are modeled using buffer zones in the map. Allowing the kinematic chain to move immediately adjacent to the object's boundary can cause the kinematic chain to come into contact with the object due to various reasons, such as measurement errors, modeling errors, and object movement. Providing a buffer zone (e.g., a fixed area or volume with a boundary at a certain distance from the object's boundary) can reduce the likelihood of contact between the kinematic chain and the object. In some embodiments, the buffer distance db of the buffer zone is determined based on various factors (e.g., detection probability, detection confidence, etc.), as shown in FIG. 36A . For example, for two objects 244 and 245 with the same physical size (and shape), if object 244 is a static object and object 245 is a dynamic, moving object, their buffer zones 246 and 247 can have different sizes.

[0170] 37 is a flow diagram illustrating a method 370 for adjusting a configuration of a robotic arm based on sensor information, according to some embodiments. The method 330 is performed by an electronic device (e.g., one or more processors, such as the processor 380 described with respect to FIG. 38) in communication with a medical robotic system (e.g., the medical robotic system 200 having the robotic arm 205 and one or more sensors described with respect to FIG. 31) that includes a first robotic arm and one or more sensors positioned to detect objects within a proximity of the first robotic arm.

[0171] In some embodiments, the one or more sensors include at least one or more of a sonar, radar, LIDAR, ultrasonic, light-based sensor, or vision-based sensor.

[0172] In some embodiments, the one or more sensors include at least one non-contact sensor, hi some embodiments, the one or more sensors include at least one contact sensor in addition to the at least one non-contact sensor.

[0173] In some embodiments, the first robotic arm is remotely controlled. In some embodiments, the stored instructions, when executed by the one or more processors, cause the one or more processors to receive control signals from an input device located separately from the one or more processors. In some embodiments, the input device is located separately from the first robotic arm or any other robotic arm.

[0174] In some embodiments, the first robotic arm is kinematically redundant, e.g., the first robotic arm has more degrees of freedom than are necessary to complete the medical task (e.g., the first robotic arm has seven, eight, nine, or more degrees of freedom, with or without associated adjustable arm supports).

[0175] In some embodiments, the medical robotic system includes a mobile patient platform, hi some embodiments, the mobile patient platform includes a rigid base and a tabletop that is movable relative to the rigid base.

[0176] The method 370 includes receiving (371) sensor information from one or more sensors corresponding to the position of one or more objects within a proximity of a first robotic arm (e.g., at a first time).

[0177] The method 370 also includes generating or updating (372) an object map (e.g., a data structure indicating the location and / or size of objects adjacent to the medical robotic system, particularly the first robotic arm) based on the sensor information, where the object map characterizes the spatial relationships of objects within the vicinity of the first robotic arm. In some embodiments, the object map characterizes the spatial relationships of objects adjacent to the medical robotic system. By utilizing multiple sensors, it is possible to detect objects that pass through occlusions. For example, an object may be located behind an obstacle in a particular sensor's field of view. However, the object may be detected by one or more other sensors viewing the object from a different angle. Thus, by utilizing multiple sensors, objects can be detected and their locations determined even when there is an obstacle obscuring the object in a particular field of view.

[0178] The method 370 further includes adjusting 373 a configuration of the first robot arm from a first configuration to a second configuration (e.g., the second configuration is different from the first configuration) based on the object map. Adjusting the configuration of the first robot arm reduces a risk of collision between the first robot arm and the detected object.

[0179] In some embodiments, the medical robotic system includes one or more robotic arms other than the first robotic arm and one or more second sensors positioned to detect the presence of objects within a vicinity of the one or more robotic arms. The method 370 further includes receiving second sensor information from the one or more second sensors corresponding to one or more positional locations of one or more objects (e.g., the same object and / or different objects represented in the first sensor information) within a vicinity of the one or more robotic arms, generating or updating an object map also based on the second sensor information, and adjusting a configuration of the one or more robotic arms based on the object map.

[0180] In some embodiments, after generating or updating the object map, the method 370 includes repeating (374) receiving subsequent sensor information from one or more sensors corresponding to the positions of one or more objects within a vicinity of the first robotic arm, updating the object map based on the subsequent sensor information, and adjusting the configuration of the first robotic arm according to the object map being updated based on the subsequent sensor information.

[0181] In some embodiments, method 370 optionally includes updating 375 the object map based on the probability of detecting each of the one or more objects. For example, objects with a low probability of detection (e.g., objects detected at frequencies below a threshold frequency and therefore less likely to be detected) are modeled with a buffer area to reduce the probability of collision with the object, and objects with a high probability of detection (e.g., objects detected at frequencies above a threshold frequency and therefore more likely to be detected) are modeled without a buffer area or with a smaller buffer area.

[0182] In some embodiments, the one or more objects include dynamically moving objects. For example, the object is located at a first location at a first time and at a second location different from the first location at a second time different from the first time. The dynamically moving object may be a patient, staff member, or accessory. In some embodiments, the object dynamically moves based on a configuration (e.g., kinematic information) of the medical robotic system (e.g., the object changes its position based on the configuration of the first robotic arm or any other robotic arm). For example, the object is a patient whose position changes based on the configuration of the patient platform (e.g., an operating table). In other embodiments, the object is a bedside staff member attempting to get out of the way of the robotic arm while it is moving. In some embodiments, the method further includes removing (376) the update to the object map (or updating the object map to reduce or eliminate the object's influence on the object map, or removing the object from the object map) after a period of time after the object map is updated to reflect the object. For example, if an object is detected at location A, an area near location A is marked on the object map. After a certain amount of time, the area around location A is no longer marked in the object map. This does not apply to objects that remain in the same location. For example, one or more processors may cease removing updates to the object map or may keep the object in the object map pursuant to a determination that the object continues to be detected (e.g., around the same location).

[0183] In some embodiments, adjusting the configuration of the first robotic arm increases the distance between the first robotic arm and the dynamic object such that the risk of a collision between the first robotic arm and the dynamic object is reduced.

[0184] In some embodiments, the one or more objects include static objects. In some embodiments, the method 370 includes maintaining the static objects in the object map (or maintaining an update of the object map for the static objects) by continuing to detect the static objects (e.g., around the same location) based on the sensor information.

[0185] In some embodiments, the method 370 includes updating (377) the object map based also on the configuration (e.g., kinematic information) of the medical robotic system (e.g., the configuration of the first robotic arm and / or any other robotic arms).

[0186] In some embodiments, the method 370 further includes performing a medical procedure. In some embodiments, the medical procedure includes a surgical procedure.

[0187] E. Configuration decisions As described above, the medical robotic system determines a new configuration of the kinematic chains based on sensor information (e.g., contact information and / or detected object information). There are certain conditions for the new configuration, such as the ADM 134 of the robot arm 205 and / or its coupled remote motion center (RCM) being kept in a static pose / position, while the distance between each kinematic chain and the detected object and the distance between any two kinematic chains need to be increased (to reduce the possibility of contact and provide an expanded workspace for manipulating the kinematic chains). While there are many ways to determine a new configuration based on these conditions, one way to determine a new configuration is based on a cost function (also called a loss function). For example, the cost function can include a penalty or points based on the conditions for the new configuration, and the new configuration is selected based on parameters (e.g., the positions of each component of the kinematic chain) that minimize or maximize the cost function.

[0188] In some implementations, the following optimization process can be performed to maximize the workspace of a medical robotic system. The goal is to maximize the minimum distance of each joint position to its joint limit (increasing the amount of movement to the joint limit reduces the likelihood of any joint reaching its joint limit) and the minimum distance between any two robot arms (reducing the likelihood of collision between the two robot arms) while maintaining the remote center position of each robot arm. Assuming there are six robot arms in total, with the first through third robot arms on one base and the fourth through sixth robot arms on another base, the cost function can be written as follows:

[0189]

number

[0190]

number

[0191] If the magnitude of the contact, either the force or torque magnitude or both, are known and used, the optimization may be performed as an online process so that the improvement in contact reduction can be measured during the optimization. The following modified cost function may be used:

[0192]

number

[0193]

number

[0194] To enable offline optimization, additional information of the coarse contact position and contact direction can be utilized to estimate the position of the object so that an estimated distance between the robot arm and the object can be calculated.

[0195] When coarse position is used without contact directional information, assuming that a contact with magnitudes |Fi,j| and |Ti,j| is detected on link i of robot arm j, the position of the object can be estimated to be min(kF / |Fi,j|,kT / |Ti,j|) away from the contact link along its perpendicular bisector, denoted as Oi,j. The distance between the contact link and the object can be estimated as ri,j(qj). For links ri where no contact was detected, j(qj)=0. A new cost function that also considers the contact distance is:

[0196]

number

[0197]

number

[0198] If contact direction information is available along with the coarse contact position, a more accurate object position can be estimated. i,j is vec i,j +k F F i,j / |F i,j | 2 can be estimated as i,j teeth,

[0199]

number

[0200] The distance between the contact link and the object can then be estimated in the same manner as described above. The estimated distance is r' i,j (q j ) In some implementations, for links on revolute joints, the optimization should include orienting the angle between the contact direction and the longitudinal link direction to 90°. i,j For contact detected on link i of robot arm j along i,j (q j )=arccos(dir i,j link i,j ) angle q between j is a function of link i,j The new cost function that also takes into account the contact direction is:

[0201]

number

[0202]

number

[0203] 3. Implementation system and terminology FIG. 38 is a schematic diagram showing electronic components of a medical robotic system, according to some embodiments.

[0204] The medical robotic system includes one or more processors 380 in communication with a computer-readable storage medium 382 (e.g., computer memory devices such as random access memory, read-only memory, static random access memory, and non-volatile memory, as well as other storage devices such as hard drives, optical disks, magnetic tape recordings, or any combination thereof) that stores instructions for performing any of the methods described herein (e.g., the operations described with respect to FIGS. 30 and 37). The one or more processors 380 also communicate (via a system bus or any suitable electrical circuitry) with an input / output controller 384. The input / output controller 384 receives sensor data from one or more sensors 388-1, 388-2, etc., and relays the sensor data to the one or more processors 380. The input / output controller 384 also receives instructions and / or data from the one or more processors 380 and relays the instructions and / or data to one or more actuators, such as first motors 387-1 and 387-2. In some embodiments, the input / output controller 384 is coupled to one or more actuator controllers 386 and provides instructions and / or data to at least a subset of the one or more actuator controllers 386, which in turn provide control signals to selected actuators. In some embodiments, one or more actuator controllers 386 are integrated with the input / output controller 384, which provides control signals directly to one or more actuators 387 (without a separate actuator controller). While FIG. 38 shows that there is one actuator controller 386 (e.g., one actuator controller for the entire mobile medical platform), in some embodiments, additional actuator controllers (e.g., one actuator controller for each actuator, etc.) may be used.

[0205] Implementations disclosed herein provide systems, methods, and apparatus for medical robotic systems that can optimize the configuration of a kinematic chain based on the positions of objects in the vicinity of the kinematic chain.

[0206] It should be noted that, as used herein, the terms "couple," "coupled," "coupled," or other variations of the word coupled, can indicate either an indirect connection or a direct connection. For example, when a first component is "coupled" to a second component, the first component may be either indirectly connected to the second component through another component, or directly connected to the second component.

[0207] The functions for power-assisted mobilization of a mobile medical platform described herein may be stored as one or more instructions on a processor-readable medium 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 media may include 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. Note that computer-readable media may be tangible and non-transitory. As used herein, the term "code" may refer to software, instructions, code, or data that is executable by a computing device or processor.

[0208] The methods disclosed herein comprise one or more steps or actions for achieving the described method. Method steps and / or actions may be interchanged without departing from the scope of the claims. In other words, unless a specific order of steps or actions is required for the proper operation of the described method, the order and / or use of specific steps and / or actions may be modified without departing from the scope of the claims.

[0209] As used herein, the term "plurality" refers to two or more than two. For example, a plurality of elements refers to two or more elements. The term "determining" encompasses a wide variety of acts, and thus "determining" can include calculating, computing, processing, calculating, investigating, looking up (e.g., viewing a table, database, or another data structure), ascertaining, and the like. "Determining" can also include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), and the like. "Determining" can also include resolving, selecting, electing, establishing, and the like.

[0210] 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."

[0211] As used herein, the phrase "proximity of a medical robotic system" may refer to the detection range of a sensor (e.g., at least one of the sensors may detect an object within the proximity of the medical robotic system) or the range of movement of a kinematic chain. In some cases, the phrase "within proximity" also encompasses "within the same room," "within field of view," adjacent, or nearby.

[0212] 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 general principles defined herein may be applied to other implementations without departing from the scope of the present invention. For example, those skilled in the art will recognize that many corresponding alternative and equivalent structural details may be employed, such as equivalent ways of fastening, mounting, coupling, or engaging tool components, equivalent mechanisms for producing specific 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.

[0213] Some embodiments or implementations are described with reference to the following clauses.

[0214] Article 1. A medical robotic system comprising: a first robotic arm; one or more sensors positioned to detect the presence of an object adjacent to the first robotic arm; one or more processors in communication with the one or more sensors; a memory storing instructions that, when executed by one or more processors, cause the one or more processors to: receiving first sensor information from one or more sensors corresponding to one or more positional locations of one or more objects within a vicinity of the first robotic arm; generating or updating an object map based on the first sensor information, the object map characterizing a spatial relationship of objects adjacent to the first robotic arm; and adjusting a configuration of a first robotic arm from a first configuration to a second configuration based on the object map.

[0215] Article 2. one or more robotic arms other than the first robotic arm; one or more second sensors positioned to detect the presence of an object within a proximity of the one or more robotic arms; The stored instructions, when executed by one or more processors, cause the one or more processors to: receiving second sensor information from one or more second sensors corresponding to one or more positional locations of one or more objects within a vicinity of the one or more robotic arms; generating or updating an object map based also on the second sensor information; and adjusting the configuration of one or more robotic arms based on the object map.

[0216] Clause 3. The medical robotic system of clause 1 or 2, wherein the one or more sensors include at least one or more of a sonar, radar, LIDAR, ultrasound, light-based sensor, or vision-based sensor.

[0217] Clause 4. A medical robot system according to any one of clauses 1 to 3, wherein the one or more sensors include at least one non-contact sensor.

[0218] Clause 5. The stored instructions, when executed by one or more processors, cause the one or more processors to, after generating or updating an object map: receiving subsequent sensor information from the one or more sensors corresponding to the position of one or more objects adjacent to the first robotic arm; updating the object map based on subsequent sensor information; A medical robot system as described in any one of clauses 1 to 4, further comprising: adjusting the configuration of the first robot arm according to an object map that is updated based on subsequent sensor information; and repeating the process.

[0219] Clause 6. A medical robotic system as described in Clause 5, wherein the stored instructions, when executed by the one or more processors, further cause the one or more processors to update the object map based on the probability of detecting each of the one or more objects.

[0220] Clause 7. A medical robot system according to any one of clauses 1 to 6, wherein the first robot arm is remotely controlled.

[0221] Clause 8. A medical robot system according to any one of clauses 1 to 7, wherein the first robot arm is kinematically redundant.

[0222] Clause 9. A medical robot system according to any one of clauses 1 to 8, wherein the one or more objects include a dynamically moving object.

[0223] Clause 10. The medical robotic system of clause 9, wherein the object moves dynamically based on the configuration of the medical robotic system.

[0224] Clause 11. A medical robotic system as described in clause 9 or 10, wherein the stored instructions, when executed by the one or more processors, further cause the one or more processors to remove updates to the object map after a period of time after the object map has been updated to reflect the object.

[0225] Clause 12. A medical robotic system according to any one of clauses 1 to 11, wherein the one or more objects include a static object.

[0226] Clause 13. A medical robotic system as described in any one of clauses 1 to 12, wherein the stored instructions, when executed by the one or more processors, cause the one or more processors to update the object map based also on the configuration of the medical robotic system.

[0227] Clause 14. The medical robotic system of any one of clauses 1 to 13, further comprising a movable patient platform.

[0228] Article 15. A medical robotic system, comprising: a first robotic arm; one or more sensors positioned to detect the presence of a dynamic object within a vicinity of the first robotic arm; one or more processors in communication with the one or more sensors; a memory storing instructions that, when executed by one or more processors, cause the one or more processors to: receiving sensor information from one or more sensors corresponding to a position of a dynamic object within a vicinity of the first robotic arm; generating or updating an object map based on the sensor information, the object map characterizing spatial relationships of objects within a vicinity of the first robotic arm; and adjusting a configuration of a first robotic arm from a first configuration to a second configuration based on the object map.

[0229] Clause 16. The medical robotic system of clause 15, wherein adjusting the configuration of the first robotic arm increases the distance between the first robotic arm and the dynamic object such that the risk of collision between the first robotic arm and the dynamic object is reduced.

[0230] Clause 17. A method performed by an electronic device in communication with a medical robotic system including a first robotic arm and one or more sensors positioned to detect the presence of an object within a proximity of the first robotic arm, the method comprising: receiving sensor information from one or more sensors corresponding to the position of one or more objects within a vicinity of the first robotic arm; generating or updating an object map based on the sensor information, the object map characterizing spatial relationships of objects within a vicinity of the first robotic arm; and adjusting a configuration of the first robotic arm from a first configuration to a second configuration based on the object map.

[0231] Article 18. After generating or updating the object map, receiving subsequent sensor information from one or more sensors corresponding to the position of one or more objects within a vicinity of the first robotic arm; updating the object map based on subsequent sensor information; 18. The method of clause 17, further comprising adjusting the configuration of the first robotic arm according to the object map being updated based on subsequent sensor information, and repeating.

[0232] Clause 19. The method of clause 17 or 18, further comprising updating the object map based on the probability of detecting each object of the one or more objects.

[0233] Article 20. the one or more objects include a dynamically moving object; 20. The method of any one of clauses 17 to 19, wherein the method further comprises removing updates to the object map after a period of time after the object map has been updated to reflect the object.

[0234] Clause 21. The method of any one of clauses 17 to 20, further comprising updating the object map based on the configuration of the medical robotic system.

[0235] Clause 22. An electronic device, one or more processors; a memory storing instructions that, when executed by one or more processors, cause the one or more processors to: receiving, from one or more sensors, sensor information corresponding to a position of one or more objects within a vicinity of a first robotic arm of the medical robotic system; generating or updating an object map based on the sensor information, the object map characterizing spatial relationships of objects within a vicinity of the first robotic arm; and adjusting a configuration of the first robotic arm from a first configuration to a second configuration based on the object map.

[0236] Clause 23. The stored instructions, when executed by one or more processors, cause the one or more processors to: After generating or updating the object map, receiving subsequent sensor information from one or more sensors corresponding to the position of one or more objects within a vicinity of the first robotic arm; updating the object map based on subsequent sensor information; and adjusting the configuration of the first robotic arm according to an object map that is updated based on subsequent sensor information.

[0237] Clause 24. An electronic device as described in clause 22 or 23, wherein the stored instructions, when executed by the one or more processors, cause the one or more processors to update the object map based on the probability of detecting each of the one or more objects.

[0238] Article 25. the one or more objects include a dynamically moving object; 25. The electronic device of any one of clauses 22 to 24, wherein the stored instructions, when executed by the one or more processors, cause the one or more processors to remove updates to the object map after a period of time after the object map has been updated to reflect the object.

[0239] Clause 26. An electronic device described in any one of clauses 22 to 25, wherein the stored instructions, when executed by one or more processors, cause the one or more processors to update the object map based on the configuration of the medical robotic system.

[0240] Clause 27. A computer-readable storage medium storing instructions for execution by one or more processors of an electronic device, the stored instructions comprising: receiving sensor information corresponding to the position of one or more objects adjacent to a first robotic arm of a medical robotic system; generating or updating an object map based on the sensor information, the object map characterizing a spatial relationship of objects adjacent to the first robotic arm; and causing an adjustment of a configuration of the first robotic arm from a first configuration to a second configuration based on the object map.

[0241] Clause 28. A computer-readable storage medium according to clause 27, wherein the stored instructions also include instructions for carrying out the method of any one of clauses 18 to 21.

[0242] [Embodiment] (1) A medical robot system, a first robotic arm; one or more sensors positioned to detect the presence of an object adjacent to the first robotic arm; one or more processors in communication with the one or more sensors; a memory storing instructions that, when executed by the one or more processors, cause the one or more processors to: receiving first sensor information from the one or more sensors corresponding to one or more positional locations of one or more objects within a vicinity of the first robotic arm; generating or updating an object map based on the first sensor information, the object map characterizing a spatial relationship of objects adjacent to the first robotic arm; adjusting a configuration of the first robotic arm from a first configuration to a second configuration based on the object map; a memory for performing the A medical robot system comprising: (2) one or more robot arms other than the first robot arm; one or more second sensors positioned to detect the presence of an object within a vicinity of the one or more robotic arms; The stored instructions, when executed by the one or more processors, cause the one or more processors to: receiving second sensor information from the one or more second sensors corresponding to one or more positional locations of one or more objects within a vicinity of the one or more robotic arms; generating or updating the object map based also on the second sensor information; adjusting a configuration of the one or more robotic arms based on the object map; A medical robot system as described in embodiment 1, which performs the following. (3) The medical robot system of embodiment 1, wherein the one or more sensors include at least one or more of a sonar, radar, LIDAR, ultrasound, light-based sensor, or vision-based sensor. (4) A medical robot system as described in embodiment 1, wherein the one or more sensors include at least one non-contact sensor. (5) The stored instructions, when executed by the one or more processors, cause the one or more processors to, after generating or updating the object map: receiving subsequent sensor information from the one or more sensors corresponding to the position of one or more objects adjacent to the first robotic arm; updating the object map based on the subsequent sensor information; adjusting the configuration of the first robotic arm according to the object map being updated based on the subsequent sensor information; A medical robot system as described in embodiment 1, further comprising repeating the steps of:

[0243] (6) A medical robot system as described in embodiment 5, wherein the stored instructions, when executed by the one or more processors, further cause the one or more processors to update the object map based on a probability of detecting each of the one or more objects. (7) A medical robotic system as described in embodiment 1, wherein the first robotic arm is remotely controlled. (8) A medical robotic system as described in embodiment 1, wherein the first robotic arm is kinematically redundant. (9) A medical robot system as described in embodiment 1, wherein the one or more objects include a dynamically moving object. (10) A medical robot system as described in embodiment 9, wherein the object moves dynamically based on the configuration of the medical robot system.

[0244] (11) A medical robot system as described in embodiment 9, wherein the stored instructions, when executed by the one or more processors, further cause the one or more processors to remove the update to the object map a period of time after the object map has been updated to reflect the object. (12) A medical robot system as described in embodiment 1, wherein the one or more objects include a static object. (13) A medical robotic system as described in embodiment 1, wherein the stored instructions, when executed by the one or more processors, cause the one or more processors to update the object map based also on the configuration of the medical robotic system. (14) The medical robotic system of embodiment 1, further comprising a movable patient platform. (15) A medical robot system, a first robotic arm; one or more sensors positioned to detect the presence of a dynamic object within a vicinity of the first robotic arm; one or more processors in communication with the one or more sensors; a memory storing instructions that, when executed by the one or more processors, cause the one or more processors to: receiving sensor information from the one or more sensors corresponding to a position of the dynamic object within a vicinity of the first robotic arm; generating or updating an object map based on the sensor information, the object map characterizing spatial relationships of objects within a vicinity of the first robotic arm; adjusting a configuration of the first robotic arm from a first configuration to a second configuration based on the object map; a memory for performing the A medical robot system comprising:

[0245] (16) The medical robotic system of embodiment 15, wherein adjusting the configuration of the first robotic arm increases the distance between the first robotic arm and the dynamic object such that the risk of collision between the first robotic arm and the dynamic object is reduced. (17) A method performed by an electronic device in communication with a medical robotic system including a first robotic arm and one or more sensors positioned to detect the presence of an object within a proximity of the first robotic arm, the method comprising: receiving sensor information from the one or more sensors corresponding to the position of one or more objects within a vicinity of the first robotic arm; generating or updating an object map based on the sensor information, the object map characterizing spatial relationships of objects within a vicinity of the first robotic arm; adjusting a configuration of the first robotic arm from a first configuration to a second configuration based on the object map; A method comprising: (18) After generating or updating the object map, receiving subsequent sensor information from the one or more sensors corresponding to the position of one or more objects within a vicinity of the first robotic arm; updating the object map based on the subsequent sensor information; adjusting the configuration of the first robotic arm according to the object map being updated based on the subsequent sensor information; 18. The method of embodiment 17, further comprising repeating (19) The method of embodiment 17, further comprising updating the object map based on a probability of detecting each object among the one or more objects. (20) The one or more objects include a dynamically moving object, The method further includes removing the updates to the object map a period of time after the object map has been updated to reflect the object. The method of embodiment 17.

[0246] (21) The method of embodiment 17, further comprising updating the object map based on a configuration of the medical robotic system. (22) An electronic device, one or more processors; a memory storing instructions that, when executed by the one or more processors, cause the one or more processors to: receiving, from one or more sensors, sensor information corresponding to a position of one or more objects within a vicinity of a first robotic arm of the medical robotic system; generating or updating an object map based on the sensor information, the object map characterizing spatial relationships of objects within a vicinity of the first robotic arm; adjusting a configuration of the first robotic arm from a first configuration to a second configuration based on the object map; and a memory for causing the electronic device to perform the above. (23) The stored instructions, when executed by the one or more processors, cause the one or more processors to: After generating or updating the object map, receiving subsequent sensor information from the one or more sensors corresponding to a position of one or more objects within a vicinity of the first robotic arm; updating the object map based on the subsequent sensor information; adjusting the configuration of the first robotic arm according to the object map being updated based on the subsequent sensor information; An electronic device as described in embodiment 22, which causes the following to be repeated. (24) The electronic device of embodiment 22, wherein the stored instructions, when executed by the one or more processors, cause the one or more processors to update the object map based on a probability of detecting each of the one or more objects. (25) The one or more objects include a dynamically moving object, An electronic device as described in embodiment 22, wherein the stored instructions, when executed by the one or more processors, cause the one or more processors to remove the update to the object map a period of time after the object map has been updated to reflect the object.

[0247] (26) The electronic device of embodiment 22, wherein the stored instructions, when executed by the one or more processors, cause the one or more processors to update the object map based on a configuration of the medical robotic system. (27) A computer-readable storage medium storing instructions for execution by one or more processors of an electronic device, the stored instructions comprising: receiving sensor information corresponding to the position of one or more objects adjacent to a first robotic arm of a medical robotic system; generating or updating an object map based on the sensor information, the object map characterizing a spatial relationship of objects adjacent to the first robotic arm; adjusting a configuration of the first robotic arm from a first configuration to a second configuration based on the object map; 10. A computer-readable storage medium containing instructions for:

Claims

1. A medical robot system, comprising: a first robotic arm; one or more sensors positioned to detect the presence of an object adjacent to the first robotic arm; one or more processors in communication with the one or more sensors; a memory storing instructions that, when executed by the one or more processors, cause the one or more processors to: receiving first sensor information from the one or more sensors corresponding to one or more positional locations of one or more objects within a proximity of the first robotic arm; generating or updating an object map based on the first sensor information, the object map characterizing a spatial relationship of objects adjacent to the first robotic arm; adjusting a configuration of the first robotic arm from a first configuration to a second configuration based on the object map; a memory for performing the Equipped with A medical robot system, wherein when generating or updating the object map, a buffer zone is provided having a boundary at a specific distance from a boundary of the object to reduce the possibility of contact between the first robot arm and the object, and the size of the buffer zone when the object is a dynamic, moving first object is larger than the size of the buffer zone when the object is a static, second object having the same size and shape as the first object.

2. one or more robot arms other than the first robot arm; one or more second sensors positioned to detect the presence of an object within a vicinity of the one or more robotic arms; The stored instructions, when executed by the one or more processors, cause the one or more processors to: receiving second sensor information from the one or more second sensors corresponding to one or more positional locations of one or more objects within a vicinity of the one or more robotic arms; generating or updating the object map based also on the second sensor information; adjusting a configuration of the one or more robotic arms based on the object map; The medical robot system according to claim 1 ,

3. 10. The medical robotic system of claim 1, wherein the one or more sensors include at least one or more of a sonar, radar, LIDAR, ultrasonic, light-based sensor, or vision-based sensor.

4. The medical robotic system of claim 1 , wherein the one or more sensors include at least one non-contact sensor.

5. The stored instructions, when executed by the one or more processors, cause the one or more processors to, after generating or updating the object map: receiving subsequent sensor information from the one or more sensors corresponding to the position of one or more objects adjacent to the first robotic arm; updating the object map based on the subsequent sensor information; adjusting the configuration of the first robotic arm according to the object map being updated based on the subsequent sensor information; The medical robot system of claim 1 , further comprising:

6. The medical robotic system of claim 1 , wherein the first robotic arm is remotely controlled.

7. The medical robotic system of claim 1 , wherein the first robotic arm is kinematically redundant.

8. The medical robotic system of claim 1 , wherein the one or more objects include a dynamically moving object.

9. The medical robotic system of claim 8 , wherein the object moves dynamically based on a configuration of the medical robotic system.

10. The medical robotic system of claim 1 , wherein the one or more objects include a static object.

11. 2. The medical robotic system of claim 1, wherein the stored instructions, when executed by the one or more processors, cause the one or more processors to update the object map based also on a configuration of the medical robotic system.

12. The medical robotic system of claim 1 , further comprising a mobile patient platform.

13. A medical robot system, comprising: a first robotic arm; one or more sensors positioned to detect the presence of a dynamic object within a vicinity of the first robotic arm; one or more processors in communication with the one or more sensors; a memory storing instructions that, when executed by the one or more processors, cause the one or more processors to: receiving sensor information from the one or more sensors corresponding to a position of the dynamic object within a vicinity of the first robotic arm; generating or updating an object map based on the sensor information, the object map characterizing spatial relationships of objects within a vicinity of the first robotic arm; adjusting a configuration of the first robotic arm from a first configuration to a second configuration based on the object map; a memory for performing the Equipped with A medical robot system, wherein when generating or updating the object map, a buffer zone is provided having a boundary at a specific distance from a boundary of the object to reduce the possibility of contact between the first robot arm and the object, and the size of the buffer zone when the object is a dynamic, moving first object is larger than the size of the buffer zone when the object is a static, second object having the same size and shape as the first object.

14. 14. The medical robotic system of claim 13, wherein adjusting the configuration of the first robotic arm increases the distance between the first robotic arm and the dynamic object such that a risk of collision between the first robotic arm and the dynamic object is reduced.

15. 1. A method executed by an electronic device in communication with a medical robotic system including a first robotic arm and one or more sensors positioned to detect the presence of an object within a proximity of the first robotic arm, the method comprising: receiving, by the electronic device, sensor information from the one or more sensors corresponding to the position of one or more objects within a proximity of the first robotic arm; generating or updating an object map based on the sensor information, the object map characterizing spatial relationships of objects within a vicinity of the first robotic arm; adjusting a configuration of the first robotic arm from a first configuration to a second configuration based on the object map by the electronic device; Including, 1. A method executed by an electronic device, wherein when the electronic device generates or updates the object map, the electronic device provides a buffer zone having a boundary at a specific distance from a boundary of the object to reduce the possibility of contact between the first robot arm and the object, wherein the size of the buffer zone when the object is a dynamic, moving first object is larger than the size of the buffer zone when the object is a static, second object having the same size and shape as the first object.

16. After the electronic device generates or updates the object map, receiving, by the electronic device, subsequent sensor information from the one or more sensors corresponding to the position of one or more objects within a vicinity of the first robotic arm; updating the object map by the electronic device based on the subsequent sensor information; the electronic device adjusting the configuration of the first robotic arm according to the object map being updated based on the subsequent sensor information; 16. The electronic device-implemented method of claim 15, further comprising repeating:

17. The electronic device-implemented method of claim 15 , further comprising the electronic device updating the object map based on a configuration of the medical robotic system.

18. 1. An electronic device comprising: one or more processors; a memory storing instructions that, when executed by the one or more processors, cause the one or more processors to: receiving, from one or more sensors, sensor information corresponding to a position of one or more objects within a proximity of a first robotic arm of a medical robotic system; generating or updating an object map based on the sensor information, the object map characterizing spatial relationships of objects within a vicinity of the first robotic arm; adjusting a configuration of the first robotic arm from a first configuration to a second configuration based on the object map; and a memory for causing the An electronic device, when generating or updating the object map, providing a buffer zone having a boundary at a specific distance from a boundary of the object to reduce the possibility of contact between the first robot arm and the object, wherein the size of the buffer zone when the object is a dynamic, moving first object is larger than the size of the buffer zone when the object is a static, second object having the same size and shape as the first object.

19. The stored instructions, when executed by the one or more processors, cause the one or more processors to: After generating or updating the object map, receiving subsequent sensor information from the one or more sensors corresponding to the position of one or more objects within a vicinity of the first robotic arm; updating the object map based on the subsequent sensor information; adjusting the configuration of the first robotic arm according to the object map being updated based on the subsequent sensor information; The electronic device of claim 18 , wherein the electronic device repeats the steps of:

20. 20. The electronic device of claim 18, wherein the stored instructions, when executed by the one or more processors, cause the one or more processors to update the object map based on a configuration of the medical robotic system.

21. 1. A computer-readable storage medium storing instructions for execution by one or more processors of an electronic device, the stored instructions comprising: receiving sensor information corresponding to the position of one or more objects adjacent to a first robotic arm of a medical robotic system; generating or updating an object map based on the sensor information, the object map characterizing a spatial relationship of objects adjacent to the first robotic arm; adjusting a configuration of the first robotic arm from a first configuration to a second configuration based on the object map; Includes instructions for A computer-readable storage medium, wherein when generating or updating the object map, a buffer zone having a boundary at a specific distance from a boundary of the object is provided to reduce the possibility of contact between the first robot arm and the object, wherein the size of the buffer zone when the object is a dynamic, moving first object is larger than the size of the buffer zone when the object is a static, second object having the same size and shape as the first object.

Images