A system and method for controlling one or more medical devices by a wireless remote control, and, in particular, a system and method for automatically powering on a remote control console in response to being brought in proximity to a central controller.
Endoscopy is a technology that allows minimally-invasive viewing of internal features of a body. In medicine, endoscopy allows acquisition of high-quality images of internal features of a human body without the need for invasive surgery. The basic tool of endoscopy is the endoscope (“scope”), which is inserted into the body to be viewed. Some endoscopic procedures involve the use of a flexible scope, as in the medical field of gastroenterology, for example. Other medical procedures, such as arthroscopy or laparoscopy, use a rigid scope. The scope is normally coupled to a high-intensity light source that transmits light into the body through the scope, and to a camera head that includes electronics for acquiring video image data. The camera head is typically coupled to a video monitor, which displays video images acquired by the camera.
In endoscopic surgery, various other medical devices may be used, such as an insufflator to pump pressurized gas into body cavities to create more space for viewing and working, an electrocautery tool to stop bleeding, and/or various tools to cut or shape body tissues. These devices are typically controlled remotely by means such as foot pedals and/or switches placed on the floor of the operating room, which are operated by the surgeon. The foot controls may control functions such as on/off, speed or intensity, direction of movement of the tool, mode of operation, etc. The use of foot controls and the like allows the surgeon to adjust various modes and settings of the tools (e.g., speed, intensity) himself, without having to put a tool down, change hands, touch potentially contaminated surfaces with his hands, or take his eyes off the patient.
First generation foot pedals and other types of remote control consoles typically functioned by relaying command signals, in the form of electrical impulses, over a conductive line or cable that physically connected the remote control console to the device being controlled.
As technology advanced, the remote controllers became wireless, thereby allowing a remote control console to be located anywhere within the operating room without having to run a cable along the floor. Such wireless remote control consoles (hereafter referred to simply as “remote consoles”) are typically configured to communicate wirelessly with a central control unit, which in turn communicates with one or more medical devices that are to be controlled remotely. To ensure the reliability of the wireless communications, and prevent any interference or accidental communication with another nearby wireless device, the remote console is synchronized with the central controller, thereby assuring that the central controller will only acknowledge command signals transmitted by an authorized remote console. The synchronization process typically involves programming the central controller to recognize an identification code that uniquely identifies all wireless communications transmitted by a specific remote console.
One method of pairing or synchronizing a remote console to a central controller involves manually entering a remote console's identification code into the central controller. Some more advanced systems partially automate the synchronization process, whereby the central controller can wirelessly retrieve the identification code of a remote console by, for example, reading an RFID tag or barcode on the console after the console has been placed into a pairing state and brought into proximity of the central controller.
Typical remote consoles are configured to switch off or enter a “sleep” state after a predefined period of inactivity in order to conserve battery power. As a result, when a user wants to synchronize a remote console to a central controller, he or she must first “awaken” or turn on the remote console so that the console can communicate with the central controller and undergo the synchronization process. Typically a remote console is turned on through some form of user interaction, such as, for example, the depressing of one or a sequence of buttons on the remote console.
Alternatively, a remote console may be configured to not turn off but instead enter a “semi-awake” state where the console continues to consume battery power, albeit at a lower level, thereby allowing the remote console to detect the initiation of the synchronization process and subsequently place itself in a full “awake” state. However, according to this later scheme, the remote console continues to draw battery power even when not in use, thereby significantly reducing the battery life of the console.
The safety of traditional remote consoles can also be compromised due to the failure of a user to “break” any previous wireless connections before implementing a new connection. For example, a remote console is synchronized, and thus wirelessly connected, to a first central controller located in a first operating room. A user then relocates the remote console to a second operating room without first disabling or “breaking” the wireless connection between the remote console and the first central controller, which typically is accomplished through some form of user interaction such as the depressing of one or more buttons on the console. A second user, who is unaware that the first central controller in the first operating room remains wirelessly connected to the remote console, may then synchronize the remote console to a second central controller located in the second operating room. As a result, use of the remote console to control one or more medical devices in the second operating room may lead to erroneous control of one or more medical devices located in the first operating room since the first central controller continues to be responsive to the command signals wirelessly transmitted by the remote console.
Accordingly, what is needed is a remote control console system that can be easily turned on or placed in an “awake” state while requiring either a minimum amount or no user interaction. Also needed is a remote control console system that will reliably and automatically terminate any previous wireless connections before a new wireless connection is established.
One or more embodiments of the present invention are illustrated by way of example and should not be construed as being limited to the specific embodiments depicted in the accompanying drawings, in which like references indicate similar elements and in which:
As described in greater detail below, a single wireless remote console in accordance with the invention (hereafter referred to simply as “console”) allows a surgeon or other operator to control one or more medical devices during an endoscopic medical procedure. The console can comprise one or multiple controls designed for operation by an operator's hand or foot to control a medical device or devices.
For illustrative purposes, consider an example of a wireless, foot-operated console that includes one or more foot pedals and/or foot switches to control one or more devices, including a selection switch to allow selection of the device to be controlled if multiple devices are connected. In response to operation of the foot controls, the console transmits signals wirelessly to a central control unit, which causes the central control unit to select a device to be controlled and to control the selected device. The foot control console may include a rechargeable battery, which may be sealed within the console's housing and charged inductively when the console is placed in a docking station. The central control unit and the docking station can be separate units or they can be integrated within a single housing.
I. The Wireless Remote Console and Central Control Unit
Connecting to each of the devices 24, either directly or through the wired communication medium 25, is a central control unit 12 labeled “receiver” in
As the console 14 is wireless, it requires its own power source. According to one embodiment, this power source can be one or more replaceable alkaline batteries. In another embodiment, the power source comprises one or more rechargeable batteries that can be removed from the console 14 for recharging. Alternatively, the rechargeable battery or batteries can be sealed within the housing of the console 14. In such an embodiment, the housing can be made of molded plastic or other similar material, making the console 14 lightweight, durable, soakable, and easy to clean. This approach is desirable because, among other reasons, it is common during certain surgical procedures for considerable amounts of water and/or other fluids to be spilled onto the floor of the operating room. A sealed console housing is advantageous, therefore, since there is no need for electrical contacts that are directly exposed to this operating room environment. In addition, the use of a rechargeable internal battery reduces the number of electrical cables needed in the operating room.
To charge the internal battery, a docking station 16 may be provided. The console 14 is placed into the docking station 16, where the battery is charged by means such as electromagnetic induction. The docking station 16 also serves as a convenient holder for the console 14 when the console 14 is not in use.
Depicted in the illustrative example of
For the remainder of the detailed discussion, all references to a remote console 14 will presume to mean a foot-controlled console 14 such as the example illustrated in
In certain embodiments, the console 14 of
In other embodiments, the console 14 is capable of controlling two or more devices simultaneously. For example, two or more separate switches and/or pedals can be used to control two or more separate devices 24 at the same time. Alternatively, the same control on remote console 14 might be used to control two or more devices 24 connected to the central control unit 12.
The central control unit 12 will detect which devices 24 are present or connected to the wired communication medium 25 or by direct connection 26. Therefore, the console 14 does not need to have any knowledge of which device 24 is currently selected, since such knowledge can be maintained entirely within the central control unit 12. The console 14 simply transmits generic control signals, which the central control unit 12 receives and translates into other control signals having the appropriate format and protocol for the device 24 currently selected device for control. In some embodiments, the central control unit 12 can receive input from multiple consoles 14 simultaneously and output the corresponding control signal to either one or multiple devices, depending on if the multiple consoles 14 are controlling the same device or multiple devices.
Further included in the console 40 is at least one rechargeable battery 50. Also present is a radio frequency identification (RFID) chip or tag 52 that is either contained within the console 40, or alternatively, fixedly attached to the exterior surface of the console 40. The internal components of the console 40 (i.e., other than the switches and pedals) are completely sealed within the housing of the console 40, which protects those components from damage from the operating room environment and reduces the risk of electrical shock and sparks.
The microcontroller 42 can communicate with the RF transmitter 48 and RF receiver 49 through, for example, a standard RS-232 interface. The RF transmitter 48 transmits control signals to a central control unit, under the control of the microcontroller 42, in response to user inputs applied at the foot operated controls (switches 44A, 44B and 44C and pedals 46A and 46B).
The microcontroller 42 in each wireless console 40 is assigned a unique identification (ID) code. This ID code allows the microcontroller 42 to uniquely identify all the command signals transmitted by the console 40 by incorporating its ID code into the signals it generates and subsequently passes on to the RF transmitter 48. The microcontroller ID code is also stored into a memory of the RFID tag 52, thereby allowing a central control unit to determine the unique identity of the console 40 by wirelessly reading the RFID tag 52.
Also included in the console 40 is a coil switching circuit 54 that is capable of powering the remote console 40 on or off by disrupting the flow of electrical current from the battery 50 to the microcontroller 42. As will be discussed in greater detail below, the coil switching circuit 54 is placed in a “closed” state, thereby permitting the battery 50 to power the microcontroller 42, when the coil switching circuit 54 is subjected to an electromagnetic field (EMF) of a particular frequency or frequencies.
Also included within the central control unit 60 is a radio frequency identification (RFID) reader 74 which generates a relatively weak electromagnetic field. When an RFID tag is brought within close proximity to the RFID reader 74, the tag picks up the electromagnetic energy and begins communicating with the RFID reader 74. More specifically, the electromagnetic field being generated by the RFID reader 74 becomes uniquely modulated in a predetermined manner when a RFID tag is in close proximity. It is by this means of modulating an electromagnetic field that the RFID tag communicates information, such as an ID code, to the RFID reader 74.
In addition to communicating information such as ID codes, the electromagnetic field generated by RFID reader 74 can also be utilized as a triggering mechanism for turning on a remote console. As will be discussed in detail below, a remote console 40, such as that depicted in
The central control unit 60 also includes one or more output indicators 64 which are used to communicate various information to the user of the system, including indicating which device or devices 24 (
Depending upon which of the devices 24 is currently selected, the microcontroller 62 uses the control signals received by the wireless receiver 66 to generate commands and/or other control signals directed to a particular device 24 on the wired communication medium 25. The microcontroller 62 is programmed to generate specific commands or other control signals in a format and/or protocol that is appropriate for the currently selected device 24. The microcontroller 62 causes the network adapter 70 to transmit these generated commands onto the wired communication medium 25.
The network adapter 70 can be, for example, a standard IEEE standard 1394 adapter, while the wired communication medium 25 is, for example, an IEEE 1394 backplane. In that case, the central control unit 60 can use standard IEEE 1394 protocols to identify the other devices that are connected to the backplane. In still other embodiments, the central control unit 60 can accommodate communication mediums other than IEEE 1394, such as, for example, connections designed for devices such as the Assignee's Integrated Device Network (SIDNE®) Control System and Total Performance System (TPS), as well as Assignee's Radio Frequency Ablation System (SERFAS™).
In certain embodiments, the central control unit 60 can also (or instead) have one or more “direct” (i.e., non-network) connections 26 to a controlled device 24, as previously mentioned and shown in
II. Coil Switching Circuit
As mentioned above, the remote console 40 of
Secondary coil 56 is configured or “wound” to have an inductance generally corresponding to the frequency or frequencies of the electromagnetic field generated by the RFID reader 74. As a result, secondary coil 56 is able to detect the electromagnetic field generated by the RFID reader 74, and subsequently cause the remote console 40 to turn on or “wake up” and enter an active state. More specifically, the electromagnetic field generated by the RFID reader 74 induces an electrical current in the secondary coil 56 when the remote console 40 is in proximity to the central control unit 60. The induced electrical current subsequently charges capacitor C1. The voltage differential across capacitor C1 establishes an electrical current that is directed by the dual diode series DN1 and DN2 to flow through resistor R1 and subsequently through the three parallel components comprising capacitor C2, diode D2 and resistor R2. This subsequently establishes a sufficiently large enough voltage differential to cause transistor T1 to switch operating states, resulting in the activation of the remote console 40 and initiation of a wireless connection between the console 40 and central control unit 60.
III. General Operation of the Wireless Remote Control System
According to one embodiment of the invention previously discussed, synchronization between a wireless remote console 40 and central control unit 60 is accomplished by means of radio frequency identification (RFID). Specifically, during the manufacturing process, the unique ID code that is assigned to each microcontroller 42 contained within each console 40 is read or obtained. This unique ID code is then written to a RFID chip or tag 52. This newly written RFID tag 52 is then sealed within or mounted upon the console 40 from which the ID code was first obtained.
In order to synchronize and thus establish a wireless connection between the wireless console 40 and the central control unit 60, a user picks up the console 40, which is “asleep” or powered down, and brings the console 40 next to the central control unit 60. More specifically, the area of the console 40 that contains the RFID tag 52 is aligned with the RFID reader 74 of the central control unit 60. The remote console 40 is then brought into close proximity (e.g., a couple of inches) to the central control unit 60, thereby displacing the secondary coil 56 of the coil switching circuit 54 within the electromagnetic field being transmitted by the RFID reader 74.
The displacement of the remote console 40 into close proximity to the central control unit 60 results in the placement of the secondary coil 56 within the electromagnetic field being transmitted by the RFID reader 74. This leads to the generation of an electrical current in the coil activation circuit 80 due to the secondary coil 56 being configured to have an inductance generally corresponding to the frequency(s) of the electromagnetic field being generated by the RFID reader 74. The amount of electrical current induced in the coil activation circuit 54 is sufficient to activate transistor T1, which subsequently leads to the powering up of microcontroller 42 and the “awakening” of the remote console 40.
Displacement of the remote console 40 into close proximity to the central control unit 60 also results in the placement of the RFID tag 52 within the electromagnetic field being generated by the RFID reader 74. Similar to the coil activation circuit 54, an electrical current is also induced in the RFID tag 52, leading to the generation of a second electromagnetic field by the RFID tag 52. Compared to the first field generated by the RFID reader 74, the second electromagnetic field generated by the RFID tag 52 is modulated to include a signal representing the unique ID code stored in a memory of the RFID tag 52 and representing the ID code of the microcontroller 42 of the remote console 40. The RFID reader 74 detects this second, modulated electromagnetic field being generated by the RFID tag 52, thereby allowing the central controller 60 to wirelessly determine the unique identity of the remote console 40 once it is brought into proximity of the central controller 60.
Accordingly, the act of bringing the remote console 40 into proximity of the central controller 60 results in two initial actions, including the automatic “awakening” or powering up of the remote console 40, and the wireless identification of the remote console 40 by the central controller 60. After the remote console 40 has been identified, the central controller 60 initiates the “pairing” process whereby the remote console 40 and central controller 60 are synchronized so as to establish a reliable wireless connection between them. For additional information on the subsequent “pairing” process, please see U.S. Patent Publication No. US2006-0116667, entitled “Apparatus and Method for Synchronizing A Wireless Remote Control To A Central Control Unit So As To Allow Remote Control Of A Medical Device Over A Secure Wireless Connection”, the disclosure of which is herein incorporated by reference in its entirety.
IV. Advantages of a Wireless Remote Control System Containing a Coil Activation Circuit
A medical device remote control system according to the embodiments described above provides several advantages over more traditional remote controllers. By utilizing a coil activation circuit 54 such as that depicted in
Unlike more traditional remote control systems such as those utilized in consumer applications and home environments, the system described in the embodiments above possesses the further advantage that it does not require the generation or receipt of a specific command or coded wireless signal to initiate the powering on of the remote console 40. Instead, the remote console 40 automatically powers on simply in response to the presence of an electromagnetic field comprised of one or more predetermined frequencies. Accordingly, the remote console 40 does not need to be programmed to recognize a specific activation or power on command.
The medical remote control system disclosed in the present application provides for a remote console that does not require any electrical contacts on the housing of the console that would be directly exposed to an operating room environment. This allows for a sealed console housing that is soakable or sterilizable. Furthermore, the remote console 40 as described in the embodiments above require no electrical connection between the RFID tag 52 and the internal circuitry that allows the remote console 40 to automatically power on in response to the presence of an electromagnetic field. The use of an electrically isolated RFID tag 52 that can be adhered to the housing of the console, and later removed if necessary, results in a remote console 40 that is easier to manufacture and maintain.
According to an additional embodiment, the coil activation circuit 54 can be configured to automatically power on the remote console 40 while also automatically terminating any previous pairing between the remote console 40 and a central controller 60. As a result, the safety of the remote control system is not affected when a user fails to terminate any previous pairing, and thus fails to break an existing wireless connection with a first central controller 60, before pairing the remote console 40 with a second central controller 60.
V. Additional Embodiments
According to an additional embodiment of the invention, the remote console does not include the coil activation circuit 54 as depicted in
According to another embodiment, the system includes a remote console that utilizes one of optical, acoustic and reflective infrared sensing technology to trigger the automatic powering on of the remote console.
Although the present invention has been described with reference to specific exemplary embodiments, it will be recognized that the invention is not limited to the embodiments described, but can be practiced with modification and alteration within the spirit and scope of the appended claims. Accordingly, the specification and drawings are to be regarded in an illustrative sense rather than a restrictive sense.
Number | Name | Date | Kind |
---|---|---|---|
4005428 | Graham | Jan 1977 | A |
4214229 | Warner | Jul 1980 | A |
4850040 | Teich et al. | Jul 1989 | A |
5204768 | Tsakiris et al. | Apr 1993 | A |
5627584 | Nishikori et al. | May 1997 | A |
5640151 | Reis et al. | Jun 1997 | A |
5767791 | Stoop et al. | Jun 1998 | A |
5850187 | Carrender et al. | Dec 1998 | A |
5855550 | Lai et al. | Jan 1999 | A |
5874902 | Heinrich et al. | Feb 1999 | A |
5923373 | Fukushima | Jul 1999 | A |
5938655 | Bisch et al. | Aug 1999 | A |
5973611 | Kulha et al. | Oct 1999 | A |
5997528 | Bisch et al. | Dec 1999 | A |
6074388 | Tockweiler et al. | Jun 2000 | A |
6255944 | Addy | Jul 2001 | B1 |
6362737 | Rodgers et al. | Mar 2002 | B1 |
6466131 | Tuttle et al. | Oct 2002 | B1 |
6509837 | Tuttle et al. | Jan 2003 | B1 |
6531964 | Loving | Mar 2003 | B1 |
6567032 | Mullaly et al. | May 2003 | B1 |
6768425 | Flaherty et al. | Jul 2004 | B2 |
6781508 | Tuttle et al. | Aug 2004 | B2 |
6791467 | Ben-Ze'ev | Sep 2004 | B1 |
6831562 | Rodgers et al. | Dec 2004 | B2 |
6874037 | Abram et al. | Mar 2005 | B1 |
6892052 | Kotola et al. | May 2005 | B2 |
6978118 | Vesikivi et al. | Dec 2005 | B2 |
7009495 | Hughes et al. | Mar 2006 | B2 |
7010369 | Borders et al. | Mar 2006 | B2 |
7064675 | Zigmond et al. | Jun 2006 | B2 |
7079008 | Castle et al. | Jul 2006 | B2 |
7079020 | Stilp | Jul 2006 | B2 |
7155159 | Weinblatt et al. | Dec 2006 | B1 |
7167090 | Mandal et al. | Jan 2007 | B1 |
7224980 | Hara | May 2007 | B2 |
7229023 | Raskar | Jun 2007 | B2 |
7345575 | Tuttle et al. | Mar 2008 | B2 |
7366934 | Narayan et al. | Apr 2008 | B1 |
7496697 | Sween et al. | Feb 2009 | B2 |
7660420 | Narayan et al. | Feb 2010 | B1 |
7737862 | Watanabe | Jun 2010 | B2 |
20020038392 | De La Huerga | Mar 2002 | A1 |
20020156466 | Sakurai et al. | Oct 2002 | A1 |
20030007473 | Strong et al. | Jan 2003 | A1 |
20030065805 | Barnes, Jr. | Apr 2003 | A1 |
20030093503 | Yamaki et al. | May 2003 | A1 |
20030195644 | Borders et al. | Oct 2003 | A1 |
20040131925 | Jenson et al. | Jul 2004 | A1 |
20040155791 | Nguyen et al. | Aug 2004 | A1 |
20040166807 | Vesikivi et al. | Aug 2004 | A1 |
20040203352 | Hall et al. | Oct 2004 | A1 |
20040205191 | Smith et al. | Oct 2004 | A1 |
20050017727 | Oberle | Jan 2005 | A1 |
20050049458 | Honda et al. | Mar 2005 | A1 |
20050068155 | Caruana | Mar 2005 | A1 |
20050080403 | Takahashi | Apr 2005 | A1 |
20050099943 | Naghian et al. | May 2005 | A1 |
20050101314 | Levi | May 2005 | A1 |
20050121526 | Stewart et al. | Jun 2005 | A1 |
20050143129 | Funk et al. | Jun 2005 | A1 |
20050145129 | Holm | Jul 2005 | A1 |
20050154896 | Widman et al. | Jul 2005 | A1 |
20050215233 | Perera et al. | Sep 2005 | A1 |
20050218726 | Jenson et al. | Oct 2005 | A1 |
20050254183 | Ishida et al. | Nov 2005 | A1 |
20060022800 | Krishna et al. | Feb 2006 | A1 |
20060038659 | Takano et al. | Feb 2006 | A1 |
20060043201 | Vesikivi et al. | Mar 2006 | A1 |
20060044153 | Dawidowsky | Mar 2006 | A1 |
20060068750 | Burr | Mar 2006 | A1 |
20060103506 | Rodgers et al. | May 2006 | A1 |
20060116667 | Hamel et al. | Jun 2006 | A1 |
20060119487 | Atkinson et al. | Jun 2006 | A1 |
20060145842 | Stilp | Jul 2006 | A1 |
20060169771 | Brookner | Aug 2006 | A1 |
20060197660 | Luebke et al. | Sep 2006 | A1 |
20060210277 | Dubnack et al. | Sep 2006 | A1 |
20060261950 | Arneson et al. | Nov 2006 | A1 |
20060286960 | Goehler | Dec 2006 | A1 |
20060294566 | Zlattner | Dec 2006 | A1 |
20070006275 | Wright et al. | Jan 2007 | A1 |
20070052548 | Hankin et al. | Mar 2007 | A1 |
20070057790 | Alden et al. | Mar 2007 | A1 |
20070080823 | Fu et al. | Apr 2007 | A1 |
20070087719 | Mandal et al. | Apr 2007 | A1 |
20070120650 | Nagai et al. | May 2007 | A1 |
20070233888 | Yamaki | Oct 2007 | A1 |
20070278998 | Koyama | Dec 2007 | A1 |
20080094245 | Hardacker et al. | Apr 2008 | A1 |
20080157993 | Du Breuil et al. | Jul 2008 | A1 |
20080240440 | Rose et al. | Oct 2008 | A1 |
20080303707 | Larsen et al. | Dec 2008 | A1 |
20090048021 | Lian et al. | Feb 2009 | A1 |
20090121865 | Hamel et al. | May 2009 | A1 |
Number | Date | Country |
---|---|---|
WO 2005053248 | Jun 2005 | WO |
WO 2005064824 | Jul 2005 | WO |
WO 2008098085 | Aug 2008 | WO |
Number | Date | Country | |
---|---|---|---|
20090121865 A1 | May 2009 | US |