Abstract: A surgical exercise performed with a surgical robotic system is sensed by depth cameras, generating 3D point cloud data. Robot system data associated with the surgical robotic system is logged. Object recognition is performed on image data produced by the one or more depth cameras, to recognized objects, including surgical equipment and people, in the operating room (OR). The surgical exercise is digitized by storing the 3D point cloud data of unrecognized objects, a position and orientation associated with the recognized objects, and c) the robot system data.

Abstract: A medical image viewer can render to a display, a three-dimensional view of patient anatomy, a multi planar reconstruction (MPR) view of the patient anatomy, and an intra-operational view. Some of the views can be synchronized to show a common focal point of the anatomy. Other embodiments are described and claimed.

Abstract: A surgical exercise performed with a surgical robotic system is sensed by depth cameras, generating 3D point cloud data. Robot system data associated with the surgical robotic system is logged. Object recognition is performed on image data produced by the one or more depth cameras, to recognized objects, including surgical equipment and people, in the operating room (OR). The surgical exercise is digitized by storing the 3D point cloud data of unrecognized objects, a position and orientation associated with the recognized objects, and c) the robot system data.

Abstract: A medical image viewer can render to a display, a three-dimensional view of patient anatomy, a multi planar reconstruction (MPR) view of the patient anatomy, and an intra-operational view. Some of the views can be synchronized to show a common focal point of the anatomy. Other embodiments are described and claimed.

Abstract: A system includes a display, and a processor. The processor may be configured to obtain a three-dimensional model of a patient including one or more blood vessels and a mass that is marked for removal, determine a position of each of one or more surgical clips within the three-dimensional model, where blood flow is restricted from a region of the three-dimensional model based on the one or more blood vessels of the three-dimensional model and the position of each of the one or more surgical clips, and present, to the display, the three-dimensional model of the patient including a visual indication of the region and the mass.

Abstract: A surgical exercise performed with a surgical robotic system is sensed by depth cameras, generating 3D point cloud data. Robot system data associated with the surgical robotic system is logged. Object recognition is performed on image data produced by the one or more depth cameras, to recognized objects, including surgical equipment and people, in the operating room (OR). The surgical exercise is digitized by storing the 3D point cloud data of unrecognized objects, a position and orientation associated with the recognized objects, and c) the robot system data.

Abstract: A surgical exercise performed with a surgical robotic system is sensed by depth cameras, generating 3D point cloud data. Robot system data associated with the surgical robotic system is logged. Object recognition is performed on image data produced by the one or more depth cameras, to recognized objects, including surgical equipment and people, in the operating room (OR). The surgical exercise is digitized by storing the 3D point cloud data of unrecognized objects, a position and orientation associated with the recognized objects, and c) the robot system data.

Abstract: User input devices (UIDs) for controlling a surgical robotic system are described. A UID can include one or more tracking sensors to generate respective spatial state signals in accordance with a pose of the UID. At least one of the tracking sensors can be a camera. In the case of multiple tracking sensors, the spatial state signals are processed by a sensor fusion algorithm to generate a more robust, single tracking signal and a quality measure. The tracking signal and the quality measure are then used by a digital control system to control motion of a surgical robotic system actuator that is associated with the UID. Other embodiments are also described and claimed.

Abstract: A surgical exercise performed with a surgical robotic system is sensed by depth cameras, generating 3D point cloud data. Robot system data associated with the surgical robotic system is logged. Object recognition is performed on image data produced by the one or more depth cameras, to recognized objects, including surgical equipment and people, in the operating room (OR). The surgical exercise is digitized by storing the 3D point cloud data of unrecognized objects, a position and orientation associated with the recognized objects, and c) the robot system data.

Abstract: Surgical robotic system includes a surgical robotic arm, a handheld user interface device (UID) having a camera. Images from the camera are processed to detect a marker in the user environment. A pose of the handheld UID is determined based on the detected marker. A movement of the surgical robotic arm is effected based on the pose of the handheld UID.

Abstract: A medical image viewer can render to a display, a three-dimensional view of patient anatomy, a multi planar reconstruction (MPR) view of the patient anatomy, and an intra-operational view. Some of the views can be synchronized to show a common focal point of the anatomy. Other embodiments are described and claimed.

Abstract: User input devices (UIDs) for controlling a surgical robotic system are described. A UID can include one or more tracking sensors to generate respective spatial state signals in accordance with a pose of the UID. At least one of the tracking sensors can be a camera. In the case of multiple tracking sensors, the spatial state signals are processed by a sensor fusion algorithm to generate a more robust, single tracking signal and a quality measure. The tracking signal and the quality measure are then used by a digital control system to control motion of a surgical robotic system actuator that is associated with the UID. Other embodiments are also described and claimed.

Abstract: A method and system for accessing database tables that contain binary large objects (BLOBs) is disclosed. The method includes encapsulating BLOB-based tables with virtual tables, which allows a user to access the content of the BLOBs via SQL. In one example, the virtual table has a generic table structure that consists of columns (e.g., class name, field name, and field value) and information regarding what level of an object hierarchy contains an element. In another example, a user can define the structure of the virtual table by identifying which object attributes to report.

Abstract: A page server and method of using the page server is described. The page server stores versioned pages. The pages, which are equally sized data chunks, can be stored with identifiers and version data in a relational database, in separate files, or in a single file where pages are concatenated. The page server may be accessed via SQL, a web interface, a proprietary key/value/version interface on top of TCP/IP, or other method. The page server facilitates incremental updates.

Abstract: A page server and method of using the page server is described. The page server stores versioned pages. The pages, which are equally sized data chunks, can be stored with identifiers and version data in a relational database, in separate files, or in a single file where pages are concatenated. The page server may be accessed via SQL, a web interface, a proprietary key/value/version interface on top of TCP/IP, or other method. The page server facilitates incremental updates.

Abstract: A page server and method of using the page server is described. The page server stores versioned pages. The pages, which are equally sized data chunks, can be stored with identifiers and version data in a relational database, in separate files, or in a single file where pages are concatenated. The page server may be accessed via SQL, a web interface, a proprietary key/value/version interface on top of TCP/IP, or other method. The page server facilitates incremental updates.

Abstract: A page server and method of using the page server is described. The page server stores versioned pages. The pages, which are equally sized data chunks, can be stored with identifiers and version data in a relational database, in separate files, or in a single file where pages are concatenated. The page server may be accessed via SQL, a web interface, a proprietary key/value/version interface on top of TCP/IP, or other method. The page server facilitates incremental updates.

Abstract: A method and system for accessing database tables that contain binary large objects (BLOBs) is disclosed. The method includes encapsulating BLOB-based tables with virtual tables, which allows a user to access the content of the BLOBs via SQL. In one example, the virtual table has a generic table structure that consists of columns (e.g., class name, field name, and field value) and information regarding what level of an object hierarchy contains an element. In another example, a user can define the structure of the virtual table by identifying which object attributes to report.