This wiki has undergone a migration to Confluence found Here
Difference between revisions of "TerminologyStrategy"
Jump to navigation
Jump to search
| Line 18: | Line 18: | ||
! Conformance | ! Conformance | ||
! Info | ! Info | ||
| + | ! Searchable (Y/N) | ||
|- | |- | ||
| Code | | Code | ||
| Line 23: | Line 24: | ||
| M | | 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. | | 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. | ||
| + | | Y | ||
|- | |- | ||
| Code System | | Code System | ||
| Line 28: | Line 30: | ||
| M | | 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. | | 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. | ||
| + | | Y | ||
|- | |- | ||
| Code System Version | | Code System Version | ||
| Line 33: | Line 36: | ||
| O | | 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. | | 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. | ||
| + | | Y | ||
|- | |- | ||
| OID | | OID | ||
| Line 38: | Line 42: | ||
| M | | M | ||
| A globally unique string representing an ISO identifier for a code system. | | A globally unique string representing an ISO identifier for a code system. | ||
| + | | Y | ||
|} | |} | ||
| Line 47: | Line 52: | ||
! Conformance | ! Conformance | ||
! Documentation | ! Documentation | ||
| + | ! Searchable (Y/N) | ||
|- | |- | ||
| Value Set Name | | Value Set Name | ||
| Line 52: | Line 58: | ||
| M | | M | ||
| Name of the Value Set | | Name of the Value Set | ||
| + | | Y | ||
|- | |- | ||
| Binding Strength | | Binding Strength | ||
| Line 57: | Line 64: | ||
| M | | M | ||
| This is to indicate whether the value set can allow for local codes (CWE) or only the exact list of concepts in the value set (CNE). | | This is to indicate whether the value set can allow for local codes (CWE) or only the exact list of concepts in the value set (CNE). | ||
| + | | N | ||
|- | |- | ||
| Concept domain | | Concept domain | ||
| Line 62: | Line 70: | ||
| O | | O | ||
| Refer to the Concept Domain Template for Concept Domain meta data | | Refer to the Concept Domain Template for Concept Domain meta data | ||
| + | | y | ||
|- | |- | ||
| Binding Realm | | Binding Realm | ||
| Line 68: | Line 77: | ||
| If the value set is bound to a concept domain, what is the binding realm e.g. Universal, Example, or Representative. | | If the value set is bound to a concept domain, what is the binding realm e.g. Universal, Example, or Representative. | ||
CD.codeSystemVersion property in the V3 abstract datatypes. | CD.codeSystemVersion property in the V3 abstract datatypes. | ||
| + | | y | ||
|- | |- | ||
| OID | | OID | ||
| Line 73: | Line 83: | ||
| O | | O | ||
| A globally unique string representing an ISO identifier for a value set. | | A globally unique string representing an ISO identifier for a value set. | ||
| − | | | + | | Y |
| + | |} | ||
==== Concept Domain Template ==== | ==== Concept Domain Template ==== | ||
| Line 81: | Line 92: | ||
! Conformance | ! Conformance | ||
! Info | ! Info | ||
| + | ! Searchable (Y/N) | ||
|- | |- | ||
| Concept Domain Name | | Concept Domain Name | ||
| M | | M | ||
| Name of the Concept domain | | Name of the Concept domain | ||
| + | | Y | ||
|- | |- | ||
| Concept domain Definition | | Concept domain Definition | ||
| M | | M | ||
| Definition of the concept domain | | Definition of the concept domain | ||
| + | | Y | ||
|- | |- | ||
| Binding Realm | | Binding Realm | ||
| M | | M | ||
| Indicates the binding syntax depending which type of binding syntax is done - please refer to the Core Principles and Properties of Version 3 Models, section on Binding Vocabulary To Coded Model Elements. | | Indicates the binding syntax depending which type of binding syntax is done - please refer to the Core Principles and Properties of Version 3 Models, section on Binding Vocabulary To Coded Model Elements. | ||
| + | | Y | ||
|} | |} | ||
Revision as of 18:06, 17 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 | Searchable (Y/N) |
|---|---|---|---|---|
| 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. | Y |
| 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. | Y |
| 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. | Y |
| OID | String | M | A globally unique string representing an ISO identifier for a code system. | Y |
Value Set Template
| Element | Type | Conformance | Documentation | Searchable (Y/N) |
|---|---|---|---|---|
| Value Set Name | String | M | Name of the Value Set | Y |
| Binding Strength | Boolean (CNE or CWE) | M | This is to indicate whether the value set can allow for local codes (CWE) or only the exact list of concepts in the value set (CNE). | N |
| Concept domain | String | O | Refer to the Concept Domain Template for Concept Domain meta data | y |
| 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.
CD.codeSystemVersion property in the V3 abstract datatypes. |
y |
| OID | String | O | A globally unique string representing an ISO identifier for a value set. | Y |
Concept Domain Template
| Element | Conformance | Info | Searchable (Y/N) |
|---|---|---|---|
| Concept Domain Name | M | Name of the Concept domain | Y |
| Concept domain Definition | M | Definition of the concept domain | Y |
| Binding Realm | M | Indicates the binding syntax depending which type of binding syntax is done - please refer to the Core Principles and Properties of Version 3 Models, section on Binding Vocabulary To Coded Model Elements. | Y |
