...
Consider the example of the SNOMEDCT to ICD10 mapping project. There is an infrequent and at most annual update to ICD10. The map projects and terminology content are "version aware", meaning there is a terminologyVersion field that must be maintained. Depending on choices made regarding this value, there are different strategies for ensuring the mapping tool has access to the intended version of the source terminologydestination terminology.
Maintaining terminologyVersion
...
- Remove the old version and import the new version
- This involves using the terminology remover to remove the prior version of the terminology and then completely reloading the release version using the corresponding terminology loader.
- This strategy works with either choice for "maintaining terminologyVersion" and guarantees the correctness of the terminology representation.
- Simply import the new version.
- This strategy only works well if using the style of "maintaining terminologyVersion" that involves having multiple simultaneous versions.
- This strategy is used for "SNOMEDCT to XXX" mappings.
Updating the map project
...
target terminology version
When using an actual terminology version value, when a new version of the terminology is loaded, the map project metadata must be updated to reflect the change in "destination terminology version". This can be done by an admin in the map project metadata editing tools.
...