{"id":43132,"date":"2026-10-16T09:55:34","date_gmt":"2026-10-16T07:55:34","guid":{"rendered":"https:\/\/smartdatamodels.org\/?p=43132"},"modified":"2026-10-14T23:58:55","modified_gmt":"2026-10-14T21:58:55","slug":"saref4ehaw-saref4wear-join-smart-data-models-41-candidate-models-for-ehealth-and-wearables","status":"publish","type":"post","link":"https:\/\/smartdatamodels.org\/index.php\/saref4ehaw-saref4wear-join-smart-data-models-41-candidate-models-for-ehealth-and-wearables\/","title":{"rendered":"SAREF4EHAW &#038; SAREF4WEAR Join Smart Data Models: 41 Candidate Models for eHealth and Wearables"},"content":{"rendered":"<p>Smart Data Models&#8217; <a href=\"https:\/\/github.com\/smart-data-models\/Candidates\">Candidates repository<\/a> now includes two more ETSI <strong>SAREF<\/strong> extensions, both from the health and personal-devices space: <strong><code>saref4ehaw<\/code><\/strong> and <strong><code>saref4wear<\/code><\/strong>, together<br \/>\ncontributing <strong>41 candidate models<\/strong>. Both ship the full Candidates artifact set \u2014 a JSON Schema, an NGSI-LD <code>@context<\/code>, and all four example serializations \u2014 validated against its own schema.<\/p>\n<h2 id=\"saref4ehaw-21-models\">SAREF4EHAW \u2014 21 models<\/h2>\n<p><a href=\"https:\/\/saref.etsi.org\/saref4ehaw\/v2.1.1\/\">SAREF4EHAW<\/a> (ETSI TS 103 410-8) is SAREF&#8217;s extension for <strong>eHealth and &#8220;ageing well&#8221; \/ active assisted living <\/strong>\u2014 the vocabulary behind remote health monitoring setups like a patient wearing a Body Area Network (BAN) of sensors, actuators, and wearables that funnel vital signs through a BAN hub to caregivers.<\/p>\n<table>\n<thead>\n<tr>\n<th>Category<\/th>\n<th>Models<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Actors<\/td>\n<td><code>HealthActor<\/code>, <code>Caregiver<\/code>, <code>Helper<\/code>, <code>User<\/code>, <code>Patient<\/code>, <code>ResponsibleParty<\/code><\/td>\n<\/tr>\n<tr>\n<td>Activity<\/td>\n<td><code>Activity<\/code>, <code>DailyActivity<\/code>, <code>NocturnalActivity<\/code><\/td>\n<\/tr>\n<tr>\n<td>Body Area Network<\/td>\n<td><code>Ban<\/code>, <code>BanApplicationTask<\/code>, <code>BanHub<\/code><\/td>\n<\/tr>\n<tr>\n<td>Devices<\/td>\n<td><code>HealthDevice<\/code>, <code>HealthActuator<\/code>, <code>HealthSensor<\/code>, <code>HealthWearable<\/code>, <code>FunctionalDevice<\/code><\/td>\n<\/tr>\n<tr>\n<td>Communication<\/td>\n<td><code>CommunicationInterface<\/code>, <code>CommunicationNetwork<\/code>, <code>CommunicationProtocol<\/code><\/td>\n<\/tr>\n<tr>\n<td>Observation<\/td>\n<td><code>ObservationCollectionExecution<\/code><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>A good chunk of this extension is pure specialization with no new properties of its own \u2014 <code>DailyActivity<\/code>, <code>HealthSensor<\/code>, <code>HealthActuator<\/code>,<code> HealthWearable<\/code>, <code>BanHub<\/code>, <code>Patient<\/code>, and <code>ResponsibleParty<\/code> all inherit everything from a richer parent class, and each candidate&#8217;s description explains exactly what it inherits rather than inventing properties that don&#8217;t exist in the ontology.<\/p>\n<p><a href=\"https:\/\/github.com\/smart-data-models\/Candidates\/tree\/master\/standards\/saref4ehaw\">https:\/\/github.com\/smart-data-models\/Candidates\/tree\/master\/standards\/saref4ehaw<\/a><\/p>\n<h2 id=\"saref4wear-20-models\">SAREF4WEAR \u2014 20 models<\/h2>\n<p><a href=\"https:\/\/saref.etsi.org\/saref4wear\/v2.1.1\/\">SAREF4WEAR<\/a> (ETSI TS 103 410-9) covers wearable technology more broadly \u2014 smartwatches, fitness bands, implantable health monitors, smart textiles, even crowd-control badges used by event staff. Devices are classified by how they relate to the body (in-body, on-body, near-body, textile\/fabric-integrated), linked to the &#8220;Wearer&#8221; they&#8217;re attached to, and described by the functions they perform (communicating, controlling, navigating, notifying) and the hardware components they&#8217;re built from.<\/p>\n<table>\n<thead>\n<tr>\n<th>Category<\/th>\n<th>Models<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Wearable-device family<\/td>\n<td><code>WearableDevice<\/code>, <code>InBodyWearable<\/code>, <code>OnBodyWearable<\/code>, <code>NearBodyWearable<\/code>, <code>TextileBasedWearable<\/code>, <code>FabricWearable<\/code><\/td>\n<\/tr>\n<tr>\n<td>Actors \/ features of interest<\/td>\n<td><code>Wearer<\/code>, <code>User<\/code>, <code>LivingOrganism<\/code>, <code>Software<\/code><\/td>\n<\/tr>\n<tr>\n<td>Hardware components<\/td>\n<td><code>Interface<\/code>, <code>PowerSupply<\/code>, <code>MemoryStorage<\/code>, <code>TextileBasedSensor<\/code><\/td>\n<\/tr>\n<tr>\n<td>Functions<\/td>\n<td><code>CommunicatingFunction<\/code>, <code>ControllingFunction<\/code>, <code>NavigatingFunction<\/code>, <code>NotifyingFunction<\/code><\/td>\n<\/tr>\n<tr>\n<td>Governance &amp; events<\/td>\n<td><code>Policy<\/code>, <code>Occurrence<\/code><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>The example data (a Garmin-style heart-rate monitor on a runner, an implanted glucose-style monitor, a crowd-control wearable detecting a restroom queue at a music festival) is drawn directly from the worked scenarios in the normative ETSI specification.<\/p>\n<p><a href=\"https:\/\/github.com\/smart-data-models\/Candidates\/tree\/master\/standards\/saref4wear\">https:\/\/github.com\/smart-data-models\/Candidates\/tree\/master\/standards\/saref4wear<\/a><\/p>\n<h2 id=\"translation-notes\">Translation notes<\/h2>\n<ul>\n<li><strong>Property-grouping classes flattened into plain attributes.<\/strong> Both ontologies classify measurable quantities (heart rate, battery level, air quality, soil moisture-style readings) using abstract grouping classes with no properties of their own, populated only by a handful of named individuals. Rather than mirroring that grouping hierarchy as<br \/>\nthin extra entities, each named individual became a directly-named attribute on the device\/wearer that carries it (e.g.<code> WearableDevice.batteryRemainingTime<\/code>, <code>Wearer.heartRate<\/code>) \u2014 the ontologies&#8217; own documentation explicitly endorses this as an open, non-exhaustive vocabulary rather than a closed enumeration.<\/li>\n<li><strong>TTL vs. normative-PDF discrepancies, documented rather than silently resolved.<\/strong> SAREF4EHAW&#8217;s PDF tables several properties (<code>hasHabit<\/code>, <code>hasInterface<\/code>, <code>availableFlash<\/code>&#8230;) with explicit domains that aren&#8217;t actually declared in the published <code>.ttl<\/code>; SAREF4WEAR has a comparable gap (<code>wearerRangeAge<\/code> in the PDF vs. <code>wearerAgeRange<\/code> in the<code> .ttl<\/code>). Every such gap is flagged plainly in the affected property&#8217;s<br \/>\nschema description and in <code>standard-metadata.yaml<\/code>, with the <code>.ttl<\/code><br \/>\ntreated as authoritative.<\/li>\n<li><strong>One real naming collision found.<\/strong> Smart Data Models&#8217; own<code> dataModel.Hl7<\/code> already publishes a <code>Patient<\/code> model (the full FHIR resource). SAREF4EHAW&#8217;s <code>Patient<\/code> is a much narrower concept \u2014 a thin, zero-own-property &#8220;cared-for person&#8221; \u2014 kept under its own name per the translation policy, with the collision flagged for reconciliation before promotion out of Candidates.<\/li>\n<li><strong>Privacy-conscious examples.<\/strong> Given the personal-health subject matter, every SAREF4EHAW example uses clearly synthetic, non-identifying placeholder data.<\/li>\n<\/ul>\n<h2 id=\"try-it-and-tell-us-whats-missing\">Try it, and tell us what&#8217;s missing<\/h2>\n<p>These are <strong>Candidates<\/strong> \u2014 first, carefully-sourced translations, not yet promoted to official Smart Data Models subjects. The <code>Patient<\/code> naming collision above is the main open item before promotion.<\/p>\n<p>Browse the models, open an issue, or send a PR:<br \/>\n\ud83d\udc49 <a href=\"https:\/\/github.com\/smart-data-models\/Candidates\/tree\/master\/standards\/saref4ehaw\">https:\/\/github.com\/smart-data-models\/Candidates\/tree\/master\/standards\/saref4ehaw<\/a><\/p>\n<p>\ud83d\udc49 <a href=\"https:\/\/github.com\/smart-data-models\/Candidates\/tree\/master\/standards\/saref4wear\">https:\/\/github.com\/smart-data-models\/Candidates\/tree\/master\/standards\/saref4wear<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Smart Data Models&#8217; Candidates repository now includes two more ETSI SAREF extensions, both from the health and personal-devices space: saref4ehaw and saref4wear, together contributing 41 candidate models. Both ship the full Candidates artifact set \u2014 a JSON Schema, an NGSI-LD @context, and all four example serializations \u2014 validated against its&#8230; <a class=\"continue-reading-link\" href=\"https:\/\/smartdatamodels.org\/index.php\/saref4ehaw-saref4wear-join-smart-data-models-41-candidate-models-for-ehealth-and-wearables\/\">More&#8230;<\/a><\/p>\n","protected":false},"author":15,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[86,182],"tags":[],"class_list":["post-43132","post","type-post","status-publish","format-standard","hentry","category-device","category-smarthealth"],"jetpack_publicize_connections":[],"jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":43130,"url":"https:\/\/smartdatamodels.org\/index.php\/saref4city-saref4inma-join-smart-data-models-35-candidate-models-for-smart-cities-and-manufacturing\/","url_meta":{"origin":43132,"position":0},"title":"SAREF4CITY &#038; SAREF4INMA Join Smart Data Models: 35 Candidate Models for Smart Cities and Manufacturing","author":"Agent","date":"18\/10\/2026","format":false,"excerpt":"Smart Data Models' Candidates repository now includes two more ETSI SAREF extensions: saref4city and saref4inma, together contributing 35 candidate models. Both ship the full Candidates artifact set \u2014 a JSON Schema, an NGSI-LD @context, and all four example serializations \u2014 validated against its own schema. SAREF4CITY \u2014 14 models SAREF4CITY\u2026","rel":"","context":"In &quot;Manufacturing&quot;","block_context":{"text":"Manufacturing","link":"https:\/\/smartdatamodels.org\/index.php\/category\/manufacturing\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":43133,"url":"https:\/\/smartdatamodels.org\/index.php\/saref4watr-saref4grid-join-smart-data-models-89-candidate-models-for-water-and-smart-grid-metering\/","url_meta":{"origin":43132,"position":1},"title":"SAREF4WATR &#038; SAREF4GRID Join Smart Data Models: 89 Candidate Models for Water and Smart Grid Metering","author":"Agent","date":"15\/10\/2026","format":false,"excerpt":"Smart Data Models' Candidates repository now includes two more ETSI SAREF extensions, both built around smart metering: saref4watr and saref4grid, together contributing 89 candidate models \u2014 the largest pair in this translation round. Both ship the full Candidates artifact set \u2014 a JSON Schema, an NGSI-LD @context, and all four\u2026","rel":"","context":"In &quot;Energy&quot;","block_context":{"text":"Energy","link":"https:\/\/smartdatamodels.org\/index.php\/category\/energy\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":43129,"url":"https:\/\/smartdatamodels.org\/index.php\/saref4ener-saref4envi-join-smart-data-models-116-candidate-models-for-energy-flexibility-and-environment\/","url_meta":{"origin":43132,"position":2},"title":"SAREF4ENER &#038; SAREF4ENVI Join Smart Data Models: 116 Candidate Models for Energy Flexibility and Environment","author":"Agent","date":"14\/10\/2026","format":false,"excerpt":"Smart Data Models' Candidates repository now includes two new candidate standards translated from ETSI's SAREF (\"Smart Applications REFerence\") ontology family: saref4ener and saref4envi, together contributing 116 candidate models. Both are official ETSI Technical Specifications, each with a normative PDF and a published Turtle\/JSON-LD\/RDF-XML ontology, and both ship the full Candidates\u2026","rel":"","context":"In &quot;Energy&quot;","block_context":{"text":"Energy","link":"https:\/\/smartdatamodels.org\/index.php\/category\/energy\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":43131,"url":"https:\/\/smartdatamodels.org\/index.php\/saref4agri-saref4auto-join-smart-data-models-58-candidate-models-for-precision-agriculture-and-connected-vehicles\/","url_meta":{"origin":43132,"position":3},"title":"SAREF4AGRI &#038; SAREF4AUTO Join Smart Data Models: 58 Candidate Models for Precision Agriculture and Connected Vehicles","author":"Agent","date":"17\/10\/2026","format":false,"excerpt":"Smart Data Models' Candidates repository now includes two more ETSI SAREF extensions: saref4agri and saref4auto, together contributing 58 candidate models. Both ship the full Candidates artifact set \u2014 a JSON Schema, an NGSI-LD @context, and all four example serializations \u2014 validated against its own schema. SAREF4AGRI \u2014 21 models SAREF4AGRI\u2026","rel":"","context":"In &quot;Agrifood&quot;","block_context":{"text":"Agrifood","link":"https:\/\/smartdatamodels.org\/index.php\/category\/agrifood\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":38306,"url":"https:\/\/smartdatamodels.org\/index.php\/introducing-the-smart-data-models-candidates-repository\/","url_meta":{"origin":43132,"position":4},"title":"Introducing the Smart Data Models Candidates Repository","author":"Agent","date":"22\/07\/2026","format":false,"excerpt":"The Smart Data Models now has a Candidates repository \u2014 a low-friction entry point where any existing standard, ontology or open dataset can be translated into the SDM shape (JSON Schema + NGSI-LD context + examples) before anyone commits to the full contribution process. The first entry, translated from the\u2026","rel":"","context":"In &quot;contribution&quot;","block_context":{"text":"contribution","link":"https:\/\/smartdatamodels.org\/index.php\/category\/contribution\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/smartdatamodels.org\/wp-content\/uploads\/2026\/07\/Gemini_Generated_Image_38hkfh38hkfh38hk-300x164.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/smartdatamodels.org\/wp-content\/uploads\/2026\/07\/Gemini_Generated_Image_38hkfh38hkfh38hk-300x164.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/smartdatamodels.org\/wp-content\/uploads\/2026\/07\/Gemini_Generated_Image_38hkfh38hkfh38hk-300x164.png?resize=525%2C300&ssl=1 1.5x"},"classes":[]},{"id":40343,"url":"https:\/\/smartdatamodels.org\/index.php\/gaia-x-ontology-joins-smart-data-models-165-candidate-models-for-cloud-connectivity-trust\/","url_meta":{"origin":43132,"position":5},"title":"Gaia-X Ontology Joins Smart Data Models: 165 Candidate Models for Cloud, Connectivity &#038; Trust","author":"maestro","date":"20\/08\/2026","format":false,"excerpt":"Smart Data Models' Candidates repository now includes a new candidate standard, gaiax-ontology-v2111, translated from the Gaia-X ontology v2111 \u2014 the vocabulary behind Self-Descriptions in Gaia-X federated data spaces and cloud ecosystems. All 165 classes published at docs.gaia-x.eu\/ontology\/v2111\/classes now have an NGSI-LD \/ NGSI-v2 representation. What's in it Gaia-X's ontology is\u2026","rel":"","context":"In &quot;Cross Sector&quot;","block_context":{"text":"Cross Sector","link":"https:\/\/smartdatamodels.org\/index.php\/category\/cross-sector\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/smartdatamodels.org\/wp-content\/uploads\/2026\/08\/Gemini_Generated_Image_3gnhx13gnhx13gnh-300x300.jpeg?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]}],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/posts\/43132","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/users\/15"}],"replies":[{"embeddable":true,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/comments?post=43132"}],"version-history":[{"count":2,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/posts\/43132\/revisions"}],"predecessor-version":[{"id":43155,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/posts\/43132\/revisions\/43155"}],"wp:attachment":[{"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/media?parent=43132"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/categories?post=43132"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/tags?post=43132"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}