@@ -46,19 +44,15 @@ SAREF4EHAW mainly reuses the following existing ontologies: SAREF, ETSI SmartBAN
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."""^^<http://www.iana.org/assignments/media-types/text/markdown>;
dcterms:title"s4ehaw: an extension of SAREF for eHealth Ageing Well"@en;
dcterms:title"SAREF4EHAW: an extension of SAREF for the eHealth Ageing Well domain."@en;
rdfs:comment"A directive that a device must support to perform a certain function. A command may act upon a state, but does not necessarily act upon a state. For example, the ON command acts upon the ON/OFF state, but the GET command does not act upon any state, it simply gives a directive to retrieve a certain value. We propose here a list of commands that are relevant for the purpose of SAREF, but this list can be extended."@en;
rdfs:isDefinedBysaref:;
rdfs:label"Command"@en.
### https://saref.etsi.org/core/NotifyCommand
saref:NotifyCommandrdf:typeowl:Class;
rdfs:comment"A type of command used for notifications."@en;
rdfs: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..."@en;
rdfs:comment"The class of activities that occur during daytime."@en.
rdfs:comment"The patient/user activities that occur during daytime."@en;
rdfs:label"Daily activity"@en.
### https://saref.etsi.org/s4ehaw/Data
s4ehaw:Datardf:typeowl:Class.
s4ehaw:Datardf:typeowl:Class;
rdfs:comment"A function has one or many data, for example a tracking function shall include latitude, longitude and speed data."@en;
rdfs:label"Data"@en.
### https://saref.etsi.org/s4ehaw/core/Device
saref:Devicerdf:typeowl:Class;
rdfs:comment"A tangible object designed to accomplish a particular task in households, common public buildings or offices. In order to accomplish this task, the device performs one or more functions. For example, a washing machine is designed to wash (task) and to accomplish this task it performs the start and stop function."@en;
rdfs:isDefinedBysaref:;
rdfs:label"Device"@en.
### https://saref.etsi.org/s4ehaw/DeviceType
s4ehaw:DeviceTyperdf:typeowl:Class.
s4ehaw:DeviceTyperdf:typeowl:Class;
rdfs:comment"A health device has a device type describing the physical characteristics of the health device."@en;
rdfs: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."@en;
rdfs: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."@en;
rdfs:label"Functional device"@en.
### https://saref.etsi.org/core/Function
saref:Functionrdf:typeowl:Class;
rdfs:comment"The functionality necessary to accomplish the task for which a device is designed for, .e.g. a temperature measurement function. A device can be designed to perform more than one function. Functions can be structured in categories (subclasses) that reflect different points of view, for example, considering the specific application area for which a function can be used (e.g., heart rate, temperature, motion, oxygen level...), or the capability that a function can support (e.g., receive, reply, notify, etc.), and so forth. "@en;
rdfs: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)."@en.
rdfs: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)."@en;
rdfs:comment"Represents the measured value made over a property. It is also linked to the unit of measure in which the value is expressed and the timestamp of the measurement."@en;
rdfs: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)."@en;
rdfs: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. "@en;
rdfs:comment"The physical location, i.e. a postal address and a geolocation when available."@en.
rdfs:comment"The physical location, i.e. a postal address and a geolocation when available."@en;
rdfs:label"Physical location"@en.
### https://saref.etsi.org/s4ehaw/Posture
s4ehaw:Posturerdf:typeowl:Class.
s4ehaw:Posturerdf:typeowl:Class;
rdfs:comment"The posture of a health actor (mainly a patient or a user), e.g. exercising, lying, running, sitting, walking..."@en;
rdfs:label"Posture"@en.
### https://saref.etsi.org/s4ehaw/PowerSource
s4ehaw:PowerSourcerdf:typeowl:Class.
s4ehaw:PowerSourcerdf:typeowl:Class;
rdfs: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, available power level...)."@en;
rdfs:comment"The legal entity responsible for a BAN, i.e. to contact in case of problem"@en.
rdfs:comment"The legal entity responsible for a BAN, i.e. to contact in case of problem"@en;
rdfs:label"Responsible party"@en.
### https://saref.etsi.org/core/Service
saref:Servicerdf:typeowl:Class;
rdfs:comment"A service is a representation of a function to a network that makes the function discoverable, registerable, remotely controllable by other devices in the network. A service can represent one or more functions. A Service like e.g. a heart rate measurement service is offered by a health device that wants (a certain set of) its function(s) to be discoverable, registerable, remotely controllable by other health devices, health applications, or health actors, in the health-related network."@en;
rdfs:comment"The goal for which a device (e.g. a health device) is designed (from a user perspective). For example, a thermometer is designed for the task of measuring a temperature."@en;
rdfs: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.".
rdfs: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.";
rdfs:comment"The unit of measure is a standard for measurement of a quantity, such as a Property. For example, Power is a property and Watt is a unit of power that represents a definite predetermined power: when we say 10 Watt, we actually mean 10 times the definite predetermined power called \"watt\". Our definition is based on the definition of unit of measure in the Ontology of units of Measure (OM). We propose here a list of some units of measure that are relevant for the purpose of the Smart Appliances ontology, but this list can be extended."@en;
rdfs:isDefinedBysaref:;
rdfs:label"Unit of measure"@en.
### https://saref.etsi.org/s4ehaw/User
s4ehaw:Userrdf:typeowl:Class;
rdfs:subClassOfs4ehaw:HealthActor.
rdfs:subClassOfs4ehaw:HealthActor;
rdfs:comment"A health actor that is not a patient and is using BANs or health devices."@en;