<!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>
      <journal-title-group>
        <journal-title>Bennett, C.-H. Chen, et al., Semantically enabling clinical decision support recommendations,
Journal of Biomedical Semantics</journal-title>
      </journal-title-group>
      <issn pub-type="ppub">1613-0073</issn>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="doi">10.1007/978</article-id>
      <title-group>
        <article-title>Observation and Progression Events Ontology</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Asara Senaratne</string-name>
          <email>asara.senaratne@flinders.edu.au</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Oshani Seneviratne</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Hon Zent Lim</string-name>
          <email>lim0862@flinders.edu.au</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Leelanga Seneviratne</string-name>
          <email>leelangas@uom.lk</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Workshop</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="editor">
          <string-name>Health Trajectory Modelling, Disease Progression, Chronic Diseases, Temporal Events, Artificial Intelligence</string-name>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>5th International Workshop on Scientific Knowledge: Representation, Discovery, and Assessment</institution>
          ,
          <addr-line>Nov 2025, Nara</addr-line>
          ,
          <country country="JP">Japan</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>College of Science and Engineering, Flinders University</institution>
          ,
          <addr-line>South</addr-line>
          <country country="AU">Australia</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Department of Computer Science, Rensselaer Polytechnic Institute</institution>
          ,
          <addr-line>Troy, NY</addr-line>
          ,
          <country country="US">USA</country>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>Faculty of Information Technology, University of Moratuwa</institution>
          ,
          <country country="LK">Sri Lanka</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2025</year>
      </pub-date>
      <volume>14</volume>
      <issue>2023</issue>
      <fpage>1</fpage>
      <lpage>11</lpage>
      <abstract>
        <p>Artificial Intelligence (AI) is increasingly applied in healthcare to enable early detection, personalized prediction, and proactive management of chronic diseases. However, their efective integration remains hindered by the lack of a semantic framework that consolidates evolving patient trajectories, intervention pathways, and computational methods. This gap leads to significant challenges in model interpretability, reproducibility of research findings, and the systematic discovery of actionable insights from longitudinal patient data. In this work, we present the Chronic Observation and Progression Events (COPE) Ontology, an ontology designed to support health informaticians and data scientists in modelling chronic disease progression and aligning it with AI-driven approaches. Using the COPE ontology, we can capture patient related knowledge, including biological, behavioural, demographic, psychographic, and geographical characteristics, as well as modifiable and non-modifiable risk factors, symptom progression, and disease outcomes. The COPE ontology introduces a temporal structure that enables the representation of timestamped clinical events, symptoms, interventions, and exposures, thereby facilitating detailed modelling of disease trajectories over time. Also, COPE integrates AI/ML techniques for analyzing chronic disease conditions gleaned from scholarly literature. It further embeds the provenance of computational models, linking them to the six datasets the models use, the twenty five research literature from which they originate, and the specific health contexts in which they are applied. By bridging patient characteristics, temporal health trajectories, intervention strategies, and AI/ML capabilities within a unified semantic framework, the ontology provides a robust foundation for interpretable, reproducible, and patient oriented decision support. We demonstrate its utility through exemplar queries, ofering it as a reusable resource for advancing the integration of AI in health trajectory modelling for chronic disease care.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        Chronic diseases such as diabetes, cardiovascular conditions, and respiratory illnesses represent a
significant burden on global healthcare systems, accounting for nearly 74% of all deaths worldwide [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ].
Early detection and efective intervention are critical to managing these conditions and improving
patient outcomes. In recent years, Artificial Intelligence (AI) and Machine Learning (ML) have emerged
as powerful tools in this space, enabling prediction, stratification, and personalized care planning [
        <xref ref-type="bibr" rid="ref2 ref3">2, 3</xref>
        ].
      </p>
      <p>
        A key challenge in advancing AI-driven health systems for chronic disease management lies in
the absence of a semantic framework that cohesively brings together knowledge on patient disease
trajectories, potential interventions over time, and the computational models used to support
decisionmaking. Traditional approaches often create fragmented knowledge [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], making it challenging to
understand the origin of AI model predictions, compare intervention efectiveness across diferent
patient groups, or identify new disease progression patterns systematically [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. This fragmentation
hinders the creation of interpretable, reproducible, and patient-centered systems, thereby limiting
our ability to gain actionable insights for precision medicine. Although notable ontology-driven
explainable approaches have emerged for chronic diseases in clinical settings [
        <xref ref-type="bibr" rid="ref6 ref7 ref8">6, 7, 8</xref>
        ], a cohesive
      </p>
      <p>CEUR</p>
      <p>ceur-ws.org
PersonCharacteristic
hasCharacteristic
RiskFactor</p>
      <p>Person
hasRiskFactor showsSymptom</p>
      <p>Symptom
observedBy observedBy</p>
      <p>ObservationSource
includes</p>
      <p>Device
hasMeasurementUnit
MeasurementUnit
pulsFromTrajectory</p>
      <p>
        TimeStamp
solution that integrates various aspects for developing comprehensive patient trajectories is still needed.
An ontology, a formal and structured representation of knowledge [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ], ofers a powerful means to
address this challenge by capturing complex interdependencies between patient characteristics, disease
progression, interventions, and computational analysis in a machine interpretable manner [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ].
      </p>
      <p>
        To address this gap, we propose Chronic Observation and Progression Events (COPE), an ontology
that unifies knowledge around the modelling of health trajectories in chronic disease contexts, the timing
and nature of interventions across these trajectories, and the AI/ML methods used to derive clinical
insights. We visualize the conceptual model of COPE in Figure 1. Unlike existing ontologies [
        <xref ref-type="bibr" rid="ref11 ref12 ref13">11, 12, 13</xref>
        ],
which often focus either only on biomedical entities or algorithmic taxonomies, our approach holistically
integrates biological, behavioural, psychographic, demographic, and geographical patient characteristics
with modifiable and non-modifiable risk factors, symptom evolution, and disease outcomes.
      </p>
      <p>The COPE ontology includes classes and properties that formalize relationships between patient
profiles, observed symptoms, clinical interventions, and the dynamic progression of chronic illnesses. It
also semantically links these entities to computational models, capturing details of AI/ML techniques
(such as classification, regression, and clustering), data types (such as structured, temporal, and
multimodal), sources (such as EHRs, ECG, and wearable sensors), and scholarly outputs (such as datasets,
publications, and venues).</p>
      <p>A major contribution of the ontology is its support for temporal reasoning. Through the
ObservationEvent class and its associated properties, it models timestamped clinical observations and intervention
records, enabling representation of time-dependent health trajectories (we describe in Section 3). This
temporal scafolding allows for complex, longitudinal queries such as; What symptoms emerged after a
specific intervention? or How did the patient’s risk profile evolve across disease stages and episodes?</p>
      <p>We also capture AI/ML models and datasets used in the literature for health trajectory modelling. The
purpose is to support health informaticians and data scientists by bringing this fragmented knowledge
into one structured, accessible space. By doing so, the ontology enables users to identify and reuse
established modelling techniques, replicate prior studies, compare performance across datasets, and
build upon proven approaches. It facilitates systematic exploration of past research, helping practitioners
avoid redundant eforts while ensuring alignment with clinically validated practices. Ultimately, this
promotes more eficient, evidence-based development of technical solutions tailored to chronic disease
trajectories.</p>
      <p>Overall, the COPE ontology is designed to serve three interconnected purposes: (1) to enable semantic
modelling of chronic disease trajectories using episodic or continuous data from diverse sources such
as wearable devices and clinical systems, (2) to support health informaticians, behavioral scientists,
and data scientists in systematically mapping AI/ML contributions to chronic disease prediction and
management, thereby accelerating scientific understanding and evidence-based practice by providing a
semantically rich foundation for advanced analytical methods, and (3) to predict suitable interventions
based on disease and patient profiles.</p>
      <p>We demonstrate the utility of COPE through a set of competency questions and example queries that
highlight its application in chronic disease research and decision support. In Section 2, we present a
review of existing literature in the domains of designing ontology and health trajectory modelling. We
present our COPE ontology in Section 4 and its evaluation in Section 5. We conclude the paper setting
the future directions in Section 6.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Literature Review</title>
      <p>In recent years, the transformation of healthcare through data has spurred the need for intelligent,
interoperable systems that can represent, reason about, and act upon complex medical knowledge.
Traditional electronic health records (EHRs) and siloed datasets, while rich in information, often
fail to capture the nuanced interplay between clinical factors such as patient characteristics, disease
progression, symptom evolution, risk factors, devices used for symptoms measuring, and therapeutic
interventions. This gap has motivated researchers and clinicians alike to turn toward ontologies for
formal and machine readable representations of domain knowledge as a means to integrate and analyse
such multidimensional information more efectively.</p>
      <p>
        Foundational biomedical ontologies like Systematized Nomenclature of Medicine: Clinical Terms
(SNOMED CT) [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ], Logical Observation Identifiers Names and Codes (LOINC) [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ], and the Gene
Ontology [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ] have laid the groundwork by establishing standardized vocabularies for clinical
observations, laboratory tests, and genetic factors. These eforts enable interoperability at a syntactic level but
often lack the semantic expressiveness needed for modelling when a symptom occurs, how a disease
evolves, or which risk factors precede a particular outcome. While the Human Disease Ontology [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]
and Human Phenotype Ontology [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ] provide well curated vocabularies for classifying diseases and
phenotypic features, they do not ofer native support for representing temporal sequences or linking
these concepts to evidence from real-world datasets and literature.
      </p>
      <sec id="sec-2-1">
        <title>2.1. Temporal Clinical Ontologies &amp; Event-Based Modelling</title>
        <p>
          Time is a fundamental aspect of clinical reasoning. Diseases unfold over time, interventions are applied
at specific moments, and symptoms often emerge in unpredictable patterns. Despite these, most existing
healthcare ontologies are atemporal. They represent what exists, but not when it exists. The W3C Time
Ontology in OWL [
          <xref ref-type="bibr" rid="ref16">16</xref>
          ] provides primitives such as instant, interval, and duration, which are designed to
model temporal relationships. However, their adoption in healthcare ontologies has been limited. One
efective workaround proposed in ontology engineering is event introduction. That is, modelling events
such as a symptom was observed or a treatment was applied as first class entities, which allows temporal
and contextual metadata to be attached to clinical interactions. More recent eforts, such as the Time
Event Ontology (TEO) [
          <xref ref-type="bibr" rid="ref17">17</xref>
          ], explicitly model complex temporal relationships found in clinical narratives,
demonstrating advanced capabilities for representing temporal reasoning in healthcare. Furthermore,
frameworks like OCEP [
          <xref ref-type="bibr" rid="ref18">18</xref>
          ] utilize ontology-based complex event processing for healthcare decision
support, integrating real-time data from various sources to identify dynamic clinical patterns.
        </p>
      </sec>
      <sec id="sec-2-2">
        <title>2.2. Semantic Integration of AI/ML Models with Clinical Data</title>
        <p>
          Parallel to this development, the growing use of AI and ML in clinical decision support systems (CDSS)
introduces a new modelling challenge [
          <xref ref-type="bibr" rid="ref19">19</xref>
          ]. Although AI/ML models are increasingly relied upon to
predict disease onset, identify risk factors, and recommend interventions, they are often treated as
black boxes with interpretation dificulties and poorly integrated into semantic healthcare frameworks.
Ontologies such as ML-Schema [20] and Ontology of Core Data Mining Entities (OntoDM-Core) [21]
have emerged to address this gap by describing ML workflows and metadata. However, their use
remains largely separate from healthcare ontologies and does not yet enable the modelling of AI models
in conjunction with specific patient data, symptoms, or interventions [ 22, 23].
        </p>
        <p>Furthermore, there is a notable disconnect between scientific evidence and its formal representation
in clinical ontologies. Ontologies such as the Bibliographic Ontology (BIBO) [24] and the Semantic
Publishing and Referencing (SPAR) Ontology [25] enable the formalization of metadata about research
publications, yet they are rarely linked to the clinical phenomena they investigate. In evidence-based
medicine, however, it is vital to trace findings back to the articles, authors, and venues that reported
them, specially when these findings underpin AI models used in real-world healthcare decisions.</p>
      </sec>
      <sec id="sec-2-3">
        <title>2.3. Semantic Clinical Pathway/Guideline Ontologies</title>
        <p>Health trajectory modelling and prevention strategy frameworks, such as the American Heart
Association (AHA) taxonomy for chronic disease management [26], aim to categorize how diseases progress
over time and how interventions can alter these trajectories. Some taxonomies explicitly incorporate
trajectory or disease stages. For instance, life-course frameworks and traditional public health models
categorize interventions by when they occur relative to disease progression (such as pre-disease, early
disease, established disease, and so on) [27]. Such taxonomies are valuable for organizing knowledge
across diverse diseases and populations, guiding research and clinical decision-making. However,
existing taxonomies vary widely in structure and focus. A narrowly scoped taxonomy can be deeply
detailed for that domain but may not extend easily to other conditions. Conversely, broad taxonomies
often categorize by disease type (such as communicable, non-communicable, mental health, and injury)
and by intervention strategy, to ensure all health issues are covered. A scalable taxonomy should ideally
allow cross-cutting modules, for example, one axis for disease category and another for intervention
type or data type, so that it can expand as new diseases or strategies are considered. Beyond mere
categorization, there is a growing need for semantic representation of clinical pathways and guidelines
to ensure standardized, evidence-based care. Ontologies like ShaRE-CP (Shareable and Reusable Clinical
Pathway) Ontology [28] focus on formalizing clinical pathways, including temporal constraints between
interventions and linking them to relevant health resources and contextual information. Such eforts
are crucial for enabling automated reasoning about treatment plans, identifying optimal intervention
sequences, and ensuring adherence to best practices, which aligns with COPE’s goal of supporting
intervention prediction based on patient and disease profiles.</p>
        <p>In summary, while existing ontologies have made strides in formalizing healthcare knowledge, most
remain limited in temporal scope, disconnected from AI workflows, and loosely coupled to scientific
evidence. Therefore, the ontology introduced in this paper aims to fill these gaps by creating a unified,
extensible, and temporally grounded ontology that reflects both clinical processes and computational
intelligence, aligned with the needs of modern health systems and data science applications.</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3. Health Trajectory</title>
      <p>
        Based on the emerging Interpretive Paradigm for knowledge representation [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] and sensitive data
representation [30], we define a health trajectory as a collection of sequentially linked observer events
that share the same membership (trajectory membership). We visualize this in Figure 2. The health
trajectory is local to a specific entity, such as a person or a community. Contrary to existing trajectory
modelling, our approach detects and allows multiple normalities to exist simultaneously. At any given
Anomalous
      </p>
      <p>Space</p>
      <p>Drift
Health Trajectory of a Person</p>
      <p>Normality of the anomalous space</p>
      <p>Drift
Anomalous</p>
      <p>Space</p>
      <p>Termination
Prominence</p>
      <p>Normality of the anomalous space</p>
      <p>Continuation
temporal point, the entity (a person in this case) accommodates one trajectory out of several possible
others. These alternative trajectories are modelled in anomalous spaces [31, 32, 33] relative to the
current trajectory the person traverses. The trajectory a person is in, is called the participating trajectory,
which will be denoted by a participation rank of 0. The ranks of the other trajectories of the same
person indicate the relative pull efect to become the participating trajectory.</p>
      <p>When trajectory progression approaches a defined drift point, the propensity to deviate is governed
by two principal forces: the pull efect and the withdrawal efect. The pull efect is quantified by the
convergence index, which measures the degree of alignment between the current progression and the
set of all feasible trajectories at time   . In contrast, the withdrawal efect is determined by the latching
strength of the present trajectory, expressed as the conditional probability that the progression will
remain within the current trajectory versus the likelihood of disengagement and transition into an
alternative trajectory.</p>
      <p>The tendency of a person to progress through the same trajectory, given the circumstances, is
represented as prominence. A drift point is a moment when an individual’s health trajectory changes
significantly, potentially pulling them from one trajectory to another. For example, from a healthy
state to a deteriorating one. Accordingly, health trajectory modelling involves the assessment of
sequentially linked observer events as a sequence of states over time. Each state will correspond to a
particular combination of physiological, emotional, and behavioural data. Machine learning techniques
such as LSTM (Long Short-Term Memory) networks potentially model these sequences, capturing the
relationships between diferent states and how they evolve. Here we study how individuals transition
from one trajectory to another by studying drift points over time. For example, we examine how
someone moves from a stable to a declining health trajectory [29].</p>
      <sec id="sec-3-1">
        <title>3.1. Use Case</title>
        <p>Having defined the conceptual structure of health trajectories, we now ground these ideas in a concrete
use case. Consider a diabetes management scenario. A patient’s health trajectory includes timestamped
laboratory observations (HbA1c values, BMI), wearable-derived data (daily step counts, heart rate
variability), and behavioural attributes (dietary habits, stress levels). These are represented in COPE as
ObservationEvents linked to PersonCharacteristics and RiskFactors.</p>
        <p>Trajectory progression. At baseline, the patient resides in a stable TrajectoryPhase. Over time,
consistently elevated HbA1c values and sedentary behaviour introduce a drift point, triggering a
transition into a deteriorating trajectory.</p>
        <p>Interventions. Pharmacological treatments (e.g., metformin) and behavioural programs (e.g.,
increased exercise) are modelled as instances of the Intervention class, applied to specific
TrajectoryPhases. Their efects can be queried across patients with similar risk profiles.</p>
        <p>Outcome. This scenario demonstrates how COPE integrates patient data, temporal trajectories,
and AI provenance into a coherent framework. Researchers can ask: Which interventions were most
efective for patients with similar risk profiles? Which AI/ML models (e.g., LSTMs) have been applied
to predict progression? While diabetes illustrates the workflow, COPE is designed to generalize across
chronic disease contexts.</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4. Ontology Overview</title>
      <p>This section presents our COPE ontology, that was developed to formally represent the intersection
between patient profile, disease profile, symptom dynamics, risk factors, and the integration of AI/ML
methods for chronic disease modelling, as shown in Figure 1. We designed the ontology to support
knowledge-driven reasoning and semantic querying in health informatics applications, particularly
those involving time-aware patient trajectory analysis and explainable ML.</p>
      <p>We developed the ontology with several key objectives in mind. First, it aims to support a
patientcentered approach to disease modelling by capturing biological, psychological, behavioural, and
demographic characteristics. Second, it is designed to represent the dynamic nature of chronic disease
progression through temporally anchored clinical events and distinct phases of health trajectories.
Third, the ontology incorporates AI and ML models that have been used in the literature for chronic
disease management, prediction and health trajectory profiling. Fourth, it integrates research
knowledge artifacts such as scientific publications, datasets, and evidence of model performance to support
informed decision-making. Finally, the ontology enables reasoning and semantic querying across
patient profiles, model metadata, and scholarly outputs, facilitating more intelligent exploration and
reuse of knowledge in chronic disease research. The COPE ontology includes the following high-level
classes:
• Person and Characteristics: The central class Person is associated with instances of
PersonCharacteristic, categorized into subtypes such as Biological, behavioural,
Demographic, Psychographic, and Geographical. These characteristics inform disease
susceptibility and model stratification. Individuals are also linked to one or more RiskFactor
instances.
• Symptoms and Observations: Clinical manifestations are represented by the Symptom class.</p>
      <p>Symptoms are temporally recorded via ObservationEvent, which encapsulates time-stamped
symptom occurrence, observation source (such as device and Electronic Health Records: EHR),
and optional quantitative values. This enables modelling symptom timelines and episodic patterns.
• Health Trajectories: Temporal sequences of observation events are grouped into a
HealthTrajectory, which consists of ordered TrajectoryPhase instances (such as onset,
exacerbation, and remission). Each phase is annotated with start and end dates, enabling longitudinal
modelling of disease progression.
• Diseases and Interventions: Diseases are modelled via the Disease class and are
connected to Symptom, RiskFactor, CycleOfDeconditioning, and DiseaseOutcome.
Interventions are instances of the Intervention class, categorized into Pharmacological, Therapeutic,
Preventive, and behavioural, and linked to either symptoms or diseases through appliedTo
or appliedIn.
• Artificial Intelligence Models: AI models are represented using the AIModel class, associated
with Dataset (via trainedOn), ModellingApproach, InputDataNature, and Explanation.
Performance metrics are modeled using PerformanceMetric and linked to the models they evaluate.
Each model or dataset may be described or proposed in a ResearchArticle, connected via
properties such as describes or evaluates. Articles are in turn linked to Author, DOI, and Venue
entities.</p>
      <sec id="sec-4-1">
        <title>4.1. Design and Development</title>
        <p>We developed COPE following a structured approach, beginning with the creation of a taxonomy
informed by requirements elicitation and literature analysis. To gather requirements related to personal
characteristics and health trajectories, we consulted Leelanga Seneviratne, a behavioural scientist and a
co-author of this paper. We also reviewed twenty five research papers focused on the application of AI in
chronic disease prediction and management. Based on this input, we formulated competency questions
to define the scope of the ontology, drawing on both our domain expertise and insights from the
literature. During the conceptualization phase, we decomposed the domain into modular components,
including patient characteristics, health trajectories, symptoms, observation events, risk factors, disease
outcomes, clinical interventions, AI models, and research artifacts. In the formalization phase, we
implemented these components in OWL 2 using Protégé, defining appropriate classes, object and data
properties, domain and range axioms, disjointness constraints, and human-readable annotations such as
rdfs:label and rdfs:comment. Finally, we evaluated the ontology by executing SPARQL queries based
on our competency questions over RDF instances to ensure completeness, correctness, and alignment
with the intended use cases.</p>
        <p>To ensure interoperability with scholarly metadata standards and integration with Research
Knowledge Graphs (RKGs), we reused elements from the Scholarly Communication Ontology (SCIO).
Specifically, we adopted:
• scio:Person represents an individual whose characteristics, behaviors, health trajectory, or
related data are captured in the ontology.
• scio:Disease captures a medical condition or diagnosis associated with a person, including
links to symptoms, risk factors, and outcomes.
• scio:Device refers to a data collection device that collects information about one or more objects.
• scio:Intervention Refers to a clinical action or treatment.
• scio:Dataset denotes a structured collection of data generated or used in research, enabling
traceability, reuse, and citation through metadata.
• scio:hasSource a relation between an entity and another entity from which it stems from.
• scio:describes a relation between one entity and another entity that it provides a description
of (detailed account).
• scio:precedes expresses a temporal or logical ordering between two entities, such as sequential
interventions, observation events or stages in a process.
• scio:isMemberOf a mereological relation between a item and a collection.
• scio:isPartOf a transitive, reflexive and anti-symmetric mereological relation between a whole
and itself or a part and its whole.</p>
      </sec>
      <sec id="sec-4-2">
        <title>4.2. Release and Sustainability Strategy</title>
        <p>To ensure best practices in ontology publication, COPE is assigned the persistent namespace: https:
//purl.archive.org/cope#, which is dereferenceable and ensures long-term accessibility. We have released
the first public version (V1) of the ontology, which is available through the open-source repository on
GitHub available at https://github.com/hzent/COPE. In addition to an interactive dashboard available at
https://hzent.github.io/COPE/CopeDashboard.html, we provide a standardized WIDOCO [34]-generated
documentation that describes the ontology’s scope, comprehensive documentation of the classes and
properties introduced, which is available from the ontology namespace https://purl.archive.org/cope.
This documentation complements this paper and the dashboard, making it easier for others to adopt</p>
        <sec id="sec-4-2-1">
          <title>Which patient characteristics are most A person who undergoes a high level of stress strongly associated with increased sus- is more susceptible for anxiety. ceptibility to specific diseases?</title>
        </sec>
        <sec id="sec-4-2-2">
          <title>Which population groups are most sus- A person whose hobby is mountain hiking is ceptible to disease X based on their more susceptible to Monge’s disease. characteristics?</title>
        </sec>
        <sec id="sec-4-2-3">
          <title>Given certain patient characteristics, A female having BRCA1/2 gene mutation is what disease(s) are they at risk of de- having high risk of getting breast cancer. veloping in the near future?</title>
        </sec>
        <sec id="sec-4-2-4">
          <title>What are the risk factors associated with lung cancer?</title>
        </sec>
        <sec id="sec-4-2-5">
          <title>What diseases are patients at risk of, and what are the associated disease outcomes, and identifying symptoms?</title>
        </sec>
        <sec id="sec-4-2-6">
          <title>Which trajectory does the person participate in at a specific observation event?</title>
        </sec>
        <sec id="sec-4-2-7">
          <title>Which disease are the symptoms observed in within the current participating trajectory?</title>
        </sec>
        <sec id="sec-4-2-8">
          <title>Smoking and prolonged exposure to Radon</title>
          <p>are risk factors associated with cancer.</p>
        </sec>
        <sec id="sec-4-2-9">
          <title>Alcoholic person is more likely to get Hypertension and might be having risk of kidney failure.</title>
        </sec>
        <sec id="sec-4-2-10">
          <title>As per the observation event noted on the 3rd of August, HT01002 is the participating trajectory of the person.</title>
        </sec>
        <sec id="sec-4-2-11">
          <title>Fatigue and chest pain observed on the 3rd of August in the participating trajectory are related to Coronary Artery Disease.</title>
        </sec>
        <sec id="sec-4-2-12">
          <title>Which AI/ML techniques are most com- LSTM and Transformers are commonly used monly used for modelling disease pro- for identifying the progression of stroke. gression?</title>
        </sec>
        <sec id="sec-4-2-13">
          <title>Which research articles focus on the Priyanga, P., Pattankar, V. V., &amp; Sridevi, S. detection or prediction of chronic dis- (2021). A hybrid recurrent neural network ‐ loeases using AI/ML methods? gistic chaos‐based whale optimization framework for heart disease prediction with EHRs.</title>
        </sec>
        <sec id="sec-4-2-14">
          <title>Computational Intelligence., 37(1), 315–343. https://doi.org/10.1111/coin.12405 is an article that proposes a hybrid RNN for predicting heart disease.</title>
        </sec>
        <sec id="sec-4-2-15">
          <title>What is the predominant nature of Unstructured clinical notes are used with</title>
          <p>datasets used for training AI/ML mod- text embeddings + SVM for determining
els in disease prediction? Alzheimer’s disease.</p>
        </sec>
        <sec id="sec-4-2-16">
          <title>What ML models and input features LSTM is commonly used with HbA1c and</title>
          <p>are commonly used for predicting dis- Sleep Patterns to assess the likelihood of
haveases? ing Diabetes Mellitus.</p>
          <p>For a given data source, which AI/ML For data from wearable devices, Random
Fortechniques are most frequently ap- est is commonly used to recognize activities
plied? such as walking and climbing.
and extend COPE. Although COPE is at a prototype stage, we have outlined a clear strategy for
longterm sustainability. Future releases will follow semantic versioning, with major and minor updates
archived with persistent identifiers via purl to ensure reproducibility and traceability. Finally, to promote
community engagement and reuse, the GitHub repository includes an issue tracker and will include
contribution guidelines in upcoming releases. This will allow external contributors to propose new
terms, raise issues, and suggest extensions.</p>
        </sec>
      </sec>
      <sec id="sec-4-3">
        <title>4.3. Competency Questions</title>
        <p>To evaluate the expressiveness and utility of the COPE ontology, we formulated a set of competency
questions (as shown in Table 1) grouped across three core dimensions: Patient and Disease Associations,
Risk and Disease Progression, and AI/ML Techniques and Applications. These questions serve as
practical benchmarks to assess whether the ontology can adequately represent and retrieve knowledge
relevant to chronic disease and trajectory progression, AI integration, and patient context.</p>
        <p>The competency questions were derived from multiple sources. First, they were informed through
discussions with domain experts, including a neuroinformatician, a digital health researcher, and a
medical devices researcher, ensuring that the questions reflect practical considerations from medical
research and practice. Second, we reviewed relevant literature in neuroinformatics and digital health to
identify commonly addressed challenges and information needs. Together, these inputs provided both
empirical grounding and theoretical justification, ensuring that the competency questions are not only
intuitively valid but also aligned with practices and requirements observed in the medical domain.</p>
        <p>The first set of questions, Patient and Disease Associations, focuses on uncovering relationships
between individual characteristics and disease susceptibility. These questions evaluate whether the
ontology can support queries such as: which patient attributes (such as stress levels, lifestyle, or
genetic markers) are linked to heightened disease risk? and which demographic or behavioural profiles
correspond to specific chronic conditions? For example, given a patient with the gene mutation, the
ontology should allow retrieval of their elevated risk for breast cancer. These questions validate the
ontology’s ability to semantically model and reason over personal, biological, and environmental
characteristics in relation to diseases.</p>
        <p>The second set of questions, Risk and Disease Progression, examines how the ontology captures
risk factors, symptom patterns, and expected outcomes. Questions in this category assess whether
the ontology can express complex relationships, such as the link between alcohol consumption and
hypertension, or between smoking and lung cancer. Moreover, they test whether the ontology can be
queried to reveal probable disease outcomes based on combined risk profiles and symptom trajectories,
thereby supporting use cases like early risk assessment and proactive intervention planning.</p>
        <p>The third set of questions, Progression of Trajectories, addresses the temporal aspects of health
trajectories, focusing on how patient conditions develop and unfold over time. This group captures
questions that investigate the sequential and evolutionary nature of trajectories, such as identifying
which trajectory follows another, how one state transitions into the next, or how multiple trajectories
interrelate as a patient’s health status changes. Typical queries include: which trajectory follows which
other trajectory?, and how do trajectories evolve over a defined period of time? Such questions are
particularly important in clinical practice and research, as they enable the detection of early warning
signs, the mapping of disease progression patterns, and the evaluation of treatment efects. By modelling
these temporal dependencies, this group provides a foundation for understanding the dynamics of
health conditions rather than viewing them as isolated events.</p>
        <p>The fourth set of questions, AI/ML Techniques and Applications, tests the ontology’s capacity to
represent computational models, data sources, and research artifacts. These questions evaluate whether the
ontology can answer queries such as: which ML techniques are frequently used for disease prediction?
What features are commonly employed in training such models? and which datasets and literature
support these models? For instance, the ontology should link LSTM models with features like HbA1c
levels and sleep patterns in the context of diabetes prediction. It should also allow users to identify
relevant publications, such as studies proposing hybrid RNN frameworks for heart disease prediction,
and associate these with datasets and input modalities (such as unstructured clinical notes, wearable
device data).</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>5. Ontology Evaluation</title>
      <p>To evaluate the practical utility of the ontology, we adopted a competency question–based approach,
whereby the ontology was queried using SPARQL to test whether it could efectively answer real-world
analytical questions relevant to our domain. You can find evaluation done for all competency questions
on the COPE website1. As clinical data is not readily available, we performed first level validation [ 35]
using a synthetically generated healthcare dataset that simulates real-world EHRs including patients,
encounters, conditions, medications, procedures, observations, care plans, payers, and claims [36].</p>
      <p>In this section, we present the conceptual overview (in Figure 3), SPARQL query (in Listing 1) and
the answers we obtained (in Table 2) for the competency question Which patient characteristics are
most strongly associated with increased susceptibility to specific diseases? . Herewith, we aimed to validate
whether the ontology could support the identification of key person-level characteristics associated
with various chronic diseases and determine how frequently those characteristics appeared across
individuals in the dataset instantiated in RDF. We also provide the conceptual overview of the two
competency questions that focus on temporal aspects of COPE in Figures 4 and 5.
1https://hzent.github.io/COPE/CopeDashboard.html#competency-questions</p>
      <p>We executed a representative SPARQL query (shown in Listing 1) that retrieves all person-level
characteristics linked to diseases via risk factors and aggregates the number of patients (such as RDF
instances of sio:Person) exhibiting those characteristics. This query traverses the ontology’s structure
by combining several object properties—namely COPE:hasCharacteristic, COPE:hasRiskFactor, and
COPE:contributesTo, and filters the results to include only relevant characteristic types (biological,
demographic, behavioural, psychographic, and geographical) while excluding structural RDF elements
such as rdf:type, rdfs:label, and rdfs:comment. The query aggregates patient counts grouped by
both characteristic and disease, allowing us to gain insight into the most salient attributes influencing
particular health outcomes.</p>
      <p>PREFIX COPE: &lt;https://purl.archive.org/cope#&gt;
PREFIX sio: &lt;http://semanticscience.org/resource/&gt;
PREFIX rdf: &lt;http://www.w3.org/1999/02/22-rdf-syntax-ns#&gt;
PREFIX rdfs: &lt;http://www.w3.org/2000/01/rdf-schema#&gt;
SELECT
?personCharacteristic
?diseaseName
(STR(COUNT(DISTINCT ?person)) AS ?patient_count)
WHERE {
?person a sio:SIO_000498 ;</p>
      <p>COPE:hasCharacteristic ?charInd ;</p>
      <p>COPE:hasRiskFactor ?risk .
?charInd a ?charType ;</p>
      <p>?personCharacteristic ?value .</p>
      <p>FILTER(?charType IN (</p>
      <p>COPE:Biological,
COPE:Demographic,
COPE:behavioural,
COPE:Psychographic,</p>
      <p>COPE:Geographical))
FILTER(
?personCharacteristic != rdf:type &amp;&amp;
?personCharacteristic != rdfs:label &amp;&amp;
?personCharacteristic != rdfs:comment)
?risk COPE:contributesTo ?disease .</p>
      <p>?disease COPE:hasDiseaseName ?diseaseName .
}
GROUP BY ?personCharacteristic ?diseaseName
ORDER BY DESC(?patient_count)
Listing 1: SPARQL query to retrieve person characteristics associated with diseases and patient counts.</p>
      <p>The results of this evaluation are shown in Table 2, which presents a subset of the query
output. Notably, certain person characteristics such as hasExerciseFrequency, alcoholConsumption,
hasGender, and hasAge emerged consistently across multiple disease types, particularly for Lung
Cancer and Hypertension. For instance, Lung Cancer was associated with eight person-level features shared
across four patient instances, indicating strong coverage of characteristic-disease relationships.
Hypertension also showed high overlap, with similar attributes represented in three individuals. Furthermore,
the ontology captured nuanced demographic and behavioural traits relevant to disease modelling.
The properties hasEthnicity, hasCity, and hasCountry appeared frequently, highlighting the role
of geo-social factors in health data representation. Psychographic traits such as hasHealthAttitude
also featured across multiple diseases, validating the ontology’s capacity to accommodate complex,
non-clinical risk factors. Importantly, the appearance of hasPostalCode in at least one patient confirms
the ontology’s support for fine-grained geospatial attributes.</p>
      <p>In capturing temporal factors, Figure 4 illustrates the relationship between a person, their health
trajectory, and observation events. A Person entity is linked to a Health Trajectory through the
property hasHealthTrajectory, indicating the longitudinal record of their health status. Each person
is also associated with an ObservationEvent via the property isPairedWith, which captures the
temporal context of health-related data collection. The ObservationEvent is further connected to the
corresponding Health Trajectory through the memberOf property, signifying that individual observations
contribute to, and are embedded within, the broader health trajectory.</p>
      <p>Similarly, Figure 5 depicts how a disease and its associated symptoms are linked within a health
trajectory. The entity Disease (such as heart condition) is connected to a Health Trajectory via the
property hasHealthTrajectory, indicating its progression over time. The disease is identified by
symptoms such as fatigue and chest pain, which serve as clinical markers of its presence. These
symptoms are further observed in a specific ObservationEvent , capturing the temporal context of
their occurrence. The ObservationEvent itself is memberOf the Health Trajectory, thereby situating the
recorded clinical findings within the patient’s broader longitudinal health record. This representation
highlights the interplay between diseases, symptoms, and observation events, enabling structured
tracking of clinical evidence across time.</p>
      <p>COPE contains 36 classes and 48 relations, and we believe this is a suficiently rich structure for
modelling the target domain while remaining tractable for reasoning tasks. The reasoning complexity is
non-trivial: as the ontology grows, entailment (especially with transitive and temporal relations such as
precedes, leadsTo, isPartOf) and role chaining may increase the computational load. However, COPE
has been structured to contain such complexity by limiting deeply nested axioms and by modularizing
domain-specific expansions (for example, keeping clinical, device, and trajectory aspects relatively
decoupled) to help mitigate blow-up. In terms of scalability, we anticipate that COPE should scale to
integrate datasets containing tens of thousands to low hundreds of instances (patients, events,
trajectories) without excessive reasoning latency, particularly for routine tasks like instance classification or
SPARQL query answering. For very large-scale deployments (millions of individuals), one may adopt
hybrid reasoning and query strategies (such as pre-computation, incremental reasoning, approximate
reasoning, partitioning) to keep response times acceptable. Going forward, further empirical
benchmarking (measuring reasoning time, memory usage, and query throughput) will be essential to validate
these projections, especially when extending COPE with additional classes, axioms, or integrating with
other ontologies.</p>
    </sec>
    <sec id="sec-6">
      <title>6. Conclusion and Future Work</title>
      <p>In this paper, we presented the first version of the Chronic Observation and Progression Events Ontology
(COPE), an evolving, modular ontology designed to support the contextualized representation of person
characteristics, observation events, and health trajectories. Grounded in domain expertise and literature,
the ontology provides a semantic foundation for linking diverse concepts such as personal attributes,
risk factors, symptoms, interventions, and outcomes in the context of disease progression.</p>
      <p>This initial version serves as a basis for further refinement and extension. Our long-term vision is to
leverage COPE in the development of digital twins for modelling individual health trajectories. Through
such applications, the ontology can support personalized, AI-assisted decision-making in clinical and
public health contexts. As our work progresses, we will iteratively enrich the ontology to reflect
evolving data sources, computational models, and domain knowledge. Furthermore, while COPE has
been designed with internally defined concepts such as Disease, Symptom, and Intervention to support
ifrst-level validation with synthetic clinical data, future work will focus on enhancing its interoperability
with established biomedical standards. In particular, we plan to extend COPE by mapping its core
concepts to widely adopted vocabularies such as ICD-10, SNOMED CT, and LOINC. This alignment
will ensure semantic interoperability with EHR and existing biomedical ontologies, enabling COPE to
integrate into clinical workflows and supporting consistent interpretation of healthcare information
across systems. Also, we aim to explore how we can dynamically update the ontology with real-time
model outputs or feedback loops from deployed systems.</p>
      <p>Another avenue for future development is the incorporation of the Fast Healthcare Interoperability
Resources (FHIR) framework. By aligning COPE with FHIR resources, we aim to support standardized
data exchange and improve its compatibility with the growing ecosystem of FHIR-enabled healthcare
applications. Such integration facilitates getting deeper insights into patients, diseases, observations,
disease progressions, and their interrelationships, thereby enhancing the efectiveness of clinical decision
support and operational healthcare applications. This extension will strengthen COPE’s capacity to act
as a bridge between patient data and clinical information systems, ensuring that the ontology not only
serves research purposes but also supports real-world healthcare delivery and decision-making.</p>
    </sec>
    <sec id="sec-7">
      <title>7. Declaration of Generative AI Use</title>
      <p>Generative AI tools were not used in the creation of the intellectual or substantive content of this
document. Grammarly was used for light editing, including grammar, spelling, and style suggestions.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>World</given-names>
            <surname>Health</surname>
          </string-name>
          <string-name>
            <surname>Organization</surname>
          </string-name>
          , Noncommunicable diseases, https://www.who.int/news-room/ fact-sheets/detail/noncommunicable-diseases,
          <year>2023</year>
          . https://www.who.int/news-room/fact-sheets/ detail/noncommunicable-diseases.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>A.</given-names>
            <surname>Rajkomar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Dean</surname>
          </string-name>
          ,
          <string-name>
            <surname>I. Kohane,</surname>
          </string-name>
          <article-title>Machine learning in medicine</article-title>
          ,
          <source>New England Journal of Medicine</source>
          <volume>380</volume>
          (
          <year>2019</year>
          )
          <fpage>1347</fpage>
          -
          <lpage>1358</lpage>
          . doi:
          <volume>10</volume>
          .1056/NEJMra1814259.
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>A. M.</given-names>
            <surname>Alaa</surname>
          </string-name>
          ,
          <string-name>
            <surname>M. van der Schaar</surname>
          </string-name>
          ,
          <article-title>Forecasting individualized disease trajectories using interpretable deep learning</article-title>
          ,
          <source>Nature Communications</source>
          <volume>10</volume>
          (
          <year>2019</year>
          )
          <article-title>3923</article-title>
          . doi:
          <volume>10</volume>
          .1038/s41467- 019- 11335- 4.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>A.</given-names>
            <surname>Senaratne</surname>
          </string-name>
          , L. Seneviratne,
          <article-title>Embedded to interpretive: A paradigm shift in knowledge discovery to represent dynamic knowledge</article-title>
          ,
          <source>in: CEUR Workshop Proceedings</source>
          , volume
          <volume>3433</volume>
          ,
          <string-name>
            <surname>CEUR-WS</surname>
          </string-name>
          ,
          <year>2023</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>S.</given-names>
            <surname>Chari</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Qi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N. N.</given-names>
            <surname>Agu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Seneviratne</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. P.</given-names>
            <surname>McCusker</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K. P.</given-names>
            <surname>Bennett</surname>
          </string-name>
          ,
          <string-name>
            <surname>A. K. Das</surname>
          </string-name>
          ,
          <string-name>
            <surname>D. L. McGuinness</surname>
          </string-name>
          ,
          <article-title>Making study populations visible through knowledge graphs</article-title>
          , in: International semantic web conference, Springer,
          <year>2019</year>
          , pp.
          <fpage>53</fpage>
          -
          <lpage>68</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>S.</given-names>
            <surname>Chari</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Seneviratne</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D. M.</given-names>
            <surname>Gruen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. A.</given-names>
            <surname>Foreman</surname>
          </string-name>
          ,
          <string-name>
            <surname>A. K. Das</surname>
          </string-name>
          ,
          <string-name>
            <surname>D. L. McGuinness</surname>
          </string-name>
          ,
          <article-title>Explanation ontology: a model of explanations for user-centered ai</article-title>
          , in: International semantic web conference, Springer,
          <year>2020</year>
          , pp.
          <fpage>228</fpage>
          -
          <lpage>243</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>S.</given-names>
            <surname>Chari</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Acharya</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D. M.</given-names>
            <surname>Gruen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Zhang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E. K.</given-names>
            <surname>Eyigoz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Ghalwash</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Seneviratne</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F. S.</given-names>
            <surname>Saiz</surname>
          </string-name>
          , P. Meyer,
          <string-name>
            <given-names>P.</given-names>
            <surname>Chakraborty</surname>
          </string-name>
          , et al.,
          <article-title>Informing clinical assessment by contextualizing post-hoc explanations of risk prediction models in type-2 diabetes</article-title>
          ,
          <source>Artificial Intelligence in Medicine</source>
          <volume>137</volume>
          (
          <year>2023</year>
          )
          <fpage>102498</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>S.</given-names>
            <surname>Chari</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Seneviratne</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Ghalwash</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Shirai</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D. M.</given-names>
            <surname>Gruen</surname>
          </string-name>
          , P. Meyer, P. Chakraborty,
          <string-name>
            <given-names>D. L.</given-names>
            <surname>McGuinness</surname>
          </string-name>
          ,
          <article-title>Explanation ontology: A general-purpose, semantic representation for supporting user-centered explanations</article-title>
          ,
          <source>Semantic Web</source>
          <volume>15</volume>
          (
          <year>2024</year>
          )
          <fpage>959</fpage>
          -
          <lpage>989</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>N.</given-names>
            <surname>Guarino</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Oberle</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Staab</surname>
          </string-name>
          ,
          <article-title>What is an ontology?</article-title>
          , Handbook on ontologies (
          <year>2009</year>
          )
          <fpage>1</fpage>
          -
          <lpage>17</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>N. F.</given-names>
            <surname>Noy</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D. L.</given-names>
            <surname>McGuinness</surname>
          </string-name>
          ,
          <article-title>Ontology Development 101: A Guide to Creating Your First Ontology</article-title>
          ,
          <source>Technical Report KSL-01-05</source>
          , Stanford Knowledge Systems Laboratory,
          <year>2001</year>
          . https: //protege.stanford.edu/publications/ontology_development/ontology101.pdf.
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>R.</given-names>
            <surname>Cornet</surname>
          </string-name>
          , N. de Keizer,
          <article-title>Forty years of snomed: a literature review, BMC Medical Informatics and Decision Making 8 (</article-title>
          <year>2008</year>
          )
          <article-title>S2</article-title>
          . doi:
          <volume>10</volume>
          .1186/
          <fpage>1472</fpage>
          - 6947- 8- S1- S2.
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <surname>C. J. McDonald</surname>
            ,
            <given-names>S. M.</given-names>
          </string-name>
          <string-name>
            <surname>Huf</surname>
            ,
            <given-names>J. G.</given-names>
          </string-name>
          <string-name>
            <surname>Suico</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          <string-name>
            <surname>Hill</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          <string-name>
            <surname>Leavelle</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          <string-name>
            <surname>Aller</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Forrey</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          <string-name>
            <surname>Mercer</surname>
          </string-name>
          , G. DeMoor, J.
          <string-name>
            <surname>Hook</surname>
          </string-name>
          , et al.,
          <article-title>Loinc, a universal standard for identifying laboratory observations: a 5-year update</article-title>
          ,
          <source>Clinical chemistry 49</source>
          (
          <year>2003</year>
          )
          <fpage>624</fpage>
          -
          <lpage>633</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>M.</given-names>
            <surname>Ashburner</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C. A.</given-names>
            <surname>Ball</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. A.</given-names>
            <surname>Blake</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Botstein</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Butler</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. M.</given-names>
            <surname>Cherry</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. A.</given-names>
            <surname>Davis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Dolinski</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S. S.</given-names>
            <surname>Dwight</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. T.</given-names>
            <surname>Eppig</surname>
          </string-name>
          , et al.,
          <article-title>Gene ontology: tool for the unification of biology</article-title>
          ,
          <source>Nature genetics 25</source>
          (
          <year>2000</year>
          )
          <fpage>25</fpage>
          -
          <lpage>29</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>L. M.</given-names>
            <surname>Schriml</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Arze</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Nadendla</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.-C.</given-names>
            <surname>Chang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Mazaitis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Felix</surname>
          </string-name>
          , G. Feng,
          <string-name>
            <given-names>W. A.</given-names>
            <surname>Kibbe</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Greene</surname>
          </string-name>
          ,
          <article-title>Human disease ontology 2018 update: classification, content and workflow expansion</article-title>
          ,
          <source>Nucleic acids research</source>
          <volume>47</volume>
          (
          <year>2019</year>
          )
          <fpage>D955</fpage>
          -
          <lpage>D962</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>P. N.</given-names>
            <surname>Robinson</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Köhler</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Bauer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Seelow</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Horn</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Mundlos</surname>
          </string-name>
          ,
          <article-title>The human phenotype ontology: a tool for annotating and analyzing human hereditary disease</article-title>
          ,
          <source>American journal of human genetics 83</source>
          (
          <year>2008</year>
          )
          <fpage>610</fpage>
          -
          <lpage>615</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>J.</given-names>
            <surname>Hobbs</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Pan</surname>
          </string-name>
          , Time ontology in owl,
          <source>W3C Working Draft</source>
          ,
          <year>2006</year>
          . https://www.w3.org/TR/ owl-time/.
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <given-names>F.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Du</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>He</surname>
          </string-name>
          , H.-Y. Song,
          <string-name>
            <given-names>M.</given-names>
            <surname>Madkour</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Rao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Xiang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Luo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H. W.</given-names>
            <surname>Chen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Liu</surname>
          </string-name>
          , et al.,
          <article-title>Time event ontology (teo): to support semantic representation and reasoning of complex temporal relations of clinical events</article-title>
          ,
          <source>Journal of the American Medical Informatics Association</source>
          <volume>27</volume>
          (
          <year>2020</year>
          )
          <fpage>1046</fpage>
          -
          <lpage>1056</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18]
          <string-name>
            <given-names>R.</given-names>
            <surname>Chandra</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Agarwal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S. S.</given-names>
            <surname>Kumar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Singh</surname>
          </string-name>
          ,
          <string-name>
            <surname>Ocep:</surname>
          </string-name>
          <article-title>An ontology-based complex event processing framework for healthcare decision support in big data analytics</article-title>
          ,
          <source>arXiv preprint arXiv:2503.21453</source>
          (
          <year>2025</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          [19]
          <string-name>
            <given-names>O.</given-names>
            <surname>Seneviratne</surname>
          </string-name>
          ,
          <string-name>
            <surname>A. K. Das</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Chari</surname>
            ,
            <given-names>N. N.</given-names>
          </string-name>
          <string-name>
            <surname>Agu</surname>
            ,
            <given-names>S. M.</given-names>
          </string-name>
          <string-name>
            <surname>Rashid</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>McCusker</surname>
            ,
            <given-names>J. S.</given-names>
          </string-name>
          <string-name>
            <surname>Franklin</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Qi</surname>
            ,
            <given-names>K. P.</given-names>
          </string-name>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>