Patent Grant
11950860
The present disclosure relates to various surgical systems, including modular electrosurgical and/or ultrasonic surgical systems. Operating rooms (ORs) are in need of streamlined capital solutions because ORs are a tangled web of cords, devices, and people due to the number of different devices that are needed to complete each surgical procedure. This is a reality of every OR in every market throughout the globe. Capital equipment is a major offender in creating clutter within ORs because most capital equipment performs one task or job, and each type of capital equipment requires unique techniques or methods to use and has a unique user interface. Accordingly, there are unmet consumer needs for capital equipment and other surgical technology to be consolidated in order to decrease the equipment footprint within the OR, streamline the equipment's interfaces, and improve surgical staff efficiency during a surgical procedure by reducing the number of devices that surgical staff members need to interact with.
A user interface for a modular energy system may be improved by including audio mitigation techniques. There is a risk that an energy generator component of a modular energy system may improperly generate a visual or audio tone to indicate alarms, alerts, and energy activation of electrosurgical/ultrasonic instruments as may be required by external standards. The risk of failure to generate a proper visual or audio tone are undesirable during the operation of the electrosurgical/ultrasonic instrument. Audio feedback to alert the user that an electrosurgical/ultrasonic instrument has been energized by an energy module is part of proper operation protocol of the electrosurgical/ultrasonic instrument. Thus, there is a need to mitigate or eliminate any potential risk of video or audio tone failures to reduce the risk of applying undesired energy by an electrosurgical/ultrasonic instrument during an operation.
In one aspect, the present disclosure provides an audio circuit. The audio circuit comprises a processor configured to generate a digital audio signal, wherein the audio signal comprises audio data bits inserted on the rising edge of a clock signal and additional data bits inserted on a falling edge of the clock signal, wherein the audio data bits on the rising edge represent a digital audio tone and the additional data bits inserted on the falling edge represent a unique tone identification of the audio data bits on the rising edge; a digital-to-analog converter configured to: receive the digital audio signal; convert the audio data bits inserted on the rising edge; and ignore the additional data bits on the falling edge; an audio mitigation control module configured to: receive the digital audio signal; read the additional data bits on the falling edge; and confirm that the audio data bits inserted on the rising edge represent a correct digital audio tone based on the unique tone identification.
In another aspect, the present disclosure provides a circuit for mitigating a function of a user interface (UI) display of a modular energy system. The circuit comprises a processor configured to couple to a surgical instrument; a display; and a video data converter circuit configured to receive formatted video data that represents an expected image to be displayed on the display and to provide differential video signaling data to the display and a copy of the differential video signaling data to the processor; wherein the processor is configured to determine whether the copy of the differential video signaling data is changing over time.
In yet another aspect, the present disclosure provides a method of mitigating a function of a user interface (UI) display of a modular energy system. The method comprises receiving, by a video data converter circuit, formatted video data at an input channel of the video data converter circuit, wherein the input channel is coupled to a processor and the formatted video data represents an expected image to be displayed on a display, the video data converter having two output channels, wherein a first output channel is coupled to the display and a second output channel is coupled back to the processor, wherein the processor is configured to couple to a surgical instrument; providing, by the video data converter circuit, differential video signaling data to the display from the first output channel of the video data converter circuit; providing, by the video data converter circuit, a copy of the differential video signaling data to the processor from the second output channel; and determining, by the processor, whether the differential video signaling data on the second output channel is changing over time.
In yet another aspect, the present disclosure provides an audio circuit. The audio circuit comprises a processor; an audio amplifier coupled to the processor by audio data lines; an audio mitigation control circuit coupled to the processor and the audio amplifier, a digital-to-analog converter (DAC) comprising a first analog output channel coupled to a first speaker; a first current shunt coupled in series with the first speaker; a first current sense amplifier having an input coupled to the first current shunt and an output coupled to an input of a first analog-to-digital converter (ADC); and wherein the output of the first ADC is coupled to the audio mitigation control module; wherein the audio mitigation control circuit is configured to: fetch, from a memory coupled to the audio mitigation control circuit, a unique identification number to identify an expected audio file, the audio file comprising audio data comprising an audio asset and a unique super-audible tone to identify the audio asset; receive the audio data from the output of the first ADC; filter the audio data to isolate a super-audible frequency range of the audio data; calculate a fast Fourier transform (FFT) on the audio data in the isolated super-audible frequency range; perform a peak detection function on the FFT results to detect a super-audible tone; compare the detected super-audible tone to the unique identification number to identify the expected audio file; and determine a specific audio file transmitted to the audio amplifier based on the comparison.
In yet another aspect, the present disclosure provides an audio circuit. The audio circuit comprises a processor; an audio amplifier coupled to the processor by audio data lines; an audio mitigation control circuit coupled to the processor and the audio amplifier, wherein the audio mitigation control circuit is configured to: fetch, from a memory coupled to the audio mitigation control circuit, a unique identification number to identify an expected audio file, the audio file comprising audio data comprising an audio asset and a unique super-audible tone to identify the audio asset; receive the audio data transmitted from the processor to the audio amplifier; filter the audio data to isolate a super-audible frequency range of the audio data; calculate a fast Fourier transform (FFT) on the audio data in the isolated super-audible frequency range; perform a peak detection function on the FFT results to detect a super-audible tone; compare the detected super-audible tone to the unique identification number to identify the expected audio file; and determine a specific audio file transmitted to the audio amplifier based on the comparison.
The various aspects described herein, both as to organization and methods of operation, together with further objects and advantages thereof, may best be understood by reference to the following description, taken in conjunction with the accompanying drawings as follows.
Corresponding reference characters indicate corresponding parts throughout the several views. The exemplifications set out herein illustrate various disclosed aspects, in one form, and such exemplifications are not to be construed as limiting the scope thereof in any manner.
Applicant of the present application owns the following U.S. patent applications filed concurrently herewith on Mar. 30, 2021, the disclosure of each of which is herein incorporated by reference in its entirety:
Applicant of the present application owns the following U.S. patent applications filed Sep. 5, 2019, the disclosure of each of which is herein incorporated by reference in its entirety:
Applicant of the present application owns the following U.S. Patent Provisional Applications filed Mar. 29, 2019, the disclosure of each of which is herein incorporated by reference in its entirety:
Applicant of the present application owns the following U.S. Patent Provisional Application filed Sep. 7, 2018, the disclosure of which is herein incorporated by reference in its entirety:
Before explaining various aspects of surgical devices and generators in detail, it should be noted that the illustrative examples are not limited in application or use to the details of construction and arrangement of parts illustrated in the accompanying drawings and description. The illustrative examples may be implemented or incorporated in other aspects, variations and modifications, and may be practiced or carried out in various ways. Further, unless otherwise indicated, the terms and expressions employed herein have been chosen for the purpose of describing the illustrative examples for the convenience of the reader and are not for the purpose of limitation thereof. Also, it will be appreciated that one or more of the following-described aspects, expressions of aspects, and/or examples, can be combined with any one or more of the other following-described aspects, expressions of aspects and/or examples.
Various aspects are directed to improved ultrasonic surgical devices, electrosurgical devices and generators for use therewith. Aspects of the ultrasonic surgical devices can be configured for transecting and/or coagulating tissue during surgical procedures, for example. Aspects of the electrosurgical devices can be configured for transecting, coagulating, scaling, welding and/or desiccating tissue during surgical procedures, for example.
Referring to
Other types of robotic systems can be readily adapted for use with the surgical system 102. Various examples of robotic systems and surgical tools that are suitable for use with the present disclosure are described in U.S. Provisional Patent Application Ser. No. 62/611,339, titled ROBOT ASSISTED SURGICAL PLATFORM, filed Dec. 28, 2017, the disclosure of which is herein incorporated by reference in its entirety.
Various examples of cloud-based analytics that are performed by the cloud 104, and are suitable for use with the present disclosure, are described in U.S. Provisional Patent Application Ser. No. 62/611,340, titled CLOUD-BASED MEDICAL ANALYTICS, filed Dec. 28, 2017, the disclosure of which is herein incorporated by reference in its entirety.
In various aspects, the imaging device 124 includes at least one image sensor and one or more optical components. Suitable image sensors include, but are not limited to, Charge-Coupled Device (CCD) sensors and Complementary Metal-Oxide Semiconductor (CMOS) sensors.
The optical components of the imaging device 124 may include one or more illumination sources and/or one or more lenses. The one or more illumination sources may be directed to illuminate portions of the surgical field. The one or more image sensors may receive light reflected or refracted from the surgical field, including light reflected or refracted from tissue and/or surgical instruments.
The one or more illumination sources may be configured to radiate electromagnetic energy in the visible spectrum as well as the invisible spectrum. The visible spectrum, sometimes referred to as the optical spectrum or luminous spectrum, is that portion of the electromagnetic spectrum that is visible to (i.e., can be detected by) the human eye and may be referred to as visible light or simply light. A typical human eye will respond to wavelengths in air that are from about 380 nm to about 750 nm.
The invisible spectrum (i.e., the non-luminous spectrum) is that portion of the electromagnetic spectrum that lies below and above the visible spectrum (i.e., wavelengths below about 380 nm and above about 750 nm). The invisible spectrum is not detectable by the human eye. Wavelengths greater than about 750 nm are longer than the red visible spectrum, and they become invisible infrared (IR), microwave, and radio electromagnetic radiation. Wavelengths less than about 380 nm are shorter than the violet spectrum, and they become invisible ultraviolet, x-ray, and gamma ray electromagnetic radiation.
In various aspects, the imaging device 124 is configured for use in a minimally invasive procedure. Examples of imaging devices suitable for use with the present disclosure include, but not limited to, an arthroscope, angioscope, bronchoscope, choledochoscope, colonoscope, cytoscope, duodenoscope, enteroscope, esophagogastro-duodenoscope (gastroscope), endoscope, laryngoscope, nasopharyngo-neproscope, sigmoidoscope, thoracoscope, and ureteroscope.
In one aspect, the imaging device employs multi-spectrum monitoring to discriminate topography and underlying structures. A multi-spectral image is one that captures image data within specific wavelength ranges across the electromagnetic spectrum. The wavelengths may be separated by filters or by the use of instruments that are sensitive to particular wavelengths, including light from frequencies beyond the visible light range, e.g., IR and ultraviolet. Spectral imaging can allow extraction of additional information the human eye fails to capture with its receptors for red, green, and blue. The use of multi-spectral imaging is described in greater detail under the heading “Advanced Imaging Acquisition Module” in U.S. Provisional Patent Application Ser. No. 62/611,341, titled INTERACTIVE SURGICAL PLATFORM, filed Dec. 28, 2017, the disclosure of which is herein incorporated by reference in its entirety. Multi-spectrum monitoring can be a useful tool in relocating a surgical field after a surgical task is completed to perform one or more of the previously described tests on the treated tissue.
It is axiomatic that strict sterilization of the operating room and surgical equipment is required during any surgery. The strict hygiene and sterilization conditions required in a “surgical theater,” i.e., an operating or treatment room, necessitate the highest possible sterility of all medical devices and equipment. Part of that sterilization process is the need to sterilize anything that comes in contact with the patient or penetrates the sterile field, including the imaging device 124 and its attachments and components. It will be appreciated that the sterile field may be considered a specified area, such as within a tray or on a sterile towel, that is considered free of microorganisms, or the sterile field may be considered an area, immediately around a patient, who has been prepared for a surgical procedure. The sterile field may include the scrubbed team members, who are properly attired, and all furniture and fixtures in the area.
In various aspects, the visualization system 108 includes one or more imaging sensors, one or more image-processing units, one or more storage arrays, and one or more displays that are strategically arranged with respect to the sterile field, as illustrated in
As illustrated in
In one aspect, the hub 106 is also configured to route a diagnostic input or feedback entered by a non-sterile operator at the visualization tower 111 to the primary display 119 within the sterile field, where it can be viewed by a sterile operator at the operating table. In one example, the input can be in the form of a modification to the snapshot displayed on the non-sterile display 107 or 109, which can be routed to the primary display 119 by the hub 106.
Referring to
Referring now to
During a surgical procedure, energy application to tissue, for sealing and/or cutting, is generally associated with smoke evacuation, suction of excess fluid, and/or irrigation of the tissue. Fluid, power, and/or data lines from different sources are often entangled during the surgical procedure. Valuable time can be lost addressing this issue during a surgical procedure. Detangling the lines may necessitate disconnecting the lines from their respective modules, which may require resetting the modules. The hub modular enclosure 136 offers a unified environment for managing the power, data, and fluid lines, which reduces the frequency of entanglement between such lines.
Aspects of the present disclosure present a surgical hub for use in a surgical procedure that involves energy application to tissue at a surgical site. The surgical hub includes a hub enclosure and a combo generator module slidably receivable in a docking station of the hub enclosure. The docking station includes data and power contacts. The combo generator module includes one or more of an ultrasonic energy generator component, a bipolar RF energy generator component, and a monopolar RF energy generator component that are housed in a single unit. In one aspect, the combo generator module also includes a smoke evacuation component, at least one energy delivery cable for connecting the combo generator module to a surgical instrument, at least one smoke evacuation component configured to evacuate smoke, fluid, and/or particulates generated by the application of therapeutic energy to the tissue, and a fluid line extending from the remote surgical site to the smoke evacuation component.
In one aspect, the fluid line is a first fluid line and a second fluid line extends from the remote surgical site to a suction and irrigation module slidably received in the hub enclosure. In one aspect, the hub enclosure comprises a fluid interface.
Certain surgical procedures may require the application of more than one energy type to the tissue. One energy type may be more beneficial for cutting the tissue, while another different energy type may be more beneficial for sealing the tissue. For example, a bipolar generator can be used to seal the tissue while an ultrasonic generator can be used to cut the sealed tissue. Aspects of the present disclosure present a solution where a hub modular enclosure 136 is configured to accommodate different generators, and facilitate an interactive communication therebetween. One of the advantages of the hub modular enclosure 136 is enabling the quick removal and/or replacement of various modules.
Aspects of the present disclosure present a modular surgical enclosure for use in a surgical procedure that involves energy application to tissue. The modular surgical enclosure includes a first energy-generator module, configured to generate a first energy for application to the tissue, and a first docking station comprising a first docking port that includes first data and power contacts. In one aspect, the first energy-generator module is slidably movable into an electrical engagement with the power and data contacts and wherein the first energy-generator module is slidably movable out of the electrical engagement with the first power and data contacts. In an alternative aspect, the first energy-generator module is stackably movable into an electrical engagement with the power and data contacts and wherein the first energy-generator module is stackably movable out of the electrical engagement with the first power and data contacts.
Further to the above, the modular surgical enclosure also includes a second energy-generator module configured to generate a second energy, either the same or different than the first energy, for application to the tissue, and a second docking station comprising a second docking port that includes second data and power contacts. In one aspect, the second energy-generator module is slidably movable into an electrical engagement with the power and data contacts, and wherein the second energy-generator module is slidably movable out of the electrical engagement with the second power and data contacts. In an alternative aspect, the second energy-generator module is stackably movable into an electrical engagement with the power and data contacts, and wherein the second energy-generator module is stackably movable out of the electrical engagement with the second power and data contacts.
In addition, the modular surgical enclosure also includes a communication bus between the first docking port and the second docking port, configured to facilitate communication between the first energy-generator module and the second energy-generator module.
Referring to
In one aspect, the hub modular enclosure 136 comprises a modular power and communication backplane 149 with external and wireless communication headers to enable the removable attachment of the modules 140, 126, 128, 129 and interactive communication therebetween.
As used throughout this description, the term “wireless” and its derivatives may be used to describe circuits, devices, systems, methods, techniques, communications channels, etc., that may communicate data through the use of modulated electromagnetic radiation through a non-solid medium. The term does not imply that the associated devices do not contain any wires, although in some aspects they might not. The communication module may implement any of a number of wireless or wired communication standards or protocols, including but not limited to Wi-Fi (IEEE 802.11 family), WiMAX (IEEE 802.16 family), IEEE 802.20, long term evolution (LTE), Ev-DO, HSPA+, HSDPA+, HSUPA+, EDGE, GSM, GPRS, CDMA, TDMA, DECT, Bluetooth, Ethernet derivatives thereof, as well as any other wireless and wired protocols that are designated as 3G, 4G, 5G, and beyond. The computing module may include a plurality of communication modules. For instance, a first communication module may be dedicated to shorter range wireless communications such as Wi-Fi and Bluetooth and a second communication module may be dedicated to longer range wireless communications such as GPS, EDGE, GPRS, CDMA, WiMAX, LTE, Ev-DO, and others.
As used herein a processor or processing unit is an electronic circuit which performs operations on some external data source, usually memory or some other data stream. The term is used herein to refer to the central processor (central processing unit) in a system or computer systems (especially systems on a chip (SoCs)) that combine a number of specialized “processors.”
As used herein, a system on a chip or system on chip (SoC or SOC) is an integrated circuit (also known as an “IC” or “chip”) that integrates all components of a computer or other electronic systems. It may contain digital, analog, mixed-signal, and often radio-frequency functions—all on a single substrate. A SoC integrates a microcontroller (or microprocessor) with advanced peripherals like graphics processing unit (GPU), Wi-Fi module, or coprocessor. A SoC may or may not contain built-in memory.
As used herein, a microcontroller or controller is a system that integrates a microprocessor with peripheral circuits and memory. A microcontroller (or MCU for microcontroller unit) may be implemented as a small computer on a single integrated circuit. It may be similar to a SoC; a SoC may include a microcontroller as one of its components. A microcontroller may contain one or more core processing units (CPUs) along with memory and programmable input/output peripherals. Program memory in the form of Ferroelectric RAM, NOR flash or OTP ROM is also often included on chip, as well as a small amount of RAM. Microcontrollers may be employed for embedded applications, in contrast to the microprocessors used in personal computers or other general purpose applications consisting of various discrete chips.
As used herein, the term controller or microcontroller may be a stand-alone IC or chip device that interfaces with a peripheral device. This may be a link between two parts of a computer or a controller on an external device that manages the operation of (and connection with) that device.
Any of the processors or microcontrollers described herein, may be implemented by any single core or multicore processor such as those known under the trade name ARM Cortex by Texas Instruments. In one aspect, the processor may be an LM4F230H5QR ARM Cortex-M4F Processor Core, available from Texas Instruments, for example, comprising on-chip memory of 256 KB single-cycle flash memory, or other non-volatile memory, up to 40 MHz, a prefetch buffer to improve performance above 40 MHz, a 32 KB single-cycle serial random access memory (SRAM), internal read-only memory (ROM) loaded with StellarisWare® software, 2 KB electrically erasable programmable read-only memory (EEPROM), one or more pulse width modulation (PWM) modules, one or more quadrature encoder inputs (QEI) analog, one or more 12-bit Analog-to-Digital Converters (ADC) with 12 analog input channels, details of which are available for the product datasheet.
In one aspect, the processor may comprise a safety controller comprising two controller-based families such as TMS570 and RM4x known under the trade name Hercules ARM Cortex R4, also by Texas Instruments. The safety controller may be configured specifically for IEC 61508 and ISO 26262 safety critical applications, among others, to provide advanced integrated safety features while delivering scalable performance, connectivity, and memory options.
Modular devices include the modules (as described in connection with
The modular energy system 2000 is configured to drive multiple surgical instruments 2204, 2206, 2208. The first surgical instrument is an ultrasonic surgical instrument 2204 and comprises a handpiece 2205 (HP), an ultrasonic transducer 2220, a shaft 2226, and an end effector 2222. The end effector 2222 comprises an ultrasonic blade 2228 acoustically coupled to the ultrasonic transducer 2220 and a clamp arm 2240. The handpiece 2205 comprises a trigger 2243 to operate the clamp arm 2240 and a combination of the toggle buttons 2234a, 2234b, 2234c to energize and drive the ultrasonic blade 2228 or other function. The toggle buttons 2234a, 2234b, 2234c can be configured to energize the ultrasonic transducer 2220 with the modular energy system 2000.
The modular energy system 2000 also is configured to drive a second surgical instrument 2206. The second surgical instrument 2206 is an RF electrosurgical instrument and comprises a handpiece 2207 (HP), a shaft 2227, and an end effector 2224. The end effector 2224 comprises electrodes in clamp arms 2242a, 2242b and return through an electrical conductor portion of the shaft 2227. The electrodes are coupled to and energized by a bipolar energy source within the modular energy system 2000. The handpiece 2207 comprises a trigger 2245 to operate the clamp arms 2242a, 2242b and an energy button 2235 to actuate an energy switch to energize the electrodes in the end effector 2224.
The modular energy system 2000 also is configured to drive a multifunction surgical instrument 2208. The multifunction surgical instrument 2208 comprises a handpiece 2209 (HP), a shaft 2229, and an end effector 2225. The end effector 2225 comprises an ultrasonic blade 2249 and a clamp arm 2246. The ultrasonic blade 2249 is acoustically coupled to the ultrasonic transducer 2220. The ultrasonic transducer 2220 may be separable from or integral to the handpiece 2209. The handpiece 2209 comprises a trigger 2247 to operate the clamp arm 2246 and a combination of the toggle buttons 2237a, 2237b, 2237c to energize and drive the ultrasonic blade 2249 or other function. The toggle buttons 2237a, 2237b, 2237c can be configured to energize the ultrasonic transducer 2220 with the modular energy system 2000 and energize the ultrasonic blade 2249 with a bipolar energy source also contained within the modular energy system 2000.
The modular energy system 2000 is configurable for use with a variety of surgical instruments. According to various forms, the modular energy system 2000 may be configurable for use with different surgical instruments of different types including, for example, the ultrasonic surgical instrument 2204, the RF electrosurgical instrument 2206, and the multifunction surgical instrument 2208 that integrates RF and ultrasonic energies delivered individually or simultaneously from the modular energy system 2000. Although in the form of
Although an “intelligent” device including control algorithms that respond to sensed data can be an improvement over a “dumb” device that operates without accounting for sensed data, some sensed data can be incomplete or inconclusive when considered in isolation, i.e., without the context of the type of surgical procedure being performed or the type of tissue that is being operated on. Without knowing the procedural context (e.g., knowing the type of tissue being operated on or the type of procedure being performed), the control algorithm may control the modular device incorrectly or sub optimally given the particular context-free sensed data. For example, the optimal manner for a control algorithm to control a surgical instrument in response to a particular sensed parameter can vary according to the particular tissue type being operated on. This is due to the fact that different tissue types have different properties (e.g., resistance to tearing) and thus respond differently to actions taken by surgical instruments. Therefore, it may be desirable for a surgical instrument to take different actions even when the same measurement for a particular parameter is sensed. As one specific example, the optimal manner in which to control a surgical stapling and cutting instrument in response to the instrument sensing an unexpectedly high force to close its end effector will vary depending upon whether the tissue type is susceptible or resistant to tearing. For tissues that are susceptible to tearing, such as lung tissue, the instrument's control algorithm would optimally ramp down the motor in response to an unexpectedly high force to close to avoid tearing the tissue. For tissues that are resistant to tearing, such as stomach tissue, the instrument's control algorithm would optimally ramp up the motor in response to an unexpectedly high force to close to ensure that the end effector is clamped properly on the tissue. Without knowing whether lung or stomach tissue has been clamped, the control algorithm may make a suboptimal decision.
One solution utilizes a surgical hub including a system that is configured to derive information about the surgical procedure being performed based on data received from various data sources and then control the paired modular devices accordingly. In other words, the surgical hub is configured to infer information about the surgical procedure from received data and then control the modular devices paired to the surgical hub based upon the inferred context of the surgical procedure.
The situational awareness system of the surgical hub 2304 can be configured to derive the contextual information from the data received from the data sources 2326 in a variety of different ways. In one exemplification, the situational awareness system includes a pattern recognition system, or machine learning system (e.g., an artificial neural network), that has been trained on training data to correlate various inputs (e.g., data from databases 2322, patient monitoring devices 2324, and/or modular devices 2302) to corresponding contextual information regarding a surgical procedure. In other words, a machine learning system can be trained to accurately derive contextual information regarding a surgical procedure from the provided inputs. In another exemplification, the situational awareness system can include a lookup table storing pre-characterized contextual information regarding a surgical procedure in association with one or more inputs (or ranges of inputs) corresponding to the contextual information. In response to a query with one or more inputs, the lookup table can return the corresponding contextual information for the situational awareness system for controlling the modular devices 2302. In one exemplification, the contextual information received by the situational awareness system of the surgical hub 2304 is associated with a particular control adjustment or set of control adjustments for one or more modular devices 2302. In another exemplification, the situational awareness system includes a further machine learning system, lookup table, or other such system, which generates or retrieves one or more control adjustments for one or more modular devices 2302 when provided the contextual information as input.
A surgical hub 2304 incorporating a situational awareness system provides a number of benefits for the surgical system 2300. One benefit includes improving the interpretation of sensed and collected data, which would in turn improve the processing accuracy and/or the usage of the data during the course of a surgical procedure. To return to a previous example, a situationally aware surgical hub 2304 could determine what type of tissue was being operated on; therefore, when an unexpectedly high force to close the surgical instrument's end effector is detected, the situationally aware surgical hub 2304 could correctly ramp up or ramp down the motor of the surgical instrument for the type of tissue.
As another example, the type of tissue being operated can affect the adjustments that are made to the compression rate and load thresholds of a surgical stapling and cutting instrument for a particular tissue gap measurement. A situationally aware surgical hub 2304 could infer whether a surgical procedure being performed is a thoracic or an abdominal procedure, allowing the surgical hub 2304 to determine whether the tissue clamped by an end effector of the surgical stapling and cutting instrument is lung (for a thoracic procedure) or stomach (for an abdominal procedure) tissue. The surgical hub 2304 could then adjust the compression rate and load thresholds of the surgical stapling and cutting instrument appropriately for the type of tissue.
As yet another example, the type of body cavity being operated in during an insufflation procedure can affect the function of a smoke evacuator. A situationally aware surgical hub 2304 could determine whether the surgical site is under pressure (by determining that the surgical procedure is utilizing insufflation) and determine the procedure type. As a procedure type is generally performed in a specific body cavity, the surgical hub 2304 could then control the motor rate of the smoke evacuator appropriately for the body cavity being operated in. Thus, a situationally aware surgical hub 2304 could provide a consistent amount of smoke evacuation for both thoracic and abdominal procedures.
As yet another example, the type of procedure being performed can affect the optimal energy level at which an ultrasonic surgical instrument or radio frequency (RF) electrosurgical instrument operates. Arthroscopic procedures, for example, require higher energy levels because the end effector of the ultrasonic surgical instrument or RF electrosurgical instrument is immersed in fluid. A situationally aware surgical hub 2304 could determine whether the surgical procedure is an arthroscopic procedure. The surgical hub 2304 could then adjust the RF power level or the ultrasonic amplitude of the generator (i.e., “energy level”) to compensate for the fluid filled environment. Relatedly, the type of tissue being operated on can affect the optimal energy level for an ultrasonic surgical instrument or RF electrosurgical instrument to operate at. A situationally aware surgical hub 2304 could determine what type of surgical procedure is being performed and then customize the energy level for the ultrasonic surgical instrument or RF electrosurgical instrument, respectively, according to the expected tissue profile for the surgical procedure. Furthermore, a situationally aware surgical hub 2304 can be configured to adjust the energy level for the ultrasonic surgical instrument or RF electrosurgical instrument throughout the course of a surgical procedure, rather than just on a procedure-by-procedure basis. A situationally aware surgical hub 2304 could determine what step of the surgical procedure is being performed or will subsequently be performed and then update the control algorithms for the generator and/or ultrasonic surgical instrument or RF electrosurgical instrument to set the energy level at a value appropriate for the expected tissue type according to the surgical procedure step.
As yet another example, data can be drawn from additional data sources 2326 to improve the conclusions that the surgical hub 2304 draws from one data source 2326. A situationally aware surgical hub 2304 could augment data that it receives from the modular devices 2302 with contextual information that it has built up regarding the surgical procedure from other data sources 2326. For example, a situationally aware surgical hub 2304 can be configured to determine whether hemostasis has occurred (i.e., whether bleeding at a surgical site has stopped) according to video or image data received from a medical imaging device. However, in some cases the video or image data can be inconclusive. Therefore, in one exemplification, the surgical hub 2304 can be further configured to compare a physiologic measurement (e.g., blood pressure sensed by a BP monitor communicably connected to the surgical hub 2304) with the visual or image data of hemostasis (e.g., from a medical imaging device 124 (
Another benefit includes proactively and automatically controlling the paired modular devices 2302 according to the particular step of the surgical procedure that is being performed to reduce the number of times that medical personnel are required to interact with or control the surgical system 2300 during the course of a surgical procedure. For example, a situationally aware surgical hub 2304 could proactively activate the generator to which an RF electrosurgical instrument is connected if it determines that a subsequent step of the procedure requires the use of the instrument. Proactively activating the energy source allows the instrument to be ready for use a soon as the preceding step of the procedure is completed.
As another example, a situationally aware surgical hub 2304 could determine whether the current or subsequent step of the surgical procedure requires a different view or degree of magnification on the display according to the feature(s) at the surgical site that the surgeon is expected to need to view. The surgical hub 2304 could then proactively change the displayed view (supplied by, e.g., a medical imaging device for the visualization system 108) accordingly so that the display automatically adjusts throughout the surgical procedure.
As yet another example, a situationally aware surgical hub 2304 could determine which step of the surgical procedure is being performed or will subsequently be performed and whether particular data or comparisons between data will be required for that step of the surgical procedure. The surgical hub 2304 can be configured to automatically call up data screens based upon the step of the surgical procedure being performed, without waiting for the surgeon to ask for the particular information.
Another benefit includes checking for errors during the setup of the surgical procedure or during the course of the surgical procedure. For example, a situationally aware surgical hub 2304 could determine whether the operating theater is setup properly or optimally for the surgical procedure to be performed. The surgical hub 2304 can be configured to determine the type of surgical procedure being performed, retrieve the corresponding checklists, product location, or setup needs (e.g., from a memory), and then compare the current operating theater layout to the standard layout for the type of surgical procedure that the surgical hub 2304 determines is being performed. In one exemplification, the surgical hub 2304 can be configured to compare the list of items for the procedure (scanned by a scanner, for example) and/or a list of devices paired with the surgical hub 2304 to a recommended or anticipated manifest of items and/or devices for the given surgical procedure. If there are any discontinuities between the lists, the surgical hub 2304 can be configured to provide an alert indicating that a particular modular device 2302, patient monitoring device 2324, and/or other surgical item is missing. In one exemplification, the surgical hub 2304 can be configured to determine the relative distance or position of the modular devices 2302 and patient monitoring devices 2324 via proximity sensors, for example. The surgical hub 2304 can compare the relative positions of the devices to a recommended or anticipated layout for the particular surgical procedure. If there are any discontinuities between the layouts, the surgical hub 2304 can be configured to provide an alert indicating that the current layout for the surgical procedure deviates from the recommended layout.
As another example, a situationally aware surgical hub 2304 could determine whether the surgeon (or other medical personnel) was making an error or otherwise deviating from the expected course of action during the course of a surgical procedure. For example, the surgical hub 2304 can be configured to determine the type of surgical procedure being performed, retrieve the corresponding list of steps or order of equipment usage (e.g., from a memory), and then compare the steps being performed or the equipment being used during the course of the surgical procedure to the expected steps or equipment for the type of surgical procedure that the surgical hub 2304 determined is being performed. In one exemplification, the surgical hub 2304 can be configured to provide an alert indicating that an unexpected action is being performed or an unexpected device is being utilized at the particular step in the surgical procedure.
Overall, the situational awareness system for the surgical hub 2304 improves surgical procedure outcomes by adjusting the surgical instruments (and other modular devices 2302) for the particular context of each surgical procedure (such as adjusting to different tissue types) and validating actions during a surgical procedure. The situational awareness system also improves surgeons' efficiency in performing surgical procedures by automatically suggesting next steps, providing data, and adjusting displays and other modular devices 2302 in the surgical theater according to the specific context of the procedure.
ORs everywhere in the world are a tangled web of cords, devices, and people due to the amount of equipment required to perform surgical procedures. Surgical capital equipment tends to be a major contributor to this issue because most surgical capital equipment performs a single, specialized task. Due to their specialized nature and the surgeons' needs to utilize multiple different types of devices during the course of a single surgical procedure, an OR may be forced to be stocked with two or even more pieces of surgical capital equipment, such as energy generators. Each of these pieces of surgical capital equipment must be individually plugged into a power source and may be connected to one or more other devices that are being passed between OR personnel, creating a tangle of cords that must be navigated. Another issue faced in modern ORs is that each of these specialized pieces of surgical capital equipment has its own user interface and must be independently controlled from the other pieces of equipment within the OR. This creates complexity in properly controlling multiple different devices in connection with each other and forces users to be trained on and memorize different types of user interfaces (which may further change based upon the task or surgical procedure being performed, in addition to changing between each piece of capital equipment). This cumbersome, complex process can necessitate the need for even more individuals to be present within the OR and can create danger if multiple devices are not properly controlled in tandem with each other. Therefore, consolidating surgical capital equipment technology into singular systems that are able to flexibly address surgeons' needs to reduce the footprint of surgical capital equipment within ORs would simplify the user experience, reduce the amount of clutter in ORs, and prevent difficulties and dangers associated with simultaneously controlling multiple pieces of capital equipment. Further, making such systems expandable or customizable would allow for new technology to be conveniently incorporated into existing surgical systems, obviating the need to replace entire surgical systems or for OR personnel to learn new user interfaces or equipment controls with each new technology.
As described in
The modular energy system 2000 can be assembled from a variety of different modules 2001, some examples of which are illustrated in
The modular energy system 2000 can further include a variety of accessories 2029 that are connectable to the modules 2001 for controlling the functions thereof or that are otherwise configured to work on conjunction with the modular energy system 2000. The accessories 2029 can include, for example, a single-pedal footswitch 2032, a dual-pedal footswitch 2034, and a cart 2030 for supporting the modular energy system 2000 thereon. The footswitches 2032, 2034 can be configured to control the activation or function of particular energy modalities output by the energy module 2004, for example.
By utilizing modular components, the depicted modular energy system 2000 provides a surgical platform that grows with the availability of technology and is customizable to the needs of the facility and/or surgeons. Further, the modular energy system 2000 supports combo devices (e.g., dual electrosurgical and ultrasonic energy generators) and supports software-driven algorithms for customized tissue effects. Still further, the surgical system architecture reduces the capital footprint by combining multiple technologies critical for surgery into a single system.
The various modular components utilizable in connection with the modular energy system 2000 can include monopolar energy generators, bipolar energy generators, dual electrosurgical/ultrasonic energy generators, display screens, and various other modules and/or other components, some of which are also described above in connection with
Referring now to
Referring still to
As noted above, the modular energy system 2000 can be assembled into different configurations. Further, the different configurations of the modular energy system 2000 can also be utilizable for different surgical procedure types and/or different tasks. For example,
As noted above, the modular energy system 2000 can be communicably couplable to an external system, such as a surgical hub 2100 as illustrated in
Referring now to
In one aspect, the header module 2002 can include various physical controls 2011 in addition to or in lieu of the GUI 2008. Such physical controls 2011 can include, for example, a power button that controls the application of power to each module 2001 that is connected to the header module 2002 in the modular energy system 2000. Alternatively, the power button can be displayed as part of the GUI 2008. Therefore, the header module 2002 can serve as a single point of contact and obviate the need to individually activate and deactivate each individual module 2001 from which the modular energy system 2000 is constructed.
In one aspect, the header module 2002 can display still images, videos, animations, and/or information associated with the surgical modules 2001 of which the modular energy system 2000 is constructed or the surgical devices that are communicably coupled to the modular energy system 2000. The still images and/or videos displayed by the header module 2002 can be received from an endoscope or another visualization device that is communicably coupled to the modular energy system 2000. The animations and/or information of the GUI 2008 can be overlaid on or displayed adjacent to the images or video feed.
In one aspect, the modules 2001 other than the header module 2002 can be configured to likewise relay information to users. For example, the energy module 2004 can include light assemblies 2015 disposed about each of the ports of the port assembly 2012. The light assemblies 2015 can be configured to relay information to the user regarding the port according to their color or state (e.g., flashing). For example, the light assemblies 2015 can change from a first color to a second color when a plug is fully seated within the respective port. In one aspect, the color or state of the light assemblies 2015 can be controlled by the header module 2002. For example, the header module 2002 can cause the light assembly 2015 of each port to display a color corresponding to the color display for the port on the GUI 2008.
As illustrated in
In
The system control unit 3024, which may be referred to herein as a control circuit, control logic, microprocessor, microcontroller, logic, or FPGA, or various combinations thereof, is coupled to the system interface 3022 via energy interface 3026 and instrument communication interface 3028. The system interface 3022 is coupled to the first energy module 3004 via a first energy interface 3014 and a first instrument communication interface 3016. The system interface 3022 is coupled to the second energy module 3012 via a second energy interface 3018 and a second instrument communication interface 3020. As additional modules, such as additional energy modules, are stacked in the modular energy system 3000, additional energy and communications interfaces are provided between the system interface 3022 and the additional modules.
The energy modules 3004, 3012 are connectable to a hub and can be configured to generate electrosurgical energy (e.g., bipolar or monopolar), ultrasonic energy, or a combination thereof (referred to herein as an “advanced energy” module) for a variety of energy surgical instruments. Generally, the energy modules 3004, 3012 include hardware/software interfaces, an ultrasonic controller, an advanced energy RF controller, bipolar RF controller, and control algorithms executed by the controller that receives outputs from the controller and controls the operation of the various energy modules 3004, 3012 accordingly. In various aspects of the present disclosure, the controllers described herein may be implemented as a control circuit, control logic, microprocessor, microcontroller, logic, or FPGA, or various combinations thereof.
In some aspects, the various hub modules can include light piping around the physical ports to communicate instrument status and also connect on-screen elements to corresponding instruments. Light piping is one example of an illumination technique that may be employed to alert a user to a status of a surgical instrument attached/connected to a physical port. In one aspect, illuminating a physical port with a particular light directs a user to connect a surgical instrument to the physical port. In another example, illuminating a physical port with a particular light alerts a user to an error related an existing connection with a surgical instrument.
Turning to
In the illustrated example, the UI module 3030 includes a touchscreen 3046, a liquid crystal display 3048 (LCD), and audio output 3052 (e.g., speaker, buzzer). The UI processor 3040 is configured to receive touchscreen inputs from a touch controller 3044 coupled between the touch screen 3046 and the UI processor 3040. The UI processor 3040 is configured to output visual information to the LCD display 3048 and to output audio information the audio output 3052 via an audio amplifier 3050. The UI processor 3040 is configured to interface to the communications module 3032 via a switch 3042 coupled to the pass-through hub connector 3034 to receive, process, and forward data from the source device to the destination device and control data communication therebetween. DC power is supplied to the UI module 3030 via DC/DC converter modules 3054. The DC power is passed through the pass-through hub connector 3034 to the communications module 3032 through the power bus 3006. Data is passed through the pass-through hub connector 3034 to the communications module 3032 through the data bus 3008. Switches 3042, 3056 receive, process, and forward data from the source device to the destination device.
Continuing with
In some aspects, all of the modules (i.e., detachable hardware) are controlled by a single UI module 3030 that is disposed on or integral to a header module.
Turning to
DC power is received and transmitted by the energy module 3004 through the power bus 3006. The power bus 3006 is coupled to DC/DC converter modules 3138 to supply power to adjustable regulators 3084, 3107 and isolated DC/DC converter ports 3096, 3112, 3132.
In one aspect, the energy module 3004 can include an ultrasonic wideband amplifier 3086, which in one aspect may be a linear class H amplifier that is capable of generating arbitrary waveforms and drive harmonic transducers at low total harmonic distortion (THD) levels. The ultrasonic wideband amplifier 3086 is fed by a buck adjustable regulator 3084 to maximize efficiency and controlled by the controller 3082, which may be implemented as a digital signal processor (DSP) via a direct digital synthesizer (DDS), for example. The DDS can either be embedded in the DSP or implemented in the field-programmable gate array (FPGA), for example. The controller 3082 controls the ultrasonic wideband amplifier 3086 via a digital-to-analog converter 3106 (DAC). The output of the ultrasonic wideband amplifier 3086 is fed to an ultrasonic power transformer 3088, which is coupled to an ultrasonic energy output portion of an advanced energy receptacle 3100. Ultrasonic voltage (V) and current (I) feedback (FB) signals, which may be employed to compute ultrasonic impedance, are fed back to the controller 3082 via an ultrasonic VI FB transformer 3092 through an input portion of the advanced energy receptacle 3100. The ultrasonic voltage and current feedback signals are routed back to the controller 3082 through an analog-to-digital converter 3102 (A/D). Also coupled to the controller 3082 through the advanced energy receptacle 3100 is the isolated DC/DC converter port 3096, which receives DC power from the power bus 3006, and a medium bandwidth data port 3098.
In one aspect, the energy module 3004 can include a wideband RF power amplifier 3108, which in one aspect may be a linear class H amplifier that is capable of generating arbitrary waveforms and drive RF loads at a range of output frequencies. The wideband RF power amplifier 3108 is fed by an adjustable buck regulator 3107 to maximize efficiency and controlled by the controller 3082, which may be implemented as DSP via a DDS. The DDS can either be embedded in the DSP or implemented in the FPGA, for example. The controller 3082 controls the wideband RF amplifier 3086 via a DAC 3122. The output of the wideband RF power amplifier 3108 can be fed through RF selection relays 3124. The RF selection relays 3124 are configured to receive and selectively transmit the output signal of the wideband RF power amplifier 3108 to various other components of the energy module 3004. In one aspect, the output signal of the wideband RF power amplifier 3108 can be fed through RF selection relays 3124 to an RF power transformer 3110, which is coupled to an RF output portion of a bipolar RF energy receptacle 3118. Bipolar RF voltage (V) and current (I) feedback (FB) signals, which may be employed to compute RF impedance, are fed back to the controller 3082 via an RF VI FB transformer 3114 through an input portion of the bipolar RF energy receptacle 3118. The RF voltage and current feedback signals are routed back to the controller 3082 through an A/D 3120. Also coupled to the controller 3082 through the bipolar RF energy receptacle 3118 is the isolated DC/DC converter port 3112, which receives DC power from the power bus 3006, and a low bandwidth data port 3116.
As described above, in one aspect, the energy module 3004 can include RF selection relays 3124 driven by the controller 3082 (e.g., FPGA) at rated coil current for actuation and can also be set to a lower hold-current via pulse-width modulation (PWM) to limit steady-state power dissipation. Switching of the RF selection relays 3124 is achieved with force guided (safety) relays and the status of the contact state is sensed by the controller 3082 as a mitigation for any single fault conditions. In one aspect, the RF selection relays 3124 are configured to be in a first state, where an output RF signal received from an RF source, such as the wideband RF power amplifier 3108, is transmitted to a first component of the energy module 3004, such as the RF power transformer 3110 of the bipolar energy receptacle 3118. In a second aspect, the RF selection relays 3124 are configured to be in a second state, where an output RF signal received from an RF source, such as the wideband RF power amplifier 3108, is transmitted to a second component, such as an RF power transformer 3128 of a monopolar energy receptacle 3136, described in more detail below. In a general aspect, the RF selection relays 3124 are configured to be driven by the controller 3082 to switch between a plurality of states, such as the first state and the second state, to transmit the output RF signal received from the RF power amplifier 3108 between different energy receptacles of the energy module 3004.
As described above, the output of the wideband RF power amplifier 3108 can also fed through the RF selection relays 3124 to the wideband RF power transformer 3128 of the RF monopolar receptacle 3136. Monopolar RF voltage (V) and current (I) feedback (FB) signals, which may be employed to compute RF impedance, are fed back to the controller 3082 via an RF VI FB transformer 3130 through an input portion of the monopolar RF energy receptacle 3136. The RF voltage and current feedback signals are routed back to the controller 3082 through an A/D 3126. Also coupled to the controller 3082 through the monopolar RF energy receptacle 3136 is the isolated DC/DC converter port 3132, which receives DC power from the power bus 3006, and a low bandwidth data port 3134.
The output of the wideband RF power amplifier 3108 can also fed through the RF selection relays 3124 to the wideband RF power transformer 3090 of the advanced energy receptacle 3100. RF voltage (V) and current (I) feedback (FB) signals, which may be employed to compute RF impedance, are fed back to the controller 3082 via an RF VI FB transformer 3094 through an input portion of the advanced energy receptacle 3100. The RF voltage and current feedback signals are routed back to the controller 3082 through an A/D 3104.
The second energy module 3012 is coupled to the header module 3150 by connecting the pass-through hub connector 3078 to the pass-through hub connector 3152 of the header module 3150. In one aspect, the header module 3150 can include a header processor 3158 that is configured to manage a power button function 3166, software upgrades through the upgrade USB module 3162, system time management, and gateway to external networks (i.e., hospital or the cloud) via an Ethernet module 3164 that may be running different protocols. Data is received by the header module 3150 through the pass-through hub connector 3152. The header processor 3158 also is coupled to a switch 3160 to receive, process, and forward data from the source device to the destination device and control data communication therebetween. The header processor 3158 also is coupled to an OTS power supply 3156 coupled to a mains power entry module 3154.
The header power module 3172 includes a mains power entry module 3190 coupled to an OTS power supply unit 3192 (PSU). Low voltage direct current (e.g., 5V) standby power is supplied to the header/UI module 3002 and other modules through a low voltage power bus 3198 from the OTS PSU 3192. High voltage direct current (e.g., 60V) is supplied to the header/UI module 3002 through a high voltage bus 3200 from the OTS PSU 3192. The high voltage DC supplies DC/DC converter modules 3196 as well as isolated DC/DC converter modules 3236. A standby processor 3204 of the header/standby module 3184 provides a PSU/enable signal 3202 to the OTS PSU 3192.
The header wireless module 3174 includes a WiFi module 3212 and a Bluetooth module 3214. Both the WiFi module 3212 and the Bluetooth module 3214 are coupled to the header/UI controller 3170. The Bluetooth module 3214 is used to connect devices without using cables and the Wi-Fi module 3212 provides high-speed access to networks such as the Internet and can be employed to create a wireless network that can link multiple devices such as, for examples, multiple energy modules or other modules and surgical instruments, among other devices located in the operating room. Bluetooth is a wireless technology standard that is used to exchange data over short distances, such as, less than 30 feet.
The header USB module 3176 includes a USB port 3216 coupled to the header/UI controller 3170. The USB module 3176 provides a standard cable connection interface for modules and other electronics devices over short-distance digital data communications. The USB module 3176 allows modules comprising USB devices to be connected to each other with and transfer digital data over USB cables.
The header audio/screen module 3178 includes a touchscreen 3220 coupled to a touch controller 3218. The touch controller 3218 is coupled to the header/UI controller 3170 to read inputs from the touchscreen 3220. The header/UI controller 3170 drives an LCD display 3224 through a display/port video output signal 3222. The header/UI controller 3170 is coupled to an audio amplifier 3226 to drive one or more speakers 3228.
In one aspect, the header/UI module 3002 provides a touchscreen 3220 user interface configured to control modules connected to one control or header module 3002 in a modular energy system 3000. The touchscreen 3220 can be used to maintain a single point of access for the user to adjust all modules connected within the modular energy system 3000. Additional hardware modules (e.g., a smoke evacuation module) can appear at the bottom of the user interface LCD display 3224 when they become connected to the header/UI module 3002, and can disappear from the user interface LCD display 3224 when they are disconnected from the header/UI module 3002.
Further, the user touchscreen 3220 can provide access to the settings of modules attached to the modular energy system 3000. Further, the user interface LCD display 3224 arrangement can be configured to change according to the number and types of modules that are connected to the header/UI module 3002. For example, a first user interface can be displayed on the LCD display 3224 for a first application where one energy module and one smoke evacuation module are connected to the header/UI module 3002, and a second user interface can be displayed on the LCD display 3224 for a second application where two energy modules are connected to the header/UI module 3002. Further, the user interface can alter its display on the LCD display 3224 as modules are connected and disconnected from the modular energy system 3000.
In one aspect, the header/UI module 3002 provides a user interface LCD display 3224 configured to display on the LCD display coloring corresponds to the port lighting. In one aspect, the coloring of the instrument panel and the LED light around its corresponding port will be the same or otherwise correspond with each other. Each color can, for example, convey a unique meaning. This way, the user will be able to quickly assess which instrument the indication is referring to and the nature of the indication. Further, indications regarding an instrument can be represented by the changing of color of the LED light lined around its corresponding port and the coloring of its module. Still further, the message on screen and hardware/software port alignment can also serve to convey that an action must be taken on the hardware, not on the interface. In various aspects, all other instruments can be used while alerts are occurring on other instruments. This allows the user to be able to quickly assess which instrument the indication is referring to and the nature of the indication.
In one aspect, the header/UI module 3002 provides a user interface screen configured to display on the LCD display 3224 to present procedure options to a user. In one aspect, the user interface can be configured to present the user with a series of options (which can be arranged, e.g., from broad to specific). After each selection is made, the modular energy system 3000 presents the next level until all selections are complete. These settings could be managed locally and transferred via a secondary means (such as a USB thumb drive). Alternatively, the settings could be managed via a portal and automatically distributed to all connected systems in the hospital.
The procedure options can include, for example, a list of factory preset options categorized by specialty, procedure, and type of procedure. Upon completing a user selection, the header module can be configured to set any connected instruments to factory-preset settings for that specific procedure. The procedure options can also include, for example, a list of surgeons, then subsequently, the specialty, procedure, and type. Once a user completes a selection, the system may suggest the surgeon's preferred instruments and set those instrument's settings according to the surgeon's preference (i.e., a profile associated with each surgeon storing the surgeon's preferences).
In one aspect, the header/UI module 3002 provides a user interface screen configured to display on the LCD display 3224 critical instrument settings. In one aspect, each instrument panel displayed on the LCD display 3224 of the user interface corresponds, in placement and content, to the instruments plugged into the modular energy system 3000. When a user taps on a panel, it can expand to reveal additional settings and options for that specific instrument and the rest of the screen can, for example, darken or otherwise be de-emphasized.
In one aspect, the header/UI module 3002 provides an instrument settings panel of the user interface configured to comprise/display controls that are unique to an instrument and allow the user to increase or decrease the intensity of its output, toggle certain functions, pair it with system accessories like a footswitch connected to header footswitch module 3186, access advanced instrument settings, and find additional information about the instrument. In one aspect, the user can tap/select an “Advanced Settings” control to expand the advanced settings drawer displayed on the user interface LCD display 3224. In one aspect, the user can then tap/select an icon at the top right-hand corner of the instrument settings panel or tap anywhere outside of the panel and the panel will scale back down to its original state. In these aspects, the user interface is configured to display on the LCD display 3224 only the most critical instrument settings, such as power level and power mode, on the ready/home screen for each instrument panel. This is to maximize the size and readability of the system from a distance. In some aspects, the panels and the settings within can be scaled proportionally to the number of instruments connected to the system to further improve readability. As more instruments are connected, the panels scale to accommodate a greater amount of information.
The header network module 3180 includes a plurality of network interfaces 3264, 3266, 3268 (e.g., Ethernet) to network the header/UI module 3002 to other modules of the modular energy system 3000. In the illustrated example, one network interface 3264 may be a 3rd party network interface, another network interface 3266 may be a hospital network interface, and yet another network interface 3268 may be located on the backplane network interface connector 3182.
The header standby processor module 3184 includes a standby processor 3204 coupled to an On/Off switch 3210. The standby processor 3204 conducts an electrical continuity test by checking to see if electrical current flows in a continuity loop 3206. The continuity test is performed by placing a small voltage across the continuity loop 3206. A serial bus 3208 couples the standby processor 3204 to the backplane connector 3182.
The header footswitch module 3186 includes a controller 3240 coupled to a plurality of analog footswitch ports 3254, 3256, 3258 through a plurality of corresponding presence/ID and switch state modules 3242, 3244, 3246, respectively. The controller 3240 also is coupled to an accessory port 3260 via a presence/ID and switch state module 3248 and a transceiver module 3250. The accessory port 3260 is powered by an accessory power module 3252. The controller 3240 is coupled to header/UI controller 3170 via an isolated communication module 3234 and first and second safety critical control modules 3230, 3232. The header footswitch module 3186 also includes DC/DC converter modules 3238.
In one aspect, the header/UI module 3002 provides a user interface screen configured to display on the LCD display 3224 for controlling a footswitch connected to any one of the analog footswitch ports 3254, 3256, 3258. In some aspects, when the user plugs in a non hand-activated instrument into any one of the analog footswitch ports 3254, 3256, 3258, the instrument panel appears with a warning icon next to the footswitch icon. The instrument settings can be, for example, greyed out, as the instrument cannot be activated without a footswitch.
When the user plugs in a footswitch into any one of the analog footswitch ports 3254, 3256, 3258, a pop-up appears indicating that a footswitch has been assigned to that instrument. The footswitch icon indicates that a footswitch has been plugged in and assigned to the instrument. The user can then tap/select on that icon to assign, reassign, unassign, or otherwise change the settings associated with that footswitch. In these aspects, the system is configured to automatically assign footswitches to non hand-activated instruments using logic, which can further assign single or double-pedal footswitches to the appropriate instrument. If the user wants to assign/reassign footswitches manually there are two flows that can be utilized.
In one aspect, the header/UI module 3002 provides a global footswitch button. Once the user taps on the global footswitch icon (located in the upper right of the user interface LCD display 3224), the footswitch assignment overlay appears and the contents in the instrument modules dim. A (e.g., photo-realistic) representation of each attached footswitch (dual or single-pedal) appears on the bottom if unassigned to an instrument or on the corresponding instrument panel. Accordingly, the user can drag and drop these illustrations into, and out of, the boxed icons in the footswitch assignment overlay to assign, unassign, and reassign footswitches to their respective instruments.
In one aspect, the header/UI module 3002 provides a user interface screen displayed on the LCD display 3224 indicating footswitch auto-assignment, in accordance with at least one aspect of the present disclosure. As discussed above, the modular energy system 3000 can be configured to auto-assign a footswitch to an instrument that does not have hand activation. In some aspects, the header/UI module 3002 can be configured to correlate the colors displayed on the user interface LCD display 3224 to the lights on the modules themselves as means of tracking physical ports with user interface elements.
In one aspect, the header/UI module 3002 may be configured to depict various applications of the user interface with differing number of modules connected to the modular energy system 3000. In various aspects, the overall layout or proportion of the user interface elements displayed on the LCD display 3224 can be based on the number and type of instruments plugged into the header/UI module 3002. These scalable graphics can provide the means to utilize more of the screen for better visualization.
In one aspect, the header/UI module 3002 may be configured to depict a user interface screen on the LCD display 3224 to indicate which ports of the modules connected to the modular energy system 3000 are active. In some aspects, the header/UI module 3002 can be configured to illustrate active versus inactive ports by highlighting active ports and dimming inactive ports. In one aspect, ports can be represented with color when active (e.g., monopolar tissue cut with yellow, monopolar tissue coagulation with blue, bipolar tissue cut with blue, advanced energy tissue cut with warm white, and so on). Further, the displayed color will match the color of the light piping around the ports. The coloring can further indicate that the user cannot change settings of other instruments while an instrument is active. As another example, the header/UI module 3002 can be configured to depict the bipolar, monopolar, and ultrasonic ports of a first energy module as active and the monopolar ports of a second energy module as likewise active.
In one aspect, the header/UI module 3002 can be configured to depict a user interface screen on the LCD display 3224 to display a global settings menu. In one aspect, the header/UI module 3002 can be configured to display a menu on the LCD display 3224 to control global settings across any modules connected to the modular energy system 3000. The global settings menu can be, for example, always displayed in a consistent location (e.g., always available in upper right hand corner of main screen).
In one aspect, the header/UI module 3002 can be configured to depict a user interface screen on the LCD display 3224 configured to prevent changing of settings while a surgical instrument is in use. In one example, the header/UI module 3002 can be configured to prevent settings from being changed via a displayed menu when a connected instrument is active. The user interface screen can include, for example, an area (e.g., the upper left hand corner) that is reserved for indicating instrument activation while a settings menu is open. In one aspect, a user has opened the bipolar settings while monopolar coagulation is active. In one aspect, the settings menu could then be used once the activation is complete. In one aspect, the header/UI module 3002 can be is configured to never overlay any menus or other information over the dedicated area for indicating critical instrument information in order to maintain display of critical information.
In one aspect, the header/UI module 3002 can be configured to depict a user interface screen on the LCD display 3224 configured to display instrument errors. In one aspect, instrument error warnings may be displayed on the instrument panel itself, allowing user to continue to use other instruments while a nurse troubleshoots the error. This allows users to continue the surgery without the need to stop the surgery to debug the instrument.
In one aspect, the header/UI module 3002 can be configured to depict a user interface screen on the LCD display 3224 to display different modes or settings available for various instruments. In various aspects, the header/UI module 3002 can be configured to display settings menus that are appropriate for the type or application of surgical instrument(s) connected to the stack/hub. Each settings menu can provide options for different power levels, energy delivery profiles, and so on that are appropriate for the particular instrument type. In one aspect, the header/UI module 3002 can be configured to display different modes available for bipolar, monopolar cut, and monopolar coagulation applications.
In one aspect, the header/UI module 3002 can be configured to depict a user interface screen on the LCD display 3224 to display pre-selected settings. In one aspect, the header/UI module 3002 can be configured to receive selections for the instrument/device settings before plugging in instruments so that the modular energy system 3000 is ready before the patient enters the operating room. In one aspect, the user can simply click a port and then change the settings for that port. In the depicted aspect, the selected port appears as faded to indicate settings are set, but no instrument is plugged into that port.
DC power is received and transmitted by the energy module 3270 through the power bus 3006. The power bus 3006 is coupled to the DC/DC converter modules 3138 to supply power to adjustable regulators 3084, 3107 and isolated DC/DC converter ports 3096, 3112, 3132.
In one aspect, the energy module 3270 can include an ultrasonic wideband amplifier 3086, which in one aspect may be a linear class H amplifier that is capable of generating arbitrary waveforms and drive harmonic transducers at low total harmonic distortion (THD) levels. The ultrasonic wideband amplifier 3086 is fed by a buck adjustable regulator 3084 to maximize efficiency and controlled by the controller 3082, which may be implemented as a digital signal processor (DSP) via a direct digital synthesizer (DDS), for example. The DDS can either be embedded in the DSP or implemented in the field-programmable gate array (FPGA), for example. The controller 3082 controls the ultrasonic wideband amplifier 3086 via a digital-to-analog converter 3106 (DAC). The output of the ultrasonic wideband amplifier 3086 is fed to an ultrasonic power transformer 3088, which is coupled to an ultrasonic energy output portion of the advanced energy receptacle 3100. Ultrasonic voltage (V) and current (I) feedback (FB) signals, which may be employed to compute ultrasonic impedance, are fed back to the controller 3082 via an ultrasonic VI FB transformer 3092 through an input portion of the advanced energy receptacle 3100. The ultrasonic voltage and current feedback signals are routed back to the controller 3082 through an analog multiplexer 3280 and a dual analog-to-digital converter 3278 (A/D). In one aspect, the dual A/D 3278 has a sampling rate of 80 MSPS. Also coupled to the controller 3082 through the advanced energy receptacle 3100 is the isolated DC/DC converter port 3096, which receives DC power from the power bus 3006, and a medium bandwidth data port 3098.
In one aspect, the energy module 3270 can include a plurality of wideband RF power amplifiers 3108, 3286, 3288, among others, which in one aspect, each of the wideband RF power amplifiers 3108, 3286, 3288 may be linear class H amplifiers capable of generating arbitrary waveforms and drive RF loads at a range of output frequencies. Each of the wideband RF power amplifiers 3108, 3286, 3288 are fed by an adjustable buck regulator 3107 to maximize efficiency and controlled by the controller 3082, which may be implemented as DSP via a DDS. The DDS can either be embedded in the DSP or implemented in the FPGA, for example. The controller 3082 controls the first wideband RF power amplifier 3108 via a DAC 3122.
Unlike the energy modules 3004, 3012 shown and described in
The output of the first wideband RF power amplifier 3108 can be fed to an RF power transformer 3090, which is coupled to an RF output portion of an advanced energy receptacle 3100. RF voltage (V) and current (I) feedback (FB) signals, which may be employed to compute RF impedance, are fed back to the controller 3082 via RF VI FB transformers 3094 through an input portion of the advanced energy receptacle 3100. The RF voltage and current feedback signals are routed back to the controller 3082 through the RF VI FB transformers 3094, which are coupled to an analog multiplexer 3284 and a dual A/D 3282 coupled to the controller 3082. In one aspect, the dual A/D 3282 has a sampling rate of 80 MSPS.
The output of the second RF wideband power amplifier 3286 is fed through an RF power transformer 3128 of the RF monopolar receptacle 3136. Monopolar RF voltage (V) and current (I) feedback (FB) signals, which may be employed to compute RF impedance, are fed back to the controller 3082 via RF VI FB transformers 3130 through an input portion of the monopolar RF energy receptacle 3136. The RF voltage and current feedback signals are routed back to the controller 3082 through the analog multiplexer 3284 and the dual A/D 3282. Also coupled to the controller 3082 through the monopolar RF energy receptacle 3136 is the isolated DC/DC converter port 3132, which receives DC power from the power bus 3006, and a low bandwidth data port 3134.
The output of the third RF wideband power amplifier 3288 is fed through an RF power transformer 3110 of a bipolar RF receptacle 3118. Bipolar RF voltage (V) and current (I) feedback (FB) signals, which may be employed to compute RF impedance, are fed back to the controller 3082 via RF VI FB transformers 3114 through an input portion of the bipolar RF energy receptacle 3118. The RF voltage and current feedback signals are routed back to the controller 3082 through the analog multiplexer 3280 and the dual A/D 3278. Also coupled to the controller 3082 through the bipolar RF energy receptacle 3118 is the isolated DC/DC converter port 3112, which receives DC power from the power bus 3006, and a low bandwidth data port 3116.
A contact monitor 3290 is coupled to an NE receptacle 3292. Power is fed to the NE receptacle 3292 from the monopolar receptacle 3136.
In one aspect, with reference to
In one aspect, with reference to
In one aspect, with reference to
In one aspect, with reference to
As described in greater detail herein, a modular energy system comprises a header module and one or more functional or surgical modules. In various instances, the modular energy system is a modular energy system. In various instances, the surgical modules include energy modules, communication modules, user interface modules; however, the surgical modules are envisioned to be any suitable type of functional or surgical module for use with the modular energy system.
Modular energy system offers many advantages in a surgical procedure, as described above in connection with the modular energy systems 2000 (
In various aspects, as illustrated in
The modular energy system 6000 comprises a header module 6002 and an “N” number of surgical modules 6004, where “N” is an integer greater than or equal to one. In various examples, the modular energy system 6000 includes a UI module such as, for example, the UI module 3030 and/or a communication module such as, for example, the communication module 3032. Furthermore, pass-through hub connectors couple individual modules to one another in a stack configuration. In the example of
The modular energy system 6000 comprises an example power architecture that consists of a single AC/DC power supply 6003 that provides power to all the surgical modules in the stack. The AC/DC power supply 6003 is housed in the header module 6002, and utilizes a power backplane 6008 to distribute power to each module in the stack. The example of
In the example illustrated in
The primary power domain 6009 is the primary power source for the functional module-specific circuits 6013, 6014, 6015 of the modules 6002, 6004. It consists of a single voltage rail that is provided to every module. In at least one example, a nominal voltage of 60V can be selected to be higher than the local rails needed by any module, so that the modules can exclusively implement buck regulation, which is generally more efficient than boost regulation.
In various aspects, the primary power domain 6009 is controlled by the header module 6002. In certain instances, as illustrated in
In various aspects, as illustrated in
Furthermore, in certain examples, the modular energy system 6000 includes secondary, low speed, communication interface between modules for critical, power related functions including module power sequencing and module power status. The secondary communications interface can, for example, be a multi-drop Local Interconnect Network (LIN), where the header module is the master and all downstream modules are slaves.
In various aspects, as illustrated in
In various aspects, as illustrated in
Accordingly, a surgical instrument connected to surgical modules 6004 of a modular energy system 6000, in the stack configuration, receives therapeutic energy for tissue treatment that is generated by the surgical module 6004 from power delivered to the surgical module 6004 from the AC/DC power supply 6003 of the header module 6002.
In at least one example, while a header module 6002 is assembled in a stack configuration with a first surgical module 6004′, energy can flow from the AC/DC power supply 6003 to the first surgical module 6004′. Further, while a header module 6002 is assembled in a stack configuration with a first surgical module 6004′ (connected to the header module 6002) and a second surgical module 6004″ (connected to the first surgical module 6004′), energy can flow from the AC/DC power supply 6003 to the second surgical module 6004″ through the first surgical module 6004′.
The energy generated by the AC/DC power supply 6003 of the header module 6002 is transmitted through a segmented power backplane 6008 defined through the modular energy system 6000. In the example of
In the example of
In the example of
The modular energy system 6000 further includes a mitigated communications interface 6021 that includes a segmented communication backplane 6027 extending between the mitigated module controls 6023. The segmented communication backplane 6027 is similar in many respects to the segmented power backplane 6008. Mitigated Communication between the mitigated module controls 6023 of the header module 6002 and the surgical modules 6004 can be achieved through the segmented communication backplane 6027 defined through the modular energy system 6000. In the example of
Although the example of
Furthermore, the primary communications interface 6040 includes a segmented communication backplane 6031, which is similar in many respects to the segmented power backplane 6008. Communication between the header module 6002 and the surgical modules 6004 can be achieved through the segmented communication backplane 6031 defined through the modular energy system 6000. In the example of
In at least one example, as illustrated in
In various aspects, as illustrated in
Referring to
Referring to
Having described a general implementation the header and modules of modular energy systems 2000, 3000, 6000, the disclosure now turns to describe various aspects of other modular energy systems. The other modular energy systems are substantially similar to the modular energy system 2000, the modular energy system 3000, and/or the modular energy system 6000. For the sake of brevity, various details of the other modular energy systems being described in the following sections, which are similar to the modular energy system 2000, the modular energy system 3000, and/or the modular energy system 6000, are not repeated herein. Any aspect of the other modular energy systems described below can be brought into the modular energy system 2000, the modular energy system 3000, or the modular energy system 6000. In one aspect, the user interface mitigation techniques includes an audio identification double clocking data circuits and associated methods for modular energy system 2000, 3000, 6000 accessories. In another aspect, the user interface mitigation techniques includes mitigation circuits and associated methods for user interface (UI) displays for the modular energy system 2000. In another aspect, the present disclosure provides audio mitigation circuits and associated methods for using super-audible tones for the modular energy systems 2000, 3000, 6000.
In various aspects of the present disclosure, there is a need to identify and confirm audio that a system controller of the modular energy system 2000, 3000, 6000 is playing through a speaker. This may be desirable in audio mitigation techniques to confirm compliance with external standards. Thus, in various aspects, the present disclosure provides circuits and associated methods to uniquely identify a digital audio data stream sent by a controller of the modular energy system 2000, 3000, 6000 to the speakers and confirm that the proper audio data stream was generated by the controller of the modular energy system 2000, 3000, 6000.
Digital audio is often transmitted from a controller to an audio output device such as a Digital-to-Analog Converter (DAC) through a standard protocol called I2S. Those skilled in the art will appreciate that the I2S protocol, also known as an Integrated Inter-IC Sound Bus (I2S), is a serial bus interface standard used for connecting digital audio devices together. The I2S component operates in master mode only. In one aspect, the present disclosure utilizes sending additional data bits inside a standard I2S data frame that serves to identify a unique tone. This technique leverages the fact that most I2S-compatible DACs only consider data present in the audio stream on the rising edge of a clock signal. As such, additional data bits can be inserted in the audio data stream at the falling edge of the clock signal. The additional data bits will be ignored by the DAC but can be read by another controller for mitigation purposes.
The processor 4202 sends a digital audio clock signal 4256 and a data signal 4254 to the DAC/amplifier circuit 4220. In one aspect, the data signal 4254 and clock signal 4256 are transmitted to the DAC/amplifier circuit 4220 using a I2S protocol. The I2S-compatible DAC/amplifier circuit 4220 considers data present in the data signal 4254 on the rising edge of the clock signal 4256. This mode is a conventional data signal shown in the upper timing diagram 4250 shown in
Turning back to
Activation tones are employed to notify the user that the electrosurgical/ultrasonic instrument has been energized. In the instance that the audio software plays an incorrect tone (i.e., a “button click tone” instead of an “activation tone”), there is a need to mitigate the risk of outputting the wrong tone. In one aspect, risk mitigation may be accomplished by adding additional data bits in the I2S audio signal by the audio mitigation control module 4206 inside the standard I2S data frame. Thus the data signal comprises additional data bits that correspond to a unique tone identification that can be read by the audio mitigation control module 4206 on the falling edge of the clock signal as explained below in the description of
Turning now to the lower timing diagram 4260, in accordance with one aspect of the present disclosure, additional data bits are inserted between the audio data bits 4252 (10011011) shown in the upper timing diagram 4250, to generate a serial double data signal 4264. The serial double data signal 4264 comprises the audio data bits 4252 (10011011) (shown circled) plus unique tone identification data bits (11000001) (shown un-circled) inserted between the audio data bits 4252 (10011011) to form a unique series of data bits 4262 (1101001010001011). The audio data bits 4252 (10011011) are inserted on the rising edge 4268 of the clock signal 4266 (rising edge bits) and the unique tone identification data bits (11000001) are inserted on the falling edge 4269 of the clock signal 4266 (falling edge bits) to form the unique series of data bits 4262 (1101001010001011). The unique tone identification data bits (11000001) inserted on the falling edge 4269 of the clock signal 4266 identify the audio data bits 4252 (10011011) as the correct audio tone for the current operation of the electrosurgical/ultrasonic instrument. Audio bit-depth is not sacrificed. This technique leverages the fact that most I2S-compatible DACs only consider data bits present on the rising edge 4268 of the clock signal 4266. The unique tone identification data bits (11000001) can represent many unique tones and tone combinations and provides for future expandability. Accordingly, the audio mitigation control module 4206 can verify the tone defined by the audio data bits 4252 (10011011) using the unique tone identification data bits (11000001) to identify the audio data bits 4252 (10011011) that represent the audio tone. It will be appreciated that the audio data bits 4252 (10011011) will change on each sample so as to define an actual audio tone, whereas the unique tone identification data bits (11000001) will remain constant, identifying the tone throughout all of the changing audio samples.
Feeding back the serial double data signal 4264 and the clock signal 4266 to the audio mitigation control module 4276 provides an elegant solution and can be read by the audio mitigation control module 4276 as digital data without any extra hardware. The additional data bits read on the falling edge 4269 of the clock signal 4266 can represent many unique tones and tone combinations that provides for future expandability. Further, this technique provides assurance that tones are correctly sent to and played by the speakers 4234, 4236 without sacrificing audio bit-depth as all the audio data bits can be used for playing audio tones. Accordingly, if an incorrect tone is detected, based on knowing the expected tone due to a knowledge of what operations are taking place, or similar activity, the processor 4202 may present a fault to a user, cease the surgical functions, among other mitigating actions.
An energy generator component of the modular energy system 2000, 3000, 6000 may improperly generate a visual indication of instrument activation status on a user interface (UI) display as required by external standards. For example, to prevent the generation of an incorrect UI display, the present disclosure provides circuits and associated methods to actively confirm that a generated visual indication is appropriate and correct, thereby reducing or eliminating the risk of displaying an incorrect UI message or graphic. In one aspect, the present disclosure provides circuits and associated methods to monitor a copy of display signals to validate the entire display data-path.
In one general aspect, it may be necessary for an energy module 2004, 3004, 6004 component of the modular energy system 2000, 3000, 6000 to provide a visual indication of instrument activation status. In the modular energy system 2000, 3000, 6000 described herein, this may be accomplished, at least in part, by changing the graphics on a graphical display unit. In this instance, the modular energy system 2000, 3000, 6000 should ensure that the display state matches the instrument activation state at all times. There may be several points of failure in the display generation path: failure of the software creating the graphics may fail, the hardware display drivers may fail, any data conversion processes may malfunction, etc. In one aspect, the present disclosure comprises a header module 2002, 3003, 6002 of the modular energy system 2000, 3000, 6000 comprises a circuit which, if a risk analysis determines is necessary, is able to confirm proper operation of a significant portion of the data pathway to the display. A block diagram of such a circuit is described below.
DisplayPort-formatted data 4284 from the processor 4282 is applied to the DisplayPort to LVDS converter 4288 via a standard DisplayPort interface 4286. The LVDS data 4294, differential video signaling data, on channel-1 is provided to the UI display 4299 via line 4298. LVDS data 4296 on channel-2 is fed back to the processor via line 4290. As shown, the data 4294 on channel-1 is the same as the data on channel-2.
The processor 4282, which may be implemented as a system on a chip (SoC or the main processor in the header module 2002, 3004, 6004 of the modular energy system 2000, 3000, 6000) generates graphics internally in software, which is then driven out through the standard DisplayPort interface 4286. The DisplayPort-formatted data 4284 then is translated into an LVDS signal (standard display interface signaling) through a specialized onboard converter device such as the DisplayPort to LVDS converter circuit 4288. The output of the DisplayPort to LVDS converter circuit 4288 has two distinct display channels: channel-1 and channel-2, that may be utilized individually or in tandem. In one aspect, in accordance with the present disclosure, the DisplayPort to LVDS converter circuit 4288 connects one channel, e.g., channel-1, to the actual user display 4299 and connects the second channel, e.g., channel-2, back to the processor 4282 for interpretation of the LVDS data 4296. The DisplayPort to LVDS converter circuit 4288 is configured to “mirror” the channels (channel-1, channel-2) such that identical data is driven out of both output channels (channel-1, channel-2).
In this way, the processor 4282 confirms the operation of the DisplayPort to LVDS converter circuit 4288 using the LVDS signals on line 4290 carrying the LVDS data 4296 on channel-2, which change over time. If the LVDS signals on line 4290 remain static and do not alter state over time, the processor 4282 may conclude that something in the display path is malfunctioning. Further, in one aspect, the processor 4282 interprets the LVDS feedback signals to reconstruct the resulting image defined by the LVDS data 4296 on channel-2, which should be identical to the LVDS data 4294 on channel-1. The reconstructed resulting image can then be compared against an expected image to confirm that the DisplayPort data 4284 is correct, is being converted to LVDS data 4294, 4296 correctly, and that the image appearing on the screen of the UI display 4299 is appropriate for the given instrument activation state (or other surgical context).
In one aspect, the LVDS data 4296 on channel-2 is provided to a second processor that is different from the processor 4282. The LVDS data 4296 on channel-2 second provides a copy of the differential video signaling data to the second processor. The second processor is configured to determine whether the differential video signaling data on the second output channel is changing over time.
In
A first LVDS output 4340 of the DP-LVDS bridge circuit 4326 is coupled to a common mode filter 4328 to suppress EMI/RFI common mode noise on high speed differential serial Display Port lines and other high speed serial interfaces. The common mode filter 4328 may comprise a very large differential bandwidth to comply with standards and can protect and filter two differential lanes. A second LVDS output 4342 of the DP-LVDS bridge circuit 4326 is coupled to a system-on-chip 4334 (SoC). A pulse width modulation output 4336 (PWMO) of the DP-LVDS bridge circuit 4326 is coupled to the display panel via the display connector 4330. A backlight enable output 4338 of the DP-LVDS bridge circuit 4326 is also coupled to the display via a display connector 4330.
In various aspects, electrosurgical energy modules 2004, 3004, 6004 in a modular energy system 2000, 3000, 6000 use audio tones to indicate alarms, alerts, and energy activations. Audio feedback is part of a protocol to alert the user that the electrosurgical instrument has been energized by the energy module 2004, 3004, 6004 and is functioning properly. Accordingly, in one aspect, audio feedback protocols employ hardware/software mitigation techniques. One potential audio failure that requires mitigation is the possibility that the software plays an incorrect audio file. Accordingly, there is a need for hardware/software techniques for mixing audio files, where each file is checked against an expected asset.
In one aspect, the present disclosure provides a hardware/software technique that employs pre-processing of audio assets, where each audio asset is filtered to reserve a portion of the spectrum outside the audible range referred to herein s super-audible to indicate that the tones are in the upper ranges of the audio frequency spectrum. This super-audible range is divided into bins, where each bin can be allocated to a unique audio asset. The audio file may be mixed with a sine wave of the allocated identification (ID) frequency prior to being loaded into the energy module 2004, 3004, 6004 of the modular energy system 2000, 3000, 6000.
In one aspect, when the modular energy system 2000, 3000, 6000 software receives a request to play one or more than one audio file, the audio files are mixed (if necessary) and streamed to an audio amplifier, such as the DAC/amplifier circuit 4220 shown in
The programmable circuit may be configured to perform the following functions when audio is played:
1) Fetch from software expected audio data file unique identification numbers stored in a memory coupled to the processor;
2) Implement a filter to filter audio data to isolate the super-audible frequency range, where the filter may be a high pass or band pass filter;
3) Under-sample (decimate) the audio data down to baseband (0 Hz to max super-audible frequency) to enable a smaller fast Fourier transform (FFT) calculation without sacrificing bin size;
4) Calculate the FFT of the under-sampled data;
5) Perform a peak detect function on the FFT; and
6) Compare the peaks to expected super-audible unique identification tones.
Depending on the under-sampling factor, the frequencies may show up as Fs/2−tone_freq, as described hereinbelow.
In one aspect, the present disclosure provides circuits and associated methods for pre-processing audio assets of the energy module 2004, 3004, 6004 of the modular energy system 2000, 3000, 6000. In one aspect, a portion of the spectrum outside the audible range is reserved. For example, this reserved range may be selected as the frequency band of 20 kHz-24 kHz. The original audio assets outside the reserved band are low-pass filtered to remove any audio content within the reserved band. Unique super-audible tones are applied to each audio asset within the reserved band to serve as an ID. In one aspect, the reserved band audio assets are divided into 50 Hz bins to produce a total of 80 unique IDs. In another aspect, the reserved band audio assets are divided into 31.49 Hz bins, resulting in 256 unique IDs. In this way, the audio file contains the original audio asset within frequencies below the reserved band, in addition to unique super-audible tone or tones serving as unique IDs within the reserved band.
With reference also to the audio output circuit 4270 shown in
The filters 4226, 4228 may be high pass filter or band pass filters. In one implementation, the filter 4226, 4228 may be a band pass filter when using a class-D versus linear amplifier. A class-D amplifier produces a lot of high frequency artifacts that can be removed with a band pass filter. Filtering is performed prior to under-sampling. Subsequently, the audio data is under-sampled to “fold” the super-audible frequency band down to baseband. This technique enables a smaller FFT calculation without sacrificing bin size. Using peak detection, the presence of unique identification tones, as described in connection the lower timing diagram 4260 in
Example audio files are described hereinbelow with reference to
According to the method 4380, the audio mitigation control circuit 4276 is configured to receive 4384 the audio data 4264 transmitted from the processor 4202 to the audio amplifier 4220. The audio data is filtered 4386 by the filters 4226, 4228 to isolate a super-audible frequency range of the audio data. In various aspects, the filters 4226, 4228 may be implemented as band-pass filters or high-pass filters. The filtered audio data is sensed by the current amplifiers 4222, 4224 and converted to digital data by the ADCs 4216, 4218 and read by the audio mitigation control circuit 4276. The audio mitigation control circuit 4276 is further to configured to calculate 4388 a fast Fourier transform (FFT) on the received digital audio data in the isolated super-audible frequency range. The audio mitigation control circuit 4276 is further to configured to detect 4390 a super-audible tone in the FFT results by performing a peak detection function. The audio mitigation control circuit 4276 is further configured to compare 4392 the detected super-audible tone to the unique identification number, e.g., the unique tone identification data bits (11000001) (shown un-circled in
In various other aspect, the audio mitigation control circuit 4276 is further configured to under-sample the filtered audio data down to baseband and calculate a fast Fourier transform (FFT) on the under-sampled filtered audio data.
In one aspect, the audio assets may be divided into 50 Hz bins to produce a total of 80 unique identification numbers. In another aspect, the audio assets may be divided into 31.49 Hz bins to produce 256 unique identification numbers.
In one aspect, the audio mitigation control circuit 4276 may be configured to detect a mismatch between the expected audio file and the specific audio file transmitted to the audio amplifier and present a fault to a user interface, cease surgical functions based on the detected mismatch between the expected audio file and the specific audio file transmitted to the audio amplifier, or prevent surgical functions based on the detected mismatch between the expected audio file and the specific audio file transmitted to the audio amplifier.
Various aspects of the subject matter described herein are set out in the following numbered examples.
Example 1. An audio circuit, comprising: a processor configured to generate a digital audio signal, wherein the audio signal comprises audio data bits inserted on the rising edge of a clock signal and additional data bits inserted on a falling edge of the clock signal, wherein the audio data bits on the rising edge represent a digital audio tone and the additional data bits inserted on the falling edge represent a unique tone identification of the audio data bits on the rising edge; a digital-to-analog converter configured to: receive the digital audio signal; convert the audio data bits inserted on the rising edge; and ignore the additional data bits on the falling edge; an audio mitigation control module configured to: receive the digital audio signal; read the additional data bits on the falling edge; and confirm that the audio data bits inserted on the rising edge represent a correct digital audio tone based on the unique tone identification.
Example 2. The audio circuit of Example 1, wherein the audio mitigation control module is implemented in any one of software or hardware or a combination of software and hardware.
Example 3. The audio circuit of any one or more of Examples 1 through 2, further comprising an amplifier circuit coupled to the digital-to-analog converter.
Example 4. The audio circuit of any one or more of Examples 1 through 3, wherein the digital-to-analog converter comprises two analog output channels, wherein a first analog output channel is coupled to a first speaker and as second analog output channel is coupled to a second speaker.
Example 5. The audio circuit of Example 4, further comprising: a first current shunt coupled in series with the first speaker; and a second current shunt coupled in series with the second speaker.
Example 6. The audio circuit of Example 5, comprising: a first current sense amplifier having an input coupled to the first current shunt and an output coupled to an input of a first analog-to-digital converter (ADC); and a second current sense amplifier having an input coupled to the second current shunt and an output coupled to an input of a second ADC; wherein each output of the first and second ADCs is coupled to the audio mitigation control module.
Example 7. A circuit for mitigating a function of a user interface (UI) display of a modular energy system, the circuit comprising: a processor configured to couple to a surgical instrument; a display; and a video data converter circuit configured to receive formatted video data that represents an expected image to be displayed on the display and to provide differential video signaling data to the display and a copy of the differential video signaling data to the processor; wherein the processor is configured to determine whether the copy of the differential video signaling data is changing over time.
Example 8. The circuit of Example 7, wherein the video data converter circuit comprises an input channel coupled to the processor and first and second output channels; wherein the input channel is configured to receive the formatted video data from the processor; wherein the first output channel is coupled to the display to provide differential video signaling data to the display; and wherein the second output channel is coupled to the processor to provide the copy of the differential video signaling data to the processor.
Example 9. The circuit of Example 8, further comprising a second processor coupled to the second output channel, wherein the second processor is different from the processor; wherein the second output channel is configured to provide a copy of the differential video signaling data to the second processor; and wherein the second processor is configured to determine whether the differential video signaling data on the second output channel is changing over time.
Example 10. The circuit of any one or more of Examples 7 through 9, further comprising a video splitter circuit having an input channel and first and second output channels; wherein the video data converter circuit comprises an input channel coupled to the processor and an output channel coupled to the video splitter circuit; wherein the first output channel of the video splitter circuit is coupled to the display to provide differential video signaling data to the display; and wherein the second output channel of the video splitter circuit is coupled to the processor to provide the copy of the differential video signaling data to the processor.
Example 11. The circuit of Example 10, further comprising a second processor coupled to the second output channel of the video splitter circuit, wherein the second processor is different from the processor; wherein the second output channel of the video splitter circuit is configured to provide a copy of the differential video signaling data to the second processor; and wherein the second processor is configured to determine whether the differential video signaling data on the second output channel is changing over time.
Example 12. The circuit of any one or more of Examples 7 through 11, wherein the formatted video data is DisplayPort formatted data.
Example 13. The circuit of any one or more of Examples 7 through 12, wherein the video data converter is configured to convert the formatted video data to low voltage differential signaling data.
Example 14. The circuit of any one or more of Examples 7 through 13, wherein the video data converter circuit comprises a driver circuit coupled to a bridge circuit.
Example 15. The circuit of any one or more of Examples 7 through 14, wherein the processor is configured to reconstruct an image based on the differential video signaling data on the second output channel.
Example 16. The circuit of Example 15, wherein the processor is configured to: compare the reconstructed image to the expected image; and enable activation of the surgical instrument based on a match between the reconstructed image and the expected image.
Example 17. The circuit of any one or more of Examples 15 through 16, wherein the processor is configured to: compare the reconstructed image to the expected image; and disable activation of the surgical instrument based on a mismatch between the reconstructed image and the expected image.
Example 18. The circuit of any one or more of Examples 7 through 17, wherein the processor is configured to disable activation of the surgical instrument based on the differential video signaling data on the second output channel not changing over time when expected.
Example 19. A method of mitigating a function of a user interface (UI) display of a modular energy system, the method comprising: receiving, by a video data converter circuit, formatted video data at an input channel of the video data converter circuit, wherein the input channel is coupled to a processor and the formatted video data represents an expected image to be displayed on a display, the video data converter having two output channels, wherein a first output channel is coupled to the display and a second output channel is coupled back to the processor, wherein the processor is configured to couple to a surgical instrument; providing, by the video data converter circuit, differential video signaling data to the display from the first output channel of the video data converter circuit; providing, by the video data converter circuit, a copy of the differential video signaling data to the processor from the second output channel; and determining, by the processor, whether the differential video signaling data on the second output channel is changing over time.
Example 20. The method of Example 19, comprising reconstructing, by the processor, an image based on the differential video signaling data on the second output channel.
Example 21. The method of Example 20, comprising: comparing, by the processor, the reconstructed image to the expected image; and enabling, by the processor, activation of the surgical instrument based on a match between the reconstructed image and the expected image.
Example 22. The method of any one or more of Examples 20 through 21, comprising: comparing, by the processor, the reconstructed image to the expected image; and disable, by the processor, activation of the surgical instrument based on a mismatch between the reconstructed image and the expected image.
Example 23. The method of any one or more of Examples 19 through 22, comprising disabling, by the processor, activation of the surgical instrument based on the differential video signaling data on the second output channel not changing over time when expected.
Example 24. An audio circuit, comprising: a processor; an audio amplifier coupled to the processor by audio data lines; an audio mitigation control circuit coupled to the processor and the audio amplifier, a digital-to-analog converter (DAC) comprising a first analog output channel coupled to a first speaker; a first current shunt coupled in series with the first speaker; a first current sense amplifier having an input coupled to the first current shunt and an output coupled to an input of a first analog-to-digital converter (ADC); and wherein the output of the first ADC is coupled to the audio mitigation control module; wherein the audio mitigation control circuit is configured to: fetch, from a memory coupled to the audio mitigation control circuit, a unique identification number to identify an expected audio file, the audio file comprising audio data comprising an audio asset and a unique super-audible tone to identify the audio asset; receive the audio data from the output of the first ADC; filter the audio data to isolate a super-audible frequency range of the audio data; calculate a fast Fourier transform (FFT) on the audio data in the isolated super-audible frequency range; perform a peak detection function on the FFT results to detect a super-audible tone; compare the detected super-audible tone to the unique identification number to identify the expected audio file; and determine a specific audio file transmitted to the audio amplifier based on the comparison.
Example 25. The audio circuit of Example 24, wherein the audio mitigation control circuit is configured to under-sample the filtered audio data down to baseband.
Example 26. The audio circuit of Example 25, wherein the audio mitigation control circuit is configured to calculate a fast Fourier transform (FFT) on the under-sampled filtered audio data.
Example 27. The audio circuit of any one or more of Examples 24 through 26, wherein the audio assets are divided into 50 Hz bins to produce a total of 80 unique identification numbers.
Example 28. The audio circuit of any one or more of Examples 24 through 27, wherein the audio assets are divided into 31.49 Hz bins to produce 256 unique identification numbers.
Example 29. The audio circuit of any one or more of Examples 24 through 28, wherein the audio mitigation control circuit is configured to detect a mismatch between the expected audio file and the specific audio file transmitted to the audio amplifier and present a fault to a user interface.
Example 30. The audio circuit of Example 29, wherein the audio mitigation control circuit is configured to cease surgical functions based on the detected mismatch between the expected audio file and the specific audio file transmitted to the audio amplifier.
Example 31. The audio circuit of any one or more of Examples 29 through 30, wherein the audio mitigation control circuit is configured to prevent surgical functions based on the detected mismatch between the expected audio file and the specific audio file transmitted to the audio amplifier.
Example 32. The audio circuit of any one or more of Examples 24 through 31, wherein the filter is implemented as a band-pass filter.
Example 33. The audio circuit of any one or more of Examples 24 through 32, wherein the filter is implemented as a high-pass filter.
Example 34. The audio circuit of any one or more of Examples 24 through 33, wherein the DAC comprises a second analog output channel; the audio circuit further comprising: a second speaker coupled to the second analog channel of the DAC; a second current shunt coupled in series with the second speaker; a second ADC; a second current sense amplifier having an input coupled to the second current shunt and an output coupled to an input of the second ADC; wherein the output of the second ADC is coupled to the audio mitigation control module; and wherein the audio mitigation control circuit is configured to receive the audio data from the output of the second ADC.
Example 35. An audio circuit, comprising: a processor; an audio amplifier coupled to the processor by audio data lines; an audio mitigation control circuit coupled to the processor and the audio amplifier, wherein the audio mitigation control circuit is configured to: fetch, from a memory coupled to the audio mitigation control circuit, a unique identification number to identify an expected audio file, the audio file comprising audio data comprising an audio asset and a unique super-audible tone to identify the audio asset; receive the audio data transmitted from the processor to the audio amplifier; filter the audio data to isolate a super-audible frequency range of the audio data; calculate a fast Fourier transform (FFT) on the audio data in the isolated super-audible frequency range; perform a peak detection function on the FFT results to detect a super-audible tone; compare the detected super-audible tone to the unique identification number to identify the expected audio file; and determine a specific audio file transmitted to the audio amplifier based on the comparison.
While several forms have been illustrated and described, it is not the intention of Applicant to restrict or limit the scope of the appended claims to such detail. Numerous modifications, variations, changes, substitutions, combinations, and equivalents to those forms may be implemented and will occur to those skilled in the art without departing from the scope of the present disclosure. Moreover, the structure of each element associated with the described forms can be alternatively described as a means for providing the function performed by the element. Also, where materials are disclosed for certain components, other materials may be used. It is therefore to be understood that the foregoing description and the appended claims are intended to cover all such modifications, combinations, and variations as falling within the scope of the disclosed forms. The appended claims are intended to cover all such modifications, variations, changes, substitutions, modifications, and equivalents.
The foregoing detailed description has set forth various forms of the devices and/or processes via the use of block diagrams, flowcharts, and/or examples. Insofar as such block diagrams, flowcharts, and/or examples contain one or more functions and/or operations, it will be understood by those within the art that each function and/or operation within such block diagrams, flowcharts, and/or examples can be implemented, individually and/or collectively, by a wide range of hardware, software, firmware, or virtually any combination thereof. Those skilled in the art will recognize that some aspects of the forms disclosed herein, in whole or in part, can be equivalently implemented in integrated circuits, as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or as virtually any combination thereof, and that designing the circuitry and/or writing the code for the software and or firmware would be well within the skill of one of skill in the art in light of this disclosure. In addition, those skilled in the art will appreciate that the mechanisms of the subject matter described herein are capable of being distributed as one or more program products in a variety of forms, and that an illustrative form of the subject matter described herein applies regardless of the particular type of signal bearing medium used to actually carry out the distribution.
Instructions used to program logic to perform various disclosed aspects can be stored within a memory in the system, such as dynamic random access memory (DRAM), cache, flash memory, or other storage. Furthermore, the instructions can be distributed via a network or by way of other computer readable media. Thus a machine-readable medium may include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer), but is not limited to, floppy diskettes, optical disks, compact disc, read-only memory (CD-ROMs), and magneto-optical disks, read-only memory (ROMs), random access memory (RAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic or optical cards, flash memory, or a tangible, machine-readable storage used in the transmission of information over the Internet via electrical, optical, acoustical or other forms of propagated signals (e.g., carrier waves, infrared signals, digital signals, etc.). Accordingly, the non-transitory computer-readable medium includes any type of tangible machine-readable medium suitable for storing or transmitting electronic instructions or information in a form readable by a machine (e.g., a computer).
As used in any aspect herein, the term “control circuit” may refer to, for example, hardwired circuitry, programmable circuitry (e.g., a computer processor including one or more individual instruction processing cores, processing unit, processor, microcontroller, microcontroller unit, controller, digital signal processor (DSP), programmable logic device (PLD), programmable logic array (PLA), or field programmable gate array (FPGA)), state machine circuitry, firmware that stores instructions executed by programmable circuitry, and any combination thereof. The control circuit may, collectively or individually, be embodied as circuitry that forms part of a larger system, for example, an integrated circuit (IC), an application-specific integrated circuit (ASIC), a system on-chip (SoC), desktop computers, laptop computers, tablet computers, servers, smart phones, etc. Accordingly, as used herein “control circuit” includes, but is not limited to, electrical circuitry having at least one discrete electrical circuit, electrical circuitry having at least one integrated circuit, electrical circuitry having at least one application specific integrated circuit, electrical circuitry forming a general purpose computing device configured by a computer program (e.g., a general purpose computer configured by a computer program which at least partially carries out processes and/or devices described herein, or a microprocessor configured by a computer program which at least partially carries out processes and/or devices described herein), electrical circuitry forming a memory device (e.g., forms of random access memory), and/or electrical circuitry forming a communications device (e.g., a modem, communications switch, or optical-electrical equipment). Those having skill in the art will recognize that the subject matter described herein may be implemented in an analog or digital fashion or some combination thereof.
As used in any aspect herein, the term “logic” may refer to an app, software, firmware and/or circuitry configured to perform any of the aforementioned operations. Software may be embodied as a software package, code, instructions, instruction sets and/or data recorded on non-transitory computer readable storage medium. Firmware may be embodied as code, instructions or instruction sets and/or data that are hard-coded (e.g., nonvolatile) in memory devices.
As used in any aspect herein, the terms “component,” “system,” “module” and the like can refer to a computer-related entity, either hardware, a combination of hardware and software, software, or software in execution.
As used in any aspect herein, an “algorithm” refers to a self-consistent sequence of steps leading to a desired result, where a “step” refers to a manipulation of physical quantities and/or logic states which may, though need not necessarily, take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It is common usage to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like. These and similar terms may be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities and/or states.
A network may include a packet switched network. The communication devices may be capable of communicating with each other using a selected packet switched network communications protocol. One example communications protocol may include an Ethernet communications protocol which may be capable permitting communication using a Transmission Control Protocol/Internet Protocol (TCP/IP). The Ethernet protocol may comply or be compatible with the Ethernet standard published by the Institute of Electrical and Electronics Engineers (IEEE) titled “IEEE 802.3 Standard”, published in December, 2008 and/or later versions of this standard. Alternatively or additionally, the communication devices may be capable of communicating with each other using an X.25 communications protocol. The X.25 communications protocol may comply or be compatible with a standard promulgated by the International Telecommunication Union-Telecommunication Standardization Sector (ITU-T). Alternatively or additionally, the communication devices may be capable of communicating with each other using a frame relay communications protocol. The frame relay communications protocol may comply or be compatible with a standard promulgated by Consultative Committee for International Telegraph and Telephone (CCITT) and/or the American National Standards Institute (ANSI). Alternatively or additionally, the transceivers may be capable of communicating with each other using an Asynchronous Transfer Mode (ATM) communications protocol. The ATM communications protocol may comply or be compatible with an ATM standard published by the ATM Forum titled “ATM-MPLS Network Interworking 2.0” published August 2001, and/or later versions of this standard. Of course, different and/or after-developed connection-oriented network communication protocols are equally contemplated herein.
Unless specifically stated otherwise as apparent from the foregoing disclosure, it is appreciated that, throughout the foregoing disclosure, discussions using terms such as “processing,” “computing,” “calculating,” “determining,” “displaying,” or the like, refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.
One or more components may be referred to herein as “configured to,” “configurable to,” “operable/operative to,” “adapted/adaptable,” “able to,” “conformable/conformed to,” etc. Those skilled in the art will recognize that “configured to” can generally encompass active-state components and/or inactive-state components and/or standby-state components, unless context requires otherwise.
The terms “proximal” and “distal” are used herein with reference to a clinician manipulating the handle portion of the surgical instrument. The term “proximal” refers to the portion closest to the clinician and the term “distal” refers to the portion located away from the clinician. It will be further appreciated that, for convenience and clarity, spatial terms such as “vertical”, “horizontal”, “up”, and “down” may be used herein with respect to the drawings. However, surgical instruments are used in many orientations and positions, and these terms are not intended to be limiting and/or absolute.
Those skilled in the art will recognize that, in general, terms used herein, and especially in the appended claims (e.g., bodies of the appended claims) are generally intended as “open” terms (e.g., the term “including” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “having at least,” the term “includes” should be interpreted as “includes but is not limited to,” etc.). It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, as an aid to understanding, the following appended claims may contain usage of the introductory phrases “at least one” and “one or more” to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles “a” or “an” limits any particular claim containing such introduced claim recitation to claims containing only one such recitation, even when the same claim includes the introductory phrases “one or more” or “at least one” and indefinite articles such as “a” or “an” (e.g., “a” and/or “an” should typically be interpreted to mean “at least one” or “one or more”); the same holds true for the use of definite articles used to introduce claim recitations.
In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should typically be interpreted to mean at least the recited number (e.g., the bare recitation of “two recitations,” without other modifiers, typically means at least two recitations, or two or more recitations). Furthermore, in those instances where a convention analogous to “at least one of A, B, and C, etc.” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., “a system having at least one of A, B, and C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.). In those instances where a convention analogous to “at least one of A, B, or C, etc.” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., “a system having at least one of A, B, or C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.). It will be further understood by those within the art that typically a disjunctive word and/or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms unless context dictates otherwise. For example, the phrase “A or B” will be typically understood to include the possibilities of “A” or “B” or “A and B.”
With respect to the appended claims, those skilled in the art will appreciate that recited operations therein may generally be performed in any order. Also, although various operational flow diagrams are presented in a sequence(s), it should be understood that the various operations may be performed in other orders than those which are illustrated, or may be performed concurrently. Examples of such alternate orderings may include overlapping, interleaved, interrupted, reordered, incremental, preparatory, supplemental, simultaneous, reverse, or other variant orderings, unless context dictates otherwise. Furthermore, terms like “responsive to,” “related to,” or other past-tense adjectives are generally not intended to exclude such variants, unless context dictates otherwise.
It is worthy to note that any reference to “one aspect,” “an aspect,” “an exemplification,” “one exemplification,” and the like means that a particular feature, structure, or characteristic described in connection with the aspect is included in at least one aspect. Thus, appearances of the phrases “in one aspect,” “in an aspect,” “in an exemplification,” and “in one exemplification” in various places throughout the specification are not necessarily all referring to the same aspect. Furthermore, the particular features, structures or characteristics may be combined in any suitable manner in one or more aspects.
Any patent application, patent, non-patent publication, or other disclosure material referred to in this specification and/or listed in any Application Data Sheet is incorporated by reference herein, to the extent that the incorporated materials is not inconsistent herewith. As such, and to the extent necessary, the disclosure as explicitly set forth herein supersedes any conflicting material incorporated herein by reference. Any material, or portion thereof, that is said to be incorporated by reference herein, but which conflicts with existing definitions, statements, or other disclosure material set forth herein will only be incorporated to the extent that no conflict arises between that incorporated material and the existing disclosure material.
In summary, numerous benefits have been described which result from employing the concepts described herein. The foregoing description of the one or more forms has been presented for purposes of illustration and description. It is not intended to be exhaustive or limiting to the precise form disclosed. Modifications or variations are possible in light of the above teachings. The one or more forms were chosen and described in order to illustrate principles and practical application to thereby enable one of ordinary skill in the art to utilize the various forms and with various modifications as are suited to the particular use contemplated. It is intended that the claims submitted herewith define the overall scope.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4171700 | Farin | Oct 1979 | A |
| 4378801 | Oosten | Apr 1983 | A |
| 4640279 | Beard | Feb 1987 | A |
| 4849752 | Bryant | Jul 1989 | A |
| D303787 | Messenger et al. | Oct 1989 | S |
| 5041110 | Fleenor | Aug 1991 | A |
| D327061 | Soren et al. | Jun 1992 | S |
| 5189277 | Boisvert et al. | Feb 1993 | A |
| 5204669 | Dorfe et al. | Apr 1993 | A |
| 5318563 | Malis et al. | Jun 1994 | A |
| 5325270 | Wenger et al. | Jun 1994 | A |
| 5383880 | Hooven | Jan 1995 | A |
| 5395033 | Byrne et al. | Mar 1995 | A |
| 5425375 | Chin et al. | Jun 1995 | A |
| 5613158 | Savage | Mar 1997 | A |
| D379346 | Mieki | May 1997 | S |
| 5667517 | Hooven | Sep 1997 | A |
| 5690504 | Scanlan et al. | Nov 1997 | A |
| 5693042 | Boiarski et al. | Dec 1997 | A |
| 5724468 | Leone et al. | Mar 1998 | A |
| 5788688 | Bauer et al. | Aug 1998 | A |
| 5817119 | Klieman et al. | Oct 1998 | A |
| 5849020 | Long et al. | Dec 1998 | A |
| 5865361 | Milliman et al. | Feb 1999 | A |
| 5872481 | Sevic et al. | Feb 1999 | A |
| 5901150 | Jhuboo et al. | May 1999 | A |
| 5910139 | Cochran et al. | Jun 1999 | A |
| 5941846 | Duffy et al. | Aug 1999 | A |
| 6019745 | Gray | Feb 2000 | A |
| 6049467 | Tamarkin et al. | Apr 2000 | A |
| 6055062 | Dina et al. | Apr 2000 | A |
| 6055458 | Cochran et al. | Apr 2000 | A |
| D431811 | Nishio et al. | Oct 2000 | S |
| 6179136 | Kluge et al. | Jan 2001 | B1 |
| 6269411 | Reasoner | Jul 2001 | B1 |
| 6273750 | Malkowski, Jr. | Aug 2001 | B1 |
| 6288606 | Ekman et al. | Sep 2001 | B1 |
| H2037 | Yates et al. | Jul 2002 | H |
| 6416471 | Kumar et al. | Jul 2002 | B1 |
| 6546270 | Goldin et al. | Apr 2003 | B1 |
| 6584358 | Carter et al. | Jun 2003 | B2 |
| 6611793 | Burnside et al. | Aug 2003 | B1 |
| 6731514 | Evans | May 2004 | B2 |
| 6760218 | Fan | Jul 2004 | B2 |
| 6839238 | Derr et al. | Jan 2005 | B2 |
| 6843657 | Driscoll et al. | Jan 2005 | B2 |
| 6888848 | Beshal et al. | May 2005 | B2 |
| 6913471 | Smith | Jul 2005 | B2 |
| 7009511 | Mazar et al. | Mar 2006 | B2 |
| 7044949 | Orszulak et al. | May 2006 | B2 |
| 7074205 | Duffy et al. | Jul 2006 | B1 |
| 7134994 | Alpert et al. | Nov 2006 | B2 |
| 7171784 | Eenigenburg | Feb 2007 | B2 |
| 7217269 | El-Galley et al. | May 2007 | B2 |
| 7252664 | Nasab et al. | Aug 2007 | B2 |
| 7268684 | Tethrake et al. | Sep 2007 | B2 |
| 7331699 | Gawalkiewicz et al. | Feb 2008 | B2 |
| 7344532 | Goble et al. | Mar 2008 | B2 |
| 7353068 | Tanaka et al. | Apr 2008 | B2 |
| D575792 | Benson | Aug 2008 | S |
| 7408439 | Wang et al. | Aug 2008 | B2 |
| D579876 | Novotney et al. | Nov 2008 | S |
| D583328 | Chiang | Dec 2008 | S |
| 7496418 | Kim et al. | Feb 2009 | B2 |
| D589447 | Sasada et al. | Mar 2009 | S |
| 7500747 | Howell et al. | Mar 2009 | B2 |
| 7518502 | Austin et al. | Apr 2009 | B2 |
| 7563259 | Takahashi | Jul 2009 | B2 |
| 7601149 | DiCarlo et al. | Oct 2009 | B2 |
| 7637907 | Blaha | Dec 2009 | B2 |
| 7656671 | Liu et al. | Feb 2010 | B2 |
| 7695485 | Whitman et al. | Apr 2010 | B2 |
| 7757028 | Druke et al. | Jul 2010 | B2 |
| D631252 | Leslie | Jan 2011 | S |
| 7932826 | Fritchie et al. | Apr 2011 | B2 |
| 7945065 | Menzl et al. | May 2011 | B2 |
| 7945342 | Tsai et al. | May 2011 | B2 |
| 7982776 | Dunki-Jacobs et al. | Jul 2011 | B2 |
| 7995045 | Dunki-Jacobs | Aug 2011 | B2 |
| 8019094 | Hsieh et al. | Sep 2011 | B2 |
| 8057492 | Ortiz et al. | Nov 2011 | B2 |
| D655678 | Kobayashi et al. | Mar 2012 | S |
| D657368 | Magee et al. | Apr 2012 | S |
| 8187263 | Behnke et al. | May 2012 | B2 |
| 8218279 | Liao et al. | Jul 2012 | B2 |
| 8239066 | Jennings et al. | Aug 2012 | B2 |
| D667838 | Magee et al. | Sep 2012 | S |
| D675164 | Kobayashi et al. | Jan 2013 | S |
| D676392 | Gassauer | Feb 2013 | S |
| D678196 | Miyauchi et al. | Mar 2013 | S |
| D678304 | Yakoub et al. | Mar 2013 | S |
| 8423182 | Robinson et al. | Apr 2013 | B2 |
| D687146 | Juzkiw et al. | Jul 2013 | S |
| 8504136 | Sun et al. | Aug 2013 | B1 |
| 8540709 | Allen | Sep 2013 | B2 |
| 8551088 | Falkenstein et al. | Oct 2013 | B2 |
| 8567393 | Hickle et al. | Oct 2013 | B2 |
| D704839 | Juzkiw et al. | May 2014 | S |
| 8795001 | Lam et al. | Aug 2014 | B1 |
| 8819581 | Nakamura et al. | Aug 2014 | B2 |
| 8840609 | Stuebe | Sep 2014 | B2 |
| D716333 | Chotin et al. | Oct 2014 | S |
| 8911437 | Horlle et al. | Dec 2014 | B2 |
| 8917513 | Hazzard | Dec 2014 | B1 |
| 8920186 | Shishikura | Dec 2014 | B2 |
| 8923012 | Kaufman et al. | Dec 2014 | B2 |
| 8961441 | Cloanta et al. | Feb 2015 | B2 |
| 8968296 | McPherson | Mar 2015 | B2 |
| 8986288 | Konishi | Mar 2015 | B2 |
| 9017326 | DiNardo et al. | Apr 2015 | B2 |
| D729267 | Yoo et al. | May 2015 | S |
| 9055870 | Meador et al. | Jun 2015 | B2 |
| 9065394 | Lim et al. | Jun 2015 | B2 |
| 9129054 | Nawana et al. | Sep 2015 | B2 |
| 9160853 | Daddi et al. | Oct 2015 | B1 |
| 9168054 | Turner et al. | Oct 2015 | B2 |
| 9168091 | Janssen et al. | Oct 2015 | B2 |
| 9198711 | Joseph | Dec 2015 | B2 |
| 9226766 | Aldridge et al. | Jan 2016 | B2 |
| 9226791 | McCarthy et al. | Jan 2016 | B2 |
| 9237921 | Messerly et al. | Jan 2016 | B2 |
| 9265429 | St. Pierre et al. | Feb 2016 | B2 |
| 9277961 | Panescu et al. | Mar 2016 | B2 |
| 9277969 | Brannan et al. | Mar 2016 | B2 |
| 9281615 | Plaza et al. | Mar 2016 | B1 |
| 9320646 | Todd et al. | Apr 2016 | B2 |
| 9345481 | Hall et al. | May 2016 | B2 |
| 9345900 | Wu et al. | May 2016 | B2 |
| 9351653 | Harrison | May 2016 | B1 |
| 9370361 | Viola et al. | Jun 2016 | B2 |
| 9391670 | Brukalo et al. | Jul 2016 | B2 |
| 9427255 | Griffith et al. | Aug 2016 | B2 |
| 9430438 | Biskup | Aug 2016 | B2 |
| 9463646 | Payne et al. | Oct 2016 | B2 |
| 9474565 | Shikhman et al. | Oct 2016 | B2 |
| D772252 | Myers et al. | Nov 2016 | S |
| 9486271 | Dunning | Nov 2016 | B2 |
| 9491895 | Steeves et al. | Nov 2016 | B2 |
| 9532827 | Morgan et al. | Jan 2017 | B2 |
| 9589720 | Akahane | Mar 2017 | B2 |
| 9600031 | Kaneko et al. | Mar 2017 | B2 |
| 9603277 | Morgan et al. | Mar 2017 | B2 |
| D783675 | Yagisawa et al. | Apr 2017 | S |
| D784270 | Bhattacharya | Apr 2017 | S |
| 9666974 | Bopp | May 2017 | B2 |
| 9713503 | Goldschmidt | Jul 2017 | B2 |
| 9715271 | Kaestner | Jul 2017 | B2 |
| 9750563 | Shikhman et al. | Sep 2017 | B2 |
| 9770103 | Cochran et al. | Sep 2017 | B2 |
| 9773093 | Bernini et al. | Sep 2017 | B2 |
| 9782214 | Houser et al. | Oct 2017 | B2 |
| 9788907 | Alvi et al. | Oct 2017 | B1 |
| 9804977 | Ghosh et al. | Oct 2017 | B2 |
| D806721 | Fischer | Jan 2018 | S |
| 9867670 | Brannan et al. | Jan 2018 | B2 |
| 9892483 | Lee et al. | Feb 2018 | B2 |
| 9892564 | Cvetko et al. | Feb 2018 | B1 |
| 9907196 | Susini et al. | Feb 2018 | B2 |
| 9971395 | Chenault et al. | Apr 2018 | B2 |
| 9974595 | Anderson et al. | May 2018 | B2 |
| 9987068 | Anderson et al. | Jun 2018 | B2 |
| 9987072 | McPherson | Jun 2018 | B2 |
| 10028402 | Walker | Jul 2018 | B1 |
| 10039589 | Virshek et al. | Aug 2018 | B2 |
| D832211 | Ladd et al. | Oct 2018 | S |
| 10098527 | Weisenburgh et al. | Oct 2018 | B2 |
| 10105470 | Reasoner et al. | Oct 2018 | B2 |
| 10109835 | Yang | Oct 2018 | B2 |
| D834541 | You et al. | Nov 2018 | S |
| 10117702 | Danziger et al. | Nov 2018 | B2 |
| 10128612 | Casto | Nov 2018 | B1 |
| 10136954 | Johnson et al. | Nov 2018 | B2 |
| 10137245 | Melker et al. | Nov 2018 | B2 |
| 10147148 | Wu et al. | Dec 2018 | B2 |
| 10166061 | Berry et al. | Jan 2019 | B2 |
| 10170205 | Curd et al. | Jan 2019 | B2 |
| 10201365 | Boudreaux et al. | Feb 2019 | B2 |
| 10339496 | Matson et al. | Jul 2019 | B2 |
| 10357184 | Crawford et al. | Jul 2019 | B2 |
| 10386990 | Shikhman et al. | Aug 2019 | B2 |
| 10441345 | Aldridge et al. | Oct 2019 | B2 |
| 10449004 | Ferro et al. | Oct 2019 | B2 |
| 10475244 | Cvetko et al. | Nov 2019 | B2 |
| 10493287 | Yoder et al. | Dec 2019 | B2 |
| 10499847 | Latimer et al. | Dec 2019 | B2 |
| 10499996 | de Almeida Barreto | Dec 2019 | B2 |
| 10523122 | Han et al. | Dec 2019 | B2 |
| 10531579 | Hsiao et al. | Jan 2020 | B2 |
| D876466 | Kobayashi et al. | Feb 2020 | S |
| 10561753 | Thompson et al. | Feb 2020 | B2 |
| 10602007 | Takano | Mar 2020 | B2 |
| 10624667 | Faller et al. | Apr 2020 | B2 |
| 10624691 | Wiener et al. | Apr 2020 | B2 |
| 10675027 | Aldridge et al. | Jun 2020 | B2 |
| 10675100 | Frushour | Jun 2020 | B2 |
| 10687884 | Wiener et al. | Jun 2020 | B2 |
| 10729502 | Wolf et al. | Aug 2020 | B1 |
| 10743872 | Leimbach et al. | Aug 2020 | B2 |
| 10758309 | Chow et al. | Sep 2020 | B1 |
| 10758310 | Shelton, IV et al. | Sep 2020 | B2 |
| 10772673 | Allen, IV et al. | Sep 2020 | B2 |
| 10878966 | Wolf et al. | Dec 2020 | B2 |
| 10881399 | Shelton, IV et al. | Jan 2021 | B2 |
| 10898256 | Yates et al. | Jan 2021 | B2 |
| 10898279 | Yang | Jan 2021 | B2 |
| 10925598 | Scheib et al. | Feb 2021 | B2 |
| 10932705 | Muhsin et al. | Mar 2021 | B2 |
| 10932772 | Shelton, IV et al. | Mar 2021 | B2 |
| 10950982 | Regnier et al. | Mar 2021 | B2 |
| 10987176 | Poltaretskyi et al. | Apr 2021 | B2 |
| 10989724 | Holmes et al. | Apr 2021 | B1 |
| 11000270 | Scheib et al. | May 2021 | B2 |
| D924139 | Jayme | Jul 2021 | S |
| 11056244 | Shelton, IV et al. | Jul 2021 | B2 |
| 11065079 | Wolf et al. | Jul 2021 | B2 |
| 11071595 | Johnson et al. | Jul 2021 | B2 |
| D928725 | Oberkircher et al. | Aug 2021 | S |
| D928726 | Asher et al. | Aug 2021 | S |
| 11077312 | Sturman et al. | Aug 2021 | B2 |
| 11083489 | Fujii et al. | Aug 2021 | B2 |
| 11116587 | Wolf et al. | Sep 2021 | B2 |
| 11185379 | Shuma et al. | Nov 2021 | B2 |
| D939545 | Oberkircher et al. | Dec 2021 | S |
| 11259793 | Scheib et al. | Mar 2022 | B2 |
| 11259875 | Boutin et al. | Mar 2022 | B2 |
| 11272839 | Al-All et al. | Mar 2022 | B2 |
| 11284963 | Shelton, IV et al. | Mar 2022 | B2 |
| 11296540 | Kirleis et al. | Apr 2022 | B2 |
| 11304763 | Shelton, IV et al. | Apr 2022 | B2 |
| 11314846 | Colin et al. | Apr 2022 | B1 |
| 11369366 | Scheib et al. | Jun 2022 | B2 |
| 11382699 | Wassall et al. | Jul 2022 | B2 |
| 11382700 | Calloway et al. | Jul 2022 | B2 |
| 11419604 | Scheib et al. | Aug 2022 | B2 |
| 11424027 | Shelton, IV | Aug 2022 | B2 |
| 11432877 | Nash et al. | Sep 2022 | B2 |
| 11464581 | Calloway | Oct 2022 | B2 |
| 11478820 | Bales, Jr. et al. | Oct 2022 | B2 |
| 11504192 | Shelton, IV et al. | Nov 2022 | B2 |
| 11510750 | Dulin et al. | Nov 2022 | B2 |
| 11559307 | Shelton, IV et al. | Jan 2023 | B2 |
| 11564678 | Scheib et al. | Jan 2023 | B2 |
| 11571205 | Scheib et al. | Feb 2023 | B2 |
| 11576677 | Shelton, IV et al. | Feb 2023 | B2 |
| 11589888 | Shelton, IV et al. | Feb 2023 | B2 |
| 11659023 | Shelton, IV et al. | May 2023 | B2 |
| 11712309 | Barak et al. | Aug 2023 | B2 |
| 20010029315 | Sakurai et al. | Oct 2001 | A1 |
| 20010031975 | Whitman et al. | Oct 2001 | A1 |
| 20020022836 | Goble et al. | Feb 2002 | A1 |
| 20020052563 | Penn et al. | May 2002 | A1 |
| 20020148942 | Payne et al. | Oct 2002 | A1 |
| 20020151770 | Noll et al. | Oct 2002 | A1 |
| 20020183734 | Bommannan et al. | Dec 2002 | A1 |
| 20030007321 | Dayley | Jan 2003 | A1 |
| 20030040670 | Govari | Feb 2003 | A1 |
| 20030050654 | Whitman et al. | Mar 2003 | A1 |
| 20030078631 | Nelson et al. | Apr 2003 | A1 |
| 20030093103 | Malackowski et al. | May 2003 | A1 |
| 20030114851 | Truckal et al. | Jun 2003 | A1 |
| 20030130677 | Whitman et al. | Jul 2003 | A1 |
| 20030199794 | Sakurai et al. | Oct 2003 | A1 |
| 20030199864 | Eick | Oct 2003 | A1 |
| 20040030328 | Eggers et al. | Feb 2004 | A1 |
| 20040059323 | Sturm et al. | Mar 2004 | A1 |
| 20040094597 | Whitman et al. | May 2004 | A1 |
| 20040111045 | Sullivan et al. | Jun 2004 | A1 |
| 20040111081 | Whitman et al. | Jun 2004 | A1 |
| 20040153724 | Nicholson et al. | Aug 2004 | A1 |
| 20040164983 | Khozai | Aug 2004 | A1 |
| 20050010209 | Lee et al. | Jan 2005 | A1 |
| 20050013459 | Maekawa | Jan 2005 | A1 |
| 20050021026 | Baily | Jan 2005 | A1 |
| 20050070800 | Takahashi | Mar 2005 | A1 |
| 20050113815 | Ritchie et al. | May 2005 | A1 |
| 20050113823 | Reschke et al. | May 2005 | A1 |
| 20050127868 | Calhoon et al. | Jun 2005 | A1 |
| 20050127869 | Calhoon et al. | Jun 2005 | A1 |
| 20050131390 | Heinrich et al. | Jun 2005 | A1 |
| 20050159778 | Heinrich et al. | Jul 2005 | A1 |
| 20050165390 | Mauti | Jul 2005 | A1 |
| 20050173490 | Shelton, IV | Aug 2005 | A1 |
| 20050229110 | Gegner et al. | Oct 2005 | A1 |
| 20050251233 | Kanzius | Nov 2005 | A1 |
| 20060020213 | Whitman et al. | Jan 2006 | A1 |
| 20060085049 | Cory et al. | Apr 2006 | A1 |
| 20060136622 | Rouvelin et al. | Jun 2006 | A1 |
| 20060149418 | Anvari | Jul 2006 | A1 |
| 20060212069 | Shelton, IV | Sep 2006 | A1 |
| 20060256516 | Cho | Nov 2006 | A1 |
| 20060278680 | Viola et al. | Dec 2006 | A1 |
| 20060278681 | Viola et al. | Dec 2006 | A1 |
| 20060289600 | Wales et al. | Dec 2006 | A1 |
| 20070061393 | Moore | Mar 2007 | A1 |
| 20070076363 | Liang et al. | Apr 2007 | A1 |
| 20070085602 | Park et al. | Apr 2007 | A1 |
| 20070136218 | Bauer et al. | Jun 2007 | A1 |
| 20070282321 | Shah et al. | Dec 2007 | A1 |
| 20080072896 | Setzer et al. | Mar 2008 | A1 |
| 20080090652 | Kuehling et al. | Apr 2008 | A1 |
| 20080129465 | Rao | Jun 2008 | A1 |
| 20080249377 | Molducci et al. | Oct 2008 | A1 |
| 20080316304 | Claus et al. | Dec 2008 | A1 |
| 20090036884 | Gregg et al. | Feb 2009 | A1 |
| 20090054908 | Zand et al. | Feb 2009 | A1 |
| 20090101692 | Whitman et al. | Apr 2009 | A1 |
| 20090131929 | Shimizu | May 2009 | A1 |
| 20090216091 | Arndt | Aug 2009 | A1 |
| 20090228024 | Whitfield et al. | Sep 2009 | A1 |
| 20090234352 | Behnke et al. | Sep 2009 | A1 |
| 20090273353 | Kroh et al. | Nov 2009 | A1 |
| 20100036405 | Giordano et al. | Feb 2010 | A1 |
| 20100069939 | Konishi | Mar 2010 | A1 |
| 20100076453 | Morris et al. | Mar 2010 | A1 |
| 20100092006 | Rosen | Apr 2010 | A1 |
| 20100120266 | Rimborg | May 2010 | A1 |
| 20100198200 | Horvath | Aug 2010 | A1 |
| 20100312239 | Sclig | Dec 2010 | A1 |
| 20110015660 | Wiener et al. | Jan 2011 | A1 |
| 20110092972 | Allen | Apr 2011 | A1 |
| 20110093796 | Plummer et al. | Apr 2011 | A1 |
| 20110106567 | Asher | May 2011 | A1 |
| 20110125149 | El-Galley et al. | May 2011 | A1 |
| 20110130689 | Cohen et al. | Jun 2011 | A1 |
| 20110238063 | Gregg | Sep 2011 | A1 |
| 20110245630 | St. Pierre et al. | Oct 2011 | A1 |
| 20110273465 | Konishi et al. | Nov 2011 | A1 |
| 20110288451 | Sanai et al. | Nov 2011 | A1 |
| 20110306840 | Allen et al. | Dec 2011 | A1 |
| 20120029304 | Medina et al. | Feb 2012 | A1 |
| 20120116380 | Madan et al. | May 2012 | A1 |
| 20120132661 | Gu et al. | May 2012 | A1 |
| 20120319890 | McCormack et al. | Dec 2012 | A1 |
| 20130031201 | Kagan et al. | Jan 2013 | A1 |
| 20130176220 | Merschon et al. | Jul 2013 | A1 |
| 20130197503 | Orszulak | Aug 2013 | A1 |
| 20130267975 | Timm et al. | Oct 2013 | A1 |
| 20130268283 | Vann et al. | Oct 2013 | A1 |
| 20140009894 | Yu | Jan 2014 | A1 |
| 20140058714 | Boyer | Feb 2014 | A1 |
| 20140087573 | Kroeckel | Mar 2014 | A1 |
| 20140097903 | Aoki et al. | Apr 2014 | A1 |
| 20140108048 | Cohn | Apr 2014 | A1 |
| 20140155721 | Hauck et al. | Jun 2014 | A1 |
| 20140194683 | Nakaguchi | Jul 2014 | A1 |
| 20140226572 | Thota et al. | Aug 2014 | A1 |
| 20140262598 | Miki et al. | Sep 2014 | A1 |
| 20140263552 | Hall et al. | Sep 2014 | A1 |
| 20140378958 | Leussler | Dec 2014 | A1 |
| 20150190189 | Yates et al. | Jul 2015 | A1 |
| 20150272575 | Leimbach et al. | Oct 2015 | A1 |
| 20150289929 | Toth et al. | Oct 2015 | A1 |
| 20150300923 | Halbert | Oct 2015 | A1 |
| 20150334879 | Fricker | Nov 2015 | A1 |
| 20150373115 | Breakstone et al. | Dec 2015 | A1 |
| 20160000495 | Elliott et al. | Jan 2016 | A1 |
| 20160045247 | Heim et al. | Feb 2016 | A1 |
| 20160045365 | Foster et al. | Feb 2016 | A1 |
| 20160058286 | Joshua et al. | Mar 2016 | A1 |
| 20160062954 | Ruff et al. | Mar 2016 | A1 |
| 20160074096 | Lieu | Mar 2016 | A1 |
| 20160120591 | Smith et al. | May 2016 | A1 |
| 20160164466 | Briffa et al. | Jun 2016 | A1 |
| 20160199240 | Newkirk et al. | Jul 2016 | A1 |
| 20160225192 | Jones et al. | Aug 2016 | A1 |
| 20160249945 | Shelton, IV et al. | Sep 2016 | A1 |
| 20160287312 | Tegg et al. | Oct 2016 | A1 |
| 20160287337 | Aram et al. | Oct 2016 | A1 |
| 20170000553 | Wiener et al. | Jan 2017 | A1 |
| 20170007146 | Schulhauser et al. | Jan 2017 | A1 |
| 20170024978 | Gulrez et al. | Jan 2017 | A1 |
| 20170078455 | Fisher et al. | Mar 2017 | A1 |
| 20170080346 | Abbas | Mar 2017 | A1 |
| 20170090507 | Wiener et al. | Mar 2017 | A1 |
| 20170151011 | Brustad et al. | Jun 2017 | A1 |
| 20170189096 | Danziger et al. | Jul 2017 | A1 |
| 20170202595 | Shelton, IV | Jul 2017 | A1 |
| 20170209718 | Tanis et al. | Jul 2017 | A1 |
| 20170251305 | Fathollahi | Aug 2017 | A1 |
| 20170252091 | Honda | Sep 2017 | A1 |
| 20170296213 | Swensgard et al. | Oct 2017 | A1 |
| 20170319259 | Dunning | Nov 2017 | A1 |
| 20170360466 | Brown et al. | Dec 2017 | A1 |
| 20180014872 | Dickerson | Jan 2018 | A1 |
| 20180042659 | Rupp et al. | Feb 2018 | A1 |
| 20180049795 | Swayze et al. | Feb 2018 | A1 |
| 20180065248 | Barral et al. | Mar 2018 | A1 |
| 20180078216 | Baker et al. | Mar 2018 | A1 |
| 20180082480 | White et al. | Mar 2018 | A1 |
| 20180099161 | Honda | Apr 2018 | A1 |
| 20180166809 | Brogan et al. | Jun 2018 | A1 |
| 20180206909 | Brustad et al. | Jul 2018 | A1 |
| 20180221005 | Hamel et al. | Aug 2018 | A1 |
| 20180228528 | Fraasch et al. | Aug 2018 | A1 |
| 20180239856 | Takeuchi et al. | Aug 2018 | A1 |
| 20180262916 | Polley et al. | Sep 2018 | A1 |
| 20180263557 | Kahlman | Sep 2018 | A1 |
| 20180296283 | Crawford et al. | Oct 2018 | A1 |
| 20180333207 | Moctezuma De la Barrera | Nov 2018 | A1 |
| 20180367870 | Shih | Dec 2018 | A1 |
| 20190000478 | Messerly et al. | Jan 2019 | A1 |
| 20190069957 | Barral et al. | Mar 2019 | A1 |
| 20190125455 | Shelton, IV et al. | May 2019 | A1 |
| 20190200844 | Shelton, IV et al. | Jul 2019 | A1 |
| 20190200906 | Shelton, IV et al. | Jul 2019 | A1 |
| 20190200981 | Harris et al. | Jul 2019 | A1 |
| 20190201102 | Shelton, IV et al. | Jul 2019 | A1 |
| 20190201140 | Yates et al. | Jul 2019 | A1 |
| 20190201158 | Shelton, IV et al. | Jul 2019 | A1 |
| 20190206563 | Shelton, IV et al. | Jul 2019 | A1 |
| 20190224434 | Silver et al. | Jul 2019 | A1 |
| 20190236840 | Zuckerman et al. | Aug 2019 | A1 |
| 20190247141 | Batchelor et al. | Aug 2019 | A1 |
| 20190247664 | Irazoqui et al. | Aug 2019 | A1 |
| 20190269457 | Schofield et al. | Sep 2019 | A1 |
| 20190278262 | Taylor et al. | Sep 2019 | A1 |
| 20190279524 | Stoyanov et al. | Sep 2019 | A1 |
| 20190348169 | Gibby et al. | Nov 2019 | A1 |
| 20190371012 | Flexman et al. | Dec 2019 | A1 |
| 20200004487 | Hanajima et al. | Jan 2020 | A1 |
| 20200015899 | Scheib et al. | Jan 2020 | A1 |
| 20200015900 | Scheib et al. | Jan 2020 | A1 |
| 20200015907 | Scheib | Jan 2020 | A1 |
| 20200015924 | Scheib et al. | Jan 2020 | A1 |
| 20200030044 | Wang et al. | Jan 2020 | A1 |
| 20200038120 | Ziraknejad et al. | Feb 2020 | A1 |
| 20200078070 | Henderson et al. | Mar 2020 | A1 |
| 20200078071 | Asher | Mar 2020 | A1 |
| 20200078076 | Henderson et al. | Mar 2020 | A1 |
| 20200078077 | Henderson et al. | Mar 2020 | A1 |
| 20200078078 | Henderson et al. | Mar 2020 | A1 |
| 20200078079 | Morgan et al. | Mar 2020 | A1 |
| 20200078080 | Henderson et al. | Mar 2020 | A1 |
| 20200078081 | Jayme et al. | Mar 2020 | A1 |
| 20200078082 | Henderson et al. | Mar 2020 | A1 |
| 20200078083 | Sprinkle et al. | Mar 2020 | A1 |
| 20200078089 | Henderson et al. | Mar 2020 | A1 |
| 20200078106 | Henderson et al. | Mar 2020 | A1 |
| 20200078110 | Henderson et al. | Mar 2020 | A1 |
| 20200078111 | Oberkircher et al. | Mar 2020 | A1 |
| 20200078112 | Henderson et al. | Mar 2020 | A1 |
| 20200078113 | Sawhney et al. | Mar 2020 | A1 |
| 20200078114 | Asher et al. | Mar 2020 | A1 |
| 20200078115 | Asher et al. | Mar 2020 | A1 |
| 20200078116 | Oberkircher et al. | Mar 2020 | A1 |
| 20200078117 | Henderson et al. | Mar 2020 | A1 |
| 20200078118 | Henderson et al. | Mar 2020 | A1 |
| 20200078119 | Henderson et al. | Mar 2020 | A1 |
| 20200078120 | Aldridge et al. | Mar 2020 | A1 |
| 20200081585 | Petre et al. | Mar 2020 | A1 |
| 20200090808 | Carroll et al. | Mar 2020 | A1 |
| 20200100825 | Henderson et al. | Apr 2020 | A1 |
| 20200100830 | Henderson et al. | Apr 2020 | A1 |
| 20200106220 | Henderson et al. | Apr 2020 | A1 |
| 20200129223 | Angeles et al. | Apr 2020 | A1 |
| 20200159313 | Gibby et al. | May 2020 | A1 |
| 20200237422 | Canady | Jul 2020 | A1 |
| 20200265398 | Lembo | Aug 2020 | A1 |
| 20200268472 | Wolf et al. | Aug 2020 | A1 |
| 20200305924 | Carroll | Oct 2020 | A1 |
| 20200305945 | Morgan et al. | Oct 2020 | A1 |
| 20200314569 | Morgan et al. | Oct 2020 | A1 |
| 20200342228 | Prevrhal et al. | Oct 2020 | A1 |
| 20200405375 | Shelton, IV et al. | Dec 2020 | A1 |
| 20210121246 | Gudalo | Apr 2021 | A1 |
| 20210169578 | Calloway et al. | Jun 2021 | A1 |
| 20210196383 | Shelton, IV et al. | Jul 2021 | A1 |
| 20210203889 | Fung et al. | Jul 2021 | A1 |
| 20210212717 | Yates et al. | Jul 2021 | A1 |
| 20210236755 | King et al. | Aug 2021 | A1 |
| 20210264680 | Cvetko et al. | Aug 2021 | A1 |
| 20210313938 | Tanaka et al. | Oct 2021 | A1 |
| 20210338343 | Swaffield et al. | Nov 2021 | A1 |
| 20210385889 | Pate | Dec 2021 | A1 |
| 20220032442 | Sheffield et al. | Feb 2022 | A1 |
| 20220104867 | Shelton, IV et al. | Apr 2022 | A1 |
| 20220104896 | Shelton, IV et al. | Apr 2022 | A1 |
| 20220104897 | Shelton, IV et al. | Apr 2022 | A1 |
| 20220104911 | Shelton, IV et al. | Apr 2022 | A1 |
| 20220151704 | Nikou | May 2022 | A1 |
| 20220155910 | Jeong | May 2022 | A1 |
| 20220261056 | Motol et al. | Aug 2022 | A1 |
| 20220313338 | Carroll et al. | Oct 2022 | A1 |
| 20220313341 | Wiener et al. | Oct 2022 | A1 |
| 20220313342 | Leuck et al. | Oct 2022 | A1 |
| 20220313357 | Geresy et al. | Oct 2022 | A1 |
| 20220313369 | Oberkircher et al. | Oct 2022 | A1 |
| 20220313370 | Morgan et al. | Oct 2022 | A1 |
| 20220313372 | Herman et al. | Oct 2022 | A1 |
| 20220313373 | Morgan et al. | Oct 2022 | A1 |
| 20220317750 | Jayme et al. | Oct 2022 | A1 |
| 20220317751 | Samuel et al. | Oct 2022 | A1 |
| 20220318179 | Morgan et al. | Oct 2022 | A1 |
| 20220319685 | Vachon et al. | Oct 2022 | A1 |
| 20220319693 | Oberkircher et al. | Oct 2022 | A1 |
| 20220321059 | Samuel et al. | Oct 2022 | A1 |
| 20220322523 | Jayme et al. | Oct 2022 | A1 |
| 20220331013 | Shelton, IV et al. | Oct 2022 | A1 |
| 20220331047 | Shelton, IV et al. | Oct 2022 | A1 |
| 20220331048 | Shelton, IV et al. | Oct 2022 | A1 |
| 20220331049 | Shelton, IV et al. | Oct 2022 | A1 |
| 20220331050 | Shelton, IV et al. | Oct 2022 | A1 |
| 20220331051 | Shelton, IV et al. | Oct 2022 | A1 |
| 20220331052 | Shelton, IV et al. | Oct 2022 | A1 |
| 20220331053 | Kimball et al. | Oct 2022 | A1 |
| 20220331054 | Kimball et al. | Oct 2022 | A1 |
| 20220331056 | Shelton, IV et al. | Oct 2022 | A1 |
| 20220334787 | Jogan et al. | Oct 2022 | A1 |
| 20220335604 | Vanosdoll et al. | Oct 2022 | A1 |
| 20220335660 | Shelton, IV et al. | Oct 2022 | A1 |
| 20220335696 | Shelton, IV et al. | Oct 2022 | A1 |
| 20220336078 | Wise et al. | Oct 2022 | A1 |
| 20220336097 | Shelton, IV et al. | Oct 2022 | A1 |
| 20220337891 | Burnley et al. | Oct 2022 | A1 |
| 20220338049 | Ross et al. | Oct 2022 | A1 |
| 20230038130 | Cvetko et al. | Feb 2023 | A1 |
| 20230039037 | Henderson et al. | Feb 2023 | A1 |
| 20230069787 | Henderson et al. | Mar 2023 | A1 |
| 20230072423 | Osborn et al. | Mar 2023 | A1 |
| 20230346446 | Henderson et al. | Nov 2023 | A1 |
| Number | Date | Country |
|---|---|---|
| 0408160 | Jan 1991 | EP |
| 0473987 | Mar 1992 | EP |
| 0929263 | Jul 1999 | EP |
| 1006892 | Jun 2009 | EP |
| 2942023 | Nov 2015 | EP |
| S635457 | Jan 1988 | JP |
| H8280706 | Oct 1996 | JP |
| H1069453 | Mar 1998 | JP |
| 2000089850 | Mar 2000 | JP |
| 2001029353 | Feb 2001 | JP |
| 2001128993 | May 2001 | JP |
| 2002336194 | Nov 2002 | JP |
| 2006303167 | Nov 2006 | JP |
| 2007174666 | Jul 2007 | JP |
| 2009291308 | Dec 2009 | JP |
| 2010063883 | Mar 2010 | JP |
| 2014210052 | Nov 2014 | JP |
| 20110081018 | Jul 2011 | KR |
| WO-0112089 | Feb 2001 | WO |
| WO-2008053485 | May 2008 | WO |
| WO-2014031800 | Feb 2014 | WO |
| WO-2014071184 | May 2014 | WO |
| WO-2015047693 | Apr 2015 | WO |
| WO-2017058617 | Apr 2017 | WO |
| WO-2018116247 | Jun 2018 | WO |
| WO-2019215354 | Nov 2019 | WO |
| WO-2021044136 | Mar 2021 | WO |
| Entry |
|---|
| Sorrells, P., “Application Note AN680. Passive RFID Basics,” retrieved from http://ww1.microchip.com/downloads/en/AppNotes/00680b.pdf on Feb. 26, 2020, Dec. 31, 1998, pp. 1-7. |
| IEEE Std 802.Mar. 2012 (Revision of IEEE Std 802.3-2008, published Dec. 28, 2012. |
| “ATM-MPLS Network Interworking Version 2.0, af-aic-0178.001” ATM Standard, The ATM Forum Technical Committe, published Aug. 2003. |
| “BOWA ARC 400” Oct. 30, 2018, posted at bowa-medical.com, [site visited Aug. 6, 2021], https://www.bowa-medical.com/tradepro/shopru/artikel/allgemein/BOWA_BRO_11181_ARC400_V2.1_2018_10_30_EN.pdf (Year: 2018). |
| “Electrosurgical Generator ECONT-0201.3” Mar. 18, 2018, posted at contact—endoscopy.com, [site visited Aug. 6, 2021], https://contact-endoscopy.com/electrosurgical-system (Year: 2018). |
| Li et al., “Wearable Energy Harvesters Generating Electricity From Low-Frequency Human Limb Movement,” Microsystems & Nanoengineering (2018), vol. 4(24), 13 pages. |
| Qian, et al., “A Review of Augmented Reality in Robotic-Assisted Surgery”, IEEE Transactions on Medical Robotics and Bionics, IEEE, vol. 2, No. 1, pp. 1-16, Feb. 2020. |
| Yu et al., “Skin-Integrated Wireless Haptic Interfaces for Virtual and Augmented Reality,” Nature, vol. 575, pp. 473-479, Nov. 21, 2019. |
| Zhu et al. “Haptic-feedback smart glove as a creative human-machine interface (HMI) for virtual/augmented reality applications,” Sci. Adv, vol. 6, No. 19, May 8, 2020. |
| Number | Date | Country | |
|---|---|---|---|
| 20220313371 A1 | Oct 2022 | US |
