The objective of SAREF4EHAW is to extend SAREF ontology 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 formalised by investigating EHAW domain related resources, as reported in ETSI TR 103 509, 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.e. - Use case 1 “elderly at home monitoring and support”, - Use case 2 “monitoring and support of healthy lifestyles for citizens”, - Use case 3 “Early Warning System (EWS) and Cardiovascular Accidents detection”. - Fulfil the eHealth Ageing Well related requirements provided in ETSI TR 103 509, mainly the ontological ones that were mostly taken as input for the ontology specification. SAREF4EHAW mainly reuses the following existing ontologies: SAREF, ETSI SmartBAN reference model, SAREF 4 Environment extension and W3C SSN System module. The following figure presents the high level view of SAREF4EHAW ontology. ![SAREF4SYST overview](diagrams/SAREF4EHAW_Model.jpg) 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 behas been fully modelled (Service class and sub-classes depicted in the previous figure). For embedded semantic analytics purposes, SAREF4EHAW shall behas been designed using the modularity principle (see ETSI TR 103 509) and can thus be mainly described by the following self-contained knowledge sub-ontologies (or modules): HealthActor, Ban, HealthDevice, Function (measured data related concepts included) and Service.
SAREF4EHAW: an extension of SAREF for eHealth Ageing Well domain
A relationship indicating a composite entity that consists of other entities (e.g., a temperature/humidity sensor that consists of a temperature sensor and a humidity sensor)
consists of
A helper may follow one or multiple users that can in particular be patients.
follows user
The grounding protocol is the protocol used to transmit the message by the service, e.g. BLE.
grounding protocol
A health actor may have one or multiple activities.
has activity
The age group of a health actor, e.g. old or young.
has age category
The BAN application domain - healthcare, telemedicine, assisted living, sport training, pervasive computing, safety and emergency... -.
has BAN application domain
A BAN has a BAN communication type that is the type of communication carried out between BAN devices and BAN Hub.
has BAN communication type
A patient can suffer from one or more chronic disease like Diabetes, azma, etc.
has chronic disease
A health device characteristic describing the processing power or capabilities of the device (e.g. processor ID and manufacturer, duty cycle, available flash/RM memory, maximum flash/RAM memory...).
has computing power
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 contact
A function has one or many data, for example a tracking function shall include latitude, longitude and speed data.
has data
Data has data constraints (validity, legal...).
has data constraint
A health device has device characteristic describing the physical characteristics of the health device, e.g. its dimensions.
has device characteristic
The habits of a user and a patient (as sub-class of user it also inherits habit), e.g. smoking or overeating.
has habit
A Body Area Network or BAN elects one hub that mainly plays the role of both a data concentrator and a network gateway.
has hub
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...
has impairment
A health device has one or multiple interfaces (Bluetooth, UWB, IEEE 802.15.6, serial interface...).
has interface
The location of an eHealth device, i.e. its position against the body (on body surface or in the body - implant -) and its physical location (i.e. its postal address and/or its current geolocation geolocation when available).
has location
Defines the relationship between data that has measurement.
has measurement
Each device has modes of operations that model its dynamic characteristic varying during its lifetime, e.g. active, hold, beacon...
has mode
The operating constraints of a health device, e.g. recommended humidity and temperature range...
has operating constraint
A measurement session has health actors as participants (caregiver controling the session, patient monitored during the session).
has participant
A caregiver may have one or multiple patients.
has patient
Defines the physical location of the patient, i.e. its postal address and/or its geolocation (when available).
has physical location
The posture of a user and a patient (as sub-class of user it also inherits habit), e.g. exercising, lying, running, sitting, walking...
has posture
A health device characteristic is its power sources, mainly describing energy source and battery related capabilities of the health device (number of power source, source type, rechargeable or not, available power level...).
has power source
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 responsible party
Data has time series measurements, a sequence taken at successive equally spaced points in time.
has time series measurement
Each eHealth device has modes of operations that model its dynamic characteristic varying during its lifetime, e.g. active, hold, beacon...
in current mode
The interface communication protocol can be e.g. BLE, serial, Ethernet...
interface protocol
A health Device is attached to a health actor such as a patient, a user and or a caregiver.
is attached to
A service is described by a service process (how the service works).
is described by
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).
precision
A service presents a service profile (what the service does).
presents
A service supports a service grounding (how to access the service).
supports
Defines the unit of measure of a measurement function.
unit of measurement
A health actor (e.g. a caregiver, a patient or a helper) uses a BAN for collecting, aggregating and relaying vital parameters.
uses ban
A measurement fucntion, in case of complex measurement like time series, has frequency measurement, i.e. the frequency in which it makes measurements.
has frequency measurement
A relationship identifying the manufacturer of an entity (e.g., device). The value is expected to be a string or a string with language tag.
has manufacturer
The duration of an activity, in second.
activity duration
The kind of atcivities that a patient or a user can have, i.e. e.g. sleeping in bed, sitting on a chair, using the shower, etc.
activity kind
The available flash memory (in byte) of a health device. It is a dynamic attribute.
available flash
Indicates the available volatile memory space (in byte) of a health device. It is a dynamic attribute.
available ram
The BAN density, i.e. its number of node.
BAN density
The geolocation of the BAN, when available and needed, shall be given relatively to the current location - geolocation as standardized ISO 6709, e.g. +40.75-074.00/ - of the patient wearing the BAN.
BAN geolocation
The BAN physical topology type, i.e Adhoc or Star or Mesh or Others.
BAN topology
The data size represents the size of the data in bytes
data size
The commercial name of a device.
device characteristic name
The dimension of the device i.e. height*weight*length string.
dimension
The date of birth of a health actor.
date of birth
The duty cycle for each health device embedded processor, in percent.
duty cycle
Defines the error rate tolerated for a measurement function.
fault tolerence
The first name of a health actor.
first name
The format is a URI for a standard format like e.g. integer.
format
The frequency is the number of instructions an embedded processor - within a health device - can perform per second (MIPS).
frequency
The geolocation, when available, shall be given relatively to the current location - geolocation as standardized ISO 6709, e.g. +40.75-074.00/ -.
geolocation
The service process has a calculation method to get the output or result, e.g. the calculation formula to determine the posture of a patient.
has calculation method
The effect of a service can be an alert, nothing, an activation of another process...
has effect
The gender of a health actor.
has gender
The service process has data input like e.g. the patient ID, the timestamp, the read value from a sensor...
has input
An email address (or mail box) of an health actor: a URI with the 'mailto' scheme as defined by RFC 6068.
has mbox
The output is e.g. the calculated value returned by the process, e.g the posture of a patient.
has output
The conditions that are imposed over the inputs of the process and the process must hold to be successufully invoked.
has precondition
The process can have many results for the same output. Those results may include a message that should be displayed, an alert...
has result
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).
has values
The interface address. The interface may have many addresses like MAC address, IP address or others.
interface address
The interface type description.
interface description
Is derived data is a Boolean property to indicate if the data is a row data or a calculated/derived data from other one.
is derived data
This boolean variable indicates if the interface is a gateway or not.
is gateway
The familly name of a health actor.
last name
The latency is the time interval between the stimulation and response of a measurement function (in ms).
latency
The BAN lifetime (in month), e.g. BAN for entertainment purposes should have a lifetime of weeks or few years whereas BAN dedicated for assisted living or anomaly monitoring should last for many years.
lifetime
Indicates the maximum flash memory space (in byte) of a health device.
maximum flash
Indicates the maximum volatile memory space (in byte) of a health device.
maximum ram
The maximum allowable value of a measurement.
maximum value
The minimum allowable value of a measurement.
minimum value
The mode name of a device, e.g. sleeping.
mode name
The BAN monitors a specific phenomenon (burned calories during exercises, glucose level...).
phenomena
The phone number of a health actor, in international format.
phone
The port number used to offer the service.
port number
Defines the postal address.
postal address
The type of power source of a health device. It can be solar, battery, electricity...
power source type
This boolean variable indicates if the power source is rechargeable or not, e.g. a rechargeable battery.
rechargeable
The level of remaining battery (if any : in percent) for a health device. It is a dynamic attribute.
remaining battery level
The sample time of a measurement function (a discrete integer).
sample time
Defines the sending frequency (in ms), at an health device level, in case of pariodic BAN communication type.
sending frequency
The serial number of a health device.
serial number
The service description should describe the offered service like e.g. heart rate measurement.
service description
The service name identify the offered service, e.g heart rate.
service name
The transmission rate of the interface, i.e. the number of bits transmitted per second (usually expressed in kbps or Mbps).
transmission rate
The velocity of a moving device (in m/s).
velocity
The activity of a patient/user, i.e. daily and nocturnal activities.
Activity
Age category
A command corresponding to alarm sending.
Alarm command
Body Area Network.
BAN
The BAN application domain, e.g. healthcare, telemedicine, assisted living, sport training, safety and emergency...
BAN application domain
The BAN communication function type, i.e. periodic, event driven or on request.
BAN Communication type
Hub of the BAN, mainly playing the role of both a data concentrator and a network gateway.
BAN hub
Defines a health device location in terms of a body surface position (i.e. on body health device).
Body surface location
For caregivers modelling.
Caregiver
For chronic disease modelling, e.g. diabetes, asthma...
Chronic disease
The communication protocol, e.g. BLE, serial, Ethernet...
Communication protocol
The computing power capabilities of a Health device.
Computing power
A BAN has one or multiple contacts, i.e. some health actors, e.g. the patient or user that is monitored through this BAN, the caregiver that is using this BAN for monitoring purposes...
Contact
The patient/user activities that occur during daytime.
Daily activity
Data
The Data constraints, e.g. validity, legal...
Data constraint
A health device has device characteristic describing the physical characteristics of the health device.
Device characteristic
BAN communication function way of working of the type event driven.
Event driven BAN communication type
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.
Functional device
Defined for users (that can in particular be patients) habits modelling, e.g. smoking, alcohol drinking, overeating, undereating...
Habit
The eHealth actors like e.g. caregivers, patients, users, helpers...
Health actor
Health-related Actuator, equivalent to SAREF Actuator.
Health actuator
Health devices, e.g. BAN hub, health sensor/actuator/Wereable.
Health Device
Health-related Sensor, equivalent to SAREF Sensor.
Health sensor
Health-related Wearable, equivalent to SAREF4WEAR Wearable.
Health wereable
Helper of patients/users, e.g. a patient's relative.
Helper
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.
Impairment
Implant Device (i.e. in body health device) position.
Implant location
Used for modelling the interfaces of a health device (e.g. Bluetooth, UWB, IEEE 802.15.6, serial interface...).
Interface
An empty container for describing the legal constraints a data can be submitted to, like e.g. anonymization.
Legal constraint
The location, i.e. a position against the body (on - body surface – or in the body – implant –) and a physical location (i.e. a postal address and/or a current geolocation when available).
Location
Task in which a health actor (mainly a patient or a user) is subject of measurement collection (recording) by both some measurement-related health Device (e.g. Sensor, Wearable, ECG Device...) and a health actor (mainly a caregiver).
Measurement collection session
The functionality necessary to accomplish the measurement task for which a measurement-related health Device (e.g. Sensor, Wearable, ECG Device...) is designed for, e.g. a heart rate measurement function.
Measurement function
The dynamic characteristics of a eHealth Device that vary during its lifetime or its BAN lifetime.
Mode
The patient/user activities that occur during the night.
Nocturnal activity
BAN communication function way of working of the type on request.
On request BAN communication type
An empty container for describing the operating constraints of a device, e.g. recommended humidity and temperature range...
Operating constraint
A user of the type patient, i.e. a cared-for person by one or multiple caregivers.
Patient
BAN communication function way of working of the type periodic.
Periodic BAN communication type
The physical location, i.e. a postal address and a geolocation when available.
Physical location
The posture of a health actor (mainly a patient or a user), e.g. exercising, lying, running, sitting, walking...
Posture
The power sources of a health device, mainly describing energy source and battery related capabilities of the health device (number of power source, source type, rechargeable or not...).
Power source
Command used for sending reminder notifications to health actors, e.g. patients, users or Caregivers.
Reminder command
The legal entity responsible for a BAN, i.e. to contact in case of problem.
Responsible party
How to access the service.
Service grounding
How the service works.
Service process
What the service does.
Service profile
A sequence of data in a successive equally spaced points in time. The O&M ontology (ISO 19156) defines Time Series Observation as an “observation whose result is a time-series”, while both Hl7 aECG and DICOM standards define the Series element as a sequence of data sharing a common frame of reference. In SAREF4health this concept is termed as Time Series Measurements since this sequence of data refers to time series measured by a health device.
Time series measurement
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.
User
Data may have validity constraint such as allowable value range.
Validity constraint
Represents the measured value made over a frequency property. It is also linked to the frequency unit of measure in which the value is expressed and the timestamp of the measurement.
Frequency measurement
Alcohol drinking habit (User level).
Alcohol drinking
Armpit location, a user body surface location.
Armpit location
Assisted living sub-domain for BAN application.
Assisted living
Asthma, a chronical disease that some users can have.
Asthma
Aural impairment (User level), i.e. impairments of auditory sensitivity.
Aural impairment
Diabetes, a chronical disease that some users can have.
Diabetes
Emergency sub-domain for BAN application.
Emergency
Posture of user doing exercises.
Exercising
Healthcare domain for BAN application.
Healthcare
Skeletal impairment (User level), e.g. ...
Intellectual impairment
Posture of a lying user.
Lying
Mobility impairment (User level).
Mobility impairment
Ocular impairment (User level), i.e. impamnents of visual acuity.
Ocular impairment (User level).
Ocular impairment
Old, one user age category.
Old
Overeating habit (User level).
Overeating
Pervasive computing sub-domain for BAN application.
Pervasive computing
Prevention sub-domain (e.g. preventive health) for BAN application.
Prevention
Posture of a running user.
Running
Safety sub-domain for BAN application.
Safety
Posture of a sitting user.
Sitting
Skeletal impairment (User level), e.g. of head and trunk regions, limbs...
Skeletal impairment
Smoking habit (User level).
Smoking
Sport training sub-domain for BAN application.
Sport Training
Telemedicine sub-domain for BAN application.
Telemedicine
Undereating habit (User level).
Undereating
Posture of a walking user.
Walking
Wrist, a user body surface location.
Wrist location
Young, one user age category.
Young