Patent Grant
11011267
The present disclosure relates to systems and methods for associating beds, rooms, and/or patients and particularly, to such association systems and methods used in a healthcare facility.
Systems and methods for determining the location of a patient bed within a healthcare facility are known. In some of the known systems, a locating tag is attached to the bed and periodically transmits a wireless signal that includes a tag identifier (aka a “tag ID”) which is a string of characters such as letters and/or numbers and/or symbols that uniquely identify the tag. In some such prior art systems, a set of wireless receivers are mounted at fixed locations throughout the healthcare facility and are coupled to the computer network of the healthcare facility. A receiver in the vicinity of a tag receives the tag ID and transmits it along with a receiver ID to other computer devices of the network. Each receiver ID corresponds to a location in the healthcare facility. Thus, one or more remote computer devices are able to determine the location of the bed based on the tag ID and the receiver ID.
In many of the prior art systems, the wireless signal from the tag is an infrared signal that requires an uninterrupted line of sight to a receiver. If the line of sight is blocked, the receiver does not receive the signal from the tag. Thus, in more recent times, the desire has been to use radio frequency (RF) tags but the drawback with those systems is that RF signals are able to penetrate floors, ceilings and walls in a healthcare facility such that multiple receivers sometimes receive the same wireless RF signal and further processing of some type is needed to resolve the ambiguity of the bed's location. Some prior art systems have resolved the ambiguities by analyzing signal strength or analyzing time of flight information.
In some known prior art systems, patient beds have circuitry that transmits a bed ID, as opposed to a tag ID, as well as bed status data from the beds. Typically, the transmissions are made over a cable that extends from the bed to some sort of interface unit mounted to a wall in a room, but there is the option to do this wirelessly in some prior art systems by using a wireless interface unit mounted to the room wall. In any event, the interface unit that receives the transmissions from the bed, either via a wired or wireless connection, is then connected to the network of the healthcare facility, typically, via a wired connection. In these prior art systems, the installation of interface units just to receive bed ID and bed status data is an added cost to the overall network of the healthcare facility.
The use of wireless access points in healthcare facilities to receive Wi-Fi signals from a variety of equipment and computer devices is becoming more widespread. Thus, there is a need to develop systems and methods for making bed-to-room associations or patient-to-room associations or patient-to-bed associations or patient-to-bed-to-room associations that minimize the amount of specialized receivers, interface units, or other equipment that must be coupled to the network of the facility.
The present invention may comprise one or more of the features recited in the appended claims and/or the following features which each are considered to be optional and which, alone or in any combination, may comprise patentable subject matter:
A system for use in a healthcare facility that may have a network may be provided according to this disclosure. The system may include a light source that may emit visible light that may have a signature that may be unique to a location of the healthcare facility. The system may also include a patient bed that may have circuitry that may analyze the light from the light source to determine the signature corresponding to the location. The circuitry may be configured to transmit data corresponding to the signature and to transmit bed identifier (ID) to the network.
In some embodiments, the signature may comprise a specified wavelength. The light source may be programmable to emit light at the specified wavelength. Alternatively or additionally, the signature may comprise a specified pulse frequency that may be sufficiently great so as to be imperceptible by human vision. The light source may be programmable to emit light at the specified pulse frequency. Thus, the signature may comprise a specified wavelength at a specified pulse frequency in some embodiments. In such embodiments, the light source may be programmable to emit light at the specified wavelength and at the specified pulse frequency.
According to this disclosure, the light source may comprise a light bulb that provides room lighting. In other embodiment, the light source may comprise a display screen, such as one that may be mounted to a ceiling or a wall of a room of the healthcare facility. The display screen may be the display screen of a computer device such as the display screen of a room station of a nurse call system, for example. There may be a light source in a number of rooms and the signature from the light source, be it a light bulb or a display screen, may be different for each room. The light source may include at least one light emitting diode (LED).
Further according to this disclosure, the circuitry of the patient bed may include a red-green-blue image sensor that may sense the light emitted by the light source. Alternatively or additionally, the circuitry of the patient bed may include a camera that receives the light emitted by the light source.
The system may further include a computer device that may be coupled to the network remote from the light source and the patient bed. The computer device may determine the location of the healthcare facility in which the light source may be located based on the data corresponding to the signature. The computer device may associate the bed ID with the location of the healthcare facility.
In some embodiments, the circuitry of the patient bed may wirelessly transmits the data corresponding to the signature and the bed ID to the computer device via a wireless access point of the network. Alternatively or additionally, the circuitry of the patient bed may transmit the data corresponding to the signature and the bed ID to the computer device via a wired connection from the bed to the network.
According to some embodiments, a light source may emit visible light and infrared (IR) light. The IR light may have a signature that may be unique to a location of the healthcare facility. A patient bed may include circuitry that may analyze the IR light from the light source to determine the signature corresponding to the location. The circuitry may be configured to transmit data corresponding to the signature and to transmit bed identifier (ID) to the network.
In some embodiments, the IR light may only be emitted when the visible light is turned off. According to this disclosure, the light source may include an energy storage device that may power the IR light while the visible light is turned off. The energy storage device may be charged when the visible light is turned on.
In some embodiments, the visible light may also be emitted with the signature such that the visible light and the IR light have the same signature. For example, the signature may comprise a specified pulse frequency. The specified pulse frequency may be programmable.
Further according to this disclosure, another system for use in a healthcare facility having a network may be provided. The system may include an array of redundant bar codes and a patient bed that may be spaced from the array of redundant bar codes. The patient bed may include circuitry that may comprise a bar code reader that may read at least one of the redundant bar codes in the array. The circuitry may be configured to transmit data corresponding to the at least one of the redundant bar codes and to transmit bed identifier (ID) to the network.
The array of redundant bar codes may be affixed to a vertical surface in a room of the healthcare facility. In such embodiments, the patient bed may include a frame that may have longitudinally spaced ends. The bar code reader may be mounted adjacent to one of the longitudinally spaced ends. The vertical surface may comprise a wall of the room or a panel of an architectural product that may be mounted to a wall of the room. The architectural product may include a bed locator unit, a headwall unit, or a column, for example. Alternatively or additionally, the array of redundant bar codes may be affixed to a horizontal surface in the room, such as the floor. The patient bed may include a frame and the bar code reader may be coupled to the frame so as to point downwardly toward the floor.
In some embodiments, the array of redundant bar codes may include at least one row having at least three identical bar codes. In other embodiments, the array of redundant bar codes may include at least three rows each having at least three identical bar codes. It should be appreciated that this disclosure contemplates any number of rows and columns of redundant bar codes greater or lesser in number than three.
Another system contemplated by this disclosure may include a patient bed that may have a frame, circuitry that may be carried by the frame, and a graphical user interface that may be carried by the frame and that may be coupled to the circuitry. The graphical user interface may display at least one user interface screen that may be used by a caregiver to manually enter location data that may be indicative of a location in a healthcare facility that may be occupied by the patient bed. The circuitry may transmit off of the bed the location data entered by the caregiver and a bed identification (ID).
In some embodiments, the location data may comprise a room number. The graphical user interface may include a change button that may be selected to initiate a change of the location data. A keyboard screen may appear on the graphical user interface in response to the change button being selected. The keyboard screen may permit the caregiver to type new location data that may be indicative of a new location that may be occupied by the patient bed.
In some embodiments, the system may include at least one remote computer device that may receive the location data and the bed ID for purposes of making a bed-to-room association. The patient bed may be coupled to the at least one remote computer device via a network of the healthcare facility. The location data and the bed ID may be transmitted off of the bed in the form of a wireless transmission. The circuitry also may transmit bed status data off of the bed.
In some embodiments, the location data may include unit data that may be indicative of a unit of the healthcare facility that may be occupied by the patient bed and a room number of the unit in which the patient bed may be situated. The graphical user interface may display a first screen that may be used to select the unit of the healthcare facility that may be occupied by the patient bed from a menu of units and a second screen that may be used to select the room number from a menu of room numbers.
Further according to this disclosure, a system for associating a bed to a room of a healthcare facility may include a locator unit that may be fixed in place and that may transmit a location ID. The system may include a patient bed that may have first circuitry that may have a first ID and that may receive the location ID. The patient bed may have second circuitry that may be independent of the first circuitry. The second circuitry may be configured to transmit a bed ID and bed status data.
The system may further have a first transceiver that may be spaced from the locator unit and that may be spaced from the patient bed. The first transceiver may receive the first ID and location ID transmitted by the first circuitry. A second transceiver of the system may be spaced from and independent of the first transceiver. The second transceiver may receive the bed ID and the bed status data that may be transmitted by the second circuitry.
The system may also have a first remote computer device that may receive the location ID and first ID that may be transmitted to the first remote computer device by the first transceiver. The system may further have a second remote computer device that may receives the bed ID and the bed status data which may be transmitted to the second computer device by the second transceiver. The first and second remote computer devices may cooperate to associate the location ID and the bed status data with the bed ID.
In some embodiments, the first circuitry may be included as part of a tag that may attach to an exterior surface of the patient bed. The first circuitry may transmit the first ID and the location ID using a first wireless transmission technology. The second circuitry may transmit the bed ID and the bed status data using a second wireless transmission technology. The first wireless transmission technology may differ from the second wireless transmission technology. For example, the first wireless transmission technology may comprise one of infrared technology, radio frequency technology, and ultrasonic technology and the second wireless transmission technology may comprise a different one of infrared technology, radio frequency technology, and ultrasonic technology.
Another system according to this disclosure may include a locator unit that may be fixed in place and that may transmit a location ID in a first format. The system may also include a patient bed that may have a bed ID and circuitry that may have stored therein ID translation software. The circuitry may receive the location ID in the first format and, in accordance with the ID translation software, may convert the location ID to a modified ID that may have a second format different than the first format. The circuitry may transmit the bed ID and the modified ID such that the location ID received by the circuitry of the patient bed may not be transmitted by the circuitry.
The system may further include a remote computer device that may receive the bed ID and the modified ID and that may determine a location of the patient bed based on the modified ID. The modified ID may include a room number of a room in a healthcare facility in which the patient bed may be located and the translation software may include a look up table that may convert the location ID into the room number of the modified ID. The location ID may have a different number of bits of information than the modified ID.
Yet another system according to this disclosure may comprise a locator unit that may be fixed in place and that transmits a location ID. The system further may have a patient bed that may have a bed ID and circuitry that may have stored therein ID mutation software. The circuitry may receive the location ID and, in accordance with the ID mutation software, may mutate the location ID and the bed ID into a mutated ID. The mutated ID may be a single unique ID. The circuitry may transmit the mutated ID, whereby neither the location ID received by the circuitry nor the bed ID of the patient bed may be transmitted by the circuitry.
According to some embodiments, mutating the location ID and the bed ID into the mutated ID may include adding the location ID and the bed ID to create an added ID. Mutating the location ID and the bed ID into the mutated ID may further include applying a hashing function to the added ID to create a hashed ID. While any suitable hashing function is contemplated by this disclosure, in some embodiments, the hashing function may comprise a cryptographic hashing function.
The system may further comprise a remote computer device that may having decoding software that may determine the location ID and the bed ID based on the hashed ID. For example, the decoding software may include a look up table that may identify a location ID and a bed ID for each possible hashed ID. Alternatively or additionally, the decoding software may generate comparison hashed ID's by sequentially adding and hashing all known bed ID's with all known location ID's until one of the comparison hashed ID's matches the hashed ID then storing in an association database the location ID and the bed ID that caused the comparison hashed ID to match the hashed ID.
According to each of the embodiments contemplated herein, the circuitry of the patient bed may also transmit bed status data and/or a patient ID of a patient assigned to the patient bed. According to some embodiments, the remote computer device may having decoding software that determines the location ID and bed ID based on the hashed ID and that associates the location ID, bed ID and the bed status data and/or the patient ID in a database.
According to this disclosure, a method may include receiving, with circuitry on a patient bed, light from a light source that may emit visible light that may have a signature that may be unique to a location of the healthcare facility. The method may further include analyzing, using software stored in the circuitry of the patient bed, the light from the light source to determine the signature corresponding to the location, and transmitting, using the circuitry of the patient bed, data corresponding to the signature and a bed ID. In some embodiments, the method further may include receiving, with a remote computer device, the bed ID and the data corresponding to the signature and associating the location of the patient bed with the patient bed.
Another method according to this disclosure may include receiving, with circuitry on a patient bed, light from a light source that may be operable to emit IR light that may have a signature that is unique to a location of the healthcare facility and that may also be operable to emit visible light. The method may further include analyzing, using software stored in the circuitry of the patient bed, the IR light from the light source to determine the signature corresponding to the location and transmitting, using the circuitry of the patient bed, data corresponding to the signature and a bed ID.
In some embodiments, the method may further include receiving, with a remote computer device, the bed ID and the data corresponding to the signature and associating the location of the patient bed with the patient bed based on the data corresponding to the signature. The IR light that may have the signature may be transmitted only when the visible light is turned off.
In some embodiments, the method further includes receiving, with the circuitry of the patient bed, visible light that may have the signature such that the visible light and the IR light may have the same signature. The signature of the visible light and/or the IR light may comprise a specified pulse frequency. As mentioned above, the specified pulse frequency may be programmable.
Yet another method according to this disclosure includes scanning, using a bar code scanner of a patient bed, at least one bar code from an array of redundant bar codes that may be mounted to a surface in a room. The bar code may be indicative of a location of the room. The method may further include transmitting off of the patient bed, using circuitry of the patient bed, data that may correspond to the at least one of the redundant bar codes and a bed ID.
In some embodiments, the method may further include receiving the data corresponding to the at least one of the redundant bar codes and receiving the bed ID at a remote computer device and associating the patient bed with the location based on the data corresponding to the at least one of the redundant bar codes and the bed ID. According to this disclosure, the surface to which the array of redundant bar codes may be mounted may comprise a surface of a room wall, a surface of architectural equipment in the room, or a floor surface.
Still another method according to this disclosure includes displaying, on a graphical user interface of a patient bed, fields that a caregiver may select to manually enter location data indicative of a location in a healthcare facility occupied by the patient bed. The method may further include receiving, on the graphical user interface, selections from the caregiver of the location data and transmitting, from the patient bed, the location data entered by the caregiver and a bed ID.
In some embodiments, the method may further comprise receiving the location data and receiving the bed ID at a remote computer device and associating the patient bed with the location based on the location data and the bed ID. The location data may comprise a room number in some embodiments and may comprise a unit number (or a unit name) and a room number in other embodiments.
Still a further method contemplated by this disclosure includes transmitting a location ID from a locator unit that may be fixed in place in a room of a healthcare facility, receiving, with first circuitry of a patient bed that may be spaced from the locator unit, the location ID. The method may further include transmitting, from the first circuitry, a first ID and the location ID and transmitting, from second circuitry of the patient bed, a bed ID and bed status data. Still further the method may include receiving, with a first transceiver that may be spaced from the locator unit and spaced from the patient bed, the first ID and location ID transmitted by the first circuitry and receiving, with a second transceiver that may be spaced from and independent of the first transceiver, the bed ID and the bed status data transmitted by the second circuitry. The method may also include transmitting the location ID and the first ID from the first transceiver, transmitting the bed ID and the bed status data from the second transceiver, receiving, with a first remote computer device, the location ID and first ID transmitted by the first transceiver, receiving, with a second remote computer device, the bed ID and the bed status data transmitted by the second transceiver, and associating the location ID with the bed status data and the bed ID via cooperation between the first and second remote computer devices.
According to this disclosure, another method may include transmitting a location ID from a locator unit that may be fixed in place in a healthcare facility. The location ID may have a first format. The method also may include receiving the location ID with circuitry of a patient bed that may be spaced from the locator unit and that has a bed ID. The further may include converting the location ID that may have the first format to a modified ID that may have a second format using translation software that may be stored in the circuitry of the patient bed. The second format may be different than the first format. The method may include transmitting, using the circuitry, the bed ID and the modified ID, whereby the location ID received by the circuitry of the patient bed may not be transmitted by the circuitry.
In some embodiments, the method further comprises receiving, with a remote computer device, the bed ID and the modified ID and determining, with the remote computer device, a location of the patient bed based on the modified ID. The modified ID may include a room number of a room in a healthcare facility in which the patient bed may be located and the translation software on the patient bed may include a look up table that may be used to convert the location ID into the room number of the modified ID. In some embodiments, the location ID has a different number of bits of information than the modified ID.
Still another method according to this disclosure may include transmitting a location ID from a locator unit that may be fixed in place in a room of a healthcare facility, receiving the location ID in circuitry of a patient bed having a bed ID, and mutating the location ID and the bed ID into a mutated ID using ID mutation software that may be stored in the circuitry. The mutated ID may be a single unique ID. The method may further include transmitting the mutated ID from the patient bed, whereby neither the location ID received by the circuitry nor the bed ID of the patient bed may be transmitted by the patient bed.
In some embodiments, mutating the location ID and the bed ID into the mutated ID may include adding the location ID and the bed ID to create an added ID. Mutating the location ID and the bed ID into the mutated ID may further comprise applying a hashing function to the added ID to create a hashed ID. The hashing function may comprise a cryptographic hashing function, for example.
The method may further comprise determining the location ID and the bed ID based on the hashed ID at a remote computer using decoding software. The decoding software may include a look up table that identifies a location ID and a bed ID for each possible hashed ID. Alternatively or additionally, the decoding software may generate comparison hashed ID's by sequentially adding and hashing all known bed ID's with all known location ID's until one of the comparison hashed ID's matches the hashed ID then storing in an association database the location ID and the bed ID that caused the comparison hashed ID to match the hashed ID.
In some embodiments, the method may further include transmitting bed status data from the patient bed and, optionally, using a remote computer device to determine the location ID and the bed ID based on the hashed ID and to associate the location ID, bed ID and bed status data in a database. Alternatively or additionally, the method may include transmitting from the patient bed a patient ID of a patient assigned to the patient bed and, optionally, using a remote computer device to determine the location ID and bed ID based on the hashed ID and to associate the location ID, bed ID and patient ID in a database.
According to another aspect of this disclosure, a hospital bed for use with a locating and tracking system may be provided and may include a patient support structure that may be configured to support a patient. The hospital bed may further have circuitry that may be carried by the patient support structure and that may be in communication with the locating and tracking system. The hospital bed may have an indicator that may be coupled to the circuitry and that may be signaled by the circuitry to provide an indication that a successful bed-to-room association has been made.
In some embodiments, the indicator may comprise a light. The light may be turned on in response to the successful bed-to-room association being made and the light may be turned off in the absence of the successful bed-to-room association. The light may be illuminated a first color in response to the successful bed-to-room association being made and the light may be illuminated a second color in the absence of the successful bed-to-room association. The indication that a successful bed-to-room association has been made may be communicated to the circuitry from the locating and tracking system.
The hospital bed may further include an indicator module that may be attachable as a unit to the patient support structure. The indicator module may include a housing and the indicator may be carried by the housing. The circuitry may be carried by the housing. Alternatively or additionally, the indicator module may include module circuitry that may be in communication with the circuitry.
The hospital bed may have at least one other indicator. The at least one other indicator may include a communication indicator to indicate that a successful communication link has been established to a network of a healthcare facility. Alternatively or additionally, the at least one other indicator may include an alarm monitor indicator to indicate that one or more conditions of the hospital bed have been selected using a remote computer for monitoring of alarm conditions. Further alternatively or additionally, the at least one other indicator may include a signal strength indicator that may indicate a strength of a wireless communication link. For example, the signal strength indicator may comprise a multi-color light that may be illuminated different colors to indicate different levels of signal strength of the wireless communication link.
According to this disclosure, a method may include receiving at a first computer device that is remote from a bed, bed data transmitted from the bed. The method may include receiving at the first computer device, prospective bed-to-room association data transmitted from a second computer device to indicate that the bed is in a particular location, the second computer device may be included as part of a locating system. According to the method, after receiving the prospective bed-to-room association data, the first computer device may analyze the bed data to determine if it includes information indicating that a power cord of the bed is plugged into a power outlet. If the bed data includes information indicating that the power cord is plugged into a power outlet, the method includes storing the prospective bed-to-room association data in a database associated with the first computer device as finalized bed-to-room association data.
In some embodiments, the method further includes transmitting a message from the first computer device to the bed to notify the bed that a successful bed-to-room location has been made. Alternatively or additionally, the method includes indicating on the bed that a successful bed-to-room association has been made. For example, indicating on the bed that a successful bed-to-room association has been made may comprise illuminating a light on the bed and/or displaying location information on a graphical display of the bed.
The method may further comprise detecting at the bed that the power cord has become unplugged from the power outlet and ceasing indicating on the bed that a successful bed-to-room association has been made. The method may also comprise transmitting further bed data from the bed to the first computer device. The further bed data may include information indicating that the power cord is unplugged.
In some embodiments, the method may further include disassociating the bed from the particular location at the first computer device after receiving at the first computer device the further bed data including the information that the power cord is unplugged. The method may further comprise displaying on a display screen coupled to the first computer device information to indicate that the bed-to-room association no longer exists.
According to another aspect of the present disclosure, a system may include a bed that may have bed circuitry that may be configured to control bed functions, to receive wireless signals, and to transmit signals. The system may also include a heart rate monitor that may be worn by a patient. The heart rate monitor may have monitor circuitry that may be programmed to store a medical record number (MRN) of the patient. The monitor circuitry also may be configured to transmit the MRN wirelessly to the bed circuitry. The bed circuitry may be configured to transmit bed identification (ID) data and the MRN. A first remote computer device may be configured to receive the bed ID data and the MRN of the patient and may be configured to generate patient-to-bed association data for storage in a database based on the bed ID data and the MRN.
In some embodiments, the monitor circuitry also may be configured to transmit heart rate data to the bed circuitry. The bed circuitry may be configured to transmit the heart rate data to the first remote computer device. Alternatively or additionally, the bed circuitry may be configured to transmit the heart rate data to a second remote computer device. In some embodiments, the heart rate monitor may have an arm strap that may attach to an arm of the patient. Alternatively or additionally, the heart rate monitor may have a chest strap that may attach to a chest of the patient.
According to still a further aspect of this disclosure, a system includes a bed that may have bed circuitry that may be configured to control bed functions, to receive wireless signals, and to transmit signals. The system may include a heart rate monitor that may be worn by a patient. The heart rate monitor may have monitor circuitry that may store monitor identification (ID) data. The monitor circuitry may transmit the monitor ID data wirelessly to the bed circuitry. The bed circuitry may, in turn, transmit bed identification (ID) data and the monitor ID data. The system may further have a first remote computer device that may receive the bed ID data and the monitor ID data, that may correlate the monitor ID data with a medical record number (MRN) of the patient and that may generate patient-to-bed association data for storage in a database based on the bed ID data and the MRN.
In some embodiments, the monitor circuitry also may be configured to transmit heart rate data to the bed circuitry. In such embodiments, the bed circuitry may be configured to transmit the heart rate data to the first remote computer device. Alternatively or additionally, the bed circuitry may be configured to transmit the heart rate data to a second remote computer device. In some embodiments, the heart rate monitor may have an arm strap that attaches to an arm of the patient. Alternatively or additionally, the heart rate monitor may have a chest strap that attaches to a chest of the patient.
According to yet another aspect of this disclosure, a system may comprise a bed may have a first radio frequency (RF) communication module that may have first identification (ID) data. The first RF communication module may transmit bed data and the first ID data wirelessly from the bed. The bed may have a power cord that carries a transponder. The system may further include a second RF communication module that may be spaced from the bed and situated adjacent to a wall of a room in which the bed is located. The second RF communication module may have second ID data. The second RF communication module may receive the bed data and first ID data transmitted wirelessly from the first RF communication module of the bed.
The system may also have a transponder reader that may be situated adjacent to the wall of the room and that may be configured to read wireless information from the transponder including the first ID data. The system may include a communication circuit that is situated adjacent to the wall of the room. The communication circuit may be coupled to the transponder reader and coupled to the second RF communication module. The communication circuit may be configured to receive the first ID data from the transponder reader and to receive the second ID data from the second RF communication module. The communication circuit may pair the first and second RF communication modules so that the second RF communication module only accepts communication packets from the first RF communication module. Alternatively or additionally, the communication circuit may pair the first and second RF communication modules so that the communication board only accepts communication packets from the second RF communication module if the packets contain the first ID data.
In some embodiments, the bed may further include a Wi-Fi communication module. In such embodiments, the first RF communication module and the Wi-Fi communication module may be controlled so as to send wireless transmissions in different, non-overlapping time slots. In some embodiments, the communication circuit may be configured to send the bed data received via the first and second RF communication modules to a remote computer device.
The system may further have a data cable that may extend from the bed and which may be coupleable to the communication circuit. Thus, the communication circuit may receive the bed data transmitted by the bed over the data cable when the communication circuit is coupled to the data cable. The communication circuit may cease to accept bed data from the second RF communication module and may accept only the bed data transmitted over the data cable. In some embodiments, the bed may include a siderail and the first RF communication module may be coupled to the siderail.
The transponder may comprise an RFID tag, if desired. For example, the RFID tag may be molded into a plug body of the power cord or may be situated on a label attached to the power cord. The transponder reader may comprise a loop antenna. The loop antenna may be located adjacent a power outlet to which the power cord couples.
Further according to this disclosure, a system may include a bed that may have a first radio frequency (RF) communication module that may have first identification (ID) data and a second RF communication module that may have second ID data. The first and second RF communication modules may transmit bed data and the respective first and second ID data wirelessly from the bed. The bed may have a power cord that may carry a transponder. A third RF communication module may be spaced from the bed and situated adjacent to a wall of a room in which the bed is located. The third RF communication module may have third ID data. The third RF communication module may receive wireless transmissions from the first and second RF communication modules of the bed. The wireless transmissions may include the bed data and the respective first and second ID data transmitted wirelessly.
The system may further have a transponder reader that may be situated adjacent to the wall of the room and that may be configured to read wireless information from the transponder including the first ID data and the second ID data. A communication circuit of the system may be situated adjacent to the wall of the room. The communication circuit may be coupled to the transponder reader and may be coupled to the third RF communication module. The communication circuit may be configured to receive the first and second ID data from the transponder reader and to receive the third ID data from the second RF communication module. The communication circuit may pair the first and second RF communication modules with the third RF communication module so that the third RF communication module only accepts communication packets from the first communication module or the second communication module.
In some embodiments, the third RF communication module may be configured to assess signal strength of the wireless transmissions from the first and second RF communication modules and to communicate only with the first or second RF communication module that may have greater signal strength. Thus, the third RF communication module may operate as a master and the first and second RF communication modules may each operate as a slave. If the third RF communication module is unable to communicate with the first and second RF communication modules, then an alarm may be triggered by the third RF communication module.
In some embodiments, the bed may further include a Wi-Fi communication module. The first and second RF communication modules and the Wi-Fi communication module may be controlled so as to send wireless transmissions in different, non-overlapping time slots. The communication circuit may be configured to send the bed data received via the third RF communication module to a remote computer device.
The system may further include a data cable which may extend from the bed and which may be coupleable to the communication circuit. The communication circuit may receive the bed data transmitted by the bed over the data cable when the communication circuit is coupled to the data cable. The communication circuit may be configured to cease accepting bed data from the third RF communication module and to accept the bed data transmitted over the data cable. The bed may include a first siderail and a second siderail. The first RF communication module may be coupled to the first siderail and the second RF communication module may be coupled to the second siderail.
In the system having the first, second and third communication modules, the transponder may comprise an RFID tag such as one molded into a plug body of the power cord or on a label attached to the power cord. In such a system, the transponder reader may comprises a loop antenna such as one that may be located adjacent a power outlet to which the power cord couples.
Still further according to this disclosure, a bed-to-room association system may comprise a bed that may have a power cord that may carry a first RFID component and a receptacle module that may carry a second RFID component. The receptacle module may have a receptacle into which the power cord may plug to receive power and to bring the first and second RFID components into communicative proximity. The receptacle module may have an indicator that may be activated in response to successful communication being established between the first and second RFID components.
In some embodiments, the indicator may comprise a light. The light may comprise a light ring, for example. The light ring may surround the receptacle. The first RFID component may comprise one of an RFID tag and an RFID reader and the second RFID component may comprise another of the RFID tag and RFID reader.
Also according to this disclosure, an apparatus for communicating with a nurse call system of a healthcare facility may be provided. The apparatus may include a bed that may have a first transceiver for wireless communication of bed identification (ID) data and bed status data. The apparatus may also include a handheld pillow speaker unit that may have a second transceiver in wireless communication with the first transceiver. The pillow speaker unit may be in hardwired communication with the nurse call system. Thus, the pillow speaker unit may serve as a communication intermediary between the bed and the nurse call system.
In some embodiments, the apparatus may further include an interface unit that may be fixed with respect to a wall in a patient room. The pillow speaker unit may have a cable with a plug that may plug into the interface unit. The interface unit may be communicatively coupled to the nurse call system.
The pillow speaker unit may include a first set of user inputs that may be used to control at least one of the following: a television, a room light, and at least one window shade. The bed may include a second set of user inputs that may be used to control at least one of the following: the television, the room light, and the at least one window shade.
In some embodiments, use of the second set of user inputs may be communicated from the first transceiver of the bed to the second transceiver of the pillow speaker unit. Thus, the pillow speaker unit may include user inputs that are used to control bed functions.
It is contemplated by this disclosure that the pillow speaker unit may include a set of manual buttons and a touchscreen graphical display that displays electronic buttons. The manual buttons may include at least one of the following: a nurse call button, a reading light button, and a room light button. The manual buttons may further include at least one of the following: a television control button, a radio control button, and a telephone dial pad button. The electronic buttons may include buttons that may be used to send distinct preprogrammed messages to at least one caregiver. At least one of the manual buttons and at least one of the electronic buttons may control a same function.
According to a further aspect of the present disclosure, a pillow speaker unit that may communicate with a nurse call system in a healthcare facility is provided. The pillow speaker unit may include a handheld housing, a set of manual buttons that may be accessible on the housing, and a touchscreen graphical display that may display electronic buttons. At least one of the manual buttons and at least one of the electronic buttons may be usable to send a respective signal to the nurse call system. The pillow speaker unit may include the features discussed previously.
Additional features, which alone or in combination with any other feature(s), such as those listed above and/or those listed in the claims, 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:
Throughout
While circuitry 22 is shown in the various figures as a single diagrammatic block, it should be understood that the single block is intended to represent all of the circuitry found on a patient bed and such circuitry may be embodied in separate, but interconnected, modules and/or circuit boards. In other words, circuitry 22 of patient bed 20 comprises a large complex circuit. See, for example, “Service Manual, Progressa™ Bed From Hill-Rom,” © 2013, Hill-Rom Services, Inc.; “Service Manual, TotalCare® Bed System From Hill-Rom,” © 2008, Hill-Rom Services, Inc.; and “Service Manual, VersaCare® Bed From Hill-Rom,” 2008, Hill-Rom Services, Inc.; each of which is hereby incorporated by reference herein. See also U.S. Pat. Nos. 5,771,511 and 7,506,390, each of which is hereby incorporated by reference herein.
Furthermore, network 24 (aka Ethernet 24 in
The various embodiments disclosed herein relate to systems and methods for making bed-to-room associations in a healthcare facility. This is accomplished by associating a bed identifier (ID) and a location identifier (ID) in a database of a computer device 26, such as a server or other computer. The term “room” in the phrase “bed-to-room” is intended to include not just patient rooms, but also hallways, service areas, supply rooms, elevators, cleaning rooms, and any other location in a healthcare facility which may be occupied by a bed. In each of the embodiments disclosed herein, other types of data may also be associated with the bed and/or room in the database, such as a patient ID, bed status data, data from other types of medical equipment (e.g., IV pumps, therapy equipment, vital signs equipment, and so forth), and data from other medical systems (e.g., electronic medical records (EMR) system, admission/discharge/transfer (ADT) system, pharmacy system, laboratory system, and so forth). Thus, patient-to-room; patient-to-bed; and patient-to-bed-to-room systems and methods are contemplated herein. It should also be appreciated that the order of association makes no difference and that “bed-to-room” and “room-to-bed” associations mean the same thing and that “patient-to-bed-to-room” and “room-to-patient-to-bed” associations mean the same thing, just to give a couple examples.
Referring now to
The light emitted from screens 32, 34 is visible light that has a signature 36 (indicated diagrammatically via a square wave). The signature 36 is unique for the location occupied by the bed 20. That is, the signature of the light emitted from screens 32, 34 is different for different rooms. Circuitry 30 is coupled to sensor 30 and analyzes the emitted light to determine its signature 36. In some embodiments, sensor 30 comprises a camera and in other embodiments, sensor 30 comprises a red-green-blue (RGB) image sensor chip. The signature 36 is emitted at a specified wavelength and/or at a specified pulsed frequency. The pulsed frequency is sufficiently large and/or the wavelength is sufficiently short in duration so as to be imperceptible to human vision. The specified wavelength and/or the specified pulse frequency is unique to each room. Thus, by analyzing the emitted light to determine the signature 36, data corresponding to the signature 36 is usable to determine the location of bed 20 in the associated healthcare facility.
Circuitry 22 commands transmitter 28 to transmit data corresponding to the signature and also commands transmitter 28 to transmit a bed identifier (ID) to at least one remote computer device 26 via a network 24. Typically, the data corresponding to the signature and the bed ID are included in the same message packet. The remote computer device 26 then makes the bed-to-room association based on the data corresponding to the signature and the bed ID. Thus, the remote computer device 26 includes a table or other similar type of relational database that correlates the data corresponding to the signature with a particular location, such as a patient room number, in the healthcare facility.
Referring now to
In some embodiments, bulbs 38a-e are high-power white LED lightbulbs that are programmable to emit a specified wavelength at a specified pulsed frequency. For example, bulbs 38 are programmable to emit different percentages of blue, red and green light (e.g., 11% blue, 30% red, and 59% green) which still appear generally as white light. In some embodiments, the bulb 38a-e in each room emit the same percentage of blue, red and green light, but at a different pulsed frequency for each room. In some embodiments, sensor 30 is embodied as a simple photovoltaic sensor and the unique light signatures are created by varying a power duty cycle of the associated light source without regard to wavelength. For example, the light source is turned on and off (e.g., flickered) at a specified frequency which is imperceptible to human vision but which is unique to each room.
Suitable programmable bulbs 38a-e are available from ByteLight of Boston, Mass. See also, U.S. Pat. Nos. 8,520,065; 8,457,502; 8,436,896; 8,432,438; 8,416,290; 8,334,901; 8,334,898; and 8,248,467; each of which is hereby incorporated by reference herein.
In some embodiments, in order to enable locating to take place in rooms that have the light source turned off, a source of infrared (IR) light is emitted with a signature and sensed by sensor 30. The processing thereafter is the same as described above with regard to signatures included in the light emitted from screens 32, 34 and bulbs 38a-e. The IR light pulses, in some embodiments, are at a lower frequency which is possible because IR light is not visible to humans anyway. Thus, a visible light signature and an IR light signature may each indicate the same room, although their pulsed frequencies are different. In other embodiments, the IR light pulses are at the same pulsed frequency as the visible light pulses. In any event, it should be understood that the IR light signatures are different from room to room.
A lower amount of power is used to drive the IR light sources when the light sources of visible and IR light are in night mode. While it is possible for the IR light source to be separate from the light sources described above, it is contemplated by this disclosure that the IR light source is included in the same light source that emits visible light when in the on state. In such embodiments, when the visible light source is turned on, some of the applied power is stored in a battery or capacitor or other energy storage device and is used to drive the IR light source after the visible light source is turned off. In some embodiment, therefore, the IR light source only operates when the visible light is turned off. In other embodiments, the IR light source operates all the time.
In some embodiments, bed 20 includes two sensors 30, one for the visible light and one for the IR light. However, combined RGB and IR image or light sensors are known in the art. See, for example, U.S. Patent Application Publication No. 2010/00289885 which is hereby incorporated by reference herein. Such a device or similar such devices may be used as the sensor 30 of bed 20 if desired.
Referring now to
Referring now to
Although only one row is included in the array 44 of
Referring now to
In response to a caregiver selecting change button 64 on GUI 60, a keypad 66 appears on the GUI 60. The text “Enter Room Number” appears above keypad 66 in the illustrative example to suggest to the caregiver that a new room number be entered into the memory of circuitry 22 to replace the old room number. In the illustrative example, keypad 66 includes buttons having numbers 0-9 arranged in similar manner as a standard telephone, a back button 68, an enter button 70, and cancel button 72. In other embodiments an alphanumeric keyboard is provided to permit the user to indicate whether the bed is at an “A” location or a “B” location in a semi-private room for example.
Keypad 66 is used by a caregiver to enter the room number in which bed 20 is located into the memory of circuitry 22 of bed 20. Circuitry 22 of bed 20 then transmits the room number in any suitable format along with the bed ID to one or more remote computer devices 26 via network 24. Thus, the room number manually entered by the user or caregiver serves as the location ID for the respective bed 20. Bed 20 does not rely on any external device or artifact (e.g., light source, locator unit, bar code label, etc.) for obtaining the location ID to be transmitted from the bed 20. Accordingly, the embodiment of
In the example of
Referring now to
In response to selection of the desired unit from unit menu 74 of
In response to selection of the desired room from room menu 76 of
Referring now to
After bed 20 queries server 26 for the existence of the association database, bed 20 proceeds to block 98 and determines whether the bed 20 is associated with a location, which in this example means the bed 20 is associated with a unit and a room. If there is no bed-to-location association in the database, then bed 20 proceeds to block 100 and the screen of
If at block 106, the caregiver selects the Try again button 82, bed 20 proceeds back to block 100 as indicated in
If at block 98 bed determines that it is associated with a location in the association database, bed 20 proceed to block 112 and determines how long the bed 20 experienced the AC power loss, such as being unplugged. As indicated at block 114, if the power loss was less than two minutes, then bed proceeds to block 110 and the prior bed-to-location association is maintained. If the power loss was more than two minutes, as determined at block 114, then Confirm Association screen 78 of
Referring now to
It is contemplated by this disclosure that the first circuitry of tag 118 transmits the first ID and the location ID using a first wireless transmission technology and that the second circuitry, here circuitry 22 of bed 20, transmits the bed ID and the bed status data using a second wireless transmission technology that is different than the first wireless transmission technology. For example, the first wireless transmission technology may comprise one of infrared (IR) technology, radio frequency (RF) technology, and ultrasonic (US) technology and the second wireless transmission technology comprises a different one of IR technology, RF technology, and ultrasonic technology.
Referring now to
According to this disclosure, the modified ID created by bed translation software 136 may also be in a more desirable format for receipt by other computer devices 26. For example, if location IDA is a MAC address of locator unit 130, administrators of a healthcare facility may prefer to receive from bed 20 ASCII code of the room number for use in various other software programs on computer devices 26. Translation software 136, therefore, permits modified ID to be converted into the desired format. Computer devices(s) 26, therefore, operate to associate the bed ID and modified ID in an association database and make no use of location IDA.
Referring now to
The mutation software 140, in some embodiments, uses a hash function, such as a cryptographic hash function, to mutate the location ID and the bed ID into the single, unique mutated ID. The one or more remote computer devices 26 then use ID decoding software 142 to correlate the mutated ID with the location ID and the bed ID. However, it should be appreciated that neither the location ID nor the bed ID were ever transmitted by the bed 20 to any device on the network 24.
To illustrate the method employed by software 140, consider the scenario in which location ID is in the form ROOM_ID_0001 and the bed ID is in the form BED_ID_0001. The software may add the location ID and the room ID and perform the hashing function by using software programming code such as SHA1(ROOM_ID_0001+BED_ID_0001) and the resulting mutated ID, in hexadecimal format, is the following: 57e4f41a507079311acbb588d14cae4d564c7d43. While this example used the known SHA-1 hashing function, other known hashing functions may be employed in software 140, including the following: GOST, HAVAL, MD2, MD4, MD5, PANAMA, RadioGatun, RIPEMD, SHA-0, SHA-3, Tiger(2), and WHIRLPOOL.
Once the modified ID is created by the adding and hashing operation just described, the modified ID is transmitted off of the bed for receipt by one or more remote computer devices 26. The software 142 of each remote computer device 26 then uses a lookup table, in some embodiments, to correlate the received modified ID with the bed ID and room ID that created it. The lookup table includes the modified ID's and the associated bed ID and room ID for each possible combination of beds and rooms in a particular healthcare facility. An simple example of a lookup table for two beds that may be located in two different rooms is given as follows (and assumes a hashing function applied to the added room ID and bed ID as described above):
Thus, if a bed with BED_ID_0001 as its bed ID is physically located in a room with ROOM_ID_0002 as its room ID, then bed 20 transmits via network 24 the modified ID bf2019c988268cd007ef7dcb0a280d1e75c8dd45 to the remote computer device 26 having software 142 and the software correlates the modified ID back to the room ID and bed ID that created it. However, neither the bed ID nor the room ID is transmitted by bed 20.
In an alternative embodiment, software 142 uses a list of all known bed ID's and a list of all known room ID's and the server computes the modified ID's (e.g., by adding and hashing) sequentially and compares each one to the received modified ID until a match is found, at which the point the bed ID and room ID that caused the match are known. This approach eliminates the need to store a large table of known combinations, but does potentially require a fair amount of computational power to perform the mutating operation sequentially.
In another contemplated embodiment, the bed only transmits a received or entered (e.g., via GUI 60) location ID along with other data such as bed status data. Thus, the bed ID is not transmitted off of the bed while the bed is in use. In such embodiments, the location ID is considered to be the bed ID while the bed is in the room associated with the room ID. In such embodiments, the bed may store in a database of circuitry 22 the room ID along with the start and end times at which the bed considered that particular room ID to be the bed ID. The start and end times include, for example, minutes, hours, day, month, and year. For many systems and software applications used in a healthcare environment, the end users are not interested in knowing the bed ID anyway. They are more interested in knowing which device status data goes with which patient. This can be accomplished in many instances by associating location ID, patient ID, and device status ID. In this regard, device status ID may include the patient's physiological data as measured by a particular device. Manufacturers are more interested in knowing bed ID for service and maintenance purposes. Thus, at a later time, a service technician downloads the bed ID along with the rooms in which the bed was located in the past. Appropriate data analysis is made by the service technician after the download.
Referring now to
Module 150 has a second LED 162 that is illuminated to indicate that a successful communication link has been established between circuitry 22 (not shown in
In one embodiment, circuitry 166 of module 150 includes a Model No. WB45NBT device available from Laird Technologies of Earth City, Mo. Details of the Model No. WB45NBT device can be found in Laird Reference Manual, Laird WB45NBT, Version 1.0, dated Aug. 20, 2013, which is hereby expressly incorporated by reference herein. Circuitry 166 of module 150 connects to circuitry 22 of bed 20 via a universal serial bus (USB) cable in some embodiments. In such embodiments, therefore, circuitry 22 and circuitry 166 each include a USB port. In other embodiments, circuitry 166 of module 22 and circuitry 22 of bed 20 communicate wirelessly. Circuitry 166 controls the illumination of LED's 160, 162, 164 via shift registers in some embodiments. Circuitry 166 includes a Wi-Fi antenna and/or a Bluetooth (BT) antenna in some embodiments. For example, a suitable antenna for either or both of these purposes is the Laird Model No. 95310 antenna. In some embodiments contemplated by this disclosure, circuitry 22 of bed 20 does not have wireless communication capability but instead relies on the wireless communication capability of circuitry 166 of module 150 to communicate bed data wirelessly to and from network 24 via wireless access point 124.
In some embodiments of the systems illustrated in
In alternative embodiments, RF triangulation is used to locate bed 20 in a healthcare facility. In such embodiments, tag 118, location unit 120 and transceiver 122 are omitted. Instead, multiple (typically three or more) Wi-Fi transceivers, such as wireless access points 124, receive wireless transmissions from bed 20 and then a remote computer device, such as one of servers 26a, 26b, analyzes signal strength and or time-of-flight information from the multiple wireless access points 124 to determine the location of bed 20. Once the location has been determined, bed 20 is notified wirelessly and indicator 164 of module 150 is illuminated.
Referring now to
As shown diagrammatically in
Still referring to
Wi-Fi module 150′ of bed 20 sends a Wi-Fi signal, as indicated at block 182, that includes bed ID data 184. It should be appreciated that bed 20 also transmits bed status data along with bed ID 184. Bed status data includes bed frame data such as siderail position data, caster brake position data, lift system data, head of bed angle data, weigh scale system data, bed exit system data, motor lockout data, and the like; support surface data such as therapy mode data, maximum inflate data, turn assist data, and the like; and other data such as battery charge data, AC present/not present data, nurse call button data, and the like. For a more exhaustive list of bed status data that may be associated with bed 20, see U.S. Patent Application Publication No. 2013/0135160 which is hereby incorporated by reference herein in its entirety to the extent not inconsistent with this disclosure which shall control as to any inconsistencies.
The bed status data and bed ID are received by server 26b and are processed by bed data aggregator software 186 as indicated diagrammatically in
Server 26a and/or server 26b stores information or has access to information that correlates the bed ID with the tag ID. Such information is entered into server 26a, 26b in connection with assigning tags 118 to the various beds 20 in some embodiments. Thus, the information correlating tag ID and bed ID is included in database table 180 in some embodiments. Furthermore, it will be appreciated that the monitor ID from each location beacon 120 corresponds to a particular location (e.g., room) of a healthcare facility. Accordingly, the bed status data that is transmitted with bed ID 184 is able to be associated with a particular location at which bed 20 is located due to the correlation of monitor ID with the tag ID of bed 20 and the correlation of the tag ID with the bed ID. These various correlated relationships are maintained in database 180 in some embodiments. The bed status data is also included in database 180 in some embodiments.
According to this disclosure, after the monitor ID, tag ID, and bed ID are correlated by server 26b, a prospective or preliminary bed-to-room association is considered to exit. However, before the bed-to-room association is considered to be finalized, server 26b determines whether a power plug 188 of power cord 190 of bed 20 is coupled into a receptacle 192 to receive AC power therefrom. The act of connecting plug 188 into receptacle 192 permits the inference to be drawn that bed 20 is likely to remain at the particular location for an extended period of time rather than simply being in transit or only temporarily at the location for a short period of time. If server 26b determines that the bed status data indicates that bed 20 is receiving AC power from receptacle 192, then location information 194 is transmitted to Wi-Fi module 150′ to indicate a successful or finalized bed-to-room association has been made.
Referring now to
As indicated at block 200, server 26b looks for location ID associated with bed 20. The location ID referenced in block 200 includes, for example, monitor ID 170 or a room number or other location name or number that correlates to monitor ID 170. If at block 202, server 26b does not find a location ID that is associated with bed 20, then the algorithm 196 loops back to block 200. It will be appreciated that, if algorithm remains in the block 200, 202 loop for a predetermined period of time or for a predetermined number of iterations, the software will exit from the loop and send an alarm message or return to some other portion of algorithm 196 or another algorithm.
If server 26b finds the location ID for bed 20 at block 202, server 26b proceeds to block 204 to check the bed status message for “AC present” data which means that the plug 188 of power cord 190 of bed 20 is plugged into receptacle 192. As indicated at block 206, if server 26b does not find AC present, then the algorithm 196 loops back to block 204. It will be appreciated that, if algorithm remains in the block 204, 206 loop for a predetermined period of time or for a predetermined number of iterations, the software will exit from the loop and send an alarm message or return to some other portion of algorithm 196 or another algorithm.
If server 26b finds AC present at block 206, server 26b proceeds to block 208 and sends a message to bed 20, including the Location or Room ID 194, to indicate that bed 20 has been successfully located. Thereafter, bed 20 indicates a successful bed-to-room location by displaying the location ID (e.g., room name or number) on a graphical display screen of bed 20 or by otherwise indicating a successful bed-to-room location such as by illuminating indicator 164 of module 150 as discussed above in connection with
Referring now to
Referring now to
Circuitry 226 of heart rate monitor 224 is programmable with the patient's MRN. For example, such programming may occur upon admittance of the patient to a healthcare facility. In some embodiments, circuitry 226 includes a Bluetooth module for communication of wireless data via the Bluetooth protocol. A suitable heart rate monitor is the Wahoo Blue TICKR monitor available from Wahoo Fitness of Atlanta, Ga. In the illustrative example of
Alternatively or additionally, monitor ID data of heart rate monitor 224 is mapped or correlated with the patient's ID data in a database, such as in a database of RTLS server 26a or in database table 180 of server 26b or some other server such an ADT server. The monitor ID data is transmitted wirelessly from monitor 224 to bed 20 and then sent wireless from the bed 20 along with the bed ID data as indicated diagrammatically by arrow 228 in
Referring now to
By using modules 232, 234, 236, the traditional bed status or nurse call cable (e.g., a 37-pin connector cable) between bed 20 and a nurse call module 244 is eliminated. Thus, the power cord 240 is the only cord that connects to, and disconnects from, an associated receptacle. The bed data is communicated wirelessly from one or both of modules 232, 234 to module 236. In the illustrative example of
In the illustrative embodiment, wall Bluetooth module 236 communicates with modules 232, 234 via radio frequency (RF) signals according to the Bluetooth protocol which operates on an unlicensed 2.4 gigahertz (GHz) band which is also shared with Wi-Fi and other protocols. To be more specific, the Bluetooth protocol implements an adaptive frequency hopping (AFH) methodology to transmit at any of 79 hopping channels that are 1 megahertz (MHz) apart between 2.4 GHz and 2.4835 GHz. Thus, in addition to receiving wireless signals from modules 232, 234 of bed 20, it is foreseeable that wall BT module 236 will be within the reception range of other devices, including other beds 20, and receive the wireless signals transmitted by those other devices. So, in order to pair module 236 with one or both of modules 232, 234, a loop antenna 256 is provided to read signals sent from transponder 23 as indicated diagrammatically at block 258 in
If module 232 is the only module on bed 20, then in response to power cord 240 being plugged in, loop antenna 256 is powered up by communication circuit 248 and reads the first module ID from transponder 238 to communication circuit 248. Communication circuit then provides the first module ID to wall BT module 236. In some embodiments, the first module ID corresponds to a unique 48 bit Bluetooth device address (aka the MAC address) of module 232. The first 24 bits of this address represent the manufacturer of the Bluetooth circuitry of module 232 and the remaining 24 bits are unique for each Bluetooth device assigned by the manufacturer. However, any unique module ID would suffice. After receiving the first module ID, wall BT module 236 then operates to accept wireless transmissions from only module 232 and to ignore all other wireless transmissions. In this regard, module 236 accepts wireless transmission packets that contain the first module ID. This is sometimes referred to as an Out of Band (OOB) pair between modules 232, 236.
The transmission packets sent between modules 232, 236 include both audio and data packets in some embodiments. For example, Bluetooth technology is rated for 3 Mega bits per second (Mbps) transmission speed, but in practice the speed is about 2.1 Mbps, which is fast enough to permit audio and data packets to be sent. The delay in the audio signal using Bluetooth technology is about 50 to about 80 milliseconds (ms) which is less than the 100 ms delay required to synchronize television video and audio. Thus, modules 232, 236 of the system in
If power cord 240 is unplugged, loop antenna 256 no longer provides the first module ID to communication circuit 248 and communication circuit 248 notifies wall BT module 236 to break its pairing with module 232 of bed 20. During the communication between module 232, 236, module 236 operates as a “master” module such as by controlling the frequency hopping channels over which communications with module 232 occur, and module 232, therefore, operates as a “slave.”
If modules 232, 234 are both present on bed 20, then in response to power cord 240 being plugged in, loop antenna 256 is powered up by communication circuit 248 and reads the first module ID and the second module ID from transponder 238 to communication circuit 248. Communication circuit then provides the first module ID and the second module ID to wall BT module 236. Module 236, acting as a “master,” assesses the signal strength of the communications from modules 232, 234 and chooses to communicate with the “slave” (i.e., one or the other of modules 232, 234) that has lower RF interference based on received signal strength indicator (rssi) and channel map. If communication with the chosen slave is lost at any time after the master-slave relationship between module 236 and one of modules 232, 234 is established, module 236 jumps or switches the communication over to the other of modules 232, 234 if the RF interference with the other of modules 232, 234 is acceptable. In some embodiments, if the master module 236 is unable to communicate with both slave modules 232, 234, then at least one of modules 232, 234, 236 triggers an audible and/or visual alarm.
In the illustrative embodiment, module 232 is on one side of bed 20 and module 234 is on the other side of bed 20. For example, module 232 is coupled to a right siderail of bed 20 and module 234 is coupled to a left siderail of bed 20 in some embodiments. It is contemplated by this disclosure that bed 20 may include an additional Wi-Fi module such as, for example, modules 150, 150′ discussed above. It is preferable to place the Wi-Fi module on bed 20 as far from modules 232, 234 as possible since Wi-Fi operates in in the same frequency band as Bluetooth. However, placing the additional Wi-Fi module at the head end of bed 20 between modules 232, 234 at the sides of bed 20 is sufficient. It is contemplated by this disclosure that the first and second BT modules 232, 234 communicate in different time slots than the additional Wi-Fi module communicates. Thus, when either of the modules 232, 234 are turned on, the additional Wi-Fi module is turned off and vice versa. Thus, the time slots of transmission are non-overlapping time slots.
Referring now to
Referring now to
Referring now to
A second AC power cord 240b has its transponder 238 embodied as an RFID tag included in a label 282 as indicated at diagrammatic block 284 in
Active and passive transponders 238 (e.g., RFID tags) are contemplated by this disclosure. For example, transponder 238 of label 282 is a passive transponder whereas transponder 238 of plug body 272 is an active transponder that is powered by a 5 Volt (V) or 3.3 V power supply of bed 20. As shown in
In some embodiments, transponder 238 is an RFID tag having an EEPROM which is programmed by bed circuitry 22, such as by using a multipoint control unit (MCU), via a serial peripheral interface (SPI) protocol or Inter-Integrated Circuit (I2C) protocol. For the passive transponder 238, the first and second module ID's are written to memory wirelessly. In some embodiments contemplated by this disclosure, transponders 238 are programmed in an active mode, such as via conductors 296, 298, and then operate in a passive mode when loop antenna 256 is reading the module ID's from the transponder 238. In such embodiments, loop antenna 256 is energized by communication circuit 248 and transfers energy to transponder 238 that is used by the transponder to transmit the first and second module ID's fro reception by antenna 256.
Referring now to
In a first scenario for determining a successful bed-to-room association, RFID component 306 includes a reader that receives bed ID data from RFID component 300 when power cord 240a is plugged in with prongs 278, 279, 280 being received by receptacle 308 of module 302. After RFID component 306 receives the bed ID data from RFID component 300, module 302 sends room ID data to the circuitry 22 of the bed 20 that is designated with the bed ID data using wireless transmission circuitry included in module 302. In some embodiments, the wireless communication circuitry of module 302 operates according to the Bluetooth protocol. In such embodiments, bed 20 includes Bluetooth circuitry. Bed 20 receives the room ID data and then transmits the bed ID data and the room ID data using a Wi-Fi transmitter of circuitry 22. Bed 20 also transmits a Bluetooth message back to the circuitry of module 302 to confirm the bed-to-room association. In response to that message, module illuminates light-up ring 312. Ring 312 is illuminated green in some embodiments.
In a second scenario for determining a successful bed-to-room association, RFID component 306 includes a passive RFID tag and RFID component 300 comprises a reader that receives power from conductors 296, 298 of cord 240a. RFID component 300 senses RFID component 306 when cord 240a is plugged into module 302 and reads room ID data that is encoded in RFID component 306. RFID component 300 then sends the room ID data to circuitry 22 of bed 20 via wired connection, such as one or both of conductors 296, 298. Bed 20 then transmits the bed ID data and the room ID data using a Wi-Fi transmitter of circuitry 22. In this scenario, module 302 receives a Wi-Fi signal or other wireless signal once a successful bed-to-room association is made (either at bed 20 or at a remote computer device, such as servers 26a, 26b) and the circuitry of module 302 turns on the light-up ring 312 to indicate the successful bed-to-room association.
Referring now to
Pillow speaker unit 320 is coupled via a wired power and data connection to a nurse call interface 330 as indicated by diagrammatic double headed arrow 328. Nurse call interface 330 is coupled to nurse call system 322 as indicated by diagrammatic double headed arrow 332. Nurse call interface 330 is also coupled to a television (TV) 334, room lights 336, and window shades 338 as indicated by diagrammatic arrows 340, 342, 344, respectively. Pillow speaker unit 320 has user inputs 350 that are used to control functions of TV 334, lights 336, shades 338, and bed 20. Bed 20 has user inputs 352 that are also used to control functions of TV 334, lights 336, shades 338, and bed 20. Thus, when user inputs 350 of unit 320 are used to control bed 20, control signals from unit 320 are communicated to transceiver 150″ wirelessly from circuitry 314 of unit 320. Similarly, when user inputs 352 of bed 20 are used to control TV 334, 336, 338, control signals from bed 20 are communicated from transceiver 150″ wirelessly to circuitry 314 of unit 320. A pairing operation, such as the pairing operation described above in connection with
Referring now to
In some embodiments, the touchscreen buttons 354 of GUI 350b have the functionality described in U.S. application Ser. No. 14/177,851, which was filed Feb. 11, 2014, which is titled “Workflow Canvas for Clinical Applications,” and which is hereby incorporated by reference herein to the extent not inconsistent with the present disclosure which shall control as to any inconsistencies. In general, each button 354 is selected to send a specific message to an assigned caregiver. Such messages, for example, indicate that the patient needs to go to the bathroom, that the patient wants water, that the patient is in pain, that there is a problem with an intravenous (IV) pump or liquid, that there is a problem with a catheter, or that there is a problem with other equipment, such as bed 20. This list of messages is not intended to be exhaustive but merely to give a few examples. GUI 350b also permits a user to navigate to screens for controlling bed functions in some embodiments.
Referring now to
It will be appreciated that units 320, 320′ of
Each of the embodiments disclosed herein can have features of one or more of each of the other embodiments. For example, the patient-to-bed association system of
Although certain illustrative embodiments have been described in detail above, variations and modifications exist within the scope and spirit of this disclosure as described and as defined in the following claims.
The present application is a continuation of U.S. application Ser. No. 14/487,279, filed Sep. 16, 2014, now U.S. Pat. No. 9,830,424, which claims the benefit, under 35 U.S.C. § 119(e), of U.S. Provisional Application No. 61/879,399, filed Sep. 18, 2013, and each of which is hereby incorporated by reference herein in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 1758546 | Wartmann | May 1930 | A |
| 2330356 | Belliveau | Sep 1943 | A |
| 2335524 | Lomax | Nov 1943 | A |
| 2736888 | McLain | Feb 1956 | A |
| 2896021 | Philipps | Jul 1959 | A |
| D188659 | Locke | Aug 1960 | S |
| 3054201 | Burns | Sep 1962 | A |
| 3098220 | De Graaf | Jul 1963 | A |
| 3181141 | Villiers | Apr 1965 | 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 |
| 3659586 | Johns et al. | May 1972 | A |
| 3696384 | Lester | Oct 1972 | A |
| 3739329 | Lester | Jun 1973 | A |
| 3767859 | Doering et al. | Oct 1973 | A |
| 3805227 | Lester | Apr 1974 | A |
| 3805265 | Lester | Apr 1974 | A |
| 3810136 | Lang et al. | May 1974 | A |
| 3913153 | Adams et al. | Oct 1975 | A |
| 3973200 | Åkerberg | Aug 1976 | A |
| 4052567 | MacKay | Oct 1977 | A |
| 4067005 | Levy et al. | Jan 1978 | A |
| 4126768 | Grenzow | Nov 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 |
| 4224596 | Knickel | Sep 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 |
| 4363029 | Piliavin et al. | Dec 1982 | A |
| 4363137 | Salisbury | Dec 1982 | A |
| 4418334 | Burnett | Nov 1983 | A |
| 4455548 | Burnett | Jun 1984 | A |
| 4489387 | Lamb et al. | Dec 1984 | A |
| 4491947 | Frank | Jan 1985 | A |
| 4495495 | Ormanns et al. | Jan 1985 | A |
| 4495496 | Miller, III | Jan 1985 | A |
| 4532419 | Takeda | Jul 1985 | A |
| 4539560 | Fleck et al. | Sep 1985 | A |
| 4556932 | Lehrer et al. | Dec 1985 | A |
| 4577060 | Webb et al. | Mar 1986 | A |
| 4577185 | Andersen | Mar 1986 | A |
| 4578671 | Flowers | Mar 1986 | A |
| 4593273 | Narcisse | Jun 1986 | A |
| 4598275 | Ross et al. | Jul 1986 | A |
| 4601064 | Shipley | Jul 1986 | A |
| 4638313 | Sherwood, Jr. et al. | Jan 1987 | A |
| 4648123 | Schrock | Mar 1987 | A |
| 4649385 | Aires et al. | Mar 1987 | A |
| 4654629 | Bezos et al. | Mar 1987 | A |
| 4663625 | Yewen | May 1987 | A |
| 4677599 | Obayashi et al. | Jun 1987 | A |
| 4680790 | Packard et al. | Jul 1987 | A |
| 4688026 | Scribner et al. | Aug 1987 | A |
| 4699149 | Rice | Oct 1987 | A |
| 4706689 | Man | Nov 1987 | A |
| 4709330 | Yokoi et al. | Nov 1987 | A |
| 4740788 | Konneker | Apr 1988 | A |
| 4748668 | Shamir et al. | May 1988 | A |
| 4752951 | Konneker | Jun 1988 | A |
| 4792798 | Wilowski | Dec 1988 | A |
| 4795905 | Zierhut | Jan 1989 | A |
| 4803599 | Trine et al. | Feb 1989 | A |
| 4814751 | Hawkins et al. | Mar 1989 | A |
| 4833452 | Currier | May 1989 | A |
| 4833467 | Kobayashi et al. | May 1989 | A |
| 4835372 | Gombrich et al. | May 1989 | A |
| 4837568 | Snaper | Jun 1989 | A |
| 4839975 | Elmer | Jun 1989 | A |
| 4843640 | Juengel | Jun 1989 | A |
| 4849615 | Mallet | Jul 1989 | A |
| 4853692 | Wolk et al. | Aug 1989 | A |
| 4857716 | Gombrich et al. | Aug 1989 | A |
| 4862088 | Etienne et al. | Aug 1989 | A |
| 4871997 | Adriaenssens et al. | Oct 1989 | A |
| 4899135 | Ghahariiran | Feb 1990 | A |
| 4947152 | Hodges | Aug 1990 | A |
| 4955000 | Nastrom | Sep 1990 | A |
| 4958645 | Cadell et al. | Sep 1990 | A |
| 4967195 | Shipley | Oct 1990 | A |
| 4980679 | Klaubert | Dec 1990 | A |
| 4990892 | Guest et al. | Feb 1991 | A |
| 4998095 | Shields | Mar 1991 | A |
| 4998939 | Potthast et al. | Mar 1991 | A |
| 5005005 | Brossia et al. | Apr 1991 | A |
| 5006830 | Merritt | Apr 1991 | A |
| 5014040 | Weaver et al. | May 1991 | A |
| 5027314 | Linwood et al. | Jun 1991 | A |
| 5031156 | Watts et al. | Jul 1991 | A |
| 5041086 | Koenig et al. | Aug 1991 | A |
| 5062151 | Shipley | Oct 1991 | A |
| 5065154 | Kaiser et al. | Nov 1991 | A |
| 5079808 | Brown | Jan 1992 | A |
| 5086290 | Murray et al. | Feb 1992 | A |
| 5103108 | Crimmins | Apr 1992 | A |
| 5119104 | Heller | Jun 1992 | A |
| 5124991 | Allen | Jun 1992 | A |
| 5131040 | Knapczyk | Jul 1992 | A |
| 5137033 | Norton | Aug 1992 | A |
| 5153584 | Engira | Oct 1992 | A |
| 5164886 | Chang | Nov 1992 | A |
| 5164985 | Nysen et al. | Nov 1992 | A |
| 5217003 | Wilk | Jun 1993 | A |
| 5231273 | Caswell et al. | Jul 1993 | A |
| 5266944 | Carroll et al. | Nov 1993 | A |
| 5274311 | Littlejohn et al. | Dec 1993 | A |
| 5276496 | Heller et al. | Jan 1994 | A |
| 5283781 | Buda et al. | Feb 1994 | A |
| 5291399 | Chaco | Mar 1994 | A |
| 5317309 | Vercellotti et al. | May 1994 | A |
| 5319191 | Crimmins | Jun 1994 | A |
| 5319355 | Russek | Jun 1994 | A |
| 5319363 | Welch et al. | Jun 1994 | A |
| 5334851 | Good et al. | Aug 1994 | A |
| 5339259 | Puma et al. | Aug 1994 | A |
| 5341126 | Boykin | Aug 1994 | A |
| 5351149 | Crimmins | Sep 1994 | A |
| 5355222 | Heller et al. | Oct 1994 | A |
| 5357254 | Kah, Jr. | Oct 1994 | A |
| 5363425 | Mufti et al. | Nov 1994 | A |
| 5375604 | Kelly et al. | Dec 1994 | A |
| 5387993 | Heller et al. | Feb 1995 | A |
| 5396224 | Dukes et al. | Mar 1995 | A |
| 5396227 | Carroll et al. | Mar 1995 | A |
| 5402469 | Hopper et al. | Mar 1995 | A |
| 5416695 | Stutman et al. | May 1995 | A |
| 5421177 | Sieber et al. | Jun 1995 | A |
| 5434775 | Sims et al. | Jul 1995 | A |
| 5446678 | Saltzstein et al. | Aug 1995 | A |
| RE35035 | Shipley | Sep 1995 | E |
| 5455560 | Owen | Oct 1995 | A |
| 5455851 | Chaco et al. | Oct 1995 | A |
| 5458123 | Unger | Oct 1995 | A |
| 5461390 | Hoshen | Oct 1995 | A |
| 5465082 | Chaco | Nov 1995 | A |
| 5471404 | Mazer | Nov 1995 | A |
| 5475367 | Prevost | Dec 1995 | A |
| 5482036 | Diab et al. | Jan 1996 | A |
| 5515426 | Yacenda et al. | May 1996 | A |
| 5519380 | Edwards | May 1996 | A |
| 5534851 | Russek | Jul 1996 | A |
| 5534876 | Erickson et al. | 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 |
| 5572195 | Heller et al. | Nov 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 |
| 5627524 | Fredrickson et al. | May 1997 | A |
| 5629678 | Gargano et al. | May 1997 | A |
| 5633742 | Shipley | May 1997 | A |
| 5635907 | Bernard et al. | Jun 1997 | A |
| 5636245 | Ernst et al. | Jun 1997 | A |
| 5639393 | Veltum et al. | Jun 1997 | A |
| 5640002 | Ruppert et al. | Jun 1997 | A |
| 5640146 | Campana, Jr. | Jun 1997 | A |
| 5640953 | Bishop et al. | Jun 1997 | A |
| 5650769 | Campana, Jr. | Jul 1997 | A |
| 5650770 | Schlager et al. | Jul 1997 | A |
| 5661457 | Ghaffari et al. | Aug 1997 | A |
| 5664035 | Tsuji et al. | Sep 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 |
| 5687109 | Protigal et al. | Nov 1997 | A |
| 5687735 | 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 |
| 5708423 | Ghaffari et al. | 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 |
| 5742238 | Fox | Apr 1998 | A |
| 5745037 | Guthrie et al. | Apr 1998 | A |
| 5748148 | Heiser et al. | May 1998 | A |
| 5751246 | Hertel | May 1998 | A |
| 5752917 | Fuchs | May 1998 | A |
| 5754125 | Pearce | May 1998 | A |
| 5760704 | Barton et al. | Jun 1998 | A |
| 5764162 | Ehrlich | Jun 1998 | A |
| 5767788 | Ness | Jun 1998 | A |
| 5767791 | Stoop et al. | Jun 1998 | A |
| 5771003 | Seymour | Jun 1998 | A |
| 5776056 | Bu et al. | Jul 1998 | A |
| 5781442 | Engleson et al. | Jul 1998 | A |
| 5781632 | Odom | Jul 1998 | A |
| 5792063 | Danielsson et al. | Aug 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 |
| 5828306 | Curran | Oct 1998 | A |
| 5831533 | Kanno | Nov 1998 | A |
| 5838223 | Gallant et al. | Nov 1998 | A |
| 5838472 | Welch et al. | Nov 1998 | A |
| 5844488 | Musick | Dec 1998 | A |
| 5867821 | Ballantyne et al. | Feb 1999 | A |
| 5877675 | Rebstock et al. | Mar 1999 | A |
| 5878143 | Moore | Mar 1999 | A |
| 5897506 | Cohn | Apr 1999 | A |
| 5898459 | Smith et al. | Apr 1999 | A |
| 5910776 | Black | Jun 1999 | A |
| 5933488 | Marcus et al. | Aug 1999 | A |
| 5936527 | Isaacman et al. | Aug 1999 | A |
| 5936539 | Fuchs | Aug 1999 | A |
| 5942986 | Shabot et al. | Aug 1999 | A |
| 5944659 | Flach et al. | Aug 1999 | A |
| 5956660 | Neumann | Sep 1999 | A |
| 5963133 | Monjo | Oct 1999 | A |
| 5963137 | Waters, Sr. | Oct 1999 | A |
| 5973598 | Beigel | Oct 1999 | A |
| 5974389 | Clark et al. | Oct 1999 | A |
| 5991728 | DeBusk et al. | Nov 1999 | A |
| 5995937 | DeBusk et al. | Nov 1999 | A |
| 5997476 | Brown | Dec 1999 | A |
| RE36530 | Heller et al. | Jan 2000 | E |
| 6014633 | DeBusk et al. | Jan 2000 | A |
| 6026818 | Blair et al. | Feb 2000 | A |
| 6028514 | Lemelson et al. | Feb 2000 | A |
| 6031458 | Jacobsen et al. | Feb 2000 | A |
| 6031459 | Lake | Feb 2000 | A |
| 6031460 | Banks | Feb 2000 | A |
| 6034603 | Steeves | Mar 2000 | A |
| 6034622 | Levine | Mar 2000 | A |
| 6037879 | Tuttle | Mar 2000 | A |
| 6040773 | Vega et al. | Mar 2000 | A |
| 6049278 | Guthrie et al. | Apr 2000 | A |
| 6049290 | Halstead | Apr 2000 | A |
| 6052710 | Saliba et al. | Apr 2000 | A |
| 6054927 | Brickell | Apr 2000 | A |
| 6055487 | Margery et al. | Apr 2000 | A |
| 6055506 | Frasca, Jr. | Apr 2000 | A |
| 6057758 | Dempsey et al. | May 2000 | A |
| 6057782 | Koenig | May 2000 | A |
| 6067019 | Scott | May 2000 | A |
| 6069555 | Skitek et al. | May 2000 | A |
| 6069564 | Hatano et al. | May 2000 | A |
| 6069570 | Herring | May 2000 | A |
| 6075707 | Ferguson et al. | Jun 2000 | A |
| 6076166 | Moshfeghi et al. | Jun 2000 | A |
| 6078251 | Landt et al. | Jun 2000 | A |
| 6078259 | Brady et al. | Jun 2000 | A |
| 6078261 | Davsko | Jun 2000 | A |
| 6078631 | Yabe et al. | Jun 2000 | A |
| RE36791 | Heller | Jul 2000 | E |
| 6084512 | Elberty et al. | Jul 2000 | A |
| 6085069 | Sharpe | Jul 2000 | A |
| 6085493 | DeBusk et al. | Jul 2000 | A |
| 6088362 | Turnbull et al. | Jul 2000 | A |
| 6091332 | Eberhardt et al. | Jul 2000 | A |
| 6091530 | Duckworth | Jul 2000 | A |
| 6093146 | Filangeri | Jul 2000 | A |
| 6097301 | Tuttle | Aug 2000 | A |
| 6097308 | Albert et al. | Aug 2000 | A |
| 6100804 | Brady et al. | Aug 2000 | A |
| 6101390 | Jayaraman et al. | Aug 2000 | A |
| 6104295 | Gaisser et al. | Aug 2000 | A |
| 6104311 | Lastinger | Aug 2000 | A |
| 6111506 | Yap et al. | Aug 2000 | A |
| 6114962 | Wiklof et al. | Sep 2000 | A |
| 6118379 | Kodukula et al. | Sep 2000 | A |
| 6127928 | Issacman et al. | Oct 2000 | A |
| 6130612 | Castellano et al. | Oct 2000 | A |
| 6133832 | Winder et al. | Oct 2000 | A |
| 6133837 | Riley | Oct 2000 | A |
| 6137411 | Tyren | Oct 2000 | A |
| 6137412 | Herzer | Oct 2000 | A |
| 6137414 | Federman | Oct 2000 | A |
| 6144301 | Frieden | Nov 2000 | A |
| 6144303 | Federman | Nov 2000 | A |
| 6147592 | Ulrich et al. | Nov 2000 | A |
| 6148291 | Radican | Nov 2000 | A |
| 6150948 | Watkins | Nov 2000 | A |
| 6150950 | Shen Liu | Nov 2000 | A |
| 6154135 | Kane et al. | Nov 2000 | A |
| 6154139 | Heller | Nov 2000 | A |
| 6157302 | Kolton et al. | Dec 2000 | A |
| 6160881 | Beyda et al. | Dec 2000 | A |
| 6169484 | Schuchman et al. | Jan 2001 | B1 |
| 6169485 | Campana, Jr. | Jan 2001 | B1 |
| 6177861 | MacLellan et al. | Jan 2001 | B1 |
| 6183417 | Geheb et al. | Feb 2001 | B1 |
| 6203495 | Bardy | Mar 2001 | B1 |
| 6204765 | Brady et al. | Mar 2001 | B1 |
| 6204813 | Wadell et al. | Mar 2001 | B1 |
| 6208250 | Dixon et al. | Mar 2001 | B1 |
| 6211666 | Acker | Apr 2001 | B1 |
| 6211781 | McDonald | Apr 2001 | B1 |
| 6211796 | Toms et al. | Apr 2001 | B1 |
| 6215389 | Schmidt | Apr 2001 | B1 |
| 6222440 | Heller | Apr 2001 | B1 |
| 6228029 | Eccardt et al. | May 2001 | B1 |
| 6236319 | Pitzer et al. | May 2001 | B1 |
| 6241668 | Herzog | Jun 2001 | B1 |
| 6249234 | Ely et al. | Jun 2001 | B1 |
| 6259355 | Chaco et al. | Jul 2001 | B1 |
| 6262666 | Lodichand | Jul 2001 | B1 |
| 6264614 | Albert et al. | Jul 2001 | B1 |
| 6268797 | Berube et al. | Jul 2001 | B1 |
| 6275153 | Brooks | Aug 2001 | B1 |
| 6279183 | Kummer et al. | Aug 2001 | B1 |
| 6280409 | Stone et al. | Aug 2001 | B1 |
| 6285742 | Haumann et al. | Sep 2001 | B1 |
| 6287253 | Ortega et al. | Sep 2001 | B1 |
| 6289237 | Mickle et al. | Sep 2001 | B1 |
| 6293699 | Bailey et al. | Sep 2001 | B1 |
| 6294953 | Steeves | Sep 2001 | B1 |
| 6302844 | Walker et al. | Oct 2001 | B1 |
| 6314556 | DeBusk et al. | Nov 2001 | B1 |
| 6320510 | Menkedick et al. | Nov 2001 | B2 |
| 6333690 | Nelson et al. | Dec 2001 | B1 |
| 6343064 | Jabbarnezhad | Jan 2002 | B1 |
| 6344794 | Ulrich et al. | Feb 2002 | B1 |
| 6348777 | Brown et al. | Feb 2002 | B1 |
| 6353413 | White et al. | Mar 2002 | B1 |
| 6362725 | Ulrich et al. | Mar 2002 | B1 |
| 6364834 | Reuss et al. | Apr 2002 | B1 |
| 6398727 | Bui et al. | Jun 2002 | B1 |
| 6400956 | Richton | 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 |
| 6418416 | Rosenberg et al. | Jul 2002 | B1 |
| 6421649 | Rattner | Jul 2002 | B1 |
| 6424264 | Giraldin et al. | 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 |
| 6486794 | Calistro 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 |
| 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 |
| 6593845 | Friedman et al. | Jul 2003 | B1 |
| 6594146 | Frangesch et al. | Jul 2003 | B2 |
| 6594519 | Stoycos et al. | Jul 2003 | B2 |
| 6600418 | Francis 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 |
| 6693513 | Tuttle | Feb 2004 | B2 |
| 6693514 | Perea, Jr. 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 |
| 6731908 | Berliner et al. | May 2004 | B2 |
| 6731989 | Engleson et al. | May 2004 | B2 |
| 6740033 | Olejniczak et al. | May 2004 | B1 |
| 6747560 | Stevens, III | Jun 2004 | B2 |
| 6747562 | Giraldin et al. | Jun 2004 | B2 |
| 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 |
| 6756918 | Fomukong | 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 |
| 6798533 | Tipirneni | Sep 2004 | B2 |
| 6801227 | Bocionek et al. | Oct 2004 | B2 |
| 6807543 | Muthya | Oct 2004 | B2 |
| 6812824 | Goldinger et al. | Nov 2004 | B1 |
| 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 |
| 6838992 | Tenarvitz | Jan 2005 | B2 |
| 6840117 | Hubbard, Jr. | Jan 2005 | B2 |
| 6843415 | Vogler | Jan 2005 | B2 |
| 6847435 | Honda et al. | Jan 2005 | B2 |
| 6847814 | Vogeleisen | Jan 2005 | B1 |
| 6859761 | Bensky et al. | Feb 2005 | B2 |
| 6868256 | Dooley et al. | Mar 2005 | B2 |
| 6871211 | Labounty et al. | Mar 2005 | B2 |
| 6873884 | Brackett et al. | Mar 2005 | B2 |
| 6876303 | Reeder et al. | Apr 2005 | B2 |
| 6876985 | Kawanaka | Apr 2005 | B2 |
| 6884255 | Newton | Apr 2005 | B1 |
| 6885288 | Pincus | Apr 2005 | B2 |
| 6891909 | Hurley et al. | May 2005 | B2 |
| 6897780 | Ulrich 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 |
| 6954148 | Pulkkinen et al. | Oct 2005 | B2 |
| 6958706 | Chaco et al. | Oct 2005 | B2 |
| 6968194 | Aljadeff et al. | Nov 2005 | B2 |
| 6972682 | Lareau et al. | Dec 2005 | B2 |
| 6988989 | Weiner et al. | Jan 2006 | B2 |
| 6998985 | Reisman et al. | Feb 2006 | B2 |
| 6998986 | Smith | Feb 2006 | B2 |
| 7002468 | Eveland et al. | Feb 2006 | B2 |
| 7003443 | Ford et al. | Feb 2006 | B2 |
| 7005980 | Schmidt et al. | Feb 2006 | B1 |
| 7009495 | Hughes et al. | Mar 2006 | B2 |
| 7009516 | Enea | Mar 2006 | B2 |
| 7014100 | Zierolf | Mar 2006 | B2 |
| 7019663 | Sharony | Mar 2006 | B2 |
| 7030761 | Bridgelall et al. | Apr 2006 | B2 |
| 7030811 | Goren et al. | Apr 2006 | B2 |
| 7034684 | Boman et al. | Apr 2006 | B2 |
| 7034690 | Chaco | Apr 2006 | B2 |
| 7035818 | Bandy et al. | Apr 2006 | B1 |
| 7038573 | Bann | May 2006 | B2 |
| 7038584 | Carter | May 2006 | B2 |
| 7038588 | Boone et al. | May 2006 | B2 |
| 7038589 | Schmidt et al. | May 2006 | B2 |
| 7042358 | Moore | May 2006 | B2 |
| 7042361 | Kazdin et al. | May 2006 | B2 |
| 7044387 | Becker et al. | May 2006 | B2 |
| 7046153 | Oja et al. | May 2006 | B2 |
| 7046162 | Dunstan | May 2006 | B2 |
| 7049594 | Wu et al. | May 2006 | B2 |
| 7053779 | Thompson | May 2006 | B2 |
| 7053781 | Haire et al. | May 2006 | B1 |
| 7053831 | Dempsey et al. | May 2006 | B2 |
| 7056289 | Kasper et al. | Jun 2006 | B2 |
| 7057509 | Gualdi et al. | Jun 2006 | B2 |
| 7061366 | Bell et al. | Jun 2006 | B2 |
| 7061384 | Fujimoto | Jun 2006 | B2 |
| 7062455 | Tobey | Jun 2006 | B1 |
| 7068143 | Doering et al. | Jun 2006 | B2 |
| 7071820 | Callaway | Jul 2006 | B2 |
| 7071843 | Hashida et al. | Jul 2006 | B2 |
| 7075438 | Kent et al. | Jul 2006 | B2 |
| 7080061 | Kabala | Jul 2006 | B2 |
| 7084740 | Bridgelall | Aug 2006 | B2 |
| 7091879 | Swetlik et al. | Aug 2006 | B2 |
| 7092376 | Schuman | Aug 2006 | B2 |
| 7099895 | Dempsey | Aug 2006 | B2 |
| 7102510 | Boling et al. | Sep 2006 | B2 |
| 7106189 | Burneske et al. | Sep 2006 | B2 |
| 7116230 | Klowak | Oct 2006 | B2 |
| 7117027 | Zheng et al. | Oct 2006 | B2 |
| 7138913 | Mackenzie et al. | Nov 2006 | B2 |
| 7142112 | Buckingham et al. | Nov 2006 | B2 |
| 7151455 | Lindsay et al. | Dec 2006 | B2 |
| 7152791 | Chappidi et al. | Dec 2006 | B2 |
| 7154397 | Zerhusen et al. | Dec 2006 | B2 |
| 7158030 | Chung | Jan 2007 | B2 |
| 7164354 | Panzer | Jan 2007 | B1 |
| 7165040 | Ehrman et al. | Jan 2007 | B2 |
| 7167095 | Carrender | Jan 2007 | B2 |
| 7170407 | Wagner | Jan 2007 | B2 |
| 7174172 | Sharony et al. | Feb 2007 | B2 |
| 7190778 | Kucmerowski | Mar 2007 | B2 |
| 7196621 | Kochis | Mar 2007 | B2 |
| 7199716 | Shanks et al. | Apr 2007 | B2 |
| 7202785 | Maloney | Apr 2007 | B2 |
| 7203690 | Braun et al. | Apr 2007 | B2 |
| 7209790 | Thompson et al. | Apr 2007 | B2 |
| 7218231 | Higham | May 2007 | B2 |
| 7225241 | Yada | May 2007 | B2 |
| 7230536 | Shinada et al. | Jun 2007 | B2 |
| 7242306 | Wildman et al. | Jul 2007 | B2 |
| 7242308 | Ulrich et al. | Jul 2007 | B2 |
| 7248880 | Gheorghiu et al. | Jul 2007 | B2 |
| 7248933 | Wildman | Jul 2007 | B2 |
| 7259676 | Knadle, Jr. et al. | Aug 2007 | B2 |
| 7265668 | Brosius | Sep 2007 | B1 |
| 7269427 | Hoctor et al. | Sep 2007 | B2 |
| 7277048 | Hessing | Oct 2007 | B2 |
| 7277889 | Addonisio et al. | Oct 2007 | B2 |
| 7283046 | Culpepper et al. | Oct 2007 | B2 |
| 7283423 | Holm et al. | Oct 2007 | B2 |
| 7286868 | Govari | Oct 2007 | B2 |
| 7292151 | Ferguson et al. | Nov 2007 | B2 |
| 7295115 | Aljadeff et al. | Nov 2007 | B2 |
| 7295132 | Steiner | Nov 2007 | B2 |
| 7298359 | Kim et al. | Nov 2007 | B2 |
| 7301451 | Hastings | Nov 2007 | B2 |
| 7304577 | Waldner et al. | Dec 2007 | B2 |
| 7304578 | Sayers et al. | Dec 2007 | B1 |
| 7304579 | Diorio et al. | Dec 2007 | B2 |
| 7307522 | Dawson | Dec 2007 | B2 |
| 7313403 | Gong et al. | Dec 2007 | B2 |
| 7315248 | Egbert | Jan 2008 | B2 |
| 7315281 | Dejanovic et al. | Jan 2008 | B2 |
| 7319386 | Collins, Jr. et al. | Jan 2008 | B2 |
| 7319395 | Puzio et al. | Jan 2008 | B2 |
| 7319397 | Chung et al. | Jan 2008 | B2 |
| 7319412 | Coppinger et al. | Jan 2008 | B1 |
| 7321305 | Göllü | Jan 2008 | B2 |
| 7333018 | Singh et al. | Feb 2008 | B2 |
| 7336187 | Hubbard, Jr. et al. | Feb 2008 | B2 |
| 7336563 | Holm | Feb 2008 | B2 |
| 7339477 | Puzio et al. | Mar 2008 | B2 |
| 7339479 | Nishimura | Mar 2008 | B2 |
| 7362656 | Holm | Apr 2008 | B2 |
| 7370808 | Eastin | May 2008 | B2 |
| 7375648 | Mulka et al. | May 2008 | B1 |
| 7375654 | Culpepper et al. | May 2008 | B2 |
| 7376123 | Reuss | May 2008 | B2 |
| 7394385 | Franco, Jr. et al. | Jul 2008 | B2 |
| 7411509 | Rosenfeld et al. | Aug 2008 | B2 |
| 7415212 | Matsushita et al. | Aug 2008 | B2 |
| 7417544 | Artem et al. | Aug 2008 | B2 |
| 7443299 | Forster | Oct 2008 | B2 |
| 7446664 | White | Nov 2008 | B2 |
| 7473097 | Raby et al. | Jan 2009 | B2 |
| 7474224 | Long et al. | Jan 2009 | B2 |
| 7515044 | Welch et al. | Apr 2009 | B2 |
| 7518502 | Austin et al. | Apr 2009 | B2 |
| 7538679 | Shanks | May 2009 | B2 |
| 7541927 | Dupler et al. | Jun 2009 | B2 |
| 7551083 | Modes et al. | Jun 2009 | B2 |
| 7567794 | Dempsey | Jul 2009 | B2 |
| 7598853 | Becker et al. | Oct 2009 | B2 |
| 7623250 | Moctezuma de la Barrera et al. | Nov 2009 | B2 |
| 7627334 | Cohen et al. | Dec 2009 | B2 |
| 7664686 | Czyszczewski et al. | Feb 2010 | B2 |
| 7667572 | Husak et al. | Feb 2010 | B2 |
| 7714728 | Koblasz | May 2010 | B2 |
| 7724147 | Brown | May 2010 | B2 |
| 7725195 | Lima et al. | May 2010 | B2 |
| 7734476 | Wildman et al. | Jun 2010 | B2 |
| 7737850 | Malik | Jun 2010 | B2 |
| 7750793 | Juels | Jul 2010 | B2 |
| 7755541 | Wisherd et al. | Jul 2010 | B2 |
| 7756723 | Rosow et al. | Jul 2010 | B2 |
| 7761320 | Fliess et al. | Jul 2010 | B2 |
| 7765286 | Mark | Jul 2010 | B2 |
| 7800914 | Dully | Sep 2010 | B2 |
| 7844505 | Arneson et al. | Nov 2010 | B1 |
| 7848760 | Caspi et al. | Dec 2010 | B2 |
| 7869861 | Moctezuma de la Barrera et al. | Jan 2011 | B2 |
| 7890349 | Cole et al. | Feb 2011 | B2 |
| 7893842 | Deutsch | Feb 2011 | B2 |
| 7907053 | Wildman et al. | Mar 2011 | B2 |
| 7916023 | Rado | Mar 2011 | B2 |
| 7920050 | Juels et al. | Apr 2011 | B2 |
| 7928844 | Mackenzie et al. | Apr 2011 | B2 |
| 7933780 | De La Huerga | Apr 2011 | B2 |
| 7958087 | Blumenau | Jun 2011 | B2 |
| 7966008 | Graves et al. | Jun 2011 | B2 |
| 8026821 | Reeder et al. | Sep 2011 | B2 |
| 8031057 | McNeely et al. | Oct 2011 | B2 |
| 8073558 | Koch et al. | Dec 2011 | B2 |
| 8102254 | Becker et al. | Jan 2012 | B2 |
| 8160677 | Gielen et al. | Apr 2012 | B2 |
| 8164444 | Anderson et al. | Apr 2012 | B2 |
| 8190730 | Dempsey | May 2012 | B2 |
| 8223009 | Anderson et al. | Jul 2012 | B2 |
| 8248467 | Ganick et al. | Aug 2012 | B1 |
| 8272892 | McNeely et al. | Sep 2012 | B2 |
| 8284047 | Collins, Jr. et al. | Oct 2012 | B2 |
| 8310364 | Derks et al. | Nov 2012 | B2 |
| 8319633 | Becker et al. | Nov 2012 | B2 |
| 8321302 | Bauer et al. | Nov 2012 | B2 |
| 8334898 | Ryan et al. | Dec 2012 | B1 |
| 8334901 | Ganick et al. | Dec 2012 | B1 |
| 8390462 | Belz et al. | Mar 2013 | B2 |
| 8416072 | Tenarvitz | Apr 2013 | B2 |
| 8416290 | Ryan et al. | Apr 2013 | B2 |
| 8432438 | Ryan et al. | Apr 2013 | B2 |
| 8436896 | Staats et al. | May 2013 | B2 |
| 8447626 | Sun et al. | May 2013 | B2 |
| 8457502 | Ryan et al. | Jun 2013 | B2 |
| 8461968 | Ball et al. | Jun 2013 | B2 |
| 8461982 | Becker et al. | Jun 2013 | B2 |
| 8514071 | Derks et al. | Aug 2013 | B2 |
| 8516514 | Belz et al. | Aug 2013 | B2 |
| 8519823 | Rinkes | Aug 2013 | B2 |
| 8520065 | Staats et al. | Aug 2013 | B2 |
| 8558660 | Nix et al. | Oct 2013 | B2 |
| 8604916 | McNeely et al. | Dec 2013 | B2 |
| 8604917 | Collins et al. | Dec 2013 | B2 |
| 8610562 | Weiner et al. | Dec 2013 | B2 |
| 8650045 | Baldock et al. | Feb 2014 | B2 |
| 8674826 | Becker et al. | Mar 2014 | B2 |
| 8689376 | Becker et al. | Apr 2014 | B2 |
| 8752045 | Fitzgerald et al. | Jun 2014 | B2 |
| 8781847 | Simms et al. | Jul 2014 | B2 |
| 9020963 | Goodman et al. | Apr 2015 | B2 |
| 9026301 | Zini et al. | May 2015 | B2 |
| 9830424 | Dixon et al. | Nov 2017 | B2 |
| 20010050610 | Gelston | Dec 2001 | A1 |
| 20010051765 | Walker et al. | Dec 2001 | A1 |
| 20020044059 | Reeder et al. | Apr 2002 | A1 |
| 20020067273 | Jaques et al. | Jun 2002 | A1 |
| 20020070867 | Conway et al. | Jun 2002 | A1 |
| 20020165733 | Pulkkinen et al. | Nov 2002 | A1 |
| 20020173286 | Lindoff et al. | Nov 2002 | A1 |
| 20020173991 | Avitall | Nov 2002 | A1 |
| 20030010345 | Koblasz et al. | Jan 2003 | A1 |
| 20030028449 | Heinen et al. | Feb 2003 | A1 |
| 20030132845 | McDaniel, III | Jul 2003 | A1 |
| 20030149598 | Santoso et al. | Aug 2003 | A1 |
| 20030176798 | Simon | Sep 2003 | A1 |
| 20040024660 | Ganesh et al. | Feb 2004 | A1 |
| 20040106854 | Muraki | Jun 2004 | A1 |
| 20040186358 | Chernow et al. | Sep 2004 | A1 |
| 20050071198 | Krupa | Mar 2005 | A1 |
| 20050122119 | Barlow | Jun 2005 | A1 |
| 20050131729 | Melby et al. | Jun 2005 | A1 |
| 20060012474 | Lu et al. | Jan 2006 | A1 |
| 20060022818 | Piltonen | Feb 2006 | A1 |
| 20060028336 | Glenn et al. | Feb 2006 | A1 |
| 20060031259 | Gibson et al. | Feb 2006 | A1 |
| 20060038676 | Richards | Feb 2006 | A1 |
| 20060071774 | Brown et al. | Apr 2006 | A1 |
| 20060082444 | Sweeney, II et al. | Apr 2006 | A1 |
| 20060097863 | Horowitz et al. | May 2006 | A1 |
| 20060135083 | Leinonen et al. | Jun 2006 | A1 |
| 20060161214 | Patel | Jul 2006 | A1 |
| 20060220798 | Willis | Oct 2006 | A1 |
| 20060253590 | Nagy et al. | Nov 2006 | A1 |
| 20070005558 | Canfield | Jan 2007 | A1 |
| 20070015960 | Gornert et al. | Jan 2007 | A1 |
| 20070033072 | Bildirici | Feb 2007 | A1 |
| 20070073116 | Kiani et al. | Mar 2007 | A1 |
| 20070093879 | Bek et al. | Apr 2007 | A1 |
| 20070123173 | Stobbe | May 2007 | A1 |
| 20070129967 | Thompson et al. | Jun 2007 | A1 |
| 20070157385 | Lemire | Jul 2007 | A1 |
| 20070210917 | Collins, Jr. et al. | Sep 2007 | A1 |
| 20070271122 | Zaleski | Nov 2007 | A1 |
| 20080004993 | Horspool et al. | Jan 2008 | A1 |
| 20080026713 | Sekhar et al. | Jan 2008 | A1 |
| 20080040244 | Ricciuti et al. | Feb 2008 | A1 |
| 20080100706 | Breed | May 2008 | A1 |
| 20080106418 | Sloan et al. | May 2008 | A1 |
| 20080108372 | Breed | May 2008 | A1 |
| 20080126125 | Lichtenstein et al. | May 2008 | A1 |
| 20080126126 | Ballai | May 2008 | A1 |
| 20080136621 | Malik et al. | Jun 2008 | A1 |
| 20080136635 | Malik | Jun 2008 | A1 |
| 20080140544 | Ehrman et al. | Jun 2008 | A1 |
| 20080180322 | Islam et al. | Jul 2008 | A1 |
| 20080201388 | Wood et al. | Aug 2008 | A1 |
| 20080215360 | Dicks et al. | Sep 2008 | A1 |
| 20080238676 | Dhillon et al. | Oct 2008 | A1 |
| 20080242945 | Gugliotti et al. | Oct 2008 | A1 |
| 20080300918 | Tenenbaum et al. | Dec 2008 | A1 |
| 20080312974 | Rosow et al. | Dec 2008 | A2 |
| 20080312975 | Rosow et al. | Dec 2008 | A2 |
| 20090018882 | Burton et al. | Jan 2009 | A1 |
| 20090033500 | Malik et al. | Feb 2009 | A1 |
| 20090079549 | Ruder | Mar 2009 | A1 |
| 20090300507 | Raghavan et al. | Dec 2009 | A1 |
| 20100001838 | Miodownik et al. | Jan 2010 | A1 |
| 20100217618 | Piccirillo et al. | Aug 2010 | A1 |
| 20100289885 | Lu et al. | Nov 2010 | A1 |
| 20110050411 | Schuman et al. | Mar 2011 | A1 |
| 20110125513 | Tenarvitz et al. | May 2011 | A1 |
| 20110125524 | Tenarvitz et al. | May 2011 | A1 |
| 20110208541 | Wilson et al. | Aug 2011 | A1 |
| 20110227740 | Wohltjen | Sep 2011 | A1 |
| 20120316892 | Huster | Dec 2012 | A1 |
| 20130069771 | Frondorf | Mar 2013 | A1 |
| 20140207490 | Shindo | Jul 2014 | A1 |
| 20150081335 | Dixon et al. | Mar 2015 | A1 |
| Number | Date | Country |
|---|---|---|
| 2031535 | Mar 2009 | EP |
| 2006105269 | Oct 2006 | WO |
| Entry |
|---|
| Reference Manual, Laird WB45NBT, Version 1.0, revised Aug. 20, 2013, 37 pages. |
| EP Search Report for Application No. EP 14185232.7-1952, dated Mar. 16, 2015, 6 pages. |
| Summons to Attend Oral Proceedings issued by the European Patent Office for European Patent Application No. 14185232.7; dated Nov. 13, 2020 (9 pages). |
| Number | Date | Country | |
|---|---|---|---|
| 20180039743 A1 | Feb 2018 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61879399 | Sep 2013 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14487279 | Sep 2014 | US |
| Child | 15784693 | US |
