초록 ▼

A hospital bed has a bed frame and communication circuitry operable to transmit bed status data to a network of a healthcare facility and to receive messages from the network. The messages include information indicating whether bed status conditions are being monitored by a remote computer of the ne

A hospital bed has a bed frame and communication circuitry operable to transmit bed status data to a network of a healthcare facility and to receive messages from the network. The messages include information indicating whether bed status conditions are being monitored by a remote computer of the network for generation of alert messages to at least one caregiver in response to alert conditions being indicated by the bed status data. The bed has at least one user input that is used locally at the bed to enable and suspend monitoring of the bed status conditions by the remote computer.

대표청구항 ▼

1. A hospital bed having a bed frame and communication circuitry that is operable upon power up of the hospital bed to determine if a static Internet Protocol (IP) address is present and if the static IP address is not present, to attempt to get an IP address using a Dynamic Host Configuration Proto

1. A hospital bed having a bed frame and communication circuitry that is operable upon power up of the hospital bed to determine if a static Internet Protocol (IP) address is present and if the static IP address is not present, to attempt to get an IP address using a Dynamic Host Configuration Protocol (DHCP). 2. The hospital bed of claim 1, wherein the communication circuitry is operable upon receipt of a state machine reset of the hospital bed to determine if the static Internet Protocol (IP) address is present and if the static IP address is not present, to attempt to get the IP address using the Dynamic Host Configuration Protocol (DHCP). 3. The hospital bed of claim 1, wherein the communication circuitry is configured to determine whether a default startup has occurred and if so, to communicate using default parameters. 4. The hospital bed of claim 3, wherein the communication circuitry determines if the static IP address is present after determining that a default startup has not occurred. 5. The hospital bed of claim 1, wherein if the attempt to get an IP address using the DHCP was not successful, the communication circuitry enters into a safe mode during which further algorithm execution is delayed for a period of time. 6. The hospital bed of claim 5, wherein the period of time is randomly established. 7. The hospital bed of claim 6, wherein the randomly established period of time is between 5 to 10 seconds. 8. The hospital bed of claim 5, wherein, after the period of time, the communication circuitry is operable to determine if a fatal error has occurred. 9. The hospital bed of claim 8, wherein if the communication circuitry determines that a fatal error has occurred, the communication circuitry proceeds to an offline mode. 10. The hospital bed of claim 8, wherein if the communication circuitry determines that a fatal error has not occurred, the communication circuitry proceeds to a link mode and sends a new endpoint message. 11. The hospital bed of claim 10, wherein in the link mode the communication circuitry also sends a process file message and an inputs mask and initial data message. 12. The hospital bed of claim 11, wherein in the link mode the communication circuitry also receives a request configuration message and a file processed message. 13. The hospital bed of claim 12, wherein the communication circuitry is operable to determine if the endpoint message, the process file message, and the inputs mask and initial data message were successfully sent and if the request configuration message and the file processed message were safely received. 14. The hospital bed of claim 13, wherein if the endpoint message, the process file message, and the inputs mask and initial data message were successfully sent and if the request configuration message and the file processed message were safely received, then the communication circuitry sends a heartbeat message. 15. The hospital bed of claim 14, wherein the heartbeat message comprises a copyright notice. 16. The hospital bed of claim 15, wherein the copyright notice comprises a company name and a year. 17. The hospital bed of claim 1, after determining that the static IP address is present or after getting the IP address suing the DHCP, the communication circuitry proceeds to a link mode and sends a new endpoint message. 18. The hospital bed of claim 17, wherein in the link mode the communication circuitry also sends a process file message, receives a request configuration message, sends an inputs mask and initial data message, and receives a file processed message. 19. The hospital bed of claim 18, wherein the communication circuitry is operable to determine if the endpoint message, the process file message, and the inputs mask and initial data message were successfully sent and if the request configuration message and the file processed message were safely received. 20. The hospital bed of claim 19, wherein if the endpoint message, the process file message, and the inputs mask and initial data message were successfully sent and if the request configuration message and the file processed message were safely received, then the communication circuitry sends a heartbeat message.