<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>LABO: an ontology for laboratory test prescription and reporting</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Paul Fabry</string-name>
          <email>paul.fabry@usherbrooke.ca</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Adrien Barton</string-name>
          <email>adrien.barton@irit.fr</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jean-François Ethier</string-name>
          <email>jean-francois.ethier@usherbrooke.ca</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Groupe de Recherche Interdisciplinaire en Informatique de la Santé (GRIIS), Université de Sherbrooke</institution>
          ,
          <addr-line>Quebec</addr-line>
          ,
          <country country="CA">Canada</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Institut de Recherche en Informatique de Toulouse (IRIT)</institution>
          ,
          <addr-line>CNRS</addr-line>
          ,
          <country country="FR">France</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>LABO is an ontology formalizing laboratory tests prescriptions and reporting documents. It is built according to the OBO Foundry methodology, and is a component of a core ontological model that aims to enable interoperability between various clinical data sources in the context of a Learning Health System.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>laboratory test; OBO Foundry; information content entity</p>
    </sec>
    <sec id="sec-2">
      <title>Introduction</title>
      <p>
        Learning Health Systems (LHS) analyze health information
generated from patients in order to provide secondary use of
clinical data and decision support. They rely on access to a wide
range of clinical data, such as drug prescriptions or laboratory test
prescriptions and results, usually scattered across numerous
heterogeneous information systems (
        <xref ref-type="bibr" rid="ref1">1</xref>
        ).
      </p>
      <p>
        Applied ontologies can support a common, source-independent
representation of these data, thus helping to solve the "Tower of
Babel problem" in medical informatics. An ontology has already
been developed for drug prescriptions: the Prescription of DRugs
Ontology (PDRO, read "Pedro") (
        <xref ref-type="bibr" rid="ref2">2</xref>
        ). This abstract presents the
creation of an ontology using a similar methodology for
representing laboratory tests prescriptions and reporting
documents: LABO (for LABoratory Ontology).
      </p>
    </sec>
    <sec id="sec-3">
      <title>Methods</title>
    </sec>
    <sec id="sec-4">
      <title>Results</title>
      <p>
        LABO has been developped according to a realist approach based
on the Basic Formal Ontology. It represents informational entities
directing and reporting on laboratory tests as subclasses of
IAO:Information content entity ("ICE") (
        <xref ref-type="bibr" rid="ref3">3</xref>
        ).
      </p>
      <p>A central class in LABO is Laboratory test directive item, which
is a subclass of IAO:Action specification, and is defined as: “An
action specification that directs one or several laboratory tests and
such that none of its proper parts directs some but not all of those
laboratory tests.” This definition is motivated by the fact that
some instructions ("complete blood count", for example) direct
several distinct tests (more than a dozen for the complete blood
count: hematocrit, hemoglobin, etc.; but no part of the ICE
'complete blood count' does specifically directly a hematocrit test,
a hemoglobin test, etc.). We define a Directed laboratory test
group as the mereological sum of laboratory tests directed by a
Laboratory test directive item. In our example, the item 'complete
blood count' written on a laboratory test prescription directs an
instance of Directed laboratory test group composed by an
instance of Hematocrit test, an instance of Hemoglobin test, etc.
A Laboratory result is a specified output of a OGMS:Laboratory
test, and LABO represents several subclasses of Laboratory result
to allow the representation of ratio, scalar, textual or range results.
A Laboratory test result item is about a OGMS:Laboratory test
and has as part a Laboratory result, as well as ICEs specifying the
time and specimen characteristic. It is a part of a Laboratory test
reporting group, which also encompass the corresponding
Laboratory test directive item.</p>
    </sec>
    <sec id="sec-5">
      <title>Conclusions</title>
      <p>The LABO ontology formalizes laboratory test prescriptions,
results and reporting, as well as their parts. Along with PDRO, it
is a part of a core ontological model to enable interoperability
between various clinical data sources in a LHS context.</p>
    </sec>
    <sec id="sec-6">
      <title>Address for correspondence</title>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Ethier J-F</surname>
            ,
            <given-names>M</given-names>
            cGilchrist M
          </string-name>
          ,
          <string-name>
            <surname>Barton</surname>
            <given-names>A</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cloutier A-M</surname>
            , Curcin
            <given-names>V</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Delaney</surname>
            <given-names>BC</given-names>
          </string-name>
          , et al.
          <article-title>The TRANSFoRm project: Experience and lessons learned regarding functional and interoperability requirements to support primary care</article-title>
          .
          <source>Learning Health Systems</source>
          .
          <year>2018</year>
          ;
          <volume>2</volume>
          (
          <issue>2</issue>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Ethier</surname>
            <given-names>J-F</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Barton</surname>
            <given-names>A</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Taseen</surname>
            <given-names>R.</given-names>
          </string-name>
          <article-title>An ontological analysis of drug prescriptions</article-title>
          .
          <source>Applied Ontology</source>
          .
          <year>2018</year>
          ;
          <volume>13</volume>
          (
          <issue>4</issue>
          ):
          <fpage>273</fpage>
          ‑
          <lpage>94</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Smith</surname>
            <given-names>B</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ceusters</surname>
            <given-names>W</given-names>
          </string-name>
          . Aboutness:
          <article-title>Towards foundations for the information artifact ontology</article-title>
          .
          <source>In</source>
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>