Creating Value Set Data Types - Terminology Server

This guide explains how to create data types using value sets from an existing terminology, such as SNOMED, using the Terminology Server feature in MetadataWorks Exchange. By following these steps, users can easily reference and import value sets into their data models, allowing for more accurate and standardized data representation. This guide is essential for anyone looking to improve the quality and consistency of their data models by leveraging existing terminologies.

1. While logged in to the MetadataWorks Exchange, navigate to the Advanced View and select a data model.

2. Once you have navigated to the relevant data model, click on Data Types.

3. Click the green plus button to create a new Data Type.

4. Enter a name and/or description for your new Data Type.

5. Next, select Value Set from the Data Type options at the bottom of the window.

6. In order to access the value sets, you must enter an evaluated expression, for example:

expand?url=http://snomed.info/sct/83821000000107/version/20231122?fhir_vs&count=100&filter=occupation

The last part of this expression (occupation) can be edited according to the name of the value set you wish to reference (e.g.: diabetes, obesity or dementia).

For SNOMED, we recommend using the following ECL builder: https://ontoserver.csiro.au/shrimp/ecl/

7. In this case, we are creating a data type for diabetes data element, so the last part of the expression has been edited to "diabetes". When you are happy with your expression, click on Save.

8. The value sets from the SNOMED code have now been imported into your new data type as enumerations. This data type can now be linked with the appropriate data element(s).

Please note that this is a one-off import of the value sets. If the original values are updated externally, the import will need to be run again with the updated evaluation expression

e.g. in the example above, if value sets for Diabetes were imported from SNOMED V1.0.0, then if SNOMED released a V2.0.0 with new values for Diabetes, the import would need to be run again with the updated evaluated expression for this new version.