SAREF4EHAW extension has been specified and formalised by investigating EHAW domain related resources, as reported in ETSI TR 103 509 [2], such as: potential stakeholders, standardization initiatives, alliances/associations, European projects, EC directives, existing ontologies, and data repositories. Therefore, SAREF4EHAW modular ontology shall both:

SAREF4EHAW mainly reuses the following existing ontologies: SAREF (see [1]), SmartBAN (see [3]), SAREF4ENVI (see [4]), SAREF4WEAR (see [5]) and SAREF4health ontology [6] which is a very first try to somehow extend SAREF ontology for the health vertical (it has nothing to do with ETSI SAREF4ABCD naming convention). Figure 1 presents the high level view of the envisioned model of SAREF4EHAW ontology. In Figure 1, classes directly imported from SAREF ontology are in blue and classes specifically developed for SAREF4EHAW are in grey.

The SAREF4EHAW Model
Figure 1 - High level view of the envisioned semantic model for SAREF4EHAW ontology

Within Figure 1, as well as within all the figures that are depicted in clause 4 of the present document, the following conventions are used:

SAREF4EHAW is extending SAREF ontology for the EHAW vertical and thus shall logically mainly model the following concepts (i.e. classes within Figure 1):

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 be fully modelled (Service class and sub-classes depicted in Figure 1).

Finally, SAREF4EHAW is an OWL-DL ontology. For embedded semantic analytics purposes, SAREF4EHAW shall be designed using the modularity principle (see ETSI TR 103 509 [2]) 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.