Human Resource Selection Based on Readability of Unstructured Text Within an Individual Case Safety Report (ICSR) and Confidence of the ICSR
First Claim
1. A method, in a data processing system comprising at least one processor and at least one memory, the at least one memory comprising instructions that are executed by the at least one processor to cause the at least one processor to be configured to implement a drug-adverse event causality evaluation engine to identify human resource selections based on a readability of unstructured text within an individual case safety report (ICSR) and a confidence value of the ICSR, the method comprising:
- receiving, by the drug-adverse event causality evaluation engine, the ICSR from a cognitive system;
analyzing, by the drug-adverse event causality evaluation engine, the unstructured natural language text within the ICSR to determine a readability value of the ICSR;
determining, by the drug-adverse event causality evaluation engine, whether or not an assessment, by a human reviewer, of the ICSR is required based on a combination of the readability value of the ICSR and the confidence value; and
outputting, by the drug-adverse event causality evaluation engine, an indication of whether human reviewer assessment is required.
1 Assignment
0 Petitions
Accused Products
Abstract
Mechanisms are provided that implement a drug-adverse event causality evaluation engine to identify human resource selections based on a readability of unstructured text within an individual case safety report (ICSR) and a confidence value of the ICSR. The drug-adverse event causality evaluation engine receives the ICSR from a cognitive system. The drug-adverse event causality evaluation engine analyzes the ICSR to determine a readability value of the ICSR. The drug-adverse event causality evaluation engine determines whether or not an assessment, by a human reviewer, of the ICSR is required based on a combination of the readability value of the ICSR and the confidence value. The drug-adverse event causality evaluation engine outputs an indication of whether human reviewer assessment is required.
-
Citations
20 Claims
-
1. A method, in a data processing system comprising at least one processor and at least one memory, the at least one memory comprising instructions that are executed by the at least one processor to cause the at least one processor to be configured to implement a drug-adverse event causality evaluation engine to identify human resource selections based on a readability of unstructured text within an individual case safety report (ICSR) and a confidence value of the ICSR, the method comprising:
-
receiving, by the drug-adverse event causality evaluation engine, the ICSR from a cognitive system; analyzing, by the drug-adverse event causality evaluation engine, the unstructured natural language text within the ICSR to determine a readability value of the ICSR; determining, by the drug-adverse event causality evaluation engine, whether or not an assessment, by a human reviewer, of the ICSR is required based on a combination of the readability value of the ICSR and the confidence value; and outputting, by the drug-adverse event causality evaluation engine, an indication of whether human reviewer assessment is required. - View Dependent Claims (3, 5, 6, 7)
-
-
2. The method of claim I, wherein the confidence value is determined based on normalizing a probability value that indicates a level of confidence of an algorithm within the cognitive system that generated the ICSR.
-
4. The method of claim I, wherein determining whether or not assessment, by the human reviewer, of the ICSR is required further comprises:
determining, by the drug-adverse event causality evaluation engine, a number of human reviewers required to review the ICSR based on the measure of readability and the confidence value.
-
8. A computer program product comprising a computer readable storage medium having a computer readable program stored therein, wherein the computer readable program, when executed on a data processing system, causes the data processing system to implement a drug-adverse event causality evaluation engine to identify human resource selections based on a readability of unstructured text within an individual case safety report (ICSR) and a confidence value of the ICSR, and further causes the data processing system to:
-
receive, by the drug-adverse event causality evaluation engine, the ICSR from a cognitive system; analyze, by the drug-adverse event causality evaluation engine, the ICSR to determine a readability value of the ICSR; determine, by the drug-adverse event causality evaluation engine, whether or not an assessment, by a human reviewer, of the ICSR is required based on a combination of the readability value of the ICSR and the confidence value; and output, by the drug-adverse event causality evaluation engine, an indication of whether human reviewer assessment is required. - View Dependent Claims (9, 10, 11, 12, 13, 14)
-
-
15. A data processing system comprising:
-
at least one processor; and at least one memory coupled to the at least one processor, wherein the at least one memory comprises instructions Which, when executed by the at least one processor, cause the at least one processor to implement a drug-adverse event causality evaluation engine to identify human resource selections based on a readability of unstructured text within an individual case safety report (ICSR) and a confidence value of the ICSR, and further cause the at least one processor to; receive, by the drug-adverse event causality evaluation engine, the ICSR from a cognitive system; analyze, by the drug-adverse event causality evaluation engine, the ICSR to determine a readability value of the ICSR; determine, by the drug-adverse event causality evaluation engine, whether or not an assessment, by a human reviewer, of the ICSR is required based on a combination of the readability value of the ICSR and the confidence value; and output, by the drug-adverse event causality evaluation engine, an indication of whether human reviewer assessment is required. - View Dependent Claims (16, 17, 18, 19, 20)
-
Specification