Automated Surgery System Setup and Configuration
The system automates the setup of surgical consoles by identifying users and tools using RFID and image recognition, addressing workflow interruptions and enhancing efficiency.
Patent Information
- Application Number
- JP2024528585
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2021-12-09
- Filing Date
- 2022-12-07
- Publication Date
- 2024-11-28
AI Technical Summary
The manual configuration of surgical consoles during surgical procedures interrupts the workflow and reduces efficiency due to the need for manual entry of user-specific settings and parameters, leading to inefficiencies in time management.
A system utilizing RFID devices, image recognition, and sensors to automatically identify users and surgical tools, mapping them to predefined settings and parameters, thereby configuring the surgical console to drive the tools accordingly.
Facilitates hands-free setup and configuration of surgical consoles, enhancing surgical efficiency by reducing manual intervention and improving time management.
Smart Images

Figure 2024544145000001_ABST
Abstract
Description
[Technical field]
[0001] Claiming priority This application claims the benefit of priority to U.S. Provisional Patent Application No. 63 / 265,168, filed December 9, 2021, entitled "AUTOMATIC SURGICAL SYSTEM SETUP AND CONFIGURATION," inventors Paul R. Hallen and Mark Alan Hopkins, all of which are incorporated herein by reference as if fully and completely set forth herein. [Background technology]
[0002] The number and complexity of surgical procedures, including ophthalmic procedures such as vitreoretinal surgery, is increasing daily. Many such surgical procedures require the use of multiple devices, such as a microscope, a display device, and various surgical tools and / or systems (e.g., a console). For example, when performing a vitrectomy procedure, a surgeon may typically use a vitrectomy probe (e.g., a vitreous cutter), an injection cannula, and an intraocular light, all of which may communicate with a surgical console, in addition to other tools and devices.
[0003] Before or during the performance of a surgical procedure, the surgical console may require certain inputs from the surgeon or other surgical staff to drive one or more appropriate surgical tools for the procedure. For example, operating mode settings, user-preferred tool settings and parameters (e.g., power, duration, etc.), display settings, and other such inputs may need to be entered and / or confirmed before or during the utilization of the surgical tools. Typically, a user, e.g., a surgeon, manually enters these various inputs, e.g., via a graphical user interface (GUI) or other interface on the surgical console. As a result, the flow of the surgical procedure may therefore be interrupted, and the surgeon's efficiency and time management may be reduced.
[0004] Thus, there is a need in the art for improved devices, systems, and methods for streamlining the configuration of a surgical console to a user's desired settings during or in preparation for a surgical procedure. Summary of the Invention [Means for solving the problem]
[0005] The present disclosure relates to surgical devices, systems, and methods, and more particularly, to devices, systems, and methods for automated setup and mode switching of surgical consoles and systems.
[0006] According to certain embodiments, a system for configuring a surgical console in a surgical environment is provided, the system comprising a memory comprising executable instructions and a processor in data communication with the memory, the processor further configured to execute instructions to cause the system to receive user identification information associated with a user in the surgical environment, map the user identification information to a user profile, identify one or more parameters for driving a surgical tool based on the user profile, and configure the surgical console to drive the surgical tool based on the one or more parameters.
[0007] So that the above-cited features of the present disclosure can be understood in detail, a more particular description of the present disclosure briefly summarized above can be had by reference to embodiments, some of which are illustrated in the accompanying drawings. It should be noted, however, that the accompanying drawings illustrate only exemplary embodiments and therefore should not be considered as limiting the scope thereof, as other equally effective embodiments may be recognized. [Brief description of the drawings]
[0008] [Figure 1] 1 illustrates a surgical environment with various surgical devices and systems whose settings may be automatically configured in accordance with certain embodiments of the present disclosure. [Figure 2A]1 illustrates a flow diagram of a method for using a surgical configuration system, according to certain embodiments of the present disclosure. [Figure 2B] 1 shows a schematic diagram of a surgical configuration system, according to certain embodiments of the present disclosure. [Diagram 3] 3 illustrates exemplary components of the surgical configuration system of FIG. 2, in accordance with certain embodiments of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0009] To facilitate understanding, the same reference numerals will be used, wherever possible, to designate identical elements common to the figures, and it is contemplated that elements and features of one embodiment may be beneficially incorporated in other embodiments without further reference.
[0010] In the following description, details are described as examples to facilitate understanding of the disclosed subject matter. However, it should be apparent to those skilled in the art that the disclosed implementations are examples and do not cover all possible implementations. Therefore, it should be understood that reference to the described embodiments is not intended to limit the scope of the present disclosure. Any changes and further modifications to the described devices, apparatuses, and methods, and any further applications of the principles of the present disclosure are fully contemplated as would normally occur to one skilled in the art to which the present disclosure pertains. In particular, it is fully contemplated that features, components, and / or steps described with respect to one implementation may be combined with features, components, and / or steps described with respect to other implementations of the present disclosure.
[0011] The embodiments of the present disclosure generally relate to a system for automatically configuring a surgical system, such as a surgical console, to a user's desired settings in a surgical environment, such as an ophthalmic surgical environment. In certain aspects, the system includes a controller configured to identify a user, such as a surgeon, through the use of a user-specific portable component, such as a radio frequency identification (RFID) device, that may communicate with a receiver operably coupled to the controller. Upon identification of the user, the controller may map the user to one or more sets of defined parameters / settings for the surgical system. The controller may further be configured to identify a surgical tool, such as an ophthalmic probe, that is or is being used by the user during a surgical procedure, for example, through a tool-specific RFID device or other sensor. In certain aspects, upon identification of the surgical tool being used, the controller may place the surgical console in an appropriate operating mode associated with the surgical tool. In certain aspects, upon identification of the user and the surgical tool, the controller may cause the surgical console to drive the surgical tool based on one or more sets of defined parameters / settings associated with the user and mapped to it. In further aspects, the controller may be configured to identify the user and / or the surgical tool through an image recognition mechanism.
[0012] As used herein, the term "surgical system" may refer to any surgical system, console, or device for performing a surgical procedure. For example, the term "surgical system" may refer to a surgical console, such as a phacoemulsification console, a vitrectomy console, a laser system, or any other console, system, or device used in an ophthalmic operating room, as known to those of skill in the art. It should be noted that although certain embodiments herein are described in the context of ophthalmic systems, tools, and environments, the embodiments described herein are applicable to other types of medical or surgical systems, tools, and environments as well.
[0013] As used herein, the term "sensor" may refer to any type of device that, for example, detects or measures, records, indicates, or otherwise responds to a physical input. For example, the term "sensor" may refer to a device configured to detect or measure the position, location, proximity (e.g., relative to a surgical console), tilt, height, speed (e.g., accelerometer), temperature, etc., of a surgical tool, system, or user. In certain embodiments, the term "sensor" may refer to a device configured to detect touch, i.e., contact of a surgical tool or system by a user, such as a capacitive or resistive touch sensor. In certain embodiments, the term "sensor" may refer to an imaging device configured to detect and relay image-based information, such as an active pixel sensor (APS) such as a charge-coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) sensor.
[0014] Although generally described with reference to ophthalmic surgical devices and systems, the devices and systems described herein may be implemented with other devices and systems, such as devices and systems for other surgeries, without departing from the scope of the present application.
[0015] As used herein, the term "about" may refer to a + / - 10% variation from the nominal value, and it is understood that such a variation can be included in any value provided herein.
[0016] FIG. 1 illustrates an example of a surgical environment 100, such as an ophthalmic surgical environment, in which a surgical console 120 may be utilized to perform a surgical procedure, according to an embodiment of the present disclosure. As shown, the surgical environment 100 further includes a surgeon 110, a patient 112, and a number of surgical systems and tools, such as a surgical console 120 having a display device 122, a microscope system 124, and a surgical tool 126. In general, examples of suitable surgical systems that may be included in the surgical environment 100 include surgical devices and consoles for performing vitreoretinal procedures, cataract surgery, corneal transplants, glaucoma surgery, LASIK surgery, refractive lens exchange, trabeculectomy, corneal incision procedures, and corneal transplant procedures, or other devices and consoles identifiable by one of ordinary skill in the art. Consoles capable of performing two or more of these procedures are also within the scope of the present disclosure. One example of a console configured to perform vitreoretinal procedures is the Constellation® system available from Alcon Laboratories, Inc., Fort Worth, Texas. One example of a console configured to perform cataract surgery is the Centurion® system available from Alcon Laboratories, Inc., Fort Worth, Texas.
[0017] The surgical console 120 includes a controller 104 (shown in phantom) and, in certain embodiments, a receiver 106 in communication with the controller 104. The controller 104 is configured to cause the surgical console 120 to perform one or more tasks to drive a surgical tool, e.g., surgical tool 126, in accordance with stored settings and parameters associated with the surgical tool. The receiver 106 may include any suitable interface for communication (e.g., one-way or two-way signals) between the controller 104 and, for example, a user identifier 130, discussed below. For example, the receiver 106 may include a wireless or wired connection between the controller 104 and the user identifier 130. In certain embodiments, the receiver 106 provides further communication (e.g., one-way or two-way signals) between the controller 104 and a tool identifier 140 and / or a usage sensor, each of which is described in further detail below.
[0018] In certain embodiments, the receiver 106 includes an RFID reader, a Bluetooth receiver, a Near Field Communication (NFC) reader, or another similar wireless receiver. In the embodiment of FIG. 1, the controller 104 and the receiver 106 are integrated within the surgical console 120, and the controller 104 includes or refers to one or more processors and / or memory devices integrated within the surgical console. In certain other embodiments, the controller 104 and / or the receiver 106 are standalone devices or modules in wireless or wired communication, for example, with the surgical console 120 and other devices within the surgical environment 100. In certain embodiments, the controller 104 refers to a set of software instructions that a processor associated with the surgical console 120 is configured to execute. In certain aspects, the operations of the controller 104 may be performed in part by a processor associated with the controller 104 and / or the surgical console 120 and in part in a public or private cloud.
[0019] In the example of FIG. 1 , the user identifier 130 is depicted on the surgeon 110. The user identifier 130 generally includes any suitable item, device, or component that may signal the presence of the surgeon 110 in the surgical environment 100 to the controller 104 and further identify the surgeon 110 for purposes of automatic setup and configuration of the surgical console 120 according to defined parameters / settings associated with the surgeon 110. In certain embodiments, the user identifier 130 includes a user-specific digital or analog barcode or other form of machine-readable code (e.g., a quick response "QR" code) that may be captured or read, for example, by an image scanner on the surgical console 120 in communication with the controller 104, and the code then utilized to identify the surgeon 110. In certain embodiments, the user identifier 130 includes a device configured to wirelessly transmit user-specific identification data to a receiver 106 in communication with the controller 104, for identification thereby. For example, user identifier 130 may include a passive or active RFID transponder or similar device for transmitting (i.e., communicating) user-specific identification data to receiver 106, which may include an RFID receiver. Particular examples of user identifier 130 may include an employee badge having an analog machine readable code, an employee badge or tag having an RFID transponder, a bracelet having an RFID transponder, etc.
[0020] In certain embodiments, the user identifier 130 may be a device configured with wireless communication capabilities, such as hardware / software, for communicating user-specific identification data to the controller 104. For example, the user identifier 130 may include a wireless cellular device, such as a smartphone, or a similar smart device, such as a smartwatch, tablet, or any other electronic device, capable of transmitting user-specific identification data to the controller 104 using technologies such as near-field communication, Bluetooth, or WiFi. In certain embodiments, the smart device may execute a software application that causes the smart device to communicate user-specific identification data to the controller 104 when the surgeon 110 is in proximity to the surgical console 120. For example, when the surgeon 110 is in proximity to the surgical console 120, the software application may be configured to communicate with the controller 104 automatically or as a result of some user action (e.g., user input). In certain embodiments, the user identifier 130 may require the surgeon 110 to enter a user-specific password to activate or unlock the user identifier 130 and enable communication between the user identifier 130 and, for example, the controller 104 or the surgical console 120. In certain embodiments, in addition to the identification data, the user identifier 130 may also provide the controller 104 with user-associated and user-preferred surgical tool and / or system settings, operational modes, operational and / or tool sub-modes, task parameters, calibration data, and the like.
[0021] During the performance of an ophthalmic surgical procedure on the patient 112, the surgeon 110 may utilize one or more surgical tools, including a surgical tool 126. As described above, the surgical tool 126 may include any suitable tool for performing an ophthalmic procedure, such as, for example, vitreoretinal surgery, cataract surgery, glaucoma surgery, etc. In certain embodiments, the surgical tool 126 and / or the surgical console 120 may include a tool identifier 140. The tool identifier 140 includes any suitable device or component that may identify or indicate to the controller 104 the type of surgical tool 126 for purposes of automatic setup, configuration, and / or operational mode selection of the surgical console 120 according to defined parameters / settings associated with the surgical tool 126. In certain embodiments, the tool identifier 140 further includes a usage sensor that may be in direct or indirect communication with the controller 104. The usage sensor may include any suitable type of sensor for detecting the use or handling of the surgical tool 126 by the surgeon 110. For example, in certain embodiments, the use sensor includes a touch or pressure sensor on the surgical tool 126 configured to detect handling of the surgical tool 126 by the surgeon 110, such as a capacitive, inductive, resistive, or piezoelectric sensor disposed on the handle of the surgical tool 126. In certain embodiments, the use sensor includes an accelerometer or tilt sensor on the surgical tool 126 configured to detect movement of the surgical tool 126, for example. In further embodiments, the use sensor includes a proximity or position sensor on the surgical tool 126 configured to detect the trajectory of the surgical tool 126 relative to the user identifier 130, the surgical console 120, and / or the surgical environment 100, for example.
[0022] In embodiments in which the surgical tool 126 is in wired communication with the surgical console 120 and / or the controller 104, the tool identifier 140 may transmit a tool-specific signal over the wired connection to the controller 104 to identify the surgical tool 126 upon detection of use or handling of the surgical tool 126, for example, by a use sensor. In certain embodiments, the tool identifier 140 may transmit a tool-specific signal over the wired connection to the controller 104 upon activation of the tool identifier 140 or the surgical tool 126. In such embodiments, the tool-specific signal may indicate both the identity of the surgical tool 126 (e.g., tool type, model, etc.) and its use or handling, which may or may not be based on detection of handling by a use sensor.
[0023] Similarly, in embodiments in which the surgical tool 126 wirelessly communicates with the surgical console 120 and / or controller 104 via the receiver 106, the tool identifier 140 may transmit a tool-specific signal via the receiver 106 to the controller 104 over the wireless connection to identify the surgical tool 126 upon detection of use or handling of the surgical tool 126 or upon activation of the tool identifier 140 or the surgical tool 126 (which may or may not be based on detection of handling by a use sensor). In certain embodiments, the surgical tool 126 may include an RFID transponder or similar component (e.g., as part of the tool identifier 140 or separately) for wirelessly transmitting tool-specific identification data to the controller 104 via the receiver 106. In certain embodiments, the tool identifier 140 includes a tool-specific barcode or other form of machine-readable code that may be captured or read, for example, by an image scanner or similar device coupled to the surgical console 120 and then in communication with the controller 104, which utilizes the code to identify the surgical tool 126. In such an embodiment, use of the surgical tool 126 may be envisioned, for example, by the surgeon 110 scanning the code.
[0024] In one particular embodiment, the use sensor includes a laser sensor or similar device positioned on the surgical console 120 and configured to detect the removal of the surgical tool 126 from the surgical console 120. In a further embodiment, the use sensor includes a weight sensor or other type of load cell disposed on the surgical console 120, such as on a tool tray 128 of the surgical console 120, configured to detect the lifting of the surgical tool 126 from the surgical console 120. In an embodiment in which the use sensor is a laser or weight sensor on the surgical console 120, the use sensor may detect the use of the surgical tool 126 and transmit a tool-specific signal to the controller 104, thereby indicating to the controller 104 both the identity of the surgical tool 126 and its handling by the surgeon 110.
[0025] In certain embodiments, the surgical environment 100 further includes an imaging device 160 that may be in direct or indirect communication with the controller 104. The imaging device 160 may be any suitable type of imaging device configured to capture and relay images of the surgeon 110 and / or surgical tool 126 to the controller 104, for example, for purposes of identification of the surgeon 110 and / or surgical tool 126 via an image recognition process. Thus, the imaging device 160 and image recognition via the controller 104 may be utilized to identify the presence of the surgeon 110 in the surgical environment 100, determine his / her identity, as well as to identify the type of tool and use (e.g., by the surgeon 110) of the surgical tool 126, instead of or in addition to the user identifier 130 and / or tool identifier 140. In certain embodiments, the imaging device 160 includes a digital camera utilizing a charge-coupled device (CCD) or complementary metal oxide semiconductor (CMOS) imaging sensor. In general, the imaging device 160 may be physically coupled to any suitable equipment or device within the surgical environment 100. In the embodiment of FIG. 1, the imaging device 160 may be coupled to the surgical console 120 and may image both the surgeon 110 and the surgical tool 126 when picked up by the surgeon 110. In further embodiments, the imaging device 160 may be coupled to, for example, the wrist of the surgeon 110 and thus configured to capture and detect images when the surgeon 110 picks up the surgical tool 126. In certain embodiments, multiple imaging devices 160 may be used in combination. For example, a first imaging device 160 on the surgical console 120 may detect and capture images of the surgeon 110 for image recognition of the surgeon 110, and a second imaging device 160 on the surgeon's wrist may detect and capture images of the surgical tool 126 for image recognition of the surgical tool 126. In certain embodiments, the imaging device 160 facilitates a two-factor parity check for both the presence of the surgeon 110 in the surgical environment 100 and whether the surgeon 110 is using and / or handling the surgical tool 126.
[0026] As discussed in more detail below with reference to Figures 2 and 3, the controller 104 interfaces (e.g., wirelessly or wired) with, for example, the user identifier 130, the tool identifier 140, and / or the imaging device 160 to determine the identity of the surgeon 110 and to identify the tools used by the surgeon 110 during the ophthalmic surgery. Upon determining the identity of the surgeon 110 and / or the surgical tools 126, the controller 104 takes one or more actions to automatically configure the surgical console 120 according to defined (e.g., pre-set or predetermined) and user-associated surgical tools and / or system settings, operational modes, operational and / or tool sub-modes, task parameters, calibration data, etc. Thus, the controller 104 allows for essentially "hands-free" system setup and configuration, thereby improving the efficiency of the surgical procedure by reducing the amount of manual configuration required from the surgeon 110 or other surgical staff whose hands may already be occupied with other tools or tasks.
[0027] FIG. 2A illustrates a flow diagram of a method 200 for automatically configuring a surgical console, such as surgical console 120, based on defined and user-associated tool and / or system settings using various devices of FIG. 1, according to certain embodiments of the present disclosure. FIG. 2B illustrates a schematic diagram of various components of FIG. 1 used during method 200, according to certain embodiments of the present disclosure. Accordingly, FIGS. 2A-2B are described with reference to various components of FIG. 1 for clarity. Although the procedure operations are described with reference to a single surgical tool 126, it should be noted that multiple surgical tools 126 may be utilized in conjunction with the systems and methods described herein. Additionally, when multiple surgical tools are utilized by method 200, the surgical tools may be different types of tools.
[0028] In operation 202, a controller associated with a surgical console receives user identification data associated with a user in the surgical environment. For example, the controller 104 of the surgical console 120 receives surgeon identification data associated with the surgeon 110 in the surgical environment 100. As described above, in certain embodiments, the controller 104 receives user identification data associated with the surgeon 110 from a user identifier 130 associated with the surgeon 110. In one example, when the user identifier 130 is present in the surgical environment 100 and in proximity to the surgical console 120, the user identifier 130 transmits a user identification signal 250 (e.g., an RF signal) to the controller 104. The user identification signal 250 transmitted to the controller 104 indicates to the controller 104 the presence of the surgeon 110 in the surgical environment 100 and identifies the surgeon 110. In certain embodiments, the user identifier 130 may transmit the user identification signal 250 (e.g., a WiFi signal) to the controller 104 regardless of whether the surgeon 110 and the user identifier 130 are or will be present in the surgical environment 100. In such an embodiment, the user identification signal 250 transmitted to the controller 104 indicates to the controller 104 the current or future presence of the surgeon 110 in the surgical environment 100 and indicates the identity of the surgeon 110 .
[0029] As described above, the user identifier 130 includes any suitable item, device, or component that may provide a user identification signal 250 to the controller 104 regarding the identity of the surgeon 110 for purposes of setting up and configuring the surgical console 120 according to defined parameters / settings associated with the surgeon 110 for the surgical tool 126. In certain embodiments, the user identifier 130 is a passive or active RFID type transponder that interfaces with the controller 104 via a receiver 106, which may be an RFID type receiver, such as an RFID type receiver configured to activate the passive RFID type user identifier 130. In such embodiments, the user identifier 130 may be brought into proximity with or contacted against the receiver 106, for example, prior to the start of a surgical procedure, such that the user identification signal 250 from the user identifier 130 may be transmitted to the controller 104. In certain other embodiments, the user identifier is a WiFi-enabled device capable of transmitting a WiFi signal to the controller 104 without the need for the user identifier 130 to be present in the surgical environment 100.
[0030] In certain embodiments, user identification data is obtained by the controller 104 through image recognition of the surgeon 110, for example, using an imaging device 160, which may be communicatively coupled to the surgical console 120 and / or the controller 104. In such examples, the imaging device 160 may capture and relay images of the surgeon 110 for transmission to the controller 104, which may utilize one or more image recognition algorithms to map the captured images of the surgeon 110 to a corresponding surgeon profile indicative of the identity of the surgeon 110.
[0031] In operation 204, upon receipt of the user identification data (e.g., signal 250), the controller 104 maps the user identification data to a user profile of the surgeon 110 and one or more corresponding defined sets of parameters / settings for the surgeon 110. The defined set of parameters / settings may be surgeon specific and may be used by the surgical console 120 to operate and drive the corresponding surgical tools. For example, the defined set of parameters / settings may include user-defined (defined by the surgeon 110) and user-preferred (preferred by the surgeon 111) surgical tool and / or console settings, modes, sub-modes, task parameters, calibration data, etc., for one or more different surgical tools and consoles, which may be predefined prior to the performance of a surgical procedure. In certain embodiments, the defined set of parameters / settings is stored within the user profile of the surgeon 110. In such embodiments, by mapping the user identification data to the surgeon profile, the controller 104 is able to access the defined set of parameters / settings for the surgeon 110. In one particular embodiment, the defined set of parameters / settings is stored in a memory of a user identifier, such as user identifier 130 , and transmitted to controller 104 via user identification signal 250 .
[0032] In certain embodiments, in operation 206, upon mapping the user identification signal 250 to the profile of the surgeon 110 and one or more defined sets of parameters / settings for the surgeon 110, the controller 104 may optionally request a confirmation 252 from the surgeon 110 to confirm the correct identification of the surgeon 110 and / or the defined set of parameters / settings. Requesting confirmation 252 may avoid incorrect identification of the surgeon 110 and incorrect mapping to non-corresponding user profiles and incorrect parameters / settings that may occur when two or more surgeons or other surgical staff with their own user identifiers 130 are present (or pass through) in the surgical environment 100. The confirmation 252 may be in the form of an audible confirmation by the surgeon 110, a tactile confirmation via, for example, pressing a physical or on-screen button, or the like. In certain embodiments, as part of the confirmation 252, the mapped profile and / or set of parameters / settings of the surgeon 110 is displayed on a display device, such as the display device 122 of the surgical console 120, for viewing by the surgeon 110. In one particular embodiment, a pop-up window having one or more on-screen buttons may be displayed on the display device 122 for the surgeon 110 to confirm or reject the surgeon's 110 identification and / or a defined set of parameters / settings by pressing an on-screen button.
[0033] In certain embodiments, in operation 208, the controller 104 optionally identifies an operational mode for the surgical console 120. For example, the surgical console 120 may have several different operational modes for different procedures, such as a "phaco" mode for performing phacoemulsification and related cataract surgery procedures, a vitreous mode for performing vitreous procedures (e.g., vitrectomy), etc. In such an example, the controller 104 may identify the operational mode by mapping a user profile of the surgeon 110 to a defined operational mode of the surgical console 120 corresponding to the surgeon 110. For example, for a surgeon 110 performing a phacoemulsification procedure, the controller 104 may identify that the surgical console 120 should be in a phacoemulsification surgery mode based on the profile of the surgeon 110. Upon mapping to an operational mode for the surgical console 120, the controller 104 may place or switch the surgical console 120 into the mapped operational mode. However, in certain embodiments, the controller 104 may request confirmation 256 of the defined operating mode by the surgeon 110 before placing or switching the surgical console 120 into the mapped operating mode, as described below. Placing or switching the surgical console 120 into the mapped operating mode may include displaying a user interface associated with the mapped operating mode on the display 122 of the surgical console 120, unlocking or activating a corresponding surgical tool 126 typically used for the mapped operating mode, etc.
[0034] In certain embodiments, in operation 210, upon identifying an operational mode, the controller 104 may optionally request confirmation 256 from the surgeon 110 to confirm the correct mapping and selection of the operational mode before placing or switching the surgical console 120 into the operational mode. Similar to confirmation 252, confirmation 254 may be in the form of an audible confirmation by the surgeon 110, a tactile confirmation via, for example, pressing a physical or touch screen button, or the like. In certain embodiments, as part of confirmation 255, the mapped operational mode is displayed on a display device, such as display device 122 of the surgical console 120, for viewing by the surgeon 110. In certain embodiments, a pop-up window having one or more on-screen buttons may be displayed on the display device 122 for the surgeon 110 to confirm or reject the correct mapping and selection of the operational mode.
[0035] In operation 212, the controller 104 receives tool identification data associated with the surgical tool 126 that the surgical console 120 is configured to drive. In certain embodiments, the tool identification data is transmitted (e.g., wired or wirelessly) to the controller 104 and / or the user identifier 130 in the form of a tool identification signal 258 that may indicate to the controller 104 the type of tool, device, model, etc., of the surgical tool 126. In certain embodiments, the tool identification signal 258 is transmitted to the controller from a tool identifier 140 associated with the surgical tool 126. As shown in FIG. 2B, the tool identifier 140 may interface directly or indirectly with the controller 104 and, in certain embodiments, with the user identifier 130. As discussed above, the tool identifier 140 generally includes any suitable component or device that may transmit the tool identification signal 258 to the controller 104 and / or the user identifier 130 regarding the identification of the surgical tool 126 for purposes of setting up and configuring the surgical console 120 according to defined parameters / settings associated with the surgical tool 126. In certain embodiments, the surgical tool 126 may include a use sensor (either as part of the tool identifier 140 or separately) for generating a sensory signal as a result of the surgical tool 126 being used. For example, the use sensor may include any suitable type of sensor, component, or device for detecting use or handling 260 of the surgical tool 126 by the surgeon 110. In certain embodiments, the tool identifier 140 transmits a tool identification signal 258 to the controller 104 and / or the user identifier 130 when the use sensor generates a sensory signal indicating the surgical tool 126 is being used.
[0036] In certain embodiments, the tool identification signal 258 is transmitted directly from the surgical tool 126 to the controller 104 upon detection of use or handling 260 of the surgical tool 126, for example, by a use sensor. However, in certain other embodiments, the tool identification signal 258 is first transmitted by the surgical tool 126 to the user identifier 130, which then relays the tool identification signal 258 to the controller 104. For example, the user identifier 130 may be an RFID-type bracelet and the tool identifier 140 may be a similar RFID-type component on the surgical tool 126. Proximity of the RFID-type bracelet to the tool identifier 140 (as a result of the surgeon 110 gripping the surgical tool 126) may signal use or handling 260 of the tool and cause the tool identification signal 258 to be transmitted from the tool identifier 140 to the user identifier 130. The user identifier 130 may then relay a tool identification signal 258 to the controller 104 (eg, along with the user identification signal 250 ), thereby indicating to the controller 104 that the surgeon 110 is using the surgical tool 126 .
[0037] In certain embodiments, instead of or in addition to a surgical tool 126 having a use sensor, a use sensor (e.g., a laser sensor, a load sensor, etc.) may be positioned on or provided as part of the surgical console 120. In such embodiments, the use sensor may be configured to generate a sensory signal when a user lifts the surgical tool 126 from its resting position on the surgical console 120. In certain embodiments, the sensory signal may then cause the controller 104 to receive a tool identification signal 258 to identify the surgical tool 126. In embodiments in which a use sensor is positioned on or provided by the surgical console 120, a sensory signal generated as a result of handling the surgical tool 126 may act as the tool identification signal 258.
[0038] In certain embodiments, the tool identification data is obtained through image recognition of the surgical tool 126, for example, using an imaging device 160, which may be communicatively coupled to the surgical console 120 and / or the controller 104. In such examples, the imaging device 160 may capture and relay images of the surgical tool 126 for transmission to the controller 104, which may then utilize one or more image recognition algorithms to map the captured images of the surgical tool 126 to corresponding tool identification data.
[0039] In operation 214, upon receipt of the tool identification data (e.g., signal 258), the controller 104 maps the tool identification data to a tool profile. For example, if the surgical tool 126 is a vitreous retinal probe, the tool identification data is mapped to a vitreous retinal probe profile. In certain embodiments, once the tool profile is mapped, the controller 104 maps the identity of the surgical tool 126 (as indicated by the tool profile) to one of the one or more surgeon-specific sets of parameters / settings previously mapped in operation 204 and / or to an operational mode of the surgical console 120. For example, the surgeon-specific parameters / settings mapped in operation 204 may include parameters / settings for performing a vitreous retinal procedure as well as parameters / settings for performing a phacoemulsification procedure. In such an example, the identity of the surgical tool 126 may be used by the controller 104 to identify which of the one or more sets of parameters / settings are applicable. For example, if the identified surgical tool 126 is a vitreous probe, the controller 104 identifies that parameters / settings for performing a vitreous procedure should be used when the surgical tool 126 is used by the surgeon 110.
[0040] Additionally, if the controller 104 is unable to select an operating mode based on the surgeon profile (e.g., if the surgeon performs various procedures that correspond to different operating modes), the tool identification data may be used by the controller 104 to map to the appropriate operating mode. For example, if the surgical tool 126 that the surgeon 110 just picked up is a vitreous retinal probe, the controller 104 may identify that the surgical console 120 should be placed or switched to an operating mode associated with vitreous retinal surgery.
[0041] In certain embodiments, in operation 216, the controller 104 may optionally request confirmation 262 from the surgeon 110 to confirm the correct identification of the surgical tool 126. Requesting confirmation 262 may avoid inaccurate identification of the surgical tool 126 and mapping to an incorresponding tool profile, which may occur when more than one surgical tool is present in the surgical environment 100. The confirmation 262 may be in the form of an audible confirmation by the surgeon 110, a tactile confirmation, such as via pressing a physical or touch screen button, etc. In certain embodiments, as part of the confirmation 262, an image of the identified surgical tool 126 or the mapped tool profile is displayed on a display device, such as the display device 122 of the surgical console 120, for viewing by the surgeon 110. In certain embodiments, a pop-up window with one or more on-screen buttons may be displayed on the display device 122 for the surgeon 110 to confirm or reject the correct identification of the surgical tool 126.
[0042] In operation 218, the controller 104 drives the surgical tool 126 according to the surgeon-specific parameters / settings in the mapped operating mode. For example, the controller 104 may first place the surgical console 120 in the mapped operating mode (e.g., vitreous retinal mode), which may cause the surgical console 120 to display a user interface (UI) associated with the operating mode (e.g., vitreous retinal related UI) on the display 122, as one example. Then, in response to a trigger (e.g., a surgeon-initiated trigger, such as by a foot pedal), the controller 104 may begin driving the surgical tool 126 according to the surgeon-specific parameters / settings. As discussed above, the surgeon-specific parameters / settings may include surgical tool and / or console settings, modes, sub-modes, task parameters, calibration data, etc. For example, in an example where the surgical tool 126 is a vitreous retinal probe, the controller 104 may begin driving the surgical tool 126 according to surgeon-specific vitreous retinal tool sub-modes, each of which may include different duty cycles, minimum and maximum cutting speeds, and / or vacuum thresholds, etc. In certain embodiments, actuation of the surgical tool 126 may be triggered by or associated with surgeon-initiated movement of a foot pedal or similar device in communication with the surgical console 120 .
[0043] FIG. 3 illustrates an exemplary diagram showing how the various components of the surgical environment 100 illustrated in FIGS. 1-2 communicate and operate together. As shown, the surgical console 120 includes a controller 104 and a receiver 106 that allows for connection of the controller 104 to, but is not limited to, a user identifier 130 and / or a tool identifier 140. The controller 104 includes an interconnect 310 and a network interface 312 for connection to a data communication network 350. The controller 104 further includes a central processing unit (CPU) 316, a memory 318, and a storage 320. The CPU 316 may retrieve and store application data in the memory 318 as well as retrieve and execute instructions stored in the memory 318. The interconnect 310 transmits programming instructions and application data between the CPU 316, the network interface 312, the memory 318, the storage 320, the surgical tools 126, the imaging device 360, etc. The CPU 316 may represent a single CPU, multiple CPUs, a single CPU with multiple processing cores, etc. Memory 318 represents a random access memory.
[0044] Storage 320 may be a disk drive. Although shown as a single unit, storage 320 may be a combination of fixed or removable storage devices, such as a fixed disk drive, a removable memory card or optical storage, a network attached storage (NAS), or a storage area network (SAN). Storage 320 may include profiles 332 of users, e.g., surgeons 110, within a surgical environment that may utilize surgical console 120, where each user profile 332 may include a mapping of user identities to user-specific parameters / settings 334 and / or one or more operating modes. Storage 320 may further include tool profiles 338, each indicating a mapping to a corresponding type of tool and / or one or more operating modes. Storage 320 may further include operating modes 336, each mode having pre-defined instructions for operating surgical console 120 in the corresponding operating mode.
[0045] The memory 318 includes a configuration module 322 that includes instructions that, when executed by the CPU 316, enable the controller 104 to identify a user and / or a tool in a surgical environment, as described in embodiments herein. The memory 318 may also include an operating system and / or one or more applications (not shown) that, when executed by the CPU 316, enable the controller 104 to operate the surgical console 120 (e.g., including the driving tool 126 based on retrieved parameters / settings). For example, according to embodiments described herein, the memory 318 includes a user identification module 324 that includes executable instructions for identifying a user via a user identifier 130 and mapping the user to a user profile 332. Additionally, the memory 318 includes a tool identification module 326 that includes executable instructions for identifying a type of surgical tool 126 and mapping it to a corresponding tool profile 338.
[0046] As used herein, a phrase referring to "at least one of" a list of items refers to any combination of those items, including single elements. By way of example, "at least one of a, b, or c" is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination of multiples of the same elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other permutation of a, b, and c).
[0047] The above description is provided to enable those skilled in the art to practice the various embodiments described herein. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments. Accordingly, the claims are not intended to be limited to the embodiments shown herein, but are to be accorded the full scope consistent with the language of the claims.
[0048] In the claims, reference to an element in the singular is not intended to mean "one and only one" unless specifically so specified, but rather "one or more." Unless otherwise specified, the term "some" refers to one or more. All structural and functional equivalents of the elements of the various embodiments described throughout this disclosure that are known or later become known to those of skill in the art are expressly incorporated herein by reference and are intended to be included in the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is expressly recited in the claims. No element of a claim is to be construed under the provisions of 35 U.S.C. 112(f) unless the element is expressly recited using the phrase "means for" or, in the case of a method claim, the element is recited using the phrase "step for." The term "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects.
Claims
1. 1. A system for configuring a surgical console in a surgical environment, comprising: a memory having executable instructions; a processor in data communication with the memory and executing the instructions to provide the system with: receiving user identification information associated with a user in the surgical environment; Mapping the user identity to a user profile; identifying one or more parameters for driving a surgical tool based on the user profile; configuring the surgical console to actuate the surgical tool based on the one or more parameters; A processor comprising: A system comprising:
2. The system of claim 1 , further configured to display the one or more parameters on a display device of the surgical console.
3. The system of claim 1 , wherein the user identification information is received from an identification tag or badge of the user.
4. 4. The system of claim 3, wherein the identification tag or badge comprises a radio frequency identification (RFID) device configured to transmit a signal comprising the user identification information, and the processor is in data communication with an RFID reader configured to receive the signal and relay the user identification information to the processor.
5. The system of claim 1 , wherein the user identification information is received as an encrypted communication signal from the user's smart device.
6. 2. The system of claim 1, wherein the user identification information comprises an image of the user captured by an imaging device in data communication with the processor, the processor utilizing one or more image recognition algorithms to map the captured image of the user to the user profile.
7. Executing the instructions further comprises the step of: receiving tool identification information associated with the surgical tool; mapping the tool identification information to a tool profile, wherein the identification of the one or more parameters is further based on the tool profile; The system of claim 1 .
8. The system of claim 7 , further configured to display the tool profile on a display device of the surgical console.
9. The system of claim 7 , wherein the tool identification information is received from a tool identifier on the surgical tool.
10. The system of claim 9 , wherein the tool identifier comprises a radio frequency identification (RFID) device.
11. 10. The system of claim 9, wherein the surgical tool comprises a sensor configured to initiate transmission of the tool identification information from the tool identifier when the surgical tool is held by the user or when the sensor is pressed.
12. 8. The system of claim 7, wherein the tool identification information comprises an image of the surgical tool captured by an imaging device in data communication with the processor, the processor utilizing one or more image recognition algorithms to map the captured image to the tool profile.
13. 13. The system of claim 12, wherein the user identification information comprises an image of the user captured by the imaging device, the processor utilizing the one or more image recognition algorithms to map the captured image of the user to the user profile, and the processor further utilizing the one or more image recognition algorithms to identify whether the surgical tool is being used by the user.
14. Executing the instructions further comprises the step of: identifying an operational mode of the surgical console associated with the user based on the user profile; causing the surgical console to enter the operational mode; The system of claim 1 .
15. The system of claim 14 , further configured to display the operational mode associated with the user on a display device of the surgical console.
