Reasoning engines

• US 9,530,100 B2
• Filed: 01/06/2016
• Issued: 12/27/2016
• Est. Priority Date: 03/22/2011
• Status: Active Grant

• Current Assignee: Nant Holdings IP, LLC (NantWorks, LLC)
• Original Assignee: Patrick Soon-Shiong
• Inventors: Soon-Shiong, Patrick
• Primary Examiner(s): Hill, Stanley K
• Assistant Examiner(s): Kim, David H
• Application Number:
  US14/989,724
• Publication Number:
  US 20160117596A1
• Time in Patent Office: 356 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 16/951 Indexing; Web crawling techniques
• CPC Class Codes: G06F 16/9537 Spatial or temporal dependent retrieval, e.g. spatiotemporal queries
• CPC Class Codes: G06N 5/022 Knowledge engineering; Knowledge acquisition
• CPC Class Codes: G06N 5/025 Extracting rules from data
• CPC Class Codes: G06N 5/04 Inference or reasoning models
• CPC Class Codes: G06N 5/041 Abduction
• CPC Class Codes: G06N 5/043 Distributed expert systems; Blackboards
• CPC Class Codes: G06N 5/046 Forward inferencing; Production systems
• CPC Class Codes: G06Q 30/0241 Advertisements
• CPC Class Codes: G06T 9/00 Image coding bandwidth or redundancy reduction for static pictures H04N1/41; coding or decoding of static colour picture signals H04N1/64; methods or arrangements for coding, decoding, compressing or decompressing digital video signals H04N19/00
• CPC Class Codes: G06V 20/00 Scenes; Scene-specific elements control of digital cameras H04N23/60
• 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 50/20 for computer-aided diagnosis, e.g. based on medical expert systems
• CPC Class Codes: G16H 50/70 for mining of medical data, e.g. analysing previous cases of other patients
• CPC Class Codes: Y04S 10/50 Systems or methods supporting the power network operation or management, involving a certain degree of interaction with the load-side end user applications

Abstract

A reasoning engine is disclosed. Contemplated reasoning engines acquire data relating to one or more aspects of various environments. Inference engines within the reasoning engines review the acquire data, historical or current, to generate one or more hypotheses about how the aspects of the environments might be correlated, if at all. The reasoning engine can attempt to validate the hypotheses through controlling acquisition of the environment data.

Claims

1. A computer-based medical reasoning engine comprising:

a medical data interface configured to acquire medical data associated with treatment of a patient; and

at least one medical inference server coupled with the medical data interface and configured to;

obtain the medical data via the medical data interface;

recognize, from the medical data, a treatment protocol and result related to the treatment of the patient, the treatment protocol and result each comprising object attributes;

select a reasoning rules set from available reasoning rules sets as a function of the medical data and object attributes of the treatment protocol and results;

establish at least one outcome hypothesis according to the selected reasoning rules set as a function of patient data, the at least one outcome hypothesis representing that the treatment protocol and result have a suspected correlation with respect to the patient; and

configure an output device to present the at least one outcome hypothesis along with reasoning supporting the at least one outcome hypothesis.

2. The engine of claim 1, wherein the at least one outcome hypothesis includes a positive outcome hypothesis with respect to the patient.

3. The engine of claim 1, wherein the at least one outcome hypothesis includes a negative outcome hypothesis with respect to the patient.

4. The engine of claim 1, wherein the at least one outcome hypothesis comprises a recommended change to the treatment protocol with respect to the patient.

5. The engine of claim 1, wherein the medical data comprises biometric data of the patient.

6. The engine of claim 5, wherein the biometric data comprises biometric sensor data.

7. The engine of claim 5, wherein the biometric data includes at least one of the following:

a change in a biometric, a pressure point, a perspiration, a body fluid metric, a respiration, a blood pressure, and a perfusion.

8. The engine of claim 1, wherein the medical data comprises genomic data.

9. The engine of claim 1, wherein the medical data reflects changes in the patient'"'"'s body.

10. The engine of claim 1, wherein the medical data includes at least one of the following data modalities:

audio data, image data, video data, tactile data, kinesthetic data, and sensor data.

11. The engine of claim 1, wherein the object attributes adhere to a normalized namespace.

12. The engine of claim 11, wherein the normalized namespace represents a nutrition namespace.

13. The engine of claim 1, further comprising an individual-specific knowledge base coupled with the medical inference server.

14. The engine of claim 13, wherein the medical inference server is further configured to establish the at least one outcome hypothesis as a function of information within the individual-specific knowledge base.

15. The engine of claim 1, wherein the available reasoning rules sets includes reasoning rules that operate according to at least one of the following:

deductive reasoning, abductive reasoning, case-based reasoning, inductive reasoning, metaphorical mapping, and fuzzy logic.

16. The engine of claim 1, wherein the medical data interface comprises a mobile device.

17. The engine of claim 1, wherein the output device comprises a mobile device.

18. The engine of claim 1, further comprising a validation module coupled with the medical inference server and configured to derive a validation plan from the suspected correlation.

19. The engine of claim 18, wherein the validation module is configured to submit a validation request according to the validation plan via the medical device interface.

20. The engine of claim 18, wherein the validation module is configured to submit a validation request according to the validation plan to another user.