Difference between revisions of "DECOR-terminology"
(→@valueSet, @flexibility) |
(→@conceptId) |
||
| Line 6: | Line 6: | ||
==terminologyAssociation== | ==terminologyAssociation== | ||
===@conceptId=== | ===@conceptId=== | ||
| − | The id of the concept to which the terminology association is to be linked to. | + | The id of the concept to which the terminology association is to be linked to, i.e. a concept list or a specific concept of a coded data element. |
===@valueSet, @flexibility=== | ===@valueSet, @flexibility=== | ||
Revision as of 11:13, 29 April 2013
Contents
General
Holds code systems, value sets, and associations between dataset concepts and terminology.
Elements
valueSet
terminologyAssociation
@conceptId
The id of the concept to which the terminology association is to be linked to, i.e. a concept list or a specific concept of a coded data element.
@valueSet, @flexibility
Typically a @valueSet by name or by id may be used to be linked to a concept. The concept denoted in @conceptId is a concept list of a coded data element.
@flexibility is either "dynamic" to refer to the latest version of @valueSet or is a date (static reference) which means that the reference is made to a specific version of of @valueSet.
@code, @codeSystem
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.
@effectiveDate, @expirationDate
These two attribute relate to the terminology association itself: they are used to denote start and end date of the validation period of the respective terminology association
