The present invention relates to a hospital bed. More particularly, the present invention relates to a hospital bed illustratively having siderails, an articulating deck, and a mattress.
Hospital bed and other patient supports are known. Typically, such patient supports are used to provide a support surface for patients or other individuals for treatment, recuperation, or rest. Many such patient supports include a frame, a deck supported by the frame, a mattress, siderails configured to block egress of a patient from the mattress, and a controller configured to control one or more features of the bed.
The detailed description particularly refers to the accompanying figures in which:
A patient support 10 according to the present disclosure is shown in
Head end siderails 20 are coupled to head section 38 and may be moved between raised and lowered positions. Foot end siderails 22 are coupled to weigh frame 32 and may also be moved between raised and lowered positions.
A control system 44 is provided to control various functions of patient support 10. Control system 44 and the remainder of patient support 10 are powered by an AC plug connection 45 to a building outlet or a battery 46 supported by frame 12.
Control system 44 operates and monitors a plurality of linear actuators 48 provided to extend and retract adjustable length leg section 42, to move intermediate frame 32 relative to base frame 28, to move head section 38 relative to weigh frame 32, to move seat section 40 relative to weigh frame 32, and to move leg section 42 relative to seat section 40.
Control system 44 includes a plurality of input devices including a detachable siderail controller 50 configured to removably couple to any of head and foot end siderails 20, 22, a first pair of permanent siderail controllers 52 coupled to head end siderails 20, a second pair of permanent siderail controllers 54 pivotably coupled to head end siderails 20, and a pair of foot pedal controls 56 coupled to base frame 28.
Control system 44 also includes an obstacle detection device 58 illustratively coupled to base frame 28 to detect possible clearance issues between intermediate frame 32 and base frame 28. Control system 44 further includes a plurality of actuator position detectors or motor sensor (as discussed below) provided with each of the plurality of actuators 48. A plurality of load cells (discussed below) are also provided between weigh frame 36 and intermediate frame 32 to provide signals that indicate of the weight supported by intermediate frame 32. Control system 44 uses these signals to determine the weight of a patient positioned on mattress 14. Additionally, control system 44 includes a plurality of siderail position detectors or sensors 60 configured to provide signals indicative of the position of siderails 20, 22.
Control system 44 is configured to control a pump 64 in fluid communication with a manifold 62 supported on head section 38 of deck 26. Manifold 62 is in fluid communication with mattress 14 to regulate the flow of air to and from mattress 14. Mattress 14 includes an outer cover 66 and a first pair of connectors 68 coupled to outer cover 66. A second pair of connectors 70 is provided on head section 38 of deck 26 that align and couple with first pair of connectors 68.
Deck Support
As previously mentioned and as shown in
As explained in more detail below, lift arms 34 and linear actuators 48a and 48b, commonly referred to as a hi/low mechanism, are configured to position deck support 24 in at least the following positions: a raised or upper position wherein intermediate frame 32 and weigh frame 36 are above base frame 28 (
Lift Arms
Referring to
Each head link 106 is slidably coupled to base frame 28 and pivotably coupled to intermediate frame 32. Alternatively, each of the head links 106 is slidably coupled to either the base frame 28 or the intermediate frame 32. As illustratively shown in
Guide 114 includes an upper channel 116 and a lower channel 118 which define two directions of travel 120 and 121 for slide block 111. Upper channel 116 and lower channel 118 are further configured to restrict the movement of slide block 111 in any direction other than directions of travel 120 and 121. Slide blocks 111 are preferred because they are capable of spreading the load of intermediate frame 32, deck 26 and other patient support components over a larger surface area than other types of couplers. Alternative methods of coupling the head links 106 to the base frame 28 can be used provided that the lower portion of the head links 106 can pivot relative to the base frame 28 and can move along the directions of travel 120, 121. Examples include a roller, a plurality of rollers, or interlocking members.
Illustratively, an upper end 122 of each head link 106 is pivotably coupled to intermediate frame 32 through a cross link 124. Alternatively, the head links 106 are directly pivotably coupled to the intermediate frame 32. In a further alternative, the head links 106 are pivotably coupled to the base frame 28 and slidably and pivotably coupled to the intermediate frame 32.
Cross link 124 extends between each head link 106 and is rigidly coupled to each head link 106. As such, cross link 124 coordinates the simultaneous movement of head links 106. Cross link 124 is received through openings (not shown) formed in intermediate frame 32 and is pivotable relative to intermediate frame 32. In one embodiment, a bearing or other means is used to increase the ease by which cross link 124 pivots relative to intermediate frame 32.
Each foot link 108, is slidably and pivotably coupled to base frame 28. Illustratively each foot link 108 is coupled to base frame 28 at pivot 126 by slide block 128 which is pivotably coupled to a lower portion 130 of foot link 108 and slidably received in a guide 132 coupled to base frame 28. Guide 132 and slide block 128 are generally identical to guide 114 and slide block 111 discussed in conjunction with head links 106. As such, guide 132 is configured to restrict the movement of slide block 128 in any direction other than directions of travel 120 and 121. Alternative methods of coupling the foot links 108 to the base frame 28 can be used provided that the lower portion of the foot links 108 can pivot relative to the base frame 28 and can move along the directions of travel 120, 121. Examples include a roller, a plurality of rollers, or interlocking members.
An upper end 134 of each foot link 108 is pivotably coupled to intermediate frame 32 through a cross link 136. Alternatively, the foot links 108 are directly pivotably coupled to the intermediate frame 32. Cross link 136 is generally identical to cross link 124 and cooperates with intermediate frame 32 and foot links 108 in the same manner as cross link 124 with intermediate frame 32 and head links 106. Alternatively, the upper end 134 of each foot link 108 is slidably and pivotably coupled to the intermediate frame 32 and pivotably coupled to the base frame 28.
Guide links 110 restrict the motion of foot links 108 such that the pivot point 138 between foot links 108 and intermediate frame 32 is restrained to move vertically without moving horizontally. This restriction prevents horizontal movement of intermediate frame 32 relative to base frame 28 during the raising and lowering of intermediate frame 32. This restrained movement prevents intermediate frame 32 from moving through an arc while moving between the upper position of
It will be appreciated that, in order for guide links 110 to perform the restriction function, the distance between pivots 140 (pivot between guide link 110 and foot link 108) and 142 (pivot between guide links 110 and base frame 28) of guide links 110 is one half the distance between pivot 126 (pivot between slide blocks 128 and base frame 28) and pivot 138 (pivot between upper ends 134 of foot links 108 and intermediate frame 32). Further, each guide link 110 is pivotably coupled to the respective foot link 108 at pivot 140 that is one half the distance between pivot 126 of the associated slide block 128 and pivot 138 of the upper end of the respective foot link 108. Thus, the distance between upper pivot 140 of each guide link 110 and the lower pivot 142 of each guide link 110 is equal to the distance between upper pivot 140 of each guide link 110 and upper pivot 138 of each foot link 108. As a result of this link geometry, upper pivots 138 of foot links 108 are maintained in vertical alignment with lower pivot 142 of guide links 110 during the raising and lowering of intermediate frame 32 relative to base frame 28.
Linear Actuators
As stated earlier, linear actuators 48a and 48b provide power to actuate lift arms 34 and in turn to raise and lower intermediate frame 32 relative to base frame 28. Linear actuator 48a is coupled to and actuates head links 106 and linear actuator 48b is coupled to and actuates foot links 108. As such, foot end 104 and head end 102 of intermediate frame 32 can be raised and lowered independent of one another. Alternatively, head links 106 and foot links 108 of the decking system are coupled together such that a single actuator raises and lowers the head end 102 and the foot end 104 of the intermediate frame 32 at the same time.
Illustratively, a first end 146 of linear actuator 48a is coupled to head links 106 through an extension link 148 that is rigidly coupled to cross link 124 which, in turn, is rigidly coupled to head links 106. As shown in
Similarly, a first end 158 of linear actuator 48b is coupled to foot links 108 through an extension link 160 that is rigidly coupled to cross link 136 which, in turn, is rigidly coupled to foot links 108. As shown in
Each actuator 48a and 48b is preferably an electric linear actuator having respective cylinder bodies 170, cylinder rods 172, and motors 604 that operate to extend and retract cylinder rods 172 relative to cylinder bodies 170. As such, actuators 48a and 48b have variable lengths and therefore adjust the distance between pivot pins 150 and 156 and pivot pins 162 and 168, respectively. In one illustrative embodiment, actuators 48a and 48b are Linak actuators, Model No. LA34, available from LINAK U.S. Inc. located at 2200 Stanley Gault Parkway, Louisville Ky. 40223. Further, actuators 48c, 48d, 48e and 48f are also illustratively electric linear actuators, and in one embodiment are also Linak actuators. More particularly, actuator 48c is illustratively a Linak actuator, Model No. LA34 and actuators 48d-48f are illustratively Linak actuators, Model No. LA31. In alternative embodiments, all of the actuators 48 or any one or more of the actuators are other types of electric actuators, pneumatic actuators, hydraulic actuators, mechanical actuators, link systems or other components known to those of ordinary skill in the art for coordinating movement of components relative to one another.
The actuation of either actuator 48a or 48b alone causes either the respective head end 102 of intermediate frame 32 or the respective foot end 104 of intermediate frame 32 to be raised or lowered relative to base frame 28. Referring to
Head end 102 of intermediate frame 32 is raised relative to base frame 28 by the extension of cylinder rod 172 of actuator 48a. As cylinder rod 172 of actuator 48a is extended the distance between pivot pins 150 and 156 is increased. This increase in pivot spacing causes extension link 148 to move away from first bracket 154 which, in turn, causes cross link 124 and head links 106 to rotate in a direction 178 counter to direction 176 about pivot 126. The rotation of head links 106 in direction 178 counter to direction 176 causes lower portions 112 of head links 106 to travel in direction 121. As a result, upper ends 122 of head links 106 are raised relative to base frame 28 and therefore, head end 102 of intermediate frame 32 is raised relative to base frame 28.
Foot end 104 of intermediate frame 32 is lowered relative to base frame 28 by the retraction of cylinder rod 172b of actuator 48b. As cylinder rod 172b of actuator 48b is retracted the distance between pivot pins 162 and 168 is reduced. This reduction in pivot spacing causes extension link 160 to move toward second bracket 166 which, in turn, causes cross link 136 and foot links 108 to rotate in direction 180 about pivot 138. Since lower portions 130 of foot links 108 are restrained to move only in directions of travel 120 and 121 of guide 132, the rotation of foot links 108 in direction 180 causes lower portions 130 of foot links 108 to travel in direction 121. As a result, upper ends 134 of foot links 108 are lowered relative to base frame 28 and therefore, foot end 104 of intermediate frame 32 is lowered relative to base frame 28.
Foot end 104 of intermediate frame 32 is raised relative to base frame 28 by the extension of cylinder rod 172b of actuator 48b. As cylinder rod 172b of actuator 48b is extended, the distance between pivots 162 and 168 is increased. This increase in pivot spacing causes extension link 160 to move away from second bracket 166 which, in turn, causes cross link 136 and foot links 108 to rotate in a direction 182 counter to direction 180 about pivot 138. The rotation of foot links 108 in direction 182 counter to direction 180 causes lower portions 130 of foot links 108 to travel in direction 120. As a result, upper ends 134 of foot links 108 are raised relative to base frame 28 and therefore, foot end 104 of intermediate frame 32 is raised relative to base frame 28.
The simultaneous actuation of actuators 48a and 48b causes both head end 102 and foot end 104 of intermediate frame 32 to raise or lower relative to base frame 28. As shown in
Further, in an alternative embodiment the direction of one of the actuators 48a, 48b is reversed such that to raise the intermediate frame 32 relative to the base frame 28 a first of the two actuators 48a, 48b is extended and the second actuator 48b, 48a is retracted. Further, to lower the intermediate frame 32 relative to the base frame 28 the second actuator 48b, 48a is extended and the first actuator 48a, 48b is retracted.
Referring further to
Deck support 24 is moved from the upper position of
Since actuators 48a and 48b retract and extend at substantially the same rates, the simultaneous retraction of actuators 48a and 48b causes intermediate frame 32 to be maintained in a generally horizontal position as it is vertically transitioned from the upper position of
One of the purposes of intermediate frame 32 being configured to raise and lower relative to base frame 28 is to aid in the ingress of a patient to and egress of a patient from patient support 10. To allow intermediate frame 32 to lower further and thus provide additional assistance in the ingress to and egress of the patient from patient support 10, patient support 10 is configured to provide a lowered position, as shown in
Nesting Frames
As shown in
It should be noted that when deck support 24 is in the lowered position, head links 106, foot links 108 and guide links 110 are rotated beyond horizontal, such that pivots 126, 138, 140 are generally lower than pivots 142, 143, 144. In one embodiment, head links 106, foot links 108 and guide links 110 are generally rotated from approximately 80 degrees above horizontal in the upper position of
It is further contemplated that portions of weigh frame 36 are configured to nest within base frame 28 when intermediate frame 32 is in the lowered position. Longitudinally extending members 198, 200, shown in
Weigh Frame
As noted above, intermediate frame 32 is coupled to weigh frame 36. As shown in
Referring further to
Block 221 is coupled to a mounting bar 223 of weigh frame 36 by suitable fasteners, such as bolts (not shown). Mounting bar 223 and block 221 are received in the interior region of weigh frame members 198, 200 as shown best in
Load cells 220, 222, 224, 226 are further configured to be coupled to transversely extending members 215, 217 of intermediate frame 32, shown in
The weight of weigh frame 36 and anything supported by weigh frame 36, such as deck 26, mattress 14, and a patient, is transmitted to load cells 220, 222, 224, 226. This weight deflects or otherwise changes a characteristic of load cells 220, 222, 224, 226 that is detected to determine the total weight supported thereby. By subtracting a known weight of weigh frame 36, deck 26, mattress 14 and any other bed components supported on weigh frame 36, the weight of the patient positioned on patient support 10 can be determined. Additional description of illustrative load cells and methods for determining a patient's weight, position in the bed, and other indications provided by load cells is provided in U.S. patent application Ser. No. 09/669,707, filed Sep. 26, 2000, titled Load Cell Apparatus, to Mobley et al., the disclosure of which is expressly incorporated by reference herein. According to alternative illustrative embodiments of the present disclosure, other configurations and methods of using load cells or other devices to determine a patient's weight or other information related to the patient known to those of ordinary skill in the art are provided herein.
Mattress Deck
As shown in
Seat section 40 is positioned adjacent head section 38 and is pivotably coupled to weigh frame 36. In the illustrated embodiment as shown in
Leg or foot section 42 is positioned adjacent seat section 40 and is pivotably coupled to seat section 40. In the illustrated embodiment as shown in
Deck 26 is configured to support mattress 14. As shown in
The lowered central portion, generally corresponding to floors 264 and 266 of head section 38 and seat section 40, respectively, provides ample space for mattress 14 to be positioned. By having a lowered central portion, the pivot of a patient's hip when the patient is positioned on mattress 14 is more in line with pivots 232, 237 of head section 38 and seat section 40 and provides ample space to provide a mattress 14 that provides adequate support for the patient. In one illustrative embodiment, the position of the pivot of the hip of the patient is about two inches above the pivots 232, 237 of the head and seat sections 38 and 40 of the deck 26. In another illustrative embodiment, the position of the pivot of the hip of the patient is generally in line with the pivots 232, 237 of the head and seat sections 38 and 40 of the deck 26. By minimizing the distance between the pivot of the patient's hip and the pivots 232, 237 of the head and seat sections 38 and 40, the amount of shear exerted against the patient is reduced as either the head or seat 38, 40 section is raised or lowered. By reducing the amount of shear exerted against the patient, the possibility of the patient experiencing skin breakdown is reduced.
As further shown in
In one illustrative embodiment, as previously described, the distance between the pivot of a patient's hip and pivots 232, 237 is about two inches. Referring to
Head Section
Referring again to
On the side opposite the mattress side, or manifold side of partition 272, manifold 62 is coupled to partition 272. Referring to
As explained in more detail herein, first and second manifold receiving connectors 70 are configured to be coupled to mattress connectors 68, which are in fluid communication with mattress 14. Manifold 62 is configured to be in fluid communication with pump 64. As such, mattress 14 may be easily assembled to patient support 10 by simply coupling first and second manifold receiving connectors 70 with connectors 68. In alternate embodiments, a single or three or more manifold receiving connectors are coupled to the partition.
In one embodiment, at least vertical wall 274 of partition 272 is removably coupled to head section 38. Vertical wall 274 is assembled with manifold 62 and first and second manifold receiving connectors 70 to form a sub-assembly. The sub-assembly is then coupled to head section 38 by any suitable fastening means including screws, bolts, snaps, clasps, latches, or other suitable fastening means. As such, the sub-assembly may be configured for a variety of mattress configurations and assembled into the remainder of patient support 10.
Foot Section
Referring further to
Referring to
Referring further to
First leg section member 290 and second leg section member 292 are maintained in longitudinal alignment at least in part by guide members 306a, 306b. Illustratively, guide member 306a, 306b are telescoping tubes that extend and retract in a linear fashion as the first and second leg section members 290 and 292 move relative to each other. As shown in
Referring to
Referring further to
In alternative embodiments other suitable extendable foot sections 42 may be used. Illustrative suitable foot sections include the patient supports and corresponding foot sections described in U.S. Pat. No. 6,212,714 issued Apr. 10, 2001 to Allen et al., the disclosure of which is expressly incorporated by reference herein, and U.S. Pat. No. 6,163,903 issued Dec. 26, 2000 to Weismiller et al., the disclosure of which is expressly incorporated by reference herein.
As previously mentioned, leg section 42 of deck 26 is adjustable in length so that it can be moved from a retracted position to an extended position. Preferably, the length of leg section 42 is adjusted depending upon the height of the patient positioned on mattress 14 so that the patient's foot is positioned adjacent to footboard 18, shown in
Also illustratively, mattress 14 is configured to be extended and retracted with leg section 42 as discussed in more detail herein. As such, the heel of the patient may be maintained over a given section of mattress 14, such as heel pressure relief member 2154 (
According one embodiment of the present disclosure, the length of leg section 42 corresponds to the position of head section 38. For example, if head section 38 is raised to the titled position as shown in
Preferably, the degree of automatic extension of leg section 42 is a function of the angle of head section 38. The further up head section 38 is raised from a generally linear relationship with seat section 40, the more leg section 42 is extended so that heel pressure relief member 2154 is continuously positioned under the patient's heel throughout the range of motion of head section 38.
Mattress Deck Articulation
As stated previously, patient support 10 is positionable in a plurality of positions. Referring to
Referring to
Also, shown in
Referring to
Referring further to
Further, leg section actuator 48e is lengthened by control system 44 when seat section 40 is lowered from the elevated position shown in
The length of slot 324 is selected to allow actuator 48e to move from a fully extended position to a fully retracted position while first end 320 of actuator 48e travels in slot 324. As such, actuator 48e will encounter the end of its range of motion or travel (fully retracted) before or coincident with first end 320 of actuator 48e reaching second end 326 of slot 324. Therefore, leg section 42 will not crush or otherwise damage obstruction 330 due to the continued pressure applied by actuator 48e, actuator 48e will not be damaged due to a larger than expected load being placed on actuator 48e, and patient support 10 will not be damaged.
Alternative methods may be used to keep the leg section 42 from damaging the obstruction and to keep from damaging the actuator 48e. A first example is to monitor the load placed on the actuator 48e with the control system 44 and to disengage or reverse the motion of the actuator 48e in response to a larger than expected load for retracting the actuator 48e. A second example is to place a pressure sensor along the bottom of the leg section 42 and to disengage the actuator 48e when a higher than expected pressure is detected. An illustrative sensor may be the obstacle detection system of the present invention disclosed herein. Other known safety systems may also be used.
In alternative embodiments, the elongated slot 324 is located on the bracket 248 attached to the weigh frame 36 and the actuator 48e is pivotably coupled to the leg section 42 and slidably and pivotably coupled to the weigh frame 36. In a further alternative embodiment, the elongated slot 324 is located on the joint between the leg section 42 and the seat section 40 such that the leg section 42 and the seat section 40 are pivotably and slidably coupled, the leg section 42 and the actuator 48e are pivotably coupled and the actuator 48e and the weigh frame 36 are pivotably coupled. In still further alternative embodiments, the elongated slot 324 feature is incorporated into the configuration for the head section 38, is incorporated into the configuration for the seat section 40, or is incorporated into the lifting arms 34 configuration.
Referring to
A further safety device 340 is shown in
In
As second end 250 of leg section 42 is translated in direction 341 and leg section 42 is rotated in direction 343 relative to seat section, first end 320 of actuator 48e is traveling within slot 324. As discussed earlier in connection with
A further instance wherein safety device 340 protects both leg section 42 and an obstruction from damage is when deck 26 is in a linear configuration with leg section 42 in an extended position and the patient support 10 is moved to a Reverse Trendelenburg position from a low position. As shown in
CPR Configuration
Often it is required to configure patient support 10 in a CPR configuration which is tailored to assist a caregiver in providing CPR to the patient supported on patient support 10. In one illustrative example, a CPR configuration is defined by placing the head, seat and leg sections 38, 40, 42 in a generally linear relationship and to inflate an upper bladder assembly 2122 to an elevated or a maximum pressure in the manner further described herein. In a further illustrative CPR configuration, the head, seat and leg sections 38, 40, 42 are placed in a generally linear relationship, the upper bladder assembly 2122 is inflated to an elevated or a maximum pressure and decking support 24 is oriented such that head end 102 is lower relative to foot end 104, generally a Trendelenburg position as shown in
Patient support 10 may be placed in the preferred CPR configuration by providing an indication to control system 44 which in turn controls actuators 48c, 48d, 48e to place head, seat, and leg sections 38, 40, 42 in a generally linear relationship, controls pump 64 to inflate upper bladder assembly 2122 to the desired pressure, and controls actuators 48a and 48b of deck support 24 to lower head end 102 relative to foot end 104. The details of control system 44 and how control system 44 controls actuators 48a-f and pump 64 are further described herein.
Illustratively, patient support 10 is placed in the preferred CPR configuration by manually lowering head section 38 to a lowered position and providing an indication to control system 44 which, in turn, controls actuators 48d and 48e to place head, seat and leg sections 38, 40, 42 in a linear relationship, controls pump 64 to inflate upper bladder assembly 2122 to the desired pressure, and controls actuators 48a and 48b of deck support 24 to lower head end 102 relative to foot end 104. Referring to
Referring to
In one illustrative embodiment, handle 352 includes an indicia 353, shown in
Referring to
Slide bracket 396 is coupled to each handle bracket 354 through cables 368. As such, the rotation of either handle 352a, 352b by a caregiver rotates respective handle bracket 354a, 354b which, in turn, translates first end 366a, 366b of cable 368a, 368b away from first end 372a, 372b of cable housing 374a, 374b, which translates second end 382a, 382b of cable 368a, 368b toward second end 384a, 384b of cable housing 374a, 374b in a direction 408 (
As known in the art, release pin 406 is biased in direction 410 counter to direction 408. As release pin 406 moves in direction 410, cylinder rod 172c of actuator 48c is no longer freely movable relative to cylinder body 170 of actuator 48c. Therefore, when the caregiver releases both handles 352a, 352b release pin 406 due to its bias translates slide bracket 396 in direction 410 which in turn through respective cables 368a, 368b rotates handle bracket 354a, 354b and handle 352a, 352b in direction 381 (
Referring to
Gas spring 432 has an uncompressed state generally corresponding to head section 38 being positioned between the intermediate position and the elevated position and a compressed state generally corresponding to head section 38 being positioned between the intermediate position and the lowered position. As head section 38 moves from the intermediate position to the lowered position, first end 434 of gas spring 432 stays proximate to second end 442 of slot 436 and a rod 444 of gas spring 432 is forced to slidably move into a housing 446 of gas spring 432 against the biasing force exerted by gas spring 432. In general, gas spring 432 prefers to be in the uncompressed state and resists movement to the compressed state. As such, gas spring 432 resists the movement of head section 38 from the intermediate position to the lowered position and thereby slows the rate of travel of head section 38 to the lowered position.
Gas spring 432 is of conventional design. In alternative embodiments, other types of dampers may be used. Example dampers include compressible foam, air bladders, compressible springs, and other suitable damping means.
Referring to
If switch 448 is opened as a result of the caregiver releasing handle 352 before control system 44 completes the aforementioned tasks, control system 44 aborts the uncompleted tasks. For example, if the caregiver could release handle 352 when head end 102 is approximately 5 degrees lower than foot end 104. It is understood that switch 448 may be located in a variety of locations and activated in a variety of ways. For instance, switch 448 may be placed on handle 352 or handle bracket 354. In alternate embodiments, the handle 352 is replaced by a foot pedal, a button, a switch, a lever arm or other suitable actuatable members.
Referring to
Referring to
Caster Braking System
Referring to
Each caster device 30 includes a braking mechanism (not shown) that is coupled to a caster-brake link, illustratively a faceted shaft such as hexagonal shaft 453, such that rotation of hexagonal shaft 453 engages the braking mechanism. As shown in
As shown in
Further, transversely spaced caster device pairs 30a, 30b and 30c, 30d are interconnected by a longitudinally extending brake links 458a, 458b, respectively. Brake links 458a, 458b are configured to interact with the caster device pairs 30a, 30b, 30c, 30d such that the braking of any one caster device 30a, 30b, 30c, 30d simultaneously brakes the remaining caster devices 30a, 30b, 30c, 30d.
As shown in
In operation, a caregiver depresses one of the foot pedals 452, such as foot pedal 452a, to simultaneously brake all four caster devices 30a, 30b, 30c, 30d. Illustratively, foot pedals 452 are shown on a first side of each caster device 30. Alternatively, the foot pedals 452 may be located on the other side of the caster devices 30 or each caster device 30 could have more than a single foot pedal 452 associated with the caster device 30. The depressed foot pedal 452a causes the rotation of hexagonal shaft 453a in direction 470 as illustrated in
The rotating of hexagonal shaft 453a in turn engages the braking mechanism (not shown) of caster device 30a, rotates rod 457a in direction 470 and rotates bracket 462a in direction 470. The rotation of rod 457a further rotates hexagonal shaft 453a in direction 470 thereby engaging the brake mechanism of caster device 30b. The rotation of bracket 462a translates brake link 458a in a direction 472. The translation of brake link 458a in direction 472 results in the rotation of bracket 462c in direction 470 which, in turn, rotates hexagonal shaft 453c in direction 470, thereby engaging the brake mechanism of caster device 30c. The braking mechanism of caster device 30d is engaged by the rotation of hexagonal shaft 453d either through the translation of brake link 458b similar to the translation of brake link 458a and/or through the rotation of rod 457b similar to the rotation of rod 457a. In alternative embodiments, the caster braking system 450 includes only two transverse rods 457 and a single brake link 458 or two brake links 458 and a single transverse rod 457.
In order to unlock the caster braking system 450 of the present invention, one of the four pedals 452, such as pedal 452a is rotated in a direction 473 counter to the direction 470, thereby disengaging the braking mechanism of caster device 30a. The braking devices of casters 30b, 30c, 30d are disengaged in a manner similar to how they are engaged through rods 457a, 457b and brake links 458a, 458b.
As stated previously, it is advantageous to lower intermediate frame 32 as low as possible to the floor to aid egress from and ingress to patient support 10 and to prevent injury in case of accidental fall from patient support 10. The configuration of caster braking system 450 has a low profile which provides additional clearance for deck 26, siderails 20, 22 and other patient support components as deck support 24 is lowered. As such, intermediate frame 32 can be further lowered. As shown in
Control System
Referring now to
As shown in
As illustrated in
With reference to
It should be understood that the configuration of network 510 permits addition of new modules and subtraction of existing modules without requiring manual reconfiguration of the existing modules. When a new module is added, network 510 recognizes the module and facilitates communications between the added module and the existing modules automatically. Additionally, it should be noted that network 510 is implemented to operate as a masterless system, wherein each module 512, 514, 516, 518, 520, 522, 524 operates substantially autonomously. One feature of network 510 is the periodic transmission of each module 512, 514, 516, 518, 520, 522, 524 of a “heartbeat” message or status message to the bus for receipt by each of the remaining modules. In this manner, control system 44 periodically verifies the functionality of each module 512, 514, 516, 518, 520, 522, 524 in system 44, and is able to identify a non-operational module by the absence of the module's “heartbeat” message. As further described herein, communications by and among modules 512, 514, 516, 518, 520, 522, 524 are initiated by the individual modules on an event-driven basis.
Power for control system 44 is supplied through power supply module 514. More specifically, AC plug 45 of a power cord (not shown) secured to frame 12 is inserted into a conventional wall outlet supplying 100 VAC, 120 VAC, or 230 VAC power. Power conditioning circuitry 556 converts the AC input power to DC levels for use by the various electronic components of control system 44. Power supply module 514 further facilitates limited functionality of patient support 10 via battery 46 when AC plug 45 is not connected to a wall outlet. Battery 46 is automatically charged by battery charger 552, which provides a status signal to power supply module 514 to indicate the condition of the charge of battery 46. In one embodiment, battery charger 552 permits use of battery 46 as a back-up power source that allows logic module 512 to perform (for 24 hours after AC power has been disconnected) a single operation of high-low up/down, head up/down, tilt/reverse tilt, foot retract/extend, Trendelenburg, and chair out. When AC power is applied to patient support 10, a light emitting diode (LED) 737 (
Power supply module 514 also receives the signal provided by obstacle detection device 58 as described herein. Power supply module outputs a message on network 510 when obstacle detection device 58 outputs a signal indicating the presence of an obstacle so that appropriate action can be taken to prevent injury or damage.
Power supply module 514 also controls night light 548. Specifically, night light 548, which illustratively is mounted to patient support 10 at a location to illuminate the ingress/egress area of patient support 10, is always active or on when AC power is provided to power supply module 514. Night light 548 may be disabled or shut off during battery powered operation. As further described herein, the illumination element (not shown) of night light 548 is enclosed by a housing, which also includes circuitry (not shown) to prevent flicker.
As further described herein, each foot pedal 1724, 1726, 1728, 1730 of foot pedal controls 56 provides a signal when depressed. Power supply module 514 uses these signals to generate messages for transmission on network 510 indicating the status of pedals 1724, 1726, 1728, 1730. Logic module 512 processes such messages to determine whether foot pedal controls 56 are enabled, and to control the operation of DC motors 604 of linear actuators 48, as further described herein. Of course, operation of DC motors 604 is conditioned upon the actual positions of the various components of patient support 10, and upon the status of various lockout signals generated by a caregiver using siderail controllers 52, 54.
Finally, power supply module 514 functions as an input location via a connector (not shown) for test device 558. Test device 558 is configured to operate as an additional module on network 510 for performing diagnostic operations on the various functions of patient support 10 as is further described herein.
Scale/ppm module 516 converts the signals from load cells 220, 222, 224, 226, described above, into actual weight measured on weigh frame 32. This information is outputted for display on a scale display (not shown) and possible transmission to a hospital information network via sidecomm module 524 and remote network interface 572. Scale/ppm module 516 further receives input from bed exit sensor 562, which determines, based on the weight measured on weigh frame 32, whether a patient has exited patient support 10.
Dynamic surface module 518 controls the dynamic air surface or mattress 14. It processes messages initiated by either of siderail controllers 52, 54 to operate solenoids 564 (part of valve assemblies 2406), which in turn adjust the level of inflation of mattress 14 during, for example, a turn assist procedure as further described herein. Additionally, dynamic surface module 518 receives feedback from pressure transducers 566 in the form of electrical signals that indicate pressure measurements of the various bladders of mattress 14. Dynamic surface module 518 operates solenoids 564 in response to the feedback signals from pressure transducers 566 to achieve the desired adjustments to mattress 14.
Sidecomm module 524 functions essentially as an environmental and communications interface. The nurse call, lighting, and entertainment functions are controlled by sidecomm module 524 based on inputs from siderail controllers 50, 52, 54. Sidecomm module 524 outputs signals to control these functions, and communicates with the facility's communication systems via remote network interface 572. Patient support 10 includes a connector 575 (
Logic module 512 controls movement of patient support 10 and is the entry point for nearly all of the position sensors for the various components of patient support 10. As shown, logic module 512 controls the plurality of motors 604 of linear actuators 48 connected to the moveable components (e.g., the articulating deck sections 38, 40, 42, etc.) of patient support 10, as is described in detail herein. When a DC drive motor 604 is activated, a motor sensor 546 associated with the drive motor 604 provides a feedback signal to logic module from which logic module 512 can determine when to deactivate the drive motor 604. When logic module 512 processes a message requesting movement of a particular component of patient support 10, logic module 512 first reads the position of the component (via the appropriate sensor 546). If movement of the component is necessary, then logic module 512 determines whether a lockout signal has been generated from either of the first or second pair of permanent siderail controllers 52, 54. If no lockout is set, logic module 512 controls the appropriate DC drive motor 604, while monitoring the appropriate motor sensor 546, to move the component to the desired position.
Controller Area Network
In one illustrative embodiment, CAN specification 2.0B as specified in ISO 11898 is used for network 510. Network 510 involves three of the seven network layers defined in the ISO model: the physical layer, the data link layer and the application layer. The physical layer includes the actual cabling or wires connecting modules 512, 514, 516, 518, 520, 522, 524. The physical layer further includes the hardware present on each of modules 512, 514, 516, 518, 520, 522, 524 for enabling operation according to the CAN specifications. As indicated above, the hardware includes a transceiver for communicating with the bus and a microcontroller with a built-in CAN controller. A suitable transceiver is a TJA1054 CAN transceiver manufactured by Philips Electronics. A suitable microcontroller is a T89C51CC01 microcontroller manufactured by Amtel. The microcontroller is connected to a crystal oscillator, such as a 20 MHz crystal.
The data layer generates and receives the messages used for communications between modules 512, 514, 516, 518, 520, 522, 524 via the CAN protocol (described below).
The application layer complies with the CANopen specification as further described below. CANopen is an open standard based on a model including communication interface and protocol software, an object dictionary, and an application program interface. The communication interface and protocol software provides a means by which a CANopen device can transmit and receive messages over network 510. The object dictionary is a collection of all of the system variable information communicated over network 510. Finally, the application program interface controls how the application software interacts with the various network parameters.
The communication interface and protocol software includes a variety of services and protocols. One protocol that handles real-time transfer of data between modules is the Process Data Objects (PDO) protocol. Two PDO services are provided: receive (RPDO) and transmit (TPDO). RPDOs are used to obtain updated information for the object dictionary entries of a module 512, 514, 516, 518, 520, 522, 524. TPDOs, on the other hand, are used to transmit updated information to object dictionary entries of another module 512, 514, 516, 518, 520, 522, 524. According to one embodiment of the invention, eight PDOs can be used for each module 512, 514, 516, 518, 520, 522, 524 (four configured as RPDOs and four configured as TPDOs). Each PDO can transfer up to eight bytes of information. While both PDO services share the same basic structure, TPDOs are essentially broadcast messages (any module 512, 514, 516, 518, 520, 522, 524 could receive a TPDO), and RPDOs must be unique for each module 512, 514, 516, 518, 520, 522, 524 that transmits. For example, power supply module 514 may send battery status information to all other modules 512, 516, 518, 520, 522, 524 using a single TPDO. Each module 512, 516, 518, 520, 522, 524 that needs to use the information must have a corresponding RPDO to receive the information from power supply module 514. Moreover, each module 512, 514, 516, 518, 520, 522, 524 that needs information from any other module 512, 514, 516, 518, 520, 522, 524 must have a separate RPDO for the other module 512, 514, 516, 518, 520, 522, 524. In other words, RPDOs can only receive a message from a single module.
PDOs are constructed from object dictionary entries in the manner depicted in
PDOs of control system 44 are event driven. When an object dictionary entry changes, for example, because a system variable changed, the corresponding PDO is automatically transmitted, and the object dictionary entry is automatically updated when a message is received. As explained herein, modules 512, 514, 516, 518, 520, 522, 524 determine which messages to process by analyzing an identifier included in the message. The identifier includes three digits in the form of x8y where x is the TPDO of the transmitting module 512, 514, 516, 518, 520, 522, 524 and y is the module ID of the transmitting module 512, 514, 516, 518, 520, 522, 524. Thus, if a module 512, 514, 516, 518, 520, 522, 524 maps one of its RPDOs with the CAN identifier 584, it correlates to TPDO2 from module 4.
Another protocol is the Service Data Objects (SDO) protocol, which is administered only by a master module. As indicated herein, control system 44 includes a master only when test device 558 is coupled to power supply module 514. In that case, SDOs allow test device 558 access to any object dictionary entry present in the other modules 512, 514, 516, 518, 520, 522, 524.
The object dictionary defines data types, communication objects, and application objects used on network 510. The object dictionary is essentially a group of objects that are accessible via network 510 in a predefined, ordered fashion, using either SDOs or PDOs. All entries in a object dictionary use a “wxyz” format where w is 2 if used by a PDO, 3 if used by an SDO, x is the module identifier for the transmitting module 512, 514, 516, 518, 520, 522, 524, y is 0 if the entry includes error information, 1 if it includes status information, and 8 if it includes control information, and z is a unique value for multiple wxy entries. For example, an object dictionary entry of 2110 indicates that the information is communicated between modules 512, 514, 516, 518, 520, 522, 524 during normal operation (i.e., using a PDO as opposed to an SDO used only during testing and diagnostics), that module number 1 is the transmitter of the information (e.g., scale/ppm module 516), and that it includes status information. The 0 indicates the unique value for multiple wxy entries.
Although in a typical CANopen implementation nodes only have object dictionary entries to information generated or received by the node, in control system 44, all PDO object dictionary entries (2xyz) are implemented in every module 512, 514, 516, 518, 520, 522, 524 to minimize the variance in software among modules 512, 514, 516, 518, 520, 522, 524. SDO entries (3xyz), however, are unique for each module 512, 514, 516, 518, 520, 522, 524 as a result of the application specific nature of built in self test (BIST) data objects.
Messages of the type mentioned above are transmitted and received using message frames, such as the message frame 586 shown in
Linear actuators driven by DC brush motors are commonly used to perform raising and lowering movements (e.g., head, foot, hi/lo, knee, leg) of deck sections on hospital beds. For example, see U.S. Pat. Nos. 5,918,505; 5,939,803; and 6,158,295, all of which are assigned to Linak A/S of Denmark. In the hospital room environment, product safety is an important concern. DC motors used in hospital beds are configured to operate safely in the medical environment.
As discussed above, control system 44 includes logic module 512. In addition to other functions, logic module 512 includes a drive control system 601 which controls the DC motors 604 of linear actuators 48 used to articulate deck sections 38, 40, 42 of patient support 10.
Drive Control System
Microcontroller 614 includes memory 616, timer 618, analog-to-digital converter 620 and central processing unit (CPU) 622. Illustratively, timer 618 may include a single system clock 624 coupled to the CPU 622 and/or a plurality of application timers 625a, 625b, . . . , 625n, as needed to execute the various features of drive control system 601. In general, application timers 625a, . . . 625n are incremented at a rate which is a function of the system clock 624 of CPU 622, as is well known.
The above-mentioned components of drive control system 601, e.g., actuators 48, power source 612, and microcontroller 614 are well-known and one of ordinary skill in the art would readily be able to select the appropriate models and/or types of such components as needed to operate the articulation functions of patient support 10. For example, memory 616 includes volatile (e.g., flash memory, RAM) and non-volatile (e.g., on-chip EEPROM) memory for storing computer programming code and data required by control system 601. In the illustrated embodiment, on-chip EEPROM memory is used for long term data storage while flash based memory is used for storage of computer programming code and RAM memory is used for short term data storage, however, it is understood that other suitable memory configurations would work equally as well.
Embodiments of drive control system 601 include one or more of the features described below.
End of Travel Control System In an illustrative embodiment, linear actuators 48 including DC drive motors 604 are used to drive the movement of head, seat, and leg sections 38, 40, 42 of patient support surface 10. In general, actuators 48 are activated by activation by a caregiver or patient of one or more of the control buttons illustratively located on controllers 50, 52, 54 (e.g., buttons 1520, 1522 on detachable siderail controller 50; buttons 1550, 1551, 1564, 1566, 1574 on first siderail controllers 52; buttons 1628, 1624, 1626 on controllers 54) or one or more of the pedals of the foot pedal controls 56. As common with most linear actuators, failure of any of actuators 48 may occur if a drive or rod reaches its mechanical end of travel, for example, due to a heavy load on the actuator.
It is known to provide an actuator with an electrical end of travel that is defined to occur earlier than the mechanical end of travel to prevent the actuator from reaching its mechanical end of travel. Using the electrical end of travel, a loss of current occurs when the driving component, such as a piston rod moves past the electrical end of travel. Many existing drives operate until the electrical end of travel is reached. However, in patient support surfaces such as hospital beds, reaching even the electrical end of travel may cause the drive to bounce back and forth due to hysteresis of the drive mechanism. Such oscillatory motion or bouncing may present a safety concern, particularly in drives used to raise and lower the head section of the patient support surface and in drives that power the hi/lo mechanism.
To prevent the above-described oscillatory motion or bouncing in patient support 10, some or all of linear actuators 48 are coupled to a closed loop end of travel control system 626, which establishes a new end of travel setting and thus prevents the actuator from reaching either the electrical or mechanical end of travel during articulation of a section of patient support 10. In the illustrated embodiment, at least head section actuator 48c and deck actuators 48a, 48b are coupled to control system 626.
Another application of end of travel control system 626 relates to the CPR function of the illustrative embodiment patient support 10. As described above, when CPR handle 352 is activated by a caregiver or operator of patient support 10, head section 38 is mechanically lowered. Also, the actuator 48d for seat section 40 is automatically activated as needed to lower seat section 40 and the actuator 48e for leg section 42 is automatically activated as needed to raise leg section 42, to put patient support 10 into the horizontal position shown in
Closed loop end of travel control system 626 of the illustrative embodiment is provided in addition to any other electrical and mechanical end of travel systems. However, it is understood that in other embodiments, closed loop end of travel control system 626 may be provided in lieu of traditional end of travel systems.
Linear actuators 48a, 48b, 48c, 48d, 48e, 48f are shown, for example, in
In the illustrated embodiment, position detector 606 is a potentiometer located inside the housing of drive motor 604, however, it is understood that other means for detecting position, such as a tachometer, may be used. For actuators 48 that are provided with end of travel control system 626, potentiometer 606 has a predetermined setting approximately equal to new end of travel limit 632. Calculation of new end of travel limit 632 is discussed below. Position detector 606 measures the current position 630 of rod 172 and compares it to new end of travel limit 632. If the actual position 630 reaches new end of travel limit 632, an error message or message indicating that the limit has been reached is sent to microcontroller 614, and subsequent actions are taken as described below.
In certain embodiments of end of travel control system 626, timer 618 includes an application timer 625a that is programmed by software to time the operation of drive motor 604, e.g., to track the time of occurrence of each measured position 630, as described below. Each time drive motor 604 starts, whether to perform an up or down/forward or backward motion, timer 625a is started. When drive motor 604 stops, timer 625a stops. Position information 630, 632, 634, 636 and time of occurrence information are stored in memory 616.
Based on the potentiometer 606 reading at the initial position of each drive rod 172 and the total stroke length of the drive rod 172 (typically provided by the drive manufacturer), a correlation can be made between the potentiometer 606 reading and the stroke length (e.g., with stroke length illustratively measured in millimeters). In this way, current position 630 of drive rod 172 during its travel is determined by comparing the current potentiometer 606 reading to a table of known potentiometer readings and the corresponding stroke length for drive rod 172.
Typically, actual position 630 is measured on a recurring basis over predefined time intervals, such as every 20 milliseconds, as counted by timer 625a. In other embodiments, the time that position 630 is measured is also captured. In the illustrative embodiment, if rod 172 is traveling upward, the last position captured before current position 630 is kept in memory and used as detailed below. It is understood that the last position could be tracked during upward, downward, forward, and/or backward movement as needed. The last position, and current position 630, along with sample times associated with each of the last position and current position 630, are converted to digital form by A/D converter 620 and stored in memory 616.
At step 648, new end of travel limit 632 is determined in the manner described above, e.g., based on the potentiometer 606 value when the rod 172 is in the extended position. For example, in one embodiment, a look-up table stored in memory 616 is used. In another embodiment, limit 632 is calculated based on the anticipated amount of hysteresis of actuator 48. The anticipated amount of hysteresis can be estimated as a percentage of the total stroke length of drive rod 172. In the illustrative embodiment, the amount of hysteresis is estimated as about 1% or less of the total stroke length, however, it is understood that other suitable methods for calculating anticipated hysteresis may be used, depending on the particular type or model of drive actuator 48 being used and/or its particular application. New limit 632 is determined, for example, by adjusting electrical end of travel limit 634 by the anticipated amount of hysteresis, so that new limit 632 occurs earlier than electrical limit 634. New limit 632 may also be based on the height of patient support 10 and/or the angle of head section 38 and/or system level noise. For example, in the illustrated embodiment, new limit 632 is calculated assuming a bed height of approximately 36 centimeters and 65-75 degrees of head angle. It is understood that the values obtained for limits 632 and 634, stroke length, and estimated amount of hysteresis are stored in memory 616 as needed to perform the above-described calculations.
At step 650, the change in position of rod 172 is analyzed. Current position 630 is compared to limit 632 using computer programming logic. In additional embodiments, a rate of change of position of rod 172, is determined by comparing the time of measurement of current position 630 to the previously measured current position and its time of measurement.
It is understood by those skilled in the art that the rate of change of position of rod 172 is determined based on the position readings of potentiometer 606 and is also affected by the drive's spindle pitch. Speed and pitch data for the drive are generally provided by the manufacturer.
The rate of change of position is monitored, for example, to determine whether the drive is overloaded or whether something is interfering with the portion of the bed being moved by the drive. For instance, if a patient is attempting to raise the head end of the bed, but does not realize that the frame is caught on something, such as a window sill, the rate of change of position analysis will indicate that though the drive is running, the position has not changed as normal. As a result, an error code is generated and the motor shuts down to avoid further damage to the system or harm to the patient.
At decision step 652, actual position 630 is compared to limit 632. Additionally, the rate of change of position is compared to a predetermined rate of change position limit 653 stored in memory 616. If the actual position 630 of rod 172 has not reached limit 632, or if the actual rate of change of position has not reached the rate of change of position limit 663, then the process returns to step 646.
The illustrated embodiments are particularly concerned with monitoring upper position and rate of change of position limits, however, it is understood that in alternative or addition, lower limits may also be defined and controlled in similar fashion.
If actual position 630 has reached or exceeded limit 632, or if the actual rate of change of position has reached or exceeded the rate of change of position limit 653, then at step 664 potentiometer 606 sends a fault condition or “limit reached” signal to microcontroller 614.
At step 656, microcontroller 614 handles the fault or limit reached condition. In certain embodiments, if position limit 632 is reached or exceeded, or if the rate of change of position limit 661 is reached or exceeded, microcontroller 614 recovers from the error condition by initiating application code, e.g., via a software process or internal or external reset, which resets position 632 to a zero or home position and requests actuator 48 to begin motion in the opposite direction. For instance, if limit 632 is reached during downward travel, position 632 is reset to zero and a signal to begin travel in the upward direction is issued. The process would occur in reverse, if the actuator 48 was moving in the opposite direction.
In other embodiments, at step 656, if position limit 632 is reached or exceeded, or if the rate of change of position limit 663 is reached or exceeded, microcontroller 614 places patient support 10 in a safe/error state that minimizes hazards to patients, caregivers, associated individuals, equipment, and/or data. For instance, microcontroller 614 may initiate a reset or signal power source 612 to interrupt, disengage, or reduce current supplied to actuator 48.
At step 656, microcontroller 614 may also set a flag to indicate to an operator that service is necessary on the affected actuator 48 or on the entire drive system. Such indication may be communicated to an operator by illuminating, blinking or flashing one or more LEDs located on one of controllers 50, 52, 54, or other suitable location on patient support 10. Different colored LEDs may be used to signal different types of errors. In the illustrated embodiment, red, green, and amber colored LEDs are used. For example, if the position 630 of actuator 48c of head section 38 has exceeded limit 634, red and green LEDs may be set to blinking while an amber LED remains off. However, it is understood that any suitable combination of colors and LED activity may be used to indicate the various possible error types. Further, other conventional alarm devices may be utilized such as audible buzzers or bells.
As discussed above, the rate of change of position is monitored to detect whether the drive actuator 48 is overloaded or when an interference condition exists, for example, if drive motor 604 is powered on to raise a deck section 38, 40, 42, but something, such as a window sill, piece of equipment, or utility cart, interferes with its movement or there is excessive weight on the deck section. The rate of change of position is determined using a potentiometer 660 or by other suitable means known in the art. In the illustrated embodiment, potentiometer 606 is used to determine the rate of change of position by measuring the rate of change of the position of drive rod 172 over time. If the rate of position change is too high or too low, an overload or interference condition is detected. In the illustrated embodiment, “too high” or “too low” means that the rate of position change is at least approximately 200% above or below the normal operating rate of change of position of drive 48 when actuated by a user (i.e., the normal rate when an “up” or “down” button is pressed to raise or lower a bed section). If an overload or interference condition is detected, based on comparison of rate of change of position to rate of change of position limit 653, an error code will be generated at step 654 and the error condition will be handled at step 656 as described above.
Duty Cycle Protection
For safety and warranty reasons, linear actuator drive manufacturers typically set a maximum run time for their actuators. Typically, the maximum run time is specified in terms of minutes per hour, e.g., 6 minutes per hour. In view of the safety concerns of the medical environment, a reliable mechanism is needed to detect in a preventative way when an actuator's run time is approaching the predefined run time limit to prevent thermal overload of the actuators, protect against overuse of the actuators, and prolong the life of the actuators. Thus, in certain illustrative embodiments of the present invention, logic module 512 of control system 44 includes a closed loop control circuit 660 that monitors both current and drive run time. Duty cycle protection circuit 660 measures the actual run time of an actuator 48 and then prevents drive operation if a maximum run time 662 is exceeded, as described below. Circuit 660 is designed to prevent thermal protection circuit 670 (described below) from experiencing a fault condition.
If an articulation signal has been received, process 660 proceeds to step 690. At step 690, microcontroller 614 determines which actuators 48a, 48b, 48c, 48d, 48e, 48f have been activated, e.g., by reference to the correspondingly activated control button and the associated articulation function. For example, if head up button 1551 is activated, then head section actuator 48c is actuated. The maximum run time 662 is determined for the activated actuators 48 and stored in memory 616. The maximum run time may 662 vary depending on the particular actuator model used and/or its particular application. As mentioned above, the maximum run time 662 is typically defined by the manufacturer of the actuator. For example, for linear actuator model LA28, made by Linak A/S, the maximum run time is currently stated as 10% or 6 minutes per hour at continuous use. In the illustrative embodiment, the duty cycles of actuators 48 range from 20% to 80%, however, it is understood that the duty cycle for a suitable actuator may fall outside this range. Further, it is understood that other methods of determining maximum run time may be used, for example, depending upon the particular function to which actuator 48 is assigned.
At step 692, an application timer 625b for circuit 660 is started, in order to keep track of how long motor(s) 604 of activated actuator(s) 48 are running. At step 694, the actual current 668 is measured using an ammeter or other suitable means known in the art. Run time 666 is tracked by timer 625b.
At step 696, measured current 668 and run time 666 are analyzed by microcontroller 614. In the illustrated embodiment, run time 666 is evaluated by using an analysis of the rate of heat transfer in drive motor 604. It is known that as current increases, temperature increases, and that the rate of heat transfer is a function of conductivity and temperature gradient. Thus, the rate of heat transfer can be assessed based on the change in current 668 over time.
Before drive motor 604 has started running, e.g., when patient support 10 is first plugged in, run time 666 (e.g., the count of timer 625b) is initialized or set to zero. While drive motor 604 is running, timer 625b is incremented by a predefined amount which is based on the measured current 668. If current 668 is high, timer 625b will be incremented by a greater amount, and if current 668 is low, timer 625b will be incremented by a lesser amount. In the illustrated embodiment, different time increments are specified for four different ranges of current, e.g., timer 625b is incremented by 12, 14, 16 or 18 counts based on the amount of current 668 being drawn by drive motor 604.
If drive motor 604 stops running, timer 625b is decremented by a value “L” representative of the rate of heat transfer based on the known thermodynamics equation, q=−K.DELTA.T, where q is the rate of heat transfer per unit area, .DELTA.T is the temperature gradient, and K is conductivity. The higher the level of the value of timer 625b, the greater the value “L” will be. In the illustrated embodiment, L is 1, 2, or 4 depending on how high timer 625b has been incremented.
If drive motor 604 is disconnected from power source 612, run time 666 (e.g., the count of timer 625b) is stored in memory 616. In this way, system 660 accounts for the fact that drive motor 604 may not have been disconnected from power for a significant time.
At decision step 698, if the drive run time 666 reaches or exceeds the predetermined run time threshold 662, the process proceeds to step 702. In the illustrated embodiment, this is determined by comparing the count of timer 625b (i.e., run time 666) to maximum run time 662.
At step 702, a fault condition is signaled and, at step 704, the current motor function (e.g., chair head up, head down, etc.) is deactivated or turned off. Also at step 702, logic may be used to allow certain emergency functions, such as CPR, to be activated prior to turning off the current motor function. For example, in the illustrated embodiment, CPR mode can still be activated at least one time after system 660 detects a duty cycle overrun. In response to a fault condition, microcontroller 614 may place patient support 10 in a “safe state” that minimizes hazards to patients, caregivers, associated individuals, equipment, and data, e.g., by signaling power source 612 to interrupt, disengage, or reduce current supplied to drive motor 604 of the activated actuator 48. Microcontroller 614 may also activate an audible or visual indicator to alert an operator that service is necessary on the affected drive or on the entire system. Such indication may be communicated to an operator by, for example, illuminating, blinking or flashing one or more LEDs located on one of controllers 50, 52, 54, or other suitable location on patient support 10.
At step 708, a timer 625c is started, which counts off a predefined wait period after which it is safe to restart the previously operating motor function. The wait period may be determined based on the value of run time 666 or maximum run time 662, or other criteria. For example, the wait period may be set equal to the maximum run time 662. In the illustrated embodiment, the wait period is set equal to half of the maximum run time 662.
At decision step 710, microcontroller 614 determines whether the wait period has expired. Step 710 is repeated until the wait period has expired. In the illustrated embodiment, when the wait period has expired, the motor function is restarted at step 712. However, it is understood that in other illustrative embodiments, it may not be necessary or desirable to restart the motor function and thus step 712 may be eliminated in those embodiments.
Returning to step 698, if run time 666 has not reached or exceeded maximum run time 662, the process proceeds to decision step 700. At step 700, system 660 determines whether drive motor 604 of the activated actuator 48 is still operating, e.g., by detecting a signal from a motor sensor 546 or by checking to see if one of the corresponding control buttons is activated. If the activated actuator 48 is still running, the process returns to step 694 to measure current 668 and run time 666. If actuator 48 is not still running, the process ends at step 706.
Thermal Protection
To protect DC drive motors 604 from thermal overload during use in a hospital room environment, a method 720 for detecting thermal failure of the drive motors 604 is provided. A thermal overload condition can occur if, for example, failure of the current overload, interference/obstruction detection, or duty cycle protection mechanisms described above occurs. The presently described method 720 is adapted to the specific safety risks of a medical environment. An embodiment of the method is shown in
At step 722, a maximum temperature 723 is determined for a drive motor 604 of a selected actuator 48. Maximum temperature 723 is typically determined by reference to the manufacturer's specifications for the particular actuator 48. However, it is understood that other means for determining maximum temperature 723, including experimentation, for example, under particular environmental conditions, may be used. Maximum temperature 723 is stored in memory 616.
Typically, activation of a selected actuator 48 occurs when a patient or caregiver selects the corresponding actuator control button on controller 50, 52, or 54, as described above. During operation of the selected actuator 48, a current temperature 724 of the drive 604 is measured inside the housing of drive motor 604, at step 726. Any suitable thermal sensing element, such as a conventional thermocouple, may be used to measure temperature 724. An application timer 625d is used to periodically sample temperature 724 during operation of actuator 48 as long as the drive is in operation and maximum temperature 723 has not been exceeded. Temperature 724 is converted to digital form by A/D converter 620 and is stored in memory 616.
At step 728, the temperature of drive motor 604 is analyzed. Current temperature 724 is compared to maximum temperature 723. At decision step 730, microcontroller 614 determines whether operation of actuator 48 should continue in view of current temperature 724. If current temperature 724 reaches or exceeds maximum temperature 723, the process 720 continues to step 732, where an error signal is generated. If current temperature 724 is less than maximum temperature 723, the process 720 returns to step 726.
At step 732, a fault condition is signaled and, at step 734, microcontroller 614 places patient support 10 in a safe state that minimizes hazards to patients, caregivers, associated individuals, equipment, and data, e.g., by signaling power source 612 to interrupt, disengage, or reduce current supplied to drive motor 604 of the activated actuator 48. Microcontroller 614 may also set a flag to indicate to an operator that service is necessary on the affected drive or on the entire system. Such indication may be communicated to an operator by illuminating, blinking or flashing one or more LEDs located on one of controllers 50, 52, 54, or other suitable location on patient support 10. In the illustrated embodiment, if measured temperature 724 exceeds maximum temperature 723, thermal failure is assumed and the drive 604 is automatically shut down. Typically, a bimetallic thermal switch located inside the motor housing opens to interrupt the current supply to drive 604.
Patient support surfaces, such as hospital beds, often include many features that are electrically powered. Such features include bed articulation controls that allow the various deck sections of the bed to be raised or lowered so that the bed can support patients in a number of different positions. There is a need for at least some of these bed controls to remain available when the bed's primary source of power is lost, i.e., due to a power outage, or while a patient is being transported from one hospital room to another.
Battery Backup System
As a result of government regulations that, for example, require hospital beds to be able to assume the emergency Trendelenburg position whether or not AC power is available, and for other reasons, existing hospital beds may include a battery backup system that powers the bed functions when AC power is not available. However, because hospital beds often require a substantial amount of power to operate the various features, a method to conserve battery power while maintaining compliance with existing regulations is desired.
As best shown in
Battery enable switch 736 allows a person, such as a health care provider, to operate electrically-controlled bed functions (such as bed articulation functions) of patient support 10 using a backup power source (in the illustrated embodiment, battery system 46) when the primary power source 738 (e.g., AC power coupled to bed 10 by plug connection 45) is not available. Such instances may occur, for example, when a power outage occurs or when a bed 10 is being moved from one area of a hospital to another.
As shown in
Circuitry for controlling the activation of backup power source 46 is included in control system 44. As illustrated in
Relay 750 includes contact 748 and coil 754. When primary power source 738 is operating, voltage is applied to switching regulator 740 through connection 744 and to microprocessor 756 through connection 758. When voltage is not present on connection 758, microprocessor 756 senses the lack of primary power and closes contact 748 of relay 750 by energizing coil 754. Closing relay contact 748 provides sufficient backup power to the bed for a predetermined amount of time to allow an orderly shutdown of the bed functions. After the predetermined period of time expires, microprocessor 756 opens relay contact 748 to remove logic power from the bed functions and put patient support 10 into sleep mode.
When patient support 10 is in sleep mode, activation of battery enable switch 736, e.g., by momentarily pressing switch 736, causes patient support 10 to switch out of sleep mode. Activating switch 736 while primary power source 738 is operating has no effect.
In the illustrated embodiment, battery enable switch 736 is activated by the application of pressure on the housing, i.e., by depressing switch 736 with one's finger. In other embodiments, activating any one of the bed function control buttons located on controllers 50, 52, 54 while patient support 736 is in sleep mode will also switch it out of sleep mode.
When switch 736 is activated, sufficient power is provided from backup power source 46 so that at least certain required electrically operational functions of patient support 10, such as articulation of patient support 10, can be performed. In the illustrated embodiment, activation of switch 736 selectively powers certain bed functions, including the bed articulation functions, while other features, such as scale/ppm module 516 and dynamic surface module 518, are not powered by backup power source 46 in order to conserve power. Also, power is always provided to nurse call control 570, even when backup source 46 is in sleep mode. It is understood however, that control system 44 may be configured so that any particular combination of electrically-controlled features of patient support surface 10 (including scale/ppm module 516 and/or dynamic surface module 518) may be powered by backup power source 46.
When microprocessor 756 detects that no power is being supplied by primary power source 738, pressing switch 736 causes microprocessor 714 to apply voltage from backup power source 46 to energize relay coil 754 and close relay contact 748. Closing relay contact 748 again provides logic power to bed functions via switching regulator 740 and Vcc power to microprocessor 756. When microprocessor 756 receives power Vcc, it activates a transistor 760 through connection 762. Microprocessor 756 includes a timer and holds transistor 760 in an on or activated state for a predetermined period of time, as further explained below. When the predetermined period of time expires, microprocessor 756 turns off or deactivates transistor 760. Turning off transistor 760 shuts off logic power to the bed electronics, thus saving battery power.
If microprocessor 756 senses that primary power source 738 is not operating, electrically-controlled functions of patient support 10 are put into sleep mode as described above, at step 772.
At step 774, microprocessor 756 monitors the system to detect whether a bed function is activated or whether battery enable switch 736 is activated, e.g., by pressing a control button, key or switch. If no such function has been activated, microprocessor 756 returns to step 770, checks to see if primary power source 738 is available yet, and thereafter continues to either step 771 or 772 as described above.
If a key has been pressed, microprocessor 756 determines if backup power source 46 is sufficiently charged to provide power to the bed functions, at step 776. If backup power source 46 is in need of recharging, the LED 737 of battery enable switch 736 will begin flashing as described above, at step 778. If backup power source 46 is sufficiently charged, relay 750 is closed so that bed functions can be activated using backup power source 46, as described above, at step 780.
As mentioned above, microprocessor 756 includes a timer. At step 782, when backup power 46 is activated, microprocessor 756 sets the timer to count until one of the following occurs: a bed function control button is depressed, battery enable switch 736 is depressed, or a predetermined amount of time (e.g., 5 minutes) elapses. It is understood that in different embodiments, less than all of these conditions may be tested. For example, in one embodiment, pressing battery enable switch 736 may not interrupt the timer.
At step 784, microprocessor 756 determines whether the preset amount of time has elapsed. If the predefined time period has elapsed, the process returns to step 772, where the bed functions are put into sleep mode. If the time period has not elapsed, microprocessor 756 checks to see if another key (e.g., a bed function-activating key or the battery enable switch) has been pressed, at step 786. If no key has been pressed, the timer continues counting until the predetermined time period expires, at step 784.
If another key has been pressed, as determined at step 786, then the timer is reset at step 788. The process then returns to step 780 and backup power source 46 is reactivated or awakened out of sleep mode.
In this manner, backup power is conserved and, in embodiments where a battery 46 is used to support backup power system, a smaller battery can be used. At the same time, battery enable switch 736 permits patient support 10 to meet the above-mentioned regulatory requirements by enabling at least a portion of the bed's articulation features to be operable on backup power when needed.
Siderails and Headboard
Head and foot end siderails 20, 22 are configured to move between upper positions, as shown in
As head section 38 of deck 26 rotates relative to weigh frame 36, head end siderail 20 also rotates relative to weigh frame 36. However, regardless of the movement of sections 38, 40, 42, foot end siderails 22 do not move relative to weigh frame 36.
Siderails 20 include rail members 1110 and linkage assemblies 1114 coupled between rail members 1110 and head section 38 of deck 26 that permits rail members 1110 to be moved between upper and lower positions. Siderails 22 include rail members 1112 and linkage assemblies 1116 coupled between respective rail members 1112 and weigh frame 36 that permits rail members 1112 to be moved between upper and lower positions.
As shown in
Third link 1122 includes a base plate 1140, a first pair of inwardly extending flanges 1142 coupled to base plate 1140, and a second pair of inwardly extending flanges 1144 also coupled to base plate 1140, as shown in
Referring to
A biasing device 1125, illustratively a conventional gas spring, may extend intermediate the first link 1118 and the fourth link 1124 in order to assist in the raising and lowering of the siderail 20. A first end 1127 of the biasing device 1125 is pivotably coupled to the rod 1134, while a second end 1129 of the biasing device 1125 is pivotably coupled to a connector 1131. The connector 1131 is illustratively coupled to the first end 1152 of the base 1146 of the fourth link 1124. The biasing device 1125 illustratively provides an upwardly acting force to control the rate of descent of the siderail 20 and to assist the caregiver 56 in raising the siderail 20.
Cover 1148 includes a pocket 1149 sized to receive a rectangular magnet 1151 therein. Magnet 1151 is coupled to cover 1148 and rotates with fourth link 1124 during raising and lowering of head end side rail 20. Hall effect sensor 60 is coupled to flanges 1130 of first link 1118 and rod 1134 to detect the position of magnet 1151. Based on this position, control system 44 knows when head end rail 20 is in the raised position and the lowered position.
With reference to
As shown in
Cord 1153 includes a portion or loop 1175 extending from notch 1171 to cable tie 1155. Portion 1175 is about three times as long as a distance 1177 from cable tie 1155 to notch 1171. This additional length provides stress relief by reducing the amount of tension on cord 1153 and chaffing of cord 1153 during raising and lowering of siderail 20.
Referring to
First link 1160 includes a base 1162 coupled to weigh frame 36 by fasteners 1128 and having outer and inner pairs of upwardly extending flanges 1164a, 1164b rigidly coupled to base 1162. Each second link 1120 has its looped first end 1132 pivotably coupled to flanges 1164a, 1164b of first link 1162 by rod 1134 and has its looped second end 1136 pivotably coupled to flanges 1142 of third link 1122 by rod 1138. First end 1152 of base 1146 of fourth link 1124 is pivotably coupled to flanges 1144 of third link 1122 by rod 1154. Second end 1156 of base 1146 is pivotably coupled to the lower ends of inner flanges 1164b of first link 1160 by rod 1158. The base plate 1140 of the third link 1122 is coupled to the body of the rail member 1112. Axial movement of each rod 1134, 1138, 1154 and 1158 is prevented by a C-shaped or open retaining ring 1133 of the type known in the art. Thus, linkage assembly 1116 provides a four bar linkage permitting foot end siderail 22 to swing between the upper and lower positions.
Each siderail 20, 22 further includes a retainer 1166 configured to “bind” the four bar linkage to prevent siderails 20, 22 from moving from the upper position to the lower position. As shown in
Handle member 1168 includes a first end 1178 pivotably coupled to rocker arms 1170 and a second end or handle portion 1180 accessible from an handle opening 1183 in base 1146 as shown in
A spring 1190 is positioned in a spring-receiving channel 1192 defined by base 1146. Spring 1190 is positioned between spring seat 1188 and a wall 1194 of base 1146 to bias handle member 1168 downwardly in direction 1196 (
To unbind linkage respective assemblies 1114, 1116 and permit respective siderails 20, 22 to swing to the down position, pins 1172 must be moved from the latched position (
Because respective first links 1118, 1160 and respective fourth links 1124 are free to pivot relative to one another, respective linkage assemblies 1114, 1116 are also unbound and free to permit siderails 20, 22 to swing between the upper and lower positions. According to alternative embodiments of the present disclosure, other retainers are provided to hold the siderails in the upper position such as clasps, catches, locks, other latches, clamps, pins, bolts, bars, hasp, hooks, or other retainers known to those of ordinary skill in the art.
An alternative embodiment slide or handle member 1201 is shown in
As shown in
Head end siderails 20′ are coupled to head section 38′ and may be moved between raised and lowered positions. Head board 16′ extends between head end siderails 20′. Foot end siderails 22′ are coupled to weigh frame 36 and may also be moved between raised and lowered positions.
Siderails 20′ include rail members 1110′ and linkage assemblies 1114 coupled between rail members 1110′ and head section 38′ of deck 26′ that permits rail members 1110′ to be moved between upper and lower positions. Siderails 22′ include rail members 1112′ and linkage assemblies 1116 coupled between respective rail members 1112′ and weigh frame 36 that permits rail members 1112′ to be moved between upper and lower positions.
As shown in
As shown in
Returning now to the illustrative embodiment siderails 20, 22 of
Controllers
As discussed above, control system 44 is coupled to a first pair of controllers or control panel 52 rigidly coupled to main body 1210, a second controller or control panel 54 pivotably coupled to main body 1210, and third detachable controller 50 that is removably received by head and foot end siderails 20, 22 so that it can be removed from one of foot end siderails 22 and coupled to the other foot end siderail 22 or head end siderails 20 to control various functions of patient support 10. As described below, controllers 52, 54, 50 control various functions of patient support 10 and are also configured to receive information from a caregiver related to a patient and to send and receive patient or bed-related data to a central computer for storage, tracking, and analysis.
Additional details of suitable electronics and other features of controllers are provided in U.S. Pat. No. 5,715,548, titled “Chair Bed,” filed Aug. 4, 1995; U.S. Pat. No. 6,008,598, titled “Hand-Held Controller For Bed and Mattress Assembly,” filed Apr. 22, 1998; U.S. Pat. No. 6,131,868, titled “Hospital Bed Communication and Control Device,” filed Jan. 1, 1997; and U.S. Provisional Application No. 60/202,284, titled “Remote Control for a Hospital Bed,” filed May 5, 2000, the disclosures of which are expressly incorporated by reference herein.
Cover 1212 includes a plurality of apertures 1230 that match with control buttons or switches 1232 of a circuit board 1233 of first controller 52 that is coupled to cover 1212. The functions controlled by switches 1232 will be described in greater detail below.
Second controller 54 includes a housing 1236 and a circuit board 1238 including a plurality of control buttons or switches 1240 and an LED display 1242. Cover 1212 includes a pocket 1244 configured to receive controller 54 as shown in
Housing 1236 includes first and second housing shells 1246, 1248 that cooperate to define a interior region 1250 sized to receive circuit board 1238. Shells 1246, 1248 cooperate to define a boss or post 1252 that is pivotably received in an aperture 1254 defined in cover 1212. Shells 1246, 1248 also cooperate to define an aperture 1256 sized to receive a torsion spring 1258, a bushing 1260, and a pin 1262. To couple second controller 54 to cover 1212, post 1252 is inserted into aperture 1254, and aperture 1256 is aligned with a corresponding aperture 1261 in cover 1212. Pin 1262 is then inserted into aperture 1261 and aperture 1256 to pivotably couple second controller 54 to cover 1212. When coupled, spring 1258 biases second controller 54 into pocket 1244.
This coupling allows the tilting of a lower edge 1264 of housing 1236 upward thereby permitting a user to better see control buttons 1240. According to alternative embodiments of the present disclosure, other configurations of couplers between the housing and the controller mount are provided. For example, hooks, hook-and-loop type fasteners, snaps, a detachable hinge, or other devices known to those of ordinary skill in the art are provided to pivotably or otherwise couple the controller to the siderail.
An electrical communication cord 1265 of controller 54 is coupled to circuit board 1238 and extends from interior region 1250 defined by shells 1246, 1248 as shown in
Portion 1277 of cord 1265 extends from post 1252 to circuit board 1233 and has a length that is about three times as long as a distance 1281 from post 1252 to where it coupled to circuit board 1238. This additional length reduces the amount of tension on cord 1265 and chaffing of cord 1265 during the pivoting of controller 54 about axis of rotation 1263.
According to an alternative embodiment of the present disclosure, a rubber grommet is provided in the channel 1253 to provide a liquid proof seal between cord 1265 and housing 1236. According to another alternative embodiment, a rubber grommet is provided between post 1252 and cover 1212 to provide a liquid proof seal therebetween.
Referring now to
Fluid Sealing
As described above, main body 1210 and cover 1212 of head end siderail 20 are sealed together to prevent fluids from entering an interior region 1218 defined between main body 1210 and cover 1212. Main body 1210 and cover 1212 include sealing edges 1268 and 1270, respectively that face each other when cover 1212 is coupled to main body 1210 (
With reference to
Sealing edge 1268 includes a channel 1332 that extends along portions 1272, 1274, 1276, 1278, 1279, 1282, 1286, 1290, 1294, 1296 of main body 1210. See, for example,
According to an alternative embodiment of the present disclosure, the sealing edges disclosed herein that press against the O-ring, such as sealing edge 1270, are provided with a ridge that “bites” into the O-ring, such as O-ring 1216, along the length of the O-ring to increase the compression of the O-ring and the contact pressure between the sealing surface and the O-ring. According to an alternative embodiment of the present disclosure, sealing edges and an O-ring are provided around the opening in main body 1210 that receives third link 1122 of linkages 1114 to seal around this opening. Similar sealing edges and O-ring may also provided for foot end rail 22. According to another embodiment, these additional sealing edges extend down to the existing sealing edges.
Shells 1246, 1248 of housing 1236 of second controller 54 are sealed together to prevent fluids from entering interior region 1250 defined between shells 1246, 1248 as shown in
Similar to rail member 1110 of head end siderail 20, rail member 1112 of foot end siderail 22 includes a main body 1211 and a cover 1213 as shown in
Sealing edge 1269 includes a channel 1333 as shown in
Detachable Siderail Controller
As shown in
Controller 50 is configured to slide in either handle opening 1292 of head end siderails 20 or handle opening 1352 of foot end siderails 22 between an infinite number of positions (
As shown in
The respective pairs of convex surfaces 1358, 1360, 1362, 1364 of siderails 20, 22 cooperate to define a top rail and a bottom rail that define a guide 1367 operably coupled to the controller 50. Concave surfaces 1354 and 1356 and a retainer 1368 coupled to housing 1344 cooperate to define a complementary formation configured to ride along the top and bottom rails/guide. According to alternative embodiments of the present disclosure, other configurations of rails and guides and complementary formations are provided such as raised rails, channels, slots, or other configurations of guides and complementary formations known to those of ordinary skill in the art.
Retainer 1368 is configured to retain controller 50 in either opening 1292, 1352 to permit sliding of controller 50 along siderails 20, 22 and to permit removal of controller 50 from openings 1292, 1352, respectively. When controller 50 is positioned in opening 1352 of foot end siderail 22, retainer 1368 is positioned adjacent to concave surface 1356 of housing 1344.
As illustrated in
To reposition controller 50 back in one of siderails 20, 22, the patient positions second concave surface 1354 adjacent to convex surface 1358, 1362 of rail member 1110, 1112 of siderail 20, 22, respectively so that a peaked tip 1378 of housing 1344 captures rail member 1110, 1112. The lower end of controller 50 is pushed in direction 1380 so that retainer member 1370 rides back over respective convex surface 1360, 1364. Peaked tip 1378 and retainer member 1370 then define a width 1382 that is greater than a width 1384 of opening 1292, 1352 so that controller 50 is retained in respective siderail 20, 22. Identical procedures are followed for placing and removing controller 50 from opening 1352 in foot end siderails 22 and for placing and removing controller 50 from opening 1292 in head end siderails 20. Furthermore, controller 50 may also be coupled to rail members 1110, 1112 through the opposite side of respective opening 1292, 1352. According to an alternative embodiment of the present disclosure, the openings in the head and foot end siderails do not extend completely through the siderails.
As shown in
As shown in
Ribs 1414 slide in channel portions 1424 of void 1394 so that retainer member 1370 can move up and down. Housing 1344 includes a pair of lips 1426 on which locking tabs 1416 are caught preventing removal of retainer member 1370 from void 1394 after retainer member 1370 is slidably moved up and locking tabs 1416 snap into place over lips 1426.
Retainer 1368 further includes a lock or blocker 1430 configured to slide on retainer cover 1396 and block or permit movement of retainer member 1370. As shown in
Depending on the position of button 1432 and blocker 1434 relative to lock guide 1428, blocker 1434 will prevent or permit movement of retainer member 1370 relative to housing 1344. If button 1432 is centered over a middle or lower portion 1438 of notched rib 1418, clearance exists between lower portion 1438 and blocker 1434 and retainer member 1370 is permitted to move further up in direction 1375 into void 1394 (
An alternative embodiment retainer 1442 and retainer cover 1444 similar to retainer 1368 and retainer cover 1396 are shown in
Retainer member 1446 includes a latch portion 1450, a pair of ribs 1452, a pair of locking tabs 1454, and a notched rib 1456. Latch portion 1450 includes a downwardly facing surface 1458 that matches the contour of upwardly facing surface 1360, 1364 of siderails 20, 22, respectively. Latch portion 1450 further includes a spring-receiving aperture 1460 sized to receive an end of spring 1398.
Ribs 1452 slide in channel portions 1424 of void 1394 so that retainer member 1446 can move up and down. Locking tabs 1454 are caught on lips 1426 of housing 1344 to prevent removal of retainer member 1446 from void 1394 after retainer member 1446 is slidably moved up and locking tabs 1454 snap into place over lips 1426.
Retainer 1442 further includes a lock or blocker 1464 configured to slide on retainer cover 1444 and block or permit movement of retainer member 1446. Lock 1464 includes slider button 1432 and a blocker or lug 1466 coupled integrally with button 1432. Lock 1464 includes a plurality of fingers 1468 that snap into an opening 1470 in cover 1444 so that lug 1466 extends through opening 1470. Cover 1444 with lock 1464 coupled thereto, is coupled to housing 1344 so that blocker 1466 is positioned above notched rib 1456.
Depending on the position of button 1432 and blocker 1466 relative to cover 1444, blocker 1466 will prevent or permit movement of retainer member 1446 relative to housing 1344. If button 1432 is centered over a middle or lower portion 1472 of notched rib 1456, clearance exists between lower portion 1438 and blocker 1466 and retainer member 1446 is permitted to move further up into void 1394. This movement permits removal of the controller 50 from respective head and foot end siderails 20, 22. However, if button 1432 is slidably moved so that blocker 1466 is positioned over a raised portion 1474 of notched rib 1456, there is little or no clearance between raised portion 1474 and blocker 1466 and retainer member 1446 is blocked from sliding further up into the void.
According to other alternative embodiments of the disclosure, other retainers known to those of ordinary skill in the art are provided to retain the controller in the siderails such as tabs, clasps, catches, locks, other latches, clamps, pins, bolts, bars, hasp, hooks, or other retainers known to those of ordinary skill in the art.
As shown in
Because two connectors 1478 are provided on opposite sides of patient support 10, controller 50 may be plugged into either side of patient support 10. Thus, if a patient or caregiver finds it more convenient to position controller 50 on the pair of head and foot end siderails 20, 22 on the first side of patient support 10, controller 50 can be plugged into connector 1478 without cord 1350 having to be strung over the mattress 14. Similarly, if a patient or caregiver finds it more convenient to position controller 50 on the pair of head and foot end siderails 20, 22 on the second side of patient support 10, controller 50 can be plugged into connector without cord 1350 having to be strung over the mattress 14. Thus, a corded controller 50 is provided that can be removably coupled to either side of the patient support 10 without having to string the cord 1350 of the controller 50 over the mattress 14 of the patient support 10.
Controller 50 further includes a rubber grommet 1480 that is positioned in a aperture 1482 in outer shell 1386 as shown in
Outer shell 1388 further includes a pair of symmetric ribs or ramps 1482 that define a tapered channel 1484 configured to receive cord 1350. A stop 1486 is coupled to cord 1350. Stop 1486 is larger than a narrow opening 1488 defined between ramps 1482 so that cord 1350 cannot be pulled axially out of outer shell 1386. This prevents wires 1490 of cord 1350 and connector 1492 that couples to circuit board 1346 from being stressed if force is applied to cord 1350. Because channel 1484 is tapered, an assembler can initially place cord 1350 in the wider portion of channel 1484 and then press down to position cord 1350 in opening 1488. When cord 1350 is pressed down on, ramps 1482 guide cord 1350 toward narrow opening 1488 so that the assembler does not have to be as accurate with the initial placement of cord 1350 in channel 1484. According to the presently preferred embodiment, the stop 1486 is a cable tie that has had any extra length removed. According to alternative embodiments of the present disclosure, other stops are provided. For example, according to one alternative embodiment, a staple or other clip is provided.
As shown in
Controller Interface Panels Controllers 50, 52, 54 each include respective interface panels 1510, 1512, 1514, illustrated in
Each interface panel 1510, 1512, 1514 includes a plurality status indicators and raised button covers having indicia. When a user presses on the button covers, they also press on one of respective switches or buttons 1348, 1232, 1240 positioned behind the button cover and initiate a function of patient support 10.
As shown in
Head up button 1520 and head down button 1522 are provided to control adjustment of the position of head section 38 of deck 26 between the raised and lowered positions. Knee up button 1524 and knee down button 1526 are provided to control adjustment of the position of leg and seat sections 42 and 40.
When a nurse call button 1528 is pressed, a signal is sent to a nurse station or directly to predetermined caregivers that indicates that the patient needs attention. Speak indicator 1529 and listen indicator 1530 are provided to indicate the direction of communication between a patient in patient support 10 and nurse or other caregiver located at a nurse call station or other location. The caregiver at the nurse call station or elsewhere controls which way the communication travels. If neither indicator 1529, 1530 is illuminated, the communication lines are closed. When speak indicator 1529 is illuminated, the patient may speak to the caregiver. The patient speaks into a microphone (not shown) coupled to head end siderail 20. When listen indicator 1530 is illuminated, the caregiver may speak to the patient in patient support 10 from speakers 1220. A graphic of a listening ear is positioned adjacent to speak indicator 1529 to indicate that a nurse or other caregiver is listening to the patient when lit. A graphic of a speaking person is positioned adjacent to listen indicator 1530 to indicate the patient is to listen to a nurse or other caregiver when illuminated.
Controller 50 is also configured to control functions of other devices located within a patient's room such as a TV or lighting of a room (not shown) as further described above with reference to
To turn on the direct lighting in a room, such a ceiling light or other lighting that shines down, a direct light button 1546 is provided that is pressed to turn the light(s) on and off. Similarly, to turn on indirect lightly, such as a light on a headwall unit that shines up on the ceiling or down on the floor from a low level, an indirect light button 1548 is provided that is pressed to turn the light(s) on and off.
As shown in
Head up button 1550 and head down button 1551 are provided to control adjustment of the position of head section 38 of deck 26 between the raised and lowered positions. Knee up button 1552 and knee down button 1554 are provided to control adjustment of the position of leg and seat sections 42 and 40. High button 1556 and low button 1558 are provided to control raising and lowering intermediate frame 32 relative to base frame 28.
Foot extend button 1560 and foot retract button 1562 cause leg section 42 to extend and retract which permits the position of footboard 18 of patient support 10 to be adjusted relative to the position of the patient's foot. To extend leg section 42, extend button 1560 is pressed until the desired position of footboard 18 is reached. To retract foot section 42, retract button 1562 is pressed until the desired position is reached.
Chair bed button 1564 and flat bed button 1566 are provided to control adjustment of the position of deck 26 between the chair and bed positions. To move patient support 10 toward the chair position, chair button 1564 is pressed until the degree of the chair position is achieved of until patient support 10 reaches the full chair position. To move patient support 10 toward the bed position, flat bed button 1566 is pressed until the desired degree of the chair position is removed or until patient support 10 reaches the flat bed position.
Tilt (Reverse Trendelenburg) button 1568 and reverse tilt (Trendelenburg) button 1570 are provided to control adjustment of the position of deck 26 between head raised (Reverse Trendelenburg) and head lowered (Trendelenburg) positions. To move patient support 10 to the head raised position, tilt button 1568 is pressed until the degree of the incline of intermediate frame 32 is achieved. To move patient support 10 toward the head lowered position, reverse tilt button 1570 is pressed until the desired degree of incline of intermediate frame 32 is achieved. When a nurse call button 1572 is pressed, a signal is sent to a nurse station or directly to predetermined caregivers that indicates that the patient needs attention.
According to the illustrative embodiment of the present disclosure, most of the buttons are only operable after a key or enable button 1584 is first pressed. This helps prevent the accidental activation and deactivation of certain functions of patient support 10. According to the preferred embodiment of the present disclosure, enable button 1584 must first be pressed before the functions controlled by the other buttons on panels 1512 and 1514 will initiate. However, the nurse call feature controlled by nurse call button 1572 will initiate without the need to first press enable button 1584.
To enable the other buttons, enable button 1584 must be pressed for at least or about 0.5 seconds. By requiring that the button be depressed for a predetermined amount of time, an accidental momentary depression of enable button 1584, such as when panel 1512 is wiped during cleaning, will not enable the other buttons.
Once enabled, the user has about a twenty second window to press the other buttons to initiate a function. Once the twenty second window passes without one of the other buttons being pressed, the other buttons are disabled and enable button 1584 must be pressed again to operate the functions. However, if one of the other buttons is pressed during the initial twenty second window, the window is reset so that the user has another twenty second window to press another button. Once twenty seconds passes without any button being pressed, the twenty second window expires and enable button 1584 must be pressed again.
According to alternative embodiments of the present disclosure, other times required to press the enable button are provided. For example, according to one embodiment, one second is required. According to another embodiment, no time is required so that the other buttons are enabled whenever the enable button is pressed. According to other alternative embodiments of the present disclosure, other windows of time are provided during which the other buttons are enabled. For example, according to some embodiments, the window is 5, 10, 15, 25, 30 or more seconds. According to another alternative embodiment, no enable button 1584 is provided.
Patient control 52 also enables and disables (locks out) specific features of patient support 10. By pressing head lock-out button 1586, the function of head up buttons 1520, 1551 and head down buttons 1522, 1550 of respective controllers 50, 52 are disabled so that head section 38 of deck 26 cannot be raised or lowered. When disabled, an indicator 1588 on button 1586 lights up. When head lock-out button 1586 is pressed again, head section 38 may be raised and lowered again and indicator 1588 goes off. A similar knee lock-out button 1590 and indicator 1592 are provided to enable and disable the function of knee up buttons 1524, 1552 and knee down buttons 1526, 1554 of respective controllers 50, 52.
A similar all actuator lock-out button 1594 and indicator 1596 are provided that disable the function or initiate movement of linear actuators 48 operated by controllers 50, 52. When pressed, all functions controlled by controllers 50, 52 that change the configuration of deck 26 or raise, lower, or tilt intermediate frame 32 are disabled and indicator 1596 lights up. When pressed again, the functions are enabled and indicator 1596 turns off. By disabling certain functions of controllers 50, 52, a caregiver can prevent accidentally articulation or other movement of patient support 10 when such articulation may be undesirable. According to alternative embodiments of the present disclosure, the other functions of controllers 50, 52, 54 are also disabled and enabled by one or more lock-out buttons.
Other indicators which relate to various patient support status functions are also included on interface panel 1512. A bed position indicator 1598 is illuminated when intermediate frame 32 is not in the lowermost position. When intermediate frame 32 is in the lowermost position, this indicator 1598 is off. A service indicator 1610 is lit when patient support 10 detects that a component needs serviced. If patient support 10 does not detect that a component needs serviced, this indicator 1610 is off.
With reference to
As shown in
Button 1616 controls activation of the position monitoring system to detect an “exit” condition when the patient has exited patient support 10. When button 1616 is pressed to activate monitoring of the exit condition, the respective indicator 1518 on button 1616 lights up. Otherwise the respective indicator 1518 on button 1616 is off. If the exit condition is detected by bed exit sensor 562, visual and audible alarms will activate notifying the caregiver that the patient has exited patient support 10.
Button 1614 controls activation of the position monitoring system to detect a “pre-exit” condition when the patient is bearing weight primarily on an edge of patient support 10, such as when the patient is sitting on the edge of patient support 10. When button 1614 is pressed to activate monitoring of the pre-exit condition, the respective indicator 1518 on button 1614 lights up. Otherwise the respective indicator 1518 on button 1614 is off. If the pre-exit condition is detected, the visual and audible alarms will activate notifying the caregiver that the patient has moved to the edge of patient support 10. Furthermore, the alarms will also activate if the exit condition is detected.
Button 1612 controls activation of the position monitoring system to detect a “patient up” condition when the patient's torso moves beyond a predetermined position relative to deck 26. When button 1612 is pressed to activate monitoring of the patient up condition, the respective indicator 1518 on button 1612 lights up. Otherwise the respective indicator 1518 on button 1612 is off. If the patient up condition is detected, the visual and audible alarms will activate notifying the caregiver that the patient has moved to the up position.
Alarm control button 1618 and volume indicator 1620 are provided to a caregiver to control the volume of the audible alarm that sounds when the patient monitoring system detects one of the above-mentioned conditions. Alarm button 1618 controls the volume of the alarm. Volume indicator 1620 comprises a plurality of LED's that are lit according to the selected volume level, i.e., the higher the volume selected, the more LED's that are lit. If a user wants to turn the volume up, alarm button 1618 is pressed repeatedly until the desired volume is reached. To lower the volume, alarm button 1618 is pressed repeatedly until the peak volume is reached. After the peak volume is reached, continued pressing on alarm button 1618 will gradually reduce the volume of the alarm until the lowest volume is reached. After the lowest volume is reached, continued pressing on alarm button 1618 will gradually increase the volume. If no LED's are lit, the alarm is deactivated.
Inflation system buttons 1622, 1624, 1626, 1628 are provided that control the function of the air pressure inflation system of mattress 14. Maximum inflation button 1622 inflates the mattress zones to a predefined air pressure level and may be used to facilitate administration of CPR. A corresponding indicator 1518 on button 1622 lights up when the maximum inflation function is activated. When pressed again, the mattress zones return to normal operating pressure and the corresponding indicator 1518 turns off.
First turn assist button 1624 controls the turning of a patient toward one side of patient support 10. Second turn assist button 1626 controls the turning of the patient toward the other side of patient support 10. When either of these buttons 1624, 1626 are pressed, they begin the turn assist function and the associated indicator 1518 lights up. When the respective turn assist function is complete, the associated indicators 1518 turn off. A rail down indicator 1627 is illuminated when any of siderails 20, 22 are not in the raised position. Patient size button 1628 button permits a caregiver to set the size of the patient positioned on mattress 14. Three graphics representing different sized patients are positioned next to corresponding indicators 1518. When patient size button 1628 is pressed, a different sized patient is selected and the corresponding indicator 1518 lights up. In an illustrative embodiment, depending on which size patient is selected, different air pressures are provided to mattress 14.
Interface panel 1514 further includes a plurality of buttons and LED display 1242 which permit a caregiver to weigh the patient using the patient weighing function. A unit selection button 1630 enables the caregiver to choose between pounds and kilograms as the unit of weight measurement. LED display 1242 displays the patient's weight and selected unit of measurement.
Calibration button 1632, change item button 1634, add item button 1636, and subtract item button 1638 are provided to the caregiver to calibrate the system for weighing a patient. For example, before a patient is placed on patient support 10, calibration button 1632 is pressed to set the weight reading to 000.0 lbs/kg so that the initial weight of mattress 14, deck 26, and any other patient support component or piece of medical equipment is negated from the weight reading. Thus, only the weight of the patient is indicated when the patient is on patient support 10.
If a patient support component or piece of medical equipment is added to or removed from patient support 10 that may affect the weight reading, change item button 1634, add item button 1636, and subtract item button 1638 are illustratively used to take the additional or subtracted weight into account. For example, if a piece of medical equipment, such as an IV pole, is added to patient support 10, change item button 1634 and add item button 1636 are pressed while the piece of medical equipment is added and the additional weight detected by the weigh system is subtracted from the measured weight so that the additional weight of the IV pole is negated from the weight displayed on display 1242. Similarly, if a piece of medical equipment is removed from patient support 10, change item button 1634 and subtract item button 1638 are pressed while the piece of medical equipment is removed and the removed weight detected by the weigh system is added to the measured weight so that the loss of weight of the removed pieced of medical equipment is negated from the weight displayed on display 1242.
Foot Pedal Controls and Nightlight
As shown in
Each foot pedal control 56 is associated with one of the above-mentioned functions and includes a pedal or control member 1660 appropriately labeled for the respective function. By stepping on any of pedals 1660 with the tip of one's foot as shown in
With reference to
Because housing portion 1666 is centrally located and raised relative to foot pedals 1660, it acts as a locator for pedals 1660. For example, a caregiver who is familiar with patient support 10 will be able to sweep their foot over pedals 1660 until striking either side of housing portion 1666. Because of their familiarity with patient support 10, they will recognize which pedal 1660 is located beneath their foot. If this pedal 1660 performs the desired function, the need only step down without looking down at the respective pedal 1660 for an decal or indicator that indicates the specific function of that respective pedal 1660. If the desired pedal 1660 is not the one located under their foot, they will recognize that they need to back away from housing portion 1666 to the next adjacent foot pedal 1660 that does perform the desired function. Preferably, the caregiver will initially sweep toward the correct side of housing portion 1666 on which the desired foot pedal 1660 is located.
As shown in
As shown in
The position of each pedal 1660 is detected by a sensor 538. If sensor 538 detects that any one of pedals 1660 is moved and held in the second lowered position for about one second and then returned to the first raised position, pedals 1660 are enabled to operate the respective functions of patient support 10 for twenty seconds. To activate any of these functions, a respective pedal 1660 must be moved to the second lowered position within the twenty second enabled window.
If a pedal 1660 is not moved back down to the second lowered position within the twenty second enabled widow, pedals 1660 are disabled and must be enabled again as described above by holding one of pedals 1660 in the second lowered position for about one second. If any of pedals 1660 are lowered within the twenty second window, the function is performed and the window is reset for another twenty seconds. If twenty seconds go by without any of the pedals 1660 being moved back down to the second lowered position, pedals 1660 are again disabled. If two pedals 1660 are simultaneously moved to the second lowered position, neither function is performed. Preferably, pedals 1660 travel through an angle of 50 degrees from the first raised position to the second lowered position.
Each of the four sensors 538 is preferably mounted to one of a pair of mounting strips 1694 as shown in
According to the preferred embodiment of the present disclosure, sensor 538 is a Hall effect field sensor that detects change in the characteristics of a magnetic field generated by pedal 1660. A magnet 1710 is positioned on sensor portion 1674 of each pedal 1660 in a position spaced apart from sensor 538. Sensor 538 detects the change in position of magnet 1710 during movement of the respective pedal 1660 by detecting the change in magnetic field. Based on this change in magnetic field, sensor 538 sends a signal indicative of the first raised and second lowered positions of the respective pedal 1660 to the control system 44. Control system 44 then initiates the application of power to actuators 48 to control and power the function of the respective components of patient support 10.
An illustrative circuitry associated with sensor 538 is shown in
As shown in
As shown in
An alternative embodiment foot pedal control 56′ is illustrated in
As shown in
According to alternative embodiments of the present disclosure, light 1732 is placed elsewhere on the patient support 10 to shine directly on foot pedals 1660. For example, according to one alternative embodiment, light 1732 is provided on the sides of housing portion 1666 (see
According to alternative embodiments of the present disclosure, other sensors are provided to detect the position of the pedals 1660 and to control the respective functions of the patient support 10, such as other proximity switches, a three-position mechanical switch, other mechanical switches, other electrical switches, other field sensors that detect changes in an electric field due to changes in capacitance or inductance, other field sensors known to those of ordinary skill in the art, or any other sensor known to those of ordinary skill in the art.
One such alternative embodiment sensor 1734 is shown in
Another such alternative embodiment sensor 1742 is shown in
Another such alternative embodiment sensor 1750 is shown in
Obstacle Detection Device
Referring now to
Each sensor 1802 and 1804 is configured to provide an obstacle detection signal to control system 44 in the event that it detects an obstacle or determines that a fault condition exists. More particularly, each sensor 1802 and 1804 is configured to provide the obstacle detection signal to control system 44 upon detecting that an object, such as an individual's foot, is supported on one of the upper surfaces 474 and 476 of the base frame 28.
In response to the obstacle detection signal from either of sensors 1802 or 1804, control system 44 will prevent the lowering of the intermediate frame 32 relative to the base frame 28. Moreover, the obstacle detection signal indicates that either an obstacle is supported on the base frame 28 or that at least one of the sensors 1802 or 1804 is not operating properly and is in a fault condition. As such, in order to avoid potential damaging impact with the detected obstacle, control system 44 prevents actuators 48a and 48b from operating to lower the intermediate frame 32. In an illustrative embodiment, control system 44 permits continued operation of the actuators 48a and 48b to raise the intermediate frame 32. Further, upon receiving the obstacle detection signal, control system 44 may instruct the actuators 48a and 48b to raise the intermediate frame 32 for a predetermined time period, illustratively 2 seconds, while preventing operation of the actuators 48a and 48b to lower the intermediate frame 32. Raising the intermediate frame 32 for a time period after an obstacle has been detected, provides for the immediate and automatic movement of the frame 32 in a direction away from the detected obstacle.
While the sensors 1802 and 1804 of the obstacle detection device 58 are illustratively positioned on the base frame 28, it should be appreciated that the sensors 1802 and 1804 could likewise be positioned on a lower surface of the intermediate frame 32. Further, the obstacle detection device 58 may be utilized to detect obstacles between any two portions of a patient support 10 which move relative to each other. For example, the obstacle detection device 58 may be used between the head end and foot end siderails 20 and 22, between the head end siderails 20 and the headboard 16, and between the foot end siderails 22 and the footboard 18.
Additional details of suitable obstacle detection devices are provided in U.S. Provisional Patent Application No. 60/373,819, title “Hospital Bed Obstacle Detection Device and Method”, filed Apr. 19, 2002, and PCT International Patent Application No. PCT/US03/12166, titled “Hospital Bed Obstacle Detection Device and Method”, filed Apr. 21, 2003, the disclosures of which are expressly incorporated by reference herein.
First Illustrative Embodiment Mattress Assembly
Referring now to the
Mattress Foot Section Assembly
As detailed above, the leg section 42 of the deck 26 is extendable and retractable.
The foot section 2110 is perforated to facilitate its longitudinal extension and retraction. More particularly, the foot section 2110 is formed to include a plurality of apertures, illustratively transversely extending slots 2138 extending in a generally vertical direction through the base and flange portions 2130 and 2132, to facilitate compressibility of the foot section 2110 in response to the retraction of the leg section 42 of the deck 26. More particularly, the plurality of slots 2138 are arranged in a plurality of laterally extending rows 2140 wherein the individual slots 2138 of each row are laterally offset from those slots 2138 of longitudinally adjacent rows 2140.
While in the illustrative embodiment, a plurality of discrete laterally and longitudinally spaced transverse slots 2138 are illustrated to facilitate retraction and extension of the foot section 2110, it should be appreciated that other structures may be readily substituted therefor. More particularly, the foot section 2110 may be formed to include serpentine channels or other forms of openings, such as a plurality of slots extending substantially the full width of the foot section 2110 between opposing side edges of the flange portions 2130 and 2132.
A foot section mounting plate 2142 is secured to a lower surface 2144 of the foot section 2110, illustratively through an adhesive bond. As described in greater detail below, the foot section mounting plate 2142 provides a securing platform for a foot section anchor 2146 which couples the foot section to the leg section 42 of the deck 26 to facilitate movement in cooperation therewith.
Heel Pressure Relief Member
The foot section 2110 includes a receiving recess 2148 extending downwardly from an upper surface 2150 of the base portion 2128 at a foot end 2152 thereof. A heel pressure relief member 2154 is configured to be received within the recess 2148. As illustrated in
An alternative embodiment heel pressure relief member 2154′ is illustrated in
The heel pressure relief member 2154 is configured to reduce the level of raised pressure between the patient's foot and the mattress. More particularly, the pressure relief member 2154 provides for a region of reduced pressure below the patient's heels. The foot section 2110 includes a calf portion 2170 (
Mattress Body Section Assembly
The body section 2112 of the receiving base 2108 is further illustrated in
The sidewalls 2176 and 2178 each include an angled or inclined portion 2188 coupled to a flange portion 2190. The angled portions 2188 are configured to conform to the angled sidewalls 260 and 262 of the deck 26, while the flange portions 2190 are configured to extend above and out beyond the sidewalls 260 and 262 of the deck 26. The body section 2112 of the receiving base 2108 includes a head portion 2192 and a seat portion 2194 separated by a laterally extending slit 2196. Opposing ends of the slit 2196 include stress relief apertures 2198 formed within the sidewalls 2176 and 2178. As described in greater detail below, the slit 2196 facilitates relative movement of the head and seat portions 2192 and 2194 of the body section 2112 during articulation of the head and seat sections 38 and 40 of the deck 26.
Mattress Mounting Substrate
Turning now to
A plurality of turn assist bladder securing slots or apertures 2216 are formed proximate opposing longitudinally extending side edges 2222 and 2224 of the mounting substrate 2116. As detailed below, the apertures 2216 are configured to receive fasteners, such as buttons 2225 for securing the turn assist bladder assembly 2120 to the mounting substrate 2116 (
Foot Section Securing Substrate With reference now to
Illustratively, the foot section securing substrate 2114 is formed from a flexible sheet material, such as pack cloth or urethane coated twill. As a flexible sheet material, the foot section securing substrate 2114 may follow a serpentine path generally from a horizontal first plane of the upper surface 2229 of the mounting substrate 2116, vertically down around a foot end edge 2240 of the receiving base 2108, and back along a horizontal plane of the lower surface 2144 of the foot section 2110.
Foam Crowning Core
The foam crowning core 2118 is received within the channel 2182 defined by the sidewalls 2176 and 2178 of the body section of the receiving base 2108. As shown in
The crowned surface 2252 is configured to facilitate lateral patient transfer from the bed 10 to another patient support device positioned adjacent to the bed 10 by creating an inclined surface which provides a slight amount of gravity assistance when the caregiver is moving the patient toward the side of the mattress 14. Additionally, since the surface 2252 at the side walls 2260 and 2261 is lower than the center portion 2254 of the mattress 14, the siderails 20 and 22 may have a lower profile and still fulfill minimum height requirements. More particularly, the distance from the top cover portion 2106 of the mattress 14 above the side walls 2260 and 2261 of the crowning core 2118 to the top of the siderails 20 and 22 is configured to be at least approximately 9 inches.
Turn Assist Bladder Assembly
With reference to
Each of the turn assist bladders 2262 and 2264 include an upper layer 2266 and a lower layer 2268 coupled to the upper layer 2266. Inlet tubes 2270 and 2272 are coupled to the manifold assembly 62 which, in turn, is coupled to the pump 64 that provides pressurized air to inflate the chamber defined between the upper and lower layers 2266 and 2268. Sensing ports 2274 and 2276 are also provided in fluid communication with the chamber defined between the upper and lower layers 2266 and 2268 of the turn assist bladders 2262 and 2264. The sensing ports 2274 and 2276 are likewise in fluid communication with the manifold assembly 62 which, in turn, is in fluid communication with a pressure sensor or transducer 566 for detecting the pressure of air within the bladders 2262 and 2264. The fill tubes 2270 and 2272 extend in a longitudinal direction toward the head end 2186 of the receiving base 2108. Mounting tabs 2277 and 2279 are coupled to the fill tubes 2270 and 2272 and extend through the end wall 2180 of the receiving base 2108. Conventional fill ports or connectors 2281 are provided in fluid communication with the fill tubes 2270 and 2272. As illustrated in
As illustrated in
Right and left mounting flanges 2286 and 2288 are coupled to opposing edges of the right and left turn assist bladders 2262 and 2264, respectively. Illustratively the mounting flanges 2286 and 2288 are secured to the lower layers 2268 of the bladders 2262 and 2264 through radio frequency (RF) welding. The mounting flanges 2286 and 2288 include a plurality of mounting apertures 2290 proximate their outside side edges 2294 and 2296. Releasable fasteners, such as the buttons 2225 identified above, are received within the apertures 2290 of the mounting flanges 2286 and 2288, and likewise are received within the apertures 2216 of the mounting substrate 2116. As such, the turn assist bladder assembly 2120 is secured to the mounting substrate 2116. The turn assist bladder assembly 2120 may be made from a polyurethane film.
Upper Bladder Assembly
With reference to FIGS. 92 and 105-108, the upper bladder assembly 2122 is positioned above the turn assist bladder assembly 2120, such that the turn assist bladder assembly 2120 is sandwiched between the foam crowning core 2118 and the upper bladder assembly 2122 (
The upper bladder assembly 2122 includes a longitudinally extending center portion 2314 positioned intermediate longitudinally extending first and second side portions 2316 and 2318. First and second longitudinally extending hinges 2320 and 2322 connect the center portion 2314 to the first and second side portions 2316 and 2318, respectively. The hinges 2320 and 2322 provide increased flexibility to the inflated upper bladder assembly 2122, thereby allowing the individual bladders 2306 to generally follow the arcuate contour of the crowning core 2118. Further, the hinges 2320 and 2322 allow the inflated upper assembly 2122 to conform to the general contour defined by the turn assist bladder assembly 2120 when it is inflated (
The upper bladder assembly 2122 further includes a peripheral mounting flange 2324 including a plurality of securing apertures 2326 for receiving fasteners, such as buttons 2227. More particularly, the buttons 2227 pass through the apertures 2218 formed in the mounting substrate 2116 and through the apertures 2326 formed in the mounting flange 2324, thereby securing the upper bladder assembly 2122 to the mounting substrate 2116 (
The upper bladder assembly 2122 may be formed by an upper sheet 2342 and a lower sheet 2344 coupled together at various locations by seals, such as RF welds. More particularly, the welds may define the walls 2308 of the bladders 2306, the wall 2312 separating the head zone 2302 and the foot zone 2304, and the mounting flange 2324.
The head zone 2302 is in fluid communication with a supply tube 2346 that delivers pressurized air to the bladders 2306 and alternatively exhausts pressurized air from the bladders 2306. A sensing line 2348 is also provided in fluid communication with the head zone 2302 and provides pressurized air to the pressure sensor 566 as detailed herein. Likewise, the seat zone 2304 is in fluid communication with a supply tube 2350 that delivers pressurized air to the bladders 2306 and alternatively exhausts pressurized air from the bladders 2306. A sensing line 2352 is also provided in fluid communication with the seat zone 2304 and provides pressurized air to the pressure sensor 566.
Fire Barrier
Referring further to
Shear Cover
With reference to
The shear cover 2125 is formed from a material having a low coefficient of friction so that the mattress outer cover 2102 can slide relative to the other mattress components. As the mattress 14 is articulated or as the patient moves, the shear cover 2125 minimizes shear forces acting between the mattress top cover portion 2106 and the patient's body. The shear cover 2125 may be made from a woven nylon or parachute material. Illustratively, the shear cover 2125 is made from a polyurethane material such as Deerfield urethane PT611OS having a thickness of approximately 0.002 inches. The polyurethane material provides an inexpensive shear material which reduces shear forces applied to the patient's body situated on the mattress 14.
Outer Cover
Referring now to
The bottom cover portion 2104 includes a bottom wall 2366 and a sidewall 2368. The sidewall 2368 is illustratively formed from a ticking material similar to the sidewall 2365 of the top cover portion 2106. The sidewall 2368 of the bottom cover portion 2104 is coupled to the sidewall 2365 of the top cover portion 2106, illustratively through RF welding. Illustratively, the bottom wall 2366 of the bottom cover portion 2104 is formed from a polyurethane coated twill material for enhanced wear resistance and to protect other components of the mattress 14 from contamination. The bottom wall 2366 includes an access panel 2370 defined by a zipper 2372. The access panel 2370 is utilized during assembly of the mattress 14 and further facilitates removal of the replacement of the modular components of the mattress 14. Illustratively, the zipper 2372 is RF welded to the bottom wall 2366. In an alternative embodiment of the invention, the zipper 2372 may be utilized to couple the sidewall 2368 of the bottom cover portion 2104 to the sidewall 2365 of the top cover portion 2106.
With further reference to
Mattress Anchors
Referring now to
With reference to
Manifold Assembly and Mattress Connectors
The pair of mattress fluid connectors 2126 and 2127 are secured to the bottom cover portion 2104 and are received within the connector recess 2184 formed within the receiving base 2108. Each connector 2126 and 2127 includes a plurality of barbed fittings 2388 which are sealingly received within flexible tubing 2390 illustratively connected to one of the right turn assist bladder 2262, the left turn assist bladder 2264, the head zone 2302 of the upper bladder assembly 2122, and the seat zone 2304 of the upper bladder assembly 2122. Additional details regarding the mattress fluid connectors 2126 and 2127 are provided below in connection with the manifold assembly 62.
Referring now to
With further reference to
The valve assembly 2406c for controlling the right turn assist bladder 2262 is coupled to the second manifold 2404 and includes a normally closed pilot valve 2408c for controlling air intake and a normally open pilot valve 2410c for controlling the air exhaust. Likewise, the valve assembly 2406d for controlling the left turn assist bladder 2264 is coupled to the second manifold 2404 and includes a normally closed pilot valve 2408d for controlling air intake and a normally open pilot valve 2410d for controlling the air exhaust. An optional valve assembly 2406e is illustrated as coupled to the first manifold 2402 and may include pilot valves 2408e and 2410e, as desired, to control optional additional air zones within the mattress 14.
In an illustrative embodiment, the normally closed pilot valves comprise SY series piloted valves, Model No. SY114-5GZ available from SMC Corporation of Indianapolis, Ind. Likewise, in an illustrative embodiment of the invention, the normally open pilot valves comprise SY Series piloted valves, Model No. SY124-5GZ available from SMC Corporation of Indianapolis, Ind.
With further reference now to
Details of the valve assembly 2406c for controlling air pressure within the right turn assist bladder 2262 is illustrated in
With reference to
Each pilot valve 2408c and 2410c includes a conventional solenoid (not shown) received within a body portion 2424 and configured to move a pin 2426. The first pilot valve 2408c is normally closed, such that a diaphragm 2428 coupled to the pin 2426 sealingly engages a valve seat 2430. The normally closed valve 2408c includes a spring 2432 concentrically disposed around the pin 2426 and biasing the diaphragm 2428 downwardly into sealing engagement with the valve seat 2430. As such, air from the fill port 2418 may not pass to a supply port 2434 connected to the right turn assist bladder 2262 of the mattress 14. However, upon activation, the solenoid is energized such that the pin 2426 is pulled upwardly and the diaphragm 2428 moves away from the valve seat 2430. As such, a passageway represented by arrow 2436 is defined such that air may pass through the fill port 2418 over the valve seat 2430 and through the supply port 2434 to the right turn assist bladder 2262.
At the same time that the normally closed valve 2408c is activated, the normally open valve 2410c is likewise activated such that the solenoid is energized to push its pin 2426 downwardly thereby causing the diaphragm 2418 to sealingly engage the valve seat 2430. As such, the supply port 2434 is sealed off from an exhaust port 2438 in fluid communication with atmosphere. In the normally open valve 2410, the spring 2432 is concentrically received within a portion of the supply port 2434 and is configured to bias against the diaphragm 2428 to push the diaphragm 2428 away from the valve seat 2430 such that the supply port 2434 is in fluid communication with the exhaust port 2438.
The sensing ports or lines 2274, 2276, 2348, and 2352 from the controlled air zones 2262, 2264, 2302, and 2304 of the mattress 14 are coupled in fluid communication with the first and second manifolds 2402 and 2404 as shown in
With reference to
The outlets 2454 are in fluid communication with the supply ports 2434 of the valve assemblies 2406, while the plugs 2458 are in fluid communication with the intake ports 2270, 2272, 2346, and 2350 of the various controlled air zones 2262, 2264, 2302 and 2304 of the mattress 14 in the manner detailed herein. The outlets 2456 are in fluid communication with the pressure sensing tubes 2440 through the manifolds 2402 and 2404, while the plugs 2460 are in fluid communication with the sensing lines 2274, 2276, 2348, and 2352 of the controlled air zones of the mattress 14. In an alternative embodiment of the invention, the sensing lines 2274, 2276, 2348, and 2352 may bypass the manifolds 2402 and 2404 and be directly connected to the pressure sensors 2442.
Each of the plugs 2458 and 2460 illustratively includes an O-ring gasket 2462 and 2463 to promote sealing with a mating outlet 2454 and 2456, respectively. The mattress connectors 2126 and 2127 each include a peripheral inner flange 2464 which is configured to be received within a peripheral outer flange 2466 of a respective manifold receiving connector 2450 and 2452. A fastener, illustratively a u-shaped staple 2468 locks the peripheral flanges 2464 and 2466 together. More particularly, the inner flange 2464 includes apertures 2470 and the outer flange 2466 includes apertures 2472 which are coaxially aligned with the apertures 2470 when the mattress connector 2126, 2127 is properly seated within the mating manifold receiving connector 2450, 2452. The staple 2468 includes a pair of legs 2474 which are received within the aligned apertures 2470 and 2472 to lock the connectors. While a staple 2468 is illustrated, it should be appreciated that other fasteners, such as latches, may be readily substituted therefor.
As described above, the manifold receiving connectors 2450 and 2452 are coupled to the manifolds 2402 and 2404, respectively, through the partition wall 272. Conventional fasteners, such as screws 2476, may be utilized to secure the manifold receiving connectors 2450 and 2452 and the first and second manifolds 2402 and 2404 relative to the partition wall 272. In one illustrative embodiment, cylindrical gaskets may be positioned intermediate each outlet 2454 of the receiving connectors 2450 and 2452 and the manifold 2402 and 2404 in order to effect sealing therebetween.
In a further illustrative embodiment, a gasket 2502 such as that shown in
The outlet seals 2508 pass through apertures formed within the vertical wall 274 of partition 272 and are compressed between the manifold connectors 2450 and 2452 and the manifolds 2402 and 2404. Each outlet seal 2508 includes first and second pairs of annular sealing rings 2512 and 2514 which extend in opposite directions (
The gasket assembly 2502 provides for a rigid substrate 2504 which does not compress during assembly and thereby provides for a definite torque specification or tightening of the receiving connectors 2450 and 2452 against the respective manifolds 2402 and 2404. Likewise, the rigid substrate 2504 provides for a positive seal and accounts for variations or discrepancy in material dimensions. The individual cylindrical outlet seals 2508 provide for zone controlled sealing and prevent cross-communication between the various outlets 2454. Finally, the perimeter seal 2506 provides secondary sealing and prevents contamination within the receiving connectors 2450 and 2452 by dirt or other contaminants.
Pressure Control System
As mentioned elsewhere in this disclosure, control system 44 includes dynamic surface module 518. In addition to other functions, dynamic surface module 518 includes a pressure control system 3000. As shown in
Pressure sensors, illustratively transducers 566, periodically sense the pressure in one or more of controlled air zones 2262, 2264, 2302, 2304 of mattress 14 and output a voltage proportional to the amount of pressure that is sensed. Analog-to-digital converter 3002 converts the voltage to digital form and feeds the digital value to microcontroller 3004. Microcontroller 3004 analyzes the current pressure and determines whether the current pressure in controlled air zones 2262, 2264, 2302, 2304 is correct, too high, or too low in comparison to a desired pressure. Memory 3010 stores data, e.g. in the form of look-up tables, which is used in this analysis. For example, the desired pressure of an air zone 2262, 2264, 2302, 2304 may depend upon the particular operating mode of the system 3000 (e.g., pressure relief, max-inflate, CPR, right turn assist, or left turn assist), whether head section 38 is elevated and the degree of elevation, and/or the size of the patient. Tables 1, 2, and 3 show examples of desired pressures for controlled air zones 2262, 2264, 2302, 2304 based on the air system operating mode, patient size, and, for seat section 42, head section elevation.
If the pressure of an air zone 2262, 2264, 2302, 2304 is too high, microcontroller 3004 actuates the appropriate valve assembly 2406 to allow air to escape from the air zone 2262, 2264, 2302, 2304. If the pressure is too low, microcontroller 3004 sends a message over network 510 to power supply module 514 of patient support 10 (parts of which are generally depicted in
Among other things, embodiments of pressure control system 3000 illustratively include one or more of the following features: a process 3030 for controlling the inflation of controlled air zones 2262, 2264, 2302, 2304 according to the size of a patient, a process 3032 for controlling inflation of turn assist bladders 2262, 2264, and/or a process 3070 for controlling inflation of seat section 40 in response to elevation of head section 38.
Mattress Pressure Determination
In certain embodiments of pressure control system 3000 of dynamic surface module 518, a process 3030 for controlling the inflation of controlled air zones 2262, 2264, 2302, 2304 according to the size of a patient disposed on patient support 10 is provided. One embodiment of process 3030 is shown in
Process 3030 begins at step 3014 of
In the illustrative embodiment of
At step 3016, the controlled air zone(s) 2262, 2264, 2302, 2304 being monitored is determined. All of head section air zone 2302, seat section air zone 2304, and turn assist bladders 2262, 2264 may be inflated to varying pressures based on patient size. However, it is understood that in alternative embodiments not all of air zones 2262, 2264, 2302, 2304 may be inflated based on patient size.
At step 3018, process 3030 determines the desired inflation pressure for the respective air zone(s) 2262, 2264, 2302, 2304 being monitored based on the patient size. In the illustrated embodiment, microcontroller 3004 obtains the desired pressure for the air zone(s) 2262, 2264, 2302, 2304 from at least one look-up table stored in memory 3010. The desired pressure may be a discrete value or a range of permissible values. Also, the desired pressure may be different for each air zone 2262, 2264, 2302, 2304. Further, various other factors, including environmental factors such as temperature and/or altitude, may affect the desired pressure values and be reflected in data in the look-up table. As an example, in one embodiment, under normal hospital room conditions, for a patient considered “small,” the appropriate pressure is about 4-7 inches in water for head section air zone 2302, about 7 to 21 inches in water for seat section air zone 2304, and about 18-24 inches in water for turn assist bladders 2262, 2264. Tables 1, 2, and 3 show examples of desired pressure values based upon patient size.
As indicated by decision step 3020, in the illustrative embodiment of
At decision step 3024, microcontroller 3004 measures the current pressure as described above and determines whether the current pressure is less than, equal to, or greater than the desired pressure determined as described above. If the current pressure is less than the desired pressure at step 3026, microcontroller 3004 commands power supply 3006 to activate pump 64 to inflate air zone 2304 to the desired pressure as described above. If the current pressure is greater than the desired pressure, then at step 3028, air zone 2304 are deflated as described above.
Patient Turn Assist
In addition to other functions discussed above and elsewhere in this disclosure, pressure control system 3000 of dynamic surface module 518 controls the operation of turn assist bladders 2262, 2264. Turn assist bladders 2262, 2264 illustratively are bladders of mattress 14 that selectively inflate to assist a caregiver in turning or rotating a patient, e.g., for therapy or treatment reasons. One embodiment of a process 3032 for controlling operation of turn assist bladders 2262, 2264 is shown in
Process 3032 begins at step 3034 of
At decision step 3036, prior to initiating the turn assist function, process 3032 checks to make sure that the siderail(s) 20, 22 toward which the patient is being turned is in the up or raised position, based on signals provided by siderail position detector(s) 60. If one or more of siderails 20, 22 toward which the patient is being turned is not in the up position (i.e. in down or lowered position), an error signal is generated at step 3038 and process 3032 returns to step 3034 without activating the turn assist bladders 2262, 2264. In the illustrative embodiment, an audible or visual signal is generated for a brief period or until the siderail or siderails 20, 22 are brought to the up position. Thus, in the illustrative embodiment, the siderails 20, 22 toward which the patient is being turned must be in the up position in order for the turn assist process to initiate. It is possible, however, that in other embodiments, a caregiver or operator may override this restriction, or that this restriction may be made optional, for example, depending on the circumstances of a particular patient.
At decision step 3040, microcontroller 3004 checks to see if the angle of head section 38 (head angle) is less than, equal to, or greater than a predetermined maximum angle. In the illustrated embodiment, the maximum head angle is about 40.degree. The head angle determination is made by logic module 512 and is discussed in connection with
At step 3044, the size of the patient being supported by patient support 10 (e.g., small-medium-large) is determined as described above so that a desired pressure based on patient size is applied to the selected turn assist bladder 2262, 2264.
At step 3046, if first turn assist button 1624 is activated, first turn assist bladder 2262 inflates to rotate a person in patient support 10 upwardly in a counter-clockwise from the perspective of a person standing behind head section 38. If second turn assist button 1626 is activated, second turn assist bladder 2264 inflates to rotate the person upwardly in the opposite direction as rotated in response to activation of first turn assist button 1624. Inflation of the selected turn assist bladder 2262, 2264 raises one side of the patient to a predetermined angle. In the illustrated embodiment, the selected turn assist bladder 2262, 2264 inflates to rotate the patient onto his or her side at about a 20 degree angle with respect to mattress 14, in approximately 20-50 seconds, depending on the size of the patient. It is understood that the predetermined angle and speed of inflation may be changed or modified as needed based on a variety of factors, including the purpose for rotating the patient.
A timer, illustratively part of the central processing unit 3012, is set at step 3048 when the selected turn assist bladder 2262, 2264 is inflated. The selected turn assist bladder 2262, 2264 remains inflated for a predetermined period of time, for example 5-30 seconds. In the illustrated embodiment, the duration of turn assist inflation is about 5 seconds. At step 3050 the timer counts out this wait period. After the wait period is complete (e.g., after 5 seconds), an audible or visual signal is generated to indicate to the patient and caregiver that the selected turn assist bladder is about to enter a “post-turn assist” phase. Process 3032 then begins deflating the selected turn assist bladder 2262, 2264 at step 3052. In the illustrated embodiment, deflation is expedited by quickly “hyperinflating” bladders 2302, 2304 to a firm, “post-turn assist” inflation pressure (see, e.g., Table 1 and Table 2). Inflation of bladders 2302, 2304 exerts pressure on turn assist bladders 2262, 2264, causing turn assist bladders 2262, 2264 to expel air more rapidly. Alternatively, a vacuum mechanism may be coupled to turn assist bladders 2262, 2264 to accelerate deflation.
The post-turn assist inflation and deflation processes may be interrupted under certain circumstances. For example, when a patient's bed 10 needs a linen change, it may be desirable for first and second turn assist bladders 2262, 2264 to be activated in more rapid succession than would be possible if the full post-turn assist process were performed. In such instances, if one of turn assist buttons 1624, 1626 is activated, and then the other turn assist button 1624, 1626 is activated before the previous turn assist process is complete, the previous process is interrupted and, as long as the turned-to-side siderails 20, 22 are in the up position as described above, and head section 38 is positioned at an angle less than or equal to 40 degrees, the new turn assist mode is started.
For example, assume a caregiver presses first turn assist button 1624. If the caregiver then presses second turn assist button 1626 while first turn assist bladder 2262 is inflating, then process 3032 will interrupt the inflation, bypass the post-turn assist phase (i.e., head and seat bladders 2302, 2304 will not be inflated), and begin inflating second turn assist bladder 2264 as long as siderails 20, 22 are up on the side of the bed the patient is being turned to, and the head angle is less than or equal to the maximum head angle. If the caregiver presses second turn assist button 1626 while first turn assist bladder 2262 is in post-turn assist mode, post-turn assist mode is interrupted and second turn assist bladder 2264 begins inflating as discussed above.
Monitor activity step 3060 is a step that is periodically executed during the turn assist operation. The monitor activity process 3060 is shown in more detail in
At step 3066, process 3060 detects whether a patient or caregiver has selected another mode, e.g., turn assist for the other side of the patient, max inflate, or pressure relief. During the turn assist operation, the selection of another mode causes process 3060 to begin exiting the turn assist mode at block 3067. If the other turn assist mode is selected, the current turn assist bladder 2262, 2264 is deflated and the other turn assist mode is entered substantially immediately. If the pressure relief mode or the max-inflate mode is selected, process 3060 immediately enters the post-turn assist operation and enters the newly selected mode upon completion of the post-turn assist phase. However, if the CPR function is activated, process 3060 immediately deflates turn assist bladder 2262, 2264 and enters the CPR mode substantially immediately. If no mode is selected during turn assist, process 3060 will exit as described previously and enter the pressure relief mode upon completion of the post-turn assist phase.
At step 3068, process 3060 detects whether the angle of head section 38 has been increased above the maximum head angle as described above. If the head angle increases above the maximum head angle, an error message, e.g., in the form of an audible or visual signal, is generated at step 3069. In the illustrated embodiment, the turn assist process 3032 is interrupted if the head angle exceeds the maximum angle. In alternative embodiments, the turn assist process 3032 is not interrupted.
Head Section Elevation
In addition to other functions discussed above and elsewhere in this disclosure, pressure control system 3000 may include another process 3070 for controlling the inflation of seat section air zone 2304 according to the position of head section 38. One embodiment of such method is shown in
When head section 38 is elevated, a portion of the patient's weight naturally shifts from head section 38 to seat section 40. To anticipate this weight shift and prevent “bottoming out,” the inflation pressure of seat section air zone 2304 is adjusted in response to changes in the position of head section 38. Table 4 below shows pressure ranges for seat section air zone 2304 depending on both patient size and angle of elevation of head section 38.
At step 3072 of
At decision step 3074, process 3070 evaluates the input received from logic module 512 and determines whether head section 38 has experienced at least a 3 degree change in position by comparing the current head angle to the previous head angle. If the head angle has changed at least approximately 3 degrees, the process 3070 continues to step 3076. If no change or less than approximately 3 degrees change in either direction has occurred, process 3070 returns to step 3072. It is understood that 3 degrees is an exemplary value and that a change in the head angle may be indicated by a greater or lesser value as appropriate. Of course, during this time, pressure control system 3000 continues to periodically measure the pressure of seat section air zone 2304 to make sure that it is within the desired ranges.
At decision step 3076, it is determined whether the change in position of head section 38 occurred in the upward or downward direction. This determination is derived from the comparison of the current head angle to the previous head angle. As shown in Table 5, the ranges of values indicating a change in head elevation overlap, in order to take into consideration hysteresis in the head angle evaluation.
For example, head section 38 will be considered to have moved from region zero to region 1 if a potentiometer value of about 52 is received by process 3070 (corresponding to a head angle of 1-10 degrees). However, once head section 38 is in region 1, it will not be considered to have moved back to region zero unless a potentiometer reading outside the specified range for region 1, e.g., approximately 40 or less, is received.
If a change in position occurs in the downward direction, i.e., head section 38 is lowered, then at step 3078 the inflation pressure of seat section air zone 2304 is decreased according to the size of the patient and the current head angle. The desired pressure range is determined by reference to a look-up table stored in memory 3010. Table 4 above is an example of such a table.
If a change in position occurs in the upward direction, i.e., head section 38 is elevated, then at step 3080 the inflation pressure of seat section air zone 2304 is increased. First, a “seat boost” is applied to seat section air zone 2304, meaning that seat section air zone 2304 is initially over-inflated for a brief period of time to compensate for the above-mentioned weight shift. Examples of the initial “seat boost” pressures are shown in Table 2 above. In the illustrated embodiment, the period of time for the seat boost is about 15 seconds. After the seat boost period expires, process 3070 adjusts the pressure of seat section bladders 2304 to the desired level based on patient size and head angle, as determined by the look-up table mentioned above.
Second Illustrative Embodiment Mattress Assembly
A second illustrative embodiment modular mattress assembly 4014 of the present invention is configured to be supported by deck 26′, as shown in
Mattress Foot Section Assembly
As detailed above with respect to leg section 42 of deck 26, the leg section 42′ of the deck 26′ is likewise extendable and retractable.
The foot section 4210 is perforated to facilitate its longitudinal extension and retraction. More particularly, the foot section 4210 is formed to include a plurality of apertures, illustratively transversely extending slots 4238 extending in a generally vertical direction through the base portion 4228 and the flange portions 4230 and 4232, to facilitate compressibility of the foot section 4210 in response to the retraction of the leg section 42′ of the deck 26′. More particularly, the plurality of slots 4238 are arranged in a plurality of laterally extending rows 4240 wherein the individual slots 4238 of each row 4240 are laterally offset from those slots 4238 of longitudinally adjacent rows 4240. It may be readily appreciated, each slot 4238 widens to accommodate the extension of the leg section 42′ and narrows to accommodate the retraction of the leg section 42′ of the deck 26′.
While in the illustrative embodiment a plurality of discrete laterally and longitudinally spaced transverse slots 4238 are illustrated to facilitate retraction and extension of the foot section 4210, it should be appreciated that other structures may be readily substituted therefor. More particularly, the foot section 4210 may be formed to include serpentine channels or a plurality of slots extending substantially the full width of the foot section 4210 between opposing side edges of the flange portions 4230 and 4232.
A foot section mounting plate 4242 is secured to a lower surface 4244 of the foot section 4210, illustratively through an adhesive tape 4245. As described in greater detail below, the foot section mounting plate 4242 provides a securing platform for a foot section anchor 4246 which couples the foot section 4210 to the leg section 42′ of the deck 26′ to facilitate movement in cooperation therewith.
The foot section 4210 further includes a receiving recess 4248 extending downwardly from an upper surface 4250 of the base portion 4228 at a foot end 4252 thereof. The heel bladder assembly 4215 defines a heel pressure relief zone 4254 and is coupled to the foot mounting substrate 4214 and is received within the recess 4248. Opposing first and second ends of the foot mounting substrate 4214 are coupled to a pair of foot attachment straps 4256. The attachment straps 4256 each have a center mounting aperture 4257 coupled to the foot section mounting member 4242 through a conventional fastener, such as a button 4258. Similarly, opposing ends of the foot attachment straps 4256 including mounting apertures 4259 which are secured to the opposing ends of the foot mounting substrate 4214 through conventional fasteners, such as buttons 4258 (
Heel Bladder Assembly
As noted above, the heel bladder assembly 4215 is supported within the recess 4248 and is coupled to the foot mounting substrate 4214. As illustrated in
Referring further to FIGS. 130 and 133-135, a plurality of outer and inner fasteners 4268 and 4270, illustratively snaps, are secured to the foot mounting substrate 4214 proximate opposing side edges thereof. The foot mounting substrate 4214 is formed from a flexible sheet material, such as polyurethane coated twill. Opposing ends of each bladder 4264 include an upper fastener 4272 and a lower fastener 4274, illustratively snaps, which cooperate with the outer fastener 4268 and the inner fastener 4270 of the foot mounting substrate 4255.
A foot fill tube 4276 is fluidly connected to the first bladder 4264a while a foot sensor tube 4278 is fluidly connected to the fourth fluid bladder 4264d. As illustrated in
The tubes 4276 and 4278 may be coupled to the foot section mounting member 4242 through a conventional cable tie (not shown). Further retention of the tubes 4276 and 4278 to the mounting substrate 4216 may be provided by a securing loop 4338 coupled to the mounting substrate 4216.
The heel bladder assembly 4215 is configured to provide heel pressure relief by reducing the level of raised pressure between the patient's foot and the mattress. More particularly, the heel bladder assembly 4215 provides for a region of reduced pressure below the patient's heels. The foot section 4210 includes a calf portion 4279 which supports the portion of the patient's weight that would otherwise be supported by the patient's heel and thus reduces the overall interface pressure between the patient's heel and the mattress 4014. It is envisioned that the calf portion 4279 of the mattress 4014 may include a transition zone where the material stiffness of the foot section 4210 decreases in a longitudinal direction extending generally from head end 4018a to the foot end 4018b of mattress 4014.
Mattress Body Section Assembly
The body section 4212 of the receiving base 4208 is further illustrated in
The sidewalls 4281 and 4282 each include an angled or inclined portion 4288 coupled to a flange portion 4290. The angled portions 4288 are configured to conform to the angled sidewalls 260 and 262 of the deck 26′, while the flange portions 4290 are configured to extend above and out beyond the sidewalls 260 and 262 of the deck 26′. The body section 4212 of the receiving base 4208 includes a head portion 4292 and a seat portion 4294 separated by a laterally extending slit 4296 (
Mattress Mounting Substrate
With reference to
The mounting substrate 4216 includes a base portion 4322 and first and second mounting portions 4324 and 4326 extending along opposing longitudinal side edges of the base portion 4322. Each mounting portion 4324 and 4326 includes a outer mounting member 4328 and an inner mounting member 4330 hingedly connected to the outer mounting member 4328 through a hinge 4329. The mounting members 4328 and 4330 include a plurality of longitudinally spaced outer and inner fasteners 4332 and 4334, illustratively snaps, configured to couple to corresponding fasteners of the upper bladder assembly 4222 as detailed below. A plurality of turn assist bladder assembly securing apertures 4336 are formed proximate opposing longitudinally extending side edges of the mounting substrate 4216. As detailed below, the apertures 4336 are configured to receive fasteners, such as buttons 4337 for securing the turn assist bladder assembly 4220 to the mounting substrate 4216. First and second securing loops 4338 and 4339 are coupled to the base portion 4322 and are configured to receive various fluid tubes for retention therein.
Foot Section Securing Substrate
With further reference to
Illustratively, the foot section securing substrate 4340 is formed from a flexible sheet material, such as pack cloth urethane coated twill. As a flexible sheet material, the foot section securing substrate 4340 may follow a serpentine path from a horizontal first plane of the bottom layer 4280 of the receiving base 4208 and vertically down around a foot end edge 4352 of the receiving base 4208, and back along a horizontal plane of the lower surface 4277 of the foot section 4210.
Foam Filler
The foam filler or panel 4218 is received within the channel 4284 defined by the sidewalls 4281 and 4282 of the body section 4212 of the receiving base 4208. Illustratively, the filler 4218 is made of polyurethane foam having an indention force deflection (IFD) of between approximately 23 pounds to approximately 29 pounds. IFD is commonly defined in the art as the amount of force necessary to indent an 8 inch disc plate 25 percent into the foam of a 4 inch thick sample 15 inches by 15 inches square. Further illustratively, the filler 4218 includes sidewalls 4354 and 4355 which are angled to conform with the angled walls 4281 and 4282 of the receiving base 4208. A fastener, illustratively a loop portion 4356 of a conventional hook and loop fastener, is secured to a lower surface of the foam filler 4218 and is configured to couple with a mating hook portion 4357 secured to an upper surface of the receiving base 4208. A clearance opening 4359 is formed within the mounting substrate 4216 to allow for coupling of the fastener portions 4356 and 4357.
Turn Assist Bladder Assembly
Referring to FIGS. 130 and 139-141, the turn assist bladder assembly 4220 is positioned above the foam filler 4218 and includes a first, or right, inflatable turn assist bladder 4358 and a second, or left, inflatable turn assist bladder 4360. As described in greater detail herein, each of the right and left turn assist bladders 4358 and 4360 are selectively and individually inflatable to assist in the turning of a patient supported on the mattress 4014.
Each of the turn assist bladders 4358 and 4360 include an upper layer 4362 and a lower layer 4364 coupled to the upper layer 4362. Right and left turn assist fill tubes 4366 and 4368 are configured to be coupled to the manifold assembly 4063 which, in turn, is coupled to the pump 4064 that provides pressurized air to inflate the chamber defined between the upper and lower layers 4362 and 4364 of the turn assist bladders 4358 and 4360, respectively. Right and left turn assist sensor tubes 4370 and 4372 are also provided in fluid communication with the chamber defined between the upper and lower layers 4362 and 4364 of the turn assist bladders 4358 and 4360, respectively. The sensor tubes 4370 and 4372 are likewise configured to be placed in fluid communication with the manifold assembly 4063 which, in turn, is in fluid communication with a pressure sensor 566 for detecting the pressure of air within the bladders 4358 and 4360. The fill tubes 4366 and 4368 extend generally in a longitudinal direction from proximate the head end of the respective bladders 4358 and 4360 to the mattress connector 4068 proximate the head end of the receiving base 4208. The sensor tubes 4370 and 4372 extend from a foot end of the respective bladders 4358 and 4360 laterally to proximate first side 4017a of the mattress 4014 and intermediate the turn assist bladder assembly 4220 and the mounting substrate 4216. The sensor tubes 4370 and 4372 continue through securing loop 4339 and are coupled to mattress connector 4068.
Right and left mounting flanges 4376 and 4378 extend in directions outwardly from opposing edges of the right and left turn assist bladders 4358 and 4360, respectively. Illustratively the mounting flanges 4376 and 4378 are secured to the lower layers 4364 of the bladders 4358 and 4360 through radio frequency (RF) welding. The mounting flanges 4376 and 4378 include a plurality of mounting apertures 4380 proximate their respective side edges 4382 and 4384. Releasable fasteners, such as the buttons 4337, are received within the apertures 4380 of the mounting flanges 4376 and 4378, and likewise are received within the apertures 4336 of the mounting substrate 4216. As such, the turn assist bladder assembly 4220 is secured to the mounting substrate 4216. The turn assist bladder assembly 4220 may be made from polyurethane film.
Upper Bladder Assembly
The upper bladder assembly 4222 is positioned above the turn assist bladder assembly 4220, such that the turn assist bladder assembly 4220 is sandwiched between the foam filler 4218 and the upper bladder assembly 4222 (
Each bladder 4398, 4400 is substantially identical to the bladders 4264 of the heel bladder assembly 4215. As such, similar or identical reference numbers are utilized to indicate similar or identical components in bladders 4264, 4398 and 4400. Bladders 4398, 4400 each includes upper and lower inflatable center portions 4402 and 4404 and opposing upper inflatable end portions 4406 and 4408. The upper inflatable center portion 4404 is separated from the end portions 4406 and 4408 by hinge portions 4403 and 4405. The end portions 4406 and 4408 define first and second notches or spaces 4407 and 4409 which are configured to provide clearance for movement of the bladder 4398 about the hinge portions 4403 and 4405. Webs 4415 and 4417 are located in the notches 4407 and 4409 and connect the lower center portion 4404 to the end portions 4406 and 4408, respectively.
The bladders 4398, 4400 each include an upper fastener 4272 and a lower fastener 4274, illustratively snaps, configured to cooperate with the outer and inner fasteners 4332 and 4334 of the mounting substrate 4216. As illustrated in
Further, the couplings between the bladders 4398 of the upper bladder assembly 4220 and the mounting substrate 4216 define an upper crowning surface 4410. More particularly, the upper surface 4410 of the bladder assembly 4220 proximate the longitudinal center axis 4019 of the assembly 4220 is positioned vertically above the upper surface 4410 proximate the opposing longitudinal side edges 4412, 4413 of the bladder assembly 4220. Illustratively, the vertical distance of the crowning upper surface 4410 from the center axis 4019 to the respective side edges 4412, 4413, as represented by reference letter “d” in
The crowning surface 4410 is configured to facilitate lateral patient transfer from the bed 4010 to another patient support device positioned adjacent to the bed 4010 by creating an inclined surface which provides a slight amount of gravity assistance when the caregiver is moving the patient toward the side of the mattress 4014. Additionally, since the surface 4410 at the side edges 4412 and 4413 is lower than proximate the center axis 4411, the siderails 4020 and 4022 may have a lower profile and still fulfill minimum height requirements.
A pair of seat attachment straps 4425 are configured to couple together selected air bladders 4440 of the seat bladder assembly 4396, illustratively bladders 4400a-4400c. The straps 4425 illustratively wrap around the bladders 4440a-4440c and have ends coupled together with conventional fasteners, such as buttons 4427.
Fluid Tube Routing
A head section fill tube 4414 and a head section sensor tube 4416 are coupled to the head section 4390. More particularly, the fill tube 4414 is fluidly coupled to the air bladder 4398e proximate the longitudinal center of the head section 4390, and the sensor tube 4416 is fluidly coupled to the air bladder 4398i proximate the seat section 4392. Both the fill tube 4414 and the sensor tube 4416 travel from respective bladders 4398e and 4398i in a generally longitudinal direction, to the mattress connector 4068 at the head end of the receiving base 4208, intermediate the bladders 4398 and the turn assist bladder assembly 4220. Both tubes 4414 and 4416 are received within securing loop 4338. A head section connection assembly 4418 fluidly connects each of the bladders 4398 and illustratively comprises a plurality of conventional T-shaped fluid connectors 4420 and L-shaped fluid connectors 4422.
A seat section fill tube 4424 and a seat section sensor tube 4426 are coupled to the seat section 4392. More particularly, the fill tube 4424 is fluidly coupled to a seat section connection assembly 4428 which, in turn, is fluidly coupled to each air bladder 4400 of the seat bladder assembly 4396. The seat section connection assembly 4428 illustratively comprises a plurality of T-shaped fluid connectors 4420 and an L-shaped fluid connector 4422. The sensor tube 4426 is fluidly coupled to air bladder 4400d located proximate the longitudinal center of the seat section 4392. Both the fill tube 4424 and the sensor tube 4426 travel from the seat bladder assembly 4396 in a generally longitudinal direction to the mattress connector 4068 at the head end of the receiving base 4208. The fill tube 4424 travels along sidewall 4282 of the receiving base 4208 intermediate the upper bladder assembly 4222 and the turn assist bladder assembly 4220, and is received within securing loop 4339 of the mounting substrate 4216. Similarly, the sensor tube 4426 travels along sidewall 4281 of the receiving base 4208 intermediate the upper bladder assembly 4222 and the turn assist bladder assembly 4220, and is received within securing loop 4338 of the mounting substrate 4216.
Fire Barrier
Referring again to
Shear Cover
The shear cover 2125 is configured to fit over the above-identified mattress components as received within the fire barrier 2124. The shear cover 2125 is configured to be located between the fire barrier 2124 and the outer cover 2102 to permit the top cover portion 2106 to slide easily over the fire barrier 2124 and move relative to the other internal mattress components, thereby reducing shear forces between the patient's body and the mattress 4014 and reducing the likelihood of sacral breakdown.
The shear cover 2125 is formed from a material having a low coefficient of friction so that the mattress outer cover 2102 can slide relative to the other mattress components. As the mattress 4014 is articulated or as the patient moves, the shear cover 2125 minimizes shear forces acting between the mattress top cover portion 2106 and the patient's body. The shear cover 2125 may be made from a woven nylon or parachute material. Illustratively, the shear cover 2125 is made from a polyurethane material such as Deerfield urethane PT611OS having a thickness of approximately 0.002 inches. The polyurethane material provides an inexpensive shear material which reduces shear forces applied to the patient's body situated on the mattress 4014.
Additional details of the shear cover 2125 and the top cover portion 2106 are described above.
Outer Cover
Referring now to
With further reference to
Mattress Anchors
With further reference to
Manifold Assembly and Mattress Connectors
Referring now to
The pneumatic connections to the manifold assembly 4063 of the present invention is further illustrated in
With further reference now to
The sensing lines 4278, 4370, 4372, 4416, and 4426 from the controlled air zones of the mattress 4014 are coupled in fluid communication with the manifold 4063. In the illustrative embodiment, each sensing line 4278, 4370, 4372, 4416, and 4426 supplies air to the mattress connector 4068 which, in turn, provides air to the manifold connector 4070. The air exits the manifold connector 4070 through pressure sensing tubes 2440. Each tube 2440 is coupled to a pressure sensor 566 supported on a valve controller circuit board 2444. The circuit board 2444 is in communication with the control system 44 and as such, provides signals to the control system 44 indicative of pressure within the various controlled air zones of the mattress 4014. In an alternative embodiment, each sensing line 4278, 4370, 4372, 4416, and 4426 supplies air which passes through fluid sensing ports (not shown) formed within the manifold 4063 and then exits through pressure sensing tubes 2440.
The mattress connector 4068 is configured to couple to the manifold connector 4070 which is in fluid communication with the manifold 4063. The partition wall 272 coupled to the deck 26′ is positioned intermediate the manifold connector 4070 and the manifold 4063. The manifold connector 4070 is configured to sealingly mate with the mattress connector 4068. The manifold connector 4070 includes a plurality of outlets 4436, 4438 configured to sealingly receive plugs 4440, 4442, respectively, of the mating mattress connector 4068. The outlets 4436 of the manifold connector 4070 are in fluid communication with the valve assemblies of the manifold 4063, while the plugs 4440a, 4440b, 4440c, 4440d, and 4440e are in fluid communication with the controlled air zones 4358, 4360, 4254, 4392, and 4390 of the mattress 4014 through respective fittings 4432 and fill tubes 4366, 4368, 4276, 4424, and 4414 in the manner detailed above. The outlets 4438 of the manifold connector are in fluid communication with the pressure sensors 566 through the manifold 4063, while the plugs 4442a, 4442b, 4442c, 4442d, and 4442e are in fluid communication with the controlled air zones 4358, 4360, 4254, 4392, and 4390 of the mattress 4014 through fittings 4434 and sensor tubes 4278, 4416, 4426, 4372, and 4370. As may be readily appreciated, in alternative embodiments, the sensor tubes may bypass the manifold 4063 and be directly connected to the respective pressure sensors 566.
Each of the plugs 4440 and 4442 illustratively includes a conventional O-ring gasket 4444 to promote sealing with a mating outlet 4436 and 4438. The mattress connector 4068 includes a peripheral inner flange 4446 which is configured to be received within a peripheral outer flange 4448 of the manifold connector 4070. Illustratively, a plurality of fasteners 4450 lock the peripheral flanges 4446 and 4448 together. Illustratively, each fastener 4450 comprises a spring-biased U-shaped tab 4452 extending outwardly from the mattress connector 4068 and including an opening 4454 configured to be received over a locking tab 4456 supported by the manifold connector 4070. A U-shaped retaining member 4457 is supported by the manifold connector 4070 in spaced relation to the locking tab 4456 such that the tab 4452 of the mattress connector 4068 may be received therebetween. In the illustrative embodiment of
As described above, the manifold connector 4070 is coupled to the manifold 4063, respectively, through the partition wall 272. Conventional fasteners, such as screws 4058, may be utilized to secure the manifold connector 4070 and the manifold 4063 relative to the partition wall 272. In one illustrative embodiment, cylindrical gaskets may be positioned intermediate each outlet 4436, 4438 of the manifold receiving connector 4070 and the manifold 4063 in order to effect sealing therebetween. In a further illustrative embodiment, a gasket 2502′ (
Mattress Sensor
With reference to
According to an illustrative embodiment, the sensor 4462 comprises a Hall effect field sensor 4464 that detects the characteristics of a dynamic field generated by the mattress connector 4068. More particularly, a magnet 4466 is positioned within a receiving boss 4468 of the mattress connector 4068 (
An illustrative circuitry associated with the sensor 4464 is shown in
Further, the type and functionality of an air mattress 4014 connected to the manifold connector 4070 may be associated with a predetermined sensitivity of Hall effect sensor 4464 or strength of magnet 4466. Alternatively, multiple magnets 4466 and associated Hall effect sensors 4464 may be used to distinguish between different types of mattresses 4014. Upon sensing a particular type of mattress 4014, the control system 44 may deactivate and/or activate selected functions. For example, should the control system 44 receive a signal from the mattress sensor 4462 indicating that the mattress 4014 has no turn assist bladder assembly 4220, then the left and right turn assist functionality may be deactivated.
In a further illustrative embodiment, the presence of the fluid connector 4068 of the mattress 4014 may be detected by the pressure sensors, illustratively pressure transducers 566, which are in communication with the control system 44. More particularly, the control system 44 can initiate a diagnostic routine or process at predetermined intervals by supplying pressure to the outlets 4436 in the manifold connector 4070. Should no mattress 4014 be connected to the manifold connector 4070, then the pressure transducers 566 connected to the sensor outlets 4438 will measure atmospheric pressure (i.e., no back pressure). However, if a mattress 4014 is connected, then the sensor outlets 4438, upon the application of fluid through the fill outlets 4436, will measure a certain amount of back pressure. As such, through this diagnostic routine, the control system 44 can determine if a mattress 4014 is connected to the manifold 4063, and also which outlets 4436 are connected to respective air zones 4254, 4358, 4360, 4390 and 4392. Again, if the control system 44, through operation of the pressure sensors 566, determines that only certain air zones 4254, 4358, 4360, 4390, and 4392 are coupled to the manifold 4063, then certain functions may be activated and others deactivated.
It should be further noted that other mattress detection devices or sensors may be readily substituted for those detailed herein. For example, mechanical switches, conducting pins, and other proximity sensors may be readily substituted therefor.
Pressure Control System
As detailed above with respect to
Pressure sensors, illustratively transducers 566, periodically sense the pressure in one or more of controlled air zones 4254, 4358, 4360, 4390, and 4392 of mattress 4014 and output a voltage proportional to the amount of pressure that is sensed. Analog-to-digital converter 3002 converts the voltage to digital form and feeds the digital value to microcontroller 3004. Microcontroller 3004 analyzes the current pressure and determines whether the current pressure in controlled air zones 4254, 4358, 4360, 4390, and 4392 is correct, too high, or too low in comparison to a desired pressure. Memory 3010 stores data, illustratively in the form of look-up tables or algorithms, which is used in this analysis. For example, the desired pressure of air zones 4254, 4358, 4360, 4390, and 4392 may depend on the particular operating mode of the system 3000 (e.g., pressure relief, max-inflate, CPR, turn assist, and post-turn assist), whether head section 4038 is elevated and the degree of elevation, and/or the size or weight of the patient. The microcontroller 3004 operates valve solenoids 564 in response to the feedback signals from pressure transducers 566 to achieve the desired adjustments to mattress 4014. The valve solenoids 564 control the flow of air to and resulting pressure within the mattress 4014. Additional details regarding the valve solenoids 564 are provided above.
Valve Sensor
With reference now to
The determination of the particular type of valve 2406 is achieved by energizing each connected solenoid 564 individually. When a valve 2406 is actuated by the closing of a valve control relay 4488, the current pulled by the respective solenoid 564 is measured by a current transducer 4490. This measurement is supplied to an analog to digital converter 4492 which, in turn, supplies the measurement to a microcontroller, illustratively the microcontroller 3004 of the pressure control system 3000. Alternatively, the microcontroller may be independent of the microcontroller 3004. The microcontroller 3004 compares the measurement to known operating current values which are representative of the direct acting solenoid valve and the pilot operated solenoid valve. This comparison is the basis for deciding the type of valve 2406 (i.e. direct acting solenoid valve or pilot operated solenoid valve).
If the microcontroller 3004 determines that the number and types of valves 2406 equal a predetermined configuration, then the valves 2406 are driven by the microcontroller 3004 as appropriate for those types. If the microcontroller 3004 determines that the number and types of valves 2406 does not equal the predetermined configuration, then an error is reported by the microcontroller 3004. In one illustrative embodiment, the predetermined configuration is defined such that all of the valves 2406 coupled to the manifold 4063 are pilot operated solenoid valves. As such, the microcontroller 3004 queries whether all of the valves 2406 are pilot operated solenoid valves. If so, then the valves 2406 are driven by the microcontroller 3004 as appropriate for pilot operated solenoid valves. If the valves 2406 collectively are determined not to be of the predetermined configuration, in this illustrative embodiment meaning that all of the valves 2406 are not pilot operated solenoid valves, then the microcontroller 3004 reports an error. It should be appreciated that the predetermined configuration may comprise all direct acting solenoid valves, all pilot operated solenoid valves, or any combination thereof.
As further illustrated in
The valve sensor 4484 permits the utilization of different predetermined configurations of valves 2406 in different patient supports. More particularly, the configuration of valves 2406 may be varied for different types or model years of patient supports in order to facilitate cost effectiveness and to take advantage of technological developments in valve design. For example, in a first patient support, all pilot operated valves may be utilized and the predetermined configuration stored in the microcontroller 3004 reflects this situation. However, in a later second patient support, all direct acting solenoid valves may be utilized. As such, the microcontroller 3004 may be modified or re-programmed to detect this new predetermined configuration.
Mattress Pressure Determination
As detailed herein, the various modes of operation include a pressure relief mode, which is a standard operating mode of the respective air zones for providing pressure relief to the body of the patient. The max inflate mode of operation is the operating mode for providing maximum inflation of the respective air zones. The CPR mode of operation is the operating mode for providing a firm pressure in the respective air zones for assisting in the delivery of CPR to the patient. The turn assist mode of operation is the operating mode for providing pressure in the respective air zones for assisting in the left or right turning or rotation of the patient. Finally, the post-turn assist mode of operation is the operating mode for providing pressure in the respective air zones for assisting in the deflation of the turn assist bladders.
Tables 6-9 illustrating examples of desired pressures of air zones 4254, 4358, 4360, 4390, and 4392 based on the air system operating mode, patient weight, and, for seat air zone 4392, head section elevation, are provided as follows:
With reference now to
Next, as indicated at block 4714, the pressures in the head, seat, right turn assist and left turn assist zones 4390, 4392, 4360 and 4362 are not regulated by the pressure control system 3000. Further, all air mode indicators 1518 on the controller 54 are deactivated or off. At block 4716, the controller 3004 queries whether a mode button 1622, 1624, 1626, 1628 for operation of the pressure control system 3000, has been selected on the controller 54. If not, then the process returns to block 4714. If a mode button 1622, 1624, 1626, 1628 has been selected, then the process continues to decision block 4718, where the controller 3004 determines if the mattress sensor 4462 detects a mattress 4014.
If at block 4718, the mattress sensor 4462 does not detect a coupled mattress 4014, then the controller 3004 at block 4720 flashes selected mode indicators 1518 on the controller 54 and also sounds an audible alarm for a selected time period. The process then returns to block 4714. If at block 4718, the mattress sensor 4462 detects a coupled mattress 4014, then the process continues to block 4722 when the pressure controller 3000 enters or initiates the selected mode of operation.
As such, it may be appreciated that the mattress sensor 4462 of the present invention provides the operator with the flexibility of utilizing the bed 10′ with a dynamic air mattress 4014 or some other support surface, such as a static foam mattress. If the bed 10′ is to be used with a static foam mattress, for example, then the mattress sensor 4462 signals the controller 3004 which, in turn, cannot be activated by the operator. The pressure control system 3000 remains in an inactive or OFF mode, thereby locking out an operator from activating or turning ON the pressure control system 3000 and attempting to use the system on a foam mattress.
The controller 3004 of pressure control system 3000 regulates pressure within the air mattress 4014. If the pressure of an air zone 4254, 4358, 4360, 4390, and 4392 is too high, controller 3004 actuates the appropriate valve assembly actuator 564 to allow air to escape from the air zone 4254, 4358, 4360, 4390, and 4392. If the pressure is too low, microcontroller 3004 sends a message over network 510 to power supply module 514 of patient support 4010 (parts of which are generally depicted in
Among other things, embodiments of pressure control system 3000 include one or more of the following functionalities: a process 3030 for controlling the inflation of air zones 4254, 4358, 4360, 4390, and 4392 according to the size or weight of a patient, a process 3032 for controlling inflation of turn assist bladders 4358, 4360, a process 3070 for controlling inflation of seat section 4392 of mattress 4014 in response to elevation of the head section 4038 of the deck 26′ and/or a process for controlling inflation of seat section 4392 of mattress 4014 in response to the patient sitting up on the bed 4014 with little or no support by the head section 4038 of the deck 26′.
Mattress Pressure Dependency on Patient Weight
In certain illustrative embodiments of pressure control system 3000 of dynamic surface module 518, a process 4730 for controlling the inflation of air zones 4254, 4358, 4360, 4390, and 4392 according to the size or weight of a patient disposed on patient support 4010 is provided. One illustrative embodiment of process 4730 is shown in
In certain illustrative embodiments as detailed above, an operator or caregiver is required to select an appropriate patient weight. In still other embodiments, the controller 3004 automatically selects a default setting, e.g., the “medium” size, if a patient weight is not selected by the operator or caregiver.
In yet another illustrative embodiment, pressure control system 3000 automatically determines the patient's weight through measurements by weigh frame 36 and/or by a force sensor supported by seat section 40′. More particularly, and with reference to
The FSRs are of conventional design and have resistance values which change depending upon the amount of force applied thereto. FSRs generally comprise polymer thick film (PTF) devices which exhibit a decrease in resistance with an increase in the force applied to an active surface. More particularly, the resistance of the FSRs drop below a predetermined value when a certain force is applied. While force sensing resistors (FSRs) are utilized in the illustrated embodiment, it should be appreciated that other sensors for detecting the presence of a patient supported on the head section 4390 and the seat section 4392 of the mattress 4014 may be substituted therefore. Illustratively, the FSRs are available from Interlink Electronics of Camarillo, Calif. as part number 408.
Patient Weight Determination
As noted above, four load cells 220, 222, 224, and 226 are attached to the four corners of the weigh frame 36 of the bed 10′. The summation of these four load cells 220, 222, 224, and 226, when their output is converted to a weight, provide the total weight supported by the weigh frame 36. The weight of weigh frame 36 and anything supported by weigh frame 36, such as deck 26′, mattress 4014, any other bed components supported on weigh frame 36, and a patient, is transmitted to load cells 220, 222, 224, 226. This weight deflects or otherwise changes a characteristic of load cells 220, 222, 224, 226 that is detected to determine the total weight supported thereby. By subtracting a known weight of weigh frame 36, deck 26′, mattress 4014 and any other bed components supported on weigh frame 36, the weight of the patient positioned on patient support 10 can be determined. Additional description of load cells and methods for determining a patient's weight, position in the bed, and other indications provided by load cells is provided in U.S. patent application Ser. No. 09/669,707, filed Sep. 26, 2000, titled Load Cell Apparatus, to Mobley et al., and PCT international Patent Application No. PCT/US/08189, titled Hospital Bed Control Apparatus, to Dixon et al., the disclosures of which are expressly incorporated by reference herein. In one illustrative embodiment, the load cells are available from HBM, Inc. of Marlborough, Mass. According to alternative embodiments of the present disclosure, other configurations and methods of using load cells or other devices to determine a patient's weight or other information related to the patient known to those of ordinary skill in the art are provided.
Information from the scale controller 5012 is transmitted to the air controller 3004 through the controller area network (CAN) 510. The information is parsed into seven data sets (four load cells 220, 222, 224, 226, three FSRs 5004, 5008, 5010) with each transmission being spaced apart by approximately 100 milliseconds. Along with each data set is an error byte that contains diagnostic information pertaining to the load cells 220, 222, 224, 226.
Referring further to the flow chart of
Process 5020 begins at block 5022 with the initialization of all variables. As detailed below, the variable Load_Beam_Offset is set to equal a value from the most recent operation of the controller 3004. At decision block 5024, the controller 3004 queries whether it is ready for processing data. More particularly, the controller 3004 determines whether a complete set of data from the FSRs 5002, 5004, 5006, 5008, 5010 and load cells 220, 222, 224, 226 is available for utilization. As noted above, a complete set of updated data is received every 700 milliseconds. More particularly, seven packages of data are received from the scale controller 5012 at the rate of one package every 100 milliseconds. Two additional packages of information are received from the first and third head section FSRs 5002 and 5006, one every 350 milliseconds. If a complete new set of data from the FSRs 5002, 5004, 5006, 5008, 5010 and the load cells 220, 222, 224, 226 is not available, then the process returns at block 5026 to start block 5022. If decision block 5024 is answered in the affirmative, then the process continues to decision block 5028 where the controller 3004 processes data from the FSRs 5002 and 5006 and the scale controller 5012. More particularly, the processor 3004 determines the value of the variable Load_Beam_Total to be equal to the sum of the four inputs from the load cells 220, 222, 224, 226. The controller 3004 further analyzes the values from the FSRs 5002, 5004, 5006, 5008, 5010. If any of the FSRs 5002, 5004, 5006, 5008, 5010 have a resistance indicating the presence of a patient, then the controller 3004 sets the flag Patient_Present to TRUE.
The process 5020 next continues to block 5030 where the controller 3004 queries whether the data from both the FSRs 5002, 5004, 5006, 5008, 5010 and the scale controller 5012 are stable. More particularly, the controller 3004 queries whether the patient has been consistently detected as being present or not present for a minimum predetermined amount of time. In the illustrative embodiment, if (1) the patient has been detected for at least approximately 3.5 seconds as indicated by the flag Patient_Present being set to TRUE, or (2) the patient has not been detected for at least approximately 3.5 seconds as indicated by the flag Patient_Present being set to FALSE, then the FSR data is considered stable. Similarly, if the Load_Beam_Total variable has not changed by more than five pounds for at least approximately 3.5 seconds, then the scale data is considered stable. If the controller 3004 determines that the data is not stable at block 5030, then the process proceeds to block 5026. If the data is considered stable, then the process 5020 then continues to process block 5032.
In one illustrative embodiment, the FSRs 5002, 5004, 5006, 5008, 5010 are grouped into two sets, with the first group comprising all of the FSRs 5002, 5004, 5006, 5008, 5010, and the second group comprising the head section FSRs 5002, 5004, 5006. In order for the FSR data to be considered stable by the controller 3004, then (1) all of the FSRs in either the first group or the second group must not detect a patient for at least approximately 3.5 seconds, or (2) any of the FSRs in either the first group or the second group must detect a patient for at least approximately 3.5 seconds.
At block 5032, the controller 3004 recalculates the variable Load_Beam_Adj. More particularly, the controller sets Load_Beam_Adj to be equal to the variable Load_Beam_Total minus the variable Load_Beam_Offset. As mentioned above, the variable Load_Beam_Offset is saved from the prior operation of the controller 3004. The Load_Beam_Offset is defined as the weight measured by the scale controller 5012 prior to a patient getting on the bed 10′ and being supported by the weigh frame 36, and following the addition of the mattress 4014, footboard 18 and any other equipment supported by the weigh frame 36. The Load_Beam_Offset takes into consideration the factory calibration, typically the zeroing or initializing of the weight measured by the scale controller 5012 without the mattress 4014, footboard 18, or other equipment supported by the weigh frame 36. In summary, the Load_Beam_Offset is equal to a load applied to the weigh frame 36 in excess of that when the bed 10′ is calibrated during manufacture and without the patient supported by the weigh frame 36.
The process 5020 then continues to decision block 5034, where the controller 3004 queries whether the conditions have been satisfied to “zero” the bed 10′. In other words, the controller 3004 determines whether conditions are satisfied for recalculating the offset (Load_Beam_Offset) for the bed 10′. More particularly, the controller 3004 queries whether (1) the variable Load_Beam_Adj is less than zero or (2) the variable Load_Beam_Adj is less than a maximum detected offset value and the flag Patient_Present is FALSE. The first instance, where the Load_Beam_Adj is negative, could occur where equipment has been removed from the weigh frame 36 since the last operation of the controller 3004. As such, the value of the variable Load_Beam_Total could be less than the value of the variable Load_Beam_Offset as saved from the prior operation. The second instance, where the variable Load_Beam_Adj is less than a maximum detected offset value and the Patient_Present flag is FALSE could occur where equipment has been added to the bed 4010 and is supported by the weigh frame 36 since the last operation of the controller 3004, and no patient is detected as being supported by the deck 26′. If at block 5034, the controller 3004 determines that the conditions are right to zero the bed 10′ then the process 5020 continues to block 5036. Illustratively, the maximum detected offset value is defined as approximately 50 pounds.
At process block 5036, the controller 3004 calculates a new offset and clears the flag New_Offset_Pending. More particularly, the controller 3004 equates the variable Load_Beam_Offset to the variable Load_Beam_Total, and sets the New_Offset_Pending flag to FALSE. As such, the controller 3004 resets the Load_Beam_Offset to be equal to the value of the Load_Beam_Total. The process then continues at block 5038 where the controller 3004 recalculates the variable Load_Beam_Adj. More particularly, the controller 3004 equates the variable Load_Beam_Adj to be equal to the variable Load_Beam_Total minus the variable Load_Beam_Offset.
The process 5020 then continues to block 5040 where the controller 3004 applies output filter and weight limits. More particularly, the controller 3004 updates the variable Patient_Weight only if (1) the variable Load_Beam_Adj is greater than the variable Patient_Weight plus a minimum patient weight change or (2) the variable Load_Beam_Adj is less than the variable Patient_Weight minus the minimum patient weight change. Illustratively, the minimum patient weight change is defined as approximately ten pounds. If the variable Load_Beam_Adj is greater than a maximum patient weight, then the controller 3004 sets Patient_Weight to be equal to a default maximum patient weight. Illustratively, the maximum patient weight is defined as approximately 350 pounds, while the default maximum patient weight is defined as approximately 400 pounds. If the variable Load_Beam_Adj is less than a minimum patient weight, then the variable Patient_Weight is set to be equal to a default minimum patient weight. Illustratively, the minimum patient weight and the default minimum patient weight are both set to be equal to approximately 65 pounds. The process 5020 then continues to return block 5026 and subsequently to decision block 5024.
Referring again to decision block 5034 of
At block 5044, the controller 3004 stores the pending offset and sets the New_Offset_Pending flag. More particularly, the variable Pending_Offset is set equal to the Load_Beam_Total and the flag New_Offset_Pending is set to TRUE. The process 5020 then continues to process block 5040 and continues to operate as detailed herein as if a patient is present on the deck 26′.
Referring again to decision block 5042, if there is no possible large offset to record, then the process continues to decision block 5046 (
At decision block 5048 of
At block 5052, the controller 3004 updates the offset with the pending offset. More particularly, the controller 3004 sets a variable Load_Beam_Offset to be equal to the variable Pending_Offset. The situation could occur where a patient is now present on the deck 26′ and the prior pending offset value was equipment supported by the weigh frame 36. The process then continues to process block 5054. At process block 5054, the controller 3004 recalculates the variable Load_Beam_Adj. Again, Load_Beam_Adj is equal to the variable Load_Beam_Total minus the variable Load_Beam_Offset. The process 5020 then continues to block 5050 where the New_Offset_Pending flag is cleared or set to FALSE. The process 5020 then continues to process block 5040 (
Once the value of the variable Patient_Weight has been determined, for example by the above detailed process 5020, the process 4730 of
At step 4736, process 4730 determines the desired inflation pressure for the air zone(s) 4254, 4358, 4360, 4390, and 4392 being monitored based on the patient weight. In the illustrated embodiment, microcontroller 3004 obtains the desired pressure for the air zone(s) 4254, 4358, 4360, 4390, and 4392 from data, such as one or more look-up tables, stored in memory 3010. The desired pressure may be a discrete value, a range of permissible values, or calculated from an equation or algorithm as a function of patient weight. Also, the desired pressure may be different for each air zone 4254, 4358, 4360, 4390, and 4392. Further, various other factors, including environmental factors such as temperature and/or altitude, may affect the desired pressure values and be reflected in data in the look-up table.
As detailed in Table 7, in the illustrated embodiment the appropriate pressures for the seat section 4392, in pressure relief and turn assist modes of operation, also depends on the elevation of head section 38′, as represented by the variable Head_Elevation. Thus, for seat section 4392, the appropriate pressure is determined by reference to both patient weight and head angle. However, adjusting the pressure of seat section 4392 based on only one of these criteria, regardless of the mode of operation, is also within the scope of the present invention.
Mattress Seat Section Boost
As may be appreciated, when the head section 38′ is elevated, a portion of the patient's weight naturally shifts from being supported by the head section 4390 of the mattress 4014 to the seat section 4392 of the mattress 4014. To compensate for this weight shift, the inflation pressure of the seat section 4392 is adjusted in response to changes in the position of the head section 4038. In the illustrated embodiment, and as shown in Table 7, the pressure in the seat section 4392 is dependent upon the elevation of the head section 4390 only during the pressure relief and turn assist modes of operation. In other words, the pressure in the seat section 4392 is not varied in response to changes in elevation of the head section 4390 in the max inflate, CPR, or post-turn assist modes of operation.
Illustratively, the position of head section 38′, or head angle, is determined by position detector 606. In the illustrated embodiment, a potentiometer reading corresponding to the head angle is determined by logic module 512 and reported to dynamic surface module 518 via network 510 for use in process 4730. Additional details regarding operation of the potentiometer for determining head angle is detailed above.
In determining the pressure for the seat section 4392 at block 4738, the microcontroller 3004 compares the angle as determined by the position detector 606 to data stored in memory 3010, such as those values contained in Table 10 below. The ranges of values for adjacent angular regions indicating a change in head elevation in Table 10 overlap, in order to take into consideration hysteresis (dependence of the state of a system on its previous history, generally in the form of a lagging of a physical effect behind its cause) in the head angle evaluation.
For example, head section 38′ will be considered to have moved from region 0 (zero) to region 1 (one) if the position detector 606 measures a head angle of between approximately 30 and 40 degrees. However, once head section 38′ is in region 1 (one), it will not be considered to have moved back to region 0 (zero) unless the position detector 606 measures a head angle below region 1 (one), e.g., approximately 26 degrees or less, is received. Further, as indicated in Table 10, the variable Head_Elevation for use in pressure calculations is set to a predetermined value for each region of measured head elevation. For example, in region 1 (one), the variable Head_Elevation is set to 40 degrees, while in region 2 (two), the variable Head_Elevation is set to 50 degrees.
If a change in position occurs in the downward direction, from one angular region to a different angular region, i.e., head section 4038 is lowered from region 2 (two) to region 1 (one) in Table 10, then at step 4738 the desired pressure of seat section 4392 is decreased according to the weight of the patient, represented by Patient_Weight, and the current head angle set as Head_Elevation. The desired pressure range (Pressure_Seat range) is determined by reference to a look-up table stored in memory 3010. Table 7 is an example of such a table.
If a change in position occurs in the upward direction, from one angular region to a different angular region, i.e., head section 38′ is elevated from region 0 (zero) to region 1 (one) in Table 10, then at step 4738 the desired pressure of seat section 4392 is increased according to the weight of the patient, represented by the variable Patient_Weight, and the current head angle set as Head_Elevation. In addition, a “seat boost” may be applied to seat section, as detailed below, meaning that seat section 4392 is initially over-inflated for a brief period of time to compensate for the above-mentioned weight shift.
At step 4740, microcontroller 3004 measures the current pressure as described above and determines whether the current pressure is less than, equal to, or greater than the desired pressure determined as described above. At block 4742, the microcontroller 3004 queries whether the actual pressure is greater than the desired pressure determined at step 4738 above. If so, then at step 4744, the zone is deflated to the desired pressure. At block 4746, the microcontroller 3004 queries whether the current pressure is less than the desired pressure. If so, the microcontroller 3004 commands power supply 3006 to activate pump 4064 to inflate bladders 2304 to the desired pressure as described above, at step 4738.
After the pressure is decreased or increased at blocks 4744 and 4748, respectively, the process 4730 continues to block 4750. At block 4750, the controller 3004 determines if the seat section 4392 requires a pressure “boost.”
In addition to other functions discussed above and elsewhere in this disclosure, pressure control system 3000 may perform additional processes 4800, 4900 for increasing or “boosting” the inflation of seat section according to the elevation of head section 4038. One embodiment of such method is shown in
As noted above, when head section 38′ is elevated, a portion of the patient's weight naturally shifts from head section 4390 of the mattress 4014 to seat section 4392 of the mattress 4014. A similar weight shift occurs when the patient sits up in the bed 10′ such that the patient's weight is supported mostly or entirely by the seat section 4392. To anticipate this weight shift and prevent “bottoming out,” the inflation pressure of seat section 4392 is boosted in response to changes in the position of head section 38′. Table 11 shows boost pressure ranges for seat section depending on ranges of patient weight.
Process 4800 begins at block 4802 with the determination of the elevation of the head section (Head_Elevation), in the manner detailed above. At decision step 4804, process 4800 evaluates the input received from logic module 512 and determines whether head section 38′ has experienced at least a 3 degree increase in position by comparing the current head angle to the previous head angle. If the head angle has increased by at least approximately 3 degrees, the process 4800 continues to step 4806. If the head section 38′ has not been elevated by at least approximately 3 degrees, then process 4800 returns to step 4802. It is understood that 3 degrees is an exemplary value and that a change in the head angle may be indicated by a greater or lesser value as appropriate. Of course, during this time, pressure control system 3000 continues to periodically measure the pressure of the seat section 4392 to make sure that it is within the desired ranges.
It should be appreciated that if a change in position occurs in the downward direction, i.e., head section 38′ is lowered, then at step 4804 no pressure increase in the seat section 4392 is triggered. If a change in position occurs in the upward direction by at least 3 degrees, i.e., head section 38′ is elevated, then at step 4806 the inflation pressure of seat section is increased. In other words, a “seat boost” is applied to seat section 4392, meaning that seat section 4392 is initially over-inflated for a brief period of time to compensate for the above-mentioned weight shift. At block 4808, a timing decision is executed by the controller 3004 to determine if the pressure boost exceeds a predetermined time, illustratively between 1 second and 30 seconds. In one illustrative embodiment, the predetermined time is set at approximately 15 seconds. If the pressure boost does not exceed the predetermined time, then the pressure boost continues at block 4806. If the predetermined time has passed, then the process 4800 continues to block 4810, where the pressure boost is terminated.
Examples of the initial “seat boost” pressures are shown in Table 11. After the seat boost period expires, process 4800 adjusts the pressure of seat section 4392 to the desired level based on patient weight and head angle, as determined by the look-up Table 7 as detailed above.
Referring now to
At decision block 4906, the controller 3004 queries whether the patient weight (Patient_Weight) is greater than a predetermined amount. In the illustrative embodiment, the predetermined amount is approximately 100 pounds. If the value of Patient_Weight is not greater than approximately 100 pounds, then the process returns to block 4902. In other words, the no pressure boost will occur in the seat section 4392 if the determined patient weight is not greater than approximately 100 pounds. If the value of Patient_Weight is greater than approximately 100 pounds, then the process 4900 continues to block 4908 where the inflation pressure of seat section 4392 is increased. In other words, a “seat boost” is applied to seat section 4392, meaning that seat section 4392 is initially over-inflated for a brief period of time to compensate for the above-mentioned weight shift. The seat boost continues indefinitely as long as the decision blocks 4904 and 4906 are answered affirmatively. Of course, during this time, pressure control system 3000 continues to periodically measure the pressure of the seat section 4392 to make sure that it is within the desired ranges.
Examples of the initial “seat boost” pressures are shown in Table 11. After the seat boost period expires, process 4900 adjusts the pressure of seat section 4392 to the desired level based on patient weight and head angle, as determined by the look-up Table 7 as detailed above.
Patent Turn Assist
In addition to other functions discussed above and elsewhere in this disclosure, pressure control system 3000 of dynamic surface module 518 controls the operation of turn assist bladder assembly 4220 during the turn assist mode of operation. Turn assist bladders 4358, 4360 are configured to be selectively inflated to assist a caregiver in turning or rotating a patient, e.g., for therapy or treatment reasons. One embodiment of a process 3032 for controlling operation of turn assist bladders 4358, 4360 is shown in
At step 3034 of
At decision step 3036, prior to initiating the turn assist function, process 3032 checks to make sure that the siderails 4020, 4022 located on the side of patient support 10′ that the patient is being turned toward are in the up position, based on signals provided by siderail position detectors 60. If one or more of siderails 4020, 4022 on the side of patient support 10′ toward which the patient is being turned is not in the up position, an error signal is generated at step 3038 and process 3032 ends. In the illustrated embodiment, an audible or visual signal is generated for a brief period or until the siderail or siderails 4020, 4022 are brought to the up position. Thus, in the illustrated embodiment, the siderails 4020, 4022 toward which the patient is being turned must be in the up position in order for the turn assist process to initiate. It is possible, however, that in other embodiments, a caregiver or operator may override this restriction, or that this restriction may be made optional, for example, depending on the circumstances of a particular patient.
At step 3040, process 3032 checks to see if the angle of head section 38′ (Head_Elevation) is less than, equal to, or greater than a predetermined maximum angle. In the illustrated embodiment, the maximum head angle is about 25 degrees. In one embodiment, signals are provided by the position detector 606 directly to the dynamic surface module 518, which determines the head angle. Alternatively, the head angle determination is made by logic module 512 which reports the head angle to dynamic surface module 518 for use in process 3032, via CAN network 510. If the head angle is less than or equal to 25 degrees, then the turn assist process continues to step 3044. However, if the head angle is greater than about 25 degrees, an error signal is generated at step 3042, and the turn assist process is not permitted to continue.
At step 3044, the weight of the patient (Patient_Weight) being supported by patient support 10′ is determined as described above so that a desired pressure based on patient weight is applied to the selected turn assist bladder 4358, 4360.
At step 3046, if first turn assist button 1624 is activated, first turn assist bladder 4358 inflates to rotate a person in patient support 10′ upwardly in a counter-clockwise from the perspective of a person standing behind head section 38′. If second turn assist button 1626 is activated, second turn assist bladder 4360 inflates to rotate the person upwardly in the opposite direction as rotated in response to activation of first turn assist button 1624. Inflation of the selected turn assist bladder 4358, 4360 raises one side of the patient to a predetermined angle. In the illustrated embodiment, the selected turn assist bladder 4358, 4360 inflates to rotate the patient onto his or her side at about a 20 degree angle with respect to mattress 4014, in approximately 20-50 seconds, depending on the weight or size of the patient. It is understood that the predetermined angle and speed of inflation may be changed or modified as needed based on a variety of factors, including the purpose for rotating the patient.
A timer is set at step 3048 when the selected turn assist bladder 4358, 4360 is inflated. The selected turn assist bladder 4358, 4360 remains inflated for a predetermined period of time and is then automatically “reset” or deflated. The predetermined time is empirically determined by the needs and desires of the patient and caregiver in an operating environment and illustratively is a time within a range of approximately 5 seconds to approximately 5 minutes. In the illustrative embodiment, the duration of turn assist inflation is about 10 seconds. At step 3050 the timer counts out this wait period. After the wait period is complete (e.g., after 10 seconds), an audible or visual signal is generated to indicate to the patient and caregiver that the selected turn assist bladder 4358, 4360 is about to enter a “post-turn assist” mode or phase.
In the post-turn assist mode, process 3032 begins deflating the selected turn assist bladder 4358, 4360 at step 3052. In the illustrated embodiment, deflation is expedited by quickly “hyperinflating” bladders of the head and seat sections 4390 and 4392 to a firm, “post-turn assist” inflation pressure (see, e.g., Table 6 and Table 7). Inflation of head and seat sections 4390 and 4392 exerts pressure on turn assist bladders 4358, 4360 causing turn assist bladders 4358, 4360 to expel air more rapidly. Alternatively, a vacuum mechanism may be coupled to turn assist bladders 4358, 4360 to accelerate deflation.
Monitor activity step 3060 is a step that is periodically executed during the turn assist operation. This process detects whether a patient or caregiver attempts to utilize other bed features while the turn assist is in operation. Additional details regarding the operation of the dynamic surface module are provided above.
CPR Configuration
Patient support 10′ may be placed in the preferred CPR configuration by providing an indication to control system 44 which in turn controls actuators 48c, 48d, 48e to place head, seat, and leg sections in a generally linear relationship, controls pump 4064, to inflate upper bladder assembly 4222 to the desired pressures, and controls deck support 24 to lower a head end relative to a foot end. In the illustrative embodiment, the control system 44 inflates the bladder assembly 4394 of the head section 4390 to its desired CPR pressure before it inflates the bladder assembly 4396 of the seat section 4392 to its desired CPR pressure. As such, the head section 4390 reaches its desired firmness prior to the seat section 4392. This functionality is desirable since CPR procedures typically require pressure to be applied to the upper torso or chest of a patient.
Mattress Air Pump
Pump 64 is configured to provide pressurized air to manifold 62 and the pneumatic devices of mattresses 14, 4014. As shown in the illustrative embodiment of
Many pump units, such as pump unit 5450, create noise and vibration during operation. Several of the components of pump 64 are configured to reduce the transmission of the noise and vibration generated by pump unit 5450.
As shown in FIGS. 113 and 162-164, support bracket 5440 includes a pair of saddle-shaped portions 5454 that hook or loop over strut 211 and four arms 5456 that extend down from saddle-shaped portions 5454. U-shaped rubber or elastic members 5458 (only one is shown in
Saddle-shape portions 5454 includes apertures 5460 sized to receive fasteners 5462 that couple bracket 5440 to strut 211. Similarly, strut 211 includes apertures 5464 sized to receive fasteners 5462. However apertures 5464 are large enough that strut 211 does not come into contact with fasteners 5462 to avoid a direct, rigid coupling between bracket 5440 and strut 211 (
Pump cover support bracket 5444 includes four arms 5466 that include fastener-receiving notches 5468. Rubber or elastic grommets 5470 (only one is shown in
Grommets 5470 are positioned in notches 5468 so that head portions 5472 overlaps portions of arms 5466 and portions of arms 5466 are positioned in grooves 5474. As shown in
Pump cover 5446 is coupled to pump cover support bracket 5444 by a plurality of fasteners 5478. A foam gasket 5480 is compressed between pump cover bracket 5444 and pump cover 5446 to reduce the transmission of noise and vibration. Similarly, a foam lining 5482 is provided on the interior surfaces of pump cover 5446. According to an alternative embodiment of the present disclosure a foam lining is also provided on the underside of pump cover support bracket 5444.
Pump unit support bracket 5448 is welded or otherwise rigidly coupled to the underside of pump cover support bracket 5444 so that pump unit support bracket 5448 is suspended within an interior region 5484 defined by foam lining 5482. Preferably, no portion of pump unit support bracket 5448 or pump unit 5450 touch foam lining 5482.
Pump unit 5450 is supported on pump unit support bracket 5448 by at least four resilient feet 5486 (only one such foot is shown in
An alternative embodiment resilient foot 5510 is shown in
As shown in
If liquid is sprayed into or otherwise enters pan 5522, it will drain out of slits 5532. Furthermore, because inlet 5536 is facing and relative close to bottom wall 5530, liquid cannot be sprayed into inlet 5536 through slits 5532 from outside of pan 5522 because the path between slits 5532 and inlet 5536 is non-linear. Thus, pan 5522 blocks any direct spray path into inlet 5536 so that it is difficult for liquid to inter filter and muffler unit 5452.
Preferably, filter and muffler unit 5452 is configured to filter out many impurities in the air so that these impurities are not introduced to pump unit 5450, manifold 62, or mattress 14. With further reference to
During operation, pump unit 5450 generates noise that can travel through tube 5540. Filter and muffler unit 5452 is configured to attenuate this noise so that it is not introduced into the patient environment.
Another tube 5548 is coupled to an outlet fitting 5550 of pump unit 5450 that supplies pressurized air to manifold 62. Tube 5548 extends through another tube-receiving notch 5552 in pump cover support bracket 5444. Tube 5548 extends along strut 211 of weight frame 36 as shown in
A further illustrative embodiment mattress air pump 4064, as shown in
As shown in
Tab sets 5659 includes apertures 5660 sized to receive fasteners 5662 that couple bracket 5654 to strut 211. Similarly, strut 211 includes apertures 5664 sized to receive steel sleeve 5661. When positioned in apertures 5664, portions of steel sleeves 5661 extend below the bottom of strut 211 as shown in
Steel sleeves 5663 (only one is shown in
Pump cover support bracket 5644 includes four arms 5666 that include fastener-receiving notches 5668. Resilient bushings 5670 and provided that are received in each of notches 5668. Bushings 5670 are positioned in notches 5668 so that upper head portions 5671 of bushings 5670 overlap portions of arms 5666 and a shank portions 5673 are positioned in notches 5668 as shown in
Bushings 5670 and wasters 5675 are preferable made of thermoset, polyether-based, polyurethane material sold under the name SORBOTHANE by Sorbothane, Inc. of Kent, Ohio. SORBOTHANE-brand material is a visco-elastic material. According to alternative embodiments, other resilient or elastic materials such as rubber are used for the bushings and washers.
Pump cover 5646 is coupled to pump cover support bracket 5644 by a plurality of fasteners 5678. As shown in
Pump unit support bracket 5648 is welded or otherwise rigidly coupled to the underside of pump cover support bracket 5644 so that pump unit support bracket 5648 is suspended within an interior region 5684 defined by foam lining 5680. As shown in phantom in
Pump unit 5650 is supported on pump unit support bracket 5648 by at least four resilient feet 5686 (only two such feet are shown in
As shown in
As shown in
If liquid is sprayed into or otherwise enters cover 5646, it will drain out of aperture 5728. Furthermore, because end 5713 of tube 5712 is facing and relative close to wall 5722 of cover 5718, liquid cannot be directly sprayed into inlet end 5713 of tube 5712 through aperture 5728 from outside of pan cover 5718 because the path between aperture 5714 and aperture 5728 is non-linear. Thus, cover 5718 blocks any direct spray path into end 5713 of tube 5712 so that it is difficult for liquid to enter filter and muffler unit 4652.
Interior components (not shown) of filter and muffler unit 5652 filter out many impurities in the air so that these impurities are not introduced to pump unit 5650, manifold 62, or mattress 4014. Air from filter and muffler unit 5652 is communicated to pump unit 5650 through interior region 5684 from an outlet 5642 of filter and muffler unit 5652. During operation of pump unit 5650, air from interior region 5684 is drawn into an inlet 5730 of pump unit 5650 that is spaced apart from filter and muffler unit 5652. This creates negative pressure within interior region 5684. Because of the pressure difference between interior region 5684 and the environment outside of pump 5660, air is drawn into interior region 5684 through filter and muffler unit 5652. This air enters interior region 5684 defined by foam lining 5680 before entering into inlet 5730 of pump unit 5650. Thus, foam lining 5680 defines a portion of the path of travel of the air through pump unit 5650.
Because inlet 5730 of pump unit 5650 is not directly coupled to filter and muffler unit 5652, noise exiting pump unit 5650 is not directly transmitted to filter and muffler unit 5652. This noise exits pump unit 5650 into interior region 5684 and is attenuated by foam lining 5680. Any noise that enters outlet 5642 of filter and muffler unit 5652 from interior region 5684 is attenuated further by filter and muffler unit 5652. Furthermore, because pump unit 5650 is not directly coupled to filter and muffler unit 5652, most vibration generated by pump unit 5650 is not transmitted outside of pump 4064 by tube 5712.
Another tube 5732 is coupled to an outlet fitting 5734 of pump unit 5650 that supplies pressurized air to manifold 62. Tube 5732 extends through an aperture 5736 in pump cover support bracket 5644. A grommet 5738 is positioned in aperture 5736 to provide a seal between tube 5732 and pump cover support bracket 5644. As shown in
Although the invention has been described in detail with reference to certain preferred embodiments, variations and modifications exist within the spirit and scope of the invention as described and defined in the following claims.
This application is a continuation of U.S. application Ser. No. 13/014,140, filed Jan. 26, 2011 which is a continuation of U.S. application Ser. No. 12/507,152, filed Jul. 22, 2009 which is a continuation of U.S. application Ser. No. 12/137,619, filed Jun. 12, 2008, now U.S. Pat. No. 7,610,637, which is a continuation of U.S. application Ser. No. 11/257,438, filed Oct. 24, 2005, now U.S. Pat. No. 7,454,805, which is a continuation of U.S. application Ser. No. 10/731,720, filed Dec. 9, 2003, now U.S. Pat. No. 6,957,461, which is (1) a divisional and a continuation-in-part of U.S. application Ser. No. 09/750,741, filed Dec. 29, 2000, now U.S. Pat. No. 6,658,680, titled Hospital Bed, which claims benefit of U.S. Provisional Application No. 60/173,428, filed Dec. 29, 1999, titled Hospital Bed; (2) a continuation-in-part of U.S. application Ser. No. 09/751,031, filed Dec. 29, 2000, now U.S. Pat. No. 6,691,346, titled Foot Controls for a Bed, which claims benefit of U.S. Provisional Application No. 60/173,428, filed Dec. 29, 1999, titled Hospital Bed; (3) a continuation-in-part of U.S. application Ser. No. 10/648,053, filed Aug. 26, 2003, now U.S. Pat. No. 6,880,189, titled Patient Support, which is a divisional of U.S. application Ser. No. 09/750,859, filed Dec. 29, 2000, titled Mattress Having a Retractable Foot Section, now U.S. Pat. No. 6,611,979, which claims benefit of U.S. Provisional Application No. 60/173,428, filed Dec. 29, 1999, titled Hospital Bed; and (4) a continuation-in-part of U.S. application Ser. No. 10/657,696, filed Sep. 8, 2003, now U.S. Pat. No. 7,296,312, which claims the benefit of U.S. Provisional Patent Application No. 60/408,698, filed Sep. 6, 2002, titled Hospital Bed; U.S. Provisional Patent Application No. 60/409,748, filed Sep. 11, 2002, titled Bed Siderail; U.S. Provisional Patent Application No. 60/489,171, filed Jul. 22, 2003, titled Hospital Bed; and U.S. Provisional Patent Application No. 60/490,467, filed Jul. 28, 2003, titled Hospital Bed; the disclosures of all of the foregoing being hereby expressly incorporated by reference herein.
Number | Name | Date | Kind |
---|---|---|---|
585834 | Ruth | Jul 1897 | A |
595734 | Rand et al. | Dec 1897 | A |
598054 | Meany | Jan 1898 | A |
609819 | J-Lawrence | Aug 1898 | A |
1017153 | Kampe | Feb 1912 | A |
1043370 | Stubbs | Nov 1912 | A |
1078077 | Arnold | Nov 1913 | A |
1261040 | Lanes | Apr 1918 | A |
1398203 | Schmidt | Nov 1921 | A |
1440783 | Kiley | Jan 1923 | A |
2120732 | Comper et al. | Jun 1938 | A |
2168649 | Johnson | Aug 1939 | A |
2245909 | Enfiajian | Jun 1941 | A |
2281209 | Smith | Apr 1942 | A |
2285474 | Urie | Jun 1942 | A |
2379080 | Hillenbrand | Jun 1945 | A |
2452366 | Frenad | Oct 1948 | A |
2477400 | Beem et al. | Jul 1949 | A |
2500742 | Taylor | Mar 1950 | A |
2517466 | Cox | Aug 1950 | A |
2527111 | Widrich et al. | Oct 1950 | A |
2556591 | Loxley | Jun 1951 | A |
2564083 | Stachert | Aug 1951 | A |
2587094 | Berg et al. | Feb 1952 | A |
2605151 | Shampaine | Jul 1952 | A |
2605481 | Burkhart | Aug 1952 | A |
2631300 | Murray | Mar 1953 | A |
2633578 | Deves et al. | Apr 1953 | A |
2651785 | Berner | Sep 1953 | A |
2684488 | Snyder | Jul 1954 | A |
2687536 | Miller | Aug 1954 | A |
2719769 | Murphy | Oct 1955 | A |
2722017 | Burst et al. | Nov 1955 | A |
2734104 | Gollhofer | Feb 1956 | A |
2766463 | Bendersky | Oct 1956 | A |
2799545 | Berne | Jul 1957 | A |
2833587 | Saunders | May 1958 | A |
2869614 | Wamsky | Jan 1959 | A |
3003160 | Goodman | Oct 1961 | A |
3010121 | Breach | Nov 1961 | A |
3012253 | Reichert | Dec 1961 | A |
3036314 | Wetzler | May 1962 | A |
3053568 | Miller | Sep 1962 | A |
3099440 | Burzlaff | Jul 1963 | A |
3112500 | MacDonald | Dec 1963 | A |
3138805 | Piazza | Jun 1964 | A |
3174161 | Black | Mar 1965 | A |
3174722 | Alm | Mar 1965 | A |
3184765 | Katz | May 1965 | A |
3195151 | Boyer | Jul 1965 | A |
3200416 | Warrick | Aug 1965 | A |
3210779 | Herbold | Oct 1965 | A |
3217340 | Durr | Nov 1965 | A |
3220021 | Nelson | Nov 1965 | A |
3220022 | Nelson | Nov 1965 | A |
3233255 | Propst | Feb 1966 | A |
3237212 | Hillenbrand et al. | Mar 1966 | A |
3239853 | MacDonald | Mar 1966 | A |
3277501 | Frisz et al. | Oct 1966 | A |
3278952 | Holm | Oct 1966 | A |
3308485 | Nesbit-Evans | Mar 1967 | A |
3309717 | Black | Mar 1967 | A |
3317931 | Benoit et al. | May 1967 | A |
3373453 | Goodman | Mar 1968 | A |
3380085 | Ferneau et al. | Apr 1968 | A |
3393004 | Williams | Jul 1968 | A |
3406772 | Ahrent et al. | Oct 1968 | A |
3436769 | Burst | Apr 1969 | A |
3456269 | Goodman | Jul 1969 | A |
3462772 | Morrison | Aug 1969 | A |
3465373 | Wilson | Sep 1969 | A |
3472183 | Goodman | Oct 1969 | A |
3506989 | Ross et al. | Apr 1970 | A |
3526008 | Pruim | Sep 1970 | A |
3585659 | Burst et al. | Jun 1971 | A |
3593350 | Knight et al. | Jul 1971 | A |
3598947 | Osborn | Aug 1971 | A |
3599199 | Bunting | Aug 1971 | A |
3608102 | Goodman | Sep 1971 | A |
3640566 | Hodge | Feb 1972 | A |
3644945 | Goodman et al. | Feb 1972 | A |
3663772 | Grabel | May 1972 | A |
3665528 | Kjellberg et al. | May 1972 | A |
3686696 | Lnigan | Aug 1972 | A |
3688319 | Gulliver | Sep 1972 | A |
3724003 | Ellwanger et al. | Apr 1973 | A |
3733623 | Croxton | May 1973 | A |
3767859 | Doering | Oct 1973 | A |
3781843 | Harrison | Dec 1973 | A |
3814414 | Chapa | Jun 1974 | A |
3821821 | Burst et al. | Jul 1974 | A |
3822425 | Scale | Jul 1974 | A |
3845947 | Lee | Nov 1974 | A |
3875598 | Foster | Apr 1975 | A |
3893197 | Ricke | Jul 1975 | A |
3897973 | Long et al. | Aug 1975 | A |
3902204 | Lee | Sep 1975 | A |
3905591 | Schorr et al. | Sep 1975 | A |
3916461 | Kerstholt | Nov 1975 | A |
3925762 | Heitlinger | Dec 1975 | A |
3932903 | Adams et al. | Jan 1976 | A |
3958283 | Adams et al. | May 1976 | A |
3977664 | Mitchell et al. | Aug 1976 | A |
3991414 | Moran | Nov 1976 | A |
3993051 | Maruyama | Nov 1976 | A |
4016613 | Benoit et al. | Apr 1977 | A |
4025972 | Adams et al. | May 1977 | A |
4038709 | Kerwit | Aug 1977 | A |
4062075 | Stern et al. | Dec 1977 | A |
4067005 | Levy | Jan 1978 | A |
4071222 | Wright | Jan 1978 | A |
4078269 | Weipert | Mar 1978 | A |
4097939 | Peck et al. | Jul 1978 | A |
4103376 | Benoit et al. | Aug 1978 | A |
4110856 | Benoit et al. | Sep 1978 | A |
4127906 | Zur | Dec 1978 | A |
4139917 | Fenwick | Feb 1979 | A |
4150269 | Henkel | Apr 1979 | A |
4168099 | Jacobs et al. | Sep 1979 | A |
4175263 | Triplett | Nov 1979 | A |
4179692 | Vance | Dec 1979 | A |
4183015 | Drew et al. | Jan 1980 | A |
4183109 | Howell | Jan 1980 | A |
4193149 | Welch | Mar 1980 | A |
4195829 | Reser | Apr 1980 | A |
4196425 | Williams, Jr. et al. | Apr 1980 | A |
4205665 | Burton | Jun 1980 | A |
4216462 | McGrath | Aug 1980 | A |
4218788 | Steckmesser | Aug 1980 | A |
4225989 | Corbett et al. | Oct 1980 | A |
4227269 | Johnston | Oct 1980 | A |
4231030 | Weiss | Oct 1980 | A |
4231124 | Croxton | Nov 1980 | A |
4236261 | Huempfner | Dec 1980 | A |
4240169 | Roos | Dec 1980 | A |
4258445 | Zur | Mar 1981 | A |
4259762 | Civitelli | Apr 1981 | A |
4264904 | McCoy | Apr 1981 | A |
4293746 | Braaten | Oct 1981 | A |
4312500 | Janssen | Jan 1982 | A |
4324010 | Houlberg et al. | Apr 1982 | A |
4336621 | Schwartz et al. | Jun 1982 | A |
4345344 | Gadoury et al. | Aug 1982 | A |
4354838 | Hoyer et al. | Oct 1982 | A |
4361917 | Wilson | Dec 1982 | A |
4369535 | Ekkerink | Jan 1983 | A |
4380838 | Lutchansky | Apr 1983 | A |
4386254 | Eberhardt et al. | May 1983 | A |
4398313 | Mitchell | Aug 1983 | A |
4409695 | Johnston et al. | Oct 1983 | A |
4411035 | Fenwick | Oct 1983 | A |
4425673 | Werner | Jan 1984 | A |
4435862 | King et al. | Mar 1984 | A |
4453732 | Assanah et al. | Jun 1984 | A |
4463418 | O'Quin, II | Jul 1984 | A |
4472845 | Chivetta et al. | Sep 1984 | A |
4472846 | Volk, Jr. et al. | Sep 1984 | A |
4484367 | Jenkins | Nov 1984 | A |
4489449 | Failor et al. | Dec 1984 | A |
4494259 | Miller et al. | Jan 1985 | A |
4539560 | Fleck et al. | Sep 1985 | A |
4542547 | Sato | Sep 1985 | A |
4545084 | Peterson | Oct 1985 | A |
4556198 | Tominaga | Dec 1985 | A |
4557471 | Pazzini | Dec 1985 | A |
4559656 | Foster | Dec 1985 | A |
4586492 | Manahan | May 1986 | A |
4592104 | Foster et al. | Jun 1986 | A |
4612679 | Mitchell | Sep 1986 | A |
4625345 | Wood | Dec 1986 | A |
4633237 | Tucknott | Dec 1986 | A |
4633539 | Morrison | Jan 1987 | A |
4638313 | Sherwood | Jan 1987 | A |
4638516 | Vrzalik | Jan 1987 | A |
4639954 | Speed | Feb 1987 | A |
4653129 | Kuck et al. | Mar 1987 | A |
4654903 | Chubb et al. | Apr 1987 | A |
4658450 | Thomspn | Apr 1987 | A |
4669136 | Waters et al. | Jun 1987 | A |
4675926 | Lindblom et al. | Jun 1987 | A |
4680753 | Fulton | Jul 1987 | A |
4680790 | Packard et al. | Jul 1987 | A |
4682376 | Feldt | Jul 1987 | A |
4685159 | Oetiker | Aug 1987 | A |
4685160 | Rizzardo | Aug 1987 | A |
4686722 | Swart | Aug 1987 | A |
4715385 | Cudahy | Dec 1987 | A |
4724555 | Poehner et al. | Feb 1988 | A |
4745647 | Goodwin | May 1988 | A |
4751754 | Bailey et al. | Jun 1988 | A |
4760615 | Furniss | Aug 1988 | A |
4764870 | Haskin | Aug 1988 | A |
4768241 | Beney | Sep 1988 | A |
4768249 | Goodwin | Sep 1988 | A |
4769584 | Irigoyen et al. | Sep 1988 | A |
4787104 | Grantham | Nov 1988 | A |
4797962 | Goode | Jan 1989 | A |
4800384 | Snijders | Jan 1989 | A |
4803744 | Peck | Feb 1989 | A |
4804950 | Moon | Feb 1989 | A |
4808994 | Riley | Feb 1989 | A |
4811435 | Foster et al. | Mar 1989 | A |
4821351 | Bergenwall | Apr 1989 | A |
4821470 | Kappers et al. | Apr 1989 | A |
4829616 | Walker | May 1989 | A |
4847929 | Pupovic | Jul 1989 | A |
4851625 | Liebich | Jul 1989 | A |
4856123 | Henderson et al. | Aug 1989 | A |
4858260 | Failor et al. | Aug 1989 | A |
4858481 | Abraham | Aug 1989 | A |
4860394 | Benessis et al. | Aug 1989 | A |
4862529 | Peck | Sep 1989 | A |
4862530 | Chen | Sep 1989 | A |
4868937 | Connolly | Sep 1989 | A |
4894876 | Fenwick | Jan 1990 | A |
4907845 | Wood | Mar 1990 | A |
4912787 | Bradcovich | Apr 1990 | A |
4921295 | Stollenwerk | May 1990 | A |
4927127 | Lock | May 1990 | A |
4934468 | Koerber | Jun 1990 | A |
4944055 | Shainfeld | Jul 1990 | A |
4949410 | Failor et al. | Aug 1990 | A |
4951032 | Langsam | Aug 1990 | A |
4953243 | Birkmann | Sep 1990 | A |
4959957 | Schmale et al. | Oct 1990 | A |
4974905 | Davis | Dec 1990 | A |
4979183 | Cowart | Dec 1990 | A |
4984774 | Zupancic et al. | Jan 1991 | A |
4985946 | Foster et al. | Jan 1991 | A |
4987897 | Funke | Jan 1991 | A |
4992926 | Janke | Feb 1991 | A |
4998939 | Potthast | Mar 1991 | A |
5004058 | Langford et al. | Apr 1991 | A |
5023967 | Ferrand | Jun 1991 | A |
5035014 | Blanchard | Jul 1991 | A |
5040253 | Cheng | Aug 1991 | A |
5054141 | Foster et al. | Oct 1991 | A |
5058871 | Congin et al. | Oct 1991 | A |
5060425 | Kappers et al. | Oct 1991 | A |
5063624 | Smith et al. | Nov 1991 | A |
5072463 | Willis | Dec 1991 | A |
5074000 | Soltani et al. | Dec 1991 | A |
5076375 | Dillon | Dec 1991 | A |
5077843 | Dale et al. | Jan 1992 | A |
5083332 | Foster et al. | Jan 1992 | A |
5083334 | Huck et al. | Jan 1992 | A |
5095561 | Green et al. | Mar 1992 | A |
5097550 | Marra, Jr. | Mar 1992 | A |
5103519 | Hasty | Apr 1992 | A |
5105486 | Peterson | Apr 1992 | A |
5109554 | Borders et al. | May 1992 | A |
5117521 | Foster et al. | Jun 1992 | A |
5127034 | Wright | Jun 1992 | A |
5129117 | Celestina et al. | Jul 1992 | A |
5137033 | Norton | Aug 1992 | A |
5138729 | Ferrand | Aug 1992 | A |
5148562 | Borders et al. | Sep 1992 | A |
5157787 | Donnellan et al. | Oct 1992 | A |
5157800 | Borders | Oct 1992 | A |
5160010 | Peterson | Nov 1992 | A |
5161274 | Hayes et al. | Nov 1992 | A |
5175897 | Marra, Jr. | Jan 1993 | A |
5179744 | Foster et al. | Jan 1993 | A |
5191663 | Holder et al. | Mar 1993 | A |
5205004 | Hayes et al. | Apr 1993 | A |
D336577 | Celestina et al. | Jun 1993 | S |
5216769 | Eakin | Jun 1993 | A |
5222132 | Rioux, Jr. | Jun 1993 | A |
5224228 | Larrimore | Jul 1993 | A |
5224496 | Palmer | Jul 1993 | A |
5230113 | Foster et al. | Jul 1993 | A |
5235258 | Schuerch | Aug 1993 | A |
5235713 | Guthrie et al. | Aug 1993 | A |
5245718 | Krauska | Sep 1993 | A |
5249270 | Stewart | Sep 1993 | A |
5255403 | Ortiz | Oct 1993 | A |
5267364 | Volk | Dec 1993 | A |
5269030 | Pahno | Dec 1993 | A |
5269388 | Reichow et al. | Dec 1993 | A |
5274311 | Littlejohn et al. | Dec 1993 | A |
5276432 | Travis | Jan 1994 | A |
5279010 | Ferrand et al. | Jan 1994 | A |
5283096 | Greenberg et al. | Feb 1994 | A |
5285792 | Sjoquist | Feb 1994 | A |
5300926 | Stoeckl | Apr 1994 | A |
5305482 | Dewert | Apr 1994 | A |
5317769 | Weismiller et al. | Jun 1994 | A |
5319355 | Russek | Jun 1994 | A |
5319363 | Welch et al. | Jun 1994 | A |
5320641 | Riddle et al. | Jun 1994 | A |
5323565 | Kappers et al. | Jun 1994 | A |
5324900 | Gonser et al. | Jun 1994 | A |
5335651 | Foster | Aug 1994 | A |
5345629 | Ferrand | Sep 1994 | A |
5348326 | Fullenkamp et al. | Sep 1994 | A |
5353012 | Barham | Oct 1994 | A |
5361755 | Schraag | Nov 1994 | A |
5365622 | Schirmer | Nov 1994 | A |
5365623 | Springer | Nov 1994 | A |
5367667 | Wahlquist | Nov 1994 | A |
5367728 | Chang | Nov 1994 | A |
5370111 | Reeder et al. | Dec 1994 | A |
5375604 | Kelly | Dec 1994 | A |
5394580 | Foster et al. | Mar 1995 | A |
5398354 | Balonick et al. | Mar 1995 | A |
5422521 | Neer et al. | Jun 1995 | A |
5423231 | Helfrich et al. | Jun 1995 | A |
5435027 | Bourgraf et al. | Jul 1995 | A |
5438721 | Pahno | Aug 1995 | A |
5444880 | Weismiller et al. | Aug 1995 | A |
5450639 | Weismiller et al. | Sep 1995 | A |
5454126 | Foster et al. | Oct 1995 | A |
5465082 | Chaco | Nov 1995 | A |
5468216 | Johnson et al. | Nov 1995 | A |
5469588 | DiMatteo et al. | Nov 1995 | A |
5471190 | Zimmermann | Nov 1995 | A |
5479666 | Foster et al. | Jan 1996 | A |
5481769 | Schneider | Jan 1996 | A |
5490298 | Goldsmith et al. | Feb 1996 | A |
RE35201 | Krauska | Apr 1996 | E |
5527097 | Martin | Jun 1996 | A |
5537701 | Elliott | Jul 1996 | A |
5542136 | Tappel | Aug 1996 | A |
5542138 | Williams et al. | Aug 1996 | A |
5544376 | Fromson | Aug 1996 | A |
5561412 | Novak | Oct 1996 | A |
5577279 | Foster et al. | Nov 1996 | A |
5577280 | Elliott | Nov 1996 | A |
5579550 | Bathrick et al. | Dec 1996 | A |
5594961 | Yokoi et al. | Jan 1997 | A |
5596437 | Heins | Jan 1997 | A |
5608932 | Hasegawa | Mar 1997 | A |
5611094 | D'Entremont | Mar 1997 | A |
5613255 | Bish et al. | Mar 1997 | A |
5615431 | Vassilli | Apr 1997 | A |
5630238 | Weismiller et al. | May 1997 | A |
5636394 | Bartley | Jun 1997 | A |
5642350 | Dailey | Jun 1997 | A |
5653064 | Kappers et al. | Aug 1997 | A |
5664270 | Bell | Sep 1997 | A |
5666681 | Meyer et al. | Sep 1997 | A |
5687437 | Goldsmith | Nov 1997 | A |
5689839 | Laganiere et al. | Nov 1997 | A |
5699038 | Ulrich | Dec 1997 | A |
5701618 | Brugger | Dec 1997 | A |
5708997 | Foster et al. | Jan 1998 | A |
5715548 | Weismiller et al. | Feb 1998 | A |
5720059 | Allevato et al. | Feb 1998 | A |
5723423 | Van Slyke | Mar 1998 | A |
5726541 | Glenn | Mar 1998 | A |
5732423 | Weismiller et al. | Mar 1998 | A |
5737781 | Votel | Apr 1998 | A |
5745937 | Weismiller et al. | May 1998 | A |
5749123 | Warren et al. | May 1998 | A |
5750884 | Field | May 1998 | A |
5771511 | Kummer et al. | Jun 1998 | A |
5781949 | Weismiller et al. | Jul 1998 | A |
5802636 | Corbin et al. | Sep 1998 | A |
5802640 | Ferrand et al. | Sep 1998 | A |
5806111 | Heimbrock et al. | Sep 1998 | A |
5808552 | Wiley et al. | Sep 1998 | A |
5854454 | Upender | Dec 1998 | A |
5870784 | Elliott | Feb 1999 | A |
5873137 | Yavets-Chen | Feb 1999 | A |
5878452 | Brooke et al. | Mar 1999 | A |
5883615 | Fago et al. | Mar 1999 | A |
5890765 | LaPointe et al. | Apr 1999 | A |
5898961 | Ambach et al. | May 1999 | A |
5906016 | Ferrand et al. | May 1999 | A |
5906017 | Ferrand et al. | May 1999 | A |
5918505 | Jensen | Jul 1999 | A |
5934280 | Viard et al. | Aug 1999 | A |
5939803 | Frost | Aug 1999 | A |
5983425 | DiMucci et al. | Nov 1999 | A |
5987671 | Heimbrock et al. | Nov 1999 | A |
6000076 | Webster et al. | Dec 1999 | A |
6006379 | Hensley | Dec 1999 | A |
6008598 | Luff et al. | Dec 1999 | A |
6016580 | Heimbrock et al. | Jan 2000 | A |
6021533 | Ellis et al. | Feb 2000 | A |
6038718 | Pennington et al. | Mar 2000 | A |
6047423 | Larson | Apr 2000 | A |
6047424 | Osborne | Apr 2000 | A |
6067019 | Scott | May 2000 | A |
6076208 | Heimbrock et al. | Jun 2000 | A |
6089593 | Hanson et al. | Jul 2000 | A |
6098223 | Larson | Aug 2000 | A |
6108838 | Connolly et al. | Aug 2000 | A |
6112345 | Foster et al. | Sep 2000 | A |
6131868 | Welling et al. | Oct 2000 | A |
6154899 | Brooke et al. | Dec 2000 | A |
6158295 | Nielsen | Dec 2000 | A |
6163903 | Weismiller et al. | Dec 2000 | A |
6178576 | Newell | Jan 2001 | B1 |
6182310 | Weismiller et al. | Feb 2001 | B1 |
6185767 | Brooke et al. | Feb 2001 | B1 |
6199508 | Miale et al. | Mar 2001 | B1 |
6208250 | Dixon et al. | Mar 2001 | B1 |
6212714 | Allen et al. | Apr 2001 | B1 |
6212718 | Stolpmann | Apr 2001 | B1 |
6223369 | Maier et al. | May 2001 | B1 |
6226821 | Heimbrock et al. | May 2001 | B1 |
6240583 | Brooke et al. | Jun 2001 | B1 |
6260221 | Grabell et al. | Jul 2001 | B1 |
6273771 | Buckley et al. | Aug 2001 | B1 |
6276011 | Antinori | Aug 2001 | B1 |
6279183 | Kummer | Aug 2001 | B1 |
6282738 | Heimbrock et al. | Sep 2001 | B1 |
6290194 | Chaconas et al. | Sep 2001 | B1 |
6295675 | Ellis et al. | Oct 2001 | B1 |
6320510 | Menkedick et al. | Nov 2001 | B2 |
6321878 | Mobley et al. | Nov 2001 | B1 |
6336235 | Ruehl | Jan 2002 | B1 |
6351678 | Borders | Feb 2002 | B1 |
6351861 | Shows et al. | Mar 2002 | B1 |
6352240 | Eckstein et al. | Mar 2002 | B1 |
6353950 | Barlett et al. | Mar 2002 | B1 |
6370448 | Eryurek | Apr 2002 | B1 |
6397286 | Chatenever et al. | May 2002 | B1 |
6397416 | Brooke et al. | Jun 2002 | B2 |
6438776 | Ferrand et al. | Aug 2002 | B2 |
6473921 | Brooke et al. | Nov 2002 | B2 |
6481688 | Welling et al. | Nov 2002 | B1 |
6484221 | Lorinser et al. | Nov 2002 | B1 |
6486792 | Moster et al. | Nov 2002 | B1 |
6496993 | Allen et al. | Dec 2002 | B2 |
6499167 | Ellis et al. | Dec 2002 | B1 |
6505365 | Hanson et al. | Jan 2003 | B1 |
6516479 | Barbour | Feb 2003 | B1 |
6539566 | Hayes | Apr 2003 | B1 |
6559783 | Stoneking | May 2003 | B1 |
6560798 | Welling et al. | May 2003 | B2 |
6565112 | Hanson et al. | May 2003 | B2 |
6606670 | Stoneking et al. | Aug 2003 | B1 |
6611979 | Welling et al. | Sep 2003 | B2 |
6629247 | Hall et al. | Sep 2003 | B1 |
6631431 | Silvkoff et al. | Oct 2003 | B1 |
6636100 | Shingaki | Oct 2003 | B1 |
6658680 | Osborne et al. | Dec 2003 | B2 |
6668408 | Grass et al. | Dec 2003 | B2 |
6684427 | Allen et al. | Feb 2004 | B2 |
6691346 | Osborne et al. | Feb 2004 | B2 |
6694548 | Foster et al. | Feb 2004 | B2 |
6708358 | Hensley | Mar 2004 | B2 |
6726279 | Figel et al. | Apr 2004 | B1 |
6735797 | Long et al. | May 2004 | B1 |
6751688 | El-Demerdash et al. | Jun 2004 | B1 |
6789280 | Paul | Sep 2004 | B1 |
6789458 | Schumacher et al. | Sep 2004 | B2 |
6791460 | Dixon et al. | Sep 2004 | B2 |
6798341 | Eckel | Sep 2004 | B1 |
6826793 | Tekulve | Dec 2004 | B2 |
6829793 | Brooke et al. | Dec 2004 | B2 |
6880189 | Welling et al. | Apr 2005 | B2 |
6904631 | Vrzalik et al. | Jun 2005 | B2 |
6910236 | Rene | Jun 2005 | B2 |
6912594 | Bartling | Jun 2005 | B2 |
6941598 | Ferrand et al. | Sep 2005 | B2 |
6944739 | Bartling et al. | Sep 2005 | B2 |
6957461 | Osborne et al. | Oct 2005 | B2 |
6976357 | Pfaff | Dec 2005 | B1 |
6978500 | Osborne et al. | Dec 2005 | B2 |
RE38968 | Black et al. | Feb 2006 | E |
7000272 | Allen et al. | Feb 2006 | B2 |
RE39049 | Black et al. | Mar 2006 | E |
7009995 | Bohrer et al. | Mar 2006 | B1 |
7017208 | Weismiller et al. | Mar 2006 | B2 |
7017210 | Ooyama et al. | Mar 2006 | B2 |
7028352 | Kramer et al. | Apr 2006 | B2 |
7076517 | Bartling | Jul 2006 | B2 |
7089612 | Rocher et al. | Aug 2006 | B2 |
7171708 | Osborne et al. | Feb 2007 | B2 |
7237287 | Weismiller | Jul 2007 | B2 |
7296312 | Menkedick et al. | Nov 2007 | B2 |
7346945 | Phillips et al. | Mar 2008 | B2 |
7406731 | Menkedick et al. | Aug 2008 | B2 |
7426760 | Vrzalik | Sep 2008 | B2 |
7454805 | Osborne et al. | Nov 2008 | B2 |
7472437 | Riley et al. | Jan 2009 | B2 |
7506390 | Dixon | Mar 2009 | B2 |
7520006 | Menkedick | Apr 2009 | B2 |
7533429 | Menkedick et al. | May 2009 | B2 |
7538659 | Ulrich | May 2009 | B2 |
7568246 | Weismiller | Aug 2009 | B2 |
7610637 | Menkedick et al. | Nov 2009 | B2 |
7669263 | Menkedick | Mar 2010 | B2 |
7676866 | Toms et al. | Mar 2010 | B2 |
7703158 | Wilker et al. | Apr 2010 | B2 |
7716762 | Ferraresi et al. | May 2010 | B2 |
7761942 | Benzo et al. | Jul 2010 | B2 |
7834768 | Dixon et al. | Nov 2010 | B2 |
7926131 | Menkedick et al. | Apr 2011 | B2 |
7986242 | Dixon et al. | Jul 2011 | B2 |
8039766 | Flanagan | Oct 2011 | B2 |
RE43193 | Osborne et al. | Feb 2012 | E |
8151387 | Osborne et al. | Apr 2012 | B2 |
RE43532 | Menkedick et al. | Jul 2012 | E |
8258944 | Riley et al. | Sep 2012 | B2 |
8258963 | Dixon et al. | Sep 2012 | B2 |
8400311 | Dixon et al. | Mar 2013 | B2 |
8502663 | Riley et al. | Aug 2013 | B2 |
8525682 | Dixon et al. | Sep 2013 | B2 |
8830070 | Dixon et al. | Sep 2014 | B2 |
8866610 | Riley et al. | Oct 2014 | B2 |
20010000828 | Hensley | May 2001 | A1 |
20010011393 | Brooke et al. | Aug 2001 | A1 |
20010011394 | Heimbrock et al. | Aug 2001 | A1 |
20010027578 | Brooke et al. | Oct 2001 | A1 |
20010029628 | Ferrand et al. | Oct 2001 | A1 |
20010032362 | Welling et al. | Oct 2001 | A1 |
20010037724 | Schumacher et al. | Nov 2001 | A1 |
20020002742 | Osborne et al. | Jan 2002 | A1 |
20020013965 | Wilson | Feb 2002 | A1 |
20020014951 | Kramer et al. | Feb 2002 | A1 |
20020059679 | Weismiller et al. | May 2002 | A1 |
20020066142 | Osborne et al. | Jun 2002 | A1 |
20020080037 | Dixon et al. | Jun 2002 | A1 |
20020092096 | Heimbrock et al. | Jul 2002 | A1 |
20020144348 | Ganance | Oct 2002 | A1 |
20020166088 | Dierauer et al. | Nov 2002 | A1 |
20030009952 | Gallant et al. | Jan 2003 | A1 |
20030019038 | Welling et al. | Jan 2003 | A1 |
20030051291 | Brooke et al. | Mar 2003 | A1 |
20030051292 | Ferrand et al. | Mar 2003 | A1 |
20030056016 | Bartling | Mar 2003 | A1 |
20030056293 | Brooke et al. | Mar 2003 | A1 |
20030061547 | Bartling | Mar 2003 | A1 |
20030079603 | Schumacher et al. | May 2003 | A1 |
20030093860 | Kramer | May 2003 | A1 |
20030115672 | Newkirk | Jun 2003 | A1 |
20030214953 | El-Demerdash et al. | Nov 2003 | A1 |
20040034936 | Welling et al. | Feb 2004 | A1 |
20040085903 | Matsumoto et al. | May 2004 | A1 |
20040128765 | Osborne et al. | Jul 2004 | A1 |
20040142722 | Everett | Jul 2004 | A1 |
20040143677 | Novak | Jul 2004 | A1 |
20040151047 | Bartling et al. | Aug 2004 | A1 |
20040153583 | Bartling | Aug 2004 | A1 |
20040177445 | Osborne | Sep 2004 | A1 |
20040205111 | Chasmawala et al. | Oct 2004 | A1 |
20050000020 | Schermel | Jan 2005 | A1 |
20050028281 | Ooyama et al. | Feb 2005 | A1 |
20050085710 | Earnst et al. | Apr 2005 | A1 |
20050172405 | Menkedick et al. | Aug 2005 | A1 |
20050273940 | Petrosenko et al. | Dec 2005 | A1 |
20050284144 | Pfaff | Dec 2005 | A1 |
20060010601 | Riley et al. | Jan 2006 | A1 |
20060053555 | Poulos et al. | Mar 2006 | A1 |
20060053562 | Poulos et al. | Mar 2006 | A1 |
20060059624 | Poulos et al. | Mar 2006 | A1 |
20060075559 | Skinner et al. | Apr 2006 | A1 |
20060075560 | Osborne et al. | Apr 2006 | A1 |
20060080777 | Rocher et al. | Apr 2006 | A1 |
20060096029 | Osborne et al. | May 2006 | A1 |
20060101317 | Uemura et al. | May 2006 | A1 |
20060162079 | Menkedick et al. | Jul 2006 | A1 |
20060168730 | Menkedick et al. | Aug 2006 | A1 |
20060168731 | Menkedick et al. | Aug 2006 | A1 |
20060179579 | Phillips et al. | Aug 2006 | A1 |
20060253982 | Kummer et al. | Nov 2006 | A1 |
20070296600 | Dixon et al. | Dec 2007 | A1 |
20080010747 | Dixon et al. | Jan 2008 | A1 |
20080010748 | Menkedick et al. | Jan 2008 | A1 |
20080189856 | Toms et al. | Aug 2008 | A1 |
20080201847 | Menkedick et al. | Aug 2008 | A1 |
20080201851 | Menkedick et al. | Aug 2008 | A1 |
20080289108 | Menkedick et al. | Nov 2008 | A1 |
20090094744 | Benzo et al. | Apr 2009 | A1 |
20090109025 | Riley et al. | Apr 2009 | A1 |
20090313758 | Menkedick et al. | Dec 2009 | A1 |
20110066287 | Flanagan | Mar 2011 | A1 |
20110162145 | Osborne et al. | Jul 2011 | A1 |
20110234408 | Dixon et al. | Sep 2011 | A1 |
20120086575 | Dixon et al. | Apr 2012 | A1 |
20120137439 | Heimbrock | Jun 2012 | A1 |
20120151678 | Richards | Jun 2012 | A1 |
20120174319 | Menkedick et al. | Jul 2012 | A1 |
20120291200 | Dixon et al. | Nov 2012 | A1 |
20120317726 | Riley et al. | Dec 2012 | A1 |
20130312183 | Riley et al. | Nov 2013 | A1 |
20130340169 | Zerhusen et al. | Dec 2013 | A1 |
20140000032 | Dixon et al. | Jan 2014 | A1 |
20140259413 | Johnson et al. | Sep 2014 | A1 |
20140352067 | Riley et al. | Dec 2014 | A1 |
Number | Date | Country |
---|---|---|
0657155 | Jun 2014 | BA |
2303037 | Mar 2000 | CA |
23106030 | Mar 1973 | DE |
3313843 | Oct 1984 | DE |
3716917 | Dec 1988 | DE |
40 25 834 | Feb 1992 | DE |
19854136 | Jun 1999 | DE |
19830518 | Jan 2000 | DE |
199 00 602 | Jul 2000 | DE |
19925340 | Dec 2000 | DE |
19962079 | Jun 2001 | DE |
10324038 | Dec 2004 | DE |
102005018686 | Nov 2006 | DE |
0 037 063 | Oct 1981 | EP |
0 485 362 | Dec 1986 | EP |
0 218 301 | Apr 1987 | EP |
150254 | Jan 1989 | EP |
0338689 | Oct 1989 | EP |
0 341 570 | Nov 1989 | EP |
0 349 067 | Jan 1990 | EP |
494551 | Jul 1992 | EP |
0529926 | Mar 1993 | EP |
541981 | May 1993 | EP |
0 558 108 | Sep 1993 | EP |
488552 | Aug 1994 | EP |
0657154 | Jun 1995 | EP |
0657155 | Jun 1995 | EP |
979641 | Feb 2000 | EP |
498111 | Mar 2001 | EP |
1086680 | Mar 2001 | EP |
1447069 | Aug 2004 | EP |
1757258 | Feb 2007 | EP |
7095 | Jan 1913 | GB |
1 466 080 | Mar 1977 | GB |
2 015 872 | Sep 1978 | GB |
2041737 | Sep 1980 | GB |
1595945 | Aug 1981 | GB |
2 169 195 | Jul 1986 | GB |
2250189 | Nov 1993 | GB |
2 313 303 | Nov 1997 | GB |
53-37515 | Jun 1978 | JP |
2-156950 | Jun 1990 | JP |
3-186212 | Aug 1991 | JP |
3-193005 | Aug 1991 | JP |
3-62422 | Sep 1991 | JP |
3-62423 | Sep 1991 | JP |
3-62424 | Sep 1991 | JP |
3-67698 | Oct 1991 | JP |
3-237976 | Oct 1991 | JP |
3-72304 | Nov 1991 | JP |
2512862 | May 1996 | JP |
2825152 | Jan 1998 | JP |
2746295 | May 1998 | JP |
11299837 | Nov 1999 | JP |
6716888 | Jun 1969 | NL |
WO 0162151 | Aug 1930 | WO |
WO 9401023 | Jan 1994 | WO |
WO 9427544 | Dec 1994 | WO |
WO 9720534 | Jun 1997 | WO |
WO 9726750 | Jul 1997 | WO |
WO 9817153 | Apr 1998 | WO |
WO 9842227 | Oct 1998 | WO |
WO 9915126 | Apr 1999 | WO |
WO 9916402 | Apr 1999 | WO |
WO 9960893 | Dec 1999 | WO |
WO 0007537 | Feb 2000 | WO |
WO 0069386 | Nov 2000 | WO |
WO 0130000 | Apr 2001 | WO |
WO 0147340 | Jul 2001 | WO |
0174286 | Oct 2001 | WO |
WO 0174286 | Oct 2001 | WO |
WO 0191689 | Dec 2001 | WO |
WO 0230284 | Apr 2002 | WO |
WO 03079953 | Oct 2003 | WO |
WO 03088885 | Oct 2003 | WO |
WO 2004021952 | Mar 2004 | WO |
WO 2007054681 | May 2007 | WO |
WO 2007058578 | May 2007 | WO |
WO 2007075701 | Jul 2007 | WO |
WO 2009065109 | May 2009 | WO |
WO 2009116859 | Sep 2009 | WO |
Entry |
---|
Complaint against Stryker Corporation, Stryker Sales Corporation. ( Filing fee $ 350 receiptnumber 0758-737485.), filed by Hill-Rom Company, Inc., Hill-Rom Services, Inc., Hill-RomManufacturing, Inc. (Attachments: # 1 JS-44 Civil Cover Sheet, # 2 Summons, # 3 Report onFiling Patent/Trademark Action, # 4 Exhibit A—U.S. Patent No. 5,771,511, # 5 Exhibit B—U.S.Patent No. 7,237,287, # 6 Exhibit C—U.S. Patent No. 7,568,246, # 7 Exhibit D—U.S. Patent No. 7,506,390, # 8 Exhibit E—U.S. Patent No. 7,520,006, # 9 Exhibit F—U.S. Patent No. 7,669,263,# 10 Exhibit G—U.S. Patent No. 5,699,038, # 11 Exhibit H—U.S. Patent No. 6,147,592, # 12Exhibit I—U.S. Patent No. 7,538,659) (Stathas, Lynn) [Transferred from Wisconsin Western onAug. 16, 2011.] (Entered: Apr. 4, 2011). |
Brief in Support of 19 Motion to Transfer by Defendants Stryker Corporation, Stryker Sales Corporation (Noel, Kristin) [Transferred from Wisconsin Western on Aug. 16, 2011.] (Entered: May 23, 2011). |
Answer, Counterclaim against Hill-Rom Company, Inc., Hill-Rom Manufacturing, Inc., Hill-Rom Services, Inc. By Defendants Stryker Corporation, Stryker Sales Corporation. (Noel, Kristin) Modified on Jun. 7, 2011 (jas). [Transferred from Wisconsin Western on Aug. 16, 2011.] (Entered: Jun. 6, 2011). |
Brief in Opposition by Plaintiffs Hill-Rom Company, Inc., Hill-Rom Manufacturing, Inc., Hill-Rom Services, Inc., Counter Defendants Hill-Rom Company, Inc., Hill-Rom Manufacturing, Inc., Hill-Rom Services, Inc. re: 19 Motion to Transfer to Southern District of Indiana filed by Stryker Sales Corporation, Stryker Corporation (Callahan, David) [Transferred from Wisconsin Western on Aug. 16, 2011.] (Entered: Jun. 13, 2011). |
Brief in Reply by Defendants/Counter Claimants Stryker Corporation, Stryker Sales Corporation, in Support of 19 Motion to Transfer. (Noel, Kristin) [Transferred from Wisconsin Western on Aug. 16, 2011.] (Entered: Jun. 23, 2011). |
Reply to Counterclaim by Plaintiffs Hill-Rom Company, Inc., Hill-Rom Manufacturing, Inc., Hill-Rom Services, Inc., Counter Defendants Hill-Rom Company, Inc., Hill-Rom Manufacturing, Inc., Hill-Rom Services, Inc.. (Callahan, David) [Transferred from Wisconsin Western on Aug. 16, 2011.] (Entered: Jun. 27, 2011). |
Motion for Leave to File reply by Plaintiffs Hill-Rom Company, Inc., Hill-Rom Manufacturing, Inc., Hill-Rom Services, Inc., Counter Defendants Hill-Rom Company, Inc., Hill-Rom Manufacturing, Inc., Hill-Rom Services, Inc. To: 44 Corrected Declaration of Kevin Conway filed by Defendants Stryker Corporation, Stryker Sales Corporation re 19 Motion to Transfer. (Attachments: # 1 Exhibit A—Reply, # 2 Text of Proposed Order) (Callahan, David) Modified event relationship and text on Jul. 11, 2011 (IIj). [Transferred from Wisconsin Western on Aug. 16, 2011.] (Entered: Jul. 8, 2011). |
Brief in Opposition by Defendants Stryker Corporation, Stryker Sales Corporation re: 46 Motion for Leave to File reply filed by Hill-Rom Services, Inc., Hill-Rom Company, Inc., Hill-Rom Manufacturing, Inc. (Tomaselli, Anthony) [Transferred from Wisconsin Western on Aug. 16, 2011.] (Entered: Jul. 12, 2011). |
Amended Answer with Jury Demand, Counterclaim and Affirmative Defenses against Hill-Rom Company, Inc., Hill-Rom Manufacturing, Inc., Hill-Rom Services, Inc. By Defendant Stryker. (Noel, Kristin) Modified on Aug. 2, 2011 (IIj). [Transferred from Wisconsin Western on Aug. 16, 2011.] (Entered: Aug. 1, 2011). |
Notice of Answer, Amended Answer and Transfer of Case in lawsuit sent to Director of U.S. Patent and Trademark Office. (Attachments: # 1 Docket Sheet from the Western District of Wisconsin case # 3:11-cv-00251-bbc, # 2 Answer filed, # 3 Amended Answer filed) (JKS) (Entered: Aug. 22, 2011). |
Joint Motion for Protective Order, filed by Plaintiffs Hill-Rom Company, Inc., Hill-Rom Manufacturing, Inc., Hill-Rom Services, Inc., Counter Defendants Hill-Rom Company, Inc., Hill-Rom Company, Inc., Hill-Rom Manufacturing, Inc., Hill-Rom Manufacturing, Inc., Hill-Rom Services, Inc., Hill-Rom Services, Inc., Counter Claimants Stryker Corporation, Stryker Corporation, Stryker Sales Corporation, Stryker Sales Corporation, Defendants Stryker Corporation, Stryker Sales Corporation. (Attachments: # 1 Text of Proposed Order Proposed Protective Order)(Callahan, David) (Entered: Aug. 31, 2011). |
Statement of Position by All Defendants. (Whistler, Philip) (Entered: Sep. 6, 2011). |
Statement of Position by Hill-Rom Company, Inc., Hill-Rom Manufacturing, Inc., Hillrom Services, Inc. (Hull, Andrew) (Entered: Sep. 9, 2011). |
Case Management Plan Tendered, filed by Plaintiffs Hill-Rom Company, Inc., Hill-Rom Manufacturing, Inc., Hill-Rom Services, Inc., Counter Defendants Hill-Rom Company, Inc., Hill-Rom Company, Inc., Hill-Rom Manufacturing, Inc., Hill-Rom Manufacturing, Inc., Hill-Rom Services, Inc., Hill-Rom Services, Inc., Counter Claimants Stryker Corporation, Stryker Corporation, Stryker Sales Corporation, Stryker Sales Corporation, Defendants Stryker Corporation, Stryker Sales Corporation. (Callahan, David) (Entered: Oct. 12, 2011). |
Case Management Plan Tendered, filed by Plaintiffs Hill-Rom Company, Inc., Hill-Rom Manufacturing, Inc., Hill-Rom Services, Inc., Counter Defendants Hill-Rom Company, Inc., Hill-Rom Manufacturing, Inc., Hill-Rom Services, Inc., Counter Claimants Stryker Corporation, Stryker Sales Corporation, Defendants Stryker Corporation, Stryker Sales Corporation. (Hull, Andrew) (Entered: Dec. 16, 2011). |
Order: Case Management Plan Approved As Amended (See Order for deadlines). Signed by Magistrate Judge Denise K. LaRue on Feb. 6, 2012.(MAC) (Entered: Feb. 6, 2012). |
Statement Joint Claim Construction Statement by Hill-Rom Company, Inc., Hill-Rom Manufacturing, Inc., Hill-Rom Services, Inc., Stryker Corporation, Stryker Sales Corporation. (Callahan, David) (Entered: May 21, 2012). |
Motion to Stay Certain Proceedings Pending Reexamination, filed by Defendants Stryker Corporation, Stryker Sales Corporation. (Lueders, Daniel) (Entered: Aug. 15, 2012). |
Brief/Memorandum in Support re 115 Motion to Stay Certain Proceedings Pending Reexamination , filed by Defendants Stryker Corporation, Stryker Sales Corporation. (Attachments: # 1 Exhibit A, Inter Parte Reexamination Filing Data, # 2 Exhibit B, Ex Parte Reexamination Filing Data)(Lueders, Daniel) (Entered: Aug. 15, 2012). |
Order—Given the procedural posture of the case at this time, the Court Orders the parties toonly address the claims and terms the parties believe the Court must construe during theMarkman process for the three patents-in-suit that are not at issue in Defendants' reexaminationrequest. Because this will limit the claims and terms that need to be briefed, the Court DENIESDefendants' request for excess pp.. [Dkt. 117.] The Court Orders the parties to file theirMarkman briefs by Aug. 31, 2012 and the opposition briefs by Oct. 5, 2012. If need be, theCourt will order the parties to file supplemental briefs following the USPTO's decision whether togrant Defendants' reexamination request. Signed by Judge Jane Magnus-Stinson on Aug. 21, 2012.(JKS) (Entered: Aug. 21, 2012). |
Response in Opposition re 115 Motion to Stay Certain Proceedings Pending Reexamination ,filed by Plaintiffs Hill-Rom Company, Inc., Hill-Rom Manufacturing, Inc., Hill-Romservices, Inc., Counter Defendants Hill-Rom Company, Inc., Hill-Rom Manufacturing,Inc., Hill-Rom Services, Inc. . . (Attachments: # 1 Exhibit A—Inter Partes Reexamination FilingData, # 2 Exhibit B—Ex Parte Reexamination Filing Data, # 3 Exhibit C—Request for Interpartes Reexamination)(Callahan, David) (Entered: Aug. 30, 2012). |
Notice of Status of Reexamination, filed by Defendants Stryker Corporation, Strykersales Corporation (Lueders, Daniel) (Entered: Sep. 19, 2012). |
Notice of Updated Status of Reexamination, filed by Defendants Stryker Corporation,Stryker Sales Corporation (Lueders, Daniel) (Entered: Oct. 2, 2012). |
Order—The Court Orders Plaintiffs and Defendants to each file a no. more than 12-pagememorandum by Oct. 16, 2012, regarding how the grant of Defendants' reexaminationrequest affects Defendants' pending motion to stay. No response brief will be allowed.Additionally, by Oct. 16, 2012, Defendants are ordered to file the communications they havereceived from the USPTO granting their requests for reexamination. Signed by Judge JaneMagnus-Stinson on Oct. 2, 2012. (JKS) (Entered: Oct. 2, 2012). |
Notice of Filing of Communications that it has received from the USPTO Granting Requests forReexamination by Stryker Corporation, Stryker Sales Corporation (Attachments: # 1Exhibit 1—PTO's Decision Granting Reexam of US 7,568,246, # 2 Exhibit 2—PTO's First OfficeAction concerning US 7,568,246, # 3 Exhibit 3—PTO's Decision Granting Reexam of US7,237,287, # 4 Exhibit 4—PTO's First Office Action concerning US 7,237,287, # 5 Exhibit 5—PTO'sDecision Granting Reexam of US 7,520,006, # 6 Exhibit 6—PTO's First Office Action concerning US7,520,006, # 7 Exhibit 7—PTO's Decision Granting Reexam of US 5,771,511, # 8 Exhibit PTO'sDecision Granting Reexam of US 7,506,390, # 9 Exhibit PTO's First Office Action concerning US7,506,390, # 10 Exhibit 10- PTO's Decision Granting Reexam of US 7,669,263, # 11 Exhibit 11—PTO's First Office Action concerning US 7,669,263) (Lueders, Daniel) (Entered: Oct. 16, 2012). |
Brief/Memorandum in Support re 115 Motion to Stay Certain Proceedings Pending Reexamination—Stryker's Memorandum Regarding How the Grant of Its Reexamination Requests Affects Its Motion to Stay, filed by Counter Claimants Stryker Corporation, Stryker Sales Corporation, Defendants Stryker Corporation, Stryker Sales Corporation. (Derringer, Steven) (Entered: Oct. 16, 2012). |
Response in Opposition re 115 Motion to Stay Certain Proceedings Pending Reexamination , filed by Plaintiffs Hill-Rom Company, Inc., Hill-Rom Manufacturing, Inc., Hill-Rom Services, Inc., Counter Defendants Hill-Rom Company, Inc., Hill-Rom Manufacturing, Inc., Hill-Rom Services, Inc . . . (Attachments: # 1 Exhibit A—Tuitionfund Case)(Callahan, David) (Entered: Oct. 16, 2012). |
Pinho, Luis Miguel et al., “Reliable Communication in Distributed Computer-Controlled Systems,” Reliable Software Technologies—Ada-Europe 2001, 136-147. |
Kirk, Brian, “Using Software Protocols to Mask Can Bus Insecurities,” IEE Colloquium on Electromagnetic Compatibility of Software (Ref. No. 1998/471) Date of Conference: Nov. 12, 1998. |
Lees, Geoff, “Led by Automotive Industry, CAN Is Beginning to Take Hold,” Electronic Buyer's News, 1996, n 1035, p. 16. |
Lian, Feng-Li, et al., “Performance Evaluation of Control Networks: Ethernet, ControlNet, and DeviceNet,” IEEE Control Systems, vol. 21, Issue: 1, pp. 66-83, Feb. 2001. |
Murrya, Charles J., “Automakers split support for safety data buses,” Electronic Engineering Times, 2001, n 1186, p. 4. |
Navet, N., “Controller are network CANs use within automobiles,” IEEE Potentials, vol. 17, Issue 4, Oct./Nov. 1998, pp. 12-14. |
Cena, G. And Valenzano, A., “An Improved Can Fieldbus for Industrial Applications,” IEEE Transactions on Industrial Electronics, vol. 44, Issue 4, pp. 553-564, Aug. 1997. |
Tindelll, K. et al., “Calculating Controller Area Network (CAN) Message Response Times” Distributed Computer Control Systems 1994, IFAC Workshop, pp. 29-34. |
Pinho, Luis Miguel et al., “Timing Analysis of Reliable Real-Time Communication in CAN Networks,” 13th Euromicro Conference on Real-Time Systems, 1001, pp. 103-114. |
Bello, Lucia Lo et al., “Randomization-Based Approaches for Dynamic Priority Scheduling of Aperiodic Messages on a CAN Network,” Languages, Compilers, and Tools for Embedded Systems, vol. 1985, 2001, pp. 1-18. |
Navet, B. Gaujal N., “Fault Confinement Mechanisms on CAN: Analysis and Improvements,” Fieldbus Systems and Their Applications 2001 (FeT'2001) Proceedsings volume from the 4th IFAC Conference, 2002, pp. 83-90. |
Rauchapt, L., “Performance Analysis of CAN Based Systems,” ICC 94, 1st Internat. CAN Conf., Proc., Aug. 18, 1994. |
Pinho, Luis Miguel et al., “Improved Fault Tolerant Broadcasts in CAN,” ETFA 2001. 8th International Conference on Emerging Technologies and Factory Automation. Proceedings, p. 305-13, vol. 1. |
Cena, Gianluca et al., “A Distributed Mechanism to Improve Fairness in CAN Networks,” Proceedings. 1995 IEEE International Workshop on Factory Communication Systems, WFCS'95 Inclusive, pp. 3-11. |
Torngren, Martin, “A perspective to the Design of Distributed Real-time Control Applications based on CAN,” ICC 95, 2nd Internat. CAN Conf., Proc., London, GB, Oct. 3-4, 1995. |
Rufino, Jose et al., “A Study on the Inaccessibility Characteristics of the Controller Area Network,” ICC 95, 2nd Internat. Can Conf., Proc., London, GB. Oct. 3-4, 1995. |
Fredriksson, Lars-Berno, “What Shall We Focus on in the Next Five Years?,” Real-Time Computing. Proceedings:of the NATO Advanced Study Institute, pp. 653-655, 1994. |
Rufino, Jose et al., Fault-Tolerant Broadcasts in CAN, 28th Annual International Symposium on Fault-Tolerant Computing, Jun. 23-25, 1998, IEEE Computer Society, pp. 150-159. |
Grillo, Jean B., “A Bit Mundane Perhaps, But Hospital Beds, Furniture Business Steady and Growing,” DOTmedbusiness news/ Dec. 2007, pp. 20-22 and 33. |
5th Anniversary CIA 1992-1997, CAN Application Spotlights, Controller Area Network (CAN) and CAN in Automotion (CIA). |
CAN in Automation, Operations Structures, CIA Rules, Services, Application Form. |
Draft of “Stryker's Preliminary Invalidity Contentions for U.S. Patents Nos. 7,506,390, 7,520,006, and 7,669,263,”66 pages. |
Thomas, Jr., L.J. et al., “Continuous Monitoring of Physiologic Variables with a Dedicated Minicomputer,” Biomedical,Computer Laboratory, Washington University School of Medicine, St. Louis, MO, Jul. 1975. |
Griffith, D.W. et al., “A Microprocessor-Based Tilting Bed for Blood Pressure Control,” IEEE, 1979. |
VanDoren, A., “Data Acquisition Systems,” Reston Publishing Company, Inc., 1982. |
Barbenel, J.C. et al., “Monitoring the Mobility of Patients in Bed,” Medical & Biological Engineering & Computing, Sep. 1985. |
Tamura, T. et al., “A Bed Temperature Monitoring System for Assessing Body Movement During Sleep,” Institute of Physical Sciences in Medicine, 1988. |
Maibaum, N. et al., “JXTA: A Technology Facilitating Mobile Peer-to-Peer Networks,” IEEE, 2002. |
Shabot, M. et al., “An Automatic PDMS Interface for the Urotrack Plus 220 Urimeter,” The Departments of Surgery and Nursing, Cedars-Sinai Medical Center, Jul. 15, 1987. |
Leyerle, B. et al., “The PDMS as a Focal Point for Distributed Patient Data,” Intl. Journal of Clinical Monitoring and Computing, 1988. |
Hawley, W. et al., “Clinical Implementation of an Automated Medical Information Bus in an Intensive Care Unit,” LDS Hospital Salt Lake City, UT, 1988. |
Tariq, H. et al., Implementation of MIB at LDS Hospital, IEEE Engineering in Medicine & Biology Society (10th Annual International Conference), 1988. |
Tompkins, W.J. et al., “Interfacing Sensors to the IMB PC,” Prentice Hall, 1988. |
Vincent, P. et al., “Digital Communications and Process Control Transmitters,” IEEE Colloquium on ‘Measurements We Couldn't Make Without a Micro’, 1988. |
Shabot, M., “Standardized Acquisition of Bedside Data: The IEEE P1073 Medical Information Bus,” International Journal of Clinical Monitoring and Computing, 6: 197-204, 1989. |
Franklin, D. et al., “Proposed Standard IEEE P1073 Medical Information Bus Medical Device to Host Computer Interface, Network Overview and Architecture,” IEEE, 1989. |
Markwalter, B. et al., “CEBUS Network Layer Description,” IEEE Transactions on Consumer Electronics, 1989. |
Wittenber, J. et al., “The Medical Device Data Language for the P1073 Medical Information Bus Standard,” Intl. Journal of Clinical Monitoring and Computing, 1990. |
Gardner, M. et al., “Computerized ICU Data Management: Pitfalls and Promises,” Kluwer Academic Publishers, 1990. |
Gardner, R. “Patient-Monitoring Systems,” Medical Informatics, Computer Applications in Health Care, 1990. |
Gage, J.S. et al., “Automated Anesthesia Surgery Medical Record System,” International Journal of Clinical Monitoring and Computing 7: 259-263, 1990. |
Nolan, L.S. et al., “The P1073 Medical Information Bus Standard: Overview and Benefits for Clinical Users,” Symposium on Computer Application in Medical Care: 216-219, 1990. |
Stanton, K. B. et al., “PSUBOT—A Voice-Controlled Wheelchair for the Handicapped,” Proceedings of the 33rd Midwest Symposium on Circuits and Systems: 669-672, 1990. |
Clemmer, T. et al., “Medical Informatics in the Intensive Care Units: State of the Art 1991,” Kluwer Academic Publishers, Oct. 25, 1991. |
Gardner, R. et al., “Real Time Data Acquisition: Recommendations for the Medical Information Bus (MIB),” Kluwer Academic Publishers, Dec. 16, 1991. |
Kampmann, J. et al., “Connection of Electronic Medical Devices in ICU According to the Standard “MIB,”” International Journal of Clinical Monitoring and Computing 8: 163-166, 1991. |
Kampmann, K. et al., “Application of the Ideas of SMDC (IEEE p. 1073) Pertaining to the Project “ALODIN/MCARE” and a Medical Device of the Urine Collection Class,” Proceedings of the Annual International Conference of the IEEE and Biology Society: 2438-2439, 1992. |
Jean, F. et al., “Distribution and Communication in Software Engineering Environments. Application to the Helios Software Bus,” AMIA, Inc. 1992. |
Echelon Networking Contol,: IEE Review, Oct. 1992. |
Howarth, M. “Youv'e Got to Have HART,” Assembly Automation, 1992. |
Stryker, “MPS Acute Care Bed—Model 3000—the First Truly Modular Patient System,” Nov. 1993. |
Stryker, “Modular Patient System (MPS) 3000 Bed—Maintenance Manual,” Oct. 1993. |
Stryker, “Modular Patient Systems (MPS) 3000 Bed—Operations Manual,” Jul. 1983. |
Toncich, D., “Data Communications and Networking for Manufacturing Industries,” Chrystobel Engineering, 1993. |
“CAN in Automation—International Users' and Manufacturers' Group,” CAN in Automation, Mar. 1992. |
Wilson, R., “Chips Push CAN Bus into Embedded World,” Electronic Engineering Times, Aug. 24, 1992. |
Curran, P. et al., “An Approach to Verifying Concurrent Systems—A Medical Information Bus (MIB) Case Study,” Fifth Annual IEEE Symposium on Computer-Based Medical Systems: 74-83, Jun. 1992. |
Van Woerden, J.A., “A Safe and Easy to Use Integrated Control and Communication Method, M3S,” IOS Press, 1993. |
Upender, B., “Embedded Communication Protocol Options,” Proceedings of the Fifth Annual Embedded System Conference—vol. 2, 1993. |
Jordan, J.R., “Transducer Interconnection with a Standard Fieldbus,” Strain, Nov. 1993. |
Dorf(ed.), R., “Data Acquisition,” The Electrical Engineering Handbook: 1799-1807, 1993. |
Salvador, C.H. et al., “An Implementation of the IEEE Medical Information Bus Standard,” IEEE Engineering in Medicine and Biology, vol. 12, No. 2, 81-88, Jun. 1993. |
Nelisse, M.W., “M3S, A Can System for Wheelchairs,” CAN Newsletter, Apr. 1994. |
Van Woerden, J.A. et al., “M3S—A Standard Communication Architecture for Rehabilitation Applications,” Computing & Control Engineering Journal, Oct. 1994. |
Cordonnier, C. et al., “Highly Integrated Cost-Effective CAN,” CAN in Automation, 1994. |
Kennelly, R.J. et al., “New IEEE Standard Enables Data Collection for Medical Applications,” Proceedings of the 18th Annual Symposium on Computer Applications in Medical Care: 531-535, 1994. |
Embacher, M., “DC Motor Control in Vehicle Body Applications as a Practical Example of a Cost Competitive CAN Networking Solution,” CAN in Automation, 1994. |
Karkkainen, P. et al., “SLIO Based Data Acquisition in Testing Brakes of Trucks,” CAN in Automation, 1994. |
Waizmann, G. et al., “CAN-base for New Applications in Vehicles,” CAN in Automation, 1994. |
Ligier, Y. et al., “Object-Oriented Design of Medical Imaging Software,” Computerized Medical Imaging and Graphics, vol. 18, No. 2, 125-135, 1994. |
Mitisuishi, M. et al., “Development of an Inter-World Tele-Micro-Surgery System with Operational Environment Information Transmission Capability,” Proceedings of the 1995 IEEE International Conference on Robotics and Automation: 3081-3088, May 1995. |
Lawrenz, W., “Worldwide Status of CAN—Present and Future.” CAN in Automation, 1995. |
Stock, M., “CAN in Flight Simulators,” CAN in Automation, 1995. |
Cooper, R., “Intelligent Control of Power Wheelchairs,” IEEE Engineering in Medicine and Biology, Jul./Aug. 1995. |
Baribaud, G. et al., “Recommendations for the Use of Fieldbuses at CERN,” European Organization for Nuclear Research, Jun. 26, 1996. |
Kiencke, U., “CAN, A Ten Years' Anniversarial Review,” CAN in Automation, Oct. 1996. |
“CANopen Communication Profile for Industrial Systems,” CAN in Automation, Oct. 30, 1996. |
Dean, A. et al., “The Pitfalls of Embedded Communication Networks,” Electronic Engineering Times—India, Sep. 1997. |
Bartle, E., “All Together Now,” IEE Review, Sep. 1998. |
Buhler, C. et al., “Modular Architecture for Wheelchairs with Environment Integration Capabilities,” IOS Press, 1999. |
“CANopen Application Layer and Communication Profile,” CAN in Automation, Jun. 16, 1999. |
Beattie, P., “The Design and Implementation of a Focused Stochastic Diffusion Network to Solve the Self-Localisation Problem on an Autonomous Wheelchair,” The University of Reading, Jul. 2000. |
Zeltwanger, H., “State-of-the-Art CAN Applications and Future Requirements,” CAN in Automation, Oct. 2000. |
Schafmayer, A. et al., “The Process-Optimized Operating Room-Implementation of an Integrated or System into Clinical Routine,” Electromedica, 2002. |
Strkyer, Stryker Epic II Model 2030/2031 Maintenance Manual, Rev. A, May 2000. |
Stryker, Stryker Epic II Model 2030/2031 Maintenance Manual, Rev.—, Oct. 2000. |
Stryker, Stryker Epic II Model 2030/2031 Operations Manual, Rev. F, Oct. 2000. |
Stryker, “Stryker Go Bed Maintenance Manual,” Dec. 2000. |
Stryker, “Stryker Go Bed Operations Manual,” Dec. 2000. |
Stryker, “Stryker Epic II Model 2030-2031 Maintenance Manual, Rev. A,” May 2001. |
Stryker, “Stryker Epic II Model 2030/2031 Maintenance Manual, Rev.—,,” Sep. 2001. |
Loy, D. et al., “Open Control Networks, LonWorks EIA/709 Technology,” Kluwer Academic Publishers, 2001. |
Noury, N. et al., “The Telemedicine Home Care Station: a Model and some Technical Hints,” Healthcomm 2001. |
Gruhler, G. et al., “Preparation Document for a CANopen Device Profile for Medical Components,” Siemens AG, Erlagen Medical Solutions, Division CO, May 2002. |
Corrigan, S., “Introduction to the Controller Area Network (CAN),” Texas Instruments, Aug. 2002. |
Siemens, “CiA SiG Medical Devices,”. |
Gardner, R. et al., “Patient Monitoring Systems,” Biomedical Informatics, Shortliffe, 2002. |
Hill-Rom, 1993 Service Manual Advance 1000/2000, 1993. |
Hill-Rom, 1994 Service Manual, Advance 2000, 1994. |
US District Court Civil Docket, for Hill-Rom Services, Inc. et al., v. Stryker Corporation er al., 1:11cv1120, 26 pages. |
Eushian Tran, “Multi-Bit Error Vulnerabilities in the Controller Area Network Protocol,” Carnegie Mellon University, Pittsburgh, PA, May 1999. |
Pazul, K., “Controller Area Network (CAN) Basics,” Microchip Technology, Inc., 1999. |
A product service manual, published in Jan. 2001 by Hill-Rom, for the TotalCare Bed System. |
H. Zeltwanger, “Designing Devices Using Can and CANopen Buses for Networking,” Fall 1999. |
CAN in Automation, “Can Technology in Embedded Networks,” Sep. 17, 1999. |
H. Zeltwanger, “Controller Area Network and CANopen Medical Equipment,” Jun. 2002. |
Philips, “Application of the P8xC592 microcontroller with Can-interface,” Jul. 2, 1992. |
Z. Stare, et al., “Automatic Data Acquisition and Control System,” 1995. |
Robert Bosch GmbH “BOSCH CAN Specification Version 2.0,” 1991. |
M. Nelisse, “A General-Purpose Integrated and Modular Architecture for the Rehabilitation Environment,” 1995. |
K. Etschberger, “Controller Area Network-Basics, Protocols, Chips and Applications,” 2001. |
U. Kiencke, “Controller Area Network—from Concept to Reality,” 1994. |
G. Schickhuber and O. McCarthy, “Distributed Fieldbus and Control Network Systems,” Feb. 1997. |
CAN in Automation, “Can Basic Knowledge,” Jul. 2, 2001. |
W. Lawrenz, “CAN System Engineering-From Theory to Practical Applications,” 1997. |
Request for Inter Partes Reexamination for 7,506,390, 775 Pages. |
Transmittal of Communication to Third Party Requester Inter Partes Reexamination, Order Granting/Denying Request for Inter Partes Reexamination, dated Sep. 19, 2012 for Reexamination Control No. 95002053; Patent No. 7,506,390, 107 pages. |
Transmittal of Communication to Third Party Requester Inter Partes Reexamination, Office Action in Inter Partes Reexamination, dated Sep. 19, 2012 for Reexamination Control No. 95002053; Patent No. 7,506,390, 34 pages. |
Amendment and Response to Inter Partes Reexamination Office Action, dated Sep. 19, 2012 for Reexamination Control No. 95002053; Patent No. 7,506,390 filed Nov. 14, 2012, 54 pages. |
Request for Inter Partes Reexamination for 7,520,006, 1910 Pages. |
Transmittal of Communication to Third Party Requester Inter Partes Reexamination, Order Granting/Denying Request for Inter Partes Reexamination, dated Sep. 13, 2012 for Reexamination Control No. 95002054; Patent No. 7,520,006, 9 pages. |
Transmittal of Communication to Third Party Requester Inter Partes Reexamination, Office Action in Inter Partes Reexamination, dated Sep. 19, 2012 for Reexamination Control No. 95002054; Patent No. 7,506,006, 9 pages. |
Amendment and Response to Inter Partes Reexamination Office Action, dated Sep. 13, 2012 for Reexamination Control No. 95002054; Patent No. 7,520,006 filed Nov. 14, 2012, 53 pages. |
Request for Inter Partes Reexamination for 7,699,263, 1457 Pages. |
Transmittal of Communication to Third Party Requester Inter Partes Reexamination, Order Granting/Denying Request for Inter Partes Reexamination, dated Sep. 27, 2012 for Reexamination Control No. 95002055; Patent No. 7,699,263, 41 pages. |
Transmittal of Communication to Third Party Requester Inter Partes Reexamination, Office Action in Inter Partes Reexamination dated Sep. 27, 2012 for Reexamination Control No. 95002055; Patent No. 7,699,263, 40 pages. |
Amendment and Response to Inter Partes Reexamination Office Action, dated Sep. 27, 2012 for Reexamination Control No. 95002055; Patent No. 7,699,263 filed Nov. 14, 2012, 49 pages. |
Rule 132 Declaration of Steven A. Dixon (along with Exhibits); 95/002,053;7,506,390, 19 pages. |
Rule 132 Declaration of Dr. Joao P. Hespanha (along with Exhibits) 95/002,053; 7,506,390, 27 pages. |
Rule 131 Declaration of William A. Morrison (along with Exhibits) 95/002,053; 7,506,39015 pages, plus exhibits 1-13. |
Rule 132 Declaration of Steven A. Dixon (along with Exhibits); 95/002,054; 7,520,006; 18 pages. |
Rule 132 Declaration of Dr. Joao P. Hespanha (along with Exhibits) 95/002,054; 7,520,006. |
Rule 131 Declaration of William A. Morrison (along with Exhibits) 95/002,054; 7,520,006. |
Rule 132 Declaration of Steven A. Dixon (along with Exhibits); 95/002,055;7,669,263. |
Rule 132 Declaration of Dr. Joao P. Hespanha (along with Exhibits) 95/002,055; 7,669,263. |
Rule 131 Declaration of William A. Morrison (along with Exhibits) 95/002,055; 7,669,263. |
Extended European Search Report for application No. 10179902.1 dated Feb. 6, 2013. |
Supplementary European Search Report from EP 03 75 9227 dated Jul. 9, 2009. |
Prior Art emme3 Bed Brochure-purported by Defendants to have been published circa Mar. 1996 (“emme3 Bed Brochure Italian”). |
Prior Art emme3 Bed Brochure-purported by Defendants to have been published circa May 1997 (“emme3 Bed Brochure English”). |
Prior Art emme3 Instructions for Use-purported by Defendants to have been published circa Mar. 1998 (emme3 Instructions). |
Complaint (filed Jun. 17, 2010 by Plaintiffs-Hill-Rom-Inc-Hill-Rom Services and Hill-Rom Company). |
Answer and Counterclaims of Defendants Huntleigh Healthcare LLC and Huntleigh Healthcare-Inc-To the Complaint of Hill-Rom-Inc.-Hil-Rom Services-Inc.-And Hill-Rom Company-Inc-(filed Aug. 5, 2010 by Defendants Huntleigh Healthcare LLC and Huntleigh Healthcare-Inc.). |
Reply to Counterclaims (filed Aug. 16, 2010 by Plaintiffs-Hill-Rom-Inc-Hill-Rom Services and Hill-Rom Company). |
Plaintiff Hill-Rom'S First Set of Interrogatories to Defendant (filed Sep. 17, 2010 by Plaintiffs-Hill-Rom-Inc-Hill-Rom Services and Hill-Rom Company). |
Plaintiff Hill-Rom's First Request for the Production of Documents and Things to Defendant Huntleigh (filed Sep. 17, 2010 by Plaintiffs-Hill-Rom-Inc-Hill-Rom Services and Hill-Rom Company). |
Huntleigh Healthcare LLC's First Request to Hill-Rom Services-Inc-For Production of Documents and Things (filed Sep. 22, 2010 by Defendants Huntleigh Healthcare LLC and Huntleigh Healthcare-Inc.). |
Huntleigh Healthcare LLC's First Request to Hill-Rom Company-Inc-For Production of Documents and Things (filed Sep. 22, 2010 by Defendants Huntleigh Healthcare LLC and Huntleigh Healthcare-Inc.). |
Huntleigh Healthcare LLC's First Request to Hill-Rom-Inc-For Production of Documents and Things (filed Sep. 22, 2010 by Defendants Huntleigh Healthcare LLC and Huntleigh Healthcare-Inc.). |
Defendant Hunteligh Healthcare LLC's First Set of Interrogatories (Nos. 1-11) to Plaintiff Hill-Rom Company-Inc-(filed Sep. 22, 2010 by Defendants Huntleigh Healthcare LLC and Huntleigh Healthcare-Inc.). |
Defendant Hungleigh Healthcare LLC's First Set of Interrogatories (Nos. 1-11) to Plaintiff Hill-Rom Services-Inc-(filed Sep. 22, 2010 by Defendants Huntleigh Healthcare LLC and Huntleigh Healthcare-Inc.). |
Defenant Huntleigh Healthcare LLC's First Set of Interrogatories (Nos. 1-11) to Plaintiff Hill-Rom-Inc-(filed Sep. 22, 2010 by Defendants Huntleigh Healthcare LLC and Huntleigh Healthcare-Inc.). |
Hill-Rom'S Initial Disclosures (filed Sep. 30, 2010 by Plaintiffs-Hill-Rom-Inc-Hill-Rom Services and Hill-Rom Company). |
Initial Disclosures for Defendants Huntleigh Healthcare LLC-and Huntleigh Healthcareinc-(filed Sep. 30, 2010 by Defendants Huntleigh Healthcare LLC and Huntleigh Healthcare-Inc.). |
Case Management Plan Order (filed Nov. 5, 2010). |
Plaintiffs' Preliminary Infringement Contentions (filed Nov. 5, 2010 by Plaintiffs-Hill-Rom-Inc-Hill-Rom Services and Hill-Rom Company). |
Responses and Objections of Defendants Huntleigh Healthcare LLC and Huntleigh Healthcare Inc-To Plaintiff Hil-Rom's First Set of Interrogatories (1-5) (filed Nov. 18, 2010 by Defendants Huntleigh Healthcare LLC and Huntleigh Healthcare-Inc.). |
Plaintiffs Hill-Rom-Inc.'s Hill-Rom Services-Inc.'s and Hill-Rom Company-Inc.'s Consolidated Answers and Objections to Defendant Huntleigh Healthcare LLC's First Set of Interrogatories (Nos. 1-11) (filed Nov. 22, 2010 by Plaintiffs-Hill-Rom-Inc-Hill-Rom Services and Hill-Rom Company). |
Plainitffs Hill-Rom-Inc.'s-Hill-Rom Services-Inc.'s and Hill-Rom Company-Inc.'s Consolidated Responses and Objections to Defendant Hunteligh Healthcare LLC's First Request for Production of Documents and Things (filed Nov. 22, 2010 by PlaintiffsHill-Rom-Inc-Hill-Rom Services and Hill-Rom Company). |
Defendants' Preliminary Invalidity Contentions (filed Dec. 22, 2010 by Defendants Huntleigh Healthcare LLC and Huntleigh Healthcare-Inc.)—Exhibits A-H. |
Responses and Objections of Defendants Huntleigh Healthcare LLC and Huntleigh Healthcare Inc-To Plaintiff Hil-Rom'S First Request for Documents and Things (filed Nov. 18, 2010 by Defendants Huntleigh Healthcare LLC and Huntleigh Healthcare-Inc.). |
European Search Report dated Jul. 24, 2008 (11 pages). |
Supplementary European Search Report dated Jul. 9, 2009 (2 pages). |
Akrotech 4000 Brochure, Lumex, 1992. |
“Impression” Brochure, Kinetic Concepts, Inc., Aug. 1996. |
Stryker Medical GO BED.TM. brochure, 2 pgs., 2001. |
Hill-Rom Med Surg Bed Accessories brochure, 1998 (6 pgs.). |
Extended European Search Report for application No. 10075016.5, dated Nov. 7, 2012. |
Minute Order for proceedings held before Judge Jane Magnus-Stinson—on Oct. 31, 2012, the Court held a Markman hearing on the parties' proposed claim construction on six of the patentsin-suit. [Dkts. 124 ; 125 ; 131 ; 132 .] Both parties were present by counsel. The Court heard oral argument and took the matter Under Advisement. Pursuant the Court's order at the hearing, the parties have until Nov. 7, 2012 to file a no more than five-page brief regarding the application of judicial estoppel in the context addressed at the hearing. Signed by Judge Jane Magnus-Stinson. (Court Reporter Jean Knepley.)(JKS) (Entered: Nov. 1, 2012). |
Rule 132 Declaration of Michael J. Hayes, 95/002053 dated Dec. 11, 2012, 9 pages. |
Rule 132 Declaration of Michael J. Hayes, 95/002054, dated Dec. 11, 2012, 9 pages. |
Rule 132 Declaration of Michael J. Hayes, 95/002055, dated Dec. 11, 2012, 9 pages. |
Rule 132 Declaration of Philip Koopman, 95/002053, (with Exhibits) dated Dec. 11, 2012, 45 pages. |
Brief/Memorandum in Support re 124 Initial Markman/Claim Construction Brief by Stryker Corporation, Stryker Sales Corporation Stryker's Memorandum Regarding the Doctrine of Judicial Estoppel, filed by Counter Claimants Stryker Corporation, Stryker Sales Corporation, Defendants Stryker Corporation, Stryker Sales Corporation. (Derringer, Steven) (Entered: Nov. 7, 2012). |
Rule 132 Declaration of Philip Koopman, 95/002054, (with Exhibits) dated Dec. 11, 2012, 45 pages. |
Rule 132 Declaration of Philip Koopman, 95/002055, (with Exhibits) dated Dec. 11, 2012, 45 pages. |
Rule 132 Declaration of C. Douglass Locke, 95/002050, (with Exhibits) dated Dec. 17, 2012, 12 pages. |
US District Court Civil Docket, 1:11cv1120, Hill-Rom Services, Inc. et al v. Stryker Corporation et al dated Jan. 8, 2013, 26 pages. |
Third Party Stryker'S Comments Addressing Issues Raised by Sep. 19, 2012 Office Action and Patent Owner's Nov. 14, 2012 Response, 95/002053, Dec. 14, 2012, 40 pages. |
Third Party Stryker'S Comments Addressing Issues Raised by Sep. 13, 2012 Office Action and Patent Owner's Nov. 13, 2012 Response, 95/002054, Dec. 13, 2012, 41 pages. |
Third Party Stryker's Comments Addressing Issues Raised by Sep. 27, 2012 Office Action and Patent Owner's Nov. 16, 2012 Response, 95/002055, Dec. 17, 2012, 57 pages. |
Brief/Memorandum in Support re 125 Initial Markman/Claim Construction Brief by Hill-Rom Company, Inc., Hill-Rom Manufacturing, Inc., Hill-Rom Services, Inc. , filed by Plaintiffs Hill-Rom Company, Inc., Hill-Rom Manufacturing, Inc., Hill-Rom Services, Inc., Counter Defendants Hill-Rom Company, Inc., Hill-Rom Manufacturing, Inc., Hill-Rom Services, Inc . . . (Attachments: # 1 Exhibit A—Appeal Brief excerpts, # 2 Exhibit B—Declaration) (Callahan, David) (Entered: Nov. 7, 2012). |
US District Court Civil Docket, 1:11cv1120, Hill-Rom Services, Inc. et al v. Stryker Corporation et al dated Jul. 19, 2013, 28 pages. |
US District Court Civil Docket, 1:13cv00765, Hill-Rom Services, Inc. et al v. Stryker Corporation et al dated Jul. 19, 2013, 16 pages. |
US District Court Civil Docket, 1:13cv00765, Hill-Rom Services, Inc. et al v. Stryker Corporation et al dated Sep. 13, 2013, 16 pages. |
Order Hill-Rom Services, Inc. et al v. Stryker Corporation et al. Signed by Judge Jane Magnus-Stinson on May 9, 2013. |
Complaint Hill-Rom Services, Inc. et al v. Stryker Corporation et al. (Entered: May 9, 2013). |
Defendant Stryker's First Amended Answer, Affirmative Defenses And Counterclaims To Plaintiff Hill-Rom's Complaint, entered May 9, 2013. |
Order Granting Motion for Partial Stay, Signed by Judge Jane Magnus-Stinson on Nov. 20, 2012. (Entered: May 9, 2013). |
Notice, Consent, And Reference Of A Civil Action To Magistrate Judge, Entered: May 10, 2013). |
Order Hill-Rom Services, Inc. et al v. Stryker Corporation et al. Signed by Judge Jane Magnus-Stinson on May 10, 2013. (Entered: May 10, 2013). |
Report on the Filing or Determination of an Action Regarding a Patent or Trademark, Signed by Judge Jane Magnus-Stinson on May 9, 2013. (Entered: May 13, 2013). |
Report on the Filing or Determination of an Action Regarding a Patent or Trademark, Signed by Judge Jane Magnus-Stinson on May 10, 2013. (Entered: May 13, 2013). |
Office Action for U.S. Appl. No. 95/002,053 dated Sep. 6, 2013. |
Third Party Stryker's Comments for U.S. Appl. No. 95/002,054 dated Aug. 9, 2013. |
Declaration of Michael J. Hayes for U.S. Appl. No. 95/002,054 dated Aug. 8, 2013. |
Declaration of Philip Koopman for U.S. Appl. No. 95/002,054 dated Aug. 8, 2013. |
Gaid, M. Ben, Arben Cela, and Rémy Kocik. “Distributed control of a car suspension system.” COSI-EEIEE-Cite Descartes, Noisy-Le-Grand Cedex (2004). |
Koopman, Philip. “Critical embedded automotive networks.” IEEE Micro (2002): 14-18. |
Klein, Mark H., John P. Lehoczky, and Ragunathan Rajkumar. “Rate-monotonic analysis for real-time industrial computing.” Computer 27.1 (1994): 24-33. |
Tindell, Ken. “Deadline Monotonic Analysis This article presents a technique for analyzing worst-case response times of tasks in a system and shows how the results of this analysis can be used to ensure the proper timing behavior of a system.” Embedded Systems Programming 13.6 (2000): 20-38. |
US District Court Civil Docket, for Hill-Rom Services, Inc. et al., v. Stryker Corporation et al., 1:11cv1120, 26 pages. |
Farsi et al., An Overview of Controller Area Network, Jun. 1999, Computing & Control Engineering Journal, pp. 113-120. |
Prof. Dr.-Ing. K. Etschberger, 5.2 CANopen, 5 Higher Layer Protocols and Profiles, pp. 201-202, 255-263, 266-269, 327-328 (2001) [ISBN 3-00-007376-0]. |
Device Net TM Technical Overview, ODVA—Open DeviceNet Vendor Association, Inc., pp. VI-XXI (1999). |
Koelmans, A., et al., “Proceedings of the First UK Embedded Forum,” University of Newcastle Upon Tyne, 2004, 195 pages. |
Negley, Bruce, “Getting Control Through CAN,” Sensors, Networking and Communications, Oct. 1, 2000, 6 pages. |
Nahas, Mouaaz, et al., “The impact of bit stuffing on the real-time performance of a distributed control system,” CAN in Automation, 2005, 7 pages. |
147. Order. Signed by Judge Jane Magnus-Stinson on Jan. 30, 2013. (JKS) (Entered: Jan. 30, 2013). |
US District Court Civil Docket, 1:11cv1120, Hill-Rom Services, Inc. et al v. Stryker Corporation et al dated Feb. 8, 2013, 26 pages. |
Buehring, Peter, and Peter Hank. “Application of the P8xC592 microcontroller with CAN-interface.” Philips Semiconductor, AN91014 Application Note (1992). |
Tsang, Peter WM, and Raymond WC Wang. “Development of a distributive lighting control system using local operating network.” Consumer Electronics, IEEE Transactions on 40.4 (1994): 879-889. |
Order granting 115 Motion for Partial Stay—This Court Grants Stryker's motion for a partial stay pending reexamination by the PTO of six of the nine patents in suit. The parties are Ordered to file any decisions by the PTO on the pending petitions for reexamination within 7 days of receiving those decisions. Either party may move to lift the stay after the PTO decides all of the pending petitions for reexamination or at an earlier time if such a motion is supported by good cause. The Markman briefing on the three patents not subject to this stay remains Under Advisement and will be ruled on in due course. Signed by Judge Jane Magnus-Stinson on Nov. 20, 2012. (JKS) (Entered: Nov. 20, 2012). |
Right of Appeal Notice for U.S. Appl. No. 95/002,053 dated Sep. 6, 2013. |
Action Closing Prosecution for U.S. Appl. No. 95/002,054 dated Sep. 19, 2013. |
Appellant's Brief of Third-Party Requester Stryker Corporation Pursuant to 37 C.F.R. § 41.67, dated Nov. 19, 2014, 27 pages. |
Patent Owner Appellant Appeal Brief, dated Nov. 19, 2014, 39 pages. |
Amendment Under 37 C.F.R. 1.116(b)(2), dated Sep. 5, 2014, 6 pages. |
Office action for U.S. Appl. No. 95/002,055, Right of Appeal Notice, dated Aug. 6, 2014, 259 pages. |
Amendment after Final or Under 37 C.F.R. 1,312, initiated by the examiner, dated Aug. 6, 2014, 1 page. |
Third-Party Requester Comments after Action Closing Prosecution and Applicant Arguments/Remarks Made in an Amendment, dated Jul. 9, 2014, 39 pages. |
Patent Owner comments after Action Closing Prosecution and Applicant Arguments/Remarks made in an Amendment, dated Jun. 9, 2014, 46 pages. |
Office Action for U.S. Appl. No. 95/002,055 closing prosecution (non-final) dated May 8, 2014, 242 pages. |
Third-Party Requester comments after non-final action, dated Dec. 12, 2013, 59 pages. |
Patent Owner Response after non-final action, Claims, and Applicant Arguments/Remarks Made in an Amendment, dated Nov. 12, 2013, 11 pages. |
Reexam—Non-Final Action, dated Sep. 10, 2013, 33 pages. |
Patent Owner Appellant's Rebuttal Brief, dated Sep. 12, 2014, 15 pages. |
Examiner's Answer to Appeal Brief, dated Aug. 12, 2014, 3 pages. |
Respondent Appeal Brief of Third-Party Requester Stryker Corporation pursuant to 37 C.F.R. § 41.68, dated Apr. 21, 2014, 27 pages. |
Appeal Brief—Owner, dated Mar. 20, 2014, 211 pages. |
Right of Appeal Notice, dated Dec. 20, 2013, 32 pages. |
Action Closing Prosecution (non-final), dated Sep. 19, 2013, 31 pages. |
Third Party Requester Comments after Non-Final Action, dated Aug. 9, 2013, 36 pages. |
Owner Response after Non-Final Action—Timely, dated Jul. 10, 2013, 39 pages. |
Reexam—Non-Final Action, dated May 10, 2013, 33 pages. |
Miscellaneous Action with SSP, dated Nov. 12, 2014, 35 pages. |
Patent Board Decision—Examiner Affirmed, Oct. 14, 2014, 27 pages. |
Reply Brief Noted—Patent Board, Dated Apr. 22, 2014, 3 pages. |
Patent Owner Appellant's Rebuttal Brief, dated Mar. 19, 2014, 15 pages. |
Examiner's Answer to Appeal Brief, dated Feb. 19, 2014, 3 pages. |
Respondent Appeal Brief of Third-Party Requester Stryker, dated Jan. 6, 2014, 27 pages. |
Patent Owner Appeal Brief, dated Dec. 4, 2013, 147 pages. |
Notice of Appeal in an Inter Partes Reexamination, dated Oct. 4, 2013, 2 pages. |
Right of Appeal Notice, dated Sep. 6, 2013, 14 pages. |
Third-Party Requester Comments After Action Closing Prosecution, dated Jun. 10, 2013, 14 pgs. |
Reexam Petition Decision—Dismissed, dated May 17, 2013, 3 pages. |
Patent Owner Comments after Action Closing Prosecution, dated May 10, 2013, 12 pages. |
Action Closing Prosecution (non-final), dated Apr. 10, 2013, 56 pages. |
Number | Date | Country | |
---|---|---|---|
20120174319 A1 | Jul 2012 | US |
Number | Date | Country | |
---|---|---|---|
60173428 | Dec 1999 | US | |
60408698 | Sep 2002 | US | |
60409748 | Sep 2002 | US | |
60489171 | Jul 2003 | US | |
60490467 | Jul 2003 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 09750859 | Dec 2000 | US |
Child | 10648053 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13014140 | Jan 2011 | US |
Child | 13421407 | US | |
Parent | 12507152 | Jul 2009 | US |
Child | 13014140 | US | |
Parent | 12137619 | Jun 2008 | US |
Child | 12507152 | US | |
Parent | 11257438 | Oct 2005 | US |
Child | 12137619 | US | |
Parent | 10731720 | Dec 2003 | US |
Child | 11257438 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 09750741 | Dec 2000 | US |
Child | 10731720 | US | |
Parent | 09751031 | Dec 2000 | US |
Child | 10731720 | US | |
Parent | 10648053 | Aug 2003 | US |
Child | 09751031 | US | |
Parent | 10657696 | Sep 2003 | US |
Child | 09750859 | US |