The present invention relates broadly to wheelchairs, beds, tables, and other such person-supporting apparatuses. More specifically, the present invention concerns a vertically and angularly repositionable person-supporting apparatus, such as is used to support a bariatric patient weighing approximately between 400 and 1200 pounds, and the operation and control of such an apparatus.
Apparatuses for supporting persons, such as, for example, hospital beds for supporting bariatric patients weighing approximately between 400 and 1200 pounds, are sometimes provided with the ability to vertically reposition (i.e., raise and lower) and angularly reposition (i.e., tilt and level) portions or all of a patient support surface to facilitate repositioning or otherwise moving a patient sitting or lying thereon. Due to design constraints, vertically repositioning the patient support surface while it is in certain angular positions, or angularly repositioning the patient support surface while it is in certain vertical positions, can bring components of the apparatus into damaging contact with each another. For example, if the support surface is lowered too far when it is angled too much, it may strike a base or other component of the apparatus, and, similarly, if the support surface is angled too much when it is too low, it may strike the base or other component.
Furthermore, it can be medically or otherwise undesirable for some patients to exceed a maximum or minimum head or foot elevation while lying on such apparatuses, or to move off of such apparatuses without calling for assistance or against medical advice.
Additionally, such apparatuses may have complex onboard electronic functionality with associated software or firmware that must be periodically updated or otherwise changed. In prior art systems, performing remote updates on the apparatus' functionality could be problematic, and, if performed improperly, could render one or more functionalities or the entire system nonfunctional. One problem occurs when there is an interruption of the update process, which can render the new image incomplete and nonfunctional. One solution to this problem has been to keep two firmware images in memory and alternate firmware updates. Unfortunately, many functionalities are associated with small microcontrollers that have limited memory space that cannot accommodate two images. Another problem arises because firmware is often stored in flash memory so it is not possible to continue executing code from a block of memory while it is being updated. In some apparatuses, firmware is run from RAM memory while the flash memory is being re-written. Unfortunately, many apparatuses or particular functionalities have insufficient RAM to implement this solution.
Due to these and other concerns, a need exists for an improved patient support apparatus.
The present invention addresses the above-identified and other concerns by providing an improved patient support apparatus, which can be used, for example, to support a bariatric patient weighing approximately between 400 and 1200 pounds. In one embodiment, the patient support apparatus comprises a patient support surface; a base frame; and a repositioning mechanism extending between the patient support surface and the base frame, and operable to vertically reposition and angularly reposition the patient support surface relative to the base frame.
In various other embodiments, the apparatus may include one or more of the following additional features. The apparatus may include one or more sensors operable to automatically detect and inhibit an attempt to vertically reposition the surface when it is in a particular angular position, and to automatically detect and inhibit an attempt to angularly reposition the surface when it is in a particular vertical position. The apparatus may include a tilt control system operable to prevent raising or lowering a head or foot end of the surface beyond a minimum or maximum extent, and an input device operable to allow for specifying the minimum or maximum extent. The apparatus may include a scale operable to determine a weight on the surface, and a warning system operable to receive input from the scale, to determine changes in the weight, and to communicate a warning when a change in the weight is indicative of a patient attempting to get off of the surface. The apparatus may include one or more sensors operable to monitor an amperage used during the vertical or angular repositioning operations, and to stop the operations if a change in the amperage exceeds a particular amount for a particular time. The apparatus may include one or more microcontrollers, with each microcontroller being operable to perform a function and having updateable programming, and a controller area network bus operable to carry electronic signals between the microcontrollers and an external program update source, wherein when it is desirable to update the programming of the microcontrollers an updated program is communicated by the source to the microcontrollers via the bus.
These and other features of the present invention are discussed in greater detail in the section below entitled.
The present invention is described herein with reference to the following drawing figures, which are not necessary to scale:
With reference to the figures, a patient support apparatus 20 is herein described, shown, and otherwise disclosed in accordance with one or more embodiments of the present invention, including one or more preferred embodiments. It will be appreciated that various embodiments of patient support apparatuses operable to vertically reposition and/or angularly reposition their patient support surfaces are known. The features of the present invention may be incorporated into many or all such embodiments generally without regard to many or all differences, including, for example, how repositioning is achieved. As such, description herein of the exemplary patient support apparatus 20 is generally limited to aspects relevant to or helpful in understanding the present invention.
Referring to
The patient support surface 22 may be a substantially flat or contoured surface and may be articulated to allow for tilting one or more portions of the surface, e.g., a head portion or a foot portion 36, 38 (as shown in
The repositioning mechanism 24 extends between the patient support surface 22 and the wheel frame 26, and is operable to vertically reposition (i.e., raise and lower) and angularly reposition (i.e., tilt and level) portions or all of the patient support surface 22 relative to the wheel frame 26. Referring also to
The wheel frame 26 movably supports the repositioning mechanism 24 and the patient support surface 22, and includes several wheels, casters, or otherwise rollable members 60. In one contemplated implementation, the wheel frame 26 is approximately rectangular in overall shape with first and second end members 64, 66 and a wheel 60 at each corner.
Referring also to
Vertically repositioning the patient support surface 22 to a low or lowest elevation while the surface 22 is not level, or attempting to angularly reposition the surface 22 while the surface 22 is at the low or lowest elevation, may result in a portion of the repositioning mechanism 24 contacting the first or second end members 64, 66 or other portion of the wheel frame 26 in such a manner as to cause damage to one or both. To facilitate avoiding such damage, an embodiment of the apparatus 20 includes one or more sensors 84 operable to automatically detect the angled patient support surface 22 reaching a minimum safe height and to automatically prevent the potentially damaging condition. In one implementation, a sensor 84 is located on each of the first and second frame members 52, 54 such that, when the surface is 22 lowered to a minimum safe height, the sensors 84 are operable to determine whether the surface 22 is level and, if it is not level, to automatically initiate leveling of the surface 22 by the repositioning mechanism 24 so that damage does not occur. In one implementation, the surface 22 is completely leveled when the sensors 84 are activated. In another implementation, the surface 22 is incrementally leveled when the sensors 84 detect that the angled surface 22 is within a predetermined distance of the minimum safe height, and is only completely leveled when it reaches the minimum safe height to avoid damage—thereby allowing the bed to continue lowering as it levels. The minimum safe height will vary depending on such factors as the physical design of the repositioning mechanism 24 and the wheel frame 26. However, the minimum safe height may correspond to a portion of the repositioning mechanism 24 being within approximately 6 inches, or within approximately 1 inch, of the first or second end members 64, 66 of the wheel frame 26. Similarly, the predetermined distance from the minimum safe height may be approximately 12 inches, approximately 6 inches, or approximately between 1 inch and 6 inches. The sensors 84 may be implemented using any suitable electronic, mechanical, optical, or other mechanism. In one embodiment, string pots are used to sense the incline of the surface 22.
Referring to
Referring to
In one embodiment, the patient support apparatus 20 includes a sensor 122 (shown diagrammatically in
As the apparatus 20 begins an operation, there is a period during which the power or amperage used can be higher than the sufficiently high threshold of change in power or amperage that indicates an obstruction to the operation, so, in one embodiment, the power or amperage is not monitored during that period or, alternatively, the operation will not be stopped if the sufficiently high threshold is reached during the period. In one implementation, the period can be set by a user within a range of approximately between 1×102 milliseconds and 1 second.
In another embodiment, the sensor 122 also monitors the duration of the change in amperage, and the apparatus 20 or controller will stop the operation when the sufficiently high amperage change has occurred for a sufficiently long duration to indicate an obstruction to the operation of the apparatus 20. In various implementations, the duration of sufficiently high change in amperage is at least approximately 1 millisecond, approximately between 1 millisecond and 1 second, approximately between 1 millisecond and 0.5 second, or approximately between 5 milliseconds and 0.5 second.
Thus, in one implementation, illustrated in
In one embodiment, the apparatus 20 includes complex onboard electronic functionality, such as, for example, the above-described repositioning control system, the tilt control system 88, and the scale 92 and movement warning system, having associated software or firmware that must be periodically updated or otherwise changed. These electronic functionalities can be characterized as independent Nodes 100 which communicate with each other and with external systems via a modified controller area network (CAN) bus 102. The CAN bus 102 comprises CAN communications signals and a power bus to allow for powering the Nodes 100. The CAN bus 102 provides a number of advantages, including that it allows for a consistent communications protocol; it allows for the Nodes 100 to be implemented as simply as possible in the apparatus 20, thereby keeping overall system complexity manageable; it facilitates future feature and functionality enhancements; and it allows for systematic system verification and validation.
The present invention updates Nodes 100 within the apparatus 20 via the CAN bus 102 as follows. As shown in
The Application contains a Magic Word which is stored in a fixed location, such as, for example, a vector table, and contains a value that is not found in a normal vector table. The Magic Word is the last entry programmed, and indicates that the new Application has been programmed without errors. More specifically, the Magic Word indicates to the Boot Loader that a viable Application exists. If the Magic Word is correct, the Boot Loader can jump to the Application in two steps: (1) load the correct stack pointer values from a fixed location in the vector table, and (2) jump to a Reset vector which is also located in a fixed location in the vector table. These are the same actions that the Node's microcontroller would otherwise follow during a power-up boot sequence. The Flash Loader is part of the Boot Loader and receives data via the CAN bus 102 and programs the corresponding memory locations in the flash memory.
In one implementation, only one Node 100 can be programmed at a time. In order to avoid interruptions due to other traffic on the CAN bus 102, a CAN mailbox is reserved and is only defined and used when an update is occurring. An Updater Host CAN update mailbox is also created.
In an exemplary application, the updating process may include the following steps. The Boot Loader starts when the system is reset or when called by the Application. Broadly, the Boot Loader initiates the Flash Loader and checks the Magic Word, and, if it is correct, jumps to the Application. More specifically, the Flash Loader erases the Application flash memory, and tells the Updater Host 104 to begin sending update data. The Flash Loader receives bytes via the CAN bus 102 and decodes them to memory locations and values, depending on the data file format stored on the Updater Host 104, until an end-of-file indicator is received. A checksum is calculated and compared with an expected value to check for errors. Once the program is verified to be error-free, the Magic Word is programmed. The Magic Word indicates to the Boot Loader that a good Application resides in flash memory, and the Boot Loader jumps to the Application.
In addition to the functionality required for the Node's firmware, the Node 100 must also be able to jump back to the Boot Loader when the update command is received when the Application is active. The response is issued within the Boot Loader and allows for time to erase the Application flash memory.
The Updater Host 104 opens the data file for the Node 100 to be updated, and sends the update command to the Node 100. When the update command is received, the Node 100 jumps to the Boot Loader and waits for a response. The Node 100 erases flash memory and sets up a Flash Loader mailbox address. The Updater Host 104 reads the data file and builds data packets. The Node 100 reads the data, decodes the memory address and the data packets, and programs the data locations in the firmware.
If the updating process is interrupted, the application will be incomplete and the Magic Word will be incorrect. If there is a flash programming error or a flash erase error, the checksum will not be correct and the Magic Word will not be programmed. Both cases may result in the Node 100 being reset and a new attempt being initiated to update via the Updater Host 104. If the Application has an error which does not allow the Flash Loader to be executed, no update command will be given. In this case, the Node 100 may be reset and reprogrammed before the Boot Loader jumps to the Application. If the Node Boot Loader becomes corrupted, no update command will be given. In this case, the Boot Loader may be reprogrammed.
Although the invention has been disclosed with reference to various embodiments, implementations, and applications, it is understood that equivalents may be employed and substitutions made without departing from the contemplated scope of the invention.
Having thus described the preferred embodiment of the invention, what is claimed as new and desired to be protected by Letters Patent includes the following:
The present non-provisional patent application is a divisional of application Ser. No. 13/771,820, filed Feb. 20, 2013, titled AUTO LEVELING LOW PROFILE PATIENT SUPPORT APPARATUS, now U.S. Pat. No. 10,123,923 which claims priority of an earlier-filed provisional patent application titled AUTO LEVELING LOW PROFILE PATIENT SUPPORT, Ser. No. 61/601,303, filed Feb. 21, 2012. The contents of the identified earlier-filed application are hereby incorporated by reference into the present application.
Number | Name | Date | Kind |
---|---|---|---|
4908844 | Hasegawa | Mar 1990 | A |
5205004 | Hayes et al. | Apr 1993 | A |
5235258 | Schuerch | Aug 1993 | A |
5317769 | Weismiller et al. | Jun 1994 | A |
5664270 | Bell et al. | Sep 1997 | A |
5697110 | Campbell | Dec 1997 | A |
5708993 | Campbell | Jan 1998 | A |
5715548 | Weismiller et al. | Feb 1998 | A |
5771511 | Kummer et al. | Jun 1998 | A |
6353949 | Falbo | Mar 2002 | B1 |
7003828 | Roussy | Feb 2006 | B2 |
7038588 | Boone et al. | May 2006 | B2 |
7154397 | Zerhusen et al. | Dec 2006 | B2 |
7208896 | Ford et al. | Apr 2007 | B2 |
7472437 | Riley | Jan 2009 | B2 |
7834768 | Dixon | Nov 2010 | B2 |
8039766 | Flanagan | Oct 2011 | B2 |
8280748 | Allen et al. | Oct 2012 | B2 |
8689376 | Becker | Apr 2014 | B2 |
8834237 | Van Hillo | Sep 2014 | B2 |
20020059679 | Weismiller | May 2002 | A1 |
20040163175 | Vogel | Aug 2004 | A1 |
20040177445 | Osborne et al. | Sep 2004 | A1 |
20050172405 | Menkedick | Aug 2005 | A1 |
20060010601 | Riley | Jan 2006 | A1 |
20070157385 | Lemire et al. | Jul 2007 | A1 |
20070163043 | Lemire et al. | Jul 2007 | A1 |
20070174965 | Lemire et al. | Aug 2007 | A1 |
20070296600 | Dixon et al. | Dec 2007 | A1 |
20080092291 | Rawls-Meehan | Apr 2008 | A1 |
20080148485 | Barthelt | Jun 2008 | A1 |
20080235872 | Newkirk et al. | Oct 2008 | A1 |
20080289108 | Menkedick | Nov 2008 | A1 |
20090044334 | Parsell et al. | Feb 2009 | A1 |
20090100599 | Rawls-Meehan | Apr 2009 | A1 |
20100132231 | Kozel et al. | Jun 2010 | A1 |
20110115635 | Petrovski et al. | May 2011 | A1 |
20120060290 | Jones | Mar 2012 | A1 |
20120138067 | Rawls-Meehan | Jun 2012 | A1 |
20120174314 | Clement | Jul 2012 | A1 |
20120317726 | Riley | Dec 2012 | A1 |
20130340165 | Dong | Dec 2013 | A1 |
Number | Date | Country | |
---|---|---|---|
20190046377 A1 | Feb 2019 | US |
Number | Date | Country | |
---|---|---|---|
61601303 | Feb 2012 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13771820 | Feb 2013 | US |
Child | 16164259 | US |