Establishing a wireless data connection between medical devices

Abstract

A system, method, and computer program product are provided for establishing a wireless connection between a user interface device and a surgical device. The medical system includes a surgical device separate from the user interface device. The wireless data connection between the surgical device and the user interface device is facilitated by a cartridge that forms a functional component of the surgical device during operation of the surgical device to perform a surgical task. The cartridge includes a tag having stored data. The tag is read with the user interface device and the surgical device, and the surgical device and the user interface device are paired based on the data read from the tag to establish the wireless connection.

Description

[Technical Field]

[0001] Regarding establishing wireless data connections between medical devices.

[0002] [Related Applications] This application claims priority to and the entire benefit of U.S. Provisional Application No. 63 / 370124, filed August 2, 2022, the entire contents of which are incorporated herein by reference. [Background technology]

[0003] Surgical procedures often involve the use of medical systems incorporating computer controllers. Such medical systems often include several devices, such as data-generating devices, data-consuming devices, and control systems, that communicate with each other to facilitate the operation of the system. Reliable data communication between multiple devices helps ensure proper functionality of the system. It would be advantageous to provide a medical system with an intuitive pairing process for facilitating wireless data communication between devices that overcomes shortcomings and deficiencies present in previously known medical systems. Summary of the Invention

[0004] A system for use in an operating room may be configured to perform a particular operation or action by having software, firmware, hardware, or a combination thereof installed on the system that causes the system to perform the action during operation. One or more computer programs may be configured to perform a particular operation or action by including instructions that, when executed by a data processing device, cause the device to perform the action. In one aspect, a method is provided for establishing a wireless connection between a user interface device and a surgical device within a system via a cartridge that includes a tag for storing a unique identifier. The surgical device may include a first reader and a first communication device. The user interface device may include a second reader and a second wireless communication device.

[0005] The method can include using a second reader to read a unique identifier on a tag of a cartridge located near the second reader. The surgical device can be configured to establish one or more of a mechanical coupling, an electrical coupling, or a fluid coupling with the cartridge. The cartridge can be located near the first reader when the coupling is established. The cartridge can include a functional component of the surgical device in operation. The method can include using the first reader to read a unique identifier on a tag of a cartridge located near the first reader. The method can include broadcasting a unique identifier and a wireless device address using a first wireless communication device. The method can include scanning the unique identifier using a second wireless communication device. The method can include pairing the surgical device and the user interface device via the wireless device address based on a match of the scanned unique identifier with the broadcasted unique identifier.

[0006] In some embodiments, the method can include generating a wireless device name including a unique identifier and scanning the wireless device name with a second wireless communication device. In some embodiments, the surgical device can include a receiver, and the method can include removably receiving the cartridge in the receiver to establish a mechanical coupling between the surgical device and the cartridge. In some embodiments, the method can include detecting insertion of the cartridge into the receiver and activating the first reader based on the detected insertion.

[0007] In some embodiments, the surgical device can include a vacuum source in fluid communication with the receiver, and the cartridge can be a manifold configured to be removably coupled to the suction tube. The method can include operating the vacuum source of the surgical device to draw surgical waste through the suction tube and the manifold, such that the manifold facilitates (facilitates / assists) the wireless connection and is a functional component of the surgical device during operation.

[0008] In some embodiments, the surgical device can include a waste container in fluid communication with the receiver and a fluid measurement system operably coupled to the waste container. The method can include determining a fluid volume in the waste container using the fluid measurement system. The method can also include transmitting fluid volume data from the surgical system to a user interface device using a wireless connection. The method can also include displaying the fluid volume data using the user interface device.

[0009] In some embodiments, the surgical device and / or cartridge can include a means for determining a concentration of blood in the surgical waste. The method can include determining a concentration of blood in the surgical waste. The method can include determining a blood volume in the waste container based on the determined concentration of blood and the determined fluid volume. The method can include transmitting blood volume data from the surgical device to a user interface device via a wireless connection. The method can include displaying the blood volume data with the user interface device.

[0010] In some embodiments, the surgical device may further include a waste container and a vacuum source in fluid communication with the waste container. The surgical device and cartridge may include means for determining a concentration of blood in the surgical waste. The method may include operating the vacuum source of the surgical device to draw the surgical waste through the cartridge. The method may also include determining a concentration of blood in the surgical waste drawn through the cartridge. The method may further include determining a flow rate of the surgical waste drawn through the cartridge. The method may further include determining a blood volume in the waste container based on the determined blood concentration and the determined flow rate. The method may additionally include transmitting blood volume data from the surgical device to a user interface device via a wireless connection. The method may also include displaying the blood volume data using the user interface device.

[0011] In some embodiments, the tag comprises an RFID tag and the method can include writing or rewriting data to the tag. The data written or rewritten to the tag can prevent (prevent) the cartridge from being reused or reprocessed.

[0012] In some implementations, the first reader and the second reader are optical sensors. The tag can include a machine-readable optical code. The wireless connection can be established via the Bluetooth® wireless pairing protocol.

[0013] In another aspect, a method for establishing a wireless connection between a surgical device and a user interface device via a cartridge is provided. The cartridge can include a tag storing a unique identifier. The surgical device can include a vacuum source, a first reader, and a first wireless communication device. The user interface device can include a second reader and a second wireless communication device. The method can include placing the cartridge near the second reader. The method can include confirming, via an output displayed on the user interface device, that the unique identifier of the tag has been read by the second reader. The cartridge can be coupled to the surgical device such that the cartridge is placed near the first reader. The method can include reading the unique identifier of the tag with the first reader. The method can include establishing a wireless connection between the surgical device and the user interface device based on a match between the unique identifier scanned by the second wireless communication device and the unique identifier broadcast by the first wireless communication device. The method can include operating the vacuum source to draw surgical waste through the cartridge. The method can include viewing on the user interface device information transmitted from the surgical device to the user interface device via the wireless connection.

[0014] In some embodiments, the surgical device includes a receiver, and the cartridge can be coupled to the surgical device by being inserted into the receiver. Inserting the cartridge into the receiver can establish one or more of a mechanical connection, a fluid connection, or an electrical connection with the surgical device and can position the cartridge near the first reader.

[0015] In some implementations, the method can include confirming, via an output displayed on the user interface device, that the unique identifier of the tag has been read by the first reader. In some implementations, the method can include confirming, via an output displayed on the user interface device, that the wireless connection has been established.

[0016] In some embodiments, the surgical device may be located at a first location in the operating room and the user interface device may be located at a second location relative to the first location in the operating room, preventing the use of near field communication to establish a wireless connection.

[0017] In other aspects, provided are computer systems, apparatus, and computer program products including computer-executable instructions recorded on one or more computer storage devices, each configured to perform one or more actions of the methods described above.

[0018] In a further aspect, a system for use in an operating room is provided. The system can include a cartridge including a tag that stores a unique identifier. The system can include a surgical device including a vacuum source. The surgical device can include a waste container in fluid communication with the vacuum source. The surgical device can include a receiver in fluid communication with the waste container. The surgical device can include a first reader coupled to the receiver. The surgical device can include a first wireless communication device. The receiver can be configured to removably receive the cartridge to position the tag near the first reader. The system can include a user interface device positionable remotely from the surgical device. The user interface device can include a display. The user interface device can include a second reader. The user interface device can include a second wireless communication device that communicates with the second reader. The first wireless communication device can be configured to broadcast the unique identifier and a device address based on reading of the tag by the first reader. The second wireless communication device may be configured to scan the unique identifier to pair the surgical device and the user interface device via the wireless device address based on reading of the tag by the second reader and to establish a wireless connection between the surgical device and the user interface device.

[0019] In an additional aspect, a system for establishing a wireless connection between devices in a medical facility is provided. The system can include a cartridge including a tag that stores a unique identifier. The system can include a surgical device including a vacuum source. The surgical device can include a waste container in fluid communication with the vacuum source. The surgical device can include a first reader. The surgical device can include a first wireless communication device. The cartridge can be configured such that the tag is positioned near the first reader while in fluid communication with the vacuum source. The system can include a user interface device that can be positioned remotely from the surgical device. The user interface device can include a display. The user interface device can include a second reader. The user interface device can include a second wireless communication device that communicates with the second reader. The first wireless communication device can be configured to broadcast the unique identifier and a device address based on reading of the tag by the first reader. The second wireless communication device may be configured to scan the unique identifier to pair the surgical device and the user interface device via the wireless device address based on reading of the tag by the second reader and to establish a wireless connection between the surgical device and the user interface device.

[0020] In some embodiments of the above system, the surgical device can include means for determining blood volume data as a measure of blood in the surgical waste that is drawn under the influence of a vacuum from the vacuum source. The surgical device can be configured to transmit the blood volume data over a wireless connection. The user interface device can be configured to display the blood volume data on a display of the user interface device.

[0021] In some implementations of the above system, the first reader and the second reader may be optical sensors, and the tag may include a machine-readable optical code.

[0022] In some implementations of the above system, the first reader may include one of an optical sensor and an RFID interrogator, the second reader may include the other of the optical sensor and the RFID interrogator, and the tag may include a machine-readable optical code and an RFID tag. In some implementations, the first reader includes an RFID interrogator and the second reader includes an optical sensor. In some implementations, the first reader may not include the other of the optical sensor and the RFID interrogator, and the second reader may not include one of the optical sensor and the RFID interrogator, and the machine-readable optical code and the RFID tag may each indicate a unique identifier.

[0023] The advantages of the present disclosure will be readily appreciated and better understood by reference to the following detailed description when considered in conjunction with the accompanying drawings, in which: [Brief explanation of the drawings]

[0024] [Figure 1] FIG. 1 illustrates a medical system for use in an operating room according to the present disclosure, the system including a user interface device, a surgical device, and a cartridge configured to be removably received by the surgical device and to facilitate pairing between the user interface device and the surgical device. [Figure 2] FIG. 2 is a diagram showing an example based on the system of FIG. 1. [Figure 3] FIG. 3 is an enlarged view of the cartridge of FIG. 2. [Figure 4] FIG. 2 is a diagram showing another example based on the system of FIG. 1. [Figure 5] FIG. 2 shows a further example in accordance with the system of FIG. 1. [Figure 6] FIG. 6 is an alternative view of the cartridge of FIG. 5. [Figure 7]10 is a flowchart of a method for establishing a wireless connection between a surgical device and a user interface device in accordance with the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0025] Aspects of the present disclosure generally relate to an intuitive and improved pairing process for facilitating wireless data communication between devices in a surgical environment. A given surgical procedure may involve several surgical devices, each performing a different surgical task to support the procedure. For example, one exemplary surgical procedure may utilize an ultrasound tool device for treating tissue at a surgical site, a medical waste collection device for collecting medical waste from the site resulting from the treatment, and a surgical sponge management device for tracking surgical sponges used during the procedure. Each of these devices may be separately locatable within the operating room and may include a local user interface for providing operational information and accepting user input for the device. However, such a configuration is insufficient as a means of supporting a surgical procedure because it may be inconvenient or impractical in some cases for a surgeon to continuously track data from each device and provide user input to each device's local user interface while attending to a patient during a surgical procedure.

[0026] Accordingly, the present disclosure describes systems, methods, and computer program products that can function to merge the data output and user input functions of multiple surgical devices into a single access point, or user interface device, that can be easily relocated during a procedure for the convenience of the surgeon. One option for achieving this goal may be to integrate multiple surgical devices into a single unit or to connect the devices by wires or cables to transmit data. However, this configuration has the disadvantage of limiting the ability of devices to be separated and / or moved relative to each other for the convenience of the surgeon during a procedure and also creates a cramped surgical environment. Accordingly, provided herein are systems, methods, and computer products for establishing wireless communication between surgical devices that help overcome the shortcomings of wired systems and avoid potential drawbacks of wireless configurations, such as complex pairing processes, a lack of flexibility in swapping various surgical devices between multiple surgical environments, and limited-range proximity-based communication technologies, such as near-field communication (NFC).

[0027] FIG. 1 illustrates a surgical system 10 including a surgical device 12, a user interface device 14, and a cartridge 16. The cartridge 16 may include or form a functional component of the surgical device 12 that cooperates with the surgical device 12 to perform a surgical task associated with a surgical procedure. In some cases, the cartridge 16 may be configured to be removably received by the surgical device 12 to enable performance of the surgical task. The cartridge 16 may also be configured to facilitate establishing a reliable wireless connection between the surgical device 12 and the user interface device 14 in an intuitive manner. For example, the wireless connection may be established by placing the cartridge 16 in an operative position for cooperation with the surgical device 12 to perform a surgical task, thus limiting the number of steps that need to be performed by the surgeon to establish a connection when preparing the system 10 for a procedure. In some cases, the cartridge 16 may be a disposable, single-use component configured to cooperate with the surgical device 12 to perform a surgical task.

[0028] Once established, the wireless connection can enable the surgical device 12 to communicate data to the user interface device 14 for display to the surgeon. The wireless connection can also enable the user interface device 14 to receive user input commands for the surgical device 12 and communicate those commands to the surgical device 12 for execution. In some embodiments, the surgical device 12 can also communicate through the user interface device 14 with remote devices, such as devices accessible through the Internet.

[0029] The surgical device 12 may be configured to perform at least one surgical task associated with a surgical procedure. Non-limiting examples of such surgical tasks may include treating tissue at a surgical site, aspirating medical waste from the surgical site as a result of the procedure, and tracking sponges used in the procedure to avoid inadvertent placement at the surgical site.

[0030] The surgical device 12 may include a controller 18 configured to control the operation of the surgical device 12, including the implementation of the functions, features, and processes of the surgical device 12 described herein. The surgical device 12 may also include a wireless communication device 20 that communicates with the controller 18. The wireless communication device 20 may be configured to provide wireless data communication between the surgical device 12 and other devices and systems, such as via radio frequency signals. The wireless communication device 20 may incorporate relatively short-range communication technologies, such as Bluetooth®. In some examples, the wireless communication device 20 may not have relatively long-range communication capabilities, such as Wi-Fi® and cellular.

[0031] The surgical device 12 may also include one or more sensors 22 in communication with the controller 18. The sensors 22 may be configured to generate operational data indicative of use of the surgical device 12. The controller 18 may be configured to receive the operational data generated by the sensors 22 and, based thereon, govern (control) the operation of the surgical device 12. The controller 18 may also be configured to generate user data for output to the operator based on the operational data.

[0032] Also, in some cases, the surgical device 12 may include a local user interface (UI) 24 in operative communication with the controller 18. The local UI 24 may include one or more output devices, such as one or more of a display and / or speakers, for presenting information, such as operational data generated by the sensors 22, from the controller 18 to a user. The local UI 24 may also include one or more input devices, such as a touchscreen display, a mouse, a keyboard, and / or a microphone, for accepting user input. Thus, the surgeon may input commands to the controller 18 to govern the operation of the surgical device 12 via the local UI 24.

[0033] As previously described, the local UI 24 may be inconvenient or inadequate for relaying information to the surgeon regarding the operation of the surgical device 12 and for receiving user input to govern the operation of the surgical device 12. Therefore, according to aspects of the present disclosure, the surgical device 12 may be paired with the user interface device 14 to establish a wireless connection therebetween, thereby enabling the user interface device 14 to function as a remote UI for the surgical device 12. The user interface device 14 may then be located at the surgeon's convenience. In some cases, the user interface device 14 may also function as a surgical device configured to perform other surgical tasks related to the surgical procedure.

[0034] The user interface device 14 may include a controller 26 configured to control the operation of the user interface device 14, including the implementation of the functions, features, and processes of the user interface device 14 described herein. For example, the controller 26 may be configured to control the operation of the surgical device 12, such as based on user input received for the surgical device 12, to receive and process operational data related to the operation of the surgical device 12, and to integrate (aggregate) data from multiple surgical devices 12 paired with the user interface device 14. As one non-limiting example, the user interface device 14 may be paired with multiple blood loss measurement devices utilized during a procedure, and the controller 26 may be configured to compile blood loss data from each of such devices to provide a more accurate real-time analysis of blood loss during a surgical procedure.

[0035] The user interface device 14 may also include a display 28 and one or more input devices 30, each in electronic communication with the controller 26. The input device 30 may include a touchscreen integrated with the display 28. The input device 30 may also include a keyboard or keypad, a mouse or other pointing device, a microphone, or other input devices known in the art. The user interface device 14 may also include a wireless communication device 32 coupled to the controller 26. The wireless communication device 32 may complement the wireless communication device 20 of the surgical device 12 to enable a wireless connection to be established. For example, the wireless communication device 32 may incorporate a relatively short-range communication technology, such as Bluetooth®, for communication with similar technologies on the surgical device 12. The wireless communication device 32 may also include technologies that enable relatively long-range communication capabilities, such as Wi-Fi® and cellular.

[0036] The cartridge 16 may be configured to facilitate pairing of the wireless communication devices 20, 32 to enable unidirectional or bidirectional communication between the surgical device 12 and the user interface device 14. The cartridge 16 may also form an operating component of the surgical device 12 and, in that way, may be configured to enable the performance of a surgical task by the surgical device 12. The surgical device 12 may include a cartridge interface 34 for removably receiving the cartridge 16, such as to form one or more of a fluid, mechanical, or electrical connection with the cartridge 16, which may facilitate (facilitate / assist) the performance of a surgical task.

[0037] The cartridge 16 may include a tag 36 that contains data usable by the surgical device 12 and the user interface device 14 in the pairing process. For example, the tag 36 may indicate one or more of a type identifier 38 or a unique identifier 40. The type identifier 38 may generally indicate the type of cartridge 16 and may be embodied as a part number or model number assigned to all cartridges 16 of a given type. The unique identifier 40 may vary between different cartridges 16 of the same type and may be used by both the surgical device 12 and the user interface device 14 to establish a wireless connection between them.

[0038] The surgical device 12 and the user interface device 14 may each include means for reading the tag 36 data. For example, the user interface device 14 may include a reader 42, such as an RFID or optical reader, to read the tag 36 data when the cartridge 16 is brought into proximity with the reader 42. The surgical device 12 may include a corresponding reader 44. The reader 44 may be positioned relative to the cartridge interface 34 of the surgical device 12 such that the controller 18 can read the data from the tag 36 via the reader 44 when the cartridge 16 is coupled to the surgical device 12.

[0039] Tag 36 may include an RFID tag (e.g., RFID tags 126A (FIG. 3), 126B (FIG. 4), and 126C (FIG. 6)), such as RFID tags conforming to the ISO / IEC 18000, ISO / IEC 15693, or ISO / IEC 14443 standards or other similar protocols. Tag 36 may also use other radio-based communication protocols. At least one of readers 42, 44 (e.g., both readers 42, 44) may include an RFID interrogator arranged to communicate in the same protocol as tag 36. Additionally or alternatively, tag 36 may include optically encoded machine-readable data, such as a barcode (e.g., barcodes 128A (FIG. 3), 128B (FIG. 4), and 128C (FIG. 6)) or a QR code. In this case, at least one of readers 42, 44 (e.g., both readers 42, 44) may include an optical scanner arranged to scan the optical encoding of information. In one example, the tag 36 may include a combination of RFID and optical encoding, optionally each storing the same data (e.g., type identifier 38, unique identifier 40), and the readers 42, 44 may be of different types, with the surgical device 12 using one type of reader, RFID or optical, to read data from the tag 36 and the user interface device 14 using the other type of reader to read data from the tag 36. In a further example, the tag 36 may include a combination of RFID and optical encoding, optionally each storing different data (e.g., the optical encoding storing the type identifier 38 and the RFID storing the unique identifier 40, or vice versa), and at least one of the readers 42, 44 (e.g., both readers 42, 44) may include both an optical reader and an RFID reader to read data from the tag 36.

[0040] In some cases, the tag 36 may include a writable or rewritable data field, and the reader 42, 44, such as an RFID interrogator of the reader 44, may be configured to write or rewrite data in the writable or rewritable data field to indicate the use of the cartridge 16 to which the tag 36 is affixed. Once used to establish a wireless connection as described herein and / or to facilitate the performance of a surgical task, such as for a specified period of time as described herein, the cartridge 16 may be rendered inoperable by the written or rewritten data to establish a further wireless connection between the surgical device 12 and the user interface device 14 and / or to facilitate the performance of a further surgical task. Whether the cartridge 16 is subsequently used to establish a wireless connection as described herein and / or to facilitate the performance of a surgical task, the information written in this field may enable the controller 18 and / or the controller 26 to identify that the cartridge 16 has been used and / or is not suitable for further use during a surgical procedure. In response to such an identification, the controller 18 and / or the controller 26 may be configured to refuse to establish a wireless connection and / or facilitate the performance of a surgical task using the cartridge 16, and / or to provide a corresponding indicator to the user in the form of a warning (alert) or error message, such as on the local UI 24 and / or the display 28 of the user interface device 14.

[0041] Additionally or alternatively, controller 18 and / or controller 26 may be configured to upload data read from tag 36 of cartridge 16 to a used cartridge database in response to a given cartridge 16 being used to establish a wireless connection as described herein and / or to facilitate performance of a surgical task, such as for a specified period of time as described herein. Such a database may be maintained on one or more of surgical device 12, user interface device 14, or a remote server accessible through one or more networks, such as the Internet. Once cartridge 16 has been subsequently used in connection with establishing a wireless connection as described herein and / or facilitating performance of a surgical task, controller 18 and / or controller 26 may be configured to cross-check data read from tag 36 of cartridge 16 against a used cartridge database to determine whether tag 36 data is indicated as used by such database. If so, the controller 18 and / or the controller 26 may be configured to refuse to establish a wireless connection and / or facilitate the performance of a surgical task using the cartridge 16, and / or to provide a corresponding indicator to the user in the form of a warning or error message, such as on the local UI 24 and / or the display 28 of the user interface device 14.

[0042] In some cases, rather than being incorporated into the cartridge 16 configured to be removably received by the surgical device 12, the tag 36 may be incorporated into a component configured to work in cooperation with the surgical device 12 during operation but to be located external to the surgical device 12. By way of example, the tag 36 may be incorporated into a flow monitoring or other monitoring device that is external to the surgical device 12 but communicates information back to the surgical device 12, such as via a wired or relatively short-range wireless connection. In this case, the information provided in the tag 36 may still be utilized to facilitate pairing of the surgical device 12 and the user interface device 14, such as by placing the component including the tag 36 near the readers 42, 44 of each device 12, 14 before placing the component in an operational position to assist in the performance of a surgical task.

[0043] It is contemplated that a medical facility may have multiple surgical devices 12 and / or multiple user interface devices 14 that may be used in a variety of configurations. Pairing a particular surgical device 12 to a particular user interface device 14 may enable proper communication between the devices within a particular operating room. It is also possible that multiple surgical devices 12 and / or multiple user interface devices 14 may be utilized for a single surgical procedure in a single operating room. The pairing process allows the surgeon to arrange for and control communication between specific pairs or groups of surgical devices 12 and user interface devices 14. The surgical devices 12, user interface devices 14, and pairing process are described in the following paragraphs with reference to various exemplary alternatives, with like features retaining like reference numerals.

[0044] Figure 2 illustrates an exemplary embodiment consistent with the surgical system 10 illustrated in Figure 1. As shown in the illustrated example, the surgical device 12 may be embodied as a waste collection unit 12A, and the user interface device 14 may be embodied as a surgical sponge management device 14A.

[0045] The waste collection unit 12A may be configured to suction and collect waste material from a surgical site and may be configured to store the waste material until it is necessary or desired to remove and dispose of the waste material. The waste collection unit 12A may include a base 102 and a plurality of wheels 104 for moving the waste collection unit 12A along a floor surface within a medical facility. The waste collection unit 12A may also include at least one waste container 106 that defines a waste volume for collecting and storing the waste material. The waste collection unit 12A may further include a vacuum source or pump 110 (shown in phantom) supported on the base 102 and configured to apply suction to the waste container 106 through one or more vacuum lines. Suitable structures and operations of several subsystems of waste collection unit 12A are disclosed in commonly owned U.S. Patent Publication No. 2005 / 0171495, published August 4, 2005, International Publication No. WO 2007 / 070570, published June 21, 2007, and International Publication No. WO 2014 / 066337, published May 1, 2014, the entire contents of each of which are incorporated herein by reference.

[0046] The waste collection unit 12A may include at least one cartridge interface 34 embodied as a receiver 34A supported on the base 102. Each receiver 34A may define an opening 114 sized to removably receive at least a portion of a cartridge 16, which may be embodied as a manifold 16A, as shown in the illustrated example. When removably inserted into the receiver 34A, a suction path may be established through the manifold 16A from one or more suction tubes 118 to each waste container 106. During a procedure, a vacuum generated by a vacuum pump 110 may be drawn into the suction tubes 118, and waste material at the surgical site may be sucked through the manifold 16A, through the suction outlets of the receiver 34A, and into the waste container 106.

[0047] The waste collection unit 12A may also include a controller 18A, which may correspond to the controller 18 described above with reference to FIG. 1. The controller 18A may provide overall control of the waste collection unit 12A. For example, the controller 18A may be in communication with the vacuum pump 110 and configured to regulate the on / off operation of the vacuum pump 110. The controller 18A may also be configured to regulate vacuum flow through the manifold 16A. The controller 18A may further include or be in communication with a wireless communication device 20A of the waste collection unit 12A. The wireless communication device 20A may correspond to the wireless communication device 20 discussed above with reference to FIG. 1.

[0048] The waste collection unit 12A may also include one or more sensors 22A in communication with the controller 18A and configured to generate operational data regarding use of the waste collection unit 12A. The sensors 22A may correspond to the sensors 22 described above with reference to FIG. 1. For example, without limitation, the sensors 22A may include a fluid measurement subsystem configured to measure the volume of waste material received in the waste container 106. Additionally or alternatively, the sensors 22A may include one or more flow sensors for measuring the flow rate of a substance passing through the manifold 16A. Additionally or alternatively, the sensors 22A may include one or more blood concentration sensors for measuring the concentration of blood in the waste material passing through the manifold 16A. An exemplary measurement or monitoring device is disclosed in commonly owned International Application No. PCT / US2021 / 058891, filed November 11, 2022, the entire contents of which are incorporated herein by reference. The data generated by the sensor 22A can provide the operator with valuable information regarding the operation of the waste collection unit 12A and the status of the surgical procedure. As one example, the controller 18A can be configured to determine the quantity of blood loss (QBL) for the surgical procedure based on the data generated by the sensor 22A.

[0049] In some cases, the waste collection unit 12A may also include a local UI 24A, which may correspond to the local UI 24 discussed above with reference to FIG. 1. The local UI 24A may be in operative communication with the controller 18A and may be configured to display information regarding the operation of the waste collection unit 12A based on data generated by the sensor 22A. The local UI 24A may also be configured to provide audible tones to a user and to accept user input. For example, the local UI 24A may include a touchscreen display. Thus, an operator may be able to input commands to control the waste collection unit 12A based on pressing button images presented on the touchscreen display of the local UI 24A.

[0050] 2 and 3, the waste collection unit 12A can additionally include a reader 44A located near each receptacle 34A to enable the controller 18A of the waste collection unit 12A to communicate with the tag 36A located on or within the manifold 16A when the manifold 16A is inserted into the receptacle 34A. In some cases, the controller 18A can be configured to prevent operation of the vacuum pump 110 until the manifold 16A is inserted into the receptacle 34A and authenticated by the controller 18A, such as based on data read from the tag 36A via the reader 44A. Thus, the controller 18A can act as a master override that prohibits the vacuum pump 110 from being activated unless the appropriate manifold 16A is attached to the waste collection unit 12A. The controller 18A can be configured to prevent operation of the vacuum pump 110 if a user attempts to activate the vacuum pump 110 without the manifold 16A being inserted and authenticated. The controller 18A may also cause an alert message to be presented on the local UI 24A and / or the display 28A of the user interface device 14, such as via an established wireless connection as described in more detail below.

[0051] The tag 36A may be configured to be detected by the reader 44A when the manifold 16A is in its fully inserted, operational position within the receptacle 34A. For example, the reader 44A may be positioned relative to the receptacle 34A such that the tag 36A is detectable by the reader 44A only when the manifold 16A is in its fully inserted, operational position within the receptacle 34A (e.g., in fluid communication with the corresponding waste container 106). In this way, if an item, such as an incompatible (mismatched) manifold, cannot be inserted into the fully inserted, operational position, data communication cannot be established between the item's tag and the reader 44A, and the controller 18A can therefore prevent operation of the waste collection unit 12A.

[0052] Various other features of manifold 16A and waste collection unit 12A are contemplated, for which the disclosures of WO 2019 / 222655, published November 21, 2019, and U.S. Pat. No. 10,471,188, issued November 12, 2019, are each incorporated herein by reference in their entirety.

[0053] Referring again to FIG. 2 , surgical sponge management device 14A may include a stand 132 and an electronic subsystem 134. Stand 132 may include a base 138, which may be wheeled for moving surgical sponge management device 14A within a medical facility. Electronic subsystem 134 may include controller 26A, display 28A, input device 30A, wireless communication device 32A, and reader 42A, which may correspond to controller 26, display 28, input device 30, wireless communication device 32, and reader 42, respectively, discussed above with reference to FIG. 1 . As shown in the illustrated example, display 28A may be incorporated into a tablet 139 that is removably coupleable to stand 132. While the illustrated example shows controller 26A and wireless communication device 32 as separate from tablet 139, in other embodiments, these components may be incorporated into tablet 139 with display 28A, which may correspondingly also be removably coupleable to stand 132. Similarly, although the illustrated example shows reader 42A as being incorporated into tablet 139 having display 28A, in other embodiments reader 42A may be separate from display 28A and tablet 139 and / or may be integrated into stand 132.

[0054] The controller 26A may be configured to implement the functions, features, and processes of the surgical sponge management device 14A described herein. For example, in addition to facilitating pairing with and functioning as a user interface device 14 for one or more surgical devices 12, such as the medical waste collection unit 12A, the controller 26A may be configured to manage surgical sponge use during a surgical procedure to prevent placement of the surgical sponge within the patient.

[0055] To that end, surgical sponge management device 14A can include a data reader 140 removably coupleable to stand 132 and in data communication with controller 26A. Data reader 140 can be configured to read unique identification information from a tag associated with a surgical sponge and transfer such information to controller 26A. In an exemplary embodiment, data reader 140 can be an RFID reader configured to detect an RFID tag associated with a surgical sponge, such as those described in commonly owned International Publication No. WO 2021 / 041795, published March 4, 2021, and commonly owned International Publication No. WO 2021 / 097197, published May 20, 2021, each of which is incorporated by reference herein in its entirety. Exemplary tags other than RFID tags are disclosed in commonly owned International Publication No. WO 2017 / 112051, published June 29, 2017, which is incorporated by reference herein in its entirety.

[0056] Controller 26A may be configured to count surgical sponges during a surgical procedure by reading tag information from the sponges when placed near data reader 140 and increment a counter of the number of surgical sponges used during the surgical procedure. The counter may be displayed on display 28A. Additionally, controller 26A may be configured to add the dry weight of each counted sponge to the dry weight of a surgical sponge previously counted as used.

[0057] Either during or after a surgical procedure, surgical sponges, both used and unused, can be identified or counted and removed. To that end, the tag on each of the surgical sponges can be repositioned to be read by data reader 140. Controller 26A can be configured to responsively decrement the counter accordingly (e.g., subtract one from its previous count) and show a count on display 28A indicating the number of surgical sponges remaining to be counted. After confirming on display 28A that a surgical sponge has been counted and removed, the sponge can be placed in a sponge sorter pocket located on arm 142 of surgical sponge management device 14A, which can be coupled to weight sensor 144 configured to generate data indicative of the sponge sorter's weight. Weight sensor 144 can be communicatively coupled to controller 26A, which can be configured to receive the generated weight data and calculate and display the patient's estimated blood loss based on the weight indicated by the weight data and the previously determined dry weight of the counted sponges. Suitable structures and operations of several subsystems of the surgical sponge management device 14A are disclosed in commonly owned International Patent Application No. PCT / US2022 / 017664, filed February 24, 2022, and published as International Publication No. _, the entire contents of which are incorporated herein by reference.

[0058] The waste collection unit 12A and the surgical sponge management device 14A may be separately positionable in the operating room. In some situations, the waste collection unit 12A and the surgical sponge management device 14A may be located at distances that may preclude the use of near-field communication or other proximity-based communication technologies to establish wireless communication between them. Therefore, to establish a wireless communication path that provides reliable communication between the waste collection unit 12A and the surgical sponge management device 14A during a surgical procedure, the waste collection unit 12A and the surgical sponge management device 14A may undergo a pairing process before the start of a surgical procedure. Once the wireless connection is established, the waste collection unit 12A may be able to communicate data to the surgical sponge management device 14A for display to the surgeon. In some embodiments, the surgical sponge management device 14A may also be configured to receive user input commands for the waste collection unit 12A and communicate those commands to the waste collection unit 12A via the wireless connection. In some further embodiments, the waste collection unit 12A can also send and receive data and commands through the surgical sponge management device 14A from remote devices or systems, such as remote devices or systems accessible via the Internet.

[0059] The waste collection unit 12A may be configured to be in one-way or two-way wireless electronic communication with a user interface device 14, such as a surgical sponge management device 14A, using a manifold 16A. More specifically, prior to a surgical procedure, the manifold 16A may be brought into proximity with a reader 42A of the surgical sponge management device 14A, which may be configured to read data from a tag 36A. The manifold 16A may then be inserted into a receptacle 34A of the waste collection unit 12A, and the controller 18A may responsively be configured to read data from the tag 36A via the reader 44A. The controllers 18A, 26A may then be configured to complete a pairing process that establishes a wireless communication link between the wireless communication device 20A of the waste collection unit 12A and the wireless communication device 32A of the surgical sponge management device 14A. This process is described in more detail below.

[0060] As previously described, tag 36A can store data indicative of type identifier 38 and / or unique identifier 40. Referring again to Figure 3, such tag data may be stored in RFID tag 126A of tag 36A, encoded in barcode 128A or other optical, machine-readable data encoding of tag 36A, or both. In some cases, barcode 128A may encode one of the above data, type identifier 38 or unique identifier 40, and RFID tag 126A may store the other of these data.

[0061] Thus, the tag 36A and the readers 42A, 44A can each use optical and / or radio-based technology. For example, the tag 36A can include an RFID tag 126A, and the readers 42A, 44A can each include an RFID interrogator. Additionally or alternatively, the tag 36A can include a barcode 128A or other optical, machine-readable data encoding, such as a QR code, and the readers 42A, 44A can each include an optical scanner. In some cases, the reader 42A can use optical or radio-based technology, and the reader 44A can use the other of the optical or radio-based technology. In this case, the tag 36A can include both an RFID tag 126A and a barcode 128A or other optical, machine-readable data encoding, each storing data to be read by the corresponding reader 42A, 44A to establish a wireless connection as described herein.

[0062] In some cases, tag 36A may include a writable or rewritable data field, such as when including RFID tag 126A, and reader 42A, 44A, such as the RFID interrogator of reader 44A, may be configured to write or rewrite data in the writable or rewritable data field to indicate use of manifold 16A to which tag 36A is attached. Once used to establish a wireless connection as described herein and / or to facilitate performance of a surgical task, such as for a specified period of time as described herein, manifold 16A may be rendered inoperable by the written or rewritten data to establish a further wireless connection between waste collection unit 12A and user interface device 14 (e.g., surgical sponge management device 14A) and / or to facilitate further performance of a surgical task. Whether manifold 16A is subsequently used to establish a wireless connection and / or to facilitate the performance of a surgical task as described herein, information written in this field may cause controller 18A and / or controller 26A to identify that manifold 16A has been used and / or is not suitable for further use during a surgical procedure. In response to such identification, controller 18A and / or controller 26A may be configured to refuse to use manifold 16A to establish a wireless connection and / or to facilitate the performance of a surgical task, and / or to provide a corresponding indicator to the user in the form of a warning or error message, such as on local UI 24A and / or display 28A of surgical sponge management device 14A.

[0063] Additionally or alternatively, controller 18A and / or controller 26A may be configured to upload data read from tag 36A of manifold 16A to a used cartridge database in response to a given manifold 16A being used to establish a wireless connection as described herein and / or to facilitate performance of a surgical task, such as for a specified period of time as described herein. Such a database may be maintained on one or more of waste collection unit 12A, surgical sponge management device 14A, or a remote server accessible through one or more networks, such as the Internet. Even if manifold 16A is subsequently used in connection with establishing a wireless connection as described herein and / or facilitating performance of a surgical task, controller 18A and / or controller 26A may be configured to cross-check data read from tag 36A of manifold 16A against a used cartridge database to determine whether tag 36A data is indicated as used by such database. If so, controller 18A and / or controller 26A may be configured to refuse to establish a wireless connection using manifold 16A and / or facilitate the performance of a surgical task, and / or to provide a corresponding indicator to the user in the form of a warning or error message, such as on local UI 24A and / or display 28A of surgical sponge management device 14A.

[0064] FIG. 4 illustrates a further exemplary embodiment consistent with the surgical system 10 illustrated in FIG. 1. As shown in the illustrated example, the user interface device 14 may be embodied as a surgical sponge management device 14A similar to that described above, one surgical device 12 may be embodied as a waste collection unit 12A similar to that described above, and an additional surgical device 12 may be embodied as a flow monitoring device 12B. The flow monitoring device 12B may generally be configured to monitor the flow of waste material between the surgical site and the waste collection unit 12A. In other words, the flow monitoring device 12B may be configured to perform one or more monitoring functions (e.g., QBL) of the waste collection unit 12A described above, external to the waste collection unit 12A. In some cases, the monitoring functions performed by the flow monitoring device 12B may be omitted from the waste collection unit 12A.

[0065] As shown in the illustrated example, the flow monitoring device 12B may include a cartridge interface 34 embodied as a slot 34B sized to receive a cartridge 16, embodied as a cassette 16B. The cassette 16B may be configured to form one or more of a fluidic, mechanical, or electrical connection with the flow monitoring device 12B when inserted into the slot 34B. Additionally, the cassette 16B may include or form functional components of the flow monitoring device 12B that facilitate performance of a surgical task, such as via a fluidic, mechanical, or electrical connection.

[0066] For example, cassette 16B may be configured to define or include a portion of an aspiration path extending from the surgical site through one or more aspiration tubes 118 and one or more manifolds 16A inserted into waste collection unit 12A, such that material aspirated from the surgical site via waste collection unit 12A passes through cassette 16B. Cassette 16B may also be configured to form a fluid connection with flow monitoring device 12B, such that material passing through cassette 16B also passes through flow monitoring device 12B.

[0067] The flow monitoring device 12B may also include a controller 18B, which may correspond to the controller 18 discussed above with reference to FIG. 1 . The controller 18B may provide overall control of the flow monitoring device 12B. For example, the controller 18B may be configured to analyze the flow of material through the suction line 118 due to the vacuum generated by the waste collection unit 12A before the material reaches the manifold 16A and to generate blood concentration data from the analysis of the material flow, such as blood concentration data representative of the concentration of blood present in the material flow. The controller 18B may further include or communicate with a wireless communication device 20B of the flow monitoring device 12B. The wireless communication device 20B may correspond to the wireless communication device 20 discussed above with reference to FIG. 1 .

[0068] Flow monitoring device 12B may also include one or more sensors 22B in communication with controller 18B, configured to generate operational data related to the use of flow monitoring device 12B, such as to facilitate (facilitate / assist) the determination of blood concentration data as described above. Sensor 22B may correspond to sensor 22 described above with reference to FIG. 1. For example, without limitation, sensor 22B may include a fluid measurement subsystem arranged to measure the volume of waste material aspirated through cassette 16B. Additionally or alternatively, sensor 22B may include one or more flow sensors for measuring the flow rate of material passing through cassette 16B. Additionally or alternatively, sensor 22B may include one or more blood concentration sensors for measuring the concentration of blood in the waste material passing through cassette 16B. An exemplary measurement or monitoring device is disclosed in commonly owned International Application No. PCT / US2021 / 058891, filed November 11, 2021, the entire contents of which are incorporated herein by reference. The data generated by the sensor 22B can provide the surgeon with valuable information regarding the operation of the waste collection unit 12A and its status during a surgical procedure.

[0069] In some cases, the flow monitoring device 12B may also include a local UI 24B, which may correspond to the local UI 24 discussed above with reference to FIG. 1. The local UI 24B may be in operative communication with the controller 18B and may be configured to display information regarding the operation of the flow monitoring device 12B based on data generated by the sensor 22B. The local UI 24B may also be configured to provide audible tones to the user and to accept user input. For example, the local UI 24B may include a touchscreen display. Thus, the operator may be able to input commands to control the flow monitoring device 12B based on pressing button images presented on the touchscreen display of the local UI 24B.

[0070] The flow monitoring device 12B may additionally include a reader 44B located near the slot 34B to enable the controller 18B of the flow monitoring device 12B to communicate with a tag 36B located on or in the cassette 16B when the cassette 16B is inserted into the slot 34B. In some cases, the controller 18B may be configured to prevent suction from the waste collection unit 12A from reaching the surgical site until the cassette 16B is inserted into the slot 34B and authenticated by the controller 18B, such as based on data read from the tag 36B via the reader 44B. By way of example, the flow monitoring device 12B or the cassette 16B may include a valve operable by the controller 18B in the suction path established between the tube 118 and the waste collection unit 12A when the cassette 16B is inserted into the slot 34B and coupled to the tube 118 and the waste collection unit 12A. Controller 18B may be configured to maintain the valve closed when cassette 16B is not inserted and authenticated, thereby preventing suction generated by waste collection unit 12A from reaching the surgical site. Controller 18B may be configured to open the valve in response to cassette 16B being inserted and authenticated, thereby allowing suction to flow through cassette 16B and flow monitoring device 12B.

[0071] The tag 36B can be configured to be detected by the reader 44B when the cassette 16B is in the fully inserted operative position within the slot 34B. For example, the reader 44B can be positioned relative to the slot 34B such that the tag 36B is detectable by the reader 44B only when the cassette 16B is in the fully inserted operative position within the slot 34B (e.g., in fluid communication with the flow monitoring device 12B). In this way, if an item, such as an incompatible (mismatched) cassette, cannot be placed in the fully inserted operative position, data communication cannot be established between the item's tag and the reader 44B, and thus the controller 18B can prevent suction from being applied to the surgical site from the waste collection unit 12A.

[0072] Similar to the waste collection unit 12A, the flow monitoring device 12B and the surgical sponge management device 14A may be separately positionable in the operating room. In some circumstances, the flow monitoring device 12B and the surgical sponge management device 14A may be located at distances that may preclude the use of near-field communication or other proximity-based communication technologies to establish wireless communication between them. Therefore, to establish a wireless communication path that provides reliable communication between the flow monitoring device 12B and the surgical sponge management device 14A during the surgical procedure, the flow monitoring device 12B and the surgical sponge management device 14A may undergo a pairing process prior to the start of the surgical procedure. Once the wireless connection is established, the flow monitoring device 12B may be able to communicate data to the surgical sponge management device 14A for display to the surgeon. In some embodiments, the surgical sponge management device 14A may also be configured to receive user input commands for the flow monitoring device 12B and communicate those commands to the flow monitoring device 12B via the wireless connection. In some further embodiments, the flow monitoring device 12B can also send and receive data and commands through the surgical sponge management device 14A from remote devices or systems, such as remote devices or systems accessible via the Internet.

[0073] The flow monitoring device 12B may be configured to be in one-way or two-way wireless electronic communication with a user interface device 14, such as a surgical sponge management device 14A, using a cassette 16B. More specifically, prior to a surgical procedure, the cassette 16B may be brought into proximity with a reader 42A of the surgical sponge management device 14A, which may be configured to read data from a tag 36B. The cassette 16B may then be inserted into a slot 34B of the flow monitoring device 12B, and the controller 18B may be configured to responsively read data from the tag 36B via the reader 44B. The controllers 18B, 26A may then be configured to complete a pairing process that establishes a wireless communication link between the wireless communication device 20B of the flow monitoring device 12B and the wireless communication device 32A of the surgical sponge management device 14A. This process is described in more detail below.

[0074] As previously described, the tag 36B can store data indicative of the type identifier 38 and / or the unique identifier 40. Such tag 36B data may be stored in the RFID tag 126B of the tag 36B, may be encoded in the barcode 128B or other optical, machine-readable data encoding of the tag 36B, or both. In some cases, the barcode 128B may encode one of the above data, the type identifier 38 or the unique identifier 40, and the RFID tag 126B may store the other of these data.

[0075] Thus, tag 36B and readers 42A, 44B can each use optical and / or radio-based technology. For example, tag 36B can include RFID tag 126B, and readers 42A, 44B can each include an RFID interrogator. Additionally or alternatively, tag 36B can include barcode 128B or other optical, machine-readable data encoding, such as a QR code, and readers 42A, 44B can each include an optical scanner. In some cases, reader 42A can use optical or radio-based technology, and reader 44B can use the other of the optical or radio-based technology. In this case, tag 36B can include both RFID tag 126A and barcode 128B or other optical, machine-readable data encoding, each storing data to be read by the corresponding reader 42A, 44B to establish a wireless connection as described herein.

[0076] In some cases, tag 36B may include a writable or rewritable data field, such as when tag 36B includes RFID tag 126B, and reader 42A, 44B, such as an RFID interrogator of reader 44B, may be configured to write or rewrite data in the writable or rewritable data field to indicate use of cassette 16B to which tag 36B is affixed. Once used to establish a wireless connection as described herein and / or to facilitate performance of a surgical task, such as for a specified period of time as described herein, cassette 16B may be rendered inoperable by the written or rewritten data to establish a further wireless connection between flow monitoring device 12B and user interface device 14 (e.g., surgical sponge management device 14A) and / or to facilitate further performance of a surgical task. Whether cassette 16B is subsequently used to establish a wireless connection and / or to facilitate the performance of a surgical task as described herein, the information written in this field may cause controller 18B and / or controller 26A to identify that cassette 16B has been used and / or is not suitable for further use during a surgical procedure. In response to such identification, controller 18B and / or controller 26A may be configured to refuse to use cassette 16B to establish a wireless connection and / or to facilitate the performance of a surgical task, and / or to provide a corresponding indicator to the user, such as in the form of a warning or error message, on local UI 24B and / or display 28A of surgical sponge management device 14A.

[0077] Additionally or alternatively, controller 18B and / or controller 26A may be configured to upload data read from tag 36B of cassette 16B to a used cartridge database in response to a given cassette 16B being used to establish a wireless connection as described herein and / or to facilitate performance of a surgical task, such as for a specified period of time as described herein. Such a database may be maintained on one or more of flow monitoring device 12B, surgical sponge management device 14A, or a remote server accessible through one or more networks, such as the Internet. Even if cassette 16B is subsequently used in connection with establishing a wireless connection as described herein and / or facilitating performance of a surgical task, controller 18B and / or controller 26A may be configured to cross-check data read from tag 36B of cassette 16B against a used cartridge database to determine whether tag 36B data is indicated as used by such database. If so, controller 18B and / or controller 26A may be configured to refuse to establish a wireless connection and / or facilitate the performance of a surgical task using cassette 16B, and / or to provide a corresponding indicator to the user in the form of a warning or error message, such as on local UI 24B and / or display 28A of surgical sponge management device 14A.

[0078] In some cases, the flow monitoring device 12B may be configured to communicate with the user interface device 14 via a wireless connection formed between the waste collection unit 12A and the user interface device 14 using a manifold 16A as described herein. Alternatively, the waste collection unit 12A may be configured to communicate with the user interface device 14 via a wireless connection formed between the flow monitoring device 12B and the user interface device 14 using a cassette 16B as described herein. For either purpose, the flow monitoring device 12B may be communicatively coupled to the waste collection unit 12A, such as via a data communication cable extending therebetween. As one example, such a data communication cable may be integrated with a fluid conduit connecting the cassette 16B to the manifold 16A and may function to connect the controller 18B of the flow monitoring device 12B with the controller 18A of the waste collection unit 12A. Thus, in addition to forming a fluid connection, cassette 16B may be configured to form an electrical connection with flow monitoring device 12B when inserted into slot 34B, and / or manifold 16A may be configured to form an electrical connection with waste collection unit 12A when inserted into receptacle 34A.

[0079] FIG. 5 illustrates another exemplary embodiment consistent with the surgical system 10 illustrated in FIG. 1. As shown in the illustrated example, the surgical device 12 may be embodied as an irrigation device, or more specifically, as an ultrasonic suction and irrigation device 12C, and the user interface device 14 may be embodied as the surgical sponge management device 14A described above. The ultrasonic suction and irrigation device 12C may be used to resect patient tissue, introduce fluids into the surgical site, and aspirate fluids and tissue from the surgical site during a surgical procedure. The introduction of irrigation fluid may assist the surgical procedure, such as by reducing heating of the surgical instruments and tissue near the surgical site.

[0080] The ultrasonic aspiration and irrigation device 12C may include a control console 202 and an ultrasonic instrument 204. The control console 202 may be configured to generate and provide an AC drive signal, such as via an integrated power supply 206, to the ultrasonic instrument 204, or more specifically, to an ultrasonic transducer 208 of the ultrasonic instrument 204. In response to receiving the AC drive signal, the ultrasonic transducer 208 may extend or retract, generating corresponding vibrations in a tip 210 coupled to the ultrasonic transducer 208. The vibrating tip 210 may then be placed against tissue of a patient at a target site to cut or ablate the tissue.

[0081] To provide the above-described irrigation and aspiration at the surgical site, the control console 202 can also include a cartridge interface 34 embodied as a slot 34C sized to receive a cartridge 16 embodied as a cassette 16C. The cassette 16C can be configured to form one or more of a fluidic, mechanical, or electrical connection with the control console 202 when inserted into the slot 34C. The cassette 16C can also include functional components of the ultrasonic aspiration and irrigation device 12C that facilitate performance of a surgical task, such as via a fluidic, mechanical, or electrical connection.

[0082] For example, cassette 16C may define or include a portion of an irrigation pathway for supplying fluid thereto, extending from irrigation fluid supply 212 through cassette 16C and then through ultrasonic instrument 204 to a distal region of tip 210. Upon insertion of cassette 16C into slot 34C, a portion of the irrigation pathway defined by or included in cassette 16C (e.g., pump tubing 213 (FIG. 6)) may engage with a peristaltic pump 214 internal to control console 202. Pump 214 may then be operated to propel irrigation fluid from fluid supply 212 through the irrigation pathway to a distal region of tip 210 for introducing the irrigation fluid to the surgical site.

[0083] Cassette 16C can also define a portion of an aspiration pathway extending from a distal region of tip 210, through cassette 16C, and to waste canister 216. More specifically, upon insertion of cassette 16C into slot 34C, an isolated pathway can be formed through cassette 16C between vacuum source 218 internal to control console 202 and waste canister 216. Vacuum source 218 can then be operated to apply suction to the aspiration pathway through the isolated pathway, aspirating fluids and other materials from the surgical site into waste canister 216.

[0084] The control console 202 may include a controller 18C configured to implement the functions, features, and processes of the control console 202 described herein. For example, the controller 18C may be coupled to and configured to govern the operation of the power source 206, the pump 214, and the vacuum source 218 during operation of the ultrasonic aspiration and irrigation device 12C. The controller 18C may also be in communication with a wireless communication device 20C and one or more sensors 22C. The sensors 22C may be configured to generate operational data regarding the operation of the ultrasonic aspiration and irrigation device 12C and, based on the received data, to provide information and feedback to the operator, such as on a display 28 of the remote user interface device 14 (e.g., the surgical sponge management device 14A) by communicating the information and feedback to the user interface device 14 via a wireless connection established as described in more detail below. For example, and without limitation, sensor 22C may include a voltage sensor for measuring the voltage of the AC drive signal supplied to ultrasonic instrument 204, a current sensor for measuring the current of the AC drive signal supplied to ultrasonic instrument 204, one or more flow sensors for measuring the flow rate of irrigation fluid and / or waste streams through cassette 16C, and / or one or more volume sensors for measuring the total volume of irrigation fluid consumed and / or waste collected during a surgical procedure.

[0085] Also, in some cases, cassette 16C may include at least two electrical contacts 220 with electrical conductors 222 extending therebetween (FIG. 6). Upon insertion of cassette 16C into slot 34C, electrical contacts 220 may contact corresponding contacts on control console 202, thereby completing a circuit that enables control console 202 to operate. As one example, insertion of cassette 16C into slot 34C may complete a circuit that electrically couples controller 18C to other components of control console 202 (e.g., reader 44C, sensor 22C, wireless communication device 20C, power supply 206, pump 214, vacuum source 218) to enable controller 18C to communicate with and / or regulate them.

[0086] In some cases, the ultrasonic aspiration and irrigation device 12C may also include a local UI 24C in operative communication with the controller 18A, which may be configured to display information regarding the operation of the ultrasonic aspiration and irrigation device 12C based on data generated by the sensor 22C. The local UI 24C may also be configured to provide audible tones to the user and to accept user input. For example, the local UI 24C may be a touchscreen display. Thus, the operator may be able to input commands to control the ultrasonic aspiration and irrigation device 12C based on pressing button images presented on the local UI 24C.

[0087] Various other features of cassette 16C and ultrasonic aspiration and irrigation device 12C are contemplated, for which the disclosures of commonly owned WO 2015 / 021216, published February 12, 2015, and WO 2020 / 068823, published April 2, 2020, are each incorporated herein by reference in their entirety.

[0088] 5 and 6, the control console 202 of the ultrasonic aspiration and irrigation device 12C may include a reader 44C located near the slot 34C to enable the controller 18C of the ultrasonic aspiration and irrigation device 12C to communicate with a tag 36C located on or within the cassette 16C when the cassette 16C is inserted into the slot 34C. In some cases, the controller 18C may be configured to prevent operation of the ultrasonic aspiration and irrigation device 12C, or more specifically, operation of the ultrasonic instrument 204, until the cassette 16C is inserted and authenticated by the controller 18C, such as based on data read from the tag 36C via the reader 44C. Thus, the controller 18C may act as a master override that prevents the ultrasonic instrument 204 from being operated unless the appropriate cassette 16C is attached to the ultrasonic aspiration and irrigation device 12C. The controller 18C may be configured to prevent operation of the ultrasonic instrument 204 if a user attempts to operate the ultrasonic instrument 204 without the cassette 16C being inserted and authenticated. The controller 18C may also cause a warning message to be presented on the local UI 24C and / or the display 28 of the user interface device 14, such as via a wireless connection as described in more detail below.

[0089] The tag 36C can be configured to be detected by the reader 44C when the cassette 16C is in its fully inserted, operational position in the slot 34C. For example, the reader 44C can be positioned relative to the slot 34C such that the tag 36C is detectable only when the cassette 16C is in its fully inserted, operational position in the slot 34C (e.g., in fluid communication with the pump 214 and vacuum source 218). Thus, if an item, such as an incompatible (mismatched) cassette, cannot be inserted into the fully inserted, operational position, data communication cannot be established between the item's tag and the reader 44C, and the controller 18C can therefore prevent operation of the ultrasonic instrument 204.

[0090] The ultrasonic aspiration and irrigation device 12C can be configured to be in one-way or two-way wireless electronic communication with a user interface device 14, such as a surgical sponge management device 14A, using a cassette 16C. More specifically, prior to a surgical procedure, the cassette 16C can be brought into proximity with a reader 42A of the surgical sponge management device 14A, which can be configured to read data from a tag 36C. The cassette 16C can then be inserted into a slot 34C of the ultrasonic aspiration and irrigation device 12C, and the controller 18C can be configured to responsively read data from the tag 36C via the reader 44C. The controllers 18C, 26A can then be configured to complete a pairing process that establishes a wireless communication link between the wireless communication device 20C of the ultrasonic aspiration and irrigation device 12C and the wireless communication device 32A of the surgical sponge management device 14A. This process is described in more detail below.

[0091] As previously described, tag 36C can store data indicative of type identifier 38 and / or unique identifier 40. Such tag data may be stored in RFID tag 126C of tag 36C, encoded in barcode 128C or other optical, machine-readable data encoding of tag 36C, or both. In some cases, barcode 128C may encode one of the above data, type identifier 38 or unique identifier 40, and RFID tag 126C may store the other of these data.

[0092] Thus, tag 36C and readers 42A, 44C can each use optical and / or radio-based technology. For example, tag 36C can include an RFID tag 126C, and readers 42A, 44C can each include an RFID interrogator. Additionally or alternatively, tag 36C can include a barcode 128C or other optical, machine-readable data encoding, such as a QR code, and readers 42A, 44C can each include an optical scanner. In some cases, reader 42A can use optical or radio-based technology, and reader 44C can use the other of the optical or radio-based technology. In this case, tag 36C can include both an RFID tag 126C and a barcode 128C or other optical, machine-readable data encoding, each storing data for reading by a corresponding reader 42A, 44C to establish a wireless connection as described herein.

[0093] In some cases, tag 36C may include a writable or rewritable data field, such as when tag 36C includes RFID tag 126C, and reader 42A, 44C, such as an RFID interrogator of reader 44C, may be configured to write or rewrite data in the writable or rewritable data field to indicate use of cassette 16C to which tag 36C is affixed. Once used to establish a wireless connection as described herein and / or to facilitate performance of a surgical task, such as for a specified period of time as described herein, cassette 16C may be rendered inoperable by the written or rewritten data to establish a further wireless connection between ultrasonic aspiration and irrigation device 12C and user interface device 14 (e.g., surgical sponge management device 14A) and / or to facilitate further performance of a surgical task. Whether cassette 16C is subsequently used to establish a wireless connection and / or to facilitate the performance of a surgical task as described herein, the information written in this field may cause controller 18C and / or controller 26C to identify that cassette 16C has been used and / or is not suitable for further use during a surgical procedure. In response to such identification, controller 18C and / or controller 26A may be configured to refuse to use cassette 16C to establish a wireless connection and / or to facilitate the performance of a surgical task, and / or to provide a corresponding indicator to the user, such as in the form of a warning or error message, on local UI 24B and / or display 28A of surgical sponge management device 14A.

[0094] Additionally or alternatively, controller 18C and / or controller 26A may be configured to upload data read from tag 36C of cassette 16C to a used cartridge database in response to a given cassette 16C being used to establish a wireless connection as described herein and / or to facilitate performance of a surgical task, such as for a specified period of time as described herein. Such a database may be maintained on one or more of ultrasound aspiration and irrigation device 12C, surgical sponge management device 14A, or a remote server accessible through one or more networks, such as the Internet. Even if cassette 16C is subsequently used in connection with establishing a wireless connection as described herein and / or facilitating performance of a surgical task, controller 18C and / or controller 26A may be configured to cross-check data read from tag 36C of cassette 16C against a used cartridge database to determine whether tag 36C data is indicated as used by such database. If so, controller 18C and / or controller 26A may be configured to refuse to establish a wireless connection and / or facilitate the performance of a surgical task using cassette 16C, and / or to provide a corresponding indicator to the user in the form of a warning or error message, such as on local UI 24C and / or display 28A of surgical sponge management device 14A.

[0095] It will be appreciated that multiple surgical devices 12 can be wirelessly connected to the same user interface device 14 simultaneously using the procedures described herein. For example, referring to the example above, a surgeon can pair a waste collection unit 12A with a surgical sponge management device 14A via a manifold 16A as described herein, and then subsequently pair an ultrasonic aspiration and irrigation device 12C with the surgical sponge management device 14A via a cassette 16C as described herein. In this manner, the user interface device 14 can serve as a user interface for each surgical device 12 via its respective wireless connection and can further integrate data from multiple surgical devices 12 to provide the surgeon with an overall picture of the status of the surgical procedure.

[0096] 7 illustrates a method 350 for pairing a surgical device 12 with a user interface device 14 in an operating room to establish a wireless connection. At block 352, a pairing tag 36 may be placed near a reader 42 of the user interface device 14. As described above, the tag 36 may be integrated with a cartridge 16 configured to be received by the surgical device 12, which forms a functional component of the surgical device 12 (e.g., enables the surgical device 12 to perform a surgical task).

[0097] At block 354, data may be read from the tag 36, such as by the controller 26 of the user interface device 14, using the reader 42 of the user interface device 14. The read data may include the type identifier 38 and / or the unique identifier 40. The controller 26 may be configured to provide a feedback response in the form of a visual or audio indication, such as via the display 28, in response to a successful reading of such data.

[0098] At block 356, multiple surgical devices 12 may be scanned, such as by the user interface device 14, based on the data read from the tag 36. More specifically, the controller 26 of the user interface device 14 may operate the wireless communication device 32 to scan for broadcasted pairing signals based at least on the unique identifier 40 of the tag 36. In some cases, the controller 26 may be configured to verify that the type identifier 38 read as described herein corresponds to the cartridge 16 before initiating the scan.

[0099] At block 358, the tag 36 may be positioned near the reader 44 of the surgical device 12. To that end, the cartridge 16 including the tag 36 may be coupled to the surgical device 12, such as by placing the cartridge 16 within the cartridge interface 34 of the surgical device 12. The act of placing the cartridge 16 within the cartridge interface 34 of the surgical device 12 may include forming one or more of a mechanical connection, a fluid connection, or an electrical connection between the surgical device 12 and the cartridge 16, such as to effect an interaction. In some cases, the sensor 22 of the surgical device 12 may include a sensor (e.g., a mechanical sensor, an optical sensor) for detecting insertion of the cartridge 16 into the cartridge interface 34. In some cases, the reader 44 of the surgical device 12 may function as such a sensor. For example, the controller 18 of the surgical device 12 may be configured to determine that the cartridge 16 has been inserted into the cartridge interface 34 of the surgical device 12 in response to the reader 44 detecting the presence of the tag 36.

[0100] In response to insertion of the cartridge 16, in some cases with the cartridge 16 in a fully inserted, operational position, the tag 36 may come within reading range of the reader 44 of the surgical device 12. Thereafter, in block 360, the tag 36 data may be read using the reader 44 of the surgical device 12, such as by the controller 18 of the surgical device 12. In some cases, the controller 18 may be configured to read the tag 36 data in response to receiving data from the sensor 22 indicating the insertion. The controller 18 may also be configured to provide a feedback response in the form of a visual or audio indication, such as via the local UI 24, upon successful reading of the tag 36 data.

[0101] At block 362, a pairing signal may be broadcast based on the data read from the tag 36. More specifically, the controller 18 may be configured to generate and broadcast, such as via the wireless communication device 20, a pairing signal that includes at least a portion of the read data, such as the unique identifier 40.

[0102] In some cases, the controller 18 and / or wireless communication device 20 may be configured to generate a pairing signal to incorporate both data read from the tag 36 and data specific to the surgical device 12, or more specifically, data specific to the wireless communication device 20. For example, referring again to FIG. 1 , the surgical device 12 may include an internal memory, such as that incorporated in the wireless communication device 20 or the controller 18, that stores one or more data specific to the surgical device 12, such as a device address 224 and / or a device name 226. The device address 224 may be an address that uniquely identifies the surgical device 12 and / or the wireless communication device 20 of the surgical device 12 and may be non-editable (e.g., a MAC address). The device name 226 may be a name that identifies the surgical device 12 and may be editable. The controller 18 and / or wireless communication device 20 may be configured to modify the device name 226 to include at least a portion of the read data, such as the unique identifier 40, in response to receiving the tag 36 data. The wireless communication device 20 may then be configured to broadcast the device address 224 and device name 226 (including tag 36 data) embedded in the pairing signal.

[0103] At block 366, a pairing signal may be detected, such as via the scan referred to in block 356 above, performed by the user interface device 14. Thereafter, at block 366, a wireless connection may be established between the surgical device 12 and the user interface device 14 based on the pairing signal and the read tag 36 data. More specifically, in response to detecting the pairing signal, such as via the wireless communication device 32, the controller 26 of the user interface device 14 may be configured to compare the device name 226 indicated by the pairing signal with data read using the reader 42 of the user interface device 14 to determine a match. For example, the controller 26 may be configured to determine whether the unique identifier 40 indicated by the device name 226 of the pairing signal matches a unique identifier 40 previously read by the controller 26 via the reader 42 of the user interface device 14. Assuming that the device name 226 of the pairing signal also indicates the type identifier 38 read from the cartridge 16, the controller 26 may be configured to determine whether the type identifier 38 indicated by the device name 226 of the pairing signal matches the type identifier 38 previously read by the controller 26 via the reader 42 of the user interface device. In response to a match of one or more of the above read data, the controller 26 may cause the wireless communication device 32 to establish a connection with the wireless communication device 20 of the surgical device 12, such as using the device address 224 indicated by the pairing signal.

[0104] In some examples, the controller 26 of the user interface device 14 may be configured to execute a user interface device application according to the type identifier 38 read from the tag 36 upon establishing a wireless connection with the surgical device 12. Notably, as described above, multiple cartridges 16 of multiple different types may have multiple different surgical applications. For example, multiple surgical devices 12 of multiple different types may be associated with different types of cartridges 16, respectively. Additionally, a given surgical device 12 may be configured to accept multiple cartridges 16 of multiple different types. By way of example, the waste collection unit 12A may be configured to accept multiple manifolds 16A of multiple different types, such as a regular type manifold 16A and a QBL-enabled type manifold 16A. The controller 26 of the user interface device 14 may be configured to execute functionality specific to the type of cartridge 16 and to present user interface components specific to the type of cartridge 16 on the display 28 of the user interface device 14, depending on the type of cartridge 16 indicated by the read type identifier 38. For example, continuing with the above example, the controller 26 may be configured to display a QBL user interface element on the display 28 in response to a type identifier 38 being displayed for a QBL-enabled type manifold 16A that would not be displayed for a normal type manifold 16A.

[0105] Following establishment of the wireless connection between the surgical device 12 and the user interface device 14, at block 368, data regarding the operation of the surgical device 12 during the performance of a surgical task, such as data generated by the sensors 22, may be transmitted over the wireless connection, such as by the controller 18 of the surgical device 12. At block 370, such data may be processed and / or displayed by the user interface device 14, such as by the controller 26 of the user interface device 14 and / or on the display 28 of the user interface device 14.

[0106] The embodiments described herein provide systems, methods, and computer program products for intuitively establishing reliable wireless connections between one or more surgical devices 12 and a user interface device 14, such as by enhancing functional components (e.g., cartridge 16) that are operable with each surgical device 12 and that are removable and / or disposable from the surgical device 12 to perform a surgical task. Additionally, the examples described herein enable multiple surgical devices 12 to be easily connected to multiple different user interface devices 14, such as for utilizing the surgical devices 12 in connection with different procedures and / or in different locations, without having to engage in complex pairing processes or requiring restrictive proximity-based protocols.

[0107] The flexibility and ease of establishing wireless connections provided by aspects of the present disclosure allows a surgeon to access data and control multiple surgical devices 12 from a single access point, i.e., the user interface device 14, which may be conveniently located relative to the surgeon. Furthermore, pairing multiple surgical devices 12 to a single user interface device 14 using the examples described herein can provide advantages in data reporting and analysis that are useful to the surgeon. For example, a given user interface device 14 can be paired with multiple surgical devices 12, each monitoring a patient's blood loss at a different point. Such data can be wirelessly transmitted to the user interface device 14, which can then consolidate blood loss data from multiple sources to indicate the total amount of blood loss from the patient due to the surgical procedure. Combining blood loss data from multiple sources can provide more accurate real-time data to the surgical team.

[0108] The method steps described herein with respect to generating data, transmitting data, and displaying data may be performed in a continuously repeating cycle as a data stream, thereby providing a real-time display to the user, or as close to real-time as technically feasible. The cycle frequency will depend on the particular sensor or measurement being performed, the communication protocol selected for the wireless communication device, and the refresh rate of the display and processing speed of the controllers of the surgical device and user interface device.

[0109] As one non-limiting example, each controller 18, 26 may include a processor, memory, and non-volatile storage. The processor may include one or more devices selected from a microprocessor, a microcontroller, a digital signal processor, a microcomputer, a central processing unit, a field programmable gate array, a programmable logic device, a state machine, a logic circuit, an analog circuit, a digital circuit, and / or any other device that manipulates signals (analog or digital) based on operational instructions loaded into memory, such as from non-volatile storage. The memory may include a single memory device or multiple memory devices, including, but not limited to, read-only memory (ROM), random access memory (RAM), volatile memory, non-volatile memory, static random access memory (SRAM), dynamic random access memory (DRAM), flash memory, cache memory, and / or any other device capable of storing information. The non-volatile storage may include one or more persistent data storage devices, such as a hard drive, an optical drive, a tape drive, a non-volatile solid-state device, and / or any other device capable of persistently storing information.

[0110] The processor may be configured to load software embodied by computer-executable instructions into memory, such as from storage, and operate under the control of the software. The computer-executable instructions may be compiled or interpreted from a variety of programming languages and / or technologies, including, but not limited to, Java, C, C++, C#, Objective C, Fortran, Pascal, JavaScript, Python, Perl, and PL / SQL, alone or in combination. The computer-executable instructions, when executed by the processor, may be configured to cause the processor to perform the functions, features, processes, and methods of each controller 18, 26 described herein. Thus, each controller 18, 26, or more specifically, the processor of each controller 18, 26, may be considered configured or programmed to perform the functions, features, processes, and methods of the surgical device 12 and the user interface device 14, respectively.

[0111] As used herein, the following definitions are included, and the terms "processor" or "controller" may be interchanged with the term "circuitry," and vice versa. The term "controller" refers to, is a part of, or includes an application specific integrated circuit (ASIC), a digital, analog, or mixed analog / digital discrete circuit, a digital, analog, or mixed analog / digital integrated circuit, a combinational logic circuit, a field programmable gate array (FPGA), a controller circuit (shared, dedicated, or group) that executes code, a memory circuit (shared, dedicated, or group) that stores code to be executed by the controller circuit, other suitable hardware component that provides the described functionality, or a combination of some or all of the above, such as in a system-on-chip.

[0112] The controller may include one or more interface circuits. In some examples, the interface circuit may implement a wired or wireless interface for connecting to a local area network (LAN) or a wireless personal area network (WPAN). Examples of LANs are the Institute of Electrical and Electronics Engineers (IEEE) Standard 802.11-2016 (also known as the WIFI wireless networking standard) and IEEE Standard 802.3-2015 (also known as the ETHERNET wired networking standard). Examples of WPANs are the BLUETOOTH wireless networking standard by the Bluetooth Special Interest Group and IEEE Standard 802.15.4.

[0113] Controllers can communicate with other controllers using interface circuitry. Although controllers may be depicted in this disclosure as being in direct logical communication with other controllers in various configurations, the controllers may actually communicate through a communication system. The communication system includes physical and / or virtual networking equipment, such as hubs, switches, routers, and gateways. In some configurations, the communication system connects to or exists across a wide area network (WAN), such as the Internet. For example, the communication system may include multiple LANs connected to each other through the Internet or point-to-point leased lines using technologies including multiprotocol label switching (MPLS) and virtual private networks (VPNs).

[0114] In various configurations, the functionality of a controller may be distributed among multiple controllers connected via a communication system. For example, multiple controllers may implement the same functionality distributed by a load balancing system. In a further example, the functionality of a controller may be split between a server (also known as a remote or cloud) controller and a client (or user) controller.

[0115] Some or all of the hardware features of the controller may be defined using a language for hardware description, such as IEEE Standard 1364-2005 (commonly referred to as "Verilog") and IEEE Standard 10182-2008 (commonly referred to as "VHDL"). The hardware description language may be used to fabricate and / or program the hardware circuit. In some configurations, some or all of the features of the controller may be defined by a language such as IEEE 1666-2005 (commonly referred to as "System C"), encompassing both code and hardware descriptions as described below.

[0116] As used above, the term code can include software, firmware, and / or microcode and can refer to programs, routines, functions, classes, data structures, and / or objects. The term shared controller circuit encompasses a single controller circuit that executes some or all code from multiple controllers. The term group controller circuit encompasses a controller circuit that executes some or all code from one or more controllers in combination with additional controller circuits. References to multiple controller circuits encompass multiple controller circuits on separate dies, multiple controller circuits on a single die, multiple cores of a single controller circuit, multiple threads of a single controller circuit, or combinations of the above. The term shared memory circuit encompasses a single memory circuit that stores some or all code from multiple controllers. The term group memory circuit encompasses a memory circuit that stores some or all code from one or more controllers in combination with additional memory.

[0117] The term memory device is a subset of the term computer-readable medium. As used herein, the term computer-readable medium does not encompass transitory electrical or electromagnetic signals propagating through a medium (such as on a carrier wave), and thus the term computer-readable medium may be considered tangible and non-transitory. Non-limiting examples of non-transitory computer-readable media are non-volatile memory circuits (such as flash memory circuits, erasable programmable read-only memory circuits, or masked read-only memory circuits), volatile memory circuits (such as static random access memory circuits or dynamic random access memory circuits), magnetic storage media (such as analog or digital magnetic tape or hard disk drives), and optical storage media (such as CDs, DVDs, or Blu-ray Discs).

[0118] The apparatus and methods described in this application may be implemented partially or completely by a special-purpose computer created by configuring a general-purpose computer to perform one or more specific functions embodied in a computer program. The functional blocks and flowchart elements described above serve as software requirements and can be translated into a computer program by the routine work of a skilled engineer or programmer.

[0119] The computer program includes controller-executable instructions stored on at least one non-transitory computer-readable medium. The computer program may also include or rely on stored data. The computer program may include a basic input / output system (BIOS) that interacts with the hardware of the special-purpose computer, device drivers that interact with specific devices of the special-purpose computer, one or more operating systems, user applications, background services, background applications, etc.

[0120] A computer program may include (i) descriptive text that is parsed, such as HTML (Hypertext Markup Language), XML (Extensible Markup Language), or JSON (JavaScript® Object Notation); (ii) assembly code; (iii) object code generated from source code by a compiler; (iv) source code for execution by an interpreter; (v) source code for compilation and execution by a just-in-time compiler; etc. By way of example only, the source code may be written using the grammar of languages including C, C++, C#, Objective-C, Swift, Haskell, Go, SQL, R, Lisp, Java®, Fortran, Perl, Pascal, Curl, OCaml, JavaScript®, HTML5 (Hypertext Markup Language Fifth Revision), Ada, ASP (Active Server Pages), PHP (PHP: Hypertext Precontroller), Scala, Eiffel, Smalltalk, Erlang, Ruby, Flash®, Visual Basic®, Lua, MATLAB®, SENSORLINK, and Python®.

[0121] The above description is not intended to be exhaustive or to limit the invention to any particular form. The terminology used is intended to be in the nature of the description, rather than of limitation. Many modifications and variations are possible in light of the above teachings, and the invention may be practiced otherwise than as specifically described.

[0122] Some embodiments can be described with reference to the following exemplary clauses.

[0123] Clause 1 - A method of establishing a wireless connection between a surgical device and a user interface device via a cartridge including a tag that stores a unique identifier, wherein the surgical device includes a vacuum source, a first reader, and a first wireless communication device, and the user interface device includes a second reader and a second wireless communication device, the method comprising: placing the cartridge near the second reader; verifying the unique identifier of the tag read by the second reader by an output displayed on the user interface device; and coupling the cartridge with the surgical device so as to place the cartridge near the first reader. a step of connecting a surgical device and a user interface device, the step being a first reader configured to read the unique identifier of the tag, and a wireless connection between the surgical device and the user interface device being established based on a second wireless communication device scanning the unique identifier read by the second reader and the first wireless communication device broadcasting the unique identifier read by the first reader; a step of operating a vacuum source to suck surgical waste through the cartridge; and a step of viewing on the user interface device information transmitted from the surgical device to the user interface device via the wireless connection.

[0124] Clause 2 - The method described in Clause 1, wherein the surgical device includes a receiver and the step of coupling the cartridge to the surgical device further includes inserting the cartridge into the receiver to establish a mechanical connection and position the cartridge near the first reader.

[0125] Clause 3 - The method of clause 1 or 2, further comprising confirming by an output displayed on a user interface device that the unique identifier of the tag has been read by the first reader.

[0126] Clause 4 - The method of any one of clauses 1 to 3, further comprising confirming that the wireless connection has been established by an output displayed on the user interface device.

[0127] Clause 5 - The method of any one of clauses 1 to 4, further comprising placing the surgical device at a first location in the operating room and placing the user interface device at a second location in the operating room that prevents the use of near field communication to establish a wireless connection.

[0128] Clause 6 - A method of establishing a wireless connection between a surgical device and a user interface device via a cartridge, the cartridge being for being removably received by a surgical device, the cartridge including a tag storing a unique identifier, the surgical device including a first reader and a first wireless communication device, and the user interface device including a second reader and a second wireless communication device, the method comprising: using the first reader to read the unique identifier of a tag of the cartridge when the cartridge is inserted into the surgical device, the tag being located near the first reader, the insertion of the cartridge into the surgical device resulting in the cartridge being located near the first reader, and the cartridge storing a unique identifier of a surgical tag associated with a surgical procedure. a wireless communication device configured to operate as a functional component of the surgical device during operation of the surgical device to perform the surgical procedure; broadcasting, using a first wireless communication device, the unique identifier read with the first reader and a wireless device address of the surgical device; receiving, by the first wireless communication device, a communication from a second wireless communication device in response to the second reader reading the unique identifier of the tag of the cartridge when the second reader is positioned near the second reader and the second wireless communication device receiving the broadcast including the unique identifier; and establishing a wireless connection between the surgical device and a user interface device based on the communication.

[0129] Clause 7 - A method of establishing a wireless connection between a surgical device and a user interface device via a cartridge, the cartridge being for being removably received by a surgical device and including a tag that stores a unique identifier, the surgical device including a first reader and a first wireless communication device, the cartridge being configured to be inserted into the surgical device such that the cartridge is positioned near the first reader when inserted and configured to operate as a functional component of the surgical device during operation of the surgical device to perform a surgical task associated with a surgical procedure, the user interface device including a second reader and a second wireless communication device, the method comprising: using the second reader to read the unique identifier of the tag of the cartridge when positioned near the second reader; scanning using the second wireless communication device the unique identifier read by the second reader; and identifying using the second wireless communication device a broadcast from the first wireless communication device including the unique identifier read using the first reader and the wireless address of the surgical device; and pairing with the surgical device via the wireless device address of the broadcast.

[0130] Clause 8 - A computer program product comprising instructions stored on at least one non-transitory computer-readable medium and configured, when executed by at least one processor, to perform the method described in clause 6 or 7.

[0131] Clause 9 - A system comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the at least one processor to perform a method according to clause 6 or 7.

Claims

1. A method for establishing a wireless connection between a surgical device and a user interface device via a cartridge that is removably accepted by the surgical device, The cartridge includes a tag that stores a unique identifier, The surgical device includes a first reader and a first wireless communication device. The user interface device includes a second reader and a second wireless communication device. The aforementioned method, When positioned near the second reader, the unique identifier of the tag on the cartridge is read using the second reader. When the cartridge is inserted into the surgical device, the first reader reads the unique identifier of the tag on the cartridge, which is located near the first reader. The steps include broadcasting the unique identifier read using the first reader and the wireless device address of the surgical device using the first wireless communication device, The steps include scanning the unique identifier read by the second reader using the second wireless communication device, In order to establish a wireless connection between the surgical device and the user interface device, the steps include pairing the surgical device and the user interface device via the wireless device address based on the match of the scanned unique identifier with the broadcasted unique identifier, Includes, As a result of inserting the cartridge into the surgical device, The cartridge will be positioned near the first reader, and The cartridge operates as a functional component of the surgical device during the operation of the surgical device for performing surgical tasks related to surgical procedures. method.

2. The surgical device generates a wireless device name for the surgical device, including the unique identifier, The wireless device name is broadcast using the first wireless communication device, The method according to claim 1, including the method described in claim 1.

3. The insertion of the cartridge into the surgical device is detected by the surgical device, Based on the detected insertion, the unique identifier of the tag is read using the first reader, including, The method according to claim 1 or claim 2.

4. The method according to claim 1 or 2, comprising writing or rewriting data to the tag in order to prevent the reuse or reprocessing of the cartridge.

5. The method according to claim 1 or 2, wherein the first reader and the second reader are optical sensors and the tag is a machine-readable optical code.

6. The method according to claim 1 or 2, wherein the cartridge is configured to form one or more mechanical, electrical, or fluid connections with the surgical device when inserted into the surgical device.

7. The method according to claim 6, wherein the surgical device includes a receiver, the receiver is configured to removably receive the cartridge in order to establish a mechanical connection between the surgical device and the cartridge.

8. The surgical device includes a vacuum source that is in fluid communication with the receiver, and the cartridge is a manifold configured to be detachably connected to a suction tube. The method according to claim 7, comprising operating the vacuum source of the surgical device to aspirate surgical waste through the suction tube and the manifold, wherein the manifold facilitates the wireless connection and subsequently operates as the functional component of the surgical device during the operation of the surgical device for aspirating surgical waste.

9. The surgical device includes a waste container that is in fluid communication with the receiver, and a fluid measuring device that is operably connected to the waste container. The aforementioned method, The fluid volume data is identified using the fluid measuring device as a measure of the fluid in the waste container, For display purposes, the fluid volume data is transmitted from the surgical device to the user interface device via the wireless connection, The method according to claim 8, including the method described in claim 8.

10. One of the surgical device and the cartridge includes a sensor for determining the concentration of blood in the surgical waste. The aforementioned method, As a measure of the blood concentration in the surgical waste, blood concentration data is identified using the sensor, Based on the blood concentration data and the fluid volume data, blood volume data is identified as a measure of the blood volume in the waste container. For display purposes, the blood volume data is transmitted from the surgical device to the user interface device via the wireless connection, The method according to claim 9, including the method described in claim 9.

11. The surgical device includes a waste container and a vacuum source in fluid communication with the waste container, and one of the surgical device and the cartridge includes a first sensor for monitoring the flow rate of surgical waste and a second sensor for determining the concentration of blood in the surgical waste. The aforementioned method, To suction surgical waste through the cartridge, the vacuum source of the surgical device is operated, The concentration of blood in the surgical waste drawn in through the cartridge is determined using the second sensor, The flow rate of the surgical waste drawn in through the cartridge is determined using the first sensor, Based on the identified blood concentration and the identified flow rate, blood volume data is identified as a measure of the blood volume in the waste container. For display purposes, the blood volume data is transmitted from the surgical device to the user interface device using the wireless connection, The method according to claim 1 or 2, including the method described in claim 1 or 2.

12. The method according to claim 9, wherein the steps of identifying and transmitting are performed continuously so that the user interface device updates the displayed data in real time.

13. The tag stores data indicating the type of the cartridge, The aforementioned method, When positioned near the second reader, the cartridge type data of the tag on the cartridge is read using the second reader, In response to the establishment of the wireless connection with the surgical device, the user interface device displays one or more user interface elements associated with the cartridge type. The method according to claim 1 or 2, including the method described in claim 1 or 2.

14. A system for use in an operating room, The system includes a cartridge, a surgical device, and a user interface device that can be positioned away from the surgical device. The cartridge includes a tag that stores a unique identifier, The surgical device includes a receiver, a first reader connected to the receiver, and a first wireless communication device, wherein the receiver is configured to removably receive the cartridge such that when the cartridge is inserted into the receiver, the tag is positioned near the first reader, and the cartridge is configured to operate as a functional component of the surgical device for performing surgical tasks related to surgical procedures. The user interface device includes a display, a second reader, and a second wireless communication device. The first wireless communication device is configured to broadcast the unique identifier and the wireless device address of the surgical device based on the reading of the tag by the first reader. A system in which the second wireless communication device is configured to pair the surgical device and the user interface device via the wireless device address and to scan the unique identifier based on the reading of the tag by the second reader in order to establish a wireless connection between the surgical device and the user interface device.

15. A surgical device for establishing a wireless connection with a user interface device via a removable cartridge containing a tag that stores a unique identifier, The aforementioned surgical device is Wireless communication devices and The leader, Receiving device and, The reader and the wireless communication device are connected to at least one processor, Includes, The receiver is configured to removably receive the cartridge such that, when the cartridge is inserted into the receiver, the tag is positioned near the reader and the cartridge is configured to function as a functional component of the surgical device for performing surgical tasks related to surgical procedures. The aforementioned at least one processor is When the cartridge is inserted into the receiver of the surgical device, the reader reads the unique identifier of the tag on the cartridge, which is located near the reader. The unique identifier read using the reader and the wireless device address of the surgical device are broadcast using the wireless communication device. Based on the communication from the user interface device in response to the broadcast between the unique identifier and the wireless device address of the surgical device, a wireless connection between the surgical device and the user interface device is established using the wireless communication device. A surgical device configured to perform the following action.

Images