HOSPITAL BED HAVING USER INPUT TO ENABLE AND SUSPEND REMOTE MONITORING OF ALERT CONDITIONS

• US 20140091913A1
• Filed: 12/06/2013
• Published: 04/03/2014
• Est. Priority Date: 08/02/2004
• Status: Active Grant

• Current Assignee: Hill-Rom Services Incorporated (Baxter International Inc.)
• Original Assignee: Hill-Rom Services Incorporated (Baxter International Inc.)
• Inventors: Collins, Williams F. Jr., Huster, Keith A., Riley, Carl W., Glidewell, Patricia A., Vanderpohl, Irvin J. III, Schuman, Richard J., Wildman, Timothy D., Allwn, James M., Howell, Benjamin E.
• Granted Patent: US 8,917,166 B2
• Time in Patent Office: Days
• US Class Current: 340/286.07
• CPC Class Codes: A61B 5/002 Monitoring the patient using a local or closed circuit, e.g. in a room or building A61B5/0017 takes precedence
• CPC Class Codes: A61B 5/024 Detecting, measuring or recording pulse rate or heart rate A61B5/0205, A61B5/021 take precedence
• CPC Class Codes: A61B 5/1115 Monitoring leaving of a patient support, e.g. a bed or a wheelchair
• CPC Class Codes: A61B 5/1117 Fall detection
• CPC Class Codes: A61B 5/447 specially adapted for aiding the prevention of ulcer or pressure sore development, i.e. before the ulcer or sore has developed
• CPC Class Codes: A61B 5/746 Alarms related to a physiological condition, e.g. details of setting alarm thresholds or avoiding false alarms alarms per se G08B
• CPC Class Codes: A61G 12/00 Accommodation for nursing, e.g. in hospitals, not covered by groups A61G1/00 - A61G11/00, e.g. trolleys for transport of medicaments or food service or tea-tables, trolleys or wagons A47B31/00; Prescription lists
• CPC Class Codes: A61G 7/018 Control or drive mechanisms
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G07C 3/00 Registering or indicating the condition or the working of machines or other apparatus, other than vehicles
• CPC Class Codes: G08B 21/22 responsive to presence or absence of persons
• CPC Class Codes: G08B 5/22 using electric transmission; using electromagnetic transmission
• CPC Class Codes: G08B 5/222 Personal calling arrangements or devices, i.e. paging systems selective calling systems and call receivers H04W84/00, H04W68/00
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 40/20 for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
• CPC Class Codes: G16H 40/40 for the management of medical equipment or devices, e.g. scheduling maintenance or upgrades
• CPC Class Codes: G16H 40/63 for local operation
• CPC Class Codes: G16H 40/67 for remote operation
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46

Abstract

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.

Claims

1-20. -20. (canceled)

21. 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).

22. The hospital bed of claim 21, 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).

23. The hospital bed of claim 21, wherein the communication circuitry is configured to determine whether a default startup has occurred and if so, to communicate using default parameters.

24. The hospital bed of claim 23, wherein the communication circuitry determines if the static IP address is present after determining that a default startup has not occurred.

25. The hospital bed of claim 21, 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.

26. The hospital bed of claim 25, wherein the period of time is randomly established.

27. The hospital bed of claim 26, wherein the randomly established period of time is between 5 to 10 seconds.

28. The hospital bed of claim 25, wherein, after the period of time, the communication circuitry is operable to determine if a fatal error has occurred.

29. The hospital bed of claim 28, wherein if the communication circuitry determines that a fatal error has occurred, the communication circuitry proceeds to an offline mode.

30. The hospital bed of claim 28, 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.

31. The hospital bed of claim 30, wherein in the link mode the communication circuitry also sends a process file message and an inputs mask and initial data message.

32. The hospital bed of claim 31, wherein in the link mode the communication circuitry also receives a request configuration message and a file processed message.

33. The hospital bed of claim 32, 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.

34. The hospital bed of claim 33, 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.

35. The hospital bed of claim 34, wherein the heartbeat message comprises a copyright notice.

36. The hospital bed of claim 35, wherein the copyright notice comprises a company name and a year.

37. The hospital bed of claim 21, 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.

38. The hospital bed of claim 37, 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.

39. The hospital bed of claim 38, 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.

40. The hospital bed of claim 39, 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.