This is a literature mining tool that facilitates scientific discovery of etiologies and treatments.
In response to a query, CQ displays a list of results (causes or treatments), where each result is backed by one or more scientific papers supporting it. CQ provides a link to each paper and highlights important sentences which triggered the match. The results are ranked by the number of papers supporting them, which is displayed in parentheses next to each result.
An attempt is made to group various names that refer to the same condition, disease or treatment into a single item, though this is very hard to achieve in practice, and the system may have errors of grouping too much, or too little.
Note that the system does not distinguish between papers that study a specific condition or phenomena, and papers that simply mention it in passing. We argue that both useful, but, of course, practitioners who are interested in a given result should consult the relevant literature and decide for themselves how to judge the evidence.
To find assertions of etiologies and treatment, the system consults around 30-40 templates, which are forms such as ____ due to ____
or ____ in patients with ____
, and attempt to match them to the literature. The matching is done at the syntactic level, after a linguistic analysis of the text, so the second template, for example, might match also sentences like ____ and other conditions in large groups of patients in a UK hospital with ____
. Some patterns also include constraints on the kind of thing that can appear in the slots, for example, requiring the term to be a disease or a chemical.
The list of results is extracted from the literature (see "how does this work") above. We try to group similar items into a single entry, either by considering various similarity rules, and/or by attempting to link each extracted item to a biomedical ontology, but (a) this automatic linking is not always accurate; and (b) sometimes that ontology itself considers two very similar conditions to be separate concepts. For this reason, the items on the left pane may seem to contain near duplicates: we were not able to determine for certain that the two items refer to the same concept, and preferred to err on the side of not linking them.
In future versions of this tool, we consider a user interface that will allow you to filter or to merge such entries.
We currently consult the text of all abstracts available on PubMed. We update the literature we consult regularly, but we may have a lag of 2-3 months after the latest PubMed release.
The application also supports two extraction modes:
Narrow: the default extraction mode, it shows fewer results than “Broad”, but the results are generally more accurate and contain fewer near-duplicates (differently named variants of what is essentially the same cause or treatment).
Broad: an extraction mode relevant to medical researchers interested in the widest coverage possible. “Broad” will return more results than “narrow” but these results may be less accurate and contain more near-duplicates.
These relate to different sets of patterns, as described in "how does this work" above (the "broad" one is naturally more inclusive).
The Clinical Queries application is a collaboration between the Allen Institute for AI, Rambam Health Care Campus, Bar Ilan University and the Technion Biomedical Engineering Lab.
The tool is intended to aid professionals, by helping them to locate information and explore and discover relevant literature, which they should then assess professionally based on their medical knowledge and the presented evidence from the literature. It does not claim to be complete and find all available information, but rather assists in this important process. The tool's output should not be taken to endorse or recommend any specific plan or a specific paper. Influence on any treatment plan, medication, or protocol, should be done after thorough verification by a medical professional.
By clicking accept or continuing to use the site, you agree to the above, and also the terms outlined in our Privacy Policy and Terms of Service