Imagine walking through a shopping mall.
The building provides the structure: floors, corridors and individual shop units. But an empty shop does not yet tell us what may be offered inside it.
For that, the shop needs an agreed assortment.
An information model works in much the same way. It defines the elements that exist and what kind of information belongs in each one. A ValueSet provides a collection of possible coded values. Terminology binding connects that collection to a specific element and determines how it may or must be used there.
The model provides the shopping mall.
The element provides the shop.
A ValueSet defines what is available.
Terminology binding defines where it belongs.
That distinction matters.
A ValueSet can exist independently and may even be reused in several places. The binding gives it a concrete role by connecting it to a particular question, field or element within the model.
For example, a model may include an element for medication administration route. The ValueSet may contain codes such as oral, intravenous and subcutaneous. The terminology binding tells the system that these are the coded values intended for that specific element.
In FHIR, the strength of that binding matters too. A required binding allows only codes from the specified ValueSet. An extensible binding allows another code when the required meaning is not available within that ValueSet, while a preferred binding recommends the ValueSet without prohibiting alternatives.
These choices influence what clinicians can record, what systems can validate and whether exchanged information can be interpreted consistently.
Two systems may implement the same structural element and still capture different meaning if their terminology bindings differ.
Perhaps terminology binding is where an information model stops being an empty structure and begins to speak a shared clinical language.
The model provides the structure.
The binding gives it a language.
.
Next week: FHIR
Why does exchanging data not automatically create interoperability?
SemanticWeekly ConceptMap SemanticInteroperability HealthInformatics
