<?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"></title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">0153EF60BDF8B3A16EA8621AEBF80205</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-19T15:53+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>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Motivation:</head><p>The previously developed Search Ontology (SO) allows domain experts to formally specify domain concepts, search terms associated to a domain, and rules describing domain concepts. So far, Lucene search queries can be generated from information contained in the SO and can be used for querying literature data bases or PubMed. However, this is still insufficient, since these queries are not well suited for querying XML documents because they are not following their structure. However, in the medical domain, many information items are coded in XML. Thus, querying structured XML documents is crucial for retrieving similar cases or for identifying potential study participants. For example, information items of patients with a similar tumor classification documented in a certain section of the respective pathology report need to be retrieved. This requires a precise definition of queries. In this paper, we introduce a concept for the generation of such queries using a Search Ontology XML extension to enable semantic searches on structured data. Results: For a gain of precision, the paragraph of a document need to be specified, in which a specific information item expressed in a query is expected to appear. The Search Ontology XML Extension (SOX) connects search terms to certain sections in XML documents. The extension consists of a class which represents the XML structure and a relation between search terms and this XML structure. This enables an automatic generation of XPath expressions, which makes an efficient and precise search of structured pathology reports in XML databases possible. The combination of standardized Electronic Health Records with an ontology based query method promises a gain of precision, a high degree of interoperability and long term durability of both, XML documents and queries on XML documents.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1">INTRODUCTION</head><p>Since untagged information in health information systems (HISs) is common, information access supported by automatic methods is difficult. It is still an open question how to accelerate the access to information captured in these systems or in Electronic Health Records (EHRs). On the one hand, content must be structured by automatic recognition processes. On the other hand, the structured data has to be queried in a structured way. This paper will focus on the query side, by introducing a new solution of semantic meaningful queries on structured XML documents, defined by the Search Ontology (SO) XML Extension. The SO <ref type="bibr" target="#b16">(Uciteli et al., 2014)</ref> has been developed to support full text search on unstructured documents. It allows an user to formally specify domain concepts, search terms associated to the domain, and rules describing domain concepts. In this way, it simplifies the definition of search rules. The SO can be used for information retrieval in any domain by extending it by the corresponding domain ontology.</p><p>In this work, we introduce an extension of the SO that enables the definition of queries on structured XML documents. Assuming that we have structured and standardized XML documents, then we can query certain parts of the XML document by XPath expressions. The development of such XPaths is time consuming for domain experts, but also for computer scientists. We suggest to use ontologies to support domain experts in modelling XML queries.</p><p>Out of the ontology based query models, XPaths can be generated automatically, which in turn can be applied to document corpora on XML database systems for searching similar cases or for the identification of potential study participants. Even though the approach is inherent independent from the underlying XML structure, we will demonstrate the approach on an example of querying standardized Electronic Health Records (EHRs) in the pathology domain.</p><p>To address the problem of creating structured queries for retrieving documents, previous work considered the unification of different XML structures on the conceptual level, on the one hand by the introduction of new query languages, e.g. CXPath <ref type="bibr" target="#b1">(Camillo et al., 2003)</ref> or XSEarch <ref type="bibr">(Cohen et al., 2004)</ref>, or on the other hand by introducing conceptual ontologies <ref type="bibr" target="#b3">(Cruz et al., 2004;</ref><ref type="bibr" target="#b6">Erdmann et al., 1999)</ref>. In contrast to this unification approaches, the SOX approach, introduced in this paper, is strongly bound to the used XML structure. Indeed, this strong binding on a structure is only meaningful when standardized XML based EHRs are used.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2">METHODS</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.1">Overview</head><p>Figure <ref type="figure" target="#fig_0">1</ref> gives an overview on the basic approach presented in this paper. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Querying standardized EHRs by a Search Ontology XML extension (SOX)</head><p>Stefan Kropf 1* , Alexandr Uciteli 1* , Peter Krücken 2 , Kerstin Denecke 3 , Heinrich Herre 1 A domain expert is in the middle of the query formulation and retrieval process. He uses Protégé, the ontology editor of the Stanford University <ref type="bibr" target="#b14">(Musen 2015)</ref>, for modeling a query using the Search Ontology (section 2.2) and SOX (section 3.1) as shown on the left side in figure <ref type="figure" target="#fig_0">1</ref>. By an adaption of the OntoQueryBuilder Plugin it will be possible to generate XPaths expressions. Additionally, the agent interacts with the XML database as shown on the right hand side of figure 1, After recognizing section boundaries, unstructured documents are stored on an XML database (section 2.3). Using the XPaths (sections 2.4, 3.2), the domain expert can retrieve relevant XML documents.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.2">Search Ontology</head><p>The formulation of structured queries can be very time consuming, especially in safety-relevant domains like post market surveillance. A concept can be described in different ways, on the one hand by synonyms, on the other hand by complex phrases, which in turn consist of multiple terms. Because of that we distinguish Sim-ple_Terms from Composite_Terms. Composite_Terms. are made up of Simple_Terms, related by the Object Property has_part and are constrained by the additional Data Property max_distance, which defines the word distance between two Simple_Terms, where max_distance=0 represents that one word immediately follows after another word. Writing variations, synonyms of abbreviations of the Sim-ple_Terms can be handled by the assignment of multiple labels to the concrete individual of a Simple_Term.</p><p>For instance, the complication of a medical device (e.g. occluder) is a reusable Search_Concept, which can be described_by several Search_Terms.</p><p>To such descriptions belongs among other things adjective phrases like incomplete closure. Instead of adjective, other terms with the same semantic meaning could be used; the noun could be replaced by any term which represents the meaning of closure. Out of this definition, a query can be generated, which is in this example the disjunction of all combinations of adjectives and nouns (cf. second disjunction in Listing 1).</p><p>Listing 1. Lucene Query for an occlusion device complication; the expression was generated by the plugin OntoQueryBuilder.</p><p>("occlusion device" OR occluder) AND (("insufficient sealing"~2 OR "insufficient closure"~2 OR "incomplete sealing"~2 OR "incomplete closure"~2 OR "inadequate sealing"~2 OR "inadequate closure"~2))</p><p>The latter example indicates that the formulation of a query can become a complex task; the cross-product of only 10 adjectives with 10 nouns results in 100 adjective substantive combinations. Hence, we have to manage Concepts and Terms by an appropriate ontology, especially if we want to reuse concepts or if we want to generate cross-products of certain term combinations.</p><p>The SO is used in practice in the OntoVigilance project (On-toVigilance Homepage 2016), where semantic searches have to be managed within post market surveillance queries of medical devices. In brief, domain experts can manage their domain search ontology (DSO). By the usage of the developed plugin OntoQuery-Builder a Lucene query can be generated.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.3">Standardized XML-based EHRs</head><p>In this paper, we will concentrate on the special domain of pathology, where a lot of semi-structured information occurs in terms of pathology reports. We consider this information semi-structured, because the pathologists structure their information by headers and keywords, but these structure is usually not technically implemented. In fact, pathology reports are based on certain section patterns and section-introducing keywords, like material, macroscopy or microscopy. We verified manually that documents originated from the Institute of Pathology of Leipzig, the sections introducing keywords like Material, Makroskopie or Mikroskopie were constantly used for section tagging. Therefore, the reports can be structured in sections by section boundary detection, which is not the main focus of this article. Consequently, legacy data can be transformed into a structured format. Suitable standards for long term persistence are EN 14822 a.k.a. HL7 RIM <ref type="bibr">(EN 14822, 2006)</ref> and EN 13606 a.k.a. openEHR <ref type="bibr">(EN 13606, 2012)</ref>. Both standards are representable in XML, EN 14822 by the usage of CDA <ref type="bibr" target="#b4">(Dolin et al., 2001)</ref> and EN 13606 by the usage of openEHR modeling tools <ref type="bibr" target="#b12">(Kropf et al., 2015)</ref>, which results in a standardized XML schema based on the openEHR XML schemas <ref type="bibr" target="#b0">(Beale 2015)</ref>.</p><p>In this work, we will use pathology reports, mapped to standardized EHRs by the usage of the openEHR archetypes openEHR-EHR-OBSERVATION.lab_test-histopathology.v1 for structuring pathology data and openEHR-EHR-CLUSTER. Listing 2. Simplified XML based pathology EHR snippet, containing a macroscopy and a TNM classification part. The snippet was cut to the necessary elements, which we want to address in the query in this paper, marked by a grey background: the macroscopy section (part of openEHR-EHR-OBSERVATION.lab_test-histopathology.v1) and the primary tumor classification (part of openEHR-EHR-CLUSTER.tnm_staging_7th.v1). The doubling of the value tag is a result of the EN 13606 reference model, in practice the two value tags have different namespace declarations. The TNM structured classification string in the XML snippet is "pT2". The sentence which introduces the overall macroscopy description contains a noun Hautexzidat (HE) (en: excised skin material), marked by a bold font. Due to linguistic variability, this noun can vary, i.e. synonyms or abbreviations such as H.E. are used in practice. In front of the noun there is an underlined adjective keilförmig (en: cuneiform) for specifying the shape. Again, semantic and linguistic variants of the term exist (e.g. rundlich (en: roundish)). Furthermore, the order of the adjectives in the phrase could change: the order "Ein ff. rundliches fadenmarkiertes H.E." was found and is also valid.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.4">XPath Queries</head><p>When EHRs are stored in structured XML, another query language is more suitable than classical free text retrieval methods such as Lucene <ref type="bibr" target="#b13">(McCandless et al., 2010)</ref> or SOLR <ref type="bibr">(Trey et al., 2014)</ref>. XPath expressions are following the structure of the EHRs and are a W3C standardized method for addressing parts in XML documents (XML Path Language (XPath), 2015). An example XPath Query is shown in Listing 3 for querying T2 and phrases of HE from EHR documents similar to those in Listing 2.</p><p>Listing 3. Required XPath expressions for a search of EHRs which contains T2 as primary tumor classification in the first part and defined phrases of HE in the second part. The first part of Listing 3 matches documents where the tumor class is T2. In the second part, each disjunction represents one adjective noun phrase. It consists of an adjective and a regular expression that reflects possible declension variations followed by the noun phrase representing Hautexzidat (HE). The expression ([\w]*\s){0,2} implies that between the adjective and the noun a maximum of two words are allowed to match the pattern.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3">RESULTS</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.1">Extension of the Search Ontology</head><p>The output of the SO are Lucene queries, but they do not follow the structure of XML documents, thus, they are not applicable to XML documents. However, the SO delivers already a reusable framework which only has to be extended for enabling structured queries in XML. By extending the SO with the SOX, queries are automatically producible out of the ontology, which can be executed on XML documents. For this purpose, two elements were added to the SO, on the top level of the ontology the class XML_Structure and the Object Property in.  Namespaces and tag names of the XML document are defined by XML_Structure class labels. Figure <ref type="figure">5</ref> illustrates the SO for the described use case, where the documents follow the structure of Listing 2 and XPaths of Listing 3 have to be generated as output.</p><p>The modelling of the SO (illustrated in fig. <ref type="figure">5</ref>) has to be done manually by the domain expert. For querying HEs with different kinds of shapes the Search_Concept HE_Shapes was defined, de-scribed_by HE_Phrase, which consists of two Sim-ple_Terms (HE_Form and HE_Term). In the example of this paper, individuals of HE_Form can be adjectives like rundlich or keilförmig; HE_Term has only one individual, the different writing variations (Hautexzidat, H.E.) can be handled by multiple label assignments. Figure <ref type="figure">5</ref> illustrates also the usage of the in relation for the specification of the position inside the XML document, for instance is the term T2_Term expected in the associated section Primary_Tumor. In a similar way, HE_Shapes are bound to the XML_Structure. The following figure <ref type="figure" target="#fig_6">4</ref> shows the class definition of HE_Shapes in Protégé. In summary, out of the DSO XML extension, it is possible to generate automatically the required XPath expressions.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.2">Automatic XPath generation</head><p>For each Search_Concept one XPath can be generated automatically. This can be done by a scheduled adaption of the Lucene export plugin, the OntoQueryBuilder, which is already developed as part of the OntoVigilance (OntoVigilance Homepage 2016) project. The first part of Listing 3 can be generated out of the Search_Concept T2, in which description the term T2_Term is bound to the appropriate search location by the in relation. The second part of Listing 3 is producible out of the Search_Con-cept HE_Shapes, which is described_by the Compo-site_Term HE_Phrase and is expected in the Over-all_macroscopic_description.</p><p>This Compo-site_Term yields to a disjunction expression of all combinations of the labels of the HE_Form individuals with the labels of HE_Term individuals, which is in essence a kind of a cross product.</p><p>The generated XPaths can be used for structured queries and for the integration in other XML techniques (XSLT or XQuery).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4">DISCUSSION</head><p>With an example on querying structured EHRs, we introduced an extension of the Search Ontology to support querying structured XML documents. The SOX approach can simplify the managing of a big pool of XPath expressions in one overarching DSO in practice.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.1">Standardized queries on standardized EHRs</head><p>Indeed, SPARQL queries on OWL based patient data would be more powerful than XPath expressions on XML, but a comprehensive and long term persistence storage of pathology data within semantic web technologies is only partially solved and still an open research question. Therefore, until there is no standardized domain ontology available, queries on standardized XML will be more stable and long term durable. To put it in brief, the first requirement is a layer of standardized EHRs and tools which work at this layer, like the introduced SOX. After that step a more powerful ontology layer is demandable.</p><p>We used the EN 13606 standardized XML in this work. However, another option would be EN 14822 or even any other proprietary XML format. When the community comes to an agreement, which EHR standard will be used in German Health Information Systems in future, not only the EHR would be interoperable, the usage of a standardized query language implies that queries could be interoperable too. Presupposed standardized EHRs would be used, it is imaginable that queries on such EHRs can be interoperable and therefore used in different hospitals. When openEHR is used, the depending SOX or the resulting queries could be stored in a repository and they could be linked to the belonging archetypes. Consequently, the Fig. <ref type="figure">5</ref>. Search Ontology for querying the concept primary tumor T2 and the concept HE_Shapes (manually defined) query can be reused like the archetype itself, this would save development time and lead to quality intensification.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.2">Recognition methods vs. querying methods</head><p>Research in Natural Language Processing (NLP) delivers methods <ref type="bibr" target="#b10">(Hahn et al., 2002;</ref><ref type="bibr" target="#b7">Friedman et al., 1999)</ref> for the recognition of clinical information in medical documents. Nevertheless, it is unclear when a reliable NLP system will automatically recognize and annotate free text pathology reports or any other free textual clinical documents in daily practice. It is important to think about practical solutions on the recognition side, but also on the query side. The SOX delivers a practical solution on the query side by the connection of Search Terms to parts in XML documents.</p><p>Listing 3 already respects declension forms of adjectives which have a stable word stem. But for the development of a minimal SO, NLP methods like stemming are necessary too. Because of that, we have to think about the integration of such methods into ontological contemplations about querying structured information in the near future.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.3">Future ontological work</head><p>XML elements are more than symbolic structures, they have to be considered in detail, last but not least they should have be bound to a top level ontology like the General Formal Ontology (GFO) <ref type="bibr" target="#b11">(Herre 2010</ref>). In the SOX, the XML document structure was realized by is_a relations, because we wanted to model queries in tree structures in standard Protégé. Of course has_part relations would be semantically better. For this reason, we plan to develop a proper plugin for the modeling of has_part relations in tree structures in Protégé. In addition, an automatic conversion of XML documents into a SOX XML_Structure tree is demandable; this would accelerate the query development in Protégé. X2OWL can generate an OWL ontology from an XML data source <ref type="bibr" target="#b8">(Ghawi et al., 2009)</ref> and is a good starting point.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5">CONCLUSION</head><p>When EHRs are persisted in standardized XML, it is possible to query them in a structured way. The introduced Search Ontology XML extension connects search terms to certain parts in XML documents and enables an ontology based definition of semantic searches. Out of this, XPath expressions can be generated for querying XML database systems. Our solution supports the reuse oriented specification of complex and powerful XPath expressions without deep syntactic knowledge about XPath. The approach is open for additional extensions; parts of the ontology can be reused and adapted easily for other use cases.</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. (1) The domain expert models the queries by the usage of SOX in Protégé. (2) Using an extended version of the OntoQueryBuilder Plugin, Protége generates XPath expressions out of the ontology. (3) The expert applies the generated XPath expressions to an XML database, that (4) returns the relevant documents.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Fig. 2 .</head><label>2</label><figDesc>Fig. 2. Overview Search Ontology</figDesc><graphic coords="2,64.30,291.66,221.63,126.80" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head></head><label></label><figDesc>tnm_staging_7th.v1 for structuring the TNM classification (Sobin et al., 2011) data. Both latter archetypes are available at the Clinical Knowledge Manager (CKM) of openEHR [http://www.openehr.org/ckm/]. Consider the following snippet of an XML based pathology EHR (cf. Listing 2) where we demonstrate the challenges of querying the content. They are mainly due to the linguistic variability of natural language.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_3"><head></head><label></label><figDesc>(value,'keilförmig(\w)* ([\w]*\s){0,2}Hautexzidat')] or /Pathology/Macroscopic_findings/Overall_macroscopic_description/ value[matches(value,'rundlich(\w)* ([\w]*\s){0,2}H.E.)] or /Pathology/Macroscopic_findings/Overall_macroscopic_description/ value[matches(value,'keilförmig(\w)* ([\w]*\s){0,2}H.E.)] or /Pathology/Macroscopic_findings/Overall_macroscopic_description/ value[matches(value,'rundlich(\w)* ([\w]*\s){0,2} Hautexzidat'')]</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_4"><head>Fig. 3 .</head><label>3</label><figDesc>Fig. 3. The Search Ontology XML Extension introduces the top level class XML_Structure and the relation in (dashed arrow).</figDesc><graphic coords="3,315.00,537.85,247.69,102.30" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_5"><head>Figure 3</head><label>3</label><figDesc>Figure 3 shows that Seach_Concepts are described_by Search_Terms, which belong to certain parts in the XML_Structure; in more detail, Search_Terms are linked to XML parts by the in relation. The subclass structure of</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_6"><head>Fig. 4 .</head><label>4</label><figDesc>Fig. 4. Class definition of HE_Shapes</figDesc></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="1" xml:id="foot_0">Institute for Medical Informatics, Statistics and Epidemiology (IMISE), Leipzig University</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="2" xml:id="foot_1">Institute of Pathology, Leipzig University</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="3" xml:id="foot_2">Institute for Medical Informatics, Bern University of Applied Sciences * Contributed equally</note>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><head>ACKNOWLEDGEMENT</head><p>Thanks to Claire Chalopin, Wolf Müller, Katrin Schierle, Lars Voitel, Christian Wittekind for their support, to the reviewers of ODLS for their constructive feedback, especially Dagmar Waltemath, and the organizers, among which we mention Frank Loebe and Daniel Schober, for arranging ODLS. This work was conducted using the Protégé resource, which is supported by grant GM10331601 from the National Institute of General Medical Sciences of the United States National Institutes of Health.</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<monogr>
		<author>
			<persName><forename type="first">T</forename><surname>Beale</surname></persName>
		</author>
		<ptr target="2016-08-30" />
		<title level="m">openEHR reference-models XSDs release 1</title>
				<imprint>
			<date type="published" when="2015">2015</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Querying heterogeneous XML sources through a conceptual schema</title>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">D</forename><surname>Camillo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">H</forename><surname>Carlos</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Santos Mello</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">International Conference on Conceptual Modeling</title>
				<imprint>
			<date type="published" when="2003">2003</date>
			<biblScope unit="page" from="186" to="199" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">XSEarch: A semantic search engine for XML</title>
		<author>
			<persName><forename type="first">S</forename><surname>Cohen</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 29th international conference on Very large data bases</title>
				<meeting>the 29th international conference on Very large data bases</meeting>
		<imprint>
			<publisher>VLDB Endowment</publisher>
			<date type="published" when="2003">2003</date>
			<biblScope unit="volume">29</biblScope>
			<biblScope unit="page" from="45" to="56" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">An ontology-based framework for XML semantic integration</title>
		<author>
			<persName><forename type="first">I</forename><forename type="middle">R</forename><surname>Cruz</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Xiao</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Hsu</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Database Engineering and Applications Symposium. IDEAS&apos;04. Proceedings. International</title>
				<imprint>
			<publisher>IEEE</publisher>
			<date type="published" when="2004">2004</date>
			<biblScope unit="page" from="217" to="226" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">The HL7 Clinical Document Architecture</title>
		<author>
			<persName><forename type="first">R</forename><forename type="middle">H</forename><surname>Dolin</surname></persName>
		</author>
		<idno>EN 13606</idno>
	</analytic>
	<monogr>
		<title level="j">Journal of the American Medical Informatics Association</title>
		<imprint>
			<biblScope unit="volume">8</biblScope>
			<biblScope unit="issue">6</biblScope>
			<biblScope unit="page" from="552" to="569" />
			<date type="published" when="2001">2001. 2012</date>
		</imprint>
	</monogr>
	<note>Health informatics -Electronic health record communication [Norm</note>
</biblStruct>

<biblStruct xml:id="b5">
	<monogr>
		<idno>EN 14822</idno>
		<title level="m">Health informatics -General purpose information components</title>
				<imprint>
			<date type="published" when="2006">2006</date>
		</imprint>
	</monogr>
	<note>Norm</note>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Ontologies as conceptual models for XML documents</title>
		<author>
			<persName><forename type="first">M</forename><surname>Erdmann</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Studer</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 12th International Workshop on Knowledge Acquisition, Modelling and Mangement (KAW&apos;99)</title>
				<meeting>the 12th International Workshop on Knowledge Acquisition, Modelling and Mangement (KAW&apos;99)<address><addrLine>Banff, Canada</addrLine></address></meeting>
		<imprint>
			<date type="published" when="1999">1999</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Natural language processing and its future in medicine</title>
		<author>
			<persName><forename type="first">C</forename><surname>Friedman</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Hripcsak</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Academic Medicine</title>
		<imprint>
			<biblScope unit="volume">74</biblScope>
			<biblScope unit="issue">8</biblScope>
			<biblScope unit="page" from="890" to="895" />
			<date type="published" when="1999">1999</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">Building Ontologies from XML Data Sources</title>
		<author>
			<persName><forename type="first">R</forename><surname>Ghawi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Cullot</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">DEXA Workshops</title>
				<imprint>
			<date type="published" when="2009">2009</date>
			<biblScope unit="page" from="480" to="484" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<monogr>
		<author>
			<persName><forename type="first">T</forename><surname>Grainger</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Potter</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Seeley</surname></persName>
		</author>
		<title level="m">Solr in action</title>
				<imprint>
			<publisher>Manning</publisher>
			<date type="published" when="2014">2014</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">MEDSYNDIKATEa natural language system for the extraction of medical information from findings reports</title>
		<author>
			<persName><forename type="first">U</forename><surname>Hahn</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Romacker</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Schulz</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">International journal of medical informatics</title>
		<imprint>
			<biblScope unit="volume">67</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page" from="63" to="74" />
			<date type="published" when="2002">2002</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title level="a" type="main">General Formal Ontology (GFO): A foundational ontology for conceptual modelling</title>
		<author>
			<persName><forename type="first">H</forename><surname>Herre</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Theory and applications of ontology: computer applications</title>
				<imprint>
			<publisher>Springer Netherlands</publisher>
			<date type="published" when="2010">2010</date>
			<biblScope unit="page" from="297" to="345" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">Template and Model Driven Development of Standardized Electronic Health Records</title>
		<author>
			<persName><forename type="first">S</forename><surname>Kropf</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Chalopin</forename></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Denecke</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Studies in health technology and informatics</title>
		<imprint>
			<biblScope unit="volume">216</biblScope>
			<biblScope unit="page" from="30" to="34" />
			<date type="published" when="2015">2015</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<monogr>
		<author>
			<persName><forename type="first">M</forename><surname>Mccandless</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Hatcher</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Otis</forename><surname>Gospodnetic</surname></persName>
		</author>
		<title level="m">Lucene in Action: Covers Apache Lucene 3</title>
				<imprint>
			<publisher>Manning Publications Co</publisher>
			<date type="published" when="2010">2010</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<analytic>
		<title level="a" type="main">The Protégé project: A look back and a look forward. AI Matters</title>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">A</forename><surname>Musen</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Association of Computing Machinery Specific Interest Group in Artificial Intelligence</title>
		<imprint>
			<biblScope unit="volume">1</biblScope>
			<biblScope unit="issue">4</biblScope>
			<biblScope unit="page" from="4" to="12" />
			<date type="published" when="2015">2015</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<monogr>
		<title level="m" type="main">TNM classification of malignant tumours</title>
		<editor>Sobin, L. H., Gospodarowicz, M. K. and Wittekind C.</editor>
		<imprint>
			<date type="published" when="2011">2011</date>
			<publisher>John Wiley &amp; Sons</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b16">
	<analytic>
		<title level="a" type="main">Search Ontology, a new approach towards Semantic Search</title>
		<author>
			<persName><forename type="first">Alexandr</forename><surname>Uciteli</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="s">GI-Jahrestagung</title>
		<imprint>
			<biblScope unit="page" from="667" to="672" />
			<date type="published" when="2014">2014</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b17">
	<analytic>
		<title level="a" type="main">XML Path Language (XPath)</title>
		<ptr target="https://www.w3.org/TR/xpath/[cited2016-06-09" />
	</analytic>
	<monogr>
		<title level="m">) Version 1.0. W3C Recommendation</title>
				<imprint>
			<date type="published" when="2015">2015</date>
		</imprint>
	</monogr>
</biblStruct>

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