METHODS AND SYSTEMS FOR AUTOMATED DEPLOYMENT OF REMOTE MEASUREMENT, PATIENT MONITORING, AND HOME CARE AND MULTI-MEDIA COLLABORATION SERVICES IN HEALTH CARE AND TELEMEDICINE

• US 20150363563A1
• Filed: 06/15/2015
• Published: 12/17/2015
• Est. Priority Date: 06/13/2014
• Status: Abandoned Application

• Current Assignee: Snappskin, Inc.
• Original Assignee: Snappskin, Inc.
• Inventors: Hallwachs, Joachim H.
• Application Number:
  US14/739,435
• Publication Number:
  US 20150363563A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 30/20 for handling medical images, e.g. DICOM, HL7 or PACS
• CPC Class Codes: G16H 40/63 for local operation
• CPC Class Codes: G16H 40/67 for remote operation
• CPC Class Codes: G16H 80/00 ICT specially adapted for facilitating communication between medical practitioners or patients, e.g. for collaborative diagnosis, therapy or health monitoring
• CPC Class Codes: G16Z 99/00 Subject matter not provided for in other main groups of this subclass
• CPC Class Codes: H04B 5/77 for interrogation
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]

Abstract

Various exemplary methods and systems for automated deployment of remote measurement, patient monitoring, and home care and multi-media collaboration services in health care and telemedicine are provided. In general, a system can allow automated deployment and simplified installation by non-technical personnel of sensor-based remote monitoring and process automation solutions.

Claims

1. A method of managing health care, comprising:

receiving at a central server sensor data from a first client terminal having a first application installed thereon, the sensor data being indicative of information gathered by at least one sensor regarding at least one parameter related to at least one of health and wellness of a patient, and the first application being configured to facilitate gathering of the information and transmission of the gathered information in real time with the gathering of the information, the sensor data received at the central server being anonymous so as to not be associated with protected health information (PHI) identifying the patient; and

causing the received sensor data to be transmitted in real time from the central server to a second client terminal having a second application installed thereon, the second application being configured to facilitate receipt of the data from the central server and display of the data on the second client terminal in real time with the receipt of the sensor data at the second client terminal.

2. The method of claim 1, further comprising analyzing the sensor data received at the central server in real time to determine if the received information indicates an alarm condition;

and

in response to determining that the alarm condition is indicated, causing an alert to be transmitted in real time to the second client terminal indicating occurrence of the alarm condition.

3. The method of claim 1, wherein the transmission to the second terminal occurs automatically in response to the receipt of the sensor data at the central server.

4. The method of claim 1, wherein the transmission to the second terminal occurs in response to a request received at the central server from the second client terminal requesting data gathered by the at least one sensor.

5. The method of claim 1, further comprising receiving an electronic order for a patient, the order indicating the at least one parameter to be measured in real time with respect to the patient;

and

in response to receiving the electronic order, causing the first application to be transmitted to a first client terminal, and causing the second application to be transmitted to the second client terminal.

6. The method of claim 1, further comprising causing the sensor data received at the central server to be persistently stored in a storage device, the stored sensor data not being associated with PHI information identifying the patient.

7. The method of claim 1, further comprising causing at least one of an electronic medical record (EMR) and electronic health record (EHR) of the patient to be updated in response to the receipt of the sensor data at the central server.

8. The method of claim 1, further comprising receiving at the central server user input data from the second client terminal, and causing at least one of an electronic medical record (EMR) and electronic health record (EHR) of the patient to be updated in response to the receipt of the user input data at the central server, the user input data being input to the second client terminal by a user and being related to the sensor data received at the second client terminal.

11. The method of claim 1, further comprising querying the first client terminal to determine a location of the at least one sensor, the location of the at least one sensor being indicative of a location of the patient.

12. The method of claim 11, further comprising querying a plurality of additional client terminals, each of the additional client terminals having associated therewith one or more sensors configured to gather information regarding at least one parameter related to at least one of health and wellness of one of a plurality of patients, to determine a location of each of the one or more sensors associated with the additional client terminals, the locations of the one or more sensors being indicative of locations of the plurality of patients.

9-10. -10. (canceled)

13-16. -16. (canceled)

17. A method of managing health care, comprising:

gathering of patient data by a first application operating as an embedded function of a first client terminal, the data being indicative of information regarding at least one parameter related to health and wellness of a patient, the gathered data not being persistently stored at the first client terminal;

transmitting the gathered patient data in real time from the first client terminal to a central server, the transmitted data being constructed as an anonymous patient data record so as to not be associated with protected health information (PHI) identifying the patient, the first application being configurable using a downloadable configuration template to facilitate the gathering of the patient data and the transmission of the gathered data in real time with the gathering of the data; and

causing the received patient data record to be transmitted from the central server to a second application operating as an embedded function of a second client terminal;

wherein the second application is configured to request and receive a patient data record from the central server, and the second application is configured to cause display of at least a portion of the requested and received patient data record on a display of the second client terminal in real time with the receipt of the requested and received patient data record.

18. The method of claim 17, wherein the second client terminal is either included as part of the first client terminal or is a client terminal independent of the first client terminal.

21. The method of claim 17, further comprising determining a presence of the patient by one of

with the first application, scanning for a Bluetooth low energy (BLE) sensor device used as an identifying radio frequency identification (RFID) device to establish an identification of the patient, receiving a real time user input at the first client terminal, and receiving a parameterization input via the second application as part of a downloadable configuration template as part of a care path directive associated with the patient;

causing the first application to confirm the presence and related identification of the patient with a cloud administration server, from which the first client terminal receives an anonymous and unique patient identification token used to record and identify the anonymous patient data record following the transmission of the gathered patient data to the central server; and

causing the cloud administration server to transmit to the first application, with the patient identification token, one or more templates, the one or more templates including the care path directive associated with the patient, the care path direction specifying time and method for the gathering of the patient data and including instructions regarding how to analyze and process data related to the patient and a care plan for the patient.

32. The method of claim 17, wherein at least one patient-wearable sensor is in communication with the first application;

the at least one patient-wearable sensor being configured to gather the patient data;

the at least one patient-wearable sensor being configured as an active radio frequency identification (RFID) sensor allowing identification of the patient at least one indirectly through a unique media access control (MAC) address thereof or directly through presentation of a system-unique patient identifier by the at least one patient-wearable sensor; and

the method further comprising the first application determining presence of the patient using the identification of the patient, thus associating a location of the patient relative to a location of the first client terminal using an open standards-based wireless association method, the location of the first client terminal being physical or logical.

34. The method of claim 17, wherein the first client terminal includes a plurality of client terminals each having an instance of the first application embedded thereon, and the method further comprises querying the first applications in real time, thereby causing the plurality of client terminals to scan for its association with one or more active radio frequency identification (RFID) sensors to determine a location of the one or more active RFID sensors relative to the associated one of the plurality of client terminals, the location of the one or more active RFID sensors being indicative of the locations of a related plurality of patients at that time relative to a location of an associated one of the client terminals, thereby establishing an overall patient census and a location map relative to physical locations of the plurality of client terminals, the location of the associated client terminals being physical or logical.

19-20. -20. (canceled)

22-31. -31. (canceled)

33. (canceled)

35-43. -43. (canceled)

44. A system for managing health care, comprising:

a cloud server configured to receive data indicative of measurements of at least one parameter with respect to a patient from a client terminal without the received data being explicitly associated with protected health information (PHI) identifying the patient, the at least one parameter being related to at least one of health and wellness of the patient;

a first storage device being configured to electronically communicate with the cloud server, the cloud server being configured to cause the first storage device to store therein the data received by the cloud server without the stored data being associated with PHI identifying the patient; and

a second storage device being configured to electronically communicate with the cloud server, the cloud server being configured to cause the second storage device to store therein the data received by the cloud server with the stored data being associated with PHI identifying the patient;

wherein the cloud server is configured to distribute the received data to at least one additional client terminal without the distributed data being associated with PHI identifying the patient, and the cloud server is configured to cause at least one of an electronic medical record (EMR) and electronic health record (EHR) of the patient to be updated based on the received data.

45. The system of claim 44, further comprising at least one sensor configured to measure the at least one parameter, the at least one sensor being configured to transmit the measurements to the client terminal that then transmits the data to the cloud server.

46. The system of claim 44, wherein the cloud server is configured to receive the data in real time with gathering thereof;

the cloud sever is configured to analyze the received data in real time with the receipt thereof to determine if the received data indicates an alarm condition; and

in response to determining that the alarm condition is indicated, the cloud server is configured to transmit an alert in real time with the determination of the alarm condition to at least one of the client terminal and one or more additional client terminals, the alert indicating occurrence of the alarm condition.

47. The system of claim 44, wherein the at least one parameter includes at least one of heart rate, blood pressure, temperature, weight, oxygen saturation (spO2), electrocardiography (ECG), glucose, sleep, pulse, and motion.

48. The system of claim 44, wherein the cloud server is configured to cause the first storage device to store therein the data received by the cloud server with a secure, anonymous patient identification token that is generated by the cloud server from the PHI identifying the patient.