Sterile handle for controlling a robotic surgical system from a sterile field

Description

BACKGROUND

Robotic-assisted surgical systems have been developed to improve surgical precision and enable the implementation of new surgical procedures. For example, robotic systems have been developed to sense a surgeon's hand movements and translate them to scaled-down micro-movements and filter out unintentional tremors for precise microsurgical techniques in organ transplants, reconstructions, and minimally invasive surgeries. Other robotic systems are directed to telemanipulation of surgical tools such that the surgeon does not have to be present in the operating room, thereby facilitating remote surgery. Feedback-controlled robotic systems have also been developed to provide smoother manipulation of a surgical tool during a procedure than could be achieved by an unaided surgeon.

However, widespread acceptance of robotic systems by surgeons and hospitals is limited for a variety of reasons. Current systems are expensive to own and maintain. They often require extensive preoperative surgical planning prior to use, and they extend the required preparation time in the operating room. They are physically intrusive, possibly obscuring portions of a surgeon's field of view and blocking certain areas around the operating table, such that a surgeon and/or surgical assistants are relegated to one side of the operating table. Current systems may also be non-intuitive or otherwise cumbersome to use, particularly for surgeons who have developed a special skill or “feel” for performing certain maneuvers during surgery and who find that such skill cannot be implemented using the robotic system. Finally, robotic surgical systems may be vulnerable to malfunction or operator error, despite safety interlocks and power backups.

Spinal surgeries often require precision drilling and placement of screws or other implements in relation to the spine, and there may be constrained access to the vertebrae during surgery that makes such maneuvers difficult. Catastrophic damage or death may result from improper drilling or maneuvering of the body during spinal surgery, due to the proximity of the spinal cord and arteries. Common spinal surgical procedures include a discectomy for removal of all or part of a disk, a foraminotomy for widening of the opening where nerve roots leave the spinal column, a laminectomy for removal of the lamina or bone spurs in the back, and spinal fusion for fusing of two vertebrae or vertebral segments together to eliminate pain caused by movement of the vertebrae.

Spinal surgeries that involve screw placement require preparation of holes in bone (e.g., vertebral segments) prior to placement of the screws. Where such procedures are performed manually, in some implementations, a surgeon judges a drill trajectory for subsequent screw placement on the basis of pre-operative CT scans. Other manual methods which do not involve usage of the pre-operative CT scans, such as fluoroscopy, 3D fluoroscopy or natural landmark-based, may be used to determine the trajectory for preparing holes in bone prior to placement of the screws. In some implementations, the surgeon holds the drill in his hand while drilling, and fluoroscopic images are obtained to verify if the trajectory is correct. Some surgical techniques involve usage of different tools, such as a pedicle finder or K-wires. Such procedures rely strongly on the expertise of the surgeon, and there is significant variation in success rate among different surgeons. Screw misplacement is a common problem in such surgical procedures.

Image-guided spinal surgeries involve optical tracking to aid in screw placement. However, such procedures are currently performed manually, and surgical tools can be inaccurately positioned despite virtual tracking. A surgeon is required to coordinate his real-world, manual manipulation of surgical tools using images displayed on a two dimensional screen. Such procedures can be non-intuitive and require training, since the surgeon's eye must constantly scan both the surgical site and the screen to confirm alignment. Furthermore, procedural error can result in registration inaccuracy of the image-guiding system, rendering it useless, or even misleading.

Certain force feedback systems are used by surgeons in certain procedures; however such systems have a large footprint and take up valuable, limited space in the operating room. These systems also require the use of surgical tools that are specially adapted for use with the force feedback system, and the training required by surgeons to operate such systems can be significant. Moreover, surgeons may not be able to use expertise they have developed in performing spinal surgeries when adapting to use of the current force feedback systems. Such systems, while precise, may require more surgical time and more operating room preparation time to ready placement of the equipment for surgery. Thus, there is a need for systems, apparatus, and methods that provide enhanced precision in performing surgeries such as spinal surgeries.

SUMMARY

Described herein are a sterile handle for use with a robotic surgical system, for example, during spinal surgery. In certain embodiments, the sterile handle adds functionalities and an interface to existing surgical tools such that the robotic system may be commanded from the sterile field during surgery. The sterile handle permits a user, such as a surgeon, to physically manipulate the location of the end-effector of a robotic surgical system from a sterile field.

The sterile handle may include an input device that allows the user to limit the movement of the end-effector, such as limiting the movement to translations or rotations only.

The sterile handle may detect the presence of a user's hand. This ensures the end-effector is only moved when the user manipulates the sterile handle and reduces the likelihood that the end-effector is moved unintentionally. For example, robotic surgical system may permit the movement of the end-effector only in circumstances when the presence detector is activated (e.g., a hand of a surgeon is detected as present because the surgeon is holding the sterile handle).

The sterile handle, in certain embodiments, is configured such that it may be used in a sterile environment.

The design of the sterile handle, in certain embodiments, permits rapid mounting of the handle on a surgical tool.

The sterile handle may be designed to avoid tight spaces between various components of the handle, thereby simply the sterilization process.

The disclosed technology, in certain embodiments, includes a sterile handle for use with a robotic surgical system.

The sterile handle may include a tightening sleeve comprising a hollow tubular structure having a first open end, said structure defining an axis along which a portion of a surgical instrument guide may be inserted into the internal housing. The tightening sleeve may include two or more openings along a length of the tightening sleeve allowing the tightening sleeve to mechanically flex under tension. The openings may be slot, holes, or perforations.

The sterile handle may include a sterile handle housing with a hollow tubular structure having a first open end, said structure defining an axis along which the tightening sleeve may be inserted into the external housing.

In certain embodiments, the sterile handle includes a tightening nut coupled to the sterile handle housing. The tightening nut may include a thread on an interior of the tightening nut. The tightening nut may be configured to engage a thread on exterior of the tightening sleeve and thereby tighten the tightening sleeve such that a diameter of a portion of the tightening sleeve decreases and securely holds a portion of a surgical instrument guide inserted into the internal housing.

The sterile handle may include an electrical assembly that includes one or more input devices for commanding the robotic surgical system. The one or more input devices may be two or more buttons configured to enable a user to place the robotic surgical system in one of a rotation mode, a translation mode, or a combined translation and rotation mode. In certain embodiments, upon selection of a first button of the two or more buttons, the robotic surgical system is in the rotation mode, upon selection of a second button of the two or more buttons, the robotic surgical system is in the translation mode, and upon selection of both the first and second buttons, the robotic surgical system is in the combined translation and rotation mode.

The sterile handle may be ambidextrous such that it may be used on either side of the operating table and/or such that the robotic surgical system may be placed on either side of the operating table.

The sterile handle may be configured to be attached directly or indirectly to an end-effector of the robotic surgical system.

In certain embodiments, the robotic surgical system may be configured to allow robotically-assisted or unassisted positioning and/or movement of the sterile handle by a user with at least six degrees of freedom, wherein the six degrees of freedom are three degrees of translations and three degrees of rotations.

In certain embodiments, the robotic surgical system may be configured to allow robotically-assisted or unassisted positioning and/or movement of the sterile handle by a user with at least four degrees of freedom, wherein the four degrees of freedom are two degrees of translations and two degrees of rotations.

The surgical instrument guide may be configured to hold and/or restrict movement of a second surgical instrument therethrough. The surgical instrument may be a drill bit, tap, screw driver, screw-based implant and awl. The surgical instrument guide may be a drill guide and the surgical instrument may be a drill bit.

The robotic surgical system may be for use in spinal surgery.

The sterile handle may be used in a sterile environment. The sterile handle is at least one of completely or partially disposable.

In some implementations, the sterile handle includes one or more sensors configured to detect a presence of a surgeon's hand in proximity to the sterile handle.

The disclosed technology, in certain embodiments, includes a method of performing surgery with a robotic surgical system. The method may include moving a mobile cart transporting a robotic surgical system comprising a robotic arm in proximity to an operating table, wherein the robotic arm has an end effector with a sterile handle attached thereto.

In certain embodiments, the method includes stabilizing the mobile cart. The method may include maneuvering the robotic arm to a desired position to align an axis defined by the surgical instrument guide at a desired trajectory in relation to a patient situation. In certain embodiments, the method includes fixing the position of the robotic arm (and, therefore, the position of the surgical instrument guide), and maneuvering a surgical instrument in a manner that is constrained by the surgical instrument guide. The method may further include maneuvering the drill bit through the drill bit guide. In certain embodiments, the method may include maneuvering the surgical instrument through the surgical instrument guide.

In some implementations, stabilizing the mobile cart includes extracting one or more rigid legs on the mobile cart such that the mobile cart rests on the one or more rigid legs of the mobile cart. In some implementations, stabilizing the mobile cart includes retracting one or more wheels on the mobile cart such that the mobile cart rests on one or more rigid legs of the mobile cart. In certain embodiments, prior to maneuvering the robotic arm to a desired position, obtaining or accessing a CT scan, 3D CT scan, fluoroscopy, 3D fluoroscopy, or natural landmark-based image of the patient situation.

In some implementations, the sterile handle includes a printed circuit board. The printed circuit board may include the one or more input devices. In some implementations, the sterile handle housing includes one or more ribs that engage one or more openings, respectively, on the tightening sleeve when the sterile handle housing is slide over the tightening sleeve, thereby preventing rotation around the axis of the handle when a torque is applied thereto.

BRIEF DESCRIPTION OF THE FIGURES

The foregoing and other objects, aspects, features, and advantages of the present disclosure will become more apparent and better understood by referring to the following description taken in conjunction with the accompanying drawings, in which:

FIG. 1 is an illustration of an example robotic surgical system in an operating room;

FIG. 2 is an illustration of an example configuration of a robotic arm for performing a surgical operation;

FIGS. 3A through 3C are illustrations of a surgical instrument guide and a sterile handle for use with a robotic surgical system;

FIG. 4 is an illustration of a cross-sectional view of an example sterile handle with a tightening sleeve and a sterile handle housing;

FIG. 5 is an illustration of an example sterile handle for use with a robotic surgical system;

FIG. 6 is an illustration of an example system sterile handle and tool holder attached to a robotic arm;

FIG. 7 is an illustration of an example robotic surgical system with a sterile handle;

FIG. 8 is an illustration of an example robotic surgical system;

FIG. 9 is a flowchart of an example method of performing surgery with a robotic surgical system;

FIGS. 10A-B are illustrations of an example sterile handle rotating along the axis of the sterile handle;

FIGS. 11A-C are illustrations of portions of an example sterile handle with a rib that engages an opening on the tightening sleeve of the sterile handle;

FIG. 12A-C are illustrations of portions of an example sterile handle with an integrated printed circuit board;

FIG. 13 shows a block diagram of an exemplary cloud computing environment; and

FIG. 14 is a block diagram of a computing device and a mobile computing device.

The features and advantages of the present disclosure will become more apparent from the detailed description set forth below when taken in conjunction with the drawings, in which like reference characters identify corresponding elements throughout. In the drawings, like reference numbers generally indicate identical, functionally similar, and/or structurally similar elements.

DETAILED DESCRIPTION

FIG. 1 illustrates an example robotic surgical system in an operating room 100. In some implementations, one or more surgeons, surgical assistants, surgical technologists and/or other technicians (e.g., 106a-c) perform an operation on a patient 104 using a robotic-assisted surgical system. In the operating room 100 the surgeon may be guided by the robotic system to accurately execute an operation. This may be achieved by robotic guidance of the surgical tools, including ensuring the proper trajectory of the tool (e.g., drill or screw). In some implementations, the surgeon defines the trajectory intra-operatively with little or no pre-operative planning The system allows a surgeon to physically manipulate the tool holder to safely achieve proper alignment of the tool for performing crucial steps of the surgical procedure. Operation of the robot arm by the surgeon (or other operator) in force control mode permits movement of the tool in a measured, even manner that disregards accidental, minor movements of the surgeon. The surgeon moves the tool holder to achieve proper trajectory of the tool (e.g., a drill or screw) prior to operation or insertion of the tool into the patient 104. Once the robotic arm is in the desired position, the arm is fixed to maintain the desired trajectory. The tool holder serves as a stable, secure guide through which a tool may be moved through or slid at an accurate angle. Thus, the disclosed technology provides the surgeon with reliable instruments and techniques to successfully perform his/her surgery.

In some embodiments, the operation may be spinal surgery, such as a discectomy, a foraminotomy, a laminectomy, or a spinal fusion. In some implementations, the surgical robotic system includes a surgical robot 102 on a mobile cart 114. The surgical robot 102 in the example shown in FIG. 1 is positioned in proximity to an operating table 112 without being attached to the operating table 112, thereby providing maximum operating area and mobility to surgeons around the operating table 112 and reducing clutter on the operating table 112. In alternative embodiments, the surgical robot 102 (or cart) is securable to the operating table 112. In certain embodiments, both the operating table 112 and the cart 114 are secured to a common base to prevent any movement of the cart or table 112 in relation to each other, even in the event of an earth tremor.

The mobile cart 114 may permit a user (operator) 106a, such as a technician, nurse, surgeon, or any other medical personnel in the operating room 100, to move the surgical robot 102 to different locations before, during, and/or after a surgical procedure. The mobile cart 104 enables the surgical robot 102 to be easily transported into and out of the operating room 100. For example, a user 106a may move the surgical robot 102 into the operating room 100 from a storage location. In some implementations, the mobile cart 114 may include wheels, a track system, such as a continuous track propulsion system, or other similar mobility systems for translocation of the cart. The mobile cart 114 may include an attached or embedded handle for locomotion of the mobile cart 114 by an operator (e.g., user 106a).

For safety reasons, the mobile cart 114 may be provided with a stabilization system that may be used during a surgical procedure performed with a surgical robot 102. The stabilization mechanism increases the global stiffness of the mobile cart 114 relative to the floor in order to ensure the accuracy of the surgical procedure. In some implementations, the wheels include a locking mechanism that prevents the cart 114 from moving. The stabilizing, braking, and/or locking mechanism may be activated when the machine is turned on. In some implementations, the mobile cart 114 includes multiple stabilizing, braking, and/or locking mechanisms. In some implementations, the stabilizing mechanism is electro-mechanical with electronic activation. The stabilizing, braking, and/or locking mechanism(s) may be entirely mechanical. The stabilizing, braking, and/or locking mechanism(s) may be electronically activated and deactivated.

In some implementations, the surgical robot 102 includes a robotic arm mounted on a mobile cart 114. An actuator may move the robotic arm. The robotic arm may include a force control end-effector configured to hold a surgical tool. The robot 102 may be configured to control and/or allow positioning and/or movement of the end-effector with at least four degrees of freedom (e.g., six degrees of freedom, three translations and three rotations, or four degrees of freedom, two translations and two rotations, or a variation thereof).

In some implementations, the robotic arm is configured to releasably hold a surgical tool, allowing the surgical tool to be removed and replaced with a second surgical tool. The system may allow the surgical tools to be swapped without re-registration, or with automatic or semi-automatic re-registration of the position of the end-effector.

In some implementations, the surgical system includes a surgical robot 102, a tracking detector 108 that captures the position of the patient and different components of the surgical robot 102, and a display screen 110 that displays, for example, real time patient data and/or real time surgical robot trajectories.

In some implementations, a tracking detector 108 monitors the location of patient 104 and the surgical robot 102. The tracking detector 108 may be a camera, a video camera, an infrared detector, field generator and sensors for electro-magnetic tracking or any other motion detecting apparatus. In some implementation, based on the patient and robot position, the display screen 110 displays a projected trajectory and/or a proposed trajectory for the robotic arm of robot 102 from its current location to a patient operation site. By continuously monitoring the patient 104 and robotic arm positions, using tracking detector 108, the surgical system can calculate updated trajectories and visually display these trajectories on display screen 110 to inform and guide surgeons and/or technicians in the operating room 100 using the surgical robot. In addition, in certain embodiments, the surgical robot 102 may also change its position and automatically position itself based on trajectories calculated from the real time patient and robotic arm positions captured using the tracking detector 108. For instance, the trajectory of the end-effector can be automatically adjusted in real time to account for movement of the vertebrae and/or other part of the patient 104 during the surgical procedure.

FIG. 2 illustrates an example configuration 200 of a robotic arm for performing a surgical operation. The robotic surgical system includes a robotic arm 202 and an end-effector 204. The manipulator is configured to allow robotically-assisted or unassisted positioning and/or movement of the surgical instrument guide 206 by a user with at least four degrees of freedom to align an axis defined by the instrument guide at a desired trajectory in relation to a patient situation. The axis can be aligned with the desired trajectory in relation to the patient situation via the manipulator.

An end-effector, such as surgical instrument guide 206, is coupled to the end-effector 204 for precisely guiding instruments during surgery. For example, the surgical instrument guide 206 may be coupled to the manipulator via a flange. The surgical instrument guide 206 is configured to hold and/or restrict movement of a surgical instrument therethrough. As shown in FIG. 2, in some implementations, the surgical instrument is a drill 218 and drill bit 208. In this example illustration, the surgical instrument guide 206 is a drill bit guide. Such a system may be used to perform spinal surgery. The surgical tool may be, for example, a tap such as the StealthStation® CR Horizon Legacy Taps from Medtronic, Inc. of Minneapolis, Minn. Other surgical instruments may be used by the system, such as a screw driver, screw-based implant, or awl. For example, the surgical instrument guide may be configured to be used to guide a screw implant and a tissue protector.

FIGS. 3A through 3C are illustrations of a surgical instrument guide and a sterile handle for use with a robotic surgical system. In some implementations, the sterile handle 302 includes a tightening sleeve 304 with a hollow tubular structure having a first open end. In some implementations, the structure of the tightening sleeve 304 defines an axis along which a portion 322 of a surgical instrument guide 320 may be inserted into the tightening sleeve 304. The portion 322 of the surgical instrument guide 320 that may be inserted into the tightening sleeve 304 may be a separate component (e.g., a handle) that can be mechanically attached to the surgical instrument guide 320. In some implementations, portion 322 of the surgical instrument guide 320 that may be inserted into the tightening sleeve 304 is an integrated component of the surgical instrument guide 320. In some implementations, a navigation tracker 324 is coupled to the surgical instrument guide 320 such that the position of the surgical instrument guide 320 may be tracked by a navigation system (e.g., tracking camera) of the robotic surgical system.

A sterile handle housing 306 may include a hollow tubular structure having a first open end. The sterile handle housing 306 structure may define an axis along which the tightening sleeve 304 may be inserted into the sterile handle housing 306.

The tightening sleeve 304 may include two or more openings 308 along a length of the tightening sleeve allowing the tightening sleeve to mechanically flex under tension. In some implementations, the two or more openings are two or more slots, holes, or perforations.

A tightening nut 312 may be permanently and removably coupled to the sterile handle housing 306. The tightening nut 312 includes a thread on an interior of the tightening nut. The tightening nut 312 is configured to engage a thread 310 on exterior of the tightening sleeve 304 and thereby tighten the tightening sleeve 304 such that a diameter of a portion of the tightening sleeve decreases and securely holds a portion 322 of a surgical instrument guide 320 inserted into the tightening sleeve 304. The tightening sleeve 304 includes a wedge 314 that engages a wedge on the interior of the sterile handle housing 306 as the tightening nut 312 is tightened and the threads inside the tightening nut 312 engage the threads 310 on the tightening sleeve 304 and pull the tightening sleeve in the direction of the tightening nut 312. The wedges force the tightening sleeve to flex and increase the friction between the portion 322 of the surgical instrument holder 320 and the tightening sleeve 304 when the sterile handle 302 is assembled with the portion 322 of the surgical instrument holder 320 inserted into the tightening sleeve 304. Thus, tightening the tightening nut 312 enables the sterile handle to securely hold the surgical instrument guide.

In some implementations, the sterile handle 302 includes an electrical assembly 316. The electrical assembly 316 may include one or more input devices 318 for commanding the robotic surgical system. The one or more input devices 318 may include two or more buttons 318a and 318b configured to enable a user to place the robotic surgical system in one of a rotation mode, a translation mode, or a combined translation and rotation mode. In some implementations, upon selection of a first button 318a of the two or more buttons, the robotic surgical system is in the rotation mode, upon selection of a second button 318b of the two or more buttons, the robotic surgical system is in the translation mode, and upon selection of both the first and second buttons 318a-b, the robotic surgical system is in the combined translation and rotation mode. In some implementations, the handle 302 and input device(s) thereon (e.g., buttons) can be used for instructing the robotic system to translate along a line when the translation button is pressed, rotate around the line if the rotation button is pressed, and/or translate and rotate around the line if both buttons are pressed.

The electrical assembly 316 may be directly integrated into the sterile handle 302. In some implementations, the electrical assembly 316 can be done separately (e.g., using over-molding on buttons and cable or epoxy resin to form an assembly which is integrated into the handle using a rapid locking mechanism).

In some implementations, the sterile handle 302 is ambidextrous. In some implementations, the sterile handle 302 is configured such that a robotic surgical system may be used on either side of an operating table when the handle 302 is in use. The sterile handle 302 is configured to be attached directly or indirectly to an end-effector of the robotic surgical system. In some implementations, the robotic surgical system is configured to allow robotically-assisted or unassisted positioning and/or movement of the sterile handle by a user with at least six degrees of freedom. The six degrees of freedom may be three degrees of translations and three degrees of rotations.

As described above, the sterile handle 302 is configured to securely hold a surgical instrument guide 320. The surgical instrument guide 320 is configured to hold and/or restrict movement of a surgical instrument therethrough. The surgical instrument may be a drill bit, tap, screw driver, screw-based implant, or awl. In some implementations, the surgical instrument guide 320 is a drill guide and the surgical instrument is a drill bit. In some implementations, the robotic surgical system is for use in spinal surgery.

The sterile handle 302 may be completely or partially disposable. For example, in some implementations, the electrical assembly 316 may be disposable. All disposable parts may be produced in molded plastic. In some implementations, reusable parts may be made of either metal or plastic. In some implementations, the entire sterile handle 302 is reusable. Assembly of the sterile handle 302 may be performed pre-operatively. For example, a disposable sterile handle 302 may be completely assembled in the packaging. In some implementations, the sterile handle 302 may be assembled intra-operatively. In some implementations, the electrical assembly 316 may be fixed in the handle before mounting the sterile handle 302 on the surgical instrument 320.

The sterile handle 302 may be made of a sterile material or a material that may be sterilized. In some implementations, the sterile handle 302 may be sterilized using different technologies, such as using Ethylene Oxide (EtO), autoclave, radiation, or other sterilization methods. Different components of the sterile handle 302 using different technologies, for example, mechanical assembly in an autoclave, electrical assembly in an EtO. In some implementations, sterilization is achieved by draping. In some implementations, the sterile handle comprises one or more sensors configured to detect a presence of a surgeon's hand in proximity to the sterile handle. In some implementations, the one or more sensors include a presence mechanism 332 that is engaged by a surgeon's hand when the surgeon holds the handle such that presence of the hand is detected. The presence mechanism may be a lever-button mechanism. In some implementations, the presence mechanism 332 includes one or more capacitive or resistive sensors, or a combination thereof.

FIG. 3B illustrates a handle 322 of a surgical instrument guide 320 with the tightening sleeve 304 of a sterile handle 302 slide over the handle 322. The sterile handle housing 306 is shown adjacent the tightening sleeve 304 and may be slide over the tightening sleeve 304. FIG. 3C illustrates a handle 322 of a surgical instrument guide 320 with the tightening sleeve 304 of a sterile handle 302 slide over the handle 322 and the sterile handle housing 306 slide over the tightening sleeve 304. As the tightening nut 312 is tightened, the body of the tightening sleeve 304 is pinched, thus increasing the friction between the handle 322 and the tightening sleeve 304 and securing the handle 322 within the tightening sleeve 304.

FIG. 4 illustrates a cross-sectional view of an example sterile handle 400 with a tightening sleeve 408 and a sterile handle housing 406. A surgical instrument guide 420 (e.g., a handle of a surgical instrument guide), may slide into the tightening sleeve 408. As a user tightens the tightening nut 412, threads 414 (e.g., threads on the sterile handle housing 406 and threads on the tightening sleeve 408) cause the tightening sleeve 408 to pull/slide towards the tightening nut 412 (e.g., towards the right as shown in FIG. 4).

The internal housing, in some implementations, includes openings 410 (e.g., slots, holes, or perforations) that allow a portion of the body of the tightening sleeve 408 to be pinched. As the tightening nut 412 is tightened, a wedge 416 causes a portion of the body of the tightening sleeve 408 to be pinched. As shown in FIG. 4, as the tightening sleeve slides to the right, a wedge on the sterile handle housing 406 contacts a wedge on the tightening sleeve 408, thus a portion of the body of the tightening sleeve 408 is pinched. When a surgical instrument guide 420 is inserted into an assembled handle 400 and the tightening nut 412 is tightened, the tightening sleeve 408 “grips” the surgical instrument guide 420 (e.g., the friction between the guide 420 and the tightening sleeve 408 is increased). Thus, the surgical handle 400 securely holds the guide 420.

FIG. 5 is an illustration of an example sterile handle for use with a robotic surgical system. In some implementations, the sterile handle 502 includes an electrical assembly 516. The electrical assembly 516 may include one or more input devices 518 for commanding the robotic surgical system. The one or more input devices 518 may include two or more buttons 518a and 518b configured to enable a user to place the robotic surgical system in one of a rotation mode, a translation mode, or a combined translation and rotation mode. In some implementations, upon selection of a first button 518a of the two or more buttons, the robotic surgical system is in the rotation mode, upon selection of a second button 518b of the two or more buttons, the robotic surgical system is in the translation mode, and upon selection of both the first and second buttons 518a-b, the robotic surgical system is in the combined translation and rotation mode. In some implementations, the electrical assembly 516 is integrated into a housing of the sterile handle 502. In some implementations, the electrical assembly 516 is removable. The handle 502 may include a rapid locking mechanism 534 that is used to attach the electrical assembly 516 to the handle 502. The electrical assembly 516 may include a wire 530 that is used to connect to the electrical system of the robotic surgical system. In some implementations, the wire 530 includes a plug that plugs into an embedded connector in a sterile drape (e.g., drape connector).

In some implementations, the sterile handle comprises one or more sensors configured to detect the presence of a surgeon's hand in proximity to the sterile handle. In some implementations, the one or more sensors include a mechanism 332 that is engaged by a surgeon's hand when the surgeon holds the handle such that presence of the hand is detected.

FIG. 6 illustrates an example system 600 sterile handle and tool holder attached to a robotic arm. In some implementations, the system 600 includes a sterile drape 602 for covering a surgical robotic arm 604 and preventing contamination of a sterile field.

In some implementations, the sterile drape 602 includes a flexible covering with a sterile outer surface. The sterile drape may be partially conformable to a surgical robotic arm. The sterile drape may include an embedded connector 608 configured (e.g., positioned on the flexible covering and sized) to permit electrical contact between the surgical robotic arm 604 (e.g., an actuator of the robotic arm) and a sterile manipulator 606 (e.g., sterile handle) of the robotic arm 604 when the sterile manipulator 606 is separated from the surgical robotic arm by the flexible covering. In some implementations, the sterile drape 602 is disposable (e.g., a single-use product).

The drape connector 608 may be configured to couple to a handle connector 610 that is connected to the sterile handle 606. The drape connector 608 may also be configured to couple to a robot connector 612 that is connected to the electrical system of the robotic surgical system. Thus, the drape connector may act as an intermediary connector that allows the handle to be electrically connected to the electrical system of the robotic surgical system through the sterile drape 602.

FIG. 7 is an illustration of an example robotic surgical system 700 with a sterile handle 710. In some implementations, the robotic surgical system is for performing surgery, such as spinal surgery. The robotic surgical system may include a robotic arm 714 with an interface 702 for engaging a sterile adapter 706. The sterile adapter 706 may be configured to attach to the robotic arm 714 via a robotic interface 706 and tightly stretch the sterile drape 704 to assure repeatable and rigid positioning of the sterile drape 704. The sterile drape 704 may be configured to protect the robotic arm from contaminating a sterile field. In some implementations, the sterile drape includes a drape connector configured to electrically couple, through the sterile drape, the manipulator to an electrical system of the robotic surgical system covered by the sterile drape. The sterile handle 710 may be coupled to a handle connector via a cable and the handle connector is configured to electrically connect to the drape connector. The electrical system of the robotic surgical system may be coupled to a robot connector and the robot connector may be configured to electrically connect to the drape connector. Thus, the robot connector may electrically couple the drape connector to the robot connector, through the sterile drape 704.

In some implementations, a surgical instrument holder 718 is configured to securely hold the surgical instrument 708. The surgical instrument holder 718 may be attached to the interface 702 via a tightening screw 716. The tightening screw 716 may protrude through the sterile drape 704 that is tightly stretched over the opening of the sterile adapter 706. The robot interface 702 may include one or more positioning elements 712 (e.g., pegs or pins) configured to provide accurate and repeatable positioning of the surgical instrument holder 714 in reference to the robotic arm. The one or more positioning elements 712 may be round or oblong. The surgical instrument holder 718 may include one or more studs or holes that engage the one or more positioning elements 712. The one or more positioning elements 712 may protrude through the sterile drape 704 when the sterile adapter 706 is attached to the interface 702. In some implementations, the one or more positioning elements 712 extend from the robotic arm 714 and engage one or more surgical instrument holder positioning members. For example, the one or more positioning elements 712 may be the one or more pegs are configured to extend from the robotic arm and engage one or more holes in the surgical instrument holder 718.

In some implementations, the robotic surgical system includes a manipulator 710 (e.g., a sterile handle) configured to allow robotically-assisted or unassisted positioning and/or movement of the surgical instrument by a user with at least four degrees of freedom to align an axis defined by the surgical instrument at a desired trajectory in relation to a patient situation.

In some implementations, the surgical instrument is a surgical instrument guide configured to hold and/or restrict movement of a second surgical instrument there through. The second surgical instrument may be a drill bit, tap, screw driver, screw-based implant, or awl. For example, in the case of spinal surgery, the second surgical instrument may be a drill bit and the surgical instrument guide may be a drill guide.

In some implementations, the robotic surgical system includes a mobile cart configured to transport the robotic surgical system. The sterile drape may be configured to protect the mobile cart from contaminating a sterile field. In some implementations, the sterile drape includes a first sterile drape to protect the robotic arm 714 and a second sterile drape to protect the mobile cart. In some implementations, the sterile drape may include printed marks configured to assist in proper draping procedure. In some implementations, the drape may be folded in a configuration that makes for easily applying the drape to the robotic system.

In some implementations, the surgical instrument holder is configured to be attached to the robotic arm using a fastening system. The fastening system may be a bolt, nut, screw, or one or more electro magnets.

In some implementations, one or more holding stripes are configured to hold the sterile drape. The one or more holding stripes may secure a portion of the sterile drape to the robotic arm. In some implementations, the system includes a suppression system configured to remove air from under the sterile drape. The suppression system may include a ventilator or a suction device that pumps out the air from under the sterile drape.

In some implementations, the surgical instrument holder 714 is made from a non-conductive material (e.g., plastic). The holder 718 may act as an insulator (prevent electrical conductivity) between the surgical instrument 708 and the robotic arm 714. In some implementations, the surgical instrument holder 718 is conductive, however, a non-conducive pad is placed between the holder 718 and the interface 702.

FIG. 8 is an illustration of an example robotic surgical system. In some implementations, one or more surgeons, surgical assistants, surgical technologists and/or other technicians, perform an operation on a patient using a robotic-assisted surgical system. In the operating room the surgeon may be guided by the robotic system to accurately execute an operation. The robotic surgical system may be transported in and out of an operating room using a mobile cart (not shown). Accordingly, the robotic surgical system, including the mobile cart, must be sterilized when used in the operating room. The system may be sterilized by applying a sterile drape 820 to a portion of the system, including the robotic arm 802 and/or the mobile cart. The sterile drape 820 may consist of a single drape or several pieces, such as a sterile cover for covering the robotic arm 802 and a sterile drape for covering the mobile cart.

In some implementations, the sterile drape 820 is attached (e.g., glued or welded) to a sterile adapter 822. The sterile adapter 822 may be attached (e.g., clipped) to a tool holder body 824 on the robotic arm 802. The sterile adapter 822 ensures the drape 820 is tightly stretched over the tool holder 824 to protect the robotic arm 802 and mobile cart from contaminating the sterile field, and provides a structure that provides for repeatable and rigid positioning of the sterile drape. Tightly stretching the drape 820 between the instrument holder 826 and tool holder 824 and tightening the instrument holder 826 to the robotic arm 802 using, for example, a tightening screw 832, reduces the likelihood of folds in the drape between the told holder and robot interface. Thus, errors between the robot model and the actual situation because of the position of the tool holder relative to the robot interface are minimized. If folds are present, the positioning of the instrument holder 826 relative to the robot interface will be different than anticipated and the robotic surgical system may have difficulty positioning tools held by the tool holder appropriately.

A sterile tool holder 826 may be connected to the robotic arm 802 through the sterile drape 820. In some implementations, the instrument holder 826 includes a base 828, clamp 830, and nut 832. In some implementations, the nut is tightened to pull the clamp 830 closer to the base 828 such that a surgical instrument, such as tool guide 814 is securely held between the base 828 and the clamp 830. The instrument holder 826 be coupled to a navigation marker 816. A sterile handle 804 may be mechanically coupled to the tool guide 814 via a handle 818 of the tool guide. A tightening nut 808 on the sterile handle 804 may be used to tighten the sterile handle to the handle 818 such that the sterile handle 804 is securely attached to the handle 818.

In some implementations, the sterile handle 804 includes an input device 806, such as button 806a and button 806b, that enables a user to control the position of the end effector 820. Thus, the disclosed technology enables a robotic surgical system to be used in a sterile operating room without having to sterilize each individual component of the system. Only the components outside of the sterile drape (e.g., the optical mark, surgical instruments, and tool holder must be sterilized individually.

The input device 806 may mimic the functionality of the mode selection panel 838. Both the input device 806 and the mode selection panel 838. In some implementations, both of these interfaces are configured to enable a user to place the robotic surgical system in one of a rotation mode, a translation mode, or a combined translation and rotation mode. In some implementations, upon selection of a first button of the two or more buttons, the robotic surgical system is in the rotation mode, upon selection of a second button of the two or more buttons, the robotic surgical system is in the translation mode, and upon selection of both the first and second buttons, the robotic surgical system is in the combined translation and rotation mode.

In some implementations, the sterile adapter 822 may be a disposable (e.g. a single-use product). For example, a new sterile adapter 822 may be used for every surgical procedure. In some implementations, the sterile adapter 822 is a rigid or semi-rigid device. It may be made from a hard plastic, polymer, or a composite material. In some implementations, the sterile adapter 822 secures a drape 820 over a surgical robotic arm 802 to prevent contamination of a sterile field.

The sterile adapter 822 may include a rigid or semi-rigid collar (e.g., ring or a hollow cylindrical structure) configured to mount (e.g., snap-mount) onto an interface 824 of the surgical robotic arm. The sterile adapter 822 may include a rigid or semi-rigid body extending from the collar and shaped to conform to a portion of the surgical robotic arm to tightly secure a flexible drape 820 in place (e.g., with no folds) over the portion of the surgical robotic arm 802 when the drape 820 is attached to the adapter 822.

In some implementations, the sterile adapter 822 is one or more tabs that engage an interface on the robot. The tabs may “click” into the interface to provide easy and secure mounting of the sterile adapter 822, and hence sterile drape 820, on the robot. The sterile drape 820 may be glued or welded to the sterile adapter 822. The adapter 822 ensures that the drape is tightly stretched over the instrument holder 826 and tool holder body 824 to provide repeatable and rigid positioning of the instrument holder 826 relative to the robotic arm 802.

In some implementations, a user applies forces and torques on an instrument guide 814 attached to a force/torque sensor 834. The force/torque sensor 834 may be attached to a flange on the robot arm 802 and measures the forces and torques applied to the tool, such as guide 814. In some implementations, the measurements are transmitted to a force control box. In some implementations, the force control box converts the analog data into digitized data and transmits them to a controller. In some implementations, the measurements from force/torque sensor 834 are sent directly to the controller. The controller processes the forces and torques and computes linear and angular correction of the end-effector 840 position of the robot. The controller sends commands to the motors of the robot to update the position of the end effector 840 to a set point position. The controller may check the current position of the position of the end-effector 840 and stops sending commands to the motors if the set point position is reached. In some implementations, this process is performed continuously. In some implementations, the motors are servo or electric motors that are controlled by a servo control. The force sensor 834 may be connected to the robot with an intermediary analog box which measures forces and torques and transmits them via a network (e.g., Ethernet, CAN, wireless, internet, private LAN, public LAN, etc.).

The force sensor 834 may be attached to system in a variety of configurations. In some implementations, the force sensor 834 is coupled to the robot arm 802 using a sensor-robot interface 836. The tool holder body 824 may be coupled to the robotic arm 802 via the force sensor 834. Using this configuration, the sterile cover 820 may be wrapped around the robot arm 802 and between the tool holder body 824 and the instrument holder 826 via the sterile adapter 828 to ensure sterilization. The force sensor 834 may provide for direct measurement of forces on the tool. The force sensor 834 may be designed to resist flexing. The force sensor 834 may be designed to flex under the stress of certain external forces. The displacement caused when an external force is applied may be calculated based on the force applied to the tool, torque applied to the tool, radial force stiffness, axial torque stiffness, and the diameter of the holder to which the tool is attached. In some implementations, the force sensor 834 is located between the tool holder 826 and robot tool holder body 824.

In some implementations, the sterile drape 820 includes a flexible covering with a sterile outer surface. The covering 820 may be at least partially conformable to a surgical robotic arm 802. The sterile drape 820 may include an embedded connector configured (e.g., positioned on the flexible covering and sized) to permit electrical contact between the electronics for controlling the surgical robotic arm (e.g., an actuator of the robotic arm) and the electronics of a sterile handle 804 of the robotic arm 802 when the sterile handle 804 is separated from the surgical robotic arm 802 by the flexible covering 820. In some implementations, the sterile drape 820 is disposable (e.g., a single-use product). In some implementations, the sterile handle 804 is connected to a handle connector 812 via a cable 810. The handle connector 812 may be plugged into or electrically coupled to the embedded connector of the sterile drape 820. In some implementations, an electrical connector is coupled to the electrical system of the robotic surgical system and may be electrically coupled to the embedded connector of the sterile drape 820 such that the handle connector 812 and the electrical connector are electrically coupled to each other through the sterile drape (e.g., via the embedded connector in the drape).

FIG. 9 is a flowchart of an example method 900 of performing surgery with a robotic surgical system. In some implementations, the method 900 includes moving a mobile cart transporting a robotic surgical system with a robotic arm in proximity to an operating table (902). In some implementations, the robotic arm has an end effector and a sterile handle thereto. In some implementations, the sterile handle includes a tightening sleeve with a hollow tubular structure having a first open end. The structure may define an axis along which a portion of a surgical instrument guide may be inserted into the internal housing. The tightening sleeve may include two or more openings along a length of the tightening sleeve allowing the tightening sleeve to mechanically flex under tension The two or more openings may be slots, holes, perforations, or a combination thereof.

In some implementations, the sterile handle includes a sterile handle housing with a hollow tubular structure having a first open end, said structure defining an axis along which the tightening sleeve may be inserted into the external housing. In some implementations, the sterile handle includes a tightening nut coupled to the sterile handle housing. The tightening nut may include a thread on an interior of the tightening nut and the tightening nut may be configured to engage a thread on exterior of the tightening sleeve and thereby tighten the tightening sleeve such that a diameter of a portion of the tightening sleeve decreases and securely holds a portion of a surgical instrument guide inserted into the internal housing. The portion of the surgical instrument guide inserted into the tightening sleeve may be a portion of the surgical instrument guide handle.

In some implementations, the sterile handle includes an electrical assembly with one or more input devices for commanding the robotic surgical system. The one or more input devices may include two or more buttons configured to enable a user to place the robotic surgical system in one of a rotation mode, a translation mode, or a combined translation and rotation mode. In some implementations, upon selection of a first button of the two or more buttons, the robotic surgical system is in the rotation mode, upon selection of a second button of the two or more buttons, the robotic surgical system is in the translation mode, and upon selection of both the first and second buttons, the robotic surgical system is in the combined translation and rotation mode.

In some implementations, the method 900 includes stabilizing the mobile cart (904). Stabilizing the mobile cart may include extracting one or more rigid legs on the mobile cart such that the mobile cart rests on the one or more rigid legs of the mobile cart. In some implementations, stabilizing the mobile cart includes retracting one or more wheels on the mobile cart such that the mobile cart rests on one or more rigid legs of the mobile cart.

In some implementations, the method 900 includes maneuvering the robotic arm to a desired position to align an axis defined by the surgical instrument at a desired trajectory in relation to a patient situation (906). The desired trajectory may be a desired path of the surgical instrument guide. In some implementations, the method 900 includes, prior to maneuvering the robotic arm to a desired position, obtaining or accessing a CT scan, 3D CT scan, fluoroscopy, 3D fluoroscopy, or natural landmark-based image of the patient situation.

In some implementations, the method 900 includes, after maneuvering the robotic arm to the desired position, fixing the position of the robotic arm (and, therefore, the position of the surgical instrument) (908). In some implementations, the method 900 includes, after fixing the position of the robotic arm, maneuvering the surgical instrument guide in a manner that is constrained by the surgical instrument guide (910). In some implementations, the surgical instrument guide is configured to hold and/or restrict movement of a second surgical instrument therethrough. The surgical instrument may be a drill bit, tap, screw driver, screw-based implant, and awl. In some implementations, the surgical instrument guide is a drill guide and the surgical instrument is a drill bit. Step 910 may include maneuvering the surgical instrument through the surgical instrument guide. For example, step 910 may include maneuvering the drill bit through the drill bit guide. In some implementations, the robotic surgical system is for use in spinal surgery.

In some implementations, the sterile handle includes one or more sensors configured to detect a presence of a surgeon's hand in proximity to the sterile handle. The sensor may include a button or lever that is activated when a user grabs a portion of the sterile handle, thus alerting the system that the hand is present. This may allow the system to detect intentional movements of the robotic arm and/or end effect and unintentional movements which may be avoided or negated by the system (e.g., such that the end effector or arm does not move).

In some implementations, features are added to the sterile handle to prevent rotation of the handle about the axis of the handle when a torque is applied thereto as shown in FIGS. 10A-B. In some implementations, one or more ribs 1102 are added to the external housing 1104 of the sterile handle 1100 (e.g., on the inner surface of the external housing) as shown in FIGS. 11A-C (various cross-sectional views of portions of the sterile handle are shown therein). The one or more ribs 1102 are designed to block rotation along the axis of the sterile handle 1100 by engaging one or more openings 1108, respectively, in the internal housing 1106 of the sterile handle 1100. In the example shown in FIGS. 11A-C, the rib 1102 engages the opening 1108 when the external housing 1104 is slide over the internal housing 1106. In some implementations, several ribs (e.g., two, three, four, five, or six ribs) are integrated in the external housing 1104 (e.g., and at least a corresponding number of openings in the internal housing 1106), thereby decreasing the load on a single rib when a torque is applied to the handle 1100. This allows, for example, a user to apply high torques around the axis of the handle without rotating the handle itself.

In some implementations, the materials used in the design of the handle are such that the friction between the inner and outer housing of the sterile handle as explained above is such that rotation of the axis is prevented (e.g., without using one or more ribs). In some implementations, interface between the inner and outer housings is coated or textured to increase the friction there between, thereby preventing the undesired rotation.

FIGS. 12A-C illustrate portions of an example sterile handle. In certain embodiments, the buttons 1218a-b (e.g., buttons 318a-b shown in FIG. 3A) are connected to a printed circuit board housed at least partially inside the sterile handle. In some implementations, the printed circuit board is part of the sterile handle housing (i.e., external housing). In some implementations, the printed circuit board is part of the tightening sleeve (i.e., the internal housing of the sterile handle). The printed circuit board (e.g., and the buttons 1218), in some implementations, are preassembled (e.g., prior to assembling the handle). In some implementations, a switch 1218c is included such as switch 332 as described in relation to FIG. 3A. In some implementations, the sterile handle (e.g., the input devices on the sterile handle and the movement detection device) are electrically connected to a plug 1206 via a cable 1204. The plug 1206 may be connected to the computer of the robotic surgical system thereby enabling the computer to communicate with the sterile handle and vice versa. In some implementations, a cable connector 1202 is included on the printed circuit board as shown in FIG. 12C.

As shown in FIG. 13, an implementation of a network environment 1300 for use with a robotic surgical system is shown and described. In brief overview, referring now to FIG. 13, a block diagram of an exemplary cloud computing environment 1300 is shown and described. The cloud computing environment 1300 may include one or more resource providers 1302a, 1302b, 1302c (collectively, 1302). Each resource provider 1302 may include computing resources. In some implementations, computing resources may include any hardware and/or software used to process data. For example, computing resources may include hardware and/or software capable of executing algorithms, computer programs, and/or computer applications. In some implementations, exemplary computing resources may include application servers and/or databases with storage and retrieval capabilities. Each resource provider 1302 may be connected to any other resource provider 1302 in the cloud computing environment 1300. In some implementations, the resource providers 1302 may be connected over a computer network 1308. Each resource provider 1302 may be connected to one or more computing device 1304a, 1304b, 1304c (collectively, 1304), over the computer network 1308.

The cloud computing environment 1300 may include a resource manager 1306. The resource manager 1306 may be connected to the resource providers 1302 and the computing devices 1304 over the computer network 1308. In some implementations, the resource manager 1306 may facilitate the provision of computing resources by one or more resource providers 1302 to one or more computing devices 1304. The resource manager 1306 may receive a request for a computing resource from a particular computing device 1304. The resource manager 1306 may identify one or more resource providers 1302 capable of providing the computing resource requested by the computing device 1304. The resource manager 1306 may select a resource provider 1302 to provide the computing resource. The resource manager 1306 may facilitate a connection between the resource provider 1302 and a particular computing device 1304. In some implementations, the resource manager 1306 may establish a connection between a particular resource provider 1302 and a particular computing device 1304. In some implementations, the resource manager 1306 may redirect a particular computing device 1304 to a particular resource provider 1302 with the requested computing resource.

FIG. 14 shows an example of a computing device 1400 and a mobile computing device 1450 that can be used to implement the techniques described in this disclosure. The computing device 1400 is intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The mobile computing device 1450 is intended to represent various forms of mobile devices, such as personal digital assistants, cellular telephones, smart-phones, and other similar computing devices. The components shown here, their connections and relationships, and their functions, are meant to be examples only, and are not meant to be limiting.

The computing device 1400 includes a processor 1402, a memory 1404, a storage device 1406, a high-speed interface 1408 connecting to the memory 1404 and multiple high-speed expansion ports 1410, and a low-speed interface 1412 connecting to a low-speed expansion port 1414 and the storage device 1406. Each of the processor 1402, the memory 1404, the storage device 1406, the high-speed interface 1408, the high-speed expansion ports 1410, and the low-speed interface 1412, are interconnected using various busses, and may be mounted on a common motherboard or in other manners as appropriate. The processor 1402 can process instructions for execution within the computing device 1400, including instructions stored in the memory 1404 or on the storage device 1406 to display graphical information for a GUI on an external input/output device, such as a display 1416 coupled to the high-speed interface 1408. In other implementations, multiple processors and/or multiple buses may be used, as appropriate, along with multiple memories and types of memory. Also, multiple computing devices may be connected, with each device providing portions of the necessary operations (e.g., as a server bank, a group of blade servers, or a multi-processor system).

The memory 1404 stores information within the computing device 1400. In some implementations, the memory 1404 is a volatile memory unit or units. In some implementations, the memory 1404 is a non-volatile memory unit or units. The memory 1404 may also be another form of computer-readable medium, such as a magnetic or optical disk.

The storage device 1406 is capable of providing mass storage for the computing device 1400. In some implementations, the storage device 1406 may be or contain a computer-readable medium, such as a floppy disk device, a hard disk device, an optical disk device, or a tape device, a flash memory or other similar solid state memory device, or an array of devices, including devices in a storage area network or other configurations. Instructions can be stored in an information carrier. The instructions, when executed by one or more processing devices (for example, processor 1402), perform one or more methods, such as those described above. The instructions can also be stored by one or more storage devices such as computer- or machine-readable mediums (for example, the memory 1404, the storage device 1406, or memory on the processor 1402).

The high-speed interface 1408 manages bandwidth-intensive operations for the computing device 1400, while the low-speed interface 1412 manages lower bandwidth-intensive operations. Such allocation of functions is an example only. In some implementations, the high-speed interface 1408 is coupled to the memory 1404, the display 1416 (e.g., through a graphics processor or accelerator), and to the high-speed expansion ports 1410, which may accept various expansion cards (not shown). In the implementation, the low-speed interface 1412 is coupled to the storage device 1406 and the low-speed expansion port 1414. The low-speed expansion port 1414, which may include various communication ports (e.g., USB, Bluetooth®, Ethernet, wireless Ethernet) may be coupled to one or more input/output devices, such as a keyboard, a pointing device, a scanner, or a networking device such as a switch or router, e.g., through a network adapter.

The computing device 1400 may be implemented in a number of different forms, as shown in the figure. For example, it may be implemented as a standard server 1420, or multiple times in a group of such servers. In addition, it may be implemented in a personal computer such as a laptop computer 1422. It may also be implemented as part of a rack server system 1424. Alternatively, components from the computing device 1400 may be combined with other components in a mobile device (not shown), such as a mobile computing device 1450. Each of such devices may contain one or more of the computing device 1400 and the mobile computing device 1450, and an entire system may be made up of multiple computing devices communicating with each other.

The mobile computing device 1450 includes a processor 1452, a memory 1464, an input/output device such as a display 1454, a communication interface 1466, and a transceiver 1468, among other components. The mobile computing device 1450 may also be provided with a storage device, such as a micro-drive or other device, to provide additional storage. Each of the processor 1452, the memory 1464, the display 1454, the communication interface 1466, and the transceiver 1468, are interconnected using various buses, and several of the components may be mounted on a common motherboard or in other manners as appropriate.

The processor 1452 can execute instructions within the mobile computing device 1450, including instructions stored in the memory 1464. The processor 1452 may be implemented as a chipset of chips that include separate and multiple analog and digital processors. The processor 1452 may provide, for example, for coordination of the other components of the mobile computing device 1450, such as control of user interfaces, applications run by the mobile computing device 1450, and wireless communication by the mobile computing device 1450.

The processor 1452 may communicate with a user through a control interface 1458 and a display interface 1456 coupled to the display 1454. The display 1454 may be, for example, a TFT (Thin-Film-Transistor Liquid Crystal Display) display or an OLED (Organic Light Emitting Diode) display, or other appropriate display technology. The display interface 1456 may comprise appropriate circuitry for driving the display 1454 to present graphical and other information to a user. The control interface 1458 may receive commands from a user and convert them for submission to the processor 1452. In addition, an external interface 1462 may provide communication with the processor 1452, so as to enable near area communication of the mobile computing device 1450 with other devices. The external interface 1462 may provide, for example, for wired communication in some implementations, or for wireless communication in other implementations, and multiple interfaces may also be used.

The memory 1464 stores information within the mobile computing device 1450. The memory 1464 can be implemented as one or more of a computer-readable medium or media, a volatile memory unit or units, or a non-volatile memory unit or units. An expansion memory 1474 may also be provided and connected to the mobile computing device 1450 through an expansion interface 1472, which may include, for example, a SIMM (Single In Line Memory Module) card interface. The expansion memory 1474 may provide extra storage space for the mobile computing device 1450, or may also store applications or other information for the mobile computing device 1450. Specifically, the expansion memory 1474 may include instructions to carry out or supplement the processes described above, and may include secure information also. Thus, for example, the expansion memory 1474 may be provided as a security module for the mobile computing device 1450, and may be programmed with instructions that permit secure use of the mobile computing device 1450. In addition, secure applications may be provided via the SIMM cards, along with additional information, such as placing identifying information on the SIMM card in a non-hackable manner.

The memory may include, for example, flash memory and/or NVRAM memory (non-volatile random access memory), as discussed below. In some implementations, instructions are stored in an information carrier and, when executed by one or more processing devices (for example, processor 1452), perform one or more methods, such as those described above. The instructions can also be stored by one or more storage devices, such as one or more computer- or machine-readable mediums (for example, the memory 1464, the expansion memory 1474, or memory on the processor 1452). In some implementations, the instructions can be received in a propagated signal, for example, over the transceiver 1468 or the external interface 1462.

The mobile computing device 1450 may communicate wirelessly through the communication interface 1466, which may include digital signal processing circuitry where necessary. The communication interface 1466 may provide for communications under various modes or protocols, such as GSM voice calls (Global System for Mobile communications), SMS (Short Message Service), EMS (Enhanced Messaging Service), or MMS messaging (Multimedia Messaging Service), CDMA (code division multiple access), TDMA (time division multiple access), PDC (Personal Digital Cellular), WCDMA (Wideband Code Division Multiple Access), CDMA2000, or GPRS (General Packet Radio Service), among others. Such communication may occur, for example, through the transceiver 1468 using a radio-frequency. In addition, short-range communication may occur, such as using a Bluetooth®, Wi-Fi™, or other such transceiver (not shown). In addition, a GPS (Global Positioning System) receiver module 1470 may provide additional navigation- and location-related wireless data to the mobile computing device 1450, which may be used as appropriate by applications running on the mobile computing device 1450.

The mobile computing device 1450 may also communicate audibly using an audio codec 1460, which may receive spoken information from a user and convert it to usable digital information. The audio codec 1460 may likewise generate audible sound for a user, such as through a speaker, e.g., in a handset of the mobile computing device 1450. Such sound may include sound from voice telephone calls, may include recorded sound (e.g., voice messages, music files, etc.) and may also include sound generated by applications operating on the mobile computing device 1450.

The mobile computing device 1450 may be implemented in a number of different forms, as shown in the figure. For example, it may be implemented as a cellular telephone 1480. It may also be implemented as part of a smart-phone 1482, personal digital assistant, or other similar mobile device.

Various implementations of the systems and techniques described here can be realized in digital electronic circuitry, integrated circuitry, specially designed ASICs (application specific integrated circuits), computer hardware, firmware, software, and/or combinations thereof. These various implementations can include implementation in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, coupled to receive data and instructions from, and to transmit data and instructions to, a storage system, at least one input device, and at least one output device.

These computer programs (also known as programs, software, software applications or code) include machine instructions for a programmable processor, and can be implemented in a high-level procedural and/or object-oriented programming language, and/or in assembly/machine language. As used herein, the terms machine-readable medium and computer-readable medium refer to any computer program product, apparatus and/or device (e.g., magnetic discs, optical disks, memory, Programmable Logic Devices (PLDs)) used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term machine-readable signal refers to any signal used to provide machine instructions and/or data to a programmable processor.

To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user and a keyboard and a pointing device (e.g., a mouse or a trackball) by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a back end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front end component (e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back end, middleware, or front end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network (LAN), a wide area network (WAN), and the Internet.

The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.

In view of the structure, functions and apparatus of the systems and methods described here, in some implementations, a system and method for performing surgery with a robotic surgical system are provided. Having described certain implementations of methods and apparatus for supporting a robotic surgical system, it will now become apparent to one of skill in the art that other implementations incorporating the concepts of the disclosure may be used. Therefore, the disclosure should not be limited to certain implementations, but rather should be limited only by the spirit and scope of the following claims.

Throughout the description, where apparatus and systems are described as having, including, or comprising specific components, or where processes and methods are described as having, including, or comprising specific steps, it is contemplated that, additionally, there are apparatus, and systems of the disclosed technology that consist essentially of, or consist of, the recited components, and that there are processes and methods according to the disclosed technology that consist essentially of, or consist of, the recited processing steps.

It should be understood that the order of steps or order for performing certain action is immaterial so long as the disclosed technology remains operable. Moreover, two or more steps or actions may be conducted simultaneously.

Claims

1. A method of performing surgery with a robotic surgical system, the method comprising: moving a mobile cart transporting a robotic surgical system comprising a robotic arm in proximity to an operating table, wherein the robotic arm has an end effector comprising a surgical instrument guide for guiding a surgical instrument, the surgical instrument guide having an internal handle and a sterile handle, wherein the sterile handle comprises: a tightening sleeve comprising a hollow tubular structure having a first open end, said structure defining an axis along which the internal handle of the surgical instrument guide may be inserted, the tightening sleeve comprising two or more openings along a length of the tightening sleeve allowing the tightening sleeve to mechanically flex under tension, wherein no part of the surgical instrument is received in the tightening sleeve,a sterile handle housing comprising a hollow tubular structure having a first open end, said structure of the sterile handle housing defining an axis along which the tightening sleeve may be inserted,a tightening nut coupled to the sterile handle housing and comprising a thread on an interior of the tightening nut, wherein the tightening nut is configured to engage a thread on exterior of the tightening sleeve and thereby tighten the tightening sleeve such that a diameter of a portion of the tightening sleeve decreases and securely holds a portion of the internal handle of the surgical instrument guide, andan electrical assembly comprising one or more input devices for commanding the robotic surgical system;stabilizing the mobile cart;maneuvering the robotic arm to a desired position to align an axis defined by the surgical instrument guide at a desired trajectory in relation to a patient situation;fixing the position of the robotic arm; andmaneuvering a surgical instrument in a manner that is constrained by the surgical instrument guide.
2. The method of claim 1, wherein the surgical instrument guide is configured to at least one of hold and restrict movement of a second surgical instrument therethrough.
3. The method of claim 2, wherein the surgical instrument is a drill bit.
4. The method of claim 3, wherein the surgical instrument guide is a drill bit guide.
5. The method of claim 4, further comprising: maneuvering the drill bit through the drill bit guide.
6. The method of claim 1, further comprising: maneuvering the surgical instrument through the surgical instrument guide.
7. The method of claim 1, wherein the robotic surgical system is for use in spinal surgery.
8. The method of claim 1, wherein the one or more input devices comprises two or more buttons configured to enable a user to active one or more of the two or more buttons to place the robotic surgical system in one of a rotation mode, a translation mode, or course positioning mode that allows translation and rotation movements.
9. The method of claim 8, wherein, upon selection of a first button of the two or more buttons, the robotic surgical system is in the rotation mode, upon selection of a second button of the two or more buttons, the robotic surgical system is in the translation mode, and upon selection of both the first and second buttons, the robotic surgical system is in the combined translation and rotation mode.
10. The method of claim 1, wherein the surgical instrument guide includes a guide tube having an axis which is disposed at an angle to the axis of the internal handle.
11. The method of claim 1, wherein the sterile handle comprises one or more sensors configured to detect a presence of a surgeon's hand in proximity to the sterile handle.
12. The method of claim 1, wherein the sterile handle is configured to be attached directly or indirectly to an end-effector of the robotic surgical system.
13. The method of claim 1, wherein the robotic surgical system is configured to allow robotically-assisted or unassisted positioning and/or movement of the sterile handle by a user with at least six degrees of freedom, wherein the six degrees of freedom are three degrees of translations and three degrees of rotations.
14. The method of claim 1, wherein the sterile handle is at least one of completely or partially disposable.
15. The method of claim 1, wherein the surgical instrument guide is configured to be used to guide a screw implant and a tissue protector.
16. The method of claim 1, wherein the sterile handle is removably attached to the robotic arm.
17. The method of claim 16, wherein the axis can be aligned with the desired trajectory in relation to the patient situation via the sterile handle.
18. The method of claim 17, wherein stabilizing the mobile cart comprises extracting one or more rigid legs on the mobile cart such that the mobile cart rests on the one or more rigid legs of the mobile cart.
19. The method of claim 18, wherein stabilizing the mobile cart comprises retracting one or more wheels on the mobile cart such that the mobile cart rests on one or more rigid legs of the mobile cart.
20. A method of performing surgery with a robotic surgical system, the method comprising: moving a mobile cart transporting a robotic surgical system comprising a robotic arm, wherein the robotic arm has an end effector comprising a surgical instrument guide for guiding a surgical instrument, the surgical instrument guide having an internal handle and a sterile handle, wherein the sterile handle comprises: a tightening sleeve comprising a hollow tubular structure having a first open end, said structure defining an axis along which the internal handle of the surgical instrument guide may be inserted, the tightening sleeve configured to mechanically flex under tension, wherein no part of the surgical instrument is received in the tightening sleeve,a sterile handle housing comprising a hollow tubular structure having a first open end, said structure of the sterile handle housing defining an axis along which the tightening sleeve may be inserted,a tightening nut coupled to the sterile handle housing and comprising a thread on an interior of the tightening nut, wherein the tightening nut is configured to engage a thread on exterior of the tightening sleeve and thereby tighten the tightening sleeve such that a diameter of a portion of the tightening sleeve decreases and securely holds a portion of the internal handle of the surgical instrument guide, andan electrical assembly comprising one or more input devices for commanding the robotic surgical system;stabilizing the mobile cart;maneuvering the robotic arm to a desired position to align an axis defined by the surgical instrument guide at a desired trajectory in relation to a patient situation.

RELATED APPLICATIONS

The present application is a continuation application of U.S. patent application Ser. No. 14/619,732, filed on Feb. 11, 2015 know U.S. Pat. No. 10,039,605), which claims priority to U.S. Provisional Application No. 61/938,423, filed Feb. 11, 2014 (expired); and U.S. Provisional Application No. 61/950,550, filed Mar. 10, 2014 (expired), the contents of each of which are hereby incorporated by reference in their entireties.

US Referenced Citations (683)

Number	Name	Date	Kind
4150293	Franke	Apr 1979	A
5246010	Gazzara et al.	Sep 1993	A
5354314	Hardy et al.	Oct 1994	A
5397323	Taylor et al.	Mar 1995	A
5598453	Baba et al.	Jan 1997	A
5772594	Barrick	Jun 1998	A
5791908	Gillio	Aug 1998	A
5820559	Ng et al.	Oct 1998	A
5825982	Wright et al.	Oct 1998	A
5887121	Funda et al.	Mar 1999	A
5911449	Daniele et al.	Jun 1999	A
5951475	Gueziec et al.	Sep 1999	A
5987960	Messner et al.	Nov 1999	A
6012216	Esteves et al.	Jan 2000	A
6031888	Ivan et al.	Feb 2000	A
6033415	Mittelstadt et al.	Mar 2000	A
6080181	Jensen et al.	Jun 2000	A
6106511	Jensen	Aug 2000	A
6122541	Cosman et al.	Sep 2000	A
6144875	Schweikard et al.	Nov 2000	A
6157853	Blume et al.	Dec 2000	A
6167145	Foley et al.	Dec 2000	A
6167292	Badano et al.	Dec 2000	A
6201984	Funda et al.	Mar 2001	B1
6203196	Meyer et al.	Mar 2001	B1
6205411	DiGioia, III et al.	Mar 2001	B1
6212419	Blume et al.	Apr 2001	B1
6231565	Tovey et al.	May 2001	B1
6236875	Bucholz et al.	May 2001	B1
6246900	Cosman et al.	Jun 2001	B1
6301495	Gueziec et al.	Oct 2001	B1
6306126	Montezuma	Oct 2001	B1
6312435	Wallace et al.	Nov 2001	B1
6314311	Williams et al.	Nov 2001	B1
6320929	Von Der Haar	Nov 2001	B1
6322567	Mittelstadt et al.	Nov 2001	B1
6325808	Bernard et al.	Dec 2001	B1
6340363	Bolger et al.	Jan 2002	B1
6377011	Ben-Ur	Apr 2002	B1
6379302	Kessman et al.	Apr 2002	B1
6402762	Hunter et al.	Jun 2002	B2
6424885	Niemeyer et al.	Jul 2002	B1
6447503	Wynne et al.	Sep 2002	B1
6451027	Cooper et al.	Sep 2002	B1
6477400	Barrick	Nov 2002	B1
6484049	Seeley et al.	Nov 2002	B1
6487267	Wolter	Nov 2002	B1
6490467	Bucholz et al.	Dec 2002	B1
6490475	Seeley et al.	Dec 2002	B1
6499488	Hunter et al.	Dec 2002	B1
6501981	Schweikard et al.	Dec 2002	B1
6507751	Blume et al.	Jan 2003	B2
6535756	Simon et al.	Mar 2003	B1
6560354	Maurer, Jr. et al.	May 2003	B1
6565554	Niemeyer	May 2003	B1
6587750	Gerbi et al.	Jul 2003	B2
6614453	Sun et al.	Sep 2003	B1
6614871	Kobiki et al.	Sep 2003	B1
6619840	Rasche et al.	Sep 2003	B2
6636757	Jascob et al.	Oct 2003	B1
6645196	Nixon et al.	Nov 2003	B1
6666579	Jensen	Dec 2003	B2
6669635	Kessman et al.	Dec 2003	B2
6701173	Nowinski et al.	Mar 2004	B2
6757068	Foxlin	Jun 2004	B2
6782287	Grzeszczuk et al.	Aug 2004	B2
6783524	Anderson et al.	Aug 2004	B2
6786896	Madhani et al.	Sep 2004	B1
6788018	Blumenkranz	Sep 2004	B1
6804581	Wang et al.	Oct 2004	B2
6823207	Jensen et al.	Nov 2004	B1
6827351	Graziani et al.	Dec 2004	B2
6837892	Shoham	Jan 2005	B2
6839612	Sanchez et al.	Jan 2005	B2
6856826	Seeley et al.	Feb 2005	B2
6856827	Seeley et al.	Feb 2005	B2
6879880	Nowlin et al.	Apr 2005	B2
6892090	Verard et al.	May 2005	B2
6920347	Simon et al.	Jul 2005	B2
6922632	Foxlin	Jul 2005	B2
6968224	Kessman et al.	Nov 2005	B2
6978166	Foley et al.	Dec 2005	B2
6988009	Grimm et al.	Jan 2006	B2
6991627	Madhani et al.	Jan 2006	B2
6996487	Jutras et al.	Feb 2006	B2
6999852	Green	Feb 2006	B2
7007699	Martinelli et al.	Mar 2006	B2
7016457	Senzig et al.	Mar 2006	B1
7043961	Pandey et al.	May 2006	B2
7062006	Pelc et al.	Jun 2006	B1
7063705	Young et al.	Jun 2006	B2
7072707	Galloway, Jr. et al.	Jul 2006	B2
7083615	Peterson et al.	Aug 2006	B2
7097640	Wang et al.	Aug 2006	B2
7099428	Clinthorne et al.	Aug 2006	B2
7108421	Gregerson et al.	Sep 2006	B2
7130676	Barrick	Oct 2006	B2
7139418	Abovitz et al.	Nov 2006	B2
7139601	Bucholz et al.	Nov 2006	B2
7155316	Sutherland et al.	Dec 2006	B2
7164968	Treat et al.	Jan 2007	B2
7167738	Schweikard et al.	Jan 2007	B2
7169141	Brock et al.	Jan 2007	B2
7172627	Fiere et al.	Feb 2007	B2
7194120	Wicker et al.	Mar 2007	B2
7197107	Arai et al.	Mar 2007	B2
7231014	Levy	Jun 2007	B2
7231063	Naimark et al.	Jun 2007	B2
7239940	Wang et al.	Jul 2007	B2
7248914	Hastings et al.	Jul 2007	B2
7301648	Foxlin	Nov 2007	B2
7302288	Schellenberg	Nov 2007	B1
7313430	Urquhart et al.	Dec 2007	B2
7318805	Schweikard et al.	Jan 2008	B2
7318827	Leitner et al.	Jan 2008	B2
7319897	Leitner et al.	Jan 2008	B2
7324623	Heuscher et al.	Jan 2008	B2
7327865	Fu et al.	Feb 2008	B2
7331967	Lee et al.	Feb 2008	B2
7333642	Green	Feb 2008	B2
7339341	Oleynikov et al.	Mar 2008	B2
7366562	Dukesherer et al.	Apr 2008	B2
7379790	Toth et al.	May 2008	B2
7386365	Nixon	Jun 2008	B2
7422592	Morley et al.	Sep 2008	B2
7435216	Kwon et al.	Oct 2008	B2
7440793	Chauhan et al.	Oct 2008	B2
7460637	Clinthorne et al.	Dec 2008	B2
7466303	Yi et al.	Dec 2008	B2
7493153	Ahmed et al.	Feb 2009	B2
7505617	Fu et al.	Mar 2009	B2
7533892	Schena et al.	May 2009	B2
7542791	Mire et al.	Jun 2009	B2
7555331	Viswanathan	Jun 2009	B2
7567834	Clayton et al.	Jul 2009	B2
7594912	Cooper et al.	Sep 2009	B2
7606613	Simon et al.	Oct 2009	B2
7607440	Coste-Maniere et al.	Oct 2009	B2
7623902	Pacheco	Nov 2009	B2
7630752	Viswanathan	Dec 2009	B2
7630753	Simon et al.	Dec 2009	B2
7643862	Schoenefeld	Jan 2010	B2
7660623	Hunter et al.	Feb 2010	B2
7661881	Gregerson et al.	Feb 2010	B2
7683331	Chang	Mar 2010	B2
7683332	Chang	Mar 2010	B2
7689320	Prisco et al.	Mar 2010	B2
7691098	Wallace et al.	Apr 2010	B2
7702379	Avinash et al.	Apr 2010	B2
7702477	Tuemmler et al.	Apr 2010	B2
7711083	Heigl et al.	May 2010	B2
7711406	Kuhn et al.	May 2010	B2
7720523	Omernick et al.	May 2010	B2
7725253	Foxlin	May 2010	B2
7726171	Langlotz et al.	Jun 2010	B2
7742801	Neubauer et al.	Jun 2010	B2
7751865	Jascob et al.	Jul 2010	B2
7760849	Zhang	Jul 2010	B2
7762825	Burbank et al.	Jul 2010	B2
7763015	Cooper et al.	Jul 2010	B2
7787699	Mahesh et al.	Aug 2010	B2
7796728	Bergfjord	Sep 2010	B2
7813838	Sommer	Oct 2010	B2
7818044	Dukesherer et al.	Oct 2010	B2
7819859	Prisco et al.	Oct 2010	B2
7824401	Manzo et al.	Nov 2010	B2
7831294	Viswanathan	Nov 2010	B2
7834484	Sartor	Nov 2010	B2
7835557	Kendrick et al.	Nov 2010	B2
7835778	Foley et al.	Nov 2010	B2
7835784	Mire et al.	Nov 2010	B2
7840253	Tremblay et al.	Nov 2010	B2
7840256	Lakin et al.	Nov 2010	B2
7843158	Prisco	Nov 2010	B2
7844320	Shahidi	Nov 2010	B2
7853305	Simon et al.	Dec 2010	B2
7853313	Thompson	Dec 2010	B2
7865269	Prisco et al.	Jan 2011	B2
D631966	Perloff et al.	Feb 2011	S
7879045	Gielen et al.	Feb 2011	B2
7881767	Strommer et al.	Feb 2011	B2
7881770	Melkent et al.	Feb 2011	B2
7886743	Cooper et al.	Feb 2011	B2
RE42194	Foley et al.	Mar 2011	E
RE42226	Foley et al.	Mar 2011	E
7900524	Calloway et al.	Mar 2011	B2
7907166	Lamprecht et al.	Mar 2011	B2
7909122	Schena et al.	Mar 2011	B2
7925653	Saptharishi	Apr 2011	B2
7930065	Larkin et al.	Apr 2011	B2
7935130	Williams	May 2011	B2
7940999	Liao et al.	May 2011	B2
7945012	Ye et al.	May 2011	B2
7945021	Shapiro et al.	May 2011	B2
7953470	Vetter et al.	May 2011	B2
7954397	Choi et al.	Jun 2011	B2
7971341	Dukesherer et al.	Jul 2011	B2
7974674	Hauck et al.	Jul 2011	B2
7974677	Mire et al.	Jul 2011	B2
7974681	Wallace et al.	Jul 2011	B2
7979157	Anvari	Jul 2011	B2
7983733	Viswanathan	Jul 2011	B2
7988215	Seibold	Aug 2011	B2
7996110	Lipow et al.	Aug 2011	B2
8004121	Sartor	Aug 2011	B2
8004229	Nowlin et al.	Aug 2011	B2
8010177	Csavoy et al.	Aug 2011	B2
8019045	Kato	Sep 2011	B2
8021310	Sanborn et al.	Sep 2011	B2
8035685	Jensen	Oct 2011	B2
8046054	Kim et al.	Oct 2011	B2
8046057	Clarke	Oct 2011	B2
8052688	Wolf, II	Nov 2011	B2
8054184	Cline et al.	Nov 2011	B2
8054752	Druke et al.	Nov 2011	B2
8057397	Li et al.	Nov 2011	B2
8057407	Martinelli et al.	Nov 2011	B2
8062288	Cooper et al.	Nov 2011	B2
8062375	Glerum et al.	Nov 2011	B2
8066524	Burbank et al.	Nov 2011	B2
8073335	Labonville et al.	Dec 2011	B2
8079950	Stern et al.	Dec 2011	B2
8086299	Adler et al.	Dec 2011	B2
8092370	Roberts et al.	Jan 2012	B2
8098914	Liao et al.	Jan 2012	B2
8100950	St. Clair et al.	Jan 2012	B2
8105320	Manzo	Jan 2012	B2
8108025	Csavoy et al.	Jan 2012	B2
8109877	Moctezuma de la Barrera et al.	Feb 2012	B2
8112292	Simon	Feb 2012	B2
8116430	Shapiro et al.	Feb 2012	B1
8120301	Goldberg et al.	Feb 2012	B2
8121249	Wang et al.	Feb 2012	B2
8123675	Funda et al.	Feb 2012	B2
8133229	Bonutti	Mar 2012	B1
8142420	Schena	Mar 2012	B2
8147494	Leitner et al.	Apr 2012	B2
8150494	Simon et al.	Apr 2012	B2
8150497	Gielen et al.	Apr 2012	B2
8150498	Gielen et al.	Apr 2012	B2
8165658	Waynik et al.	Apr 2012	B2
8170313	Kendrick et al.	May 2012	B2
8179073	Farritor et al.	May 2012	B2
8182476	Julian et al.	May 2012	B2
8184880	Zhao et al.	May 2012	B2
8202278	Orban, III et al.	Jun 2012	B2
8208708	Homan et al.	Jun 2012	B2
8208988	Jensen	Jun 2012	B2
8219177	Smith et al.	Jul 2012	B2
8219178	Smith et al.	Jul 2012	B2
8220468	Cooper et al.	Jul 2012	B2
8224024	Foxlin et al.	Jul 2012	B2
8224484	Swarup et al.	Jul 2012	B2
8225798	Baldwin et al.	Jul 2012	B2
8228368	Zhao et al.	Jul 2012	B2
8231610	Jo et al.	Jul 2012	B2
8263933	Hartmann et al.	Jul 2012	B2
8239001	Verard et al.	Aug 2012	B2
8241271	Millman et al.	Aug 2012	B2
8248413	Gattani et al.	Aug 2012	B2
8256319	Cooper et al.	Sep 2012	B2
8271069	Jascob et al.	Sep 2012	B2
8271130	Hourtash	Sep 2012	B2
8281670	Larkin et al.	Oct 2012	B2
8282653	Nelson et al.	Oct 2012	B2
8301226	Csavoy et al.	Oct 2012	B2
8311611	Csavoy et al.	Nov 2012	B2
8320991	Jascob et al.	Nov 2012	B2
8332012	Kienzle, III	Dec 2012	B2
8333755	Cooper et al.	Dec 2012	B2
8335552	Stiles	Dec 2012	B2
8335557	Maschke	Dec 2012	B2
8348931	Cooper et al.	Jan 2013	B2
8353963	Glerum	Jan 2013	B2
8358818	Miga et al.	Jan 2013	B2
8359730	Burg et al.	Jan 2013	B2
8374673	Adcox et al.	Feb 2013	B2
8374723	Zhao et al.	Feb 2013	B2
8379791	Forthmann et al.	Feb 2013	B2
8386019	Camus et al.	Feb 2013	B2
8392022	Ortmaier et al.	Mar 2013	B2
8394099	Patwardhan	Mar 2013	B2
8395342	Prisco	Mar 2013	B2
8398634	Manzo et al.	Mar 2013	B2
8400094	Schena	Mar 2013	B2
8414957	Enzerink et al.	Apr 2013	B2
8418073	Mohr et al.	Apr 2013	B2
8450694	Baviera et al.	May 2013	B2
8452447	Nixon	May 2013	B2
RE44305	Foley et al.	Jun 2013	E
8462911	Vesel et al.	Jun 2013	B2
8465476	Rogers et al.	Jun 2013	B2
8465771	Wan et al.	Jun 2013	B2
8467851	Mire et al.	Jun 2013	B2
8467852	Csavoy et al.	Jun 2013	B2
8469947	Devengenzo et al.	Jun 2013	B2
RE44392	Hynes	Jul 2013	E
8483434	Buehner et al.	Jul 2013	B2
8483800	Jensen et al.	Jul 2013	B2
8486532	Enzerink et al.	Jul 2013	B2
8489235	Moll et al.	Jul 2013	B2
8500722	Cooper	Aug 2013	B2
8500728	Newton et al.	Aug 2013	B2
8504201	Moll et al.	Aug 2013	B2
8506555	Ruiz Morales	Aug 2013	B2
8506556	Schena	Aug 2013	B2
8508173	Goldberg et al.	Aug 2013	B2
8512318	Tovey et al.	Aug 2013	B2
8515576	Lipow et al.	Aug 2013	B2
8518120	Glerum et al.	Aug 2013	B2
8521331	Itkowitz	Aug 2013	B2
8526688	Groszmann et al.	Sep 2013	B2
8526700	Issacs	Sep 2013	B2
8527094	Kumar et al.	Sep 2013	B2
8528440	Morley et al.	Sep 2013	B2
8532741	Heruth et al.	Sep 2013	B2
8541970	Nowlin et al.	Sep 2013	B2
8548563	Simon et al.	Oct 2013	B2
8549732	Burg et al.	Oct 2013	B2
8551114	Ramos de la Pena	Oct 2013	B2
8551116	Julian et al.	Oct 2013	B2
8556807	Scott et al.	Oct 2013	B2
8556979	Glerum et al.	Oct 2013	B2
8560118	Green et al.	Oct 2013	B2
8561473	Blumenkranz	Oct 2013	B2
8562594	Cooper et al.	Oct 2013	B2
8571638	Shoham	Oct 2013	B2
8571710	Coste-Maniere et al.	Oct 2013	B2
8573465	Shelton, IV	Nov 2013	B2
8574303	Sharkey et al.	Nov 2013	B2
8585420	Burbank et al.	Nov 2013	B2
8594841	Zhao et al.	Nov 2013	B2
8597198	Sanborn et al.	Dec 2013	B2
8600478	Verard et al.	Dec 2013	B2
8603077	Cooper et al.	Dec 2013	B2
8611985	Lavallee et al.	Dec 2013	B2
8613230	Blumenkranz et al.	Dec 2013	B2
8621939	Blumenkranz et al.	Jan 2014	B2
8624537	Nowlin et al.	Jan 2014	B2
8630389	Kato	Jan 2014	B2
8634897	Simon et al.	Jan 2014	B2
8634957	Toth et al.	Jan 2014	B2
8638056	Goldberg et al.	Jan 2014	B2
8638057	Goldberg et al.	Jan 2014	B2
8639000	Zhao et al.	Jan 2014	B2
8641726	Bonutti	Feb 2014	B2
8644907	Hartmann et al.	Feb 2014	B2
8657809	Schoepp	Feb 2014	B2
8660635	Simon et al.	Feb 2014	B2
8666544	Moll et al.	Mar 2014	B2
8675939	Moctezuma de la Barrera	Mar 2014	B2
8678647	Gregerson et al.	Mar 2014	B2
8679125	Smith et al.	Mar 2014	B2
8679183	Glerum et al.	Mar 2014	B2
8682413	Lloyd	Mar 2014	B2
8684253	Giordano et al.	Apr 2014	B2
8685098	Glerum et al.	Apr 2014	B2
8693730	Umasuthan et al.	Apr 2014	B2
8694075	Groszmann et al.	Apr 2014	B2
8696458	Foxlin et al.	Apr 2014	B2
8700123	Okamura et al.	Apr 2014	B2
8706086	Glerum	Apr 2014	B2
8706185	Foley et al.	Apr 2014	B2
8706301	Zhao et al.	Apr 2014	B2
8717430	Simon et al.	May 2014	B2
8727618	Maschke et al.	May 2014	B2
8734432	Tuma et al.	May 2014	B2
8738115	Amberg et al.	May 2014	B2
8738181	Greer et al.	May 2014	B2
8740882	Jun et al.	Jun 2014	B2
8746252	McGrogan et al.	Jun 2014	B2
8749189	Nowlin et al.	Jun 2014	B2
8749190	Nowlin et al.	Jun 2014	B2
8761930	Nixon	Jun 2014	B2
8764448	Yang et al.	Jul 2014	B2
8771170	Mesallum et al.	Jul 2014	B2
8781186	Clements et al.	Jul 2014	B2
8781630	Banks et al.	Jul 2014	B2
8784385	Boyden et al.	Jul 2014	B2
8786241	Nowlin et al.	Jul 2014	B2
8787520	Baba	Jul 2014	B2
8792704	Isaacs	Jul 2014	B2
8798231	Notohara et al.	Aug 2014	B2
8800838	Shelton, IV	Aug 2014	B2
8808164	Hoffman et al.	Aug 2014	B2
8812077	Dempsey	Aug 2014	B2
8814793	Brabrand	Aug 2014	B2
8816628	Nowlin et al.	Aug 2014	B2
8818105	Myronenko et al.	Aug 2014	B2
8820605	Shelton, IV	Sep 2014	B2
8821511	von Jako et al.	Sep 2014	B2
8823308	Nowlin et al.	Sep 2014	B2
8827996	Scott et al.	Sep 2014	B2
8828024	Farritor et al.	Sep 2014	B2
8830224	Zhao et al.	Sep 2014	B2
8834489	Cooper et al.	Sep 2014	B2
8834490	Bonutti	Sep 2014	B2
8838270	Druke et al.	Sep 2014	B2
8844789	Shelton, IV et al.	Sep 2014	B2
8855822	Bartol et al.	Oct 2014	B2
8858598	Seifert et al.	Oct 2014	B2
8860753	Bhandarkar et al.	Oct 2014	B2
8864751	Prisco et al.	Oct 2014	B2
8864798	Weiman et al.	Oct 2014	B2
8864833	Glerum et al.	Oct 2014	B2
8867703	Shapiro et al.	Oct 2014	B2
8870880	Himmelberger et al.	Oct 2014	B2
8876866	Zappacosta et al.	Nov 2014	B2
8880223	Raj et al.	Nov 2014	B2
8882803	Iott et al.	Nov 2014	B2
8883210	Truncale et al.	Nov 2014	B1
8888821	Rezach et al.	Nov 2014	B2
8888853	Glerum et al.	Nov 2014	B2
8888854	Glerum et al.	Nov 2014	B2
8894652	Seifert et al.	Nov 2014	B2
8894688	Suh	Nov 2014	B2
8894691	Iott et al.	Nov 2014	B2
8906069	Hansell et al.	Dec 2014	B2
8964934	Ein-Gal	Feb 2015	B2
8992580	Bar et al.	Mar 2015	B2
8996169	Lightcap et al.	Mar 2015	B2
9001963	Sowards-Emmerd et al.	Apr 2015	B2
9002076	Khadem et al.	Apr 2015	B2
9044190	Rubner et al.	Jun 2015	B2
9107683	Hourtash et al.	Aug 2015	B2
9125556	Zehavi et al.	Sep 2015	B2
9131986	Greer et al.	Sep 2015	B2
9215968	Schostek et al.	Dec 2015	B2
9308050	Kostrzewski et al.	Apr 2016	B2
9380984	Li et al.	Jul 2016	B2
9393039	Lechner et al.	Jul 2016	B2
9398886	Gregerson et al.	Jul 2016	B2
9398890	Dong et al.	Jul 2016	B2
9414859	Ballard et al.	Aug 2016	B2
9420975	Gutfleisch et al.	Aug 2016	B2
9492235	Hourtash et al.	Nov 2016	B2
9592096	Maillet et al.	Mar 2017	B2
9750465	Engel et al.	Sep 2017	B2
9757203	Hourtash et al.	Sep 2017	B2
9795354	Menegaz et al.	Oct 2017	B2
9814535	Bar et al.	Nov 2017	B2
9820783	Donner et al.	Nov 2017	B2
9833265	Donner et al.	Nov 2017	B2
9848922	Tohmeh et al.	Dec 2017	B2
9925011	Gombert et al.	Mar 2018	B2
9931025	Graetzel et al.	Apr 2018	B1
10034717	Miller et al.	Jul 2018	B2
10039605	Kostrzewski	Aug 2018	B2
20010036302	Miller	Nov 2001	A1
20020035321	Bucholz et al.	Mar 2002	A1
20040068172	Nowinski et al.	Apr 2004	A1
20040076259	Jensen et al.	Apr 2004	A1
20050096502	Khalili	May 2005	A1
20050143651	Verard et al.	Jun 2005	A1
20050171558	Abovitz et al.	Aug 2005	A1
20060100610	Wallace et al.	May 2006	A1
20060142657	Quaid	Jun 2006	A1
20060173329	Marquart et al.	Aug 2006	A1
20060184396	Dennis et al.	Aug 2006	A1
20060241416	Marquart et al.	Oct 2006	A1
20060291612	Nishide et al.	Dec 2006	A1
20070015987	Benlloch Baviera et al.	Jan 2007	A1
20070021738	Hasser et al.	Jan 2007	A1
20070038059	Sheffer et al.	Feb 2007	A1
20070073133	Schoenefeld	Mar 2007	A1
20070156121	Millman et al.	Jul 2007	A1
20070156157	Nahum et al.	Jul 2007	A1
20070167712	Keglovich et al.	Jul 2007	A1
20070233238	Huynh et al.	Oct 2007	A1
20070270685	Kang	Nov 2007	A1
20080004523	Jensen	Jan 2008	A1
20080013809	Zhu et al.	Jan 2008	A1
20080033283	Dellaca et al.	Feb 2008	A1
20080046122	Manzo et al.	Feb 2008	A1
20080082109	Moll et al.	Apr 2008	A1
20080108912	Node-Langlois	May 2008	A1
20080108991	von Jako	May 2008	A1
20080109012	Falco et al.	May 2008	A1
20080144906	Allred et al.	Jun 2008	A1
20080161680	von Jako et al.	Jul 2008	A1
20080161682	Kendrick et al.	Jul 2008	A1
20080177203	von Jako	Jul 2008	A1
20080214922	Hartmann et al.	Sep 2008	A1
20080228068	Viswanathan et al.	Sep 2008	A1
20080228196	Wang et al.	Sep 2008	A1
20080235052	Node-Langlois et al.	Sep 2008	A1
20080269596	Revie et al.	Oct 2008	A1
20080287771	Anderson	Nov 2008	A1
20080287781	Revie et al.	Nov 2008	A1
20080300477	Lloyd et al.	Dec 2008	A1
20080300478	Zuhars et al.	Dec 2008	A1
20080302950	Park et al.	Dec 2008	A1
20080306490	Lakin et al.	Dec 2008	A1
20080319311	Hamadeh	Dec 2008	A1
20090012509	Csavoy et al.	Jan 2009	A1
20090030428	Omori et al.	Jan 2009	A1
20090080737	Battle et al.	Mar 2009	A1
20090185655	Koken et al.	Jul 2009	A1
20090198121	Hoheisel	Aug 2009	A1
20090216113	Meier et al.	Aug 2009	A1
20090228019	Gross et al.	Sep 2009	A1
20090259123	Navab et al.	Oct 2009	A1
20090259230	Khadem et al.	Oct 2009	A1
20090264899	Appenrodt et al.	Oct 2009	A1
20090281417	Hartmann et al.	Nov 2009	A1
20100022874	Wang et al.	Jan 2010	A1
20100039506	Sarvestani et al.	Feb 2010	A1
20100125286	Wang et al.	May 2010	A1
20100130986	Mailloux et al.	May 2010	A1
20100228117	Hartmann	Sep 2010	A1
20100228265	Prisco	Sep 2010	A1
20100249571	Jensen et al.	Sep 2010	A1
20100274120	Heuscher	Oct 2010	A1
20100280363	Skarda et al.	Nov 2010	A1
20100331858	Simaan et al.	Dec 2010	A1
20110022229	Jang et al.	Jan 2011	A1
20110077504	Fischer et al.	Mar 2011	A1
20110098553	Robbins et al.	Apr 2011	A1
20110137152	Li	Jun 2011	A1
20110213384	Jeong	Sep 2011	A1
20110224684	Larkin et al.	Sep 2011	A1
20110224685	Larkin et al.	Sep 2011	A1
20110224686	Larkin et al.	Sep 2011	A1
20110224687	Larkin et al.	Sep 2011	A1
20110224688	Larkin et al.	Sep 2011	A1
20110224689	Larkin et al.	Sep 2011	A1
20110224825	Larkin et al.	Sep 2011	A1
20110230967	O'Halloran et al.	Sep 2011	A1
20110238080	Ranjit et al.	Sep 2011	A1
20110276058	Choi et al.	Nov 2011	A1
20110282189	Graumann	Nov 2011	A1
20110286573	Schretter et al.	Nov 2011	A1
20110295062	Gratacos Solsona et al.	Dec 2011	A1
20110295370	Suh et al.	Dec 2011	A1
20110306986	Lee et al.	Dec 2011	A1
20120035507	George et al.	Feb 2012	A1
20120046668	Gantes	Feb 2012	A1
20120051498	Koishi	Mar 2012	A1
20120053597	Anvari et al.	Mar 2012	A1
20120059248	Holsing et al.	Mar 2012	A1
20120071753	Hunter et al.	Mar 2012	A1
20120108954	Schulhauser et al.	May 2012	A1
20120136372	Amat Girbau et al.	May 2012	A1
20120143084	Shoham	Jun 2012	A1
20120184839	Woerlein	Jul 2012	A1
20120197182	Millman et al.	Aug 2012	A1
20120226145	Chang et al.	Sep 2012	A1
20120235909	Birkenbach et al.	Sep 2012	A1
20120245596	Meenink	Sep 2012	A1
20120253332	Moll	Oct 2012	A1
20120253360	White et al.	Oct 2012	A1
20120256092	Zingerman	Oct 2012	A1
20120294498	Popovic	Nov 2012	A1
20120296203	Hartmann et al.	Nov 2012	A1
20130006267	Odermatt et al.	Jan 2013	A1
20130016889	Myronenko et al.	Jan 2013	A1
20130030571	Ruiz Morales et al.	Jan 2013	A1
20130035583	Park et al.	Feb 2013	A1
20130060146	Yang et al.	Mar 2013	A1
20130060337	Petersheim et al.	Mar 2013	A1
20130094742	Feilkas	Apr 2013	A1
20130096574	Kang et al.	Apr 2013	A1
20130113791	Isaacs et al.	May 2013	A1
20130116706	Lee et al.	May 2013	A1
20130131695	Scarfogliero et al.	May 2013	A1
20130144307	Jeong et al.	Jun 2013	A1
20130158542	Manzo et al.	Jun 2013	A1
20130165937	Patwardhan	Jun 2013	A1
20130178867	Farritor et al.	Jul 2013	A1
20130178868	Roh	Jul 2013	A1
20130178870	Schena	Jul 2013	A1
20130204271	Brisson et al.	Aug 2013	A1
20130211419	Jensen	Aug 2013	A1
20130211420	Jensen	Aug 2013	A1
20130218142	Tuma et al.	Aug 2013	A1
20130223702	Holsing et al.	Aug 2013	A1
20130225942	Holsing et al.	Aug 2013	A1
20130225943	Holsing et al.	Aug 2013	A1
20130231556	Holsing et al.	Sep 2013	A1
20130237995	Lee et al.	Sep 2013	A1
20130245375	DiMaio et al.	Sep 2013	A1
20130261640	Kim et al.	Oct 2013	A1
20130272488	Bailey et al.	Oct 2013	A1
20130272489	Dickman et al.	Oct 2013	A1
20130274761	Devengenzo et al.	Oct 2013	A1
20130281821	Liu et al.	Oct 2013	A1
20130296884	Taylor et al.	Nov 2013	A1
20130303887	Holsing et al.	Nov 2013	A1
20130307955	Deitz et al.	Nov 2013	A1
20130317521	Choi et al.	Nov 2013	A1
20130325033	Schena et al.	Dec 2013	A1
20130325035	Hauck et al.	Dec 2013	A1
20130331686	Freysinger et al.	Dec 2013	A1
20130331858	Devengenzo et al.	Dec 2013	A1
20130331861	Yoon	Dec 2013	A1
20130342578	Isaacs	Dec 2013	A1
20130345717	Markvicka et al.	Dec 2013	A1
20130345757	Stad	Dec 2013	A1
20140001235	Shelton, IV	Jan 2014	A1
20140012131	Heruth et al.	Jan 2014	A1
20140031664	Kang et al.	Jan 2014	A1
20140046128	Lee et al.	Feb 2014	A1
20140046132	Hoeg et al.	Feb 2014	A1
20140046340	Wilson et al.	Feb 2014	A1
20140049629	Siewerdsen et al.	Feb 2014	A1
20140058406	Tsekos	Feb 2014	A1
20140073914	Lavallee et al.	Mar 2014	A1
20140080086	Chen	Mar 2014	A1
20140081128	Verard et al.	Mar 2014	A1
20140088612	Bartol et al.	Mar 2014	A1
20140094694	Moctezuma de la Barrera	Apr 2014	A1
20140094851	Gordon	Apr 2014	A1
20140096369	Matsumoto et al.	Apr 2014	A1
20140100587	Farritor et al.	Apr 2014	A1
20140121676	Kostrzewski et al.	May 2014	A1
20140128882	Kwak et al.	May 2014	A1
20140135796	Simon et al.	May 2014	A1
20140142591	Alvarez et al.	May 2014	A1
20140142592	Moon et al.	May 2014	A1
20140148692	Hartmann et al.	May 2014	A1
20140163581	Devengenzo et al.	Jun 2014	A1
20140171781	Stiles	Jun 2014	A1
20140171900	Stiles	Jun 2014	A1
20140171965	Loh et al.	Jun 2014	A1
20140180308	von Grunberg	Jun 2014	A1
20140180309	Seeber et al.	Jun 2014	A1
20140187915	Yaroshenko et al.	Jul 2014	A1
20140188132	Kang	Jul 2014	A1
20140194699	Roh et al.	Jul 2014	A1
20140130810	Azizian et al.	Aug 2014	A1
20140221819	Sarment	Aug 2014	A1
20140222023	Kim et al.	Aug 2014	A1
20140228631	Kwak et al.	Aug 2014	A1
20140234804	Huang et al.	Aug 2014	A1
20140257328	Kim et al.	Sep 2014	A1
20140257329	Jang et al.	Sep 2014	A1
20140257330	Choi et al.	Sep 2014	A1
20140275760	Lee et al.	Sep 2014	A1
20140275985	Walker et al.	Sep 2014	A1
20140276931	Parihar et al.	Sep 2014	A1
20140276940	Seo	Sep 2014	A1
20140276944	Farritor et al.	Sep 2014	A1
20140288413	Hwang et al.	Sep 2014	A1
20140299648	Shelton, IV et al.	Oct 2014	A1
20140303434	Farritor et al.	Oct 2014	A1
20140303643	Ha et al.	Oct 2014	A1
20140305995	Shelton, IV et al.	Oct 2014	A1
20140309659	Roh et al.	Oct 2014	A1
20140316436	Bar et al.	Oct 2014	A1
20140323803	Hoffman et al.	Oct 2014	A1
20140324070	Min et al.	Oct 2014	A1
20140330288	Date et al.	Nov 2014	A1
20140364720	Darrow et al.	Dec 2014	A1
20140371577	Mallet et al.	Dec 2014	A1
20150039034	Frankel et al.	Feb 2015	A1
20150085970	Bouhnik et al.	Mar 2015	A1
20150146847	Liu	May 2015	A1
20150150524	Yorkston et al.	Jun 2015	A1
20150196261	Funk	Jul 2015	A1
20150213633	Chang et al.	Jul 2015	A1
20150335480	Alvarez et al.	Nov 2015	A1
20150342647	Frankel et al.	Dec 2015	A1
20160005194	Schretter et al.	Jan 2016	A1
20160166329	Langan et al.	Jun 2016	A1
20160235480	Scholl et al.	Aug 2016	A1
20160249990	Glozman et al.	Sep 2016	A1
20160302871	Gregerson et al.	Oct 2016	A1
20160320322	Suzuki	Nov 2016	A1
20160331335	Gregerson et al.	Nov 2016	A1
20170135770	Scholl et al.	May 2017	A1
20170143284	Sehnert et al.	May 2017	A1
20170143426	Isaacs et al.	May 2017	A1
20170156816	Ibrahim	Jun 2017	A1
20170202629	Maillet et al.	Jul 2017	A1
20170212723	Atarot et al.	Jul 2017	A1
20170215825	Johnson et al.	Aug 2017	A1
20170215826	Johnson et al.	Aug 2017	A1
20170215827	Johnson et al.	Aug 2017	A1
20170231710	Scholl et al.	Aug 2017	A1
20170258426	Risher-Kelly et al.	Sep 2017	A1
20170273748	Hourtash et al.	Sep 2017	A1
20170296277	Hourtash et al.	Oct 2017	A1
20170360493	Zucker et al.	Dec 2017	A1

Non-Patent Literature Citations (1)

Entry
US 8,231,638 B2, 07/2012, Swarup et al. (withdrawn)

Related Publications (1)

	Number	Date	Country
	20180325609 A1	Nov 2018	US

Provisional Applications (2)

	Number	Date	Country
	61950550	Mar 2014	US
	61938423	Feb 2014	US

Continuations (1)

	Number	Date	Country
Parent	14619732	Feb 2015	US
Child	16026272		US

Sterile handle for controlling a robotic surgical system from a sterile field

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

CPC

Field of Search

CPC

International Classifications

Term Extension

Abstract