Difference between revisions of "TerminologyStrategy"
Line 42: | Line 42: | ||
! Conformance | ! Conformance | ||
! Documentation | ! Documentation | ||
− | |||
− | |||
|- | |- | ||
| Value Set Name | | Value Set Name | ||
Line 49: | Line 47: | ||
| | | | ||
| | | | ||
+ | |- | ||
+ | |Binding Strength | ||
+ | |Boolean (CNE or CWE) | ||
+ | | M | ||
| | | | ||
|- | |- | ||
− | | | + | | Concept domain |
− | | | + | | String |
− | | | + | | O |
− | | | + | | Refer to the Concept Domain Template for Concept Domain meta data |
− | | | + | |- |
+ | | Binding Realm | ||
+ | | String | ||
+ | | O | ||
+ | | If the value set is bound to a concept domain, what is the binding realm e.g. Universal, Example, or Representative. | ||
|} | |} | ||
+ | |||
==== Concept Domain Template ==== | ==== Concept Domain Template ==== | ||
Revision as of 19:53, 6 May 2010
Back to Templates Registry Pilot
Rob - you need to fill this in - ask Wendy for instructions. One important aspect is to describe the binding syntax discussion currently happening in the Vocab WG, and describe how it applies to a template registry.
Binding syntax - from HL7 perspective - Core Principles and Properties of V3 Models. Please note this material is going under HL7 normative ballot and is only linked here as a reference guide for binding syntax.
Meta Data Searching
Contents
Terminology Templates Searching Capability
Code System and Value Set meta data is drawn from the Templates Registry Business Requirement & Templates DSTU 2007 with the exception of Concept Domain - this vocabulary binding methodology was introduced by MnM & Vocab work groups subsequent to the Templates DSTU publication
Code System Template
Element | Type | Conformance | Info |
---|---|---|---|
Code | String | M | An expression in a syntax defined by the code system which describes the concept. Usually this would be a simple code, but post-coordinated expressions may also be used |
Code System | String | M | The identity of the codeSystem that defines the syntax and concepts used in the code. This must be a UID, as defined in the rules for the CD.codeSystem property in the V3 abstract datatypes. |
Code System Version | String | O | If applicable, a version descriptor defined specifically for the given code system. For further information, consult the rules for the CD.codeSystemVersion property in the V3 abstract datatypes. |
Value Set Template
Element | Type | Conformance | Documentation |
---|---|---|---|
Value Set Name | String | ||
Binding Strength | Boolean (CNE or CWE) | M | |
Concept domain | String | O | Refer to the Concept Domain Template for Concept Domain meta data |
Binding Realm | String | O | If the value set is bound to a concept domain, what is the binding realm e.g. Universal, Example, or Representative. |
Concept Domain Template
Element | Conformance | Info |
---|---|---|
Concept Domain Name | M | Name of the Concept domain |
Concept domain Definition | M | Definition of the concept domain |
Binding Realm | M | Indicates the binding syntax depending which type of bnindg syntax is done - please refer to the Core Principles and Properties of Version 3 Models, section on Binding Vocabulary To Coded Model Elements. |