The present disclosure relates to mattresses for a hospital bed for use in a healthcare facility. More particularly, the present disclosure relates to a mattress or support surface having a unique identifier to identify a location of the mattress within the healthcare facility and more particularly to identify a location of the mattress within a room of the healthcare facility.
Some hospital beds can be configured to communicate information to a nurse call system or to other information systems located within a healthcare facility. Such systems typically include a computer system or other electronic communication system at a nurses station which is remotely located from the hospital bed. The computer system can include a monitor to display information relating to the status of a bed. The hospital bed can include one or more nurse call buttons located on the side rails of the bed and/or on a hand-held pendant which is located adjacent to or at the bed. The patient can press one of the buttons to request or to speak to a nurse or other caregiver. In addition, the nurse at the remote station can communicate with the patient with a two-way communications link including audio circuitry such as a microphone and a speaker located either on the bed itself or mounted on equipment or the wall of the room.
Hospital beds which can communicate with such computer systems, typically connect via a wired connection established by a cable that extends between the bed and an interface unit mounted on a wall or a head wall of the hospital room. Such a wired communication cannot only provide for communication between a patient and a caregiver, but also provide bed status information to locations which are remote from the bed. Such bed status information allows medical personnel and other caregivers to monitor the status of the bed including the location of siderails, the position of an articulating deck, and the current status of certain bed components such as brakes not set or bed exit system not armed.
For instance, it is also possible for such a bed status information to provide information unique to a particular bed frame. Identification information can identify the model type of the bed frame, the serial number of the bed frame, and its functional capabilities.
The present invention may comprise a system, apparatus and/or method that may have one or more of the following features and/or steps, which alone or in any combination may comprise patentable subject matter.
In accordance with one aspect of the disclosed embodiments, there is provided a mattress for use in a healthcare facility having a communications system and a plurality of bed frames. The mattress includes a support member and a unique electronic identifier, associated with the mattress, to uniquely identify the mattress.
In accordance with another aspect of the disclosed embodiments, there is provided a method of determining the location of a mattress within a health care facility having a communication system, a plurality of bed frames, and a plurality of mattresses. The method includes the steps of assigning a unique identifier to each of the plurality of mattresses, placing one of the uniquely identified mattresses on one of the plurality of bed frames, confirming placement of one of the uniquely identified mattresses on the one of the plurality of bed frames, and sending the unique identifier assigned to one of the uniquely identified mattresses over the communication system.
Pursuant to another aspect of the disclosed embodiments, there is provided a system including a communication system, a plurality of uniquely identified mattresses wherein each of the uniquely identified mattresses includes a unique electronic identifier, and a plurality of bed frames. The system may further include an install confirmation device to confirm association of one of the uniquely identified mattresses with one of the bed frames.
Each of the plurality of uniquely identified mattresses includes a support member and a transceiver associated with the mattress. Each of the uniquely identified mattresses may includes a network interface device operably coupled to the transceiver. The transceiver is operably coupled to the communication system to transmit the unique electronic identifier over the communication system. The network interface device is adapted to store the unique electronic identifier. The unique electronic identifier may include an internet protocol address. The transceiver may include a wireless transceiver and the wireless transceiver may be part of the network interface device.
The system may further include a computing device coupled to the communication system to receive and store the unique electronic identifiers from the plurality of uniquely identified mattresses. The computing device may provide an interface to present information regarding the plurality of uniquely identified mattresses. In particular, the interface may present information that identifies each mattress of the plurality of uniquely identified mattresses and that identifies a patient assigned to each mattress of the plurality of uniquely identified mattresses. The interface may also present information that identifies each mattress of the plurality of uniquely identified mattresses, a location of each mattress in the healthcare facility, a type for each mattress, features provided by each mattress, and/or a history of use for each mattress.
The healthcare group 10 includes one or more healthcare facilities 12 each of which can be coupled to the worldwide web through an internet server 30 located either within the healthcare facility 12 or remotely therefrom. While the description of the present invention includes reference to a healthcare group 10 including one or more healthcare facilities, the present invention is equally applicable to individual healthcare facilities which are not affiliated with a larger healthcare group. Consequently, the internet server which is used by a healthcare facility to communicate with the internet/worldwide web 14 may also be located remotely at an internet service provider, such as is understood by those skilled in the art.
The healthcare facility can include one or more units 32 which typically are devoted primarily to providing a particular or specialized type of healthcare. For instance, one healthcare unit 32 might be particularly devoted to providing cardiac healthcare, while another particular unit 32 might be devoted to providing orthopedic healthcare. Consequently, the present invention is not limited in any way by the type of healthcare provided and can include all types of healthcare.
Each of the healthcare units typically includes a plurality of healthcare beds, each including a frame 34 and a mattress 36. Frames and mattresses are well know in the art. Mattresses include a support member which can include foam, air bladders, or combinations thereof. Each of the mattresses includes a unique electronic identifier. While illustrated here as being separate components, a single mattress is typically associated with a single frame and is adapted to support a patient. The healthcare unit 32 further includes one or more transceivers (xcvr) 38 which can provide communication between the beds and a nurses station 40 through a local area network 42. The nurses station 40 can provide the functions of a nurse call station as well as to provide an administrative station for an administrator to set up the communication/computing/informational system of the present invention.
The network application 50 of the present invention enables the administrator to assign each of the mattresses 36 with a unique identifier such as a unique IP address. The term IP address refers to an internet protocol (IP) address which is also known as a network address. The IP address can be assigned and changed in various ways, including being assigned and changed by a system administrator or by an authorized user having access to the network application 50. A fixed IP address can include a 32-bit (4-byte) binary number that uniquely identifies the mattress 36. Other electronic identifiers can also be used.
To uniquely identify each of the mattresses 36, a network interface device or card (NIC) 52 is incorporated into the mattress 36. The network interface card 52 is a known device which can be purchased from a variety of vendors. The network interface card 52 includes a central processing unit (CPU) 54 for manipulating data which is received by or transmitted by the network interface card over the local area network 42. The network interface card 52 also includes the assignable IP address 56. Communication over the local area network 42 can be accomplished by a wireless transceiver 58 which can communicate with the network interface card 52. The wireless transceiver 52 can either be incorporated into the network interface card 52 or can be a separate device as is understood by those skilled in the art. In addition, the wireless transceiver 58 can be incorporated either into the mattress 36, into the frame 34 or other components of the hospital bed. It is preferred, however, that the wireless transceiver be incorporated as a component of the mattress, such that when a mattress is moved from one location to another, the transceiver moves with the mattress.
In addition to the network interface card 52 located within the mattress 36, a surface controller 60 located within the mattress 36 is coupled to the network interface card 52. The surface controller 60 can include a variety of control functions for controlling the operation of the mattress. For instance, the mattress can include features such as percussion, vibration, turning, rotation, turn assist, as well as heating and cooling. A user interface 62 coupled to the surface controller 60 can be used to adjust the various control functions. The user interface 62 includes for instance, a touch screen or other manually activated buttons which enable a caregiver to control the various described functions. One or more confirming indicators 63 as described later herein can be included. Voice recognition can also be provided. The user interface 62 is typically incorporated into a control box which can be external to the mattress 36 but is coupled thereto by one or more control lines as is known by those skilled in the art. It is also possible to incorporate some, many, or all of the components of the control box into the mattress.
Upon selection of the desired functions through the user interface 62, one or more actuators or valves 64 respond accordingly to control the described features, such as percussion and/or vibration. In addition, one or more sensors and/or monitors 66 can be coupled to the surface controller 60 to provide sensed characteristics of the patient, the bed, or the interface between the patient and bed. For instance, the mattress 36 can include pressure sensors for determining patient pressure upon the mattress and send such information to the surface controller 60. The surface controller 60, which includes a central processing unit, can cause the actuators/valves to respond accordingly to address the sensed pressures based upon algorithms which can be located in a memory 68. The memory 68, not only can include algorithms for controlling the mattress 36, but can also be used to store data received from the actuators 64 and the sensors/monitors 66. The data stored in the memory 68 can then be accessed by the local area network 42 through the wireless transceiver 58.
The mattress 36 is supported by the frame 34. The frame 34 includes a frame controller 70 which includes a central processing unit to control the various functions of the frame. For instance, one or more actuators 72 such as a motor can be activated by the frame controller 70 upon entry of commands through a user interface 74. The user interface 74 can be included in a control pendant, a controller either coupled to or incorporated into a siderail, or other user interface devices which may be incorporated into the headboard, footboard, or other portions of the frame 34. The frame 34 also includes sensors/monitors 76 which can be used to monitor the operation of the actuators 72 or which can also be used to monitor the position and/or location of a patient being supported by the frame. In addition, the frame controller 70 can be coupled to the brake pedal 78 which can receive a signal from the brake pedal indicating the status thereof. Such a status signal can be communicated by the frame controller 70 to a wireless transceiver 72 which communicates with the local area network 42 to provide status information to the nurse station 40. While the wireless transceiver 72 is indicated as being distinct from the wireless transceiver 58, certain functions of the transceiver 72 can be shared by the transceiver 58. A memory 80 is coupled to the frame controller 70 and includes software having instructions for controlling the central processing unit. The memory 80 can also be used to store status information which is received from the actuators 72, the sensors 76 and user inputs through the user interface 74.
Each of the frames 34 can include an identifier, which can be unique, which can be communicated to the nurse call station 40 using a network interface unit and/or wireless interface unit.
Once the mattress 36 is placed on the frame 34, an association device or a communicator 90 recognizes that a surface or support 36 has now been associated with the frame 34. The association device can reside on the mattress 36, on the frame 34, or portions thereof can be located on both the frame 34 and the mattress 36. For instance, as illustrated in
The surface can also be associated with the frame through a partially automatic system which includes an interactive response with or from a service technician or other installer. For instance, a wi-fi system 96 can be incorporated into the mattress 36. Upon toggling of the brake 78, a signal is sent from the brake to the frame controller 70 of
As illustrated in
Once the surface controller 60 has received the signal from the frame controller 70, the surface controller 60, in combination with the network interface card 52, provides a signal, including the unique mattress IP address, which is transmitted by the wireless transceiver 58 to the local area network 42 and eventually to the nurse station 40. The nurse station 40 upon receipt of this information enters the unique identifier IP address to the network application used to indicate the location of the mattress. The IP address can be entered into a database automatically by the network application.
Once this information has been entered into the nurse station 40, the network application provides a signal from the nurse station 40 to the LAN 42 and back to the wireless transceiver 58. Such a signal causes the surface controller 60 to communicate with the frame controller 70 and to illuminate a mattress/network indicator 108. Other indicators are also possible as previously described.
It is not necessary to include the install button 106 in the interface 100 since the previously described sensor 92, RFID 94, and wi-fi device 96 can be used to transmit the necessary signal to the mattress to indicate that the frame and mattress have been associated as indicated by the indicator 106. In addition, it is not necessary to include both the indicator 106 and the indicator 108. It is within the scope of the present disclosure to include a single indicator which indicates that the mattress has been associated with the frame and that the mattress and its unique identifier have been recognized by the network.
An install/confirmation device 110 can also be incorporated into the mattress controller 104. The install/confirmation device 110 includes an install button 112, a frame/mattress indicator 114 and a mattress/network indicator 116. If either the frame/mattress indicator and/or mattress/network indicator does not illuminate, the installer can act accordingly. For instance, if the frame/mattress indicator 106 does not illuminate, the installer can contact the appropriate service technician who is familiar with the operation of the frame controller and its various related components and the surface controller and its various related components. The service technician can then diagnose the problem and make a repair or provide a replacement as necessary. However, if the frame/mattress indicator 114 does illuminate, but the mattress/network indicator 116 does not, then the installer can contact either a service technician familiar with the frame and mattress systems or can contact a service technician familiar with the network systems. Consequently, the use of a first and/or a second confirming indicator(s) can provide information useful for localizing a problem should one exist.
Once the mattress has been associated with the frame and the unique IP address of the mattress has been transmitted to the nurse station 40, the mattress identification information can be accessed by a caregiver or nurse at the nurse station. Because the system includes the use of the internet/world wide web 14, a remotely located user can also access the information through a computer system such as computer system 16. It is therefore possible for an individual to view information when located externally to the healthcare group 10, such as at home.
At the nurse station 40, or other location, the caregiver can view a variety of data which can be associated with a particular mattress. A user application residing at the nurse station 40 can include a number of user interface screens such as those illustrated in
A first user interface screen 140 includes information relating to a patient, a mattress, and a location of the mattress. Because it is possible to uniquely identify the mattress and the location thereof, the patient currently on the mattress can also be linked or associated with the identified mattress. Consequently, the user interface screen 140 of
The unique mattress identifier can provide a variety of useful information to the caregiver. For instance, a healthcare unit 32, such as an intensive care unit (ICU), may have a number of mattresses. The network administrator setting up the system can use the unique identifiers of each mattress to provide a mattress ID (identifier) for use in this particular screen. For instance, if there are ten mattresses in the ICU, they could be given mattress ID's ICU ONE through ICU TEN, since IP addresses when displayed may provide only the numbers. Consequently, the mattress ID, ICU ONE, is not unlike a domain name, since web addresses can be both the actual IP address and a domain name associated therewith. A third column STATUS, in the screen 142 can include the status of the mattress. If the mattress has indeed been associated with a frame, then the status “IN USE” can be displayed. If a mattress, however, has not been associated with a frame, the status could be indicated as “NOT IN USE.” A fourth column, LOCATION, indicates the location of the mattress which has now been associated with a particular frame. In this case, the location is indicated as ICU-Third Floor.
Because the mattress has a unique identifier and that identifier can indicate the type of mattress being used, a column indicating TYPE will display the type of mattress. For instance, the type can be generalized such that there are a limited number of types which might include a foam mattress, an air mattress, and a therapy mattress. The types can be respectively identified at TYPE 1, TYPE 2, or TYPE 3. Because the type of mattress is known, a FEATURES column can indicate the features which are included for that type of mattress. For instance, the features list could say “FOAM” or as is illustrated, the features list can indicate that the mattress has “MULTIPLE” features. It is within the scope of the present invention for the caregiver to move the cursor of the mouse over the word “FEATURES.” A drop down menu, provided by the application software, can automatically be displayed indicating each of the features present in that particular mattress.
Should the caregiver viewing user interface screen 140 instead desire to view a particular uniquely identified mattress, the caregiver can select the “MATTRESS” selector in
As illustrated in
If, however, the caregiver had selected the history of “PRIOR” at the user interface screen 146 of
While an exemplary embodiment incorporating the principles of the present invention has been disclosed hereinabove, the present invention is not limited to the disclosed embodiments. Instead, this application is intended to cover any variations, uses, or adaptations of the invention using its general principles. Further, this application is intended to cover such departures from the present disclosure as come within known or customary practice in the art to which this invention pertains and which fall within the limits and scope of the appended claims.
Number | Name | Date | Kind |
---|---|---|---|
2330356 | Belliveau | Sep 1943 | A |
2335524 | Lomax | Nov 1943 | A |
2736888 | McLain | Feb 1956 | A |
2896021 | Philipps | Jul 1959 | A |
3098220 | De Graaf | Jul 1963 | A |
3439320 | Ward | Apr 1969 | A |
3478344 | Schwitzgebel et al. | Nov 1969 | A |
3553383 | Rochtus | Jan 1971 | A |
3599199 | Bunting | Aug 1971 | A |
3599200 | Bunting | Aug 1971 | A |
3696384 | Lester | Oct 1972 | A |
3739329 | Lester | Jun 1973 | A |
3767859 | Doering et al. | Oct 1973 | A |
3805265 | Lester | Apr 1974 | A |
3913153 | Adams et al. | Oct 1975 | A |
3973200 | Akerberg | Aug 1976 | A |
4067005 | Levy et al. | Jan 1978 | A |
4150284 | Trenkler et al. | Apr 1979 | A |
4151407 | McBride et al. | Apr 1979 | A |
4183015 | Drew et al. | Jan 1980 | A |
4216462 | McGrath et al. | Aug 1980 | A |
4225953 | Simon et al. | Sep 1980 | A |
4228426 | Roberts | Oct 1980 | A |
4237344 | Moore | Dec 1980 | A |
4264982 | Sakarya | Apr 1981 | A |
4275385 | White | Jun 1981 | A |
4279433 | Petaja | Jul 1981 | A |
4298863 | Natitus et al. | Nov 1981 | A |
4331953 | Blevins et al. | May 1982 | A |
4356475 | Neumann et al. | Oct 1982 | A |
4418334 | Burnett | Nov 1983 | A |
4455548 | Burnett | Jun 1984 | A |
4489387 | Lamb et al. | Dec 1984 | A |
4495495 | Ormanns et al. | Jan 1985 | A |
4495496 | Miller, III | Jan 1985 | A |
4539560 | Fleck et al. | Sep 1985 | A |
4577185 | Andersen | Mar 1986 | A |
4578671 | Flowers | Mar 1986 | A |
4582280 | Nichols et al. | Apr 1986 | A |
4593273 | Narcisse | Jun 1986 | A |
4598275 | Ross et al. | Jul 1986 | A |
4601064 | Shipley | Jul 1986 | A |
4649385 | Aires et al. | Mar 1987 | A |
4680790 | Packard et al. | Jul 1987 | A |
4709330 | Yokoi et al. | Nov 1987 | A |
4740788 | Konneker | Apr 1988 | A |
4752951 | Konneker | Jun 1988 | A |
4792798 | Wilowski | Dec 1988 | A |
4795905 | Zierhut | Jan 1989 | A |
4814751 | Hawkins et al. | Mar 1989 | A |
4833452 | Currier | May 1989 | A |
4833467 | Kobayashi et al. | May 1989 | A |
4837568 | Snaper | Jun 1989 | A |
4853692 | Wolk et al. | Aug 1989 | A |
4899135 | Ghahariiran | Feb 1990 | A |
4947152 | Hodges | Aug 1990 | A |
4955000 | Nastrom | Sep 1990 | A |
4967195 | Shipley | Oct 1990 | A |
4990892 | Guest et al. | Feb 1991 | A |
4998095 | Shields | Mar 1991 | A |
4998939 | Potthast et al. | Mar 1991 | A |
5006830 | Merritt | Apr 1991 | A |
5027314 | Linwood et al. | Jun 1991 | A |
5041086 | Koenig et al. | Aug 1991 | A |
5062151 | Shipley | Oct 1991 | A |
5065154 | Kaiser et al. | Nov 1991 | A |
5086290 | Murray et al. | Feb 1992 | A |
5103108 | Crimmins | Apr 1992 | A |
5124991 | Allen | Jun 1992 | A |
5137033 | Norton | Aug 1992 | A |
5153584 | Engira | Oct 1992 | A |
5266944 | Carroll et al. | Nov 1993 | A |
5291399 | Chaco | Mar 1994 | A |
5319355 | Russek | Jun 1994 | A |
5319363 | Welch et al. | Jun 1994 | A |
5357254 | Kah, Jr. | Oct 1994 | A |
5375604 | Kelly et al. | Dec 1994 | A |
5396224 | Dukes et al. | Mar 1995 | A |
5396227 | Carroll et al. | Mar 1995 | A |
5416695 | Stutman et al. | May 1995 | A |
5434775 | Sims et al. | Jul 1995 | A |
5446678 | Saltzstein et al. | Aug 1995 | A |
5455560 | Owen | Oct 1995 | A |
5458123 | Unger | Oct 1995 | A |
5461390 | Hoshen | Oct 1995 | A |
5475367 | Prevost | Dec 1995 | A |
5534851 | Russek | Jul 1996 | A |
5537459 | Price et al. | Jul 1996 | A |
5548637 | Heller et al. | Aug 1996 | A |
5549113 | Halleck et al. | Aug 1996 | A |
5561412 | Novak et al. | Oct 1996 | A |
5568119 | Schipper et al. | Oct 1996 | A |
5576952 | Stutman et al. | Nov 1996 | A |
5579001 | Dempsey et al. | Nov 1996 | A |
5588005 | Ali et al. | Dec 1996 | A |
5594786 | Chaco et al. | Jan 1997 | A |
5621388 | Sherburne et al. | Apr 1997 | A |
5635907 | Bernard et al. | Jun 1997 | A |
5636245 | Ernst et al. | Jun 1997 | A |
5640953 | Bishop et al. | Jun 1997 | A |
5650769 | Campana, Jr. | Jul 1997 | A |
5650770 | Schlager et al. | Jul 1997 | A |
5664270 | Bell et al. | Sep 1997 | A |
5682139 | Pradeep et al. | Oct 1997 | A |
5686888 | Welles, II et al. | Nov 1997 | A |
5686902 | Reis et al. | Nov 1997 | A |
5687734 | Dempsey et al. | Nov 1997 | A |
5689229 | Chaco et al. | Nov 1997 | A |
5691980 | Welles, II et al. | Nov 1997 | A |
5699038 | Ulrich et al. | Dec 1997 | A |
5705980 | Shapiro | Jan 1998 | A |
5708421 | Boyd | Jan 1998 | A |
5713856 | Eggers et al. | Feb 1998 | A |
5719761 | Gatti et al. | Feb 1998 | A |
5731757 | Layson, Jr. | Mar 1998 | A |
5742237 | Bledsoe | Apr 1998 | A |
5751246 | Hertel | May 1998 | A |
5752917 | Fuchs | May 1998 | A |
5760704 | Barton et al. | Jun 1998 | A |
5767791 | Stoop et al. | Jun 1998 | A |
5781442 | Engleson et al. | Jul 1998 | A |
5793290 | Eagleson et al. | Aug 1998 | A |
5808564 | Simms et al. | Sep 1998 | A |
5812056 | Law | Sep 1998 | A |
5822418 | Yacenda et al. | Oct 1998 | A |
5822544 | Chaco et al. | Oct 1998 | A |
5838223 | Gallant et al. | Nov 1998 | A |
5844488 | Musick | Dec 1998 | A |
5867821 | Ballantyne et al. | Feb 1999 | A |
5877675 | Rebstock et al. | Mar 1999 | A |
5933488 | Marcus et al. | Aug 1999 | A |
5936539 | Fuchs | Aug 1999 | A |
5942986 | Shabot et al. | Aug 1999 | A |
5944659 | Flach et al. | Aug 1999 | A |
5963137 | Waters, Sr. | Oct 1999 | A |
5974389 | Clark et al. | Oct 1999 | A |
5991728 | DeBusk et al. | Nov 1999 | A |
5995937 | DeBusk et al. | Nov 1999 | A |
6014633 | DeBusk et al. | Jan 2000 | A |
6057758 | Dempsey et al. | May 2000 | A |
6057782 | Koenig | May 2000 | A |
6067019 | Scott | May 2000 | A |
6076166 | Moshfeghi et al. | Jun 2000 | A |
6085493 | DeBusk et al. | Jul 2000 | A |
6088362 | Turnbull et al. | Jul 2000 | A |
6093146 | Filangeri | Jul 2000 | A |
6097308 | Albert et al. | Aug 2000 | A |
6128512 | Trompower et al. | Oct 2000 | A |
6133837 | Riley | Oct 2000 | A |
6147592 | Ulrich et al. | Nov 2000 | A |
6183417 | Geheb et al. | Feb 2001 | B1 |
6208250 | Dixon et al. | Mar 2001 | B1 |
6218942 | Vega et al. | Apr 2001 | B1 |
6241668 | Herzog | Jun 2001 | B1 |
6259355 | Chaco et al. | Jul 2001 | B1 |
6264614 | Albert et al. | Jul 2001 | B1 |
6279183 | Kummer et al. | Aug 2001 | B1 |
6287253 | Ortega et al. | Sep 2001 | B1 |
6302844 | Walker et al. | Oct 2001 | B1 |
6314556 | DeBusk et al. | Nov 2001 | B1 |
6320510 | Menkedick et al. | Nov 2001 | B2 |
6344794 | Ulrich et al. | Feb 2002 | B1 |
6348777 | Brown et al. | Feb 2002 | B1 |
6362725 | Ulrich et al. | Mar 2002 | B1 |
6364834 | Reuss et al. | Apr 2002 | B1 |
6398727 | Bui et al. | Jun 2002 | B1 |
6406426 | Reuss et al. | Jun 2002 | B1 |
6407335 | Franklin-Lees et al. | Jun 2002 | B1 |
6412980 | Lounsberry et al. | Jul 2002 | B1 |
6416471 | Kumar et al. | Jul 2002 | B1 |
6421649 | Rattner | Jul 2002 | B1 |
6439769 | Polkus et al. | Aug 2002 | B1 |
6441742 | Lovely et al. | Aug 2002 | B1 |
6442290 | Ellis et al. | Aug 2002 | B1 |
6445299 | Rojas, Jr. | Sep 2002 | B1 |
6450956 | Rappaport et al. | Sep 2002 | B1 |
6462656 | Ulrich et al. | Oct 2002 | B2 |
6486792 | Moster et al. | Nov 2002 | B1 |
6493568 | Bell et al. | Dec 2002 | B1 |
6494831 | Koritzinsky | Dec 2002 | B1 |
6510344 | Halpern | Jan 2003 | B1 |
6516324 | Jones et al. | Feb 2003 | B1 |
6526310 | Carter et al. | Feb 2003 | B1 |
6529164 | Carter | Mar 2003 | B1 |
6533453 | Heidsieck et al. | Mar 2003 | B1 |
6535576 | Vafi et al. | Mar 2003 | B2 |
6539393 | Kabala | Mar 2003 | B1 |
6544173 | West et al. | Apr 2003 | B2 |
6544174 | West et al. | Apr 2003 | B2 |
6551243 | Bocionek et al. | Apr 2003 | B2 |
6553106 | Gould et al. | Apr 2003 | B1 |
6554174 | Aceves | Apr 2003 | B1 |
6556630 | Brinsfield et al. | Apr 2003 | B1 |
6560274 | Leitgeb et al. | May 2003 | B1 |
6572556 | Stoycos et al. | Jun 2003 | B2 |
6575901 | Stoycos et al. | Jun 2003 | B2 |
6581204 | DeBusk et al. | Jun 2003 | B2 |
6584182 | Brodnick | Jun 2003 | B2 |
6584454 | Hummel, Jr. et al. | Jun 2003 | B1 |
6585645 | Hutchinson | Jul 2003 | B2 |
6589170 | Flach et al. | Jul 2003 | B1 |
6593528 | Franklin-Lees et al. | Jul 2003 | B2 |
6594146 | Frangesch et al. | Jul 2003 | B2 |
6594519 | Stoycos et al. | Jul 2003 | B2 |
6600421 | Freeman | Jul 2003 | B2 |
6603494 | Banks et al. | Aug 2003 | B1 |
6609115 | Mehring et al. | Aug 2003 | B1 |
6616606 | Petersen et al. | Sep 2003 | B1 |
6622088 | Hood | Sep 2003 | B2 |
6640246 | Gary, Jr. et al. | Oct 2003 | B1 |
6643238 | Nakajima | Nov 2003 | B2 |
6650346 | Jaeger et al. | Nov 2003 | B1 |
6659947 | Carter et al. | Dec 2003 | B1 |
6665385 | Rogers et al. | Dec 2003 | B2 |
6665820 | Frowein et al. | Dec 2003 | B1 |
6669630 | Joliat et al. | Dec 2003 | B1 |
6671547 | Lyster et al. | Dec 2003 | B2 |
6671563 | Engelson et al. | Dec 2003 | B1 |
6685633 | Albert et al. | Feb 2004 | B2 |
6689091 | Bui et al. | Feb 2004 | B2 |
6694367 | Miesbauer et al. | Feb 2004 | B1 |
6694509 | Stoval et al. | Feb 2004 | B1 |
6697765 | Kuth | Feb 2004 | B2 |
6707476 | Hochstedler | Mar 2004 | B1 |
6714913 | Brandt et al. | Mar 2004 | B2 |
6721818 | Nakamura | Apr 2004 | B1 |
6726634 | Freeman | Apr 2004 | B2 |
6727818 | Wildman et al. | Apr 2004 | B1 |
6731311 | Bufe et al. | May 2004 | B2 |
6731989 | Engleson et al. | May 2004 | B2 |
6740033 | Olejniczak et al. | May 2004 | B1 |
6749566 | Russ | Jun 2004 | B2 |
6751630 | Franks et al. | Jun 2004 | B1 |
6754545 | Haeuser et al. | Jun 2004 | B2 |
6754883 | DeBusk et al. | Jun 2004 | B2 |
6759959 | Wildman | Jul 2004 | B2 |
6763541 | Mahoney et al. | Jul 2004 | B2 |
6771172 | Robinson et al. | Aug 2004 | B1 |
6773396 | Flach et al. | Aug 2004 | B2 |
6778225 | David | Aug 2004 | B2 |
6781517 | Moster et al. | Aug 2004 | B2 |
6784797 | Smith et al. | Aug 2004 | B2 |
6791460 | Dixon et al. | Sep 2004 | B2 |
6792396 | Inda et al. | Sep 2004 | B2 |
6801227 | Bocionek et al. | Oct 2004 | B2 |
6807543 | Muthya | Oct 2004 | B2 |
6825763 | Ulrich et al. | Nov 2004 | B2 |
6826578 | Brackett et al. | Nov 2004 | B2 |
6828992 | Freeman et al. | Dec 2004 | B1 |
6829796 | Salvatini et al. | Dec 2004 | B2 |
6830549 | Bui et al. | Dec 2004 | B2 |
6832199 | Kucek et al. | Dec 2004 | B1 |
6840117 | Hubbard, Jr. | Jan 2005 | B2 |
6847302 | Flanagan et al. | Jan 2005 | B2 |
6847814 | Vogeleisen | Jan 2005 | B1 |
6868256 | Dooley et al. | Mar 2005 | B2 |
6871211 | Labounty et al. | Mar 2005 | B2 |
6873884 | Brackett et al. | Mar 2005 | B2 |
6876985 | Kawanaka | Apr 2005 | B2 |
6885288 | Pincus | Apr 2005 | B2 |
6891909 | Hurley et al. | May 2005 | B2 |
6904161 | Becker et al. | Jun 2005 | B1 |
6909995 | Shiraishi | Jun 2005 | B2 |
6912549 | Rotter et al. | Jun 2005 | B2 |
6915170 | Engleson et al. | Jul 2005 | B2 |
6925367 | Fontius | Aug 2005 | B2 |
6930878 | Brackett et al. | Aug 2005 | B2 |
6987448 | Catton et al. | Jan 2006 | B2 |
7068143 | Doering et al. | Jun 2006 | B2 |
7464001 | Adams | Dec 2008 | B1 |
7868740 | McNeely et al. | Jan 2011 | B2 |
8031057 | Mcneely et al. | Oct 2011 | B2 |
20010050610 | Gelston | Dec 2001 | A1 |
20010051765 | Walker et al. | Dec 2001 | A1 |
20020014951 | Kramer et al. | Feb 2002 | A1 |
20020044043 | Chaco et al. | Apr 2002 | A1 |
20020044059 | Reeder et al. | Apr 2002 | A1 |
20020057340 | Fernandez et al. | May 2002 | A1 |
20020067273 | Jaques et al. | Jun 2002 | A1 |
20020070867 | Conway et al. | Jun 2002 | A1 |
20020080037 | Dixon et al. | Jun 2002 | A1 |
20020103674 | Reeder et al. | Aug 2002 | A1 |
20020143320 | Levin | Oct 2002 | A1 |
20020151990 | Ulrich et al. | Oct 2002 | A1 |
20020173991 | Avitall | Nov 2002 | A1 |
20020186136 | Schuman | Dec 2002 | A1 |
20020196141 | Boone et al. | Dec 2002 | A1 |
20030010345 | Koblasz et al. | Jan 2003 | A1 |
20030028449 | Heinen et al. | Feb 2003 | A1 |
20030030569 | Ulrich et al. | Feb 2003 | A1 |
20030052787 | Zerhusen et al. | Mar 2003 | A1 |
20030074222 | Rosow et al. | Apr 2003 | A1 |
20030146835 | Carter | Aug 2003 | A1 |
20030149598 | Santoso et al. | Aug 2003 | A1 |
20030176798 | Simon | Sep 2003 | A1 |
20030206116 | Weiner et al. | Nov 2003 | A1 |
20040183681 | Smith | Sep 2004 | A1 |
20040183683 | Funahashi | Sep 2004 | A1 |
20040183684 | Callaway | Sep 2004 | A1 |
20040186358 | Chernow et al. | Sep 2004 | A1 |
20040193449 | Wildman et al. | Sep 2004 | A1 |
20050035862 | Wildman et al. | Feb 2005 | A1 |
20050219059 | Ulrich et al. | Oct 2005 | A1 |
20050242946 | Hubbard, Jr. et al. | Nov 2005 | A1 |
20060279427 | Becker et al. | Dec 2006 | A1 |
20070120689 | Zerhusen et al. | May 2007 | A1 |
20080010752 | Chambers et al. | Jan 2008 | A1 |
20090070942 | Chambers et al. | Mar 2009 | A1 |
20120013452 | McNeely et al. | Jan 2012 | A1 |
Number | Date | Country |
---|---|---|
WO 02091297 | Nov 2002 | WO |
WO 2004036390 | Apr 2004 | WO |
Number | Date | Country | |
---|---|---|---|
20090056027 A1 | Mar 2009 | US |