Lexicon · Ontology as economic infrastructure
Semantic interoperability
Fully specified name: Semantic interoperability (concept)
The capacity to exchange information while preserving intended meaning for a use.
- Scope note
- Successful transport does not demonstrate shared interpretation.
- Synonyms
- None recorded as true synonyms in this context.
- Monograph
- Semantic interoperability (planned; brief only)
- External mappings
- None recorded. In W0 no mapping to SNOMED CT® or any external authority is asserted for this entry. A future mapping record will carry source system, identifier, version, relation type, evidence, author, confidence where meaningful, and review state.
- Formal status
- Editorial entry only. It is not part of any released ontology and a prose edit here changes no formal definition.
Draft. This entry is an unreviewed draft. Its sources have not been checked by a named person and no domain reviewer has approved it. Treat every claim as provisional.
Notes
Interoperability is usually described in layers. Technical interoperability means two systems can connect and move bytes. Structural (or syntactic) interoperability means the receiving system can parse what arrives into the fields the sender intended; FHIR largely solves this for healthcare. Semantic interoperability means the receiving system, and the people who use it, interpret the content as the sender meant it, closely enough for the use at hand. The qualification "for a use" is deliberate: two systems may share meaning well enough for billing and not well enough for a dosimetry calculation.
The scope note is the economic point of this section. A successful message exchange is evidence of transport, not of understanding. A field labeled "administered activity" can arrive intact and still be interpreted in the wrong unit, at the wrong reference time, or for the wrong product, and the error is invisible until someone reconciles by hand. The cost of that reconciliation is where the case for shared meaning begins, and it has to be measured rather than assumed.
For a physician or physicist the relevance is concrete: a nuclear medicine report, a pharmacy record, and a research registry may each hold a true statement about the same administration and still disagree. The entries on Concept map and Data quality cover two of the tools used to narrow that gap; the monograph examines what evidence of benefit would look like.