SAREF4EHAW
type: Ontology
issued: date when the document is online
modified: do not set this
created: start date of the STF 2019-01-01
preferred namespace prefix: s4ehaw
comment: Extension of SAREF for eHealth Ageing Well domain.
description: s4ehaw is an extension of SAREF for eHealth Ageing Well
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](diagram/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 de…
title: s4ehaw: an extension of SAREF for eHealth Ageing Well
version info: v0.1.2
license: etsi-software-license
source: s4ehaw
version IRI: s4ehaw
imports: core
imports: saref4envi
publisher: www.etsi.org
creator: ~girodgen
contributor: ~girodgen
contributor: lina-nachabe-2b292457
contributor: www.maxime-lefrancois.info
contributor: joão-luiz-moreira
contributor: maurodragoni

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

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

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

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

has computing power
type: ObjectProperty
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...).
range: ComputingPower
domain: DeviceType

has constraint
type: ObjectProperty
comment: Data has constraints (validity, operating, security...).
range: Constraint
domain: Data

has contact
type: ObjectProperty
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).
domain: Ban
range: Contact

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

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

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

has impairment
type: ObjectProperty
comment: The impairment type of a patient, e.g. deaf, hearing, handling, visual, mobility...
range: Impairment
domain: Patient

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

has location
type: ObjectProperty
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).
domain: Health Device
range: Location

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

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

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

has participant
type: ObjectProperty
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).
range: HealthActor
range: Health Device
domain: MeasurementCollectionSession

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

has posture
type: ObjectProperty
comment: The posture of a health actor, e.g. exercising, lying, running, sitting, walking...
domain: HealthActor
range: Posture

has power source
type: ObjectProperty
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...).
domain: DeviceType
range: PowerSource

has responsible party
type: ObjectProperty
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.
domain: Ban
range: ResponsibleParty

has time series measurements
type: ObjectProperty
comment: Data has time series measurements, a sequence taken at successive equally spaced points in time.
domain: Data
range: Time series measurements

has values
type: ObjectProperty
comment: A relationship defining the set of values (an array) of a certain property, e.g., energy or power
type: DatatypeProperty

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

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

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

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

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

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

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

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

has command
type: ObjectProperty
comment: A function has a command (a directive that a device must support to perform a given function).
range: Command
domain: Function

has function
type: ObjectProperty
comment: A device has a function (e.g., for an ehealth device, temperature measurement, blood pressure measurement, insulin regulation).
range: Function
domain: Device

offers
type: ObjectProperty
comment: A device offers services, e.g., for an eHealth device, a thermometer offers a temperature measurement service.
range: Service
domain: Device

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

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

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

available flash
type: DatatypeProperty
comment: The available flash memory of a health device.
range: double
domain: ComputingPower

available ram
type: DatatypeProperty
comment: Indicates the available volatile memory space of a health device.
range: double
domain: ComputingPower

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

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

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

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

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

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

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

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

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

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

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

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

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

has calculation method
type: DatatypeProperty
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.
range: string
domain: ServiceProcess

has effect
type: DatatypeProperty
comment: The effect of a service can be an alert, nothing, an activation of another process...
range: string
domain: ServiceProcess

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

has geolocation
type: DatatypeProperty
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.
range: string
domain: Ban

has habit
type: DatatypeProperty
comment: The habits of a health actor, e.g. smoking.
range: string
domain: HealthActor

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

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

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

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

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

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

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

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

is derived data
type: DatatypeProperty
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.
range: boolean
domain: Data

is gateway
type: DatatypeProperty
comment: This boolean variable indicates if the interface is a gateway or not.
range: boolean
domain: Interface

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

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

lifetime
type: DatatypeProperty
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.
range: dateTime
domain: Ban

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

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

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

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

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

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

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

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

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

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

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

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

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

remaining battery level
type: DatatypeProperty
comment: The level of remaining battery for a given power source of a health device.
range: double
domain: PowerSource

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

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

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

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

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

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

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

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

DailyActivity
type: Class
subclass of: Activity
comment: The class of activities that occur during daytime.

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

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

Health Device
type: Class
subclass of: FunctionRelated

BAN Hub
type: Class
subclass of: Health Device

LegalConstraint
type: Class
subclass of: Constraint
comment: This is 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).

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

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

OperatingConstraint
type: Class
subclass of: Constraint
comment: This is an empty container for describing the operating constraints of a device, e.g. prescribed humidity and temperature range...

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

ResponsibleParty
type: Class
subclass of: HealthActor
comment: The legal entity responsible for a BAN, i.e. to contact in case of problem

ServiceGrounding
type: Class
comment: How to access the service.

ServiceProcess
type: Class
comment: How the service works.

ServiceProfile
type: Class
comment: What the service does.

Time series measurements
type: Class
subclass of: Measurement
subclass of: Restriction
  on property: has values
  all values from: float
subclass of: Restriction
  on property: has frequency measurement
  all values from: FrequencyMeasurement
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 we termed this concept as Time Series Measurements since this sequence of data refers to time series measured by a device. Notice that in this term we avoided prefixing with ECG because this concept can be applied to other types of data.

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

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