doc generated from pipeline

catalog-v001.xml

scripts

ts

documentation/ts_*

SAREF4EHAW mainly reuses the following existing ontologies: SAREF (see ETSI TS 103 264 [1]), SmartBAN (see ETSI TS 103 378 [2]), SAREF4ENVI (see ETSI TS 103 410-2 [3]) and SSN (see [i.1]). SAREF4EHAW modular ontology will be fully specified and formalized in clause 4.2 of the present document. Figure 1 presents the high level view of the envisioned model of SAREF4EHAW ontology. In 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 id="Figure_1">

<figure>

        <img data-docx-width="25.20cm" src="diagrams/SAREF4EHAW.Overall.png" alt="High level view of the envisioned semantic model for SAREF4EHAW ontology "/>

        <figcaption>Figure 1: High level view of the envisioned semantic model for SAREF4EHAW ontology </figcaption>

    </figure>

A detailed view of SAREF4EHAW HealthActor module is depicted in Figure 2.

<figure id="Figure_2">

<figure>

        <img data-docx-width="21.19cm" src="diagrams/SAREF4EHAW.HealthActor.png" alt="Detailed view of SAREF4EHAW HealthActor module "/>

        <figcaption>Figure 2: Detailed view of SAREF4EHAW HealthActor module </figcaption>

    </figure>

The object properties defined for SAREF4EHAW HealthActor module are described in Table 2. The data properties defined for SAREF4EHAW HealthActor module are described in Table 3.

<table id="Table_2" data-docx-preferred-width="4.69cm 3.50cm 4.00cm 5.19cm">

<table data-docx-preferred-width="4.69cm 3.50cm 4.00cm 5.19cm">

  <caption>Table 2: List of object properties of SAREF4EHAW HealthActor module</caption>

  <tr>

    <th>Object property</th>

A detailed view of SAREF4EHAW Ban module is depicted in Figure 3.

<figure id="Figure_3">

<figure>

        <img data-docx-width="19.34cm" src="diagrams/SAREF4EHAW.Ban.png" alt="Detailed view of SAREF4EHAW Ban module "/>

        <figcaption>Figure 3: Detailed view of SAREF4EHAW Ban module </figcaption>

    </figure>

The object properties defined for SAREF4EHAW Ban module are described in Table 4. The data properties defined for SAREF4EHAW Ban module are described in Table 5.

<table id="Table_3" data-docx-preferred-width="4.69cm 2.25cm 5.25cm 5.19cm">

<table data-docx-preferred-width="4.69cm 2.25cm 5.25cm 5.19cm">

  <caption>Table 3: List of object properties of SAREF4EHAW Ban module</caption>

  <tr>

    <th>Object property</th>

A detailed view of SAREF4EHAW HealthDevice module is depicted in Figure 4.

<figure id="Figure_4">

<figure>

        <img data-docx-width="15.90cm" src="diagrams/SAREF4EHAW.HealthDevice.png" alt="Detailed view of SAREF4EHAW HealthDevice module "/>

        <figcaption>Figure 4: Detailed view of SAREF4EHAW HealthDevice module </figcaption>

    </figure>

The object properties defined for SAREF4EHAW HealthDevice module are described in Table 6. The data properties defined for SAREF4EHAW HealthDevice module are described in Table 7.

<table id="Table_4" data-docx-preferred-width="3.99cm 3.49cm 3.98cm 5.94cm">

<table data-docx-preferred-width="3.99cm 3.49cm 3.98cm 5.94cm">

  <caption>Table 4: List of object properties of SAREF4EHAW HealthDevice module</caption>

  <tr>

    <th>Object property</th>

<table id="Table_5" data-docx-preferred-width="4.69cm 4.25cm 2.25cm 6.25cm">

<table data-docx-preferred-width="4.69cm 4.25cm 2.25cm 6.25cm">

  <caption>Table 5: List of data properties of SAREF4EHAW HealthDevice module</caption>

  <tr>

    <th>Data Property</th>

<figure id="Figure_5">

<figure>

        <img data-docx-width="16.43cm" src="diagrams/SAREF4EHAW.Function.png" alt="Detailed view of SAREF4EHAW Function module "/>

        <figcaption>Figure 5: Detailed view of SAREF4EHAW Function module </figcaption>

    </figure>

* Data, that has both data constraints (such as validity or legal constraints) and measurement (single or time series measurements) that are measured in a given unit of measure, as depicted in Figure 5 (_DataConstraint, Observation_ and _TimeSeriesObservation classes_).

* The _TimeSeriesObservation_ is inspired on existing classes from other standards in the health domain (listed in Table 6). This class represents a sequence of data in a successive equally spaced points in time (i.e. with a fixed frequency) measured by a health device, e.g. ECG time series data measured by an ECG device during a recording session. 

<table id="Table_6" data-docx-preferred-width="4.74cm 4.25cm 8.12cm">

<table data-docx-preferred-width="4.74cm 4.25cm 8.12cm">

  <caption>Table 6: Classes representing Time Series from other data models</caption>

  <tr>

    <th>Class</th>

The object properties defined for SAREF4EHAW Function module are described in Table 7 The data properties defined for SAREF4EHAW Function module are described in Table 8.

<table id="Table_7" data-docx-preferred-width="4.69cm 3.75cm 4.00cm 4.94cm">

<table data-docx-preferred-width="4.69cm 3.75cm 4.00cm 4.94cm">

  <caption>Table 7: List of object properties of SAREF4EHAW Function module</caption>

  <tr>

    <th>Object property</th>

<table id="Table_8" data-docx-preferred-width="3.94cm 4.25cm 3.25cm 6.00cm">

<table data-docx-preferred-width="3.94cm 4.25cm 3.25cm 6.00cm">

  <caption>Table 8: List of data properties of SAREF4EHAW Function module</caption>

  <tr>

    <th>Data Property</th>

* Dr. Knock is created as a `s4ehaw:Caregiver` that has Bob as patient (`s4ehaw:hasPatient` property).

* SpireStone and ScanWatch wearables, as well as TUCKY thermometer, are health devices (`s4ehaw:HealthDevice`) that are attached to Bob (`s4ehaw:isAttachedTo` property).

<figure id="Figure_6">

<figure>

        <img data-docx-width="16.32cm" src="diagrams/SAREF4EHAW_examples.Patient_Bob.png" alt="Patient Bob individuals "/>

        <figcaption>Figure 6: Patient Bob individuals </figcaption>

    </figure>

Figure 7 depicts the SpireStone wearable device (a `s4ehaw:HealthDevice`) of Bob (a `s4ehaw:Patient`), as described using SAREF4EHAW extension.

<figure id="Figure_7">

<figure>

        <img data-docx-width="17.00cm" src="diagrams/SAREF4EHAW_examples.BobSpireStone_HealthDevice.png" alt="BobSpireStone HealthDevice individuals "/>

        <figcaption>Figure 7: BobSpireStone HealthDevice individuals </figcaption>

    </figure>

Each of `BobSpireHealth` sensors has a certain function (`saref:hasFunction` property), as depicted in Figure 8. For example, the `BobSpireBreathSens` sensor has a respiration measurement function (a `s4ehaw:MeasurementFunction`), called `Respiration` and described in Figure 8.

<figure id="Figure_8">

<figure>

        <img data-docx-width="15.93cm" src="diagrams/SAREF4EHAW_examples.Respiration_function.png" alt="Respiration function individuals "/>

        <figcaption>Figure 8: Respiration function individuals </figcaption>

    </figure>

Figure 9 depicts the ScanWatch wearable device (a `s4ehaw:HealthDevice`) of Bob (a `s4ehaw:Patient`), as described using SAREF4EHAW extension.

<figure id="Figure_9">

<figure>

        <img data-docx-width="17.00cm" src="diagrams/SAREF4EHAW_examples.BobScanWatch.png" alt="Bob's Scan Watch individuals "/>

        <figcaption>Figure 9: Bob's Scan Watch individuals </figcaption>

    </figure>

Figure 10 describes the `Oxymeter` measurement function (a `s4ehaw:ObservationFunction`): it has data (`s4ehaw:hasData` property), a SPO2 level (a `s4ehaw:Data`).

<figure id="Figure_10">

<figure>

        <img data-docx-width="15.93cm" src="diagrams/SAREF4EHAW_examples.Oxymeter_Function.png" alt="Oxymeter Function individuals "/>

        <figcaption>Figure 10: Oxymeter Function individuals </figcaption>

    </figure>

Figure 11 shows the `SystolicPressureSens` measurement function which has data (`s4ehaw:hasData` property) the `SystolicPressure` (a `s4ehaw:Data`).

<figure id="Figure_11">

<figure>

        <img data-docx-width="16.72cm" src="diagrams/SAREF4EHAW_examples.SystolicPressureSens.png" alt="Systolic Pressure function Individuals "/>

        <figcaption>Figure 11: Systolic Pressure function Individuals </figcaption>

    </figure>

Figure 12 describes the third device which is the TUCKY Thermometer (a `s4ehaw:HealthDevice`) of Bob (a `s4ehaw:Patient`) called `BobBodyThermo`. It is a sensor patch which function is to measure accurately the body temperature in degree Celsius.

<figure id="Figure_12">

<figure>

        <img data-docx-width="17.00cm" src="diagrams/SAREF4EHAW_examples.BobBodyThermo.png" alt="Bob's Thermometer Health device individuals"/>

        <figcaption>Figure 12: Bob's Thermometer Health device individuals</figcaption>

    </figure>

Figure 13 describes the `BodyThermometer` observation function (a `s4ehaw:ObservationFunction`).

<figure id="Figure_13">

<figure>

        <img data-docx-width="16.72cm" src="diagrams/SAREF4EHAW_examples.BodyTemperature.png" alt="Body's temperature function individuals "/>

        <figcaption>Figure 13: Body's temperature function individuals </figcaption>

    </figure>

Figure 14 describes `BobMonitorBan`, the BAN (a `s4ehaw:Ban`) that Bob (a `s4ehaw:Patient`) uses (`s4ehaw:usesBan` property) for vital parameters monitoring purposes.` 

<figure id="Figure_14">

<figure>

        <img data-docx-width="17.00cm" src="diagrams/SAREF4EHAW_examples.BobMonitorBan.png" alt="Bob's BAN individuals "/>

        <figcaption>Figure 14: Bob's BAN individuals </figcaption>

    </figure>

Figure 15 illustrates the composition of the ECG device (a `s4ehaw:HealthDevice`) of this example. The ECG device ECG_unit_T9JRN42 is an `s4ehaw:HealthDevice` that is composed of 4 leads (`ECGLead_I_`, `ECGLead_II_`, `ECGLead_III_` and `ECGLead_Vx_RL`) and three accelerometer sensors (X, Y and Z). The acceleration data can be used by the EWS to detect collisions (e.g. car accidents) and correlate with the ECG data for detecting heart damages. The ECG device plays the role of a recorder in the complex event (action) of a `s4ehaw:ObservationCollectionSession` (the ECG recording session `s4ehawInst:RecordingECGSession_01`). In SAREF, this complex action can be classified as a `saref:Task` that an ECG device `saref:accomplishes`. 

<figure id="Figure_15">

<figure>

        <img data-docx-width="17.00cm" src="diagrams/SAREF4EHAW_examples.ECGunit.png" alt="Composition of ECG device with a recording measurement session "/>

        <figcaption>Figure 15: Composition of ECG device with a recording measurement session </figcaption>

    </figure>

The `saref:hasValue` property limits the value domain of a `Observation` to exactly one number. The `s4ehaw:hasValues` property was added to overcome this issue, in which a `s4ehaw:TimeSeriesObservation` can instantiate this property multiple times as an ordered (depending on the serialization format) array of numbers. The size of this array should reflect the frequency of the time series measurement and, if not, it shows a possible issue on missing measurements in the Bluetooth communication between the ECG device and the mobile application. 

<figure id="Figure_16">

<figure>

        <img data-docx-width="17.00cm" src="diagrams/SAREF4EHAW_examples.EGCTimeSeries.png" alt="An ECG time series measurement "/>

        <figcaption>Figure 16: An ECG time series measurement </figcaption>

    </figure>

### Normative references

# References

## Normative references

* <a id="[0]">[0]</a> [ETSI TS 103 410-8 (V2.1.1)](https://www.etsi.org/deliver/etsi_ts/103400_103499/10341008/02.01.01_60/ts_10341008v020101p.pdf): "SmartM2M;; Extension to SAREF; Part 8: eHealth/Ageing-well Domain".

* <a id="[1]">[1]</a>	[ETSI TS 103 264](https://www.etsi.org/deliver/etsi_ts/103200_103299/103264/): "SmartM2M; Smart Applications; Reference Ontology and oneM2M Mapping".

* <a id="[4]">[4]</a>	[ETSI TS 103 410-9 (V1.1.1) (2020-07)](https://www.etsi.org/deliver/etsi_ts/103400_103499/10341009/01.01.01_60/ts_10341009v010101p.pdf): "SmartM2M; Extension to SAREF; Part 9: Wearables Domain".

### Informative references

## Informative references

* <a id="[i.1]">[i.1]</a>	W3C<sup>®</sup> Recommendation 19 October 2017:"[Semantic sensor network ontology](https://www.w3.org/TR/vocab-ssn/)", OGC<sup>®</sup> and W3C<sup>®</sup> Spatial Data on the Web working Group.

* <a id="[i.2]">[i.2]</a>	B. Gonçalves, G. Guizzardi, J. G.Pereira Filho: "Using an ECG reference ontology for semantic interoperability of ECG data", Journal of Biomedical Informatics, vol. 44, issue 1, pp. 126-136, February 2011.

* <a id="[i.3]">[i.3]</a>	[HL7 FHIR<sup>®](http://www.hl7.org/)</sup>: "Fast Healthcare Interoperability Resources".

!!! alert-info "NOTE:"

!!! alert alert-info "NOTE:"

    FHIR<sup>®</sup> is an example of an existing eHealth standard. This information is given for the convenience of users of the present document and does not constitute an endorsement by ETSI of this standard.

* <a id="[i.4]">[i.4]</a>	S. Cox: "[Observations and measurements-xml implementation](https://www.ogc.org/standard/om/)" OGC document, 2011 (also published as ISO/DIS 19156).

* <a id="[i.5]">[i.5]</a>	[HL7 annotated ECG (aECG) R1 and R2 (US realm)](https://www.hl7.org/implement/standards/product_brief.cfm?product_id=102): "Implementation Guide: Annotated ECG (aECG) R1, Release 2 - US Realm".

* <a id="[i.6]">[i.6]</a>	[Digital Imaging and Communications in Medicine (DICOM<sup>®</sup>) international standard](https://www.dicomstandard.org/).

!!! alert-info "NOTE:"

!!! alert alert-info "NOTE:"

    DICOM<sup>®</sup> is an example of an existing eHealth standard. This information is given for the convenience of users of the present document and does not constitute an endorsement by ETSI of this standard.

* <a id="[i.7]">[i.7]</a>	ETSI TR 103 509: "SmartM2M; SAREF extension investigation; Requirements for eHealth/Ageing-well".