SAREF4EHAW: an extension of SAREF for eHealth Ageing Well domain

Latest version
https://saref.etsi.org/saref4ehaw/
Permanent IRI for this version (v2.1.1)
https://saref.etsi.org/saref4ehaw/v2.1.1/
Previous version
https://saref.etsi.org/saref4ehaw/v1.1.1/
ETSI Technical Specification:
https://www.etsi.org/deliver/etsi_ts/103400_103499/10341008/02.01.01_60/ts_10341008v020101p.pdf
Sources on the ETSI Forge
https://saref.etsi.org/sources/saref4ehaw/
Publication Date
2025-04-25
Last Modification Date
2025-04-25
Creators
Contributors
Ontology requirements and tests
requirements and tests
Imports ontologies
Examples
Prefix and namespace declaration
Turtle: @prefix s4ehaw: <https://saref.etsi.org/saref4ehaw/> .
SPARQL: PREFIX s4ehaw: <https://saref.etsi.org/saref4ehaw/>
Download serialization
License
Browse ontology
NOTE: The text in this section is extracted from ETSI TS 103 410-8 (V2.1.1) [0], and therefore falls inside the ETSI IPR Policy

SAREF4EHAW ontology and semantics

Introduction and overview

The objective of SAREF4EHAW is to extend SAREF ontology (see ETSI TS 103 264 [1]) for the eHealth/Ageing-well (EHAW) vertical. Clause 4.1 of the present document 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], 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.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], 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]), 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.

High level view of the envisioned semantic model for SAREF4EHAW ontology
Figure 1: High level view of the envisioned semantic model for SAREF4EHAW ontology

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

  • EHAW system actors (HealthActor class depicted in 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) may have one or multiple patients. A helper (Helper class depicted in Figure 1) may follow one or multiple users and or patients. As also shown in 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 a possible States of each actor.
  • Health devices (HealthDevice class depicted in 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), Health-dedicated sensors (HealthSensor class depicted in Figure 1), Health-dedicated actuators (HealthActuator class depicted in Figure 1) and Health-dedicated wearables (HealthWearable class depicted in Figure 1). Those health devices have a given function (Function class depicted in Figure 1) aiming to support to accomplish their tasks. Function can act upon features, properties, or states. An instance of saref: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.
  • An actuator is used for an actuation process and does action materialized via the Command class as depicted in 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 present document since they are already fully specified and formalized in ETSI TS 103 410-9 [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).
  • BAN (Ban class depicted in 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.
  • Observation collection session (ObservationCollectionSession class depicted in Figure 1) that logically has health actors (at least a caregiver and/or a patient/user) as participants (see 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).

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]) 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 present document. The prefixes and namespaces used in SAREF4EHAW and in the present document are listed in Table 1.

Prefix Namespace
dct http://purl.org/dc/terms/
foaf http://xmlns.com/foaf/0.1/
owl http://www.w3.org/2002/07/owl#
rdf http://www.w3.org/1999/02/22-rdf-syntax-ns#
rdfs http://www.w3.org/2000/01/rdf-schema#
s4ehaw https://saref.etsi.org/saref4ehaw/
s4syst https://saref.etsi.org/saref4syst/
s4wear https://saref.etsi.org/saref4wear/
saref https://saref.etsi.org/core/
skos http://www.w3.org/2004/02/skos/core#
vann http://purl.org/vocab/vann/
voaf http://purl.org/vocommons/voaf#
xsd http://www.w3.org/2001/XMLSchema#
Table 1: Namespace Declarations

SAREF4EHAW

Introduction

As already introduced in clause 4.1 of the present document SAREF4EHAW is an OWL-DL ontology and shall be designed using the modularity principle (see ETSI TR 103 509 [i.7]) and can thus be mainly described by the following self-contained knowledge modules:

  • HealthActor module that models eHealth system actors, i.e. caregivers, patients, users, helpers and responsibility parties (see Figure 1). It is fully specified and formalized in clause 4.2.1 of the present document.
  • Ban module that models Body Area Networks or BANs (see Figure 1). It is fully specified and formalized in clause 4.2.2 of the present document.
  • HealthDevice module that models health devices, e.g. sensors and actuators (see Figure 1). It is fully specified and formalized in clause 4.2.3 of the present document.
  • FunctionalDevice module that models functional devices (see Figure 1). Those devices are non-purely eHealth/ageing-well devices that can be used for modelling/detecting activities or behaviours of patients/users, like for example beacons that can detect indoor positioning of a patient in a house. It is fully specified and formalized in clause 4.2.4 of the present document.
  • Function module that models observation and actuation functions (via the Command class), as well as observations (see Figure 1). It is fully specified and formalized in clause 4.2.5 of the present document.

HealthActor module

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

Detailed view of SAREF4EHAW HealthActor module
Figure 2: Detailed view of SAREF4EHAW HealthActor module

SAREF4EHAW HealthActor module models the eHealth system actors, i.e. responsible parties (the legal entity responsible for a Body Area Network - BAN -), caregivers, patients, users and helpers (see Figure 2). A health actor also uses a BAN for complex monitoring purposes.

Caregiver, Patient, User, Helper and ResponsibleParty are all sub-classes of HealthActor (rdfs:subClassOf relation). Patient and User may have in particular:

  • One or multiple activities (Activity class depicted in Figure 2), characterized by a kind (e.g. sleeping in bed, sitting on a chair, using the shower, etc.) and a duration (in second).
  • Habits (Habit class depicted in Figure 2), modeled as a State, that should mainly have for value one of the following SAREF4EHAW individuals (non-exhaustive): Smoking, AlcoholDrinking, Overeating, Undereating.
  • Postures (Posture individual depicted in Figure 2), modeled as a State, that should mainly have for value one of the following SAREF4EHAW individuals (non-exhaustive): Lying, Sitting, Walking, Exercising, Running.
  • Impairments (Impairment class depicted in Figure 2), modeled as a State, that should mainly have for value one of the following SAREF4EHAW individuals (non-exhaustive): AuralImpairement, SkeletalImpairment, OcularImpairement, MobilityImpairment, IntellectualImpairement. Those impairments (non exhaustive) are compatible with the World Health Organization (WHO) classification (see https://apps.who.int/iris/bitstream/handle/10665/41003/9241541261_eng.pdf;jsessionid=6AB8BF561C227503A5B55496EB606C36?sequence=1) [i.11].
  • Chronic Disease (ChronicDisease individual depicted in Figure 2; instantiating the SAREF State class_)_ that should mainly be the broader of SAREF4EHAW individuals (non-exhaustive): Diabetes, Asthma.

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 2: List of object properties of SAREF4EHAW HealthActor module
Object property Domain Range Definition
s4ehaw:followsUser s4ehaw:Helper s4ehaw:User A helper may follow one or multiple users that can in particular be patients.
s4ehaw:hasActivity s4ehaw:HealthActor s4ehaw:Activity A health actor may have one or multiple activities.
s4ehaw:hasHabit s4ehaw:User s4ehaw:Habit The habits of a user and a patient (as sub-class of user it also inherits habit), e.g. smoking or overeating.
s4ehaw:hasImpairment s4ehaw:User s4ehaw:Impairment The impairment type of a user and a patient (as sub-class of user it also inherits impairment), e.g. aural, skeletal, ocular, mobility, intellectual, etc.
s4ehaw:usesBan s4ehaw:HealthActor s4ehaw:Ban A health actor (e.g. a caregiver, a patient or a helper) uses a BAN for collecting, aggregating and relaying vital parameters.

Ban module

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

Detailed view of SAREF4EHAW Ban module
Figure 3: Detailed view of SAREF4EHAW Ban module

A BAN (Ban class depicted in Figure 3) is mainly used for collecting, aggregating and relaying patient or user vital parameters, thus for complex monitoring purposes. It therefore contains health devices, and has a hub (playing both the BAN network gateway and the data concentrator roles) as depicted in Figure 3. A BAN enables the execution of tasks (class Task depicted in Figure 3) modeled as the following SAREF4EHAW individuals: Healthcare, Telemedicine, AssistedLiving, SportTraining, PervasiveComputing, Safety, Emergency.

As shown in Figure 3, a BAN has:

  • Responsible party that plays the role of the legal entity responsible for a BAN. ResponsibleParty class, already detailed in clause 4.2.1 of the present document, is thus not detailed again in clause 4.2.3 of the present document.
  • BAN communication function (class BANCommunicationFunction depicted in Figure 3) that is either periodic, event driven or on demand, as depicted in Figure 3.

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 3: List of object properties of SAREF4EHAW Ban module
Object property Domain Range Definition
s4ehaw:hasHub s4ehaw:Ban s4ehaw:Hub A Body Area Network or BAN has one hub mainly playing the role of both a data concentrator and a network gateway.
s4ehaw:hasResponsibleParty s4ehaw:Ban s4ehaw:ResponsibleParty A BAN has a responsible party which plays the role of the legal entity responsible for this BAN (e.g. to contact in case of problem). It should be an organization or a person.

HealthDevice module

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

Detailed view of SAREF4EHAW HealthDevice module
Figure 4: Detailed view of SAREF4EHAW HealthDevice module

As depicted in Figure 4, an HealthDevice is a sub-class of SAREF Device class (rdfs:subClassOf relation). A HealthDevice has a given function (e.g. a heart rate observation function) and offers services (e.g. a heart rate observation service), both inherited form SAREF Device, and is also attached to a health actor (e.g. a patient and/or a caregiver).

As shown in Figure 4, a health device also has an Interface that models the data transmission and network protocol related interface of the device (e.g. serial or wireless interface, address, transmission rate, etc.). A HealthDevice also has a set of properties, like ComputingPower, characterizing it.

HealthSensor, HealthActuator, HealthWearable and BanHub classes are all sub-classes of HealthDevice class (rdfs:subClassOf relation). HealthSensor and HealthActuator classes are sub-classes of the SAREF Sensor/Actuator ones. They will therefore not be described within clause 4.2.3 of the present document in order to reduce duplication with SAREF documentation (see ETSI TS 103 264 [1] for details). HealthWearable class is a sub-class of to SAREF4WEAR Wearable class. It will therefore not be described within clause 4.2.3 of the present document in order to reduce duplication with SAREF4WEAR documentation (see ETSI TS 103 410-9 [4] for details).

Finally and for reducing duplication with SAREF documentation, the reader is referred to the SAREF specification ETSI TS 103 264 [1] for details about all the classes that are reused from SAREF within Figure 4.

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 4: List of object properties of SAREF4EHAW HealthDevice module
Object property Domain Range definition
s4ehaw:hasInterface s4ehaw:HealthDevice s4ehaw:Interface A health device has one or multiple interfaces (Bluetooth®, UWB, IEEE 802.15.6 [i.10], serial interface, etc.).
s4ehaw:isAttachedTo s4ehaw:HealthDevice s4ehaw:HealthActor A health Device is attached to a health actor such as a patient, a user and or a caregiver.
Table 5: List of data properties of SAREF4EHAW HealthDevice module
Data Property Domain Range Definition
s4ehaw:availableFlash s4ehaw:HealthDevice xsd:long The available flash memory (in byte) of a health device. It is a dynamic attribute.
s4ehaw:availableRam s4ehaw:HealthDevice xsd:long Indicates the available volatile memory space (in byte) of a health device. It is a dynamic attribute.
s4ehaw:interfaceAddress s4ehaw:Interface xsd:string The interface address. The interface may have many addresses like MAC address, IP address or others.

s4ehaw:

remainingBatteryLevel

s4ehaw:HealthDevice xsd:int The level of remaining battery (if any, in percent) for a health device. It is a dynamic attribute.
s4ehaw:serialNb s4ehaw:HealthDevice xsd:string The serial number of a health device.

FunctionalDevice module

FunctionalDevice are non-purely eHealth/ageing-well devices that can be used for modelling/detecting activities or behaviours of patients/users, like for example beacons that can detect indoor positioning of a patient in a house.

A functional device is a sub-class of SAREF Device class (rdfs:subClassOf relation) and shall thus have exactly the same object and data properties. Therefore and for reducing duplication with SAREF documentation, It will not be detailed in clause 4.2.5 of the present document and the reader is referred to the SAREF specification (ETSI TS 103 264 [1]).

Function module

A detailed view of SAREF4EHAW Function module is depicted in Figure 5.

Detailed view of SAREF4EHAW Function module
Figure 5: Detailed view of SAREF4EHAW Function module

SAREF4EHAW Function module models the observation and actuation functions (see Figure 5).

As shown in Figure 5, a function has:

  • Command (e.g. an actuation command or a command for getting a body temperature measurement). Alarms (class AlarmCommand) are considered as SAREF commands (rdfs:subClassOf relation) as depicted in Figure 5.
  • 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 6: Classes representing Time Series from other data models
Class Source(s) Definition
Sample sequence UFO ECG [i.2] Collective: "ordered sequence of samples resulting from an Observation series" (ecgOnto:095).
Observation series UFO ECG [i.2] Complex event: "Series of observations evenly spaced in time carried out in an ECG Recording session" (ecgOnto:093).
Sampled data (Observation.component.valueSampledData) HL7 FHIR® [i.3] "Data that come from a series of measurements taken by a device, which may have upper and lower limits".
Time Series Observation OGC O&M (ISO 19156) [i.4] "observation whose result is a time-series".
Series HL7 aECG [i.5] "Contains one or more sequence sets sharing a common frame of reference".
Series (General Series Module) DICOM® [i.6] A property of General ECG that "specifies the attributes that identify and describe general information about the Series within a Study". A Series is as a sequence of data elements sharing a common frame of reference.

Figure 5 also shows that a observation function (a sub-class of SAREF Function class, rdfs:subClassOf relation), in case of complex observations such as time series provided by ECG devices (sequences of data in a successive equally spaced points in time), shall have a frequency property that is the frequency in which the measurements are made.

Finally and for reducing duplication with both SAREF and SAREF4ENVI documentation, the reader is referred to the SAREF and SAREF4ENVI specifications (ETSI TS 103 264 [1], ETSI TS 103 410-2 [3]) for details about all the classes that are reused from SAREF within Figure 5.

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 7: List of object properties of SAREF4EHAW Function module
Object property Domain Range definition
saref:hasCommand saref:Function saref:Command A function has a command (a directive that a health device is supporting to perform a given function).
s4ehaw:hasDataConstraint s4ehaw:Data s4ehaw:DataConstraint Defines the relationship between a data that has constraints (validity, legal, etc.).
s4ehaw:hasData saref:Function s4ehaw:Data A function has one or many data, for example a tracking function shall include latitude, longitude and speed data.
s4ehaw:hasParticipant

s4ehaw:

MeasurementSession

s4ehaw:HealthActor A measurement session has health actors as participants (caregiver controlling the session, patient monitored during the session).

s4ehaw:

hasTimeSeriesMeasurement

s4ehaw:Data

s4ehaw:

TimeSeriesMeasurement

Data has time series measurements, a sequence taken at successive equally spaced points in time.
Table 8: List of data properties of SAREF4EHAW Function module
Data Property Domain Range Definition
s4ehaw:hasValues

s4ehaw:

TimeSeriesMeasurement

xsd:decimal A relationship defining the set of values (an ordered array of numbers) of a certain property, e.g. heart rate. Attention: to assure ordering in the serialization format, it is necessary to use either rdf:Seq (RDF/XML) or @list (JSON-LD).
s4ehaw:maximumValue s4ehaw:ValidityConstraint xsd:decimal The maximum allowable value of a measurement.
s4ehaw:minimumValue s4ehaw:ValidityConstraint xsd:decimal The minimum allowable value of a measurement.

Instantiating SAREF4EHAW

Monitoring and support of healthy lifestyles for citizens, in the context of Covid-19

This use case is about a patient of around 50 years old, Bob, with overeating habit. In the context of Covid-19, Bob as a risky patient is thus remotely followed/monitored/controlled by a caregiver, Dr. Knock, for Covid-19 signs detection purposes. Our patient is equipped with a BAN with an android smartphone as the BAN hub, as well as three COVID-19 related devices (wearables, sensors). Bob is equipped with SpireStone wearable device for breathing rate monitoring, a ScanWatch wearable for monitoring the SPO2 level and a TUCKY thermometer for the body temperature monitoring. Thus, using SAREF4EHAW ontology and has depicted in Figure 6:

  • Bob is created as a s4ehaw:Patient that uses (s4ehaw:usesBan property) Bob monitoring BAN (a s4ehaw:Ban).
  • Bob has a habit (a s4ehaw:Habit) of Overeating (s4ehaw:hasHabit property).
  • 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).
Patient Bob individuals
Figure 6: Patient Bob individuals

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

BobSpireStone HealthDevice individuals
Figure 7: BobSpireStone HealthDevice individuals

As depicted in Figure 7, Bob SpireStone wearable, called BobSpireHealth, consists of three embedded sensors (saref:consistsOf property) that are health devices (s4ehaw:HealthDevice): an accelerometer (BobSpireAccelero), a vibration monitor (BobSpireVbro) and a breath rate sensor (BobSpireBreathSens). In the case presented in clause 4.3.1 of the present document, the Respiration function of this device will only be described as it measures the respiratory rate in bpm which is one of the key COVID-19 indicators to monitor. Figure 8 also shows that the SpireStone wearable (BobSpireHealth) is connected through the Bob monitoring BAN (s4syst:connectedThrough property) and is also attached to Bob (s4ehaw:isAttachedTo property).

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.

Respiration function individuals
Figure 8: Respiration function individuals

Figure 8 shows that Respiration observation function has data (s4ehaw:hasData property), a respiratory rate (a s4ehaw:Data.

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

Bob's Scan Watch individuals
Figure 9: Bob's Scan Watch individuals

As depicted in Figure 9, Bob is using the Withings_ScanWatch wearable (a s4ehaw:HealthDevice) that consists of many embedded sensors (saref:consistsOf property): an altimeter, a combined SPO2/heart rate sensor, and three electrodes for ECG. In the case of COVID-19 prevention, SPO2 level and heart rate can be described. This Scan watch has two functions (saref:hasFunction): an oxymeter measurement and a systolic pressure measurement.

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

Oxymeter Function individuals
Figure 10: Oxymeter Function individuals

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

Systolic Pressure function Individuals
Figure 11: Systolic Pressure function Individuals

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.

Bob's Thermometer Health device individuals
Figure 12: Bob's Thermometer Health device individuals

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

Body's temperature function individuals
Figure 13: Body's temperature function individuals

As depicted in Figure 13, the BodyThermometer observation function has data (s4ehaw:hasData property).

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

Bob's BAN individuals
Figure 14: Bob's BAN individuals

Since Bob is using three s4ehaw:HealthDevice, these health devices should be part of Bob's BAN. Therefore and as shown in Figure 14, BobMonitorBan connects (s4syst:connectsSystem property) the tree aforementioned health devices: BobSpireHealth, BobScanWatch, and BobBodyThermometer (all s4ehaw:HealthDevice). As also shown in Figure 14, BobMonitorBan has a hub (s4ehaw:hasHub property), which plays the role of the data aggregator/collector and gateway of the BAN. This hub (a s4ehaw:BanHub) is called BobAndroidPhone (see Figure 14).

This scenario supports a set of rules, as described below.

As general rule, the doctor who is monitoring a patient should be inferred as using the ban used by this patient.

As COVID-19 early detection rules, the first scenario consists of early detection of suspected COVID-19 symptoms. When the body temperature rises above 37,5 degrees Celsius and the breathing rate exceeds 22 breaths/min a warning is sent to the BAN hub, in our case s4ehawInst:BobAndroidPhone.

The second scenario consists of another, more severe symptom of COVID-19. When the breathing rate rises above 22 breaths/min, the ambient SPO2 level is below 90 %, and the systolic pressure < 90 % an immediate alert is sent for hospitalisation of the patient.

In these two cases, if the caregiver/doctor confirms that this user has COVID-19, the user is automatically inferred as patient that has (s4ehaw:hasChronicDisease property) COVID-19 disease (a s4ehaw:ChronicDisease).

The third scenario focuses on detecting the users that met a COVID-19 patient. It is done by monitoring the distance maintained between Bob (or any patient) and any nearby COVID-19 patient. Thus, the distance between two nearby patients (s4ehaw:Patient) is computed using the geolocation property (s4ehaw:hasPhysicalLocation property) of these patients. Whenever this computed distance is below 1 meter, and if one of nearby patients is infected with COVID-19, an alarm is sent to the Ban Hub indicating that there is a high risk of COVID-19. The distance is computed using the latitude and longitude of the geolocation properties (s4ehaw:hasPhysicalLocation property) of patients (s4ehaw:Patient) with Haversine formula as follows:

  • R = radius of earth, 6 371 km
  • A = Sin² (Δlat/2) + Cos (lat1).Cos (lat2).Sin² (Δlong/2), angle in rad
  • C = 2.atan2(√A, √(1−A))
  • D = R.C × 1 000 is the distance in meters between the two patients (s4ehaw:Patient)

Early Warning System (EWS) for Cardiovascular Accidents

This example describes how a cardiovascular Early Warning System (EWS) instantiates SAREF4EHAW. In this use case, the EWS collects data from an e-Health solution that allows monitoring the ECG data of a person (the patient) using the device. The chosen ECG solution for this example includes the Shimmer3 ECG, which is an ECG unit (device), a mobile application responsible for receiving high-frequency data (e.g. 256 Hz) via Bluetooth from the ECG device and sending the aggregated data to a service deployed in a cloud vendor. Therefore, the mobile app aggregates the ECG data and sends the aggregated data to an cloud IoT Hub (a publish/subscribe cloud gateway), allowing a service in the cloud to detect and warn possible emergency situations with the patient based on ECG time series and acceleration data.

An ECG Device registers the Heart Electrical Activity through electrodes attached to different places of the body, under the assumption that the heart is beating inside the body of a living person. Two electrodes enable an ECG lead to be measured, which is an electrical vector characterized by the depolarization of the heart resulted by the electrical signal between the atria and the ventricles. Manufacturers commonly characterize an ECG device by its number of ECG leads. An ECG device is composed by extremity electrodes, which are attached close to the Left Arm (LA), Right Arm (RA), Left Leg (LL) and the Right Leg (RL); and the chest (precordial), varying from one to six units (V1-6). By convention, lead I measures the electrical activity from the electrodes RA to LA, lead II measures of the electrical activity from RA to LL, lead III measures the electrical activity from LA to LL. The rule lead I + lead III = lead II makes it possible to derive a lead based on the other two. Lead I, Lead II and Lead III are known as Bipolar Limb. Unipolar leads measure the electrical activity from the Wilson's central terminal (negative pole) to each of the chest electrodes (positive poles). For example, the Shimmer3 ECG is a four-lead ECG device wired with four extremity electrodes and one chest electrode, enabling the measurement of three bipolar and one unipolar lead.

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.

Composition of ECG device with a recording measurement session
Figure 15: Composition of ECG device with a recording measurement session

The frequency of an ECG device can be set through an API, which becomes the frequency of each ECG Sample Sequence measured during a recording session (a s4ehaw:ObservationCollectionSession).

The term s4ehaw:TimeSeriesObservation refers to a time series of a sequence of measurements made by a device, in line with the terminology often used in the measurement science (metrology). This term can be applied to several types of measurements, such as ECG time series. As illustrated in Figure 16, the ECGseries_Example002 is a s4ehaw:TimeSeriesObservation that is measured in ElectricPotential units (an array) and relates to the HeartElectricalActivity property. s4ehaw:TimeSeriesObservation is classified as saref:Observation in SAREF for two reasons:

i) this representation adheres to the definition of Observation, i.e. measured value (Electric Potential units) of a property (HeartElectricalActivity);

ii) reuse of SAREF structure regarding class axioms of object properties, e.g. saref:hasTimestamp, and saref:isMeasuredIn.

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.

An ECG time series measurement
Figure 16: An ECG time series measurement

Discussion

In the following, several observations about the SAREF4EHAW ontology and its usage are mentioned.

The hierarchies and individuals defined for SAREF4EHAW extension in the present document should not be considered as exhaustive. It might be needed to extend the hierarchies and lists of individuals for particular use cases, as well as to specialize some of the defined classes. Furthermore, SAREF4EHAW is a dynamic semantic model that can thus evolve over the time. Therefore, eHealth/Ageing Well domain stakeholders are invited to use and validate SAREF4EHAW extension, as well as to give feedback on it and to collaborate with SAREF experts so that amendments and improvements can be incorporated in future releases of the present document.

Regarding s4ehaw:TimeSeriesObservation and its values property (s4ehaw:hasValues), it shall be highlighted that this approach has a formalization issue regarding the ordering of the values. Although the RDF language syntax provides the rdf:Seq element for ordered lists, ordering of triples may be an issue for OWL2 DL reasoners. Some serialization formats dealing with this issue, e.g. RDF/XML and JSON-LD (via @list), was taken into account. Particularly, JSON-LD is recommended for the serialization since it addresses some data exchange needs of modern e-Health solutions that rely on IoT technologies, such as dealing with the verbosity issue of messages. Verbosity relies on message size (payload), which is one of the most common non-functional requirement affecting performance and costs of IoT solutions. JSON-LD is one of the most recommended type of serialization for "semantic IoT" solutions and the other types of serializations (e.g. XML and TTL) are more verbose for ordered data.

Finally, a last attention point is related to the possibility that this extension will overlap with existing key initiatives and standards partially related to eHealth/Ageing Well, in particular:

  • SAREF4WEAR, extension of SAREF for the Wearable domain. During STF 566 phase of specification and design of SAREF extensions, special attention was drawn to avoid overlapping in particular between SAREF4EHAW and SAREF4WEAR. However, further alignments may be required.
  • HL7 Fast Healthcare Interoperability Resources (FHIR®) [i.3]. FHIR® is intended for providing reasoning and decision making supports about healthcare processes and clinical systems, which means that it is more at the organizational level while SAREF4EHAW ontology is more at the engineering level (i.e. one layer below FHIR®). In that sense, SAREF4EHAW ontology is rather complementary with FHIR®. However, further mapping and alignments may be required and could also be investigated.
  • HL7 annotated ECG (aECG) [i.5] standard is a medical record data format for storing and retrieving electrocardiogram (ECG), chosen by the US Food and Drug Administration (FDA) for clinical trials, implemented as a lexicon approach, i.e. using XML schemas, running nowadays in several hospital information systems.
  • Digital Imaging and Communications in Medicine (DICOM®) [i.6] is the international standard to transmit, store, retrieve, print, process, and display medical imaging information. It is one of the most used standards in e-Health solutions, being a lexicon approach that makes medical imaging information interoperable.
  • OGC Observations and Measurements (O&M) [i.4] is one of the core standards in the OGC Sensor Web Enablement (SWE) suite standard and defines a conceptual schema encoding for observations, and for features involved in sampling when making observations, adhering to ISO 19156 [i.4]. The model is derived from generic patterns and is not limited to spatial information.
  • Unified Foundational Ontology ECG (UFO ECG) [i.2] is a well-founded ECG ontology designed through an ontological analysis of existing health standards based on the ontology-driven conceptual modelling approach with the Unified Foundational Ontology. The main goal of UFO ECG is to serve as a reference "unified Electronic Health Record (EHR) model", providing mappings to the most common standards that support the representation of ECG data.
  • ACTIVAGE Data Model. ACTIVAGE LSP (see http://www.activageproject.eu) is a European Large Scale Pilot (9 deployment sites in seven European countries) on Smart Living Environments that in particular specified and designed a dedicated data model for such environments. Therefore, it might be required to investigate possible alignments and/or mappings between SAREF4EHAW ontology and ACTIVAGE Data Model. Contact has already been established between ACTIVAGE LSP representatives and SAREF4EHAW ontology designers for that purpose.

Ontology Reference

s4ehaw:Activity — Activity top Classes ToC

The activity of a patient/user, i.e. daily and nocturnal activities.

s4ehaw:Ban — BAN top Classes ToC

s4ehaw:BanApplicationTask — BAN application tasks top Classes ToC

BAN application tasks, suchas healthcare, telemedicine, assisted living, sport training, safety and emergency...

s4ehaw:BanHub — BAN hub top Classes ToC

Hub of the BAN, mainly playing the role of both a data concentrator and a network gateway.

has super-classes
s4ehaw:HealthDevice
is in range of
s4ehaw:hasHub

s4ehaw:Caregiver — Caregiver top Classes ToC

The class of caregivers.

has super-classes
s4ehaw:HealthActor
is in domain of
s4ehaw:hasPatient

s4ehaw:CommunicationInterface — Communication Interface top Classes ToC

A communication interface of a device to a communication network.

s4ehaw:CommunicationNetwork — Communication Network top Classes ToC

A communication network.

has super-classes
saref:FeatureOfInterest
s4syst:Connection
is in domain of
s4ehaw:hasGateway

s4ehaw:CommunicationProtocol — Communication protocol top Classes ToC

A communication protocol, e.g. BLE, serial, Ethernet...

s4ehaw:DailyActivity — Daily activity top Classes ToC

The patient/user activities that occur during daytime.

has super-classes
s4ehaw:Activity

s4ehaw:FunctionalDevice — Functional device top Classes ToC

Functional Devices are non-purely eHealth/ageing-well devices that can be used for modelling/detecting activities or behaviours of patients/users, like for example beacons that can detect indoor positioning of a patient in a house.

has super-classes
saref:Device

s4ehaw:HealthActor — Health actor top Classes ToC

s4ehaw:HealthActuator — Health actuator top Classes ToC

Health-related Actuator, sub-class of SAREF Actuator.

s4ehaw:HealthDevice — Health Device top Classes ToC

Health devices, e.g. BAN hub, health sensor/actuator/Wereable.

s4ehaw:HealthSensor — Health sensor top Classes ToC

Health-related Sensor, sub-class of SAREF Sensor.

has super-classes
saref:Sensor
s4ehaw:HealthDevice

s4ehaw:HealthWearable — Health wereable top Classes ToC

Health-related Wearable, sub-class of SAREF4WEAR Wearable.

s4ehaw:Helper — Helper top Classes ToC

Helper of patients/users, e.g. a patient's relative.

has super-classes
s4ehaw:HealthActor
is in domain of
s4ehaw:followsUser

s4ehaw:NocturnalActivity — Nocturnal activity top Classes ToC

The patient/user activities that occur during the night.

has super-classes
s4ehaw:Activity

s4ehaw:ObservationCollectionExecution — Observation Collection Execution top Classes ToC

Execution consisting in collecting observations made by Device (e.g. Sensor, Wearable, ECG Device...). Use saref:madeBy to link to the person or the Device that made it. Use saref:observes to link to the patient. Use saref:hasResult to link to the result, an ObservationCollection

has super-classes
saref:ProcedureExecution

s4ehaw:Patient — Patient top Classes ToC

A user of the type patient, i.e. a cared-for person by one or multiple caregivers.

has super-classes
s4ehaw:User
is in range of
s4ehaw:hasPatient

s4ehaw:ResponsibleParty — Responsible party top Classes ToC

The legal entity responsible for a BAN, i.e. to contact in case of problem.

has super-classes
s4ehaw:HealthActor
is in range of
s4ehaw:hasResponsibleParty

s4ehaw:User — User top Classes ToC

A health actor (patient included) that can be equiped with BANs or health devices for monitoring, control, care (specific case of patients) or support purposes.

has super-classes
s4ehaw:HealthActor
has sub-classes
s4ehaw:Patient
is in range of
s4ehaw:followsUser

s4ehaw:followsUser — follows user top Object Properties ToC

A helper may follow one or multiple users that can in particular be patients.

has domain
s4ehaw:Helper
has range
s4ehaw:User

s4ehaw:hasActivity — has activity top Object Properties ToC

A health actor may have one or multiple activities.

has domain
s4ehaw:HealthActor
has range
s4ehaw:Activity

s4ehaw:hasContact — has contact top Object Properties ToC

A BAN has one or multiple contacts (e.g. the patient or user that is monitored through this BAN, the caregiver that is using this BAN for monitoring purposes).

has domain
s4ehaw:Ban
has range
s4ehaw:HealthActor

s4ehaw:hasEffect — has effect top Object Properties ToC

Links a command or operation to the effect of invoking it. Can be an alert, nothing, an activation of another process...

s4ehaw:hasGateway — has gateway top Object Properties ToC

Links a communication network to its gateway, the communication interface of a device.

s4ehaw:hasHub — has hub top Object Properties ToC

A Body Area Network or BAN elects one hub that mainly plays the role of both a data concentrator and a network gateway.

has super-properties
s4syst:connectsSystem
has domain
s4ehaw:Ban
has range
s4ehaw:BanHub

s4ehaw:hasPatient — has patient top Object Properties ToC

A caregiver may have one or multiple patients.

has domain
s4ehaw:Caregiver
has range
s4ehaw:Patient

s4ehaw:hasPrecondition — has precondition top Object Properties ToC

Links a command or operation to the conditions that are imposed over its inputs to be successufully invoked.

s4ehaw:hasResponsibleParty — has responsible party top Object Properties ToC

A BAN that has a responsible party which plays the role of the legal entity responsible for this BAN (e.g. to contact in case of problem). It should be an organization or a person.

has domain
s4ehaw:Ban
has range
s4ehaw:ResponsibleParty

s4ehaw:isAttachedTo — is attached to top Object Properties ToC

A health Device is attached to a health actor such as a patient, a user and or a caregiver.

s4ehaw:isExposedOn — is exposed on top Object Properties ToC

Links a service to a Connection/FeatureKind (such as ex:Bluetooth), to a Connection/FeatureOfInterest (such as ), to a ConnectionPoint/FeatureKind (such as ex:TCPPort), to a ConnectionPoint/FeatureOfInterest (such as ).

s4ehaw:usesBan — uses ban top Object Properties ToC

A health actor (e.g. a caregiver, a patient or a helper) uses a BAN for collecting, aggregating and relaying vital parameters.

has domain
s4ehaw:HealthActor
has range
s4ehaw:Ban

s4ehaw:activityDuration — activity duration top Data Properties ToC

The duration of an activity, in second.

has domain
s4ehaw:Activity
has range
xsd:float

s4ehaw:dob — date of birth top Data Properties ToC

The date of birth of a health actor.

has domain
s4ehaw:HealthActor
has range
xsd:dateTime

s4ehaw:firstName — first name top Data Properties ToC

The first name of a health actor.

has domain
s4ehaw:HealthActor
has range
xsd:string

s4ehaw:hasIPv4Address — has IPv4 address top Data Properties ToC

The IPv4 address of a host.

has super-properties
saref:hasIdentifier
has domain
s4ehaw:CommunicationInterface

s4ehaw:hasMACAddress — has MAC address top Data Properties ToC

The MAC address of an interface.

has super-properties
saref:hasIdentifier
has domain
s4ehaw:CommunicationInterface

s4ehaw:hasMbox — has mbox top Data Properties ToC

An email address (or mail box) of an health actor: a URI with the 'mailto' scheme as defined by RFC 6068.

has domain
s4ehaw:HealthActor
has range
xsd:anyURI

s4ehaw:hasPortNumber — port number top Data Properties ToC

The port number used to offer the service.

has super-properties
saref:hasIdentifier
has domain
s4ehaw:CommunicationInterface

s4ehaw:lastName — last name top Data Properties ToC

The familly name of a health actor.

has domain
s4ehaw:HealthActor
has range
xsd:string

s4ehaw:phone — phone top Data Properties ToC

The phone number of a health actor, in international format.

has domain
s4ehaw:HealthActor
has range
xsd:string

s4ehaw:serialNb — serial number top Data Properties ToC

The serial number of a health device.

has domain
s4ehaw:HealthDevice
has range
xsd:string

Named Individuals

s4ehaw:AdhocBanTopology — Adhoc BAN Topology top Named Individuals ToC

Adhoc BAN topology type.

s4ehaw:AgeCategory — Age category top Named Individuals ToC

The age group of a health actor, e.g. old or young.

belongs to
saref:State

s4ehaw:Alarm_Get — Alarm Get top Named Individuals ToC

Command used for getting the alarm status.

belongs to
saref:Command

s4ehaw:Alarm_Reset — Alarm Reset top Named Individuals ToC

Command used for resetting an alarm.

belongs to
saref:Command

s4ehaw:Alarm_ResetLog — Alarm Reset Log top Named Individuals ToC

Command used for resetting the alarm log.

belongs to
saref:Command

s4ehaw:Alarm_Trigger — Alarm Trigger top Named Individuals ToC

Command used for triggering an alarm.

belongs to
saref:Command

s4ehaw:AlcoholDrinking — Alcohol drinking top Named Individuals ToC

Alcohol drinking habit (User level).

s4ehaw:ArmpitWeared — Armpit location top Named Individuals ToC

Armpit location, a user body surface location.

s4ehaw:AssistedLiving — Assisted living top Named Individuals ToC

Assisted living task for BAN application.

s4ehaw:Asthma — Asthma top Named Individuals ToC

Asthma, a chronical disease that some users can have.

s4ehaw:AuralImpairment — Aural impairment top Named Individuals ToC

Aural impairment (User level), i.e. impairments of auditory sensitivity.

s4ehaw:AvailableFlash — available flash top Named Individuals ToC

The available flash memory (in byte) of a device. It is a dynamic attribute.

belongs to
saref:Property

s4ehaw:AvailablePowerLevel — Available Power Level top Named Individuals ToC

Power level still available for the feature of interest to function.

belongs to
saref:Property

s4ehaw:AvailableRam — available ram top Named Individuals ToC

The available volatile memory space (in byte) of a device. It is a dynamic attribute.

belongs to
saref:Property

s4ehaw:BanTopology — BAN topology top Named Individuals ToC

The BAN topology type, i.e Adhoc or Star or Mesh or Others.

belongs to
saref:State

s4ehaw:BatteryPowered — BatteryPowered top Named Individuals ToC

Kind of feature of interest powered by batteries.

belongs to
saref:FeatureKind

s4ehaw:BluetoothLowEnergy — Bluetooth Low Energy top Named Individuals ToC

Bluetooth Low Energy, a communication protocol.

s4ehaw:BodySurfaceLocation — Body surface location top Named Individuals ToC

The location in terms of a body surface position (i.e. on body health device).

s4ehaw:CPUFrequency — Frequency top Named Individuals ToC

The number of instructions an embedded processor - within a device - can perform per second (MIPS).

belongs to
saref:Property

s4ehaw:ChronicDisease — Chronic disease top Named Individuals ToC

For chronic disease modelling, e.g. diabetes, asthma...

belongs to
saref:State

s4ehaw:CommunicationFunction — Communication Function top Named Individuals ToC

A device may have a communication function.

belongs to
saref:Function

s4ehaw:ComputingPower — has computing power top Named Individuals ToC

s4ehaw:Diabetes — Diabetes top Named Individuals ToC

Diabetes, a chronical disease that some users can have.

s4ehaw:Dimensions — Dimensions top Named Individuals ToC

The dimensions of a feature of interest, consisting of a length, a width, and a height.

s4ehaw:DutyCycle — Duty cycle top Named Individuals ToC

The duty cycle of an embedded processor of a device, typically in percent.

belongs to
saref:Property

s4ehaw:Emergency — Emergency top Named Individuals ToC

Emergency task for BAN application.

s4ehaw:EventDrivenCommunicationFunction — Event driven Communication Function top Named Individuals ToC

Function to communicate upon an event to report observations and receive actuations.

s4ehaw:Exercising — Exercising top Named Individuals ToC

Posture of user doing exercises.

s4ehaw:Female — Female top Named Individuals ToC

s4ehaw:Gateway — Gateway top Named Individuals ToC

Kind of devices that serve the role of a gateway.

belongs to
saref:DeviceKind

s4ehaw:Gender — has gender top Named Individuals ToC

The gender of a health actor.

belongs to
saref:State

s4ehaw:Habit — Habit top Named Individuals ToC

Defined for users (that can in particular be patients) habits modelling, e.g. smoking, alcohol drinking, overeating, undereating...

s4ehaw:Healthcare — Healthcare top Named Individuals ToC

Healthcare domain for BAN application.

s4ehaw:Height — Height top Named Individuals ToC

The height dimension of a feature of interest.

belongs to
saref:Property

s4ehaw:IEEE802-15-6 — IEEE 802.15.6 top Named Individuals ToC

IEEE 802.15.6, a communication protocol.

s4ehaw:Impairment — Impairment top Named Individuals ToC

Defined for users (that can in particular be patients) impairments modelling, e.g. aural impairment, skeletal impairment, ocular impairment, mobility impairment, intellectual impairment. Those non exhaustive impairments are compatible with the World Health Organization classification.

belongs to
saref:State

s4ehaw:ImplantLocation — Implant location top Named Individuals ToC

Implant Device (i.e. in body health device) position.

s4ehaw:IntellectualImpairment — Intellectual impairment top Named Individuals ToC

Skeletal impairment (User level), e.g. ...

s4ehaw:Length — Length top Named Individuals ToC

The length dimension of a feature of interest.

belongs to
saref:Property

s4ehaw:Location — Location top Named Individuals ToC

The location. For example a position against the body (on - body surface – or in the body – implant –) or a physical location (a postal address, a geolocation).

belongs to
saref:State

s4ehaw:LocationRelativeToBody — Location Relative to Body top Named Individuals ToC

The location relative to the body (on - body surface – or in the body – implant –).

s4ehaw:Lying — Lying top Named Individuals ToC

Posture of a lying user.

s4ehaw:MainsPowered — MainsPowered top Named Individuals ToC

Kind of feature of interest powered by the mains.

belongs to
saref:FeatureKind

s4ehaw:MaximumFlash — Maximum flash top Named Individuals ToC

The maximum flash memory space (in bytes) of a device.

belongs to
saref:Property

s4ehaw:MaximumRam — Maximum ram top Named Individuals ToC

The maximum volatile memory space (in bytes) of a device.

belongs to
saref:Property

s4ehaw:MaximumRecommended — Maximum recommended top Named Individuals ToC

The maximum recommended property value for some entity

s4ehaw:MeshBanTopology — Mesh BAN Topology top Named Individuals ToC

Mesh BAN topology type.

s4ehaw:MinimumRecommended — Minimum recommended top Named Individuals ToC

The minimum recommended property value for some entity

s4ehaw:MobilityImpairment — Mobility impairment top Named Individuals ToC

Mobility impairment (User level).

s4ehaw:NonBinary — Non-binary top Named Individuals ToC

non-binary gender

s4ehaw:NotRechargeable — Not Rechargeable top Named Individuals ToC

Kind of feature of interest whose power source is not rechargeable.

belongs to
saref:FeatureKind

s4ehaw:NumberOfPowerSource — Number Of Power Source top Named Individuals ToC

Number of power source of a feature of interest.

belongs to
saref:Property

s4ehaw:OcularImpairment — Ocular impairment top Named Individuals ToC

Ocular impairment (User level), i.e. impamnents of visual acuity.

s4ehaw:Old — Old top Named Individuals ToC

Old, one user age category.

s4ehaw:OnRequestCommunicationFunction — On request Communication Function top Named Individuals ToC

Function to communicate on request to report observations and receive actuations.

s4ehaw:Overeating — Overeating top Named Individuals ToC

Overeating habit (User level).

s4ehaw:PeriodicCommunicationFunction — Periodic Communication Function top Named Individuals ToC

Function to communicate periodically to report observations and receive actuations.

s4ehaw:PervasiveComputing — Pervasive computing top Named Individuals ToC

Pervasive computing task for BAN application.

s4ehaw:Posture — Posture top Named Individuals ToC

The posture of a health actor (mainly a patient or a user), e.g. exercising, lying, running, sitting, walking...

belongs to
saref:State

s4ehaw:Precision — Precision top Named Individuals ToC

Precision refers to the degree of reproducibility of a measured quantity (when the same quantity is measured several times how close are the measurements from each other).

belongs to
saref:Property

s4ehaw:Prevention — Prevention top Named Individuals ToC

Prevention task (e.g. preventive health) for BAN application.

s4ehaw:Rechargeable — Rechargeable top Named Individuals ToC

Kind of feature of interest whose power source is rechargeable.

belongs to
saref:FeatureKind

s4ehaw:RemainingBatteryLevel — remaining battery level top Named Individuals ToC

The level of remaining battery (if any : in percent) for a device. It is a dynamic attribute.

belongs to
saref:Property

s4ehaw:Reminder — Reminder top Named Individuals ToC

Function for sending reminder notifications.

s4ehaw:Reminder_Send — Reminder Send top Named Individuals ToC

Command used for sending a reminder.

belongs to
saref:Command

s4ehaw:Running — Running top Named Individuals ToC

Posture of a running user.

s4ehaw:Safety — Safety top Named Individuals ToC

Safety task for BAN application.

s4ehaw:SendingFrequency — Sending Frequency top Named Individuals ToC

The sending frequency of a device with a periodic communication function.

belongs to
saref:Property

s4ehaw:Sitting — Sitting top Named Individuals ToC

Posture of a sitting user.

s4ehaw:SkeletalImpairment — Skeletal impairment top Named Individuals ToC

Skeletal impairment (User level), e.g. of head and trunk regions, limbs...

s4ehaw:Smoking — Smoking top Named Individuals ToC

Smoking habit (User level).

s4ehaw:SolarPowered — Solar Powered top Named Individuals ToC

Kind of feature of interest powered by the sun.

belongs to
saref:FeatureKind

s4ehaw:SportTraining — Sport Training top Named Individuals ToC

Sport training task for BAN application.

s4ehaw:StarBanTopology — Star BAN Topology top Named Individuals ToC

Star BAN topology type.

s4ehaw:Telemedicine — Telemedicine top Named Individuals ToC

Telemedicine task for BAN application.

s4ehaw:TransmissionRate — transmission rate top Named Individuals ToC

The transmission rate of the interface, i.e. the number of bits transmitted per second (usually expressed in kbps or Mbps).

belongs to
saref:Property

s4ehaw:UltraWideBand — Ultra Wide Band top Named Individuals ToC

Ultra Wide Band, a communication protocol.

s4ehaw:Undereating — Undereating top Named Individuals ToC

Undereating habit (User level).

s4ehaw:UndeterminedGender — Undetermined top Named Individuals ToC

undetermined gender

s4ehaw:Velocity — Velocity top Named Individuals ToC

The velocity of a moving entity. Typically expressed in m/s.

belongs to
saref:Property

s4ehaw:Walking — Walking top Named Individuals ToC

Posture of a walking user.

s4ehaw:Weight — Weight top Named Individuals ToC

The weight of a feature of interest.

belongs to
saref:Property

s4ehaw:Width — Width top Named Individuals ToC

The width dimension of a feature of interest.

belongs to
saref:Property

s4ehaw:WristWeared — Wrist location top Named Individuals ToC

Wrist, a user body surface location.

s4ehaw:Young — Young top Named Individuals ToC

Young, one user age category.

References

Normative references

Informative references

  • [i.1] W3C® Recommendation 19 October 2017:"Semantic sensor network ontology", OGC® and W3C® Spatial Data on the Web working Group.
  • [i.2] 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.
  • [i.3] HL7 FHIR®: "Fast Healthcare Interoperability Resources".

NOTE:

FHIR® 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.

NOTE:

DICOM® 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.

Acknowledgements

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.