dcterms: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.
dcterms:issued"date when the document is online"^^xsd:date;
dcterms:modified"do not set this"^^xsd:date;
dcterms:title"SAREF4EHAW: an extension of SAREF for eHealth Ageing Well domain"@en;
dcterms: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:
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.
- 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 1 “elderly at home monitoring and support”,
...
@@ -26,567 +41,371 @@ SAREF4EHAW extension has been specified and formalised by investigating EHAW dom
...
@@ -26,567 +41,371 @@ SAREF4EHAW extension has been specified and formalised by investigating EHAW dom
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.
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.
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 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>;
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:issued"date when the document is online"^^xsd:date;
dcterms:modified"do not set this"^^xsd:date;
dcterms:title"SAREF4EHAW: an extension of SAREF for eHealth Ageing Well domain"@en;
rdfs: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...)."@en;
rdfs:ranges4ehaw:ComputingPower;
rdfs:domains4ehaw:DeviceType.
### https://saref.etsi.org/saref4ehaw/consistsOf
s4ehaw:consistsOfrdf:typeowl:ObjectProperty;
rdfs:domains4ehaw:HealthDevice;
rdfs:ranges4ehaw:HealthDevice;
rdfs:comment"An eHealth device can be a composite health device that consists of one or multiple sub-devices."@en;
rdfs:label"consists of"@en.
### https://saref.etsi.org/s4ehaw/hasConstraint
s4ehaw:hasConstraintrdf:typeowl:ObjectProperty;
rdfs:label"has constraint"@en;
rdfs:comment"Data has constraints (validity, operating, security...)."@en;
rdfs:ranges4ehaw:Constraint;
rdfs:domains4ehaw:Data.
### https://saref.etsi.org/core/v3.1.1/contains
s4ehaw:containsrdf:typeowl:ObjectProperty;
rdfs:domains4ehaw:Ban;
rdfs:ranges4ehaw:HealthDevice;
rdfs:comment"A Body Area Network or BAN contains one or multiple health devices"@en;
rdfs:comment"A helper may follow one or multiple users that can in particular be patients."@en;
rdfs:label"follows user"@en.
s4ehaw:hasContactrdf:typeowl:ObjectProperty;
rdfs:label"has contact"@en;
rdfs: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)."@en;
rdfs: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...)."@en;
rdfs:comment"A health device has a device type describing the physical characteristics of the health device."@en;
rdfs:ranges4ehaw:Constraint;
rdfs:comment"Data has constraints (validity, operating, security...)."@en;
rdfs:ranges4ehaw:DeviceType;
rdfs:label"has constraint"@en.
rdfs:domains4ehaw:HealthDevice.
### https://saref.etsi.org/core/v3.1.1/hasContact
s4ehaw:hasContactrdf:typeowl:ObjectProperty;
rdfs:domains4ehaw:Ban;
rdfs:ranges4ehaw:Contact;
rdfs: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)."@en;
rdfs:label"has contact"@en.
### https://saref.etsi.org/s4ehaw/hasHub
s4ehaw:hasHubrdf:typeowl:ObjectProperty;
### https://saref.etsi.org/core/v3.1.1/hasData
s4ehaw:hasDatardf:typeowl:ObjectProperty;
rdfs:label"has hub"@en;
rdfs:domainsaref:Function;
rdfs:ranges4ehaw:Data;
rdfs:comment"A Body Area Network or BAN elects one hub that mainly plays the role of both a data concentrator and a network GW."@en;
rdfs:comment"A function has one or many data, for example a tracking function shall include latitude, longitude and speed data."@en;
rdfs: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..."@en;
rdfs:domains4ehaw:User;
rdfs:domains4ehaw:User;
rdfs:ranges4ehaw:Impairment;
rdfs:ranges4ehaw:Impairment.
rdfs: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..."@en;
rdfs: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)."@en;
rdfs:domains4ehaw:HealthDevice;
rdfs:domains4ehaw:HealthDevice;
rdfs:ranges4ehaw:Location;
rdfs:ranges4ehaw:Location.
rdfs: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)."@en;
rdfs:comment"Defines the relationship between data that has measurement."@en;
rdfs:domains4ehaw:Data;
rdfs:domains4ehaw:Data;
rdfs:rangesaref:Measurement;
rdfs:rangesaref:Measurement.
rdfs:comment"Defines the relationship between data that has measurement."@en;
rdfs:label"has measurement"@en.
### https://saref.etsi.org/s4ehaw/hasMode
### https://saref.etsi.org/core/v3.1.1/hasMode
s4ehaw:hasModerdf:typeowl:ObjectProperty;
s4ehaw:hasModerdf:typeowl:ObjectProperty;
rdfs:label"has mode"@en;
rdfs:comment"Each device type has modes of operations that model its dynamic characteristic varying during its lifetime, e.g. active, parked, sleeping..."@en;
rdfs:domains4ehaw:DeviceType;
rdfs:domains4ehaw:DeviceType;
rdfs:ranges4ehaw:Mode;
rdfs:ranges4ehaw:Mode.
rdfs:comment"Each device type has modes of operations that model its dynamic characteristic varying during its lifetime, e.g. active, parked, sleeping..."@en;
rdfs:comment"Defines the physical location of the patient, i.e. its postal address and/or its geolocation (when available)."@en;
rdfs:domains4ehaw:Patient;
rdfs:domains4ehaw:Patient;
rdfs:ranges4ehaw:PhysicalLocation;
rdfs:ranges4ehaw:PhysicalLocation.
rdfs:comment"Defines the physical location of the patient, i.e. its postal address and/or its geolocation (when available)."@en;
rdfs:label"has physical location"@en.
### https://saref.etsi.org/s4ehaw/hasPosture
### https://saref.etsi.org/core/v3.1.1/hasPosture
s4ehaw:hasPosturerdf:typeowl:ObjectProperty;
s4ehaw:hasPosturerdf:typeowl:ObjectProperty;
rdfs:label"has posture"@en;
rdfs: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..."@en;
rdfs:domains4ehaw:User;
rdfs:domains4ehaw:User;
rdfs:ranges4ehaw:Posture;
rdfs:ranges4ehaw:Posture.
rdfs: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..."@en;
rdfs: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...)."@en;
rdfs:domains4ehaw:DeviceType;
rdfs:domains4ehaw:DeviceType;
rdfs:ranges4ehaw:PowerSource;
rdfs:ranges4ehaw:PowerSource.
rdfs: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...)."@en;
rdfs: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."@en;
rdfs:domains4ehaw:Ban;
rdfs:domains4ehaw:Ban;
rdfs:ranges4ehaw:ResponsibleParty;
rdfs:ranges4ehaw:ResponsibleParty.
rdfs: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."@en;
rdfs:comment"Each eHealth device has modes of operations that model its dynamic characteristic varying during its lifetime, e.g. active, parked, sleeping..."@en;
rdfs:domains4ehaw:HealthDevice;
rdfs:domains4ehaw:HealthDevice;
rdfs:ranges4ehaw:Mode;
rdfs:ranges4ehaw:Mode.
rdfs:comment"Each eHealth device has modes of operations that model its dynamic characteristic varying during its lifetime, e.g. active, parked, sleeping..."@en;
rdfs:comment"A measurement fucntion, in case of complex measurement like time series, has frequency measurement, i.e. the frequency in which it makes measurements."@en;
rdfs:domains4ehaw:MeasurementFunction;
rdfs:domains4ehaw:MeasurementFunction;
rdfs:ranges4envi:FrequencyMeasurement;
rdfs:ranges4envi:FrequencyMeasurement.
rdfs:comment"A measurement fucntion, in case of complex measurement like time series, has frequency measurement, i.e. the frequency in which it makes measurements."@en;
rdfs: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."@en;
rdfs:rangexsd:string;
rdfs:rangexsd:string;
rdfs: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."@en;
rdfs:domains4ehaw:ServiceProcess.
rdfs:label"has calculation method"@en.
### https://saref.etsi.org/s4ehaw/hasEffect
### https://saref.etsi.org/core/v3.1.1/hasEffect
s4ehaw:hasEffectrdf:typeowl:DatatypeProperty;
s4ehaw:hasEffectrdf:typeowl:DatatypeProperty;
rdfs:domains4ehaw:ServiceProcess;
rdfs:label"has effect"@en;
rdfs:comment"The effect of a service can be an alert, nothing, an activation of another process..."@en;
rdfs:rangexsd:string;
rdfs:rangexsd:string;
rdfs:comment"The effect of a service can be an alert, nothing, an activation of another process..."@en;
rdfs: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."@en;
rdfs:rangexsd:string;
rdfs:rangexsd:string;
rdfs: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."@en;
rdfs:domains4ehaw:Ban.
rdfs:label"has geolocation"@en.
### https://saref.etsi.org/s4ehaw/hasInput
### https://saref.etsi.org/core/v3.1.1/hasInput
s4ehaw:hasInputrdf:typeowl:DatatypeProperty;
s4ehaw:hasInputrdf:typeowl:DatatypeProperty;
rdfs:domains4ehaw:ServiceProcess;
rdfs:label"has input"@en;
rdfs:comment"The service process has data input like e.g. the patient ID, the timestamp, the read value from a sensor..."@en;
rdfs:rangexsd:string;
rdfs:rangexsd:string;
rdfs:comment"The service process has data input like e.g. the patient ID, the timestamp, the read value from a sensor..."@en;
rdfs:domains4ehaw:ServiceProcess.
rdfs:label"has input"@en.
### https://saref.etsi.org/s4ehaw/hasMbox
### https://saref.etsi.org/core/v3.1.1/hasMbox
s4ehaw:hasMboxrdf:typeowl:DatatypeProperty;
s4ehaw:hasMboxrdf:typeowl:DatatypeProperty;
rdfs:domains4ehaw:HealthActor;
rdfs:label"has mbox"@en;
rdfs:comment"An email address (or mail box) of an health actor: a URI with the 'mailto' scheme as defined by RFC 6068."@en;
rdfs:rangexsd:anyURI;
rdfs:rangexsd:anyURI;
rdfs:comment"An email address (or mail box) of an health actor: a URI with the 'mailto' scheme as defined by RFC 6068."@en;
rdfs:domains4ehaw:HealthActor.
rdfs:label"has mbox"@en.
### https://saref.etsi.org/s4ehaw/hasOutput
### https://saref.etsi.org/core/v3.1.1/hasOutput
s4ehaw:hasOutputrdf:typeowl:DatatypeProperty;
s4ehaw:hasOutputrdf:typeowl:DatatypeProperty;
rdfs:domains4ehaw:ServiceProcess;
rdfs:label"has output"@en;
rdfs:comment"The output is e.g. the calculated value returned by the process, e.g the posture of a patient."@en;
rdfs:rangexsd:string;
rdfs:rangexsd:string;
rdfs:comment"The output is e.g. the calculated value returned by the process, e.g the posture of a patient."@en;
rdfs: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."@en;
rdfs:rangexsd:boolean;
rdfs:rangexsd:boolean;
rdfs: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."@en;
rdfs:domains4ehaw:Data.
rdfs:label"is derived data"@en.
### https://saref.etsi.org/s4ehaw/isGateway
### https://saref.etsi.org/core/v3.1.1/isGateway
s4ehaw:isGatewayrdf:typeowl:DatatypeProperty;
s4ehaw:isGatewayrdf:typeowl:DatatypeProperty;
rdfs:domains4ehaw:Interface;
rdfs:label"is gateway"@en;
rdfs:comment"This boolean variable indicates if the interface is a gateway or not."@en;
rdfs:rangexsd:boolean;
rdfs:rangexsd:boolean;
rdfs:comment"This boolean variable indicates if the interface is a gateway or not."@en;
rdfs:domains4ehaw:Interface.
rdfs:label"is gateway"@en.
### https://saref.etsi.org/s4ehaw/lastName
### https://saref.etsi.org/core/v3.1.1/lastName
s4ehaw:lastNamerdf:typeowl:DatatypeProperty;
s4ehaw:lastNamerdf:typeowl:DatatypeProperty;
rdfs:domains4ehaw:HealthActor;
rdfs:label"last name"@en;
rdfs:comment"The familly name of a health actor."@en;
rdfs:rangexsd:string;
rdfs:rangexsd:string;
rdfs:comment"The familly name of a health actor."@en;
rdfs:domains4ehaw:HealthActor.
rdfs:label"last name"@en.
### https://saref.etsi.org/s4ehaw/latency
### https://saref.etsi.org/core/v3.1.1/latency
s4ehaw:latencyrdf:typeowl:DatatypeProperty;
s4ehaw:latencyrdf:typeowl:DatatypeProperty;
rdfs:domains4ehaw:MeasurementFunction;
rdfs:label"latency"@en;
rdfs:comment"The latency is the time interval between the stimulation and response of a measurement function."@en;
rdfs:rangexsd:float;
rdfs:rangexsd:float;
rdfs:comment"The latency is the time interval between the stimulation and response of a measurement function."@en;
rdfs:domains4ehaw:MeasurementFunction.
rdfs:label"latency"@en.
### https://saref.etsi.org/s4ehaw/lifetime
### https://saref.etsi.org/core/v3.1.1/lifetime
s4ehaw:lifetimerdf:typeowl:DatatypeProperty;
s4ehaw:lifetimerdf:typeowl:DatatypeProperty;
rdfs:domains4ehaw:Ban;
rdfs:label"lifetime"@en;
rdfs: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."@en;
rdfs:rangexsd:dateTime;
rdfs:rangexsd:dateTime;
rdfs: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."@en;
rdfs:comment"The computing power capabilities of a Health device."@en;
rdfs:label"Computing power"@en;
rdfs:label"Computing power"@en.
rdfs:comment"The computing power capabilities of a Health device."@en.
### https://saref.etsi.org/s4ehaw/Constraint
### https://saref.etsi.org/core/v3.1.1/Constraint
s4ehaw:Constraintrdf:typeowl:Class;
s4ehaw:Constraintrdf:typeowl:Class;
rdfs:comment"The Data constraints, e.g. validity, operating, security..."@en;
rdfs:label"Constraint"@en;
rdfs:label"Constraint"@en.
rdfs:comment"The Data constraints, e.g. validity, operating, security..."@en.
### https://saref.etsi.org/s4ehaw/Contact
### https://saref.etsi.org/core/v3.1.1/Contact
s4ehaw:Contactrdf:typeowl:Class;
s4ehaw:Contactrdf:typeowl:Class;
rdfs:label"Contact"@en;
owl:equivalentClasss4ehaw:HealthActor;
owl:equivalentClasss4ehaw:HealthActor;
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"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"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: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/s4ehaw/Habit
### https://saref.etsi.org/core/v3.1.1/Habit
s4ehaw:Habitrdf:typeowl:Class;
s4ehaw:Habitrdf:typeowl:Class;
rdfs:comment"Defined for users (that can in particular be patients) habits modelling, e.g. smoking, alcohol drinking, overeating, undereating..."@en;
rdfs:label"Habit";
rdfs:label"Habit".
rdfs:comment"Defined for users (that can in particular be patients) habits modelling, e.g. smoking, alcohol drinking, overeating, undereating..."@en.
"Health-related Wearable, equivalent to SAREF4WEAR Wearable";
owl:equivalentClasss4wear:Wearable;
owl:equivalentClasss4wear:Wearable;
rdfs:subClassOfs4ehaw:HealthDevice;
rdfs:subClassOfs4ehaw:HealthDevice.
rdfs:label"Health wereable"@en,
"Health-related Wearable, equivalent to SAREF4WEAR Wearable".
### https://saref.etsi.org/s4ehaw/Helper
### https://saref.etsi.org/core/v3.1.1/Helper
s4ehaw:Helperrdf:typeowl:Class;
s4ehaw:Helperrdf:typeowl:Class;
rdfs:label"Helper"@en;
rdfs:subClassOfs4ehaw:HealthActor;
rdfs:subClassOfs4ehaw:HealthActor;
rdfs:comment"Helper of partients/users of a health system, e.g. a patient's relative."@en;
rdfs:comment"Helper of partients/users of a health system, e.g. a patient's relative."@en.
rdfs:label"Helper"@en.
### https://saref.etsi.org/s4ehaw/Impairment
### https://saref.etsi.org/core/v3.1.1/Impairment
s4ehaw:Impairmentrdf:typeowl:Class;
s4ehaw:Impairmentrdf:typeowl:Class;
rdfs: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..."@en;
rdfs:label"Impairment";
rdfs:label"Impairment".
rdfs: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..."@en.
rdfs:comment"An empty container for describing the legal constraints a data can be submitted to, like e.g. anonymization."@en;
rdfs:comment"An empty container for describing the legal constraints a data can be submitted to, like e.g. anonymization."@en.
rdfs:label"Legal constraint"@en.
### https://saref.etsi.org/s4ehaw/Location
### https://saref.etsi.org/core/v3.1.1/Location
s4ehaw:Locationrdf:typeowl:Class;
s4ehaw:Locationrdf:typeowl:Class;
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:label"Location"@en;
rdfs:label"Location"@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"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"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 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:label"Measurement function"@en.
### https://saref.etsi.org/core/v3.1.1/Mode
### https://saref.etsi.org/s4ehaw/Mode
s4ehaw:Moderdf:typeowl:Class;
s4ehaw:Moderdf:typeowl:Class;
rdf:comment"The dynamic characteristics of a eHealth Device that vary during its lifetime or its BAN lifetime."@en;
rdfs:label"Mode"@en;
rdfs:label"Mode"@en.
rdf:comment"The dynamic characteristics of a eHealth Device that vary during its lifetime or its BAN lifetime."@en.
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...)."@en;
rdfs:label"Power source"@en;
rdfs:label"Power source"@en.
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...)."@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 this concept is termed as Time Series Measurements since this sequence of data refers to time series measured by a health device.";
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 this concept is termed as Time Series Measurements since this sequence of data refers to time series measured by a health device.".
rdfs:label"Time series measurements".
### https://saref.etsi.org/s4ehaw/User
### https://saref.etsi.org/core/v3.1.1/User
s4ehaw:Userrdf:typeowl:Class;
s4ehaw:Userrdf:typeowl:Class;
rdfs:label"User"@en;
rdfs:subClassOfs4ehaw:HealthActor;
rdfs:subClassOfs4ehaw:HealthActor;
rdfs: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."@en;
rdfs: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."@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"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;
