Wireless link pairing authentication
Through the automatic pairing system combined with multiple communication channels, the problem of difficult pairing of medical equipment and control equipment in complex hospital environments is solved, efficient and accurate equipment pairing and communication is achieved, and the hospital layout changes are adapted to changes.
Patent Information
- Application Number
- CN202111296585.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2020-11-06
- Filing Date
- 2021-11-03
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2041-11-03
AI Technical Summary
The automatic pairing method of existing medical equipment and control equipment depends on line-of-sight communication, and there is a problem of communication disorders caused by changes in equipment angle and position under the complex layout of the hospital. Users operate cumbersomely and prone to errors.
Using an automatic pairing system combining multi-communication channels (wireless communication and optical communication), the processor receives and matches the identifier of the medical device, realizes automatic pairing, and disassociates when the signal intensity is below the threshold, and uses visual indicators to reflect the device status. .
It improves the efficiency and accuracy of automatic pairing of medical equipment and control equipment, reduces user intervention, adapts to changes in equipment layout in complex hospital environments, and ensures communication reliability.
Smart Images

Figure CN114531677B_ABST
Abstract
Description
Technical Field
[0001] The present disclosure generally relates to systems and / or methods for pairing medical devices, receiver devices, and control devices, and more particularly to systems and / or methods for pairing medical devices, receiver devices, and control devices utilizing line-of-sight optical links and / or wireless links. Background Art
[0002] A medical facility may include multiple rooms, each of which may include one or more medical devices. Each medical device (MD) may be permanently fixed in the room or may be movable between multiple rooms. In addition, each medical device may be wirelessly controlled by a respective control device (CD), which may be permanently fixed in the room or may be movable between multiple rooms. Accordingly, considering the portability of medical devices and / or control devices, a system and / or method for ensuring wireless communication between a specific control device and a specific medical device is needed.
[0003] Existing methods require some form of user intervention to place a pairable device in a discoverable state and / or manually select a device to be paired from a list of detected pairable devices. Placing a device in a discoverable state can be inconvenient for the user and / or difficult for the user to remember or perform, while manually selecting a device may cause the user to select the wrong device. In addition, current automatic pairing methods rely on line of sight between the two devices being paired with each other. For example, an infrared (IR) receiver on a wall unit (such as a control device) must be located in a line of sight to capture transmissions from an IR transmitter mounted at a fixed position on a bed (such as a medical device). This can be problematic because hospital rooms have a wide variety of layouts and designs. The control devices of some wall units are mounted at an angle to the bed, even 90 degrees. For example, the control unit may also be mounted at shoulder height, while the transmitter on the bed is lowered to close to the ground. When the bed is close to the wall, reliable IR communication between the two will be hindered.
[0004] Ultimately, the user's focus is diverted, so these methods are not the preferred option. Summary of the invention
[0005] In one aspect, an automatically pairable control device may include a first communication system configured to communicate via a first communication channel and a second communication system configured to communicate via a second communication channel different from the first communication channel. The automatically pairable control device may also include a processor and a memory storing program instructions. When the program instructions are executed by the processor, the processor receives a first identifier associated with the medical device from the medical device via the first communication channel. The program instructions also cause the processor to receive a second identifier associated with the medical device from a receiver device via the second communication channel. The program instructions further cause the processor to determine that the first identifier received via the first communication channel matches the second identifier received via the second communication channel. The program instructions further cause the processor to automatically pair with the medical device associated with the matching identifier via the second communication channel.
[0006] In this aspect, according to certain aspects, the first communication channel and the second communication channel are wireless communication channels. On the other hand, the third communication channel is a wireless communication channel or an optical communication channel, or the receiver device includes a camera to visually detect a visual identifier located in the line of sight between the receiver device and the medical device. On the other hand, when the program instructions are executed by the processor, the processor can further receive status data from the medical device through the first communication channel associated with the matching identifier, and send a control input to the medical device through the first communication channel associated with the matching identifier, wherein the control input is used to control the function of the medical device. On the other hand, the optical communication channel is an infrared (IR) communication channel, and the wireless communication channel is a radio frequency (RF) communication channel. On the other hand, when the program instructions are executed by the processor, the processor further determines that at least one of the first communication channel and the second communication channel is associated with a signal below a predetermined threshold strength, and disassociates from the medical device associated with the matching identifier. On the other hand, when the program instructions are executed by the processor, the processor further disassociates from the medical device automatically based on no longer detecting the first identifier through the first communication channel or no longer detecting the second identifier through the first communication channel.
[0007] On the other hand, a system for automatically pairing devices may include an automatically pairable control device, which may include a first communication system configured to communicate via a first communication channel, a second communication system configured to communicate via a second communication channel different from the first communication channel, a processor, and a memory storing program instructions. When the program instructions are executed by the processor, the processor receives a first identifier associated with the medical device from the automatically pairable medical device via the first communication channel. The program instructions further cause the processor to receive a second identifier associated with the medical device from a receiver device paired with the control device via the second communication channel. The program instructions additionally cause the processor to determine that the first identifier received via the first communication channel matches the second identifier received via the second communication channel. The program instructions further automatically pair with the medical device associated with the matching identifier via the second communication channel. The receiver device paired with the control device may be configured to receive the second identifier associated with the medical device from the medical device via a second communication channel different from the first communication channel and the third communication channel. The receiver device may be further configured to send the second identifier associated with the medical device to the control device via the second communication channel.
[0008] In this other aspect, according to certain aspects, the first communication channel and the second communication channel are wireless communication channels. In other aspects, the third communication channel is a wireless communication channel or an optical communication channel, or the receiver device includes a camera to visually detect a visual identifier located in the line of sight between the receiver device and the medical device. On the other hand, the program instructions are further executed by the processor to cause the processor to send a control input to the medical device associated with the matching identifier, wherein the control input is used to control the function of the medical device. On the other hand, the optical communication channel is an infrared (IR) communication channel, and the wireless communication channel is a radio frequency (RF) communication channel. On the other hand, the program instructions are further executed by the processor to cause the processor to determine that at least one of the first communication channel and the second communication channel is associated with a signal below a predetermined threshold strength, and to disassociate with the medical device associated with the matching identifier. On the other hand, the program instructions are further executed by the processor to cause the processor to automatically disassociate the control device from the medical device based on no longer detecting the first identifier through the first communication channel or no longer detecting the second identifier through the first communication channel. On the other hand, the control device further includes a visual indicator, and wherein the program instructions are further executed by the processor to cause the processor to update the visual indicator to reflect that the medical device is not in the line of sight of the receiver device.
[0009] In another aspect, a system for automatically pairing devices may include an automatically pairable control device, which may include a first communication system configured to communicate via a first communication channel, a second communication system configured to communicate via a second communication channel different from the first communication channel, a processor, and a memory storing program instructions. When the program instructions are executed by the processor, the processor receives a first identifier associated with the medical device from the automatically pairable medical device via the first communication channel. The program instructions further cause the processor to receive a second identifier associated with the medical device from a receiver device paired with the control device via the second communication channel. The program instructions further cause the processor to determine that the first identifier received via the first communication channel matches the second identifier received via the second communication channel. The program instructions further cause the control device to automatically pair with the medical device associated with the matching identifier via the first communication channel. The receiver device paired with the control device may include a communication system configured to communicate via a third communication channel different from the first communication channel and the second communication channel. The receiver device may be additionally configured to receive a second identifier associated with the medical device from the medical device via the third communication channel. The receiver device may be further configured to send the second identifier associated with the medical device to the control device via the second communication channel. The automatically-pairable medical device may be further configured to send a first identifier associated with the medical device to the automatically-pairable control device via the first communication channel. The automatically-pairable medical device may also be configured to send the first identifier associated with the medical device to the receiver device via the second communication channel.
[0010] In this further aspect, according to certain aspects, the first communication channel and the second communication channel are wireless communication channels. In other aspects, the third communication channel is a wireless communication channel or an optical communication channel, or the receiver device includes a camera to visually detect a visual identifier located in the line of sight between the receiver device and the medical device. On the other hand, the program instructions are further executed by the processor to cause the processor to send a control input to the medical device associated with the matching identifier, wherein the control input is used to control the function of the medical device. On the other hand, the optical communication channel is an infrared (IR) communication channel, and the wireless communication channel is a radio frequency (RF) communication channel. On the other hand, the program instructions are further executed by the processor to cause the processor to determine that at least one of the first communication channel and the second communication channel is associated with a signal below a predetermined threshold strength, and to disassociate with the medical device associated with the matching identifier. On the other hand, the program instructions are further executed by the processor to cause the processor to automatically disassociate the control device from the medical device based on no longer detecting the first identifier through the first communication channel or no longer detecting the second identifier through the first communication channel. On the other hand, the control device further includes a visual indicator, and wherein the program instructions are further executed by the processor to cause the processor to update the visual indicator to reflect that the medical device is not in the line of sight of the receiver device.
[0011] In yet another aspect, a method for automatically pairing a medical device with a control device via a receiver device may include receiving an identifier associated with the medical device via a first communication channel. The method may further include receiving a second identifier associated with the medical device via a second communication channel different from the first communication channel. The method may also include determining that the first identifier received via the first communication channel matches the second identifier received via the second communication channel. The method may additionally include automatically pairing the control device with the medical device associated with the matching identifier via the first communication channel.
[0012] In this further aspect, according to certain aspects, the first communication channel and the second communication channel are wireless communication channels. In other aspects, the third communication channel is a wireless communication channel or an optical communication channel, or the receiver device includes a camera to visually detect a visual identifier in the line of sight between the receiver device and the medical device. Still other aspects include receiving status data from the medical device through the first communication channel associated with the matching identifier, and sending a control input to the medical device through the first communication channel associated with the matching identifier, wherein the control input is used to control the function of the medical device. In another aspect, the optical communication channel is an infrared (IR) communication channel, and the wireless communication channel is a radio frequency (RF) communication channel.
[0013] In another aspect, a method for automatically pairing a control device with a medical device via a control device may include receiving, at the control device, a first identifier associated with the medical device from the medical device via a first communication channel. The method may further include receiving, from the medical device via a third communication channel different from the first communication channel, a second identifier associated with the medical device. The method may additionally include sending the second identifier associated with the medical device from a receiver device to the control device via a second communication channel different from the first communication channel and the third communication channel. The method may also include determining, at the control device, that the first identifier received via the first communication channel matches the second identifier received via the second communication channel. The method may further include automatically pairing, via the first communication channel, the control device with the medical device associated with the matching identifier.
[0014] In this further aspect, according to certain aspects, the first communication channel and the second communication channel are wireless communication channels. In certain other aspects, the third communication channel is a wireless communication channel or an optical communication channel, or the receiver device includes a camera to visually detect a visual identifier located in the line of sight between the receiver device and the medical device. This additional aspect may further include receiving status data from the medical device through the first communication channel associated with the matching identifier, and sending a control input from the control device to the medical device through the first communication channel associated with the matching identifier, wherein the control input is used to control the function of the medical device. In certain additional aspects, the optical communication channel is an infrared (IR) communication channel, and the wireless communication channel is a radio frequency (RF) communication channel. Certain additional aspects include determining that at least one of the first communication channel and the second communication channel is associated with a signal below a predetermined threshold strength, and disassociating the control device from the medical device associated with the matching identifier. Still other aspects may include automatically disassociating the medical device based on no longer detecting the first identifier through the first communication channel or no longer detecting the second identifier through the first communication channel.
[0015] In another aspect, a method for automatically pairing a control device with a medical device by a control device may include sending an identifier associated with the medical device from the medical device to the control device via a first communication channel. The method may further include receiving a first identifier associated with the medical device from the medical device at the control device via the first communication channel. The method may also include sending a second identifier associated with the medical device from the medical device to a receiver device via a third communication channel different from the first communication channel. The method may additionally include receiving a second identifier associated with the medical device from the medical device at the receiver device via the third communication channel. The method may further include sending the second identifier associated with the medical device from the receiver device to the control device via a second communication channel different from the first communication channel and the third communication channel. The method may additionally include determining at the control device that the first identifier received via the first communication channel matches the second identifier received via the second communication channel. The method may further include automatically pairing the control device with the medical device associated with the matching identifier via the first communication channel.
[0016] In yet another aspect, according to certain aspects, the method includes sending a control input from a control device to a medical device associated with a matching identifier, wherein the control input is used to control a function of the medical device. In other aspects, the optical communication channel is an infrared (IR) communication channel and the wireless communication channel is a radio frequency (RF) communication channel. Still other aspects may include automatically disassociating the control device from the medical device based on no longer detecting the first identifier through the first communication channel or no longer detecting the second identifier through the first communication channel. Additional aspects may include updating a visual indicator to reflect that the medical device is not within a line of sight of the receiver device.
[0017] The following detailed description will set forth additional features and advantages of the embodiments described herein, some of which will be self-evident to those skilled in the art based on the content or understood by practicing the embodiments described herein, including the following detailed description and the accompanying drawings.
[0018] It should be understood that the above summary of the invention and the following detailed description describe various embodiments and are intended to provide an overview or framework to understand the nature and characteristics of the subject matter claimed. The accompanying drawings provide a further understanding of the various embodiments, are incorporated into and constitute a part of this specification. The drawings illustrate various embodiments described herein and together with the description are used to explain the principles and operation of the subject matter claimed. BRIEF DESCRIPTION OF THE DRAWINGS
[0019] The embodiments illustrated in the accompanying drawings are illustrative and exemplary in nature and are not intended to limit the subject matter defined in the claims. The following detailed description of the illustrative embodiments can be understood when read in conjunction with the accompanying drawings, in which like reference numerals refer to like structures, in which:
[0020] Figure 1 depicts a block diagram illustrating wireless communication between a control device and a plurality of medical devices distributed in a plurality of rooms and a plurality of floors of a medical facility and a plurality of receiver devices in accordance with one or more embodiments illustrated and described herein;
[0021] Figure 2A depicts illustrative internal components of a control device communicatively coupled to one another to provide wireless link pairing with a receiver device and wireless control of a medical device in accordance with one or more embodiments illustrated and described herein;
[0022] Figure 2B depicts illustrative internal components of a receiver device communicatively coupled to each other to provide wireless, infrared, and / or optical identification of a medical device and wireless link pairing with a control device in accordance with one or more embodiments illustrated and described herein;
[0023] Figure 2C depicts illustrative internal components of a medical device communicatively coupled to one another to provide identification of a receiver device and receive wireless control from a control device in accordance with one or more embodiments illustrated and described herein;
[0024] Figure 3 An illustrative wireless link pairing authentication system is depicted, including a track-mounted lift as a medical device, a receiver device, and a tethered handheld control unit, a wireless handheld control unit, and / or a wall-mounted control unit as a control device, in accordance with one or more embodiments illustrated and described herein;
[0025] Figure 4A depicts an illustrative boom control unit as a control device in accordance with one or more embodiments illustrated and described herein;
[0026] Figure 4B depicts an illustrative coupled control unit as a control device in accordance with one or more embodiments illustrated and described herein;
[0027] Figure 5 depicts a flow chart of an illustrative method of pairing a medical device with a control device via a receiver device utilizing an optical channel in accordance with one or more embodiments illustrated and described herein;
[0028] Figure 6depicts a flow chart of another illustrative method of pairing a medical device with a control device via a receiver device utilizing a wireless communication channel in accordance with one or more embodiments illustrated and described herein;
[0029] Figure 7 A flowchart depicting an illustrative method of associating or disassociating a medical device, a receiver device, and a control device according to one or more embodiments illustrated and described herein; and
[0030] Figure 8 A flow chart is depicted of an illustrative method of a control device issuing commands or control inputs to a paired medical device in accordance with one or more embodiments illustrated and described herein. DETAILED DESCRIPTION
[0031] Reference will now be made in detail to embodiments for pairing a medical device with a control device via a receiver device to identify the medical device using a line-of-sight optical link, wireless radio frequency and / or camera, with reference to the accompanying drawings for example. Wherever possible, the same reference numerals are used throughout the drawings to refer to the same or similar parts. Figure 1 Various embodiments of the present disclosure are described. Generally speaking, the medical structure 100 may include multiple rooms and / or multiple floors (e.g., rooms A and B on the second floor and rooms C and D on the first floor). In these aspects, one or more medical devices (e.g., MD A ,MD B ,MD C and / or MD D ), one or more control devices CD A and one or more receiver devices (e.g., RD A , RD B , RD C and / or RD D ) can be distributed in various rooms and floors (see Figure 1 ) and / or within a subspace of a given room (e.g., a large triage room with multiple beds, a ward shared by two or more patients, etc.).
[0032] On the one hand, referring to Figure 1 , receiver device (e.g., RD A ) and medical devices (e.g., MD A) can be fixedly positioned in a room (e.g., Room A) and located in line of sight with each other. For example, line of sight may refer to an arrangement in which the optical system (e.g., IR system) of the medical device can have an unobstructed view of the optical system (e.g., IR system) of the receiver device (RD) so that the emitted radiation (e.g., IR) is transmitted between the two along a straight line or a straight path. Alternatively, line of sight may refer to an arrangement in which the visual system (e.g., camera system) of the receiver device (RD) can have an unobstructed view of the visual identifier (QR code, barcode, April tag, ArUco mark, etc.) of the medical device (MD) so that visual light is transmitted between the two along a straight line or a straight path. According to the optical system aspect, the control device (e.g., CD A ) can be used with a receiver device (e.g., RD A ) wireless pairing (e.g., via a Bluetooth RF signal), wherein in some aspects such pairing may be permanent and / or the receiver device may be permanently located in the room. In some aspects, a medical device (e.g., an MD A ,MD B ,MD C ,MD D etc.) can use their identifiers (MD A ID、MD B ID、MD C ID、MD D ID, etc.) is wirelessly transmitted (e.g., via Bluetooth RF signals and / or radio frequency identification (RFID)) to a receiver device and / or a control device. Since wireless signals can penetrate the walls and / or floors of the medical institution 100, multiple receiver devices (RDs) within range (e.g., up to 300 feet for Bluetooth Class 1, up to 33 feet for Bluetooth Class 2, etc.) A , RD B , RD C , RD D etc.) and / or control devices (e.g., CD A etc.) can wirelessly receive medical equipment (MD A ,MD B ,MD C ,MD DFor example, the receiver device may transmit a low power signal to obtain a response from a tag, such as a passive radio frequency identification (RFID) tag, located on the medical device. Once the passive RFID tag on the medical device receives the power sent from the receiver device, the RFID tag may wirelessly send data (e.g., a medical device identifier MD ID) back to the receiver device. In this regard, the receiver device may be located close to the ground level of the room, but in other aspects, other suitable locations / heights may also be utilized. In certain aspects, when the medical device is a bed utilizing an optical system, the IR transmitter may be located at the head of the bed, but in other aspects, other suitable locations on the medical device may also be utilized. Continuing with this aspect, when a medical device such as a bed is pushed into the room and parked in place, the receiver device is almost always in direct line of sight of the IR transmitter of the medical device (e.g., bed). Thus, if the wireless link is pairable, discoverable, and / or user-configurable, the systems and / or methods described herein may be used to ensure that a particular control device is paired with a particular medical device to avoid inadvertent actuation and / or control of a similar or identical medical device (e.g., a medical device located in another room or another subspace of a given room), but where the wireless link of the similar or identical medical device is accessible to the particular control device (e.g., through a wall or within a subdivided room).
[0033] Further to this aspect, medical devices (e.g., MD A ) can be used to identify its identifier (for example, MD A ) optically transmits (e.g., via an IR light signal) to a receiver device (e.g., RD A ). On the other hand, a receiver device (eg, RD A ) can visually detect / scan (e.g., via a camera) a medical device (MD A ) to obtain a medical device identifier (e.g., MD A Since neither optical signals nor visual light can penetrate the walls and / or floor of the medical institution 100, the medical device can only identify its identifier (e.g., MD A ID) is optically transmitted to and / or visually available to a receiver device in its room (e.g., RD in room A). A ). This aspect further includes optically receiving a signal from a receiver device (eg, RD) via its wireless communication channel (eg, IR channel). A ) of a medical device identifier (e.g., MD A Each control device (e.g., CD A ) can be configured to scan its wireless communication channel (e.g., RF channel) to determine a medical device identifier (e.g., MD) received from a receiver device via its wireless communication channel (e.g., IR channel) AWhether the medical device ID) is wirelessly received from the medical device (e.g., MD) via its wireless communication channel (e.g., RF channel) A ) matches the medical device identifier of the device. If a match occurs, the device (e.g., CD A ) can be configured to automatically identify / authenticate the corresponding A Medical devices with ID (e.g., MD A ) and the identified medical device (e.g., MD A ) pairing. As used herein, authentication between devices may refer to verifying an ID number or any other suitable mechanism for verifying or otherwise identifying the identity of a particular device. After such authenticated pairing (e.g., one-way identification), each identified medical device (e.g., MD A ) can be configured to receive a signal from a control device (e.g., a CD) via its wireless communication channel (e.g., an RF channel) A ) control signal. In certain aspects, after such an identified pairing (eg, one-way authentication), each identified medical device (eg, MD A ) can be configured to receive a signal from a control device (e.g., a CD) via its wireless communication channel (e.g., an RF channel) A ) control signal. Figure 1 , not in the receiver device (e.g., RD A ) within the line of sight of medical devices (e.g., MD B ,MD C ,MD D etc.) cannot be used to identify its identifier (e.g., MD B ID、MD C ID、MD D ID) is optically transmitted to and / or visually available to a receiver device (e.g., RD A ), so the control device (CD A ) scan their respective wireless communication channels to connect medical devices (MD A ) provided by the Medical Device Identifier (MD A ID) and the receiver device (RD A ) provided by the Medical Device Identifier (MD A ID) matches.
[0034] On the other hand, referring to Figure 1 , medical devices (e.g., MD A ) and receiver devices (e.g., RD A ) can be fixedly located in a room (e.g., Room A) and in sight of each other. According to this aspect, the medical device (e.g., MD A) can be received from a receiver device (e.g., RD A ) and then wirelessly transmits (eg, via RFID) its identifier (MD A Furthermore, since wireless signals can penetrate the walls and / or the ground of the medical institution 100, multiple medical devices and control devices (CD A ) and / or multiple receiver devices (e.g., RD B etc.) can wirelessly receive an identifier (eg, MD A ID). Further to this aspect, medical devices (e.g., MD A ) can be used to identify its identifier (for example, MD A ID) is optically transmitted (e.g., via an IR light signal) and / or visually available to a receiver device within its line of sight (e.g., an RD A ). Furthermore, since optical signals cannot penetrate the walls and / or the floor of the medical institution 100, medical equipment (e.g., MD A ) can only be used by its identifier (for example, MD A ID) is optically transmitted to and / or visually available to a receiver device in its room (e.g., RD in room A). A ). This aspect further receives wirelessly from a receiver device (RD) via its wireless communication channel (eg, RF channel) A ) of a medical device identifier (e.g., MD A Each control device (e.g., CD A ) can be configured to scan its wireless communication channel (e.g., RF channel) to determine whether a wireless signal is received from a receiver device (RD) via its wireless communication channel (e.g., IR channel) A ) of a medical device identifier (e.g., MD A Whether the medical device ID) is wirelessly received from the medical device (e.g., MD) via its wireless communication channel (e.g., RF channel) A ) matches the medical device identifier of the device. If a match occurs, the device (e.g., CD A ) can be configured to automatically authenticate the corresponding matching identifier (e.g., MD A Medical devices with ID (e.g., MD A ) and the certified medical device (e.g., MD A ) pairing. After such authenticated pairing, each control device (e.g., CD A ) can be configured to send control signals to the identified control device (e.g., MD) through its wireless communication channel (e.g., RF channel) A ).
[0035] On the other hand, still referring to Figure 1 , receiver device (e.g., RD C ) and medical devices (e.g., MD C ) can be located in a room (e.g., Room C) in a non-fixed manner and within the line of sight of each other. According to this aspect, a medical device (e.g., MD) located outside a room (e.g., Room C) C ) can wirelessly transmit (e.g., via a passive RFID signal) its identifier (e.g., MD C ID) so that it is not visible in any other receiver device (e.g., RD A , RD B , RD D Receiver devices within the line of sight of C ) and / or control equipment (CD A ) can wirelessly receive an identifier (e.g., MD C ID). Similar to the above, the control device (e.g., CD A ) can be used to identify its identifier (e.g., CD A ID) is optically transmitted (e.g., via an IR light signal) and / or visually available. Figure 1 , since the receiver device (e.g., RD C ) is not yet in medical devices (e.g., MD C ) within the line of sight of the receiver device (e.g., RD C ) will not be able to optically receive and / or visually receive / scan medical device identifiers (e.g., MD C ID) and will not be triggered to send a medical device identifier (e.g., MD C ID) is sent to the control device (CD) via its wireless communication channel A ). However, when placing medical devices (e.g., MD C ) is relocated in a room (e.g., Room C) and positioned at a receiver device (e.g., RD C ) within the line of sight, the receiver device (e.g., RD C ) can optically / visually receive a medical device identifier (e.g., MD C ID). It can trigger a previously associated control device (CD A ) wirelessly paired receiver device (e.g., RD C ) to identify the medical device identifier (e.g., MD C ID) is sent to the control device (CD A ). Receive a medical device identifier (e.g., MD C ID), the control device (CD A) can scan its wireless communication channel for a matching medical device identifier and automatically authenticate and pair with the matching medical device identifier (e.g., MD C ID) associated with the medical device (e.g., MD C ). Medical devices (e.g., MD C ) can be configured to receive a signal from an identified control device (e.g., a CD) through its wireless communication channel. C ) control input / command. Further, given Figure 1 , with the identified control device (e.g., CD A ) after pairing, the medical device (e.g., MD C ) can be relocated to another room (e.g., Room D) without line of sight to the receiver device (e.g., Room RD C ).
[0036] According to various aspects of the present disclosure, the identified control device (e.g., CD A ) after pairing, the receiver device (e.g., RD C ) can be further configured to identify a medical device identifier (e.g., MD C ID) monitors its optical communication channel. On the one hand, if the receiver device (e.g., RD C ) no longer receives a medical device identifier (e.g., MD) via the optical communication channel C ID), control devices (e.g., CD A ) can be configured to communicate with medical devices (e.g., MD) via a wireless communication channel C ) and / or vice versa. However, when a medical device (e.g., MD C ) is relocated to another room (e.g., within room D, or between sub-spaces of a given room) and positioned to another receiver device (e.g., RD D ) within the line of sight, the receiver device (e.g., RD D ) can optically / visually receive a medical device identifier (e.g., MD D ID). In turn, the control device (the same control device CD in this figure) can be triggered. A , but another control device may also be used in the room / outside or in a sub-division of the room (e.g., Room A) to scan its wireless communication channel for a matching medical device identifier, and automatically identify and pair with a matching medical device identifier (e.g., MD D ID) associated with the medical device (e.g., MD D ). Medical devices (e.g., MD C) can be configured to receive control input from a newly paired control device through its wireless communication channel. In this way, although not specifically described, it should be understood that the control device can alternatively authenticate / identify and pair the medical device (e.g., MD) via one-way authentication. C ), or medical devices (e.g., MD C ) can authenticate and pair the control device, and the control device can authenticate and pair the medical device (e.g., MD) via two-way authentication. C ), either of which can utilize a receiver device to obtain a medical device ID and send it to a control device for comparison with any medical device ID received by the control device. In addition, similar to the above, the same medical device (e.g., MD C ) After pairing, the control device can be further configured to identify the authenticated / recognized medical device identifier (e.g., MD C In one aspect, if the medical device identifier (e.g., MD ID) is no longer received via the respective wireless (RF) communication channel, C ID), the control device can be configured to communicate with the medical device (e.g., MD) through respective wireless communication channels. C ) is automatically disconnected.
[0037] In another aspect, a receiver device (eg, RD D ) and medical devices (e.g., MD D ) may not be fixedly positioned in a room (e.g., room D). Figure 1 , although medical devices (e.g., MD D ) can be repositioned, but it can remain positioned on the receiver device (e.g., MD D ) is within the line of sight of the control device (e.g., CD A ) and medical devices (e.g., MD D ) can be automatically paired with each other as described herein (e.g., one-way authentication, two-way authentication). In this way, as described herein, another medical device (e.g., MD C ) can be located in the room receiver device (e.g., RD D ). Accordingly, the receiver device (e.g., RD D ) can optically / visually receive another medical device identifier (e.g., MD C ID). In this regard, a receiver device (e.g., RD D ) can be configured for a recognized medical device identifier (e.g., MD DIn one example, if the identified medical device identifier (e.g., MD ID) is still being received through its optical communication channel, D ID), control devices (e.g., CD A ) can be configured to maintain automatic pairing to medical devices (e.g., MD D ) and ignore other medical devices (e.g., MD C ) exists. In an alternative example, if the receiver device (e.g., RD D ) optical communication channel receives the identified medical device identifier (e.g., MD D ID), control devices (e.g., CD A ) can be configured to further pair with other medical devices (e.g., MD C ).
[0038] On the other hand, a receiver device (eg, RD B ) may have an associated room identifier (e.g., R B ID). In this aspect, a room identifier (e.g., R B Each receiver device (e.g., RD B ) can be configured to transmit a room identifier (e.g., R B ID) and its own identifier (e.g., RD B ID) is wirelessly sent to the control device (e.g., CD A ). Similarly, in some aspects, a room identifier (e.g., R B Medical devices with ID (e.g., MD B ) can be configured to transmit the received room identifier (e.g., R B ID) and its identifier (e.g., MD B ID) is wirelessly sent to the control device (e.g., CD A ) and / or upon receiving a signal from a receiver device (e.g., RD B ) is then wirelessly transmitted to a receiver device (e.g., RD B ). Alternatively, this may be sent via an optical communication channel (eg, an IR channel) to a receiver device (eg, an RD B In this way, in one example, a room identifier (e.g., R B Each control device (e.g., CD A) may be further configured to scan its wireless communication channel to determine whether a medical device (e.g., MD) is wirelessly received via its optical communication channel. B )'s room identifier (e.g., R B ID) is wirelessly received from a receiver device (e.g., RD B ) matches the room identifier and / or medical device identifier (e.g., MDID) of the device. If a match occurs, each control device (e.g., CD B ) can be configured to automatically identify the room through its wireless communication channel with the room identifier (e.g., R B ID) wirelessly received identifier (e.g., MD B ID) corresponding to the medical device (e.g., MD B ) and pair the identified medical device. After such pairing (e.g., one-way identification), each control device (e.g., CD A ) can be configured to send control signals to an authenticated medical device (e.g., MD) via its wireless communication channel. B ). In some aspects, a control device (e.g., a CD A ) to pair with an authenticated medical device (e.g., MD B ) and medical devices (e.g., MD B ) to pair with the identified control device (e.g., CD A ) after which the control device (e.g., CD A ) can send control signals to medical devices (e.g., MD B ), while medical devices (e.g., MD B ) can receive data from a control device (e.g., CD A ) control signal. Additionally, medical equipment (e.g., MD B ) can send status updates to the controlling device (e.g., CD A ), while medical devices (e.g., MD B ) can receive data from a control device (e.g., CD A ) status updates.
[0039] Figure 2A Depicted are illustrative internal components of a control device 200 that are communicatively coupled to each other to provide wireless link pairing with a receiver device and control of a medical device identified by the receiver device in accordance with one or more embodiments illustrated and described herein. Figure 2A As shown, the control device 200 may include a local interface 202 (eg, a bus) that communicatively interconnects various components including, but not limited to, a processing device 204 , a memory 206 , input / output hardware 208 , a network interface hardware 210 , and / or a data storage device 212 .
[0040] The processing device 204, such as a computer processing unit (CPU), may be the central processing unit of the control device 200, and performs the calculations and logical operations required to execute the program. The processing device 204 may be used alone or in combination with Figure 2A One or more of the other elements disclosed herein may be combined to be an illustrative processing device, computing device, processor, or combination thereof, as such terms are used in this disclosure.
[0041] The memory 206, such as read-only memory (ROM) and random access memory (RAM), may constitute illustrative memory devices (e.g., non-transitory processor-readable storage media). Such memory 206 may include one or more programming instructions that, when executed by the processing device 204, cause the processing device 204 to perform various processes such as the processes described herein. Optionally, the program instructions may be stored on a tangible computer-readable medium, such as a digital disk, flash memory, memory card, USB drive, optical disk storage media (e.g., Blu-ray Disc, etc.). TM , CD, DVD) and / or other non-transitory processor-readable storage media.
[0042] In some embodiments, the program instructions contained in the memory 206 may be embodied as a plurality of software modules, wherein each module provides programming instructions for performing one or more tasks. Figure 2A As shown, the memory 206 may include one or more operation logic 214, communication logic 216 and UI logic 218. It should be understood that the present invention is based on the Figure 2A The various logic modules described are merely illustrative, and other logic modules, including logic modules that combine the functionality of two or more modules described above, may be used without departing from the scope of the present disclosure.
[0043] Still refer to Figure 2A , the data storage device 212 may generally be a storage medium independent of the memory 206, and may include a data repository for storing electronic data and / or data related to the location of the control device 200, the identification of the control device 200, configuration settings, UI data, etc. The data storage device 212 may be any physical storage medium, including but not limited to a hard disk drive (HDD), memory, removable storage, etc. The data storage device 212 is depicted as a local device, but it should be understood that the data storage device 212 may be a remote storage device 200 that is remote from the control device 200, such as a server computing device.
[0044] Illustrative data that may be contained within the data storage device 212 may include, for example, location data 220, configuration data 222, UI data 224, pairing data 226, etc. The pairing data 226 may include identification data (serial number, etc.) of one or more medical device identifiers to which the control device 200 is or was automatically paired via a receiver device in the methods described herein.
[0045] The input / output hardware 208 may generally include a wireless system 230, an indicator 232, a location system 234, and a user interface system 236. The wireless system 230 may include a transceiver 242 configured to send and receive wireless signals (e.g., RF, Bluetooth, UWB, etc.) according to respective wireless protocols. According to various aspects, RF may be used to efficiently transmit data with few errors. In certain aspects, data transmission techniques including encryption / decryption, forward error correction, etc. may be formulated. The indicator 232 may include a light emitting diode, an indicator light, etc. The location system 234 may include a global positioning system (GPS), a global navigation satellite system (GLONASS), a WiFi positioning system, etc. The user interface system may include a display 244 and / or a user interface control 246, which is configured to receive transmission control inputs through the input / output hardware 208 and display outputs received from the input / output hardware 208.
[0046] The network interface hardware 210 may generally provide the control device 200 with the ability to interface with one or more external devices (e.g., a healthcare facility server, a nurse station, etc.). Communication with the external devices may occur using various communication ports (not shown). Illustrative communication ports may be attached to a communication network such as the Internet, an intranet, a local network, a direct connection, etc.
[0047] It should be appreciated that in some embodiments, the input / output hardware 208 and the network interface hardware 210 may be combined into a single device that allows for communication with other devices, whether or not those other devices are located within the control device 200 .
[0048] It should be understood that Figure 2A The components shown are illustrative only and are not intended to limit the scope of the present disclosure. More specifically, Figure 2A The components in the present invention are shown as residing within the control device, but this is a non-limiting example. In some embodiments, one or more components may reside outside the control device. Similarly, one or more components may be embodied in other devices not specifically described herein. In addition, the present invention (e.g., Figure 3 ) describes various control devices, all of which are non-limiting examples. Other control devices may include a user's personal cellular phone with wireless communication channel capability, a nurse call system device, etc.
[0049] Figure 2BDepicted are illustrative internal components of a receiver device 201 that are communicatively coupled to each other to provide identification of a medical device in accordance with one or more embodiments illustrated and described herein. Figure 2B As shown, the receiver device 201 may include a local interface 203 (e.g., a bus) that communicatively interconnects various components, including but not limited to a processing device 205, a memory 207, input / output hardware 209, network interface hardware 211 and / or a data storage device 213.
[0050] The processing device 205, such as a CPU, can be the central processing unit of the receiver device 201, which performs the calculations and logical operations required to execute the program. The processing device 205 can be used alone or in conjunction with Figure 2B One or more of the other elements disclosed herein may be combined to be an illustrative processing device, computing device, processor, or combination thereof, as such terms are used in this disclosure.
[0051] The memory 207, such as ROM and RAM, may constitute an illustrative memory device (e.g., a non-transitory processor-readable storage medium). Such memory 207 may include one or more programming instructions that, when executed by the processing device 205, cause the processing device 205 to perform various processes such as the processes described herein. Optionally, the program instructions may be stored on a tangible computer-readable medium, such as a digital disk, flash memory, memory card, USB drive, optical disk storage media (e.g., Blu-ray TM , CD, DVD) and / or other non-transitory processor-readable storage media.
[0052] In some embodiments, the program instructions contained in the memory 207 may be embodied as a plurality of software modules, wherein each module provides programming instructions for performing one or more tasks. Figure 2B As shown, the memory 207 may include one or more operation logic 215 and communication logic 217. It should be understood that the present invention refers to Figure 2B The various logic modules described are merely illustrative, and other logic modules, including logic modules that combine the functionality of two or more modules described above, may be used without departing from the scope of the present disclosure.
[0053] Still refer to Figure 2B, the data storage device 213 may generally be a storage medium independent of the memory 207, and may include a data repository for storing electronic data and / or data related to the location of the receiver device 201, the identification of the receiver device 201, configuration settings, UI data, etc. The data storage device 213 may be any physical storage medium, including but not limited to an HDD, memory, removable storage, etc. The data storage device 213 is depicted as a local device, but it should be understood that the data storage device 213 may be a remote storage device 200 that is remote from the receiver device 201, such as a server computing device.
[0054] Illustrative data that may be contained within the data storage device 213 may include, for example, location data 221, configuration data 223, pairing data 227, etc. The pairing data 227 may include one or more medical device identifiers that the receiver device 201 has recognized along with pairing data associated with the control device 200 to which the receiver device is paired in the methods described herein.
[0055] The input / output hardware 209 may generally include an IR system 229, a wireless system 231, an indicator 233, a position system 235, and a user interface system 237. The IR system 229 may include an IR diode 239 (e.g., an infrared LED) configured to emit / transmit infrared light and a phototransistor 241 configured to receive infrared light and convert the infrared light into an electric current (e.g., according to an IR protocol). The IR system 229 may be unidirectional (e.g., the dashed line shows an optional phototransistor 241) or bidirectional (e.g., including a phototransistor 241). In addition, the phototransistor 241 may be omnidirectional to receive misaligned (e.g., within a defined tolerance) and / or reflected (e.g., reflected from a wall or an object in a room, etc.) light signals. According to various aspects, the IR system 229 may further include a transceiver module. The wireless system 231 may include a transceiver 243 configured to send and receive wireless signals (e.g., RFID, RF, Bluetooth, UWB, etc.) according to respective wireless protocols. According to various aspects, RF may be used to efficiently transmit data with few errors. In some aspects, data transmission techniques including encryption / decryption, forward error correction, etc. may be formulated. Indicator 233 may include a light emitting diode, an indicator light, etc. Position system 235 may include a GPS, GLONASS, WiFi positioning system, etc.
[0056] The network interface hardware 211 may generally provide the receiver device 201 with the ability to interface with one or more external devices (e.g., a healthcare facility server, a nurse station, etc.). Communication with the external devices may occur using various communication ports (not shown). Illustrative communication ports may be attached to a communication network such as the Internet, an intranet, a local network, a direct connection, etc.
[0057] It should be appreciated that in some embodiments, the input / output hardware 209 and the network interface hardware 211 may be combined into a single device that allows for communication with other devices, whether or not those other devices are located within the receiver device 201 .
[0058] It should be understood that Figure 2B The components shown are illustrative only and are not intended to limit the scope of the present disclosure. More specifically, Figure 2B The components in the embodiment are shown as being resident in the control device, but this is a non-limiting example. In some embodiments, one or more components may reside outside the control device. Similarly, one or more components may be embodied in other devices not specifically described herein.
[0059] Figure 2C Depicted are illustrative internal components of a medical device 250 that are communicatively coupled to each other to provide control device wireless link pairing authentication in accordance with one or more embodiments illustrated and described herein. Figure 2C As shown, the medical device 250 may include a local interface 252 (e.g., a bus) that communicatively interconnects various components including, but not limited to, a processing device 254, a memory 256, input / output hardware 258, network interface hardware 260, and / or a data storage device 262.
[0060] The processing device 254, such as a computer processing unit (CPU), can be the central processing unit of the medical device 250, which performs the calculations and logical operations required to execute the program. The processing device 254 can be used alone or in combination with Figure 2C One or more of the other elements disclosed herein may be combined to be an illustrative processing device, computing device, processor, or combination thereof, as such terms are used in this disclosure.
[0061] Memory 256, such as read-only memory (ROM) and random access memory (RAM), may constitute illustrative memory devices (e.g., non-transitory processor-readable storage media). Such memory 256 may include one or more programming instructions that, when executed by the processing device 254, cause the processing device 254 to perform various processes such as the processes described herein. Optionally, the program instructions may be stored on a tangible computer-readable medium, such as a digital disk, flash memory, memory card, USB drive, optical disk storage media (e.g., Blu-ray Disc, etc.). TM , CD, DVD) and / or other non-transitory processor-readable storage media.
[0062] In some embodiments, the program instructions contained in the memory 256 may be embodied as a plurality of software modules, wherein each module provides programming instructions for performing one or more tasks. Figure 2CAs shown, the memory 256 may include one or more operation logic 264, communication logic 266, and movement logic 268. It should be understood that the present invention is referred to as Figure 2C The various logic modules described are merely illustrative, and other logic modules, including logic modules that combine the functionality of two or more modules described above, may be used without departing from the scope of the present disclosure.
[0063] Still refer to Figure 2C , the data storage device 262 can generally be a storage medium independent of the memory 256, and can include a data repository for storing electronic data and / or data related to the location of the medical device 250, the identification of the medical device 250, configuration settings, etc. The data storage device 262 can be any physical storage medium, including but not limited to a hard disk drive (HDD), memory, removable storage, etc. The data storage device 262 is depicted as a local device, but it should be understood that the data storage device 262 can be a remote storage device 200 away from the medical device 250, such as a server computing device.
[0064] Illustrative data that may be contained within the data storage device 262 may include, for example, location data 270, configuration data 272, pairing data 274, etc. The pairing data 274 may include one or more control device identifiers to which the medical device 250 is or was automatically paired and / or a receiver device 201 to which the medical device 250 has communicated in the methods described herein.
[0065] The input / output hardware 258 may generally include an IR system 278, a wireless system 280, an indicator 282, and a position system 284. The IR system 278 may include an IR diode 288 (e.g., an infrared LED) configured to emit / transmit infrared light and a phototransistor 290 configured to receive infrared light and convert the infrared light into an electric current (e.g., according to an IR protocol). The IR system 278 may be unidirectional (e.g., the dashed line shows an optional IR diode 288) or bidirectional (e.g., including an IR diode 288). In addition, the phototransistor 290 may be omnidirectional to receive misaligned (e.g., within a defined tolerance) and / or reflected (e.g., reflected from a wall or an object in a room, etc.) light signals. According to various aspects, the IR system 278 may further include a transceiver module. The wireless system 280 may include a transceiver 292 configured to send and receive wireless signals (e.g., RFID, RF, Bluetooth, UWB, etc.) according to respective wireless protocols. According to various aspects, RF may be used to efficiently transmit data with few errors. In some aspects, data transmission techniques including encryption / decryption, forward error correction, etc. may be formulated. Indicator 282 may include a light emitting diode, an indicator light, etc. Position system 284 may include a global positioning system (GPS), a global navigation satellite system (GLONASS), a WiFi positioning system, etc.
[0066] The network interface hardware 260 may generally provide the medical device 250 with the ability to interface with one or more external components (e.g., a medical facility server, a nurse station, etc.). Communication with external devices may occur using various communication ports (not shown). Illustrative communication ports may be attached to a communication network such as the Internet, an intranet, a local network, a direct connection, etc.
[0067] It should be understood that in some embodiments, the input / output hardware 258 and the network interface hardware 260 may be combined into a single device that allows communication with other devices, whether or not those other devices are located within the medical device 250 .
[0068] It should be understood that Figure 2C The components shown are illustrative only and are not intended to limit the scope of the present disclosure. More specifically, Figure 2C The components in are illustrated as residing within the medical device 250, but this is a non-limiting example. In certain embodiments, one or more components may reside outside the medical device 250. Similarly, one or more components may be embodied in other devices not specifically described herein.
[0069] Figure 3 An illustrative wireless link pairing authentication system 300 is depicted, including a rail-mounted lift 302 as an illustrative medical device, a receiver device 340, and a plurality of remote devices 304, 306, 308 as control devices, in accordance with one or more embodiments illustrated and described herein. Figure 3 , the track lift 302 is coupled to a track 310. According to various aspects, the track 310 can be along a room (e.g., Figure 1 A room in the room), along the ceiling of more than one room (e.g. Figure 1 310). More specifically, the track lift 302 includes a lift unit 312 slidably coupled to the track 310 via a carriage 314. The lift unit 312 can be used to support and / or lift the main body with the help of a lifting belt, which is coupled to a motor (not shown) contained in the lift unit 312. The motor promotes the extension or retraction of the lifting belt 316 from the lift unit 312, thereby raising or lowering the main body attached to the lifting belt 316. According to various embodiments, the main body can be attached to the lifting belt 316, and the lifting belt 316 has a suspension rod 318 or a similar accessory attached to the lifting belt 316 via a joint 317. The suspension rod 318 or a similar accessory can be attached to the sling or sling where the main body is positioned, thereby facilitating the lifting operation.
[0070] Various control units, such as the tethered handheld control unit 304, the wireless handheld control unit 306, and / or the wall-mounted control unit 308, can be wirelessly coupled to the receiver device 340 (e.g., via RF, Bluetooth, UWB, etc.). In one aspect, such wireless coupling can be permanent based on the receiver device 340 being maintained in a particular room, regardless of whether the control unit resides in the room. According to the methods described herein, the receiver device 340 can detect and identify a medical device (e.g., a track-mounted lift 302). In one aspect, the receiver device 340 can utilize an infrared sensor 342 to detect an infrared signal periodically emitted by the track-mounted lift 302. In another aspect, the receiver device 340 can utilize a camera 344 to visually scan or otherwise visually detect a visual identifier displayed on the track-mounted lift 302. In yet another aspect, the receiver device 340 can wirelessly detect a wireless signal emitted by the track-mounted lift 302. Once the receiver device 340 has identified the track-mounted lift 302, various components of the track-mounted lift 302 (such as the lift unit 312 and / or its components) can operate in conjunction with a control device such as a tethered handheld control unit 304, a wireless handheld control unit 306 and / or a wall-mounted control unit 308 that is communicatively coupled to the lift unit 312.
[0071] Given that Figure 3, the tethered handheld control unit 304 can be directly wired to the riser unit 312 and / or wirelessly coupled or paired to the riser unit 312 (e.g., according to the methods described herein) to facilitate remote operation of the track-mounted riser 302. According to various aspects, the tethered handheld control unit 304 can include a display 320 and one or more user interface controls 322A (e.g., for extending the lift belt 316) and user interface controls 322B (e.g., for retracting the lift belt 316). Similarly, the wireless handheld control unit 306 can be wirelessly coupled or paired to the riser unit 312 (e.g., according to the methods described herein) and can include a display 324 and one or more user interface controls 326A (e.g., for extending the lift belt 316), user interface controls 326B (e.g., for retracting the lift belt 316), user interface controls 326C (e.g., for translating the riser unit 312 in a first lateral direction L1 along the track 310), and user interface controls 326D (e.g., for translating the riser unit 312 in a second lateral direction L2 along the track 310). ), and the wall-mounted control unit 308 can be wirelessly coupled or paired to the lift unit 312 (e.g., according to the methods described herein) and can include a display 328 and one or more user interface controls 330A (e.g., for extending the lift belt 316), a user interface control 330B (e.g., for retracting the lift belt 316), a user interface control 330C (e.g., for translating the lift unit 312 in a first lateral direction L1 along the track 310), and a user interface control 330D (e.g., for translating the lift unit 312 in a second lateral direction L2 along the track 310). Further, the user interface controls of the wall-mounted control unit 308 can activate the lift unit 312, pair the main body with the lift unit 312, return the lift unit 312 to a "home" position, receive information from the lift unit 312 (e.g., battery status, the size of the load supported by the lift unit, etc.), cause an emergency stop of the lift unit 312, reset the lift unit 312, etc.
[0072] Reference Figure 4A and Figure 4B According to another aspect of the present disclosure, the rail-type lifter 302 (e.g., Figure 3) can operate in conjunction with a boom control unit 400 positioned on boom 318 and / or a coupling control unit 410 positioned on a joint 317 attached to the D-shaped distal end of the lifting belt 316. Boom control unit 400 can be recognized by receiver device 340 (wirelessly, infrared, and / or visually) and wirelessly coupled or paired to riser unit 312 (e.g., according to methods described herein), and can include one or more user interface controls 402A (e.g., for extending lifting belt 316) and user interface controls 402B (e.g., for retracting lifting belt 316). Similarly, coupling control unit 410 can be recognized by receiver device 340 (wirelessly, infrared, and / or visually) and wirelessly coupled or paired to riser unit 312 (e.g., according to methods described herein), and can include one or more user interface controls 412A (e.g., for extending lifting belt 316) and user interface controls 412B (e.g., for retracting lifting belt 316).
[0073] Given that Figure 3 , Figure 4A and Figure 4B , multiple control devices (e.g., tethered handheld control unit 304, wireless handheld control unit 306, wall-mounted control unit 308, boom-mounted control unit 400, coupled control unit 410, etc.) may have been physically present in the room, physically brought into the room, and / or physically taken out of the room.
[0074] According to certain aspects of the present disclosure, medical equipment (e.g., track-mounted lift 302) can be allowed to be moved within a room. Figure 3 and Figure 4B , the control device is physically maintained in the room (e.g., wall-mounted control unit 308) or physically maintained coupled to a medical device that is itself located in the room (e.g., tethered handheld control unit 304, coupled control unit 410), wherein the receiver device 340 is maintained in line of sight to identify the medical device, and the control device can be configured to control the medical device identified by the receiver device 340. For example, the control device 200 ( Figure 2A ) may store pairing data 226 (e.g., the associated RD ID in the fixed pairing file and / or the MD ID of the rail-mounted elevator 302) on its data storage device ( Figure 2A 212). These aspects are further described with reference to Figure 3 and Figure 4A, one or more control devices may not be physically maintained in the room (e.g., the wireless handheld control unit 306 and the boom-mounted control unit 400). In these aspects, the control unit can be configured to not only recognize and pair the medical devices when they are brought into the room, but also to periodically or continuously monitor pairing with the medical devices in conjunction with recognition of the medical devices by the receiver devices in the room. Periodicity as used herein may refer to time intervals or time periods that occur regularly (e.g., every "X" seconds, every "Y" minutes, etc.).
[0075] Continuing with this example, the control device may send pairing data (eg, Figure 2A 226, such as the MD ID and / or RD ID associated in the temporary pairing file) is stored in its data storage device ( Figure 2A 212), and the receiver device may periodically determine whether it is still receiving each authenticated receiver device identifier and / or control device identifier (e.g., RD ID and / or CD ID) through its optical communication channel (or wireless channel, or otherwise via visual detection). According to various aspects, if the receiver device 340 is still optically / visually receiving the authenticated medical device identifier (e.g., stored in the temporary pairing file), the medical device (e.g., a track-mounted lift) may remain authenticated with the paired control device, and if the infrared sensor 342 and / or camera 344 of the receiver device 340 no longer optically / visually receives the authenticated control device identifier, the control device may be automatically disassociated from the medical device (e.g., a medical device deemed to be physically removed from the room).
[0076] Further in view of Figure 3 , Figure 4A and Figure 4B, a medical device fixedly positioned in a room can be configured to establish a hierarchy for control inputs received from multiple authenticated paired control devices (e.g., received at the same time or nearly the same time). For example, the medical device can be configured to prioritize control inputs received from a first group including control devices physically held in the room (e.g., tethered handheld control unit 304, wall-mounted control unit 308, and / or coupled control unit 410) relative to control inputs received from a second group including control devices that may not be physically held in the room (e.g., wireless handheld control unit 306 and / or boom-mounted control unit 400), and utilize receiver device 340. Further in this example, the medical device can be configured to prioritize control inputs received from control devices within the first group (e.g., tethered handheld control unit 304 is prioritized over coupled control unit 410 over wall-mounted control unit 308, etc.) and / or prioritize control inputs received from control devices within the second group (e.g., boom-mounted control unit 400 is prioritized over wireless handheld control unit 306, etc.). It should be understood here that the above-described hierarchy is a non-limiting example and other hierarchies may be established.
[0077] According to other aspects of the present disclosure, the medical device (e.g., track-mounted lift 302) may not be fixedly positioned in a room. For example, the lift unit may be moved along track 310 ( Figure 3 ) from a room (e.g. Figure 1 A in the room) to another room (for example, Figure 1 B in a given room), or move between subspaces of a given room. Figure 3 and Figure 4B , control devices (e.g., tethered handheld control unit 304, coupled control unit 410) that are physically coupled to the medical device itself are maintained in the line of sight of the receiver device 340, and the medical device can be configured to authenticate and maintain pairing to all such control devices. For example, the track-mounted elevator 302 can send pairing data ( Figure 2C 274, such as the RD ID and / or CD ID associated in the fixed pairing file) is stored in its data storage device ( Figure 2C 262). These aspects are further described with reference to Figure 3 and Figure 4A, one or more control devices may not be physically coupled to the medical device itself. This may include control devices that are physically maintained in a given room (e.g., wall-mounted control unit 308) and / or control devices that may not be physically maintained in any given room (e.g., wireless handheld control unit 306, boom-mounted control unit 400). In these aspects, the medical device may be configured to not only authenticate and pair these control devices and receiver devices 340 in the room, but also periodically or continuously monitor authenticated pairings with these control devices via receiver device 340.
[0078] Continuing with this example, the receiver device 340 may send pairing data (e.g., Figure 2C 274, such as the MD ID and / or CD ID associated in the temporary pairing file) is stored in its data storage device (e.g., Figure 2B 213 in the optical communication channel), and can periodically determine whether each authenticated medical device identifier (e.g., MD ID) is still received through its optical communication channel. According to various aspects, when movement is detected, the receiver device 340 can be configured to continuously monitor the authenticated pairing with these medical devices. Accordingly, if the authenticated medical device identifier (e.g., MD ID for medical devices between rooms or between subspaces of a given room) is still optically / visually received, the medical device (e.g., track-mounted lift) can maintain the authenticated paired control device, and if the authenticated medical device identifier is no longer optically / visually received, the control device can automatically disassociate with the medical device. Further in this regard, based on the identification (IR, wireless, visual scanning) of the receiver device 340 of the medical device arriving in the new room, as the medical device moves between rooms (or between subspaces of a given room), the receiver device 340 can be configured to authenticate the new medical device and pair it with the control device (e.g., the wall-mounted control unit 308 in the new room).
[0079] Further in view of Figure 3 , Figure 4A and Figure 4B, a medical device fixedly positioned within a room can be configured to be part of a hierarchy that accepts control inputs from multiple authenticated paired control devices (e.g., received at the same time or near the same time) via a receiver device. For example, the medical device can be configured to prioritize control inputs received from a first group that includes control devices that are physically maintained coupled to the medical device itself (e.g., tethered handheld control unit 304, coupled control unit 410) relative to control inputs received from a second group that includes control devices that are physically maintained in a given room (e.g., wall-mounted control unit 308) and / or control devices that may not be physically maintained in any given room (e.g., wireless handheld control unit 306, boom-mounted control unit 400). In another example, the first group can include control devices (e.g., wireless handheld control unit 306) for moving the medical device between rooms or control devices for moving the medical device between subspaces within a given room. Here, for the track-mounted lift 302, it may be desirable to use the wireless handheld control unit 306 to move the track-mounted lift 302 between rooms or between subspaces within a given room in preference to the tethered handheld control unit 304 and / or the coupled control unit 410. Further in this example, the medical device may be configured to prioritize control inputs received from control devices within the first group (e.g., the tethered handheld control unit 304 or the wireless handheld control unit 306 is prioritized over the coupled control unit 410, etc.) and / or prioritize control inputs received from control devices within the second group (e.g., the wireless handheld control unit 306 is prioritized over the boom-mounted control unit 400 is prioritized over the wall-mounted control unit 308, etc.). It should be understood that the above-described hierarchy is a non-limiting example, and other hierarchies may be established.
[0080] Figure 5 A flow chart is depicted of an illustrative method 500 for pairing a medical device with a control device via a receiver device using an optical communication channel in accordance with one or more embodiments of the present disclosure. Figure 5 , MD of Medical Devices X The control device can be authenticated / identified and automatically paired. At block 502, the receiver device RD X Can be used with control device CD X Pairing. Receiver device RD X CD with control equipment X The medical device MD may be paired via a wireless communication channel (eg, an RF channel) so that they may not be located in the same room. X Can not communicate with any receiver device RD X Associated and / or not in any receiver device RD X At the same time, in block 506, the receiver device RD XThe medical device MD may not be associated with any medical device (MD) and / or may not be in the line of sight of any medical device (MD). From block 504, proceed to block 508, the medical device MD X Its identifier MD can be displayed visually X ID and / or periodically transmits its identifier through its optical communication channel (e.g., IR channel). Periodicity as described herein may refer to a time interval or time period that occurs periodically (e.g., every "X" seconds, every "Y" minutes, etc.). According to another aspect, the medical device MD X can be configured to manually send its identifier MD via its optical communication channel (eg, IR channel) X ID (for example, when a user touches a medical device MD X At the same time, in block 510, the receiver device RD X Can wait for a medical device identifier (e.g., MD ID) via its optical communication channel and / or visually via its camera. Still referring to Figure 5 , at block 512, the medical device MD X and receiver device RD X can be positioned in line of sight with respect to each other. At block 514, the receiver device RD X through its optical communication channel and / or via the receiver device RD X Vision (camera) detection receives medical device identifier MD X ID. At block 516, the control device CD X Can be targeted at medical device MD X Independent of the receiver device RD X The medical device identifier MD sent by X ID scans its wireless communication channel. At decision block 518, the control device CD X It can be determined whether the receiver device RD X and Medical Device MD X Receive the same medical device identifier MD X If there is no match between the medical device identifiers, the flowchart returns to block 508 to allow the medical device MD X Again optically (or visually) providing its identifier MD X ID, while at block 510, the receiver device RD X Waiting for another Medical Device Identifier MD ID.
[0081] Returning to decision block 518, if the received X and Medical Device MD X If the medical device identifiers of the medical devices MDX It can communicate with the control device CD through its wireless communication channel X Automatic association. According to various aspects, medical equipment MD X This association can be used as paired data (e.g. Figure 2C 274) is stored in its data storage device (e.g., Figure 2C At the same time, in box 526, the control device CD X Can authenticate and automatically pair medical devices MD. Control device CD X May not be associated with any medical device and / or not in sight of any medical device. From block 520 proceed to block 522 (eg, dashed lines are shown as optional), the medical device MD X A visual indicator may be displayed that it is associated with the control device. According to certain aspects, the visual indicator may be a light emitting diode (LED) (e.g., Figure 2C 282), which can be used in medical device MD X According to another aspect, when the medical device MD X When the control device is associated with the visual indicator through its wireless channel, the visual indicator can be flashing and / or non-flashing. According to another aspect, the visual indicator can include a display indicating the control device associated with it. At the same time, at block 528 (e.g., dashed lines are shown as optional), the control device CD X A visual indicator may be displayed that it is associated with the medical device. According to certain aspects, the visual indicator may be a light emitting diode (LED) ( Figure 2C 282), which is in the control device CD X According to another aspect, when the control device CD X When associated with a medical device through its wireless channel, the visual indicator may flash and / or light up without flashing. According to yet another aspect, the visual indicator may include a display indicating the medical device associated with it. From block 522, proceed to block 524, the same as the control device CD X After authentication and pairing, the medical device MD X Status information can be sent to the control device CD X and / or from the control device CD X Receive control input or command. At the same time, in block 530, the medical device MD X After authentication pairing, control device CD X Control input or command can be sent or issued to medical device MD X and / or from a medical device MD X Receive status information. According to various aspects of the present disclosure, the medical device MD X It is possible not to send status information to the control device CDX and / or not from the control device CD X Receives control input or commands and controls the device CD X Control input or command may not be sent or issued to the medical device MD X and / or not from a medical device MD X Status information is received until such mutual authentication occurs.
[0082] Figure 6 A flow chart is depicted of an illustrative method 600 for pairing a medical device with a control device via a receiver device using a wireless communication channel in accordance with one or more embodiments of the present disclosure. Figure 6 , MD of Medical Devices X The control device can be authenticated / identified and automatically paired. At block 602, the receiver device RD X Can be used with control device CD X Pairing. Receiver device RD X CD with control equipment X The medical device MD may be paired via a wireless communication channel (eg, an RF channel) so that they may not be located in the same room. X may not be paired or otherwise wirelessly associated with any receiver device RD. Meanwhile, at block 606, the receiver device RD X The medical device MD may not be paired or otherwise wirelessly associated with any medical device (MD). X The wireless communication channel (eg, RF channel) may periodically send its identifier MD X ID. According to another aspect, the medical device MD X Can be configured to manually send its identifier MD via its wireless communication channel X ID (for example, when a user touches a medical device MD X At the same time, in block 610, the receiver device RD X In the medical device (MD X ) can periodically search for an RFID medical device identifier (eg, MD ID) through its wireless communication channel after power is provided.
[0083] Still refer to Figure 6 , at block 614, the receiver device RD X The medical device identifier MD may be received via its wireless communication channel (such as via RFID) X ID. At block 614, the control device CD X Can be targeted at medical device MD X Independent of the receiver device RDX The medical device identifier MD sent by X ID scans its wireless communication channel. At decision block 616, the control device CD X It can be determined whether the receiver device RD X and Medical Device MD X Receive the same medical device identifier MD X If there is no match between the medical device identifiers, the flowchart returns to block 608 to allow the medical device MD X Periodically wirelessly transmits its identifier MD X ID, while at block 610, the receiver device RD X Periodically searches for other incoming medical device identifiers MD through its wireless communication channel X Returning to decision block 616, if the received X and Medical Device MD X If the medical device identifiers of the medical devices MD X It can communicate with the control device CD through its wireless communication channel X Automatic association. According to various aspects, medical equipment MD X This association can be used as paired data (e.g. Figure 2C 274) is stored in its data storage device (e.g., Figure 2C At the same time, in box 624, the control device CD X Can authenticate and automatically pair medical devices MD. Control device CD X May not be associated with any medical device and / or not in sight of any medical device. From block 618 proceed to block 620 (eg, dashed line shown as optional), the medical device MD X A visual indicator may be displayed that it is associated with the control device. According to certain aspects, the visual indicator may be a light emitting diode (LED) (e.g., Figure 2C 282), which can be used in medical device MD X According to another aspect, when the medical device MD X When the control device is associated with the control device through its wireless channel, the visual indicator may flash and / or light up without flashing. According to another aspect, the visual indicator may include a display indicating the control device associated with it. At the same time, at block 626 (e.g., dashed lines are shown as optional), the control device CD X A visual indicator may be displayed that it is associated with the medical device. According to certain aspects, the visual indicator may be a light emitting diode (LED) ( Figure 2C 282), which is in the control device CDX According to another aspect, when the control device CD X When associated with a medical device through its wireless channel, the visual indicator may flash and / or light up without flashing. According to yet another aspect, the visual indicator may include a display indicating the medical device associated with it. From block 620, proceed to block 622, the same as the control device CD X After authentication and pairing, the medical device MD X Status information can be sent to the control device CD X and / or from the control device CD X Receive control input or command. At the same time, in block 628, the medical device MD X After authentication pairing, control device CD X Control input or command can be sent or issued to medical device MD X and / or from a medical device MD X Receive status information. According to various aspects of the present disclosure, the medical device MD X It is possible not to send status information to the control device CD X and / or not from the control device CD X Receives control input or commands and controls the device CD X Control input or command may not be sent or issued to the medical device MD X and / or not from a medical device MD X Status information is received until such mutual authentication occurs.
[0084] Figure 7 A flow chart is depicted of an illustrative method 700 of associating or disassociating a medical device, a receiver device, and a control device in accordance with one or more embodiments of the present disclosure. Figure 7 At block 702, as described herein, the medical device MD X The paired control device CD may be authenticated via a wireless communication channel (eg, an RF channel) X , and / or control device CD X Can authenticate and pair medical devices MD through wireless communication channels X At decision block 704, the medical device MD X can be determined with the receiver device RD X Whether the optical communication channel (e.g., IR channel) or wireless channel (e.g., RFID) between the two devices is weak (e.g., below a predetermined threshold signal strength), or the receiver device RD X Can determine the paired medical device MD X Whether the optical communication channel or the wireless communication channel between them is weak (for example, the optical signal strength is lower than a predetermined threshold).X and / or receiver device RD X Can be configured to use optical communication channels and / or wireless communication channels as medical devices MD X If it is determined at decision block 704 that the optical communication channel or the wireless communication channel is weak, then at block 716, the medical device MD X Can be configured as the same control device CD X Automatically disassociate and / or control device CD X Can be configured as the same medical device MD X According to another aspect, the medical device MD X Can be configured as the same control device CD X Manual disassociation (for example, when the user touches the medical device MD X ), and / or the control device CD X Can be configured as the same medical device MD X Manual disassociation (for example, when the user touches the control device CD X As described herein, when disassociating, at block 718, the control device CD X The wireless communication channel may be monitored for a medical device identifier (eg, MD ID), and at block 712, the control device CD X Can initiate a new medical device (e.g., MD Y ) authentication pairing.
[0085] If it is determined at decision block 704 that the optical communication channel or the wireless communication channel is not weak, then at block 714, the medical device CD X The control device CD that is paired with the authentication can be determined X whether the wireless communication channel (e.g., RF channel) between the two devices is weak (e.g., lower than a predetermined threshold wireless signal strength), and / or the control device CD X Can determine the medical device MD that is paired with the authentication X Is the wireless communication channel between the medical device MD weak (eg, below a predetermined threshold wireless signal strength)? If it is determined at decision block 706 that the wireless communication channel is weak, then at block 716, the medical device MD X Can be configured similarly to the same control device CD X Automatically disassociate and / or control device CD X Can be configured similarly to the same medical device MD X Automatically disassociate.
[0086] At decision block 708, the control device CD XCan determine whether a new or different medical device identifier MD is received via its wireless communication channel Y If it is determined at decision block 708 that a new or / different medical device identifier MD is not received via the wireless communication channel. Y ID, then in block 702, the control device CD X Can maintain authentication through its wireless communication channel paired medical device MD Y If it is determined at decision block 708 that a new or / different medical device identifier MD is received via the wireless communication channel Y ID, then at block 710, the receiver device RD X Can be configured to wait for a medical device MD to pair with it X Associated medical device identifier MD X If it is determined at decision block 712 that a medical device identifier MD has been detected, X ID, then in block 792, the control device CD X Can maintain authentication through its wireless communication channel paired medical device MD X .according to Figure 7 In the aspect described, the control device CD X Only one medical device can be authenticated and paired. This prevents the control device CD X The control signal is sent to more than one medical device. It should be understood that other embodiments may include a control device CD X Authentication pairing of multiple medical devices (e.g., in the same room, such as in a sub-space of a given room, or between different rooms). If it is determined at decision block 712 that the medical device identifier MD has not been detected X ID, then in block 714, the control device CD X It can communicate with medical equipment MD through its wireless communication channel X Automatically disassociated, and at block 720, the receiver device RD X and / or control device CD X Can initiate MD with new or different medical device Y Authentication pairing.
[0087] Figure 8 A flowchart of an illustrative method 800 of a control device issuing commands or control inputs to a paired medical device according to one or more embodiments of the present disclosure is depicted. According to various aspects, the method 800 can be used for all control functions, or only for major key functions (e.g., actuating a motor, turning on a pump, etc.). Figure 8 At block 802, as described herein, control device CD X Can authenticate and pair medical devices MD through their wireless communication channelsX At decision block 804, the control device CD X Can be configured to determine (for example, based on Figure 2A Whether to issue or send the command or control input to the medical device MD X If it is determined that the command or control input is not to be issued or sent to the medical device MD X , then in block 802, the control device CD X Can maintain pairing of medical devices MD through its wireless communication channel X If it is determined that the command or control input is sent to the medical device MD X , then in decision block 806, the control device CD X It may be configured to determine whether the wireless communication channel is weak (eg, below a predetermined threshold wireless signal strength). If it is determined that the wireless communication channel is weak, then at block 808, the control device CD X Can be configured to communicate with medical devices MD via wireless communication channels X Automatically disassociate. In block 810 (the dashed line indicates an optional step), control device CD X Can be configured to update its visual indicator to reflect the disassociation (e.g., LED turns off).
[0088] If it is determined that the wireless communication channel is not weak, then at block 812, the receiver device RD X Can be configured to poll a medical device MD via its optical communication channel X (e.g., sending a query token) or polling the medical device MD via its wireless channel X According to an alternative aspect (as shown by the dashed line), the method may proceed directly from decision block 804 to block 812 and continue as described herein. At decision block 814, the receiver device RD X It can be configured to determine whether a medical device MD has received a signal from the medical device MD via its optical communication channel or wireless communication channel. X Receive a response (e.g., response token, MD ID, etc.). If the receiver device RD X Not from medical device MD X Upon receiving the response, at block 816, the control device CD X Can be configured not to send commands or control inputs to or from the medical device MD X In block 818 (dashed line indicates an optional step), the control device CD X Can be configured to update its visual indicator to reflect the same medical device MD X Pairing issues (e.g., medical device MD X Not in receiver device RD X In the sight of the medical device MDX Must be relocated to the receiver device RD X If the receiver device RD X MD from Medical Devices X Upon receiving the response, at block 820, the control device CD X Can be configured to send commands or control inputs to medical devices MD via its wireless communication channel X According to these aspects, if the medical device MD X Move to an adjacent room (e.g. no longer located at the receiver device RD X within the line of sight), the control device CD X Unable to send command or control input to medical devices (MD X ), but can be sent down in other ways through stronger wireless communication channels.
[0089] According to another embodiment, review Figure 2A to Figure 2C , the control device 200 may include a location system 234, the receiver device 201 may include a location system 235, and the medical device 250 may include a location system 284. In these aspects, as described herein, the medical device 250, the receiver device 201, and / or the control device 200 may be configured to further send respective location information (e.g., MD LOC, RD LOC, and CD LOC) and respective identifiers (e.g., MD ID, RD ID, and CD ID). In these aspects, the control device 200 may be configured to compare the received MD LOC (received from the receiver device and / or the medical device) with its CD LOC to determine in part whether to authenticate the paired medical device. In certain aspects, an initial range (e.g., a radius of about 2 meters to about 5 meters) may be used for initial authentication, while a control range (e.g., an average room size) may be used for disassociation. In other aspects, the control device 200 may be configured to use the medical facility location MF LOC location beacon with known coordinates to adjust / correct its CD LOC and / or RD LOC and the received MD LOC. Likewise, the control device 200 may be configured to use the medical facility location MF LOC location beacon with known coordinates to adjust / correct its CD LOC and received MD LOC and / or RDLOC. According to various embodiments, these aspects may be used to further validate other authentication / identification methods described herein.
[0090] According to various embodiments described herein, each of the optical communication channel (e.g., IR channel) and the wireless communication channel (e.g., RFID channel) can be configured as a one-way communication channel or a two-way communication channel. In addition, although the line-of-sight communication channel is described herein as an optical communication channel, the line-of-sight communication channel can be any auxiliary line-of-sight communication channel that ensures line-of-sight only. That is, the line-of-sight communication channel is accessible to the device to be controlled (e.g., medical device) when it is visible from the identification point (e.g., receiver device).
[0091] It should be understood that the systems and methods described herein are suitable for pairing a medical device with a control device using a line-of-sight optical link (e.g., an IR link) through a receiver device. Specifically, the systems and methods described herein automatically authenticate / identify a configurable pairable wireless connection (e.g., an RF channel) to be used to perform control actions on a medical device (e.g., a track-mounted lift) to ensure that the control input comes from a control device (e.g., a tethered handheld control unit, a wireless handheld control unit, a wall-mounted control unit, a boom-mounted control unit, a coupled control unit, etc.) located in the same room as the medical device. These systems and methods ensure that the control input from the control device is only for medical devices that are directly observable or viewable by the user of the control device.
[0092] It should be understood that various elements are described as optional, which is only for one or more illustrative embodiments, such as storage Figure 2A 206 and Figure 2B The program instructions in 207 and Figure 2A 234 Figure 2B 235 and 241, Figure 2C 284 and 288, Figure 5 522 and 528, Figure 6 in 620 and 626 and Figure 8 The features depicted in 810 and 818 in FIG. That is, in other embodiments, these elements may be required. In addition, the description of these elements as optional (e.g., drawn as dashed lines in the figure) does not imply the need for the processes described for other elements in each figure.
[0093] Although specific embodiments are illustrated and described herein, it should be understood that various changes and modifications may be made without departing from the spirit and scope of the claimed subject matter. In addition, although various aspects of the claimed subject matter are described herein, these aspects do not have to be used in combination. Therefore, the appended claims are intended to cover all such changes and modifications within the scope of the claimed subject matter.
Claims
1. A control device capable of automatic pairing, comprising: a first communication system configured to communicate via a first communication channel; a second communication system configured to communicate via a second communication channel different from the first communication channel; processor; and a memory storing program instructions which, when executed by the processor, cause the processor to: receiving, from a medical device via the first communication channel, a first identifier associated with the medical device; receiving, from a receiver device via the second communication channel, a second identifier associated with the medical device; determining that the first identifier received via the first communication channel matches the second identifier received via the second communication channel; and Automatically pairing with a medical device associated with a matching identifier via the first communication channel.
2. The automatically pairable control device according to claim 1, wherein: The first communication channel and the second communication channel are wireless communication channels.
3. The automatically pairable control device according to claim 1 or 2, wherein: The third communication channel is a wireless communication channel or an optical communication channel; or The receiver device includes a camera to visually detect a visual identifier located in a line of sight between the receiver device and the medical device.
4. The automatically pairable control device according to claim 1 or 2, wherein: When the program instructions are executed by the processor, the processor further causes the processor to: receiving status data from the medical device via the first communication channel associated with the matching identifier, wherein a control input is used to control a function of the medical device; and The control input is sent to the medical device via the first communication channel associated with the matching identifier, wherein the control input is used to control a function of the medical device.
5. The automatically pairable control device according to claim 3, wherein: The optical communication channel is an infrared (IR) communication channel, and the wireless communication channel is a radio frequency (RF) communication channel.
6. The automatically pairable control device according to claim 1 or 2, wherein: When the program instructions are executed by the processor, the processor further causes the processor to: determining that at least one of the first communication channel and the second communication channel is associated with a signal below a predetermined threshold strength; and Disassociating from the medical device associated with the matching identifier.
7. The automatically pairable control device according to claim 1 or 2, wherein: When the program instructions are executed by the processor, the processor further causes the processor to: Automatically disassociating from the medical device based on the first identifier no longer being detected via the first communication channel or the second identifier no longer being detected via the first communication channel.
8. A system for automatically pairing devices, comprising: A control device capable of automatic pairing, comprising: a first communication system configured to communicate via a first communication channel; a second communication system configured to communicate via a second communication channel different from the first communication channel; Processor; and a memory storing program instructions which, when executed by the processor, cause the processor to: receiving, from the automatically-pairable medical device via the first communication channel, a first identifier associated with the medical device; receiving, via a second communication channel, a second identifier associated with a medical device from a receiver device paired with the control device; determining that a first identifier received via a first communication channel matches a second identifier received via a second communication channel; and automatically pairing with a medical device associated with the matching identifier via the first communication channel; and The receiver device, paired with the control device, is configured as follows: receiving a second identifier associated with the medical device from the medical device via a third communication channel different from the first communication channel and the second communication channel; and A second identifier associated with the medical device is sent to the control device via the second communication channel.
9. The system of claim 8, wherein: The first communication channel and the second communication channel are wireless communication channels.
10. The system of claim 8 or 9, wherein: The third communication channel is a wireless communication channel or an optical communication channel; or, the receiver device comprises a camera to visually detect a visual identifier located in a line of sight between the receiver device and the medical device.
11. The system of claim 8 or 9, wherein: When the program instructions are executed by the processor, the processor further causes the processor to: A control input is sent to a medical device associated with the matching identifier, the control input being used to control a function of the medical device.
12. The system of claim 10, wherein: The optical communication channel is an infrared (IR) communication channel, and the wireless communication channel is a radio frequency (RF) communication channel.
13. The system of claim 8 or 9, wherein: When the program instructions are executed by the processor, the processor further causes: At least one of the first communication channel and the second communication channel is determined to be associated with a signal below a predetermined threshold strength and is disassociated from the medical device associated with the matching identifier.
14. The system of claim 8 or 9, wherein: When the program instructions are executed by the processor, the processor further causes the processor to: Automatically disassociating from the medical device based on the first identifier no longer being detected via the first communication channel or the second identifier no longer being detected via the first communication channel.
15. The system of claim 8 or 9, wherein: The control device further includes a visual indicator, and wherein the program instructions, when executed by the processor, further cause the processor to update the visual indicator to reflect that the medical device is not within the line of sight of the receiver device.
16. A system for automatically pairing devices, comprising: A control device capable of automatic pairing, comprising: a first communication system configured to communicate via a first communication channel; a second communication system configured to communicate via a second communication channel different from the first communication channel; Processor; and A memory storing program instructions which, when executed by a processor, cause the processor to: receiving, from the automatically-pairable medical device via the first communication channel, a first identifier associated with the medical device; receiving, via a second communication channel, a second identifier associated with the medical device from a receiver device paired with the control device; A first identifier received via the first communication channel matches a second identifier received via the second communication channel; and automatically pairing the control device with the medical device associated with the matching identifier via the first communication channel; a receiver device, paired with the control device, comprising: a communication system configured to communicate via a third communication channel different from the first communication channel and the second communication channel, and configured to: receive a second identifier associated with the medical device from the medical device via the second communication channel; and transmitting a second identifier associated with the medical device to the control device via the second communication channel; and Medical device configurations that can be automatically paired are: transmitting a first identifier associated with the medical device to the automatically pairable control device via a first communication channel; A first identifier associated with the medical device is transmitted to the receiver device over the second communication channel.
17. The system of claim 16, wherein: The first communication channel and the second communication channel are wireless communication channels.
18. The system of claim 16 or 17, wherein: The third communication channel is a wireless communication channel or an optical communication channel, or the receiver device includes a camera to visually detect a visual identifier located in a line of sight between the receiver device and the medical device.
19. The system of claim 16 or 17, wherein the program instructions, when executed by a processor, further cause the processor to: A control input is sent to a medical device associated with the matching identifier, the control input being used to control a function of the medical device.
20. The system of claim 16 or 17, wherein: The optical communication channel is an infrared (IR) communication channel, and the wireless communication channel is a radio frequency (RF) communication channel.
21. The system of claim 16 or 17, wherein: When the program instructions are executed by the processor, the processor further causes the processor to: At least one of the first communication channel and the second communication channel is determined to be associated with a signal below a predetermined threshold strength and is disassociated from the medical device associated with the matching identifier.
22. The system of claim 16 or 17, wherein: When the program instructions are executed by the processor, the processor further causes the processor to: The control device is automatically disassociated from the medical device based on the first identifier no longer being detected via the first communication channel or the second identifier no longer being detected via the first communication channel.
23. The system of claim 16 or 17, wherein: The control device further includes a visual indicator, and wherein the program instructions, when executed by the processor, further cause the processor to update the visual indicator to reflect that the medical device is not within the line of sight of the receiver device.
24. A method for automatically pairing a medical device with a control device via a receiver device, the method comprising: receiving, via a first communication channel, a first identifier associated with a medical device; receiving a second identifier associated with the medical device via a second communication channel different from the first communication channel; determining that the first identifier received via the first communication channel matches the second identifier received via the second communication channel; automatically pairing the control device with the medical device associated with a matching identifier via the first communication channel; and Upon determining that at least one of the first communication channel and the second communication channel is associated with a signal below a predetermined threshold strength, the medical device is disassociated.
25. The method according to claim 24, wherein: The first communication channel and the second communication channel are wireless communication channels; and The third communication channel is a wireless communication channel or an optical communication channel; or The receiver device includes a camera to visually detect a visual identifier located in a line of sight between the receiver device and the medical device.
26. The method of claim 24 or 25, further comprising: receiving status data from the medical device via the first communication channel associated with the matching identifier, wherein a control input is used to control a function of the medical device; and The control input is sent to the medical device via the first communication channel associated with the matching identifier, wherein the control input is used to control a function of the medical device, wherein the optical communication channel is an infrared (IR) communication channel and the wireless communication channel is a radio frequency (RF) communication channel.
27. A method for automatically pairing a control device with a medical device through a control device, comprising: receiving, at the control device, from the medical device via the first communication channel, a first identifier associated with the medical device; receiving, at a receiver device, a second identifier associated with the medical device from the medical device via a third communication channel different from the first communication channel; transmitting a second identifier associated with the medical device from the receiver device to the control device via a second communication channel different from the first communication channel and the third communication channel; determining, at the control device, that a first identifier received via the first communication channel matches a second identifier received via the second communication channel; and The control device is automatically paired with the medical device associated with the matching identifier via the first communication channel.
28. The method of claim 27, wherein: The first communication channel and the second communication channel are wireless communication channels.
29. The method of claim 27 or 28, wherein: The third communication channel is a wireless communication channel or an optical communication channel, or the receiver device includes a camera to visually detect a visual identifier located in a line of sight between the receiver device and the medical device.
30. The method of claim 27 or 28, further comprising: receiving status data from the medical device via a first communication channel associated with the matching identifier; and A control input is sent from the control device to the medical device via a first communication channel associated with the matching identifier, the control input being used to control a function of the medical device.
31. The method of claim 27 or 28, wherein: The optical communication channel is an infrared (IR) communication channel, and the wireless communication channel is a radio frequency (RF) communication channel.
32. The method of claim 27 or 28, further comprising: At least one of the first communication channel and the second communication channel is determined to be associated with a signal below a predetermined threshold strength, and the control device is disassociated from the medical device associated with the matching identifier.
33. The method of claim 27 or 28, further comprising: Automatically disassociating from the medical device based on the first identifier no longer being detected via the first communication channel or the second identifier no longer being detected via the first communication channel.
34. A method for automatically pairing a control device with a medical device through a control device, comprising: sending a first identifier associated with the medical device from the medical device to the control device via the first communication channel; receiving, at the control device, from the medical device via the first communication channel, a first identifier associated with the medical device; transmitting a second identifier associated with the medical device from the medical device to the receiver device via a third communication channel different from the first communication channel; receiving, at the receiver device via the third communication channel, from the medical device a second identifier associated with the medical device; transmitting a second identifier associated with the medical device from the receiver device to the control device via a second communication channel different from the first communication channel and the third communication channel; determining, at the control device, that a first identifier received via the first communication channel matches a second identifier received via the second communication channel; and The control device is automatically paired with the medical device associated with the matching identifier via the first communication channel.
35. The method of claim 34, further comprising: A control input is sent from the control device to the medical device associated with the matching identifier, the control input being used to control a function of the medical device.
36. The method of claim 34 or 35, wherein: The optical communication channel is an infrared (IR) communication channel, and the wireless communication channel is a radio frequency (RF) communication channel.
37. The method of claim 34 or 35, further comprising: The control device is automatically disassociated from the medical device based on the first identifier no longer being detected via the first communication channel or the second identifier no longer being detected via the first communication channel.
38. The method of claim 34 or 35, wherein: The control device further comprises a visual indicator, and the method further comprises: Updated visual indicators to reflect that the medical device is not within the receiver device's line of sight.
