DECOR-terminology - Revision history

Admin at 12:37, 21 May 2021

2021-05-21T12:37:41Z

Mligtvoet: /* @exeption */ typo

2019-04-02T19:52:47Z

‎@exeption: typo

Ahenket: /* @experimental */

2019-01-16T17:24:41Z

‎@experimental

Ahenket: /* @versionLabel */

2019-01-16T17:24:18Z

‎@versionLabel

Ahenket: /* @exeption */

2019-01-16T17:22:23Z

‎@exeption

Ahenket: /* @equivalence */

2018-08-24T14:56:14Z

‎@equivalence

Ahenket: /* @strength */

2018-08-24T14:55:58Z

‎@strength

Ahenket: /* @effectiveDate, @expirationDate */

2018-08-24T14:49:16Z

‎@effectiveDate, @expirationDate

Admin at 15:58, 21 May 2016

2016-05-21T15:58:12Z

Admin: /* Examples */

2013-06-09T19:27:21Z

‎Examples

@@ Line 287: / Line 287: @@
 ===@code, @codeSystem, @displayName===
-A specific @code from a @codeSystem may be used to link to a concept. The concept denoted in @conceptId is typically a concept from a concept list of a coded data element. A displayName may be used to override the displayName as defined for the code in the codeSystem. This may be a localization or a synonym, but should in now way alter the semantics of the coded concept.
+A specific @code from a @codeSystem may be used to link to a concept. The concept denoted in @conceptId is typically a concept from a concept list of a coded data element. A displayName may be used to override the displayName as defined for the code in the codeSystem. This may be a localization or a synonym, but should in no way alter the semantics of the coded concept.
 ===@effectiveDate, @expirationDate===
@@ Line 328: / Line 328: @@
 ===@equivalence===
-Details of how two concepts map to each other, the source is : relatedto | equivalent | equal | wider | subsumes | narrower | specializes | inexact | unmatched | disjoint; See also FHIR ConceptMapEquivalence http://hl7.org/fhir/concept-map-equivalence; Releationship with "ISO/TR 12300:2014 Health informatics, Principles of mapping between terminological systems" is also indicated
+Details of how two concepts map to each other, the source is : relatedto | equivalent | equal | wider | subsumes | narrower | specializes | inexact | unmatched | disjoint; See also FHIR ConceptMapEquivalence http://hl7.org/fhir/concept-map-equivalence; Relationship with "ISO/TR 12300:2014 Health informatics, Principles of mapping between terminological systems" is also indicated
 {| class="artdecorwiki"

@@ Line 154: / Line 154: @@
 An optional static or dynamic binding for the value set that is included. Default value is 'dynamic', meaning: ''the latest available version''.
-=====@exeption=====
+=====@exception=====
 An optional boolean value that determines if the included value sets coded concepts should be included as exceptions or as regular coded concepts. Note that this ''switch'' applies to all coded concepts in the included value set. Default is ''false''.

@@ Line 68: / Line 68: @@
 ===@experimental===
-DECOR project, codeSystem, valueSet or other artifact is for testing purposes, not real usage. Note that all artifacts in an experimental project are also considered experimental.
+Value set is for testing purposes, not real usage. Note that all artifacts in an experimental project are also considered experimental.
 ==Sub-elements of value set==

@@ Line 66: / Line 66: @@
 ===@versionLabel===
 The optional human readable version label for the value set to be able to determine the correct version of a value set. This is not intended for machine processing.
 ==Sub-elements of value set==

@@ Line 153: / Line 153: @@
 =====@exeption=====
 An optional boolean value that determines if the included value sets coded concepts should be included as exceptions or as regular coded concepts. Note that this ''switch'' applies to all coded concepts in the included value set. Default is ''false''.
 ===Examples===

@@ Line 319: / Line 319: @@
 {| class="artdecorwiki"
-! align="left" width="5%" | Datatype !! align="left" width="10%" | Nederlands !! align="left" width="10%" | Deutsch !! align="left" width="40%" |Description
+! align="left" width="5%" | Mnemonic !! align="left" width="10%" | Nederlands !! align="left" width="10%" | Deutsch !! align="left" width="40%" |Description
 |-
 | bgcolor="#eee" valign="top" id="count" | '''relatedto'''

← Older revision		Revision as of 14:49, 24 August 2018
Line 287:		Line 287:
	code="SRG" codeSystem="2.16.840.1.113883.2.4.3.22.99.2.1"/>		code="SRG" codeSystem="2.16.840.1.113883.2.4.3.22.99.2.1"/>
	</syntaxhighlight>		</syntaxhighlight>
		+
		+	===@strength===
		+	Coding strength of a vocabulary binding to a value set
		+
		+	{\| class="artdecorwiki"
		+	! align="left" width="5%" \| Datatype !! align="left" width="10%" \| Nederlands !! align="left" width="10%" \| Deutsch !! align="left" width="40%" \|Description
		+	\|-
		+	\| bgcolor="#eee" valign="top" id="count" \| '''required'''
		+	\| valign="top" \|verplicht
		+	\| valign="top" \|Erforderlich
		+	\|Required (formerly known as CNE). Coded with no exceptions; this element SHALL be from the specified value set
		+	\|-
		+	\| bgcolor="#eee" valign="top" id="count" \| '''extensible'''
		+	\| valign="top" \|uitbreidbaar
		+	\| valign="top" \|Erweiterbar
		+	\|Extensible (formally known as CWE). Coded with Exceptions; this element SHALL be from the specified value set if any of the codes within the value set can apply to the concept being communicated. If the value set does not cover the concept (based on human review), alternate codings (or, data type allowing, text) may be included instead.
		+	\|-
		+	\| bgcolor="#eee" valign="top" id="count" \| '''preferred'''
		+	\| valign="top" \|Voorkeur
		+	\| valign="top" \|Bevorzugt
		+	\|Preferred. Instances are encouraged to draw from the specified codes for interoperability purposes but are not required to do so to be considered conformant.
		+	\|-
		+	\| bgcolor="#eee" valign="top" id="count" \| '''example'''
		+	\| valign="top" \|voorbeeld
		+	\| valign="top" \|Beispiel
		+	\|Example. Instances are not expected or even encouraged to draw from the specified value set. The value set merely provides examples of the types of concepts intended to be included.
		+	\|}
		+
		+	===@equivalence===
		+	Details of how two concepts map to each other, the source is : relatedto \| equivalent \| equal \| wider \| subsumes \| narrower \| specializes \| inexact \| unmatched \| disjoint; See also FHIR ConceptMapEquivalence http://hl7.org/fhir/concept-map-equivalence; Releationship with "ISO/TR 12300:2014 Health informatics, Principles of mapping between terminological systems" is also indicated
		+
		+	{\| class="artdecorwiki"
		+	! align="left" width="5%" \| Datatype !! align="left" width="10%" \| Nederlands !! align="left" width="10%" \| Deutsch !! align="left" width="40%" \|Description
		+	\|-
		+	\| bgcolor="#eee" valign="top" id="count" \| '''relatedto'''
		+	\| valign="top" \|gerelateerd aan
		+	\| valign="top" \|verwandt mit
		+	\|The concepts are related to each other, and have at least some overlap in meaning, but the exact relationship is not known
		+	\|-
		+	\| bgcolor="#eee" valign="top" id="count" \| '''equivalent'''
		+	\| valign="top" \|equivalent
		+	\| valign="top" \|äquivalent
		+	\|The definitions of the concepts mean the same thing (including when structural implications of meaning are considered) (i.e. extensionally identical). / ISO 12300: 2 = Equivalence of meaning, but with synonymy. For example, ureteric calculus and ureteric stone; gall stones and cholelithiasis.
		+	\|-
		+	\| bgcolor="#eee" valign="top" id="count" \| '''equal'''
		+	\| valign="top" \|gelijk
		+	\| valign="top" \|gleich
		+	\|The definitions of the concepts are exactly the same (i.e. only grammatical differences) and structural implications of meaning are identical or irrelevant (i.e. intentionally identical). / ISO 12300: 1 = Equivalence of meaning; lexical, as well as conceptual. For example, asthma and asthma; ovarian cyst and cyst of ovary.
		+	\|-
		+	\| bgcolor="#eee" valign="top" id="count" \| '''wider'''
		+	\| valign="top" \|breder
		+	\| valign="top" \|breiter
		+	\|The target mapping is wider in meaning than the source concept. / ISO 12300: 3 = Source concept is broader and has a less specific meaning than the target concept/term. For example, obesity and morbid obesity; diabetes and diabetes mellitus type II.
		+	\|-
		+	\| bgcolor="#eee" valign="top" id="count" \| '''subsumes'''
		+	\| valign="top" \|omvat
		+	\| valign="top" \|umfasst
		+	\|The target mapping subsumes the meaning of the source concept (e.g. the source is-a target).
		+	\|-
		+	\| bgcolor="#eee" valign="top" id="count" \| '''narrower'''
		+	\| valign="top" \|nauwer
		+	\| valign="top" \|enger
		+	\|The target mapping is narrower in meaning than the source concept. The sense in which the mapping is narrower SHALL be described in the comments in this case, and applications should be careful when attempting to use these mappings operationally. / ISO 12300: 4 = Source concept is narrower and has a more specific meaning than the target concept/term. For example, feels ugly and self-image finding; acute renal failure syndrome secondary to dehydration and acute renal failure syndrome.
		+	\|-
		+	\| bgcolor="#eee" valign="top" id="count" \| '''specializes'''
		+	\| valign="top" \|specialiseert
		+	\| valign="top" \|spezialisiert
		+	\|The target mapping specializes the meaning of the source concept (e.g. the target is-a source).
		+	\|-
		+	\| bgcolor="#eee" valign="top" id="count" \| '''inexact'''
		+	\| valign="top" \|onnauwkeurig
		+	\| valign="top" \|ungenau
		+	\|The target mapping overlaps with the source concept, but both source and target cover additional meaning, or the definitions are imprecise and it is uncertain whether they have the same boundaries to their meaning. The sense in which the mapping is narrower SHALL be described in the comments in this case, and applications should be careful when attempting to use these mappings operationally.
		+	\|-
		+	\| bgcolor="#eee" valign="top" id="count" \| '''unmatched'''
		+	\| valign="top" \|onvergelijkbaar
		+	\| valign="top" \|unvergleichbar
		+	\|There is no match for this concept in the destination concept system. / ISO 12300: 5 = No map is possible. No concept was found in the target with some degree of equivalence (as measured by any of the other four ratings).
		+	\|-
		+	\| bgcolor="#eee" valign="top" id="count" \| '''disjoint'''
		+	\| valign="top" \|elkaar uitsluitend
		+	\| valign="top" \|sich auschließend
		+	\|This is an explicit assertion that there is no mapping between the source and target concept.
		+	\|}

@@ Line 36: / Line 36: @@
 The mandatory status of a defining value set. According to the Business Requirements for Value Set Registries ART-DECOR uses the following subset of status codes of a value set (in bold).
-{|class=artdecor
+{|class="artdecorwiki"
 |-
 ! statusCode !! Description
@@ Line 121: / Line 121: @@
 A required code for the type of code as indicated by the code system. Valid values are:
-{|class=artdecor
+{|class="artdecorwiki"
 |-
 ! Type !! Description

@@ Line 243: / Line 243: @@
 '''Alternatively this same value set ActConsentTypeWithNulls could be done using:'''
-<syntaxhighlight lang="xml">
+<syntaxhighlight lang="xml" heading="Value Set that includes HL7 V3 Value Set adding NullFlavor UNK and OTH">
 <valueSet id="2.16.840.1.113883.2.4.999.1.2"
            name="ActConsentTypeWithNulls"