SYSTEM AND METHOD FOR RELIABLE AND SCALABLE HEALTH MONITORING

• US 20130099936A1
• Filed: 10/25/2011
• Published: 04/25/2013
• Est. Priority Date: 10/25/2011
• Status: Active Grant

• Current Assignee: Vital Connect, Inc.
• Original Assignee: Vigilo Networks, Inc.
• Inventors: AZIMI, Saeed
• Granted Patent: US 9,247,004 B2
• Time in Patent Office: Days
• US Class Current: 340/870.01
• CPC Class Codes: A61B 2560/0412 Low-profile patch shaped housings
• CPC Class Codes: A61B 2560/045 with a separable interface unit, e.g. for communication
• CPC Class Codes: A61B 5/0002 Remote monitoring of patients using telemetry, e.g. transmission of vital signals via a communication network A61B5/07 takes precedence; transmission systems for measured values G08C; transmission H04B; transmission of digital information H04L; wireless communication networks H04W
• CPC Class Codes: A61B 5/0015 characterised by features of the telemetry system
• CPC Class Codes: A61B 5/0024 for multiple sensor units attached to the patient, e.g. using a body or personal area network
• CPC Class Codes: A61B 5/1113 Local tracking of patients, e.g. in a hospital or private home
• CPC Class Codes: A61B 5/6833 Adhesive patches
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application
• CPC Class Codes: G16H 20/00 ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance
• 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/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• CPC Class Codes: H04Q 2209/00 Arrangements in telecontrol or telemetry systems
• CPC Class Codes: H04Q 2209/10 using a centralized architecture
• CPC Class Codes: H04Q 2209/40 using a wireless architecture
• CPC Class Codes: H04Q 2209/86 Performing a diagnostic of the sensing device
• CPC Class Codes: H04Q 9/00 Arrangements in telecontrol or telemetry systems for selectively calling a substation from a main station, in which substation desired apparatus is selected for applying a control signal thereto or for obtaining measured values therefrom

Abstract

A health-monitoring system and method are disclosed. The health-monitoring system and method comprise a sensory system and a sensory to front-end communication (SFCM) protocol coupled to the sensory system. The health-monitoring system and method include a front-end system coupled to the sensory system and a front-end to back-end communication (FBCM) protocol coupled to the front-end system. The health-monitoring system and method include a back-end system. The SFCM protocol communicates with the front-end system using a first state awareness link and the FBCM protocol communicates with the back-end system using a second state awareness link.

Claims

1. A health-monitoring system comprising:

a sensory system;

a sensory to front-end communication (SFCM) protocol coupled to the sensory system;

a front-end system coupled to the sensory system;

a front-end to back-end communication (FBCM) protocol coupled to the front-end system; and

a back-end system coupled to the front-end system;

wherein the SFCM protocol communicates with the front-end system using a first state awareness link and wherein the FBCM protocol communicates with the back-end system using a second state awareness link.

2. The system of claim 1, wherein at least one sensory communication (SCM) task within the sensory system includes at least one task that processes data measured by the sensory system.

3. The system of claim 2, wherein the SFCM protocol receives data from the at least one SCM task and transports the data to at least one front-end communication (FCM) task within the front-end system.

4. The system of claim 3, wherein the FBCM protocol receives the data from the at least one FCM task and transports the data to a back-end communication (BCM) process within the back-end system.

5. The system of claim 1, wherein state awareness information of the sensory system is detected and the detected state awareness information is communicated to the at least one FCM task through the first state awareness link.

6. The system of claim 1, wherein state awareness information of the front-end system is detected and the detected state awareness information is communicated to the BCM process through the second state awareness link.

7. The system of claim 6, wherein the BCM process utilizes the detected state awareness information to receive data from the at least one FCM task.

8. The system of claim 6, wherein the BCM process utilizes the detected state awareness information to message and establish a connection with either the sensory system or the front-end system.

9. The system of claim 7, wherein the BCM process receives data from communication paths that do not depend on underlying architectures of the sensory, front-end, and back-end systems.

10. The system of claim 1, wherein the SFCM protocol is a two-way communication protocol between the sensory system and the front-end system and the FBCM protocol is a two-way communication protocol between the front-end system and the back-end system.

11. The system of claim 1, wherein the sensory system is a collection of body vital sign metrics in patch form.

12. A method for monitoring the health of a body, the method comprising:

providing a sensory system;

coupling a sensor to front-end communication (SFCM) protocol to the sensory system;

coupling a front-end system to the sensory system;

coupling a front-end to back-end communication (FBCM) protocol to the front-end system;

coupling the front-end system to a back-end system;

communicating data between the SFCM protocol and the front-end system using a first state awareness link; and

communicating data between the FBCM protocol and the back-end system using a second state awareness link.

13. The method of claim 12, wherein at least one sensory communication (SCM) task within the sensory system includes at least one task for processing data measured by the sensory system.

14. The method of claim 13, further comprising:

receiving data by the SFCM protocol from the at least one SCM task; and

transporting the data to at least one front-end communication (FCM) task within the front-end system.

15. The method of claim 14, further comprising:

receiving data by the FBCM protocol from the at least one FCM task; and

transporting the data to a back-end communication (BCM) process within the back-end system.

16. The method of claim 12, further comprising:

detecting state awareness information of the sensor system; and

communicating the detected state awareness information to the at least one FCM task through the first state awareness link.

17. The method of claim 12, further comprising:

detecting state awareness information of the front-end system; and

communicating the detected state awareness information to the BCM process through the second state awareness link.

18. The method of claim 17, further comprising:

utilizing the detected state awareness information by the BCM process to receive data from the at least one FCM task.

19. The method of claim 17, further comprising:

utilizing the detected state awareness information to message and establish a connection with either the sensory system or the front-end system.

20. The method of claim 18, further comprising:

receiving data by the BCM process from communicating paths that do not depend on underlying architectures of the sensory, front-end, and back-end systems.

21. The method of claim 12, wherein the SFCM protocol is a two-way communication protocol between the sensory system and the front-end system and the FBCM protocol is a two-way communication protocol between the front-end system and the back-end system.