Communication System for a Patient Support Device

Abstract

The patient support device includes a plurality of ultra-wideband wireless transceivers, a display, a controller, and a near-field transceiver. The controller is adapted to determine the position of an object relative to the patient support device using wireless radio frequency (RF) communication between the plurality of ultra-wideband wireless transceivers and the object, to determine whether the object is located inside or outside a spatial volume, to automatically associate the object with the patient support device when the object is located inside the communication range of the near-field transceiver, to automatically dissociate the object from the patient support device when the object is located outside the spatial volume, to transfer and / or display data from the object when the object is associated, and not to transfer and / or display data when the object is not associated. This object is a nurse call device, a departure detection sensor, a second patient support device, etc.

Description

Technical Field

[0001] The present disclosure relates to patient support devices such as beds, cots, stretchers, recliners, etc. More specifically, the present disclosure relates to a patient support device that communicates with one or more devices that are separate from the patient support device itself.

Summary of the Invention

[0002] According to various aspects described herein, the present disclosure is directed to a patient support device system that assists in tracking the location of assets within a healthcare facility. The patient support device system assists a patient in communicating with a nurse while the patient is moving around, assists in alerting a caregiver when the patient has left the patient support device, and assists in reducing the caregiver's workload to aid in the patient's recovery. The system automatically associates assets within the healthcare facility with a particular patient support device, patient, and / or room, and enables the patient to call a nurse when the patient is outside of their bed, for example, in a recliner or other secondary patient support device. In some embodiments, the system includes a mobile nurse call device that can be attached to the patient support device, whereby the patient support device is provided with nurse call communication capabilities. In some embodiments, the system includes a mobile departure detection pad that can be disposed on the patient support device, whereby the patient support device is provided with departure detection capabilities. The departure detection capabilities include the ability to transmit departure detection alerts remotely through an existing nurse call system. These or other aspects of the present disclosure will become apparent to those skilled in the art in light of the detailed description and the accompanying drawings described below.

[0003] According to a first aspect of the present disclosure, there is provided a patient support device comprising a support surface adapted to support a patient, a first transceiver coupled to a first position of the patient support device, a second transceiver coupled to a second position of the patient support device, a third transceiver coupled to a third position of the patient support device, and a controller adapted to determine a position of the departure detection sensor relative to the patient support device using radio frequency (RF) communication between the first transceiver, the second transceiver, and the third transceiver and the departure detection sensor. The controller is adapted to determine whether the departure detection sensor is disposed inside or outside a spatial volume so as to receive a departure detection alert signal from the departure detection sensor. When the departure detection sensor is disposed inside the spatial volume, the controller is further adapted to transmit a departure detection alert to an off-board recipient in response to receiving the departure detection alert signal from the departure detection sensor.

[0004] According to another aspect of the present disclosure, there is provided a patient support device comprising: a support surface adapted to support a patient; a display; a first transceiver coupled to a first position of the patient support device; a second transceiver coupled to a second position of the patient support device; a third transceiver coupled to a third position of the patient support device; and a controller adapted to determine a position of the second patient support device relative to the patient support device using radio frequency (RF) communication between the first transceiver, the second transceiver, and the third transceiver and the second patient support device. The controller is adapted to receive data from the second patient support device to determine whether the second patient support device is disposed inside or outside a spatial volume. The controller is further adapted to perform at least one of transferring the data to an off-board recipient or displaying the data on the display when the second patient support device is disposed inside the spatial volume.

[0005] According to another aspect of the present disclosure, there is provided a patient support device comprising a support surface adapted to support a patient, a first transceiver coupled to a first position of the patient support device, a second transceiver coupled to a second position of the patient support device, a third transceiver coupled to a third position of the patient support device, and a controller. The controller is adapted to determine a first position of the object relative to the patient support device using radio frequency (RF) communication between the first transceiver, the second transceiver, and the third transceiver and the object. The controller is further adapted to determine a second position of the patient support device relative to a fixed locator using RF communication between the first transceiver, the second transceiver, and the third transceiver and the fixed locator to determine whether the object is located inside or outside a first volume of space, whether both the patient support device and the fixed locator are located inside or outside a second volume of space, and, if both the object is located inside the first volume of space and the fixed locator and the patient support device are located inside the second volume of space, to transfer position information indicating the position of the object within a medical facility to a server.

[0006] According to yet another aspect of the present disclosure, there is provided a patient support device comprising a support surface adapted to support a patient, a display, a plurality of ultra-wideband wireless transceivers, a near-field transceiver, and a controller. The controller is adapted to automatically associate an object with the patient support device when the object is disposed within the communication range of the near-field transceiver. The controller is configured to determine the position of the object relative to the patient support device using wireless radio frequency (RF) communication between the plurality of ultra-wideband wireless transceivers and the object, to determine whether the object is disposed inside or outside a spatial volume, to automatically dissociate the object from the patient support device when the object is disposed outside the spatial volume, not to transfer data received from the object to an off-board recipient when the object is dissociated from the patient support device, and when the object is associated with the patient support device, to further be adapted to perform at least one of (a) transferring data received from the object to an off-board recipient or (b) displaying data received from the object on the display.

[0007] According to yet another aspect of the present disclosure, the patient support device may further comprise a nurse call system interface adapted to communicate with a nurse call system consent integrated into a wall of a medical facility. The nurse call system consent comprises a plurality of electrical pins, and the controller is adapted to transmit the departure detection alert to the off-board recipient by changing an electrical state of a pin of the nurse call system consent.

[0008] In some aspects, the nurse call system interface is adapted to communicate with the nurse call system consent by wireless communication or wired communication.

[0009] In some embodiments, the controller is further adapted to determine whether the second patient support device is disposed inside or outside a second volume of space using wireless radio frequency (RF) communication between the first transceiver, the second transceiver, and the third transceiver and the second patient support device.

[0010] In some embodiments, the egress detection sensor includes a pressure sensing pad adapted to be disposed under the patient. The pressure sensing pad can be adapted to be removable from the patient support device and to be disposed on a support surface of a second patient support device.

[0011] In some embodiments, the first transceiver, the second transceiver, and the third transceiver are all ultra-wideband wireless transceivers. Additionally or alternatively, more or fewer ultra-high-band wireless transceivers can be included in the patient support device.

[0012] In some embodiments, the patient support device further includes a memory in which the first position, the second position, and the third position of the first transceiver, the second transceiver, and the third transceiver are stored.

[0013] In some embodiments, the controller is further adapted to determine whether the egress detection sensor is disposed inside or outside the volume of space using the stored positions of the first transceiver, the second transceiver, and the third transceiver.

[0014] In some embodiments, the controller is further adapted not to transmit the egress detection alert to the off-board recipient in response to receiving the egress detection alert signal from the egress detection sensor when the egress detection sensor is disposed outside the volume of space.

[0015] In some aspects, the controller is further adapted to determine the position of the patient support device relative to the fixed locator using RF communication between the first transceiver, the second transceiver, and the third transceiver and the fixed locator.

[0016] In some aspects, the controller is further adapted to receive an identifier from the fixed locator to determine whether the patient support device is disposed within a threshold distance of the fixed locator, and, if the patient support device is disposed within the threshold distance, to transfer the identifier of the fixed locator to a server.

[0017] In some aspects, the off-board recipient includes the fixed locator if the patient support device is disposed within the threshold distance.

[0018] In some aspects, the patient support device further includes a microphone adapted to convert the patient's voice into an audio signal, and the controller is adapted to transmit the audio signal to the fixed locator if the fixed locator is disposed within the threshold distance, and not to transmit the audio signal to the fixed locator if the fixed locator is disposed outside the threshold distance.

[0019] In some aspects, the off-board recipient is a nurse call system consent integrated into a wall of a medical facility.

[0020] In some aspects, the controller is further adapted to transfer location information indicating the location of the object within the medical facility to a server by using radio frequency (RF) communication between the first transceiver, the second transceiver, and the third transceiver and the object to determine a second position of the object relative to the patient support device, by using RF communication between the first transceiver, the second transceiver, and the third transceiver and a fixed locator to determine a third position of the patient support device relative to the fixed locator, by determining whether both the patient support device and the fixed locator are disposed inside or outside a third volume of space, and when the object is disposed inside the second volume of space and the fixed locator and the patient support device are disposed inside the third volume of space.

[0021] In some aspects, the controller is further adapted to use the position of the retraction detection sensor and the second position of the object to determine whether the retraction detection sensor is coupled to the object.

[0022] In some aspects, the location information indicates that the object and the patient support device are disposed within a common room of the medical facility.

[0023] In some aspects, the controller may be further adapted to determine the position of the nurse call device relative to the patient support device using wireless radio frequency (RF) communication between the first transceiver, the second transceiver, and the third transceiver, and a tag coupled to the nurse call device. The controller is adapted to receive a nurse call signal from the nurse call device to determine whether the nurse call device is disposed inside or outside the spatial volume, and, if the nurse call device is disposed inside the spatial volume, to transmit the nurse call signal to the nurse call system in response to receiving the nurse call signal from the nurse call device.

[0024] The patient support device may further comprise a nurse call system interface adapted to communicate with a nurse call system consent integrated into a wall of a medical facility, the nurse call system consent comprising a plurality of electrical pins, and the controller is adapted to transmit the nurse call signal to the nurse call system by changing an electrical state of a pin of the nurse call system consent.

[0025] In some aspects, the patient support device further comprises a first near-field transceiver adapted to read data from a second near-field transceiver coupled to the tag.

[0026] In some aspects, the controller is further adapted to automatically associate the tag with the patient support device when the tag is disposed close enough to the patient support device such that the first near-field transceiver and the second near-field transceiver can communicate with each other.

[0027] In some embodiments, the controller is further adapted to automatically disassociate the tag from the patient support device when the tag is moved outside the spatial volume.

[0028] In some embodiments, the controller is further adapted to not transmit the nurse call signal to the nurse call system in response to receiving the nurse call signal from the nurse call device when the tag is disassociated from the patient support device.

[0029] In some embodiments, the controller is adapted to display a first message on the display when the controller associates the tag with the patient support device, and to display a second message on the display when the controller disassociates the tag from the patient support device.

[0030] In some embodiments, the patient support device further comprises a fourth transceiver adapted to communicate with a fifth transceiver coupled to the tag, and the controller is further adapted to (a) transfer an audio signal received from the tag to the nurse call system consent via the fourth transceiver when the tag is associated with the patient support device, and (b) not transfer an audio signal from the tag to the nurse call system consent when the tag is disassociated from the patient support device.

[0031] In some embodiments, the patient support device further comprises a plurality of side rails and a footboard, and the first proximity field transceiver is integrated into one of the side rails or the footboard.

[0032] In some aspects, the controller is further adapted to receive an ID from the second patient support device, to determine and verify whether the ID conforms to a specification, to transfer the data to the off-board recipient if the ID conforms to the specification and the second patient support device is disposed inside the spatial volume, and not to transfer the data to the off-board recipient if the ID does not conform to the specification.

[0033] In some aspects, the off-board recipient includes the fixed locator if the patient support device is disposed inside the threshold distance.

[0034] In some aspects, the data comprises a departure detection alert signal.

[0035] In some aspects, the patient support device is a bed and the second patient support device is a recliner.

[0036] In some aspects, the data comprises at least one of the brake state of the second patient support device, the locked state of the lock of the second patient support device, the angle of a component of the second patient support device, an error message, or an occupancy detection signal.

[0037] In some aspects, the second patient support device comprises a departure detection sensor including a pressure sensing pad adapted to be disposed under the patient.

[0038] In some aspects, the pressure sensing pad is adapted to be removable from the second patient support device and to be disposed on the support surface of another patient support device.

[0039] In some aspects, the patient support device further comprises a network transceiver adapted to communicate with a computer network of a medical facility in which the patient support device is disposed. The off-board recipient can be a server communicating with the computer network.

[0040] In some aspects, the first transceiver, the second transceiver, and the third transceiver are ultra-wideband wireless transceivers and are adapted to communicate with a fourth ultra-wideband wireless transceiver coupled to the second patient support device.

[0041] In some aspects, the fourth ultra-wideband wireless transceiver is incorporated into a removable tag coupled to the second patient support device.

[0042] In some aspects, the controller is further adapted to transfer the data to the off-board recipient and to display the data on the display when the second patient support device is disposed inside the spatial volume.

[0043] In some aspects, the controller is further adapted not to transfer the location information to the server if either or both of (a) the second patient support device or object is disposed outside the spatial volume, or (b) both the fixed locator and the patient support device are not disposed inside the second spatial volume are satisfied.

[0044] In some aspects, the location information includes a first ID received from the object and a second ID received from the fixed locator. The second ID corresponds to a specific location of the fixed locator within the medical facility.

[0045] In some aspects, both the first spatial volume and the second spatial volume are defined in a fixed relationship with respect to the patient support device.

[0046] In some embodiments, the first spatial volume is defined in a fixed relationship with respect to the patient support device, and the second spatial volume is defined in a fixed relationship with respect to the fixed locator.

[0047] In some embodiments, the object is a mobile object adapted to assist in the treatment of the patient.

[0048] In some embodiments, the object is a recliner.

[0049] In some embodiments, the controller is further adapted to receive data from the object.

[0050] In some embodiments, the data includes a departure detection alert signal and / or a nurse call signal.

[0051] In some embodiments, the object is a second patient support device, and the data includes a departure detection alert signal.

[0052] In some embodiments, the object is a nurse call device, and the data includes a nurse call signal.

[0053] In some embodiments, the patient support device further comprises a Bluetooth® transceiver, and the controller is further adapted to: (a) when the nurse call device is associated with the patient support device, receive an audio signal from the nurse call device via the Bluetooth® transceiver and transfer the audio signal to the nurse call system console via the nurse call system interface; and (b) when the nurse call device is disassociated from the patient support device, not transfer any audio signal from the nurse call device to the nurse call system console.

[0054] In some embodiments, the object is a device adapted to improve the patient's mobility level.

[0055] In some embodiments, the object is a mobile tag adapted to be attached to a second patient support device.

[0056] In some embodiments, the tag comprises an adhesive adapted such that the tag can be releasably attached to the second patient support device.

[0057] In some embodiments, the tag comprises a button adapted to be depressed by the patient, and the tag is adapted to transmit a nurse call signal to the patient support device in response to the button being depressed.

[0058] In some embodiments, the object comprises a departure detection sensor.

[0059] In some embodiments, the departure detection sensor is a pressure sensing pad adapted to be disposed under the patient.

[0060] In some aspects, the controller is further adapted to determine a second position of the fixed locator of the patient support device using RF communication between the plurality of ultra-wideband wireless transceivers and the fixed locator, to associate the fixed locator with the patient support device if both the patient support device and the fixed locator are disposed inside a second volume of space, and to disassociate the fixed locator from the patient support device if it is not the case that both the patient support device and the fixed locator are disposed inside the second volume of space.

[0061] In some aspects, the controller is further adapted to (a) transfer position information indicating the position of the object within the healthcare facility to the server if the object is associated with the patient support device, and (b) not transfer the position information to the server if the object is disassociated from the patient support device.

[0062] Before various aspects of the present disclosure are described in detail, it should be understood that the claims are not to be limited to the details of operation, or the details of the construction and arrangement of components, described in the following detailed description or shown in the drawings. The aspects described herein can be practiced or carried out in alternative ways not explicitly disclosed herein. Also, it should be understood that the terms and phrases used herein are for the purpose of description and should not be regarded as limiting. The use of "including" and "comprising," or variations thereof, is meant to encompass the items listed thereafter and their equivalents, as well as additional items and their equivalents. Further, in the description of various embodiments, enumeration may be used. Unless explicitly stated otherwise, the use of enumeration should not be construed as limiting the claims to a particular order or number of components. The use of enumeration should not be construed as excluding any additional steps or components that can be combined with or incorporated into the enumerated steps or components from the scope of the claims.

Brief Description of the Drawings

[0063]

Figure 1

[0064]

Figure 2

[0065]

Figure 3

[0066]

Figure 4

[0067]

Figure 5

[0068]

Figure 6

[0069]

Figure 7

[0070]

Figure 8

[0071]

Figure 9

[0072]

Figure 10

[0073]

Figure 11

DETAILED DESCRIPTION OF THE INVENTION

[0074] An exemplary patient support device 20 according to one embodiment of the present disclosure is shown in FIG. 1. Although the particular form of the patient support device 20 illustrated in FIG. 1 is a bed adapted for use in a hospital or other medical environment, it will be understood that the patient support device 20 can be a cot, stretcher, recliner, or any other structure capable of supporting a patient in a medical environment in different embodiments.

[0075] Generally, the patient support device 20 includes a base 22 having a plurality of wheels 24, a pair of lift devices 26 supported on the base 22, a litter frame 28 supported on the lift devices 26, and a support deck 30 supported on the litter frame 28. The patient support device 20 further includes a headboard 32, a footboard 34, and a plurality of side rails 36. The side rails 36 are shown in FIG. 1 as all being in the raised position, but each is individually movable to the lowered position. Here, in the lowered position, access to the patient support device 20 is not impeded by the lowered side rails 36.

[0076] The lift devices 26 are adapted to lift and lower the litter frame 28 relative to the base 22. The lift devices 26 can be hydraulic actuators, electric actuators, or any other suitable device for lifting and lowering the litter frame 28 relative to the base 22. In the illustrated embodiment, the lift devices 26 are independently operable such that the inclination of the litter frame 28 relative to the base 22 can be adapted to position the litter frame 28 in a flat or horizontal orientation, Trendelenburg orientation, or reverse Trendelenburg orientation. That is, the litter frame 28 includes a head end 38 and a foot end 40, the heights of which can be independently adjusted by the nearest lift device 26 respectively. The patient support device 20 is designed such that when an occupant lies thereon, his or her head is positioned adjacent to the head end 38 and his or her feet are positioned adjacent to the foot end 40.

[0077] The return frame 28 provides a structure for supporting the support deck 30, the headboard 32, the footboard 34, and the side rails 36. The support deck 30 provides a support surface for a mattress 42 or other soft cushion such that a human can lie and / or sit thereon. In some embodiments, the mattress 42 includes one or more inflatable bladders that are controllable via a blower or other compressed air source. In at least one embodiment, inflation of the mattress 42 bladders is controllable via electronics mounted on the patient support device 20. In such one embodiment, the mattress 42 can comprise any of the functions and / or structures of any of the mattresses disclosed in U.S. Patent No. 9,468,307 of the same applicant, issued October 18, 2016, by inventors Patrick Lafleche et al. The entire foregoing disclosure is incorporated herein by reference. Other types of mattresses may also be used.

[0078] The support deck 30 is made up of a plurality of sections, some of which are pivotable about a generally horizontal pivot axis. In the embodiment shown in FIG. 1, the support deck 30 includes at least a head section 44, a leg section 46, and a foot section 48. All of them are disposed under the mattress 42 and form a generally flat surface that supports the mattress 42. The head section 44 is sometimes also referred to as a Fowler section and is pivotable between a generally horizontal orientation (not shown in FIG. 1) and a plurality of lifted positions (one of which is shown in FIG. 1) about a generally horizontal pivot axis. The leg section 46 and the foot section 48 may also be pivotable about a generally horizontal pivot axis.

[0079] In some embodiments, the patient support device 20 can include one or more components adapted to be modified from the illustrated state so that a user can expand the width of the patient support deck 30, thereby enabling the patient support device 20 to accommodate patients of various body builds. When so modified, the width of the deck 30 can be adjusted horizontally in any increment, for example, between a first width or minimum width, a second width or intermediate width, and a third width or expanded / maximum width.

[0080] As used herein, the term "longitudinal direction" refers to a direction parallel to the axis between the head end 38 and the foot end 40. The terms "transverse direction" or "lateral direction" refer to a direction perpendicular to the longitudinal direction and parallel to the plane on which the patient support device 20 is seated.

[0081] One of ordinary skill in the art will understand that, although the patient support device 20 may be designed with other types of mechanical configurations different from those shown in the accompanying drawings, for example, it may be designed with the configuration described in U.S. Patent No. 10,130,536 of the same applicant, entitled "Patient Support Usable With Bariatric Patients" and invented by Roussy et al. The entire above disclosure is incorporated herein by reference. In other embodiments, the mechanical configuration of the patient support device 20 may include the same or substantially the same structure as the Model 3002 S3 bed manufactured and sold by Stryker Corporation, located in Kalamazoo, Michigan. This configuration is described in more detail in the "Stryker Maintenance Manual for the MedSurg Bed 3002 S3" published in 2010 by Stryker Corporation, located in Kalamazoo, Michigan, and the entire disclosure thereof is incorporated herein by reference. In yet other embodiments, the mechanical configuration of the patient support device 20 may have the same or substantially the same structure as the Model 3009 Procuity MedSurg bed manufactured and sold by Stryker Corporation, located in Kalamazoo, Michigan. This configuration is described in more detail in the "Stryker Maintenance Manual for the 3009 Procuity MedSurg bed (3009-009-002 Rev.A.0)" published in 2020 by Stryker Corporation, located in Kalamazoo, Michigan.

[0082] Those skilled in the art will understand that, although not limited thereto, the patient support device 20 may be designed with other types of mechanical configurations, for example, the mechanical configuration described in U.S. Patent No. 7,690,059 of the same applicant, issued on April 6, 2010, entitled "Hospital Bed" by Lemire et al., and / or the mechanical configuration described in U.S. Patent Application No. 2007 / 0163045 of the same applicant, entitled "Patient handling Device Including Local Status Indication, One-Touch Fowler Angle Adjustment, and Power-On Alarm Configuration" filed by Becker et al. The entire disclosure of both is also incorporated herein by reference. The overall mechanical configuration of the patient support device 20 may take other forms that are even different from those disclosed in the above-referenced documents when the patient support device includes one or more of the functions, features, and / or structures discussed in more detail below.

[0083] The patient support device 20 further includes a plurality of control panels 54 such that a user of the patient support device 20, for example, a patient and / or a related caregiver, can control one or more features of the patient support device 20. In the embodiment shown in FIG. 1, the patient support device 20 includes a footboard control panel 54a, a pair of outer side rail control panels 54b (only one can be seen), and a pair of inner side rail control panels 54c (only one can be seen). The footboard control panel 54a and the outer side rail control panels 54b are intended to be used by a caregiver or other authorized person, while the inner side rail control panels 54c are intended to be used by a patient associated with the patient support device 20. Each control panel 54 includes a plurality of control units 50 (e.g., FIGS. 2-3), but each control panel 54 does not necessarily have the same control units and / or functions.

[0084] Among other functions, the control unit 50 of the control panel 54a enables the user to control one or more of the following, namely, changing the height of the support deck 30, raising or lowering the head section 44, activating and deactivating the brakes of the wheels 24, operating and deactivating the departure detection system 136 (FIG. 5), changing various settings of the patient support device 20, viewing the current position of the patient support device 20 as determined by the position detection system discussed herein, viewing one or more devices associated with the patient support device 20, such as, but not limited to, a nurse call device, a departure detection sensor, a secondary patient support device, a medical device, etc., and also enables other actions. One or both of the inner side rail control panels 53c also include at least one control unit that enables a nurse (or other caregiver) who is in a remote location to call the patient. In addition to this nurse call control unit, one or both of the inner side rail control panels 53c also include one or more control units for controlling one or more features of one or more room devices located in the same room as the patient support device 20. As will be described in more detail below, such room devices include, but are not necessarily limited to, a television, a reading lamp, and a room light. With respect to the television, features that may be controllable by one or more control units 50 on the control panel 54c include, but are not limited to, volume, channel, closed captioning, and / or the power state of the television. With respect to the room light and / or the night light, features that may be controllable by one or more control units 50 on the control panel 54c include the on / off state and / or the brightness level of these lights.

[0085] The control panel 54a includes a display 52 (Figure 2) configured to display a plurality of different screens. A plurality of navigation control units 50a - f surround the display 52, and when activated, cause the display 52 to display different screens thereon. More specifically, when the user presses the navigation control unit 50a, the control panel 54a displays a departure detection control screen on the display 52. This departure detection control screen includes one or more icons that, when touched, control the on-board departure detection system 136 (Figure 5). The departure detection system 136 is adapted to issue an alert when a patient leaves the patient support device 20. The departure detection system 136 may have any of the same features and functions as, and / or be configured in any of the same ways as, the departure detection system disclosed in U.S. Patent Application No. 62 / 889254, filed on August 20, 2019, by the same applicant and entitled "Person Support Apparatus with Adjustable Exit Detection Zones" by inventors Sujay Sukumaran et al. The entire foregoing disclosure is incorporated herein by reference. Other types of departure detection systems may be included within the patient support device 20.

[0086] When the user presses the navigation control unit 50b (Fig. 2), the control panel 54 displays a monitoring control screen. This monitoring control screen includes a plurality of control icons that control the on-board monitoring system installed in the patient support device 20 when touched. The on-board monitoring system alerts the caregiver, through the integrated display, with, for example, a single light or multiple lights controlled in an integrated manner, when one or more of the plurality of settings of the patient support device 20 are in an undesirable state, and provides a display using the same integrated display when all of the plurality of settings are in their respective desired states. Further details of one type of monitoring system that can be installed in the patient support device 20 are disclosed in U.S. Patent Application No. 62 / 864638, filed on June 21, 2019, by the same applicant and titled "Patient Support Apparatus with Caregiver Reminders" by inventors Kurosh Nahavandi et al., and in U.S. Patent Application No. 16 / 721133, filed on December 19, 2019, by the same applicant and titled "Patient Support Apparatuses with Motion Customization" by inventors Kurosh Nahavandi et al. The entire disclosures of both are incorporated herein by reference. Other types of monitoring systems may be provided within the patient support device 20.

[0087] When the user presses the navigation control unit 50c, the control panel 54a displays a scale control screen. This scale control screen includes a plurality of control icons that control the scale system 138 (FIG. 5) of the patient support device 20 when touched. Such a scale system may have any of the features and functions and / or be configured in any of the ways disclosed in U.S. Patent Application No. 62 / 889,254, filed Aug. 20, 2019, by the inventors Sujay Sukumaran et al., titled "Person Support Apparatus with Adjustable Exit Detection Zones", and in U.S. Patent Application Publication No. 62 / 885,954, filed Aug. 13, 2019, by the inventors Kurosh Nahavandi et al., titled "Patient Support Apparatus with Equipment Weight Log", both of the same applicant. The entire disclosure of both is incorporated herein by reference. This scale system can utilize the same force sensors and / or other components as those utilized by the departure detection system 136, but one or more different sensors and / or other components may be utilized. Other scale systems other than those described in the above '254 application and '954 application may alternatively be provided within the patient support device 20.

[0088] When the user presses the navigation control unit 50d, the control panel 54 displays a motion control screen. This motion control screen, when touched, controls the movement of various components of the patient support device 20. For example, without being limited, it includes a plurality of control icons that control movements such as the height of the retractable frame 28 and the pivotal movement of the head section 44. In some embodiments, the motion control screen displayed on the display 52 in response to pressing the control unit 50d may be the same as or similar to the position control screen 216 disclosed in U.S. Patent Application No. 62 / 885953, filed on August 13, 2019, by the same applicant and entitled "Patient Support Apparatus with Touchscreen" by inventors Kurosh Nahavandi et al. The entire above disclosure is incorporated herein by reference. Other types of motion control screens may be provided within the patient support device 20.

[0089] When the user presses the navigation control unit 50e, the control panel 54a displays a motion lock control screen. This motion lock control screen includes a plurality of icons that control one or more motion lockout functions of the patient support device 20 when touched. Such motion lockout functions typically include the ability for a caregiver to use the control panel 54a to lock out one or more of the motion control units 50 of the patient control panel 53c, preventing the patient from controlling the movement of one or more components of the patient support device 20 using the control units 50 on the control panel 54c. The motion lockout screen may comprise any features, functions of the motion lockout features, functions, and configurations disclosed in U.S. Patent Application No. 16 / 721,133, filed December 19, 2019, by the same applicant and entitled "Patient Support Apparatus with Motion Customization" by inventors Kurosh Nahavandi et al., and / or may be configured in the same manner. The entire foregoing disclosure is incorporated herein by reference. Other types of motion lockout sections may be provided within the patient support device 20.

[0090] When the user presses the navigation control unit 50f, the control panel 54a displays a menu screen. This menu screen includes a plurality of menu icons that list one or more additional screens for controlling and / or viewing one or more other features of the patient support device 20 when touched. Such other features include, but are not limited to, information about one or more devices currently associated with the patient support device 20, diagnostic information and / or service information for the patient support device 20, mattress control information and / or status information, configuration settings, position information, and other settings and / or information. An example of a suitable menu screen is menu screen 100 disclosed in U.S. Patent Application No. 62 / 885953, filed on August 13, 2019, by the same applicant and titled "Patient Support Apparatus with Touchscreen" by inventors Kurosh Nahavandi et al. The entire foregoing disclosure is incorporated herein by reference. Other types of menus and / or settings may be included within the patient support device 20. In at least one embodiment, utilization of the navigation control unit 50f enables the user to navigate to a screen that shows which devices are currently located inside a predefined spatial volume in which the device houses the patient support device 20, if the device is currently located inside such a predefined spatial volume. As discussed in more detail below, the patient support device 20 includes an on-board locating system that is adapted to automatically determine the relative position of one or more devices with respect to the patient support device 20, and in some examples is further adapted to automatically associate those devices with the patient support device 20 (and / or the patient assigned to the patient support device 20) according to the proximity of the medical devices to the patient support device 20. Further details of this locating system are provided below.

[0091] For all of the navigation control units 50a to 50f (Fig. 2), in response to the user pressing these control units, screens other than those specifically described above may be displayed on the display 52 in other embodiments of the patient support device 20. Thus, it will be understood that the specific screens described above merely indicate the types of screens that can be displayed on the display 52 in response to the user pressing one or more of the navigation control units 50a to 50f. Also, although the navigation control units 50a to 50f are shown in the accompanying drawings as dedicated control units all arranged in proximity to the display 52, it will also be understood that, alternatively, one or more of these control units 50a to 50f can be touch screen control units arranged at one or more positions on the display 52. Further, although the control units 50a to 50f are shown as buttons in this specification, it will also be understood that, alternatively or additionally, any one of the control units 50a to 50f can be a switch, dial, or other non-button type of control unit. Additionally, the patient support device 20 can be modified to include additional navigation control units, a smaller number of navigation control units, and / or different navigation control units than the navigation control units 50a to 50f shown in Fig. 2.

[0092] FIG. 3 is an example of a patient control panel 54c that is incorporated in the patient support device 20 and can be disposed at a position on the patient support device 20 that is convenient for a patient to access while being supported on the support deck, for example, on the inner side of one of the side rails 36. The control panel 54c includes a plurality of controls 50g - t that are intended to be operated by a patient. The nurse call control 50g, when depressed by a patient, transmits a signal to the nurse call system, requesting a nurse who is in a remote location to talk to the patient. The Fowler up control 50h, when depressed by a patient, causes an on - board electric actuator in the patient support device 20 to lift the Fowler section 44 upward. The Fowler down control 50i, when depressed by a patient, causes the electric actuator to lower the Fowler section downward. The gatch up control 50j, when depressed by a patient, causes another electric actuator to lift the knee section of the support deck 30, while the gatch down control 50k causes the electric actuator to lower the knee section of the support deck 30. The knee section can refer to a joint portion that couples the leg section 46 to the foot section 48.

[0093] The volume up control 50l, when depressed by a patient, causes the patient support device 20 to transmit a signal to the in - room television instructing the television to increase its volume, while the volume down control 50m, when depressed, causes the patient support device 20 to transmit a signal to the television instructing the television to decrease its volume. The channel up control 50n, when depressed by a patient, causes the patient support device 20 to transmit a signal to the television instructing the television to increase the channel number, while the channel down control 50o, when depressed, causes the patient support device 20 to transmit a signal to the television instructing the television to decrease the channel number.

[0094] When pressed, the mute control unit 50p causes the patient support device 20 to send a signal to the television instructing it to mute or unmute itself, depending on whether the television is currently muted or not. In other words, the mute control unit 50p is a toggle control unit that alternately sends mute or unmute commands to the television when pressed.

[0095] The power control unit 50q is a toggle control unit that, when pressed, sends a signal to the television causing it to turn the power on or off depending on the current power state of the television. The closed caption control unit 50r is another toggle control unit that, when pressed, sends a signal to the television causing it to turn the closed caption feature on or off depending on whether the closed caption feature is currently on or off.

[0096] The control unit 50s is a toggle control unit that, when pressed, sends a signal to the first light causing it to turn on or off depending on the current state of the first light. The control unit 50t is another toggle control unit that, when pressed, sends a signal to the second light causing it to turn on or off depending on the current state of the second light. In some embodiments, the first light is a reading light and the second light is a room light, both of which are disposed off-board of the patient support device 20.

[0097] It will be appreciated that not only the number of control units 50 on the control panel 54c, but also the functions of the control units 50 on the control panel 54c, the layout of the control units 50 on the control panel 54c, and / or other aspects of the control panel 54c can be modified from those shown in FIG. 3. In some embodiments, the control panel 54c is implemented on a pendant controller that includes a cable that plugs into a port of the patient support device 20. In other embodiments, one or more of the control units 50 of the control panel 54c can be omitted, increased, and / or split to other control panels and / or locations. Still other ways of implementing the control panel 54c are also possible.

[0098] FIG. 4 illustrates the patient support device 20 disposed within a room 58 of a medical facility. FIG. 4 also shows additional items that may be present within the medical facility and are configured to communicate with the patient support device 20, which include, but are not limited to, a locator unit 60, a conventional local area network 80 of the medical facility, and one or more other devices used during the treatment of a patient, such as, but not limited to, a secondary patient support device 20a. The locator unit 60 is disposed at a known fixed position within the medical facility where the patient support device 20 is located. The locator unit 60 functions as a fixed locator. That is, the locator unit 60 communicates with the patient support devices 20 and shares information that enables them to determine the location of the patient support devices 20.

[0099] In some embodiments, the patient support device 20 is configured to be able to communicate with at least two different types of locator units 60, i.e., to be able to communicate with a coupled locator unit and an uncoupled locator unit. An example of the coupled locator unit 60 is shown in FIG. 4. An example of an uncoupled locator unit (uncoupled locator unit 60b) is shown in FIG. 6 of U.S. Patent Application No. 63 / 306279 of the same applicant, filed on February 3, 2022, entitled "Communication System for Patient Support Apparatuses" by inventors Madhu Sandeep Thota et al. The entire above disclosure is incorporated herein by reference. In some embodiments, the patient support device 20 is configured to communicate with the uncoupled locator unit 60b described in the '279 application and to perform any one or more of the functions described in that application that utilize information provided by such an uncoupled locator unit and / or such an uncoupled locator unit.

[0100] The locator unit 60 is communicatively coupled to a conventional communication consent 64 and is adapted to provide location information to the patient support device 20. The locator unit 60 is also adapted to act as a communication conduit for routing wireless communication between the patient support device 20 and one or more devices and / or systems communicatively coupled to the communication consent 64 (e.g., room devices 72, 74, 76 and / or a nurse call system 70; see FIG. 4). Generally, the locator unit 60 is typically located in a hospital room where one or more communication consents 64 are normally present. Unless otherwise stated, references herein to "locator unit 60" may refer to either a coupled locator unit 60 or an uncoupled locator unit 60.

[0101] As shown in FIG. 4, the locator unit 60 is adapted to be mounted on a wall 62, such as on the headwall of a patient room 58 within a medical facility. The headwall of a conventional patient room 58 in a medical facility typically includes a conventional communication outlet 64 physically integrated therewith. The communication outlet 64 is adapted to receive a nurse call cable 66, the other end of which is physically connected to either a patient support device 20 (not shown) or the locator unit 60 (shown in FIG. 4). In many medical facilities, the communication outlet 64 includes a 37-pin connector. However, other types of connectors are also often found in certain medical facilities. As will be discussed in more detail below, the locator unit 60 and the nurse call cable 66 enable the patient support device 20 to communicate with the nurse call system and one or more room devices disposed within the room 58.

[0102] The communication outlet 64 is electrically coupled to one or more cables, wires, or other conductors 68, which electrically couple the communication outlet 64 to a nurse call system 70 and one or more conventional room devices, such as a television 72, a room light 74, and / or a reading light 76. The conductors 68 are typically disposed behind the wall 62 and are not visible. In some medical facilities, the conductors 68 may first be coupled to a room interface circuit board, which may include one or more conductors 68 for coupling the room interface circuit board to the room devices 72, 74, 76 and / or the nurse call system 70. Other communicable arrangements for coupling the communication outlet 64 to the nurse call system 70 and / or one or more room devices 72, 74, 76 are also possible.

[0103] The nurse call cable 66 (FIG. 4) enables the locator unit 60 to communicate with the nurse call system 70 and / or the room devices 72, 74, 76. Further, since the patient support device 20 can wirelessly communicate with the locator unit 60, the patient support device 20 can thereby communicate with the nurse call system 70 and the room devices 72, 74, 76. When a patient supported on the patient support device 20 activates a nurse call control unit (e.g., 50b. See FIG. 3) on the patient support device 20, a signal is wirelessly transmitted from the patient support device 20 to the locator unit 60. Subsequently, this causes the signal to be carried to the nurse call system 70 via the nurse call cable 66, and the nurse call system 70 transfers the signal to one or more nurses (e.g., nurses at one or more nurse stations 78) who are in a remote location. When the patient activates one or more room device control units (e.g., control units 50l - t. See FIG. 3), one or more wireless signals are carried to the locator unit 60, and subsequently, this causes appropriate signals to change one or more characteristics (e.g., volume, channel, on / off state) of these devices to be transmitted to the communication consent 64 and the room devices 72, 74, 76 via the nurse call cable 66.

[0104] As also shown in FIG. 4, the patient support device 20 is further configured to communicate with the local area network 80 of the medical facility. In the embodiment shown in FIG. 4, the patient support device 20 includes a wireless network transceiver 96 (FIG. 5) that wirelessly communicates with the local area network 80. In at least some embodiments, the network transceiver 96 is a WiFi transceiver (e.g., IEEE 802.11) that wirelessly communicates with one or more conventional wireless access points of the local area network 80. In other embodiments, the network transceiver 96 can be a wireless transceiver that wirelessly communicates with the network 80, one or more servers hosted thereon, and / or other devices using conventional 5G technology. In some embodiments, the network transceiver 96 may include either the structure and / or function of the communication module 56 disclosed in U.S. Patent No. 10,500,401 to the same applicant, titled "Network Communication for Patient Support Apparatuses" and issued to Michael Hayes. The entire above disclosure is incorporated herein by reference. Still other types of wireless network transceivers may be utilized.

[0105] In some embodiments, the network transceiver 96 is a wired transceiver adapted to enable the patient support device 20 to communicate with the network 80 via a wired connection, e.g., via an Ethernet cable plugged into an Ethernet port (e.g., an RJ-45 type port, an 8P8C port) mounted on the patient support device 20. In still other embodiments, the patient support device 20 includes both a wired transceiver 96 for communicating with the network 80 via a wired connection and a wireless transceiver 96 for wirelessly communicating with the network 80.

[0106] The patient support device 20 is configured to communicate with one or more servers on the local area network 80 of a medical facility. One such server is the patient support device server 84. The patient support device server 84, in at least one embodiment, is adapted to receive status information from the patient support device 20 disposed within the medical facility and to distribute this status information to caregivers, other servers, and / or other software applications. As will be discussed in more detail below, the server 84 may be configured to receive data from one or more medical devices disposed inside one or more spatial volume portions defined around the patient support device 20 and / or inside a spatial volume portion defined around the locator unit 60. In some embodiments in which data from medical devices is collected, the data from one or more medical devices may be transferred to an EMR server 92 and / or one or more other servers 94 (and / or one or more electronic devices 98) on the network 80, such as a caregiver assistance server and / or a caregiver assistance software application. These will be discussed in more detail below.

[0107] In some embodiments, the patient support device server 84 is configured to communicate at least a portion of the patient support device status data and / or medical device data received from the patient support device 20 to a remote server 86 located at a geographically remote location from the medical facility. Such communication may occur via conventional network appliances 88, such as routers and / or gateways coupled to the Internet 90, although it is not limited thereto. The remote server 86 is, in turn, coupled to the Internet 90, and the patient support device server 84 is provided with other information necessary to communicate with the remote server 86 via a URL and / or the Internet connection between the network 80 and the server 86.

[0108] In some alternative embodiments, the patient support device 20 may be configured to communicate directly with one or more cloud-based servers, such as remote server 86, without utilizing the patient support device server 84. That is, in some embodiments, the patient support device 20 may be configured to communicate directly with a remote server without the involvement of any local host server (e.g., a server hosted on network 80). In such an embodiment, the patient support device 20 utilizes Microsoft Azure cloud computing services to directly connect to one or more remote servers 86 without using server 84. In some such embodiments, network appliance 88 is a router configured to support such a direct connection. Further types of cloud direct connections may be utilized with one or more patient support devices 20. When the patient support device 20 is configured to communicate directly with the remote server 86, the patient support device server 84 may be omitted, or one or more of the functions of the patient support device server 84 described herein may be performed by the remote server 86.

[0109] The patient support device server 84 is also configured to determine the location of each patient support device 20 (and / or devices associated therewith), or to receive the location of each patient support device 20 from the patient support device 20 (and / or devices associated therewith). In some embodiments, the patient support device server 84 determines the bay area of each patient support device 20 and associated devices disposed within the room number and / or room 58, and similarly determines the location of patient support devices 20 and associated devices disposed outside of room 58, such as in a hallway, maintenance area, or some other area where patient support devices 20 and associated devices may be located. Generally, the patient support device server 84 may be configured to determine the location of any patient support device 20 disposed within the communication range of one or more locator units 60 and the location of any associated devices disposed within one or more spatial volumes defined around the patient support device 20. This will be discussed in detail below.

[0110] The patient support device server 84 is adapted to communicate with the EMR server 92 and exchange data therewith. In some embodiments, the server 84 communicates with the EMR server 92 and transmits patient data (e.g., vital sign readings from one or more vital sign sensors, weight readings taken from a scale mounted on the patient support device 20, treatments provided to the patient using the on-board powered mattress 42 of the patient support device 20, data from other devices determined to be associated with the patient assigned to the patient support device 20) to be recorded in the patient's health record. Additionally, in some embodiments, the server 84 communicates with the EMR server 92 to receive data from one or more of the devices used by a particular patient.

[0111] It will be understood that the architecture and content of the local area network 80 may vary from medical facility to medical facility, and that the example shown in FIG. 4 is merely one example of the type of network that a medical facility may adopt. Typically, one or more additional servers 94 may be hosted on the network 80, and one or more of them may be adapted to communicate with the patient support device server 84. The local area network 80 also typically enables one or more electronic devices 98 to access the local area network 80 via the wireless access point 82. Such electronic devices 98 include, but are not limited to, smartphones, tablet computers, portable laptops, desktop computers, smart TVs, and other types of electronic devices that have WiFi capabilities and include appropriate authentication means (e.g., SSID, password) for accessing the network 80 (and, in at least some embodiments, the patient support device server 84). As will be discussed in more detail below, in some embodiments, the patient support device server 84 is configured to share data with one or more electronic devices 98 that are related to the patient support device 20, related to one or more devices associated with the patient support device 20 (or the patient assigned thereto), and / or related to one or more medical records of the patient stored in the EMR server 92.

[0112] The locator unit 60 is adapted to wirelessly receive signals from the patient support device 20 and to deliver those signals to the communication consent 64 in a manner that is consistent with how signals are delivered to the communication consent 64 when a conventional nurse call cable 66 is directly connected between the patient support device 20 and the communication consent 64 (via cable port 148; see FIG. 5). The locator unit 60 is also adapted to transmit signals received from the communication consent 64 to the patient support device 20 via the BT transceiver 106 and / or the UWB transceiver 104 (FIG. 5). In this way, the patient support device 20 and the locator unit 60 cooperate to transmit and receive signals to and from the communication consent 64 in a manner that is transparent to the communication consent 64 such that the communication consent 64 cannot detect whether the locator unit 60 is communicating with the patient support device 20 via a wired connection between the patient support device 20 and the locator unit 60 (wherein the latter is in wired communication with the consent 64) or whether it is communicating with the patient support device 20 via wireless communication. In this way, a healthcare facility can utilize the wireless communication capabilities of one or more patient support devices 20 without having to make any changes to their existing communication consents 64.

[0113] As described above, in addition to transmitting the signals received from the patient support device 20 to the communication consent 64, the locator unit 60 is also adapted to transfer the signals received from the communication consent 64 to the patient support device 20. Accordingly, the locator unit 60 is adapted to perform two-way communication between the patient support device 20 and the communication consent 64. This two-way communication includes, but is not limited to, communicating command signals from any of the control units 50 and / or any of the electronic devices 98 to the corresponding room devices 72, 74, and / or 76, and communicating audio signals between the person supported on the patient support device 20 and the caregiver located at a location away from the patient support device 20. The audio signals from the microphone on the patient support device 20 received by the locator unit 60 are transferred to the communication consent 64 (for transfer to the nurse call system 70), and the audio signals of the nurse located at a remote location, received by the communication consent 64 (from the nurse call system 70), are transferred to the on-board speaker of the patient support device 20.

[0114] In some embodiments, the nurse call cable 66 has a conventional 37-pin connector at each end, one adapted to be inserted into the outlet 64 and the other adapted to be inserted into the locator unit 60. Such a 37-pin connection is one of the most common types of connectors found in existing walls of a medical facility for connecting the nurse call system 70 and the room devices 72, 74, and 76. The locator unit 60 and the nurse call cable 66 are thus configured to couple to one of the most common types of communication outlets 64 used in a medical facility. However, such 37-pin connectors are not the only type of connector, and it will be understood that the locator unit 60 can also utilize different types of connectors adapted to be electrically coupled to different types of nurse call cables 66 and / or different types of communication outlets 64. An example of such alternative communication outlets 64 and cables 66 is disclosed in U.S. Patent Application No. 14 / 819,844, filed Aug. 6, 2015, entitled “Patient Support Apparatuses with Wireless Headwall Communication” by inventors Krishna Bhimavarapu et al. The entire foregoing disclosure is incorporated herein by reference. Still other types of communication outlets 64 and corresponding connectors may be utilized.

[0115] The locator unit 60 (FIG. 4) also includes an electrical cord 102 having a plug disposed at its distal end adapted to be inserted into a conventional electrical outlet 108. The electrical cord 102 enables the locator unit 60 to receive power from a central power source via the outlet 108. In some embodiments, it will be understood that the locator unit 60 is battery-powered and the cord 102 may be removed. In yet other embodiments, the locator unit 60 is battery-powered and also includes the cord 102, and in the event of a power loss, battery power may supply the locator unit 60 and / or power may be received through the outlet 108 in the event of a dead battery.

[0116] In some embodiments, the locator unit 60 includes a video port 120 adapted to receive a display cable 110 (FIG. 4). The display cable 110 is adapted to couple to the locator unit 60 at one end thereof and to a display device 56 at the opposite end thereof. The locator unit 60 may be configured to transmit, using the cable 110, data to be displayed thereon to the display device 56. Such data may include data from one or more medical devices (or other types of devices) associated with a patient on the patient support device 20 (or associated with the patient support device 20 itself), status data from one or more sensors onboard the patient support device 20, location data regarding the location of the patient support device 20, and / or other data. The cable 110 may be an HDMI (High-Definition Multimedia Interface) cable, a VGA (Video Graphics Array) cable, a DP (DisplayPort) cable, a plurality of RCA (Radio Corporation of America) cables, a DVI (Digital Visual Interface) cable, and / or other types of cables. The locator unit 60 is configured to include a complementary type of connector that couples to a connector at one end of the cable 110. Further details regarding communication between the patient support device 20 and the display device 56 are provided below, and in some embodiments, the patient support device 20 may be configured to communicate directly with a particular display device without using the locator unit 60 as a communication medium.

[0117] In addition to the structures and functions described herein, the locator unit 60 is configured to communicate location data to the patient support device 20 that enables the patient support device 20 and / or the patient support device server 84 to determine the location of the patient support device 20 within the medical facility. Generally, such location determination is performed by the patient support device 20 analyzing wireless signals communicated between itself and the locator unit 60, and its position relative to the locator unit 60 is determined. If the patient support device 20 or a predefined reference point on the patient support device 20 (e.g., its head end) is located within the threshold distance of the locator unit 60, the patient support device 20 associates itself with the locator unit 60. When associated, the patient support device 20 transmits data to and receives data from the locator unit 60 and also determines that its location within the medical facility is the same as the location of the locator unit 60. When the patient support device 20 is outside the threshold distance, the patient support device 20 does not associate itself with the locator unit 60, and thus does not exchange data with the locator unit 60 and does not determine that its location is the same as the location of the locator unit 60.

[0118] In some embodiments, the patient support device 20 is configured to associate itself with a particular locator unit 60 when both the patient support device 20 (or a reference point thereon) and the locator unit 60 are simultaneously disposed inside a common volumetric space 152a (see FIG. 4). In some embodiments, the volumetric space 152a is defined in relation to each locator unit 60 and is not movable. In other embodiments, the volumetric space 152a is defined in relation to the patient support device 20 and moves as the patient support device 20 moves. In both embodiments, the patient support device 20 associates itself with the nearby locator unit 60 when both the locator unit 60 and the patient support device 20 (or a reference point thereon) are simultaneously present inside a predefined volumetric space 152a. This example is shown in FIG. 4, in which the head end 38 of the patient support device 20 and the locator unit 60 are both disposed inside the volumetric space 152a, and thus the patient support device 20 associates itself with that particular locator unit 60.

[0119] After associating itself with a particular locator unit 60, the patient support device 20 is configured to be able to determine its absolute position within the healthcare facility by receiving a unique locator identifier (ID) 122 (FIG. 5) from the locator unit 60. The position of each of the locator units 60 within the healthcare facility is surveyed during installation of the locator unit 60, and the unique ID 122 of each locator unit 60 is also recorded during installation of the locator unit 60. This survey information and corresponding ID information can be stored within the patient support device server 84 and / or onboard the patient support device 20, such that when the patient support device 20 is associated with a particular locator unit 60, the patient support device 20 and / or the patient support device server 84 can determine the position of the patient support device 20.

[0120] In an embodiment where the patient support device server 84 is configured to determine the position of the patient support device 20, the patient support device 20 transmits its relative position information and / or the ID 122 of the associated locator unit 60 (as well as its own unique patient support device ID 130 (FIG. 5)) to the server 84. The server 84 has a table of all the positions of the locator unit 60 (generated through the survey work during the installation of the locator unit 60 as described above), and the server 84 uses this table to associate the patient support device ID 130 and the locator unit 60 ID 122 it received with a specific position within the medical facility. Thus, when a specific patient support device 20 (having a specific ID 130) transmits the ID 122 of the associated locator unit corresponding to room 430, the server 84 determines that the specific patient support device 20 is currently located within room 430. Generally speaking, as will be discussed in more detail below, the position of the patient support device 20 is adapted to correspond to any locator unit 60 with which it is currently associated, and if it is not currently associated with any locator unit 60, its position may be considered not to be determined.

[0121] In some embodiments of the patient support device 20 and the locator unit 60, the relative position of the patient support device 20 with respect to the locator unit 60 is determined using only ultra-wideband wireless communication between the patient support device 20 and the locator unit 60. Alternatively, in some embodiments, the patient support device 20 uses only short-range infrared communication with the locator unit 60 to determine its relative position. Here, such short-range infrared communication is possible only when the patient support device 20 is placed in the vicinity of the locator unit 60 (e.g., in a range of about 1 to 3 meters without obstacles). In these latter embodiments, when the patient support device 20 can successfully communicate with the nearby locator unit 60 using these short-range infrared communications, the patient support device 20 may report that its position coincides with the position of the nearby locator unit 60. Further, in some embodiments, the patient support device 20 and the locator unit 60 can communicate with each other using both infrared communication and ultra-wideband wireless communication. Further details regarding the use of short-range infrared communication for position determination are described in U.S. Patent No. 9,999,375 to the same applicant, issued on June 19, 2018, entitled "Location Detection Systems and Methods" by inventors Michael Hayes et al. The entire above disclosure is incorporated herein by reference.

[0122] In some embodiments, the locator unit 60 and / or the patient support device 20 may be configured to include any or all of the functions of the wireless headwall unit and / or the patient support device disclosed in U.S. Patent Application No. 14 / 819,844, filed Aug. 6, 2015, by the same applicant, titled "Patient Support Apparatuses with Wireless Headwall Communication," by inventors Krishna Bhimavarapu et al.; U.S. Patent Application No. 63 / 026,937, filed May 19, 2020, by the same applicant, titled "Patient Support Apparatuses with Headwall Communication," by inventors Alexander Bodurka et al.; and / or U.S. Patent Application No. 63 / 245,245, filed Sep. 17, 2021, by the same applicant, titled "System for Locating Patient Support Apparatuses," by inventors Kirby Neihouser et al. The entire above disclosure is incorporated herein by reference.

[0123] Further, in some embodiments, the locator unit 60 and / or the patient support device 20 may be configured to include any of the features and / or functions of the headwall unit 144a and / or the patient support device disclosed in U.S. Patent Application No. 63 / 131,508, filed Dec. 29, 2020, by the same applicant, titled "Tool for Configuring Headwall Units Used for Patient Support Apparatus Communication," by inventors Kirby Neihouser et al. The entire above disclosure is incorporated herein by reference.

[0124] FIG. 5 shows a block diagram of the patient support device 20, the locator unit 60, the departure detection sensor 100, the nurse call device 150, the display device 56, the secondary patient support device 20a, and the network 80. As will be discussed in more detail below, the patient support device 20 is configured to automatically determine the location of one or more of the secondary patient support device 20a, the locator unit 60, the departure detection sensor 100, the nurse call device 150, and / or other devices. In addition, the patient support device 20 is configured to automatically communicate with those devices when they are disposed proximal to the predefined patient support device 20. In some embodiments, when a particular device is disposed within the defined proximal, the patient support device 20 automatically associates that device with the patient assigned to the patient support device 20 (and / or to the patient support device 20 itself), such that data from that device(s) is displayed on one or more display devices 56, and / or such that data from that device(s) is transferred to the patient support server 84 and / or the EMR server 92 communicating with the network 80. When the device is disposed outside the defined proximal, the patient support device 20 may automatically disassociate itself from that device, and in some instances, may terminate communication with that device and / or communicate the disassociation to the patient support server 84.

[0125] The locator unit 60 includes an ultra-wideband wireless transceiver 104, a Bluetooth® transceiver 106, a locator unit controller 112, a configuration circuit 114, a television controller 116, a headwall interface 118, a video port 120, a unit ID 122, and in some embodiments, an infrared transceiver 124. The Bluetooth® transceiver 106 is adapted to communicate with an on-board Bluetooth® transceiver 128 in the patient support device 20 using RF waves that comply with any of the conventional Bluetooth® standards (e.g., IEEE802.14 and / or the standards maintained by the Bluetooth® Special Interest Group (SIG) of Kirkland, Washington, USA). In some embodiments, transceivers 106 and 128 utilize Bluetooth® Low Energy communication.

[0126] The ultra-wideband wireless transceiver 104 is adapted to communicate with one or more ultra-wideband wireless transceivers 132 disposed onboard the patient support device 20. The transceiver 104 is adapted to determine the distance between itself and the patient support device 20. Alternatively or additionally, the transceiver 104 may be adapted such that one or more of the UWB transceivers 132 onboard the patient support device 20 can determine their distance from the transceiver 104. In some embodiments, the transceivers 104 and 132 use time of flight (TOF) calculations to determine these distances. In other embodiments, the transceivers 104 and 132 can utilize other techniques, either in addition to or instead of TOF calculations, to determine the distance from each other. In some embodiments, the transceivers 104, 132 can also determine the angle formed between them, using angle information derived from the positions of the antenna arrays onboard the transceivers 104, 132, or by using other techniques. The position and orientation of each transceiver 132 onboard the patient support device 20 are known, stored in the onboard memory 134, and used to determine the position and orientation of the patient support device 20 relative to the locator unit 60 with which it is communicating.

[0127] In some embodiments, transceivers 104, 132 are implemented as any of the Trimension™ ultra-wideband wireless modules available from NXP Semiconductors located in Austin, Texas. These modules utilize, among others, but not limited to, any of the chips such as NXP SR150, SR100T, SR040, NCJ29D5, and / or OL23DO chips, and include Trimension™ UWB modules such as ASMOP1BO0N1, ASMOP1CO0R1, and / or ASMOP1CO0A1. Modules manufactured and / or sold by other companies may also be used, including, among others, but not limited to, Decawave DWM1000, DWM10001C, DWM3000 modules (available from Decawave located in Dublin, Ireland), Nordic TSG5162 SiP modules (available from Tsingoal Technology located in Beijing, China), and / or UWB hubs, wands, and / or sensors available from Zebra technologies located in Lincolnshire, Illinois. Additionally, other types of UWB modules may be used to implement transceivers 104 and 132.

[0128] The locator unit controller 112 is adapted to control the operation of transceivers 104, 106, the configuration circuit 114, the TV controller 116, the headwall interface 118, the video port 120, and, if included, the IR transceiver 124 (FIG. 5). When the infrared transceiver 124 is included, it may be provided to provide backward compatibility with patient support devices 20 that do not include the UWB transceiver 132. That is, some medical facilities may have one or more patient support devices that do not include the UWB transceiver 132 but include an IR transceiver adapted to communicate with the IR transceiver 124. When the locator unit 60 includes the IR transceiver 124, the locator unit 60 can communicate its unit ID 122 to such a patient support device via the IR transceiver 124, which is a short-range transceiver configured to communicate only with adjacent patient support devices when the patient support device is in proximity (e.g., does not have a distance of about 5 feet). Such an adjacent patient support device 20 can then communicate the received locator unit ID 122, along with its own unique ID 130 (FIG. 5), to a server 84 that can associate the locator unit ID 122 with a specific location within the medical facility as described above. By doing so, the server 84 can use the locator unit 60 to determine the location of a version of the patient support device 20 that does not have the UWB transceiver 132 but has an IR transceiver.

[0129] The headwall interface 118 is adapted to change the electrical state of one or more pins that are in electrical communication with the communication outlet 64 (via cable 66). The headwall interface 118 changes these electrical states in response to commands from the controller 112. For example, if the patient egress detection system 136 of the patient support device 20 detects patient egress, the controller 140 of the patient support device 20 transmits an egress alert signal to the locator unit 60, and the controller 112 commands the headwall interface 118 to change the electrical state of at least one pin that is used to signal an egress alert (or a generic priority alert) to the nurse call system 70 via the communication outlet 64, in response. Additionally, if an egress detection sensor 100 associated with the patient support device 20 detects egress from a secondary patient support device 20a, the egress detection sensor 100 transmits an egress detection alert signal to the patient support device 20, and in turn the patient support device 20 forwards that egress alert signal to the locator unit 60, and the controller 112 responds by commanding the headwall interface 118 to change the electrical state of the same pins as it does in response to receiving an egress detection alert from the egress detection system 136. This is discussed in more detail below.

[0130] In some embodiments, the headwall interface 118 can be configured in the same manner as the cable interface 88 described in U.S. Patent Application No. 63 / 193,778, filed May 27, 2021, by the same applicant and entitled "Patient Support Apparatus and Headwall Unit Syncing" by inventors Krishna Bhimavarapu et al., and / or can include any one of its functions. The entire above disclosure is incorporated herein by reference. Alternatively or additionally, the headwall interface 118 can be configured in the same manner as the headwall interface 120 disclosed in U.S. Patent Application No. 63 / 131,508, filed December 29, 2020, by the same applicant and entitled "Tool for Configuring Headwall Units Used for Patient Support Apparatus Communication" by inventors Kirby Neihouser et al., and / or can include any one of its same functions. The entire above disclosure is incorporated herein by reference. The locator unit 60 may also be configured to perform any of the functions of the headwall unit 94 disclosed in the above '778 application.

[0131] The configuration circuit 114 and the TV controller 116 may be configured to implement any of the same functions as the configuration circuit 132 and the TV control circuit 134, respectively, of U.S. Patent Application No. 63 / 131,508, filed on December 29, 2020, by the same applicant and entitled "Tool for Configuring Headwall Units Used for Patient Support Apparatus Communication" by Kirby Neihouser et al., and / or may be configured in any one of the same ways. The entire above disclosure is already incorporated herein by reference. Additionally or alternatively, the locator unit 60 may be configured to implement any of the functions of the headwall unit 144 disclosed in the above '508 application.

[0132] The patient support device 20 includes a controller 140, a memory 134, a departure detection system 136, a microphone 142, a Bluetooth® transceiver 128, one or more UWB transceivers 132, a display 52 (which may be part of the control panel 54a and / or part of another control panel 54), a network transceiver 96, a proximity field transceiver 144, a nurse call interface 146, and a plurality of additional elements not shown in FIG. 5. The UWB transceivers 132 are each disposed at known locations of the patient support device 20. This known location information is stored in the memory 134 and / or elsewhere and can be defined with respect to any suitable reference system common to the patient support device 20. This known location information can include the spatial relationships between the UWB transceivers 132 and / or between any other components of the patient support device 20. For example, in some embodiments, the known location information includes not only the spatial relationships between the UWB transceivers 132 but also the spatial relationships between the UWB transceivers 132 and one or more of the following: the head end 38 of the patient support device 20, the foot end of the patient support device 20, the sides of the patient support device 20, reference points defined on the patient support device 20, the floor surface, and / or other components and / or landmarks of the patient support device 20. In some embodiments, this location information is used to determine the orientation of the patient support device 20 with respect to one or more walls 62, locator units 60, other patient support devices 20a, and / or other objects or structures within the medical facility.

[0133] In some embodiments, the patient support device 20 includes four UWB transceivers 132, each of which is disposed generally adjacent to one of the four corners of the patient support device 20. In such some embodiments, the four UWB transceivers 132 are attached to or disposed in the vicinity of the four corners of the retractable frame 28. In other embodiments, the four UWB transceivers 132 are attached to or disposed in the vicinity of the four corners of the base 22. In some embodiments, the four UWB transceivers 132 are each attached to a corner of the support deck 30. Additionally, UWB transceivers 132 at other locations, and other numbers of UWB transceivers 132, may be incorporated into the patient support device 20. In embodiments of the patient support device 20 in which one or more of the UWB transceivers 132 are coupled to a movable component of the patient support device 20 (e.g., the retractable frame 28 that can change its height and orientation, or the support deck 30 whose sections, such as the head section 44, can be pivoted), the sensor is provided inside the patient support device 20 and communicates the current position of the movable component to the controller 140, whereby the controller 140 can determine the current position of the UWB transceivers 132 and further use their positions when determining the current positions of, for example, a secondary patient support device 20a, a nurse call device 150, an occupancy detection sensor 100, a locator unit 60, and / or other devices.

[0134] Similar to controller 112, controller 140 can have many different forms. In the illustrated embodiment, these controllers are each implemented as a conventional microcontroller. However, these controllers may be modified for use with many different types of circuits - either alone or in combination with one or more other microcontrollers. Here, different types of circuits include, but are not limited to, for example, any one or more microprocessors, FPGAs (field programmable gate arrays), SoCs (systems on a chip), volatile or non-volatile memories, discrete circuits, and / or other hardware, software, or firmware known to those skilled in the art that can perform the functions described herein. Such components can be physically configured in any suitable way, such as by mounting them on one or more circuit boards, or by combining them into a single unit or distributing them across multiple units, etc. The instructions followed by controllers 112 and 140 when performing the functions described herein, like the data required to perform these functions, are stored in the corresponding memory accessible to a particular controller (e.g., memory 134 for controller 140 and memory (not shown) for controller 112). In some embodiments, controller 140 can include or operate with a microcontroller integrated with or associated with UWB transceiver 132. And, controller 112 can include or operate with a microcontroller integrated with or associated with UWB transceiver 132.

[0135] The controller 140 uses the UWB transceiver 132 to determine the relative position of the patient support device 20 with respect to one or more nearby locator units 60 and to determine the relative position of one or more objects or devices with respect to the patient support device 20. When the patient support device 20 is disposed within the range of the locator unit 60, its UWB transceiver 132 communicates with the UWB transceiver 104 disposed on the locator unit 60, and the transceivers 132 and 104 exchange signals that enable them to determine the distance therebetween. This distance determination is performed for each UWB transceiver 132 disposed on board the patient support device 20 (or for the number of UWB transceivers 132 necessary to determine the exact position of the locator unit 60 with respect to the patient support device 20).

[0136] In some embodiments, the UWB transceivers 104, 132 may also be configured to determine the angular relationship between them. The distance (and angular information) in at least some embodiments is calculated by the UWB transceiver 132 and the controller 140 of the patient support device 20. In other embodiments, the UWB transceiver 104 and the controller 112 can calculate the distance (and angular information) and transfer the calculation result to the patient support device 20 (either via the UWB transceiver 104 or the BT transceiver 106). In any situation, the patient support device controller 140 is informed of the distance (and, in some embodiments, angular information as described above) between the transceivers 132 and 104. These distances and orientations are then used to calculate the relative position of the patient support device 20 with respect to the locator unit 60 in a common reference system. Here, the common reference system can be defined in a relationship fixed with respect to the patient support device 20 or in a relationship fixed with respect to the locator unit 60.

[0137] Although FIGS. 4 and 5 show only a single locator unit 60, it will be understood that a typical medical facility may include a plurality of locator units 60 located at different positions throughout the facility, including those located inside and outside of patient rooms. Typically, at least one locator unit 60 is located in each patient room of the medical facility, and additional locator units 60 may be included such that each patient support device 20 has a locator unit 60 located adjacent to each bay area within the room, if the room is intended to be occupied by multiple patients (e.g., includes multiple bays). Additional locator units 60, such as, for example, uncoupled locator units 60, may also be located at other positions throughout the medical facility.

[0138] The position of the patient support device 20 relative to the locator unit 60 is repeatedly determined by the exchange of communication signals between the UWB transceivers 104 and 132. This exchange is initiated by an interrogation signal that can be transmitted by the UWB transceiver 104 of the locator unit 60 and / or can be transmitted by the UWB transceiver 132 of the patient support device 20. In at least some embodiments, the trigger for transmitting these interrogation signals (from either source) may simply be the elapse of a pre-determined time. That is, in some embodiments, the patient support device 20 and / or the locator unit 60 may be configured to periodically transmit interrogation signals that are responded to by the UWB transceivers 104 or 132 disposed within their signal range. In embodiments where the patient support device 20 is configured to transmit such interrogation signals, the time interval between the interrogation signals may be varied according to the position and / or other state of the patient support device 20. For example, in some embodiments, the patient support device 20 may be configured to transmit interrogation signals with a longer time interval between them when the patient support device is stationary, and to transmit interrogation signals with a shorter time interval between them when the patient support device is moving. Indeed, in some embodiments, the controller 140 may be configured to stop transmitting such interrogation signals after the patient support device 20 has stopped moving and until it starts moving again. In any of the above embodiments, the movement of the patient support device 20 may be detected in any suitable manner, for example, by including one or more motion sensors (e.g., one or more accelerometers) on the patient support device 20 and / or by monitoring the numerical values of repeated distance measurements and looking for changes that indicate its movement.

[0139] The measured distance (and / or angle information between the locator unit 60 and the patient support device 20) generated from the communication between the UWB transceivers 104, 132 can utilize AoA (Angle of Arrival) information, TOF information, CSI (Channel State Information), TDoA (Time Difference of Arrival) information, TWR (Two-Way Ranging) information, and / or other information. In some embodiments, each transceiver 104, 132 includes an array antenna that is used to generate distance and / or angle information for the transceivers 104, 132 with which it is communicating. Further, in some embodiments, the UWB transceivers 104, 132 include one or more of their own microcontrollers, and the positions of the UWB transceivers 104, 132 can be determined by these internal controllers without utilizing the controllers 140 and / or 112. In other embodiments, the controllers 112 and / or 140 can cooperate with the microcontrollers of the transceivers 104, 132 to determine their relative positions with respect to each other.

[0140] The nurse call interface 146 of the patient support device 20 (see FIG. 5) includes a Bluetooth® transceiver 128 and a cable port 148 in some embodiments. The nurse call interface 146 provides an interface to the patient support device 20 for communicating with the outlet 64 of the nurse call system 70. That is, the nurse call interface 146 provides the patient support device 20 with means for communicating bi-directionally with the communication outlet 64. As has been discussed, in some situations, the patient support device 20 communicates with the Bluetooth® transceiver 106 of the locator unit 60 using the Bluetooth® transceiver 128, and the locator unit 60 exchanges communications between the outlet 64 and the patient support device 20. In other words, in some situations, the locator unit 60 functions as an intermediary between the nurse call interface 146 and the outlet 64. Alternatively, the nurse call cable 66 can be directly coupled between the patient support device 20 and the wall outlet 64, thereby obviating the need to use the locator unit 60 as a communication intermediary. In such a situation, one end of the nurse call cable 66 is plugged into the cable port 148 of the patient support device 20 and the other end of the cable 66 is plugged directly into the outlet 64. The nurse call interface 146 thereby provides the patient support device 20 with the ability to communicate with the outlet 64 either wirelessly or via wired means.

[0141] Patient support device 20 also includes, in at least some embodiments, a microphone 142 (FIG. 5) that is used to detect the patient's voice when the patient wishes to speak to a nurse who is in a remote location. The patient's voice is converted by the microphone 142 into an audio signal, and the controller 140 is adapted to transfer these audio signals to an adjacent communication outlet 64 disposed within the wall 62 (FIG. 4). When a cable 66 is coupled between the cable port 148 of the patient support device 20 and the outlet 64, the controller 140 transfers these audio signals to the outlet 64 via the cable 66. When such a cable 66 does not extend between the patient support device 20 and the outlet 64, the controller 140 wirelessly transfers these audio signals to the locator unit 60 with which it is currently associated (using the transceiver 128 or, in some embodiments, one of the transceivers 132), and the controller 112 of the locator unit 60 transfers these audio signals to the outlet 64. As described, the outlet 64 is in electrical communication with a conventional nurse call system 70 that is adapted to direct the audio signals to the correct nurse station 78 and / or to other locations. In some embodiments, the microphone 142 serves as both a microphone and a speaker. In other embodiments, a separate speaker may be included for transmitting voice signals received from a nurse in a remote location. In some embodiments, the audio communication between the patient support device 20 and the communication outlet 64 is performed and / or includes any of the structures of any of the ways disclosed in U.S. Patent Application No. 16 / 847,753, filed Apr. 14, 2020, of the same applicant, entitled “Patient Support Apparatuses with Nurse Call Audio Management” by inventors Alexander Bodurka et al. The entire foregoing disclosure is incorporated herein by reference.

[0142] After the locator unit 60 is installed within a particular medical facility, the location of each locator unit 60 within that facility is recorded. In some embodiments, the coordinates of the location of the locator unit 60 in a common reference system are recorded (or, after recording, converted to a common reference system). Such coordinates may be three-dimensional (i.e., including a vertical component and two horizontal components), or may be two-dimensional (without a height component). In other embodiments, rather than the exact coordinates of one or more locator units 60, a more generalized location of the locator unit 60 is determined. The generalized location of the locator unit 60 may include an indication of the room, bay, area, corridor, portion of a corridor, wing, maintenance area, etc. in which the locator unit 60 is located. In still other embodiments, the location of one or more locator units 60 is determined both generally and more precisely.

[0143] Regardless of how the location of each locator unit 60 is initially determined after the locator unit 60 is installed within the medical facility (e.g., whether their coordinates are determined or a more general location is determined), the locations of all locator units 60 are stored in a memory accessible to the server 84, along with their unique IDs 122. The server 84 then uses this location data and ID data to determine the location of the patient support device 20. Alternatively or additionally, this location data and ID data 122 are transferred to the patient support device 20 for storage in its on-board memory 134 and for use in determining its own location. In some embodiments, the location of each locator unit 60 (regardless of whether it is specific or general) is additionally or alternatively stored in the memory within that particular locator unit 60 and shared with a device (e.g., the patient support device 20) that communicates with it. In some other embodiments, the location of each locator unit 60 may be stored in multiple locations.

[0144] It will be appreciated that the patient support device 20 is configured to communicate with the locator unit 60 regardless of the orientation of the patient support device 20. That is, the UWB transceivers 104 and 132 are wireless high-frequency transceivers that do not rely on LOS (line of sight) communication, unlike the IR transceiver 124 (if present). Thus, the patient support device 20 does not need to be oriented in any particular direction with respect to the locator unit for the transceivers 104 and 132 to communicate. This is different from some prior art systems that use IR communication between the patient support device and the locator unit and require an on-board IR transceiver of the patient support device 20 to be oriented towards the locator unit to establish communication. It will also be appreciated that the locator unit 60 can be placed in contact with a wall, column, ceiling, or any other fixed structure within the medical facility.

[0145] The patient support device 20 is also configured to use the UWB transceiver 132 to determine the positions of various other devices relative to the patient support device 20, such as one or more departure detection sensors 100, one or more nurse call devices 150, one or more secondary patient support devices 20a, and / or one or more other devices physically separated from the patient support device 20 (Figure 5). As will be discussed in more detail below, the controller 140 uses the UWB transceiver 132 to communicate with one or more respective UWB transceivers mounted on or attached to tags on those devices to determine the relative positions of those devices. Such UWB transceivers operate in the same manner as the transceiver 132 and / or the UWB transceiver 104 of the locator unit 60. And, as will also be discussed in more detail below, the controller 140 of the patient support device 20 uses the relative position information to determine how the patient support device 20 interacts with these devices, including whether to associate with these devices. As will be discussed in detail below, when the controller 140 associates the patient support device 20 with one or more of these devices, the controller 140 and / or the server 84 may perform one or more of the following actions, namely, display data from these devices on the display 52 and / or the display device 56, transmit data from one or more of these devices to the patient support device server 84 and / or the EMR server 92 via the network transceiver 96, transmit one or more signals from these devices to the communication consent 64 (either via the cable 66 or through the locator unit 60), transfer one or more signals from the consent 64 to one or more of these devices, retrieve data generated by these devices from the EMR server 92, retrieve data from these devices via another route independent of the EMR server 92, and / or may perform other actions.

[0146] The nurse call device 150 (FIG. 5) includes a UWB transceiver 154, a controller 156, a near-field transceiver 158, a nurse call button 160, a unique ID 166, and in some embodiments, a microphone / speaker 162 and a Bluetooth® transceiver 164. The UWB transceiver 154 is adapted to communicate with a UWB transceiver 132 disposed onboard the patient support device 20 such that the position of the nurse call device 150 relative to the patient support device 20 can be repeatedly determined. The UWB transceiver 154 may be the same as all other UWB transceivers discussed herein (e.g., UWB transceivers 132, 104). The UWB transceiver 154 is further adapted to transmit the unique ID 166 of the nurse call device 150 to the patient support device 20 so that the patient support device 20 can know which specific nurse call device 150 it is communicating with.

[0147] The controller 156 of the nurse call device 150 monitors the operation of the nurse call device 150, processes communications between the UWB transceiver 154 and other UWB transceivers (e.g., transceiver 132), responds to activation of the nurse call button 160, and, when the microphone / speaker 162 and Bluetooth® transceiver 164 are included, monitors their operation. The nurse call device 150 is designed to be a stand-alone device that can be attached to a structure in a hospital room and give that structure nurse call capabilities (i.e., the ability for adjacent patients to call a nurse using the nurse call device 150). For example, a secondary patient support device 20a, such as a recliner, chair, or other patient support, may be configured by its manufacturer to not have the ability for a patient to call a nurse using it. By physically attaching the nurse call device 150 to the secondary patient support device 20a, the secondary patient support device 20a then gains the ability for a patient to call a nurse. This will be discussed in more detail below.

[0148] When the controller 156 detects that the nurse call button 160 has been pressed, it transmits a nurse call signal to the patient support device 20 using the UWB transceiver 154 and / or the Bluetooth® transceiver. The controller 140 of the patient support device 20 is configured to respond to this nurse call signal in the same manner as when it responds to the activation of the nurse call control unit 50g (FIG. 3) on its control panel 54. The above control unit 50g causes the controller 140 to transmit a signal to the nurse call system 70 that requests a nurse who is in a remote location to talk to the patient. More specifically, the controller 140 responds to both the activation of the control unit 50g and the reception of a nurse call button press from the nurse call device 150 by changing the electrical characteristics of one or more of the pins within the communication consent 64. When the patient support device 20 is coupled to the consent 64 by a cable 66, the controller 140 changes the state of one or more on-board relays of the patient support device 20 that are in electrical communication with one or more pins of the cable 66 (and thus in electrical communication with the pins of the consent 64). When the patient support device 20 is wirelessly coupled to the consent 64 by an adjacent locator unit 60, the controller 140 transmits a message to the locator unit 60 (via the Bluetooth® transceiver 128 and / or one or more UWB transceivers 132) that instructs the controller 112 to control the headwall interface 118 such that the electrical state of one or more pins of the consent 64 is changed. In many conventional consents 64, the nurse call signal is communicated by changing the electrical state of pin 25 (nurse call +) or pin 26 (nurse call normally open / normally closed) with respect to a common pin. Of course, the patient support device 20 and the headwall interface 118 can be configured to change the electrical state of one or more other pins in response to a nurse call signal (from the control unit 50g or the nurse call device 150) depending on the specific communication consent 64 installed within a particular medical facility.

[0149] Regardless of which pins are being changed in their electrical state, the conventional nurse call system 70 is configured to detect these changes in electrical state and provide a signal to one or more nurse stations 78 indicating that a patient in a particular room is requesting to speak with a nurse. The nurse call system 70 enables a nurse to answer this call by picking up a telephone handset or other means. When the nurse answers this call, audio communication between the nurse and the patient can be carried out on conductor 68. That is, an electrical signal corresponding to the nurse's voice is transmitted on conductor 68 to communication consent 64 on a particular pin (typically pins 8 and 9, although other pins may be used), and then these are transferred to the patient support device 20 either through cable 66 coupled to the patient support device 20 and consent 64 or (if cable 66 is coupled between the locator unit 60 and consent 64) through the locator unit 60. When the locator unit 60 is plugged into consent 64 by cable 66, the controller 112 transmits an audio signal corresponding to the nurse's voice to the patient support device 20 by means of the Bluetooth transceiver 106. The controller 140 of the patient support device 20 then either transmits these audio signals to an on-board speaker (not shown) or transmits them to the nurse call device 150. The controller 150 makes this routing decision based on whether the nurse call signal was caused by activation of the on-board control unit 50g or by reception of a nurse call signal from the nurse call device 150. That is, if the nurse call signal is originated from the nurse call device 150, the controller 140 transmits the audio signal to the nurse call device 150 via the Bluetooth transceiver 128, and the nurse call device 150 transmits these audio signals to the speaker 162, which converts these audio signals into sound waves that the patient can hear.When the nurse call signal is issued because the patient has activated the on-board nurse call control unit 50g, the controller 140 transmits an audio signal to the on-board speaker, and the speaker also converts the audio signal into sound waves that the patient can hear.

[0150] In addition to transferring an audio signal from a nurse located in a remote location to the on-board speaker of the patient support device 20 or the nurse call device 150, the controller 140 is configured to transmit the patient's voice signal to the nurse call system. These patient voice signals can be detected by the on-board microphone 142 of the patient support device 20 (when the patient is on-board the patient support device 20) or by the microphone 162 when the patient is located in the vicinity of the nurse call device 150. However, once they are detected, the controller 140 transfers them to the appropriate pins of the outlet 64 either through the nurse call cable 66 or through the locator unit 60. Thus, two-way communication between the patient and the nurse can be established not only when the patient is in bed but also when the patient is adjacent to the nurse call device 150.

[0151] The nurse call device 150 is designed to be a portable device that can be applied to structures that do not have the function of enabling patients to call nurses using them, i.e., it is designed to be a portable device that can apply the function of enabling patients to call nurses to structures that do not have it installed thereon. As discussed below, in some embodiments, the nurse call device 150 may include an adhesive material or other fixing structure that enables the nurse call device 150 to be coupled to such structures. In still other embodiments, the nurse call device 150 can be coupled to a structure carried by a patient by being attached to, for example, a necklace, a wristband, a clothing item, or some other structure that is carried by the patient in a worn or other manner. Further, the nurse call device 150 can be a completely stand-alone device that is located at a position separated from the patient support device 20 and is located in an area where a patient may tend to be located.

[0152] A given medical facility may have multiple nurse call devices 150 disposed therein. Additionally, at any time, there may be multiple nurse call devices 150 disposed within the communication range of a particular patient support device 20. The patient support device 20 is configured to transfer a nurse call signal received from an associated nurse call device 150 only to the nurse call system 70. In fact, the patient support device 20 can be configured to ignore communications from all nurse call devices 150 that have been disassociate from the patient support device 20. The patient support device 20 is also configured to transmit an audio signal of the patient's voice from the nurse call device 150 that it is currently associated with and / or to transmit an audio signal of the nurse's voice thereto. The patient support device 20 does not communicate an audio signal to or from a nurse call device 150 that it is currently disassociated from.

[0153] The manner in which the controller 140 associates and then dissociates the nurse call device 150 with the patient support device 20 is described below. The association process is carried out by the user physically bringing the nurse call device 150 into the proximity field range 168 (FIG. 5) of the patient support device 20. The proximity field range 168 may be on the order of several inches and may be according to the design and configuration of proximity field transceivers 144 and 158, which may be conventional proximity field transceivers. When the proximity field transceiver 158 of the nurse call device 150 is brought within the range of the on-board proximity field transceiver 144 of the patient support device 20, the two transceivers 144 and 158 automatically communicate with each other using proximity field communication. During such communication, the proximity field transceiver 158 of the nurse call device 150 transmits its unique identifier 166 to the patient support device 20, and the controller 140 of the patient support device 20 retains this identifier 166 in the memory 134. In some embodiments, the proximity field transceiver 144 of the patient support device 20 can transfer its unique patient support device identifier 130 to the proximity field transceiver 158 of the nurse call device 150, and the controller 156 of the nurse call device 150 can place the identifier 130 in a memory (not shown). In some embodiments, one or more of the proximity field transceivers 144 can be integrated into one or more of the siderails 36, headboard 32, footboard 34, and / or other locations of the patient support device 20.

[0154] In some embodiments, after the patient support device 20 receives the identifier 166 of the nurse call device 150 via the proximity field transceiver 144, the controller 140 automatically associates the nurse call device 150 with the patient support device 20. Further, the controller 140 can display a message indicating that the association between the nurse call device 150 and the patient support device 20 has been successful on the display 52 (and / or the display device 56). FIG. 10 shows an example of such a message regarding the successful association of the departure detection sensor 100 with the patient support device 20. A similar message may be displayed on the display 52 in response to the successful association of the nurse call device with the patient support device 20. Also, a message similar to that shown in FIG. 11 can be displayed on the display 52 (and / or the display device 56) when the controller 140 disassociates the nurse call device 150 from the patient support device 20.

[0155] When the nurse call device 150 is associated with the patient support device 20, the nurse call device 150 then remains associated with the patient support device 20 until it moves outside the spatial volume 152b (Figs. 4 and 6). When the nurse call device 150 moves outside the spatial volume 152b, the controller 140 is configured to automatically disassociate the nurse call device 150 from the patient support device 20. The controller 140 repeatedly determines and monitors the position of the nurse call device 150 after it associates the nurse call device 150 with the patient support device 20. The controller 140 repeatedly determines the relative position of the nurse call device 150 with respect to the patient support device 20 using the UWB transceiver 132 that communicates with the on-board UWB transceiver 154 of the nurse call device 150. The controller 140 compares this relative position with the spatial volume 152b and, if it is outside the spatial volume 152b, automatically disassociates the nurse call device 150 from the patient support device 20. On the other hand, if the position of the nurse call device 150 remains inside the spatial volume 152b, the controller 140 maintains the association between the nurse call device 150 and the patient support device 20.

[0156] When the patient presses the nurse call device button 160 on the nurse call device 150, the nurse call device 150 transfers a nurse call signal to the patient support device 20. Specifically, this nurse call signal may be transmitted to a specific patient support device 20 associated with the nurse call device 150 (e.g., using the patient support device ID 130 that it may receive during a proximity field association process), or it may be broadcast without a specific address. In either case, the nurse call signal includes the identifier 166 of the nurse call device 150. When the patient support device 20 receives this nurse call signal, it checks the identifier 166 stored in the nurse call signal and determines whether it matches the identifier 166 of the associated nurse call device 150. If they match, the controller 140 transfers the nurse call signal to the receptacle 64 in one of the above ways. If the identifier 166 does not match the currently associated nurse call device 150, the controller 140 does not transfer that nurse call signal to the receptacle 64.

[0157] The spatial volume 152b (FIGS. 4 and 6) is defined relative to the patient support apparatus 20 and therefore moves with the movement of the patient support apparatus 20. The spatial volume 152b is generally sized so that it substantially encompasses all of the room 58 in which the patient support apparatus 20 is located, or encompasses at least a portion of the room in which the nurse call device 150 is expected to be located. When the nurse call device 150 is intended to be coupled to a secondary patient support apparatus 20a, for example a chair or recliner, the spatial volume 152b is selected to have a size that encompasses the area of ​​the room 58 in which the chair or recliner is located or may be located. In some circumstances, the spatial volume 152b may be wide enough to extend into adjacent rooms 58, but this does not affect the proper operation of the nurse call device 150 insofar as the nurse call device 150 cannot gain access to those rooms without moving outside the spatial volume 152b. In other words, the spatial volume 152b can be advantageously defined such that when the nurse call device 150 is moved outside the room 58 through the doorway, the nurse call device 150 will necessarily be outside the spatial volume 152b, thereby disassociating it from the patient support apparatus 20.

[0158] In some embodiments, the spatial volume 152b can be defined by one or more fixed dimensions. In other embodiments, the patient support device 20 and / or the patient support device server 84 can be configured such that an authenticated person can change one or more dimensions of the spatial volume 152b. Further, in some embodiments, the spatial volume 152b may have dimensions that vary based on the particular room, bay, or other location in which it is currently disposed. In these embodiments, the controller 140 can utilize a table stored in the memory 134 that defines the spatial volume 152b based on the current position of the patient support device 20. The position of the patient support device 20 may be determined by the controller 140 from a locator unit ID 122 received from the locator unit 60 with which it is associated and / or may be obtained from information received from the patient support device server 84.

[0159] The spatial volume 152b can be different from the spatial volume 152a (and the spatial volume 152c, which will be described in more detail below). FIG. 6 shows an example of an arbitrary room 58 in a medical facility where the patient support device 20, the secondary patient support device 20a, the departure detection sensor 100, and the nurse call device 150 are arranged. FIG. 6 also shows the first spatial volume 152a, the second spatial volume 152b, and the third spatial volume 152c. As has been discussed, the first spatial volume 152a is used to determine whether the patient support device 20 should associate itself with the locator unit 60 arranged adjacent to or inside the first spatial volume 152a. The second spatial volume 152b, as has been described, is used by the controller 140 to determine whether the nurse call device 150 and the patient support device 20 should be associated. The third spatial volume 152c, as will be described in more detail below, is used by the controller 140 to determine whether one or more medical devices typically arranged in the vicinity of the patient when used in the treatment of the patient (as opposed to the departure detection sensor 100 and / or the nurse call device 150, which are preferably arranged at a location away from the patient support device 20, such as at a separate patient support device 20a, etc.) should be associated with the patient support device 20. Thus, the controller 140 of the patient support device 20 can be configured to determine whether to associate a device with the patient support device 20 using a plurality of different criteria - some for the locator unit 60, others for the departure detection sensor 100 (and / or the nurse call device 150), still others for devices physically supported by or coupled to the patient support device 20, and / or yet others for different types of devices.

[0160] As shown in FIG. 6, the first spatial volume 152a is a relatively small spatial volume that is disposed proximate to or encompasses the fixed locator 60. The second spatial volume 152b encompasses a substantial portion of the room 58, and the third spatial volume 152c encompasses the patient support device 20 and a relatively small spatial volume surrounding the patient support device 20. This small spatial volume around the periphery of the third spatial volume 152c can be defined for the purpose of including an IV pole, an infusion pump, or other medical devices that can be used during the treatment of the patient but are not directly supported on the patient support device 20.

[0161] Returning to FIG. 5, the controller 156 of the nurse call device 150 can include a microcontroller and / or any of the other structures including the controller 140 and / or the controller 112 mentioned above. The controller 156 is adapted to send a signal to the associated patient support device 20 in response to activation of the nurse call button 160 and to handle voice communication between a nurse located at a location remote from the nurse call device 150. The controller 156 can be configured to additionally or alternatively monitor the operation of the UWB transceiver 154, the near field transceiver 158, and the Bluetooth® transceiver 164. In some embodiments, the controller 156 uses the Bluetooth® transceiver 164 to transmit the patient's audio signal to the patient support device 20 and to receive the nurse's audio signal from the patient support device 20. The patient's audio signal is generated by the microphone 162 and transmitted to the transceiver 128 of the patient support device 20. On the other hand, the nurse's audio signal is received by the Bluetooth® transceiver 164 and transferred to the speaker 162 for conversion to sound waves. As shown in FIG. 5, the nurse call device 150 includes a combined microphone and speaker 162. In other embodiments, the nurse call device 150 can comprise a separate microphone and a separate speaker.

[0162] The patient support device 20 can be configured to determine the relative position of one or more external egress detection sensors 100 (Figs. 5 and 6) using, additionally or alternatively, the UWB transceiver 132. The external egress detection sensors 100 refer to egress detection sensors that are external to and separate from the sensors mounted in the egress detection system 136 of the patient support device 20. Such external egress detection sensors 100 can include a UWB transceiver 170, a controller 172, a near-field transceiver 174, one or more sensors 176, and a unique ID 178 that uniquely identifies each egress detection sensor 100. The UWB transceiver 170 communicates with the UWB transceiver 132 disposed on board the patient support device 20 and is adapted to repeatedly determine the position of the egress detection sensor 100 relative to the patient support device 20. The UWB transceiver 170 can be the same as all of the other UWB transceivers discussed herein (e.g., UWB transceivers 132, 104, 154). The UWB transceiver 170 is further adapted to transmit the unique ID 178 to the patient support device 20 so that the patient support device 20 knows which particular egress detection sensor it is communicating with. The controller 140 can track which egress detection sensor 100 it is associated with using this ID 178 if it is currently associated with the egress detection sensor 100.

[0163] The controller 172 of the departure detection sensor 100 is adapted to monitor the operation of the departure detection sensor 100, process the output of the sensor 176, and control the communication executed by the UWB transceiver 170 and the near-field transceiver 174. The sensor 176 may include one or more sensors of different types adapted to detect the presence or absence of a patient on a patient support device, such as a secondary patient support device 20a. In some situations, the sensor 176 may include one or more force sensors adapted to detect the weight of the patient when the patient is supported on the departure detection sensor 100. Alternatively, the sensor 176 may include one or more infrared sensors, one or more cameras, and / or other types of sensors adapted to detect the presence and absence of the patient when the patient is disposed on the secondary patient support device 20a.

[0164] In some embodiments, the departure detection sensor 100 comprises a departure detection pad 180, an example of which is shown in FIG. 7. As shown in the figure, the departure detection sensor 100 comprises a pad 180, a cable 182, and a control unit 184. The control unit 184 houses the UWB transceiver 170, the controller 172, the identifier 179, and, in some embodiments, the near-field transceiver 174. The pad 180 itself houses the sensor 176. The pad 180 is configured to be disposed on the upper or lower side of a cushion on which a patient sits when the patient sits on a patient support device (which may be either the primary patient support device 20 or the secondary patient support device 20a). In such an embodiment, the sensor 176 detects the weight of the patient when the patient is sitting or lying on the cushion. The cushion may be a mattress, a chair cushion, or any other type of soft support adapted to provide comfortable support to the patient. When the patient departs from the patient support device on which the pad 180 is disposed, the sensor 176 detects a decrease (or complete absence) of the patient's weight, and the controller 172 is adapted to issue a departure alert.

[0165] The controller 172 is configured to issue a departure alert by transmitting a departure detection message (including ID 178) to the patient support device 20 that conveys the departure alert to the patient support device 20 (using the UWB transceiver 170). The controller 140 of the patient support device 20 responds to this departure detection message in the same way as it responds to a departure detection alert created by the on-board departure detection system 136. That is, the controller 140 is configured to issue a local alert (e.g., by emitting one or more sounds, lighting one or more lights, displaying one or more messages on the display 52, and / or taking other actions) and to transmit a remote alert to the nurse call system 70. The controller 140 transmits a remote alert to the nurse call system 70 by changing the electrical state of one or more pins of the communication consent 64. When the patient support device 20 is connected to the consent 64 by the cable 66, the controller 140 can change the state of one or more relays on-board the patient support device 20 that is in electrical communication with one or more pins of the cable 66. When the patient support device 20 is connected to the consent 64 by a wireless connection to the locator unit 60, the controller 140 transmits a departure detection message to the locator unit 60 (using the Bluetooth® transceiver 128 and / or one or more UWB transceivers 132), and the locator unit 60 responds by instructing the headwall interface 118 to change the electrical state of one or more pins of the communication consent 64.

[0166] As can be seen from the above description, by adding the departure detection sensor 100 to the secondary patient support device 20a, the secondary patient support device 20a not only gains the ability to detect the departure of the patient therefrom, but the departure detection sensor 100 also piggybacks on the primary patient support device 20 to communicate a departure detection alert to the nurse call system 70. That is, even though the secondary patient support device 20a does not have any cables 66 or the ability to communicate directly with the locator unit 60 (or communication outlet 64), the departure detection sensor 100 can utilize the communication channel of the primary patient support device 20 with the nurse call system 70 to transfer the departure detection alert to the nurse call system 70. By doing so, even in a situation where the hospital room 58 of the medical facility has only a single communication outlet 64 (which can be used by the primary patient support device 20), and even in a situation where the secondary patient support device 20a has no built-in ability to communicate with other structures in the room, such as the outlet 64 and / or the locator unit 60, a nurse located remotely can still be informed that the patient has departed from the secondary patient support device 20a. Medical personnel only need to attach the departure detection sensor 100 to the secondary patient support device 20a and ensure that it has power (either including a battery inside the control unit 184 (Fig. 7) or including an AC cable to be plugged into an AC wall outlet).

[0167] After a healthcare provider attaches the departure detection sensor 100 to a patient support such as the secondary patient support device 20a, the departure detection sensor 100 is adapted to automatically transfer its departure detection alert to the associated patient support device 20. The manner in which the departure detection sensor 100 is associated with and then disassociated from a particular patient support device 20 can be the same as the association and disassociation processes described above with respect to the nurse call device 150. That is, the association process is carried out by the user bringing the departure detection sensor 100 within the proximity field range (see FIG. 5) of the patient support device 20. When the proximity field transceiver 174 of the departure detection sensor 100 is brought within the range 168 of the on-board proximity field transceiver 144 of the patient support device 20, the two transceivers 144 and 174 automatically communicate with each other using proximity field communication. During such communication, the proximity field transceiver 174 of the departure detection sensor 100 transmits its unique identifier 178 to the patient support device 20, and the controller 140 of the patient support device 20 holds this identifier 178 in the memory 134. In some embodiments, the proximity field transceiver 144 of the patient support device 20 transfers its unique patient support device identifier 130 to the proximity field transceiver 174 of the departure detection sensor 100, and the controller 172 of the departure detection sensor 100 places that identifier 130 in a memory (not shown).

[0168] In some embodiments, after the patient support device 20 receives the identifier 178 of the departure detection sensor 100 via the proximity field transceiver 144, the controller 140 automatically associates the departure detection sensor 100 with the patient support device 20. Further, as discussed in more detail below, the controller 140 can display, on the display 52 (and / or the display device 56), a message indicating that the departure detection sensor 100 is currently successfully associated with the patient support device 20. FIG. 10 shows an example of such a message regarding the successful association of the departure detection sensor 100 with the patient support device 20. The controller 140 can also display a message, an example of which is shown in FIG. 11, when the nurse call device 150 is automatically disassociate from the patient support device 20.

[0169] When the departure detection sensor 100 is associated with the patient support device 20, the departure detection sensor 100 then remains associated with the patient support device 20 until it moves outside the spatial volume 152b (Figs. 4 and 6). When the departure detection sensor 100 moves outside the spatial volume 152b, the controller 140 is configured to automatically disassociate the departure detection sensor 100 from the patient support device 20. After it associates the departure detection sensor 100 with the patient support device 20, the controller 140 repeatedly determines and monitors the position of the departure detection sensor 100. The controller 140 uses the UWB transceiver 132 that communicates with the on-board UWB transceiver 170 of the departure detection sensor 100 to repeatedly determine the relative position of the departure detection sensor 100 with respect to the patient support device 20. The controller 140 compares this relative position with the spatial volume 152b and, if it is outside the spatial volume 152b, automatically disassociates the departure detection sensor 100 from the patient support device 20. On the other hand, as long as the position of the departure detection sensor 100 remains inside the spatial volume 152b, the controller 140 maintains the association between the departure detection sensor 100 and the patient support device 20. As described above, the dimensions of the spatial volume 152b used for the association / disassociation process of the departure detection sensor 100 may be the same as or different from the dimensions of the spatial volume 152b used for the association / disassociation process of the nurse call device 150 and / or other devices that are automatically associated with and / or disassociated from the patient support device 20.

[0170] Returning to FIG. 7, cable 182 couples pad 180 to control unit 184. As described, control unit 184 may store UWB transceiver 170, controller 172, identifier 179, and in some embodiments, proximity field transceiver 174 and pad 180, which may contain sensor 176. Control unit 184 houses one or more batteries (not shown) for powering departure detection sensor 100 and / or a power cable may be coupled to control unit 184, which may enable it to receive power from a conventional AC outlet. In the embodiment shown in FIG. 7, departure detection sensor 100 need not communicate with an electronic system that may be mounted on secondary patient support device 20a, and thus has no connections or other communication means for secondary patient support device 20a. Instead, departure detection sensor 100 is adapted to communicate directly with patient support device 20 and, when a patient's departure is detected thereby, notifies patient support device 20.

[0171] Secondary patient support device 20a (FIGS. 4 and 5) is, in some embodiments, a recliner or other chair typically positioned within patient room 58. Secondary patient support device 20a differs from primary patient support device 20 in that it typically does not have as many functions and typically does not have a departure detection function or a nurse call function (unless departure detection sensor 100 or nurse call device 150 is added thereto), is typically not intended for a patient to fall asleep on, and typically does not have circuitry for communicating with communication consent 64 (except when departure detection sensor 100 or nurse call device 150 is added thereto). Secondary patient support device 20a may be intended to provide an alternative seating spot for a patient while the patient is within the healthcare facility, thereby assisting in promoting patient movement. Secondary patient support device 20a may take other forms in addition to a chair or recliner.

[0172] As shown in FIG. 5, the secondary patient support device 20a may include a controller 186, a UWB transceiver 188, and an identifier 190. The secondary patient support device 20a may also include additional components, which may be, but are not limited to, for example, any of the components of the primary patient support device 20. In some embodiments, the secondary patient support device 20a may include any or all of the components of a recliner disclosed in any of the following U.S. patents of the same applicant, namely, U.S. Patent No. 9,713,559, issued July 25, 2017, entitled "Medical Support Apparatus" by inventors Christpher Hough et al.; U.S. Patent No. 9,782,005, issued October 10, 2017, entitled "Medical Support Apparatus" by inventors Anish Paul et al.; and U.S. Patent No. 10,330,522, issued June 25, 2019, entitled "Person Support Apparatus with Exit Detection System and / or Scale System" by inventors Anish Paul et al. The entire foregoing disclosure is incorporated herein by reference. The secondary patient support device 20a may further have other forms.

[0173] In some embodiments, the secondary patient support device 20a omits the identifier 190 and the UWB transceiver 188, as shown by the dashed line in FIG. 5. In such embodiments, the controller 186 cannot communicate with the UWB transceiver 132 disposed on board the primary patient support device 20. However, if a nurse call device 150, an occupancy detection sensor 100, and / or a UWB tag are added to the secondary patient support device 20a, then the device 150, sensor 100, and / or the tag can communicate with the UWB transceiver 132 and the controller 140 of the primary patient support device 20, and the controller 140 can not only determine the positions of the device 150, sensor 100, and / or the tag, but also, by proxy, determine the position of the secondary patient support device 20a to which the device 150, sensor 100, and / or the tag are attached.

[0174] The controller (FIG. 5) can comprise one or more microcontrollers and / or can take any of the forms of the above-described controllers 112, 140, 156, and / or 172, and is adapted to monitor the operation of the secondary patient support device 20a. In some embodiments, the secondary patient support device 20a comprises one or more sensors, and the controller 186 is adapted to transfer data from one or more of those sensors to the primary patient support device 20. The primary patient support device 20 can transfer some or all of this data to the patient support server 84, can display some or all of this data on the display 52, can transfer some or all of this data to the display device 56 (via the associated locator unit 60), and / or it can transfer some or all of this data to the EMR server 92. When the secondary patient support device 20a comprises a brake, an electrical cable, a departure detection system, a patient presence detector, a timer, and / or one or more actuators for moving the seat, backrest, and / or legrest, the controller 186 can transfer data regarding the brake (on or off), data regarding the electrical cable (plugged in or not), the departure detection system (activated or deactivated, alarming or not alarming), data regarding the current presence or absence of a patient on the secondary patient support device 20a, data regarding the amount of time a patient is present or absent on the secondary patient support device 20a, and / or data regarding the position and / or orientation of the actuator, and / or data regarding the position and / or orientation of one or more components of the secondary patient support device 20a (e.g., seat, backrest, and / or legrest).The controller 186 may further transfer other data to the primary patient support device 20 using the UWB transceiver 188 or, in some embodiments, one or more other transceivers that may be incorporated into the secondary patient support device 20a, such as, but not limited to, for example, a Bluetooth (registered trademark) transceiver.

[0175] As described, a particular embodiment of the secondary patient support device 20a shown in FIG. 5 does not include a departure detection sensor and a nurse call device. However, if a caregiver modifies the secondary patient support device 20a to include a departure detection function and / or a nurse call function, he or she can add a departure detection sensor 100 and / or a nurse call device 150 to the secondary patient support device 20a. The departure detection sensor 100 can be added as follows, i.e., first associate it with the primary patient support device 20 using proximity field transceivers 174 and 144 (described above), and then add it by placing it under or on the secondary patient support device 20a. The nurse call device 150 can be added to the secondary patient support device 20a as follows, i.e., first associate it with the primary patient support device 20 using proximity field transceivers 158 and 144 (described above), and then add it to the secondary patient support device 20a by attaching it to any conventional location of the secondary patient support device 20a. Once any of these devices are attached and associated, they enable the secondary patient support device 20a to detect a patient's departure and / or call (and in some embodiments, talk to) a nurse who is in a remote location. It should be understood that the addition of the departure detection sensor 100 and / or the nurse call device 150 to the secondary patient support device 20a does not require any cable connection between these devices and the secondary patient support device 20a, nor any electronic pairing or other configuration steps between these devices and the secondary patient support device 20a. In fact, neither the departure detection sensor 100 nor the nurse call device 150 need to be communicable with the controller 186 in order to perform their respective detection and nurse call functions. This is because, as described above, the departure detection sensor 100 and the nurse call device 150 are stand-alone devices that can operate independently regardless of the structure (e.g., secondary patient support device 20a) to which they are attached.

[0176] In an embodiment of the secondary patient support device 20a that includes the controller 186 and the UWB transceiver 188, it is possible for the primary patient support device 20 to receive three separate data flows from the secondary patient support device 20a. The first flow can come from the UWB transceiver 188, and this flow can include data regarding the various components of the secondary patient support device 20a discussed above. The second flow can come from the UWB transceiver 170 when the departure detection sensor 100 is coupled to the secondary patient support device 20a. Further, the third flow can come from the UWB transceiver 154 when the nurse call device 150 is coupled to the secondary patient support device 20a. Of course, the primary patient support device 20 may receive a smaller number of data flows if the departure detection sensor 100 and / or the nurse call device 150 are not coupled to the secondary patient support device 20a and / or if the secondary patient support device 20a does not include the UWB transceiver 188.

[0177] In addition to determining the relative positions of the UWB transceivers 154, 170, 188, and / or 104, the controller 140 (FIG. 5) of the patient support device 20 can also be configured to determine the positions of UWB transceivers that are attached to other devices and / or incorporated into UWB tags attached to other devices. Such UWB tags may comprise any of the forms of tags disclosed in U.S. Patent Application No. 63 / 193,777, filed May 27, 2021, by the same applicant and entitled "System for Associating Medical Device Data" by inventors Thomas Deeds et al. The entire foregoing disclosure is incorporated herein by reference. Devices to which such tags can be attached or on which UWB transceivers can be mounted include, but are not limited to, one or more of the following: a secondary patient support device 20a, an infusion pump, a vital sign sensor, an exercise device, a heel care boot, an IV stand and / or pole, a ventilator, a DVT pump, a patient monitor (e.g., a saturation oxygen (SpO2) monitor, an EKG monitor, a vital sign monitor), a patient positioning device (e.g., a wedge, a turning device, a pump), an environmental sensor (e.g., temperature, air flow, light, humidity, pressure, altitude, sound / noise), a mattress 42, an incontinence pad, or one or more sensors adapted to detect patient incontinence, a Holter device adapted to monitor and record a patient's heartbeat signal, a patient ID tag or bracelet worn by a patient to identify the patient, a caregiver tag or ID bracelet worn by a caregiver to identify the caregiver, a patient temperature management device (or an associated device, e.g., one or more hoses, heat wraps, etc.), one or more mobility assistance devices that a patient may be expected to use, and / or other types of devices. Alternatively or additionally, any of these devices can be configured to include one or more built-in UWB transceivers adapted to communicate with the UWB transceiver 132 disposed on board the patient support device 20.

[0178] In some embodiments, after determining that the relative position of one or more of these devices is inside the corresponding spatial volume 152, the controller 140 transfers to the patient support device server 84 a message indicating that these devices (whose IDs are included in the message) are currently located in the same room as the patient support device 20. The patient support device server 84 can transfer this information to one or more of the electronic devices 98, thereby enabling an authenticated person to track the location of the pieces of equipment within the medical facility. Thus, in addition to determining the position of the UWB-enabled devices for the purpose of communicating data to / from those devices, the controller 140 can also determine the position of those devices for tracking purposes. Thus, the patient support device 20 can facilitate the tracking of a number of pieces of equipment used within the medical facility.

[0179] By including such tags on the device and / or a built-in type UWB transceiver, the controller 140 can automatically associate and automatically disassociate the patient support device 20 with any of these devices. This automatic association can be achieved by the device or tag moving inside a predetermined spatial volume (e.g., inside spatial volume 152b, 152c, or one of the other spatial volumes) defined for the patient support device 20, or inside a predetermined spatial volume defined for another structure (e.g., locator unit 60 and spatial volume 152a, and / or other spatial volumes). The automatic disassociation can be achieved by the device or tag moving outside the same predetermined spatial volume. Alternatively, the controller 140 can use a modified spatial volume - not necessarily limited, but for example, a larger spatial volume - when automatically determining whether to disassociate one or more of these devices or tags from the patient support device 20. In other words, if a device or tag is determined to be located inside a particular spatial volume (e.g., inside spatial volume 152b or 152c) (and any additional association conditions are met if present), and the controller 140 associates that tag or device with the patient support device 20, then later, when the controller 140 determines whether to disassociate that device, it can increase the size of the spatial volume - and / or change one or more of its dimensions. By doing so, the spatial volume 152 has a certain hysteresis behavior, where the device or tag must be placed inside a smaller space to be associated with the patient support device 20, but can only be disassociated if it then moves outside a larger-sized spatial volume. In still other embodiments, one or more dimensions of the spatial volume are the same for both the purposes of association and disassociation.

[0180] Generally, the tags discussed herein include UWB transceivers that can communicate with each UWB transceiver 132 onboard the patient support device 20. This communication enables the controller 140 of the patient support device 20 to determine the distance between each UWB transceiver 132 and the tag. In addition to the positions of each transceiver 132 on the patient support device 20, by also knowing these distances, the controller 140 can determine the relative position of the tag with respect to the patient support device 20, including whether the tag is located inside or outside a particular volume of space 152.

[0181] In some embodiments, the UWB transceivers 104, 132, 154, 170, and 188 (FIG. 5) may operate in the same manner as, and may have any of the same functions as, the anchors and pseudo-anchors disclosed in U.S. Patent Application No. 63 / 193,777, filed May 27, 2021, by the same applicant and entitled "System for Associating Medical Device Data" by inventors Thomas Deeds et al. The entire disclosure of the foregoing is incorporated herein by reference. In some embodiments, the locator unit 60 may be configured to determine the position of a device (e.g., the departure detection sensor 100, the nurse call device 150) in any of the ways disclosed in U.S. Patent Application No. 63 / 132,514, filed December 31, 2020, by the same applicant and entitled "Patient Support Apparatus and Medical Device Networks" by inventors Alexander Bodurka et al., and in U.S. Patent Application No. 63 / 154,677, filed February 27, 2021, by the same applicant and entitled "System for Determining Patient Support Apparatus and Medical Device Location" by inventors Celso Pereira et al. The entire disclosure of the foregoing is incorporated herein by reference.

[0182] The display device 56 (FIG. 5) includes a display controller 192 and a display 194. The display device 56 is different from the other devices and / or tags discussed herein in that it need not include a UWB transceiver as may be found in these other devices and / or tags, for example. This is because the patient support device 20 is not configured to determine the position of the display device 56. Instead, the controller 140 of the patient support device 20 is configured to use the UWB transceiver 132 to determine the position of the locator unit 60 to which the display device 56 is coupled. If both the patient support device 20 (or a reference point thereon) and the locator unit 60 are not both disposed inside the spatial volume 152a, the controller 140 does not send the data to be displayed to the locator unit 60. If both the locator unit 60 and the patient support device 20 (or a reference point thereon) are disposed inside the spatial volume 152a, the controller 140 is configured to be able to send the data to be displayed on the coupled display device 56 by transferring the data to be displayed to the associated locator unit 60, whereupon the associated locator unit 60 transfers it to the display device 56 via the video port 120 and the video cable 110. In some embodiments, the controller 140 transfers the data to be displayed on the display device 56 to the associated locator unit 60 using a Bluetooth® transceiver 128. On the other hand, in other embodiments, it may use the UWB transceiver 132 or another type of transceiver. In at least some embodiments, transferring the data to be displayed on the display device 56 is to transfer the data from the patient support device 20 directly to the locator unit 60 and from there to the display device 56 without intervening other media.

[0183] Since the display device 56 does not necessarily include a UWB transceiver, the display device 56 may be a conventional television, computer monitor, or other conventional device capable of displaying a video signal transmitted over the video cable 110. Additionally, it is not essential for the display device 56 to execute any dedicated software application that authenticates communication with the coupled locator unit 60 and / or the patient support device 20. Instead, when the controller 140 determines that both the patient support device 20 (or a reference point thereon) and the locator unit 60 are inside the spatial volume 152a, the controller 140 need not execute any additional security protocol regarding the display device 56. In fact, it is not necessary for the controller 140 to communicate with the display device 56 other than transferring the data to be displayed to the associated locator unit 60. In this way, the display device 56 need not know anything about the locator unit 60 and / or the patient support device 20. It simply displays the video signal from the video cable 110 and thus does not require the patient support device 20 and / or the locator unit 60 and / or a software application dedicated to UWB communication.

[0184] Note that displaying data from an associated device on display device 52 and / or display device 56 is automatically performed by patient support device 20. That is, for example, when the user configures patient support device 20 to display data from secondary patient support device 20a on display 56, it automatically transfers this data to the associated display device 56. Similarly, when a patient wearing a UWB-tagged heart rate monitor enters a bay area of a hospital room equipped with display device 56 coupled to locator unit 60, controller 140 is configured to automatically start displaying the patient's heart rate information on that display device 56 as soon as patient support device 20 completes the following two association processes. Here, the two association processes are: (1) the association between patient support device 20 and locator unit 60 to which display device 56 is coupled, and (2) the association between patient support device 20 and the heart rate monitor. This way, the caregiver will be able to view the patient's heart rate data displayed on display device 56 within seconds after patient support device 20 is moved into the bay area. Further, the caregiver does not need to connect any cables, press any buttons, or perform any other actions to display the heart rate data on display device 56. Similarly, when patient support device 20 is moving outside the bay area, the display of the patient's data on display device 56 automatically ends. This automatic termination is performed after patient support device 20 moves outside the spatial volume 152a associated with locator unit 60 to which display device 56 is connected. When controller 140 exits outside this spatial volume 152a, it disassociates patient support device 20 from that locator unit 60 and the associated display device 56, and when this disassociation occurs, patient support device 20 stops transmitting data to be displayed on display device 56.

[0185] As another example of automatically displaying device data on a display, when a caregiver approaches the patient support device 20 while carrying a portable electronic device 98, for example, a smartphone or a tablet computer having a display, a UWB transceiver, and a suitable software application, the controller 140 is adapted to automatically initiate transferring the data to the portable electronic device 98 for display on its screen. In this way, a caregiver who brings his or her portable electronic device inside the spatial volume 152b (or other spatial volume defined for such a device 98) can automatically cause the patient's heart rate data (and / or other data, e.g., data from a secondary patient support device 20a, a departure detection sensor 100, and / or a nurse call device 150) to be displayed on his or her device. When the caregiver moves his or her portable electronic device 98 outside the spatial volume 152b, the controller 140 automatically releases the association between the patient support device 20 and the portable electronic device 98 and stops sending data to be displayed thereto, so the display of the patient's data is automatically stopped. Thereafter, when the caregiver moves toward the patient support device 20 of another patient and steps inside the spatial volume 152b of that patient support device, he or she can automatically view data from the medical devices associated with that patient displayed on his or her portable electronic device 98.

[0186] In some embodiments, the controller 140 may be configured to display data from a device associated with the patient support device 20 and / or to process data from an associated device in any of the ways disclosed in U.S. Patent Application No. 63 / 306279, filed on February 3, 2022, by the same applicant and entitled "Communication System for Patient Support Apparatuses" and invented by Madhu Sandeep Thota et al. The entire foregoing disclosure is incorporated herein by reference.

[0187] In some embodiments, the patient support device 20 is configurable by the user (e.g., via the control panel 54a) such that if information is transmitted to an associated display device 56, to a patient support device server 84, and / or to an EMR server 92, the patient support device 20 controls what information is transmitted. In this way, the user can command the patient support device 20 to transmit, for example, blood pressure readings, respiratory rate readings, and heart rate readings from a UWB-tagged vital sign sensor (which is associated with the patient support device 20) to the EMR server 92, but not transmit status data from a secondary patient support device 20a. As another example, the patient support device 20 is configurable by the user such that the controller 140 transmits data of the secondary patient support device 20 to the display device 56 and the patient support device server 84, but does not transmit any data from the departure detection sensor 100 to the associated display device 56.

[0188] The locator unit 60 is configured to send a message to the patient support device 20 indicating whether the display device 56 (Figs. 4-5) is coupled thereto via the video port 120. In such an embodiment, upon receiving a signal indicating that the display device 56 is coupled to the associated locator unit 60, the controller 140 of the patient support device 20 refers to the customized user settings and is configured to determine which data to send to the locator unit 60 for transfer to the display device 56 coupled to the video port 120 if it is to send data. It should be noted that when the patient support device 20 associates itself with a particular locator unit 60 having a display device 56 coupled to its video port 120, it is not necessary for the display device 56 to be disposed inside the spatial volume 152 for the controller 140 to send the data to be displayed on the display device 56. Instead, the controller 140 is configured to check only whether the locator unit 60 is associated with the patient support device 20. In such a case, the controller 140 may send data (depending on the user settings) to the locator unit 60 for transfer to the display device 56. If the locator unit 60 is not associated with the patient support device 20, the controller 140 does not send any data to the locator unit 60 for display on the display device 56.

[0189] If data is to be transmitted to the display device 56, in addition to enabling the user to customize which data is transmitted to the display device 56, the controller 140 is further configured to enable the user to customize which data is transmitted to different types of display devices 56. In this way, the controller 140 can be programmed such that the user can transmit a first data set to the display device 56 coupled to the associated locator unit 60 and can transmit a second data set different from the first data set to a different display. Here, the different displays include, for example, the display 52 of the patient support device 20 and / or, without limitation, other displays incorporated, for example, into a conventional smartphone, a laptop computer, a tablet computer, a smart TV and / or a smart monitor, either communicating with the patient support device server 84 and / or disposed inside the spatial volume 152, the spatial volume 152 being determined by one or more UWB transceivers coupled to the smart TV and / or smart monitor adapted to communicate with the UWB transceiver 132 of the patient support device 20, including other displays incorporated therein. In such an example, it will be understood that a conventional smartphone, laptop computer, tablet computer, or other type of display device is equipped with a software application that monitors UWB communication with the patient support device 20 and controls the display of data on the display (i.e., the screen) of the display device. This software application has one or more security features incorporated therein. The security features enable only an authenticated user to display this data on the display device, thereby preventing an unauthenticated user from viewing this data on their smartphone, laptop computer, tablet computer, etc.In some embodiments, the controller 140 is configured to execute a security check protocol with the display device to authenticate the display device before sending data for display thereon to the display device.

[0190] The patient support device 20 may include one or more screens that can be displayed on the display 52. By means of such screens, it becomes possible for the user to customize data from the associated devices shown on the display 52 and / or the display device 56. In addition, the patient support device 20 is configured to enable the user to change the format and / or layout in which the selected data is displayed.

[0191] The secondary patient support device 20a, the departure detection sensor 100, the nurse call device 150, and / or other UWB - equipped devices have been described herein as communicating data directly to the associated patient support device 20. However, it should be understood that any of these devices (the secondary patient support device 20a, the departure detection sensor 100, the nurse call device 150, and / or other UWB - equipped devices) may alternatively or additionally communicate such data directly to the locator unit 60 associated with them (or associated with the patient support device 20 with which they are associated). In such embodiments, the patient support device 20 need not function as a conduit for communicating information from these devices to the communication consent 64 and / or the display device 56.

[0192] While the foregoing description first suggests that the controller 140 first determines whether to associate the patient support device 20 with one or more devices, it should be understood that the process of association and / or disassociation can alternatively, partially, and / or additionally be performed by the patient support device server 84. In such an embodiment, the controller 140 transfers information to the patient support device server 84 such that the server 84 can determine whether to associate a particular device with a particular patient support device 20. In such an embodiment, the server 84 sends back to the patient support device 20 a message communicating to the patient support device 20 which devices it should be associated with and which devices it should not be associated with.

[0193] In some embodiments, the server 84 is configured to associate or not associate a device with a particular patient. The server 84 makes this determination of patient association and / or non - association by storing in memory data that associates an identifier of a particular device (e.g., the identifier 178 of the departure detection sensor, the identifier 166 of the nurse call device, the identifier 190 of the secondary patient support device, etc.) - an identifier that is sent by that device to the patient support device 20 and then transferred by the patient support device 20 to the server 84 via the network transceiver 96 - with the identifier 130 of a particular patient support device. To associate a particular device with a particular patient, the patient support server 84 uses the location identifier 122 it received from the particular patient support device 20 to determine the location of the room of that particular patient support device 20. From this room location, the server 84 receives data identifying a particular patient associated with a particular room (or bay within the room) from a conventional ADT (Admission, Discharge, and Tracking) server or other server coupled to the network 80. And the server 84 can then associate a particular device (associated with a particular patient support device 20 within that room) with the identifier of a particular patient because it knows the room (or bay) of the patient support device 20, the specific ID of the device associated with that particular patient support device 20, and the identifier of the patient associated with the particular room (or bay). After associating a device with a particular patient, the server 84 can automatically retrieve data from the medical record of the particular patient stored in the EMR server 92 and / or can automatically send data from a particular device to the medical record of the particular patient stored in the EMR server 92.

[0194] FIG. 5 shows a single departure detection sensor 100, a single nurse call device 150, and a single secondary patient support device 20a, but it should be understood that this is for illustrative purposes only. A plurality of departure detection sensors 100, nurse call devices 150, secondary patient support devices 20a, and / or a plurality of other types of devices, and / or any combination of these devices, can be used for a particular patient. Further, the controller 140 of the patient support device 20 is adapted to determine the position of those devices relative to the spatial volumes 152b, 152c, etc., and, if they are disposed inside the corresponding spatial volume 152, automatically associate them with the patient support device 20, make their data available for display, transfer their data to the patient support device server 84, and / or take other actions.

[0195] In some embodiments, the controller 140 is adapted to automatically associate itself with one or more of the devices disclosed in U.S. Patent Application No. 63 / 154,677, filed Feb. 27, 2021, of the same applicant, entitled "System for Determining Patient Support Apparatus and Medical Device Location," by inventors Celso Pereira et al. The entire foregoing disclosure is incorporated herein by reference. The patient support device 20 is additionally or alternatively configurable by a user to automatically display any of the data from these other types of devices on either the display 52 and / or an associated display device 56 when these devices are associated with the patient support device 20.

[0196] Figures 8 and 9 illustrate an example of a nurse call device 150 that can be coupled to a secondary patient support device 20a or other structure. FIG. 8 shows a nurse call device 150 coupled to an armrest 200 of a secondary patient support device 20a. In some embodiments, the nurse call device 150 includes an adhesive coupled to one or more of its sides such that it can be adhesively attached to the secondary patient support device 20a (or other structure), and alternatively or additionally, the nurse call device 150 may include one or more fixtures, and / or the nurse call device 150 may include one or more hooks, joints, clamps, surface fastener mechanisms, or other structures that enable it to be temporarily or permanently affixed to the secondary patient support device 20a (or other device).

[0197] FIG. 9 shows an example of a nurse call button 160. When depressed, the controller 156 is adapted to send a nurse call signal to the patient support device 20, and in turn the patient support device 20 transfers that signal to the communication consent 64 (either directly via cable 66 or indirectly through locator unit 60). The nurse call device 150 includes a pull tab 202 as shown in FIG. 9. In some embodiments, the pull tab 202 is designed to be pulled out from the nurse call device 150 prior to use. The tab 202 is disposed inside the device 150 such that one or more batteries stored therein are not in electrical contact with the electrical components of the nurse call device 150, and thus their depletion does not begin until the pull tab 202 is removed from the device 150. The tab 202 thus aids in preserving the life of any internal batteries until the device 150 is actually put into use.

[0198] The nurse call device 150 can be a disposable device that is adapted for use only as long as its internal battery lasts, as long as a single patient stays in the healthcare facility, or for some other defined period. In some embodiments, the nurse call device 150 can be attached to or incorporated into a chain, strap, or other structure that can be coupled to or included in a bracelet or necklace worn by the patient. In this way, the nurse call device 150 moves with the patient, and the patient can call a nurse regardless of whether he or she is currently supported on either the patient support device 20 or 20a.

[0199] When the nurse call device 150 is intended to be worn by a patient, the controller 140 can utilize a larger spatial volume 152 than it does for a nurse call device 150 that is attached to a device (e.g., a secondary patient support device 20a). The larger spatial volume 152 can be used to prevent disassociation when the patient enters an adjacent dressing room or moves outside the spatial volume 152b where the secondary patient support device 20a is being used. In fact, in some embodiments where the nurse call device 150 is adapted to be worn by a specific patient, the controller 140 may be configured not to use the spatial volume 152 to automatically disassociate the device from the patient support device 20. Instead, the controller 140 can be adapted to maintain the association (established by the proximity field transceivers 144 and 158) as long as the nurse call device 150 lasts and / or until the nurse call device 150 is moved inside the association field 168 of a different patient support device 20.

[0200] Figures 4 and 5 show a patient support device 20 adapted to automatically monitor the position of the departure detection sensor 100, a nurse call device 150, and a secondary patient support device 20a. However, it should be understood that this is merely an example of a device that can be adapted such that the patient support device 20 automatically monitors its position and / or is automatically associated and / or dissociated. For example, in some embodiments, the patient support device 20 can be modified to monitor only the position of the departure detection sensor 100 and not the position of the nurse call device 150 and / or the secondary patient support device 20a. As another example, other embodiments of the patient support device 20 can be configured to monitor the positions of the nurse call devices 150, one or more vital sign sensors, and the locator unit 60, but not the position of the departure detection sensor 100 and / or the secondary patient support device 20a. The patient support device 20 can be further modified to monitor the positions of other devices and / or combinations of devices.

[0201] It should be understood that the frequency at which the controller 140 repeatedly determines the relative positions of the departure detection sensor 100, the nurse call device 150, the secondary patient support device 20a, the locator unit 60, and / or other devices 156 can vary depending on the embodiment. In some embodiments, this occurs multiple times per second. In other embodiments, this occurs at a frequency lower than once per second. In yet other embodiments, the frequency at which the controller 140 determines the relative position of the device with respect to the patient support device 20 can vary depending on the device, the current position of the patient support device 20, the movement state of the patient support device 20 (i.e., whether it is moving or stationary), the brake state of the patient support device 20 (i.e., whether the brake is on or off), and / or one or more other factors.

[0202] The controller 140 is configured to determine where to send data for transfer to an adjacent communication consent 64 using the associated state of the locator unit 60 and the patient support device 20, and to determine which locator unit 60 will receive data issued from that communication consent 64 (see FIGS. 5 and 6). Accordingly, the associated locator unit 60 is the locator unit 60 to which the patient support device 20 sends the voice signal of that patient (and / or a departure detection alert from either the departure detection system 136 or the departure detection sensor 100) for transfer to the nurse call system 70. It is also the locator unit 60 to which the controller 140 sends a television command when a patient on board the patient support device 20 activates one or more of the television control units 50l - 50r. Similarly, it is also the locator unit 60 to which the controller 140 sends a light command when a patient on board the patient support device 20 activates one or more of the reading lamp or room lamp control units 50s or 50t. The locator unit 60 with which the patient support device 20 associates itself is also the locator unit 60 to which the patient support device 20 receives an audio signal from its on-board speaker and directs the audio signal to that speaker (and / or to the nurse call device 150). Such an audio signal may correspond to a voice signal from a nurse in a remote location transferred by the nurse call system 70 to the corresponding communication consent 64, or such an audio signal may correspond to a television audio signal directed from the television 72 to the communication consent 64 by one or more conductors 68.

[0203] It should be understood that some of the devices that the patient support device 20 can be configured to automatically monitor its position are devices that can be associated with and / or disassociate from the patient support device 20 in a different way than the departure detection sensor 100 and / or the nurse call device 150. That is, the controller 140 can be configured to automatically associate some devices with the patient support device 20 when they move inside the spatial volumes 152b, 153c, and / or other spatial volumes, rather than associating them via the proximity field transceiver 144. The controller 140 can be configured to automatically disassociate these devices from the patient support device 20 when their devices move outside the spatial volumes 152b, 153c, and / or other spatial volumes (which can have an expanded or hysteresis type of modification). Alternatively, the controller 140 can be configured to associate the patient support device 20 with some devices in both ways (via the proximity field transceiver 144 and spatial volume monitoring).

[0204] It will be understood that manually associating the departure detection sensor 100, the nurse call device 150, and / or other devices with the patient support device 20 can be performed in other ways in addition to using the proximity field transceiver 144. For example, one way includes incorporating a barcode scanner adapted to read barcodes attached to the device into the patient support device 20. When the barcode is moved within the detection range of the scanner, the scanner automatically reads the barcode and associates the device with the patient support device 20 using the identification information encoded therein.

[0205] In some embodiments, when the patient support device 20 and / or the server 84 associates a device with a particular patient support device 20, the controller 140 and / or the server 84 is configured to inform (via the electronic device 98) the healthcare provider that the device is associated with the particular patient support device 20 and / or the particular patient assigned to that patient support device 20. By doing so, data from the device can be associated with a particular patient, room location, and / or the patient support device 20. Thus, the patient support device 20 can be configured to transfer data from the associated medical device to the server 84 after the device is associated with the patient support device 20. Such data can then be automatically transferred by the server 84 to the EMR server 92 for entry into the corresponding patient's electronic medical record. In this way, when the controller 140 associates a device with the patient support device 20, data from the device can be automatically stored in the particular patient's electronic medical record without the caregiver having to associate the device with either the patient and / or the patient support device 20 assigned to that patient. In other words, the controller 140 automatically determines that the device is located inside the volume 152, so the caregiver does not have to take any manual steps to ensure that data from the device is transferred to the appropriate corresponding patient's electronic medical record, because the patient support device 20, together with the server 84, automatically determines the correct patient associated with the medical device.

[0206] In any of the embodiments disclosed herein, server 84 may be configured to additionally execute a caregiver assistance software application of the type described in the following patent applications of the same applicant, namely, in U.S. Patent Application No. 62 / 826,978, filed Mar. 29, 2019, entitled "Patient Care System" by inventors Thomas Durlach et al., in U.S. Patent Application No. 16 / 832,760, filed Mar. 27, 2020, entitled "Patient Care System" by inventors Thomas Durlach et al., and / or in PCT / US2020 / 039587, filed Jun. 25, 2020, entitled "Caregiver Assistance System" by inventors Thomas Durlach et al., and may be configured to cause a caregiver to further execute a caregiver assistance software application of the type described therein. The entire foregoing disclosure is incorporated herein by reference. That is, server 84 may be configured to share any of the information shared with the electronic devices disclosed in these above patent applications with one or more electronic devices 98. Thus, for example, server 84 may not only share the location of the patient support devices 20 (and any devices that may be associated therewith) with electronic device 98, but server 84 may also transfer to device 98 patient vital sign data, infusion pump data, status data of primary and / or secondary patient support devices (e.g., current siderail position, bed exit state, brake state, motion lockout state, height state, scale data), data from the exit detection sensor 100, data from the nurse call device 150, and / or caregiver round data (e.g., the time when the last round for a particular patient was performed, the time when the next round is scheduled).

[0207] In some embodiments, the locator unit 60 may store and include additional information that is shared with the patient support device 20 when the patient support device 20 is associated with the locator unit 60. Such additional information may include location information that identifies the relative position of the locator unit 60 with respect to one or more locator units 60 disposed in the vicinity. Additionally or alternatively, the locator unit 60 may include information regarding the thickness and / or material of the wall 62 to which it is attached. Here, such information provides an indication to the patient support device 20 of the amount of attenuation that a UWB signal may experience as it travels through the wall. Additionally or alternatively, the locator unit 60 may include information that identifies its approximate location within the medical facility (e.g., room 400, bay A302 of the room, corridor X, maintenance area Y, radiology department, emergency department, etc.) and / or information that identifies the more specific location of the locator unit 60 within the medical facility (a set of X, Y, Z coordinates of a reference system that includes all or a portion of the medical facility, height on the wall 62, distances from one or more landmarks and / or architectural features within the medical facility, and / or other more specific information). In some embodiments, the patient support device 20 is adapted to utilize this information to determine its location within the medical facility and / or to determine whether it is disposed on the same side of the wall 62 as a particular locator unit 60. In some embodiments, the patient support device 20 and / or the locator unit 60 comprises any of the same structures, functions, and / or features as the patient support device and / or wall unit disclosed in U.S. Patent Application No. 63 / 245,245, filed September 17, 2021, by the same applicant and entitled "System for Locating Patient Support Apparatuses" by inventors Kirby Neihouser et al. The entire foregoing disclosure is hereby incorporated by reference into this specification.

[0208] One of ordinary skill in the art will appreciate that the use of the term "transceiver" throughout this specification is not intended to be limited to devices in which the transmitter and receiver are necessarily located within the same housing or share the same circuitry. Instead, the term "transceiver" is used broadly herein to refer to both structures in which circuitry is shared between a transmitter and a receiver and transmitter-receivers in which the transmitter and receiver do not share circuitry and / or a common housing. Thus, the term "transceiver" refers to any device having a transmitter element and a receiver element, regardless of whether those two elements are a common entity, separate entities, or have some overlap in their structures.

[0209] In addition to what has already been described herein, various additional modifications and changes can be made to the above-described embodiments. The present disclosure is presented for purposes of illustration and should not be construed as an exhaustive description of all embodiments or as limiting the scope of the claims to the specific elements described or depicted in connection with these embodiments. For example, any individual element of the above-described embodiments can be replaced, without limitation, by an alternative element that provides substantially similar functionality or performs adequately. This includes, for example, currently known alternative elements that may be known to one of ordinary skill in the art as of the present time and alternative elements that may be developed in the future and recognized as alternatives by one of ordinary skill in the art upon their development. References to elements in the claims in the singular, such as the use of the articles "a," "an," "the," or "said," should not be construed as limiting the element to the singular.

Claims

1. A patient support device, the patient support device comprising: A support surface adapted to support a patient; A first transceiver coupled to a first position of the patient support device; A second transceiver coupled to a second position of the patient support device; A third transceiver coupled to a third position of the patient support device; A controller adapted to determine the position of the departure detection sensor relative to the patient support device using radio frequency (RF) communication between the first transceiver, the second transceiver, and the third transceiver and the departure detection sensor, the controller being further adapted to receive a departure detection alert signal from the departure detection sensor, determine whether the departure detection sensor is disposed inside or outside a spatial volume, and, if the departure detection sensor is disposed inside the spatial volume, transmit a departure detection alert to an off-board recipient in response to receiving the departure detection alert signal from the departure detection sensor.

2. The patient support device further comprises a nurse call system interface adapted to communicate with a nurse call system outlet integrated into a wall of a healthcare facility, the nurse call system outlet comprising a plurality of electrical pins, and the controller is adapted to transmit the departure detection alert to the off-board recipient by changing an electrical state of a pin of the nurse call system outlet. The patient support device according to claim 1.

3. The nurse call system interface of claim 2, wherein the nurse call system interface is adapted to communicate with the nurse call system outlet by wireless or wired communication.

4. The controller of claim 1, further adapted to determine whether a second patient support device is disposed inside or outside a second spatial volume using radio frequency (RF) communication between the first transceiver, the second transceiver, and the third transceiver and the second patient support device.

5. The patient support device of claim 1, wherein the departure detection sensor includes a pressure sensing pad adapted to be disposed under the patient. **Claim 6** The patient support device according to claim 5, wherein the pressure sensing pad is adapted to be removable from the patient support device and to be disposed on the support surface of a second patient support device. **Claim 7** The patient support device according to claim 1, wherein the first transceiver, the second transceiver, and the third transceiver are all ultra-wideband wireless transceivers. **Claim 8** The patient support device according to claim 7, further comprising a memory for storing the first position, the second position, and the third position of the first transceiver, the second transceiver, and the third transceiver, respectively. **Claim 9** The patient support device according to claim 8, wherein the controller is further adapted to determine whether the departure detection sensor is disposed inside or outside the spatial volume using the stored positions of the first transceiver, the second transceiver, and the third transceiver. **Claim 10** The patient support device according to claim 1, wherein the controller is further adapted not to transmit the departure detection alert to the off-board recipient in response to receipt of the departure detection alert signal from the departure detection sensor when the departure detection sensor is disposed outside the spatial volume. **Claim 11** The patient support device according to claim 1, wherein the controller is further adapted to determine the position of the patient support device relative to the fixed locator using RF communication between the first transceiver, the second transceiver, and the third transceiver and the fixed locator. **Claim 12** The patient support device according to claim 11, wherein the controller is adapted to receive an identifier from the fixed locator to determine whether the patient support device is disposed inside a threshold distance relative to the fixed locator, and, if the patient support device is disposed inside the threshold distance, to transfer the identifier of the fixed locator to a server. **Claim 13** The off-board recipient according to claim 12, wherein the fixed locator is included when the patient support device is disposed inside the threshold distance. **Claim 14** The patient support device further comprises a microphone disposed onboard the patient support device, the microphone being adapted to convert the voice of the patient into an audio signal, and the controller being further adapted to transmit the audio signal to the fixed locator if the fixed locator is disposed inside the threshold distance and not to transmit the audio signal to the fixed locator if the fixed locator is disposed outside the threshold distance, the patient support device according to claim 13.

15. The off-board recipient is a nurse call system consent integrated into a wall of a medical facility, the patient support device according to claim 1.

16. The controller is adapted to determine a second position of the object relative to the patient support device using radio frequency (RF) communication between the first transceiver, the second transceiver, and the third transceiver and the object, to determine whether the object is disposed inside or outside a second volume of space, to determine a third position of the patient support device relative to the fixed locator using RF communication between the first transceiver, the second transceiver, and the third transceiver and the fixed locator, to determine whether the patient support device and the fixed locator are disposed inside a threshold distance of each other, and to transfer position information indicating the position of the object within the medical facility to a server if the object is disposed inside the second volume of space and the fixed locator and the patient support device are disposed inside the threshold distance of each other, the patient support device according to claim 1.

17. The controller is further adapted to use the position of the departure detection sensor and the second position of the object to determine whether the departure detection sensor is coupled to the object, the patient support device according to claim 16.

18. The position information indicates that the object and the patient support device are disposed within a common room of the medical facility, the patient support device according to claim 17.

19. The controller is further adapted to determine the position of the nurse call device relative to the patient support device using wireless radio frequency (RF) communication between the first transceiver, the second transceiver, and the third transceiver, and tags coupled to the nurse call device. The controller is further adapted to receive a nurse call signal from the nurse call device to determine whether the nurse call device is disposed inside or outside the spatial volume, and, if the nurse call device is disposed inside the spatial volume, to transmit the nurse call signal to a nurse call system in response to receiving the nurse call signal from the nurse call device. The patient support device according to claim 1.

20. The patient support device further comprises a nurse call system interface adapted to communicate with a nurse call system consent integrated into a wall of a medical facility. The nurse call system consent comprises a plurality of electrical pins, and the controller is adapted to transmit the nurse call signal to the nurse call system by changing an electrical state of a pin of the nurse call system consent. The patient support device according to claim 19.

21. The patient support device according to claim 19 further comprises a first near field transceiver adapted to read data from a second near field transceiver coupled to the tag.

22. The controller is further adapted to automatically associate the tag with the patient support device when the tag is disposed close enough to the patient support device for the first near field transceiver and the second near field transceiver to communicate with each other. The patient support device according to claim 21.

23. The controller is further adapted to disassociate the tag from the patient support device when the tag is moved outside the spatial volume. The patient support device according to claim 22.

24. The patient support device according to claim 23, wherein the controller is further adapted not to transmit the nurse call signal to the nurse call system in response to receiving the nurse call signal from the nurse call device when the tag is unassociated from the patient support device.

25. The patient support device according to claim 23, further comprising a display, wherein the controller is adapted to display a first message on the display when the controller associates the tag with the patient support device, and to display a second message on the display when the controller disassociates the tag from the patient support device.

26. The patient support device according to claim 25, further comprising a fourth transceiver adapted to communicate with a fifth transceiver coupled to the tag, wherein the controller is further adapted to: (a) transfer an audio signal received from the tag to a nurse call system consent via the fourth transceiver when the tag is associated with the patient support device; and (b) not transfer an audio signal from the tag to the nurse call system consent when the tag is unassociated from the patient support device.

27. The patient support device according to claim 21, further comprising a plurality of side rails and a footboard, wherein the first proximity field transceiver is integrated with one of the side rails or the footboard.

28. A patient support device, comprising: a support surface adapted to support a patient; a display; a first transceiver coupled to a first position of the patient support device; a second transceiver coupled to a second position of the patient support device; a third transceiver coupled to a third position of the patient support device; A controller, adapted to determine the position of the second patient support device relative to the patient support device using radio frequency (RF) communication between the first transceiver, the second transceiver, and the third transceiver and the second patient support device, and a controller, and the controller is adapted to receive data from the second patient support device to determine whether the second patient support device is disposed inside or outside the spatial volume, and when the second patient support device is disposed inside the spatial volume, the patient support device is further adapted to perform at least one of transferring the data to an off-board recipient or displaying the data on the display.

29. The controller is adapted to receive an ID from the second patient support device, to determine and verify whether the ID conforms to a specification, and when the ID conforms to the specification and the second patient support device is disposed inside the spatial volume, to transfer the data to the off-board recipient, and when the ID does not conform to the specification, not to transfer the data to the off-board recipient. The patient support device according to claim 28, further adapted.

30. The data includes a departure detection alert signal. The patient support device according to claim 28.

31. The patient support device is a bed, and the second patient support device is a recliner. The patient support device according to claim 28.

32. The patient support device further includes a nurse call system interface adapted to communicate with a nurse call system consent integrated into a wall of a medical facility. The nurse call consent includes a plurality of electrical pins, and the controller is adapted to respond to the departure detection alert signal by changing an electrical state of a pin of the nurse call system consent. The patient support device according to claim 30.

33. The nurse call system interface is adapted to communicate with the nurse call system consent by wireless communication or wired communication. The patient support device according to claim 32.

34. The patient support device according to claim 28, wherein the data comprises at least one of a brake state of the second patient support device, a locked state of a lock of the second patient support device, an angle of a component of the second patient support device, an error message, or an occupancy detection signal.

35. The patient support device according to claim 30, wherein the second patient support device comprises a departure detection sensor including a pressure sensing pad adapted to be disposed under the patient.

36. The patient support device according to claim 35, wherein the pressure sensing pad is adapted to be removable from the second patient support device and to be disposed on a support surface of another patient support device.

37. The patient support device according to claim 28, wherein the first transceiver, the second transceiver, and the third transceiver are all ultra-wideband wireless transceivers.

38. The patient support device according to claim 37, further comprising a memory in which the first position, the second position, and the third position of the first transceiver, the second transceiver, and the third transceiver are stored, respectively.

39. The patient support device according to claim 28, wherein the controller is further adapted to determine a position of the patient support device relative to the fixed locator using RF communication between the first transceiver, the second transceiver, and the third transceiver and the fixed locator.

40. The patient support device according to claim 39, wherein the controller is adapted to receive an identifier from the fixed locator, to determine whether the patient support device is disposed inside a threshold distance relative to the fixed locator, and to transfer the identifier of the fixed locator to a server when the patient support device is disposed inside the threshold distance.

41. The patient support device according to claim 40, wherein the off-board recipient comprises the fixed locator when the patient support device is disposed inside the threshold distance.

42. The patient support device further comprises a microphone disposed onboard the patient support device, the microphone being adapted to convert the voice of the patient into an audio signal, and the controller is further adapted to transmit the audio signal to the fixed locator if the fixed locator is disposed inside the threshold distance and not to transmit the audio signal to the fixed locator if the fixed locator is disposed outside the threshold distance, the patient support device according to claim 41.

43. The off-board recipient is a nurse call system consent integrated into a wall of a medical facility, the patient support device according to claim 28.

44. The patient support device further comprises a network transceiver adapted to communicate with a computer network of a medical facility in which the patient support device is disposed, and the off-board recipient is a server communicating with the computer network, the patient support device according to claim 28.

45. The first transceiver, the second transceiver, and the third transceiver are ultra-wideband wireless transceivers and are adapted to communicate with a fourth ultra-wideband wireless transceiver coupled to the second patient support device, the patient support device according to claim 28.

46. The fourth ultra-wideband wireless transceiver is incorporated into a removable tag coupled to the second patient support device, the patient support device according to claim 45.

47. The controller is further adapted to both transfer the data to the off-board recipient and display the data on the display if the second patient support device is disposed inside the spatial volume, the patient support device according to claim 28.

48. The controller, using radio frequency (RF) communication between the first transceiver, the second transceiver, and the third transceiver and a fixed locator, is further adapted to determine a second position of the patient support device relative to the fixed locator of the patient support device, to determine whether the patient support device and the fixed locator are located inside a threshold distance from each other, and, if both the second patient support device is disposed inside the spatial volume and the fixed locator and the patient support device are disposed inside the threshold distance from each other, to transfer position information indicating the position of the second patient support device within the medical facility to a server, the patient support device according to claim 28.

49. The patient support device according to claim 48, wherein the position information indicates that the patient support device and the second patient support device are disposed within a common room of the medical facility.

50. The controller of the patient support device according to claim 48 is further adapted not to transfer the position information to the server if either or both of (a) the second patient support device is disposed outside the spatial volume or (b) the fixed locator and the patient support device are not disposed inside the threshold distance from each other.

51. The controller is further adapted to use radio frequency (RF) communication between the first transceiver, the second transceiver, and the third transceiver and a tag coupled to a nurse call device to determine the position of the nurse call device relative to the patient support device, the controller being adapted to receive a nurse call signal from the nurse call device, to determine whether the nurse call device is disposed inside or outside the spatial volume, and, if the nurse call device is disposed inside the spatial volume, to transmit the nurse call signal to a nurse call system in response to receiving the nurse call signal from the nurse call device, the patient support device according to claim 28.

52. The patient support device further comprises a nurse call system interface adapted to communicate with a nurse call system receptacle integrated into a wall of a healthcare facility, the nurse call system receptacle comprising a plurality of electrical pins, and the controller being adapted to transmit the nurse call signal to the nurse call system by changing an electrical state of a pin of the nurse call system receptacle. The patient support device according to claim 51.

53. The patient support device according to claim 52, further comprising a first near field transceiver adapted to read data from a second near field transceiver coupled to the tag.

54. The controller of the patient support device according to claim 53 is further adapted to automatically associate the tag with the patient support device when the tag is positioned close enough to the patient support device for the first and second near field transceivers to communicate with each other.

55. The controller of the patient support device according to claim 54 is further adapted to disassociate the tag from the patient support device when the tag is moved outside the spatial volume.

56. The controller of the patient support device according to claim 55 is further adapted not to transmit the nurse call signal to the nurse call system in response to receiving the nurse call signal from the nurse call device when the tag is disassociated from the patient support device.

57. The controller of the patient support device according to claim 55 is adapted to display a first message on the display when the controller associates the tag with the patient support device and to display a second message on the display when the controller disassociates the tag from the patient support device.

58. The patient support device further comprises a fourth transceiver adapted to communicate with a fifth transceiver coupled to the tag, and the controller is further adapted to (a) transfer an audio signal received from the tag to a nurse call system consent via the fourth transceiver when the tag is associated with the patient support device, and (b) not transfer the audio signal of the tag to the nurse call system consent when the tag is disassociated from the patient support device. The patient support device according to claim 57.

59. A patient support device, wherein the patient support device comprises a support surface adapted to support a patient, a first transceiver coupled to a first position of the patient support device, a second transceiver coupled to a second position of the patient support device, a third transceiver coupled to a third position of the patient support device, a controller adapted to determine a first position of the object relative to the patient support device using radio frequency (RF) communication between the first transceiver, the second transceiver, and the third transceiver and the object, and the controller is adapted to determine whether the object is located inside or outside a first volume of space, determine a second position of the patient support device relative to the fixed locator using RF communication between the first transceiver, the second transceiver, and the third transceiver and the fixed locator, determine a distance between the patient support device and the fixed locator, and transfer position information indicating the position of the object within the medical facility to a server when both the object is located inside the first volume of space and the fixed locator and the patient support device are located within a threshold distance of each other. The patient support device is further adapted.

60. The patient support device according to claim 59, wherein the position information includes a first ID received from the object and a second ID received from the fixed locator.

61. The patient support device according to claim 60, wherein the second ID corresponds to a specific position of the fixed locator within the medical facility.

62. The controller is further adapted such that it does not transfer the position information to the server if either or both of (a) the object is located outside the first volume of space, or (b) the fixed locator and the patient support device are not located within the threshold distance of each other, for the patient support device according to claim 59.

63. The patient support device according to claim 59, wherein the first volume of space is defined in a fixed relationship with respect to the patient support device.

64. The patient support device according to claim 59, wherein the first volume of space is defined in a fixed relationship with respect to the fixed locator.

65. The patient support device according to claim 59, wherein the object is a mobile object adapted to assist in the treatment of the patient.

66. The patient support device according to claim 59, wherein the object is a recliner.

67. The patient support device according to claim 59, wherein the position information suggests that the object and the patient support device are located within a common room of the medical facility.

68. The patient support device according to claim 59, wherein the controller is further adapted to receive data from the object.

69. The patient support device according to claim 68, wherein the object is a second patient support device and the data includes a departure detection alert signal.

70. The patient support device further comprises a nurse call system interface adapted to communicate with a nurse call system consent integrated into a wall of the medical facility, the nurse call consent comprising a plurality of electrical pins, and the controller is adapted to respond to the departure detection alert signal by changing an electrical state of a pin of the nurse call system consent, for the patient support device according to claim 69.

71. The patient support device according to claim 70, wherein the nurse call system interface is adapted to communicate with the nurse call consent by wireless communication or wired communication.

72. The patient support device according to claim 69, wherein the data includes at least one of a brake state of the second patient support device, a locked state of a lock of the second patient support device, an angle of a component of the second patient support device, an error message, or an occupancy detection signal.

73. The patient support device according to claim 69, wherein the second patient support device includes a departure detection sensor including a pressure sensing pad adapted to be disposed under the patient.

74. The patient support device according to claim 73, wherein the pressure sensing pad is adapted to be removable from the second patient support device and disposed on a support surface of another patient support device.

75. The patient support device according to claim 59, wherein the first transceiver, the second transceiver, and the third transceiver are all ultra-wideband wireless transceivers.

76. The patient support device according to claim 75, further comprising a memory storing the first position, the second position, and the third position of each of the first transceiver, the second transceiver, and the third transceiver.

77. The controller is further adapted to determine a position of the nurse call device relative to the patient support device using radio frequency (RF) communication between the first transceiver, the second transceiver, and the third transceiver and a tag coupled to the nurse call device, the controller is adapted to determine whether the nurse call device is disposed inside or outside the first volume of space so as to receive a nurse call signal from the nurse call device, and when the nurse call device is disposed inside the first volume of space, the controller is further adapted to transmit the nurse call signal to a nurse call system in response to receiving the nurse call signal from the nurse call device. The patient support device according to claim 59.

78. The patient support device further comprises a nurse call system interface adapted to communicate with a nurse call system receptacle integrated into a wall of the medical facility, the nurse call system receptacle comprising a plurality of electrical pins, and the controller being adapted to transmit the nurse call signal to the nurse call system by changing an electrical state of a pin of the nurse call system receptacle, the patient support device according to claim 77.

79. The patient support device according to claim 78, further comprising a first near field transceiver adapted to read data from a second near field transceiver coupled to the tag.

80. The controller of the patient support device according to claim 79, further adapted to automatically associate the tag with the patient support device when the tag is positioned close enough to the patient support device for the first and second near field transceivers to communicate with each other.

81. The controller of the patient support device according to claim 80, further adapted to disassociate the tag from the patient support device when the tag is moved outside the first volume of space.

82. The controller of the patient support device according to claim 81, further adapted not to transmit the nurse call signal to the nurse call system in response to receiving the nurse call signal from the nurse call device when the tag is disassociated from the patient support device.

83. The patient support device according to claim 81, further comprising a display, and the controller being adapted to display a first message on the display when the controller associates the tag with the patient support device, and to display a second message on the display when the controller disassociates the tag from the patient support device.

84. The patient support device further comprises a fourth transceiver adapted to communicate with a fifth transceiver coupled to the tag, and the controller is further adapted to: (a) when the tag is associated with the patient support device, transfer an audio signal received from the tag via the fourth transceiver to a nurse call system consent; and (b) when the tag is disassociated from the patient support device, not transfer an audio signal from the tag to the nurse call system consent. The patient support device according to claim 81.

85. A patient support device, wherein the patient support device comprises: a support surface adapted to support a patient; a display; a plurality of ultra-wideband wireless transceivers; a proximity field transceiver; a controller adapted to automatically associate an object with the patient support device when the object is disposed within the communication range of the proximity field transceiver. The controller is adapted to determine the position of the object relative to the patient support device using radio frequency (RF) communication between the plurality of ultra-wideband wireless transceivers and the object, to determine whether the object is disposed inside or outside a spatial volume, to automatically disassociate the object from the patient support device when the object is disposed outside the spatial volume, not to transfer data received from the object to an off-board recipient when the object is disassociated from the patient support device, and when the object is associated with the patient support device, to further perform at least one of: (a) transferring data received from the object to an off-board recipient; or (b) displaying data received from the object on the display. The patient support device.

86. The patient support device according to claim 85, wherein the object is a nurse call device and the data includes a nurse call signal.

87. The patient support device further comprises a nurse call system interface adapted to communicate with a nurse call system outlet integrated into a wall of a healthcare facility, the nurse call system outlet comprising a plurality of electrical pins, and the controller being adapted to transmit the nurse call signal to the nurse call system by changing an electrical state of a pin of the nurse call system outlet. The patient support device according to claim 86.

88. The patient support device further comprises a Bluetooth® transceiver, and the controller is further adapted to: (a) when the nurse call device is associated with the patient support device, receive an audio signal from the nurse call device via the Bluetooth® transceiver and transfer the audio signal to the nurse call system outlet via the nurse call system interface; and (b) when the nurse call device is disassociate from the patient support device, not transfer any audio signal from the nurse call device to the nurse call system outlet. The patient support device according to claim 86.

89. The patient support device further comprises a display, and the controller is adapted to display a first message on the display when the controller associates the object with the patient support device, and to display a second message on the display when the controller disassociates the object from the patient support device. The patient support device according to claim 85.

90. The object is a device adapted to improve a mobility level of the patient. The patient support device according to claim 85.

91. The object is a recliner. The patient support device according to claim 90.

92. The object is a mobile tag adapted to be attached to a second patient support device. The patient support device according to claim 85.

93. The patient support device according to claim 92, wherein the mobile tag comprises an adhesive adapted such that the mobile tag can be releasably attached to the second patient support device.

94. The patient support device according to claim 92, wherein the mobile tag comprises a button adapted to be depressed by the patient, and the mobile tag is adapted to transmit a nurse call signal to the patient support device in response to the button being depressed.

95. The patient support device according to claim 85, wherein the object comprises a departure detection sensor.

96. The patient support device according to claim 95, wherein the departure detection sensor is a pressure sensing pad adapted to be disposed under the patient.

97. The patient support device according to claim 96, wherein the pressure sensing pad is adapted to be removable from under the patient and is disposed on a different patient support device.

98. The patient support device according to claim 85, wherein the controller is further adapted to determine a second position of the patient support device relative to the fixed locator using RF communication between the plurality of ultra-wideband wireless transceivers and the fixed locator, and to associate the fixed locator with the patient support device if the patient support device and the fixed locator are disposed within a threshold distance of each other, and to disassociate the fixed locator from the patient support device if the patient support device and the fixed locator are not both disposed within the threshold distance of each other.

99. The patient support device according to claim 98, wherein the controller is further adapted to (a) transfer position information indicating the position of the object within the medical facility to the server if the object is associated with the patient support device, and (b) not transfer the position information to the server if the object is disassociated from the patient support device.

100. The patient support device according to claim 99, wherein the position information includes a first ID received from the object and a second ID received from the fixed locator.

101. The patient support device according to claim 100, wherein the second ID corresponds to a specific position of the fixed locator within the medical facility.

Images