TerminologyReport - Revision history

Mligtvoet: /* Terminology Report */

2020-02-15T22:21:39Z

‎Terminology Report

Mligtvoet: /* Terminology Report */

2019-09-03T08:50:16Z

‎Terminology Report

Mligtvoet: /* How to perform a Terminology Check */ added screenshots

2017-05-13T22:16:56Z

‎How to perform a Terminology Check: added screenshots

Ahenket: /* Terminology Association */

2017-04-21T13:43:55Z

‎Terminology Association

Kheitmann: /* Terminology Association */

2017-04-21T13:43:24Z

‎Terminology Association

Kheitmann at 13:42, 21 April 2017

2017-04-21T13:42:36Z

Ahenket at 13:41, 21 April 2017

2017-04-21T13:41:17Z

Kheitmann at 13:35, 21 April 2017

2017-04-21T13:35:42Z

Kheitmann: Created page with "=Terminology Report= It is possible to initiate a Terminology Report to check the terminologies used in a project. For projects with large value sets this can be a lengthy pro..."

2017-04-21T13:34:32Z

Created page with "=Terminology Report= It is possible to initiate a Terminology Report to check the terminologies used in a project. For projects with large value sets this can be a lengthy pro..."

New page

=Terminology Report=
It is possible to initiate a Terminology Report to check the terminologies used in a project. For projects with large value sets this can be a lengthy process.

The check can be performed calling the Terminology Report service, e.g. on the ART-DECOR main server at https://art-decor.org/decor/services/TerminologyReport.

A project must be chosen. The report type determines the type of report:
*'''overview''' will you both valuesets and terminology associations as described below
*'''valuesets''' will give you, as much as possible, differences between display names in the value set and the original display name from the codesystem. Look for @originalDisplayName in the result.
*'''terminologyassociations''' will give you, as much as possible, differences between display names in the terminology associations and the display name in the value set (if it links to a dataset conceptList/concept and the conceptList binds to a value set) or codesystem (if it links to a dataset concept). This option gives you best results when the valueSets are correct.

You can filter the report by specifying one or more code systems, multiple separate with a space in between, e.g. for SNOMED-CT and LOINC "2.16.840.1.113883.6.96 2.16.840.1.113883.6.1".

You can specify whether to show the report or to download it.

The following checks are performed.
#valueSet with concepts/exceptions using a different displayName than the original codeSystem (All active names SNOMED, others usually have only one
#terminologyAssociation[@code][@codeSystem] where
##the association is based on dataset//concept and the @displayName differs from the codeSystem or if it is a local codeSystem available only in a local valueSet, then if it differs from the name in that local valueSet
##the association is based on dataset//concept/conceptList/concept and the @displayName differs from the corresponding code in the valueSet that the conceptList is associated with, or if the conceptList doesn't have an association, then all local valueSets
#If a terminologyAssociation connects to a dataset//concept then behavior matches a valueSet:
**Get codeSystem names (e.g. SNOMED uses "http://[server]/terminology/snomed/getConcept/6797001")
**If I can get at least one lower-case match, all is well
**If there is none then for SNOMED the active fsn is returned or the only name in other cases (eg. LOINC) including status (if available)

If the terminologyAssociation is to a dataset//conceptList/concept:
*Search all local valueSets for the code+codeSystem
*If I can get at least one lower-case match, all is well
*If there is none, return all distinct matches from the valueSets

@@ Line 2: / Line 2: @@
 It is possible to initiate a Terminology Report to check the terminologies used in a project. The report detects whether a coded concept in a value set has an illegal display name or is deprecated and should no longer be used.
-Usually this check will be perfomed before creating a publication, as part of [[ART_Project_Editor#Preflighting_publication_and_quality_checks|Preflighting publication and quality checks]] but could of course be run more often.
+Usually a Terminology Report check will be perfomed before creating a publication, as part of [[ART_Project_Editor#Preflighting_publication_and_quality_checks|Preflighting publication and quality checks]] but could of course be run more often.
 For projects with large value sets this can be a lengthy process.

@@ Line 8: / Line 8: @@
 ==How to perform a Terminology Check==
 A project must be chosen.
 The report type determines the type of report:
@@ Line 17: / Line 19: @@
 You can specify whether to show the report or to download it.
 ==What is performed?==

@@ Line 29: / Line 29: @@
 #If a terminologyAssociation connects to a dataset//concept then behavior matches a valueSet:
 #*Get codeSystem names (e.g. SNOMED uses "http://[server]/terminology/snomed/getConcept/6797001")
-#*If I can get at least one lower-case match, all is well
+#*If it can get at least one lower-case match, all is well
-#*If there is none then for SNOMED the active fsn is returned or the only name in other cases (eg. LOINC) including status (if available)
+#*If there is none then for SNOMED the active ''Fully Specified Name'' (FSN) is returned or the only name in other cases (eg. LOINC) including status (if available)
 If the terminologyAssociation is to a dataset//conceptList/concept:
 *Search all local valueSets for the code+codeSystem
-*If I can get at least one lower-case match, all is well
+*If it can get at least one lower-case match, all is well
 *If there is none, return all distinct matches from the valueSets

@@ Line 25: / Line 25: @@
 ===Terminology Association===
 #terminologyAssociation[@code][@codeSystem] where
-**the association is based on dataset//concept and the @displayName differs from the codeSystem or if it is a local codeSystem available only in a local valueSet, then if it differs from the name in that local valueSet
+#*the association is based on dataset//concept and the @displayName differs from the codeSystem or if it is a local codeSystem available only in a local valueSet, then if it differs from the name in that local valueSet
-**the association is based on dataset//concept/conceptList/concept and the @displayName differs from the corresponding code in the valueSet that the conceptList is associated with, or if the conceptList doesn't have an association, then all local valueSets
+#*the association is based on dataset//concept/conceptList/concept and the @displayName differs from the corresponding code in the valueSet that the conceptList is associated with, or if the conceptList doesn't have an association, then all local valueSets
 #If a terminologyAssociation connects to a dataset//concept then behavior matches a valueSet:
-**Get codeSystem names (e.g. SNOMED uses "http://[server]/terminology/snomed/getConcept/6797001")
+#*Get codeSystem names (e.g. SNOMED uses "http://[server]/terminology/snomed/getConcept/6797001")
-**If I can get at least one lower-case match, all is well
+#*If I can get at least one lower-case match, all is well
-**If there is none then for SNOMED the active fsn is returned or the only name in other cases (eg. LOINC) including status (if available)
+#*If there is none then for SNOMED the active fsn is returned or the only name in other cases (eg. LOINC) including status (if available)
 If the terminologyAssociation is to a dataset//conceptList/concept:

@@ Line 17: / Line 17: @@
 #valueSet with concepts/exceptions using deprecated codes (if code system has status information at all)
 #terminologyAssociation[@code][@codeSystem] where
-**the association is based on dataset//concept and the @displayName differs from the codeSystem or if it is a local codeSystem available only in a local valueSet, then if it differs from the name in that local valueSet
+#*the association is based on dataset//concept and the @displayName differs from the codeSystem or if it is a local codeSystem available only in a local valueSet, then if it differs from the name in that local valueSet
-**the association is based on dataset//concept/conceptList/concept and the @displayName differs from the corresponding code in the valueSet that the conceptList is associated with, or if the conceptList doesn't have an association, then all local valueSets
+#*the association is based on dataset//concept/conceptList/concept and the @displayName differs from the corresponding code in the valueSet that the conceptList is associated with, or if the conceptList doesn't have an association, then all local valueSets
 #If a terminologyAssociation connects to a dataset//concept then behavior matches a valueSet:
-**Get codeSystem names (e.g. SNOMED uses "http://[server]/terminology/snomed/getConcept/6797001")
+#*Get codeSystem names (e.g. SNOMED uses "http://[server]/terminology/snomed/getConcept/6797001")
-**If I can get at least one lower-case match, all is well
+#*If I can get at least one lower-case match, all is well
-**If there is none then for SNOMED the active fsn is returned or the only name in other cases (eg. LOINC) including status (if available)
+#*If there is none then for SNOMED the active fsn is returned or the only name in other cases (eg. LOINC) including status (if available)
 If the terminologyAssociation is to a dataset//conceptList/concept: