US20220370132A1

US20220370132A1 - Surgical Simulation Navigation System

Info

Publication number: US20220370132A1
Application number: US17/332,399
Authority: US
Inventors: Frederick E. Shelton, IV; Charles J. Scheib; Dwight Alan Meglan
Original assignee: Cilag GmbH International
Current assignee: Cilag GmbH International
Priority date: 2021-05-21
Filing date: 2021-05-27
Publication date: 2022-11-24
Also published as: US20220370137A1; EP4150606A1; US20220370131A1; US20220375620A1; JP2024521114A; US20250253058A1; JP2024521111A; JP2024521721A; JP2024521113A; EP4150603A1; US12272463B2; US20220370134A1; JP2024521719A; JP2024521112A; US20220370138A1; EP4150603B1; EP4150611A1; BR112023023905A2; EP4150605A1; EP4150610A1

Abstract

An interactive and dynamic surgical simulation system may be used in the context of a computer-implemented interactive surgical system. The surgical simulation system may enable enhanced navigation, such as to provide simulation support during a live surgical procedure. A processor may be configured to identify a procedure plan for a live surgical procedure and identify a stored simulation of a surgical procedure that corresponds to the procedure plan. The processor may determine, from information received during the live surgical procedure, a present portion of the live surgical procedure. And the processor may retrieve, from the stored simulation, a portion of the stored simulation that corresponds to the present portion of the live surgical procedure. The portion of the simulation that corresponds to the present portion of the live surgical procedure may then be presented for user interaction.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of Provisional U.S. Patent Application No. 63/191,681, May 21, 2021, the disclosure of which is incorporated herein by reference in its entirety.
This application is related to the following, filed contemporaneously, the contents of each of which are incorporated by reference herein:

- U.S. patent application Ser. No. 17/332,594, filed May 27, 2021, (Attorney Docket No. END9338USNP1), titled METHODS FOR SURGICAL SIMULATION
- U.S. patent application Ser. No. 17/332,524, filed May 27, 2021, (Attorney Docket No. END9338USNP2), titled SURGICAL SIMULATION OBJECT RECTIFICATION SYSTEM
- U.S. patent application Ser. No. 17/332,441, filed May 27, 2021, (Attorney Docket No. END9338USNP4), titled SURGICAL SIMULATION SYSTEM WITH COORDINATED IMAGINING
- U.S. patent application Ser. No. 17/332,462, filed May 27, 2021, (Attorney Docket No. END9338USNP5), titled SURGICAL SIMULATION SYSTEM WITH SIMULATED SURGICAL EQUIPMENT COORDINATION
- U.S. patent application Ser. No. 17/332,197, filed May 27, 2021, (Attorney Docket No. END9338USNP6), titled SIMULATION-BASED SURGICAL PROCEDURE PLANNING SYSTEM
- U.S. patent application Ser. No. 17/332,407, filed May 27, 2021, (Attorney Docket No. END9338USNP7), titled SIMULATION-BASED DIRECTED SURGICAL DEVELOPMENT SYSTEM
- U.S. patent application Ser. No. 17/332,449, filed May 27, 2021, (Attorney Docket No. END9338USNP8), titled SURGICAL ADVERSE EVENT SIMULATION SYSTEM
- U.S. patent application Ser. No. 17/332,496, filed May 27, 2021, (Attorney Docket No. END9338USNP9), titled SIMULATION-BASED SURGICAL ANALYSIS SYSTEM
- U.S. patent application Ser. No. 17/332,480, filed May 27, 2021, (Attorney Docket No. END9338USNP10), titled DYNAMIC ADAPTATION SYSTEM FOR SURGICAL SIMULATION

BACKGROUND

Surgical simulations, such as computer-based, three-dimensional simulations of a surgical environment and/or surgical procedure for example, present an opportunity to advance the surgical arts. Surgical simulations have potential to benefit surgical training, planning, development, and the like. For example, surgical simulations may be used to train surgeons in new procedures and/or to improve the performance of procedures they already know. Surgical simulations may be used as a virtual “dress rehearsal” to help a surgeon prepare for an upcoming procedure. And surgical simulations may be used to experiment with unproven procedures and techniques.
However, surgical simulation platforms are complex systems that face many limitations in capabilities, scope, and applicability. For example, many platforms are technology “silos,” specifically programmed and tailored to address a particular learning objective or to simulate the operation of a singular piece of equipment, such as simulating the operation of a surgical robot. Limitations, such as these, may dimmish a platform's effectiveness as a tool to advance the surgical arts. And such limitations may represent significant technological roadblocks to the integration of simulation-based applications into other aspects of the surgical process, such a pre-operative planning, intra-operative support, post-operative analysis, and the like.
Accordingly, innovation in surgical simulation technology, such as technical advancements that address surgical simulation capabilities, scope, and applicability for example, may accelerate further progress in the surgical arts.

SUMMARY

An interactive and dynamic surgical simulation system is disclosed. The surgical simulation system may be used in the context of a computer-implemented interactive surgical system. The surgical simulation system may enable enhanced navigation. For example, a device may be used to provide simulation support during a live surgical procedure.
The device may include a processor. The processor may be configured to identify a procedure plan for a live surgical procedure and identify a stored simulation of a surgical procedure that corresponds to the procedure plan. The processor may determine, from information received during the live surgical procedure, a present portion of the live surgical procedure. And the processor may retrieve, from the stored simulation, a portion of the stored simulation that corresponds to the present portion of the live surgical procedure. The portion of the simulation that corresponds to the present portion of the live surgical procedure may then be presented for user interaction.
The procedure plan may include a set of tasks. And the stored simulation may include information indicative of a simulated activity that is indexed according to the set of tasks. The processor may determine the present portion of the live surgical procedure by determining a present task from the procedure plan. The processor may retrieve a portion of the simulation that corresponds to the present portion of the live surgical procedure by retrieving a selected portion of the information indicative of simulated activity that is indexed the present task.
Accordingly, a visualization of the present portion of the live surgical procedure may be presented concurrently with a presentation of the portion of the simulation that corresponds to the present portion of the live surgical procedure.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a computer-implemented interactive surgical syste.

FIG. 2 shows an example surgical system being used to perform a surgical procedure in an operating room.

FIG. 3 shows an example surgical hub paired with a visualization system, a robotic system, and an intelligent instrument, in accordance with at least one aspect of the present disclosur.

FIG. 4 illustrates a surgical data network having a communication hub configured to connect modular devices located in one or more operating theaters of a healthcare facility, or any room in a healthcare facility specially equipped for surgical operations, to the cloud, in accordance with at least one aspect of the present disclosure.

FIG. 5 illustrates an example computer-implemented interactive surgical system.

FIG. 6 illustrates an example surgical hub comprising a plurality of modules coupled to the modular control tower.

FIG. 7 is a block diagram of an example surgical simulator system.

FIG. 8 is a block diagram of an example surgical simulator system.

FIG. 9 is a block diagram depicting an example surgical simulator user interface device.

FIG. 10 is a flow chart of an example surgical simulator operation.

FIGS. 11A-B illustrate example surgical procedural plan data structures for use with a computer-implemented interactive surgical system and/or a surgical simulator.

FIG. 12 illustrates a system for providing simulation support in a live surgical procedur.

FIG. 13 illustrates time-based surgical and simulation data.

FIG. 14 illustrates a task-based indexing of the time-based surgical and simulation data.

FIG. 15 is a flow diagram of example process for providing simulation support in a live surgical procedure.

DETAILED DESCRIPTION

Surgical simulation systems, devices, and methods may include aspects of integration with other medical equipment, data sources, processes, and institutions. Surgical simulation systems, devices, and methods may include aspects of integration with a computer-implemented interactive surgical system and/or with one or more elements of a computer-implemented interactive surgical system, for example.
Referring to FIG. 1, a computer-implemented interactive surgical system 100 may include one or more surgical systems 102 and a cloud-based system (e.g., the cloud 104 that may include a remote server 113 coupled to a storage device 105). Each surgical system 102 may include at least one surgical hub 106 in communication with the cloud 104 that may include a remote server 113.
One or more simulation devices 103, 111 may be in communication with and/or integrated as part of the computer-implemented interactive surgical system 100. For example, the simulation device 103 may be an element of the one or more surgical systems 102. For example, the simulation device 103 may be in communication with one or more surgical hubs 106. For example, the simulation device 111 may be in communication with the computer-implemented interactive surgical system 100 via the cloud 104.
In one example, as illustrated in FIG. 1, the surgical system 102 includes a visualization system 108, a robotic system 110, and a handheld intelligent surgical instrument 112, which are configured to communicate with one another and/or the hub 106. In some aspects, a surgical system 102 may include an M number of hubs 106, an N number of visualization systems 108, an O number of robotic systems 110, and a P number of handheld intelligent surgical instruments 112, where M, N, O, and P may be integers greater than or equal to one.
In various aspects, the visualization system 108 may include one or more imaging sensors, one or more image-processing units, one or more storage arrays, and one or more displays that are strategically arranged with respect to the sterile field, as illustrated in FIG. 2. In one aspect, the visualization system 108 may include an interface for HL7, PACS, and EMR. Various components of the visualization system 108 are described under the heading “Advanced Imaging Acquisition Module” in U.S. Patent Application Publication No. US 2019-0200844 A1 (U.S. patent application Ser. No. 16/209,385), titled METHOD OF HUB COMMUNICATION, PROCESSING, STORAGE AND DISPLAY, filed Dec. 4, 2018, the disclosure of which is herein incorporated by reference in its entirety.
As illustrated in FIG. 2, a primary display 119 is positioned in the sterile field to be visible to an operator at the operating table 114. In addition, a visualization tower 111 is positioned outside the sterile field. The visualization tower 111 may include a first non-sterile display 107 and a second non-sterile display 109, which face away from each other. The visualization system 108, guided by the hub 106, is configured to utilize the displays 107, 109, and 119 to coordinate information flow to operators inside and outside the sterile field. For example, the hub 106 may cause the visualization system 108 to display a snapshot of a surgical site, as recorded by an imaging device 124, on a non-sterile display 107 or 109, while maintaining a live feed of the surgical site on the primary display 119. The snapshot on the non-sterile display 107 or 109 can permit a non-sterile operator to perform a diagnostic step relevant to the surgical procedure, for example.
In one aspect, the hub 106 may also be configured to route a diagnostic input or feedback entered by a non-sterile operator at the visualization tower 111 to the primary display 119 within the sterile field, where it can be viewed by a sterile operator at the operating table. In one example, the input can be in the form of a modification to the snapshot displayed on the non-sterile display 107 or 109, which can be routed to the primary display 119 by the hub 106.
Referring to FIG. 2, a surgical instrument 112 is being used in the surgical procedure as part of the surgical system 102. The hub 106 may also be configured to coordinate information flow to a display of the surgical instrument 112. For example, in U.S. Patent Application Publication No. US 2019-0200844 A1 (U.S. patent application Ser. No. 16/209,385), titled METHOD OF HUB COMMUNICATION, PROCESSING, STORAGE AND DISPLAY, filed Dec. 4, 2018, the disclosure of which is herein incorporated by reference in its entirety. A diagnostic input or feedback entered by a non-sterile operator at the visualization tower 111 can be routed by the hub 106 to the surgical instrument display 115 within the sterile field, where it can be viewed by the operator of the surgical instrument 112. Example surgical instruments that are suitable for use with the surgical system 102 are described under the heading “Surgical Instrument Hardware” and in U.S. Patent Application Publication No. US 2019-0200844 A1 (U.S. patent application Ser. No. 16/209,385), titled METHOD OF HUB COMMUNICATION, PROCESSING, STORAGE AND DISPLAY, filed Dec. 4, 2018, the disclosure of which is herein incorporated by reference in its entirety, for example.
FIG. 2 depicts an example of a surgical system 102 being used to perform a surgical procedure on a patient who is lying down on an operating table 114 in a surgical operating room 116. A robotic system 110 may be used in the surgical procedure as a part of the surgical system 102. The robotic system 110 may include a surgeon's console 118, a patient side cart 120 (surgical robot), and a surgical robotic hub 122. The patient side cart 120 can manipulate at least one removably coupled surgical tool 117 through a minimally invasive incision in the body of the patient while the surgeon views the surgical site through the surgeon's console 118. An image of the surgical site can be obtained by a medical imaging device 124, which can be manipulated by the patient side cart 120 to orient the imaging device 124. The robotic hub 122 can be used to process the images of the surgical site for subsequent display to the surgeon through the surgeon's console 118.
Other types of robotic systems can be readily adapted for use with the surgical system 102. Various examples of robotic systems and surgical tools that are suitable for use with the present disclosure are described in U.S. Patent Application Publication No. US 2019-0201137 A1 (U.S. patent application Ser. No. 16/209,407), titled METHOD OF ROBOTIC HUB COMMUNICATION, DETECTION, AND CONTROL, filed Dec. 4, 2018, the disclosure of which is herein incorporated by reference in its entirety.
Various examples of cloud-based analytics that are performed by the cloud 104, and are suitable for use with the present disclosure, are described in U.S. Patent Application Publication No. US 2019-0206569 A1 (U.S. patent application Ser. No. 16/209,403), titled METHOD OF CLOUD BASED DATA ANALYTICS FOR USE WITH THE HUB, filed Dec. 4, 2018, the disclosure of which is herein incorporated by reference in its entirety.
In various aspects, the imaging device 124 may include at least one image sensor and one or more optical components. Suitable image sensors may include, but are not limited to, Charge-Coupled Device (CCD) sensors and Complementary Metal-Oxide Semiconductor (CMOS) sensors.
The optical components of the imaging device 124 may include one or more illumination sources and/or one or more lenses. The one or more illumination sources may be directed to illuminate portions of the surgical field. The one or more image sensors may receive light reflected or refracted from the surgical field, including light reflected or refracted from tissue and/or surgical instruments.
The one or more illumination sources may be configured to radiate electromagnetic energy in the visible spectrum as well as the invisible spectrum. The visible spectrum, sometimes referred to as the optical spectrum or luminous spectrum, is that portion of the electromagnetic spectrum that is visible to (i.e., can be detected by) the human eye and may be referred to as visible light or simply light. A typical human eye will respond to wavelengths in air that are from about 380 nm to about 750 nm.
The invisible spectrum (e.g., the non-luminous spectrum) is that portion of the electromagnetic spectrum that lies below and above the visible spectrum (i.e., wavelengths below about 380 nm and above about 750 nm). The invisible spectrum is not detectable by the human eye. Wavelengths greater than about 750 nm are longer than the red visible spectrum, and they become invisible infrared (IR), microwave, and radio electromagnetic radiation. Wavelengths less than about 380 nm are shorter than the violet spectrum, and they become invisible ultraviolet, x-ray, and gamma ray electromagnetic radiation.
In various aspects, the imaging device 124 is configured for use in a minimally invasive procedure. Examples of imaging devices suitable for use with the present disclosure include, but not limited to, an arthroscope, angioscope, bronchoscope, choledochoscope, colonoscope, cytoscope, duodenoscope, enteroscope, esophagogastro-duodenoscope (gastroscope), endoscope, laryngoscope, nasopharyngo-neproscope, sigmoidoscope, thoracoscope, and ureteroscope.
The imaging device may employ multi-spectrum monitoring to discriminate topography and underlying structures. A multi-spectral image is one that captures image data within specific wavelength ranges across the electromagnetic spectrum. The wavelengths may be separated by filters or by the use of instruments that are sensitive to particular wavelengths, including light from frequencies beyond the visible light range, e.g., IR and ultraviolet. Spectral imaging can allow extraction of additional information the human eye fails to capture with its receptors for red, green, and blue. The use of multi-spectral imaging is described in greater detail under the heading “Advanced Imaging Acquisition Module” in U.S. Patent Application Publication No. US 2019-0200844 A1 (U.S. patent application Ser. No. 16/209,385), titled METHOD OF HUB COMMUNICATION, PROCESSING, STORAGE AND DISPLAY, filed Dec. 4, 2018, the disclosure of which is herein incorporated by reference in its entirety. Multi-spectrum monitoring can be a useful tool in relocating a surgical field after a surgical task is completed to perform one or more of the previously described tests on the treated tissue. It is axiomatic that strict sterilization of the operating room and surgical equipment is required during any surgery. The strict hygiene and sterilization conditions required in a “surgical theater,” i.e., an operating or treatment room, necessitate the highest possible sterility of all medical devices and equipment. Part of that sterilization process is the need to sterilize anything that comes in contact with the patient or penetrates the sterile field, including the imaging device 124 and its attachments and components. It will be appreciated that the sterile field may be considered a specified area, such as within a tray or on a sterile towel, that is considered free of microorganisms, or the sterile field may be considered an area, immediately around a patient, who has been prepared for a surgical procedure. The sterile field may include the scrubbed team members, who are properly attired, and all furniture and fixtures in the area.
Referring now to FIG. 3, a hub 106 is depicted in communication with a visualization system 108, a robotic system 110, and a handheld intelligent surgical instrument 112. The hub 106 includes a hub display 135, an imaging module 138, a generator module 140, a communication module 130, a processor module 132, a storage array 134, and an operating-room mapping module 133. In certain aspects, as illustrated in FIG. 3, the hub 106 further includes a smoke evacuation module 126 and/or a suction/irrigation module 128. During a surgical procedure, energy application to tissue, for sealing and/or cutting, is generally associated with smoke evacuation, suction of excess fluid, and/or irrigation of the tissue. Fluid, power, and/or data lines from different sources are often entangled during the surgical procedure. Valuable time can be lost addressing this issue during a surgical procedure. Detangling the lines may necessitate disconnecting the lines from their respective modules, which may require resetting the modules. The hub modular enclosure 136 offers a unified environment for managing the power, data, and fluid lines, which reduces the frequency of entanglement between such lines. Aspects of the present disclosure present a surgical hub for use in a surgical procedure that involves energy application to tissue at a surgical site. The surgical hub includes a hub enclosure and a combo generator module slidably receivable in a docking station of the hub enclosure. The docking station includes data and power contacts. The combo generator module includes two or more of an ultrasonic energy generator component, a bipolar RF energy generator component, and a monopolar RF energy generator component that are housed in a single unit. In one aspect, the combo generator module also includes a smoke evacuation component, at least one energy delivery cable for connecting the combo generator module to a surgical instrument, at least one smoke evacuation component configured to evacuate smoke, fluid, and/or particulates generated by the application of therapeutic energy to the tissue, and a fluid line extending from the remote surgical site to the smoke evacuation component. In one aspect, the fluid line is a first fluid line and a second fluid line extends from the remote surgical site to a suction and irrigation module slidably received in the hub enclosure. In one aspect, the hub enclosure comprises a fluid interface. Certain surgical procedures may require the application of more than one energy type to the tissue. One energy type may be more beneficial for cutting the tissue, while another different energy type may be more beneficial for sealing the tissue. For example, a bipolar generator can be used to seal the tissue while an ultrasonic generator can be used to cut the sealed tissue. Aspects of the present disclosure present a solution where a hub modular enclosure 136 is configured to accommodate different generators, and facilitate an interactive communication therebetween. One of the advantages of the hub modular enclosure 136 is enabling the quick removal and/or replacement of various modules. Aspects of the present disclosure present a modular surgical enclosure for use in a surgical procedure that involves energy application to tissue. The modular surgical enclosure includes a first energy-generator module, configured to generate a first energy for application to the tissue, and a first docking station comprising a first docking port that includes first data and power contacts, wherein the first energy-generator module is slidably movable into an electrical engagement with the power and data contacts and wherein the first energy-generator module is slidably movable out of the electrical engagement with the first power and data contacts. Further to the above, the modular surgical enclosure also includes a second energy-generator module con-figured to generate a second energy, different than the first energy, for application to the tissue, and a second docking station comprising a second docking port that includes second data and power contacts, wherein the second energy-generator module is slidably movable into an electrical engagement with the power and data contacts, and wherein the second energy-generator module is slidably movable out of the electrical engagement with the second power and data contacts. In addition, the modular surgical enclosure also includes a communication bus between the first docking port and the second docking port, configured to facilitate communication between the first energy-generator module and the second energy-generator module. Referring to FIG. 3, aspects of the present disclosure are presented for a hub modular enclosure 136 that allows the modular integration of a generator module 140, a smoke evacuation module 126, and a suction/irrigation module 128. The hub modular enclosure 136 further facilitates interactive communication between the modules 140, 126, 128. The generator module 140 can be a generator module with integrated monopolar, bipolar, and ultrasonic components supported in a single housing unit slidably insertable into the hub modular enclosure 136. The generator module 140 can be configured to connect to a monopolar device 142, a bipolar device 144, and an ultrasonic device 146. Alternatively, the generator module 140 may comprise a series of monopolar, bipolar, and/or ultrasonic generator modules that interact through the hub modular enclosure 136. The hub modular enclosure 136 can be configured to facilitate the insertion of multiple generators and interactive communication between the generators docked into the hub modular enclosure 136 so that the generators would act as a single generator.
FIG. 4 illustrates a surgical data network 201 comprising a modular communication hub 203 configured to connect modular devices located in one or more operating theaters of a healthcare facility, or any room in a healthcare facility specially equipped for surgical operations, to a cloud-based system (e.g., the cloud 204 that may include a remote server 213 coupled to a storage device 205). In one aspect, the modular communication hub 203 comprises a network hub 207 and/or a network switch 209 in communication with a network router. The modular communication hub 203 also can be coupled to a local computer system 210 to provide local computer processing and data manipulation. The surgical data network 201 may be configured as passive, intelligent, or switching. A passive surgical data network serves as a conduit for the data, enabling it to go from one device (or segment) to another and to the cloud computing resources. An intelligent surgical data network includes additional features to enable the traffic passing through the surgical data network to be monitored and to configure each port in the network hub 207 or network switch 209. An intelligent surgical data network may be referred to as a manageable hub or switch. A switching hub reads the destination address of each packet and then forwards the packet to the correct port.
Modular devices 1 a-1 n located in the operating theater may be coupled to the modular communication hub 203. The network hub 207 and/or the network switch 209 may be coupled to a network router 211 to connect the devices 1 a-1 n to the cloud 204 or the local computer system 210. Data associated with the devices 1 a-1 n may be transferred to cloud-based computers via the router for remote data processing and manipulation. Data associated with the devices 1 a-1 n may also be transferred to the local computer system 210 for local data processing and manipulation. Modular devices 2 a-2 m located in the same operating theater also may be coupled to a network switch 209. The network switch 209 may be coupled to the network hub 207 and/or the network router 211 to connect to the devices 2 a-2 m to the cloud 204. Data associated with the devices 2 a-2 n may be transferred to the cloud 204 via the network router 211 for data processing and manipulation. Data associated with the devices 2 a-2 m may also be transferred to the local computer system 210 for local data processing and manipulation.
It will be appreciated that the surgical data network 201 may be expanded by interconnecting multiple network hubs 207 and/or multiple network switches 209 with multiple network routers 211. The modular communication hub 203 may be contained in a modular control tower configured to receive multiple devices 1 a-1 n/2 a-2 m. The local computer system 210 also may be contained in a modular control tower. The modular communication hub 203 is connected to a display 212 to display images obtained by some of the devices 1 a-1 n/2 a-2 m, for example during surgical procedures. In various aspects, the devices 1 a-1 n/2 a-2 m may include, for example, various modules such as an imaging module 138 coupled to an endoscope, a generator module 140 coupled to an energy-based surgical device, a smoke evacuation module 126, a suction/irrigation module 128, a communication module 130, a processor module 132, a storage array 134, a surgical device coupled to a display, and/or a non-contact sensor module, among other modular devices that may be connected to the modular communication hub 203 of the surgical data network 201.
In one aspect, the surgical data network 201 may comprise a combination of network hub(s), network switch(es), and network router(s) connecting the devices 1 a-1 n/2 a-2 m to the cloud. Any one of or all of the devices 1 a-1 n/2 a-2 m coupled to the network hub or network switch may collect data in real time and transfer the data to cloud computers for data processing and manipulation. It will be appreciated that cloud computing relies on sharing computing resources rather than having local servers or personal devices to handle software applications. The word “cloud” may be used as a metaphor for “the Internet,” although the term is not limited as such. Accordingly, the term “cloud computing” may be used herein to refer to “a type of Internet-based computing,” where different services-such as servers, storage, and applications—are delivered to the modular communication hub 203 and/or computer system 210 located in the surgical theater (e.g., a fixed, mobile, temporary, or field operating room or space) and to devices connected to the modular communication hub 203 and/or computer system 210 through the Internet. The cloud infrastructure may be maintained by a cloud service provider. In this context, the cloud service provider may be the entity that coordinates the usage and control of the devices 1 a-1 n/2 a-2 m located in one or more operating theaters. The cloud computing services can perform a large number of calculations based on the data gathered by smart surgical instruments, robots, and other computerized devices located in the operating theater. The hub hardware enables multiple devices or connections to be connected to a computer that communicates with the cloud computing resources and storage.
Applying cloud computer data processing techniques on the data collected by the devices 1 a-1 n/2 a-2 m, the surgical data network can provide improved surgical outcomes, reduced costs, and improved patient satisfaction. At least some of the devices 1 a-1 n/2 a-2 m may be employed to view tissue states to assess leaks or perfusion of sealed tissue after a tissue sealing and cutting procedure. At least some of the devices 1 a-1 n/2 a-2 m may be employed to identify pathology, such as the effects of diseases, using the cloud-based computing to examine data including images of samples of body tissue for diagnostic purposes. This may include localization and margin confirmation of tissue and phenotypes. At least some of the devices 1 a-1 n/2 a-2 m may be employed to identify anatomical structures of the body using a variety of sensors integrated with imaging devices and techniques such as overlaying images captured by multiple imaging devices. The data gathered by the devices 1 a-1 n/2 a-2 m, including image data, may be transferred to the cloud 204 or the local computer system 210 or both for data processing and manipulation including image processing and manipulation. The data may be analyzed to improve surgical procedure outcomes by determining if further treatment, such as the application of endoscopic intervention, emerging technologies, a targeted radiation, targeted intervention, and precise robotics to tissue-specific sites and conditions, may be pursued. Such data analysis may further employ outcome analytics processing, and using standardized approaches may provide beneficial feedback to either confirm surgical treatments and the behavior of the surgeon or suggest modifications to surgical treatments and the behavior of the surgeon.
The operating theater devices 1 a-1 n may be connected to the modular communication hub 203 over a wired channel or a wireless channel depending on the configuration of the devices 1 a-1 n to a network hub. The network hub 207 may be implemented, in one aspect, as a local network broadcast device that works on the physical layer of the Open System Interconnection (OSI) model. The network hub may provide connectivity to the devices 1 a-1 n located in the same operating theater network. The network hub 207 may collect data in the form of packets and sends them to the router in half duplex mode. The network hub 207 may not store any media access control/Internet Protocol (MAC/IP) to transfer the device data. Only one of the devices 1 a-1 n can send data at a time through the network hub 207. The network hub 207 may not have routing tables or intelligence regarding where to send information and broadcasts all network data across each connection and to a remote server 213 (FIG. 4) over the cloud 204. The network hub 207 can detect basic network errors such as collisions, but having all information broadcast to multiple ports can be a security risk and cause bottlenecks.
The operating theater devices 2 a-2 m may be connected to a network switch 209 over a wired channel or a wireless channel. The network switch 209 works in the data link layer of the OSI model. The network switch 209 may be a multicast device for connecting the devices 2 a-2 m located in the same operating theater to the network. The network switch 209 may send data in the form of frames to the network router 211 and works in full duplex mode. Multiple devices 2 a-2 m can send data at the same time through the network switch 209. The network switch 209 stores and uses MAC addresses of the devices 2 a-2 m to transfer data.
The network hub 207 and/or the network switch 209 may be coupled to the network router 211 for connection to the cloud 204. The network router 211 works in the network layer of the OSI model. The network router 211 creates a route for transmitting data packets received from the network hub 207 and/or network switch 211 to cloud-based computer resources for further processing and manipulation of the data collected by any one of or all the devices 1 a-1 n/2 a-2 m. The network router 211 may be employed to connect two or more different networks located in different locations, such as, for example, different operating theaters of the same healthcare facility or different networks located in different operating theaters of different healthcare facilities. The network router 211 may send data in the form of packets to the cloud 204 and works in full duplex mode. Multiple devices can send data at the same time. The network router 211 uses IP addresses to transfer data.
In an example, the network hub 207 may be implemented as a USB hub, which allows multiple USB devices to be connected to a host computer. The USB hub may expand a single USB port into several tiers so that there are more ports available to connect devices to the host system computer. The network hub 207 may include wired or wireless capabilities to receive information over a wired channel or a wireless channel. In one aspect, a wireless USB short-range, high-bandwidth wireless radio communication protocol may be employed for communication between the devices 1 a-1 n and devices 2 a-2 m located in the operating theater.
In examples, the operating theater devices 1 a-1 n/2 a-2 m may communicate to the modular communication hub 203 via Bluetooth wireless technology standard for exchanging data over short distances (using short-wavelength UHF radio waves in the ISM band from 2.4 to 2.485 GHz) from fixed and mobile devices and building personal area networks (PANs). The operating theater devices 1 a-1 n/2 a-2 m may communicate to the modular communication hub 203 via a number of wireless or wired communication standards or protocols, including but not limited to Wi-Fi (IEEE 802.11 family), WiMAX (IEEE 802.16 family), IEEE 802.20, new radio (NR), long-term evolution (LTE), and Ev-DO, HSPA+, HSDPA+, HSUPA+, EDGE, GSM, GPRS, CDMA, TDMA, DECT, and Ethernet derivatives thereof, as well as any other wireless and wired protocols that are designated as 3G, 4G, 5G, and beyond. The computing module may include a plurality of communication modules. For instance, a first communication module may be dedicated to shorter-range wireless communications such as Wi-Fi and Bluetooth, and a second communication module may be dedicated to longer-range wireless communications such as GPS, EDGE, GPRS, CDMA, WiMAX, LTE, Ev-DO, and others.
The modular communication hub 203 may serve as a central connection for one or all of the operating theater devices 1 a-1 n/2 a-2 m and may handle a data type known as frames. Frames may carry the data generated by the devices 1 a-1 n/2 a-2 m. When a frame is received by the modular communication hub 203, it is amplified and transmitted to the network router 211, which transfers the data to the cloud computing resources by using a number of wireless or wired communication standards or protocols, as described herein.
The modular communication hub 203 can be used as a standalone device or be connected to compatible network hubs and network switches to form a larger network. The modular communication hub 203 can be generally easy to install, configure, and maintain, making it a good option for networking the operating theater devices 1 a-1 n/2 a-2 m.
FIG. 5 illustrates a computer-implemented interactive surgical system 200. The computer-implemented interactive surgical system 200 is similar in many respects to the computer-implemented interactive surgical system 100. For example, the computer-implemented interactive surgical system 200 includes one or more surgical systems 202, which are similar in many respects to the surgical systems 102. Each surgical system 202 includes at least one surgical hub 206 in communication with a cloud 204 that may include a remote server 213. In one aspect, the computer-implemented interactive surgical system 200 comprises a modular control tower 236 connected to multiple operating theater devices such as, for example, intelligent surgical instruments, robots, and other computerized devices located in the operating theater. As shown in FIG. 6, the modular control tower 236 comprises a modular communication hub 203 coupled to a computer system 210.
As illustrated in the example of FIG. 5, the modular control tower 236 may be coupled to an imaging module 238 that may be coupled to an endoscope 239, a generator module 240 that may be coupled to an energy device 241, a smoke evacuator module 226, a suction/irrigation module 228, a communication module 230, a processor module 232, a storage array 234, a smart device/instrument 235 optionally coupled to a display 237, and a non-contact sensor module 242. The operating theater devices may be coupled to cloud computing resources and data storage via the modular control tower 236. A robot hub 222 also may be connected to the modular control tower 236 and to the cloud computing resources. The devices/instruments 235, visualization systems 208, among others, may be coupled to the modular control tower 236 via wired or wireless communication standards or protocols, as described herein. The modular control tower 236 may be coupled to a hub display 215 (e.g., monitor, screen) to display and overlay images received from the imaging module, device/instrument display, and/or other visualization systems 208. The hub display also may display data received from devices connected to the modular control tower in conjunction with images and overlaid images.
FIG. 6 illustrates a surgical hub 206 comprising a plurality of modules coupled to the modular control tower 236. The modular control tower 236 may comprise a modular communication hub 203, e.g., a network connectivity device, and a computer system 210 to provide local processing, visualization, and imaging, for example. As shown in FIG. 6, the modular communication hub 203 may be connected in a tiered configuration to expand the number of modules (e.g., devices) that may be connected to the modular communication hub 203 and transfer data associated with the modules to the computer system 210, cloud computing resources, or both. As shown in FIG. 6, each of the network hubs/switches in the modular communication hub 203 may include three downstream ports and one upstream port. The upstream network hub/switch may be connected to a processor to provide a communication connection to the cloud computing resources and a local display 217. Communication to the cloud 204 may be made either through a wired or a wireless communication channel.
The surgical hub 206 may employ a non-contact sensor module 242 to measure the dimensions of the operating theater and generate a map of the surgical theater using either ultrasonic or laser-type non-contact measurement devices. An ultrasound-based non-contact sensor module may scan the operating theater by transmitting a burst of ultrasound and receiving the echo when it bounces off the perimeter walls of an operating theater as described under the heading “Surgical Hub Spatial Awareness Within an Operating Room” in U.S. Patent Application Publication No. US 2019-0200844 A1 (U.S. patent application Ser. No. 16/209,385), titled METHOD OF HUB COMMUNICATION, PROCESSING, STORAGE AND DISPLAY, filed Dec. 4, 2018, which is herein incorporated by reference in its entirety, in which the sensor module is configured to determine the size of the operating theater and to adjust Bluetooth-pairing distance limits. A laser-based non-contact sensor module may scan the operating theater by transmitting laser light pulses, receiving laser light pulses that bounce off the perimeter walls of the operating theater, and comparing the phase of the transmitted pulse to the received pulse to determine the size of the operating theater and to adjust Bluetooth pairing distance limits, for example.
The computer system 210 may comprise a processor 244 and a network interface 245. The processor 244 can be coupled to a communication module 247, storage 248, memory 249, non-volatile memory 250, and input/output interface 251 via a system bus. The system bus can be any of several types of bus structure(s) including the memory bus or memory controller, a peripheral bus or external bus, and/or a local bus using any variety of available bus architectures including, but not limited to, 9-bit bus, Industrial Standard Architecture (ISA), Micro-Charmel Architecture (MSA), Extended ISA (EISA), Intelligent Drive Electronics (IDE), VESA Local Bus (VLB), Peripheral Component Interconnect (PCI), USB, Advanced Graphics Port (AGP), Personal Computer Memory Card International Association bus (PCMCIA), Small Computer Systems Interface (SCSI), or any other proprietary bus.
The processor 244 may be any single-core or multicore processor such as those known under the trade name ARM Cortex by Texas Instruments. In one aspect, the processor may be an LM4F230H5QR ARM Cortex-M4F Processor Core, available from Texas Instruments, for example, comprising an on-chip memory of 256 KB single-cycle flash memory, or other non-volatile memory, up to 40 MHz, a prefetch buffer to improve performance above 40 MHz, a 32 KB single-cycle serial random access memory (SRAM), an internal read-only memory (ROM) loaded with StellarisWare® software, a 2 KB electrically erasable programmable read-only memory (EEPROM), and/or one or more pulse width modulation (PWM) modules, one or more quadrature encoder inputs (QEI) analogs, one or more 12-bit analog-to-digital converters (ADCs) with 12 analog input channels, details of which are available for the product datasheet.
In one aspect, the processor 244 may comprise a safety controller comprising two controller-based families such as TMS570 and RM4x, known under the trade name Hercules ARM Cortex R4, also by Texas Instruments. The safety controller may be configured specifically for IEC 61508 and ISO 26262 safety critical applications, among others, to provide advanced integrated safety features while delivering scalable performance, connectivity, and memory options.
The system memory may include volatile memory and non-volatile memory. The basic input/output system (BIOS), containing the basic routines to transfer information between elements within the computer system, such as during start-up, is stored in non-volatile memory. For example, the non-volatile memory can include ROM, programmable ROM (PROM), electrically programmable ROM (EPROM), EEPROM, or flash memory. Volatile memory includes random-access memory (RAM), which acts as external cache memory. Moreover, RAM is available in many forms such as SRAM, dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM (DRRAM).
The computer system 210 also may include removable/non-removable, volatile/non-volatile computer storage media, such as for example disk storage. The disk storage can include, but is not limited to, devices like a magnetic disk drive, floppy disk drive, tape drive, Jaz drive, Zip drive, LS-60 drive, flash memory card, or memory stick. In addition, the disk storage can include storage media separately or in combination with other storage media including, but not limited to, an optical disc drive such as a compact disc ROM device (CD-ROM), compact disc recordable drive (CD-R Drive), compact disc rewritable drive (CD-RW Drive), or a digital versatile disc ROM drive (DVD-ROM). To facilitate the connection of the disk storage devices to the system bus, a removable or non-removable interface may be employed.
It is to be appreciated that the computer system 210 may include software that acts as an intermediary between users and the basic computer resources described in a suitable operating environment. Such software may include an operating system. The operating system, which can be stored on the disk storage, may act to control and allocate resources of the computer system. System applications may take advantage of the management of resources by the operating system through program modules and program data stored either in the system memory or on the disk storage. It is to be appreciated that various components described herein can be implemented with various operating systems or combinations of operating systems.
A user may enter commands or information into the computer system 210 through input device(s) coupled to the I/O interface 251. The input devices may include, but are not limited to, a pointing device such as a mouse, trackball, stylus, touch pad, keyboard, microphone, joystick, game pad, satellite dish, scanner, TV tuner card, digital camera, digital video camera, web camera, and the like. These and other input devices connect to the processor through the system bus via interface port(s). The interface port(s) include, for example, a serial port, a parallel port, a game port, and a USB. The output device(s) use some of the same types of ports as input device(s). Thus, for example, a USB port may be used to provide input to the computer system and to output information from the computer system to an output device. An output adapter may be provided to illustrate that there can be some output devices like monitors, displays, speakers, and printers, among other output devices that may require special adapters. The output adapters may include, by way of illustration and not limitation, video and sound cards that provide a means of connection between the output device and the system bus. It should be noted that other devices and/or systems of devices, such as remote computer(s), may provide both input and output capabilities.
The computer system 210 can operate in a networked environment using logical connections to one or more remote computers, such as cloud computer(s), or local computers. The remote cloud computer(s) can be a personal computer, server, router, network PC, workstation, microprocessor-based appliance, peer device, or other common network node, and the like, and typically includes many or all of the elements described relative to the computer system. For purposes of brevity, only a memory storage device is illustrated with the remote computer(s). The remote computer(s) may be logically connected to the computer system through a network interface and then physically connected via a communication connection. The network interface may encompass communication networks such as local area networks (LANs) and wide area networks (WANs). LAN technologies may include Fiber Distributed Data Interface (FDDI), Copper Distributed Data Interface (CDDI), Ethernet/IEEE 802.3, Token Ring/IEEE 802.5 and the like. WAN technologies may include, but are not limited to, point-to-point links, circuit-switching networks like Integrated Services Digital Networks (ISDN) and variations thereon, packet-switching networks, and Digital Subscriber Lines (DSL).
In various aspects, the computer system 210 of FIG. 6, the imaging module 238 and/or visualization system 208, and/or the processor module 232 of FIGS. 5-6, may comprise an image processor, image-processing engine, media processor, or any specialized digital signal processor (DSP) used for the processing of digital images. The image processor may employ parallel computing with single instruction, multiple data (SIMD) or multiple instruction, multiple data (MIMD) technologies to increase speed and efficiency. The digital image-processing engine can perform a range of tasks. The image processor may be a system on a chip with multicore processor architecture.
The communication connection(s) may refer to the hardware/software employed to connect the network interface to the bus. While the communication connection is shown for illustrative clarity inside the computer system, it can also be external to the computer system 210. The hardware/software necessary for connection to the network interface may include, for illustrative purposes only, internal and external technologies such as modems, including regular telephone-grade modems, cable modems, and DSL modems, ISDN adapters, and Ethernet cards.
FIG. 7 is a block diagram of an example surgical simulator system. The surgical simulator system may include a simulation device 30000. The surgical simulator system may include an application creation device 30002, a human interface device 30004, a surgeon agent device 30006, and/or a surgical data system 30008.
The simulation device 30000 may provide core simulation functionality. For example, the loading/running of one or more simulations, the reception and processing of user control information input, the generation and transmission of visual, audible, and/or haptic information output, the collection of simulation operation and activity information, and the primary simulation cycle processing may be performed by the simulation device 30000.
The application creation device 30002 may provide simulation authoring functionality. Individual simulation applications may be stored as application modules 30010 at the simulation device 30000. The application modules 30010 may be created, modified, and/or deleted by the application creation device 30002. The application modules 30010 may include computer readable and/or executable instructions to direct an operation of the simulation device 30000. For example, the application modules 30010 may include any filetype suitable for storing information to run a surgical simulation, for example, simulation scripts, programming code, structure data files such as Extensible Markup Language (XML) files, database files, and the like.
The application creation device 30002 may include a graphical user interface with controls to author application modules 30010. The application creation device 3002 may communicate with the simulation device 30000 to retrieve, modify, and/or load application modules 30010 for simulation operation. For example, the graphical user interface may include interface structures to allow a user to select simulation activities, to input various simulation parameters, to set simulation objectives, and to confirm simulation execution. The application creation device 30002 may be provided as a stand-alone device and/or integrated with one or more other devices of the surgical simulation system, such as integrated with the simulation device 30000 for example.
The human interface device 30004 may include any hardware, software, and/or combination thereof that enables a human user to interact with a simulation provided by the simulation device 30000. The human interface device 30004 may enable a user to provide control input to the simulation device 300000 and/or to receive output information (such as visual, audible, and/or haptic information) from the simulation device 30000. In one example, the human interface device 30004 may include a traditional desktop computer.
The human interface device 30004 may include suitable physical equipment. For example, the human interface device 30004 may include physical equipment that mimic physically and/or virtually aspects of a surgical procedure. For example, such equipment may include bench-top units, part-task virtual reality units, high fidelity virtual reality units, high fidelity full-size patient units, suite units, high fidelity full operating room units, full physics virtual reality units, surgical robot console units, and the like. For example, the human interface device 30004 may include devices such as the computer-based simulator interfaces disclosed by Gallager et al, “Simulations for Procedural Training,” Fundamentals of Surgical Simulation, Principles and Practice, Springer (2012).
The human interface device 30004 may include physical equipment that mimics, physically and/or virtually, surgical instruments. For example, the human interface device 30004 may include physical devices that mimic surgical instruments, appliances, and consumables, such as access equipment, such as trocars, hand-access ports, insufflation needles, and guiding sheaths; adjunctive hemostats, such as patches, gelatins, and powders; craniomaxillofacial appliances, like distractors and plates; balloons and inflators; catheters, like diagnostic catheters, access catheters, vascular catheters, and therapeutic catheters; energy sealing and dissecting devices, like tissue sealers, shears, blades, and forceps; orthopedic equipment, like reduction wires, compression screws, plates, implants, drills, burrs, rods, and connectors; ligation instruments, like open and endoscopic clip appliers; microwave ablation equipment; ancillary endoscopic instruments, like drains, sutures, ligature, needle holders, retrievers, and suture clips; surgical stapling equipment, like open staplers, endoscopic staplers, cutter staplers, powered staplers, circular staplers, vascular staplers, linear staplers, staple cartridges, and staple line reinforcement applicators; wound closure materials, like suture, adhesives, needles, and knotless tissue control devices; imaging devices, like minimally invasive imaging devices; and the like. For example, the human interface device 30004 may include virtual reality handheld controllers, that when operated with a virtual reality headset, mimics the surgical instruments, appliances, and consumables, such as those disclosed above.
The human interface device 30004 may include a display that communicates visual representations of the simulation to the user. The human interface device 30004 may include a computer display. The human interface device 30004 may include a virtual reality headset display. For example, the virtual reality headset display may be used display the surgical environment, such as that disclosed in FIG. 2, herein. A user with such a virtual reality headset display may view and/or interact with any of the elements in the surgical operating room 116, including, for example, the patient, the robotic system 110, the surgeon's console 118, the surgical robotic hub 122, one or more surgical tools 117, the imaging device 124, the patient side cart 120, one or more displays 119, 107, 109, and the like.
The human interface device 30006 may present visual information that represents the point of the view of the surgeon. The human interface device 30006 may present visual information from a simulated imaging device, such as an arthroscope, angioscope, bronchoscope, choledochoscope, colonoscope, cytoscope, duodenoscope, enteroscope, esophagogastro-duodenoscope (gastroscope), endoscope, laryngoscope, nasopharyngo-neproscope, sigmoidoscope, thoracoscope, ureteroscope, and their related instruments, controls, and the like. The human interface device 30006 may present visual information from a simulated supplemental intra-operative imaging equipment, like computed tomography (CT) units, magnetic resonance imaging (MRI) units, image-guided surgery units, intra-operative ultrasound units; fluoroscopy units, and the like. Such point-of-view visual information, surgical imaging information, and supplemental intra-operative imaging information may be displayed in any combination to the user suitable for the simulation's operation. For example, such information may be presented to the user as a single full-screen view, a tiled window view, a picture-in-a-picture view, or registered to a simulated display unit in a virtual reality view.
The human interface device 30004 may include a physical and/or virtual reality surgical robot surgeon console. For example, an example surgeon-console-like human interface device 30004 may include a display, such as a stereo vision display and control inputs, including hand-held manipulators, foot pedals, and the like. For example, the surgeon-console-like human interface device 30004 may include an interface of the surgeon's console 118, disclosed herein. The human interface device 30004 may enable voice controls via, for example, a microphone and speech recognition functionality. The human interface device 30004 may provide audible feedback via, for example, a speaker. The human interface device 30004 may provide haptic feedback via, for example, vibration, force feedback, air vortex rings, and ultrasound techniques.
As implemented, the human interface device 30004 may be provided as a stand-alone device and/or integrated with one or more other devices of the surgical simulation system, such as integrated with the simulation device 30000 for example. The simulation device 30000 may include an interface module 30012 to communicate with the human interface device 30004. In an example, human interface device 30004 may be integrated into one or more elements of the computer-implemented interactive surgical system 100. For example, the human interface device 30004 may be integrated into the computer system 210. For example, the human interface device 30004 may be integrated into the hub 106. For example, the human interface device 30004 may be integrated into the visualization system 108. The interface module 30012 may communicate with the one or more elements of the computer-implemented interactive surgical system 100 via the surgical data system interface module 30014 for example.
In an embodiment, more than one human interface device 30004 may concurrently engage with the simulation device 30000. For example, a multi-person simulation applicatio.
The surgeon agent device 30006 may include any hardware and/or software suitable for providing a computer-based control and response to the input and output of the simulation device 30000. The surgeon agent device 30006 may include a computer process that mimics human input to the simulation device 30000. For example, the surgeon agent device 30006 may be able to record and register control inputs, such as basic instrument manipulation. The surgeon agent device 30006 may include a computer process that can access a input/output application programming interface (API) of the simulation device 30000. For example, the API may reveal one or more input/output functions that may be directed according to the surgeon agent device 3006. The functions may include granular manipulation and physics-based input/output functions, such as functions that directly control the location and movement of instruments. The functions may include less granular surgical-activity-based input/output functions, such as a ligation activity, a suturing activity, a stapling activity, and the like. The functions may include less granular surgical task and/or stage-based input/output functions, such as surgical access function, organ mobilization function, and the like. Each function may include parameter consistent with its level of granularity. The parameters may provide specific details to direct the operation of the function within the simulation. The surgeon agent 30006 may include functionality for generating and operating multiple simulation runs. For example, a user may wish to estimate the duration of various suturing techniques. A surgeon agent device 30006 may be used to script the simulation of any number of different techniques, each of which can be run via the simulation device, and the metrics collected by the simulation device may be used to estimate the difference in durations.
The surgeon agent device 30006 may be provided as a stand along device and/or integrated with one or more other devices of the surgical simulation system, such as integrated with the simulation device 30000 for example. The simulation device 30000 may include an interface module 30012 to communicate with the surgeon agent device 30006. For example, the surgeon agent device 30006 may be integrated as a module of the simulation device 30000. For example, the surgeon agent device 30006 may be integrated into an application module 30010 of the simulation device.
The surgical data system 30008 may include any hardware and/or software suitable for providing external, structured surgical information and functionality to the simulation device 30000. The surgical data system 30008 may include the structure and/or functions described in connection with FIGS. 1-6 herein. For example, the surgical data system 30008 may include one or more elements of a computer-implemented interactive surgical system 100. The surgical data system 30008 may include, for example, a surgical hub 106. For example, the simulation device 30000 include a surgical data system interface module 30014 that enables communication with the surgical hub 106 via the surgical hub's communication module 130. The surgical data system 30008 may include, for example, on or more surgical data repositories. For example, the surgical data system 30008 may include the computer system 210 located in the surgical theater. For example, the surgical data system 30008 may include the remote server 213 in the cloud 204.
A surgical data system 30008, such as the surgical hub 106 for example, may provide data to the simulation device 30000 and/or the application creation device 30002. For example, the data may include any surgical data collected and/or generated by the surgical hub 106. Also for example, the simulation device 30000 may receive similar data directly from any of the networked devices disclosed in FIGS. 1-6. Such data may include information about a live surgical procedure, for example. Such data may include information about a past surgical procedure. Such data may include information about future, scheduled surgical procedures.
Information about the surgical procedures may include information about the patient, the staff, the procedure as planned, the procedure as experienced, and post-operative activity including patient outcomes. For example, the information received and used by the simulation device may include patient records, patient imaging, models of patient anatomy, patient lab results, patient medical history, and the like. For example, the information received and used by the simulation device may include a staff manifest for a procedure, details about the past procedures of the specific staff members, staff metrics, experience, recent scheduling and workload, and historical surgical activity, such instrument use statistics, procedure duration, and the like. For example, the information received and used by the simulation device may include procedure plans, equipment and inventory information, pull-lists, checklists, procedure plan analysis and recommendations. For example, the information received and used by the simulation device may include any data collected or generated during a live procedure, such as procedure progress, milestones, patient information, vitals, operating theater setup, staff movement, imaging, instrument use, surgical technique, such as that captured by video, recorded manually, and/or inferred from smart-instrument reporting for example, duration, abnormal event reporting, and the like. Any data captured during a live procedure may also be stored and made available as a past procedure. For example, the information received and used by the simulation device may include post-operative records, patient recovery information, and patient outcome information, post-operative diagnostic information, such as labs, imaging, etc.
The simulation device 30000 may include any computer or processing platform suitable for executing one or more simulations. The simulation may include a computer-modeled environment of a surgical procedure. For example, the simulation may include a model of a patient's anatomy and/or physiology. For example, the simulation may include a model of the actions and/or instruments of one or more healthcare professionals, such as the actions of a surgeon, nurse, other doctor, technician, or the like.
The simulation device 30000 may include one or more functional modules. Each module may include hardware, software, or a combination thereof that enable functionality of the module. One or more modules, operating in concert, may represent a computer framework on which a simulation of a medical procedure may be executed. The modules may include hardware elements, such as a computer processing unit, a graphics processing unit, a field-programmable gate array (FPGAs), communications hardware, memory, and the like. The modules may include software elements that when executed by a processor cause the module to perform certain functions.
The simulation device may include a core simulation module 30016, a simulation applications module directory 30018, the interface module 30012, an object properties module 30020, a physics module 30022, a physiology model 30024, a texture model 30026, a 3D graphics pipeline 30028, the surgical data system interface module 30014, a metrics extraction module 30030, a session storage and management module 30032, for example. The simulation device may include an operating system module 30034.
The core simulation model 30016 may provide primary simulation functionality of the simulation device 30000. For example, the core simulation module 30016 may include code for initializing a simulation, for communicating and interacting with other modules of the simulation device 30000, and/or for managing architectural level simulation parameters. For example, the core simulation module 30016 may include a master event clock to provide time alignment and/or coordination of the operation of the modules of the simulation device 30000. For example, the core simulation module 30016 may establish the overall simulation frame rate.
The core simulation module 30016 may include core for providing a master simulation cycle. The core simulation module 30016 may run one or more iteration of the master simulation cycle. Each iteration of the master simulation cycle may represent an individual time slice for simulation. In an example, the core simulation module 30016 may run the master simulation cycle according to the flow disclosed in FIG. 10.
The simulation applications module directory 30018 may manage the storing, retrieving, and/or linking of the one or more application modules 30010. Each application module 30010 may include code that directs the application-level aspects of a simulation. For example, an application module 30010 may include the functionality to provide a simulation of specific anatomy, of specific teaching scope, of specific equipment, or the like. In an example simulation device 30000, an application-specific simulation device 30000 may operate with a single application module 30010 with or without a simulation application module directory 30010. The simulation application module directory 30018 may operate based on interaction with the core simulation module 30016 and/or the application creation device 30002.
The interface module 30012 may provide functionality for interacting with the human interface device 30004 and/or the surgeon agent device 30006. For example, the interface module 30012 may include one or more drivers to translate information received from human interface device 30004 into software commands, interrupts, and the like. For example, the interface module 30012 may include a software application programming interface (API) for interacting with the surgeon agent 30006. The interface module 30012 may provide information received from the human interface module 30004 and/or the surgeon agent device 30006 to other modules of the simulation device 30000. For example, the interface module 30012 may receive a control input from the human interface module 30004 and/or the surgeon agent device 30006 that represents movement of a simulated instrument and provide that information to one or more other modules of the simulation device 30000 so the movement may be represented in the simulation.
The interface module 30012 may provide the API to enable a more granular interaction with the surgeon agent device 30006. For example, the API may provide an interface to receive simulation parameters and simulation settings from the surgeon agent device 30006. Such simulation parameters and/or simulation settings may be like those input by the user via the application creation device 30002, for example. For example, the surgeon agent device 30006 may be enabled to run one or more computer-controlled simulation trials through the simulation device 30000. For example, the surgeon agent device 30006 may be enabled to run multiple simulations, each with alternative interactions.
The interface module 30012 may send output from the simulation device 30000 to the human interface device 30004 and/or the surgeon agent device 30006. For example, the output may include visual output, haptic output, audio output, and/or structured data output, or the like.
The object properties module 30020 may provide functionality for managing the simulated appearance and/or behavior of objects within in the simulation. Simulated objects may include objects such as anatomy, instrument, equipment, consumables, fluids, and the like. An object's appearance may be managed by object properties, such as location, dimensions, scale, material, parent/child relationships, vertices, faces, interactivity, transparency, trajectory, rendering properties, textures, surface reflectivity, motion blur, layering, and the like. An object's behavior may be managed by object properties, such as physics properties, mass, motion, collision behavior, elasticity, viscosity, surface tension, rigging constraints, hardness, shear strength, tearing behavior, grain, and the like. The physics module 30022 may provide functionality to calculate the physical responses and/or interaction of objects within the simulation. The physical module may determine such responses and/or interactions according to classical mechanics, fluid mechanics, soft body dynamics, Brownian motion, collision detection, cloth behavior, finite element analysis, and the like. The physics module 30022 may include commercial and/or open-source modules, such as PhysX™, Simulation Open Framework Architecture (SOFA)™, VisSim™, and the like.
The physiology module 30024 may provide functionality to calculate physiological responses and/or interactions of the anatomy and/or patient as a whole in the simulation. The physiology module 30024 may provide physiological models for key organs and/or systems. The physiological models may include mathematical models, statistical models, or the like. For example, the physiology module 30024 may module the patient's vitals to calculate their response and/or interaction to activities performed during the simulation. For example, a circulatory model may calculate blood pressure in response to a severed vessel in the simulation. The physiology module 30024 and the physics module 30022 may coordinate with each other during the calculation of each state of the simulation. For example, blood pressure calculated by the circulatory model may be used to determine fluid dynamics properties calculated by the physics module 30022 and managed by the object properties module 30020.
The texture module 30026 may provide functionality to determine, retrieve, and/or generate the appropriate surfacing of objects within the simulation. The texture module 30026 may include one or more surfacing modalities that may be controlled according to parameters of the simulation. The surfacing modalities may include artificially generated surfaces, surfaces based on real-world imagery, and combinations thereof. The texture module 30026 may coordinate operation with the physics module 30022 to provide accurate haptic feedback to the user via the user interface module 30012.
The 3D graphics pipeline 30028 may provide functionality for visual rendering of the simulation environment. The 3D graphics pipeline 30028 may receive object properties and a perspective. The 3D graphics pipeline 30028 may determine the visualization to be presented to the user that represents the objects in 3D space as viewed from the camera perspective. The 3D graphics pipeline 30028 may determine geometric aspects of the rendering, such as lighting, projection, clipping, view transformation, and the like. The 3D graphics pipeline 30028 may determine rasterization aspects of the rendering, such as fragmentation, pixel shading, vertex shading, geometry sharing, texture filtering, and the like. The 3D graphics pipeline 30028 may coordinate with the texture module 30026 to provide accurate visual feedback to the user via the interface module 30012.
The surgical data system interface module 30014 may provide interactive connectivity to one or more elements of computer-implemented interactive surgical system 100. Information from the one or more elements of the computer-implemented interactive surgical system 100 may be communicated via the surgical data system interface module 30014 to one more modules of the simulation device 30000 to influence operation of a simulation. For example, the surgical data system interface module 30014 may receive information about a surgical procedure an communicate it to a corresponding application module 30010. For example, the surgical data system interface module 30014 may receive information about an instrument and communicate it to the object properties module 30020. For example, the surgical data system interface module 30014 may receive information about a patient and communicate to the physiology module. For example, the surgical data system interface module 30014 may receive information about tissue imaging and communicate it to the texture module 30026.
Information from the modules of the simulation device 30000 may be provided, via the surgical data system interface 30014, to one or more elements of the computer-implemented interactive surgical system 100. For example, one or more elements of the computer-implemented interactive surgical system 100 may receive statistics related to a simulated procedure plan from the metrics extraction module 30030. For example, one or more elements of the computer-implemented interactive surgical system 100 may receive replayed simulation visualization procedure plan from the session storage and management module 30032. For example, the surgical data system interface module 30014 may provide a communications pathway between the interface module 30012 and one or more elements of the computer-implemented interactive surgical system 100. For example, a surgeon during a live surgical procedure may access simulation information and/or operate a simulation from the operating theater. For example, a surgeon may use the surgeon console 118 to access and/or interact with a simulation that corresponds to the live surgical procedure.
The metrics extraction module 30014 may provide recording functionality of various parameters related to the operation of the simulation. For example, the metrics extraction module 30014 may record metrics related to the simulation as a whole, such as duration, number of activities, number of movements, complexity of movements, staff employed, staff movement, equipment and/or instrument changes, etc. For example, the metrics extraction module 30014 may record metrics related to a particular aspect of the simulation, such as simulated patient vitals, complications, collisions, bleeding, etc. The metrics extraction module 30014 may maintain a master log of metric-related events during a simulation. For metrics extraction module 30014 may record metric-related events according to a configuration from the application module 30010 employed for the simulation.
The session storage and management module 30032 may provide management functionality of the main simulation run-record. For example, the session storage and management module 30032 may store the information to enable a simulation to be rerun, viewed, and/or analyzed in its entirety. The session storage and management module 30032 may store the information about each input, simulation state, and output, such as the input, simulation state, and output disclosed with regard to FIG. 10. The session storage and management module 30032 may enable a previous simulation to be recalled, copied, and initialized with new user input. To illustrate, a surgeon in training may recall a simulation run by an experienced surgeon, pause the simulation at a critical step, and attempt that step on her own. The session storage and management module 30032 may provide overlay functionality between various runs of a particular simulation. Such overlays may highlight similarities and differences and may enhance training.
The operating system module 30034 may manage the hardware and/or software resources for the simulation device 30000. The operating system module 30034 may provide common computing system-level services for the other modules of simulation device 30000. For example, the operating system module 30034 may provide hardware input and output handling, memory allocation, hardware interrupt handling, software interrupt handling, thread processing, single task handling, multi-task handling, and the like. The simulation device 30000 may be a real-time computing device. The operating system module 30034 may include a real-time operating system. For example, the operating system module 30034 may be driven by the events and frame rate established by the core simulation module 30016.
FIG. 8 is a block diagram of an example surgical simulator system. The simulation device 30000 is depicted with an example hardware architecture. For example, the simulation device 30000 may include a processor 30034, a memory 30036, a storage 30038, a display adapter 30040, a manipulation interface adapter 30042, a surgical data system adapter 30044, and/or a network adapter 30046. One or more of the processor 30034, a memory 30036, a storage 30038, a display adapter 30040, a manipulation interface adapter 30042, a surgical data system adapter 30044, and/or a network adapter 30046 may be used to enable operation of the modules of the simulation device 30000 disclosed herein.
The processor 30046 may include computer processing unit, graphics processing unit, any suitable microcontroller, microprocessor, field programmable gate array (FPGA), application specific integrated circuit (ASIC), or the like, and/or any combination thereof that is suitable for processing and delivering a 3D simulated environment for interaction with a computer agent and/or human user. In one example, the processor 30046 may include one or more processing units. The processor 30046 may be a processor of any suitable depth to perform the digital processing requirements disclosed herein. For example, the processor 30046 a 32-bit processor, a 64-bit processor, a 128-bit processor, or the like.
Such processors may comprise, or may be in communication with, media, for example computer-readable media, that may store instructions that, when executed by the processor, can cause the processor to perform the steps described herein as carried out, or assisted, by a processor. Embodiments of computer-readable media may comprise, but are not limited to, an electronic, optical, magnetic, or other storage device capable of providing a processor, such as the processor in a web server, with computer-readable instructions. Other examples of media comprise, but are not limited to, a floppy disk, CD-ROM, magnetic disk, memory chip, ROM, RAM, ASIC, configured processor, all optical media, all magnetic tape or other magnetic media, or any other medium from which a computer processor can read. The processor, and the processing, described may be in one or more structures, and may be dispersed through one or more structures. The processor may comprise code for carrying out one or more of the methods (or parts of methods) described herein.
The memory 30036 may include any component or collection of components suitable for storing data. For example, the memory 30036 may include volatile memory and/or nonvolatile memory. The memory 30036 may include random-access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), (electrically erasable programmable read-only memory) EEPROM, flash memory, or the like.
The storage 30038 may include any component or collection of components suitable for storing large quantities of data. For example, storage 30038 may include hard disk drives (HDD), solid state drives (SSD), network-attached storage (NAS), or the like. The storage 30038 may include a database structure and/or a database management system (DBMS).
The display adapter 30040 may include any component or collection of components suitable for outputting the visual representation of a 3D simulation environment. For example, the display adapter 30040 may include a graphics card, a display card, a graphics adapter, or the like. The display adapter 30040 may be used to generates a feed of output images to a display device, such as a display of the human interface device 30004. The display adapter 30040 may include a graphics processing unit (GPU). The display adapter 30040 may include hardware to render a graphics pipeline, for example. The manipulation interface adapter 30042 may include any component or collection of components suitable for receiving manipulation information from the human interface device and/or outputting feedback information to the human interface device. For example, the manipulation interface adapter 30042 may receive motion tracking information from a virtual reality headset and in turn, manipulate the view being displayed to the user. For example, the manipulation interface adapter 30042 may receive control input indicative of a user manipulating a surgical instrument and, in turn, output haptic feedback to the user's handheld device. For example, the manipulation interface adapter 30042 may receive control information from a traditional desktop keyboard and mouse. The manipulation interface adapter may include input/output hardware such as serial input/output ports, parallel input/output ports, universal asynchronous receiver transmitters (UARTs), discrete logic input/output pins, analog-to-digital converters, digital-to-analog converters, universal serial bus (USB) ports, USB-C ports, FireWire ports, High Performance Parallel Interface (HIPPI), Thunderbolt port, Yapbus, Ethernet, Gigabit Ethernet, and/or any other suitable peripheral interface technology.
The surgical data system adapter 30044 may include any component or collection of components suitable for communicating with the surgical data system 30008. The surgical data system adapter 30044 may include communications hardware to establish a physical channel between the simulation device 30000 and the surgical data system 30008. For example, the surgical data system adapter 30044 may include a communication port such as, a USB port, USB-C ports, FireWire ports, HIPPI port, Thunderbolt port, Yapbus port, Ethernet port, Gigabit Ethernet port, and/or any other suitable peripheral interface. The surgical data system adapter 30044 may include hardware, software, and/or a combination thereof to establish a logical channel between the simulation device 30000 and the surgical data system 30008 over the network adapter 30046 and the network 30048.
The network adapter 30046 may include any component or collection of components suitable for communication over a network, such as network 30048 for example. The network adapter 30046 may enable communication over networks such as local area networks (LANs), wide area networks (WANs), and/or mobile networks. LAN technologies may include Fiber Distributed Data Interface (FDDI), Copper Distributed Data Interface (CDDI), Ethernet/IEEE 802.3, Token Ring/IEEE 802.5, Wi-Fi/IEEE 802.11, and the like. WAN technologies may include, but are not limited to, point-to-point links, circuit-switching networks like Integrated Services Digital Networks (ISDN) and variations thereon, packet-switching networks, and Digital Subscriber Lines (DSL). The mobile networks may include communication links based on one or more of the following mobile communication protocols: GSM/GPRS/EDGE (2G), UMTS/HSPA (3G), long term evolution (LTE) or 4G, LTE-Advanced (LTE-A), new radio (NR) or 5G, etc.
In an embodiment, the network adapter 30046 may include a wireless network adapter, such as a 5G network adapter. Such a 5G network adapter 30046 may use a 5G New Radio (NR) transceiver to provide enhanced mobile broadband (eMBB) with ultra-reliable and low latency communications (URLLC). Such a 5G network adapter 30046 may use wireless bands, such as higher wireless bands like the 3.5 Ghz-7 Ghz and/or the 24 GHz-48 GHz bands. The network 30048 servicing such a 5G network adapter 30046 may include a public wireless network, a semi-private (e.g., network slicing-based) network, and/or a fully private wireless network.
FIG. 9 is a block diagram depicting an example surgical simulator human user interface device 30004. The human user interface device 30004 is depicted with an example hardware architecture. For example, the human user interface device 30004 may include a processor 30050, a memory 30052, a display subsystem 30054, and/or a manipulation subsystem 30056.
The processor 30050 may include computer processing unit, graphics processing unit, any suitable microcontroller, microprocessor, field programmable gate array (FPGA), application specific integrated circuit (ASIC), or the like, and/or any combination thereof that is suitable for handling the processing associated with displaying visual information received from the simulation device 30000, processing manipulation information for sending to the simulation device, processing feedback information received from the simulation device 30000, and the like. The processor 30050 may include a microcontroller to interface with one or more local sensors to sense control manipulation from the user and/or to interface with one or more local actuators to provide feedback from the user.
Such processors may comprise, or may be in communication with, media, for example computer-readable media, that may store instructions that, when executed by the processor, can cause the processor to perform the steps described herein as carried out, or assisted, by a processor. Embodiments of computer-readable media may comprise, but are not limited to, an electronic, optical, magnetic, or other storage device capable of providing a processor, such as the processor in a web server, with computer-readable instructions. Other examples of media comprise, but are not limited to, a floppy disk, CD-ROM, magnetic disk, memory chip, ROM, RAM, ASIC, configured processor, all optical media, all magnetic tape or other magnetic media, or any other medium from which a computer processor can read. The processor, and the processing, described may be in one or more structures, and may be dispersed through one or more structures. The processor may comprise code for carrying out one or more of the methods (or parts of methods) described herein.
The memory 30036 may include any component or collection of components suitable for storing data. For example, the memory 30036 may include volatile memory and/or nonvolatile memory. The memory 30036 may include random-access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), (electrically erasable programmable read-only memory) EEPROM, flash memory, or the like.
The display subsystem 30054 may include any component or collection of components suitable for displaying visual representations of a 3D simulation from the simulation device 30000 to a user. The display subsystem may include display hardware such as a monitor, a digital projector, a smart phone, a digital headset, a virtual reality headset, a stereoscopic display, a robotic surgery surgeon's console display, a surgical display unit, a surgical microscope, and the like.
The manipulation subsystem 30056 may include any component or collection of components suitable for collecting manipulation controls from the user to send to the simulation device 30000 and/or providing feedback information, received from the simulation device 30000, to the user. Manipulation from the user may include any interface with sensors that engage with the user, for example, engaging to indicate a user's intent in the simulation. For example, the interfaces may include keyboards, mice, joysticks, physical equipment that mimics the size, shape, and operation of actual surgical instruments, virtual reality hand-held controllers, smart gloves, motion sensing systems (such as hand tracking systems, for example), a robotic surgery surgeon's console manipulators and/or controls, a physical unit that mimics the size, shape, and operation of an actual robotic surgery surgeon's console manipulators and/or controls, and the like. For example, the interface may include a point of view sensor, such as an accelerometer, in a headset to indicate a user's point of view within the simulation.
Feedback from the simulation device 30000 may include any interface with an actuator that provides sensory input to the user. For example, the feedback may include haptic feedback, force feedback, temperature feedback, moisture feedback, audio feedback, olfactory feedback, and the like. For example, a force feedback and/or haptic actuator in the manipulator of a robotic surgery surgeon's console may be used to simulate the feedback the user would feel if operating such a manipulator in a live procedure. For example, a force feedback and/or haptic actuator in a user device that mimics the size, shape, and operation of actual surgical stapler may be used to simulate the feedback the user would feel if operating such a device on live tissue, including force feedback when engaging the tissue and firing the stapler for example.
FIG. 10 is a flow chart of an example surgical simulator operation. At 30058, a simulation application may be loaded. For example, the core simulation module 30016 may cause data associated with a particular application module 30010 to be loaded into memory 30036. The loaded data may include instructions for the processor 30034 to operate a particular simulation. The loaded data may include a procedural plan for the simulation. For example, the procedural plan may be structured as disclosed herein, for example with regard to FIGS. 11A-B. The loaded data may include an initial state for the simulation.
At 30060, the simulation output may be determined and/or sent. For example, the simulation output may be determined and/or sent by the simulation device 30000. Here, the core simulation module 30016 may reference a current state of the simulation (e.g., an initial state and/or a subsequent state). The core simulation module 30016 may engage one or more other modules to process the current state for output. For example, the core simulation module may engage any of the object properties module 30020, the texture module 30026, the application module 30010, the 3D graphics pipeline 30028, the interface module 30012, and/or the surgical data system interface module 30014 to process the current simulation state into information for output. Information related to the output maybe processed and/or stored by the metrics extraction module 30030 and/or the session storage and management module 30032, for example.
In a human-operated simulation session, for example, output information may be sent via the display adapter 30040 and/or the manipulation interface adapter 30042 to the display subsystem 30054 and/or the manipulation subsystem 30056 of the human interface device 30004. In a computer-controlled simulation session, for example, output information may be sent via the interface module 30012 to a surgeon agent 30006. Also for example, in a computer controlled simulation session, output information may be sent (e.g., processed locally) at an application module 30010. In a session accessed via the surgical data system 30008, for example, output information may be sent by the surgical data system interface module 30014 via the surgical data system adapter 30044 and/or the network adapter 30046.
At 30062, simulation input may be received and/or processed. For example, simulation input may be received and/or processed by the simulation device 30000. Here, the core simulation module may engage with the interface device, the surgical data system interface module, and/or the application module 30010 to receive control input. Information related to the input maybe processed and/or stored by the metrics extraction module 30030 and/or the session storage and management module 30032, for example.
In a human-operated simulation session, for example, input information may be sent from a manipulation subsystem 30056 of the human interface device 30004 and received via the manipulation interface adapter 30042. In a computer-controlled simulation session, for example, input information may be sent from a surgeon agent 30006 and received via the interface module 30012. Also for example, in a computer controlled simulation session, input information may be received (e.g., processed locally) at an application module 30010. In a session accessed via the surgical data system 30008, for example, input information may be received via the surgical data system adapter 30044 and/or the network adapter 30046 and initially handled by the surgical data system interface module 30014.
At 30064, a subsequent simulation state may be determined. For example, a subsequent simulation state may be determined from the current simulation state and/or the any received input. The core simulation module 30016 may engage one or more of the other modules of the simulation device 30000 to determine the subsequent simulation state. For example, the code simulation module 30016 may engage the application module, the object properties module, the physics module, the physiology module, and the like. The subsequent simulation state may be determined by operation of the processor 30034. Information related to the input maybe processed and/or stored by the metrics extraction module 30030 and/or the session storage and management module 30032, for example.
At this stage, the process may loop to receiving input at 30060. Each iteration of this flow may represent a corresponding time cycle in the simulation. The framerate of the simulation may be set to a level suitable for the goal of the simulation and the processing capabilities of the surgical simulation device 30000. Lower framerates may enable processing that achieves a live human interaction simulation. Higher framerates may enable greater simulation fidelity. For example, when operating computer-controlled simulations, with a surgeon agent 30006 for example, a higher framerate may be used, even if the higher framerate causes the processing time of the simulation to exceed the real-world time it is simulating.
FIGS. 11A-B illustrate example surgical procedural plan data structures for use with a computer-implemented interactive surgical system and/or a surgical simulator. A surgical procedure plan may include information that outlines the staff, equipment, technique, and steps that may be used to perform a surgical procedure. For example, the procedure plan may include a staff manifest indicating what roles and/or what specific health care professionals are to be involved in the procedure. The procedure plan may include a listing of equipment, such as durable surgical equipment, imaging equipment, instruments, consumables, etc. that may be used during the procedure. For example, the procedure plan may include a pick list for a surgical technician to use to assemble the appropriate tools and materials for the surgeon and the surgery when prepping the operating theater. The procedure plan may include information about the procedure's expected technique. For example, the procedure plans for the same surgical goal may include different methods of access, mobilization, inspection, tissue joining, wound closure, and the like.
The procedure plan may reflect a surgeon's professional judgement with regard to an individual case. The procedure plan may reflect a surgeon's preference for and/or experience with a particular technique. The procedure plan may map specific surgical tasks to roles and equipment. The procedure plan may provide an expected timeline for the procedure.
The procedure plan may include one or more decision points and/or branches. Such decision points and/or branches may provide surgical alternatives that are available for particular aspects of the procedure, where selection of one of the alternatives may be based on information from the surgery itself. For example, the choice of one or more alternatives may be selected based on the particular planes of the particular patient's anatomy, and the surgeon may select an alternative based on her assessment of the patient's tissue during the live surgery.
The procedural plan may include one or more contingencies. These may include information about unlikely but possible situations that may arise during the live surgery. The contingencies may include one or more surgical tasks that may be employed if the situation does occur. The contingencies may be used to ensure that adequate equipment, staff, and/or consumables are at the ready during the procedure.
The procedure plan may be recorded in one or more data structures. A procedure plan data structure may be used to record data about a future live surgery, about a completed live surgery, about a future simulated surgery, about a completed simulated surgery, and the like. A procedure plan data structure for live surgeries may be used by the computer-implemented interactive surgical system 100. For example, the procedure plan data structure for live surgeries may be used by surgical hub 106 to enhance situational awareness and/or the operational aspects of the computer-implemented interactive surgical system 100. The procedure plan data structure for live surgeries may be used by the surgical hub 106 to record discrete elements of the live surgery for structured analysis.
A procedure plan data structure may be used by a simulation device 30000. For example, the procedure plan data structure may be used by the simulation device 30000 to establish a setting and/or one or more objectives for a simulation session. For example, the procedure plan data structure may be used by the simulation device 30000 to record the discrete elements of the simulated surgery for structured analysis.
The procedure plan data structure may include any structure suitable for capturing data elements related to the procedure. For example, the procedure plan may be recorded in a tree-like data structure, such as the one shown in FIG. 11A, for example. Here, the root of the tree structure represents the core procedure data 30066. The core procedure data 30066 may include information about the procedure as a whole, such as procedure name, procedure code, patient name, date, time, and the like. For a simulation, the core procedure data 30066 may include information about simulation device, such as device ID, software version, user, the simulation run settings, such as frame rate, resolution, connected user interface devices, and the like.
The procedure data may include leaves of the tree structure. The first level of leaves may include data regarding the main aspects of the procedure plan, such as the procedure setup 30068, one or more procedure stages 30070, one or more contingencies 30072, and the data regarding the result of the procedure 30074.
The setup data 30068 may include information related to the preparations and/or initial state of the procedure. For example, the setup data 30068 may include elements such as staff manifest, staff roles and/or staff IDs, operating room ID, an equipment list, a room layout, an initial surgical table position, a listing of instruments and/or consumables on prepared in the surgical field, any initial settings associated with equipment, pre-surgical imaging, patient record, etc. For a simulation, the setup data 30068 may include information related the simulated environment, such as a record of the simulated anatomy, a record of the simulated physiology, pre-surgical imaging, and the like.
The stage data 30070 may include data elements related to a major milestone of the procedure. For example, a stage of a procedure may include a milestone such as establishing access. The stage data 30070 may include information related to the staff, equipment, technique, and steps that may be used to perform the particular stage of the procedure. The stage data 30070 may include a stage ID.
The stage may be further detailed by one or more sub-leaves, such as one or more surgical tasks 30076. The surgical task may represent a discrete surgical step within a given stage. For example, within the stage of access, placing a trocar may be a surgical task. The surgical task data 30076 may include a task ID. The surgical task data 30076 may include information related to the particular task, such as the staff and/or surgeon performing the task, the equipment to be used, the particular technique being applied, the patient vitals at the time the task is being performed, other environment information, and the list. Each task may be further detailed with goal data 30078, data related to an anatomy-instrument interaction 30080, and result data 30082. The goal data 30078 may include information indicative of the relative success of the task performance. The goal data 30078 may include information about expected task duration, acceptable performance specificity, efficiency modality, avoidance of complications, and the like. The result data 30082 may include information related to one or more goals. The result data 30082 may record the surgical performance (e.g., live and/or simulated) relative to the goals.
The task data 30076 may include one or more elements of anatomy-instrument interaction data 30080. The anatomy-instrument interaction data 30080 may represent a granular indication of surgical performance. The anatomy-instrument interaction data 30080 may represent the one or more specific activities used to perform the surgical task. The anatomy-instrument interaction data 30080 may represent the observable behavior of the surgeon.
In an example, the anatomy-instrument interaction data 30080 may include the specific positions, forces, angles, and the like being applied to the anatomy by the surgeon. For example in a live surgery, data recorded from smart instruments by the surgical hub 106 may be captured as anatomy-instrument interaction data 30080. For example, a smart surgical stapler in cooperation with other elements of the computer-implemented interactive surgical system 100 may record stapler position, angle, tip forces, jaw forces, staple cartridge type, closing pressure, firing rate, and the like. In a simulated surgery, similar data elements may be captured.
The contingency data 30072 may indicate any complications that may be relevant to the procedure. Each contingency data 30072 may include one or more task data elements 30084 that address the appropriate response to the particular complication. The contingency data 30072 may indicate deviations from an original procedure plan. Also for example, contingency data may be cross-referenced to one or more tasks 30078 and/or anatomy-instrument interactions 30080. For example, if a certain performance in an anatomy-instrument interactions 30080 could lead to a complication, the nature of that performance and a cross-reference to the contingency may include in the result data 30082 associated with that anatomy-instrument interactions 30080.
The result data 30074 may be indicative of the result of the procedure. Here overall metrics of the surgical performance may be stored, notes, actual and/or simulated patient recovery information, and/or patient outcomes. For example, the result data 30074 may include efficiency information, cost information, surgical duration, workload metrics, percentage of planned consumables used, and the like.
FIG. 11B illustrates a procedural plan data structure with the above disclosed elements, which further establishes structure of alternative steps for completing a particular procedure, task, or activity. As shown, the procedure represented by the procedure data 30086 may include two alternative setups, each indicated by respective setup data-a first setup data 30088, 30090 and a second setup data 30092. The first setup data 30088, 30090 may include two alternative tasks 30094, 30096. The second setup data 30092 may include one task 30098. In this illustration, the procedure represented by procedure data 30086 may be accomplished in three different ways. First via first setup 30088 and the first task 30094. Second via the first setup 30090 and the second task 30096. And third via the second setup 30092 and its corresponding task 30098.
Each path of the tree structure may represent a particular set of alternative ways to perform the procedure. Such a structure may be useful to aid the creation of a particular procedure plan for a particular live and/or simulated surgery. Such a structure may be useful to simulate many possible alternatives of a procedure to assess the differences in results.
FIG. 12 illustrates a system for providing simulation support in a live surgical procedure. A live surgical procedure may employ a simulation device 31500, a surgical data system, and the like. There may be stored a simulation of a particular surgical procedure. And a surgeon may benefit, when performing that particular procedure, from retrieving the stored simulation and interacting with it during the live procedure. The stored simulation may provide guidance, training, aid in memory and/or recall, and the like. The stored simulation may enable the surgeon to simulate a task and/or technique in temporal proximity to performing the task and/or technique live. The stored simulation may provide expert guidance on a particular task and/or technique, where the simulated anatomy and/or simulated patient conditions aligns with the live patient.
The simulation device 31500 may include a computing platform capable of storing, recalling, and/or running a simulation as disclosed herein. For example, the simulation device 31500 may include simulation device 30000 as disclosed herein. The simulation device 31500 may be in communication with a surgical data system 31502. For example, the simulation device 31500 may be in communication with a surgical data system 31502 via a communications leg 31504.
The surgical data system 31502 may include a surgical computing platform capable of providing surgical situational awareness, live imaging, simulation imaging, and the like. For example, the surgical data system 31502 may include the surgical data system 30008 disclosed herein. For example, the surgical data system 31502 may include one or more components of the computer-implemented interactive surgical system 100 disclosed herein. For example, the surgical data system 31502 may include the surgical hub 106 disclosed herein.
The surgical data system 31502 may be in communication with a simulation human user interface 31506. For example, the surgical data system 31502 may be in communication with the simulation human user interface 31506 via a communications leg 31508. The human interface device 31506 may include the human interface device 30004 disclosed herein. In an example, the human interface device 31506 may include user controls particularly suited for the operating room environment. For example, the human interface device 31506 may include simplified play-back controls. For example, the human interface device 31506 may include a robotic surgery surgeon's console with a simulation/live cutover switch, such that the same console may be used to interact with the simulation and interact with the live patient. In an embodiment, such a human interface device 31506 may enable a video overlay of imaging of the live procedure and imaging of the simulation.
The surgical data system 31502 may be in communication with a surgical display 31510. For example, the surgical data system 31502 may be in communication with the surgical display 31510 via a communications leg 31512. The surgical display 31510 may include one or more components of the computer-implemented interactive surgical system 100 disclosed herein. For example, the surgical display 31510 may include aspects of the visualization system 108, such as the primary display 119, the first non-sterile display 107, the second non-sterile display 109, and the like.
The surgical data system 31502 and/or the simulation device 31500 may be used to access archived portions of a simulation during the procedure, for example, to reorient and/or reanalyze key steps due to unanticipated deviations from the pre-surgery plan. In an example, a procedure plan may be created with surgical choices at key surgical steps. A simulation of this procedure plan may be recorded, archived, and/or later recalled during the actual procedure. For example, such simulated snap shots may be recalled by the surgeon to review and/or update with new data and/or unanticipated issues encountered during the procedure. For example, the simulation may be re-run during the procedure to provide the surgeon with new outcomes, choices, and/or impacts. Also for example, the simulation may be updated with information learned during the procedure, such as revising the simulated patient's anatomy. Such an updated simulation may be rerun during the procedure according to the procedure plan (and, for example, a corresponding surgeon agent). And such an updated simulation may be used to more closely align with the live procedure than the original simulation, for example.
In an example, the surgical data system 31502 and/or the simulation device 31500 may be used capture simulated and/or real-world snapshots of the procedure. Such snapshots may be recalled at a later point in procedure, at a time for example, when one or more organs and/or retractions are distorting and/or occluding the surgeon's view. For example, the operative view may be augmented with one or more snapshots from a preferred point in time, such as a preferred point in time associated with indocyanine green-based (ICG-based) anatomic delineation clarity. And once a critical structure is identified, the surgical data system 31502 and/or the simulation device 31500 may be used to re-apply (e.g., overlay) the snapshot as last viewed in the simulation.
In an example, the surgical data system 31502 and/or the simulation device 31500 may be used to archive certain alternative steps in simulation, such as alternate surgeon choices of approach, retraction, instrument usage, and the like. Such simulated alternative tasks may be accessed during the procedure. A simulation may be updated to align with the current state of the live procedure and then re-run with a selected alternative to provide metrics related to expected results. Such re-run simulations may be re-run automatically with this new information. And the surgical data system 31502 and/or the simulation device 31500 may incorporate such new information to update procedure forecasting.
In an example, new and/or updated simulations may be constructed “on the fly” during a live procedure. Such simulations may enable a surgeon to infer patient responses (e.g., micro-outcomes) and to explore the implication of certain granular surgical step choices. For example, such a simulation may enable a surgeon to determine a cause and/or correlated response to an activity and/or observed behavior in the live procedure.
In an example, the surgical data system 31502 and/or the simulation device 31500 may be used compare to work backwards from a desired outcome and identify one or more steps and/or boundary conditions that are associated with the desired outcome. For example, a comparison, using forward and backward simulation steps, may enable a surgeon to estimate the similarity between an actual and simulated surgical approach and its relation to a particular objective.
The operation of the simulation in concert with the live surgery may be coordinated by the surgical data system 31502, for example. The operation of the simulation in concert with the live surgery may be coordinated with reference to one or more procedure datasets.
Illustrating a use of the surgical data system 31502 and/or the simulation device 31500, the surgical display 31510 may show the present live surgery. The surgical display 31502 may be displaying a current task associated with upper lobe manipulation in a thoracic lobotomy. As shown, the surgeon's present technique is causing poor visualization of the pulmonary vein and/or pulmonary artery structures on the surgical display 31502. At this point, the surgeon may access a simulation of the corresponding task via the simulation human user interface 31506. The stored simulation may include a simulated based on the same and/or similar anatomy, performed by the same surgeon, performed by an expert surgeon, simulated with the same and/or similar instruments, and the like. The present task of the live procedure may be coordinated (e.g., coordinated via common task-based indexing) with a corresponding portion of the stored simulation. In response to the request, the surgical data system 31502 and/or the simulation device 31500 may retrieve the appropriate portion of the simulation and present it to the surgeon for interaction. As shown, the simulation may inform the surgeon of an improved instrument technique that may enhance visualization of the pulmonary vein and/or pulmonary artery structures by showing the simulation of the technique via the simulation human user interface 31506.
The operation of the simulation in concert with the live surgery may be coordinated with reference to a procedure plan for the simulated procedure, the procedure data associated with the actual simulation as executed, the procedure plan data for the live surgical procedure, the situational awareness data from the live surgical procedure, and the like.
FIG. 13 illustrates time-based surgical and simulation data. Here, example procedure plan data for the simulated procedure 31516, example procedure data associated with the actual simulation as executed 31518, example procedure plan data for the live surgical procedure 31520, and example situational awareness data from the live surgical procedure 31522 are illustrated as a series of tasks with reference to a timeline 31524. The datasets 31516, 31518, 31520, 31522 may be similarly structured. For example, the datasets 31516, 31518, 31520, 31522 may be structured according to a common and/or compatible data structure, such as the example data structure disclosed herein with reference to FIG. 11A.
The simulated procedure plan 31516 planned for task 1 to end and for task 2 to begin at time T1. Similarly, when the simulated procedure was executed as a simulation, for example before the actual live procedure, the simulated task 1 ended and simulated task 2 began at time T1, as recorded by the simulation data 31518. In this example, the procedure plan data 31520 for the live procedure indicated that the task 1 was planned to end and task 2 was planned to begin at time T1. However, during the live surgical procedure, as indicated by the surgical situational awareness data 31522, task 1 ended and task 2 began at time T2, which is different and/or after time T1.
Here, with a time-based reference, a surgeon retrieving a copy of the simulated procedure for viewing and/or interacting during the live procedure would face mismatched timing. Such a surgeon may sync the playback of the simulation to the live procedure by a jog operation forward and/or backward to find the appropriate time T1 in the simulation that matched the corresponding task in the live surgery at time T2.
FIG. 14 illustrates a task-based indexing of the time-based surgical and simulation data. Here, example procedure plan data for the simulated procedure 31526, example procedure data associated with the actual simulation as executed 31528, example procedure plan data for the live surgical procedure 31530, and example situational awareness data from the live surgical procedure 31532 are illustrated as a series of tasks with reference to a task-based index 31534. The datasets 31526, 31528, 31530, 31532 may be similarly structured. For example, the datasets 31526, 31528, 31530, 31532 may be structured according to a common and/or compatible data structure, such as the example data structure disclosed herein with reference to FIG. 11A. For example, the datasets 31526, 31528, 31530, 31532 may be structured with a task identifier field that provides unique identifier for individual tasks. For example, datasets 31526, 31528, 31530, 31532 may be structured with a task type field that is a common key for data elements that contain information about various planned, simulated, or actual instances of the same task.
In the simulated procedure plan 31526, the transition for planned task 1 to end and/or for planned task 2 to begin may be indexed at index 01. Similarly, when the simulated procedure was executed as a simulation, the end of simulated task 1 and/or the start of simulated task 2 may be indexed at index 01 in the simulation data 31528. Likewise, the procedure plan data 31530 for the live procedure indexes the end of task 1 as planned and the start of task 2 as planned with index 01. And during the live surgical procedure, as indicated by the surgical situational awareness data 31532, the end of task 1 and/or the beginning of task 2 may be indexed with index 01.
The indexing may be based on the transition from one task to a subsequent task, for example. The indexing may be based on completion of a task. The indexing may be based on the start of a task. The indexing may be common across different data sets. For example, a task may have common indexing for each corresponding instance of that task in different data sets. The procedure data structure may enable such common indexing. In an example, a transition from a particular task to the subsequent task may be commonly indexed with corresponding instances of the task and subsequent task in other data sets regardless of the time planned and/or actually elapsed associated with the task. Similarly, the transition from a particular simulated task to the subsequent simulated task may be commonly indexed with corresponding instances of the live task and subsequent live task in another data set regardless of the time cycle and/or framerate of the simulated task.
Here, with task-based indexing, a surgeon retrieving a copy of the simulated procedure for viewing and/or interacting during the live procedure may use the common index, index 01 for example, to skip to the appropriate portion of the simulation, such as the portion of the simulation that corresponds to the present point in the live procedure.
In an embodiment, the surgeon may run and/or retrieve one or more alternative simulated tasks. The alternative simulated task may be indicated by corresponding procedure plan data for the alternate simulated task 31536. The alternate simulated task may be indicated by the simulation data of the alternate simulated task 31538. Here, the start of the corresponding alternate task as planned for simulation may be similarly indexed at index 01. The start of the corresponding alternate task as simulated may be similarly indexed at index 01. Such alternatives may be recorded via a common data structure. For example, such alternatives may be accommodated by the data structure disclosed herein with reference to FIG. 11B for example. For example, tasks that may serve as alternatives for one another, such as at branching and/or decision points, may be commonly indexed.
Index information may be stored as part of the disclosed datasets 31526, 31528, 31530, 31532, 31536, 31538, for example. Index information may be stored apart from the disclosed datasets 31526, 31528, 31530, 31532, 31536, 31538, for example. Index information may be stored in a centralized data base, for example. Index information in a centralized database may provide cross referencing to unique task identifiers present in the disclosed data sets 31526, 31528, 31530, 31532, 31536, 31538, for example.
FIG. 15 is a flow diagram of example process for providing simulation support in a live surgical procedure. At 31540, a procedure plan for a live surgical procedure may be identified. For example, the procedure plan for the live surgical procedure may be identified, created, copied, modified, or the like, such as part of a pre-surgical planning process. Such a procedure plan for the live surgical procedure may be used by a surgical data system in managing and/or supporting the live surgical procedure. For example, such a procedure plan may be used by the surgical data system to support situational awareness functionality.
At 35142, a stored simulation may be identified. The stored simulation may be a simulation of a surgical procedure that corresponds to the procedure plan identified at 31540, for example. The stored simulation may be a simulation of a surgical plan that corresponds to the procedure plan by having common tasks, for example. The stored simulation may be a simulation of a surgical plan that corresponds to the procedure plan by having setup, such as patient anatomy, for example. The stored simulation may be a simulation of a surgical plan that corresponds to the procedure plan by having tasks that may serve as alternatives to the tasks set forth in the procedure plan, for example.
In an example, the procedure plan may include a set of tasks. The stored simulation may include information indicative of simulated activity. The information of simulated activity may be indexed according to the set of tasks in the procedure plan.
At 31544, a present portion of the live surgical procedure may be determined. For example, the present portion of the live surgical procedure may be determined from information received during the live surgical procedure. For example, the present portion of the live surgical procedure may be determined from information received during the live surgical procedure at a surgical data system, such as a surgical hub 106 for example. For example, the present portion of the live surgical procedure may be determined from surgical situational awareness information received during the live surgical procedure. For example, the present portion of the live surgical procedure may be determined from task index information received during the live surgical procedure.
At 31546, a portion of the stored simulation that corresponds to the present portion of the live surgical procedure may be retrieved. For example, the portion of the stored simulation that corresponds to the present portion of the live surgical procedure may be retrieved based on an analysis of the information received during the live surgical procedure, at 31544 for example. For example, the portion of the stored simulation that corresponds to the present portion of the live surgical procedure may be retrieved based on a common index between the portion of the stored simulation and the present portion of the live surgical procedure.
In an example, the present portion of the live surgical procedure may be determined, at 31546, according to a present task (such as by an index of the present task) from the procedure plan identified at 31542. A portion of the store simulation (e.g., a portion of information indicative of simulated activity) may be retrieved based on an index of the present task.
At 31546, the portion of the stored simulation that corresponds to the present portion of the live surgical procedure may be retrieved. For example, the portion of the stored simulation that corresponds to the present portion of the live surgical procedure may be retrieved from the stored simulation. For example, the portion of the stored simulation that corresponds to the present portion of the live surgical procedure may be retrieved from the stored simulation in a simulation device, such as simulation device 31500, for example.
At 31546, the portion of the simulation that corresponds to the present portion of the live surgical procedure may be presented for user interaction. For example, the portion of the simulation that corresponds to the present portion of the live surgical procedure may be presented for user playback. For example, the portion of the simulation that corresponds to the present portion of the live surgical procedure may be presented for a user to perform simulated activities. For example, the portion of the simulation that corresponds to the present portion of the live surgical procedure may be presented for a user to consider alternative surgical tasks.
The portion of the simulation that corresponds to the present portion of the live surgical procedure may be presented for a user interaction by the surgical data system, such as surgical data system 31502, for example. The portion of the simulation that corresponds to the present portion of the live surgical procedure may be presented for a user interaction by the simulation device, such as simulation device 31500, for example. The portion of the simulation that corresponds to the present portion of the live surgical procedure may be presented for a user interaction by the simulation device in cooperation with a surgical data system, such as by simulation device 31500 in cooperation with surgical data system 31502, for example.
For example, control input may be received during the live procedure. The control input may be for the portion of the simulation that corresponds to the present portion of the live surgical procedure. Based on the control input, a live simulation may be executed. The live simulation may be executed during the live procedure. For example, the live simulation may correspond to the portion of the stored simulation that corresponds to the present portion of the live surgical procedure. In an example, such a control may include a modification of the user activity in the stored simulation. For example, the modification of the user activity may include modifying any of selection, instrument configuration, technique selection, application location, or the like. In an example, such a control may include a modification of the simulation settings of the stored simulation. For example, the modification of the settings may include modifying the simulated anatomy.
A visualization of the present portion of the live surgical procedure may be presented. A presentation of the retrieved portion of simulation may be presented. The visualization of the present portion of the live surgical procedure may be presented concurrently with a presentation of the portion of the simulation that corresponds to the present portion of the live surgical procedure. In an example, a user control may include a timeline user control to view the stored simulation at a time other than that which corresponds to the present portion of the live surgical procedure. In an example, a different portion of the stored simulation may be retrieved based on a user's selection of the timeline control.
In an example, a user control may include a task-based index user control to view the stored simulation at a task other than that which corresponds to the present portion of the live surgical procedure. In an example, a different portion of the stored simulation may be retrieved based on a user's selection of the task-based index user control. In an example, a user control may include a procedure plan user control. The user may use the procedure plan user control to view a different portion of stored simulation that corresponds to that selected by the procedure plan user control. For example, a different portion of the stored simulation may be retrieved based on a user's selection of the procedure plan control.
The process flow at 31540-31548 may be performed at any suitable configured processor, such as a processor of the surgical data system 31502, a processor of the simulation device 31500, a processor of the human interface device 31506, and the like.
Simulation support may refer to the use of a surgical simulation during a live surgical procedure so as to provide active guidance to the surgeon during a surgery. For example, simulation support may refer to having a simulation environment that runs simultaneously and continuously with the live surgical procedure. For example, simulation support may refer to a simulation which is not actively being run simultaneously with the live surgical procedure, but one which can be queried so as to present a portion of a simulation which has been run at least once. Each of these embodiments can be considered to provide support, or guidance, to a surgeon during a live surgical procedure.
User interaction may also refer to user guidance. In other words, the portion of the simulation may be presented or displayed to the surgeon for the purposes of guiding the surgery. It may be understood that a live surgical procedure may refer to a surgical procedure that is happening in real-time. In other words, the live surgical procedure can be happening concurrently with the operation of the simulation.
The processor may be configured to determine a portion of the live surgical procedure through information received (e.g. through image processing or through information received from a surgical hub, configured to determine surgical context).

Claims

1. A device for providing simulation support in a live surgical procedure, the device comprising:

a processor configured to:

identify a procedure plan for a live surgical procedure;

identify a stored simulation of a surgical procedure that corresponds to the procedure plan;

determine, from information received during the live surgical procedure, a present portion of the live surgical procedure;

retrieve, from the stored simulation, a portion of the stored simulation that corresponds to the present portion of the live surgical procedure; and

present, for user interaction, the portion of the simulation that corresponds to the present portion of the live surgical procedure.

2. The device of claim 1, wherein the procedure plan comprises a set of tasks, and wherein the stored simulation comprises information indicative of simulated activity indexed according to the set of tasks.

3. The device of claim 2, wherein the processor is further configured to determine the present portion of the live surgical procedure by determining a present task from the procedure plan.

4. The device of claim 3, wherein the processor is further configured to retrieve a portion of the simulation that corresponds to the present portion of the live surgical procedure by retrieving a selected portion of the information indicative of simulated activity that is indexed the present task.

5. The device of claim 1, wherein the processor is further configured present a visualization of the present portion of the live surgical procedure concurrently with a presentation of the portion of the simulation that corresponds to the present portion of the live surgical procedure.

6. The device of claim 1, wherein the user control comprises a timeline user control to view the stored simulation at a time other than that which corresponds to the present portion of the live surgical procedure.

7. The device of claim 6, wherein the processor is configured to retrieve a different portion of the stored simulation based on a user's selection of the timeline control.

8. The device of claim 1, wherein the user control comprises a procedure plan user control to view a different portion of stored simulation that corresponds to that selected by the procedure plan user control.

9. The device of claim 8, wherein the processor is configured to retrieve a different portion of the stored simulation based on a user's selection of the procedure plan control.

10. The device of claim 1, wherein the processor is further configured to receive control input during the live procedure, and to execute, with the control input, a live simulation that corresponds to the portion of the stored simulation that corresponds to the present portion of the live surgical procedure.

11. The device of claim 10, wherein the control input is a modification of the user activity in the stored simulation.

12. The device of claim 11, wherein the user activity comprises any of instrument selection, instrument configuration, technique selection, or application location.

13. The device of claim 10, wherein the control input is a modification of the simulation settings.

14. The device of claim 10, wherein the control input is a modification of simulated anatomy.

15. A method for providing simulation support in a live surgical procedure, the method comprising:

identifying a procedure plan for a live surgical procedure;

identifying a stored simulation of a surgical procedure that corresponds to the procedure plan;

determining, from information received during the live surgical procedure, a present portion of the live surgical procedure;

retrieving, from the stored simulation, a portion of the stored simulation that corresponds to the present portion of the live surgical procedure; and

presenting, for user interaction, the portion of the simulation that corresponds to the present portion of the live surgical procedure.

16. The method of claim 15, wherein the procedure plan comprises a set of tasks, and wherein the stored simulation comprises information indicative of simulated activity indexed according to the set of tasks.

17. The method of claim 16, further comprising determining the present portion of the live surgical procedure by determining a present task from the procedure plan.

18. The method of claim 17, further comprising retrieving a portion of the simulation that corresponds to the present portion of the live surgical procedure by retrieving a selected portion of the information indicative of simulated activity that is indexed the present task.

19. A device for providing simulation support in a live surgical procedure, the device comprising:

a processor configured to:

identify a procedure plan for a live surgical procedure;

retrieve, from the stored simulation, a portion of the stored simulation that corresponds to a portion of the live surgical procedure;

present, for user interaction, the portion of the stored simulation that corresponds to the present portion of the live surgical procedure;

receive control input during the live procedure; and

execute, with the control input, a live simulation that corresponds to the portion of the stored simulation that corresponds to the portion of the live surgical procedure.

20. The device of claim 19, wherein the control input is any of a modification of user activity in the stored simulation, a modification of the simulation settings, or a modification of simulated anatomy.