<!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>Decentralized Management of Patient Pro les and Tra jectories through Semantic Web Agents?</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Jean-Paul Calbimonte</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Davide Calvaresi</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Michael Schumacher</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>University of Applied Sciences and Arts Western Switzerland (HES-SO)</institution>
          ,
          <addr-line>Sierre</addr-line>
          ,
          <country country="CH">Switzerland</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>The usage of healthcare data for analytics and patient applications has increased in recent years opening a number of technical, ethical and scienti c challenges. Among these, those related to the management of personal and sensitive health data have been addressed through decentralized solutions for patient data, often implemented and modelled using distributed agents and semantic technologies. In this paper1 we present a technical summary of our previous works in this area, comprising e orts to: (i) use ontology models to represent patient trajectories, (ii) employ agent-based architectures to model and employ decentralized patient data exchanges, (iii) de ne agent cooperation and negotiation strategies for healthcare data interactions, (iv) adopt semantic data models for privacy-aware agents, and (v) implement multi-agent systems for real-time healthcare data processing.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        An increasing number of patients face the challenge of having to follow
treatments at home, often having to cope with complications and issues, having to
rely on healthcare professionals only when the situation becomes critical. Typical
examples include people su ering from chronic diseases, or conditions following
cancer survival [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]. Under these circumstances, physicians and healthcare
personnel need to personalize the treatment and take into account individual
characteristics of each patient, e.g., understanding the details of previous medical
encounters, interventions, medication, symptoms, and co-morbidities.
Digitization of health care records and the use of hybrid care technologies including
monitoring and virtual health coaching have showed a great potential for
improving the quality of support for these patients. In fact, nowadays health records
include a considerable amount of information, which is often not fully exploited
for the bene t of patients.
      </p>
      <p>
        The emergence of methodologies to characterize patient trajectories [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] has
opened a way for systematic analysis of patient contextual data, including
healthcare events, conditions, co-morbidities, emotional and social indicators,
selfreported outcomes, and observations during and after treatment [
        <xref ref-type="bibr" rid="ref15 ref8">8, 15</xref>
        ]. However,
? Copyright c 2020 for this paper by its authors. Use permitted under Creative
Commons License Attribution 4.0 International (CC BY 4.0).
1 This paper is a Technical Summary of previous published works.
so far there is still a need for comprehensive techniques that allow exploiting
trajectory data using Machine Learning (ML) and other related AI techniques.
Although numerous previous works have focused on prediction, classi cation
and automated learning on speci c types/parts of a patient health record, the
key challenge lies on the combination of the di erent layers that constitute a
trajectory.
      </p>
      <p>In this work, we advocate the use of intelligent agents as the foundational
information management entity for patient trajectories, in conjunction with
semantic models to support data exchange. We summarize our previous e orts in
this context, which constitute a solid basis for semantic-aware and decentralized
management of patient trajectory data. We argue that patients can delegate
the management of personal trajectory data to dedicated agents, which in turn
can automatically negotiate and cooperate with other agents, for instance to
share and aggregate anonymized data, to grant access to agents of medical sta ,
or to allow ML processing and prediction. The scienti c contributions
summarized in this work essentially identify two key research axes: patient trajectory
heterogeneity, and decentralization of data and processing. The rst dimension
refers not only to the high diversity of potential data sources (EHR, sensor data,
imaging, self-reported outcomes), but also to the heterogeneity of modelling and
representation of trajectories. Regarding decentralization, given the distributed
nature of data sources and processing units, as well as the necessity for
patients to have full control over their personal data, it is mandatory to provide
technological means for autonomous data management.</p>
      <p>In the remainder of this paper, we introduce the di erent challenges addressed
in this context (Section 2), before brie y describing how each of our previous
works addresses them. Hence, we discuss our contributions on ontology-based
modelling of trajectory data in Section 3, decentralized personal data in
Section 4, agent cooperation and negotiation in Section 5, privacy-aware agents in
Section 7, and real-time and stream processing of trajectory data in Section 6.
We provide a discussion on perspectives and future research lines in Section 8.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Challenges in Patient Trajectory Data Management</title>
      <p>
        Among the numerous challenges regarding patient trajectory management and
its exploitation we focus on the following fundamental aspects:
{ Trajectory modelling. The di culty of exchanging heterogeneous data is of
particular importance in the healthcare domain, and more so in trajectories
where information pieces may span from demographics to radiology images,
or multi-parametric sensor observations. A coherent trajectory model can
only be constructed if it relies on solid foundations, linked to existing
standard vocabularies in the medical realm. Moreover, these models must be
machine-understandable in order to allow autonomous entities (i.e., agents)
to take decisions based on their contents.
{ Decentralization. Patient data is bound to be stored, managed and processed
in a distributed manner. The provenance of trajectory data typically includes
di erent hospitals, clinics and medical cabinets, which are not expected to
respond to central governance. Moreover, given the current regulations on
personal health data [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ], patients may now have full control over where and
how their data is stored and/or processed. It is imperative to empower
patients and participants and allow them to take informed decisions regarding
their own data, as well as results, clinical studies and processing outcomes
based on them.
{ Cooperation. A comprehensive approach to the exploitation of patient
trajectory data can only be possible if multiple decentralized parties exchange
responsibility and processing/analytics duties. Given that trajectory data
may be managed by di erent entities, it becomes necessary to provide the
mechanisms that guarantee e ective interactions among them. These
cooperation schemes include participatory data collection, data reuse, collaborative
processing, etc.
{ Data Volume &amp; Velocity. It is essential to consider not only the large volumes
of data related to patient trajectories, but also the speed at which they
are produced and processed. We underline the importance of providing the
capability of responding to real-time constraints, as well as to the streaming
nature of certain trajectory data sources, e.g., those provided by sensing and
IoT devices.
{ Data Privacy. None of the above challenges can be fully addressed if the
sensitive nature of patient data is not taken into consideration. Privacy
preservation as well as trustful interactions are absolutely necessary for any
trajectory-based system to be acceptable according to current regulations
regarding data protection [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ].
      </p>
      <p>In the next sections we indicate how our previous works addressed these
challenges, fundamentally through agent-based models and semantic technologies.
3</p>
    </sec>
    <sec id="sec-3">
      <title>Ontology-based Trajectory Modelling</title>
      <p>
        In order to cope with the heterogeneity of patient trajectory data sources
and types of data, we have proposed to represent them using semantic models
linked to standard vocabularies in the medical, pharmaceutical and healthcare
domain [
        <xref ref-type="bibr" rid="ref4 ref6">4, 6</xref>
        ]. Our approach regarding trajectory modeling follows an
ontologybased methodology. A trajectory is conceived as a knowledge graph centered
around the patient, and linking di erent entities that represent medical
conditions, therapies, symptoms, drug prescription, diagnosis, monitoring
observations, etc. We depict in Figure 1 a subset of such ontology model, based on
the widely used schema.org [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] vocabulary. The implementation of this data
model provides a solid basis for trajectory data exchange, with the possibility
of mapping to standard formats such as HL7 FHIR. In parallel, our approach
also emphasizes on the use on standard healthcare and bioinformatics
ontologies. In our data model, we link schema.org coding attributes to standard terms
in ontologies such as MeSH [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] or ICD-10 [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]. As a result, and as we will see
later, a trajectory encoded as RDF following this model can be shared, processed
and consumed by autonomous entities, according to established goals.
Furthermore, explainable results can be represented using this semantic representation,
providing the means for human-understandable trajectory analysis.
4
      </p>
    </sec>
    <sec id="sec-4">
      <title>Decentralized Personal Data Management</title>
      <p>
        One of the central contributions of our research on patient trajectories is the
design of autonomous agents capable of managing personal health information. A
main application for such agents is to provide behavior change support to patient
with chronic conditions [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. As depicted in Figure 2, we propose a model in which
each user (patient) agent has exclusive access to personal data, providing with
the ability to manage ne-grained access control and consent for any sharing or
processing actions. Each agent is equipped with a domain model that describes
as a knowledge graph the di erent factors that may a ect behavior change.
For example, this may include motivation or ability factors towards speci c
behavior change goals, e.g., adherence to a rehabilitation treatment. The agent
also includes a set of stages, goals and milestones which can be incorporated to
an internal state machine, as well as computational persuasion strategies that
might be launched according to currently detected inputs and interactions. All
these agent processes take into account the patient-speci c information contained
in the user pro le, which is kept as part of the agent beliefs, and is typically
composed of trajectory information modeled as described in Section 3.
      </p>
      <p>Beyond the patient private sphere, the model also considers the following
additional agents: (i) coordinator: it oversees the incorporation of new patient
agents, as well as governing over stage changes and regulating interactions and
disseminating domain model information that may a ect groups of participants
in a behavior change program; (ii) coach: it provides specialized guidance to a
patient through his user agent, demanding access to certain personal data if it
requires to be processed by a behavior agent; (iii) mediator: allows
patient-topatient interactions that may be useful in order to adopt peer-to-peer strategies
for behavior change; (iv) behavior agent: in charge of providing trajectory and
behavior pattern analysis through AI exploitation of anonymized data.</p>
    </sec>
    <sec id="sec-5">
      <title>Inter-agent Cooperation and Negotiation</title>
      <p>
        Beyond modelling the agents themselves, it is critical to provide well-de ned
strategies for cooperation among patient (And trajectory) agents, so that they
are able to interact as described in the previous section. We introduced in [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] the
concept of Agents, or patient trajectory management agents (Figure 3), which
are characterized by a set of goals, beliefs, and behaviors; and include specialized
knowledge graphs of patient trajectory data. Agents may play di erent roles
and accordingly adopt di erent (and even competing) goals and behaviors. For
instance, a patient agent may focus on improving quality of life indicators, or
to retain moderate physical activity over time. In contrast, a coaching agent
may de ne its goals in terms of level of adherence of its assigned patients a
certain therapy. The same logic applies to beliefs and behaviors, and the resulting
interactions among Agents. As seen in Figure 3, some agents may focus on data
acquisition behaviors (e.g., continuous monitoring of health indicators), others
on trajectory analysis (e.g., through machine learning algorithms), or patient
trajectory anonymization and aggregation through a negotiation process (e.g.,
consent granting). We provide further details in [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] about how communication
channels in Agents use RDF as underlying representation model to achieve
these interactions, embedded into standard agent protocols.
6
      </p>
    </sec>
    <sec id="sec-6">
      <title>Real-time stream processing agents</title>
      <p>
        The ubiquity of sensor technologies for monitoring and reporting health-related
observations has already had a profound impact on clinical protocols, studies,
and patient support services. The consumption and analysis of data streams
produced by these sensors is challenging, especially for decentralized architectures.
In [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] we propose a model for stream processing agents, capable of acting
according to beliefs and goals represented as RDF streams, and including real-time
constraints. The proposed architecture is centered on the notion of RDF Stream
Processing RSP agents, which are autonomous entities as those in Section 5,
with the added ability of communicating and exchanging RDF streams.
      </p>
      <p>Following the Semantic Web principles, each agent and its resources are
uniquely identi ed through URIs, and are equipped with endpoints that can
be used to reach the RSP agent resources. The resources of each RSP agent
includes the metadata of the RDF streams it manages, as well as other information
relative to them (i.e., background RDF datasets, RDF stream bu ers, ontology
TBoxes, and RDF constraint rules). Depending on the nature of the RSP agent,
it may implement di erent types of stream processing mechanisms such as
continuous query processing, complex event processing, and stream reasoning.</p>
      <p>As an example, the Stream Receiver in Figure 4 is a special case of a RSP
agent that is able to consume streaming messages arriving at its inbox. The
producer agent, or Stream Sender, can push streaming data at a given rate,
which can be negotiated between the two parties. All streaming RDF stream
messages are semantically annotated, e.g., using the data model in Section 3.</p>
    </sec>
    <sec id="sec-7">
      <title>Privacy-aware Agents for Patient Data Exchange</title>
      <p>
        Having described our approach for agent-based decentralized management of
patient information, it would not be complete without considering complying with
privacy protection regulations and guarantees. The enforcement of the General
Data Protection Regulation (GDPR) [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ] imposes, for instance, the need for
explicit consent for data reuse, the right to timely receive all collected data, or
the right to completely delete personal data. Beyond existing GDPR-compliant
frameworks [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] that rely on centralized solutions, we explored and proposed in [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]
the adoption of decentralized agent-based data privacy negotiation, coordination,
and enforcement, using semantic representations of personal data privacy.
      </p>
      <p>
        We de ned a set of minimal personal data privacy interaction requirements
among agents and the design principles of privacy-aware agent interactions
regarding personal data handling. Then, we integrated these concepts into an
architecture design based on multi-agent protocol speci cations, encoded as RDF
messages. We base this speci cation in the Data Privacy Vocabulary (DPV) [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ],
developed by the Data Privacy Vocabularies and Controls Community Group of
the W3C. We identi ed three main design principles to enable privacy compliant
agent interactions:
{ Decentralized agents: Following the nomenclature of the GDPR these
privacyaware agents can be: data controllers, subjects, recipients, and processors
(Figure 5). Controllers refer to people or organizations that govern personal
data processing. Subjects are the persons to which the data is related, while
recipients are those to which personal information is disclosed. Processors
are entities that process personal data on behalf of the controller.
{ Shared semantic vocabulary: Semantic interoperability among these agents
is dictated by the use of a common ontology for representing privacy data.
      </p>
      <p>We advocate the use of the Data Privacy Vocabulary (DPV)2.
{ Data privacy agent interactions: In principle, we base the de nition of these
interactions in existing FIPA protocols. For instance, a data consent request
can be embedded in a request interaction protocol, or a data crowd-sourcing
request can be represented as a ContractNet protocol.
8</p>
    </sec>
    <sec id="sec-8">
      <title>Perspectives and Future Directions</title>
      <p>Our vision for decentralized management of patient trajectory data using
semantic agents has shown the potential of relying on autonomous processing and
delegation of sensitive data processing. Nevertheless, it still remains necessary to
take these building blocks and use them to implement our vision of decentralized
2 https://www.w3.org/ns/dpv
patient trajectory management. In this section we provide a rst glimpse of how
this could be materialized.</p>
      <p>As shown in Figure 6 we can represent the past events and circumstances of
the patient history as a (retrospective) trajectory, in which each item is encoded
as a semantically annotated entity (as described in Section 3). This trajectory
is therefore part of a patient knowledge graph, in which |for example{ a
diagnosis can be represented as a MedicalCondition, with a speci c ICD-10 code.
The trajectory itself can also characterize the patient degree of
distress/wellness, not only from a physical perspective, but also considering the social and
psychological dimensions. For instance, the patient trajectory may exhibit a
general physical decline after a surgery, while she can show general emotional
improvement following physical therapy. If these trajectories are collected for a
large number of participants, it is then possible to compute patterns and build
models that allow predicting future outcomes. In Figure 6 we also show how
predictive trajectories can be build using ML models, providing alternative
trajectories depending on previous events, as well as on actions taken and achieved
goals. As an example, given a certain retrospective trajectory, the system may
predict three distinct trajectory outcomes depending on the degree of adherence
to a therapy, enabling a personalized assessment of risks.</p>
      <p>Following our architectural and conceptual propositions described in
Sections 4, 5, and 6, we provide a use-case example of how agent-based interactions
can be used to enact trajectory-based analytics and support (Figure 7). Consider
a cancer survivor who follows physical therapy to regain and maintain muscular
strength. She is equipped with wearable sensors that collect motion data that
can constitute part of her trajectory, using a stream-based model as explained
in Section 6. However, this trajectory data is controlled by her through a patient
trajectory agent ( Agent), and is not available to others unless explicit
permissions are granted. As explained in Section 7, a coaching Agent can emit a call
for data, specifying purposes and other details through a consent, to which the
patient agent can a rmatively respond. Once the access is granted, the data
provided by the patient's sensor agents can be shared with the coaching agent.
Similarly, retrospective trajectory data can be collected from a set of patient agents,
and used to build a predictive trajectory model. The interaction between the
coaching and processing Agents allows the former to provide a personalized
advice to the patient, while informing a therapist (through his corresponding
agent) about the general progress, risks, and other relevant information.</p>
      <p>Although our contributions in the works summarized in this paper provide
preliminary evidence of applicability in the eHealth domain, there are still several
research directions to be explored, included in our road-map. In the following
we mention the most prominent ones:
(i) Trajectory modelling. Our proposed semantic model approach for patient
trajectories is a rst attempt that still needs to be validated in more
complex scenarios, possibly in conjunction with data exchange, for instance
in clinical trials where consent management and data restitution are
critical. We also anticipate the need for domain-speci c vocabularies/ontologies
that may be required in order to better represent trajectory events, decision
support, and delegation scenarios.
(ii) Implementation and validation. A key step in future research is the
implementation and deployment of the proposed agent-based architecture,
under real conditions and with a large cohort of patients. The complexity
of the evaluation and validation of this approach is an additional challenge
that will need to be addressed in order to provide an assessment from a
technological and health-care point of view.
(iii) Decentralized explainability. A topic that has not been su ciently explored
concerns the explainability of trajectory analysis, and more so when ML
algorithms are executed in a decentralized manner, with the risk of losing
provenance information or missing relevant contextual information.
(iv) Trust and accountability. Unlike top-down approaches for data privacy
compliance, our vision for decentralized personal data privacy interactions
has the potential of allowing more exible and scalable processing and
protection of sensitive data. Nevertheless, it remains necessary to study the
degrees of trust among participating agents, and to establish negotiation
procedures when undesirable behaviors are detected. Accountable
trajectory agents should be studied in order to address these concerns.
(v) Patient empowerment. Privacy protection is not the only aspect in which
patients have the right to manage their own data. Patients should be
provided with mechanisms for tracking their own data (e.g., for a clinical
study) or even providing feedback, reusing it for her own bene t in a
different context, or even exploring it through a set of third party services.</p>
    </sec>
    <sec id="sec-9">
      <title>Acknowledgements</title>
      <p>This work is partially supported by the H2020 project PERSIST: Patient-centered
survivorship care plan after cancer treatment (GA 875406); and the HES-SO
RCSO ISNet Project PERSA.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Alexander</surname>
            ,
            <given-names>G.L.</given-names>
          </string-name>
          :
          <article-title>The nurse|patient trajectory framework</article-title>
          .
          <source>Studies in health technology and informatics 129(Pt 2)</source>
          ,
          <volume>910</volume>
          (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Bourgeois</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kortuem</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kawsar</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          :
          <article-title>Trusted and gdpr-compliant research with the internet of things</article-title>
          .
          <source>In: Proceedings of the 8th International Conference on the Internet of Things</source>
          . pp.
          <volume>1</volume>
          {
          <issue>8</issue>
          (
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Calbimonte</surname>
            ,
            <given-names>J.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Calvaresi</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dubosson</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schumacher</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Towards pro le and domain modelling in agent-based applications for behavior change</article-title>
          .
          <source>In: Intl Conf on Practical Applications of Agents and Multi-Agent Sys</source>
          . pp.
          <volume>16</volume>
          {
          <issue>28</issue>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Calbimonte</surname>
            ,
            <given-names>J.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dubosson</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schumacher</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Towards semantic models for proceeding and behavior change in ehealth applications</article-title>
          .
          <source>In: Proc. of the PD Track of the 15th Intl. Conference on Semantic Systems SEMANTiCS</source>
          . pp.
          <volume>41</volume>
          {
          <issue>45</issue>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Calvaresi</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Calbimonte</surname>
            ,
            <given-names>J.P.</given-names>
          </string-name>
          :
          <article-title>Real-time compliant stream processing agents for physical rehabilitation</article-title>
          .
          <source>Sensors</source>
          <volume>20</volume>
          (
          <issue>3</issue>
          ),
          <volume>746</volume>
          (
          <year>2020</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Calvaresi</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schumacher</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Calbimonte</surname>
            ,
            <given-names>J.P.</given-names>
          </string-name>
          :
          <article-title>Agent-based modeling for ontology-driven analysis of patient trajectories</article-title>
          .
          <source>J. Med. Systems</source>
          <volume>44</volume>
          (
          <issue>9</issue>
          ),
          <volume>1</volume>
          {
          <fpage>11</fpage>
          (
          <year>2020</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Calvaresi</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schumacher</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Calbimonte</surname>
            ,
            <given-names>J.P.</given-names>
          </string-name>
          :
          <article-title>Personal data privacy semantics in multi-agent systems interactions</article-title>
          .
          <source>In: International Conference on Practical Applications of Agents and Multi-Agent Systems</source>
          . pp.
          <volume>55</volume>
          {
          <fpage>67</fpage>
          . Springer (
          <year>2020</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Chung</surname>
            ,
            <given-names>J.Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lee</surname>
            ,
            <given-names>D.H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Park</surname>
            ,
            <given-names>J.H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lee</surname>
            ,
            <given-names>M.K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kang</surname>
            ,
            <given-names>D.W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Min</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kim</surname>
            ,
            <given-names>D.I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jeong</surname>
            ,
            <given-names>D.H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kim</surname>
            ,
            <given-names>N.K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Meyerhardt</surname>
            ,
            <given-names>J.A.</given-names>
          </string-name>
          , et al.:
          <article-title>Patterns of physical activity participation across the cancer trajectory in colorectal cancer survivors</article-title>
          .
          <source>Supportive Care in Cancer</source>
          <volume>21</volume>
          (
          <issue>6</issue>
          ),
          <volume>1605</volume>
          {
          <fpage>1612</fpage>
          (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Guha</surname>
            ,
            <given-names>R.V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Brickley</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Macbeth</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          : Schema.
          <article-title>org: evolution of structured data on the web</article-title>
          .
          <source>Communications of the ACM</source>
          <volume>59</volume>
          (
          <issue>2</issue>
          ),
          <volume>44</volume>
          {
          <fpage>51</fpage>
          (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Koutkias</surname>
            ,
            <given-names>V.G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chouvarda</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Triantafyllidis</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Malousi</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Giaglis</surname>
            ,
            <given-names>G.D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Maglaveras</surname>
          </string-name>
          , N.:
          <article-title>A personalized framework for medication treatment management in chronic care</article-title>
          .
          <source>IEEE Trans. on Inf. Tech. in Biomedicine</source>
          <volume>14</volume>
          (
          <issue>2</issue>
          ),
          <volume>464</volume>
          {
          <fpage>472</fpage>
          (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Nelson</surname>
            ,
            <given-names>S.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schopen</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Savage</surname>
            ,
            <given-names>A.G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schulman</surname>
            ,
            <given-names>J.L.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Arluk</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          :
          <article-title>The mesh translation maintenance system: structure, interface design, and implementation</article-title>
          . In: Medinfo. pp.
          <volume>67</volume>
          {
          <issue>69</issue>
          (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Organization</surname>
            ,
            <given-names>W.H.</given-names>
          </string-name>
          , et al.:
          <article-title>Icd-10: international statistical classi cation of diseases and related health problems: tenth revision (</article-title>
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Pandit</surname>
            ,
            <given-names>H.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Polleres</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bos</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Brennan</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bruegger</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ekaputra</surname>
            ,
            <given-names>F.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fernandez</surname>
            ,
            <given-names>J.D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hamed</surname>
            ,
            <given-names>R.G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kiesling</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lizar</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          , et al.:
          <article-title>Creating a vocabulary for data privacy</article-title>
          .
          <source>In: OTM to Meaningful Internet Systems</source>
          . pp.
          <volume>714</volume>
          {
          <issue>730</issue>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Voigt</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Von dem Bussche</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>The eu general data protection regulation (gdpr). A Practical Guide</article-title>
          , 1st Ed., Cham: Springer International Publishing (
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Wu</surname>
            ,
            <given-names>H.S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Harden</surname>
            ,
            <given-names>J.K.</given-names>
          </string-name>
          :
          <article-title>Symptom burden and quality of life in survivorship: a review of the literature</article-title>
          .
          <source>Cancer nursing</source>
          <volume>38</volume>
          (
          <issue>1</issue>
          ),
          <source>E29{E54</source>
          (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>