Terminology Change Set Exchange
0.2.0 - CI Build International flag

Terminology Change Set Exchange, published by HL7 International - Termionology Infrastructure Work Group. This guide is not an authorized publication; it is the continuous build for version 0.2.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/tinkar-ig/ and changes regularly. See the Directory of published versions

FHIR Limitiations

Page standards status: Informative

Contents:

FHIR Limitations and Possible Solutions

Recognizing that FHIR's Terminology resources were not designed to enable collaboration between terminology authoring entities, there are several limitations implementers should be aware of when using FHIR for Terminology Change Set Exchange. Many of these limitations can be addressed through FHIR's inherent extensibility, but others are more difficult to address.

Limitations addressed via Extensions

Concept attributes

These are primary attributes directly related to concepts

  • Concept Additional Identifiers -

Concept description attributes

These are secondary attributes adding context to concept descriptions

  • Concept description dialect -
  • Concept description case sensitivity -
  • Concept description acceptability -

Concept property attributes

These are secondary attributes adding context to properties for concepts

  • Concept property defining relationship type -
  • Concept property EL++ profile set (Necessary vs. Sufficient) -
  • Concept Description Acceptability -

Other Limitations

Standardization of CodeSystem.property codes

HL7 has published some guidance on codes to use to represent properties from several terminologies (see: https://terminology.hl7.org/SNOMEDCT.html#snomed-ct-properties and https://terminology.hl7.org/LOINC.html#loinc-properties), but widespread implementations appear inconsistent. Additionally, any terminology exchange that lacks this standardization will likely struggle to convey semantic detail for concepts.

Change Sets with granularity below the concept level

As currently modelled, the smallest change that can be represented in a CodeSystem resource is a full "snapshot" representation of a Concept from that CodeSystem. If for example, the only change made to a Concept was a change to one of it's designation values, implementations would need to include the full semantic detail for that Concept in a Change Set. The specific change made would only be apparent via some comparison to the prior representation of the Concept"

Provanance to small changes

In the situation where multiple small changes were authored by several individuals, there are limits to how those changes can be referenced via a Provenance resource. Recognizing that with FHIR R5 a common extension was published allowing Provenances to reference elements within a resource (https://hl7.org/fhir/extensions/StructureDefinition-targetElement.html), even this approach is limited to those elements that have id attributes. In a CodeSystem change set instance, the most granular structure a Provenance could refer to using this approach would be an individual CodeSystem.concept, and changes specifically to sub-elements such as a Concept designation can not be indicated in this way.