<?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">DIMMI -Drug InforMation Mining in Italian: A CALAMITA Challenge</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Raffaele</forename><surname>Manna</surname></persName>
							<email>raffaele.manna@unior.it</email>
							<affiliation key="aff0">
								<orgName type="institution">University of Naples &quot;L&apos;Orientale&quot;</orgName>
								<address>
									<addrLine>via Duomo 219</addrLine>
									<postCode>80139</postCode>
									<settlement>Napoli</settlement>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Maria</forename><surname>Pia Di Buono</surname></persName>
							<affiliation key="aff0">
								<orgName type="institution">University of Naples &quot;L&apos;Orientale&quot;</orgName>
								<address>
									<addrLine>via Duomo 219</addrLine>
									<postCode>80139</postCode>
									<settlement>Napoli</settlement>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Luca</forename><surname>Giordano</surname></persName>
							<email>giordanoluca.uni@gmail.com</email>
							<affiliation key="aff0">
								<orgName type="institution">University of Naples &quot;L&apos;Orientale&quot;</orgName>
								<address>
									<addrLine>via Duomo 219</addrLine>
									<postCode>80139</postCode>
									<settlement>Napoli</settlement>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<author>
							<affiliation key="aff1">
								<orgName type="department">Tenth Italian Conference on Computational Linguistics</orgName>
								<address>
									<addrLine>Dec 04 -06</addrLine>
									<postCode>2024</postCode>
									<settlement>Pisa</settlement>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">DIMMI -Drug InforMation Mining in Italian: A CALAMITA Challenge</title>
					</analytic>
					<monogr>
						<idno type="ISSN">1613-0073</idno>
					</monogr>
					<idno type="MD5">C193FB9449B70EED7B3FECCD2E415829</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2025-04-23T17:34+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>Patient information leaflets, Information extraction, Large Language Models, Italian L. Giordano) 0009-0006-6285-8557 (R. Manna)</term>
					<term>0009-0009-9372-3323 (M. P. d. Buono)</term>
					<term>0009-0002-3048-4408 (L. Giordano)</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Patients' knowledge about drugs and medications is crucial as it allows them to administer them safely. This knowledge frequently comes from written prescriptions, patient information leaflets (PILs), or from reading drug Web pages. DIMMI (Drug InforMation Mining in Italian) is a challenge aiming at evaluating the proficiency of Large Language Models in extracting drug-specific information from PILs. The challenge seeks to advance the understanding of effectiveness in processing complex medical information in Italian, and to enhance drug information extraction and pharmacovigilance efforts. Participants are provided with a dataset of 600 Italian PILs and the objective is to develop models capable of accurately answering specific questions related to drug dosage, usage, side effects, drug-drug interactions. The challenge should be approached as an information extraction task through a zero-shot mode, purely based on the model pre-existing knowledge and understanding or through in-context learning (Retrieval-Augmented Generation (RAG) or few-shot mode). The answers generated by the models will be compared against the gold standard (GS), created to establish a reliable, accurate, and a comprehensive set of answers against which participant submissions can be evaluated. For each drug and each information category, the GS contains the correct information extracted from the leaflets through a manual annotation.</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 Motivation</head><p>Patients' knowledge about drugs and medications is crucial as it allows them to administer them safely. This knowledge frequently comes from written prescriptions, patient information leaflets (PILs), or from reading drug Web pages. Nevertheless, this information has been described as often inconsistent, incomplete, and difficult for patients to read and understand <ref type="bibr" target="#b0">[1]</ref>. Despite the fact that in 2009 the European Commission issued guidelines 1  to recommend the publication of patient information leaflets with accessible and understandable information for patients, several scholars <ref type="bibr" target="#b1">[2,</ref><ref type="bibr" target="#b2">3,</ref><ref type="bibr" target="#b3">4]</ref> account for the absence of improvement in the readability of such documents. Thus, educating patients about their medications seems to be a challenging task due to the linguistic nature of drug written information, which includes a high presence of specialized terms used to describe adverse drug reactions, diseases and other medical concepts that 1 </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>GUIDELINE ON THE READABILITY OF THE LABELLING AND PACKAGE LEAFLET OF MEDICINAL PRODUCTS FOR HUMAN USE -European Commission (2009).</head><p>https://health.ec.europa.eu/document/download/ d8612682-ad17-40e3-8130-23395ec80380_en are not easy to understand. Recently, there has been a growing interest in the utilization of Large Language Models (LLMs) within the medical field to improve various aspects of healthcare, including medical education and clinical decision-making support <ref type="bibr" target="#b4">[5]</ref>. Several specialized medical LLMs have been developed through novel pre-training methodologies or enhancements of existing models. Moreover, several evaluation campaigns have been undertaken to evaluate the efficacy of natural language processing models in facilitating knowledge retrieval for clinicians and patients alike. Examples of such campaigns are the 1) Medical Question Answering Task at TREC-2017 LiveQA <ref type="bibr" target="#b5">[6]</ref> and subsequent studies <ref type="bibr" target="#b6">[7]</ref>, which led to two datasets, LiveQA and Med-icationQA; 2) the tasks on Medical Consumer Question Answering proposed by Nguyen et al. <ref type="bibr" target="#b7">[8]</ref> based on their dataset MedRedQA. Both campaigns have contributed significantly to bridging the gap between consumers' medication questions and trusted answers, and, more generally, to the development of resources tailored to healthcare information retrieval. For a thorough survey of evaluation campaigns on clinical natural language processing refer to Filannino and Uzuner <ref type="bibr" target="#b8">[9]</ref>. The application of LLMs as patient assistants to support drug knowledge and ease their administration seems very attractive, however it needs to be evaluated carefully due to the presence of model hallucinations, potentially causing medical malpractice <ref type="bibr" target="#b9">[10]</ref>, as any concealed inaccuracies in diagnoses and health advice could lead to severe outcomes <ref type="bibr" target="#b10">[11]</ref>. For these reasons, in the evolving landscape of Artificial Intelligence (AI) applications in medicine, considerations have been raised regarding the regulatory approval of LLMs as medical devices, highlighting the ethical and legal dimensions associated with deploying such technologies in healthcare settings <ref type="bibr" target="#b11">[12]</ref>.</p><p>To delve deeper into this topic, within the CALAMITA campaign <ref type="bibr" target="#b12">[13]</ref>, we introduce DIMMI (Drug InforMation Mining in Italian), a challenge centered on evaluating the proficiency of LLMs in extracting drug-specific information from Italian PILs. By this, the task aims at contributing to the development of AI systems for enhancing drug information extraction and pharmacovigilance efforts, specifically for the Italian language.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">DIMMI</head><p>As DIMMI seeks to advance the understanding of LLM effectiveness in processing complex medical information in Italian, participants are provided with the complete leaflets for each drug and the objective is to develop models capable of accurately answering specific questions related to a drug, such as its dosage, usage, etc. The challenge should be approached as an information extraction task through a zero-shot mode, purely based on the model pre-existing knowledge and understanding or through in-context learning (Retrieval-Augmented Generation (RAG) or few-shot mode). The answers generated by the models will be compared against the gold standard (GS), created to establish a reliable, accurate, and comprehensive set of answers against which participant submissions can be evaluated. For each drug and each information category (e.g., dosage, usage, side effects, drug-drug interactions), the GS contains the correct information extracted from the leaflets, manually annotated according to some categories described in Section 4.1.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">Data description</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.1.">Origin of data</head><p>The challenge dataset is derived from the D-LeafIT Corpus <ref type="bibr" target="#b13">[14]</ref>, available on GitHub 2 , made up of 1819 Italian drug package leaflets. The corpus has been created extracting PILs available on the Italian Agency for Medications (Agenzia Italiana del Farmaco -AIFA) website 3 , among which 1439 refer to generic drugs and 380 to class A drugs. In the original corpus, the generic drug leaflets amount to 6,154,007 tokens while the class A to 1,650,879 tokens, for a total amount of 7,804,886 tokens. The DIMMI dataset 2 https://github.com/unior-nlp-research-group/D-LeafIT 3 https://www.aifa.gov.it/en/home represents a subset of 600 entries randomly selected from the D-LeafIT corpus.</p><p>It is worth stressing that the information is extracted from pdf files and converted into texts, this means that some errors and typos may occur. Furthermore, the original D-LeafIT presents some data noise, e.g., the presence of paratext, and wrong encoding from pdf files. To fix these issues, we perform a cleaning procedure as a pre-processing phase, to obtain the final dataset. The procedure is mainly automatic and based on recurrent patterns, so that some of the aforementioned issues could be still present. The dataset pre-processing phase can be summarized in two main steps, that are: </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.2.">Data format</head><p>The whole leaflets are provided in the dataset, so that the context is available. Additionally we provide the drug name for each leaflet. The final dataset, released<ref type="foot" target="#foot_0">4</ref> as a .tsv (tab-separated values) format, contains four columns. For</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>ID</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>ID_Loc</head><p>Drug_Name Text 119 119_276 BOTAM BOTAM 0,4 mg capsule (...) Tamsulosina cloridrato Medicinale equivalente (...).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Table 1</head><p>Example of a DIMMI entry each entry we present an ID, an ID_LOC which indicates the id location in the original corpus, the drug name (without any reference to the ingredient amount, the dosage form, and the pharmaceutical company), and the leaflet text (Table <ref type="table">1</ref>). Participants in the DIMMI challenge are required to use LLMs to extract the following information from the PILs text: 'Molecule', 'Usage', 'Dosage', 'Drug Interaction', and 'Side Effect'. These information must be provided as output in a structured format such as TSV or JSON, with reference to each ID and drug name contained in the evaluation dataset. The information extracted for each ID and drug name with reference to 'Molecule', 'Usage', 'Dosage', 'Drug Interaction', and 'Side Effect' must be represented in the form of a list of strings (see Section 4.2). The evaluation dataset for the DIMMI corpus contains columns for the following entity types: 'Molecule', 'Usage', 'Dosage', 'Drug Interaction', and 'Side Effect'. For each instance (drug leaflet) in the DIMMI corpus, these entity-specific columns are populated with a list of strings, representing the annotated entities of the corresponding type. The 'Molecule' column will contain a list of the unique molecular entities mentioned in the text, while the 'Usage' column will include a list of the specific uses or indications for the drug. The 'Dosage' column will hold a list of the textual spans describing the dosage, administration, or regimen information. The 'Drug Interaction' column will contain a list of the potential interactions with other drugs, and the 'Side Effect' column will include a list of the adverse effects associated with the drug.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.3.">Prompting</head><p>For each drug in the dataset, we evaluate the results from two types of zero-shot prompts in Italian, i.e., specific task-focused prompts and structured prompts.</p><p>The former type is composed of five questions for each of the information type we want to extract, as reported below<ref type="foot" target="#foot_1">5</ref> :</p><p>1. Qual è la molecola di {drug_name}? (What is the molecule of {drug_name}?) -to extract the molecule 2. Per cosa si usa {drug_name}? (What is {drug_name} used for?) -to extract the usage 3. Qual è la posologia raccomandata per {drug_name}? (What is the recommended dosage for {drug_name}?) -to extract the dosage 4. Quali sono gli effetti collaterali di {drug_name}?</p><p>(What are the potential side effects of taking {drug_name}?) -to extract side effects 5. Con quali medicinali interagisce {drug_name}?</p><p>(What are the drug interaction of {drug_name}?) -to extract the interaction with other drugs</p><p>The latter type of prompt aims at extracting all the relevant information with a specific instruction to help the model understand the expected output structure and facilitates extraction as it follows:</p><p>• Fornisci le seguenti informazioni su {drug_name}: Molecola: Uso: Posologia: Effetti collaterali: Interazioni con altri medicinali: (Provide the following information about {drug_name}: Molecule: Usage: Dosage: Side Effects: Drug interaction:)</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.4.">Dataset statistics</head><p>As mentioned before, the final dataset is composed by 600 unique PILs in Italian, providing a comprehensive dataset for the challenge. The documents in the DIMMI dataset exhibit a wide range of lengths ( </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">Evaluation metrics</head><p>We will evaluate the results using accuracy, precision, recall and F-1 score using a gold standard as benchmark (see Section 4.1). The details for each metric are provided below: </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.1.">Gold Standard Creation</head><p>In order to evaluate the system results, we created a gold standard (GS), manually annotating the following categories: i) molecule; ii) dosage; iii) drug interaction; iv) usage; v) side effect. For each of the aforementioned classes we define some guidelines and specifications for the annotation, as summarised in the following paragraphs.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Molecule</head><p>The category is used to identify the main ingredient(s) of the drug. In some cases, the bulking agent(s) may be reported together with the molecule(s). These are not included in the molecule class.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Dosage information</head><p>This class refers to the recommended dosage for drug administration. We do not annotate the treatment duration neither the maximum dosage in the dosage information.</p><p>For dosage information we distinguish between dosage for children and adults. We do not distinguish dosage for infants or elders (the former is annotated as dosage information for children, the latter as dosage information for adults, as reported below).</p><p>When the same dosage can be used for both adults and children, the general dosage information category is applied.</p><p>Example: 10 mg una volta al giorno negli adulti e nei bambini di età uguale o superiore ai 10 anni (10 mg once a day in adults and children aged 10 years or older) Furthermore, dosage information could be differentiated on the basis of age/weight. In such cases, unless dosages for adults and children are explicitly differentiated, we always use the general category dosage.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Example:</head><p>Adulti, anziani e bambini di età pari o superiore a 12 anni con un peso corporeo pari o superiore a 50 chilogrammi (kg): • da 1 a 2 g una volta al giorno a seconda della gravità e del tipo di infezione (Adults, elderly, and children aged 12 years and older with a body weight of 50 kilograms (kg) or more: • 1 to 2 g once a day, depending on the severity and type of infection.) Dosage for infants can be expressed through a coreference to some other dosage, e.g., for adults or children, sometimes with a different time schedule, as in lo stesso dosaggio sopra descritto ma somministrato una volta ogni due giorni (The same dosage as described above, but administered once every two days.). Unless the dosage is explicitly mentioned, we do not annotate these spans, as the information is context-dependent. The treatment of specific diseases might require different dosages for the same drug. When they are reported in the leaflet, following a minimum span principle, we annotate all the dosages without any specification about the disease. Due to the aforementioned annotation choice, the annotation results will be a set of dosage information, as in the following example (annotated spans reported in bold face).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Example:</head><p>Aspergillosi: - When the same dosage can be applied in more than one cases, span duplicates may be present (e.g., 2 capsule una volta al giorno). In the final GS, these are removed so that only one span for each type is kept. Some drugs must be administered according to a schedule that spans different time periods, with or without dosage variations. In such cases, we annotate only the initial recommended dosage.</p><p>In some cases, the posology section does not provide specific dosage information and instead includes a general recommendation to consult a doctor. In these instances, we consider the information to be missing and do not annotate the general statement.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Drug interaction</head><p>As for drug interactions" we annotate the name of molecules and drugs when they are available. In some cases, the information about drug interaction is reported as a general reference to the use of some drugs (e.g., medicinali per abbassare la pressionemedicines to lower blood pressure). In such instances, as we cannot identify the specific molecule or drug, we annotate the general reference. Information about drug interactions may also appear as a reference to certain types of relationships with other molecules, as in derivati della fenotiazina (phenothiazine derivatives). For our annotations, we omit additional information and select the minimal span, in the aforementioned example, fenotiazina (phenothiazine). Similarly, when the information pertains to the drug class instead of reporting the molecule, e.g., lassativi (laxatives), we annotate the minimal span, even though in some cases the drug use is specified, e.g., medicinali usati per trattare la stipsi (medicines used to treat constipation).</p><p>We apply a hierarchical priority to identify and annotate the minimal span that conveys the information about drug interactions, as follows:</p><p>1. Molecule 2. Drug class 3. Drug use</p><p>The aforementioned hierarchy helps us identify the span to be annotated. When included, drug names are always annotated.</p><p>When the interaction information is reported with the specific pharmaceutical form (e.g., eritromicina iniettabile), only the minimal possible span is annotated, i.e., eritromicina.</p><p>In some cases, examples of interacting molecules or drug names are provided alongside the drug class or use (e.g., medicinali usati per il trattamento dell'HIV AIDS, per esempio ketoconazolo e itraconazolo -medicines used for the treatment of HIV/AIDS, for example, ketoconazole and itraconazole). In these instances, we annotate both, as the list of drugs and molecules may not be exhaustive.</p><p>If the list is exhaustive, we do not annotate the general reference to the drug use; we only annotate the drug molecules or names.</p><p>Interactions with some other molecules can be conditioned by the taken amount, e.g. cimetidina, preso in dosi giornaliere superiori a 800mg (cimetidine, taken in daily doses greater than 800 mg). Also in these cases the molecule name is the only span annotated. Some interacting drugs are reported as the general drug class, together with a plain language explanation and a subclass specification, as in the following example diuretici (compresse per urinare in particolare quelli chiamati risparmiatori di potassio) (diuretics (tablets for urination, particularly those called potassium-sparing))</p><p>As the molecule is not noted, we do annotate both the general class and sublcass (both in bold face in the previous excerpt). Additionally, also food and beverage can interact with drugs, e.g., pompelmo, alcol (grapefruit, alcohol). We opt not to include these substances within the drug interaction class, as we want to focus only on the pharmaceutical drug interaction. Drug interaction information are considered missing when there is only a general sentence to the fact that the use of any further drug should be reported.</p><p>Usage With respect to usage, we consider the minimal possible span, which indicates the disease treated by the specific drug. Thus, for instance, in the sentence {drug_name} è usato nel trattamento della gotta ({drug_name} is used in the treatment of gout), we annotate only gotta (gout).</p><p>In other cases, some examples of usage may be reported as in traumi (ad esempio causati dallo sport) (injuries (for example, those caused by sports)). As those cases are not representative enough of usages, we do not include them in the annotation, so in the previous excerpt we annotate just traumi (injuires). Within the usage section, sometimes the use of plain text is reported together with reference to the specific disease, e.g., meningite cirptococcica -un'infezione micotica del cervello (...). We always annotate the specific term for the disease and discard the plain text description. When the generic disease class is presented, e.g., infezioni cutanee (skin infections), followed by a non exhaustive list of examples, we annotate just the generic use.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Side effects</head><p>This class indicates all the possible side effects caused by the drug consumption. In PILs, this type of information is generally grouped on the basis of the number of people affected by the side effects to identify different diffusion levels, e.g., very common side effects, very rare side effects. We do not differentiate among the diffusion levels and consider all the side effects belonging to the same class side_effect. In some cases, side effects affecting other subjects than the person consuming the drug are reported. For instance, some drugs can affect the fetus as in the following excerpt.</p><p>Example: (...) Se assume Ricap durante le ultime fasi della gravidanza, il suo bambino potrebbe manifestare i seguenti sintomi: problemi a respirare, colorito bluastro o violaceo della pelle, convulsioni (...).</p><p>[(...) If you take Ricap during the later stages of pregnancy, your baby may experience the following symptoms: breathing problems, bluish or purplish skin discoloration, seizures (...)]</p><p>We do not annotate these secondary side effects and the ones derived from drug overdose. When the side effect type is reported together with its symptoms we do include those within the class of side effects. For instance, in some cases a list of symptoms difficoltà respiratoria, riduzione della pressione sanguigna is combined with the general side effect reazioni allergiche. Each of them is annotated separately and included into the list of side effects. Similarly, we annotate both the plain language side effect and the term, as in problemi del flusso della bile (colestasi) (bile flow problems (cholestasis)).</p><p>When the side effects are reported as worsening of an already existing disease, e.g., aumentata perdita di capelli, we annotate the minimum possible span, i.e., perdita di capelli.</p><p>For drugs containing more than one molecule, side effects are reported along with the side effects for each individual molecule. We annotate all of them. Side effects can be reported with reference to some patient/disease type, e.g., Se è HIV positivo può mostrare effetti indesiderati (If you are HIV positive, you may experience side effects). In such cases, symptoms are annotated without any further specification. If duplicates are presented, those are not annotated or removed in the post-processing phase, so that just one entry for symptom type is recorded in the GS. Sometimes, side effects are grouped by indicating the general area (e.g., organ or functionality) affected, e.g., nervous system disorders. The information might be followed by a list of specific side effects. When this is the case, we discard the general information in favor of the most specific one.</p><p>It is worth stressing that other information may be presented in PILs, for instance Precautions for use. As we are not interested in this type of information, we do not annotate such sections.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Inter-Annotator Agreement</head><p>The annotation has been performed by three people with computational linguistic backgrounds and different levels of expertise. An initial inter-annotator agreement has been evaluated after the first draft of guidelines has been created. Borderline cases and issues have been collected by each of the annotators and subsequently discussed and solved. The guidelines have been updated accordingly and a second round of annotation has been performed in order to compute the final inter-annotator agreement.</p><p>The annotation round for evaluating the final interannotator agreement has been performed on a subset of 60 leaflets. The results, calculated before the post-processing phase, show a complete agreement on the molecule class among all the annotators, while for the remaining classes the agreement spans from .61 for posology and .80 for side effects (Table <ref type="table">3</ref>). To assess the inter-annotator agreement (IAA) for the creation of the gold standard, we employed two different metrics: pairwise F1 score <ref type="bibr" target="#b15">[15,</ref><ref type="bibr" target="#b16">16]</ref> and token-level agreement percentage <ref type="bibr" target="#b17">[17]</ref>. The pairwise F1 score was used to calculate the IAA for the "Molecule" and "Usage" labels, as the information contained in the text for these entities refers to unique and well-defined concepts. This metric provides a balanced measure of the precision and recall of the annotations, allowing us to quantify the level of agreement between annotators on the identification of these specific entities.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Class</head><p>On the other hand, for the "Dosage", "Drug Interaction", and "Side Effect" classes, we opted to use the token-level agreement percentage as the IAA metric. This choice was motivated by the fact that these classes involve variable text spans, which can be more challenging to align between annotators. Before calculating the token-level agreement percentage, we performed preprocessing steps on the annotated portions, removing punctuation marks (such as -and • that indicate a list) and Italian stopwords from the Spacy Italian language model 6 . The token-level agreement percentage provides a more granular assessment of the consistency in the identification of the relevant text segments, which is crucial for the accurate extraction of these types of entities from the source documents.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>GS Post-processing</head><p>To ensure high consistency among annotations and to remove additional information that does not meet the specified annotation criteria, we perform a post-processing step. During this phase, we review the GS, using recurring patterns and regular expressions to clean the data and correct errors. We also carry out manual cleaning to produce the final GS. For instance, when applicable, we remove the drug name mentioned in the posology specification (e.g., one tablet of drug_name once a day) so that only the general information related to the molecule is retained. The resulting evaluation dataset contains XXX annotated molecules, XXX drug interactions, XXX usage information, and XXX side-effects (Table <ref type="table" target="#tab_7">4</ref>).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Class</head><p>Tot </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.2.">Results</head><p>The expected results should be presented as a list of entities for each of the classes of information about each drug. To obtain the result lists, we consider the annotated terms and their simplifications as unique entities e.g., the span livelli aumentati di calcio nel sangue (ipercalcemia) (elevated levels of calcium in the blood (hypercalcemia)) is listed as two separate entities that are livelli aumentati Since this is an information extraction task in a zero-shot setting based on PILs, it is expected that LLMs will be able to extract the exact terminology used in the different sections of the PILs and provide a list of terms. The performance will be evaluated based on the metrics described in 4. Potential limitations in accurately assessing the performance of LLMs may arise from: 1) the variability in the models' choice of terms to extract, and 2) the provision of terms and their simplifications as two entities. In these cases, forcing the LLMs to provide a more structured and less ambiguous output might help, as currently the gold standard does not account for a set of synonyms to handle variability in the output, or employing additional metrics to address the second case.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.">Limitations</head><p>One important limitation of the DIMMI dataset is the disclaimer provided by the Italian Medicines Agency (AIFA) regarding the content available on their website in section A. Disclaimer <ref type="foot" target="#foot_2">7</ref> . AIFA states that all the information and services offered on their website are provided "as is" and "with all faults". The Italian Medicines Agency, therefore, does not provide any kind of warranty, either explicit or implied, regarding the content, including, without limitation, the legality, ownership, suitability, or fitness for particular purposes or uses.</p><p>This disclaimer from the data source raises concerns about the reliability and quality of the patient information leaflets (PILs) that were used to construct the DIMMI corpus. While the dataset has been carefully curated and annotated, the underlying data may contain errors, inaccuracies, or other issues that are not explicitly acknowledged by the original provider. Researchers and developers using the DIMMI dataset should be aware of this limitation and exercise caution when relying on the information contained within the corpus, particularly for critical applications or decision-making processes.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6.">Ethical issues</head><p>Ethical considerations are crucial when working with a dataset that contains sensitive information from PILs. The DIMMI corpus, which is derived from the AIFA (Italian Medicines Agency) Database, must be handled with the utmost care and respect for individual privacy, data protection, and the diversity of the target population.</p><p>Additionally, the use of the DIMMI corpus for the development and evaluation of natural language processing models must be guided by ethical principles that consider the diversity of the target population. The models trained on this data should be designed and deployed in a way that respects individual privacy, avoids potential misuse or discrimination, and ultimately benefits the public good, regardless of ethnicity or age. Careful consideration should be given to the potential societal impact of the applications built upon the DIMMI dataset, ensuring that they are inclusive and equitable.</p><p>By upholding the ethical standards in the handling and utilization of the DIMMI corpus, the research community can ensure that the valuable pharmacological information contained in the PILs is leveraged responsibly and in a manner that prioritizes the well-being of patients and the general public, while respecting the diversity of the target population.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="7.">Data license and copyright issues</head><p>The DIMMI corpus has been created using the patient information leaflets (PILs) from the AIFA (Italian Medicines Agency) Database. As reported in the Web site <ref type="foot" target="#foot_3">8</ref> , the distribution license used by AIFA for these data is the Creative Commons Attribution (CC-BY) license, version 4.0. This license allows third parties to distribute, modify, adapt, and use the data, even for commercial purposes, with the sole requirement of providing attribution to the original source.</p><p>By making the DIMMI corpus available under the CC-BY 4.0 license, the dataset can be freely accessed, utilized, and built upon by the scientific community, contributing to the advancement of research and applications in the field of biomedical text mining and pharmacological information extraction.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_0"><head>the less recent leaflet has been removed.</head><label></label><figDesc></figDesc><table><row><cell>• Correcting the separation of each leaflets by iden-</cell></row><row><cell>tifying regular patterns which indicate the begin-</cell></row><row><cell>ning/end of a unique leaflet.</cell></row><row><cell>• Removing additional information about the is-</cell></row><row><cell>sue date, the pharmaceutical company, and the</cell></row><row><cell>marketing authorization.</cell></row><row><cell>Additionally, we notice the presence of several cases of</cell></row><row><cell>duplicate entries, due to different reasons, as described</cell></row><row><cell>below:</cell></row><row><cell>1. Same drug name, same dosage form, same ingre-</cell></row><row><cell>dient amount, different issue dates → These</cell></row><row><cell>cases indicate that the leaflet has been updated</cell></row><row><cell>and all the versions are recorded into the AIFA</cell></row><row><cell>repository. In such cases, on the basis of their ID,</cell></row><row><cell>2. Same drug name, same dosage form, different in-</cell></row><row><cell>gredient amount → These cases may present, or</cell></row><row><cell>not, the same information leaflets.</cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_1"><head>We do not re- move the duplicate entries, even</head><label></label><figDesc></figDesc><table><row><cell>though they</cell></row><row><cell>present the same information about the classes</cell></row><row><cell>we are interested in.</cell></row><row><cell>3. Same drug name,</cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_2"><head>different dosage form, same ingredient amount → These duplicates are not removed as dosage information can be differen- tiated on the basis of the drug form. 4. Same drug name, same dosage form, same ingre- dient amount, different pharmaceutical com- pany -These duplicates are removed and just one entry is kept. We usually prefer keeping the one reporting in the name 'DOC generici'. If</head><label></label><figDesc>this is not possible, we keep the first occurrence.</figDesc><table /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_3"><head>Table 2</head><label>2</label><figDesc></figDesc><table><row><cell>), with the</cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_5"><head>2 capsule una volta al giorno per</head><label></label><figDesc></figDesc><table><row><cell>un</cell></row><row><cell>periodo di 2-5 mesi; (...) Candidosi: 1-2 capsule 1 volta</cell></row><row><cell>al giorno per un periodo da 3 settimane a 7 mesi (...)</cell></row><row><cell>Criptococcosi non meningea: 2 capsule una volta al</cell></row><row><cell>giorno per un periodo dai 2 mesi ad 1 anno (...)</cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_7"><head>Table 4</head><label>4</label><figDesc>Annotated entities for each class</figDesc><table><row><cell></cell><cell cols="2">. Entities Unique Entities</cell></row><row><cell>Molecule</cell><cell>657</cell><cell>657</cell></row><row><cell>Usage</cell><cell>2159</cell><cell>2113</cell></row><row><cell>Posology</cell><cell>831</cell><cell>827</cell></row><row><cell cols="2">Drug interaction 8617</cell><cell>8458</cell></row><row><cell>Side effect</cell><cell>36748</cell><cell>30313</cell></row><row><cell>Total</cell><cell>49012</cell><cell>42368</cell></row></table></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="4" xml:id="foot_0">https://huggingface.co/datasets/RafaMann/DIMMI</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="5" xml:id="foot_1">It is worth stressing that in the prompt examples {drug_name} is not a masked word, it represents a placeholder to indicate one of the entries from the column drug_name in DIMMI dataset.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="7" xml:id="foot_2">https://www.aifa.gov.it/en/copyright</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="8" xml:id="foot_3">https://www.aifa.gov.it/en/copyright</note>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Acknowledgments</head><p>Luca Giordano has been supported by Borsa di Studio GARR "Orio Carlini" 2023/24 -Consortium GARR, the National Research and Education Network.</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">Educating patients about their medications: the potential and limitations of written drug information</title>
		<author>
			<persName><forename type="first">W</forename><forename type="middle">H</forename><surname>Shrank</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Avorn</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Health affairs</title>
		<imprint>
			<biblScope unit="volume">26</biblScope>
			<biblScope unit="page" from="731" to="740" />
			<date type="published" when="2007">2007</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Quality improvement of health information included in drug information leaflets. patient and health professional expectations</title>
		<author>
			<persName><forename type="first">P</forename><surname>Rodríguez</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Azarola</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Lorda</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Cantalejo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Danet</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Atencion primaria</title>
		<imprint>
			<biblScope unit="volume">42</biblScope>
			<biblScope unit="page" from="22" to="27" />
			<date type="published" when="2009">2009</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Readability analysis of the package leaflets for biological medicines available on the internet between 2007 and 2013: an analytical longitudinal study</title>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">Á</forename><surname>Piñero-López</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Modamio</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><forename type="middle">F</forename><surname>Lastra</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><forename type="middle">L</forename><surname>Mariño</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Journal of medical Internet research</title>
		<imprint>
			<biblScope unit="volume">18</biblScope>
			<biblScope unit="page">e100</biblScope>
			<date type="published" when="2016">2016</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">Simplifying drug package leaflets written in spanish by using word embedding</title>
		<author>
			<persName><forename type="first">I</forename><surname>Segura-Bedmar</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Martínez</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Journal of biomedical semantics</title>
		<imprint>
			<biblScope unit="volume">8</biblScope>
			<biblScope unit="page" from="1" to="9" />
			<date type="published" when="2017">2017</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<monogr>
		<author>
			<persName><forename type="first">M</forename><surname>Yuan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Bao</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Yuan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Shen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Z</forename><surname>Chen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Xie</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Zhao</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Chen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Zhang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Shen</surname></persName>
		</author>
		<idno type="arXiv">arXiv:2311.01918</idno>
		<title level="m">Large language models illuminate a progressive pathway to artificial healthcare assistant: A review</title>
				<imprint>
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
	<note type="report_type">arXiv preprint</note>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Overview of the medical question answering task at trec 2017 liveqa</title>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">B</forename><surname>Abacha</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Agichtein</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Pinter</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Demner-Fushman</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">TREC</title>
		<imprint>
			<biblScope unit="page" from="1" to="12" />
			<date type="published" when="2017">2017</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Bridging the gap between consumers&apos; medication questions and trusted answers</title>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">B</forename><surname>Abacha</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Mrabet</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Sharp</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><forename type="middle">R</forename><surname>Goodwin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">E</forename><surname>Shooshan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Demner-Fushman</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">MEDINFO 2019: Health and Wellbeing e-Networks for All</title>
				<imprint>
			<publisher>IOS Press</publisher>
			<date type="published" when="2019">2019</date>
			<biblScope unit="page" from="25" to="29" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Medredqa for medical consumer question answering: Dataset, tasks, and neural baselines</title>
		<author>
			<persName><forename type="first">V</forename><surname>Nguyen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Karimi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Rybinski</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Z</forename><surname>Xing</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 13th International Joint Conference on Natural Language Processing and the 3rd Conference of the Asia-Pacific Chapter of the Association for Computational Linguistics</title>
		<title level="s">Long Papers</title>
		<meeting>the 13th International Joint Conference on Natural Language Processing and the 3rd Conference of the Asia-Pacific Chapter of the Association for Computational Linguistics</meeting>
		<imprint>
			<date type="published" when="2023">2023</date>
			<biblScope unit="volume">1</biblScope>
			<biblScope unit="page" from="629" to="648" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">Advancing the state of the art in clinical natural language processing through shared tasks</title>
		<author>
			<persName><forename type="first">M</forename><surname>Filannino</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Ö</forename><surname>Uzuner</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Yearbook of medical informatics</title>
		<imprint>
			<biblScope unit="volume">27</biblScope>
			<biblScope unit="page" from="184" to="192" />
			<date type="published" when="2018">2018</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">Chatgpt: Is this version good for healthcare and research?</title>
		<author>
			<persName><forename type="first">R</forename><surname>Vaishya</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Misra</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Vaish</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Diabetes &amp; Metabolic Syndrome: Clinical Research &amp; Reviews</title>
		<imprint>
			<biblScope unit="volume">17</biblScope>
			<biblScope unit="page">102744</biblScope>
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">Benefits, limits, and risks of gpt-4 as an ai chatbot for medicine</title>
		<author>
			<persName><forename type="first">P</forename><surname>Lee</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Bubeck</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Petro</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">New England Journal of Medicine</title>
		<imprint>
			<biblScope unit="volume">388</biblScope>
			<biblScope unit="page" from="1233" to="1239" />
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title level="a" type="main">Large language model ai chatbots require approval as medical devices</title>
		<author>
			<persName><forename type="first">S</forename><surname>Gilbert</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Harvey</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Melvin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Vollebregt</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Wicks</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Nature Medicine</title>
		<imprint>
			<biblScope unit="volume">29</biblScope>
			<biblScope unit="page" from="2396" to="2398" />
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">CALAMITA: Challenge the Abilities of LAnguage Models in ITAlian</title>
		<author>
			<persName><forename type="first">G</forename><surname>Attanasio</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Basile</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Borazio</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Croce</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Francis</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Gili</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Musacchio</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Nissim</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Patti</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Rinaldi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Scalena</surname></persName>
		</author>
		<ptr target="CEUR-WS.org" />
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 10th Italian Conference on Computational Linguistics (CLiC-it 2024)</title>
		<title level="s">CEUR Workshop Proceedings</title>
		<meeting>the 10th Italian Conference on Computational Linguistics (CLiC-it 2024)<address><addrLine>Pisa, Italy</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2024-12-06">December 4 -December 6, 2024. 2024</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<analytic>
		<title level="a" type="main">Large language models as drug information providers for patients</title>
		<author>
			<persName><forename type="first">L</forename><surname>Giordano</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">P</forename><surname>Di Buono</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the First Workshop on Patient-Oriented Language Processing</title>
				<meeting>the First Workshop on Patient-Oriented Language Processing</meeting>
		<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<monogr>
		<title level="m">@ LREC-COLING</title>
				<imprint>
			<date type="published" when="2024">2024. 2024</date>
			<biblScope unit="page" from="54" to="63" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<analytic>
		<title level="a" type="main">Agreement, the fmeasure, and reliability in information retrieval</title>
		<author>
			<persName><forename type="first">G</forename><surname>Hripcsak</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">S</forename><surname>Rothschild</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Journal of the American medical informatics association</title>
		<imprint>
			<biblScope unit="volume">12</biblScope>
			<biblScope unit="page" from="296" to="298" />
			<date type="published" when="2005">2005</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b16">
	<analytic>
		<title level="a" type="main">Building gold standard corpora for medical natural language processing tasks</title>
		<author>
			<persName><forename type="first">L</forename><surname>Deleger</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Q</forename><surname>Li</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Lingren</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Kaiser</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Molnar</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Stoutenborough</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Kouril</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Marsolo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>Solti</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">AMIA Annual Symposium Proceedings</title>
				<imprint>
			<publisher>American Medical Informatics Association</publisher>
			<date type="published" when="2012">2012. 2012</date>
			<biblScope unit="page">144</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b17">
	<analytic>
		<title level="a" type="main">Proposal for an extension of traditional named entities: From guidelines to evaluation, an overview</title>
		<author>
			<persName><forename type="first">C</forename><surname>Grouin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Rosset</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Zweigenbaum</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Fort</surname></persName>
		</author>
		<author>
			<persName><forename type="first">O</forename><surname>Galibert</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Quintard</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 5th linguistic annotation workshop</title>
				<meeting>the 5th linguistic annotation workshop</meeting>
		<imprint>
			<date type="published" when="2011">2011</date>
			<biblScope unit="page" from="92" to="100" />
		</imprint>
	</monogr>
</biblStruct>

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