Patent Grant
10886024
Some hospital beds are configured to communicate information to a nurse call system. Such nurse call systems typically have a computer at a remote nurse's station with a display on which information concerning bed status is shown. One or more nurse call buttons are sometimes provided on a hospital bed, such as on one or more siderails of the bed and/or on a handheld pendant that is coupled to the bed. A patient may press one of the nurse call buttons to request to speak with a nurse. A nurse at the remote nurse's station and the patient may communicate with each other over a two-way communications link which includes audio circuitry, such as a microphone and a speaker included on the bed or mounted on a room wall near the bed. In addition, the nurse at the remote nurse's station may use the computer to establish a two-way communications link between the remote nurse's station and a caregiver at some other location in a healthcare facility and/or between the patient placing the nurse call and a caregiver at some other location in the healthcare facility.
Hospital beds that connect to nurse call systems, typically do so via a wired connection established by a nurse call cable that extends between the bed and an interface unit having a jack mounted on a wall or headwall unit in the hospital room in which the bed is situated. Typically, a power cord from the bed also plugs into a power outlet on the wall or headwall unit. Before the bed is moved from one location to another in a healthcare facility, the nurse call cable and the power cord need to be unplugged. Caregivers sometimes forget to unplug the nurse call cable resulting in damage to the nurse call cable when the bed is wheeled away from the wall. When the bed arrives at its new location, the caregivers need to remember to plug in both the power cord and the nurse call cable. When the nurse call cable is unplugged, bed status data is no longer communicated to the nurse call system. In addition, many prior art nurse call systems are configured as local area networks (LAN's) which require the installation in the healthcare facility of the associated network infrastructure, such as the bed interface units and the wiring from the bed interface units to the computer at the remote nurse's station.
Support surfaces such as, for example, mattresses may be placed upon decks of the hospital beds. The support surfaces often include an array of different functions used to care and/or treat various ailments and/or conditions of a patient. Hospital beds are often configured to receive support surfaces from different manufactures and/or different models from the same manufacture. As a result, a healthcare facility may include numerous different combinations of hospital bed models and support surface models.
The present invention may comprise a system, apparatus and/or method that may have one or more of the following features and/or steps, which alone or in any combination may comprise patentable subject matter:
A surface association system for a healthcare facility may comprise a plurality of beds. The system may further comprise a computing device and a plurality of support surfaces to be placed upon beds of the plurality of beds. The computing device may associate a support surface of the plurality of support surfaces with a bed of the plurality of beds. The computing device may make the association based upon status data received from the plurality of beds and the plurality of support surfaces.
In one embodiment, the bed to be associated may initiate a surface association request. The computing device, in response to the surface association request initiated by the bed, may request performance of one or more actions on the support surface to be associated with the bed in order to identify the support surface. The support surface to be associated may provide the computing device with data indicative of the one or more actions in response to the one or more actions being performed.
The system may further comprise a plurality of location transmitters. Each location transmitter may transmit a location identifier signal comprising a location identifier indicative of a location of the respective location transmitter. Each of the plurality of beds may include a location receiver to receive the location identifier. The computing device may associate the support surface of the plurality of support surfaces with the bed of the plurality of beds based upon the location identifier of the bed. Each of the plurality of surfaces may also include a location receiver to receive the location identifier. The computing device may associate the bed of the plurality of beds with the support surface of the plurality of support surfaces based upon the location identifier of the support surface.
A method for associating a bed of a plurality of beds and a support surface of a plurality of support surfaces is also disclosed. The method may comprise receiving data from the plurality of beds and the plurality of support surfaces. The method also may comprise determining that a support surface of the plurality of support surfaces is placed upon a bed of the plurality of beds based upon the data received from the plurality of beds and the plurality of support surfaces, and updating data to associate the support surface and the bed. The method may further determine that the support surface is placed upon the bed based upon a location identifier of the support surface and a location identifier of the bed.
In one embodiment, the method may request a user to perform one or more actions upon the bed to identify the bed of the plurality of beds. The method may then determine that the support surface of the plurality of support surfaces is placed upon the bed of the plurality of beds based upon data that indicates the user performed the one or more actions upon the bed.
In another embodiment, the method may request a user to perform one or more actions upon the support surface to identify the support surface. The method may then determine that the support surface of the plurality of support surfaces is placed upon the bed of the plurality of beds based upon data that indicates the user performed the one or more actions upon the support surface.
Embodiments of the method may further comprise receiving location identifiers for the plurality of beds and the plurality of support surfaces. The method may then determine that the support surface is placed upon the bed based upon at least a portion of the location identifiers received for the plurality of beds and the plurality of support surfaces.
Other embodiments may include transmitting location identifiers from location transmitters located throughout a healthcare facility to the plurality of beds and/or the plurality of support surfaces. The method may then determining that the support surface is placed upon the bed based upon at least a portion of the location identifiers received for the plurality of beds and/or the plurality of support surfaces.
A bed for use in a healthcare facility comprising a plurality of location transmitters and a network is also described. The bed may comprise a deck to receive a support surface and a location receiver to receive a location identifier signal from a location transmitter of the plurality of location transmitters of the healthcare facility. The bed may have a network interface to establish a communications link between the bed and the network. The bed may also have a communications interface to establish a communications link between the bed and a support surface that has been placed into position upon the deck of the bed. The bed may also have a user interface having a plurality of user inputs to control operation of the bed. The user interface may also have one or more user inputs to initiate a request to associate a support surface to the bed. The user interface may also request one or more actions be performed upon the support surface and the one or more actions may selected to identify the support surface from a plurality of support surfaces.
The bed may also have control circuitry to control operation of the bed and to control the transfer of data between the bed and the network of the healthcare facility. The control circuitry may control operation of the support surface based upon data received from the network via the network interface by providing control words to the support surfaces via the communications interface. The control circuitry may initiate a request to associate a support surface to the bed in response to one or more actions performed upon the bed. In one embodiment, the one or more actions may include actions beyond activating user inputs of the user interface.
A support surface is described for use in a healthcare facility comprising a plurality of location transmitters and a network. The support surface may be placed upon a deck of a bed and may include a location receiver to receive a location identifier signal from a location transmitter of the plurality of location transmitters. The support surface may include a communications interface and a network interface. The communications interface may establish a communications link between the support surface and the bed upon which the support surface has been placed. The network work interface may establish a communications link between the support surface and the network.
The support surface may also comprise a user interface. The user interface may include a plurality of user inputs to control operation of the support surface. The user interface may also include one or more user inputs to initiate a request to associate a support surface to the bed. The user interface may requests that one or more actions be performed upon the bed to be associated with the support surface to identify the bed from the plurality of beds of the healthcare facility.
The support surface may include control circuitry to control operation of the support surface and to control the transfer of data between the bed and the network of the healthcare facility. The control circuitry may control operation of the bed based upon data received from the network via the network interface by providing control words to the bed via the communications interface. The control circuitry may initiate a request to associate the support surface to the bed in response to one or more actions performed upon the support surface and/or bed. The one or more actions may includes actions beyond activating user inputs of the user interface.
A machine readable medium for associating beds and supports surfaces is also described herein. The machine readable medium may comprise a plurality of instructions, that in response to being executed, result in a device providing an interface to receive user input that identifies a bed of a healthcare facility and a location of the healthcare facility, and updating data to reflect the bed being associated with the location of the healthcare facility in response to receiving user input that requests the bed be associated with the location. The plurality of instructions may further result in the device providing the interface to further receive user input that identifies a support surface of the healthcare facility, and updating data to further reflect the support surface being associated with the bed in response to receiving user input that requests the support surface be associated with the bed. The instructions may also result in the device providing the interface to receive user input that identifies a previously associated bed, surface and location, and updating data to reflect that the previously associated bed, surface and location are no longer associated in response to user input that requests the bed, surface and location be unassociated.
Additional features, which alone or in combination with any other feature(s), such as those listed above, may comprise patentable subject matter and will become apparent to those skilled in the art upon consideration of the following detailed description of various embodiments exemplifying the best mode of carrying out the embodiments as presently perceived.
The detailed description particularly refers to the accompanying figures, in which:
Embodiments contemplated by this disclosure may be implemented in hardware, firmware, software, or any combination thereof. Embodiments disclosed herein may also be implemented as instructions stored on a machine-readable medium, which may be read and executed by one or more processors. A machine-readable medium may include any mechanism for storing information in a form readable by a machine (e.g., a computing device). For example, a machine-readable medium may include read only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; flash memory devices; and others.
The following description describes techniques for associating a support surface such as a mattress to a hospital bed and/or associating a hospital bed with a support surface. Such techniques may be incorporated into a surface association system of a healthcare facility such as the healthcare facility shown diagrammatically in
Each computing device 4, in one embodiment, provides the network 10 and devices connected thereto with one or more healthcare support services. Such healthcare support services may include, for example, a nurse call system, an admission-discharge-tracking (ADT) system, an electronic medical records (EMR) system, a workflow system, a medical records archiving system, a surface association system, and the like. As explained in greater detail below, one or more of the computing devices 104 includes software and/or firmware that, in response to being executed, results in one or more computing devices 104 providing the healthcare facility with a surface association service. The surface association service associates beds 22 with surfaces 46 and/or surfaces 46 with beds 22 based upon data received from the beds 22 and/or surfaces 46. Furthermore, the surface association service in some embodiments associates the beds 22 and/or surfaces 46 with locations in the healthcare facility based upon the data received from the beds 22 and/or surfaces 46.
As shown, the healthcare facility comprises several rooms 20 with bed stations 24. The bed stations 24 include power outlets, audio stations, and various other equipment and/or ports for connecting equipment used to care for a patient lying in a corresponding bed 22. While
Referring now to
The support surface 46, when placed into position, rests upon the support deck 47 of hospital bed 22. A particular hospital bed 22 may be compatible with multiple types of supports surfaces 46 such as, for example, air mattresses including therapy mattresses of various types (e.g. lateral rotation mattresses, alternating pressure mattresses, low air loss mattresses, and so on), and other specialty mattresses that each provide various features to support patient care. The support surface 46 may comprise a control unit in a housing that couples to a footboard of a bed 22, or to some other portion of the bed 22. Such surface control units typically have pumps, compressors, blowers, valves, manifolds, and the like, as well as electrical control circuitry and user interfaces to provide control signals to the various other components housed in the control unit. Other support surfaces 46 may integrate some or all of the components of such a control unit into a portion of the surface, such as a foot section of the surface.
The hospital bed 22 further has a label 76 with bed ID data 78 thereon as shown in
In connection with the wireless communication capability provided by the network interfaces of bed 22 and/or support surface 46 of
Successive presses of enabled button 70 enable and suspend a Care Alert template for bed 22. Successive presses of housekeeping button 72 makes a housekeeping request and cancels the housekeeping request. However, in order for presses of buttons 70, 72 to be effective, key button 61 is first be pressed and held for a predetermined period of time, such as one second. Once button 261 has been pressed for the predetermined period of time, then buttons 70, 72 may be pressed within another predetermined period of time, such as 20 seconds, to change the state of the associated feature of buttons 70, 72. This control scheme for buttons 61, 70, 72 prevents inadvertent presses of buttons 70, 72 from changing the associated state of the associated feature. In some embodiments, Care Alerts enabled indicator 71 of Care Alerts enable button 70 shines green when the Care Alert template associated with bed 22 is enabled, blinks or flashes green when the Care Alert template associated with bed 22 is suspended, and is turned off when no Care Alert template is set up for bed 22. In some embodiments, the housekeeping indicator 73 shines green when a housekeeping request has been made by a press of housekeeping button 72 and is turned off when no housekeeping request has been made or after a housekeeping request has been canceled. The housekeeping request may be canceled before or after a staff member actually cleans the bed and/or room.
Referring now to
Referring now to
As shown in
The location transmitter 332 transmits a location identifier (ID) signal from which the location of the transmitter 332 may be determined. In one embodiment, the location transmitter 332 transmits a number such as, for example, a serial number which the has been uniquely assigned to the location transmitter 332. In such an embodiment, a user or technician may supply a surface association service of a computing device 4 with the location and location IDs for each location transmitter 332. As such, the surface association computing device 4 may maintain associations or mappings of location IDs to locations in the healthcare facility.
In another embodiment, the location transmitter 332 may be assigned a location ID that comprises data in addition to or instead of a serial number or an otherwise unique number. In particular, a location transmitter 332 may be assigned a location ID that comprises information regarding the location of the location transmitter 332. For example, the location ID may comprise one or more identifying location fields such as a floor, a room, a care unit, a zone, bed station, and/or some other location field. A technician or user may configure the location transmitters 332 with appropriate values for such fields thus resulting in a location ID for the location transmitter 332 from which the location of the location transmitter 332 may be determined. For example, a transmitter 332 may be configured to transmit an location ID with a value of “520” in the room field and a value of “2” in the zone field to indicate the transmitter 332 is located in zone 2 of room 520. It should be appreciated that the location ID may be implemented with numerous different fields, and the selection of appropriate fields for the location ID is influenced by the healthcare facility. For example, if the healthcare facility has unique room numbers for every room in the healthcare facility, then a room field is sufficient to uniquely identify the room in which the transmitter 332 is located. In contrast, for other healthcare facilities a room number may be insufficient and additional information (e.g. building number, wing, etc.) may be provided in order to uniquely specify the locations of the location transmitter 332 is located. Accordingly, the location ID of transmitter 332 is programmed at the discretion of the end users in some embodiments.
In one embodiment, the location transmitters 332 comprise stand-alone units that are not operatively coupled to the network 10 of the healthcare facility. Such an embodiment enables location transmitters 332 to be placed throughout a healthcare facility regardless of whether the healthcare facility has network infrastructure in the vicinity of a particular location transmitter 332. In other embodiments, one of more of the location transmitters 332 may be coupled to the network 10. In such an embodiment, a location identifier may be assigned to each location transmitters 332 via the network 10. In some embodiments, stand-alone transmitters 332 are battery powered, whereas network connected transmitters 332 receive power from the network (e.g. power of LAN). However, it should be appreciated that other means of powering the transmitters 332 are contemplated such as connecting to the main power of the healthcare facility.
Furthermore, various wireless technologies may be used to implement the location transmitters 332. In some embodiments, the location transmitters 332 transmit the location IDs using infrared signals. In other embodiments, the location transmitters 332 transmit the location IDs using radio frequency (RF) signals. Similarly, various wireless technologies may be used to implement the location ID receivers 342. Moreover, the location receivers 342 and location transmitters 332 may support multiple wireless technologies to increase the compatibility of the receivers 342 of the beds 22′ with the transmitters 332. In other words, the receivers 342 may be implemented to receive multiple types of location signals thus supporting reception of location signals from different types of location transmitters 332. Similarly, the location transmitters 332 may be implemented to transmit multiple types of location signals thus supporting transmission of location IDs to different types of locations receivers 342.
The bed 22′ includes a user interface 50 coupled to bed control circuitry 344 to enable a user such as a patient or a caregiver to control the operation of various functions 346 of the bed 22′ as shown diagrammatically in
The support surface 46′ includes a user interface 360 coupled to surface control circuitry 364 to enable a user such as a patient or a caregiver to control the operation of various functions 366 of the support surface 46′ as shown in
In one embodiment, the communication interfaces 348, 368 are coupled to one another via a cable to establish a physical communications link between the bed 22′ and the support surface 46′. In another embodiment, the communication interfaces 348, 368 comprise electrical contacts, interconnection ports, or the like which when the support surface 46′ is positioned upon bed 22′ results in the electrical contacts, interconnection ports or the like to engage each other to establish a physical communications link between the bed 22′ and the support surface 46′. In yet another embodiment, the communication interface 348, 368 establish a wireless communications link between the bed 22′ and the support surface 46′. Such a wireless communications link may be implemented using various wireless technologies such as infrared transceivers and/or RF transceivers. Moreover, the communication interfaces 348, 368 may support wirelessly communicating between the bed 22′ and the support surface 46′ via a capacitive and/or inductive coupling established between the communication interfaces 348, 368.
The network interface 340 of the bed 22′ provides a wired and/or wireless communications link to the network 10 of a healthcare facility. The bed control circuitry 344 may monitor the bed functions 346 and maintain status data regarding the bed 22′ and its support surface 46′. Using the network interface 340, the bed control circuitry 344 may communicate a location ID received via location receiver 342, bed status data of the bed functions 446 and/or surface status data of the surface 46′ to the network 10 and the computing devices 4 coupled thereto. In one embodiment, the network interface 340 may be incorporated into the bed control circuitry 344. In another embodiment, the network interface 340 is provided by a separate networking card, wireless communications module (WCM), and/or a network interface unit (NIU).
In one embodiment, the network interface 340 transmits data between the bed 22′ and the network 10 using a networking protocol such as, for example, the IEEE 802.11 (Wi-Fi) wireless communication protocols and/or the IEEE 802.3 (Ethernet) protocol. In an embodiment supporting a wired connection to the network 10, the network interface 340 includes a communications port to which a networking cable such as, for example, a coaxial cable, a twisted pair cable, or and fibre optic cable may be coupled in order to establish a wired communication link between the bed 22′ and the network 10. In one embodiment, the communications port comprises an RJ-45 port, but other ports such as BNC connector ports are contemplated. In some wireless embodiments, the network interface 340 comprises a wireless transceiver to transfer data in accordance with the wireless protocol such as IEEE 802.11a, 802.11b, 802.11g, and/or 802.11n.
The network interface 370 of the support surface 46″ couples the support surface 46″ to the network 10 of the healthcare facility. The network interface 370 may support establishing a wired and/or wireless communications link between the support surface 46″ and the network 10. As shown, the support surface control circuitry 364 may use the network interface 370 to transfer support surface ID data, location ID data, support surface support data, control words and possibly other data between the network 10 and the support surface 46″. Further, the network interface 370 may be implemented in a similar fashion to the network interface 340 of bed 22″ which was described above in regard to
Thus, the control circuitry 344, 364 of the bed 22″ and the support surface 46″ may respectively control the operation of bed functions 346 and support surface functions 366 based upon inputs received via the user interfaces 50, 360. Furthermore, the control circuitry 344, 364 may respectively control the operation of the bed functions 346 and support surface functions 366 based upon control words from the network 10 via the network interface 340, 370. Moreover, the bed 22″ may receive information from the support surface 46″ such as support surface ID data, location ID data, support surface status data, and control via network interfaces 340, 370. Likewise, the support surface may receive information from the bed 22″ such as bed ID data, location ID data, bed status data, and control words via network interfaces 340, 370. While not shown, the bed 22″ and support surface 46″ may optionally comprise communication interfaces similar to the communication interfaces 348, 368 of
Referring now to
Thus, the control circuitry 344, 364 of the bed 22′″ and the support surface 46′″ may respectively control the operation of bed functions 346 and support surface functions 366 based upon inputs received via the user interfaces 50, 360. Furthermore, the support surface control circuitry 364 may control the operation of the support surface functions 366 based upon control words from the network 10 via the network interface 370. Moreover, the bed 22′″ and support surface 46′″ may use communication interfaces 348, 368 in order to transfer information such as support surface ID data, bed ID data, location ID data, support surface status data, bed status data, and control words between the bed 22′″ and support surface 46′″. Further, it should be appreciated that operation of the bed 22′″ may be controlled via the network 10 by transferring a control word to the network interface 370 of the support surface 46′″ associated with the bed 22′″. The support surface control circuitry 364 may in turn transfer the control word to the bed 22′″ via the communication interfaces 348, 368.
In some embodiments, location receivers 342, 362 may be omitted from the beds 22 and/or the surfaces 46 of
As another technique, the beds 22 and/or surfaces 46 may obtain a location ID from a computing device 4 of the healthcare facility which determines the location of the beds 22 and/or surfaces 46 based upon network parameters associated with the beds 22 and/or surfaces 46 and provides the beds 22 and/or surfaces 46 with the appropriate location ID via network interfaces 348 and/or 368. In particular, the strength of signals or lack of signals between an access point 12 and beds 22 and/or surfaces 46 of the healthcare facility may be indicative of the position of such beds 22 and/or surfaces 46 in relation to the access point 12. Based upon data received from the beds 22, surfaces 46 and/or access points 12 regarding the strength of such signals or lack of such signals, the computer device 4 may determine the position of the beds and/or surfaces 46 in the healthcare facility using triangulation and/or other positioning techniques. The computer device 4 may also determine location of the bed 22″ and/or surface 46 based upon other network parameters of the bed 22″ and/or surface 46″ such as network routing paths of communications between the bed/surface and the computing device 4.
As yet another technique for providing beds 22 and/or surfaces 46 with a location ID, an administrator may associate beds 22 and/or the surfaces 46 with locations using an interface of a computing device 4, the beds 22, and/or surfaces 46 such as the interfaces shown in
Referring now to the interface shown in
The interface further includes an unassigned beds control 1004 that identifies beds 22 of the healthcare facility that have yet to be associated with a location of the healthcare facility. The unassigned beds control 1004 may be implemented in a manner similar to the locations control 1002. In particular, the unassigned beds control 1004 may comprise a simple list control that provides a list of bed identifiers which each identify a bed 22 of the healthcare facility that has yet to be associated with a location of the healthcare facility. In another embodiment, the unassigned beds control 1004 comprises a table control in which each row of the table corresponds to an unassigned bed of the healthcare facility and the columns provide information that identifies the respective bed such as, for example, serial number, MAC address, IP address, bed identifier, etc.
The interface of
As shown in
The user interface also includes an unassociate control 1014. The unassociate control 1014 may include a button control or other control which when clicked, pressed, or otherwise activated causes the computing device 4 to unassociate the bed or beds selected by the beds and associated locations control 1012 from their respective locations. In particular, the beds and associated location control 1012 may enable a user to select one or more beds, and the unassociate control 1014 upon being activated may unassociate the selected beds from their respective locations.
The user interface of
The interface of
Referring now to
In one embodiment, data transmitted by the network interface 340 between the bed 22 and the network 10 includes bed status data as well as surface status data. One example of bed status data and surface status data is given in Tables 1-3 which are described below.
As shown in Table 1, brake status data indicates whether a brake for one or more of the casters of the hospital bed is set or not set; surface prevent mode data indicates whether a surface of the hospital bed is or is not activated to control air bladder pressures in a manner which attempts to inhibit formation of pressure ulcers (e.g., bed sores); bed exit armed status to indicate whether or not bed exit system which detects whether or not a patient has exited the bed is armed or not armed; bed low position data to indicate whether or not an upper frame which carries a mattress support deck is in its lowest position relative to a base frame of the bed; head rail position data to indicate whether head end siderails are up or down; and foot rail position data to indicate whether foot end siderails are up or down.
As shown in Table 2, patient position mode data indicates whether or not a patient position monitoring system of the hospital bed is in move mode in which patient movement of a first amount is considered an alarm condition, a start egress mode in which patient movement of a second amount greater than the first amount is considered an alarm condition, or patient exit mode in which patient movement of a third amount greater than the second amount (including movement off of the bed) is considered an alarm condition, and the patient position mode data also indicates whether or not an alarm condition, of the selected mode, has occurred. As also shown in Table 2, siderail position data indicates whether each of a right head rail, a left head rail, a right foot rail, and a left foot rail are in up or down positions; motor lockout data indicates whether or not a head motor which is operable to raise and lower a head section of the mattress support deck is locked out; whether or not a knee motor which is operable to raise and lower a thigh section (or seat section) of the mattress support deck is locked out; whether or not one or more high-low motors which are operable to raise and lower an upper frame carrying the mattress support deck relative to a base frame of the bed is locked out; and whether or not all of the motors just described are locked out.
Table 2 further shows surface status data such as whether or not a left turn assist mode or right turn assist mode to turn the patient, on a one-time basis, in one direction or another is active; whether or not a max inflate mode to inflate air bladders of the mattress to a preprogrammed maximum pressure to harden the surface for patient transfer, patient ingress or egress, or CPR is active; whether or not a heel suspension mode to deflate bladders in a heel region of the patient to attempt to inhibit formation of pressure ulcers on the patient's heels is active; whether or not a rotation mode to cyclically rotate the patient to the left and to the right is active; whether or not an optirest mode to sequentially inflate head zone bladders, seat zone bladders, and foot zone bladders is active; whether or not percussion to pulsate one or more air bladders of the surface is active; and whether or not vibration to vibrate one or more air bladders of the surface is active. In other embodiments, the surface status data may indicate whether or not a low air loss mode in which air is expelled from openings in the mattress to cool the patient and/or to transport moisture away from the patient is active and/or whether or not an alternating pressure mode in which sets of alternating bladders are each inflated and deflated at different times so that different portions of the patient are primarily supported by different bladders sets at different times is active.
As further shown in Table 2, housekeeping data indicates whether or not a housekeeping switch or button on the bed is active (e.g., has been pressed) to request that a staff member clean the hospital bed and/or the associated room; battery status data indicates whether or not a battery is present on the bed, whether or not the battery is disconnected from bed circuitry, whether or not the battery needs to be charged, and whether or not the battery is fully charged; AC power data indicates whether or not AC power is being received by the bed; service data indicates whether or not the bed needs to serviced; CPR mode data indicates whether or not a CPR release handle of the bed, which causes a head section of the mattress support deck to be lowered rapidly so that CPR can be quickly administered to a patient, has been activated; nurse call data indicates whether or not a nurse call switch to request to speak with a caregiver has been activated; and Care Alert data indicates whether or not a Care Alert switch to enable and disable any Care Alerts set up in templates at a remote computer has been activated.
As shown in Table 3, bed type data indicates the type of bed (e.g., manufacturer and model number) transmitting the data; bed location data indicates the location in the healthcare facility at which the bed is located such as the location ID received from the location transmitters 332; head angle data indicates an angle at which the head section of the mattress support deck is elevated relative to another portion of the bed, such as an upper frame or another deck section, or relative to horizontal or vertical; switch installed data indicates whether or not one or more brake switches, siderail foot switches, siderail head switches, and/or nurse call switches are installed on the bed; information availability data to indicate whether or not bed exit data and/or bed low position data is available from the bed; and patient weight data indicates the weight of a patient as measured by a weigh scale system of the hospital bed.
Any of the bed status data in any of the three above tables may be transmitted to the network 10 via network interface 340 and/or network interface 370. The data may then used by one or more healthcare support services provided by the computing devices 4 such as a nurse call service which operates to contact assigned caregivers when certain conditions on the bed 22 or surface 46 are detected, a workflow service to assign tasks to caregivers and other staff members, a locating-and-tracking service to track the whereabouts of people and/or equipment, an admission discharge and transfer (ADT) service, a bed assignment service, a surface/bed association service and the like.
It will be appreciated that a hospital will have multiple beds, similar to bed 22, multiple support surfaces 46 associated with the various beds 22, and multiple location transmitters 332 positioned throughout the healthcare facility. Each location transmitter 332 may be mounted at a particular location in a hospital. For example, one or more location transmitters 332 may be located in various patient rooms such as, for example, at the bed stations 24. Each bed 22, support surface 46, and location transmitter 332 in one embodiment is assigned a unique identification (ID) code, such as a serial number. In some embodiments, one or more of the computing devices 4 comprises software to associate bed ID data with location ID data to keep track of which bed 22 is located in each room of the hospital and convey this information to caregivers. Moreover, one or more of the computing devices 4 comprises software to associated surface ID data with bed ID data to keep track of which support surface 46 is associated with which bed 22.
Beds 22 and surfaces 46 may each have power cords (not shown) that are plugged into electrical outlets in hospital rooms during normal use of the beds 22 regardless of whether the beds 22 communicate with other devices in the associated network via wired or wireless connections. In some embodiments, beds 22 may have a socket into which a power cord of an accessory such a surface 46 may be plugged. According to this disclosure, when the power cords of beds 22 and/or surfaces 46 are unplugged, which usually happens when the bed is to be moved from one location in a healthcare facility to another, the associated Care Alert templates are automatically disabled. Thus, even if the bed 22 and/or surface 46 is still able to communicate wirelessly during transit from one location to another, the associated nurse call system does not initiate any communications with the wireless communication devices carried by the caregivers. Such alarm notifications are not generally needed because other caregivers should be accompanying the bed 22 during transit. Before the automatic disabling of the Care Alert templates, a slight delay period, such as 10 or 20 seconds, may be required to elapse so that, if the bed's power plug was unplugged inadvertently, there is time to plug the bed back in before the Care Alert templates are disabled.
In the case of beds 22 and/or surfaces 46 that communicate wirelessly, data is sent from the respective wireless transmitters to notify the associated nurse call system that the bed and/or surface has been unplugged. Such data may be transmitted after the above-mentioned delay period (i.e., the bed determines when the delay period has elapsed) or substantially immediately in response to the bed and/or surface being unplugged (i.e., the nurse call system determines when the delay period has elapsed). In the latter case, appropriate data is sent from the wireless transmitter if the bed and/or surface is plugged back in before the delay period elapses so that the nurse call system does not disable the Care Alert template.
Beds and/or surfaces having wireless communication circuitry may be powered by battery back-up power or by one or more capacitors for a period of time sufficient to permit the transmission of data indicating that the bed and/or surface has been unplugged (and, in some embodiments, for a return acknowledgment to be received by the bed and/or surface). Additionally or alternatively, the nurse call system may also conclude that the bed 22 and/or surface 46 has been unplugged and is in transit if a different wireless transceiver or receiver receives a signal from the bed 22 and/or surface 46, such as a wireless access point or a transceiver of an associated locating-and-tracking system, and proceed to automatically disable the Care Alert alarm notifications as a result.
Moreover, it should be appreciated that even beds 22 without a network interface 340 or a network interface 340 without wireless circuitry may still notify the associated nurse call system that the bed 22 has been unplugged using its associated support surface 46 to relay such information. In particular, the bed 22 may inform the support surface 46 via communication interfaces 348, 368 that the bed 22 has been unplugged and the support surface 46 may in turn send such information to the network 10 using its network interface 370. Likewise, it should be appreciated that even surfaces 436 without a network interface 370 or a network interface 370 without wireless circuitry may still notify the associated nurse call system that the surface 46 has been unplugged using its associated bed 22 to relay such information. In particular, the support surface 46 may inform the bed 22 via communication interfaces 348, 368 that the support surface 46 has been unplugged and the bed 22 may in turn send such information to the network 10 using its network interface 340.
In some embodiments, after the bed 22 and/or surface 46 reaches its new location and the associated power cord is plugged back in, a caregiver signals the nurse call system to re-enable the Care Alert templates for the particular bed. Caregivers may re-enable the Care Alert templates for the particular bed 22 by making appropriate entries on either an audio station in the room, a computer at the master nurse call station, or the wireless communication device carried by the caregiver. The re-enabling of the Care Alert template may be made by voice commands entered into the wireless communication device in some embodiments.
Because the nurse call system receives bed ID data, the particular Care Alert template associated with the bed 22 is known by the nurse call system. Thus, unless overridden by users of the nurse call system, the association between bed, patient, and assigned caregivers is maintained by the nurse call system even if the bed is moved to a new location. If one of the assigned caregivers does not re-enable the Care Alert template within a predetermined period of time after the nurse call system determines that the bed has been plugged back in (such determination being made in any of the ways described above for determining that the bed has been unplugged), then a reminder to re-enable the Care Alert template may be initiated by the nurse call system to the wireless communication devices carried by one or more of the assigned caregivers.
In alternative embodiments, the nurse call system may re-enable the Care Alert templates automatically after bed 22 and/or surface 46 has been moved and then plugged back in. Alternatively or additionally, the nurse call system may initiate a communication to the wireless communication devices of one or more assigned caregivers advising that the nurse call system will re-enable the Care Alert templates within a predetermined period of time unless receiving instructions not to do so. Alternatively or additionally, the nurse call system may initiate a communication to the wireless communication devices of one or more assigned caregivers with a notification that an assigned bed is now determined to be at a new location and the one or more caregivers should communicate via appropriate measures (entries on a nurse call computer, voice commands, entries on a user interface of a wireless communication device, etc.) to re-enable the associated Care Alert templates.
The data received from beds 22 and/or support surface 46 by the associated nurse call system may be provided to other systems of the hospital network. In one example, beds 22 having weigh scale systems transmit patient weight to a nurse call system which, in turn, transmits the patient weight data to an electronic medical records (EMR) system which, in turn, stores the weight information in the associated patient's record. The nurse call system may convert the data from one communication protocol into another communication protocol. Thus, patient weight data received by the nurse call system may be converted by the system into the Health Level 7 (HL7) protocol for transmission to the EMR system. In some embodiments, patient weight data is transmitted to the nurse call system only in response to a query initiated by a caregiver via entries on a nurse call computer, voice commands, entries on a user interface of a wireless communication device, etc. Such a system reduces extraneous data transmissions on the network for data, such as patient weight, of the type which does not vary much with time and which may be desired by caregivers only sporadically.
Bed status data from beds 22 and surface status data from surfaces 46 may be routed to different computers or to different software applications on the same computer. For example, some bed status data packets may be sent by beds 22 and used by a nurse call software application and other bed status data packets may be sent by beds 22 and used by some other software application, such as a workflow software application. Each of the data packets of bed status data may include a destination address, such an Internet Protocol (IP) address, of the computer for which the particular bed status data is destined. As previously mentioned different bed status data and/or surface status data may be destined for different software applications run on the same computer, in which case the IP address included in each packet of bed status data and/or surface status data may or may not have the same IP address depending upon whether or not the software applications on the same computer have been assigned different IP addresses. Alternatively or additionally, the bed status data and/or surface status data may be routed to different software application, be they on the same computer or different computers, based on the data type.
In addition, each of the data packets of bed status data include bed identification data, such as a serial number of the associated bed 22 and/or an IP address and/or a MAC address of the associated bed 22. Furthermore, if known, then each of the data packets of bed status data include location data, such as a room number or other location ID indicating the location of the associated bed 22 in the healthcare facility. In accordance with this disclosure, the IP address of each of beds 22 may be assigned in accordance with the Dynamic Host Configuration Protocol (DHCP). Likewise, each of the data packets of surface status data include surface identification data, such as a serial number of the associated surface 46 and/or an IP address and/or a MAC address of the surface 46. Furthermore, if known, then each of the data packets of surface status data include location data, such as a room number or other location ID indicating the location of the associated surface 46 in the healthcare facility. In accordance with this disclosure, the IP address of each of surfaces 46 may be assigned in accordance with the Dynamic Host Configuration Protocol (DHCP).
As mentioned above, one or more computing devices 4 may provide a surface association service that associates beds 22 and supports surfaces 46 to one another. Hospital beds 22 may support various makes and models of support surfaces 46. As explained in more detail below, a computing device 4 may send control messages to a bed 22 based upon the surface status data for the surface 46 of the bed 22 and/or bed status data of the bed 22. Similarly, a computing device 4 may send control messages to a support surface 46 based upon the surface status data for the surface 46 of the bed 22 and/or bed status data of the bed 22. The surface association service supports such activities by maintaining associations between beds 22 and the support surfaces 46 placed upon the decks 47 of the beds 22.
One embodiment of a surface association method implemented by a service association service of one or more computing devices 4 is shown in
As indicated at block 720, the computing device may receive a request to associate a bed 22 and surface 46 with one another. In one embodiment, the computing device 4 may receive the surface association request in response to a caregiver activating one or more inputs of the user interface 50 of the bed 22 and/or the user interface 360 of the surface 46. In some embodiments, the user interfaces 50, 360 may include a button, switch and/or other user input that, in response to being activated, initiates the surface association request. In another embodiment, the computing device 4 further supports beds 22 and/or surfaces 46 which were designed without surface association requests in mind and therefore do not provide a button, switch an/or other user input for initiating a surface association request. In such an embodiment, the computing device 4 may detect a surface association request based upon bed status data and/or surface status data received from the bed 22 and/or surface 46 indicating the occurrence of a predetermined sequence of actions which the computing device 4 recognizes as a surface association request.
For example, the predetermined sequence of actions for a surface association request may be defined as toggling the brake release on a bed 22 a threshold number (e.g. 3) or more times within a predetermined period (e.g. 2 seconds). However, it should be appreciated that the computing device 4 may define and therefore recognize just about any sequences of actions as an association request. Such actions may involve actuating the user interface 50, 460 and/or actuating mechanical aspects (e.g. raising/lowering siderails, toggling brakes, etc.) that do not involve the user interfaces 50, 360. Generally, the computing device 4 assigns an event to be detected a sequence of actions that is unlikely to occur in the normal course of operation of the bed 22 and/or surface 46 in order to reduce the likelihood of false or inadvertent requests. However, it should also be appreciated that inadvertent requests are generally not problematic as such inadvertent requests merely result in extra processing by the computing device 4 and re-association of the bed 22 and surface 46.
Moreover, the sequence of actions assigned to an event do not necessarily need to be unique. In other words, the computing device 4 may assign different events to the same sequence of actions. For example, the computing device 4 may associate the same sequence of actions to association requests, device identifications as explained below in regard to
At block 730, the computing device 4 attempts to associate beds 22 and surfaces 46 based upon the data received from each bed 22 and surface 46. In an embodiment, the computing device 4 may determine that a bed 22′ and surface 46′ (See,
For a bed 22″ and surface 46″ that each have a network interface (See,
In one embodiment, computing device 4 as indicated at block 730 may attempt to memorialize the determined association between the bed 22 and surface 46. For example, the computing device 4 may update a database to reflect the determined association between the bed 22 and surface 46. The computing device 4 in other embodiments may memorialize the determined association by updating data stored in memory of the computing device 4, requesting another computing device 4 to store the association between the bed 22 and surface 46, and/or storing the association in a non-volatile memory (e.g. hard drive, RAID drive, etc.) of the computing device 4.
As indicated at block 740, the computing device 4 may determine whether the attempted association was successful. The computing device 4 may be unable to associate a bed 22 and surface 46 for a number of reasons. For one, multiple beds 22 and/or surfaces 46 may be located sufficiently close to the same location transmitter 332 of the healthcare facility to result in the multiple beds 22 and/or surfaces 46 receiving the same location ID data. Thus, the computing device 4 in such circumstances may be unable to uniquely associate a single bed 22 with a single support surface 46 without further data to distinguish the multiple beds 22 and/or surfaces 46. However, it should also be appreciated that by careful positioning of the location transmitters 332 and tuning of the transfer range between the location transmitters 332 and location receivers 342, 362, the number of conflicts may be reduced to a very small number and/or practically eliminated for a given healthcare facility. As another example, the computing device 4 may experience one or more faults and/or errors such as, for example, disk read errors, network faults, database timeouts, etc. which prevent the computing device 4 from completing the requested association.
If the requested association was successful, the computing device 4 as indicated at 750 may provide the person requesting the association with an indication of the successful association. In one embodiment, the computing device 4 transmits a control message to the bed 22 and/or surface 46 which results in the user interface 50 of the bed 22 and/or the user interface 360 of the surface 46 to display the successful association. For example, a user interface 50, 360 in response to the received control message may display a textual message upon its display and/or may update the status of one or more LEDs of the user interface 50, 360 (e.g. turning on, turning off, blinking, and/or changing the illuminated color of one or more LEDs) to signal the success of the requested bed/surface association. Alternatively, or in addition to, the computing device 4 may send a message (e.g. audio message and/or text message) to a pager, PDA or other type of wireless communication device such as Vocera® handsets or telephone handsets that have bidirectional voice communication capability and that may have text messaging capability of a caregiver located near the bed 22 and surface 46 and/or an audio message to an audio station and/or text message of the bed station 24 near the location identified by the received location ID data.
Conversely, if the requested association was not successful, the computing device may provide the person requesting the association with an indication of the unsuccessful association of the bed and surface in a manner similar to block 750 as indicated at block 760. In one embodiment, if the requested association was not successful due to multiple beds 22 and/or surfaces 46 being identified for a single association, the computing device 4 may alert a user of the computing device 4 and/or the person who requested the association of the bed 22 and the surface 46 of the conflict so that they can manually resolve the conflict. For example, the user requesting the association may simply manually enter the bed ID data and surface ID data into the computing device 4 and/or relay such data to an operator of the computing device 4 for entry into the computing device 4 or may be instructed to perform a function on the bed (e.g. raise then lower siderail, unbrake then brake casters, etc.) to indicate the bed to which a surface is to be associated.
A technique to resolve such conflicts in an automated manner is incorporated in the surface association method presented in
As shown, the computing device 4 as indicated at block 810 may receive bed ID data and location ID data from beds 22 of the healthcare facility and may receive surface ID data and location ID data from support surfaces 46 of the healthcare facilities in a manner similar to block 710 above. As indicated at block 820, the computing device 4 may receive a request to associate a bed 22 and surface 46 with one another in a manner similar to block 720 above.
In response to receiving the surface association request, the computing device 4 may request that the caregiver perform a predetermined sequence of actions on the bed 22 and/or the surface 46 to identify the bed 22 and surface 46 to be associated with one another as indicated at block 830. The identifying sequence of actions in one embodiment is selected such that the sequence of actions is unlikely to otherwise occur during normal operation of the bed 22 or surface 46 to be associated. Thus, the computing device 4 may identify a bed 22 and/or surface 46 of a surface association request based upon receipt of status data that indicates the occurrence of the identifying sequence of actions.
At block 830, the computing device 4 may provide the caregiver with the request to perform the identifying actions using various mechanisms. The computing device 4 may transmit one or more control messages to a bed 22 or bed(s) 22 having the same location ID as the received surface association request in order to cause user interface(s) 50 of the bed(s) 22 to display the request. The computing device 4 may transmit one or more control messages to surface(s) 46 having the same location ID as the received surface association request in order to cause the user interface(s) 360 to display the request. As another option, the computing device 4 may send the control messages to the device (e.g. bed 22 or surface 46) that initiated the surface association request in order to cause the respective user interface 50, 360 to display the request. As yet another option, the computing device 4 may send a message (e.g. audio message and/or text message) to a pager, PDA or other type of wireless communication device such as Vocera® handsets or telephone handsets that have bidirectional voice communication capability and that may have text messaging capability of a caregiver located near the bed 22 or surface 46 that initiated the request. The computer device 4 may also send an audio message and/or text message to an audio station of a bed station 24 located near the multiple beds 22 or surface 46 that are possibly the ones that initiated the request.
As indicated at block 840, the computing device 4 may detect the identifying sequence based upon whether status data received from the bed 22 and/or surface 46 indicates the performance of the identifying sequence of actions. In one embodiment, the computing device 4 determines that identifying sequence of actions were performed only if received from a bed 22 and/or a surface 46 having the same location ID data as the surface association request. As mentioned above, multiple beds 22 and/or surfaces 46 may be located sufficiently close to the same location transmitter 332 of the healthcare facility to result in multiple beds 22 and/or surfaces 46 receiving and then re-transmitting the same location ID data. Thus, the healthcare facility may have multiple beds 22 and/or surfaces 46 with the same location ID data as the surface association request. However, the computing device 4 may identify the one bed 22 and/or surface 46 to be associated based upon status data identifying the predetermined sequence of actions and such actions being associated with a bed 22 and/or surface 46 with the same location ID data. In this manner, computing device 4 may support multiple surface association requests and appropriately match beds 22 and surfaces 46 of different overlapping requests within the healthcare facility.
If the sequence of actions is received from an appropriate bed 22 and/or surface 46, the computing device 4 may attempt to associate the identified bed 22 and surface 46 as indicated at block 850. The computing device 4 at block 860 may determine whether the attempt to associated the bed 22 and surface 46 succeeded in a manner similar to block 740 above. In manner similar to block 830 above, the computing device 4 at block 870 may provide the person requesting the association with an indication of the successful association. Conversely, if the predetermined sequence of actions was not received within a predetermined period (e.g. 20 seconds) or the attempted association failed, the computing device as indicated at block 880 may provide the person requesting the association with an indication of the unsuccessful association of the bed. Again, the computing device 4 may provide the indication in a manner similar to block 830 above.
Another technique to resolve such conflicts in an automated manner is incorporated in the surface association method presented in
In response to receiving the surface association request, the computing device 4 as indicated at block 930 may request that the caregiver perform a predetermined sequence of actions on the bed 22 and/or the surface 46 to confirm which bed 22 and/or surface 46 to be associated. In one embodiment, the computing device 4 in response to receiving the surface association request from the surface 46 transmits a control message to the bed or beds 22 having the same location ID as the surface 46. Similarly, the computing device 4 in response to receiving the surface association request from a bed 22 transmits a control message to the surface or surfaces 46 having the same location ID as the bed 22. As explained above, the healthcare facility may have multiple beds 22 and/or surfaces 46 within range of a location transmitter 332, thus resulting in multiple beds 22 and/or surfaces 46 having the same location ID. In such a case, the computing device 4 may send the request to multiple beds 22 or surfaces 46.
As indicated at block 940, the computing device 4 may determine based upon status data received from the bed 22 and/or surface 46 whether a confirmation from a caregiver was received. In one embodiment, the caregiver performs the actions on the bed 22 or surface 46 to be associated thus identifying the one device from potentially several devices to be associated. The computing device 4 in one embodiment determines that confirming actions were performed only if received from a bed 22 and/or a surface 46 having the same location ID data as the surface association request.
If confirmation is received, the computing device 4 as indicated at block 950 attempts to associate the identified bed 22 and surface 46. As indicated at block 960, the computing device 4 determines whether the attempted association was successful. If successful, the computing device provides the person requesting the association with an indication of the successful association as indicated at block 970. Conversely, if the predetermined sequence of actions was not received within a predetermined period (e.g. 20 seconds) or the attempt was otherwise unsuccessful, the computing device may provide the person requesting the association with an indication of the unsuccessful association of the bed as indicated at block 980. It should be appreciated that the computing device 4 may provide the user with a successful indication or an unsuccessful indication using numerous different approaches as mentioned above in regard to blocks 750 and 760.
The above surface association services may be used by a nurse call system to control the operation of a bed 22 and its associated surface 46. In one embodiment, one or more computing devices 4, such as those implementing a nurse call system, are operable to send command or control messages through the network infrastructure to beds 22 and surfaces 46 to control some aspect of the operation of beds 22 and surfaces 46. The words “command” and “control” are intended to be interchangeable according to this disclosure and each is intended to have the broad meaning of both. Therefore, such computing devices 4 may be operable to receive bed status data from bed 22, process it, and then, based on the bed status data from bed 22, transmit a control words or messages to bed 22 and/or surface 46. For example, if the bed status data from bed 22 indicates that a CPR release handle of the bed 22 has been pulled, then the control message to the support surface 46 associated with the bed 22 may result in the support surface 46 going into a max inflate mode to harden the air bladders in surface 46 in preparation for CPR being performed on the patient or, alternatively, the control message may result in support surface 46 completely deflating so that the patient is supported by the support deck 47 underlying the support surface 46 in preparation for CPR being performed on the patient.
As another example, if the bed status data from bed 22 indicates that casters of the hospital bed have been unbraked, then the command message to the associated support surface 46 may indicate that a therapy, such as lateral rotation therapy, alternating pressure therapy, percussion therapy, etc. should be stopped in preparation for the bed 22 being moved to a new location. As another example, one or more computing devices 4 may be operable to receive the surface status data from support surface 46, process it, and then, based on the surface status data, transmit a control message to bed 22. For example, if the surface status data indicates that lateral rotation therapy is active, then the control message to bed 22 may lock out a head section motor to prevent the head section of the bed 22 from being raised during the lateral rotation therapy. Computing device 4 may be configured to send surface status data to any other computer devices 4 coupled to network 10.
While embodiments are disclosed, the description is not intended to be construed in a limiting sense. Various modifications of the described embodiments, as well as other embodiments which are apparent to persons skilled in the art, are deemed to lie within the spirit and scope of the appended claims.
This application is a continuation of U.S. application Ser. No. 15/273,831, filed Sep. 23, 2016, which issued as U.S. Pat. No. 10,566,088, which is a continuation of U.S. application Ser. No. 14/098,704, filed Dec. 6, 2013, which issued as U.S. Pat. No. 9,465,915, which is a continuation of U.S. application Ser. No. 13/242,255, filed Sep. 23, 2011, which issued as U.S. Pat. No. 8,604,916, which is a continuation of U.S. application Ser. No. 12/961,608, filed Dec. 7, 2010, which issued as U.S. Pat. No. 8,031,057, which is a continuation of U.S. application Ser. No. 11/846,906, filed Aug. 29, 2007, which issued as U.S. Pat. No. 7,868,740, each of which is hereby incorporated by reference herein.
| Number | Name | Date | Kind |
|---|---|---|---|
| 2330356 | Beliveau | Sep 1943 | A |
| 2335524 | Lomax | Nov 1943 | A |
| 2736888 | McLain | Feb 1956 | A |
| 2896021 | Philipps | Jul 1959 | A |
| 3098220 | De Graaf | Jul 1963 | A |
| 3439320 | Ward | Apr 1969 | A |
| 3478344 | Schwitzgebel et al. | Nov 1969 | A |
| 3553383 | Rochtus | Jan 1971 | A |
| 3599199 | Bunting | Aug 1971 | A |
| 3599200 | Bunting | Aug 1971 | A |
| 3696384 | Lester | Oct 1972 | A |
| 3739329 | Lester | Jun 1973 | A |
| 3767859 | Doering et al. | Oct 1973 | A |
| 3805265 | Lester | Apr 1974 | A |
| 3913153 | Adams et al. | Oct 1975 | A |
| 3973200 | Akerberg | Aug 1976 | A |
| 4067005 | Levy et al. | Jan 1978 | A |
| 4150284 | Trenkler et al. | Apr 1979 | A |
| 4151407 | McBride et al. | Apr 1979 | A |
| 4183015 | Drew et al. | Jan 1980 | A |
| 4216462 | McGrath et al. | Aug 1980 | A |
| 4225953 | Simon et al. | Sep 1980 | A |
| 4228426 | Roberts | Oct 1980 | A |
| 4237344 | Moore | Dec 1980 | A |
| 4264982 | Sakarya | Apr 1981 | A |
| 4275385 | White | Jun 1981 | A |
| 4279433 | Petaja | Jul 1981 | A |
| 4298863 | Natitus et al. | Nov 1981 | A |
| 4331953 | Blevins et al. | May 1982 | A |
| 4356475 | Neumann et al. | Oct 1982 | A |
| 4418334 | Burnett | Nov 1983 | A |
| 4455548 | Burnett | Jun 1984 | A |
| 4489387 | Lamb et al. | Dec 1984 | A |
| 4495495 | Ormanns et al. | Jan 1985 | A |
| 4495496 | Miller, III | Jan 1985 | A |
| 4539560 | Fleck et al. | Sep 1985 | A |
| 4577185 | Andersen | Mar 1986 | A |
| 4578671 | Flowers | Mar 1986 | A |
| 4582280 | Nichols et al. | Apr 1986 | A |
| 4593273 | Narcisse | Jun 1986 | A |
| 4598275 | Ross et al. | Jul 1986 | A |
| 4601064 | Shipley | Jul 1986 | A |
| 4649385 | Aires et al. | Mar 1987 | A |
| 4680790 | Packard et al. | Jul 1987 | A |
| 4709330 | Yokoi et al. | Nov 1987 | A |
| 4740788 | Konneker | Apr 1988 | A |
| 4752951 | Konneker | Jun 1988 | A |
| 4792798 | Wilowski | Dec 1988 | A |
| 4795905 | Zierhut | Jan 1989 | A |
| 4814751 | Hawkins et al. | Mar 1989 | A |
| 4833452 | Currier | May 1989 | A |
| 4833467 | Kobayashi et al. | May 1989 | A |
| 4837568 | Snaper | Jun 1989 | A |
| 4853692 | Wolk et al. | Aug 1989 | A |
| 4899135 | Ghahariiran | Feb 1990 | A |
| 4947152 | Hodges | Aug 1990 | A |
| 4955000 | Nastrom | Sep 1990 | A |
| 4967195 | Shipley | Oct 1990 | A |
| 4990892 | Guest et al. | Feb 1991 | A |
| 4998095 | Shields | Mar 1991 | A |
| 4998939 | Potthast et al. | Mar 1991 | A |
| 5006830 | Merritt | Apr 1991 | A |
| 5027314 | Linwood et al. | Jun 1991 | A |
| 5041086 | Koenig et al. | Aug 1991 | A |
| 5062151 | Shipley | Oct 1991 | A |
| 5065154 | Kaiser et al. | Nov 1991 | A |
| 5086290 | Murray et al. | Feb 1992 | A |
| 5103108 | Crimmins | Apr 1992 | A |
| 5124991 | Allen | Jun 1992 | A |
| 5137033 | Norton | Aug 1992 | A |
| 5153584 | Engira | Oct 1992 | A |
| 5266944 | Carroll et al. | Nov 1993 | A |
| 5291399 | Chaco | Mar 1994 | A |
| 5319355 | Russek | Jun 1994 | A |
| 5319363 | Welch et al. | Jun 1994 | A |
| 5357254 | Kah, Jr. | Oct 1994 | A |
| 5375604 | Kelly et al. | Dec 1994 | A |
| 5396224 | Dukes et al. | Mar 1995 | A |
| 5396227 | Carroll et al. | Mar 1995 | A |
| 5416695 | Stutman et al. | May 1995 | A |
| 5434775 | Sims et al. | Jul 1995 | A |
| 5446678 | Saltzstein et al. | Aug 1995 | A |
| 5455560 | Owen | Oct 1995 | A |
| 5458123 | Unger | Oct 1995 | A |
| 5461390 | Hoshen | Oct 1995 | A |
| 5475367 | Prevost | Dec 1995 | A |
| 5534851 | Russek | Jul 1996 | A |
| 5537459 | Price et al. | Jul 1996 | A |
| 5548637 | Heller et al. | Aug 1996 | A |
| 5549113 | Halleck et al. | Aug 1996 | A |
| 5561412 | Novak et al. | Oct 1996 | A |
| 5568119 | Schipper et al. | Oct 1996 | A |
| 5576952 | Stutman et al. | Nov 1996 | A |
| 5579001 | Dempsey et al. | Nov 1996 | A |
| 5588005 | Ali et al. | Dec 1996 | A |
| 5594786 | Chaco et al. | Jan 1997 | A |
| 5621388 | Sherburne et al. | Apr 1997 | A |
| 5635907 | Bernard et al. | Jun 1997 | A |
| 5636245 | Ernst et al. | Jun 1997 | A |
| 5640953 | Bishop et al. | Jun 1997 | A |
| 5650769 | Campana, Jr. | Jul 1997 | A |
| 5650770 | Schlager et al. | Jul 1997 | A |
| 5664270 | Bell et al. | Sep 1997 | A |
| 5682139 | Pradeep et al. | Oct 1997 | A |
| 5686888 | Welles, II et al. | Nov 1997 | A |
| 5686902 | Reis et al. | Nov 1997 | A |
| 5687734 | Dempsey et al. | Nov 1997 | A |
| 5689229 | Chaco et al. | Nov 1997 | A |
| 5691980 | Welles, II et al. | Nov 1997 | A |
| 5699038 | Ulrich et al. | Dec 1997 | A |
| 5705980 | Shapiro | Jan 1998 | A |
| 5708421 | Boyd | Jan 1998 | A |
| 5713856 | Eggers et al. | Feb 1998 | A |
| 5719761 | Gatti et al. | Feb 1998 | A |
| 5731757 | Layson, Jr. | Mar 1998 | A |
| 5742237 | Bledsoe | Apr 1998 | A |
| 5751246 | Hertel | May 1998 | A |
| 5752917 | Fuchs | May 1998 | A |
| 5760704 | Barton et al. | Jun 1998 | A |
| 5767791 | Stoop et al. | Jun 1998 | A |
| 5781442 | Engleson et al. | Jul 1998 | A |
| 5793290 | Eagleson et al. | Aug 1998 | A |
| 5808564 | Simms et al. | Sep 1998 | A |
| 5812056 | Law | Sep 1998 | A |
| 5822418 | Yacenda et al. | Oct 1998 | A |
| 5822544 | Chaco et al. | Oct 1998 | A |
| 5838223 | Gallant et al. | Nov 1998 | A |
| 5844488 | Musick | Dec 1998 | A |
| 5867821 | Ballantyne et al. | Feb 1999 | A |
| 5877675 | Rebstock et al. | Mar 1999 | A |
| 5933488 | Marcus et al. | Aug 1999 | A |
| 5936539 | Fuchs | Aug 1999 | A |
| 5942986 | Shabot et al. | Aug 1999 | A |
| 5944659 | Flach et al. | Aug 1999 | A |
| 5963137 | Waters, Sr. | Oct 1999 | A |
| 5974389 | Clark et al. | Oct 1999 | A |
| 5991728 | DeBusk et al. | Nov 1999 | A |
| 5995937 | DeBusk et al. | Nov 1999 | A |
| 6014633 | DeBusk et al. | Jan 2000 | A |
| 6057758 | Dempsey et al. | May 2000 | A |
| 6057782 | Koenig | May 2000 | A |
| 6067019 | Scott | May 2000 | A |
| 6076166 | Moshfeghi et al. | Jun 2000 | A |
| 6085493 | DeBusk et al. | Jul 2000 | A |
| 6088362 | Turnbull et al. | Jul 2000 | A |
| 6093146 | Filangeri | Jul 2000 | A |
| 6097308 | Albert et al. | Aug 2000 | A |
| 6128512 | Trompower et al. | Oct 2000 | A |
| 6133837 | Riley | Oct 2000 | A |
| 6147592 | Ulrich et al. | Nov 2000 | A |
| 6183417 | Geheb et al. | Feb 2001 | B1 |
| 6208250 | Dixon et al. | Mar 2001 | B1 |
| 6241668 | Herzog | Jun 2001 | B1 |
| 6259355 | Chaco et al. | Jul 2001 | B1 |
| 6264614 | Albert et al. | Jul 2001 | B1 |
| 6279183 | Kummer et al. | Aug 2001 | B1 |
| 6287253 | Ortega et al. | Sep 2001 | B1 |
| 6302844 | Walker et al. | Oct 2001 | B1 |
| 6314556 | DeBusk et al. | Nov 2001 | B1 |
| 6320510 | Menkedick et al. | Nov 2001 | B2 |
| 6344794 | Ulrich et al. | Feb 2002 | B1 |
| 6348777 | Brown et al. | Feb 2002 | B1 |
| 6362725 | Ulrich et al. | Mar 2002 | B1 |
| 6364834 | Reuss et al. | Apr 2002 | B1 |
| 6398727 | Bui et al. | Jun 2002 | B1 |
| 6406426 | Reuss et al. | Jun 2002 | B1 |
| 6407335 | Franklin-Lees et al. | Jun 2002 | B1 |
| 6412980 | Lounsberry et al. | Jul 2002 | B1 |
| 6416471 | Kumar et al. | Jul 2002 | B1 |
| 6421649 | Rattner | Jul 2002 | B1 |
| 6439769 | Polkus et al. | Aug 2002 | B1 |
| 6441742 | Lovely et al. | Aug 2002 | B1 |
| 6442290 | Ellis et al. | Aug 2002 | B1 |
| 6445299 | Rojas, Jr. | Sep 2002 | B1 |
| 6450956 | Rappaport et al. | Sep 2002 | B1 |
| 6462656 | Ulrich et al. | Oct 2002 | B2 |
| 6486792 | Moster et al. | Nov 2002 | B1 |
| 6493568 | Bell et al. | Dec 2002 | B1 |
| 6494831 | Koritzinsky | Dec 2002 | B1 |
| 6510344 | Halpern | Jan 2003 | B1 |
| 6516324 | Jones et al. | Feb 2003 | B1 |
| 6526310 | Carter et al. | Feb 2003 | B1 |
| 6529164 | Carter | Mar 2003 | B1 |
| 6533453 | Heidsieck et al. | Mar 2003 | B1 |
| 6535576 | Vafi et al. | Mar 2003 | B2 |
| 6539393 | Kabala | Mar 2003 | B1 |
| 6544173 | West et al. | Apr 2003 | B2 |
| 6544174 | West et al. | Apr 2003 | B2 |
| 6551243 | Bocionek et al. | Apr 2003 | B2 |
| 6553106 | Gould et al. | Apr 2003 | B1 |
| 6554174 | Aceves | Apr 2003 | B1 |
| 6556630 | Brinsfield et al. | Apr 2003 | B1 |
| 6560274 | Leitgeb et al. | May 2003 | B1 |
| 6572556 | Stoycos et al. | Jun 2003 | B2 |
| 6575901 | Stoycos et al. | Jun 2003 | B2 |
| 6581204 | DeBusk et al. | Jun 2003 | B2 |
| 6584182 | Brodnick | Jun 2003 | B2 |
| 6584454 | Hummel, Jr. et al. | Jun 2003 | B1 |
| 6585645 | Hutchinson | Jul 2003 | B2 |
| 6589170 | Flach et al. | Jul 2003 | B1 |
| 6593528 | Franklin-Lees et al. | Jul 2003 | B2 |
| 6594146 | Frangesch et al. | Jul 2003 | B2 |
| 6594519 | Stoycos et al. | Jul 2003 | B2 |
| 6600421 | Freeman | Jul 2003 | B2 |
| 6603494 | Banks et al. | Aug 2003 | B1 |
| 6609115 | Mehring et al. | Aug 2003 | B1 |
| 6616606 | Petersen et al. | Sep 2003 | B1 |
| 6622088 | Hood | Sep 2003 | B2 |
| 6640246 | Gary, Jr. et al. | Oct 2003 | B1 |
| 6643238 | Nakajima | Nov 2003 | B2 |
| 6650346 | Jaeger et al. | Nov 2003 | B1 |
| 6659947 | Carter et al. | Dec 2003 | B1 |
| 6665385 | Rogers et al. | Dec 2003 | B2 |
| 6665820 | Frowein et al. | Dec 2003 | B1 |
| 6669630 | Joliat et al. | Dec 2003 | B1 |
| 6671547 | Lyster et al. | Dec 2003 | B2 |
| 6671563 | Engelson et al. | Dec 2003 | B1 |
| 6685633 | Albert et al. | Feb 2004 | B2 |
| 6689091 | Bui et al. | Feb 2004 | B2 |
| 6694367 | Miesbauer et al. | Feb 2004 | B1 |
| 6694509 | Stoval et al. | Feb 2004 | B1 |
| 6697765 | Kuth | Feb 2004 | B2 |
| 6707476 | Hochstedler | Mar 2004 | B1 |
| 6714913 | Brandt et al. | Mar 2004 | B2 |
| 6721818 | Nakamura | Apr 2004 | B1 |
| 6726634 | Freeman | Apr 2004 | B2 |
| 6727818 | Wildman et al. | Apr 2004 | B1 |
| 6731311 | Bufe et al. | May 2004 | B2 |
| 6731989 | Engleson et al. | May 2004 | B2 |
| 6740033 | Olejniczak et al. | May 2004 | B1 |
| 6749566 | Russ | Jun 2004 | B2 |
| 6751630 | Franks et al. | Jun 2004 | B1 |
| 6754545 | Haeuser et al. | Jun 2004 | B2 |
| 6754883 | DeBusk et al. | Jun 2004 | B2 |
| 6759959 | Wildman | Jul 2004 | B2 |
| 6763541 | Mahoney et al. | Jul 2004 | B2 |
| 6771172 | Robinson et al. | Aug 2004 | B1 |
| 6773396 | Flach et al. | Aug 2004 | B2 |
| 6778225 | David | Aug 2004 | B2 |
| 6781517 | Moster et al. | Aug 2004 | B2 |
| 6784797 | Smith et al. | Aug 2004 | B2 |
| 6791460 | Dixon et al. | Sep 2004 | B2 |
| 6792396 | Inda et al. | Sep 2004 | B2 |
| 6801227 | Bocionek et al. | Oct 2004 | B2 |
| 6807543 | Muthya | Oct 2004 | B2 |
| 6825763 | Ulrich et al. | Nov 2004 | B2 |
| 6826578 | Brackett et al. | Nov 2004 | B2 |
| 6828992 | Freeman et al. | Dec 2004 | B1 |
| 6829796 | Salvatini et al. | Dec 2004 | B2 |
| 6830549 | Bui et al. | Dec 2004 | B2 |
| 6832199 | Kucek et al. | Dec 2004 | B1 |
| 6840117 | Hubbard, Jr. | Jan 2005 | B2 |
| 6847814 | Vogeleisen | Jan 2005 | B1 |
| 6868256 | Dooley et al. | Mar 2005 | B2 |
| 6871211 | Labounty et al. | Mar 2005 | B2 |
| 6873884 | Brackett et al. | Mar 2005 | B2 |
| 6876985 | Kawanaka | Apr 2005 | B2 |
| 6885288 | Pincus | Apr 2005 | B2 |
| 6891909 | Hurley et al. | May 2005 | B2 |
| 6904161 | Becker et al. | Jun 2005 | B1 |
| 6909995 | Shiraishi | Jun 2005 | B2 |
| 6912549 | Rotter et al. | Jun 2005 | B2 |
| 6915170 | Engleson et al. | Jul 2005 | B2 |
| 6925367 | Fontius | Aug 2005 | B2 |
| 6930878 | Brackett et al. | Aug 2005 | B2 |
| 6987448 | Catton et al. | Jan 2006 | B2 |
| 7068143 | Doering et al. | Jun 2006 | B2 |
| 7187268 | Armstrong et al. | Mar 2007 | B1 |
| 7319386 | Collins et al. | Jan 2008 | B2 |
| 7399205 | McNeely et al. | Jul 2008 | B2 |
| 7461425 | Chambers et al. | Dec 2008 | B2 |
| 7598853 | Becker et al. | Oct 2009 | B2 |
| 7852208 | Collins, Jr. | Dec 2010 | B2 |
| 7868740 | McNeely et al. | Jan 2011 | B2 |
| 8031057 | McNeely et al. | Oct 2011 | B2 |
| 8604916 | McNeely et al. | Dec 2013 | B2 |
| 9465915 | McNeely et al. | Oct 2016 | B2 |
| 10566088 | McNeely et al. | Feb 2020 | B2 |
| 20010050610 | Gelston | Dec 2001 | A1 |
| 20010051765 | Walker et al. | Dec 2001 | A1 |
| 20020014951 | Kramer et al. | Feb 2002 | A1 |
| 20020044043 | Chaco et al. | Apr 2002 | A1 |
| 20020044059 | Reeder et al. | Apr 2002 | A1 |
| 20020067273 | Jaques et al. | Jun 2002 | A1 |
| 20020070867 | Conway et al. | Jun 2002 | A1 |
| 20020080037 | Dixon et al. | Jun 2002 | A1 |
| 20020103674 | Reeder et al. | Aug 2002 | A1 |
| 20020151990 | Ulrich et al. | Oct 2002 | A1 |
| 20020173991 | Avitall | Nov 2002 | A1 |
| 20020186136 | Schuman | Dec 2002 | A1 |
| 20020196141 | Boone et al. | Dec 2002 | A1 |
| 20030010345 | Koblasz et al. | Jan 2003 | A1 |
| 20030028449 | Heinen et al. | Feb 2003 | A1 |
| 20030030569 | Ulrich et al. | Feb 2003 | A1 |
| 20030052787 | Zerhusen et al. | Mar 2003 | A1 |
| 20030074222 | Rosow | Apr 2003 | A1 |
| 20030146835 | Carter | Aug 2003 | A1 |
| 20030149598 | Santoso et al. | Aug 2003 | A1 |
| 20030176798 | Simon | Sep 2003 | A1 |
| 20030206116 | Weiner et al. | Nov 2003 | A1 |
| 20040183681 | Smith | Sep 2004 | A1 |
| 20040183684 | Callaway | Sep 2004 | A1 |
| 20040186358 | Chernow et al. | Sep 2004 | A1 |
| 20040193449 | Wildman et al. | Sep 2004 | A1 |
| 20050035862 | Wildman et al. | Feb 2005 | A1 |
| 20050177400 | Rosenfeld | Aug 2005 | A1 |
| 20050219059 | Ulrich et al. | Oct 2005 | A1 |
| 20050242946 | Hubbard, Jr. et al. | Nov 2005 | A1 |
| 20060049936 | Collins, Jr. | Mar 2006 | A1 |
| 20060179571 | Newkirk | Aug 2006 | A1 |
| 20060267740 | Bixler et al. | Nov 2006 | A1 |
| 20060271207 | Shaw | Nov 2006 | A1 |
| 20060279427 | Becker et al. | Dec 2006 | A1 |
| 20070010719 | Huster et al. | Jan 2007 | A1 |
| 20070106518 | Wildman et al. | May 2007 | A1 |
| 20070141869 | McNeeley et al. | Jun 2007 | A1 |
| 20070210917 | Collins, Jr. | Sep 2007 | A1 |
| 20070247310 | Ulrich | Oct 2007 | A1 |
| 20070250191 | Rourke | Oct 2007 | A1 |
| 20080068447 | Mattila | Mar 2008 | A1 |
| 20080109255 | Allen | May 2008 | A1 |
| 20080311959 | Wang et al. | Dec 2008 | A1 |
| 20090056027 | Ball et al. | Mar 2009 | A1 |
| 20090063183 | McNeely et al. | Mar 2009 | A1 |
| 20110072583 | McNeely et al. | Mar 2011 | A1 |
| 20110074571 | Collins, Jr. et al. | Mar 2011 | A1 |
| 20120013452 | McNeely et al. | Jan 2012 | A1 |
| 20140095197 | McNeely et al. | Apr 2014 | A1 |
| 20170011181 | McNeely et al. | Jan 2017 | A1 |
| Number | Date | Country |
|---|---|---|
| WO 02091297 | Nov 2002 | WO |
| WO 2004036390 | Apr 2004 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 20200152325 A1 | May 2020 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15273831 | Sep 2016 | US |
| Child | 16739486 | US | |
| Parent | 14098704 | Dec 2013 | US |
| Child | 15273831 | US | |
| Parent | 13242255 | Sep 2011 | US |
| Child | 14098704 | US | |
| Parent | 12961608 | Dec 2010 | US |
| Child | 13242255 | US | |
| Parent | 11846906 | Aug 2007 | US |
| Child | 12961608 | US |
