The role of a conformant model

A model conformant to ISO 13940 acts as the shared semantic foundation on which information systems, integration programmes, service specifications, and analyses are built — the fixed point that keeps them all saying the same thing.

ContSys does not tell anyone how to deliver care, and it does not prescribe a database design. What it defines is the layer underneath both: the concepts and relationships that any description of care — a referral form, an API payload, a commissioning specification, a dashboard — is implicitly relying on. A conformant model makes that layer explicit and puts it under governance.

Figure 1. One semantic foundation beneath every use
One semantic foundation beneath every useLayered diagram: the DOLCE top-level ontology anchors and validates the conformant concept model, which in turn supplies the same concepts to information systems, record exchange, care service directories, specifications and commissioning, and analytics and policy. WHAT THE MODEL SUPPORTS Information systems & EHRs Record exchange FHIR · ISO 13606 Care service directories Specifications & commissioning Analytics, research & policy the same concepts behind every use Conformant concept model ISO 13940:2026 — shared system of concepts for continuity of care concepts relationships normative statements anchors and validates DOLCE top-level ontology ISO/IEC 21838-3 — formal categories beneath the concept system Conformance constrains meaning, not technology — implementations add detail without losing shared semantics.

Where the model earns its keep

  • Logical reference models. Within the information viewpoint of an architecture, the model provides the common basis for semantic interoperability at local, national, and international levels — every interface and dataset traces back to the same concept system.
  • Information system development. Analysts and suppliers design against agreed concepts such as episode of care, care mandate, or health condition assessment rather than reinventing (and subtly contradicting) them per project.
  • Specifying care process information. When a service defines what must be recorded for a given pathway, the model supplies precise building blocks — requests for care, reasons for request for care, care activities, intended outcomes — so the specification is complete and testable.
  • Service directories and signposting. The concept system includes care service offerings and care service directories, giving directory and referral infrastructure the same semantic anchor as record systems.
  • Analysis, planning, and policy. Because the concepts are independent of any software, the same model supports business analysis, organisational decision-making, and the secondary use of care data.

What conformance means in practice

The standard states, concept by concept, the generalisations and relationships that a supporting product must uphold — for instance that a particular kind of plan must address a particular kind of issue. A conformant model honours those normative statements. It remains free to add the attributes, identifiers, and implementation detail that a working system needs; conformance constrains meaning, not technology. The result is a model that can be re-platformed, extended, and mapped to new partners without renegotiating its semantics each time.