<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">A Post-Analysis of Query Reformulation Methods for Clinical Trials Retrieval DISCUSSION PAPER</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Maristella</forename><surname>Agosti</surname></persName>
							<email>maristella.agosti@unipd.it</email>
							<affiliation key="aff0">
								<orgName type="department">Department of Information Engineering</orgName>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Giorgio</forename><forename type="middle">Maria</forename><surname>Di</surname></persName>
							<affiliation key="aff0">
								<orgName type="department">Department of Information Engineering</orgName>
							</affiliation>
							<affiliation key="aff1">
								<orgName type="department">Department of Mathematics</orgName>
								<orgName type="institution">University of Padua</orgName>
								<address>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Stefano</forename><surname>Marchesin</surname></persName>
							<email>stefano.marchesin@unipd.it</email>
							<affiliation key="aff0">
								<orgName type="department">Department of Information Engineering</orgName>
							</affiliation>
						</author>
						<title level="a" type="main">A Post-Analysis of Query Reformulation Methods for Clinical Trials Retrieval DISCUSSION PAPER</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">ED2FAEC659592F53AA14C71AE6F659A2</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T13:57+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>Query reformulation</term>
					<term>knowledge base</term>
					<term>precision medicine</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>The Precision Medicine (PM) track of the Text REtrieval Conference (TREC) focuses on providing useful precision medicine information to clinicians treating cancer patients. The PM track gives the unique opportunity to evaluate medical IR systems on two different collections: scientific literature and clinical trials. In this paper, we evaluate several state-of-the-art query expansion and reduction methods to see whether a particular approach can be helpful in clinical trials retrieval. We present those approaches that are consistently effective in all three TREC PM editions and we compare them to the results obtained by the research groups who participated in all three editions.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1">Introduction and Motivations</head><p>Medical Information Retrieval (IR) helps a wide variety of users to access and search medical information archives and data <ref type="bibr" target="#b5">[6]</ref>. In <ref type="bibr" target="#b8">[9]</ref>, a classification of textual medical information is proposed: 1) Patient-specific information which applies to individual patients. This type of information can be structured, as in the case of an Electronic Health Record (EHR), or can be free narrative text. 2) Knowledge-based information that has been derived and organized from observational or experimental research. In the case of clinical research, the information is most commonly provided by books and journals, but can take a wide variety of other forms. Therefore, the design of effective tools to access and search textual medical information requires, among other things, enhancing the query through expansion and/or rewriting methods that leverage the information contained within knowledge resources. <ref type="bibr" target="#b14">[15]</ref> identified some challenges arising from the differences between general and medical case-based retrieval. In particular, state-of-the-art retrieval methods, combined with selective query term weighing based on medical thesauri and physician feedback, improve performance significantly <ref type="bibr" target="#b15">[16,</ref><ref type="bibr" target="#b4">5]</ref>. In 2017, 2018, and 2019 the PM <ref type="bibr" target="#b10">[11]</ref> track<ref type="foot" target="#foot_0">1</ref> at TREC<ref type="foot" target="#foot_1">2</ref> focused on an important use case in clinical decision support: providing useful precision medicine information to clinicians treating cancer patients. This track gives a unique opportunity to evaluate medical IR systems since the experimental collection is composed of a set of topics (synthetic cases created by precision oncologists) for two different collections that target two different tasks: 1) retrieving biomedical articles addressing relevant treatments for a given patient, and 2) retrieving clinical trials for which a patient -described in the information need -is eligible.</p><p>This work combines and discusses the methodology and the results originally presented at SIGIR 2019 <ref type="bibr" target="#b1">[2]</ref> and TREC 2019 <ref type="bibr" target="#b3">[4]</ref>. The objective is to evaluate several state-of-the-art query expansion and reduction methods to examine whether a particular approach can be helpful in clinical trials retrieval. Precisely, we compare the results obtained with our approach to the best experiments submitted to the 2017 and 2018 PM tracks <ref type="bibr" target="#b1">[2]</ref>. Then, we select the top three query reformulations found in 2017 and 2018 PM tracks and we evaluate whether their effectiveness also holds in the 2019 PM track <ref type="bibr" target="#b3">[4]</ref>. We conduct a systematic comparison between our approach and those proposed by the research groups that participated in all three years of TREC PM. The analysis shows the effectiveness of the proposed query reformulations in 2017 and 2018 PM tracks and confirms the trend in the 2019 PM track. The obtained runs achieve top performing results in all PM tracks <ref type="bibr" target="#b10">[11]</ref><ref type="bibr" target="#b11">[12]</ref><ref type="bibr" target="#b12">[13]</ref>. In particular, a specific query reformulation allows the retrieval system to achieve top results in all three PM tracks.</p><p>The rest of the paper is organized as follows: Section 2 describes the approach used to evaluate different query reformulation methods. Section 3 presents the experimental setup and Section 4 compares the results obtained using our approach with those obtained by the other research groups who participated in TREC PM 2017, 2018 and 2019. Finally, Section 5 reports some final remarks.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2">Approach</head><p>The approach we propose consists of four steps: (i) indexing, (ii) query reformulation, (iii) retrieval and (iv) filtering.</p><p>Indexing. We create the following fields to index clinical trials collections: &lt;docid&gt;, &lt;text&gt;, &lt;max_age&gt;, &lt;min_age&gt; and &lt;gender&gt;. Fields &lt;max_age&gt;, &lt;min_age&gt; and &lt;gender&gt; contain information extracted from the eligibility section of clinical trials and are used in the filtering step. The &lt;text&gt; field contains the entire content of each clinical trial.</p><p>Query Reformulation. The approach relies on two types of query reformulation methods: query expansion and query reduction.</p><p>Query expansion: We perform a knowledge-based a priori query expansion. First, we rely on MetaMap <ref type="bibr" target="#b2">[3]</ref>, a state-of-the-art medical concept extractor, to extract from each query field all the Unified Medical Language System (UMLS)<ref type="foot" target="#foot_2">3</ref> concepts belonging to the following semantic types: <ref type="foot" target="#foot_3">4</ref> Neoplastic Process (neop), Gene or Genome (gngm) and Cell or Molecular Dysfunction (comd ). The gngm and comd semantic types are related to the query &lt;gene&gt; field, while neop is related to the &lt;disease&gt; field. For those collections where an additional &lt;other&gt; field is included -which considers other potential factors that may be relevant -MetaMap is used on &lt;other&gt; with no restriction on the semantic types, as its content does not refer to any particular semantic type. Second, for each extracted concept, we consider all its name variants contained into the following knowledge sources: National Cancer Institute (NCI), Medical Subject Headings (MeSH), SNOMED CT (SNOMEDCT) and UMLS Metathesaurus (MTH). All knowledge sources are manually curated and up-to-date. The expanded queries consist of the union of the original terms with the set of name variants. For example, consider a query only containing the word "melanoma"which is mapped to the UMLS concept C0025202. The set of name variants for the concept "melanoma" contains, among many others: cutaneous melanoma, malignant melanoma, malignant melanoma (disorder). Therefore, the final expanded query is the union of the original term "melanoma" with all its name variants. Additionally, we expand queries that do not mention any kind of blood cancer (e.g. "lymphoma" or "leukemia") with the term solid. This expansion proved to be effective in <ref type="bibr" target="#b6">[7]</ref> where the authors found that a large part of relevant clinical trials do not mention the exact disease. A more general term like solid tumor is preferable and more effective.</p><p>Query reduction: We reduce original queries by removing, whenever present, gene mutations from the &lt;gene&gt; field. To clarify: consider a topic where the &lt;gene&gt; field mentions "BRAF (V600E)". After reduction, the &lt;gene&gt; field becomes "BRAF". The reduction aims at mitigating the over-specificity of topics, since the information contained in a topic is too specific compared to those contained in the target documents <ref type="bibr" target="#b9">[10]</ref>. Additionally, we remove the &lt;other&gt; field from those collections that include it -since it contains additional factors that are not necessarily relevant, thus representing a potential source of noise in retrieving precise information for patients.</p><p>Retrieval. We use BM25 <ref type="bibr" target="#b13">[14]</ref> as retrieval model. Query terms obtained through query expansion are weighted lower than 1.0 to avoid introducing too much noise in the retrieval process <ref type="bibr" target="#b7">[8]</ref>.</p><p>Filtering. The eligibility section in clinical trials comprises three important demographic aspects that a patient needs to satisfy to be considered eligible for the trial, namely: minimum age, maximum age and gender; where minimum age and maximum age are the minimum and the maximum age, respectively, required for a patient to be considered eligible for the trial, while gender is the required gender. After the retrieval step, we filter out from the list of candidate trials those for which a patient is not eligible -i.e. his/her demographic data (age and gender) does not satisfy the three aforementioned eligibility criteria. In those cases where part of the demographic data is not specified, a clinical trial is kept or discarded on the basis of the remaining demographic information. For instance, if the clinical trial does not specify a required minimum age, then it is kept or discarded based on its maximum age and gender required values.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3">Experimental Setup</head><p>This section describes the experimental collections and the setup used to apply and evaluate our approach.</p><p>Experimental Collections. We report the main information related to topics and document collections below.</p><p>Topics consist of 30, 50, and 40 synthetic cases created by precision oncologists in 2017, 2018, and 2019, respectively. In 2017, each topic contained four key elements in a semi-structured format: (1) disease (e.g. a type of cancer), (2) genetic variants (primarily present in tumors), (3) demographic information (e.g. age, gender), and (4) other factors (which could impact certain treatment options). In 2018 and 2019, each topic had three of the four key elements used in 2017: (1) disease, (2) genetic variants, and (3) demographic information. Furthermore, the 2019 topics contain ten non-cancer-related topics.</p><p>Clinical Trials consist of a set of 241,006 clinical trial descriptions, for both 2017 and 2018, and of an updated version of 306,238 descriptions for 2019. The collections are derived from ClinicalTrials.gov<ref type="foot" target="#foot_4">5</ref> -a database of privately and publicly funded clinical studies conducted around the world. When none of the available treatments are effective on oncology patients, the common recourse is to determine if any potential treatments are undergoing evaluation in a clinical trial. Therefore, it would be helpful to automatically identify the most relevant clinical trials for an individual patient. Precision oncology trials typically use a certain treatment for a certain disease with a specific genetic variant. Such trials can have complex inclusion and/or exclusion criteria that are challenging to match with automated systems.</p><p>Experimental Procedure. We use Whoosh, <ref type="foot" target="#foot_5">6</ref> a Python search engine library, for indexing, retrieval, and filtering. For BM25, we keep the default values k 1 = 1.2 and b = 0.75 provided -as we found them to be a good combination <ref type="bibr" target="#b0">[1]</ref>. For query expansion, we rely on MetaMap to extract and disambiguate concepts from UMLS. Below we report the procedure used for each experiment.</p><p>-Indexing</p><p>• Index clinical trials using the following created fields: &lt;docid&gt;, &lt;text&gt;, &lt;max_age&gt;, &lt;min_age&gt; and &lt;gender&gt;.</p><p>-Query reformulation • Use MetaMap to extract from each query field the UMLS concepts restricted to the following semantic types: neop for &lt;disease&gt;, gngm/comd for &lt;gene&gt;, and all for &lt;other&gt;; • Extract from concepts all name variants belonging to NCI, MeSH, SNOMED CT and MTH knowledge sources; • Expand (or not) topics that do not mention "lymphoma" or "leukemia" with the term solid ; • Reduce (or not) queries by removing, whenever present, gene mutations from the &lt;gene&gt; field; • Remove (or not) the &lt;other&gt; field.</p><p>-Retrieval</p><p>• 2017/2018 PM track: Adopt any combination of the reformulation strategies; • 2019 PM track: Adopt the three best reformulation strategies from 2017/2018 PM tracks; • Weigh expanded terms with a value k = 0.1; • Perform a search using expanded queries with BM25.</p><p>-Filtering</p><p>• Filter out clinical trials for which the patient is not eligible.</p><p>Evaluation Measures. We use the measures adopted in the TREC PM tracks, that are: inferred nDCG (infNDCG), R-precision (Rprec) and P@10.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4">Experimental Results and Discussion</head><p>In Table <ref type="table">1</ref>, we report the results of our experiments on query reformulation (Part A) and compare them with the results obtained by the research groups that participated at TREC PM 2017, 2018 and 2019 (Part B). Given the large number of experiments we performed, we decided to only present the 5 runs with the highest P@10 for each year. Each line shows a particular combination (yes or no values) of semantic types (neop, comd, gngm), usage and expansion of &lt;other&gt; field (oth, oth exp), query reduction (orig), and expansion using weighted solid (tumor) keyword. We use the symbol '•' to indicate that the features oth, oth exp are not applicable for the years 2018 and 2019 due to the absence of the &lt;other&gt; field in 2018 and 2019 topics. We highlight in bold the top 3 scores for each measure, and we use the symbol ‡ to indicate the combination that performs well in all three years. For the TREC PM participants, we select those participants who submitted runs in all three years and reached the top 10 performing runs in at least one edition for each measure <ref type="bibr" target="#b10">[11]</ref><ref type="bibr" target="#b11">[12]</ref><ref type="bibr" target="#b12">[13]</ref>. The results</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Analysis of Query Reformulations. The results from Table 1 (Part A)</head><p>highlight that the use of solid expansions with weight 0.1 as well as query gene reductions (orig = n) seems to improve performance consistently in 2017 -two of the three best runs in terms of P@10 (lines 1 and 2) applying both techniques.</p><p>Regarding knowledge-based expansions, the semantic type gngm (lines 1 and 5) seems more effective than neop (line 3), while comd does not seem to have any positive effect at all. All five runs do not consider the other field (oth = n) nor its expansion (oth exp = n) -confirming our intuition that it might represent a potential source of noise in retrieving precise information for patients.</p><p>Similarly to 2017, two of the best three runs of 2018 use no knowledge-based expansions and rely on the solid (tumor) expansion with weight 0.1 (lines 7 and 9). In particular, the runs combining query gene reductions and solid expansions (marked as ‡) provide the best performances for all the measures considered, both in 2017 and 2018. This suggests that removing highly specialized information (i.e. the gene mutation) or adding general terms (e.g. solid) benefits the retrieval.</p><p>A possible reason is related to the nature of the document collections, since clinical trials often contain general requirements to allow patients to enroll. The results obtained in 2019 with the top three query reformulations from 2017 and 2018 confirm this trend. The run combining query gene reductions and solid expansions (line 13 ‡) is one of the top three runs of 2019, however two query reformulations from 2017 (line 14) and 2018 (line 11) provide better performance. This result shows how difficult the task is. In fact, even though we found a particular query reformulation approach (marked as ‡) to be highly effective in all three years -especially in 2017 and 2018 -it was not the best approach for 2019. Therefore, this analysis helps researchers to select an effective subset of query reformulations to build strong baselines for clinical trials retrieval.</p><p>Comparison with TREC PM Participants. The results from Table <ref type="table">1</ref> (Part B) mark a clear division between the 2017 and 2018 tracks and the 2019 track. In 2017 and 2018, most of the participant runs did not reach the top 10 threshold in any of the considered measures -the only exception is the research group from Poznan University of Technology, whose best runs always belong to the top 10 performing runs for the track. Conversely, in 2019 all the participant groups submitted runs that achieved results higher than the top 10 threshold.</p><p>Compared with the results obtained using the query reformulations from Table 1 (Part A), we can see that all runs employing the best query reformulations obtain results higher than the top 10 threshold for all the considered measures in all three years. Furthermore, the runs using the top five query reformulations achieved consistently better results than participant runs for each measure in all three years. This is an indication of the robustness of our approach across the different collections and also of the effectiveness of the proposed query reformulations for the clinical trials retrieval. In particular, it is worth to mention that the runs using the ( ‡) query reformulation achieve performances that belong to the top three best performing systems of each year PM track <ref type="bibr" target="#b10">[11]</ref><ref type="bibr" target="#b11">[12]</ref><ref type="bibr" target="#b12">[13]</ref>. Therefore, the analysis of query reformulations made on the 2017 and 2018 PM tracks con-firmed its trend in the 2019 PM track and allowed us to identify a specific set of query reformulations beneficial for the retrieval of clinical trials.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5">Conclusions and Final Remarks</head><p>In this paper, we further elaborate the results originally presented at SIGIR 2019 <ref type="bibr" target="#b1">[2]</ref> and TREC 2019 <ref type="bibr" target="#b3">[4]</ref> to evaluate several query expansion and reduction methods and to see whether a particular approach can be helpful in clinical trials retrieval. The experimental analysis showed the effectiveness of the proposed query reformulations in 2017 and 2018 PM tracks, and we confirmed this positive trend in the 2019 PM track. The obtained runs achieve top performing results in all PM tracks <ref type="bibr" target="#b10">[11]</ref><ref type="bibr" target="#b11">[12]</ref><ref type="bibr" target="#b12">[13]</ref>. In particular, the run marked as ‡ in Table <ref type="table">1</ref> can be considered as a valid baseline to build stronger multi-stage systems in the future.</p></div>			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="1" xml:id="foot_0">http://www.trec-cds.org/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="2" xml:id="foot_1">https://trec.nist.gov/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="3" xml:id="foot_2">https://www.nlm.nih.gov/research/umls/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="4" xml:id="foot_3">https://metamap.nlm.nih.gov/SemanticTypesAndGroups.shtml</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="5" xml:id="foot_4">https://clinicaltrials.gov/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="6" xml:id="foot_5">https://whoosh.readthedocs.io/en/latest/intro.html</note>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Acknowledgements. This work is partially supported by the ExaMode project, as part of the European Union H2020 research and innovation program under grant agreement no. 825292.</p></div>
			</div>

			<div type="annex">
<div xmlns="http://www.tei-c.org/ns/1.0"> <ref type="table">1</ref><p>: Results for the TREC PM tasks. Part A (top) reports the results achieved using the five most effective query reformulations for each year. ( ‡) indicates a particular query reformulation effective in all three years. Part B (bottom) reports the results obtained by participant runs, along with the lowest score required to enter the top 10 TREC results list and the score obtained by the best combination of our approach. Further details are reported in Section 4.</p><p>reported in part B of Table <ref type="table">1</ref> indicate the best score obtained by a particular run for a specific measure; the best results of a participant are often related to different runs. The symbol '−' means that the measure is not available, while '&lt;' indicates that none of the runs submitted by the participant achieved the top 10 performing runs. For the sake of comparison, we add for each measure the lowest score required to enter the top 10 TREC results list, and the score obtained by the best combination of our approach -indicated by the line number -as if we were participants of these tracks.</p></div>			</div>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">The University of Padua IMS Research Group at TREC 2018 PM Track</title>
		<author>
			<persName><forename type="first">M</forename><surname>Agosti</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><forename type="middle">M</forename><surname>Di Nunzio</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Marchesin</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. TREC</title>
				<meeting>TREC</meeting>
		<imprint>
			<date type="published" when="2018">2018</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">An Analysis of Query Reformulation Techniques for Precision Medicine</title>
		<author>
			<persName><forename type="first">M</forename><surname>Agosti</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><forename type="middle">M</forename><surname>Di Nunzio</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Marchesin</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. ACM SIGIR Conf</title>
				<meeting>ACM SIGIR Conf</meeting>
		<imprint>
			<date type="published" when="2019">2019</date>
			<biblScope unit="page" from="973" to="976" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Effective mapping of biomedical text to the UMLS Metathesaurus: the MetaMap program</title>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">R</forename><surname>Aronson</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. AMIA Symposium</title>
				<meeting>AMIA Symposium</meeting>
		<imprint>
			<date type="published" when="2001">2001</date>
			<biblScope unit="page" from="17" to="21" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">Exploring how to combine query reformulations for precision medicine</title>
		<author>
			<persName><forename type="first">G</forename><forename type="middle">M</forename><surname>Di Nunzio</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Marchesin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Agosti</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. TREC</title>
				<meeting>TREC</meeting>
		<imprint>
			<date type="published" when="2019">2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">The Research of Query Expansion Based on Medical Terms Reweighting in Medical IR</title>
		<author>
			<persName><forename type="first">L</forename><surname>Diao</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">EURASIP J. Wireless Comm.&amp;Networ</title>
		<imprint>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page">105</biblScope>
			<date type="published" when="2018">2018</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Medical Information Retrieval: Introduction to the Special Issue</title>
		<author>
			<persName><forename type="first">L</forename><surname>Goeuriot</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Jones</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Kelly</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Müller</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Zobel</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Inform Retrieval J</title>
		<imprint>
			<biblScope unit="volume">19</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page" from="1" to="5" />
			<date type="published" when="2016">2016</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">UTD HLTRI at TREC 2017: Precision medicine track</title>
		<author>
			<persName><forename type="first">T</forename><forename type="middle">R</forename><surname>Goodwin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">A</forename><surname>Skinner</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">M</forename><surname>Harabagiu</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. TREC</title>
				<meeting>TREC</meeting>
		<imprint>
			<date type="published" when="2017">2017</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Semi-supervised information retrieval system for clinical decision support</title>
		<author>
			<persName><forename type="first">H</forename><surname>Gurulingappa</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Toldo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Schepers</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Bauer</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Megaro</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. TREC</title>
				<meeting>TREC</meeting>
		<imprint>
			<date type="published" when="2016">2016</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">Information Retrieval: A Health and Biomedical Perspective</title>
		<author>
			<persName><forename type="first">W</forename><surname>Hersh</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Health and Informatics Series</title>
				<meeting><address><addrLine>New York, NY, USA</addrLine></address></meeting>
		<imprint>
			<publisher>Springer-Verlag</publisher>
			<date type="published" when="2009">2009</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">HPI-DHC at TREC 2018: PM Track</title>
		<author>
			<persName><forename type="first">M</forename><surname>Oleynik</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. TREC</title>
				<meeting>TREC</meeting>
		<imprint>
			<date type="published" when="2018">2018</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">Overview of PM Track</title>
		<author>
			<persName><forename type="first">K</forename><surname>Roberts</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. TREC</title>
				<meeting>TREC</meeting>
		<imprint>
			<date type="published" when="2017">2017</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title level="a" type="main">Overview of PM Track</title>
		<author>
			<persName><forename type="first">K</forename><surname>Roberts</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. TREC</title>
				<meeting>TREC</meeting>
		<imprint>
			<date type="published" when="2018">2018</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">Overview of PM Track</title>
		<author>
			<persName><forename type="first">K</forename><surname>Roberts</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. TREC</title>
				<meeting>TREC</meeting>
		<imprint>
			<date type="published" when="2019">2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<analytic>
		<title level="a" type="main">The probabilistic relevance framework: BM25 and beyond</title>
		<author>
			<persName><forename type="first">S</forename><surname>Robertson</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Zaragoza</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Foundations and Trends R in Information Retrieval</title>
		<imprint>
			<biblScope unit="volume">3</biblScope>
			<biblScope unit="issue">4</biblScope>
			<biblScope unit="page" from="333" to="389" />
			<date type="published" when="2009">2009</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<analytic>
		<title level="a" type="main">Leveraging Medical Thesauri and Physician FB for Improving Medical Literature Retrieval for Case Queries</title>
		<author>
			<persName><forename type="first">P</forename><surname>Sondhi</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">JAMIA</title>
		<imprint>
			<biblScope unit="volume">19</biblScope>
			<biblScope unit="issue">5</biblScope>
			<biblScope unit="page" from="851" to="858" />
			<date type="published" when="2012">2012</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<analytic>
		<title level="a" type="main">Using Large Clinical Corpora for QE in Text-Based Cohort Identification</title>
		<author>
			<persName><forename type="first">D</forename><surname>Zhu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Wu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Carterette</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Liu</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">J. of Biomedical Informatics</title>
		<imprint>
			<biblScope unit="volume">49</biblScope>
			<biblScope unit="page" from="275" to="281" />
			<date type="published" when="2014">2014</date>
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
