Method and apparatus for alert validation

• US 10,504,338 B2
• Filed: 06/14/2018
• Issued: 12/10/2019
• Est. Priority Date: 08/30/2012
• Status: Active Grant

• Current Assignee: Arria Data2text Limited
• Original Assignee: Arria Data2text Limited
• Inventors: Reiter, Ehud B.
• Primary Examiner(s): Tweel, Jr., John A
• Application Number:
  US16/009,006
• Publication Number:
  US 20190035232A1
• Time in Patent Office: 544 Days
• Field of Search: 3406916
• CPC Class Codes: G06F 40/14 Tree-structured documents parsing G06F40/205; validation G06F40/226
• CPC Class Codes: G06F 40/186 Templates
• CPC Class Codes: G06F 40/56 Natural language generation
• CPC Class Codes: G08B 21/0453 worn on the body to detect health condition by physiological monitoring, e.g. electrocardiogram, temperature, breathing detecting, measuring or recording for diagnostic purposes A61B5/00
• CPC Class Codes: G08B 23/00 Alarms responsive to unspecified undesired or abnormal conditions
• CPC Class Codes: G08B 29/18 Prevention or correction of operating errors G08B29/02, G08B29/12 take precedence
• CPC Class Codes: G08B 5/22 using electric transmission; using electromagnetic transmission
• CPC Class Codes: G08B 5/36 using visible light sources
• CPC Class Codes: G08B 7/06 using electric transmission , e.g. involving audible and visible signalling through the use of sound and light sources
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 15/00 ICT specially adapted for medical reports, e.g. generation or transmission thereof
• CPC Class Codes: G16H 50/20 for computer-aided diagnosis, e.g. based on medical expert systems
• CPC Class Codes: G16H 50/30 for calculating health indices; for individual health risk assessment
• CPC Class Codes: G16H 50/70 for mining of medical data, e.g. analysing previous cases of other patients
• CPC Class Codes: G16H 70/00 ICT specially adapted for the handling or processing of medical references

Abstract

Methods, apparatuses, and computer program products are described herein that are configured to enable validation of an alert condition. In some example embodiments, a method is provided that comprises detecting an alert condition. The method of this embodiment may also include generating a set of messages based on one or more key events in a primary data channel and one or more significant events in one or more related data channels in response to the alert condition. The method of this embodiment may also include determining a validity of the alert condition based on the set of messages that express the one or more key events, the one or more significant events, a relationship between the one or more key events and the one or more significant events, an alert context and the one or causes of the alert condition.

Claims

1. A method for verifying a cause of an alert condition associated with one or more data channels, the method comprising:

determining, using at least one processor, at least one key event in each of one or more primary data channels, wherein the at least one key event indicates the alert condition;

identifying, using the at least one processor and a diagnostic model, one or more possible causes of the alert condition;

determining, using the at least one processor and the diagnostic model, one or more secondary data channels to verify a cause of the alert condition of the one or more possible causes;

verifying the cause of the alert condition; and

generating, using the at least one processor, an alert validation text, wherein the alert validation text is configured to linguistically express the at least one key event and the cause of the alert condition.

2. The method of claim 1, wherein the one or more secondary data channels are related to the one or more primary data channels.

3. The method of claim 1, wherein the alert validation text is further configured to linguistically express a recommended response to the alert condition based at least on the cause of the alert condition.

4. The method of claim 1, herein identifying one or more possible causes of the alert condition comprises generating an alert context.

5. The method of claim 4, further comprising:

generating an alert context based on one or more of a determination of whether the alert condition is an intermittent alert condition, a determination of whether there is at least one previous instance of the alert condition on an apparatus that is currently experiencing the alert condition, a determination of one or more actions taken with respect to the previous instance of the alert condition in an instance in which there is at least one previous instance of the alert condition, a determination of whether there is at least one of another active alert condition or a maintenance request on the apparatus, or a determination of whether there is at least one of another active alert condition or another maintenance request on a related apparatus.

6. The method of claim 1, wherein verifying the cause of the alert condition comprises evaluating raw data in the one or more secondary data channels.

7. The method of claim 1, wherein the one or more secondary data channels are identified as related to the one or more primary data channels based in part on a detection of a significant event in raw data in the one or more secondary data channels.

8. The method of claim 1, wherein the one or more secondary data channels are selected based on a rule language that is configured to qualitatively specify expected relationships between data channels.

16. The apparatus of claim 1, wherein the one or more secondary data channels are selected based on a rule language that is configured to qualitatively specify expected relationships between data channels.

9. An apparatus for verifying a cause of an alert condition associated with one or more data channels, the apparatus comprising at least one processor and at least one non-transitory memory including program code, the at least one memory and the program code being configured to, with the at least one processor, cause the apparatus to:

determine at least one key event in each of one or more primary data channels, wherein the at least one key event indicates the alert condition;

identify, using a diagnostic model, one or more possible causes of the alert condition;

determine, using the diagnostic model, one or more secondary data channels to verify a cause of the alert condition of the one or more possible causes;

verify the cause of the alert condition; and

generate an alert validation text, wherein the alert validation text is configured to linguistically express the at least one key event and the cause of the alert condition.

10. The apparatus of claim 9, wherein the one or more secondary data channels are related to the one or more primary data channels.

11. The apparatus of claim 9, wherein the alert validation text is further configured to linguistically express a recommended response to the alert condition based at least on the cause of the alert condition.

12. The apparatus of claim 9, wherein identifying one or more possible causes of the alert condition comprises generating an alert context.

13. The apparatus of claim 12, further caused to:

generate an alert context based on one or more of a determination of whether the alert condition is an intermittent alert condition, a determination of whether there is at least one previous instance of the alert condition on an apparatus that is currently experiencing the alert condition, a determination of one or more actions taken with respect to the previous instance of the alert condition in an instance in which there is at least one previous instance of the alert condition, a determination of whether there is at least one of another active alert condition or a maintenance request on the apparatus, or a determination of whether there is at least one of another active alert condition or another maintenance request on a related apparatus.

14. The apparatus of claim 9, wherein verifying the cause of the alert condition comprises evaluating raw data in the one or more secondary data channels.

15. The apparatus of claim 9, wherein the one or more secondary data channels are identified as related to the one or more primary data channels based in part on a detection of a significant event in raw data in the one or more secondary data channels.