SAREF4EHAW: an extension of SAREF for eHealth Ageing Well domain
type: Ontology
imports: v3.1.1
creator: ~girodgen
contributor: lina-nachabe-2b292457
contributor: joão-luiz-moreira
contributor: dragoni
contributor: www.maxime-lefrancois.info
publisher: www.etsi.org
license: etsi-software-license
source: saref4ehaw
version IRI: v1.1.1
version info: v1.1.1
preferred namespace prefix: s4ehaw
issued: 2020-02-01
modified: 2020-05-01
description: 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, SAREF 4 Wearables extension, SAREF4health ontology which is a very first try to somehow extend SAREF ontology for the health vertical (it has nothing to do with ETSI SAREF4XYZ naming convention). 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 d…

consists of
type: ObjectProperty
domain: Health Device
range: Health Device
comment: An eHealth device can be a composite health device that consists of one or multiple sub-devices.

contains
type: ObjectProperty
domain: BAN
range: Health Device
comment: A Body Area Network or BAN contains one or multiple health devices

follows user
type: ObjectProperty
domain: User
range: Helper
comment: A helper may follow one or multiple users that can in particular be patients.

has activity
type: ObjectProperty
domain: Health actor
range: Activity
comment: A health actor may have one or multiple activities.

has ban application domain
type: ObjectProperty
domain: BAN
range: BAN application domain
comment: The BAN application domain - healthcare, telemedicine, assisted living, sport training, pervasive computing, safety and emergency... -.

has communication function
type: ObjectProperty
domain: BAN
range: Communication function
comment: A BAN has a communication function that is the type of communication carried out between BAN devices and BAN Hub.

has computing power
type: ObjectProperty
domain: Device type
range: Computing power
comment: A health device type has computing power 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 constraint
type: ObjectProperty
domain: Data
range: Constraint
comment: Data has constraints (validity, operating, security...).

has contact
type: ObjectProperty
domain: BAN
range: Contact
comment: 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 data
type: ObjectProperty
domain: Function
range: Data
comment: A function has one or many data, for example a tracking function shall include latitude, longitude and speed data.

has device type
type: ObjectProperty
domain: Health Device
range: Device type
comment: A health device has a device type describing the physical characteristics of the health device.

has habit
type: ObjectProperty
domain: User
range: Habit
comment: The habits of a user and a patient (as sub-class of user it also inherits habit), e.g. smoking or overeating.

has hub
type: ObjectProperty
domain: BAN
range: BAN hub
comment: A Body Area Network or BAN elects one hub that mainly plays the role of both a data concentrator and a network GW.

has impairment
type: ObjectProperty
domain: User
range: Impairment
comment: The impairment type of a user and a patient (as sub-class of user it also inherits habit), e.g. deaf, hearing, handling, visual, mobility...

has interface
type: ObjectProperty
domain: Health Device
range: Interface
comment: A health device has one or multiple interfaces (Bluetooth, UWB, IEEE 802.15.6, serial interface...).

has location
type: ObjectProperty
domain: Health Device
range: Location
comment: The location of an eHealth device, i.e. its position against the body (on ¡V body surface ¡V or in the body ¡V implant ¡V) and its physical location (i.e. its postal address and/or its current geolocation geolocation when available).

has measurement
type: ObjectProperty
domain: Data
range: Measurement
comment: Defines the relationship between data that has measurement.

has mode
type: ObjectProperty
domain: Device type
range: Mode
comment: Each device type has modes of operations that model its dynamic characteristic varying during its lifetime, e.g. active, parked, sleeping...

has operating constraint
type: ObjectProperty
domain: Health Device
range: Operating constraint
comment: The operating constraints of a health device.

has participant
type: ObjectProperty
domain: Measurement collection session
range: Health actor
range: Health Device
comment: A measurement session has health actors as participants (caregiver controling the session, patient monitored during the session).
comment: A measurement session has one or multiple health devices as participants (sensor, actuator, wearable).

has patient
type: ObjectProperty
domain: Caregiver
range: Patient
comment: A caregiver may have one or multiple patients.

has physical location
type: ObjectProperty
domain: Patient
range: Physical location
comment: Defines the physical location of the patient, i.e. its postal address and/or its geolocation (when available).

has posture
type: ObjectProperty
domain: User
range: Posture
comment: 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 power source
type: ObjectProperty
domain: Device type
range: Power source
comment: A health device type has 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 responsible party
type: ObjectProperty
domain: BAN
range: Responsible party
comment: 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 time series measurements
type: ObjectProperty
domain: Data
range: Time series measurements
comment: Data has time series measurements, a sequence taken at successive equally spaced points in time.

in current mode
type: ObjectProperty
domain: Health Device
range: Mode
comment: Each eHealth device has modes of operations that model its dynamic characteristic varying during its lifetime, e.g. active, parked, sleeping...

is attached to
type: ObjectProperty
domain: Health Device
range: Health actor
comment: A health Device is attached to a health actor such as a patient, a user and or a caregiver.

is described by
type: ObjectProperty
domain: Service
range: Service process
comment: A service is described by a service process (how the service works).

presents
type: ObjectProperty
domain: Service
range: Service profile
comment: A service presents a service profile (what the service does).

supports
type: ObjectProperty
domain: Service
range: Service grounding
comment: A service supports a service grounding (how to access the service).

unit of measurement
type: ObjectProperty
domain: Measurement function
range: UnitOfMeasure
comment: Defines the unit of measure of a measurement function.

uses ban
type: ObjectProperty
domain: Health actor
range: BAN
comment: A health actor (e.g. a caregiver, a patient or a helper) uses a BAN for collecting, aggregating and relaying vital parameters.

has chronic disease
type: ObjectProperty
domain: Patient
range: Chronic disease
comment: A patient can suffer from one or more chronic disease like Diabetes, azma, etc.

has frequency measurement
type: ObjectProperty
domain: Measurement function
range: Frequency measurement
comment: A measurement fucntion, in case of complex measurement like time series, has frequency measurement, i.e. the frequency in which it makes measurements.

activity duration
type: DatatypeProperty
domain: Activity
range: double
comment: The duration of an activity, in second.

activity kind
type: DatatypeProperty
domain: Activity
range: string
comment: 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.

age category
type: DatatypeProperty
domain: Health actor
range: Datatype
  one of: old
  one of: young
comment: The age group of a health actor, i.e. old or young.

available flash
type: DatatypeProperty
domain: Health Device
range: double
comment: The available flash memory of a health device. It is a dynamic attribute.

available ram
type: DatatypeProperty
domain: Health Device
range: double
comment: Indicates the available volatile memory space of a health device. It is a dynamic attribute.

baud
type: DatatypeProperty
domain: Interface
range: double
comment: The baud rate of the interface, the number of bits transmitted by second.

data size
type: DatatypeProperty
domain: Data
range: integer
comment: The data size represents the size of the data e.g. 20 bits

density
type: DatatypeProperty
domain: BAN
range: long
comment: The BAN density, i.e. its number of node.

device type name
type: DatatypeProperty
domain: Device type
range: string
comment: The commercial name of a device.

dimension
type: DatatypeProperty
domain: Device type
range: string
comment: The dimension of the device i.e. height*weight*length.

date of birth
type: DatatypeProperty
domain: Health actor
range: dateTime
comment: The date of birth of a health actor.

duty cycle
type: DatatypeProperty
domain: Computing power
range: float
comment: The duty cycle for each health device embedded processor in order to determine the processing speed.

fault tolerence
type: DatatypeProperty
domain: Measurement function
range: double
comment: Defines the error rate tolerated for a measurement function.

first name
type: DatatypeProperty
domain: Health actor
range: string
comment: The first name of a health actor.

format
type: DatatypeProperty
domain: Data
range: anyURI
comment: The format is a UDDI for a standard format like integer, memo, etc.

frequency
type: DatatypeProperty
domain: Computing power
range: double
comment: The frequency is the number of instructions an embedded processor - within a health device - can perform per second.

geolocation
type: DatatypeProperty
domain: Physical location
range: string
comment: The geolocation, when available, shall be given relatively to the current location - geolocation as standardized ISO 6709 -.

grounding protocol
type: DatatypeProperty
domain: Service grounding
range: string
comment: The grounding protocol is the protocol used to transmit the message of the service, e.g. BLE.

has calculation method
type: DatatypeProperty
domain: Service process
range: string
comment: 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 effect
type: DatatypeProperty
domain: Service process
range: string
comment: The effect of a service can be an alert, nothing, an activation of another process...

has gender
type: DatatypeProperty
domain: Health actor
range: Datatype
  one of: female
  one of: male
  one of: undetermined
comment: The gender of a health actor.

has geolocation
type: DatatypeProperty
domain: BAN
range: string
comment: The geolocation of the BAN, when available and needed, shall be given relatively to the current location - geolocation as standardized ISO 6709 - of the patient wearing the BAN.

has input
type: DatatypeProperty
domain: Service process
range: string
comment: The service process has data input like e.g. the patient ID, the timestamp, the read value from a sensor...

has mbox
type: DatatypeProperty
domain: Health actor
range: anyURI
comment: An email address (or mail box) of an health actor: a URI with the 'mailto' scheme as defined by RFC 6068.

has output
type: DatatypeProperty
domain: Service process
range: string
comment: The output is e.g. the calculated value returned by the process, e.g the posture of a patient.

has precondition
type: DatatypeProperty
domain: Service process
range: string
comment: The conditions that are imposed over the inputs of the process and the process must hold to be successufully invoked.

has result
type: DatatypeProperty
domain: Service process
range: string
comment: The process can have many results for the same output. Those results may include a message that should be displayed, an alert...

interface address
type: DatatypeProperty
domain: Interface
range: string
comment: The interface address. The interface may have many addresses like MAC address, IP address or others.

interface description
type: DatatypeProperty
domain: Interface
range: string
comment: The interface type description.

interface protocol
type: DatatypeProperty
domain: Interface
range: string
comment: The interface communication protocol can be e.g. BLE, serial, Ethernet...

is derived data
type: DatatypeProperty
domain: Data
range: boolean
comment: 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 gateway
type: DatatypeProperty
domain: Interface
range: boolean
comment: This boolean variable indicates if the interface is a gateway or not.

last name
type: DatatypeProperty
domain: Health actor
range: string
comment: The familly name of a health actor.

latency
type: DatatypeProperty
domain: Measurement function
range: float
comment: The latency is the time interval between the stimulation and response of a measurement function.

lifetime
type: DatatypeProperty
domain: BAN
range: dateTime
comment: The BAN lifetime, 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.

manufacturer
type: DatatypeProperty
domain: Computing power
range: string
comment: The manufacturer name of the embedded processor of a health device, e.g. Intel.

maximum flash
type: DatatypeProperty
domain: Computing power
range: double
comment: Indicates the maximum flash memory space of a health device.

maximum ram
type: DatatypeProperty
domain: Computing power
range: double
comment: Indicates the maximum volatile memory space of a health device.

maximum value
type: DatatypeProperty
domain: Validity constraint
range: double
comment: The maximum allowable value of a measurement.

minimum value
type: DatatypeProperty
domain: Validity constraint
range: double
comment: The minimum allowable value of a measurement.

mode name
type: DatatypeProperty
domain: Mode
range: string
comment: The mode name of a device, e.g. sleeping.

phenomena
type: DatatypeProperty
domain: BAN
range: string
comment: The BAN monitors a specific phenomenon (burned calories during exercises, glucose level...).

phone
type: DatatypeProperty
domain: Health actor
range: string
comment: The phone number of a health actor, in international format.

port number
type: DatatypeProperty
domain: Service grounding
range: positiveInteger
comment: The port number used to offer the service.

postal address
type: DatatypeProperty
domain: Physical location
range: string
comment: Defines the postal address.

power source type
type: DatatypeProperty
domain: Power source
range: string
comment: The type of power source of a health device. It can be solar, battery, electricity...

precision
type: DatatypeProperty
domain: Measurement function
range: float
comment: Precision of a measurement function is the uncertainty of the measured data.

rechargeable
type: DatatypeProperty
domain: Power source
range: boolean
comment: This boolean variable indicates if the power source is rechargeable or not, e.g. a rechargeable battery.

remaining battery level
type: DatatypeProperty
domain: Health Device
range: double
comment: The level of remaining battery (if any) for a health device. It is a dynamic attribute.

sample time
type: DatatypeProperty
domain: Measurement function
range: float
comment: The sample time of a measurement function.

sending frequency
type: DatatypeProperty
domain: Periodic communication function
range: float
comment: Defines the sending frequency at an health device level.

serial number
type: DatatypeProperty
domain: Health Device
range: string
comment: The serial number of a health device.

service description
type: DatatypeProperty
domain: Service profile
range: string
comment: The service description should describe the offered service like e.g. heart rate measurement.

service name
type: DatatypeProperty
domain: Service profile
range: string
comment: The service name identify the offered service, e.g heart rate.

topology
type: DatatypeProperty
domain: BAN
range: Datatype
  one of: Adhoc
  one of: Mesh
  one of: Star
comment: The BAN physical topology type, i.e Adhoc or Star or Mesh or Others. @ne

velocity
type: DatatypeProperty
domain: Device type
range: float
comment: The velocity of a moving device.

Activity
type: Class
comment: The activity of a patient/user, i.e. daily and nocturnal activities.

Alarm comand
type: Class
subclass of: Command

BAN
type: Class
comment: Smart Body Area Network (BAN), as defined within ETSI SmartBAN TC (see ETSI TR 103 394).

BAN application domain
type: Class
comment: The BAN application domain, e.g. healthcare, telemedicine, assisted living, sport training, safety and emergency...

BAN hub
type: Class
subclass of: Health Device
comment: Hub of the BAN, mainly playing the role of both a data concentrator and a network GW.

Body surface location
type: Class
subclass of: Location
comment: Defines a helth device location in terms of a body surface position (i.e. on body health device).

Caregiver
type: Class
subclass of: Health actor
comment: For caregivers modelling.

Chronic disease
type: Class
comment: For chronic disease modelling chronic, e.g. Diabetes, azma...

Communication function
type: Class
comment: The BAN communication function way of working, i.e. periodic, event driven or on request.

Computing power
type: Class
comment: The computing power capabilities of a Health device.

Constraint
type: Class
comment: The Data constraints, e.g. validity, operating, security...

Contact
type: Class
equivalent class: Health actor
comment: 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...

Daily activity
type: Class
subclass of: Activity
comment: The patient/user activities that occur during daytime.

Data
type: Class
comment: A function has one or many data, for example a tracking function shall include latitude, longitude and speed data.

Device type
type: Class
comment: A health device has a device type describing the physical characteristics of the health device.

Event driven communication function
type: Class
subclass of: Communication function
comment: BAN communication function way of working of the type event driven.

Functional device
type: Class
subclass of: FunctionRelated
comment: 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.

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

Health actor
type: Class
comment: The eHealth system actors like e.g. caregivers, patients, users, helpers...

Health actuator
type: Class
equivalent class: Actuator
subclass of: Health Device
comment: Health-related Actuator, equivalent to SAREF Actuator

Health Device
type: Class
subclass of: FunctionRelated
comment: Health Devices, e.g. BAN hub, health sensor/actuator/Wereable.

Health-related Sensor, equivalent to SAREF Sensor
type: Class
equivalent class: Sensor
subclass of: Health Device
label: Health sensor

Health-related Wearable, equivalent to SAREF4WEAR Wearable
type: Class
equivalent class: Wearable
subclass of: Health Device
label: Health wereable

Helper
type: Class
subclass of: Health actor
comment: Helper of partients/users of a health system, e.g. a patient's relative.

Impairment
type: Class
comment: Defined for users (that can in particular be patients) impairments modelling, e.g. deaf impairment, hearing impairement, handling impairment, visual impairement, blindI impairement, mobility impairement...

Implant location
type: Class
subclass of: Location
comment: Implant Device (i.e. in body health device) position.

Interface
type: Class
comment: Used for modelling the interfaces of a health device (e.g. Bluetooth, UWB, IEEE 802.15.6, serial interface...).

Legal constraint
type: Class
subclass of: Constraint
comment: An empty container for describing the legal constraints a data can be submitted to, like e.g. anonymization.

Location
type: Class
comment: 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 geolocation when available).

Measurement collection session
type: Class
subclass of: Task
comment: 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, Wereable, ECG Device...) and a health actor (mainly a caregiver).

Measurement function
type: Class
subclass of: Function
comment: The functionality necessary to accomplish the measurement task for which a measurement-related health Device (e.g. Sensor, Wereable, ECG Device...) is designed for, e.g. a heart rate measurement function.

Mode
type: Class
comment: The dynamic characteristics of a eHealth Device that vary during its lifetime or its BAN lifetime.

Nocturnal activity
type: Class
subclass of: Activity
comment: The class of activities that occur during the night.

On request communication function
type: Class
subclass of: Communication function
comment: BAN communication function way of working of the type on request.

Operating constraint
type: Class
subclass of: Constraint
comment: An empty container for describing the operating constraints of a device, e.g. recommended humidity and temperature range...

Patient
type: Class
subclass of: User
comment: A user of the type patient, i.e. a cared-for person by one or multiple caregivers.

Periodic communication function
type: Class
subclass of: Communication function
comment: BAN communication function way of working of the type periodic.

Physical location
type: Class
subclass of: Location
comment: The physical location, i.e. a postal address and a geolocation when available.

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

Power source
type: Class
comment: 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...).

Reminder command
type: Class
subclass of: NotifyCommand
comment: Command used for sending reminder notifications to health actors, e.g. pationts, users or Caregivers.

Responsible party
type: Class
subclass of: Health actor
comment: The legal entity responsible for a BAN, i.e. to contact in case of problem

Service grounding
type: Class
comment: How to access the service.

Service process
type: Class
comment: How the service works.

Service profile
type: Class
comment: What the service does.

Time series measurements
type: Class
subclass of: Measurement
subclass of: Restriction
  on property: has frequency measurement
  all values from: Frequency measurement
subclass of: Restriction
  on property: hasValues
  all values from: float
comment: 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.

User
type: Class
subclass of: Health actor
comment: 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.

Validity constraint
type: Class
subclass of: Constraint
comment: Data may have validity constraint such as allowable value range.

Frequency measurement
type: Class
comment: 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.