<?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">Automatic Detection of Contraindications of Medicines in Package Leaflet</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Jonas</forename><surname>Žalinkevičius</surname></persName>
							<email>jonas.zalinkevicius@hotmail.com</email>
							<affiliation key="aff0">
								<orgName type="department">Faculty of Informatics</orgName>
								<orgName type="institution">Kaunas University of Technology Kaunas</orgName>
								<address>
									<country key="LT">Lithuania</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Rita</forename><surname>Butkienė</surname></persName>
							<email>rita.butkiene@ktu.lt</email>
							<affiliation key="aff1">
								<orgName type="department">Faculty of Informatics</orgName>
								<orgName type="institution">Kaunas University of Technology Kaunas</orgName>
								<address>
									<country key="LT">Lithuania</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Automatic Detection of Contraindications of Medicines in Package Leaflet</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">48EFDB45933D3D82C53812484ED0BFE6</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-23T22:51+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>medicine contraindications</term>
					<term>drug-drug interactions</term>
					<term>shallow parsing</term>
					<term>morphological analysis</term>
					<term>noun phrase detection</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Before physicians prescribe medicines, they must take into consideration the patient's diseases and medicines they use. This is done to avoid complications that may occur. All information about possible contraindications is written in the medicine package leaflet. A system that can automatically detect contraindication mention in the Lithuanian text of leaflet applying natural language parsing is presented. This system gives a possibility to shorten the time needed for medicines prescription decision making. The results of the experiment showed that the created system successfully detected 56 per cent contraindications.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>I. INTRODUCTION</head><p>When a patient is diagnosed with a new disease, additionally physician asks the patient about his allergies, previous health problems, chronic deceases, what medications and food supplements he is using. After taking gathered information into consideration and evaluation of possible contraindications with prescribed medication physician assigns treatment and, if needed, changes previous assignments. Almost all information about contraindications can be found in the medicine package leaflet. According to Lithuania's medicines registration procedure <ref type="bibr" target="#b0">[1]</ref>, every package must have a leaflet written in Lithuanian. Information in the leaflet must be divided into six sections <ref type="bibr" target="#b1">[2]</ref>, although the text in a section can be written in not structural manner. So, if a physician needs to find possible contraindications, he must read all text in the second section (Table <ref type="table">1</ref>) or search for information on the Internet. Usually, health care information consists of unstructured data and that leads to inaccurate search results that contain hundreds of links to not relevant documents. And the user must read through results to find relevant information.</p><p>Automatic information extraction tools can extract biomedical data, save it in a structural way, and minimize information search problem. However, automatic text analysis and information extraction from unstructured text in the medical domain is a challenging task <ref type="bibr" target="#b2">[3]</ref>. The aim of this paper is to present a system that gives physicians the possibility of a faster and more accurate way of finding contraindications using automated contraindication detection in the medicine package leaflet.</p><p>A system that automates the extraction of contraindications from leaflet text is described is in Section 3. Using this system all leaflets of medicines registered in Lithuania were analyzed. The results of this analysis (contraindications extracted) are used in a commercial medications information system that is used by Lithuanian physicians for prescription of medications. The evaluation of the obtained results is presented in Section 4.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>II. RELATED WORK</head><p>In Lithuania, it is established that each medicine registered in Lithuania must contain a package leaflet describing therapeutic indications, possible contraindications, safety precautions, and usage information in the Lithuanian language. In order to be sure that the patient does not suffer from possible contraindication, the physician should read through all leaflet text before prescribing the medicine. Usually, the analysis of leaflets is time-consuming, so physicians tend to skip it and rely on the knowledge and experience they have gained.</p><p>There are lots of systems developed for analysis and information extraction from the biomedical text in the English language. But there is no solution for the detection of contraindication (i.e. contraindication with disease or contraindication with the pharmacological group) mentions in Lithuanian written text. We have analyzed articles that describe similar problems when analyzing biomedical text. For example, a tool Semantator <ref type="bibr" target="#b3">[4]</ref> was created for converting biomedical text to linked data. It used ontology-based information extraction using biomedical ontology terms hosted in BioPortal and ontology editor Protégé for text preprocessing. A semantic annotation and inference platform SENTIENT-MD <ref type="bibr" target="#b2">[3]</ref> creates a dependency graph as the first step for dependency parsing which is one of the tasks of semantic annotation of medical knowledge in natural language text. Markus Bundschus <ref type="bibr" target="#b4">[5]</ref> used probabilistic graphical models (Conditional Random Fields) to identify semantic relations.</p><p>Although all these authors work on texts written in English, we found that common rules and approaches could be applied to Lithuanian texts as well. In order to extract information from text, preprocessing is needed using natural language processing: text segmentation, a morphological analysis should be performed and then a syntactic parse tree or the dependency graph <ref type="bibr" target="#b5">[6]</ref>. <ref type="bibr" target="#b6">[7]</ref> should be formed. For semantic relations detection, existing ontologies or knowledge bases should be used.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>III. SYSTEM DESCRIPTION</head><p>In this section, a system for the detection of contraindication mentions in the medicine leaflet text written in Lithuanian is presented. The system implements a text analysis pipeline of four analysis stages: extraction of contraindication text block, morphological analysis, noun phrase detection, and annotation.</p><p>Additionally, all annotated phrases are checked is it in the database of noun phrases to be ignored or not. This database is manually filled and helps to obtain more precise results. The overall pipeline for the detection of contraindication mentions is shown in fig. <ref type="figure" target="#fig_0">1</ref>.</p><p>Below each stage of text analysis is discussed in more detail.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>A. Extraction of contraindication text blocks</head><p>In Lithuania, when describing the medicine, a producer must follow a certain template of the package leaflet <ref type="bibr" target="#b1">[2]</ref>. This template splits the description of leaflet into 6 sections listed in Table 1 The information which, the patient should be aware of before he or she takes the medicine, is presented in section number two. An example of this section is shown in fig. <ref type="figure">2</ref> with highlighted contraindications phrases. So, the first task of our system is to find this section and extract its text for further analysis.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>B. Morphological analysis</head><p>A morphological analysis forms a background for information extraction about contraindications. In this stage, a given text is split into lexical units (e.g. sentences, lexemes) and analyzed morphologically. For this task, a web service provided by the system "http://semantika.lt" <ref type="bibr" target="#b7">[8]</ref> is used. The web service returns morphological features for each given lexeme: part of speech, gender, number and so on.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>C. Noun phrase detection</head><p>Phrases that express a specific contraindication usually are noun phrases, for example, heart attack, type one diabetes, pancreatitis, and so on. Therefore, we chose a phrase structure grammar method because it better fits for noun phrase detection than dependency grammar as it was suggested by Axel Halvoet in his monography <ref type="bibr" target="#b8">[9]</ref>. Phrase structure rules are used to split natural language written sentence into its constituent parts: lexical and phrasal categories <ref type="bibr" target="#b8">[9]</ref>, <ref type="bibr" target="#b9">[10]</ref>, <ref type="bibr" target="#b10">[11]</ref>. For the noun phrase detection in the medicine's leaflet, three phrase structure rules ware specified (see Table <ref type="table">2</ref>). An algorithm implemented for the noun phrase detection checks every lexeme in the sentence for the satisfaction of conditions of at least one rule presents in Table <ref type="table">2</ref>. If the condition is satisfied a lexeme is included in the noun phrase. The workflow of analysis of the noun phrase Lėtinis reumatinis perikarditas (Chronic rheumatic pericarditis) is shown in Table <ref type="table">3</ref>.  When the construction of the noun phrase is complete the form of the head noun in the phrase is changed to its canonical form (lemma). This is done because the name of item registered in the International Classification of Diseases (ICD) <ref type="bibr" target="#b11">[12]</ref>, Anatomical Therapeutic Chemical Classification System (ATC) <ref type="bibr" target="#b12">[13]</ref> or lists of active substances are in the canonical form, therefore, normalization is required to ensure the correct comparison of values in the next stage of analysis.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>D. Annotation</head><p>All noun phrases identified in the previous stage are reviewed and checked for contraindication. If a contraindication is identified, the phrase is annotated. For annotation three databases are used: ICD, ATC and the lists of active substances. The algorithm compares the noun phrase and name of the item from the database. If the noun phrase matches the name in ICD the phrase is tagged as contraindication with the disease. If the phrase matches the ATC item name, it is tagged as contraindication with a pharmaceutical chemical group, and if the phrase matches the name of the active substance, it is tagged as contraindication with an active substance.</p><p>It is worthy to mention that before comparison of the noun phrases all identified phrases are checked against phrases in the database of noun phrases to be ignored. In the text of medicine package leaflet, a lot of words (i.e. illness, hand and so on) that are irrelevant (do not express a contraindication) but are used in ICD, ATC and active substances lists could be found. The database of noun phrases to be ignored was filled manually with the help of a professional pharmacist.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>IV. EXPERIMENT</head><p>The aim of the experiment is to evaluate the created system and check if a tool can achieve its target -to give physicians the possibility of a faster and more accurate way of finding contraindications. The experiment was done by manually annotating contraindications mentions in the package leaflet text block and comparing results with the system's results. This was done by a professional pharmacist who works in JSC Skaitos kompiuterių servisas.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>A. Plan</head><p>The experiment was organized as follows. From medicines database ten randomly selected leaflets were analyzed using the system created. The results of the analysis were automatically gathered into the table, which example is presented in Table <ref type="table">4</ref> In the first column the code of item automatically found in the text of leaflet by the system is indicated. The second column represents the database (ATC, ICD or active substances) where the item is registered. The third column was used for the evaluation of annotation correctness. The same randomly selected leaflets were analyzed and annotated manually, and the table of the same structure was filled in with manual annotation results. Manually found contraindications were not interpreted or changed to synonyms. For example, heart attack and myocardial infarction are the same diseases. But ICD contains only one name of this disease -myocardial infarction. The created system is not able to recognize the heart attack as a synonym of myocardial infarction.</p><p>Additionally, the active substances, mentioned in leaflet, were translated into the Latin language (nominative and genitive grammatical cases). This was done because the database of active substances, that was provided, has three versions of translation: Lithuanian, Latin in the nominative case and Latin in the genitive case.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>B. Results</head><p>The results of the evaluation are presented in Table <ref type="table">5</ref>. The precision, recall and F-Score metrics have been calculated for each leaflet analyzed. Additionally, the ratio between the number of correctly detected contraindications and overall automatically detected contraindications was calculated as well. This metric allows to evaluate how accurate the results are and to use them in further calculations.</p><p>Results showed that the system developed is able to correctly detect 56% of relevant contraindications. The average number of links detected automatically is 1482.8 while manually detected links are 197.9. The number of links detected automatically in one leaflet is average four times higher, than detected manually. The average number of erroneous links to ICD is 72%, to ATC -90%, and links to the list of active substances -61%.</p><p>Calculations show that the system is able to achieve 0.25(±0.23) precision, 0.56(±0.32) recall, and 0.31(±0.19) Fscore value. To give a better perspective where the system's failures were and possible reasons for that, Pearson correlation coefficient calculations between various indicators were done (Table <ref type="table">6</ref>). The biggest impact on F-Score had incorrectly detected links to ICD, a coefficient was -0.89. The reason why precision was so low is that of the high ratio between automatically and manually detected links.  </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>C. Conclusions of the experiment</head><p>The experiment shows that the system automatically successfully detected more than half of the relevant contraindication links (56%). But 75% of links were erroneous and the system lacks precision. The reason for that is a high number of incorrect links to ICD (r=-0.9655), this indicator has the most negative impact on the precision and F-Score results. This might be because of commonly used phrases that are not contraindications but used in the ICD list. For example, the word allergy does not imply that this is a contraindication and must be ignored. Another reason for low estimates results is, the number of detected contraindications phrases. Calculations show, that the higher is the difference between automatically and manually detected contraindications phrases, the lower are precision and F-Score results. The reason for that is, a high number of noun phrases that are irrelevant to contraindications noun phrases, for example, pill, driving.</p><p>Additionally, considering why F-Score is so low (0.31) the assumption that this is because of low precision (0.25) can be done. To raise this indicator the list of phrases to be ignored (common word and phrases) must be used. The most frequent reasons for the incorrect detection of contraindications are:</p><p> the context of the phrase in the sentence is not taken into account;</p><p> Conjunctions are not taken into account and two or more noun phrases (i.e. "…kidney and liver diseases…") are not identified;</p><p> Brackets that are used to specify contraindication are not taken into account ("…liver tumor (malignant or benign)…").</p><p>To avoid errors caused by those reasons, users of "https://gydytojams.vaistai.lt" IS will be able to mark contraindication as erroneous and if the pharmacist approves that it will be removed from the database.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>V. CONCLUSIONS</head><p>In this paper, the system which automatically detects contraindications and links them to existing "Skaitos kompiuterių servisas" databases have been introduced. System analyses text of medications leaflets, it extracts noun phrases and links them to corresponding items in ATC, ICD, and active substances list. The system presented was used for the extraction of contraindications from leaflets of all medications registered in Lithuania. Extracted data was used in the pilot project for extending the functionality of the system "https://gydytojams.vaistai.lt". The additional function supports physicians in search of possible contraindications that are relevant to patient medical records. Moreover, physicians have the possibility to give feedback about erroneous contraindications presented. In such a way they help in expanding the list of phrases to be ignored and eliminating incorrect contraindication links.</p><p>The experiment shows that approximately 56% of contraindications are found but only every fourth is correct. Several changes in the algorithm remain for future work. First, before the noun phrase is looked up in databases, a context must be identified. This would reduce the number of incorrect links. Second, to detect phrases that refer to medication analyzed and to ignore them.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Fig. 1 .</head><label>1</label><figDesc>Fig. 1. Contraindications lookup process activity</figDesc><graphic coords="2,50.76,544.56,492.60,196.38" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0"><head></head><label></label><figDesc></figDesc><graphic coords="3,50.88,85.20,488.88,238.44" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_0"><head>TABLE I</head><label>I</label><figDesc></figDesc><table><row><cell></cell><cell>.</cell><cell>MEDICINE PACKAGE LEAFLET SECTIONS</cell></row><row><cell>No</cell><cell></cell><cell>Section</cell></row><row><cell>1</cell><cell cols="2">What X is and what it is used for</cell></row><row><cell>2</cell><cell cols="2">What you need to know before you &lt;take&gt; &lt;use&gt; X</cell></row><row><cell>3</cell><cell cols="2">How to &lt;take&gt; &lt;use&gt; X</cell></row><row><cell>4</cell><cell cols="2">Possible side effects</cell></row><row><cell>5</cell><cell cols="2">How to store X</cell></row><row><cell>6</cell><cell cols="2">Contents of the pack and other information</cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_1"><head>TABLE II</head><label>II</label><figDesc></figDesc><table><row><cell></cell><cell>.</cell><cell>NOUN PHRASE STRUCTURE RULES</cell></row><row><cell>No</cell><cell></cell><cell>Rule</cell></row><row><cell></cell><cell cols="2">A lexeme is a part of a noun phrase if it is a noun in the genitive</cell></row><row><cell>1</cell><cell cols="2">case and follows another noun in the genitive case or adjective or</cell></row><row><cell></cell><cell cols="2">numeral or participle.</cell></row></table><note>2A lexeme is a part of a noun phrase if it is an attributive adjective in the same case, number, and gender as a base noun and follows noun in the genitive case or adjective or numeral or participle.3A lexeme is a part of noun phrase if it is an attributive numeral in the same case, number and gender as the base noun and follows noun in the genitive case, or adjective, or numeral, or participle.</note></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_2"><head>TABLE III .</head><label>III</label><figDesc></figDesc><table><row><cell></cell><cell>The second word reumatinis</cell><cell cols="3">No rule condition is satisfied</cell></row><row><cell></cell><cell>is an adjective in the</cell><cell cols="3">fully, but according to rule</cell></row><row><cell>2</cell><cell>nominative case, singular and</cell><cell cols="3">No. 2 the lexeme is a good</cell></row><row><cell></cell><cell>of masculine gender and</cell><cell cols="3">candidate for the noun phrase.</cell></row><row><cell></cell><cell>follows the adjective Lėtinis</cell><cell></cell><cell></cell></row><row><cell></cell><cell></cell><cell cols="3">The condition of rule No. 2 is</cell></row><row><cell></cell><cell>The third word perikarditas is</cell><cell cols="3">satisfied. The noun is a base</cell></row><row><cell></cell><cell>a noun in the nominative case,</cell><cell cols="3">noun for the first two</cell></row><row><cell></cell><cell>singular and of masculine</cell><cell>adjectives.</cell><cell>They</cell><cell>are</cell></row><row><cell>3</cell><cell>gender It follows the adjectives lėtinis and</cell><cell cols="3">attributive adjectives of the noun. So, the condition of rule</cell></row><row><cell></cell><cell>reumatinis which are in the</cell><cell cols="3">No. 2 is satisfied as well. The</cell></row><row><cell></cell><cell>same case, number and</cell><cell cols="3">analysis of the third lexeme</cell></row><row><cell></cell><cell>gender.</cell><cell cols="3">completes the construction of</cell></row><row><cell></cell><cell></cell><cell cols="2">the noun phrase.</cell></row></table><note>EXAMPLE OF NOUN PHRASE DETECTION WORKFLOW Step Action Rule satisfaction 1 The first lexeme Lėtinis (Chronic) is an adjective in the nominative case, singular and of masculine gender No rule condition is satisfied fully, but according to rule No. 2 the lexeme is a good candidate for the noun phrase.</note></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_3"><head>TABLE IV</head><label>IV</label><figDesc></figDesc><table><row><cell></cell><cell>.</cell><cell cols="2">AUTOMATICALLY DETECTED CONTRAINDICATIONS</cell></row><row><cell></cell><cell cols="3">RESULTS EVALUATION FOR SINGLE LEAFLET</cell></row><row><cell>Code</cell><cell></cell><cell>Domain</cell><cell>Is detection correct</cell></row><row><cell>J01CR</cell><cell>ATC</cell><cell></cell><cell>False</cell></row><row><cell>J05AE</cell><cell>ATC</cell><cell></cell><cell>True</cell></row><row><cell>I09.2</cell><cell>ICD</cell><cell></cell><cell>True</cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_4"><head>TABLE V</head><label>V</label><figDesc></figDesc><table><row><cell></cell><cell></cell><cell></cell><cell></cell><cell>.</cell><cell cols="2">EXPERIMENT RESULTS</cell><cell></cell><cell></cell><cell></cell><cell></cell></row><row><cell>ID</cell><cell>Auto.</cell><cell>Auto.</cell><cell>Man.</cell><cell>Precision</cell><cell>Recall</cell><cell>F-Score</cell><cell>Ratio of</cell><cell>Err. links</cell><cell>Err. links</cell><cell>Err. links</cell></row><row><cell></cell><cell>detected</cell><cell>correctly</cell><cell>detected</cell><cell></cell><cell></cell><cell></cell><cell>links</cell><cell>to ICD</cell><cell>to ATC</cell><cell>to active</cell></row><row><cell></cell><cell>links</cell><cell>detected</cell><cell>links</cell><cell></cell><cell></cell><cell></cell><cell>amounts</cell><cell></cell><cell></cell><cell>substances</cell></row><row><cell></cell><cell></cell><cell>links</cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell></row><row><cell>13092</cell><cell>1906</cell><cell>346</cell><cell>385</cell><cell>0.18</cell><cell>0.90</cell><cell>0.30</cell><cell>4.95</cell><cell>82%</cell><cell>100%</cell><cell>65%</cell></row><row><cell>13571</cell><cell>1899</cell><cell>367</cell><cell>444</cell><cell>0.19</cell><cell>0.83</cell><cell>0.31</cell><cell>4.28</cell><cell>81%</cell><cell>100%</cell><cell>58%</cell></row><row><cell>859</cell><cell>87</cell><cell>67</cell><cell>162</cell><cell>0.77</cell><cell>0.41</cell><cell>0.54</cell><cell>0.54</cell><cell>17%</cell><cell>100%</cell><cell>100%</cell></row><row><cell>1300</cell><cell>400</cell><cell>28</cell><cell>146</cell><cell>0.07</cell><cell>0.19</cell><cell>0.10</cell><cell>2.74</cell><cell>98%</cell><cell>100%</cell><cell>24%</cell></row><row><cell>10958</cell><cell>464</cell><cell>14</cell><cell>71</cell><cell>0.03</cell><cell>0.20</cell><cell>0.05</cell><cell>6.54</cell><cell>100%</cell><cell>25%</cell><cell>21%</cell></row><row><cell>1872</cell><cell>283</cell><cell>66</cell><cell>68</cell><cell>0.23</cell><cell>0.97</cell><cell>0.38</cell><cell>4.16</cell><cell>77%</cell><cell>100%</cell><cell>43%</cell></row><row><cell>5363</cell><cell>473</cell><cell>237</cell><cell>291</cell><cell>0.50</cell><cell>0.81</cell><cell>0.62</cell><cell>1.63</cell><cell>46%</cell><cell>88%</cell><cell>49%</cell></row><row><cell>13273</cell><cell>158</cell><cell>51</cell><cell>72</cell><cell>0.32</cell><cell>0.71</cell><cell>0.44</cell><cell>2.19</cell><cell>45%</cell><cell>100%</cell><cell>100%</cell></row><row><cell>10744</cell><cell>1199</cell><cell>150</cell><cell>175</cell><cell>0.13</cell><cell>0.29</cell><cell>0.18</cell><cell>6.85</cell><cell>87%</cell><cell>100%</cell><cell>100%</cell></row><row><cell>16551</cell><cell>1090</cell><cell>120</cell><cell>204</cell><cell>0.11</cell><cell>0.25</cell><cell>0.15</cell><cell>5.34</cell><cell>90%</cell><cell>87%</cell><cell>51%</cell></row><row><cell>Median</cell><cell>468.5</cell><cell>93.5</cell><cell>168.5</cell><cell>0.185</cell><cell>0.56</cell><cell>0.305</cell><cell>4.22</cell><cell>82%</cell><cell>100%</cell><cell>55%</cell></row><row><cell>Q1</cell><cell>312.25</cell><cell>54.75</cell><cell>90.5</cell><cell>0.115</cell><cell>0.26</cell><cell>0.158</cell><cell>2.328</cell><cell>54%</cell><cell>91%</cell><cell>45%</cell></row><row><cell>Q3</cell><cell>1171.75</cell><cell>215.25</cell><cell>269.25</cell><cell>0.298</cell><cell>0.825</cell><cell>0.425</cell><cell>5.243</cell><cell>89%</cell><cell>100%</cell><cell>91%</cell></row><row><cell>Avg</cell><cell>795.9</cell><cell>144.6</cell><cell>201.8</cell><cell>0.25</cell><cell>0.56</cell><cell>0.31</cell><cell>3.92</cell><cell>72%</cell><cell>90%</cell><cell>61%</cell></row><row><cell>Std dev</cell><cell>686.52</cell><cell>129.45</cell><cell>132.27</cell><cell>0.23</cell><cell>0.32</cell><cell>0.19</cell><cell>2.10</cell><cell>27%</cell><cell>23%</cell><cell>30%</cell></row><row><cell>Min</cell><cell>87</cell><cell>14</cell><cell>68</cell><cell>0.03</cell><cell>0.19</cell><cell>0.05</cell><cell>0.54</cell><cell>17%</cell><cell>25%</cell><cell>21%</cell></row><row><cell>Max</cell><cell>1906</cell><cell>367</cell><cell>444</cell><cell>0.77</cell><cell>0.97</cell><cell>0.62</cell><cell>6.85</cell><cell>100%</cell><cell>100%</cell><cell>100%</cell></row></table></figure>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><p>ACKNOWLEDGMENT Data for this system was provided by JSC Skaitos kompiuterių servisas</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">Įsakymas 2015 m</title>
		<author>
			<persName><forename type="first">L</forename><forename type="middle">R</forename><surname>Vvkt</surname></persName>
		</author>
		<author>
			<persName><surname>Sam</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Dėl paraiškų registruoti vaistinį preparatą, perregistruoti vaistinį preparatą, pakeisti registracijos pažymėjimo sąlygas, teisės į vaistinio preparato registraciją perleidimo, nereglamentiniam pakuotės ir</title>
				<imprint>
			<biblScope unit="volume">03</biblScope>
			<biblScope unit="page" from="7" to="2016" />
		</imprint>
	</monogr>
	<note>liepos 3 d. Nr.(1.72E</note>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title/>
	</analytic>
	<monogr>
		<title level="j">European Medicines Agency</title>
		<imprint>
			<biblScope unit="page">2</biblScope>
			<date type="published" when="2019">2019</date>
			<publisher>European Medicines Agency</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<monogr>
		<title level="m" type="main">Semantic Annotation and Inference for Medical Knowledge Discovery</title>
		<author>
			<persName><forename type="first">S</forename><surname>Sahay</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Agichtein</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Li</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><forename type="middle">V</forename><surname>Garcia</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Ram</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2007">2007</date>
		</imprint>
	</monogr>
	<note>Online</note>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">Semantator: Semantic annotator for converting biomedical text to linked data</title>
		<author>
			<persName><forename type="first">C</forename><surname>Tao</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Song</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Sharma</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><forename type="middle">G</forename><surname>Chute</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Journal of Biomedical Informatics</title>
		<imprint>
			<biblScope unit="volume">46</biblScope>
			<biblScope unit="issue">5</biblScope>
			<biblScope unit="page">12</biblScope>
			<date type="published" when="2016">Oct2016</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">Extraction of semantic biomedical relations from text using conditional random fields</title>
		<author>
			<persName><forename type="first">M</forename><surname>Bundschus</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Dejori</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Stetter</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Tresp</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H.-P</forename><surname>Kriegel</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">BMC Bioinformatics</title>
		<imprint>
			<biblScope unit="volume">9</biblScope>
			<biblScope unit="page" from="1" to="14" />
			<date type="published" when="2008">2008</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Leveraging syntactic and semantic graph kernels to extract pharmacokinetic drug drug interactions from biomedical literature</title>
		<author>
			<persName><forename type="first">Y</forename><surname>Zhang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H.-Y</forename><surname>Wu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Xu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Wang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Ergin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Li</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Xu</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">BMC Systems Biology</title>
		<imprint>
			<biblScope unit="volume">107</biblScope>
			<biblScope unit="page" from="8" to="26" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<monogr>
		<title level="m" type="main">Phrase Structure Composition and Syntactic Dependencies</title>
		<author>
			<persName><forename type="first">R</forename><surname>Frank</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2002">2002</date>
			<publisher>The MIT Press</publisher>
			<biblScope unit="volume">38</biblScope>
			<biblScope unit="page" from="2" to="27" />
			<pubPlace>Cambridge, Mass</pubPlace>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">IMF mode demixing in EMD for jitter analysis</title>
		<author>
			<persName><forename type="first">R</forename><surname>Damaševičius</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Napoli</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Sidekerskienė</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Woźniak</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Journal of Computational Science</title>
		<imprint>
			<biblScope unit="volume">22</biblScope>
			<biblScope unit="page" from="240" to="252" />
			<date type="published" when="2017">2017</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<monogr>
		<title level="m">Lietuvių kalbos sintaksinės ir semantinės analizės informacinė sistema</title>
				<imprint/>
		<respStmt>
			<orgName>Kaunas University of Technology and Vytautas Magnus University</orgName>
		</respStmt>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<monogr>
		<author>
			<persName><forename type="first">A</forename><surname>Holvoet</surname></persName>
		</author>
		<title level="m">Vilniaus Universitetas, Asociacija</title>
				<meeting><address><addrLine>Vilnius</addrLine></address></meeting>
		<imprint>
			<publisher>Academia Salensis</publisher>
			<date type="published" when="2009">2009</date>
		</imprint>
	</monogr>
	<note>Bendrosios sintaksės pagrindai</note>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">Formal Grammars of English</title>
		<author>
			<persName><forename type="first">D</forename><surname>Jurafsky</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">H</forename><surname>Martin</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Speech and Language Processing (2Nd Edition)</title>
				<imprint>
			<publisher>Prentice-Hall, Inc</publisher>
			<date type="published" when="2009">2009</date>
			<biblScope unit="page" from="396" to="408" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title level="a" type="main">Lietuvių kalbos sintaksinė analizė</title>
		<author>
			<persName><forename type="first">D</forename><surname>Šveikauskienė</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Lietuvių kalba</title>
		<imprint>
			<biblScope unit="volume">7</biblScope>
			<date type="published" when="2013">2013</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">Novel approach toward medical signals classifier</title>
		<author>
			<persName><forename type="first">M</forename><surname>Wózniak</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Połap</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><forename type="middle">K</forename><surname>Nowicki</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Napoli</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Pappalardo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Tramontana</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">International Joint Conference on Neural Networks (IJCNN)</title>
				<imprint>
			<publisher>IEEE</publisher>
			<date type="published" when="2015-07">2015. July. 2015</date>
			<biblScope unit="page" from="1" to="7" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<monogr>
		<title level="m">TLK-10-AM / ACHI / ACS elektroninis vadovas</title>
				<imprint/>
	</monogr>
	<note>Valstybinė ligonių kasa</note>
</biblStruct>

<biblStruct xml:id="b14">
	<monogr>
		<title level="m">WHOCC -Structure and principles</title>
				<imprint/>
		<respStmt>
			<orgName>Norwegian Institute of Public Health</orgName>
		</respStmt>
	</monogr>
</biblStruct>

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