Patient sensor data exchange systems and methods

• US 10,437,959 B2
• Filed: 08/26/2015
• Issued: 10/08/2019
• Est. Priority Date: 08/28/2014
• Status: Active Grant

• Current Assignee: NantHealth, LLC (NantWorks, LLC)
• Original Assignee: NantHealth, LLC (NantWorks, LLC)
• Inventors: Dyell, David, Rogowski, Christopher, Kahler, Scott, Milan, Jennifer
• Primary Examiner(s): Syed, Nabil H
• Assistant Examiner(s): Eustaquio, Cal J
• Application Number:
  US14/835,714
• Publication Number:
  US 20160058390A1
• Time in Patent Office: 1,504 Days
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• 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/63 for local operation
• CPC Class Codes: G16H 40/67 for remote operation

Abstract

A system for patient data exchange is provided and includes a plurality of sensors monitoring a patient according to a default sensor configuration, and a patient data exchange engine that receives a request comprising one or more parameters, identifies at least one applicable sensor from the plurality of sensors based on the one or more parameters, and reconfigures the at least one applicable sensor from the default sensor configuration to a different sensor configuration in accordance with the one or more parameters to generate applicable sensor data responsive to the request. In specific embodiments, the patient data exchange engine further computes a monetary value for the generated sensor data based at least on an attribute of the patient and an attribute of the sensor data.

Claims

1. An apparatus comprising:

a non-transitory, computer readable memory storing software instructions that comprises a patient data exchange engine; and

a processor coupled with the memory wherein the processor, upon execution of the software instructions, performs operations comprising;

communicating with a clinical operating system (cOS) executing in a remote server in a network;

communicating with a plurality of sensors coupled to the apparatus, wherein each of the plurality of sensors monitors a patient according to a first sensor configuration;

receiving, from the cOS, a request from a client in the network for patient sensor data associated with a patient health status, the patient health status comprising one or more health status parameters;

receiving, from the cOS, patient health status factors associated with the plurality of patients;

identifying a sensor from among the plurality of sensors based on the one or more health status parameters and the patient health status factors;

generating a second sensor configuration based on the request, the second sensor configuration being different from the first sensor configuration; and

reconfiguring the identified sensor according to the second sensor configuration.

2. The apparatus of claim 1, further configured for:

receiving the sensor data from the reconfigured sensor; and

transmitting the received sensor data to the cOS, wherein the cOS forwards the received sensor data to the client.

3. The apparatus of claim 1, wherein the apparatus associates the sensor data with the patient and stores the associated sensor data in a patient database.

4. The apparatus of claim 1, wherein the first sensor configuration comprises a time-synchronization with another of the plurality of sensors.

5. The apparatus of claim 1, wherein the identified sensor generates patient sensor data at a first sampling rate according to the first sensor configuration, wherein the patient data exchange engine further reconfigures the identified sensor to have a second sampling rate according to the one or more parameters.

6. The apparatus of claim 1, wherein the patient data exchange engine further reconfigures the identified sensor to remove an identifier associated with the patient from the sensor data according to the one or more parameters.

7. The apparatus of claim 1, wherein the patient data exchange engine further rejects the request if reconfiguring the identified sensor defeats an original purpose of the identified sensor.

8. The apparatus of claim 1, wherein the patient data exchange engine further computes a monetary value for generated sensor data based at least on an attribute of the patient and an attribute of the sensor data.

9. The apparatus of claim 8, wherein the patient data exchange engine further enables a transaction with respect to generated sensor data using the computed monetary value.

10. The apparatus of claim 8, wherein the patient data exchange engine further computes the monetary value based on a rarity of the attribute among a plurality of patients.

11. The apparatus of claim 8, wherein the attribute of the patient comprises a demographic attribute of the patient.

12. The apparatus of claim 8, wherein the attribute of the patient comprises a health condition of the patient.

13. The apparatus of claim 12, wherein the health condition comprises at least one of a disease, a treatment, and a reaction to a treatment.

14. The apparatus of claim 8, wherein the attribute of the patient comprises a location of the patient.

15. The apparatus of claim 1, wherein the patient data exchange engine aggregates multiple streams of the sensor data that are associated with a plurality of patients sharing at least one attribute.

16. The apparatus of claim 1, wherein the patient data exchange engine provides a user access to generated sensor data.

17. The patient data exchange system of claim 16, wherein the patient data exchange engine further scrubs the generated sensor data to remove any information that can identify the patient before providing the user access to the generated sensor data.

18. The patient data exchange system of claim 16, wherein the patient data exchange engine further compresses the generated sensor data before providing to the user.

19. The patient data exchange system of claim 1, wherein the patient data exchange engine further:

derives a patient health attribute from the generated sensor data responsive to the request;

determines a rarity of the patient health attribute among a plurality of patients;

derives a correlation between the patient health attribute and the at least one health status parameter of the request; and

computes a monetary value for the request based on the determined rarity and the correlation.

20. A method comprising:

communicating with a clinical operating system (cOS) executing in a remote server in a network;

communicating with a plurality of sensors, wherein each of the plurality of sensors monitors a patient according to a first sensor configuration;

receiving, from the cOS, a request from a client in the network for patient sensor data associated with a patient health status, the patient health status comprising one or more health status parameters;

receiving, from the cOS, patient health status factors associated with the plurality of patients;

identifying a sensor from among the plurality of sensors based on the one or more health status parameters and the patient health status factors;

generating a second sensor configuration based on the request, the second sensor configuration being different from the first sensor configuration; and

reconfiguring the identified sensor according to the second sensor configuration.

21. A non-transitory program storage medium on which are stored instructions executable by a processor or programmable circuit to perform operations comprising:

communicating with a clinical operating system (cOS) executing in a remote server in a network;

communicating with a plurality of sensors, wherein each of the plurality of sensors monitors a patient according to a first sensor configuration;

receiving, from the cOS, a request from a client in the network for patient sensor data associated with a patient health status, the patient health status comprising one or more health status parameters;

receiving, from the cOS, patient health status factors associated with the plurality of patients;

identifying a sensor from among the plurality of sensors based on the one or more health status parameters and the patient health status factors;

generating a second sensor configuration based on the request, the second sensor configuration being different from the first sensor configuration; and

reconfiguring the identified sensor according to the second sensor configuration.