SYSTEM FOR FACILITY MANAGEMENT OF MEDICAL DATA AND PATIENT INTERFACE

• US 20110161111A1
• Filed: 11/03/2010
• Published: 06/30/2011
• Est. Priority Date: 10/24/2006
• Status: Active Grant

• Current Assignee: Medapps Incorporated (Abbott Laboratories Incorporated)
• Original Assignee: Medapps Incorporated (Abbott Laboratories Incorporated)
• Inventors: Kent, Ralp, Bartlett, Terry, Tripp, Robert, Crosley, Thomas, Dicks, Kent E.
• Granted Patent: US 8,131,566 B2
• Time in Patent Office: Days
• US Class Current: 705/3
• CPC Class Codes: A61B 2560/045 with a separable interface unit, e.g. for communication
• CPC Class Codes: A61B 5/0022 Monitoring a patient using a global network, e.g. telephone networks, internet
• CPC Class Codes: A61N 1/37247 User interfaces, e.g. input or presentation means
• CPC Class Codes: A61N 1/37282 characterised by communication with experts in remote locations using a network
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 40/67 for remote operation
• CPC Class Codes: G16H 50/20 for computer-aided diagnosis, e.g. based on medical expert systems

Abstract

A system according to the present invention includes a processor, a device interface, a data relay transceiver, and a memory coupled to the processor. The memory stores instructions that, when executed by the processor, cause the processor to receive, using the device interface, data for a plurality of patients from a medical device. The received data includes a location for at least one of the plurality of patients. The memory further stores instructions to cause the processor to transmit a message including the received data, using the data relay transceiver, to one or more of: a provided medical data server; and a provided intermediary device. The intermediary device includes a software program configured to retransmit the message to the medical data server.

Claims

1. A system comprising:

a processor;

a device interface;

a data relay transceiver; and

a memory coupled to the processor and storing instructions that, when executed by the processor, cause the processor to;

receive, using the device interface, data for a plurality of patients from a medical device, wherein the received data includes a location for at least one of the plurality of patients;

transmit a message including the received data, using the data relay transceiver, to one or more of;

a provided medical data server; and

a provided intermediary device, wherein the intermediary device includes a software program configured to retransmit the message to the medical data server.

2. The system of claim 1, wherein the received data includes one of a respective patient identifier for each of the respective plurality of patients and a respective health status indicator for each of the respective plurality of patients.

3. The system of claim 1, wherein the received data includes one or more of:

biological information for a patient;

biometric information for a patient; and

behavioral information for a patient.

4. The system of claim 1, wherein the message is encrypted.

5. The system of claim 1, wherein the device interface is configured to receive the data from the medical device through a wired connection selected from the group consisting of an optical fiber connection, a tip and sleeve (TS) connection, a tip, ring, and sleeve (TRS) connection, a tip, ring, ring, and sleeve (TRRS) connection, a serial peripheral interface bus (SPI) connection, a universal serial bus (USB) connection, an RS-232 serial connection, an Ethernet connection, a FireWire connection, and combinations thereof.

6. The system of claim 1, wherein the device interface is configured to receive the data from the medical device through a wireless connection using a protocol selected from the group consisting of a Zigbee protocol, a Wibree protocol, an IEEE 802.11 protocol, an IEEE 802.15 protocol, an IEEE 802.16 protocol, an Ultra-Wideband (UWB) protocol, an Infrared Data Association (IrDA) protocol, a Bluetooth protocol, and combinations thereof.

7. The system of claim 1, wherein the data includes an environmental parameter, wherein the environmental parameter includes at least one of a battery charge level, a temperature, a barometric pressure, a code relating to an accessory for the medical device, a data validity measurement, an elapsed time since a previous reading by the medical device, a test result parameter, a signal-to-noise parameter, and a quality of service (QoS) parameter.

8. The system of claim 1, wherein the data relay transceiver is configured to transmit the message through a wireless network selected from the group consisting of:

a cellular network;

a General Packet Radio Service (GPRS) network;

a wireless Local Area Network (WLAN);

a Global System for Mobile Communications (GSM) network;

a Personal Communication Service (PCS) network;

an Advanced Mobile Phone System (AMPS) network;

a satellite communication network; and

combinations thereof.

9. The system of claim 1, wherein the memory further stores instructions to cause the processor to request a medical device identifier from the medical device through the device interface.

10. The system of claim 1, further comprising the medical data server, wherein the medical data server further comprises a user interface, and the medical data server is configured to:

extract the data for a plurality of patients from the message;

respectively associate the data for the plurality of patients with a plurality of graphical patient indicia; and

present the graphical patient indicia on a map using the user interface, wherein the graphical patient indicia are arranged in accordance with respective location data for the plurality of patients on the map.

11. The system of claim 10, wherein the map corresponds to a layout of a healthcare facility.

12. The system of claim 10, wherein:

the message further comprises respective health status indicators corresponding to the plurality of patients; and

the presented graphical patient indicia includes respective graphical representations of the respective health status indicators.

13. The system of claim 12, wherein:

the respective graphical representations of the respective health status indicators includes a graphical indicia that indicates when a patient of the plurality of patients requires medical assistance.

14. The system of claim 12, wherein the medical data server is further configured to:

analyze the respective health status indicators;

determine whether at least one of the respective health status indicators satisfies a predetermined threshold condition that a respective patient requires assistance; and

provide, through the user interface, the location of the respective patient that requires assistance.

15. The system of claim 14, wherein determining that at least one of the respective health status indicators satisfies a predetermined threshold condition that a respective patient requires assistance includes at least one of:

determining that the patient has left a predefined area;

receiving information from a sensor in a medical device associated with the patient that indicates the patient is in distress;

determining that a biometric for the patient exceeds a predetermined threshold value; and

receiving a communication from the patient indicating that the patient requires assistance.

16. The system of claim 14, wherein the user interface is further configured to provide instructions to direct a healthcare provider to the patient requiring assistance.

17. The system of claim 16, wherein the medical data server is further configured to format a dispatch message for transmission to the healthcare provider, the dispatch message including the respective patient location information and the instructions to direct the healthcare provider to the patient.

18. The system of claim 16, wherein the dispatch message further comprises at least one of:

the patient identifier and the respective health status indicator.

19. The system of claim 10, wherein the user interface is further configured to initiate a voice communication with a patient.

20. The system of claim 19, wherein the voice communication with the patient is initiated in response to input from a healthcare provider using the user interface.