Alignment with the DOLCE upper ontology

Every upper-level concept in the model is aligned with DOLCE — the Descriptive Ontology for Linguistic and Cognitive Engineering standardised in ISO/IEC 21838-3:2023 — giving the concept system a formally validated backbone.

A domain concept system is only as sound as the categories beneath it. For the 2026 edition, the upper-level concepts and their definitions were aligned with the DOLCE top-level ontology as defined in ISO/IEC 21838-3:2023 — itself built on the requirements for top-level ontologies in ISO/IEC 21838-1:2021 — and DOLCE was used to structurally validate the continuity model. In other words, the distinctions the model draws between things like persons, organisations, activities, processes, states, plans, and information objects are not ad hoc: each is anchored to a rigorously defined top-level category.

Figure 1. Model concepts in relation to DOLCE
Model concepts in relation to DOLCEDiagram relating the model's upper-level concepts to the top-level categories of the DOLCE ontology from ISO/IEC 21838-3, with each concept anchored by generalisation beneath a DOLCE category. THE MODEL’S CONCEPTS ANCHORED IN DOLCE thing (OWL) stative role physical object mental object social object abstract quality event (DOLCE-Lite) (DOLCE-Lite) (DOLCE-Lite) (DOLCE-Lite) (DOLCE-Lite) (DOLCE-Lite) (DOLCE-Lite) state (DOLCE-Lite) process (DOLCE-Lite) health state subject of care desire health need social need care process care actor subject of care medical device medicinal product person data repository care pathway care plan care record extract health circumstance knowledge mandate care employment care professional entitlement subject of care proxy care mandate organization risk unintended event appointment demand for care health related period care administration is a kind of (generalisation) DOLCE-Lite top-level category — ISO/IEC 21838-3 upper-level concept of the conformant model — ISO 13940 Every upper-level concept of the model is anchored beneath a DOLCE top-level category (after the informative Annex B of ISO 13940:2026).

The standard's master drawing of this alignment appears full-size in The master diagrams.

Why an upper ontology matters

  • Structural validation. Anchoring every concept to a top-level category exposes category errors — an "activity" that is really a document, a "state" that is really an event — before they harden into interfaces and data.
  • Safe extension. When local concepts must be added, the DOLCE backbone dictates where they belong, so extensions stay consistent with the core rather than drifting away from it.
  • Reliable mapping. Terminologies, other standards, and other ontologies that share (or can be related to) a top-level ontology can be mapped to the model with far greater confidence, because alignment is checked at the category level, not just by name similarity.
  • Readiness for machine reasoning. A concept system with formal ontological commitments is a sound basis for knowledge graphs, inference, and the automated consistency checking that large-scale interoperability increasingly demands.

Some ontological elements needed to understand the structure sit above the care domain itself; they can appear in the model's diagrams even though they are not care concepts. That is a feature of the approach: the care concepts stay focused on care, while the upper ontology quietly guarantees their coherence.