Unverified Commit 9fb04548 authored by Maxime Lefrançois's avatar Maxime Lefrançois
Browse files

update documentation according to TS 2.1.1

parent ee93c0c4
Loading
Loading
Loading
Loading
Loading

documentation/abstract.html

deleted100644 → 0
+0 −3
Original line number Diff line number Diff line
<!--TS 103 673 v0.3.4 Clause 9.7.1-->
<!--The optional documentation source abstract.html or abstract.md shall contain a short description of the SAREF project version ontology. It shall not include diagrams.-->
<p>The objective of SAREF4EHAW is to extend <a href="https://saref.etsi.org/core/">SAREF ontology</a> for the eHealth/Ageing-well (EHAW) vertical. </p>
 No newline at end of file
+35 −0
Original line number Diff line number Diff line
<div class="alert-warning">NOTE: The text in this section is extracted from ETSI TS 103 410-8 (V2.1.1) <a href="#[0]">[0]</a>, and therefore falls inside the <a href="https://www.etsi.org/intellectual-property-rights">ETSI IPR Policy</a></div>

The objective of SAREF4EHAW is to extend SAREF ontology (see ETSI TS 103 264 [[1]](#[1])) for the eHealth/Ageing-well (EHAW) vertical. Clause 4.1 of [the technical specification ETSI TS 103 410-8](#[0]) shortly introduces a high level view of the envisioned SAREF4EHAW semantic model and modular ontology, with the retained concepts (i.e. classes) and their relations. 

SAREF4EHAW extension has been specified and formalized by investigating EHAW domain related resources, as reported in ETSI TR 103 509 [[i.7]](#[i.7]), such as: potential stakeholders, standardization initiatives, alliances/associations, European projects, EC directives, existing ontologies and data repositories. Therefore, SAREF4EHAW modular ontology shall both:

* Allow the implementation of a limited set of typical EHAW related use cases already identified in ETSI TR 103 509 [[i.7]](#[i.7]), i.e.:
    * use case 1 "monitoring and support of healthy lifestyles for citizens";
    * use case 2 "Early Warning System (EWS) and Cardiovascular Accidents detection".
* Fulfill the EHAW related requirements provided in ETSI TR 103 509 [[i.7]](#[i.7]), mainly the ontological ones that were mostly taken as input for the ontology specification.

SAREF4EHAW mainly reuses the following existing ontologies: SAREF (see ETSI TS 103 264 [[1]](#[1])), SmartBAN (see ETSI TS 103 378 [[2]](#[2])), SAREF4ENVI (see ETSI TS 103 410-2 [[3]](#[3])) and SSN (see [[i.1]](#[i.1])). SAREF4EHAW modular ontology will be fully specified and formalized in clause 4.2 of [the technical specification ETSI TS 103 410-8](#[0]). [Figure 1](#Figure_1) presents the high level view of the envisioned model of SAREF4EHAW ontology. In [Figure 1](#Figure_1), classes directly imported from SAREF ontology are in yellow, classes directly imported from SAREF4ENVI ontology are in pink and finally classes specifically developed for SAREF4EHAW are in blue.


<figure>
    <img src="diagrams/Overall.png" alt="High level view of the envisioned semantic model for SAREF4EHAW ontology "/>
    <figcaption id="Figure 1">Figure 1: High level view of the envisioned semantic model for SAREF4EHAW ontology </figcaption>
</figure>


SAREF4EHAW is extending SAREF ontology for the EHAW vertical and thus shall logically mainly model the following concepts (i.e. classes within [Figure 1](#Figure_1)):

* EHAW system actors (HealthActor class depicted in [Figure 1](#Figure_1)) that are mainly responsibility parties (plays the role of the legal entity responsible for a Body Area Network - BAN -), patients/users, caregivers, helpers. A caregiver (Caregiver class depicted in [Figure 1](#Figure_1)) may have one or multiple patients. A helper (Helper class depicted in [Figure 1](#Figure_1)) may follow one or multiple users and or patients. As also shown in [Figure 1](#Figure_1), users and patients may have habits (e.g. smoking or overeating), impairments (e.g. visual or mobility), and postures (e.g. sitting or running) modelled as possible States of each actor.
* Health devices (HealthDevice class depicted in [Figure 1](#Figure_1)) that are main components of an eHealth system and are mainly BAN hubs (i.e. Body Area Networks dedicated hubs, BanHub class depicted in [Figure 1](#Figure_1)), Healthdedicated sensors (HealthSensor class depicted in [Figure 1](#Figure_1)), Health-dedicated actuators (HealthActuator class depicted in [Figure 1](#Figure_1)) and Health-dedicated wearables (HealthWearable class depicted in [Figure 1](#Figure_1)). Those health devices have a given function (Function class depicted in [Figure 1](#Figure_1)) aiming to support to accomplish their tasks. Function can act upon features, properties, or states. An instance of [saref:Function](https://saref.etsi.org/core/Function) can apply to different devices.
* A health device could be attached to one or multiples health actors, for example a caregiver that is using this device for a measurement collection session, a patient whose some vital data are measured by this device. This is modelled through the HealthActor class as depicted in [Figure 1](#Figure_1).
* An actuator is used for an actuation process and does action materialized via the Command class as depicted in [Figure 1](#Figure_1).
* Wearables, that are smart electronic devices, are also used for monitoring simple/complex vital parameters of patients/users. Wearables are not developed in [the technical specification ETSI TS 103 410-8](#[0]) since they are already fully specified and formalized in ETSI TS 103 410-9 [[4]](#[4]). However, they shall also be listed as possible health-dedicated devices (i.e. through HealthWearable as sub-class of HealthDevice, as depicted in [Figure 1](#Figure_1)).
* BAN (Ban class depicted in [Figure 1](#Figure_1)) that is mainly used for collecting, aggregating and relaying patient or user vital parameters. It shall therefore logically contain BAN-dedicated hubs, health-dedicated sensors, health-dedicated actuators and health-dedicated wearables, as depicted in [Figure 1](#Figure_1).
* Observation collection session (ObservationCollectionSession class depicted in [Figure 1](#Figure_1)) that logically has health actors (at least a caregiver and/or a patient/user) as participants (see [Figure 1](#Figure_1)).

For semantic interoperability handling purposes, an ontology based solution, combined with sensing-as-a-service and WoT strategies, is retained for SAREF4EHAW. Therefore, an upper level ontology, at service level, shall also be fully modelled (Service class and sub-classes depicted in [Figure 1](#Figure_1)).

Finally, SAREF4EHAW is an OWL-DL ontology. For embedded semantic analytics purposes, SAREF4EHAW shall be designed using the modularity principle (see ETSI TR 103 509 [[i.7]](#[i.7])) and can thus be mainly described by the following self-contained knowledge modules: HealthActor, Ban, HealthDevice, Function (measured data related concepts included) and Service. All these SAREF4EHAW modules will be fully detailed in clause 4.2 of [the technical specification ETSI TS 103 410-8](#[0]). The prefixes and namespaces used in SAREF4EHAW and in [the technical specification ETSI TS 103 410-8](#[0]) are listed in [the Namespace Declarations section](#namespacedeclarations).

+0 −2
Original line number Diff line number Diff line
<!--TS 103 673 v0.3.4 Clause 9.7.1-->
<!--The optional documentation source acknowledgement.html or acknowledgement.md shall contain a list of acknowledgements. It shall not include diagrams.-->
+5 −0
Original line number Diff line number Diff line
The editors would like to thank the ETSI SmartM2M technical committee for providing guidance and expertise.

Also, many thanks to the ETSI staff and all other current and former active Participants of the ETSI SmartM2M group for their support, technical input and suggestions that led to improvements to this ontology.

Also, special thanks goes to the ETSI SmartM2M Technical Officer Guillemin Patrick for his help.

documentation/contributors.html

deleted100644 → 0
+0 −8
Original line number Diff line number Diff line
<!--TS 103 673 v0.3.4 Clause 9.7.1-->
<!--The optional documentation source contributors.html or contributors.md shall describe the list of any contributor. The Steering Board and project leader are responsible for approving the list of contributors. The set of contributors in the ontology document shall correspond to the list of contributors in this document source.-->
<ul>
  <li><a href="https://www.linkedin.com/in/lina-nachabe-2b292457/">Lina Nachabe</a> (<a href="http://www.mines-telecom.fr/en/">Institut Mines-Télécom - Télécom SudParis</a>)</li>
  <li><a href="https://research.utwente.nl/en/persons/jo%C3%A3o-luiz-moreira">João Luiz Moreira</a> (<a href="https://utwente.nl/">University of Twente</a>)</li>
  <li><a href="https://pdi.fbk.eu/people/profile/dragoni">Mauro Dragoni</a> (<a href="http://www.fbk.eu/">Fondazione Bruno Kessler</a>)</li>
  <li><a href="http://www.maxime-lefrancois.info/">Maxime Lefrançois</a> (<a href="http://www.mines-telecom.fr/en/">Institut Mines-Télécom - MINES Saint-Étienne</a>)</li>
</ul>
 No newline at end of file
Loading